Just thought I would update everyone on my current experiments with mac mini's.
Before that though, I would like to report that on my main DAW having the entire Cube installed gives me a start up time of 6mins48 - not good. However subsequent starts are of course much quicker.
Anyway, the MacMini slave idea seems to be working well. I am using MidiOverLan as the transport. Each MacMini is running Bootcamp Windows XP (because that's my sphere of knowledege) and VSTACK, I am using a Core Duo Mini with 2GB Ram and an external 250GB Lacie Mini HD. I also have an Edirol UA1EX attached which pumps audio back to the main DAW's RME Fireface.
I can happily load 12 VIs fully populated mostly with performance legato or trill instruments and play them live without clicking or popping. 16 VIs is possible but I run out of memory if I use all performance instruments - using non-perf smaller patches this works fine too.
The next step is to upgrade my 2nd mini to 2GB which will hopefully be done this week and buy another UA1EX. I will probably add a 3rd later on which will be the last - primarily because my Dr Bott KVM only supports 4 devices.
Stability is great, and I use the Windows Hibernate feature so that I can boot up the Mini quickly and fully populated with VI patches.
My overall plan is to use the main DAW for final mixing, reverb and other plugins (I use Cubase SX and a Powercore) plus it will host one section of the orchestra - probably percussion (as this is the smallest). Each MacMini will support the other sections, e.g. strings, woods, brass.
I hope others find this useful and anyone considering a MacMini as a slave device should seriously consider doing so, they don't take up much space and are sufficiently powerful to host the VIs. Longer term if the Intel Merom processor turns out to be as good as anticipated it may well be possible to replace my large PC DAW with a Mac Mini too as the master DAW.
Regards
Tim
Before that though, I would like to report that on my main DAW having the entire Cube installed gives me a start up time of 6mins48 - not good. However subsequent starts are of course much quicker.
Anyway, the MacMini slave idea seems to be working well. I am using MidiOverLan as the transport. Each MacMini is running Bootcamp Windows XP (because that's my sphere of knowledege) and VSTACK, I am using a Core Duo Mini with 2GB Ram and an external 250GB Lacie Mini HD. I also have an Edirol UA1EX attached which pumps audio back to the main DAW's RME Fireface.
I can happily load 12 VIs fully populated mostly with performance legato or trill instruments and play them live without clicking or popping. 16 VIs is possible but I run out of memory if I use all performance instruments - using non-perf smaller patches this works fine too.
The next step is to upgrade my 2nd mini to 2GB which will hopefully be done this week and buy another UA1EX. I will probably add a 3rd later on which will be the last - primarily because my Dr Bott KVM only supports 4 devices.
Stability is great, and I use the Windows Hibernate feature so that I can boot up the Mini quickly and fully populated with VI patches.
My overall plan is to use the main DAW for final mixing, reverb and other plugins (I use Cubase SX and a Powercore) plus it will host one section of the orchestra - probably percussion (as this is the smallest). Each MacMini will support the other sections, e.g. strings, woods, brass.
I hope others find this useful and anyone considering a MacMini as a slave device should seriously consider doing so, they don't take up much space and are sufficiently powerful to host the VIs. Longer term if the Intel Merom processor turns out to be as good as anticipated it may well be possible to replace my large PC DAW with a Mac Mini too as the master DAW.
Regards
Tim