Forget TLs Maximizer or Kjarhus Classic Limiter ..

[Roman Empire]

All this I did with winamp, because my wavelab fails to load energize II.
Does anybody else have this problem?

did you make sure to put the EnergizeII.in file in your root of c:\ like the instructions say?

Yes. At first I did not do this and no sound came out of winamp, and then I read the instructions about doing this, so now it works - but still only in winamp

[JonnySun 2.0]

Because it's only for winamp?

[Roman Empire]

Because it's only for winamp?

There was a link posted here to a ziparchive that contained both a dll for winamp and one for the vstfx version.

[Dazza66]

Because it's only for winamp?

There was a link posted here to a ziparchive that contained both a dll for winamp and one for the vstfx version.

I have the dll working fine in FL Studio 5.02. As it says in the instruction, make sure the .in file (supplied in the download here: http://www.bustad.com/energize/download.htm )is located in the directory C:\ (ie: the root directory of your hard-drive). Don't rename the .in file, or the dll won't find it!

My impressions: well it makes the mix a lot louder and cleaner(?). I'm not sure how it works, but the difference is very noticeable - roll on a version that has tweakable parameters in a GUI (even a default GUI would be nice!)

[PeterL]

All this I did with winamp, because my wavelab fails to load energize II.
Does anybody else have this problem?

did you make sure to put the EnergizeII.in file in your root of c:\ like the instructions say?

Yes. At first I did not do this and no sound came out of winamp, and then I read the instructions about doing this, so now it works - but still only in winamp

I have the same problem. I put the EnergizeII.in in C: root directory and EnergizeII.dll in VstPlugins folder. When I load the plugin in Wavelab, it crashes Wavelab. When I load the plugin in CubaseSX, the plugin loads, but no sliders are available !? I use v1.40.

[Paulie Phonick]

I have managed to run the plugin in Renoise without problems. I'm not very keen on the sound though. It certainly is loud, but somehow ugly. Might be the case with default parameter values, I admit I didn't take time to tweak em, cause setting parameters via a text config file with a fixed location in C:\ is about the ugliest solution I have ever seen! Come on, would mapping parameters to VST standard be really that much work? Hope not!

[kilroy]

It certainly is loud, but somehow ugly.

Funnily enough...a rather appropriate descriptiion of a great deal of popular music.

[Roman Empire]

All this I did with winamp, because my wavelab fails to load energize II.
Does anybody else have this problem?

did you make sure to put the EnergizeII.in file in your root of c:\ like the instructions say?

Yes. At first I did not do this and no sound came out of winamp, and then I read the instructions about doing this, so now it works - but still only in winamp

I have the same problem. I put the EnergizeII.in in C: root directory and EnergizeII.dll in VstPlugins folder. When I load the plugin in Wavelab, it crashes Wavelab. When I load the plugin in CubaseSX, the plugin loads, but no sliders are available !? I use v1.40.

Good to know that I´m not alone!
That there are no sliders is because it´s got no GUI, you know.

But anyway, a workaround to the wavelab prob is to use write to wave from inside of winamp.
If you need further modification, you can then import the wave into wavelab.
I tried this, and added 6 db boost with buzzmax3, and got the mix louder than the things I´m normally drewling over that are commercially mastered - without no damn pumping!
Of course there ain´t much dynamics left if treating the music this way, but it´s nice now being ABLE to do it, and find out what suits the music the best.

[jens]

That there are no sliders is because it´s got no GUI, you know.

bollocks!

[Paulie Phonick]

It certainly is loud, but somehow ugly.

Funnily enough...a rather appropriate descriptiion of a great deal of popular music.

True true.

[;-)]

I mean, GUIless plugins is the one side (I could always live with) ...
But makin a plugin, which is merely editable "offline" with an config file (which by the way has to be placed into a certain location on harddisk too) is quite more than stoopid.

Completely useless to me (cause I am a "tweaker" and power user and can't work with crap like that).

So I would always prefer the tools you mentioned as "to forget".

.

[Roman Empire]

I mean, GUIless plugins is the one side (I could always live with) ...
But makin a plugin, which is merely editable "offline" with an config file (which by the way has to be placed into a certain location on harddisk too) is quite more than stoopid.

Completely useless to me (cause I am a "tweaker" and power user and can't work with crap like that).

So I would always prefer the tools you mentioned as "to forget".

.

It´s not useless as long as it does something no other plugin can do, and it was not stupid of the developer, because if he did not do this, there would have been no plugins at all doing what EnergizeII does.
But wouldn´t it be easy to just throw a synthedit GUI on top of it?

[;-)]

I mean, GUIless plugins is the one side (I could always live with) ...
But makin a plugin, which is merely editable "offline" with an config file (which by the way has to be placed into a certain location on harddisk too) is quite more than stoopid.

Completely useless to me (cause I am a "tweaker" and power user and can't work with crap like that).

So I would always prefer the tools you mentioned as "to forget".

.

It´s not useless as long as it does something no other plugin can do, and it was not stupid of the developer, because if he did not do this, there would have been no plugins at all doing what EnergizeII does.
But wouldn´t it be easy to just throw a synthedit GUI on top of it?

No, because the parameters cannot be edited in realtime obviously.

The plug loads it on initialization.
That is quite stoopid, I think. Because then you have to reload the plug all the time after editing some parameters and you never can hear, what the parameters do in realtime.

Also there are other problems too: It don't report the latency right to the VST host.

That is all a brunch of code "loveless" put together. Makes something that may be useful to somebody, but not really usable in a real production situation / environment.

Sorry. That's what I call crap then. It "beams" you back into last century.

If I actually "compile" a VST plugin, why to f**k I cannot implement the parameters right then (instead using a 80's technique of an external initialization file, which has also to be placed manually by the user) ...

That (implementing an external initialization file) actually makes more work to the developer than implementing the parameters right into the plugin. I guess he had a certain fun to delivering it that way to us. I don't think it is was "unability" ...

.

[Roman Empire]

I think you forget that this plugin is free, and a free plugin that nomatter that it´s obviously in a very early stage of its development does something that no other plugins can do, also if not tweaked at all by the user, makes it useful - as long as that what it does is something that people need, and reading this thread proves that this is the case.
It is completely obvious to everybody that this plugin have more potential than in its current stage of development, but if the programmer is reading this thread and sees that there are people outthere being so spoiled that they´ll spend all their energy complaining about a free product, there´s a chance that he´ll just stop developing on it.
That´s not excactly what you want, is it?

[martian]

doesnt work for me in sx3.1, get an error and no parameters on the plug.