Hi. I don’t want to litter the forum with yet another topic about my setup, even though this may not be directly related to this thread about the new demuxer: latest Android 8.29 lost the ability to play AAC 5.1 as surround on my setup (CCwGTV via lg-49UJ635V using HDMI to Sony HT-S20R) completely. I have logs of me trying for 30m to change every possible setting. It either plays LPCM 2.0 or gives An error occurred when attempting to play this video. Let me know if you prefer me to open (yet) another topic… Thx!
As your post doesn’t seem related to the new video demuxer I recommend you start a new thread and attach your logs.
1 Like
Is there a link where we can access the latest nightly build available for download going forward? Going to https://downloads.plex.tv/Kepler/nightly/ just redirects to the basic download page.
Loving this build, BTW. All of my playback issues seem to be resolved.
2 Likes
This build has absolutely solved my playback issues but it’s defaulting to transcodinf 100% of the time claiming dirextolay failed. Please let me know if you need logs. Thank you!
Yes, the Android Logs would be needed here to see what happened.
The only bug I’ve noticed is that I have “play next episode” disabled in settings…
Visually it acts appropriately (video goes back to plex/series menu), but the audio (and subtitles) for the next episode begin to play. Extra odd, because I don’t even have subtitles turned on.
Not sure if you saw my post above, but is there a resource for the nightly builds? Or are you going to be posting each build as a new topic? Thanks!
Plex Media Server.log (3.4 MB)
thank you again! (just don’t judge my movie choice(s) haha)
That’s the server log, we’d need the Android Logs (as I linked previously).
I will test the next build if it’s not public beta. Just tag me and I’ll run through it on the Firestick 4k.
Having issues with any file (4k and 1080p) that have TrueHD audio. The video playback (direct play) stutters (slow motion) when a TrueHD audio track is passed through. No issues with changing the audio to AC3 or files with DTS-HD, EAC3 etc.
On a 2015 Shield with audio passed through to receiver (supports all audio codecs).
Also network debugging shows an IP http://10.153.246.9:32500/logging which is not the local LAN.
Plex-nightly-truehd.txt (1.9 MB)
1 Like
We’re aware of the issue relating to TrueHD audio, and are investigating it at the moment.
1 Like
Gave this a go last night. It seemed to play anything i had ripped fine but was playing recorded TV way too fast. I’m in the UK and have never found livetv or recorded programs to work particuarly well so i’m looking forward to this improving things. Hopefully someone else has given logs from UK recordings but if they havent let me know and i’ll get them for you.
I’m trying out this version and wondering if there is anyway to bypass the select user and enter pin before going into the home page. Everything time on Android tv version, I switch to another app and come back, I need to select the user and enter the pin.
Yes, you can. First, login as the main admin on your account (the one with the crown next to it). Then go to settings, and turn “automatic login” on. Then switch to another account and use your pin to login. It’ll remember this and will auto-login from now on.
1 Like
Well that’s embarrassing. I went into settings and didn’t see the option. So I am blind. Thanks for your help
This nightly keeps falling back to only transcode, direct play doesn’t work any more. is this expected with the new build
Its not able to lookup this address, I am blocking outgoing lookups (rather redirecting all outgoung lookups to my lan’s dns servers. is there something I need to be doing here to allow specific domain lookups
02-05 18:41:13.918 e: Stacktrace: com.google.android.exoplayer2.ExoPlaybackException: Source error
at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(ExoPlayerImplInternal.java:628)
at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:600)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:223)
at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: com.google.android.exoplayer2.upstream.HttpDataSource$HttpDataSourceException: java.net.UnknownHostException: Unable to resolve host "192-168-100-4432323234234.plex.direct": No address associated with hostname
at com.google.android.exoplayer2.upstream.DefaultHttpDataSource.open(DefaultHttpDataSource.java:365)
at com.plexapp.plex.player.engines.exoplayer.extractor.CachedDataSource.open(CachedDataSource.kt:97)
at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:84)
at com.google.android.exoplayer2.source.ProgressiveMediaPeriod$ExtractingLoadable.load(ProgressiveMediaPeriod.java:1013)
at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:409)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by: java.net.UnknownHostException: Unable to resolve host "192-168-100-20.4453ddsds.plex.direct": No address associated with hostname
Ensured *.plex.direct could be looked up, now directPlay seems to be working. Strange.
So is there just 1 build (v8.29.0.30173) of this “nightly” from 6 weeks ago? I’ve asked twice in this thread if there’s a resource (buildbot) for this but it has been ignored.
For those wondering:
PROS of this build: The “fails to start” bug is fixed on Nvidia Shield TV (not fixed yet in normal Plex).
CONS of this build: New bug where the audio of the next episode will auto-play even when “play up next” is off in settings. Also reflected in “continue watching” if stopped.
This fixes the fail to start but seems that when Refresh Rate matching is enabled it still does the same thing. I honestly cannot tell the interpolation when refresh rate is isn’t matched. the Shield must be doing a good job with the pull-up or whatever mechanism it uses to show. Haven’t ran into your 2nd problem yet, but will keep an eye out for it it.
The shield has its own match refresh rate to frame rate settings that can used as needed on specific movies once the playback starts.
So I would try turning off refresh rate matching and then running this “nightly”, the beta build has higher version than the “nightly” btw 
the current public beta version also has this bug
8.30.0.30648-beta
