CPU overload on example track!?!?

[AD80]

crystals first preset (atmosphere) just went to 20% cpu. Its a real mother for cpu i've read.

I'm not ill then?

Mine goes up to 20% then settles at around 10%. This is while still online and with anti-virus on and no XP tweaks.

[Karbon L. Forms]

Isn't there a setting in the tracktions settings page to adjust for p4 denormalisation? I'm not sure, 'cos i've an athlon processor, so it's never bothered me. Not got T in front of me either, but don't you just turn something on there ...?

Good f**king lord above us! I just looked and you are indeed right!

"add low level noise to avoid denormalization"

Tiny bastard font as well! Can't be arsed testing it now - I'm in chill mode (ie mildly drunk).

None of you other guys notice that?

Suffering f**k, that's annoying.

Nice one mate!

f**ks sake!

Sorry about all the swearing but I am scottish.

[AD80]

Well even that's not completely effective some times. But it helps.

[valley]

Well even that's not completely effective some times.

Any of the time?

It only stops plugs denormalising on values input to them, but in most cases the denormal values are generated inside the plug, which can't be protected against anywhere except inside the plug.

Best cure for denormalisation : don't use plugs that denormal.

[AD80]

[P.T.]

I thought I heard that the newer P4 had fixed the denormal problem.

Is that not true?

I don't know as I am still on a PIII?

[Karbon L. Forms]

Any of the time?

It only stops plugs denormalising on values input to them, but in most cases the denormal values are generated inside the plug, which can't be protected against anywhere except inside the plug.

Ah well, excitement over. So the delay doodad was maybe just doing a diminishing internal sample thing and hitting those wee numbers?

I'll try the demo again later with noise on.

[DarkStar]

I decided to do a complete port of my cubase project to tracktion. . . . now i'm replicating the entire VSTi/FX chain in T.

If you feel real lucky, you could add the dub-delay filter in at some stage and see what happens.

I'm half way through and i've got a feeling in my water that T (see! I'm calling it "T" already!) is the girl for me. !

Real glad you're on board, you won't regret it.

BTW, in the demo the buzzwav2 stopped at bar 24 and the problem started at bar 33 - this is a distance of 8 bars - is this just coincidence or some bug in dub-delay or some consequence of the dub-delay settings? Just a thought.

[Karbon L. Forms]

If you feel real lucky, you could add the dub-delay filter in at some stage and see what happens.

Yeah. I'll have a play about - investigate the 8 bars thing maybe.