![]() ![]() I don't have any of the weird swing settings or offset settings, or even divisions playing from acme. 1 x audio input 1 x MIDI/DIN input 4 x MIDI/DIN/Modular output 1 x LFO output (0-5 V) 4 x USB MIDI inputs 1 x USB MIDI output 1 x power supply socket. BUT if i leave things at that lower tempo (and we're talking about relatively high bpms, like 135), and i start up the acme, the multiclock flashes the 'clock running' band along the bottom, but then stops and doesn't pick it up. When i lower the tempo on the acme, the multiclock follows along. If i turn up the tempo on the acme to somewhere around 160 bpm, and then start it - the multiclock picks up the sync, shows the correct tempo, etc. ![]() So, i didn't suspect it.īut this is the weird problem. But it turns out that the problem was that i was syncing (or trying to) to the acme 4, which works with everything else. Two DIN output sockets connect to your gear. Improve your musical setup now by removing clock jitter and get rid of sloppy timing. so, given that it syncs up immediately to the octatrack, there doesn't appear to be a problem with midi clock per se. The E-RM Midiclock+ Master Clock Source generates incredibly accurate MIDI Clock messages, DIN Sync & analog clock pulses in a range from 40-300 BPM with a jitter of max. I have no problem starting the multiclock with other clocks (analog clock, and then i tried the octatrack). Some more detailed troubleshooting today.found what the issue is, but i have no idea why this is happening. Sounds like everything will run without any problems! Can't wait to get it, DAW integration with my system has always been the intention, but it's taken me much longer than anticipated to get it done. Thanks a lot for the detailed explanation. I put the output on the scope and can confirm Multiclock's reset gate goes high when I start Reaper and stays high until I stop Reaper then if goes low, and Pams starts and stops on the gate. (PSN), i.e., IR- drop and Ldi/dt events, caused by excessive switching. I set the Multiclock Channel to Gate mode with Positive Polarity and on Pams, I set Run to "Gate Sets Clock State". and LOC) may suffe from this problem, whose the major cause is Power Supply Noise. Really a ton of options on the Multiclock side! One can also set the Start Polarity to positive or negative. Channel 1 on Multiclock is set to "Analog" Channel Mode, which has a submenu called "Start Mode" which one can set to either a Gate, a Trigger, or a Trigger that skips one click. There is one virtual MIDI output for each channel and all commands are priority-merged with the accurate clock. This enables you to send any MIDI commands from a DAW to your connected slaves while syncing to audio clock. ![]() I was just a bit concerned that somebody said it didn't stop when the run receives zero gate but hopefully it's been resolved!Ī little more detail on how this is configured in my setup: I'm using output 1 TRS from Multiclock to a Y cable to Pams Clock and Reset inputs. If you want, you can have your multiclock with an extra class-compliant USB Midi Add-On. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |