Tagged: ableton, issue's, midi clock, syncing, traktor
This topic contains 18 replies, has 6 voices, and was last updated by Christian 9 years, 5 months ago.
-
AuthorPosts
-
October 19, 2014 at 6:08 pm #800
hi there,
I’ve been tweaking with the new firmware and having a blast. but i haven’t found a way to sync up the sequencer with either ableton or traktor. the tips in the manual about shifting the midi clock delay to negative 1 also didn’t work. i’m using a UMONE roland midi to usb to convert the midi clock. any tips?
October 19, 2014 at 9:50 pm #804I have set mine up so Ableton sends midi sync to the BCR. (Remember to turn on the midi ports midi sync in Abletons midi settings)
Just make sure on the BCR Seq you set midi clock to external.
Works fine for me.
October 20, 2014 at 8:46 am #811hi! ok it should work like this: on zaquencer set “clock” in global menu to “ext” (on encoder 2 in the topmost row).
then make sure that your software sends the clock on the correct midi port. does the green “in” LED light up on the BCR?the negative 1ms delay described in the manual was meant for triggering patterns from midi CC, not for syncing to an external clock (although you might have to adjust the midi driver delay in your DAW settings).
October 26, 2014 at 1:40 pm #1000On the same subject, and forgive my hi-jacking of the OP….
@Andrew: Are you experiencing a bit of jittering (loose timing) when Zaquencer is “slaved” to Ableton Live. Here, internal clock seems to be “tighter” than the external one with a clock division of 16steps and all steps active.
Perhaps my cheapo USB-to-MIDI interface is the culprit?
ALSO: specifically, for Ableton Live compensation of the natural “latency” can be achieved by setting a negative delay value in the settings of Ableton Live’s midi clock output. Hope this helps anyone else dealing with the same set up.
- This reply was modified 10 years ago by Theodor.
October 26, 2014 at 1:59 pm #1002I’m syncing to Ableton also, and it seems pretty tight. I have beats playing on a Korg M3 that is also synced to Live’s clock, and am not hearing any drift even after 10 or 15 minutes.
October 27, 2014 at 8:37 am #1016Hi Theodor,
we´ve done quite a few measurements on Midi clock jitter and found that cheap USB-Midi Interfaces may introduce random delays (jitter) of up to 20 ms, which is a lot.With a good Midi Interface, the syncing to external clock should be as tight as on internal clock.
Cheers!
October 27, 2014 at 12:46 pm #1021Aaaah thanks a bunch! I know its not of your responsibility, but if you or any other member has any recommendations for a reliable one, Im all ears. Truth is, I have 2 BCR units, and one of em has the built-in USB to midi interface broken so I am already using the cheapo one I have with my “factory” BCR so I was planning on getting a second one for the ZAQ BCR anyway. So, a recommendation will come in handy!
Thanks again!
October 27, 2014 at 3:00 pm #1025I would love to give you a recommendation for a reasonably priced USB Midi Interface, but I´m afraid we don´t have too much experiences with isolated USB-Midi devices. We always used the RME Fireface 400 + 800 Midi Interfaces for our high-end tests but that´s most likely a bit overkill.
Maybe the other members can chime in with their experiences?
October 27, 2014 at 4:20 pm #1037I’m using the MIDI on my Presonus Firebox.
I have a cheapo USB MIDI cable, which works OK but of course I’m not going to recommend that if you already might be having MIDI problems.
I also have an iConnectMIDI 2+, but haven’t even hooked it up directly to the BCR.
October 31, 2014 at 3:00 pm #1135Thank you for all the info, still doing some tests with different midi options. Also tried the sound card option, using a audio 8 be still a midi delay of -43 ms. so i think there’s something else going on with my set up. will keep you posted.
May 25, 2015 at 11:48 am #2654hi there all.
I just bought the firmwave on a friends advice, but haven’t actually checked if this can do what i am looking for. I am trying to find a hands on solution to step edit ( and if possible more ) my jomox airbase99. Until now i was doing it on ableton.
Will this firmware + a BCR actually allow me to still have ableton as midi master, but then sequence and edit my jomox sounds and patterns from the BCR?
And if so probably stupid question, but what the best way to connect the midi. I work with a Fireface 400 + midi patch.
RME midi out > BCR Midi In // BCR midi Through > Airbase99 Midi in ?
Are decay or tuning or .. as well controllable from the BCR?- This reply was modified 9 years, 5 months ago by charly.
May 25, 2015 at 7:20 pm #2656Hi charly,
yes what you ask is possible.
You can have ableton as master, send the clock to the Zaquencer and connect the Jomox to it´s outs to sequence it. The Midi connection you describe seems the way to go.You need to map the Zaquencer´s and the Jomox´ drum notes to correspond to each other.
Please check out the getting started here (starting with “to create a drum track”):
https://zaqaudio.com/forums/topic/sticky-usage-getting-startedYou have one velocity value per step (not per drum instrument), and can make it work similar to the accent on an 808.
You should be able to control the Jomox´ sound parameters with the CC lanes on the Zaquencer (2 per track). These are mapped from the Global Menu. If you only use one Zaquencer track for sequencing notes, you can use the CCs of the other tracks as well and route them to the same receiver (for a total of 8 CCs).Let us know how you go!
May 25, 2015 at 11:18 pm #2657wow ! thanks ‘Keymaster’ .
it seems you guys really have nailed something amazing here !
I thank you for the effort and the sharing, really great !
Picking the BCR tomorrow, will probably post an other massive THANK YOU then !!!
( and if i understand well, seems I am gonna go a 2nd one for some of my synth… )
Thanks a lot ! Really can’t wait to have some hands feeling on this Airbase.May 30, 2015 at 9:53 pm #2668Ok, not as simple as i had hoped.
I just assigned key number for each drums of the jomox aibase 99 to the BCR)but it doesn’t seem to catch :
Sequences\ cursor only moves when pressing play for the BCR, not when pressing play ableton. And no sound is coming out. Neither when pressing play from ableton or from BCR.Few things i am un-sure of :
- couldn’t find where to edit the ”150ms delay between buffers” when transfering the new firmware. I just played the sysex to the machine. ( it went up no14, i authorsied and everything )
- I tried assigning drum midi keys to track 1 on the BCR, but then couldn’t edit the steps (it worked on BCR’s track 2 , but still no moving cursor when playing from ableton, nor any sound even from press play on BCR)
- i screened up and down the jomox manual, and found some midi infos that i might be of help, but i do not understand them fully – too technical.
I’m based in Berlin so had hoped to be able to find someone able to help me, but no one in my circles. I’m not sure what do do you now.any possible help here?
here is the link of the jomox, maybe that can help someone to direct me.
http://www.jomox.de/upload/manuals/AirBase99_E.pdfthanks by advance.
May 31, 2015 at 8:46 am #2671Ok, it seems your Zaquencer is still running on internal clock.
Go to Global and the turn encoder 2 until it says “etL” (external) in the display.
Press Global again to store the setting. This should make it respond to Abletons Start/Stop and clock. You cannot use Start/Stop on the Zaquencer in etL mode.Secondly, please make sure to read this if you haven´t yet (starting with “to create a drum track”): https://zaqaudio.com/forums/topic/sticky-usage-getting-started
You need to match three things from the Zaquencer to the Jomox´s settings:
- Midi Notes of the individual drums
- Midi Channel of the track you´re using
- Midi Output A/B of the track you´re usingThe trackmode needs to be set to “drum” (in Global Menu).
Also, the Track you´re using needs to be unmuted in the Mixer Menu
(Track 1 is the only unmuted by default, the others are muted).Regarding your questions:
- 150ms delay is for safety, in many cases it might work with other settings. if it installed correctly with authorization etc you should be good to go.
- maybe in your example, only track 2 was in drum mode, and not track 1? but maybe then track 2 was still muted? did you see the Midi output light (A/B) blinking, when playing the sequence? -
AuthorPosts
You must be logged in to reply to this topic.