ZynewaveThis is dragging out a bit. I’ve been busy with a couple of other things in my life, so I’ll need another week before the next beta is ready. Sorry for the delay.
ZynewaveHi Mick,
Yes Podium is still in development. The date you quoted is the date where the topic was created (around Podium 1.00 I guess). I edit this post with new links for each release, but this does not modify the date. If you want to follow the releases, you can take a look at the topics in the Releases forum. The dates there reflect when each version was released.
btw. I took the liberty of removing some of the text you quoted, as the download instructions are for Podium licensees only.
Zynewave@CymaticCycle wrote:
Another thing that I noticed is that when I adjust the parameters in the dialog and then close it, with or without saving the changes, every next time I open it, the settings are as I left them. This also happens when I create a new automation track for a completely different instrument, and then click the Adjust Points, the last used settings are remembered. The settings are remembered even after restarting Podium.
Maybe this is not a “bug”, but if they were neutral by default would be better.
That is intended. All the adjust dialogs remembers the last settings (except preview on/off). I thought it convenient that if you have dialed in some favorite settings, you don’t have to recreate them every time you open the dialog. In a future update I may add some simple form of preset system to the Adjust dialogs.
Zynewave@MikaFrench31 wrote:
I can’t select the option “clipboard” in adjust points and adjust velocities but maybe I have not selected an option ?
You need to copy at least one note or point event to the clipboard, before opening the dialog. Tip: If you select a range of notes/points and copy them (Ctrl+C) before opening the Adjust dialog, the clipboard option is a quick way to gradually align the events to the value of the first event in the selection.
ZynewaveMany thanks for the feedback. Beta 2 is up. The bug with the Adjust Points dialog should be fixed, plus:
• Note editor: Added “Invert Notes”, “Reverse Notes”, “Invert Velocities”, “Reverse Velocities” to the edit menu.
• Reorganized the edit menu. Inactive menu commands that were previously hidden are now shown as grayed out, to make the appearance of the edit menu more consistent.
ZynewaveI have Kontakt 4, and have experienced various problems. I was planning to revise my plugin loading system, as I mentioned in the other topic you linked to, but I ended up doing the velocity editing improvement instead. I’ll examine the Kontakt problem after the 3.2.0 release.
ZynewaveI looked over the velocity region for ways to improve the editing. I already had a few velocity region improvements on my todo list, so it seems the next 3.1.3 release will include some velocity editing improvements.
One of my todo features was a way to draw over velocity bars to adjust their relative value rather than drawing absolute velocity values. This is now done by holding the Alt key down.
Holding the Shift key down will start a marquee selection so that you can select notes based on their velocities.
Holding Ctrl down and dragging up/down will offset all selected velocities. Ctrl was previously used to set default velocity values. This can now be done with a new “Adjust Velocities” dialog. This dialog will also include a randomize option and various other stuff.
ZynewaveThanks for the file. The reason the input selectors are missing is because Podium interprets your “Mastering” group track as being part of the bus return section. Input selectors are hidden in the bus return section. You can get the input selectors back by moving your “Rev” track (with “Return 1” assigned) outside of the Mastering group.
I’ve modified the Podium code so that group tracks are no longer included in the bus return section. Only single tracks with bus return mappings will now show up in the optional docked bus return section in the mixer. Fix will be available in 3.1.3.
Zynewave@MikaFrench31 wrote:
“Is the Shift key used to access “-” on an azerty keyboard? “
If shift key : “6”. No shift key : “-“
I installed the French azerty keyboard driver on my PC, and can confirm that “-” cannot be used as shortcut on azerty key layouts. Podium receives the raw key codes for the number keys, and not the character as interpreted by the keyboard driver. The problem is that if Podium should respond to the translated character (i.e. “-” instead of “6”), then it cannot use the 1-9 shortcut keys for switching editors and the Shift+1-9 keys for selecting snapshots.
ZynewaveI have Kontakt 4, and I have experienced problems when loading the plugin/presets. Depending on the amount of sample data, K4 will sometimes crash if the plugin editor is opened shortly after the plugin is loaded and before the preset is done loading. I’m about to begin experimenting with a different method of loading plugins, which hopefully also will cure the problem of the inresponsive Podium UI if the plugin loading takes seconds to complete.
ZynewaveIf you email the project file to me (no need to include the wav files), I’ll have a look.
Zynewave@MikaFrench31 wrote:
@kingtubby wrote:
@MikaFrench31 wrote:
The “+” and “-” of the numeric keyboards do not allow it.
Only the “+” of the touch “+=}” allow it to increase.
But no touch to decrease.What about the “-” key next to the “+=” key. It works for me.]
TheThank you for your answers
On my keyboard, the “-” isn’t next to the “+=” (I have an “azerty” keyboard)
?????????
Is the Shift key used to access “-” on an azerty keyboard?
Another problem in the editor: on an chord, I do not manage to change the velocity of a single note, even if ‘ there is only selected note.
Make sure the “edit only selected events” option button in the velocity region is on.
ZynewaveYou can only assign MIDI cc to plugin parameters if the plugin supports MIDI learn natively. Podium does not yet support mapping MIDI cc to VST parameters.
ZynewaveI’m sorry, but I cannot provoke a crash with Oatmeal. I managed to get a UI freeze after hitting the ‘Random’ button 50 times, but that was with 3.1.1. Are you sure you were testing with 3.1.2?
Did you get the crash when using different presets as starting point? It’s possible that a certain combination of parameters can cause instability in a plugin.
Anyone else using Oatmeal with 3.1.2?