ok so here's the skinny. currently the SSL drivers take over the core audio drivers when SSL is started. this prevents any application from using the sixty-two's MIDI when SSL is running. The only exception is ableton via the bridge. this has been an issue with the sixty-eight as well. Rane has confirmed that the mixer is fully capable of sending midi with SSL running, but SSL needs to allow it. So this is a serato issue. There are a couple threads on the serato forums discussing this. This is unfortunate because i would like to send MIDI clock to Resolume. I never noticed it before, because i was using the ME workaround previously (SSL 2.3.3 with an SL 2 + Sixty-Two). currently the only workaround is to use another soundcard (i.e. SL2) or plug both usb's into the same computer. i have tried the both usb workaround and it only works about 1% of the time. SSL seems to still 'grab on' to both usb.
