Hello !
Just curious about that “Brand new video player” in 6.13 !
So I understand PLEX wont be using the native player in android anymore ?
What’s the Basis of this player ?
What does it compare to ? Kodi ? VLC ?
Are you testing on android to eventually deploy this player over other OSes ?
Thanks !
Is it coming to the “Fire TV” also?
Is it still based on ExoPlayer (and/or the Amazon port of it)?
If so, which version… the most actual would be 2.6.1 on both variants?
The new player is a heavily modified version of Exoplayer 2. I don’t know the exact version, but it is a very recent one.
The big difference is that this player can perform client side decoding of more codecs, so you should be able to direct play a lot more files.
Yes, this will come to the Amazon Fire devices too.
@“MovieFan.Plex” Thank you for that kind of insight. It is much appreciated.
In the past, release notes mentioned the used version of ExoPlayer… maybe this can be added. I have waited a long time.
And - as a side note: As the Android release is also the one for Fire TV… it would help a lot, if you could find a way of making more clear in the release notes, if a certain feature is available on Fire TVs… the small effort would probably reduce forum questions a bit.
Thx.
Just as an aside it doesn’t solve the Atmos dropout issues that occur on certain UHD-BD titles. I have put a ticket in at GitHub in the hopes this problem can be solved.
@rossinior said:
@“MovieFan.Plex” Thank you for that kind of insight. It is much appreciated.In the past, release notes mentioned the used version of ExoPlayer… maybe this can be added. I have waited a long time.
I’ll see what we can do.
And - as a side note: As the Android release is also the one for Fire TV… it would help a lot, if you could find a way of making more clear in the release notes, if a certain feature is available on Fire TVs… the small effort would probably reduce forum questions a bit.
All features should work regardless if it’s a Fire TV or Android TV, with the only exception being PiP. For notes specific to Fire TV devices, they are marked with[Fire TV]. Is there something specific you had in mind?
@Balthazar2k4 said:
Just as an aside it doesn’t solve the Atmos dropout issues that occur on certain UHD-BD titles. I have put a ticket in at GitHub in the hopes this problem can be solved.
Can you provide the link? This issues doesn’t ring a bell.
@“MovieFan.Plex” said:
The big difference is that this player can perform client side decoding of more codecs, so you should be able to direct play a lot more files.Yes, this will come to the Amazon Fire devices too.
interesting.
“The big difference is that this player can perform client side decoding of more codecs, so you should be able to direct play a lot more files.”??
the developers could of mentioned what it can now play … like seriously
@TwistedEndz said:
the developers could of mentioned what it can now play.
Agreed. More transparancy on this front would really help debugging or converting media (or players) if issues arise during playback.
@“MovieFan.Plex” said:
@Balthazar2k4 said:
Just as an aside it doesn’t solve the Atmos dropout issues that occur on certain UHD-BD titles. I have put a ticket in at GitHub in the hopes this problem can be solved.Can you provide the link? This issues doesn’t ring a bell.
I never raised the issue because I was unaware that you guys were modifying ExoPlayer. I did raise the issue over at ExoPlayer’s GitHub (Atmos Audio Dropouts · Issue #3803 · google/ExoPlayer · GitHub), as well as, over at Kodi (Atmos Audio Dropouts with UHD-BD). I realize Kodi uses their own player, but it has the issue as well. Andrew over at GitHub says that possibly raising the DefaultAudioSink may do the trick. Since I have no way to make that adjustment in the Plex version of ExoPlayer this is something you guys will need to test.
@“MovieFan.Plex” said:
The new player is a heavily modified version of Exoplayer 2. I don’t know the exact version, but it is a very recent one.The big difference is that this player can perform client side decoding of more codecs, so you should be able to direct play a lot more files.
Yes, this will come to the Amazon Fire devices too.
Does this fix the “subtitles always transcode” (FireTV) if direct stream is required for audio transcoding “bug”/“feature”?
(i.e video would normally direct play, but because of a bug in exoplayer you forced transcodes of the video too in situations where the file could not be wholly direct played)
@sn00p said:
Does this fix the “subtitles always transcode” (FireTV) if direct stream is required for audio transcoding “bug”/“feature”?
No. If a direst stream occurs, the subs are still transcoded. However, more codecs are now supported for direct play so there will be less times when direct stream is needed.
Andrew Lewis closed the audio dropout ticket over at GitHub saying that adjusting the ExoPlayer buffer fixed the issue. I believe this is also how nevcairel fixed the issue in LavFilters. Can someone at Plex confirm that this adjustment will be made into their forked ExoPlayer?
