Hi there, tried the trial, and it seems that when i've got two tracks and one of them is stopped or paused, if any fuction on the EQ isn't on the default position the prog becomes extremely slugish (100% cpu load), but as soon as i press play returns to normal, or when i reset the EQ settings it returns to normal too, if i don't reset the EQ settings when a new track is added and is being analyzed it happens the same thing.
Maybe it's some kind of limitation of the trial, but it seems a littlle strange!
I've got a slow computer P4 1.7 1gb ram, but besides that the prog runs almost flawlessly!
Will probably buy it as soon as i can afford it, the only glitch will be this small (or big) bug, if it is a bug!
Keep up the good work!
Take Care
Maybe it's some kind of limitation of the trial, but it seems a littlle strange!
I've got a slow computer P4 1.7 1gb ram, but besides that the prog runs almost flawlessly!
Will probably buy it as soon as i can afford it, the only glitch will be this small (or big) bug, if it is a bug!
Keep up the good work!
Take Care
geposted Thu 11 Jan 07 @ 3:59 am
djcel
The high cpu with eq on stop is due to underflow exceptions being triggered on some CPUs when the coprocessor deal with floating-precision numbers nearing zero.
It's the case for the Intel Pentium 4 and Powerpc.
If you're curious, here's a paper speaking about that problem: Here
[sent by dev staff]
It's the case for the Intel Pentium 4 and Powerpc.
If you're curious, here's a paper speaking about that problem: Here
[sent by dev staff]
geposted Thu 11 Jan 07 @ 11:00 am