Voxengo Premium Membership - All Voxengo Plugins For a Fixed One-Time Fee
Forums     Plugins     CurveEQ Beta 1.8c released

This topic was created before release of the latest product version, and it may contain details irrelevant to this version.  Replying is disabled for this topic.

Last

Next

Previous

First



OK, I hope this one fixes hangups and 'non-standard window close' problem.  Help file has been slightly updated too.

This one's working for me, Aleksey.  The last release was causing some lockups on startup occasionally, but with this release that problem's a thing of the past.  Thanks a lot!


Sorry to say, still the same problem with closing the GUI.

I have to say, that this is not a show stopper.

As the first click does nothing, I'm warned, to use the normel method to close the window !

It might as well be a SX 1.05x problem.

Maybe we should wait for 1.06 ...

Some news :

Same error with 1.7 versions :(

Not happening with EssEQ 1.1 :)

( didn't have time to update ... )

bye, Jan


Ok, Jan.  Could you try this with v1.8c:

Instantiate plug-in and open its GUI.  But don't hover your mouse over the control surface (this is important).  For example, move your mouse to 'out gain' slider and then try to close window.  I think there can be a problem closing GUI window if your mouse is currently pointing the control surface.


Yep, clicking on the slider, closes the window as expected.

BTW.:

Since I'm testing this, another weird thing happens :

I often get an XP Blue Screen, when turning of my PC, at the end of the day.

Error message is :

IRQL_ NOT_LESS_OR_EQUAL

bye, Jan


Hm..  I really don't know too much about XP.  Do you think this bug is interconnected with CurveEQ?

Very impressed with the sound quality of CurveEQ and Sonic Finalizer, but when I tried them within existing projects I found that they introduced intermittant clicking in the audio.

As a test, I tried replacing VintageWarmer + Waves L1 (which I find to be a fairly heavy CPU load) with Sonic Finalizer on a project that was showing less than 50% CPU load.  Load went up by about 5%, but the dreaded crackling started.

Since the machine is a well specified dual 2.2GHz Xeon running XP I wonder if you have a possible problem in relation to dual processors?


If you are using Cubase, the only way to get rid of crackling is to increase latency.

Crackling is most frequent with CurveEQ, because it uses block processing that loads CPU every 2048 samples, so if your soundcard latency is about 256 samples, every 8 blocks CPU usage will be used much higher than always and this will result in crackling.

Since Sonic Finalizer loads CPU evenly, it must not crackle in excessive way.

In any case increasing sound card latency must help.


Aleksey Vaneev wrote:

Hm..  I really don't know too much about XP.  Do you think this bug is interconnected with CurveEQ?

Well, I thought it was caused by the non standard closing of CurveEQ,

'cause this started, when I started testing the 1.8* betas.

BUT,

I was wrong :)

Did some thorough testing today and found that CurveEQ is NOT causing the blue screens !!

Also, middle click on the fader works flawless,

so I have no further complains !

bye, Jan


Aleksey Vaneev wrote:

If you are using Cubase, the only way to get rid of crackling
is to increase latency.
Thanks, I wasn't looking for a way to work around the problem, I was giving you some feedback on the bug.  I have done some more empirical testing with System Monitor and I can see that one of the hyperthreads is being loaded excessively compared to the other three.

In comparative tests, VintageWarmer and SIR both use slightly more CPU than your products, but don't cause any audio drop-outs, so I would suspect perhaps an inner loop problem in your code.

Note that both CurveEQ and Sonic Finalizer have severe stability issues under Cubase SX.

Sonic Finalizer :

Flipping between patches with audio running periodically causes very loud bursts of oscillation.

Disabling and then re-enabling using the blue 'power switch' causes the sequencer to crash out to the desktop quite frequently.

CurveEQ :

Failed to load plug-in on one occasion.  Sequencer crashed.

Attempting to replace CEQ with a different plug-in in the same slot crashes the sequencer.

Note - switching off the visual monitoring results in negligable saving in CPU resources.

Let me know if there are any other tests you would like me to run?

This topic was created before release of the latest product version, and it may contain details irrelevant to this version.  Replying is disabled for this topic.

Last

Next

Previous

First