6/21/2023 0 Comments E rm multiclock usb sync interface![]() ![]() It means “PPQN Detection = catastrophic” (but a bit explicit IMO ) in fact isn’t the detection itself, but the constant unstability (BPMs on both slaves CLOCKED and KlokSpid MkII constantly change around 210 - as defined from DAW). Sorry about French Détection PPQN = catastophique because this screen capture was sent to French friend (social network). If the CLK/N doesn’t work as expected, it becomes useless. ![]() I sync it through the audio plugin provided, as I find the midi sync did not work for me. If youre having trouble syncing your daw to your hardware, this is the way to go. Also I don’t use source part of Clocked, I’ve mine source since I’ve developed KlokSpid, who use discrete DSP frame counters (since 2017). Integrated 4-channel USB MIDI interface (class compliant) Adjustable speed: 30 - 300 BPM LCD display. My new module sync perfectly and stays stable behind another clocking source module such CLOCKED and 2017 KlokSpid.Īlso, always on Windows machine (I don’t know about Linux and Mac), timings are erratic (bad value) until a AUDIO-xx module is present and correcly configured, otherwise all modules are running too quickly. Same fact from standalone VCV Rack, and Arturia BeatStep Pro sequencer as MIDI clocking source (24 PPQN), for any BPM setting from BSP controller. Unstabilities either from any DAW (Bitwig & REAPER confirmed, I don’t have tested Renoise at the moment but I’m nearly sure in advance about the result), but I repeat… all from Windows platform. The unstabilities also are existing from CLK input (from MIDI > CV module) you’ve shown in screen capture. Overview Stereo Balanced ins and outs for the studio or the road. I can’t compare because I’m not owner of either Linux / MacOS machines. Please let’s compare what is comparable, aren’t? Maybe Linux & MacOS platforms aren’t affected by these timing issues. I’ve mentioned Windows 10 - totally different platform. ![]()
0 Comments
Leave a Reply. |