PDA

View Full Version : Apogee Duet (firewire) on 10.7 Lion




HoldernessMedia
Jul 12, 2011, 03:39 AM
3 TEMPORARY WORKAROUNDS for 1st gen Apogee Duet and Lion 10.7

**Lion is still considered unsupported by Apogee at this point, so if you upgrade to Lion before Apogee releases an official update to Maestro or the Duet installer software, please don't cry about it here. :)
Just try one of the workarounds below until Apogee releases their official software updates.
These workarounds are for those of us who just have to try all the new stuff, or those who updated unknowingly.


Let me first state that Im not sure these work across the board, both solutions have worked for different users. kittyflipping's method seems to work on both new and old machines, so try this process first. If that doesn't work, try #2 and see if that will work for your machine.


Here's the rundown.

Problems/Symptoms:

You have an original firewire Duet, and installed the latest Maestro/duet installer on your machine running Lion. The Duet initially would show up as an available core audio device in both Logic and system sounds, but would not play back audio.

If you try to playback audio or adjust the volume, the Duet would keep disappearing and reappearing as an available core audio device in Logic, same happens if trying to play from iTunes, etc. System sounds would show the Duet appearing and reappearing as an available device, but still NO audio.
Tried rebooting, no dice. Permissions repair, reinstall Maestro, etc. and still the same issues.


**Workaround solution #1 **
(From kittyflipping, also confirmed working by Smeeth123 and HoldernessMedia)

1. Open activity monitor
2. Make sure "all processes" is selected in the popup menu at the top of the window.
3. Select DuetDaemon and force quit it. For me I've had to force quit it twice to actually kill it.

The Duet should be working fine now. Try the volume knob on the Duet.


*Additionally, even though the Duet volume knob works fine after this, and system preferences recognizes the Duet, for some reason the volume icon in the menu bar remains grayed out, and my volume up/down keys on MBP don't do anything. So for anyone trying this, be sure and try the duet's volume knob if your keys aren't working.


Also, on this solution, user Nitrus submitted this, using the kill duetDaemon method in an applescript:
Here is what I am using... Works for me!

With the AppleScript editor, add the following:

do shell script "killall duetDaemon" password <your password here> with administrator privileges

SAVE AS APPLICATION!

Finally, add the script to your Login items.





**Workaround solution #2**

From Macrumors user VoiceofReason: (verified also by user vtk)

"I have read the fixes so far for the Apogee Duet under OSX Lion, e.g. killing off "duetDaemon", etc.

Here's a new one. Disconnect the duet, run the official uninstaller, and let it reboot. Then plug-in the Duet and re-select it as output device. Now, the Duet seems to work just fine and no killing of processes is needed. Of course, you can't go in and run Maestro b/c it doesn't exist, but when I killed of duetDaemon before it was annoying, it still didn't allow me to use the keyboard volume control for the Duet, and I was getting crackling audio with another drive running off the same firewire port. With THIS method (uninstalling the software) it at least works and you get volume control back."






**Workaround solution #3 (Original)**

(From HoldernessMedia, also confirmed working for aguaplano).

Try this, in THIS EXACT ORDER. Opening Maestro BEFORE trying to do anything with audio is absolutely crucial. This also assumes that you already have the latest Duet installer/Maestro software from Apogee's site installed on your computer. (Version 1.9.14 at the time of this posting.)

1.) Reboot the computer.

2.) Do not touch the duet, or try to adjust volume yet. Seriously, don't do it yet. If you do, you will need to reboot.

3.) Open Maestro, click on the "identify unit" button. You will see the Duet's hardware meters go full into the red. Wait a second or so, then click the "identify unit" button again. The Duet's hardware meters should return to normal.

4.) If need be, in Maestro unmute the Duet's outputs.

5.) Try playing audio out of the Duet now. Try using it as normal in Logic, GarageBand, iTunes, whatever.



Please, anyone who upgraded to Lion please report back here if this works for you, or if you find any further information!

I hope this works for others, although I'm sure Apogee is already working hard to get it ready either before or shortly after Lion's release.



kittyflipping
Jul 12, 2011, 10:51 AM
I just tried this, and unfortunately it didn't work for me. On my machine I get audio but if I try to adjust the volume the unit resets. I found that if I kill Duet Daemon after I boot up, sometimes this will restore the ability to adjust the volume (when the unit resets, it goes back to the previous volume setting).

destroyer01
Jul 12, 2011, 11:02 AM
I tried that also and had the same errors as before, so thats why I reverted back to Snow Leopard until they fix the driver issue. Apogee will not respond back to me either. I asked when will they have a fix for this but said its not supported at this time. Thats not good if you want to upgrade !!!!!!

