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?
-
Yes it sounds great. A tigers leap forward both in DAW-slave interaction, with the VE and VI. I would prefer ethernet connection, setting it up isn't that hard - I managed[H]
Re 1 gigabyte ethernet; I worked with one for a year or so. Yes it works seamlessly, however I did have to maintain latency between DAW PC and FX-T slave PC mostly because Spectrasonics Trilogy demanded it; even when freezing tracks (Cubase 4) it kept cutting up the sound. -until I enlarged latency. Which was a surprise at 1GB connection. But it works.
best regards, Jorgen
-
cm -
Since it seems that you're back online following NAMM, will I need a PC slave with my Mac DAW in order to use VE?
I may need to buy a computer this week and this would be extremely good to know.
Thanks
(I want to thank Plowman for his help on teaching me how to create paragraphs with Safari!)
-
Hi timkiel,
I certainly will get a Mac for my slave machine if possible. I just haven't gotten confirmation from the powers-that-be at VSL that a Mac will work for this.
Mainly at the moment, I might need to replace my multi-use PC this week because my old one is on its last legs. I use it mostly for stereo editing in WaveLab and hang my customer's drive off it
. And I thought that maybe if a Mac wouldn't work for the slave that I'd buy some high end PC that could be both the slave and my multi-use machine. Otherwise this week I'll buy a low end PC to handle the editing.
Best regards
-
not neccessarily you would need a mac, but you can use a mac ... my recommendation would be to not use a PPC mac (hint, hint) ...
depending on what you're intending to burden on this machine you wouldn't even need a too expensive one ... two cores, maybe 4 would already do more than *the job*
if you like to run only VE on it and don't have money to waste get a PC, if the compter has to stand near your desk (and you like it silent) get a macPro.
what you will need anyway: a flawlessly working gigabit connection
as posted earlier: get a system you are already familiar with or be aware of a learning curve.
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
i have to admit i didn't run FXT for a looong time, but be aware it is not neccessarily FXT which checks across the network .. there are so many services which decide by themselves to *do something* ... uPnP, detection of shares, announcements, software updates (eg. java), ... endless list VE itself does nothing, except listening to incoming data and delivering the result.
i'm not up to date with a release schedule so i'd like to say nothing, but as you know meanwhile we have fully working copies.
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
Thanks for the reply. I would however say that many people will have network problems, and probably much more severe than the one I've mentioned, so a thorough, exhaustive networking guide will be essential. My network was set up by a specialist, and still I have these minor glitches, so it is not necessarily easy to solve. A networking "tool" that configures the network perfectly fro VE would be fantastic, but not easy to do I guess. I think that it could be even more tricky on Mac, where networking seems not to be so easy.
DG
-
@DG said:
A networking "tool" that configures the network perfectly fro VE would be fantasticwould be nice to have, but impossible. too many options for too many possible environments.
basically it doesn't matter if its a mac or pc or any other operating system fortunately - ethernet is ethernet is ethernet.
of course you will get some advise or help or recommendation, but in detail it is you or your technician who is responsible for a working environment (as for a working operating system as such)
what will be not supported is a 100 mBit network or a network only using afp or netbeui (the latters should no longer exist) - TCP/IP is mandatory.
either mac and pc have the tools built in to check if a network is healthy and a connection can be established.
what i have not yet checked in detail is network over firewire, but this should be only needed at rare occasions.
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
Interesting, having had a quick read through on the (now working) vicontrol site it looks like the demo rig was between two macpro's. Which begs the question about multiple hosts and how well it works when you have more than 1 slave.
More than 1 slave = more network traffic = potential timeouts on ethernet?
Hopefully some official info will come out soon - maybe they're still debating the price, who knows - personally some info and no price would be great. If it works as well as we all hope then price might well be pretty immaterial. (well almost)
-
apperently vista 64 on the macPros has not even been launched ;-)
if you can't load enough into one slave (because you're limited with RAM) use two. or three ...
i think i did the math already: 24bit 44.1 stereo is ~260 kB/s that gives times 64 tracks ~ 16.5 MB/s which is close beyond 100 Mbit/s but far below 1Gbit/s ...
assuming now theoretically _every_ package would collide we are still below 50% of the gigabit network capacity (caused by the repeated send of packages) we would still be on the safe side. such a collided package would be delayed for average 14 microseconds, which is more than a factor of 1000 below usual soundcard latency.
so to talk about network timeouts isn't of any relevance - there are a lot of other reasons for dropouts way before ...
christian
and remember: only a CRAY can run an endless loop in just three seconds.
