Tried out the CV options on the A4 yesterday, worked super with my SlimPhatty. Tried using it in a track in my DAW (Cubase) and found latency issues when using overbridge, not sure why. Things I tested:
-
Internal sounds on the A4 synced fine with the DAW clock - so overbridge sync was fine
-
Just triggering the SlimPhatty via midi worked fine - so latency shouldn’t be a problem there
-
Setting overbridge to tempo only and then starting the A4 CV sequence worked fine
-
Setting Overbridge to clock worked fine for TRK1 (internal A4 Sounds), but not for the CV track that controlled the SlimPhatty - it seemed to run in time, only that it started the sequence a little late (If I moved the trigs with micro timing I could get it to line up the sound, but the trigs would not be placed on beat) - this seems like latency, no? (Only it worked with midi triggering the SP from keyboard, DAW and the BeatStep)
Any ideas?