Just wanted to say a huge thank you for adding AC3 support in CentBrowser!
You’ve officially made browser-based movie nights sound awesome — literally!
As a video site owner, I can’t overstate how helpful this is. I actually filter access to certain AC3-based streams depending on the browser’s capabilities. So yeah — this update made my day. I suspect that when this news hits the radar of streaming platform owners, you'll see a nice little surge in users (if not a standing ovation).
Also, small but important suggestion:
Right now, CentBrowser identifies itself just like a generic Chromium build — same User-Agent, same Brand. It’d be really helpful to have a setting to optionally identify as Cent, CentBrowser, or even custom brand — just like Edge and Opera do.
This would let devs like me distinguish CentBrowser from plain old Chrome, and allow us to say:
"Ah yes, this one can handle AC3 like a pro."
Sure, I could load a small AC3 audio snippet via JavaScript and check codec support manually...
But that feels a bit like asking the browser to solve a Rubik's Cube every time someone loads a page — not ideal for performance.
Anyway, just wanted to say: you're doing amazing work. CentBrowser still remains the best Chromium-based browser out there, hands down.
Thanks again — and keep rocking!
P.S. Just wanted to follow up and let you know that I’ve tested AC3 detection using MediaSource.isTypeSupported() — and it works perfectly!
Quick, clean, and no need to poke the browser with actual audio files — exactly what I needed.
Thanks once more for adding native AC3 support. It’s a game-changer, especially for those of us managing video content platforms. You’ve really raised the bar for Chromium-based browsers (and set it to Dolby Digital levels).
Keep up the amazing work!
You’ve officially made browser-based movie nights sound awesome — literally!
As a video site owner, I can’t overstate how helpful this is. I actually filter access to certain AC3-based streams depending on the browser’s capabilities. So yeah — this update made my day. I suspect that when this news hits the radar of streaming platform owners, you'll see a nice little surge in users (if not a standing ovation).
Also, small but important suggestion:
Right now, CentBrowser identifies itself just like a generic Chromium build — same User-Agent, same Brand. It’d be really helpful to have a setting to optionally identify as Cent, CentBrowser, or even custom brand — just like Edge and Opera do.
This would let devs like me distinguish CentBrowser from plain old Chrome, and allow us to say:
"Ah yes, this one can handle AC3 like a pro."
Sure, I could load a small AC3 audio snippet via JavaScript and check codec support manually...
But that feels a bit like asking the browser to solve a Rubik's Cube every time someone loads a page — not ideal for performance.
Anyway, just wanted to say: you're doing amazing work. CentBrowser still remains the best Chromium-based browser out there, hands down.
Thanks again — and keep rocking!
P.S. Just wanted to follow up and let you know that I’ve tested AC3 detection using MediaSource.isTypeSupported() — and it works perfectly!
Quick, clean, and no need to poke the browser with actual audio files — exactly what I needed.
Thanks once more for adding native AC3 support. It’s a game-changer, especially for those of us managing video content platforms. You’ve really raised the bar for Chromium-based browsers (and set it to Dolby Digital levels).
Keep up the amazing work!