[:|] [:|] [:|] [:|] [:|] [:|] [:|] [:|]
WHOA!!
That is more or less my wettest dream coming true right there...
-
SUPI!
5 minutes ago I found my brandnew creditcard in my mailbox :))
Seems I am deeply in need of a test-purchase.
I hardly can believe, VE3 isn't just a rumour. [D]
It's absolutely great how VSL is inventing and inventing to help us composers work with more and more quality and speed and flexibility. Whom should I give my money but you? :)
Thanks VSL.
Angel
-
[...] No audio interfaces, no midi interfaces on your additional computers (slaves) all you need is Ethernet with a Gigabit connection. - No third party software to send audio and midi data between computers. - No hassle with audio hardware and drivers, especially on 64-bit systems. [...]
Dear VSL,
You guys are the best.
Sincerely.
-
-
It's better than free. It'll save me buying two RME MADI interfaces and MoL CP. Thanks VSL!
-
@Simsy said:
I wonder how many audio channels you can get running accross ethernet? I wonder would it be possible to route all instruments back individually and be able to mix them all in the DAW?Wonder the same thing! I also wonder how much latency there will be related to the number of simultaniously streamed channels and how much strain that will force on CPU of both slave and host computer.
-
Gigabit ethernet can stream a LOT more than 16 stereochannels fyi. We have had a SAN setup at my studio that were easilly running 60+ stereo channels of 24bit 48khz audio, and it was all running using a single gigabit ethernet connection. Throughput up to 400 MB/s should be the "roof" approximately.[H]
-
Regarding the number of outputs for VE3 per machine:
Here are some tips to some more specs that were divulged somewhat quietly by VSL on another thread from early January:
http://community.vsl.co.at/forums/t/17788.aspx
Dietz wrote on January 9th:
Regarding your question: No, we won't use a "classical" audio-connection between MIR-host and VI-slaves, although it is clear that you will need audio-outputs on the MIR in almost all imaginable setups. The system we have now is a proprietary driver-stucture for FireWire-connections, theoretically enabling us to bring in up to 64 stereo-channels into the MIR-machine from up to 64 slave-machines. - But for some guys within the VSL this is not enough, so maybe we will see yet another solution for the final product.
cm wrote on January 14th:
some things to consider:
ethernet has been invented for reliably receiving data, firewire for realtime streaming, ethernet needs configured identity of hosts (IPs), firewire is autoconfiguring (deviceIDs), ethernet puts a tic more load on the processor than firewire, ethernet packages can collide (get dropped and resent), firewire works basically *timesliced*
128 tracks 44.1/24 need 16 MB/s which is below the limit of both connection types and it depends on the circumstances beyond which load dropouts will occur.
last but not least: ethernet support or resolving connection problems can be tricky, firewire works or not.
on the other hand: if the issues with firewire continue as they came up lately maybe we should drop it ....
-
Some day I'll figure out how to create paragraphs in the new VSL forum software. My apologies.
-
Some day I'll figure out how to create paragraphs in the new VSL forum software. My apologies.
Use Firefox as browser.... (I guess you are on mac using safari?)
-
Jack, I'm sure we're all grateful for your reporting. I know I am.
I use Safari too. Type SHIFT comma (to get the "less than" sign), then type "br" (without the quotes), and then SHIFT period (to get the "greater than" sign). Do all of that twice to get a double space. "br" stands for "break." You can verify that you've got it right using the Preview tab.
Christian, do you know when VSL will post this information officially and in greater detail?
