My old system was a p4 2.6 with 1 gig RAM. Using FAT mode in Cubase SX2, CPU usage was around 60% for 1 instance of MC. The same system running wavelab only saw 18%.

I just upgraded to a Quad Core 2.6 mac pro with 4 gigs of RAM. Using PTHD, and fat mode, a single instance of MC uses approx 45%.

All of my other plugins have experienced HUGE performance gains. Why doesn't MC reflect this huge increase in processing power? It seems oddly inneficient in certain DAW apps.

-Z-

The performance depenends on many issues including plug-in version, sample rate, audio buffer setup and other factors.
I don't know all those important details of your setup but from our expearience you should notice a similar increase in processing power that you notice with other plug-ins.
Please notice that every host is using CPUs and internal CPU cores in a different way. It may also display performance ina different. For instance it is possible that the application is turned to run on a single core r it shows how much the plug-in is using of a signle core while other cores are still ready to run other instances of the plug-ins.

Regards,

The PT sessions are 24 bit/44.1 and the audio buffer is set to 256 samples. More importantly, these settings are exactly the same as I used with the previous projects/system.


AFAIK, PT is set up to handle multiple cores, but I will check into that and report back...

Thanks,

-Z-

Which version of the plug-in do you use?

I'm using 1.5.4 ilok.

Using MasterComp 1.5.4, in a 24/96 project with I/O buffers maxed at 1024 and Process Buffer maxed to Large, I can't run even one instance of MasterComp with FAT setting engaged at all. Without FAT my CUP meter shows 50%, with FAT it red-lines into 100%. No other plugs at all. Ouch, that hurts. What can I do?

Mateusz,

I'm not trying to be a pain here, but there are clearly performance issues with mastercomp in various hosts. None of my other plugins are nearly as sensitive to the host application for performance as MC.

Have you actually tested this plugin with Protools HD on a Intel Mac? If you have then you must agree that the current situation is unusable.

Thanks,

-Zak

I just tried to use MC in a PTHD session at 96k. This is a Quad 2.6 macpro and in fat mode, I was unable to get even a single instance!!!!!
When I switched it to regular mode it crashed PT and I had to force quit...not happy.
Clearly something is wrong.This is the ONLY plugin that's giving me grief with my system.

Can you please address this problem or at least aknowledge it?

Thanks,

-Zak

MasterComp is CPU hungry plug-in. The real CPU usage depends on host type, buffering settings, host's CPU scheduling, sample rate and FAT of course. We will take a closer look at this problem.

Which version of PTHD do you work on?

Regards,

just a question: i thought fat is for upsampling internally to get better results (less distortion etc.).
so if i have already a high samplerate like 88.2 or 96 khz, does engaging fat make any difference to the sound ???
mathias