Menu

Equalizer APO and VB-Cables?

papoy
2016-07-24
2016-07-27
  • papoy

    papoy - 2016-07-24

    System: Windows 10

    Equalizer APO doesn't seem to want to cooperate with VB-Cables (virtual audio devices).

    In summary, if I select an input device and an output device, there is no sound on the output device.

    I've set as EAPO playback device VB-Cables Input B (see: http://vb-audio.pagesperso-orange.fr/Cable/VirtualCables.htm), and for the input of my Airplay streamer (Airfoil and Tuneblade) I set VB-Cables output B, but there is no sound (going through the cable).

    VB-Cable A is working good between my System Audio and PEACE Equalizer. I'm sure VB-Cables A&B are working good, so I think the culprit might be EAPO not sending a signal through VB-Cables, which it indeed marks as "experimental" in the setup.

    If I 'short circuit' between System Audio (plugging it into VB-Cable A Input) and Airfoil or Tuneblade (VB-Cable A output), then all works fine (except for some bugs in the streamer sofware haha).

    So this is a bug report I suppose.

     

    Last edit: papoy 2016-07-24
  • papoy

    papoy - 2016-07-24

    If I set only one capture device (VB Cable A out) and only one playback device (VB Cable B in), and if I set the processing stage to post-mix and capture, then I still get no sound at VB Cable B out. I also always get the following popup when running the Editor:

    Equalizer APO has not been installed to the selected device. Do you want to run the Configurator application to fix the problem?

    So, in summary, if I select an input device and an output device, there is no sound on the output device.

    Please help!

     

    Last edit: papoy 2016-07-24
  • papoy

    papoy - 2016-07-24

    I don't know what exactly happened, but I did the following: I added the soundcard in- and outputs with Configurator. In the Editor though, I selected VB Cable A out and VB Cable B in. I still have VB Cable A in as system audio output. However, now it is the only one checked, where previously I could only check it with the audiocard checked also. So now, the audiocard is mysteriously unchecked.

    One would say that the route would be System Audio -> VB Cable A in -> VB Cable A out -> Equalizer APO -> VB Cable B in -> VB Cable B out -> Streamer in. However, the streamer catches VB Cable A out and EAPO filters it.

    So, do my efforts finally pay off? You tell me! ;)

     
  • Juha

    Juha - 2016-07-27

    https://msdn.microsoft.com/en-us/library/windows/hardware/mt243885(v=vs.85).aspx

    Remember that VB-Cable needs to be set to use device driver API which supports APOs.

     
    • papoy

      papoy - 2016-07-27

      How do I do that? They are device drivers and I cannot find any APO settings in the relevant window settings. I have installed ASIO although I was not sure what I was doing and if it works!

       
  • papoy

    papoy - 2016-07-27

    I think the 'device' setting in PEACE is the output setting, although it is nowhere mentioned if it is ment to be an input or output setting. It would make sense though, because it works. The diagram would be: System Audio out -> PEACE -> VB Cable A in -> VB Cable A out -> Airplay streamer.

     
    • Juha

      Juha - 2016-07-27

      AFAIK, PEACE only writes commands for EqualizerAPO (to file peace.txt or something) which file is then included in config.txt (EqualizerAPO config file). You should see these command lines through Configuration Editor.

      Actually, do you need that VB-Cable in your playback setup if you want your audio go through system audio to Airfoil or Tuneblade? EqualizerAPO is systemwide so if the Airplay streamer software takes its input from 'System audio' then it could work without VB-Cable. If it does not work that way then your connection is OK if it works as wanted but the diagarm you wrote is kind of wrong because of the nature of PEACE software ... its a GUI for EqualizerApo which means that the audio stream does not go through PEACE.

       

      Last edit: Juha 2016-07-27

Log in to post a comment.

MongoDB Logo MongoDB