Sorry Martin
I posted re snow leopard, not leopard hence the (my) confusion.
Colin
194,228 users have contributed to 42,914 threads and 257,937 posts.
In the past 24 hours, we have 2 new thread(s), 13 new post(s) and 88 new user(s).
I must of missed the post Colin. Glad to hear we're moving forward in the process. Been a long wait..... Thanks for the update.
Thanks Martin. One other question..... If I use a single i7 slave computer and my MacPro 8-core for sequencing, considering your testing, will MIR be able (on a single slave i7 computer) to handle the exact same template that was used in the VE Tutorial Demo where a slave had two instances of VE and an instance of VE on the Sequence Machine? I'm trying to obtain a baseline as to how large a template, we the users can have if we purchase an i7 PC for a slave and use MIR for ALL orchestral template needs. I think your Video Tutorial would make a great baseline to work from or will the template need to be scaled back due to CPU resources on the Slave i7 PC considering that all the Reverb processing will be accomplished on the slave?
I ask this because I'm not sure if your using the same reverb engine for MIR that you have for the Vienna Suite Reverb but I have noticed a significant increase in CPU usage when using the VSL reverb in a template compared to Altiverb (Todd-AO). In using only 16 channels of a single VE instance and having the reverb run within Cubase, comparing the two, my CPU goes from approx 35% to 60%, just switching reverbs. I hope you understand my concerns and want to understand expectations before I make another computer purchase. Thanks in advance for your response.
With the current MIR design, it won't be just a matter of adding another slave to increase template size as with VE..... one slave will need to handle everything -- if I'm understanding correctly how MIR is going to work.....
Martin,
Will VE-Pro have the ability when used as a plug-in to have more than 16 MIDI channels available as it does as a stand-alone? If VE-Pro is not memory constraint, then it would be nice to have all the instruments required (as much as available memory will allow) in a single instance of VE plugged into the sequencer for audio return. Please advise......
Thanks
Martin,
Will VE-Pro have the ability when used as a plug-in to have more than 16 MIDI channels available as it does as a stand-alone? If VE-Pro is not memory constraint, then it would be nice to have all the instruments required (as much as available memory will allow) in a single instance of VE plugged into the sequencer for audio return. Please advise......
Thanks
If you really mean VE Pro, then it is already the case that multiple MIDI ports are possible. The only exception to this is for those people using AU, and this is because of the limitation imposed by the AU spec.
DG
@DG said:
If you really mean VE Pro, then it is already the case that multiple MIDI ports are possible. The only exception to this is for those people using AU, and this is because of the limitation imposed by the AU spec.
Woops, I mean MIR. I was thinking of VE-PRO only having 16 Midi channels in the AU spec when using Logic. Was wondering if MIR when implemented on the Mac will have the same limitation or is there a solution around this? Cubase & Pro-Tools - there is not an issue.