I assume you mean from the CCwGTV. Sure, I can do that when I get home from work.
Itās more complicated than being beneficial, Plex must work with the OS enabled framerate matching because that option must be kept ON for when other apps support it. We canāt constantly toggle it OFF before starting Plex.
My understanding is that apps must requests framerate matching from the OS by calling a new Android 12 API. If thatās the case, Plex should not request it and instead do its own switching, right?
1 Like
I totally agree with your reflection @plxstrm
Similar problem. some level of h264 are stuttering. it stop a bit every sec. Other type of h264 are work well.
i try with latest stable and beta versrion. It worked well with Android 11 (i use chromecast with google tv)
Yes, it happens with H264 Level 4.1 with 4 Ref.Frames content, as reported by @VTron21:
āI am on the beta version 9.11.0.36101. With Match Framerate set to Never in OS and Refresh Rate Switching and Resolution Switching set to Off in Plex. I get 1 second of video played in 30 seconds and then pauses for 30 seconds on any File that is H264 Level 4.1 with 4 Ref Frames when Direct Played. H264 Level 4.1 with 2 Ref Frames will play fineā
Well, I recently bought a CCwGTV on sale, since my Nvidia Shield is in the process of being replaced or repaired under warranty.
As I put it on the TV, it was updated to Android 12 and what seemed to be a good start with this device seems that some playbacks were crashing or having problems.
Looking for possible solutions to these problems, I found both this thread and another on Reddit commenting on the problem in question.
For my part, it seems that with the latest beta versions, it seems to work fine on most content. One of the problems that persist is the one commented by @vampywiz17 and @yossSP, part of the content in 1080ā¦ sounds good but plays badly.
Iāve also managed to configure Plex to transcode EAC3 content, which CCwGTV doesnāt support, into AC3 instead of OPUS stereo audio. Selecting the Passthrough in Optical and activate only AC3. With the Nvidia Shield I could passthrough AC3 and DTS (I have a Samsung KS7000 TV and Logitech Z5500) and although the change between DTS and AC3 had to be done manually on the TV, I could reproduce DTS and EAC3 (Dolby Digital) on the Logitechā¦ But well for me now itās OK.
An exampleā¦
Now I have to do tests with DTS formats or have it transcode everything to AC3, it wouldnāt be a drama either until I have equipment that can actually play HD sound formats.
Hi, my solution is to convert the best quality audio in my language if itās not supported. I do it with ffmpeg converting to EAC3 5.1 1536kbps, and adding it as default audio track. Practically there is no film with more than 5.1 channels in my language and my ear canāt distinguish the new track from the original.
The problem you are having is your Logitech z5500 only supports DD and DTS. And looking at the images of it you are feeding the audio to is using optical. Otherwise, the CCwGTV will pass eac3 through to a receiver.
Hi @VTron21, you are right. The z5500 does not support EAC3, however with the Nvidia Shield could do passthrough and play the EAC3 track like a normal AC3. Everything connected as now, HDMI to the TV and toslink to the speakersā¦
But I think this is not the big problem for me, of course, in a few of months I will buy a receiver and I will be able to receive the HD audio tracks.
However, I prefer now that in the CCwGTV works the change of hz and the reproduction of all the formats that it can play work correctly 
Hi all, I report new feedback.
I updated a few days ago the new Android system update STTE.220920.015.A1, but, for me, it persists the same bugs arrived with Android 12 update, mainly the issue that if we select DV standar processing (which I prefer) in CCwGTV settings, Plex, Youtube, Emby , etcā¦ can only play DV content, any other HDR content plays in SDR. So I have to select Low Latency DV processing to be able to play any HDR content with the appropiate processing.
Iām on Plex beta 9.12.1.36893 which match resolution and framerate properly.
The only issue I suffer from Plex is that it can play every Dolby Vision profile 7 titles from begining, but it loses DV processing when jumping forward and backward or changing chapters.
No issues with other HDR or SDR titles, even DV profile 5 or 8, only with DV FEL/MEL profile 7 ones.
Any progress on the way @sixones?
Thanks for your help.
Amazing. This explains why I havenāt been able to play HDR content, not only via Plex but other apps too.
Iām having the a similar issue. My Chromecast with Google TV (Android TV) can play every single file, even 80+ mbit remuxes without issuesā¦ from the start. But if I try to seek, or resume from where I left off, it buffers forever, or tells me to try again and check my connection.
The thing is, both the server and client are wired (and Iām using a 3rd party adapter so my Chomecast sees ~300mbit via speed tests), and the other clients Iāve tried (Android, Windows, Web) all work fine. Iām 99% certain this is a Android TV issue.
Not to mention, these files that are causing issues have 100% worked flawlessly in the past as well.
EDIT: I tried a new server on my Windows machine (5900x CPU) and the exact same issues occur.
Effectively itās the same issue I have. Some people say itās an issue caused by the changes introduced in native Android 12 video playback. Hope there is somebody working on thisā¦
Iāve tried a certain competitorās server/client and it appears to have the same issue so I think youāre right in that it is an overall Android 12 issue.
1 Like
Is this still being worked on?
I have had to turn off Match Framerate because it creates a 1 second lip-sync issue.
I have no problem now with resolution and framerate match. It works fine for me.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
