Cant get A4 in sync with computer (Solved)

Soju · 2014-05-07T09:57:38.000Z

Hey guys.

Im using Bitwig as my DAW and i cant get it to stay synced via MIDI. I’m using an I connect 1 MIDI cable .

The A4 is definitely receiving the clock and transport, but it’s really erratic. When they DAW is playing, I hit the tempo button and i can see the tempo shifting. Lets say the DAW is at 110 BPM, The tempo will read 109.2 then 110.8 then 111.

This is proving to be a major hassle as I’m trying to use the A4 to jam along with what’s in the DAW.

Any ideas?

Thanks.

Soju · 2014-05-07T10:16:07.000Z

Seems to be ok now. Perhaps i had weird pattern length setting on the A4. Does forum etiquette dictate that i delete this useless thread or should I just leave it?

TrabanT · 2014-05-07T19:39:59.000Z

just leave it, somebody may write something in a month or year, then you could maybe be helpfull again … dont know, maybe deleting is better, just a thought from me

Soju · 2014-05-07T21:49:02.000Z

In that case. If you’re reading this from the future and are having a similar problem. Be sure to look at the pattern settings on your A4. If your pattern length is set to 63, it could throw all of your business out of whack.

glidepro · 2014-05-08T14:03:39.000Z

The BPM will likely fluctuate on the display while the A4 works out a tempo based on the clock.

When tempo is calculated from a MIDI clock, it’s actually not a lot different from you using the Tap Tempo functionality. It will likely take a couple of seconds before the device averages out the intervals in the ‘taps’ and shows a more even tempo.

Tempo is not just sent as a numeric value, it’s calculated over time from the MIDI clock pulses, so it relies in this case, on your DAW/MIDI interface having good timing!

Sorry if that was obvious, just clarifying

Soju · 2014-05-08T21:29:19.000Z

""glidepro"":

The BPM will likely fluctuate on the display while the A4 works out a tempo based on the clock.

When tempo is calculated from a MIDI clock, it’s actually not a lot different from you using the Tap Tempo functionality. It will likely take a couple of seconds before the device averages out the intervals in the ‘taps’ and shows a more even tempo.

Tempo is not just sent as a numeric value, it’s calculated over time from the MIDI clock pulses, so it relies in this case, on your DAW/MIDI interface having good timing!

Sorry if that was obvious, just clarifying

Not at all. That’s interesting.

glidepro · 2014-05-09T07:25:22.000Z

I actually experienced the same thing last night with my Analog Four.

I wouldn’t really have noticed, except, because the delay effect timing was syncing to the fluctuating tempo, it kept on causing funny pitch issues on the delay.

I think that sometimes it might be worth setting the tempo separately on the Analog Four rather than syncing it.

Luckily, it’s possible to make the Analog Four sequencer respond to “Transport In” without needing the clock - too many manufacturers just lump sync, clock etc in one one/off setting I’ve found…

Soju · 2014-05-11T05:26:21.000Z

""glidepro"":

I actually experienced the same thing last night with my Analog Four.

I wouldn’t really have noticed, except, because the delay effect timing was syncing to the fluctuating tempo, it kept on causing funny pitch issues on the delay.

I think that sometimes it might be worth setting the tempo separately on the Analog Four rather than syncing it.

Luckily, it’s possible to make the Analog Four sequencer respond to “Transport In” without needing the clock - too many manufacturers just lump sync, clock etc in one one/off setting I’ve found…

Thats a really good idea.