9/25/2023 0 Comments Erm multiclock vs daw![]() ![]() ![]() I’m guessing the timing may be fractionally tighter if the MIO distributes the clock rather than it passing through the Pyramid and the Pyramid resending it along with all the other MIDI info it has to crunch and distribute. ![]() Although this might not be at all noticeable in the real world. Once I’ve got it all going I want to jam with my tracks and sequences and send a duplicate of the Pyramid’s MIDI outs out to my DAW MIDI ins to track my arrangement in MIDI as a left to right timeline. Thereafter I can finalise/ fine edit my arrangement in the DAW without needing Pyramid to drive my hardware. I can route this MIDI out via the MIO to the other gear and completely bypass the Pyramid. I find the Pyramid is incredible for jamming and generating ideas but I’m struggling to write detailed, finished work on it. Especially while the sequence chaining functionality is still broken and I have lost patience waiting for the fix in OS 3. Other than the usual DAW/MIDI latency/jitter woes (hence the acquisition of the multiclock) I’ve not had any latency issues with machines that are sequenced or clocked (synched) by the Pyramid. So using the separate clock offsets on the mulitclock to account for that hadn’t occurred to me. The old Super Bass Station can be a bit sloppy with its timing, as it goes. This leads me back to my original question.Or should I send the mulitclock clock wherever it needs to go knowing that everything is receiving the same clock and therefore there won’t be any clock doubling? Or would I be better to distribute the multiclock clock direct to the machines via the MIO and tell Pyramid not to send clocking? (And ignoring the Super Bass Station for the moment) Should I just send the multiclock clock to the Pyramid and slave my machines sequenced by the Pyramid to that? So assuming that I am happy with the Pyramid clocking my machines. ![]() So your solution is nice but it clearly hinges on having a very expensive sequencer that has a multi year waiting list. And yea the cirklon is super tight and can clock everything but how many ppl have a cirklon? Not many. I too had a cirklon and a usamo combo for a while and switched to the multiclock because of the issues i had. If the Usamo works for you that is awesome, but for me that was the case for the above reasons. I have been down both paths and for my studio it is no contest and worth the extra money. The erm plugin is rock solid in ableton and never hiccups or crashes for me. The erm has an onboard user interface that i can quickly adjust for latency. This is excellent for portable live jam syncing. The erm has 4 outputs so i can clock 4 pieces of hardware directly with no thru device if needed. The erm sends midi out along with clock so i can send that midi from ableton into my sequencer of choice and into my synths. No finnicky dial needs to be fine tuned on the erm, it works out of the box with about any interface. Also noted by os on his compatibility site. Usamo is not consistently sending clock out of my rme interface and constantly requires fine tuning to get close. Not sure on that one but its never been resolved thT im aware of. It is a known issue and Os says its an ableton thing. The usamo plugin fails to start in ableton consistently after i hit a track count of around 20. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |