Topic: Renaming VST Parameters

Viewing 7 posts - 1 through 7 (of 7 total)
  • #2718
    bladerunner
    Participant

    Today I decided to rename rhinocm’s automation parameters to make them more meaningful. I then shut down podium, then reopened podium some time later to find they had all defaulted back to their original names 🙁 Is there a way to save them so they are recalled each time the plugin is subsequently used?

    #21598
    The Telenator
    Participant

    bladerunner, thanks for posting this topic. I can only add a second voice here by saying I’ve had the exact same thing happen both times I’ve tested this renaming option, but I’ve been so busy and had much larger fish to fry — no time to figure out what the problem is. Eventually, I will need to do some serious renaming on several plugins’ parameters and presets. IIRC, I may have observed the same issue with renaming plugin presets but will have to recheck that.

    #21599
    thcilnnahoj
    Participant

    Did this happen in one and the same project? I just tried, and it remembers any changed names fine for me as long as it’s the same project.

    Regarding changes to plug-in configurations, it’s probably best to make them in the plug-in database (PluginDatabase.pod) if you want them to appear in all (new) projects.

    #21602
    The Telenator
    Participant

    thcilnnahoj, not one and the same I think in my case — I just tried it a couple of times for the heck of it.

    The other thing you said: Yes, I would want all in the database and that’s the way I’ll need to go. When I make changes I’m almost without exception thinking globally, for the sake of consistency and time-saving.

    #21609
    bladerunner
    Participant

    Thanks for the replies 🙂 i didn’t do any saving – I, perhaps naively, assumed that the parameter names would be remembered as a global thing perhaps stored in a podium configuration file somewhere. I don’t mind if you have to save a project once the names have been changed as i tend to work from template projects anyway. It’s all good – nice to have a host that allows this. It would make it complete if you could delete/hide parameters as so many plugins have reams of parameters simply marked as ‘unused’ or something.

    #21611
    thcilnnahoj
    Participant

    @bladerunner wrote:

    It would make it complete if you could delete/hide parameters as so many plugins have reams of parameters simply marked as ‘unused’ or something.

    Oh, but you can! 😉 It’s a little tricky, though.

    There’s a little button in the top right corner of the project page (called “Project page mode”). When you click it, it takes you to a different view of your project and all sequences/devices used in it.
    Now you have to locate the plug-in you’d like to edit – first, select “Devices”, then navigate to it (remember the plug-in folder structure here is freely configurable and doesn’t necessarily have to mirror the structure of your VST folder).
    For each plug-in, you’ll see a folder that says something like “Objects: 23”. If you enter this folder, then enter itssub-folder “VST Parameters”, you finally get the big list, where you can rename, reorder, or delete parameters to your liking.

    Just remember that changes to parameters you delete of course won’t be recorded anymore. Unfortunately I don’t know of any way to only hide parameters, so make sure that you absolutely don’t need them before deleting.

    You’ll also probably want to create a backup of your template before editing this deeply!

    #21616
    bladerunner
    Participant

    Thanks for the info thcilnnahoj – it’s pretty awesome there is this level of control over plugins (especially awesome for obssesive organisers like me…!).

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.
© 2021 Zynewave