Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@Malcolm Jacobson wrote:
I agree with others comments that the “Add new effect” button should be above the existing FX, and that the new effect should be added at the top, so the behaviour in the Group Panel matches the order of the Mixer.
By popular request, the “add new effect” (or “+”) button is now placed at the end of the chain.
I don’t understand the need for the Tick button. I like the information about the effect to be shown in the Inspector as soon as I click on the effect name. I don’t like having to click the “Tick” button as well. Can we add an option to hide this button and have the information automatically displayed?
I can’t see how I can avoid the tick/select button. There need to be an indication in the group panel of which effect track is selected, and thus which track is being edited with the object lists at the bottom of the inspector. I can’t see how I can combine this into the selector buttons. The selectors already use colors to indicate plugin open/close state. Clicking selectors are used to open menus or open/close editors, and you don’t always want the track to be automatically selected when you just want to open a plugin editor.
ZynewaveKeymaster@LiquidProj3ct wrote:
@Zynewave wrote:
In beta6 the effect record buttons are finally gone. The track lane record button will also record enable all plugin effect tracks.
I love those minor changes that simplify Podium workflow! I was trying it and I saw this:
Since green inputs are the same that red input, the green inputs hasn’t too much sense, I see them as a waste of space and an unnecesary interface overload. Unless you have another plans for them, I would hide them from children tracks.
Thanks, that’s a bug. The fader, source and input selectors should not be shown at all on parameter tracks. Only the parameter selector should be shown. I’ll fix it for the next beta.
ZynewaveKeymaster2. I can’t help but to think those shadows look a little exaggerated on brightly colored backgrounds, like the default blue for selections on Vista. I don’t know about your UI rendering engine, of course, but is there any way you could try something similar to rendering shadows with a different blend mode? You know, Like in image editors – multiply, screen, overlay… A “simple matter of programming”, surely. 😉
I agree that the shadows are a bit too agressive. I’ve toned down the button shadows in the new beta6.
In beta6 the effect record buttons are finally gone. The track lane record button will also record enable all plugin effect tracks.
ZynewaveKeymasterBeta 5 is up.
The major addition since beta 4, is that the track headers now use the same style as the new group panel. Resizing the track header height will determine which elements are shown. There are still some things to do, like updating the options in the tracks region dialog. I would appreciate your opinion on this new track header layout.
ZynewaveKeymasterThe MIDI channel information is embedded in the MIDI messages that a VSTi outputs, so technically it shouldn’t be difficult to filter the MIDI notes to different slave synths, according to MIDI channel. The main problem is probably to provide a way in the UI to select the MIDI channel. When I get around to implementing this in Podium, I’ll probably use the MIDI channel settings in the device mapping properties to support MIDI channel filtering.
ZynewaveKeymasterI don’t know when I’ll have this implemented. My development focus recently shifted towards improving and simplifying the existing featureset, which will occupy me for the next 2-3 months.
ZynewaveKeymasterEither use the device listbox in the inspector, or arrange the waves plugins into more managable subfolders in the device list on the project start page.
ZynewaveKeymaster@sam c wrote:
is there an udated pdf manual or just the wiki page?
The pdf that came with the 2.22 installer is up to date with the latest additions to the wiki guide.
ZynewaveKeymasterBeta4:
Another button bites the dust. The select and menu buttons are now combined into one. Clicking the button will select the track. Clicking the button when the track is selected will open the menu.
The “add effect” selector is now a simple “+” button. It can be hidden with the “show new effect buttons” option in the inspector options menu.
Clicking a selector with a send assigned will toggle the display of send controls.
Still to do:
Right-click on buttons.
Drag-reordering.
And I’m still thinking of ways to get rid of the record buttons.ZynewaveKeymaster@Markus wrote:
okay, can someone make me sidechain template? Please? Thanks.
When I’m done with 2.23, I’ll make a YouTube video of how to use side-chaining. The only freeware (and stable) sidechain capable compressor I know of is Compressive by: http://www.martineastwood.com
Are there other freeware alternatives?
ZynewaveKeymaster@Markus wrote:
@Zynewave wrote:
@Markus wrote:
How about coding just simple compressor / duck / gate fx? It doesnt have to be good. Just that good so we can use it for sidechain.
How long it will take to code something like this? Simple duck fx? Thanks for your time.
Based on my experience with zPEQ, zReverb and zPitch, I estimate that it will take me at least a month to make a zComp. I tend to be thorough when I start on a new plugin. At present time my time is better spent on Podium, but I’m looking forward to when I get time to expand on the zPlugins suite.
No, i mean SIMPLE. Very simple. We can use third part compressors. But i’m asking very very simple ducking fx. Something what you can code like in couple days or one week. Or then you may add support to some free compressors. Or something.. Like i said, it doesnt have to be good.
I really want to change Podium to my main DAW:n. But as an electornic music producer, lack of this kinda feature is deal breaker for me (and many others)..
Anyway, thanks.
The ducking effect is achieved using a compressor and the compressor needs to support sidechain input. If you are talking about the sidechain track routing within Podium, then that is already supported. I’m sorry that it doesn’t work the way you prefer.
ZynewaveKeymaster@thcilnnahoj wrote:
@Zynewave wrote:
Beta3:
The selector buttons now turn into editor buttons once a plugin is assigned. That gets rid of the separate editor buttons. Good riddance, I say. When you alt+click the selector button, the effect is removed, and the effect selector menu reappears.
Is there anything assigned to right-clicking it, other than selecting the track? You could use it to bring up the replace/unassign device menu, otherwise people who don’t like keyboard shortcuts may have a hard time with it. 😛
Agreed. I’ll make right-click on the selector open the device menu, no matter if a device is already assigned or not.
ZynewaveKeymaster@Markus wrote:
How about coding just simple compressor / duck / gate fx? It doesnt have to be good. Just that good so we can use it for sidechain.
How long it will take to code something like this? Simple duck fx? Thanks for your time.
Based on my experience with zPEQ, zReverb and zPitch, I estimate that it will take me at least a month to make a zComp. I tend to be thorough when I start on a new plugin. At present time my time is better spent on Podium, but I’m looking forward to when I get time to expand on the zPlugins suite.
ZynewaveKeymaster@kyran wrote:
Here comes another suggestion to eliminate a button:
right clicking the track selection button could serve as a track mute. Right clicking a muted track could unmute it.
Left clicking still selects the track.By track mute, do you mean effect bypass?
I can’t see how I can avoid a separate bypass button, if it should be possible to toggle bypass without key modifiers.
I’d still like the empty track to be on top of the chain, where I most of the time add new tracks.
Anyone else have a preference on where the “add effect” selector should be placed?
ZynewaveKeymaster@Zynewave wrote:
You know, I’m very tempted to remove the per-effect record buttons, and just rely on the source track record button
Oops, scratch that suggestion. I now remember why I made plugin automation recording optional: Some plugins will send out parameter changes in response to program changes, MIDI controller input, etc.
So you can end up with a lot of unwanted parameter tracks when you just want to record MIDI on a track.