@sixones I’m curious did they have anything to say about the MAT support not being detected correctly for TrueHD support?
Now i’m confused.
I though,t there were Kodi users who said that for them passthrough of DTS:X is working.
And, as has been said MANY times, including in this very thread, that is not relevant because Kodi uses a different method to perform pass-through. And that method is outside the Andriod development API’s.
Not only that, Kodi doesn’t work properly, at least for me on the cube.
Have a look at this:
https://forum.kodi.tv/showthread.php?tid=366954
If you use the Android IEC packer you get what is specified in the audio pass-through specs but if you use the Kodi IEC packer you can additionally pass through DTS-HD MA and X.
You can use latest Plex v9.0.6 and DTS HD MA works flawlessly with Cube 3rd gen
Since 9.1 it is broken. You can Google for kepler-armv7a-amazon-stdExo-9.0.6.31998-fa17c77a.apk
Use Xplore File Manager or any other to copy it via Wlan Server to Cube 3rd gen and install
PS. deactivate Automatic App Updates to avoid install of Plex v9.1 …
I’ll have to give it a try. Does it also fix TrueHD(works in Kodi but not in Plex)?
If anyone from Plex is reading this any chance of a new beta with this regression fixed?
Sry, TrueHD not working ![]()
No somewhere this thread went wrong and became personal attack on people not understanding plex.
The issue " DTS-HD passthrough not working on new Fire TV Cube (3rd)"
For me I get no sound\plex Crashes when playing such content. I wouldn’t care if it’s TRANSCODED, but still [not working] months later is pretty poor form.
Found a workaround: “Disable frame rate matching”
Hi, will there be a fix for Plex crashes\freezing playing DTS-HD content on the Fire Cube (3rd Gen)?
Current workaround, is to force transcoding (not all users know how), or disabling refresh rate switching.
To be fair I think this is actually Amazon or the silicon manufacturers fault and apparently this is pretty common across the Android ecosystem. Kodi cannot play either codec using the default system IEC packer that is part of the system image provided by Amazon(which is what Plex uses). The thing I don’t understand is why they can’t just copy and add the Kodi IEC packer into the Plex client as an option. It seems like it would be a win almost everywhere(as from reading the Kodi forums it seems they made this packer because it is a very common problem across many Android platforms that a broken or buggy IEC packer is provided by the vendor in the system image. The only things I can think of is perhaps Plex might have some corporate thing against the GPL or something like that which would be unfortunate. Or that perhaps it would require additional work in the A/V sync area or integration might be harder than I think(hard to tell since Plex doesn’t seem to have a github with their client source). One other thing to remember is even Kodi’s IEC packer is not 100%(although where it is broken the system one does work) so there is unfortunately no silver bullet.
I’m pretty sure the Plex client is closed source so adding anything from Kodi is a breach of copyright.
You can’t just use GPL code in other projects, you must satisfy the license requirement of making the code of the project it was added to available for others, among other requirements.
Yeah that is true but it really depends the legalities of it are really confusing. My Synology NAS is Linux based but they definitely do not provide source code for it and same thing with my cablebox, modem and probably a dozen things in my house that use GPL code.
There’s no confusion.
If you use code from a GPL licensed product the code in which it is used needs to be made available.
It is true that there are many cases where it is questionable whether people or companies are exposed to this legally but the requirement is clear and if Plex does this they are potentially exposed to legal action.
I do have some idea of these requirements since I’ve been an open source developer for around 40 years.
That is interesting. I’m curious now doesn’t Plex use ffmpeg to do audio conversions anyways which I thought was GPL as well. I see a lot of use of ffmpeg and few other GPL products used in other commercial products that don’t provide souce but usually do provide the GPL license notice somewhere and I never understood how this worked.
I’m also not sure that “definitely do not provide source code for it” is the right thing to say since it looks like you may be wrong.
See:
Ok now I think that makes me understand. Synology are simply posting the OSS software they are using but not any of their own code that might use it. So that would mean Plex could use Kodi’s code as long as they posted a copy of the source they used and upstream any changes they made to whatever they might want to use which would help both Plex and Kodi in the long run. That doesn’t sound very onerous to me and it appears they already do with other GPL code listed in the Plex license page.
You are mostly right. Actually, Plex could embed KODI’s IEC packer, but unfortunately there’s a lot more to it. Plex has built a simple client that should work on virtually any Android platform. It’s as complex as a mediocre IT graduate’s project and easy to maintain. I’m confident that if they gave it the right amount of attention and put their best resources on it, they would be able to get it to work on the latest Fire TV Cube. However, it wouldn’t be fair to ask them that. Fire OS is forked from an ancient version of Android and is still lightyears behind. Both Plex and KODI work flawless on an Nvidia Shield Pro, which is running a flavor of Android 11. The only downside is that the Shield’s hardware dates from 2015 (the 2017 and 2019 revisions are mild SOC adjustments) and doesn’t support VP9 and AV1. If you’re looking for a single media player to rule them all, your best bet is to wait for a new Shield.
I can play all the audio formats on kodi but not on plex. Is there any plan to update plex in coming days? Thank you.
Yes an update on the intended solution would be highly appreciated.
You would think that fixing the hangs on DTS playback when frame rate matching is enabled would be a higher priority than expecting an update to support audio codecs that aren’t supported according to the manufacturer specifications and explained in this thread.