I have had conversations with the Nvidia team about the tube. There is always some sort of issue with the Tube due to only having 2GB of ram. I don’t know what either the Plex or the Jellyfin devs do with exoplayer, but I take Nvidia’s reply to me as truth. The Tube is a crapshoot with 4K UHD BD remuxes. I returned mine promptly for the Pro in 2019.
Oddly enough, I just uninstalled Plex. Rebooted the tube, reinstalled the beta 9.1.0, and I’m getting solid playback on par with Jellyfin. Maybe it is a ram issue. Hmmm. I’ll try my 2017 Shield Pro later tonight. It’s currently only setup on a 1080p Plasma in the bedroom. Lol
I gave away my Panasonic TC-P65ZT60 1080p plasma in 2020 to my family. I t was replaced with the LG OLED77CX
I’m still rocking a Samsung from 2013 in the bedroom, I can’t remember the model.
My theatre is rocking the 65” Panasonic GZ1000, and living room the 55” LG C1.
Did they say why every other device with 2GB RAM doesn’t have the same problems the Tube has, or used to have? I no longer have any issues with the Tube that don’t also show up on the Pro with Plex.
So I redid the remx of f9 using what appeared to be the theatrical release. It changed where the sync issues started, butt it still happened.
I’ll try a few more methods to see if I can get an mkv that works…
I keep my Emby server up and running in conjunction with Plex. Honestly I think I’m going to use Emby more now. Issues like this and the recent update with Discover that I’m not a fan of, has me looking to switch. Emby isn’t as pretty but its functional and really isn’t bad at all. It’s been playing everything flawlessly.
I’ve been on beta 8.29.0.30300 for weeks now. It’s playing back everything I throw at it and I’m just enjoying my Plex libraries. I’m also bitstreaming all audio tracks to my A/V receiver with Dolby Vision enabled.
Do you by chance own Step Brothers (1080p rip)? I still cannot play that one through even on 8.29.xxxx. It was much better than 8.30.xxxx but still went way out of sync. It just took longer.
Yes, I have a full quality MKV from the 1080p Blu-ray. I will try to watch it soon-ish and let you know.
The next time you playback a 1080p movie, check to see if your tv is receiving the native framerate (e.g. 23.976, 24, 59.94). I have found that every once in a while a 23.976 movie will output as 59.94 to my tv. This usually results in eventual sync issues. If I stop and restart the same movie, it will output correctly at 23.976. Not sure if this is a Plex app bug or something with the Shield Experience update. I have version 9 with all the current hot fixes.
Running the latest beta client, and stable PMS server.
During playback of misc 4K / TRUEHD files, getting random cutouts of audio, while the video is still playing. Audio then is out of sync and you have to rewind / stop & resume to get it in sync until it happens again. Latest test was with 3-4 different versions of Fast 9.
As soon as the seek happens is when the audio dropped a second or so prior, but nothing appears to show in the log for that.
04-12 21:27:54.251
Client Logs:
plex-client.txt (13.9 KB)
Server Logs:
Plex Media Server Logs_2022-04-12_21-28-54.zip (4.0 MB)
Seamless branching problem with F9. If you backread a bit, there are other people who experience the same.
Yep. Still broken on my end too. New update did nothing to fix the TRUEHD issue.
VLC also does not play it correctly so. It’s definitely Nvidia.
Plex Client 9.1.0.31883-beta
Nvidia shield 9.0.2(33.1.0.319) (PRO)
PMS 1.26.0.5715
Having studering and dropouts with this latest beta as well.
Current release is botched, but prior release was working (mostly, although who knows as was dealing with the Android 11 issues).
Last Night in Soho is a good example, studering all throughout the opening credits and opening scene.
Godfather Part III Coda won’t even start playing and it’s a TrueHD 5.1 track, but skipping in 2 min seems to work. Shield says it’s sending PCM not bitstream, and PMS says it’s playing (counting up) and direct playing audio/video, but image and sound is black on the TV.
AC3 track starts fine.
I’m just gonna chime in here also.
I think there were two different reports of symptoms of frozen playback. (As it’s mentioned in the release notes)
However the one where seeking causes a frozen frame and no audio and yet an active playback timer is still there and probably quicker to reproduce.
It’s late here. I will test that movie out in the morning.
Anyone with the seek/freeze issue try the latest beta from today yet?
BETA:
- Player: prevent seeks from freezing playback.
If I recall you had the same issue as me.
Seek too much.
Frozen frame.
No Audio.
Active timer?
If so it’s still broke. And yes that’s on the beta you mentioned with the fix from earlier today.
If anything it’s more frequent.
Not me, as I don’t normally seek/ff/rw. In fact, I haven’t had a single playback issue since the initial 9.1.x beta, but I realize I’m in the minority ![]()
Ah right. It’s still there anyway.
But to be fair I think I’m in the minority.