Zynewave's Forum Page

Release 2.10 will have this feature:

Context help for UI elements under the mouse cursor can now be shown in a docked help panel below the inspector panel or the list panel. The help panel can be toggled with the “Docked help” option in the help menu.

That will be it for this release. Later on this docked help can be extended to have the wiki links, and possibly interactive tutorials etc.

The pdf that is installed with Podium unfortunately does not contain the latest updates to the wiki guide. I’ll remember to create an updated pdf guide for the next release.

@22tape wrote:

(this is meloday, by the way. i’ve changed my name since i originally registered on the forums here, which was a while ago.)

🙂

If you want to keep your old posts associated with your user profile, you can alternatively rename your old “meloday” account to “22tape” in your user profile. Let me know if you prefer this, and I can delete your new 22tape account.

FR is now added to the future plan.

@H-man wrote:

I’m guessing the ‘recording notes at the same time as automation’ is still an issue tho?

Not if the length of the arrangement is longer than your recording range. The curve events will still be set to the arrangement length, even if the note sequence is being gradually extended as you record. A tip for setting the length of a new arrangement with empty tracks: Add a marker event at the desired length.

@meloday wrote:

how might i be able to change these options in podium?

Podium will always run the plugins, as long as the arrangement power button is on.

@aMUSEd wrote:

OK we are post 2.09 so is this on the roadmap for a fix yet? I’m sorry to have to keep bringing this up but please understand that the current implementation basically makes recording synths with automation unworkable for me at present and I see this as a very serious issue – to show how serious I took this screenshot which I hope demonstrates the extent of the problem

here I think it is plain to see in this relatively simple sequence example every time I adjust the cutoff and then switch to the res knob, the cutoff drops to zero and every time I adjust the res and then switch back to cutoff it does the same – all the time having the cutoff at zero makes the sound silent so I would hastily adjust it back only to then have the res drop down and have to be corrected. It’s like I was fighting the host all the way and this is just a simple example.

This is not a bug with this particular VSTi (Korg Legacy Cell) – I have encountered similar behaviour with every synth and effect I have tried to automate and I chose LC as the example as it is widely known to be a stable and well established “classic VSTi. No host should do this – it takes away control from the musician – not one of those drops to zero in either param was intentional and even if I could edit them out afterwards the whole flow of the track and of my playing was ruined.

Did you record the MIDI notes and the knob automation at the same time?

I assume that the curve sequences were not set to the full length of the arrangement from the start, but rather gradually extended as recording progressed?

@Zynewave wrote:

@LiquidProj3ct wrote:

Please, how can I avoid this? I thought that default value was the value that the knob had in the moment of the creation of the automation track. At least with other VST/Parameters I hadn’t got this problem and the default value was always the value which I create the automation track.

The problem here is that this method of creating a parameter track does not also create a curve sequence on the track. So the current plugin value is not retrieved, as it is done when you create the parameter track by recording knob changes in the plugin editor. You can get around your problem by manually drawing in a curve sequence on the track before starting playback. I’ll change this so that a curve sequence is automatically created when you manually add the automation tracks.

I’ve now implemented this change for the upcoming 2.10 release:

Creating a new plugin parameter track from the inspector parameter panel or the track context menu, will also create a curve sequence on the track. The current plugin parameter value is set as the starting point in the curve sequence.