|
Post by silvano on Apr 4, 2023 21:17:40 GMT
Hi folks! I'm new here and basically starting out and looking for putting together my first rig. Since a very long time I'm phantasizing with getting into this beautiful world of modular synths. I mostly produce 4/4 minimal tracks in the box (DAW) but want to make a hybrid setup basically, using AE Modular for sound design and recording it into Ableton. I basically want to have the modular synced tightly to my Ableton Sessions. I've read about the bastl-instruments.com/instruments/klik but it seems like it's discontinued. :-( The easiest and cheapest way I think is to do it via an Audio Pulse (like explained here on Ableton's page ) signal from my Audio interface to the Modular. CLK input, right? My big question (and probably stupid one) is this: What Module can I use to get the Audio Pulse synced with the AE modular? I see the Heartbeat has a Clock input but since the Inpute is like this PIN cable I would probably need an adapter or something else? Sorry for this very noob question but I'm really starting out with this (even tough I've read "Patch & Tweak" but those smaller tips / inputs confuse me a bit :-)) Thanks a lot in advance, happy to connect with you and it seems like this community is a very generous one. Best Silvano
|
|
|
Post by pt3r on Apr 5, 2023 8:34:18 GMT
This is actually very straight forward; connect a midi interface from your DAW to your master module midi input configure midi clock data to be sent out from your DAW over the connected midi interface. This will provide you with a midi clock pulse available on the bus clk pin on a midi clock divider module from where you patch it into the clock input of the midi clock divider or heartbeat fr that matter.
|
|
|
Post by silvano on Apr 5, 2023 9:37:47 GMT
Thanks a lot for your input.
So is it stable and without any latency via Midi?
I remember that I've read that a computer/DAW can't put out a constant, stable midi clock, maybe I'm wrong?
Thanks!
|
|
|
Post by pt3r on Apr 5, 2023 10:03:35 GMT
Midi is not latency free, that is simply mechanically impossible. The real question is whether you will notice the latency and whether it will cause an issue for your music. I work dawless but I use external midi gear to provide a common clock signal to my AEmodular and I never encountered any midi latency issues.
|
|
|
Post by admin on Apr 5, 2023 10:07:41 GMT
Please check out the documentation on the Wiki for the Master module, which allows you to put MIDI clock into the AE. At the bottom of the page you can see two of my introduction videos with more information: wiki.aemodular.com/pmwiki.php/AeManual/MASTER
|
|
|
Post by silvano on Apr 5, 2023 12:42:44 GMT
Awesome thanks!
|
|
|
Post by maydonpoliris on Apr 6, 2023 12:37:51 GMT
I used the midi clock for the first time this week from FL Studio DAW in Windows to the Ae Beat Divider via Bus, used a Roland UM-One USB Midi Interface and it worked great. www.roland.com/global/products/um-one/
|
|
pol
Wiki Editors
Posts: 1,349
Member is Online
|
Post by pol on Apr 19, 2023 17:01:08 GMT
I've run my AE from various Akai MPCs midi outs going to the midi in on the master module with no issues, other than sometimes the sequencer modules don't start on the step I expect them to (which I suspect is a user error). Timing is fine.
|
|
|
Post by pt3r on Apr 19, 2023 18:37:38 GMT
I've run my AE from various Akai MPCs midi outs going to the midi in on the master module with no issues, other than sometimes the sequencer modules don't start on the step I expect them to (which I suspect is a user error). Timing is fine.
This is easily solved by patching the clk stop to the reset of your sequencer.
|
|
|
Post by solipsistnation on Apr 21, 2023 17:20:34 GMT
Ah, sorry I missed this when it was posted.
Yes, you can reliably sync to a DAW-- if you have a MIDI interface that pretends to be multiple interfaces, it can be helpful to dedicate a MIDI out to modular sync, especially if you're doing a lot of other MIDI stuff. (These days multi-interfaces like MOTU's various devices aren't super expensive, and audio interfaces often have MIDI built in as well.)
As described above, run MIDI into the MASTER module's MIDI in and make sure Ableton is set up to send sync to that midi port. You should see blinky lights on the MASTER when it's receiving clock. You can also use the Heartbeat and expander, which has its own MIDI in and is VERY flexible. I'll talk about that in a minute.
The MASTER will send 24ppqn clock out on the system's bus and out of the B.Clock output. It will also grab MIDI start and stop events and send them on the bus and out of its own B.Stop and B.Start outputs. This is important for keeping stuff in sync.
The most basic way to set this up would be to patch the bus clock (which, remember, is 24ppqn, which comes out to 6 pulses per 16th note or 12 per eighth note) into a clock divider to turn the 24ppqn into single 16th note pulses (or other useful divisions). The MM-Divider module is the current easiest way to do this. You then patch the divided output of that into the clock in of your sequencer. You probably also want to patch the Stop signal from the MASTER module (either from the bus or its own wire straight from the master module) into the RESET input of your sequencer. This will ensure that every time you hit stop on your DAW it sets the sequencer back to its first step and should keep stuff in sync.
The Heartbeat and Heartbeat Expander modules give you something similar, but a LOT more flexibility with divisions and multiple outputs that can be set up with different clock divisions-- a 16th output, plus an 8th note, plus whole notes or triplets or whatever. It's quite nice and very flexible. If you're going to do a lot of MIDI syncing it's worth picking up.
Where I've run into timing instability has been when trying to clock a lot of sequencers from a single pin on the master module-- hooking up a bunch of clock inputs to one output can cause voltage drops, I believe, and the sequencers will miss notes. You will need a buffered mult between the clock source and the sequencers to keep everything happy. You will probably want to do the same with either the start or stop triggers, with a buffered mult between them and the reset inputs on the sequencers.
I have also found that the SEQ8 and SEQ16 modules handle resets a little differently, so be prepared to do a little testing with the bus stop and start signals.
Anyway, I usually have a bunch of different sequencers going at all times (2xSEQ16, 2xSEQ8, Topograf, Euclid Grid, TRIQ164) and all synced to MIDI for the sake of recording, and I've had good luck setting it up like this and keeping it all in sync. The buffered mults made the biggest difference, but if you're not running more than, say, 2 sequencers you can probably get away without that. But more than that, and you'll want buffers in there.
I hope this helps.
|
|