EAC3 support for Chrome browser

[tlkounev 14]

Hi,

Im facing problems with transcoding EAC-3 in Chrome when Edge with same core can direct play EAC-3. Both browser are on same core and Emby see them as Chrome.

Both has to have EAC-3 support as EAC-3 codec should be build to Gecko. Is this bug or feature? :)

 

 

chrome.txt edge.txt

[Luke 42077]

HI, I don't think it actually supports eac3. I've not heard of any browser supporting it at this point.

If it does, then it should direct play without requiring any changes from us as we're already detecting whether it is supported or not.

[EarlyOnsetPooka 1]

On 3/5/2025 at 9:59 AM, tlkounev said:

Hi,

Im facing problems with transcoding EAC-3 in Chrome when Edge with same core can direct play EAC-3. Both browser are on same core and Emby see them as Chrome.

Both has to have EAC-3 support as EAC-3 codec should be build to Gecko. Is this bug or feature?

 

 

chrome.txt 151.97 kB · 0 downloads edge.txt 196.68 kB · 0 downloads

I've got the same behavior. I haven't pulled logs, but I attempted to play a file with EAC3 in Chrome, Edge, and the Emby windows app. Chrome forces transcode to mp3, while the other two direct play the EAC3

[RanmaCanada 494]

Just because they use the same core, doesn't mean they have the same features. The core is there, but Google hasn't implemented it, but it appears MS has.

https://issues.chromium.org/issues/41253735

Just some proofs.