Serato DJ Pro General Discussion

Forum
 Serato DJ Pro General Discussion
High CPU usage on a MacBook Pro using itch 1.03
Talk about Serato DJ Pro, expansion packs and supported hardware

High CPU usage on a MacBook Pro using itch 1.03

EG 2:43 PM - 14 November, 2008
Hello,

I got a VCI-300 recently and played with itch for a few hours. I have the previous model of MBP (2.4Ghz and 4GB of RAM) and get quite a high cpu usage using nothing but itch... No wifi, bluetooth, email notification, MSN, etc.

1 CPU is fully loaded so the fans are at full speed almost as soon as I start itch and I get a few audio artifacts from time to time (barely noticeable but still...). Traktor Pro demo version uses only 15% of the CPU and runs smoothly compared to itch.

Do you guys see this as an issue and are working on performance improvements? Did I do anything wrong? Only switching to the "setup" screen drops the CPU usage of 20% so the UI has something to do with this. Itch is supposed to be "lightweight" so I don't see why Traktor is performing a lot better.

Thanks!
Dj Robin 3:27 PM - 14 November, 2008
Hi,

I have the new MacBook Pro 2.53 GHz and the same problem: Itch needs exessively of CPU-Power, like EG described. Even with the public beta.

The same problem was was there with my iBook G4 (but no problem with a friends normal white MacBook), which was the cause to buy the new MacBook Pro with much higher performance. There I got another heavy problem: The VCI-300 is not completely detected. But that´s off-topic and I ask in another thread for help.
So far after good experience with SSL I´m not very happy to invest 3000 Euro for new and professional System-Components that do not work.

Serato
Zeb 3:40 AM - 4 December, 2008
Another user has reported this on a new Macbook, we have not reproduced this on the latest model Macbook/Pro's or the previous, this is definitely not how it should be.

EG, have you tried using the latest beta version?

Dj Robin, what is the build number of the version you are experiencing this on.
thanks guys, hang in there, we will get this sorted as soon as possible.