Isn't it lovely? Everyone's waiting for the christmas parcels :)
Me too :)
I don't regret to have purchased my first VI SE-Downloadpack even more now VE3 is announced!
Angel
199,036 users have contributed to 43,150 threads and 258,880 posts.
In the past 24 hours, we have 5 new thread(s), 13 new post(s) and 63 new user(s).
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
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
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
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 fantastic
would 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
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
Christian:
I note your lack of enthusiasm for PPC Macs with VE 3. I currently own a dual 2.5GHz G5 machine and am planning to buy a Mac Pro 8 processor machine as my main computer and to use it for Logic, DP etc. and samples while retaining the G5 as a slave for more samples. Is this unlikely to work well with VE 3? Would I be better off selling the G5 and replacing it with something else?
I'd very much appreciate your thoughts,
Stephen
haha - its not a lack of enthusiasm, it is just that they do not perform (as we understand performance currently) - you can't open as much instances on a G5 as you can on a macPro ... is it the little vs. big endian thing or the processor pipeline, don't ask me why in detail ...
the 8-cores ... if you like to hear my opinion ... they are only a minor step forward in relation to the last generation macPros, actually not even compared to the 4-cores. i'm not even sure everything is scaling as expected across the 8 proc. intel themselves releases some *code optimization tool* lately to allow full access to the capabilties of these processors ...
regarding several reports about the new firewire chip and strange USB behaviour it would maybe a good idea to let their first release pass by until everything is clear ...
as i read the news the Q9000 (quadcore penryn) series is a little bit delayed but should be delivered soon.
my 2c only, christian
@nomad said:
haha - its not a lack of enthusiasm, it is just that they do not perform (as we understand performance currently) - you can't open as much instances on a G5 as you can on a macPro ... is it the little vs. big endian thing or the processor pipeline, don't ask me why in detail ...
the 8-cores ... if you like to hear my opinion ... they are only a minor step forward in relation to the last generation macPros, actually not even compared to the 4-cores. i'm not even sure everything is scaling as expected across the 8 proc. intel themselves releases some *code optimization tool* lately to allow full access to the capabilties of these processors ...
regarding several reports about the new firewire chip and strange USB behaviour it would maybe a good idea to let their first release pass by until everything is clear ...
as i read the news the Q9000 (quadcore penryn) series is a little bit delayed but should be delivered soon.
my 2c only, christian
good to hear everything works flawless with your 8-core, jbm - its just that several reports reached my desk that USB gets lost unexpectedly.
i've been under the impression the new macPro is using the E5472 XEON with an intel 5000 family chipset and here i'm considering the processor bus to be too small for 8 cores (or better: for what 8 cores could process in the sampling world)
christian