2 replies to this topic

[SilverStreak]

Dudes I though this would be the best place to ask this,

Am testing one of these with my rig atm, and all the audio/vst stuff works fine with Cubase SE. But when I try to run a midi clock to another sequencer, it wigz out and goes skatty on me 

Have re-installed drivers etc, Yet I have a cheapo 1xi/o Edirol um1sx that eats the M-Audio as far as clocks go, still not %100 perfect but a shitheap better than this M-Audio.

Midi chain goes PC>AudioPhile>PatchBay>Sp505

Has anyone else had midiclock issues with these units???

[no-fi]

could be more of a computer interface question, but try pulling the patchbay out of the chain for a test and see what happens.....

have you ever run the SP505 clocked to anything where you were really happy with the results?

[SilverStreak]

Am using a pci f/w card so this might have something to do with the errors. Seriously giving me the shits atm!

The reason I bought a powered unit was to get a more stable clock, but atm my bus powered um1-sx is by far more stable. The 505 has been sweet for holding tempo even with radical swing/quant etc from a sync/midi converter, so its not the 505 and its not the patchbay. Its also wigging out the xl1t as you can watch the bpm constantly scroll up and down between 120-130 bpm just playing a 130 bpm clock from Cubase.

I dunno might see if I can find newer driver for the pci card and see how that goes. I should really take the s/c to a pc that has onboard f/w and check how stable she runs.