Closed rudism closed 2 years ago
It is likely because of the roku's device profile. There was a condition where AAC will be transcoded if it's not first or default. There is an open PR which will correct it. https://github.com/jellyfin/jellyfin-roku/pull/543 if you want it to start working now, use 10.8 and delete the AAC Codec profile as indicated in the PR.
Is it possible to remove a codec from the Roku's profile on the server side?
no but 543 has been merged so if you just clone the git and sideload according to the development guide, it will work with a 10.8b1 server
Nice, I never knew it was so easy to sideload to the Roku. That merge appears to have fixed my problem so I'll close this. Thanks.
Describe the bug Roku Ultra hooked up to AC3/Dolby capable receiver via HDMI is not reporting AC3 as a supported codec, causing videos with AC3 5.1 audio to be transcoded.
Roku settings:
To Reproduce
Expected behavior The Roku Ultra is capable of playing HEVC 10-bit video and the receiver is capable of playing AC3 5.1 audio, so I would expect this to play without any transcoding.
Logs This showed up in the logs while using 10.7.7 when playing a file on the Roku. I haven't seen a similar profile message show up since switching to 10.8.0-beta1 and not sure how to enable this more verbose logging.
Screenshots
Additional context I did manage to find a work-around:
This is not optimal, though, since there are other cases where I have media that really is not compatible with the Roku and those can no longer be played with these settings.
Possibly related to #532 but in this case as far as I can tell the Roku is correctly detecting that the receiver supports all the Dolby Digital formats and yet those audio formats are not being posted to Jellyfin as being compatible with direct play.
The Plex Roku app plays the same media fine without transcoding, and I can cast to a Chromecast Ultra connected to the same receiver from the Jellyfin Android app and it plays fine without transcoding.