OSX USB issues

[drawerfixer]

Hello,

I was hoping a saavy Mac user could help me out with a problem of mine. I'm having problems with my iSub working correctly after I wake it from sleep. I sometimes can swith the USB port, and it will begin working again, but often that does not help. Here is an email I sent to the iSub manufacturer, and his reply:

Message:

Model Number: ISUB

Hello,

I am on a 17 inch iMac with a 1Ghz processor and 768 MB RAM, running OSX
10.3.3, though I am upgrading to 10.3.4 later tonight.__Often, when I wake
up my computer from sleep, the iSub does not work.__When I unplug the
iSub's USB connection, the regular speakers get louder, which I assume
means the computer thought the iSub was working, and now the regular
speakers have to return to normal duties including bass.__Reading that
paragraph over, I didn't word it particularly well, but hopefully you
understand my problem.

Sometimes, after I unplug and replug in the iSub USB connection, it beings
working again.__However, other times this does not fix the problem, and I
must restart my computer to get the iSub to function correctly.__I only
have three USB connections into my computer, with one being the iSub, and
the other two being the mouse and keyboard.__So I don't quite understand
what is causing the malfunction.__Can you shed some light on how to get my
iSub to work correctly 24/7, including after waking from sleep?

Thanks,
xxx

Reply:

Hi,

Thank you for your inquiry.__Unfortunately, this is an issue with the operating system.__It is not specific to the iSub.__It happens with other USB devices.__When the computer wakes up from sleep it does not reinitialize the USB audio drivers/extensions.__Apple develops all the software for USB audio devices and is integrated into the operating system.


Best Regards,
xxx

I merely want my iSub to work correctly when I wake it from sleep without restarting. Does anyone know a Terminal command that I can make into an Applescript that 're-initializes' the USB drivers/extensions? Hopefully there is an easy fix. Thanks for the help.

[shazbotus]

You know what, I believe this is being fixed in the next minor OS update (10.4.3) that should be out very soon. Hopefully you will still be happy that the changes are coming soon, or maybe you fixed the problem by now (or just avoided it).