User input welcome.
-> I am finalizing a "project sync" device that will dispatch BPM and sync signals to use in more than one device such as LogiQ, KrOn or Echo etc.
->REASON: using Midi CCs "live" is no problem (see my videos), but after recording in Studio One V4 there is a huge problem of "ghost" signals sent with wrong notes-on. This obliges to clean the Midi CC so they don't happen at the same time as the Midi CC = pain in the bottom. It looks like a bug of Studio One V4 (may be solved in V5) but this could affect other sequencers. At the same time, I recall similar behaviours in noah long time ago, when the sequencer would go wild for no apparent reason, well, that must be it.
-> I do not have another sequencer than studio one v4 (and will not upgrade to v5 anytime soon), and no hardware sequencer to verify that it is a studio one error or a more general bug, so i have made that device.
-> The device completely solves the issue, in addition to be the main tempo for several devices which is something i've been thinking about making for years....
-> I added 3 "LG" outputs, so you could synch a quad modulators easily, ie, allows the device to receive more than 1 note-on gate at the same time, without the need to route audio signals or use Midi CCs.
-> For the moment it is only for Notes-On and I do not think I will make a "self-sync" like in LogiQ because I have not noticed any issue when the devices and Midi CCs are used without notes-on messages. Also because using several self-sync requires an self-self-sync to resynch all the self-syncs (you are following me right?
)
-> Also , I am *not* adding manual tempo to the device for the moment, because it's another type of signal and seems difficult to implement at project level, at least not immediately because it requires a lot of test and trials and errors, and I want to make this one available "ASAP" and get rid of all those studio one/*scope issues which are workflow killers.
- > The new device is best used on its own midi driver, in order to completely seperate the re-sync messages and the midi Ccs etc. so the 2 information never overlap. Bye Bye midi overflows, hello awesomely precise sync
There are 3 outputs mainly to be able to use a different sync per device,, or to better sync the quad modulators which can be retriggered independantly from other sequencers.
-> I have been testing this for 3 days and all is very solid even when using intense Midi CCs automations. The devices never go out of sync, all signals are treated completely separetely, and all is much better like that. A huge improvement, and also great to be able to set tempo once for all in a single device.
see you in a couple of days.