clock output when slaved

[duncan]

I’ll keep this brief because I’m on a vista machine & firefox lasts about three minutes each time I start it….

I am slaving the octopus to an external clock, & passing the clock to the next device (a p3). so the 200 LED is red.
start-ok.
general clock stability seems ok, though I haven’t done the 10 minute cubase tests mentioned elsewhere.
BUT
the stop command is not echoed.

this is in 1.6, & persists in the latest beta.

duncan.

(PS if it helps at all, the start/stop/clock is transmitted fine when the octopus is the master clock, but this prevents me using my preferred master clock, which is a tap-tempo device).

Post edited by: duncandisorderly, at: 2009/06/15 17:35

Post edited by: admin, at: 2009/06/24 08:27

[duncan]

ah, this still seems to be the case in 1.62……

d.

[zahir manek]

i’m having the same problem with my MAQ. if the Octopus is the master clock, it stops and starts fine. With Ableton or Cubase as the master clock, when i stop the DAW, the Octopus stops but the MAQ keeps playing at a slower speed, it doesn’t stop.

[Author]

Posts