HoldernessMedia
Jul 12, 2011, 01:29 PM
I just tried this, and unfortunately it didn't work for me. On my machine I get audio but if I try to adjust the volume the unit resets. I found that if I kill Duet Daemon after I boot up, sometimes this will restore the ability to adjust the volume (when the unit resets, it goes back to the previous volume setting).
What year/model machine are you using? I am not having any issues with the Duet on GM build of Lion. Aguaplano also has it working on his machine using this process, and the only common factor I can see is we are both on older 2008/2009 model MacBook pros. Im wondering if maybe this only works on specific FireWire chipsets.

Also, can you try this.

Unplug the duet completely from your computer.

Go into system preferences and select "built in audio" for your system sounds input and output. Make sure the duet is not chosen for either.

If you have any kind of startup application that would access the duet to play back audio, disable it for now.

If anything tries to use the Duet before you open Maestro and click "identify" you will have to reboot and start again.

Now power down the computer, plug the Duet back, and boot the computer.

Repeat the process above.

kittyflipping
Jul 12, 2011, 05:56 PM
What year/model machine are you using? I am not having any issues with the Duet on GM build of Lion. Aguaplano also has it working on his machine using this process, and the only common factor I can see is we are both on older 2008/2009 model MacBook pros. Im wondering if maybe this only works on specific FireWire chipsets.

Also, can you try this.

Unplug the duet completely from your computer.

Go into system preferences and select "built in audio" for your system sounds input and output. Make sure the duet is not chosen for either.

If you have any kind of startup application that would access the duet to play back audio, disable it for now.

If anything tries to use the Duet before you open Maestro and click "identify" you will have to reboot and start again.

Now power down the computer, plug the Duet back, and boot the computer.

Repeat the process above.

I'm on a MacBookPro8,3 17" i7 (latest model) running the GM. I did disable any startup items I knew would use audio (Skype, iChat, etc.) but I haven't tried setting the built-in audio as the default. I'll give this a try later and post back the results, but killing the duet daemon did the trick for me as far as getting the volume to work, so I'm fine with sticking with that for now.

Luckily I am not working on any music projects at the moment, so it's not an urgent need for me to get this fixed, just an annoyance. I did get a response from Apogee and they said to check back when Lion was released to the public.

HoldernessMedia
Jul 12, 2011, 06:42 PM
I'm on a MacBookPro8,3 17" i7 (latest model) running the GM. I did disable any startup items I knew would use audio (Skype, iChat, etc.) but I haven't tried setting the built-in audio as the default. I'll give this a try later and post back the results, but killing the duet daemon did the trick for me as far as getting the volume to work, so I'm fine with sticking with that for now.

Luckily I am not working on any music projects at the moment, so it's not an urgent need for me to get this fixed, just an annoyance. I did get a response from Apogee and they said to check back when Lion was released to the public.

Thanks for the info. Interested to see the results after you set built in as default.

kittyflipping
Jul 12, 2011, 11:10 PM
Thanks for the info. Interested to see the results after you set built in as default.

I tried setting the built-in as default, rebooting, repeating the steps, then setting the duet back as default. Same thing as before -- freezes when I try to change the volume. Also, same as before, I killed the duetDaemon and the volume started working again. :confused:

Smeeth123
Jul 12, 2011, 11:34 PM
I'm happy to report that I have managed to solve this issue using kittyflipping's technique. Unless anyone knows some disadvantage to killing DuetDaemon. For me at least, the following steps cause the Duet to work completely normally:

1. Open activity monitor
2. Make sure "all processes" is selected in the popup menu at the top of the window.
3. Select DuetDaemon and force quit it. For me I've had to force quit it twice to actually kill it.

From there, everything appears to be working perfectly. In the few times I've tested this, it hasn't mattered if I run any audio beforehand or what the system audio settings are set to. Thanks kittyflipping!

HoldernessMedia
Jul 12, 2011, 11:34 PM
I tried setting the built-in as default, rebooting, repeating the steps, then setting the duet back as default. Same thing as before -- freezes when I try to change the volume. Also, same as before, I killed the duetDaemon and the volume started working again. :confused:

Hmm...so this process doesn't seem to be working on newer machines maybe?
But killing the duetDaemon does work consistently?

*Edit - looks like your technique worked for Smeeth123 as well. Thanks!

HoldernessMedia
Jul 12, 2011, 11:41 PM
I'm happy to report that I have managed to solve this issue using kittyflipping's technique. Unless anyone knows some disadvantage to killing DuetDaemon. For me at least, the following steps cause the Duet to work completely normally:

1. Open activity monitor
2. Make sure "all processes" is selected in the popup menu at the top of the window.
3. Select DuetDaemon and force quit it. For me I've had to force quit it twice to actually kill it.

From there, everything appears to be working perfectly. In the few times I've tested this, it hasn't mattered if I run any audio beforehand or what the system audio settings are set to. Thanks kittyflipping!

Awesome :)
Thanks Smeeth123. I'm going to add this to the notes so people can try both and hopefully one way or the other will work for their machines.
Now I'm going to see if I can get my test machine NOT working, so I can try this. Sounds stupid I know, but I'm really curious as to whether this affects different machines/firewire chipsets differently.

