[quote=Ginge]I doubt it has anything to to with my nose and face
Run the Mac using XP and you will be able to try it. When it's available. If your Mac is fast enough.....
DG
-
@Ginge said:
Is it a technical issue or a manpower-problem that is behind the pc-only decision?at the time the basic decisions have been made the intel Macs have not even been suspected and the PPC have obviously been at a dead end (IBM did not issue the new PPC multi core processors to third parties)
on one hand the already known hunger for CPU power and forseeable road map for intel processors has affected this decision, on the other hand it was clear R&D cannot happen for 2 platforms simultaneously.
finally seeing apple also on intel this turned up to have been a wise decision and now it is as it is, fortunately no development resources have been wasted ...
further decisions about platforms will be made when time has come - any outlook is useless regarding apple's secret and fickle development policy - their road map is simply not calculatable.
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
[quote=Dietz]All this leaves not much to add than - uummm - "Yes"! :-)
Hey, now that you've emerged from your cave, are we going to get any new information about MIR? I would love to see a video of it in action, even if it is just an explanation of how all the components for Vienna Instruments fit in. Pretty please? I'll even promise to be polite on the forum..... Actually I think that the last might be beyond my capabilities, but at least I will try. [;)]
DG
-
@Dietz said:
All this leaves not much to add than - uummm - "Yes"! :-)/Dietz
Hey Dietz!
What would it leave to add, when I said the following:
Since streaming multiple audio channels to the mir machine via ethernet would be taking away quite a lot of CPU power, it would be more likely to be done via hardware digital I/Os (ADAT,Madi,...). Would that leave you with a "uumm - "Yes!"", too??? [;)]
I'm asking, because I need to know for the audiosetup of my studio. I certainly don't expect yout to say anything about mir itself - got that. But since it is very likely to be released in this year, it would be nice to know, wether it's wasted money to go for a DSP ADAT sollution on the vienna slave(s).
Fritz.
-
Sorry, my first message was meant as a joke - I certainly didn't try to sound snotty.
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.
I hope this is cleartext ;-) ... thanks for your interest, Fritz.
/Dietz - Vienna Symphonic Library -
Ok! Thats great to know. Thanks for the information Dietz. PC only would mean, that also the VI slave can be PC only in order to work with mir? in other words: will you be able to connect a mac with these firewire connections to a PC running mir? - Thanks!
-
[...] will you be able to connect a mac with these firewire connections to a PC running mir?
This is how it's meant to work - as long as our developers can keep up with the unexpected changes in Apples's OS-X.
/Dietz - Vienna Symphonic Library -
... though currently it seems the firewire chip manufacturers are troubling us more than any OS issue does ....
too bad such a great protocol (responsibly developed by apple btw and invented for streaming) gets screwed up by a handful profiteers ...
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
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 occure.
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 ....
christian
and remember: only a CRAY can run an endless loop in just three seconds.
