201,360 users have contributed to 43,244 threads and 259,255 posts.
In the past 24 hours, we have 5 new thread(s), 15 new post(s) and 56 new user(s).
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.
[...] 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.
... 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
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
