![]() ![]() Send the clock stream through Ableton's External Audio Effect. It's pretty painfull for drums because the drums triggered 20ms later can sound drastically different. I've done the track delay thing but it can't get me under those 20ms. Thing is i can't really align tightly to the grid in ableton there is still like 20ms of decay on receiving midi from the cirklon. +100 ms then and you can move back and forth from there The zero position in time on the multiclock is at ![]() Example: Set the trackĭelay to -100 ms on the DAW and the shift range of the channels The ability to perform negative shifts using Audio Sync if youĪre able to configure a negative track delay on the Plugin or You can set machine mode on the multiclock to POS and keep Hahaha, indeed, this seems like a mission doesn't it ? So from your observation, I'm thinking that the issue is coming from the machines, not the multiclock ? interesting, I will have to try it again in standalone mode with "proper" sequencers (i'm thinking the Elektrons). Definitely not going to use this one live !!įirst I've heard anyone mention this, but to be fair you're basically trying to sync up all of the most notorious "does not like external clock" pieces of gear ever. Sometimes they would stay together for a while, but nudging the swing or delay would put everyting out of sync. In standalone mode, the machines drift wildly out of sync with each other, fall out of sync, it's a complete and utter mess and impossible to deal with. The setup includes a 909 in din sync mode, a Tempest, a pocket piano and an Elektron AR. Secretmusicuk wrote:Well, it looks like I might be the only one here with a pretty bad experience with this clock, at least in stand alone mode. So this is a very mixed feelings review, i'm still a big supporter of the ACME, it just works ! We also hooked up the modular, and being able to make up for enveloppe attack times by sliding everything is invaluable. On the plus side, when it does sync and works, it's a pleasure to have all machines perfectly tight, it's very inspiring to work with, especially considering the Tempest is always way late, being able to nudge it forward is a godsend. I realize that all clocks depending on an audio signal from the DAW will suffer the same fate, I just wish that freewheeling mode was tighter, and would catch up when the unit receives clock again. Also, the tempo in free wheeling mode drifts very quickly from the actual clock, so this is not a fix. You could activate free wheeling mode, but once that mode takes over, you need to stop the clock in order for it to latch on again. Since it uses an output from your soundcard, soloing a channel in your DAW effectively mutes the clock output, which stops the clock. Syncing to a DAW (Ableton in this case) proved more successful, but this has its problems as well. Definitely not going to use this one live !! ![]() ![]() Well, it looks like I might be the only one here with a pretty bad experience with this clock, at least in stand alone mode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |