christian you surprise me! you are in fact starting a pc vs mac debate which I won't counter your arguments, which are of course the pc side arguments, and there are many on the mac side, or at least arguments to neutralise some of yours, again I don't want to go into it because it's something that has been running SINCE 1997 all over the net and beyond, and has been discussed and argued to death. As I said, you're the expert, if you decide that it can't be done on Mac or is too expensive or bad for the project, people will trust you decision on that, however, I think backwards compatibility that you have pointed out, at the risk of countering your argument, is one of the great things about mac osx in my opinion, so, it does often come down to a matter of perspective much of the time. I still don't however understand your point on hypocrasy... from reading the thread I think nobody has denied the fact that computers cannot presently run a VI+MIR set up on a single machine, or could in the near future - we're just debating being able to run VI, mix down to bus groups or just audio files, then playback the audio files through MIR with say a machine predicted to be available around January (8cpu machine). In THAT case, it would be good for somebody like myself who would possibly buy such a machine to have it capable of running both VI and MIR on the same machine (but not necessarily at the same time), as I only need then to invest in one hardware box of cpu's instead of two. At least that was my point perhaps it wasn't clear from what I said. PC's and Macs are fairly on par in terms of power and architechture at least compared to PPC Macs, I'm no expert but if you can run most windows apps paralell, that's a pretty big testament to the fact, however, nobody is arguing that MIR is a unique piece of software probably requiring fulll dedicated access to the hardware. Still, my point is simply that it would be better as a mac user to buy one machine rather than two, even if I have to mix down to audio buses or many stereo files than having two machines (in which case I would still need to find a way to send the audio into the pc either via audio files, hard disk or some kind of audio or network streaming,), and although the "single project file" argument seems a small and trite argument on the surface, I think in the real world with how much work people do in audio to be able to save and archive a single project file is really quite a big issue, not just for convenience but also for "backward compatibility" he he. [:D]
However I understand from a purist point of the view the idea is that MIR take the direct output of VI and mix it - that would depend on whether MIR will be designed to run with the outputs of VI being streamed into it over network, or if it will be able to run from audio files generated from VI - which is how I have to mix now anyway.
Miklos.
However I understand from a purist point of the view the idea is that MIR take the direct output of VI and mix it - that would depend on whether MIR will be designed to run with the outputs of VI being streamed into it over network, or if it will be able to run from audio files generated from VI - which is how I have to mix now anyway.
Miklos.