Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@thcilnnahoj wrote:
– You may want to adjust the default size of the editor window (if not related to screen size) or horizontal size of the piano keys, as the new linked velocity buttons don’t fit anymore.
Done.
– A minor inconsistency concerning the MIDI/note editor. The EE (embedded editor) will in some rare cases copy the velocity region height from the SWE (separate window editor), though they’re fine with having different region heights most of the time. Here’s one way to reproduce this:
Switch to the ‘Editor’ profile > select a MIDI sequence > in the EE, set height of velocity region with the drag-handle > double-click a MIDI sequence to bring up the SWE and leave it there (it should have a different velocity region height) > click on a sound or curve sequence, so the EE switches to a different editor > select a MIDI sequence again > the EE should have assumed the velocity region height from the SWE.
…That’s a mouthful! :-#That’s because they are using the same editor profile. Besides the settings you find in the region dialogs, the profile also logs the “last used” size of resizable panels. So if you have two editors open showing the same profile, the last resize action will determine the size used the next time the editor is opened.
ZynewaveKeymasterWow. This turned out to be the same bug that I found in IK Amplitube over two years ago:
http://www.zynewave.com/forum/viewtopic.php?t=1406
It’s likely that the new plugins use some of the code that is also found in Amplitube. It appears to me that this would be a very simple bug to fix.
If you search for Amplitube on this forum you’ll see that I and other users have failed to get a reply from IK about this.
Since it seems unlikely that IK will fix this soon, I’ve modified Podiums code so that the standard “all notes off” and “all sound off” MIDI messages are only sent to VST instruments and not effects. Fingers crossed that this will not cause other plugins to suffer from hanging notes. Hopefully the IK synths will not crash if they receive “all notes off” messages π
Now all the tracks are active in that arrangement and I canΒ΄t even get it to open anymore.
You can disable the “activate power when opening arrangement editor” in the Preferences. That will allow you to open and edit the arrangement without loading the crashing plugin.
September 16, 2009 at 18:06 in reply to: Key focus problem experienced with certain plug-ins (solved) #16390
ZynewaveKeymaster@thcilnnahoj wrote:
@Zynewave wrote:
If this works in other hosts, then it could be because these hosts parse keypress messages before Windows distributes the messages to the key focus window.
Is this not recommended, then, or something you’d rather not do?
I believe the way I’m doing it is the standard way to respond to key messages in Windows. I prefer to keep to the norm, to ensure compatibility with future Windows versions.
If so, would you suggest I ask FF again about this, and also point them to your post? Theirs are the only plug-ins I know of that exhibit this problem, but judging from some posts I’ve found here, there seem to be a few others, too.
You’re welcome to present my response to the fabfilter developers.
If you are referring to the posts about the space key (start/stop) being inactive when a plugin editor has focus, then that may not be the same problem. That could be the plugin editor responding to Podium that it used a key press, in which case Podium will not use it for its own shortcuts.
ZynewaveKeymaster@psychesonic wrote:
Yes. I find that if I have, say, a couple of hours of material – music, or dialogue for example – arranged sequentially on the track page, that if I only want to render a few minutes starting at the 1 hour point, the render process seems to start from the very beginning of the timeline. I once had to edit 3 hours of a forum into individual speeches – you can imagine how long this process took. Is it possible to specify where the render begins and ends… or have I missed something?
Are you using the “render within punch range” command? The render should start where you set your punch-in position.
ZynewaveKeymaster@swindus wrote:
Little bug: When using the command ‘crop unique sequence’ the view of an opened sound event editor is not updated correctly. The position of the sound event is wrong (navigator zoom?). After unselecting and selecting the sequence again the display is right.
The editor is not really linked to the sound event, but is only initialized with the sound object and zoom range once the sound event is clicked. Eventually I’ll change this so that the editor keeps a link to the sound event, and thus will react to changes to the event.
ZynewaveKeymaster@psychesonic wrote:
I really like the wav browser on the right hand side – right eyed or whatever. It seems a little cluttered having the Inspectror and browser bunched together. Is it possible to add align right/left?
I’d like to keep the embedded inspector and browser bunched together. If you prefer a different setup, you can open a browser window and place it to the right of the project window. The F9-F12 key shortcuts can be used to switch between different window layouts.
September 16, 2009 at 03:00 in reply to: Key focus problem experienced with certain plug-ins (solved) #16379
ZynewaveKeymasterI tried the Volcano2 demo. I also read the comment from fabfilter in the topic you linked to.
Clicking on the plugin Window frame to give the plugin key focus works fine. Podium receives key press messages from Windows (WM_KEYDOWN/WM_KEYUP) and distributes these to the plugin with the editKeyUp() and editKeyDown() VST messages. The plugin can then respond to the key press and return to the host whether it “consumed” the key press. If not consumed, then Podium checks the key for Podium key shortcuts.
It appears that the when you activate the Volcano plugin editor by clicking inside the editor window, it consumes the WM_KEYxxx messages, which then is never received by Podium. I read their comment about the mousewheel focus, but I can’t see why this should prevent them from letting the WM_KEYxxx messages through to the Podium parent window.
If this works in other hosts, then it could be because these hosts parse keypress messages before Windows distributes the messages to the key focus window.
ZynewaveKeymasterThe next 2.22 release includes new bounce options. Check the 2.22 preview topic for more info.
September 16, 2009 at 02:18 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymasterBeta 2:
β’ Added “export to sound file” to the arrangement editor and sound editor file menus. The commands show a dialog with bit resolution and normalize settings. The arrangement export uses the bounced audio of the master track. An “export bounced audio to sound file” command is also available in the bounce submenu of each individual track.
β’ Removed the MIDI and bounce settings from the effect track properties dialog. The bounce settings are now exclusively managed with the track bounce submenu. The MIDI settings are still available in the source track properties dialog.
β’ Reorganized the layout of the fader, meter and bounce track submenus.
β’ Added “move bounced audio to new track” command to the bounce menu. Removed the now redundant “hide bounce track lane” option.
The “export to sound file” dialog will in the future be extended with settings for sample rate, dither and encoding to mp3, ogg, flac etc.
ZynewaveKeymaster@kingtubby wrote:
The other thing is, I wonder if it would be possible to have an option to set limits on the range of individual controls. e.g. right click on a slider and choose ‘set control range’ or something. Then you could set an upper and lower limit like 0db and -30db or whatever. Likewise with pan controls left 50% and Right 50% for example.
It could be represented graphically like so:

