Topic: Alternative VST Folders?

Viewing 8 posts - 1 through 8 (of 8 total)
  • April 18, 2007 at 17:11 #1261
    Conquistador
    Participant

    Hi Frits,

    I have been thinking about a bit more flexibilty in Podium as far as folders are concerned.

    For instance Acid Pro 6 allows for more than one location for VST plugs, it actually provides separate alternative options for VST fx and VSTi plugin locations see below…

    The VST tab next to the VSTi tab also has 3 locations of its own that a user can set up. Frankly only one extra location is all I am suggesting here to add to the single location we of course already have. 😉

    A user defined location for sound files would be very useful as well IMO.

    The List view does allow for browsing sounds as well (which is still very useful) but I would still be interested in an option to set a particular sound location and not have to browse to the same location each time I click on the Import file option in the Arrangements and sound column.

    To summarise…

    1. One additional user defined location for VST searches as in ACID Pro. So two VST locations would be offered.

    2. A possible user defined global location for Sounds (for audio and midi files for instance) that would be linked to the Import file option in the Arrangement and Sounds Menu. So click on that and it always goes to the user specified Sounds location.

    Where would these options fit in?

    Maybe here… 😉

    There is space under the Default VST plugin Folder menu for at least two more search locations to be set up.

    Also there is space next to the Various tab for a dedicated Sounds tab where one could set locations for…

    1.Midi files

    2.Audio files

    If you are wondering what will then be visible on the VST plugin button on the project start page when creating new projects, it could be modified in this way…instead of the current Select VST plugin folder text it could read Select VST plugin folders so only the slightest of changes would be needed there.

    Two locations would be then be visible next to the VST button not one.

    Clicking on that button would then show you a box with the VST fx and VSTi location fields ready to be set by a user in the same way that clicking on the first button when creating a new project (the Project Properties button) provides a user with options for three different types of background images in Podium.

    Thoughts?

    April 19, 2007 at 01:34 #9774
    Zynewave
    Keymaster

    When you use the “Import file” command, Podium will log the last folder you browse to, and use that the next time you use the import command. The path is stored in the setup file.

    As for the two VST paths; I may add this later on. However I do think it’s less important for Podium than for other hosts, because of the way that you can import plugins from user specified folders. Setting up two paths for VST plugins also poses a problem with the “relative path” option for the plugin filename in the mapping properties. Podium would not know which of the two VST folders it should use to search for the plugins.

    April 19, 2007 at 12:54 #9777
    Conquistador
    Participant

    @Zynewave wrote:

    When you use the “Import file” command, Podium will log the last folder you browse to, and use that the next time you use the import command. The path is stored in the setup file.

    Correct yes it does 🙂 FWIW the suggestion I put forward for sound files is not essential of course, but I still think having a new tab for Sounds and allowing for one Audio files path and another for Midi files to be set by a user would not clutter or bloat Podiums feature set but it would I think just offer a bit more flexibility.

    Of course for now the Import File option can be used for both Midi and Audio files.

    As for the two VST paths; I may add this later on. However I do think it’s less important for Podium than for other hosts, because of the way that you can import plugins from user specified folders.

    Maybe less important, then again maybe not…something that is less important to one user can be important to another user 😉

    This why I think it is significant… in ACID it allows for one to work quicker or manage plugins easier than in Podium which is why I made the suggestion for two paths. Getting the job done faster saves time and money. But why is it easier..?

    a) In ACID Pro I can set up various VST paths and set it and forget it. In Podium this can be set but only for one path.

    b) When ACID pro starts up any new plugins that have been added to those folders since the last time I used ACID will be automatically scanned and updated for use when ACID starts up (it takes seconds).

    In Podium I would have to manually add new plugins each time.

    The whole VST path idea is hardly a Major deal as such, but just a suggestion that I think might make things even easier and quicker in Podium. It is in no way a ‘problem’ as such in Podium right now, far from it, but just an area that I thought might benefit from a slight degree of further refinement.

    I think Podium has matured to a point where Major requests are not really that many as it has matured very nicely indeed I would even say the mixers flexibility and the Group panel are ahead of many if not any host out there. 🙂

    Setting up two paths for VST plugins also poses a problem with the “relative path” option for the plugin filename in the mapping properties. Podium would not know which of the two VST folders it should use to search for the plugins

    .
    Your comments here actually raised some questions for me…But first a possible solution to Podium not knowing which of two folders to search…

    If Podium needs the relative path option to know which VST path to use would it not be possible to…

    a) Add a second relative path option to the Device mapping properties area?

    The fiirst relative path could default to VST fx while the second could default to VSTi plugins.

    If you think that might cause a problem for the “Mapping type” also found in the Devices menu would it not be possible to split the current Software plugin Mapping Type option into two types…Software FX plugin and Software Instrument plugin?

    April 19, 2007 at 13:38 #9780
    Zynewave
    Keymaster

    a) Add a second relative path option to the Device mapping properties area?

    I don’t want to complicate the mapping configuration more than needed.

    Regarding the distinction between VST effect and instrument plugins: Some hosts (older Cubase version comes to mind) require that a plugin is classified as an effect, or else it will not be available in some of the UI menus. That’s why you see some instrument plugins come as two .dll versions, one compiled as an instrument and the other as an effect. There is none such UI restriction in Podium.

    April 19, 2007 at 15:50 #9783
    Conquistador
    Participant

    Ok Frits it was just a suggestion at the end of the day which I still think will refine certain aspects of Podium but I certainly do not want you to change any aspect of Podium beyond what you are comfortable with. 🙂

    As for the questions raised by your earlier comments on the relative path…

    The Podium Guide mentions Absolute and Relative paths. From what I have read it appears that an absolute path would mean Podium must have the exact path to find a particular VST if the VST folder or location is moved. Is that correct?

    If the Relative option is selected then Podium can still find a plugin even if the VST folder is moved to another location and the “Search for missing plugins” option is used to find it for instance….correct?

    Some other things I noticed about the device mapping properties relative option…I recently had to relink or search for missing VST plugs in certain projects and I noticed that some of my mappings had the relative option grayed out after they had been found. Why is this?

    Does that mean if I have to move my VST location again in future that Podium will now treat those plugs as if they have absolute paths instead?

    Also I noticed one of my plugins had the relative option unticked. I thought by default it was always ticked or selected. Any idea why the relative option for any plug would not be already selected if it is an option that should be switched on by default?

    Alot of questions (sorry) but I just need a bit of clarification on the whole relative / absolute “thang” in Podium 🙂

    Thanks.

    April 19, 2007 at 16:45 #9786
    Zynewave
    Keymaster

    I think I’ll eventually remove this “relative path” option for plugins. It’s causing too much confusion. Plugin filenames can be configured as relative to a root VST folder (the VST folder you specify at project creation). The idea was that if you moved your entire plugin collection to a different drive or a different folder, you would only need to change the VST root folder in Podium, and the plugins in your projects would then load correctly from the new path. If the plugins are configured with absolute paths, you would need to use the “search” command if you move the plugins.

    If the “Relative path” option is grayed out, it means that the plugin file is located outside the VST folder you’ve specified, and thus the filename cannot be relative to this folder.

    April 19, 2007 at 22:16 #9791
    duncanparsons
    Participant

    FWIW, I lik ethe relative paths thing… I did move laptops, and changed my base folder, but kept the heirarchy – this meant it was a breeze, and all my old projects loaded fine 😉

    wrt providing other base paths, I would be in favour of that as well, as it goes… Tho’ I wouldn’t restrict it to 2 or three, but ratherthan a list that can be editted. I aslo use Console, which has just this.. you give it a list of possible locations, and it does it’s search that way, just iterating each entry and it’s sub-structure.

    If this were done in Podium, just iterate until you find a plug that matches the spec of the plug required. If the user has a similar plug in 2 locations, then they would have to use the single import.

    Must say, I also like the single import thing – it makes it really easy with VST dev, I just bring it in from it’s dev folder, and it’s all done. When needed, I turn off Podiums engine, recompile, and restart the engine – then I’m ready for the next test cycle…

    But none of this is top of the list! I’m happy with the current config 🙂

    DSP

    April 20, 2007 at 11:36 #9793
    Conquistador
    Participant

    @Zynewave wrote:

    I think I’ll eventually remove this “relative path” option for plugins. It’s causing too much confusion.

    🙂 That is up to you of course, but please do not only base that decision on my comments as there are plenty of other Podium users who may have no problem with it at all. I don’t have a ‘problem’ with it but just wanted a bit more clarification on it, I was in no way trying to have it removed 🙂

    Plugin filenames can be configured as relative to a root VST folder (the VST folder you specify at project creation). The idea was that if you moved your entire plugin collection to a different drive or a different folder, you would only need to change the VST root folder in Podium, and the plugins in your projects would then load correctly from the new path. If the plugins are configured with absolute paths, you would need to use the “search” command if you move the plugins.

    If the “Relative path” option is grayed out, it means that the plugin file is located outside the VST folder you’ve specified, and thus the filename cannot be relative to this folder

    Thanks for the clarification 8)

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