kittyflipping
Jul 12, 2011, 11:43 PM
Hmm...so this process doesn't seem to be working on newer machines maybe?
But killing the duetDaemon does work consistently?
Do you mind writing out the process that works for you so if anyone else has issues they could try that as well?

Sure, this works consistently for me:

1) Reboot (you might not need to if you haven't had any 'freezes' yet
2) Load Activity Monitor, find and select the duetDaemon process and push the 'Quit Process' button + Quit (or Force Quit if you have to)

That's it! The process (for me) restarts immediately, but the volume control now works.

HoldernessMedia
Jul 13, 2011, 12:01 AM
Sure, this works consistently for me:

1) Reboot (you might not need to if you haven't had any 'freezes' yet
2) Load Activity Monitor, find and select the duetDaemon process and push the 'Quit Process' button + Quit (or Force Quit if you have to)

That's it! The process (for me) restarts immediately, but the volume control now works.

Nice. :) Added your info to the initial post as a 2nd workaround for people to try via Smeeth123's post.
Going to go see if I can recreate the problem on machine, then fix it with this solution. I'll be back in a few.

quasinormal
Jul 13, 2011, 12:01 AM
If you just want the Duet for audio playback, you need not install the apogee software. Just plug it in and hold the volume knob down till the light stops blinking. Sound preferences should pick it up automatically, otherwise choose it manually. It shouldn't be any different from using any other USB DAC.

HoldernessMedia
Jul 13, 2011, 12:03 AM
If you just want the Duet for audio playback, you need not install the apogee software. Just plug it in and hold the volume knob down till the light stops blinking. Sound preferences should pick it up automatically, otherwise choose it manually. It shouldn't be any different from using any other USB DAC.

Good to know, thanks!
This has me wondering now, Smeeth and kittyflipping, are you able to use the Duet 100% normally? Recording and playing back audio?

HoldernessMedia
Jul 13, 2011, 12:35 AM
Sweet. So I was able to get kittyflippings process to work on my machine as well! I am moving your process to the preferred method as it seems to be working for both new and old machines.

In order for me to recreate the problem, I have to hotplug my Duet after the system is booted and running as it's been working without issue for awhile now. It works fine until I hotplug the Duet, then Duet drops and is not recognized by the system or by Maestro until I kill the duetDaemon.

One quirky thing I noticed, even though the Duet volume knob works fine after this, and system preferences recognizes the Duet, for some reason the volume icon in the menu bar remains grayed out, and my volume up/down keys on MBP don't do anything. So for anyone trying this, be sure and try the duet's volume knob if your keys aren't working.

jorgus
Jul 13, 2011, 09:42 AM
The kill duetDaemon seems to work :-). I have input too - not just output (someone wondered). Duet does not sync with system speaker volume (up in the top menubar) - and I don't have the floating transparent volume and info window Popup) when I do stuff on the Duet knob - but it works. So far.

So - it seems like the first load of the daemon - or the order/sequence it comes together with other stuff that loads at OS start - becomes corrupt. Killing it so it can restart seems to produce a healthy daemon.

Anyway - Apogee have to fix this. I want the info popup back :-). And peace in mind - no ghost daemons and other evil stuff.

This is a good place - I'm glad I signed up. Thanks.

HoldernessMedia
Jul 13, 2011, 02:16 PM
The kill duetDaemon seems to work :-). I have input too - not just output (someone wondered). Duet does not sync with system speaker volume (up in the top menubar) - and I don't have the floating transparent volume and info window Popup) when I do stuff on the Duet knob - but it works. So far.

So - it seems like the first load of the daemon - or the order/sequence it comes together with other stuff that loads at OS start - becomes corrupt. Killing it so it can restart seems to produce a healthy daemon.

Anyway - Apogee have to fix this. I want the info popup back :-). And peace in mind - no ghost daemons and other evil stuff.

This is a good place - I'm glad I signed up. Thanks.

This is cool, it seems killing the duetDaemon is working pretty well across the board. :)
I get the same issues with not syncing with system speaker volume and no pop up, but only when I use the kill daemon technique.

For whatever reason, my original process worked really well on my machine and everything on the Duet works normally, I have to hotplug it to intentionally cause issues. But after that, I still can just reboot and it behaves normally. Weird.

I'm pretty hopeful Apogee will have an update soon. It may be as someone suggested in the other thread, maybe they can't release it yet due to NDA's and such.
Now if Ableton will just push an update to Live soon, I'll be able to upgrade to Lion right away. I've got the itch, even after just playing around on the test machine, I go back to my main MBP and find myself doing some gestures and wondering "wtf? why isn't it working now?". Then I remember I'm on Snow Leopard, lol.

jorgus
Jul 13, 2011, 04:10 PM
My popup is suddenly back :-). It comes and goes. The OSX speaker symbol (and volume adjuster) in top menu bar is greyed out, but that's ok. I never use it anyway.

