Topic: Preview: Zynewave zPEQ

This topic has 57 replies, 11 voices, and was last updated 19 years, 12 months ago by Conquistador.

Viewing 15 posts - 1 through 15 (of 58 total)

1 2 3 4 →

March 16, 2006 at 18:54 #756

Zynewave
Keymaster

The last week or so I’ve been working on ‘zPEQ’, a parametric EQ plugin which probably is going to be the first official Zynewave plugin. It was not on the plan a few weeks ago, but I came up with some ideas I wanted to follow through. Much of the time was spent on creating a plugin framework, which will be helpful for the following plugin projects. I plan to make a small suite of simple plugins (zDither, zComp, zChannel, zReverb etc.) which will provide a good starting point for many users. It does not offer advanced signal processing, but it integrates well in the Podium UI.

The screendump below shows the current state of the zPEQ plugin. It supports VST 2.4 64-bit processing which was added to Podium recently. The red curve is an optional display of the phase response.

Following the discussion in this topic I ended up with creating a non-ui plugin, with the editor implemented in Podium. This provides numerous advantages: It allows the plugin editor to be embedded in the track inspector. Popup help for the controls in the editor. The layout of the editor will scale according to the available space when you drag the size of the track inspector or the editor window. The plugin can be used in other hosts using their generic plugin editor.

I would appreciate your feedback on some issues I’m undecided on:

Should the zPEQ use fixed band types (low shelf, high shelf, 3 parametric bands) or should there be a type parameter for each band? The screendump shows the type parameters in the separate editor window (for testing purposes). Having a band type parameter allows for selecting a notch filter type, which would not be available in a fixed band type layout. The only advantage to fixed band types is less clutter in the editor. The aim with the z suite of plugins is to keep the number of parameters to an absolute minimum. At a later time I may start on another suite of plugins with more advanced controls.

How do you work with mono/stereo plugins? Should there be two separate plugin dll files?

How should the plugins be installed? Should they be included in the Podium installer, or be available as a separate zip download? Note that since the plugins will not have native editors, the size of each plugin dll file is only around 100 KB.

Should the plugins be free (i.e. included in the Podium demo installer) or should they only be available as a bonus for Podium license owners?

March 16, 2006 at 21:06 #6292

Conquistador
Participant

HO HO! Frits you have done it again! Play down your timeframe for features and then *zap* out of nowhere 🙂

This is great work! The EQ looks like it has always been there in a strange kind of way. I guess the fit is that good.

It supports VST 2.4 64-bit processing which was added to Podium recently.

Ohhh it gets better… 8)

How do you work with mono/stereo plugins? Should there be two separate plugin dll files?

I think they should be separate. The Kjearhus GEQ plug has three variations Mono and Stereo are two of them. Giving people options is always a better idea IMHO. Everyone is happy that way.

How should the plugins be installed? Should they be included in the Podium installer, or be available as a separate zip download? Note that since the plugins will not have native editors, the size of each plugin dll file is only around 100 KB.

I think if you talking about such a small size I would have to say why not just include them in the Podium installer?

Should the plugins be free (i.e. included in the Podium demo installer) or should they only be available as a bonus for Podium license owners?

As a fully paid up owner of Podium 8) it would be nice to have the plugs as a bonus. However…I think it would be far more beneficial to add them to the Podium demo as this of course would be a major step towards elminiating the perception of difficulty people have with Podium. Surely they should be added to the demo. The plugs will help get users up and running with the Podium demo song/s. As Podium owners we would get the plugs anyway. Errr…right Frits? 😀

If getting new users is important (which of course it is for the future of Podium) then by all means add them to the Podium demo download I say.

I plan to make a small suite of simple plugins (zDither, zComp, zChannel, zReverb etc.) which will provide a good starting point for many users. It does not offer advanced signal processing, but it integrates well in the Podium UI.

Clever stuff with the z theme. I totally agree with your choice of plugs as well, all the key areas are covered. Very nice. You said they will not offer advanced processing. What do you mean exactly as they already will be 2.4 compliant with 64 bit processing or is that just the EQ?

March 16, 2006 at 21:31 #6293

Zynewave
Keymaster

You said they will not offer advanced processing. What do you mean exactly as they already will be 2.4 compliant with 64 bit processing or is that just the EQ?

