Topic: Preview 2.24: Embedded plugin editors in the rack

@thcilnnahoj wrote:

@Zynewave wrote:

For zPEQ, only the curve display will be shown with draggable points. You’ll need to use the rack or open the plugin editor window to toggle EQ bands on/off and to do fine adjustments.

Excuse me if I this is a misunderstanding, but it sounds like you’d be taking away the second-most important control from the embedded EQ editor. I think at least the band-enable buttons should remain in the mini-editor. Or add a right-click menu with band-toggling options… Maybe it’s too much to ask right now. 😛
Edit: Mixer strips! Note to self: learn to read! 😳

There’s a handful of plug-ins in my collection that seem to report strange values (mostly Kjaerhus classic series’ parameters adding a % sign). I guess it’s the plug-in maker’s fault, but I thought I’d mention it anyway.

The second one is kinda cute. 😆

I checked the output of the Classic Delay, and it is indeed the plugin that returns “%” for all parameters. The VST spec uses one function for returning parameter “display” and another for returning parameter “label”. The Classic Delay returns “%” for all parameters. It should really return an empty string, because it returns the label as part of the string returned by the “display” function.

@thcilnnahoj wrote:

@H-man wrote:

@thcilnnahoj wrote:

Any kind of resizing (mixer, inspector, etc.) is extremely sluggish here when even just one embedded parameter is shown in the mixer.

I hate to stir things up but mine has become much better :-s and I have not updated drivers etc.

Correction to what I said: There doesn’t even have to be a single parameter visible – it’s enough that the “show editors” function is enabled. My guess is that it has to do with plug-ins that have long parameter lists, as it only seems to happen with those on my system. Here’s a test that worked for me: in an arrangement with just one or two tracks, load the free Voyager as the only plug-in, grab the mixer and drag it up and down as far as it goes. Try this with and without enabling embedded editors. CPU load is pretty much the same on my system for both, but the dragging is jerky with editors enabled.
As with all other things in Podium, the processing load on my graphics card (Radeon 3850) is rather low, so I doubt it has to do with that. :-k

I’m looking at this now. I added 10000 fake VST parameters to the Nucleum device definition, and it has revealed a few places that needs to be speed optimized. Please test again when the next beta is up.

@thcilnnahoj wrote:

Here’s a little more difficult suggestion: When you double-click somewhere to activate a band, it jumps right to the cursor position. That makes it impossible to toggle bands on/off for a quick comparison in the mini-editor. How about changing this so a band stays at its last position upon (re-)activating it, and only follows the cursor if you still hold the mouse button to drag it after the double-click.

I don’t think that would work reliably. If you double-click a band to remove it, then double-clicking again will not reenable the same band you just disabled, if there are unused bands before that band. That could be confusing. For band on/off comparisons, it’s better to open the editor where you have the band enable buttons.

I also like the fact that you can quickly click along to set an approximate EQ curve with multiple bands.

Beta 6 is up. Minor changes and some bug fixes. I think I still need a couple of days working through all the bug reports.