destroyer01
Jul 14, 2011, 03:34 PM
After reading all the post related to this I re-installed the Lion GM and tried out the "Kill Daemon" and what do you know it worked. I hope apogee will fix this soon so all of us don't have to go through these steps each and every time. Thanks people of the Music world for finding out the issue here, it's a life saver if your doing what I am :)
:D

HoldernessMedia
Jul 14, 2011, 04:52 PM
After reading all the post related to this I re-installed the Lion GM and tried out the "Kill Daemon" and what do you know it worked. I hope apogee will fix this soon so all of us don't have to go through these steps each and every time. Thanks people of the Music world for finding out the issue here, it's a life saver if your doing what I am :)
:D

Glad the thread is helping people out. :)

So, do you have to do the Kill Daemon trick every time you reboot?
I'm still confused as to how/why my original process worked on my machine to the point of basically "curing" it. I don't have to do any tricks, works after reboots, behaves as normal now with the exception of hotplugging.

HoldernessMedia
Jul 14, 2011, 04:52 PM
After reading all the post related to this I re-installed the Lion GM and tried out the "Kill Daemon" and what do you know it worked. I hope apogee will fix this soon so all of us don't have to go through these steps each and every time. Thanks people of the Music world for finding out the issue here, it's a life saver if your doing what I am :)
:D

Glad the thread is helping people out. :)

So, do you have to do the Kill Daemon trick every time you reboot?
I'm still confused as to how/why my original process worked on mine to the point of basically "curing" it. I don't have to do any tricks, works after reboots, behaves as normal now with the exception of hotplugging.

Nitrus
Jul 15, 2011, 05:56 AM
The kill duetDaemon seems to work :-). I have input too - not just output (someone wondered). Duet does not sync with system speaker volume (up in the top menubar) - and I don't have the floating transparent volume and info window Popup) when I do stuff on the Duet knob - but it works. So far.

So - it seems like the first load of the daemon - or the order/sequence it comes together with other stuff that loads at OS start - becomes corrupt. Killing it so it can restart seems to produce a healthy daemon.

Anyway - Apogee have to fix this. I want the info popup back :-). And peace in mind - no ghost daemons and other evil stuff.

This is a good place - I'm glad I signed up. Thanks.

Run DuetPopup once, and make sure it's also in your Login items.
DuetPopup can be found here: System/Library/Extensions/DuetPlugIn.bundle/Contents

goodgnus
Jul 17, 2011, 12:58 PM
Run DuetPopup once, and make sure it's also in your Login items.
DuetPopup can be found here: System/Library/Extensions/DuetPlugIn.bundle/Contents

Can you expand on that a little? Are you saying to run DuetPopup in addition to the following AppleScript Editor solution?

Here is what I am using... Works for me!

With the AppleScript editor, add the following:

do shell script "killall duetDaemon" password <your password here> with administrator privileges

SAVE AS APPLICATION!

Finally, add the script to your Login items.

Just so I'm clear... let's say that my password is hotcoffee (it obviously isn't, but MMmmmmm, I'm drinking a delicious cup right now). Would I cut/paste EXACTY this into Applescript Editor?:

do shell script "killall duetDaemon" password hotcoffee with administrator privileges

Thanks for the info! I found this thread by doing a google search for "Apogee Duet" +Lion. I'm dying to upgrade as soon as possible and am checking to see what works and what I need to watch out for.

jorgus
Jul 17, 2011, 02:02 PM
Info:

If you daisy chain FW800 with Duet last in the chain (Duet is FW400) - or have a FW800 hub - the speed from FW disks goes down 40-45% (to around 400 Mb/s.) after a while. Forcequitting/restarting duetDaemon brings up the speed again - for some time. This is new for Lion - did not happen in Snow Leopard. In Snow Leopard the speed was stabile around 6-700 Mb/s (thats what to expect from FW800 disks).

Yes, I'm in desperate need for a new Lion driver update from Apogee. :-D. This is not good. This is bad. Apogee! Listen!

Nitrus
Jul 17, 2011, 08:35 PM
do shell script "killall duetDaemon" password hotcoffee with administrator privileges

this would be correct.
hide it somewhere... and add it into your login items.

If you're not seeing your Volume popup, make sure that it is listed in your Login items. If it is not, you can add it manually, or you can just reinstall the duet package.

If it is... run it once manually, and reboot.

Now everything should be working 100%!

jorgus
Jul 18, 2011, 05:11 AM
Doesn't work for me. "Variable xsr342 not specified (or definition - I have swedish OS)".

I pasted this:

do shell script "killall duetDaemon" password xsr342 with administrator privileges

Not working - cant run script.

do shell script "killall duetDaemon" password hotcoffee with administrator privileges

this would be correct.
hide it somewhere... and add it into your login items.

If you're not seeing your Volume popup, make sure that it is listed in your Login items. If it is not, you can add it manually, or you can just reinstall the duet package.

If it is... run it once manually, and reboot.

