The MIDI express 128 often does not appear after a reboot. It needs to be powered off and on (by unplugging the USB cable). That is because there is nothing in the hardware that can recognize a reboot, and some motherboards do not kill power to the USB ports, even when the computer is shut down! Maybe the XT as well?

I don't think I've ever had that problem with any USB hardware, and it doesn't really make sense to me because many USB devices, including the Express XT, are not bus-powered so they can be (and maybe even should be) powered up when the O/S is booted so that they'll be properly detected.

You should generally be able to plug-in or power up any USB device either before or after boot, and have it detected and the driver loaded by the O/S. Whether a running application can pick it up on the fly or not is another question, but I'm wasn't asking ClockWorks to do that.

All that said, the problem turned out to be much more basic... someone (I'm blaming the dogs) pulled the USB cable out of the DAW. 

Danny Danzi


Sorry about that. Try this link for the one that didn't load up. http://dl.dropbox.com/u/4909348/6oclock.mid

Hey. Danny. This one is playing fine with the new XT driver in place. I'm not sure where you need to look on you system to correct thtis problem, but at least we know it can work.

The only thing I think we've pretty much ruled out is a general SONAR bug and the XT driver and Clockworks software. It could still be any of:

SONAR Config
ClockWorks Config
XT firmware/hardware (Mine is one of the earliest made with Windows-compatible firmware - it actually shipped with a chip that I had to swap in).
O/S, MOBO or 3rd-party hardware/driver interoperability issue.
Hardware synth response.

This last one we can probably rule out if it's happening with more than one synth.

brundlefly

The MIDI express 128 often does not appear after a reboot. It needs to be powered off and on (by unplugging the USB cable). That is because there is nothing in the hardware that can recognize a reboot, and some motherboards do not kill power to the USB ports, even when the computer is shut down! Maybe the XT as well?

I don't think I've ever had that problem with any USB hardware, and it doesn't really make sense to me because many USB devices, including the Express XT, are not bus-powered so they can be (and maybe even should be) powered up when the O/S is booted so that they'll be properly detected.

You should generally be able to plug-in or power up any USB device either before or after boot, and have it detected and the driver loaded by the O/S. Whether a running application can pick it up on the fly or not is another question, but I'm wasn't asking ClockWorks to do that.

All that said, the problem turned out to be much more basic... someone (I'm blaming the dogs) pulled the USB cable out of the DAW. 

I was referring specifically to the express 128.  It recognizes only a power dip in order to be re-enumerated (detected on a USB port) by Windows, even after a reboot. Most USB devices do not have this behavior, but the express 128 is the 2nd one I've seen that cannot be reinitialized without a power dip. It is a hardware limitation of at least one cheap USB peripheral chipset I know of (the micro CPU and bus logic that is part of the USB device). Couple that with a M.B. that does not drop power from the USB ports, and thus it requires unplugging the USB cable. Trained dogs would help .

Glad to help. Like i said at the outset, that's a tough one. Sure would like to know what's going on, but I think I'd have to lay hands on the system to get any further, and even then, it might remain a mystery.

SONAR always runs at 960PPQ internally for both recording and playback The PPQ resolution setting in Preferences only affects editing resolution.