SignalTools - Big CPU hit!

[ricren]

I was waiting for this plug-in because I could really use good “in–the-box” meters. Since Spectrafoo is not longer available as a plug-in in OSX, there’s a void on this department. I really miss the possibility of customize every detail of a meter, like size, scale, colors, you name it.

So I downloaded the plug and I tested it briefly.

The good: is free.

The bad: Big CPU hog. I tested the RTAS version on this Macbook 2.0-2Gig Ram + PT 7.1.1. With a single “phase scope” instance and its window open, in a small session PT becomes very sluggish and the display is a bit jerky. (Not good on meters).
Strangely, the CPU meter inside PT only shows a modest hit (less than 1/5 of scale), but Activity Monitor shows that with the plug-in loaded the machine CPU utilization jumps from 20% to almost 100%, regardless of the setting in the “playback engine” window. Weird.

I could not test it in TDM (still in 6.9.1) so things could be different there.

Ric

[JanuS]

Hmmmm.. I wish I could confirm or deny your foundings, but I'll get an installation error when I want to
install the Signal Tools (HD2 PT 7.1cs7 G5 2.0)
Digi? Is this just the first batch, or could there be more (me?)

[Aquarius]

Hi,
So what's the deal in TDM ?
I'm curious if set to compare to Dolby LM100 (LeqA)
Cheers,
A

[Frank Kruse]

Not here. Dual 2.5Ghz G5. No increased CPU-load. Although the scope reacts so slow it´s far inferior to a hardware scope.

Frank.

[ricren]

The CPU hit is so big that I wonder if this package is UB. May be not. That could explain it.

Ric

[jimlongo]

In a fair sized session with video I experience little CPU hit, but half a HDCore chip.

UPDATE: I just tried it as RTAS, it seems to react the same (except that of course no DSP hit)


Dual2.0G5 / 3GB ram / 7.2

[Kirkland]

Click on "compatibility" in the Signatools section and you'll see that the very first line says "Not yet compatible with Intel Macs". You're running that plug under Rosetta which would explain the steep CPU usage...

[1150Post]

Click on "compatibility" in the Signatools section and you'll see that the very first line says "Not yet compatible with Intel Macs". You're running that plug under Rosetta which would explain the steep CPU usage...

Bingo... Signal Tools is a No-Go for Intel Mac. My guess would be that the Intel Update for Intel will probably coincide with the Intel 7.2 TDM release.