Topic: Plugin rescanning

Viewing 9 posts - 1 through 9 (of 9 total)
  • #2010
    aMUSEd
    Participant

    When does Podium do this? I just reorganised my VST folder quite radically but it is not being reflected in the Devices list and neither are new plugins even though I have changed the VST folder path in prefs

    #15980
    LiquidProj3ct
    Participant

    You can consider the devices list as a “direct access list”. You can move them, delete, rename because they are just direct access to plugins. If Podium doesn’t find a plugin that you have changed its path do Devices–>Search missing plugins

    Hope this helps πŸ™‚

    #15981
    aMUSEd
    Participant

    @LiquidProj3ct wrote:

    You can consider the devices list as a “direct access list”. You can move them, delete, rename because they are just direct access to plugins. If Podium doesn’t find a plugin that you have changed its path do Devices–>Search missing plugins

    Hope this helps πŸ™‚

    Yeah I know that but I don’t want to fiddle about plugin by plugin – I want it just to rescan and update the list (and without having to start a whole new project) – it should have done it when I changed my directory path – in most hosts there would be a rescan now button or something

    #15982
    LiquidProj3ct
    Participant

    try to load the device setup from a new template with the new path?

    #15983
    Zynewave
    Keymaster

    If you have radically changed the folder layout on your harddrive and want those folders reflected as folders in the project device list, the easiest way is:

    Create a new project and continue to do a normal plugin scan.
    When asked if you want to save as a template, do so.
    Load your old project, and select the new template you created from the “project/project templates/load device setup” menu.

    #15987
    Conquistador
    Participant

    @Zynewave wrote:

    If you have radically changed the folder layout on your harddrive and want those folders reflected as folders in the project device list, the easiest way is:

    Create a new project and continue to do a normal plugin scan.
    When asked if you want to save as a template, do so.
    Load your old project, and select the new template you created from the “project/project templates/load device setup” menu.


    That is exactly what I have been doing since its addtion to PDM and the load process (here) is instant.
    Impressive.

    2.20 Usability e.t.c…

    However…I do think that some sort of option should be added to Podium to allow a user to have their VST folder scanned automatically and their device list automatically updated as well.

    How could that work?

    You could simply have Podium automatically load up the last saved device setup. Either from the last saved Project in Podium or last saved Project template.

    I would assume most people would have at least one project template but I think it is 99.9% likely they will at least have one recently saved Project by the time they need to update their VST folder.

    So Podium can automatically load that device set up after an autoscan of VSTs. The layout will follow the layout of their VST folder but also add any new additional mappings in a VST fodler added to the list.

    I noticed that Podium sometimes leaves empty folders if they already exist in a device set up list after loading a new one, so I would imagine those duplicate folders should be automatically deleted as well after an auto VST scan and an auto device set up load for a nice 100% tidy process. πŸ™‚

    HTH

    #15988
    aMUSEd
    Participant

    Thanks – I was hoping not to have to go through creating a new project again as it always crashes somewhere along the scan before I’ve even saved the project. A simple way to update what is already there would be more efficient. Anyway I will try it again.

    #15989
    aMUSEd
    Participant

    Oh well it crashed during scan again so I lost the new Project – this is why an update scan would be better – then I could just rescan and pick it up where it left off instead of starting from scratch each time with a new project

    #15993
    druid
    Participant

    I don’t know if it will help, but I found when I let it scan my entire VST folder (split into a few subgroups and then subsubgroups) it would crash, and so I, instead of scanning entire folder, got a new project, didn’t scan, and then manually told it to import VSTs from select folders. I found that I could import them all; I have no idea why it crashed when it does them all at once, but you might try this, if you have them grouped in folders. I assume you do, since you said you reorganised them.

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