Apogee Duet, Mavericks, Volume control keys!

This issue has been fixed. Just download the latest installer from Apogee's site.

http://www.apogeedigital.com/company/support.php

-Rob

I'm seeing the Duet getting confused between the level set using the volume knob and the level set using keyboard volume keys. Previously, they worked together. Now, the volume jumps based on which is used, as if the two represent two entirely different volume levels. You can even see it in the on screen floating volume display.

Have they fixed this yet?

I was experiencing this the other day, and found a fix. If you go into Maestro and click "Output" then set the output below the volume knob to Out 1-2 instead of Mixer that should fix the issue. You will see two slightly different volume "squares" but the outputs will be linked. Hope this helps.

Thanks for the reply. Any idea why the volume squares are not linked? I swear they used to be. Ugh Apogee!

I don't have my Duet 2 on hand at the moment but thought they might have addressed this in the newest driver/firmware update for Mavericks.

the problem is still there and there is no fix at this point. Between this issue and OTHERS Duet is not reliable for professionals at this point. Mavericks should not be considered ready for prime time either if this is the way that issues will be address as problems arise. I just spent 3K on a new iMac and it is basically usless for what I intended to use it for AUDIO!!!!!! Sure glad Apple reads these blogs.

Having the same kind of problem.

The Apogee duet volume button (the hardware part) is working fine but the software volume bars (hope that definition makes sense) is not visible when I run logic pro or garage band, or even otherwise when the duet is set as the default audio device for the Mac.

Sometimes I do a restart after which it reappears, but that doesn't make sense as a long term solution.

Is there are any fix for this?

P.S. This is all after installing Mavericks.

Umm, yeah. The issue has NOT been fixed, thank you.

I wrote to Apogee about this. Here's their response:

So, while it was nice to know that they are aware of this problem, for now it looks like we are SOL.

Thanks.

Guess we just wait till then, twiddle our thumbs.

Would be great if it comes up on this thread, once it's fixed.

Thanks again!