Server Version#:1.18.8.2527
Player Version#:6.4.12.6214
Hi everyone! We are running a Plex setup consisting of the server running on a NUC and around 15 Roku clients. Due to the sheer number of clients that might play at the same time and the limited CPU & GPU power of the NUC, we have to choose to force the Roku to direct play. Every thing was running flawlessly until two weeks ago when, over night, we got stuck with the following error to some of the videos" There was no audio detected during forced direct playback. Would you like to change Direct Play to Auto and try again?". We don’t want to set it to “Auto” but even if we select “No” or press “Back” the audio is still working as expected. The only inconvenience is that error popping which would be misleading and would make the users select “Yes” and enable Auto on Direct Play which would lead to overwhelming of the server. Did anyone else experience this behavior?Any suggestions would be much appreciated. Thanks!
I’m getting that same warning on my roku too, and it’s super annoying. Especially because you can clearly hear the audio in the background. Does anyone know of a way to turn this warning/error off?
In the Roku settings, what is Audio Mode and HDMI set to?
What is the Roku Software version: Roku Settings -> System -> About
During playback, press * and make sure that Audio mode is set to Off
A media sample would help us troubleshoot locally.
With that said, ideally Direct Playshould be set to Auto as there are scenarios where audio codecs and subtitles may need help to play correctly, and this is very lightweight for the server to process. I’d be more than happy to also troubleshoot the need to set Direct Play to forced, but let’s tackle the prompt first.
I am getting the very same exact issue on my Roku Ultra with the latest firmware update that just came out, and also before the update going back months. However this only happens with certain AVI files. I have it set on Direct Play but a stupid annoying prompt comes up incorrectly informing me that there is no audio detected and wants me to switch off Direct Play and put it on Auto.
This prompt is an error because there absolutely IS audio on my files whether I put it on Auto or Direct Play, the audio and video are both fine, so why does every single episode in my TV series which are all AVI files prompt me with this stupid ridiculous error message when I load each video?
This is a serious bug in the app and needs to be resolved. Make this stupid prompt go away, the audio is fine! Stop telling me there is no audio because there IS!
Can you supply a sample or full source of a file that exhibits this behavior? It should only happen when someone has forced direct play (or enabled allowing DTS-HD), and the video player didn’t detect any audio. The main reason for this, is that forcing direct play will simply attempt to play the file without any compatibility checks, and may often result in no audio. Sounds like there may be a regression either in the our code or the Roku firmware. I’ll file internally to try and reproduce, but again, a sample or source that exhibits the issue would be a great help.
(edit: I see the previous user supplied a sample. I go with that first)
I can see what is happening on the m2ts sample originally included here.
It has a TRUE-HD audio track. When you force direct play, it does initially detect the audio is not available (correct). However, playback actually fails for this item due to the TRUE-HD track, and we auto fallback to a direct stream w/ converting the audio. So the prompt here is wrong, in that we need to make sure playback is working (without audio) before prompting. This may be the same issue the AVI file is running into, because that container cannot be direct played, but when forcing direct play, we’ll attempt play it first.
So does this mean Plex is going to fix this? So we don’t see a stupid message informing us that no audio is detected in files before they play even though they do have audio and it’s fine?
Is there an update on this one? I have the same issue. I am using a Raspberry PI 3 as a plex server and it is not set up to transcode; hence the need to force.
Yes, the issue reported by the OP was fixed in v6.6.1. If you are still experiencing the issue, please provide a sample or full media source of an affected file, and we’ll troubleshoot it.
Thank you very much for making sure this error was fixed. Could you also please do something about another issue that needs correcting that is currently being ignored?
