You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe The Bug
Unsupported audio tracks correctly trigger audio transcode.
Although multichannel audio is transcoded correctly to multichannel AAC (or AC3, when selected), the TV passes through stereo PCM through eARC.
This behavior occurs both using the TV browser and the jellyfin-webos application.
This behavior occurs regardless of the maximum channels option being set to 5.1/7.1
Steps To Reproduce
Play an unsupported multichannel audio track (tested with DTS[-HD MA] and FLAC 5.1) or lower the playback quality to force a transcode due to bitrate
Verify using Playback Info that the client receives multichannel AAC (or multichannel AC3, when opted in client playback options)
Check the eARC receiver to state that it is, in fact, receiving stereo PCM
Expected Behavior
If transcoding to multichannel AAC, the TV should play multichannel PCM through eARC. I have verified that HE-AAC and AAC-LC correctly play as multichannel PCM when not transcoding.
If transcoding to multichannel AC3, the TV should pass through the codec through eARC. I have verified that AC3 correctly passes through eARC when not transcoding.
Logs
jellyfin-server log with DTS-HD MA to AAC 6-channel
System (please complete the following information):
Platform: LG OLED C2 v23.20.56 (recent webOS 24 update). Both with Jellyfin v1.2.2 and using the TV browser.
Jellyfin Version: 10.10.5
Additional Context
Additional bug: jellyfin-webos supports Opus playback, but when opting to transcode unsupported tracks to Opus, it requests the server for AAC.
Edit: This seems webOS specific, but it needs further testing with different versions since my TV was updated to webOS24 this January. I've tested with a Windows laptop connected directly to the eARC receiver and transcoded AAC shows as multichannel PCM, while transcoded AC3 gets passed through directly (correct behavior).
The text was updated successfully, but these errors were encountered:
I've realized that the problem is occurring not only with transcoding.
I've tried to play a mkv Dolby Vision media, which is unsupported and triggers a remux.
Jellyfin on TV receives the remuxed stream with both video and audio as direct.
The audio track is EAC3, which is normally passed through eARC, but when remuxing, although still direct playing, gets sent as stereo PCM.
Describe The Bug
Unsupported audio tracks correctly trigger audio transcode.
Although multichannel audio is transcoded correctly to multichannel AAC (or AC3, when selected), the TV passes through stereo PCM through eARC.
This behavior occurs both using the TV browser and the jellyfin-webos application.
This behavior occurs regardless of the maximum channels option being set to 5.1/7.1
Steps To Reproduce
Expected Behavior
Logs
jellyfin-server log with DTS-HD MA to AAC 6-channel
System (please complete the following information):
Additional Context
Additional bug: jellyfin-webos supports Opus playback, but when opting to transcode unsupported tracks to Opus, it requests the server for AAC.
Edit: This seems webOS specific, but it needs further testing with different versions since my TV was updated to webOS24 this January. I've tested with a Windows laptop connected directly to the eARC receiver and transcoded AAC shows as multichannel PCM, while transcoded AC3 gets passed through directly (correct behavior).
The text was updated successfully, but these errors were encountered: