ejci / Chrome-Audio-EQ

Audio EQ for Chrome
GNU General Public License v2.0
107 stars 40 forks source link

works not with the quobuz web player although html5 playback is selected #15

Open ChristophHeilmann opened 9 years ago

ejci commented 9 years ago

By quobuz you mean qobuz? I will try to get an account (of they have free option) and debug whats the problem.

ChristophHeilmann commented 9 years ago

Yes, excuse me for the mistake. I meant qobuz.

It's great that you will debug the problem.

 

Gesendet: Donnerstag, 06. November 2014 um 21:33 Uhr Von: "Miroslav Magda" notifications@github.com An: ejci/Chrome-Audio-EQ Chrome-Audio-EQ@noreply.github.com Cc: ChristophHeilmann christoph.heilmann@gmx.de Betreff: Re: [Chrome-Audio-EQ] works not with the quobuz web player although html5 playback is selected (#15)

By quobuz you mean qobuz? I will try to get an account (of they have free option) and debug whats the problem.

— Reply to this email directly or view it on GitHub.

 

ejci commented 9 years ago

Does it work now with 0.3.2.x version?

ChristophHeilmann commented 8 years ago

No, I own a Chromebook with Chrome OS and this system use the Chrome Audio Server (CRAS). The Chrome Audio Server has an inbuild DSP which could activated by a website. See http://events.linuxfoundation.org/sites/events/files/slides/CRAS%20ELC%202014%20(1).pdf and http://audio-tuning.appspot.com/.

But this works only with speakers and until now I haven't found a possibility to use the EQ with an external DAC.

ejci commented 8 years ago

Hi, http://audio-tuning.appspot.com/ is doing exactly the same thing as this extension. Both are using HTML5 audio API to manipulate the sound. The only difference is that in the extension Im attaching EQ to all HTML5 video/audio sources on all pages.

This will never work with external DAC.

ChristophHeilmann commented 8 years ago

I suppose that the CRAS EQ is different. You need a python script to convert the EQ config file into a CRAS dsp.ini file, see https://chromium.googlesource.com/chromiumos/third_party/adhd/+/2ab4ecc17852ae6e95b398d2fac45791e105488f

ejci commented 8 years ago

But thats something different. You export the "config file" and then use it on OS level. It has nothing to do with chrome.

ChristophHeilmann commented 8 years ago

Yes, that is what I've said. I don't know if its possible to make a chrome OS app from it because if you change the EQ settings you always have to rebuild CRAS. Here you can see the architecture of CRAS: http://freepine.blogspot.co.at/2014/06/introduction-of-audio-pipeline-in.html

The whole thing was made for vendors, who want to tune the loudspeakers of their devices. With the web audio application they could test the changes they made. But in the end the equalization has to take place at OS level. An Chrome OS app wich makes use of the inbuild CRAS equalizer will overcome all the shortcomings of your chrome extension, it will work everywhere.