Voxengo Premium Membership - All Voxengo Plugins For a Fixed One-Time Fee
Forums     Plugins     CurveEQ Prerelease BETA testing v1.7

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



Hello,

I have uploaded a new prerelease beta version of CurveEQ.  Change list is as follows:

1.  Several minor bugfixes.

2.  Performance of EQ engine was improved by at least 70%.  This means one can run 70% more EQ plug-ins in the same project now.  This allows to use CurveEQ plug-ins seamlessly even in audio track inserts.

3.  16 new exclusively-captured gear options added.

4.  Gear option list was upgraded to a scrolling list with arrows.

5. "/" and "*" labels on buttons were changed to arrows.

6.  IMPORTANT ADDITION.  Now it is possible to enable saturator's latency buffering.  It can be enabled or disabled in "?" screen.  Please, note that when this feature is enabled plug-in will issue additional 4500 samples of latency while allowing host application to correctly buffer saturator's latency.  If your host does not buffer plug-in latency at all, there is no reason in enabling saturator's latency buffering.  Also, when this buffering is enabled, plug-in will consume slightly more CPU power.  Saturator's latency buffering works only with sample rates up to 192 kHz.

7.  Help file updated.

8.  Added "pre gain" control which is showed on the control surface in the form of a horizontal dashed line.  This control is useful when saturator is enabled.  To get this control visible 0 dB baseline must be dragged first.  Please, note that dashed line snaps to 0 dB baseline if moved close to it.

9.  New factory presets added.

10.  Main skin was changed.

11.  Captured spectrum file options added.

URL for download: http://www.voxengo.com/downloads/

Comments and suggestions are welcomed as always!

Cheers,

Aleksey.


Hi

I am testing out this EQ, and so far I really love it!  I was able to apply the EQ and really smooth out and "round out" this kick drum in a track I am doing and make the mix sound overall more smooth.  It seems to be quite a useful tool so far.

A few questions/requests.

Testing in Cubase SX, it doesn't seem to always compensate on track insert.  I have it on one track insert in the project, and that seems to stay in time.

I then put it on another track, and in this case it introduced a delay causing the audio to fall out of time with the rest of the project.  Thats confusing me.

Also, it does not appear in the "apply fx" process dialog in Cubase SX.  I am using Cubase SX 1.03 legal.

Request:

Can there please be a broader manual with greater explanation as to the functions and ways of use for the plugin?  I do not fully understand how the curves/saturation modes etc are doing.  Also, it seems to me that when applying lets say the "tape" curve, it then makes that curve fixed.  Is there a way to lets say, apply the high end sound of tape, but then not have it cutting off all of the bottom end?  Ie, starting from a particular frequency overlay, and then modifying aspects so that it fits better.  So in this case, a tape impulse sound which gives you more the sound of tape on a harsh top end, but leaving the heavy bottom end untouched.


Sync problem can appear if you are using saturation in one of the plug-ins.  If you want to get rid of it, press '?' and enable saturator's latency compensation (Release package will make it enabled by default).

As for 'apply fx', I will check it out.

It is impossible to give comments on gear options, because they are very different and full description cannot be given.  Sometimes low end of some curves can be adjusted with ordinary curve editing (you can check 'vintage mastering' preset to see how this works).

Saturation modes are also difficult to explain.  I guess it is best to try different modes and choose the most appropriate.

Cheers,

Aleksey.


I was testing v 1.7 in both cubase sx and nuendo (PC versions)

I noticed alot of latency that didn't seem to be compensated for in either app.

Am I doing something wrong .

I love the sound but the uncompensated latency was a real problem.

Looking forward to your response.

Thanks


I forgot to mention in the previous email...the latency was a problem with and without the use of saturation..

Thanks..


I have read somewhere that Cubase SX at least has got compensation only on track inserts and not on main bus and sends.  Actually, there must be no problems in track inserts.  If that does not answers your question, please, be more specific on what you are doing and what do you expect to get.

Thanks,

Aleksey.


Aleksey.

I reinstalled the demo and enabled the latency buffer and now everything works and sounds great.

I do notice the plugin is pretty cpu intensive when buffering is enabled.

Can you tell me how much latency is added when saturation is used.

I could see using this eq on a lot of tracks but I would need to find away around the toll it takes on my processor.

Are there any other tips or tricks to minimizing the cpu load?

Thanks and love the sound of this..


buffering did solve the problem in SX with the latency on the insert

but I still don't see it in apply plugins

another bug I discovered:

I was trying to bounce a file in Wavelab with this chain.

Voxengo

Sonic Foundry Acoustic Mirror Impulse

Waves L2

If I do that, the output file had some strange distortion, with only some sound in the left file.

Now, if I just bounced Voxengo + L2 it was ok, and then Acoustic Mirror + L2 it was ok.  Somehow the interaction of the plugins with the chain is causing an issue. perhaps because of how voxengo buffers, its causing an overload?  I am not sure.  I have never seen this effect bouncing before which is why I mentioned it here.


I have uploaded the latest development snapshot version: http://www.voxengo.com/VoxengoCurveEQ.dll

It possibly fixes 'apply fx' problem.  Also it implements more optimizations and clean-ups.  However, spectrum monitoring (if not OutAvg) temporarily processes only a single channel (left or right depending on channel setting, if it's 'mix' then it shows the right channel).

As for performance of CurveEQ, actually it eats pretty much if you compare it to any other EQ.  The most efficient mode is when saturation and VP are turned off completely.  For example, in this mode I think I can get about 25 stereo channels with CurveEQ on my Athlon 1333 without full load.  If you go with mono tracks, multiply that value by a factor of 1.7 at least.

I was trying to bounce a file in Wavelab with this chain.
Voxengo
Sonic Foundry Acoustic Mirror Impulse
Waves L2
I can't say for sure what can cause this.  I'll check it out.  But I clearly don't see any problem in CurveEQ itself.  Actually, I have read many complaints about Acoustic Mirror's performance in non-sonicfoundry environments, so this might be one of those problems.

Cheers,

Aleksey.


Hi Alesksy,

I was rather dissapointed to hear your last response to having a clearer manual.  I am experimenting with the demo of curve eq, and have mixed fellings about it.

On the one hand it adds a certain polish to my mixes, and on the other hand it ruins them.  Now I am sure that this is not because your plug in is bad, but rather because I do not understand how to use it best.  I have read the manual 3 times over, and consider myself a competent audio engineer, so I can only conclude that the manual needs to be fuller, and have more explanation, especially about the gears.

I appreciate that this would mean more work for you guys, however I know that I am unlikely to purchase this plug in without a more informative manual with examples, otherwise I won't know how to use it right, and will end up paying money to destroy my mixes.

So please do give us more information, and then you will probably get more customers like me who are waiting in the wings at the moment.

By the way I respect the fact that you are on this forum, I wish more companies did this.

Cheers

MD

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