From my point of view it would be useful as I like to mix stuff on the fly and I could throw faders etc, without having worry about going too loud or soft and so on.
Adding this feature doesn’t quite gel with my current quest for UI simplification :). Perhaps we can discuss this again after I’ve completed my revision of the track header UI.
Is there a reason why you can’t settle with resizing the track headers horizontally to widen the sliders?
ZynewaveKeymaster@Conquistador wrote:
Drums π
I would say (yes I have said it before) that the Midi drum presentation and set up is now just so far behind other parts of Podium (as of 2.22 especially) it really does stand out.How about a one click set up?
I would ask if possible to consider adding a “Drum kit” button to the Presets panel for loaded VSTi’s. Currently the “Use Preset as drum kit” is hidden well out of view. Clicking on that new button should also automatically delete all notes that do not have drum note names as well. Those changes would at least get drum presentation and set up to a far more pleasurable level. More is needed but these two changes IMO are really basic, critical needs for that area of Podium at this point.What about this…? π

Your “critical” priorities are changing almost as frequently as mine :). That updating the drum editor is critical was not on your mind when we had the most recent VIP discussion of what I should spend my time on. The drum editor is scheduled for an update, but I would like to keep that out of the current series of overall UI revisions.
Zoom Presets
Studio One has a rather nice little feature which i dismissed the first time I saw it but find it quite slick in terms of its simplification of UI navigation. Its effectively a set of Zoom presets for the Arranger. Any chance of that kind of feature making it into 2.22?
Not in 2.22. I think it was in the preview topic for the navigator that I mentioned I plan to add a zoom snapshot feature. The blank space to the left of the navigator will hold the controls for the snapshots.
ZynewaveKeymasterPlease postpone your bounce worries until the next 2.22 beta. The last few days I’ve been working on a redesign of the bounce options. Check back when the next beta is available.
ZynewaveKeymaster@Malcolm Jacobson wrote:
Added a new video showing how to assign and record a VSTi, and how to assign a VST effect:
Thanks. Favorited. I like that you are keeping the videos short.
I was surprised that I didn’t get an email from Youtube, even though I’ve subscribed to your channel. Apparently I only see updates to my subscriptions if I log in, and go to the “subscriptions” page.
ZynewaveKeymaster
