Beta1 is available in the VIP lounge. Change-log so far:
• The track inspector rack can now show embedded generic editors for all plugins in the effect chain. This feature is enabled with the new “Editors” option button in the track inspector toolbar. When enabled, a show/hide button will appear next to each plugin selector in the rack.
• A scrollbar will appear in the inspector rack panel if the rack is too large to fit in the panel. The panel can be resized by dragging the bottom of the panel.
• Removed the redundant gain/pan/send controls as well as the embedded plugin editor from the track panel in the inspector.
• The track panel in the inspector now always show information for the source track even if an effect track is selected.
• Changed the appearance of the zPEQ editor response curve so that is centered around 0dB.
I think the rack is done now, but let me know if you have further suggestions. I already have tested that the embedded editors work in the mixer strips as well, but I need to make some adjustments to the zPlugin editors so that they will scale to the small space available in the strip. 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.
Please note that the minimize/restore state of the individual plugins in the rack are not yet saved in the project file.
A suggestion. When there’re too much parameters in plugins this will be extremately useful: Custom favorites parameter for each track.
1. Adding parameters from mda DX10 checking them
2. Adding a parameter from TAL Flanger checking it
3. Final result. Uncheck from favorite list to remove.
And a minor problem, the minimum with of inspector is too short and it “eats” a part of List button:
Thanks you Frits 🙂
I sort of agree with liquid on the favourites, but not on a per track, but per plugin basis.
This is especially usefull for complex synths:
I’d like to be able to configure the embedded editor of alchemy so that it only shows the 8 performance knobs and hides all the others.
Other than that: brilliant update!
edit: it managed to bluescreen my computer, while shutting down podium and pressing no to save the project. It might be a glitch in the asiodriver too. (after the bluescreen all my podium settings were lost, as were the editor profiles in the project)
It would also be nice to have the embedded editors start out minimized, or have an option to do that. It makes more usability sense to start out with an overview and reveal more detail on request than the other way around.
That was quick! 😮 Here are some things that come to mind:
– In my opinion, the editors should start off minimized. I’d rather select the ones I want shown than scrolling through a gigantic list and having to close all of those I don’t need.
– Speaking of scrolling… Since every parameter listbox in the rack of course has its own scrollbar, there’s little space left to put the cursor while scrolling the rack itself. Using the mouse-wheel directly over scrollbars is awfully slow – could this be changed or is it some Windows default? It would also be good for, e.g., the horizontal scrollbar in the mixer if you don’t want to use shift all the time.
– It seems the scrollbar position is remembered individually for every track. I think I’d like it better if it was auto-scrolling to the focus track in the chain, like the mixer does.
– Maybe the max. parameter listbox size should be a little less tall. Here, the default rack size is too small to accommodate one complete listbox. If it would cut off 5 or 6 parameters earlier, you wouldn’t have to resize the rack to see and use the whole box and its scrollbar. (This is on a screen with 1024 px vertical resolution.)
– Oh, and add another yes, please to showing user-chosen parameters only (and all parameters if none are chosen)! I thought you already hinted at this during the 2.23 preview. 🙂
@thcilnnahoj wrote:
– In my opinion, the editors should start off minimized. I’d rather select the ones I want shown than scrolling through a gigantic list and having to close all of those I don’t need.
Totally agree!
@thcilnnahoj wrote:
– Speaking of scrolling… Since every parameter listbox in the rack of course has its own scrollbar, there’s little space left to put the cursor while scrolling the rack itself. Using the mouse-wheel directly over scrollbars is awfully slow – could this be changed or is it some Windows default? It would also be good for, e.g., the horizontal scrollbar in the mixer if you don’t want to use shift all the time.
I saw this also. I’d say that parameter list shouldn’t respond to mouse wheel (mouse wheel only for rack scroll).
@thcilnnahoj wrote:
– Maybe the max. parameter listbox size should be a little less tall.
I agree here also.
@LiquidProj3ct wrote:
@thcilnnahoj wrote:
– In my opinion, the editors should start off minimized. I’d rather select the ones I want shown than scrolling through a gigantic list and having to close all of those I don’t need.
Totally agree!
Agreed here too.
@kyran wrote:
…it managed to bluescreen my computer, while shutting down podium and pressing no to save the project.
Same here, under the same circumstances, except it didn’t bluescreen, just crashed.
Would it be possible for the parameters in the editor to double up as the regular parameter objects so you could drag/drop them onto tracks and so on?
Mart.
@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. 😆
Hi all,
Does anyone like the idea of an “Automate VST Parameter” option direct from the editor(s)?
Might be tricky but seems useful to me rather than having to navigate to the parameter through a menu with a different layout.
@H-man wrote:
Hi all,
Does anyone like the idea of an “Automate VST Parameter” option direct from the editor(s)?
Might be tricky but seems useful to me rather than having to navigate to the parameter through a menu with a different layout.
Sounds like a great idea
@H-man wrote:
Hi all,
Does anyone like the idea of an “Automate VST Parameter” option direct from the editor(s)?
Might be tricky but seems useful to me rather than having to navigate to the parameter through a menu with a different layout.
Yes, sounds good!
@H-man wrote:
Hi all,
Does anyone like the idea of an “Automate VST Parameter” option direct from the editor(s)?
Might be tricky but seems useful to me rather than having to navigate to the parameter through a menu with a different layout.
That’s sort of what I was suggesting… 🙂
Mart.
@H-man wrote:
Hi all,
Does anyone like the idea of an “Automate VST Parameter” option direct from the editor(s)?
Might be tricky but seems useful to me rather than having to navigate to the parameter through a menu with a different layout.
I love the idea also. It could be useful for future midi controller linking even.
@LiquidProj3ct wrote:
….It could be useful for future midi controller linking even.
Yes, I too would like that this update lay the basis for something like an easy midi learn function to map parameters to hardware controllers.
@kingtubby wrote:
@H-man wrote:
Hi all,
Does anyone like the idea of an “Automate VST Parameter” option direct from the editor(s)?
Might be tricky but seems useful to me rather than having to navigate to the parameter through a menu with a different layout.
That’s sort of what I was suggesting… 🙂
Mart.
@ Kingtubby,
haha …sry mate 😳 , ritght you are. When I read your post I got to the bit about the crash bug and kinda just skipped to the next post.
I like the non-GUI editors, all plugs look/feel the same and all the graphical distractions are removed. Also, you can get access to parameters that do not have a GUI element at all.
Oh, and LiquidProj3ct (& Kyran’s) suggestion of Favourites for the parameters is an excellent one 🙂
@H-man wrote:
haha …sry mate 😳 , ritght you are. When I read your post I got to the bit about the crash bug and kinda just skipped to the next post.
I like the non-GUI editors, all plugs look/feel the same and all the graphical distractions are removed. Also, you can get access to parameters that do not have a GUI element at all.
Oh, and LiquidProj3ct (& Kyran’s) suggestion of Favourites for the parameters is an excellent one 🙂
no worries 🙂
a combination of user selectable parameters that also function as automation objects would be a really cool addition, nicely integrated into the inspector.
Mart.