Erm multiclock used5/17/2023 ![]() Analogue clock signals are configurable in polarity and start/reset behavior and individual clock dividers are available. Each channel can be set to either emit MIDI, DIN sync or analogue clock. Synchronisation of the multiclock to a DAW relies on a sample accurate audio clock, which allows for rock solid sync signals. So anyway, I was wondering if a Multiclock could fit in with my setup too.Īs I understand, a plugin (in logic) sends a sound trigger to the multi clock (via my audio interface) which then sends out to all the elements of the studio.The multiclock can be it’s own master or synced to external MIDI, DIN sync or Analogue master clocks. Alongside them I also have Maschine via USB but I think thats ok for now) (Clock is the only reason the TR8 and Sub37 are connected via USB. The TR8 has been a bit unstable though getting a steady clock from Logic and I'm not really into the reliance on USB I currently have. There's different degrees of latency across the board, but after struggling with it for a Ive got it to a place where it's fairly tight and if needed it only takes a small trim in logic to get recordings locked in. I also have a Sub37 which is currently getting clock via usb direct from Logic to sync sequences and patterns. I'm currently sending clock from logic to a TR8 via USB, and from there it sends clock to various sequencers, synths and to a Kenton Pro Solo which converts and sends clock to an 808 and a Linndrum. I was looking into ERM midi clocks and have just started looking at the multi clock and it looks like your setup is quite similar to mine. Just stumbled onto this thread and your response could help out a lot with my setup. Not sure if there's anything else I can add that would but happy to answer questions. Within Logic I have all MIDI clock output turned off and took an afternoon to measure the latency across each MIDI device so I could build in a compensation delay for each track in my Logic templates. I'm not at my studio at the moment so can't recall how but I have a connection also to a Poly61M with a small v-trig>s-trig converter in-line which drives the arpeggiator on the 61M (which doesn't sync to MIDI clock)Īs far as production workflow goes it's transparent: I simply ignore any concerns around MIDI Clock and let the hardware routing get on with everything. The routing software for the mio10 lets me route it where I need it.įor non-MIDI hardware I use the clock out from the ERM and put it through a mult via a patchbay so I can share the clock across multiple hardware devices (like the gate in of a Pro One for example)Īnother output goes to a Kenton MIDI to DIN SYNC conversion box which drives my Linndrum. I take one of the MIDI outputs from the ERM and feed MIDI clock to all my MIDI DIN hardware via my two iConnectivity mio10 interfaces. I have the ERM plug-in on all of my Logic templates but also use the ERM in standalone mode. I was able to get tighter recordings than in the past and it was due to how I monitored in.ĭo you have any further tips for how you’ve integrated the Multiclock into your workflow? Especially interested if you’ve found utility with modular clock & modulation.I don't have any modular setup but have used the Multiclock with both DIN MIDI and analog clock for my studio I noticed this early on when recording bass guitar. Apparently Ableton tries to compensate for what you are hearing (latency) if you monitor through the software while recording, and that can throw the timings of a sequencer right off. The other thing that some people may not know is that the best way to record into Ableton is to turn monitoring off in the DAW and monitor through your soundcard mixer. ![]() My possibly dumb question - is it possible to just send a start and stop message to the Digitakt from ableton - which would simply start the machine at the same exact time every time and then just record audio instead of also sending MIDI clock? I should find out today how it goes, but I am optimistic. I have no problem with imperceptible jitter of that nature, as long as that is the case. This is where we get down to the part where we make music and move on. ![]() This is probably correct but in practice that variation is imperceptible in my experience.Yes.
0 Comments
Leave a Reply. |