Looking at getting Quad Core 3.0 GHz, running Leopard 10.5.1

[Ruzzo]

Thinking of getting the Quad core 3.0 GHz - with Leopard 10.5.1…to run M-Powered 7.4

Should I expect issues with Pro Tools..even though M-Powered is not officially supported in 10.5.1?

Thanks

[Ruzzo]

Forget that I asked - I knew the site said it wasn't compatible, but I thought i saw on here where folks were running it on 10.5.1 anyway...i was mistaken.

[m01]

Hi Ruzzo,
I had to make the make the upgrade to Leopard mac book 2.4Ghz and I use M-Powered. I'm currently running 10.5.2 and my PT 7.1.1 works for basic vocals. (Using Ozonic interface)The only troubles I've run into are that my comp. crashes after I'm done and unplug my firewire. So I can work but just expect it to do this once I finish. The other problem I ran into and am still awaiting an answer on is I tried using midi with my keyboard. It records it but won't play it back with sound and I think that maybe that the patches aren't readable and I don't know how to fix it in addition to not being the sharpest tool during the initial set up.
Hope that helps a bit. If you can you hold out till digi gets things worked out within the next 2-3 months I'd wait.
I miss Tiger, but it does work for me in the most basic capacity.


m01

[ericdano]

Thinking of getting the Quad core 3.0 GHz - with Leopard 10.5.1…to run M-Powered 7.4

Should I expect issues with Pro Tools..even though M-Powered is not officially supported in 10.5.1?

Thanks

As I posted in a previous post, I'm running ProTools M-Powered 7.4cs3 (and now cs4) on a Quad Core MacPro (2008 model). You need to set the number of CPUs to 4, and it works fine. I actually have mine set to 3. I'm running Altiverb and McDSP plugins, no issues at all.

It is a whole other story trying to do this on my iMac though. Setting the cores to 1, and using a M-Audio Fast Track Ultra interface, I get stutters and all kinds of strange things.....It is good for basic recording...sometimes....

Actually, I think it might be an issue working off a firewire drive. I noticed something similar when I tried to work on a project with my MacPro that I had brought from the iMac on a Firewire drive. The MacPro CPU usage was a lot higher, and it glitched a couple of times during playback. Moving the project to the internal drive solved the problem.

Anyhow, your mileage will vary, but I'm currently working on a 22+ track project on my MacPro and it is going perfectly.