this post was submitted on 18 Sep 2024
110 points (98.2% liked)
Plex
2508 readers
1 users here now
Welcome to Plex, a community dedicated to Plex, the media server/client solution for enjoying your media!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What I would do if look at every point in the video and audio chain and validate they all support hardware decoding (or passthrough / direct stream) for your supported codec.
Based on what you told me. I know your chain might look something like this:
For your two speaker setup, is it hooked up with a digital cable or analogue?
If the stereo is analogue, does it support audio at a different sampling and bitrate than what the player puts out?
Or if it's digital, does it support AC3? In a quick search I saw complaints about EAC3 not working well despite being advertised as such. So I wouldn't rule it out.
When you stream from the Roku, you can look in your media servers settings to see if it's transcoding the video or audio. However for the stereo system, or whatever is powering the speakers, you would have to reference its supported formats.
I did find the Roku Developers page and something noteworthy is
Something else that may be a good lead, looking at their supported audio codecs it lists
For AC3, this is a but ambiguous to me, if given 44.1hkz (much more popular), will it pass through 44.1khz? Will it be delayed? Will it refuse to play? They also don't specify if this is hardware accelerated or software decoding within the Roku.
If the Roku's cpu is being fully utilized decoding video in software, it may not have the cpu to decode the audio reliably. This is unlikely as most streamers are built with hardware decoding support to enable cheaper smaller lower power components to be used.
I did see on the forums people recommend AAC for general support but Roku themselves recommenf E-AC3 for 5.1 audio.
People often recommend forcing Direct Stream and disabling transcoding as a troubleshooting step to force out the container formats that won't work. It may also be worth a test and see if you lose audio.
As for where I look specifically, I tend to look for the most verbose documentation I can find, the Roku developer docs i linked would be what I would look for. I also did a lot of research on audio gear which helped as prior knowledge. Audio-science review forums taught me a lot over time from reading reviews.
As an aside I generally recommend Open Source formats where possible (AC3 and EAC3 are not) because they tend to have broader support in perpetuity. I also find Android players tend to have very broad codec support (piggybacking mobile phone components).
But I don't like to recommend new hardware in general because not everyone can buy a new device.
This is a bit all over the place at this point, but I hope it gives you some leads for determining the cause!
That's an amazing writeup. Thanks! I'll take a look.
I did some testing, and it turns out I did not have Direct ~~Stream~~ Play forced. I think I enabled it at one point, but I didn't see much difference on the "worst case scenario" video I was testing with, so I turned it back off. Looking at the Dashboard page, I can see that, even with the setting forced, that particular video is still transcoding video from MPEG2VIDEO to H264, and audio from AC3 5.1 to AAC. I may have to look into re-encoding that particular series, though the files for that show should have followed the same process as most of my other files, so I'm not sure why they're different.
Some other videos that I tested did show improvements when forcing Direct Play, but the Dashboard still shows transcoding (hw) video from H.264 to H264 (note the missing period) and transcoding audio from DTS-HD MA 5.1 to AC3.
As far as my TV setup, I don't have external speakers. I'm essentially feral, and I don't feel like they're worth it in most situations. The built-in TV speakers get loud enough, and sound fine to me. I'd rather not have to defend that setup, so hopefully no one comes at me for that unless it's actually responsible for the audio delay.