return to tranceaddict TranceAddict Forums Archive > DJing / Production / Promotion > Production Studio

 
PC to PC via MIDI
View this Thread in Original format
jammer42777
I have a simple question,
what hardware and software functionality would be required for me to have 2 computers connected via MIDI cable (one PC is the sequencer, the other runs vsti's) and the vsti PC would be sending audio to the host PC via S/PDIF cable?
I would already have low latentcy soundcards installed (m-audio audiophile 2496)
are there any requirements that I'm missing?
groundzero74
I think you have a setup there, both PC's have 2496's right ? Just hoop up the sequencers midi OUT to the "VSTi" machine's midi IN on the soundcards, configure the correct midi outputs&channels in the sequencer and VSTi PC (maybe running Steinberg V-Stack), hook up the SP/DIF output of the VSTi to the input on the sequencer, configure input channels to monitor, and you're a go.
jammer42777
quote:
Originally posted by groundzero74
I think you have a setup there, both PC's have 2496's right ? Just hoop up the sequencers midi OUT to the "VSTi" machine's midi IN on the soundcards, configure the correct midi outputs&channels in the sequencer and VSTi PC (maybe running Steinberg V-Stack), hook up the SP/DIF output of the VSTi to the input on the sequencer, configure input channels to monitor, and you're a go.


even if the sequencer on the host machine is roseguarden in Linux, I'm mainly concerned about latetncy is there an issue with this in this case?
groundzero74
Don't know about Linux Software, i have a comparable setup, with Cubase on 1 PC and V-Stack on the other, both with RME cards, conencted via ADAT, both card run about 3ms latency, that means that when the VSTi pc get a midi signal , it takes 3ms to play the note , and the sequencer get the audio data but takes 3ms to process it (the latency will grow higher , the higher the load gets on your machine) .. that's 6ms in total , i usually solve this by using the Cubase Midi Quantizer, and play the outgoing midi signals -6ms ahead of the local signals , after some tweaking you'll get kind of "in sync" ... but don't worry if it isn't perfect to the 0.1ms, this will give a more swinging feel to the notes.
jammer42777
quote:
Originally posted by groundzero74
Don't know about Linux Software, i have a comparable setup, with Cubase on 1 PC and V-Stack on the other, both with RME cards, conencted via ADAT, both card run about 3ms latency, that means that when the VSTi pc get a midi signal , it takes 3ms to play the note , and the sequencer get the audio data but takes 3ms to process it (the latency will grow higher , the higher the load gets on your machine) .. that's 6ms in total , i usually solve this by using the Cubase Midi Quantizer, and play the outgoing midi signals -6ms ahead of the local signals , after some tweaking you'll get kind of "in sync" ... but don't worry if it isn't perfect to the 0.1ms, this will give a more swinging feel to the notes.


I'll see if I can find a roseguarden forum, thanks!
IDarkISwordI
Hey. Not sure of the operating system being used but theres a tool exactly like your wanting for windows machines. As I remember, instead of MIDI, it uses eithernet and transfers the MIDI and sound data across the ethernet cable so no hassle of quality loss. Its called FX-Teleport. It costs money unfortunately but they do claim low latency (haha :P, pull out your salt shaker of course). Just an option to consider :).

Cheers,
Zac
jammer42777
quote:
Originally posted by IDarkISwordI
Hey. Not sure of the operating system being used but theres a tool exactly like your wanting for windows machines. As I remember, instead of MIDI, it uses eithernet and transfers the MIDI and sound data across the ethernet cable so no hassle of quality loss. Its called FX-Teleport. It costs money unfortunately but they do claim low latency (haha :P, pull out your salt shaker of course). Just an option to consider :).

Cheers,
Zac


not sure if it will run in Linux, but I can always test that (I'll do that tomorrow)
CLICK TO RETURN TO TOP OF PAGE
 
Privacy Statement