Agreed. I’ve had the same thoughts for a while.
The default dial position of the pitch control in zPitch is wrong when enabled in the mixer. When ctrl-clicking on it to set it to the default position (0 cents) it goes to -1200 cents. In fact it’s the same with all the controls in zReverb too. It seems that in the mixer, all the enabled controls default to the extreme left when using ctrl+click.
Mart.
@LiquidProj3ct wrote:
That curve is the phase 🙂 zPEQ isn’t phase linear and shows you the offset.
Thanks, I figured it probably was a feature. The thing is though that it doesn’t behave consistently. As in the picture, the red coloured fill is not always in the same place. Sometimes in the inspector, it displays the same as it does in the mixer, sometimes not.
Mart.
@thcilnnahoj wrote:
The fader wouldn’t have to move over alone, though.
That’s exactly how I envisaged it when it was first suggested. I like it 🙂
@Malcolm Jacobson wrote:
I would suggest “Add Parameters”
How about “Add Plugin Parameters” for absolute clarity?
Edit: Further thoughts. Using “add parameters” encourages the user to click on the text in the expectation that the option to add parameters will be available there, rather than where it is currently. Would it be possible to move the right-click add parameters menu to the “…parameters” text?
Mart.
Currently the available embedded parameters are only read from the top level of the device definition. I have a device definition for NI pro53 that has the parameters organised into sub-folders and only the folder names are displayed. The picture should illustrate what I’m describing.
Mart.
@LiquidProj3ct wrote:
Another thing that you could add would be an assignable XY pad, where you can put your two more frecuently parameters per track. It’s something incredibly creative. If you don’t believe it, try to do some sweeps and recordings with zPEQ, and try to do the same with knobs below it. Compare. Now imagine you can do the same with two custom parameters.
nice idea, +1 from me
s+m is *ahem* fine with me 😉
Mart.
You’re on a roll Frits 8) it’s looking really good so far. No doubt a few tweaks are still needed but I’m liking it very much.
Mart.
@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.
@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.
@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.
You have to select the sysex parameter in the inspector and either hit alt+enter or right-click/properties.
The event view is just a list of, err…events 🙂 though I’ve always thought it should possible to edit the events from within the list.
Mart.
@Zynewave wrote:
I don’t see any bypass buttons in the Reaper mixer strips either.
It’s shift+left click by default, though key shortcuts can be re-defined.
I think having the “show bypass buttons” option satisfies most users. I wouldn’t call it a “step backward” just by having them hidden in the default setup 😉
The reason I would like to have them hidden, is to provide more space for the effect name. A lot of plugins have long names which will be truncated in the narrow buttons on the mixer strips.
Agreed.
Mart.
Looking good 🙂
I like the subtle colour variations – It’d be nice if when you select a track colour that any child tracks are automatically assigned a different but similar colour.
Mart.
@LiquidProj3ct wrote:
@LiquidProj3ct wrote:
Podium is portable. I tried it. Although it writes something in the windows registry (nothing critical)
It isn’t fully portable, I was wrong. I think it writes something in registry as audio in/outputs, colors, profiles…
Maybe those things could be written in an “ini” file in the same folder that Podium.exe, so it would be portable. I’ve said this pretty happily, but maybe it’s difficult to code ><
I can’t see anything in the registry, and the .ini files are stored in:
C:Users…AppDataRoamingZynewavePodium
Mart.