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.

___________________
-= Insert witty comment here ... =-

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?

___________________
"Logic .. a stark contrast to the real world"

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.

___________________
-= Insert witty comment here ... =-

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!

___________________
"Logic .. a stark contrast to the real world"

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

___________________
DarkSword - Turn On
DarkSword - Hell Bound
DarkSword - Fresh
DarkSword - Styled
DarkSword - Shadowed Sun
DarkSword - Turning Forward
DarkSword - ALLFRUIT
Pacific Mint vs DarkSword - Climax Zone 2005
SoundClick Page

---FL Studio 9 User---

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)

___________________
"Logic .. a stark contrast to the real world"