What I mean is that the plugins will be based on existing DSP technology. I will not spend time on trying to invent new stuff, until I have the bases covered with the z plugins. Currently the zPEQ is based on the public domain RBJ cookbook filters, which I suspect is used in a large number of freeware and commercial plugins.

March 16, 2006 at 22:04 #6294

Conquistador
Participant

@Zynewave wrote:

You said they will not offer advanced processing. What do you mean exactly as they already will be 2.4 compliant with 64 bit processing or is that just the EQ?

What I mean is that the plugins will be based on existing DSP technology. I will not spend time on trying to invent new stuff, until I have the bases covered with the z plugins. Currently the zPEQ is based on the public domain RBJ cookbook filters, which I suspect is used in a large number of freeware and commercial plugins.

Ahh. OK. Thats fine. I thought you meant something else. 😉

March 16, 2006 at 23:06 #6295

Max
Participant

@Zynewave wrote:

Should the zPEQ use fixed band types (low shelf, high shelf, 3 parametric bands) or should there be a type parameter for each band?

EQ types should be selectable IMO, ’cause plugin will be much more flexible. If you want to save some place in editor, I’m sure there should be a compromise… Something like rightclick on a band in a graphical part of editor to change the type of the filter. BTW, what about lp/hp types? It’s very useful sometimes. For example, HP filter to cut lowfreq noises to prevent DC offset. I use it a lot, and I will be happy to use zPEQ for it.

@Zynewave wrote:

How do you work with mono/stereo plugins? Should there be two separate plugin dll files?

Personally I prefer to choose between stereo/mono processing right in plugin window.

@Zynewave wrote:

How should the plugins be installed? Should they be included in the Podium installer, or be available as a separate zip download?

I think that they should be included in Podium installer, but with an option to install them or not.

@Zynewave wrote:

Should the plugins be free (i.e. included in the Podium demo installer) or should they only be available as a bonus for Podium license owners?

I agree with Conquistador. First of all, plugins pack should be useful for new users. So they should be included in demo installer.

March 17, 2006 at 03:20 #6296

darcyb62
Participant

This looks exciting. I agree fully with Max’s responses on this.

March 17, 2006 at 06:15 #6297

super_crunchy
Participant

I agree with Max’s responses too

March 17, 2006 at 06:16 #6298

super_crunchy
Participant

A size of 100kb is nothing in the scheme of things too, and it would be great to see new users’ benefiting from having demo project files to work with, with plugins loaded, so they understand how Podium works

March 17, 2006 at 10:05 #6299

Jaegerteam
Participant

have no special ideas or suggestions,
just want to say that it is great great great stuff !

March 18, 2006 at 18:44 #6300

Zynewave
Keymaster

Ok, the band type parameter stays. I have settled on the following types:

Low shelf
High shelf
Parametric
Band reject
Band pass
Low pass
High pass

The shelving types use Q as a slope in dB/octave.
The parametric and band reject/pass types use Q as bandwidth in octaves.
The low/high pass types use Q as a resonance value.

I’m having fun with this 🙂

March 19, 2006 at 15:23 #6301

Max
Participant

@Zynewave wrote:

I’m having fun with this 🙂

Can we join you in playing with the first Zynewave plugin? 😉

March 19, 2006 at 17:34 #6302

darcyb62
Participant

@Max wrote:

@Zynewave wrote:

I’m having fun with this 🙂

Can we join you in playing with the first Zynewave plugin? 😉

I’m with Max on this.

March 20, 2006 at 08:58 #6303

Conquistador
Participant

My guess is Frits is probably 99% down the line with the EQ plug anyway. I could be wrong though…

March 20, 2006 at 13:58 #6304

Zynewave
Keymaster

The basic plugin functionality is done. I’m working on optimization and also the editor needs a few extra touches. Hopefully I can release it in a couple of days.

March 20, 2006 at 18:14 #6305

Joachim
Participant

Initial reaction… *jawdrop*
Whoa… This looks amazing! I’m sure it will sound like a milliion dollars too! 8)
I agree with both Conquistador and Max.

The only question I have is: Will the LP/BP/HP filters have selectable dB/oct slopes and resonance?

Have’nt had the time to test the 1.53 release yet. Will report as soon as I’ve tested the MIDI-mapping thing you fixed for me 🙂

Cheers mate!
/Joachim

Viewing 15 posts - 1 through 15 (of 58 total)

1 2 3 4 →

You must be logged in to reply to this topic.