Hello there,
what is the current state of 3D MVC capability on RPi4B? Has something had changed in the last three two months since the last post? Curious whether buying an RPi4B for 3D MVC is worth it already, or if it is still troublesome.
Hello there,
what is the current state of 3D MVC capability on RPi4B? Has something had changed in the last three two months since the last post? Curious whether buying an RPi4B for 3D MVC is worth it already, or if it is still troublesome.
I have never seen any 2160p60 H.264 content to be honest. All 2160p60 content is HEVC and as far as I know this is the only Codec that is intended for 2160p content. H.264 is an older codec that needs higher bitrates for comparable quality and as 2160p has four times the pixel count as 1080p (where H.264 was meant for) HEVC is the only sane way to go. That is why mostly no device supports H264 with a resolution of 2160p. It is not used by the industry, hence there is no content, thus no need to implement such capability in fixed hardware units.
I've been told that RPi4 will support open "static" metadata standards (HDR/HLG) not the commercial "dynamic" ones like Dolby Vision which would require a license fee to be paid on every board sold. Not sure about Atmos audio, but if it requires fees I'd expect the position to be the same. I've asked for a clarification.
While you are at it, could perhaps you ask if there was the possibility to make such an hypothecital Dolby Vision Licence available for purchase, just like the optional MPEG2 Licence, that one could buy for the old Raspberries? This would just be as awesome as Dolby Atmos Support
Thanks for this incredibly exciting news of the day!!
Thank you very much for your quick reply.
That's a real shame, since still all the blockbusters are still released on 3D BluRay and all those discs in so many users collections
Thank you through, and have a nice day
Happy to read about coming Support for Odroid N2
Any idea about probability of 3D MVC Support on Odroid N2? Something on the Roadmap regarding this?
Currently OSMC has almost finished its Support for 3D MVC and as their Vero is also based on AMLogic SoC there might perhaps be a soultion suitable for Odroid N2 or other S905yxz Hardware?
Cheers and my very best regards
Great to hear awiouy appreciate all your work on this!
Hi, since the maintainer (plietar) has left the librespot project, what is your opinion on the future of your LE addon?
Tested it 2 days ago. Cec seems not to work yet. I don't own a 4k tv, so cannot say anything about it.
But automatic framerate switching worked during my short test. HD-audio is not there yet, but is worked on. The device speed feels pretty similar to Odroid C2. As it's a veeeery early stage, we may not expect too much now.
me too, there are also some LibreElec-users, which are interested in 3D-MVC...
It isn't an issue for everyone, but for us...
Well, that's unfortunately nothing that kszaq could implement just by the way... I hoped/asked because I wanted to know whether there are some guys working or planning to work on that. Apparently nothing changed, so RPi2/3 is the way to go if needed this function.
According to this post Sam@OSMC is working on frame packed output for his S905x based Vero4K box. If we're lucky, this could happen to become the basis for frame packed in other similar SOCs like this S905 one in Odroid C2.
thanks kszaq.
Just wanted to ask whether there are any plans
Regarding the 3D topic: Are there any plans reganding Frame Packed output, as I've read it might be possible with nougat kernel basically? And as follow up to frame packing: Is there even something new about MVC, since frame packing would enable the technical basis for FullHD 3D encoded as MVC format, just like the RPi does?
Display MoreHere is a new preview release that attempts to solve two issues:
- latency in streaming to Kodi
- audio device not ready on service startup ( Camella)
On RPi2 latency is significantly improved
I have no hardware to test that audio device is ready before librespot service starts.
Thank you for you feedback.
Preview for RPi2 (should also run on Odroid_C2/arm)
This works great on my C2/arm! Virtually every isse is gone. It reacts reasonably fast to my phones control (skip, play/pause) and seeking is also working flawlessly done from my phone. Only glitches I see so far are that the shown elapsed time, which Kodi shows in current playing track (librespot) is always 2s ahead of the actual timestamp of the track: "04:11/4:13"- So the time after the slash is not that what I would expect, but that's not important.
Second thing is that "shuffle" and "repeat" buttons in Android app have no effect if pressed.
Awesome work, especially this 102b version!
Okay, I'm still a bit confused, sorry for that...
What is "spotify user" in your view?
So far I understood:
If my point 2.) is understood corretly by me. Then the unsuccessful control via smartphone app was caused by the changed api, or is this something that is still WIP? It is actually supposed to be controlled through, smartphone app, if issues are resolved, right?
And where do I find in kodi the currently played playlist? Is the playlist not present because the audio is simply streamed to kodi from librespot via via ffmpegx/RTP without further infos (e.g. playlist info and track info) as a pure audio-stream?
Thanks for your patience and the time you took to explain it
Since GDPR-1 released a new LE build, the kodi-output option finally started working
Now I see what the aim was, to include this function:
However there are some issues I'd like to mention and to get explained, if possible:
librespot.start
INFO:librespot: librespot ebeb776 (2017-07-08). Built on 2017-07-08.
*** WARNING *** The program 'librespot' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=librespot>
INFO:librespot::session: Connecting to AP "gew1-accesspoint-b-f822.ap.spotify.com:4070"
INFO:librespot::session: Authenticated as "*******" !
INFO:librespot::session: Country: "DE"
INFO:librespot::player: Loading track "C O O L"
INFO:librespot::player: Track "C O O L" loaded
INFO:librespot::util: Running kodi-send --action=RunAddon(service.librespot)
INFO:librespot::util: Exit status: exit code: 0
=== args='time_base=1/44100:sample_rate=44100:sample_fmt=s16:channel_layout=0x3'
=== args='sample_fmts=s16:'
[rtp @ 0x1644f30] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: WireError("invalid value for enum: 12")', /checkout/src/libcore/result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.
Display More
And a second attempt:
LibreELEC:~ # librespot.start
INFO:librespot: librespot ebeb776 (2017-07-08). Built on 2017-07-08.
*** WARNING *** The program 'librespot' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=librespot>
INFO:librespot::session: Connecting to AP "gew1-accesspoint-b-dz71.ap.spotify.com:4070"
INFO:librespot::session: Authenticated as "wmissal" !
INFO:librespot::session: Country: "DE"
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: WireError("invalid value for enum: 12")', /checkout/src/libcore/result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.
Two different issues here, apparently. And after that it dissappears again as available device in the smartphone app. Need to restart Kodi.
Independently from the other issues: Once the connection works the song starts playing after ca. 5s on Kodi and plays for about 3s. Then the sound disappears, the timestamps seem to jump betweet 4 and 5 seconds up and down (like a hickup without audio)... this takes about 5 seconds and then the song proceeds to play. Observed this many times.
Thats the log for this:
13:38:25.155 T:4100526080 NOTICE: VideoPlayer: Opening: special://profile/addon_data/service.librespot/librespot.sdp
13:38:25.155 T:4100526080 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
13:38:25.159 T:3459371936 NOTICE: Creating InputStream
13:38:25.163 T:3459371936 NOTICE: Creating Demuxer
13:38:26.257 T:3459371936 NOTICE: Opening stream: 0 source: 256
13:38:26.257 T:3459371936 NOTICE: Finding audio codec for: 65542
13:38:26.257 T:3459371936 NOTICE: Creating audio thread
13:38:26.258 T:3642401696 NOTICE: running thread: CVideoPlayerAudio::Process()
13:38:26.268 T:3642401696 NOTICE: Creating audio stream (codec id: 65542, channels: 2, sample rate: 44100, no pass-through)
13:38:26.277 T:3459371936 WARNING: CDVDMessageQueue(video)::Put MSGQ_NOT_INITIALIZED
13:38:30.085 T:3642401696 NOTICE: CVideoPlayerAudio::Process - stream stalled
Display More
"stream stalled"
In kodi the showed playtime does not display the correct values. It is simply proceeding and doesn't start counting from 0 after the next song starts playing. It is always showing proceeding times like this: 06:48/06:56 with a delta of 8s between both times.
That's a load of issues, so I guess it is platform specific here, isn't it?
Is this mmal thing something raspberry specific? How does your addon work then on aarch64 systems like the official 64bit C2 builds? Is mmal mandatory for it, also in the future?
Good that we know the issue now
Nice approach!
here you are (errors indeed):
LibreELEC:~ # librespot.start
ffmpegx: error while loading shared libraries: libmmal_core.so: cannot open shar ed object file: No such file or directory
INFO:librespot: librespot 3fd667b (2017-07-05). Built on 2017-07-05.
*** WARNING *** The program 'librespot' uses the Apple Bonjour compatibility lay er of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libd ns_sd&e=librespot>
INFO:librespot::session: Connecting to AP "gew1-accesspoint-b-xj7b.ap.spotify.co m:4070"
INFO:librespot::session: Authenticated as "*******" !
INFO:librespot::session: Country: "DE"
INFO:librespot::player: Loading track "Two Weeks"
INFO:librespot::player: Track "Two Weeks" loaded
INFO:librespot::util: Running kodi-send --action=RunAddon(service.librespot)
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr
INFO:librespot::util: Exit status: exit code: 0
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Err or { repr: Os { code: 32, message: "Broken pipe" } }', /checkout/src/libcore/res ult.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.
Display More
During this my Android app showed that track is playing on Librespot@LibreELEC. But actually it did not.
Then the device (Librespot@LibreELEC) disappeared from the overview of connect devices in android spotify app.
Hope this helps to narrow it down somehow.
Well yeah, he has it there, but I haven't installed it. Inputsteam.adaptive is the successor of inputstream.rtmp as far as I know.
Here's the log, where you can see which add-ons are installed: eOYE There is no inputstream.rtmp mentioned.
Nope, as far as I can see I have only inputstream.adaptive v1.0.8.
No other inputstream addons present.