WavTap icon indicating copy to clipboard operation
WavTap copied to clipboard

Volume is low after installation

Open yvg opened this issue 13 years ago • 1 comments

After installing WavTap the volume of my MacBook dropped considerably.

I found out that WavTap set itself as the Output Device and by setting it manually back to "internal speakers" my volume was correct again. After that setting it back to WavTap fixed the volume level of my speakers and I could enjoy WavTap :)

yvg avatar Sep 22 '12 16:09 yvg

Yeah, this is a design flaw.

Ideally, WavTap would just tap into the outgoing audio stream of the system's preexisting output device. Outside of relying on something like JACK or SoundFlower, this is straight-up not possible with existing CoreAudio APIs (It would be really really really awesome if someone could tell me I'm wrong about this), so WavTap has to do a lot of behind-the-scenes hacks to make it seem like this is what's happening.

In particular, WavTap needs to respond to system volume changes. Initially, this is the algorithm I chose:

on launch:

  • make a note of the system's current audio output device
  • set WavTap as the system's default audio output device
    • make WavTap to accept audio input from the previous system output device
    • set WavTap's volume to the maximum

on quit:

  • restore the stashed audio device as the system's default audio output device

This approach has one benefit. Namely, WavTap can quit or crash without worrying about modifying the preexisting audio device's volume settings. But there's one major problem: WavTap can never get louder than your system was when you launched it.

A better design for this whole procedure is a really high priority right now, and I'm open to suggestions!

pje avatar Nov 23 '12 21:11 pje