Now everything should be working 100%!

Nitrus
Jul 18, 2011, 11:13 PM
Doesn't work for me. "Variable xsr342 not specified (or definition - I have swedish OS)".

I pasted this:

do shell script "killall duetDaemon" password xsr342 with administrator privileges

Not working - cant run script.

Try password "xsr342" ...

jorgus
Jul 19, 2011, 05:15 AM
Yes, works. Thank you!

Try password "xsr342" ...

HoldernessMedia
Jul 19, 2011, 05:48 PM
Ok, so LION is officially released tomorrow. Hopefully Apogee releases their updates soon, but in the meantime, anyone who updates tomorrow make sure to try the solutions in the first post.

Benedict
Jul 19, 2011, 09:46 PM
Info:

If you daisy chain FW800 with Duet last in the chain (Duet is FW400) - or have a FW800 hub - the speed from FW disks goes down 40-45% (to around 400 Mb/s.) after a while. Forcequitting/restarting duetDaemon brings up the speed again - for some time. This is new for Lion - did not happen in Snow Leopard. In Snow Leopard the speed was stabile around 6-700 Mb/s (thats what to expect from FW800 disks).

Yes, I'm in desperate need for a new Lion driver update from Apogee. :-D. This is not good. This is bad. Apogee! Listen!

If u are desperate don't get lion!

musio
Jul 20, 2011, 10:54 AM
Duet 2 Beta Software Installer - July 2011 - Mac OS X Lion Compatible with Mac OS 10.7 -
Do not install unless you are updating to Mac OS X Lion

http://support.apogeedigital.com/


Be warned, it's a beta and you're a beta tester even though Lion has gone live...

Mattww
Jul 20, 2011, 11:44 AM
Oh well - look like I'll be trying these work arounds then as it says September for Duet 1 :(

I appreciate it is no longer the current model and that stability is most important with kernel extensions but one of the reasons I choose Apogee was that it was recommended on the Apple site and integrated with Mac OS X. Many vendors for whom the Mac isn't their main platform lagged with support for new operating systems and point updates I had hoped for a near simultaneous release. I need to get experience of 10.7 and dual booting gets old really quick.

goodgnus
Jul 20, 2011, 02:28 PM
Oh well - look like I'll be trying these work arounds then as it says September for Duet 1 :(

Considering we're already toward the end of July, that's not really bad news. I wonder if we'll also get Maestro 2 at the same time. The new Mac Mini that was just announced today still has Firewire, so I'm probably sticking with my original Duet.

jorgus
Jul 21, 2011, 11:31 AM
I think Apogee is a lazy bunch of people :-D. September! Even small companies and solo persons developing apps like PleaseSleep and LittleSnitch have delivered updates for Lion.
I bought Duet just a year ago and have no plans for Duet 2. I don't think my next sound card will be Apogee at all - despite their beauty and good sound. They are just to slow in software - the driver we have now is over two years old and it's not 100% stabile. They didn't care to fix it...after two years.
The Duet also drags down speed in a FW800 setup. That's sad. No - I will look for other brands next time.

(you can disagre - but if you questioning my right to complain I think you're an agent for Apogee :-)

Considering we're already toward the end of July, that's not really bad news. I wonder if we'll also get Maestro 2 at the same time. The new Mac Mini that was just announced today still has Firewire, so I'm probably sticking with my original Duet.

Papanate
Jul 21, 2011, 01:58 PM
I updated to Lion before I read the Apogee working list..what a doofus huh?

Anyway wanted to let you know that Workaround #1 was successful here...
iMac 25 i7, Apogee Duet Firewire.

Thanks for the insights.

jorgus
Jul 22, 2011, 10:40 AM
Ha! Now Apogge changed and say that a new Lion-friendly driver for Duet will come in august. That's better! They must have read my critisism here :-D.

Papanate
Jul 22, 2011, 12:59 PM
I think Apogee is a lazy bunch of people :-D. They are just to slow in software - the driver we have now is over two years old and it's not 100% stabile. They didn't care to fix it...after two years.
The Duet also drags down speed in a FW800 setup. That's sad. No - I will look for other brands next time.


Your experience with the Duet doesn't mirror mine at all. And some of what you say is misleading I think.

If you put any FW400 item last in line before the computer it will slow down anything behind it. It has long been recommended that you use a FW Hub in order to mix speeds on the same bus so you don't burn a FW800 speed on a FW400 bus.

Two the drivers in my setup (iMac 27, i7 CPU, 16gb ram) are not in the least unstable. And as noted above the first work around did the trick on my system. Perhaps you have other things going on that conflict with Apogee.

And third...not that I'm an Apogee PR firm.....but they have been highly responsive to my inquiries and/or questions over the year I've owned a Duet. They have also been quite helpful and not the least bit
sour.

Now if they did listen to your tirade and put out the driver because of it...I take everything back.

jorgus
Jul 22, 2011, 05:49 PM
I have a FW800 hub. Of course I have. Duet slows down F800 - wherever you put it - first in chain - last in chain - in hub - anywhere it slows FW800 down. That's a fact. Try it youself if you don't belive me.


If you put any FW400 item last in line before the computer it will slow down anything behind it. It has long been recommended that you use a FW Hub in order to mix speeds on the same bus so you don't burn a FW800 speed on a FW400 bus.

deuce sluice
Jul 23, 2011, 03:04 PM
I was experiencing the same problems that you all were with my Duet, but running the Duet Uninstaller (http://www.apogeedigital.com/downloads.php#DUET) from Apogee's website cleared them up.

The keyboard buttons work to control volume as normal, but the mute button doesn't work right - it automatically unmutes itself. You have to hold down the volume button on the duet to actually mute it.

I haven't tried recording anything yet, but playback is perfectly stable.

atlatnesiti
Jul 24, 2011, 04:48 AM
Duet works just fine on my iMac 27" i7. Mind you, it is not set as default sound card (internal audio is), but Reason, Record, Live and Cubase 6 all seem to be "happy" with playing back through Duet without any hacks whatsoever...
Haven't tried recording yet though...

Papanate
Jul 24, 2011, 07:13 AM
I have a FW800 hub. Of course I have. Duet slows down F800 - wherever you put it - first in chain - last in chain - in hub - anywhere it slows FW800 down. That's a fact. Try it youself if you don't belive me.


If you have a hub then you shouldn't be chaining FW devices - that is what the hub is for.

goodgnus
Jul 27, 2011, 12:53 AM
I was experiencing the same problems that you all were with my Duet, but running the Duet Uninstaller (http://www.apogeedigital.com/downloads.php#DUET) from Apogee's website cleared them up.

The keyboard buttons work to control volume as normal, but the mute button doesn't work right - it automatically unmutes itself. You have to hold down the volume button on the duet to actually mute it.

I haven't tried recording anything yet, but playback is perfectly stable.

Weird. After lots of glitchy audio, I tried running the uninstaller, but that definitely didn't accomplish much - if anything. It seems the main problem comes when any second audio source attempts to send audio to the Duet. For example, if I'm listening to iTunes and I get an email, instead of hearing the new mail sound, I get brief silence as even the iTunes audio drops out.

I'm looking forward to Lion drivers for the Duet.

goodgnus
Jul 27, 2011, 09:30 PM
Weirder still. Sometimes my keyboard volume keys work, sometimes they don't. At this moment, my keyboard volume keys work, but the Duet volume knob does nothing.

Yup - I'm looking forward to getting Lion drivers for the firewire Duet. August can't come soon enough. Granted, I'm the one who upgraded to Lion (I bought a new Mini) so I'm not complaining :)

HoldernessMedia
Jul 30, 2011, 04:51 AM
Added a 3rd workaround via user VoiceofReason and user vtk, who have completely uninstalled the Duet/Maestro software and have their Duets working well by completely bypassing the Maestro software for now.

Personally, I've been getting on fine just killing the duetdaemon now and then if something gets funky, but I'm itching for both Apogee and Ableton to push their updates so everything is smooth and up to date. So far, I know a lot of people are whining and fussing just like every other major OS update, but I friggin' love Lion, don't regret updating my main system at all. :)

Nitrus
Aug 3, 2011, 11:34 PM
Added a 3rd workaround via user VoiceofReason and user vtk, who have completely uninstalled the Duet/Maestro software and have their Duets working well by completely bypassing the Maestro software for now.

Personally, I've been getting on fine just killing the duetdaemon now and then if something gets funky, but I'm itching for both Apogee and Ableton to push their updates so everything is smooth and up to date. So far, I know a lot of people are whining and fussing just like every other major OS update, but I friggin' love Lion, don't regret updating my main system at all. :)

Weird. I haven't experienced any funkiness with workaround #1. Everything works as it did out of the box. Even keyboard volume keys!

HoldernessMedia
Aug 4, 2011, 12:56 AM
Weird. I haven't experienced any funkiness with workaround #1. Everything works as it did out of the box. Even keyboard volume keys!

I'm only having an issue with Ableton. When running the latest ableton beta (8.2.5b1) everything works except when I try to adjust the master volume. Ableton instantly crashes, whether I adjust the volume using the keys, duet knob, or maestro to adjust the master volume.

Funny thing is, I had less problems with my original solution. I only started getting problems again once I tried out the kill duetdaemon solution. At this point I'm too busy to do any further investigation, and Apogee is supposed to be releasing new Duet software sometime this month anyways.

Anyhow, it's no big deal really. In the last week, I've still managed to compose 3 new pieces for a short film and 2 ambient pieces for a new game I'm making, even though you're not supposed to be able to accomplish anything with betas as they're SOOO unstable and unreliable that it just ruins your whole life, lol.

goodgnus
Aug 5, 2011, 01:26 PM
Uninstalling was the solution that worked best for me. There's still some weirdness in the behavior of the volume keys and volume knob. It's as if each one has a different memory of where the volume currently is, meaning that if I use the Duet to turn the volume up and then later use the volume keys on my keyboard, the graphic on screen shows a completely different volume than what the volume actually is. Weird. Other than that, everything seems to be working quite well after uninstalling Apogee drivers.

I'm looking forward to new Lion drivers though. That'll be great!

Benedict
Aug 7, 2011, 10:19 AM
Uninstalling was the solution that worked best for me. There's still some weirdness in the behavior of the volume keys and volume knob. It's as if each one has a different memory of where the volume currently is, meaning that if I use the Duet to turn the volume up and then later use the volume keys on my keyboard, the graphic on screen shows a completely different volume than what the volume actually is. Weird. Other than that, everything seems to be working quite well after uninstalling Apogee drivers.

I'm looking forward to new Lion drivers though. That'll be great!

Meo too. I use ableton live and it kept on crashing until I removed Maestro.

Mark Octavian
Aug 17, 2011, 03:24 PM
Uninstalling was the solution that worked best for me.

Uninstalling (or not installing at all, if you made a clean Lion install or just bought your new Mac) is the best solution if you only use Duet for output. For the input, however, you still need the drivers.

HoldernessMedia
Aug 31, 2011, 06:10 PM
Apogee just released the drivers for Duet Firewire and the ONE. :D

http://www.apogeedigital.com/downloads.php

Just installed, everything seems to be working perfect, back to normal.

This thread is now moot, go download the new software!

goodgnus
Aug 31, 2011, 07:38 PM
Yup. The update is out.
Nope. It's definitely not flawless. 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.

Boost the volume using keyboard keys. Note the display with white volume indicators. Now, turn down the volume using the Duet knob. I see dark gray indicators rather than white in the floating volume window and they don't match up.

Also: the Help menu item references Maestro 1 rather than Maestro 2.

Benedict
Sep 1, 2011, 04:22 AM
Tbh it looks and feels a bit rushed. It seems a bit sluggish too.

Daubster
Sep 2, 2011, 02:03 PM
About three weeks ago I bought two used Duets and a brand new iMac. Imagine my frustration when I spent a grip and couldn't record anything. I have been waiting sometime for the new driver release, and though I would share my experience.

My situation, however, is a little different. I [successfully] aggregated two Duets with the new drivers and Logic 9 in OSX Lion. You can read more about my experience on my blog in the link below, with a detailed report on how I did it. I would be happy to answer any questions. Overall, I would say the drivers need a bit of work, but I have managed to successfully record for several hours without significant problems...

http://www.daubsters.com/2011/09/02/dual-duets-aggregate-device-osx-lion/

Luap
Sep 3, 2011, 08:14 PM
About three weeks ago I bought two used Duets and a brand new iMac. Imagine my frustration when I spent a grip and couldn't record anything. I have been waiting sometime for the new driver release, and though I would share my experience.

My situation, however, is a little different. I [successfully] aggregated two Duets with the new drivers and Logic 9 in OSX Lion. You can read more about my experience on my blog in the link below, with a detailed report on how I did it. I would be happy to answer any questions. Overall, I would say the drivers need a bit of work, but I have managed to successfully record for several hours without significant problems...

http://www.daubsters.com/2011/09/02/dual-duets-aggregate-device-osx-lion/


Why are you spamming this all over the place? Looking for blog hits?

Daubster
Sep 4, 2011, 12:54 AM
Why are you spamming this all over the place? Looking for blog hits?
Spamming? :confused: I posted this in another thread at Gearslutz. Pardon my malicious intent to share information.

jorgus
Nov 30, 2011, 11:58 AM
No - the driver for Lion is really not good at all. My iMac lose contact with Duet every other day - sometimes many times a day. After iMac sleep. Duet seems to Mute. Replugging FW contact - or pressing M (mute) button in Maestro2 - restart the Duet - but mostly the sound is trash - sounds like a analog distortion. Restar is the only thing that fixes it - untill next time the Duet goes mute.
Apogee - where is the REAL driver for Lion?

glocke12
Dec 8, 2011, 07:48 PM
So whats going on with this ?

I have the duet FW and am running lion. Can play music via iTunes, but I have no audio output for my instruments even though meters register input signals..

bpm103
Jan 14, 2012, 12:07 PM
I just picked up a new MBP and trying to hook up the old duet. It wasn't working like it did on my old iMac so I downloaded the new drivers and now everything that I run through is pinned in the red. I tried adjusting everything I could in the Maestro settings to no avail.

I guess Im SOL for now... back to headphones until they fix it or I get a new card.

L8

jpmizell
Jan 27, 2012, 02:13 PM
Apogee Duet (1) Firewire Lion System Trouble
--
System:
17" MBP
OS X 10.7.2
GarageBand 5.1
Duet (1) Firewire (plugged in 800 port)
Maestro 2.4.3 (downloaded 2012-01-27)

---
Symptoms:

Duet manages system audio output.
System audio does not recognize the duet - Device Unknown - Firewire (800).
Screen indication of volume changes from the Duet are missing.
System output is locked to the Duet.
Maestro 2 shows the Duet but does not have options for controlling inputs. (i.e. turning phantom power on/off)
Maestro 2 is slow to open/close (damn the pinwheel).
Unplugging the duet crashes Maestro 2.
Unplugging the duet kills the system audio. (w/-w/o Maestro 2 open)
Plugging the Duet back in restores audio at Full volume (no device memory).
Closing Maestro with the Duet attached does nothing (this is good)

---
Attached:
Screen Shot of Maestro 2 with Duet attached (via FW800), on input screen.
http://blog.johnmizell.com/wp-content/uploads/2012/01/Screen-Shot-2012-01-27-at-11.30.33-AM.png

---
It is disappointing that Apogee would release an update that is so fickle. I've essentially got a $500 volume knob until I manage to figure this issue out.

Benedict
Jan 28, 2012, 02:39 AM
It is quit shocking how bad the drivers are. my next audio card won't be an apogee. My duet v1 is unusable on lion. I now have to run a dual boot machine with SL on when I am producing.

jorgus
Mar 5, 2012, 07:09 AM
I will leave Apogee too - never again I by anything from them. It's a pitty - the hardware is good and pretty, but they just don't master the programming. It's obvius - it's always ben bad and late bugfixes. Always. And Duet FW is not a thing for 20 dollars - it's an expensive hardvare and they sold it untill recently and still sell it for special price - but it seems like they already stopped developing the driver for it. Shame on them. Goodbye Apogee.

It is quit shocking how bad the drivers are. my next audio card won't be an apogee. My duet v1 is unusable on lion. I now have to run a dual boot machine with SL on when I am producing.

LurchNC
Mar 8, 2012, 07:25 PM
Unfortunatly I'm on my way out as well. My Duet was fine under SL, but its too unstable under Lion. I thought buying from a Mac only company was going to be a huge advantage. They seemed to work closely with Apple to integrate everything, so having dodgy drivers for Lion is just unaceptable. They won't get any more of my money I'm afraid.

I'm thinking of going back to MOTU. I had an ultralite before the Duet and it was always solid and stable.

Any other suggestion I should look at?

Thanks

I will leave Apogee too - never again I by anything from them. It's a pitty - the hardware is good and pretty, but they just don't master the programming. It's obvius - it's always ben bad and late bugfixes. Always. And Duet FW is not a thing for 20 dollars - it's an expensive hardvare and they sold it untill recently and still sell it for special price - but it seems like they already stopped developing the driver for it. Shame on them. Goodbye Apogee.

HoldernessMedia
Mar 20, 2012, 06:49 PM
I must have really lucked out, I don't have all this instability that some of you seem to be having. Things have been chugging along fine. I have 2 MacBook pros, my main machine is a 2009 2.8ghz C2D running Lion 10.7.3, the other is a 2008 2.4ghz C2D running the latest Mountain Lion Developer Preview 2. Both are connected with FW800. No issues with either setup.

Is this problem happening only on newer i5/i7 machines, maybe with certain FW chipsets? If you're having that much trouble, have you uninstalled the Duet software, and reinstalled the latest version?

goodgnus
Jul 9, 2012, 02:24 PM
Any word on the original Duet with Mountain Lion?

HoldernessMedia
Jul 9, 2012, 02:30 PM
Any word on the original Duet with Mountain Lion?

For me, performance is the same as with Lion. I started a thread on it here.
http://forums.macrumors.com/showthread.php?t=1390624
Hope it helps.

HoldernessMedia
Jul 25, 2012, 11:51 AM
Apogee released a new software installer for the FireWire Duet for Lion and Mountain Lion here.

http://apogeedigital.com/downloads.php#DUET

Apparently you don't need to use this if you already installed the August 2011 duet software before upgrading to 10.7/10.8, it's intended for fresh installs.

theSeaHawk
Nov 12, 2012, 06:15 PM
Apogee released a new software installer for the FireWire Duet for Lion and Mountain Lion here.

http://apogeedigital.com/downloads.php#DUET

Apparently you don't need to use this if you already installed the August 2011 duet software before upgrading to 10.7/10.8, it's intended for fresh installs.

I'm on a MBP with 10.7.4, with no install of Maestro in place (I had used my Duet 1st Gen Firewire on 10.6 on a MB).

So I downloaded the Duet-specific software installer noted above and when I click to install, it opens in text edit as text.

What do I need to do to get my 1st Gen Duet to work in 10.7.4?

thanks

ChrisA
Nov 13, 2012, 11:13 AM
So I downloaded the Duet-specific software installer noted above and when I click to install, it opens in text edit as text....

What does the test look like. Is is a script of some kind? If you you can likely run it in the terminal. Would help to post at lleast the first few lines of the text