Can I get some advice from other Pyramid users on integrating iconnectivity MIO, my DAW and ERM multiclock?
I’ve got the MIO and the Pyramid hooked up already. Working fine. (DAW is not involved at this point)
What’s the best way to distribute the clock from the multiclock to my hardware that is connected to and sequenced by Pyramid?
My DAW is going to send the audio pulse to the ERM to generate the clock in the ERM. The clock will then come into the MIO for routing. Do I want to send that clock just to the Pyramid and then slave all my devices to Pyramid?
Or should I turn the sync send off on the Pyramid and just split the clock from the multiclock out direct to all my devices that need it? Effectively slaving everything to the ERM rather than Pyramid.
Or should the clock go everywhere it needs to go with Pyramid sending clock/sync too? Would this result in clock doubling?
Or will it not make any material difference however I do it so long as everything gets the same clock from the same source?
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.
Appreciate your advice, folks.