fernmeister, please keep us posted on this if you find more troubles with the Duet. I'm planning on buying one as soon as I get my taxe-returns and this put me off a bit, although you gave me hope by telling me that it works with the new firmware!
no the problem is just mildly treated.
you dont get KP for EVERY sample rate change or everytime you turn it on.
fernmeister, please keep us posted on this if you find more troubles with the Duet. I'm planning on buying one as soon as I get my taxe-returns and this put me off a bit, although you gave me hope by telling me that it works with the new firmware!
I'm glad this thread got bumped so I can amend my last post. The firmware update dramatically improved the performance of the Duet, but the Kernel panics are sadly not gone. It's pretty clear from the various DAW forums that I'm not the only one struggling. In particular I have a Duet-specific problem when switching users. I'm still getting responses from Apogee along the lines of
"We are working to help resolve the issue and hope to see an update in the very near future." But that is not solid.
It's a real shame because the Duet is such a great piece of kit, sounds great and is simple to use. But the stability is still a let down and it *might* be best to wait until a new driver and/or major OS update comes out.
I was having the same problems of a KP on the initial start up with my M-Audio 1814 interface. Just purchased a SIIG Firewire 400 card just to run my audio interface off of, and am no longer having the KP's. It only happens when I am plugged into the stock Apple FW ports. Just figured that may help some of you guys here. Kind of a drag for such a pricey computer, but I was having problems running my 1814 with FW drives as well. Just so happened to cure both issues.
hmmmmm........
the plot thickens.....
I am not sure that it'll help people with other brand interfaces. I was pleasantly surprised that it cured my woes. Not a single KP when I start up anymore Now I'll just use the standard Apple ports for drives and such
I'm hoping 10.5.3 will clear this up. I doubt it.
ugh, this suggests that faulty hardware is a possibility. good god, that's probably a logic board replacement.
what a pain in the neck. I guess I should start the dialog with applecare while I have free time right now.