Roku update broke ac3 native audio on roku express (not ultra) #2012
Comments
|
Using roku express here too. Audio broke today, but in my case, it's transcoding OPUS to aac. direct play works fine, but transcoding will not play any audio. Edit: worth noting that the original encode is AV1. |
|
i am very grateful for jellyfin and the devs, it's incredible. that being said, we can't prevent updates on roku devices, at least easily. so we can't roll back to an old version, we are dead in the water with no self solution and that kind of ruins all the glory of this entire thing. edit: i think i can compile the player myself and sideload it to prevent updates, or maybe even sideload another build to prevent updates, hopefully.... |
|
sideloading release 2.2.0 took 2 minutes, but the problem persists. i also tried 2.1.6 with no luck. yesterday i also updated my jellyfin server trying to fix this, so either the bug is on the server, or ROKU changed something too. will report back after downgrading server. |
|
looks like the server can't be newer than the player for this, so i can't run client from a month ago if the server is up to date. the only previous windows jellyfin server exe i have is 10.8.13 but when i downgrade the server just crashes, so i will have to scrap all my settings and user accounts to downgrade the server to 10.8.13 and get it working? |
|
Tested 264h file with AC3 5.1,instead of AAC 5.1 to run test and the Roku 4K stick would not play it. A FFmpeg did show up with a [q] command received at end of line but refused to play it. Had to change it to AAC codec. With version 2.2.0 & 2.2.1 installed. Here's the FFmpeg: `/usr/bin/ffmpeg -analyzeduration 200M -probesize 1G -fflags +genpts -f matroska -i file:"/home/alliyance/files/Movies/Twisters.2024.mkv" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 copy -bsf:v h264_mp4toannexb -start_at_zero -codec:a:0 copy -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 5000000 -hls_time 6 -hls_segment_type mpegts -start_number 0 -hls_segment_filename "/dev/shm/1011/jellyfin/transcodes/5d67d29682a00ef4046fc4eb20742428%d.ts" -hls_playlist_type vod -hls_list_size 0 -y "/dev/shm/1011/jellyfin/transcodes/5d67d29682a00ef4046fc4eb20742428.m3u8" ffmpeg version 6.1.1 Copyright (c) 2000-2023 the FFmpeg developers [q] command received. Exiting. [hls @ 0x5593ef748ec0] Opening '/dev/shm/1011/jellyfin/transcodes/5d67d29682a00ef4046fc4eb2074242886.ts' for writing |
|
I now think the issue is related to new Roku firmware. I spun up a 2nd jelly-fin server from scratch using a very old server 10.8.13 which i know worked, and i can't get it to work even using client 2.1.8 my roku ultra 4800x works fine, but my roku premiere 3920x devices don't play anything with AC3 audio native anymore. |
|
server 10.8.13 and client 2.1.3 also fails, which must have worked because had no issues all summer. i think RoKu changed something, but I don't know when they pushed the last update. |
|
Pretty sure the jellyfin team are looking into it. Whatever Roku change something or not, I'm sure a change is needed on the jellyfin app. |
|
i bought another roku ultra (i wanted to go ethernet anyways) i was just sharing my findings for devs and anyone else who might be troubleshooting a workaround for the less expensive players. wasn't trying to rush anyone! |
|
It's an important issue and it needs to be fix. |
They definitely pushed an update because all of my fonts on my Roku TV look different now. This was within the last week. In the Roku Matrix chat others noticed it to. |
|
The last update was 5 days ago but available since Wednesday. |
|
Ok, I did some experimenting... TLDR: Longer version:
According to this post: The Express 4k+ does not have a DD+ decoder and therefore whatever it is connected to must have a decoder and do the heavy lifting. |
|
Unfortunately, this doesn't explain how it was working in the past (without transcoding). My only thought is that the Roku Express must have (incorrectly) reported it could accept DD+ and with the latest Roku update they have "fixed" that. Which is a shame because the only reason to "fix" something like that would be if it was causing other issues (I haven't heard of any) or they want to force users to upgrade to newer hardware (just speculation on my part) |
jimdogx
changed the title
|
Same issue with resent Roku community, The Roku tech are looking into the issue. |
thank you for updating the title. in my case, I only use AC3, not EAC3. DD+ caused me problems in the past, so the end result of what's going on here could be different for AC3 and EAC3. AC3 should work. its been around since DVD days, and ATSC HDTV standards use it, so almost every HDTV in the world should be able to accept it, even if it's not a smart TV. right? |
The issue is cause by the latest Roku firmware update 14.0 and +. They should be a fix in the coming days. |
where are you getting your info from? I am interested to follow along if it's a forum |
In the Roku forum community: |
|
thank you, i could not locate that. seems it effects some ultra models also, that's good to know. good thing youtube TV sucks and only sends down 2ch audio....so the wife is happy |
|
I can play AC3 5.1 on a tv with a soundbar 2.0 but not without soundbar. weird |
are you suggesting that the roku's that are effected can accept AC3 if the roku is passthrough the audio? that would make sense. |
|
i just noticed I can't select 5.1 audio output on my roku, which seems weird because i would want the ability to passthrough 5.1 audio to my TV to output via toslink from the TV to my 5.1 receiver, if i had that hooked up this way. |
Seem like it. Will run more test. My soundbar is connected via optical. |
|
I was able to get AC3 working by selecting DOLBY output, not auto. unless roku pushed an update today, we may have a workaround at least for jellyfin audio mode --> auto (DD) I'm back in business, no idea if these settings are related or if Roku fixed something today |
optical is 1-way, so the roku and TV have no idea of something is on the other end. |
|
my uptime is 8 hours, so it was not an update. it appears @Alliyance discovered a workaround! thank you roku 3920x can now play mkv with AC3 5.1 audio natively again with below settings audio mode --> auto (DD) |
|
That's fantastic. Will try it out when I get home. Supposedly it's like this since version 14.0. About a week. |
|
Did run more test. I presume it depends on the tv build in speakers or soundbar. One of my newest Samsung tv will play without a soundbar. The older Samsung tv refused to play without a soundbar. With your settings to Dolby, it worked. |
|
Since we've determined that this is a Roku issue (that they are hopefully working on), I'm going to go ahead and close this issue 👍 |
Software Versions
Describe the bug
5.1 ac3 640k audio has worked with server transcoding disabled on my roku express for 2 years, but stopped working today. my roku ultra still works. aac 2.0 still works on both players
How To Reproduce
server has video and audio trans-coding DISABLED.
as of oct23 release, 5.1 ac3 640k audio will no longer play on roku express, but still works on roku ultra.
my library is mostly mkv x265 1080p 5mbit with AC3 640k 5.1 audio, which is why i have transcoding off. i only want players that work native.
Expected behavior
worked for the past 2 years
Logs
Screenshots
Connection Information
Additional context
sometimes it says server error, sometimes the error closes before it can be read and goes back to main menu, other times it crashes the app
The text was updated successfully, but these errors were encountered: