Updating FL Studio: selecting plug-ins
-
- KVRAF
- 10597 posts since 13 Jun, 2004 from Alberto Balsam
Is there an easier way than doing this manually? I wish FL Studio made some kind of system file that kept track of it's VST list, and wouldnt replace this file when re-installed and allowed you to paste it in the corresponding folder of different locations.
-
- Rad Grandad
- 38041 posts since 6 Sep, 2003 from Downeast Maine
why is that so hard? I just keep a vst folder outside FL and all my apps point to it...The Chase wrote:Is there an easier way than doing this manually? I wish FL Studio made some kind of system file that kept track of it's VST list, and wouldnt replace this file when re-installed and allowed you to paste it in the corresponding folder of different locations.
The highest form of knowledge is empathy, for it requires us to suspend our egos and live in another's world. It requires profound, purpose‐larger‐than‐the‐self kind of understanding.
-
- KVRian
- 1256 posts since 22 Aug, 2003
Because it takes FOREVER to re-enable all the VST(i)'s that are necessary! (mostly the Effects).
-
- KVRAF
- Topic Starter
- 10597 posts since 13 Jun, 2004 from Alberto Balsam
I'm talking about checking the little "F" boxes when you pull up the list of VST via "More..." under "Channel.". I have an excel spreadsheet of all my plugs, 99 instruments and 105 effects, not all of which have obvious file names to check the box near.Hink wrote:why is that so hard? I just keep a vst folder outside FL and all my apps point to it...The Chase wrote:Is there an easier way than doing this manually? I wish FL Studio made some kind of system file that kept track of it's VST list, and wouldnt replace this file when re-installed and allowed you to paste it in the corresponding folder of different locations.
Last edited by The Chase on Mon Dec 19, 2005 11:44 pm, edited 1 time in total.
-
- Rad Grandad
- 38041 posts since 6 Sep, 2003 from Downeast Maine
you kids crack me up...Rellik...forever? Well let's say you got 100 vsts, that would take you tops 2 minutes to enable, something you should have to do once a year...is two minutes a year that intolerable...chase either I missed your point or you missed mine......still what would you guys do back in the day when studios needed daily maintenance, cleaning then heads took longer for crying out loud 
:hihi:The highest form of knowledge is empathy, for it requires us to suspend our egos and live in another's world. It requires profound, purpose‐larger‐than‐the‐self kind of understanding.
-
- KVRAF
- Topic Starter
- 10597 posts since 13 Jun, 2004 from Alberto Balsam
2 minutes more like 10...but you've still got a point...Hink wrote:
-
- KVRAF
- Topic Starter
- 10597 posts since 13 Jun, 2004 from Alberto Balsam
it only saves colors and file paths, not selected VSt's.Micha wrote:I remember a favorite file in FLStudio 5 that you can copy to FLS 6.
-
- KVRAF
- Topic Starter
- 10597 posts since 13 Jun, 2004 from Alberto Balsam
-
- KVRian
- 1256 posts since 22 Aug, 2003
The list also gets cleared sometimes when FL crashesHink wrote:
so I'd say I have to do this at least 10-15 times a year.It takes maybe 10-15 minutes to do, since I have to go through and actually think about whether I want it "on call", or don't want it in the list for normal usage. You have to scroll through the long list and try to find which is which in the often cryptic names, and it eventually gets old after a while...
Thanks for the tip on the favorites file, by the way
.Studios weren't generally run by a single person, "back in the day". They also weren't normally maintained by the same people who actually wanted to use them to compose, record and produce the music. The maintenance was also normally a full-time or part-time job for the staff. Also, they didn't have as many VST'sHink wrote:still what would you guys do back in the day when studios needed daily maintenance, cleaning then heads took longer for crying out loud
-
- Rad Grandad
- 38041 posts since 6 Sep, 2003 from Downeast Maine
It takes maybe 10-15 minutes to do, since I have to go through and actually think about whether I want it "on call", or don't want it in the list for normal usage. You have to scroll through the long list and try to find which is which in the often cryptic names, and it eventually gets old after a while...
The highest form of knowledge is empathy, for it requires us to suspend our egos and live in another's world. It requires profound, purpose‐larger‐than‐the‐self kind of understanding.
-
- KVRAF
- Topic Starter
- 10597 posts since 13 Jun, 2004 from Alberto Balsam
-
- KVRAF
- 8082 posts since 9 Jan, 2003 from Saint Louis MO
I'm kind of annoyed by that too... mostly because I had to do it twice this morning due to my crash, and that took away from time I could have spent playing with the new stuff.
I've often thought the interface for assigning plugins, and for picking them once you've done it, are weak points.
A multi-column interface for classifying DLLs as instruments, effects, or both would let you do it all in one pass instead of two.
A way of assigning plugins to categories, either predefined or custom, would be even better. Instead of "insert... pick something out of a list of 150 things with obscure names" it'd be "insert... pick 'chorus'... pick something out of a list of 8 things". That would just be awesome. It'd have to be optional though, so as not to piss off people with fewer plugins.
And then FL could come with a modest database of plugins by default, so it automatically knows that Kubik.dll is a wavetable instrument for instance. The amount of data that would take would be fairly small in the scheme of things, but would accelerate setup.
I've often thought the interface for assigning plugins, and for picking them once you've done it, are weak points.
A multi-column interface for classifying DLLs as instruments, effects, or both would let you do it all in one pass instead of two.
A way of assigning plugins to categories, either predefined or custom, would be even better. Instead of "insert... pick something out of a list of 150 things with obscure names" it'd be "insert... pick 'chorus'... pick something out of a list of 8 things". That would just be awesome. It'd have to be optional though, so as not to piss off people with fewer plugins.
And then FL could come with a modest database of plugins by default, so it automatically knows that Kubik.dll is a wavetable instrument for instance. The amount of data that would take would be fairly small in the scheme of things, but would accelerate setup.
-
- KVRAF
- Topic Starter
- 10597 posts since 13 Jun, 2004 from Alberto Balsam
Even more badass, would be the ability to select them at random within these catagories. Is that what you meant?foosnark wrote:A way of assigning plugins to categories, either predefined or custom, would be even better. Instead of "insert... pick something out of a list of 150 things with obscure names" it'd be "insert... pick 'chorus'... pick something out of a list of 8 things". That would just be awesome. It'd have to be optional though, so as not to piss off people with fewer plugins.