Is there a way to run two computers and have the software work together? I can see running VCV as a stand alone on my laptop and running the audio out just like you would any synth, but how might I sync clocks?
for non-âclock syncâ signal transfers between computers.
I tried this and it receives syncs fine over Ableton Link protocol from my MPC One. Iâd like to find module that can act as Mater Ableton Link source in VCV⊠currently Stellare module only receives clockâŠ
OK, thanks, I assumed, after I read the docs, that it could be master.
âThe link module is a very simple module which provides a âlinkâ connection with a link enabled application like Ableton Live. It will allow you also to connect two or more VCV rack instances on different computers together which are connected in the same WLAN or LAN.â source
But, I didnât try it - only with Ableton Live as master. I see now, that there is no way to set the tempo on the module.
Some other network utilities for the toolbox
NetVST, use VSTs across network. Also supports loading 32bit VSTs and calling from 64bit app http://netvst.org/wiki/doku.php
rptMidi, network MIDI for Windows
Interesting. Will give this a whirl when I get home. Thx.
Mmmmm⊠that may be above my pay grade but Iâll look into it as well. Thanks Ben.
Not sure⊠it is free?
Iâm pretty sure I have it on my home desktop with the rest of the ReaPlugs. I just wouldnât have had much call to look at it.
Iâd like to bump this topic to see if anything has been figured out about this. I can, more or less, run 2 instances of Rack on two different computers running as a VST thru Ableton on each. But this is REALLY a PITA (and just plain clunky), and of course Ableton itself eats a lot of CPU I would rather be using just for Rack. That And I can only run two instances of Ableton without having to buy another instants of that. I donât find the Ableton Link all that reliable as well. If I had a way for Rack to talk to itself I could easily have 3 or 4 computers in my studio running Rack as a stand alone and this would be a real step towards real life Euro-rack.
thatâs a pretty ambitious setup. Are you sure you can handle all that power?
Ambitious would be trying to deduce what the heck GC3 is trying to teach me. The above is simple - all the computers can be on the same network, all I need is a module that will share clocks between them (I believe or wish as it were). DACs are cheap to get decent sound from the computer to the audio interface and I have three off those as well.
I will look into it! Thanks!
I link multiple machines frequently, all running nothing but rack (2013MBPro i7, 2011MacMini i7, Vostro7590 i5-8th gen). Usually, sâa case of getting clock / run / reset distributed, which I tend to do over ADAT IO between them (each machine has an old MOTU MkII era FireWire interface on various bodges of thunderbolt converters, as they can be picked up for next-to-naff-all comparatively), and then return their audio back to the clock master over ADAT.
Masterâs audio is then delayed to account for round trip latency of [each slaveâs input latency (account for clock latency) + masterâs input latency (return audio latency)] to get all the audio back in sync (Usually a 22ms delay for me) prior to mixing it in with the slave returns (master mixer > delay > âpostâ mixer bringing in slave returns > main monitor output)
Master sends 24x clock from impromptu clocked, slaves receive it in PPQ24 mode to BPM input. Everything else between them is done over remaining ADAT channels and MIDI. Can send any signal you like over ADAT between machines. Over MIDI you have to be mindful of bi/unipolar and offset / rescale accordingly.
All physical controllers are MIDI merged with a Raspberry Pi which then sends / receives across all machines.
Attempts to do this over network / rtpMIDI never seemed to be solidly reliable⊠but thatâs probs more my junk (Sky) router and busy network than the underlying method.
Doing it this way using Audio/ADAT I/O, you have to be mindful of block size / cpu on each machine as any extraneous pops / clicks due to too low block or CPU overrun get introduced into the ADAT streams and thus create additional clock pulses that cause drift / offset at the slaves. (If your house has dodgy electrics like mine does, someone turning a light on/off in another room, or compressor on a fridge/freezer kicking in can throw a slave out by 1x pulse. Experimentation with LPF on the clock stream at the slaves and ground-lifted power strips tend to be necessary), and make sure DC Blocking is disabled on the AudioI/O modules that are handling CV-over-ADAT.
TLDR; youâd do it as youâd expect to be able to do it in any modular environment, you just need appropriate I/O between the machines.
Hey thanks, Iâll look into it. Looks similar to the Blue Cat mentioned earlier.
Lol! Love it brother but youâre leaps and bounds ahead of my technical abilities!