|
This topic was last updated 180 days ago, and thus it can be considered old. Replying is disabled for this topic.
|
jonathantneal
on Jul 26, 2006, 11:28pm:
Hi there,
I really enjoyed trialing your Voxengo VST plugins. I have two suggestions off the top of my head to throw at you. I'll try make them as quick and to the point as I can.
Suggestion 1:
In Cakewalk Sonar, Mackie Tracktion, and probably many other programs, the Voxengo plugins show up very disorganized, and this can be fixed by...
... 1. Having a parent folder which is named "Voxengo" which resides in the VstPlugins directory (ie: "C:\Program Files\VstPlugins\Voxengo\").
... 2. Having child subfolders inside the parent "Voxengo" folder which are named "Marquis Compressor" /"GlissEQ" / etc accordingly (ie: "C:\Program Files\VstPlugins\Voxengo\Marquis Compressor").
... 3. Naming the VSTs "Voxengo Marquis Compressor.dll" / "Voxengo GlissEQ.dll" / etc accordingly (ie: "C:\Program Files\VstPlugins\Voxengo\Marquis Compressor\Voxengo Marquis Compressor.dll").
All the plugins will now appear organized. Ooo, it looks good.
Suggestion 2:
In the Start Menu, Voxengo plugins could look a lot cleaner by...
... 1. Removing the "Voxengo" prefix and the "VST" suffix on each subfolder name under the "Voxengo" parent Start Menu folder.
... 2. Replacing the "Purchase" and "Register" shortcuts with a new, single register.exe app. I made one to show you and placed it on my website @ http://www.turboultra.com/voxengo/
(cont) Take a look at the registration wizard I made because it should work for all of your plugins. It will display, write, edit, and remove any Voxengo plugin registration data, as well as direct you to each plugin homepage for purchase and more info.
(cont) If you were to follow both of these suggestions then you could include the register.exe in the Voxengo parent folder, and there wouldn't be a dozen duplicates for Voxengo fans. (ie "C:\Program Files\Voxengo\register.exe")
I have many more suggestions if you would like to know them, and I'm not asking for any money. I float around the internet in my spare time contributing to various projects that I really admire.
Sincerely,
- Jonathan
I really enjoyed trialing your Voxengo VST plugins. I have two suggestions off the top of my head to throw at you. I'll try make them as quick and to the point as I can.
Suggestion 1:
In Cakewalk Sonar, Mackie Tracktion, and probably many other programs, the Voxengo plugins show up very disorganized, and this can be fixed by...
... 1. Having a parent folder which is named "Voxengo" which resides in the VstPlugins directory (ie: "C:\Program Files\VstPlugins\Voxengo\").
... 2. Having child subfolders inside the parent "Voxengo" folder which are named "Marquis Compressor" /"GlissEQ" / etc accordingly (ie: "C:\Program Files\VstPlugins\Voxengo\Marquis Compressor").
... 3. Naming the VSTs "Voxengo Marquis Compressor.dll" / "Voxengo GlissEQ.dll" / etc accordingly (ie: "C:\Program Files\VstPlugins\Voxengo\Marquis Compressor\Voxengo Marquis Compressor.dll").
All the plugins will now appear organized. Ooo, it looks good.
Suggestion 2:
In the Start Menu, Voxengo plugins could look a lot cleaner by...
... 1. Removing the "Voxengo" prefix and the "VST" suffix on each subfolder name under the "Voxengo" parent Start Menu folder.
... 2. Replacing the "Purchase" and "Register" shortcuts with a new, single register.exe app. I made one to show you and placed it on my website @ http://www.turboultra.com/voxengo/
(cont) Take a look at the registration wizard I made because it should work for all of your plugins. It will display, write, edit, and remove any Voxengo plugin registration data, as well as direct you to each plugin homepage for purchase and more info.
(cont) If you were to follow both of these suggestions then you could include the register.exe in the Voxengo parent folder, and there wouldn't be a dozen duplicates for Voxengo fans. (ie "C:\Program Files\Voxengo\register.exe")
I have many more suggestions if you would like to know them, and I'm not asking for any money. I float around the internet in my spare time contributing to various projects that I really admire.
Sincerely,
- Jonathan
Aleksey Vaneev
on Jul 27, 2006, 2:20am:
Thanks for your message.
Actually, I'm already planning to rework plug-in naming scheme and installation folder structure.
Your idea to put Register.exe into the same folder won't work as expected, because in this scenario - if some plug-in was removed - Register.exe will be uninstalled as well leaving other plug-ins without means to enter registration information. Right now I'm thinking of introducing alternative entry method - right inside the plug-in. This won't require any additional executables.
As for the plug-in names, even though what you are offering looks obviously more convenient, I can't be sure this naming scheme will be working in all hosts. It should be confirmed working before I will be using such naming scheme. (I plan to rename 'VoxengoGlissEQ.dll' into just 'GlissEQ.dll', placed into Voxengo subfolder - other DLLs in a similar manner).
Beside putting companion files into subfolders (e.g. "Voxengo GlissEQ VST") in VstPlugins folder I plan to put them into Program Files/Voxengo folder - many plug-ins from other vendors install that way.
To sum up, right now I won't be changing anything, but the first plug-in release (that will be hopefully released soon) is going to follow this new installation scheme.
Actually, I'm already planning to rework plug-in naming scheme and installation folder structure.
Your idea to put Register.exe into the same folder won't work as expected, because in this scenario - if some plug-in was removed - Register.exe will be uninstalled as well leaving other plug-ins without means to enter registration information. Right now I'm thinking of introducing alternative entry method - right inside the plug-in. This won't require any additional executables.
As for the plug-in names, even though what you are offering looks obviously more convenient, I can't be sure this naming scheme will be working in all hosts. It should be confirmed working before I will be using such naming scheme. (I plan to rename 'VoxengoGlissEQ.dll' into just 'GlissEQ.dll', placed into Voxengo subfolder - other DLLs in a similar manner).
Beside putting companion files into subfolders (e.g. "Voxengo GlissEQ VST") in VstPlugins folder I plan to put them into Program Files/Voxengo folder - many plug-ins from other vendors install that way.
To sum up, right now I won't be changing anything, but the first plug-in release (that will be hopefully released soon) is going to follow this new installation scheme.
jonathantneal
on Jul 27, 2006, 4:04am:
Hello again Aleksey,
About the 1st thing:
Superb! Registering plugins within the actual plugin is much easier and more secure. Besides, you can still have it read the same registry values. I was just trying to help, and thanks for the update :)
About the 2nd thing:
In any music software, VST plugins will only appear in one of three ways.
In all Cakewalk software, plugins are organized by their filename, so if you have more than one VST or VSTi with the word "Voxengo " (with the space) then they will appear to be under a common subfolder. In this instance you will get:
Voxengo > Gliss EQ
(where > represents the appearance of a subfolder)
In Mackie Tracktion or Chainer, folders and subfolders are recognized, so you'll get:
Voxengo > Gliss EQ > Voxengo Gliss EQ
In all Sony Software or MiniHost, there are no child folders at all. This means you would have all your effects listed out without subfolders, so you'll get:
Voxengo Gliss EQ
In all three instances, using the naming scheme I presented will result in an orderly appearance of your VST effects.
Thanks for the quick reply, I'm assured you put a great deal of effort into these plugins and it is deeply appreciated!
About the 1st thing:
Superb! Registering plugins within the actual plugin is much easier and more secure. Besides, you can still have it read the same registry values. I was just trying to help, and thanks for the update :)
About the 2nd thing:
In any music software, VST plugins will only appear in one of three ways.
In all Cakewalk software, plugins are organized by their filename, so if you have more than one VST or VSTi with the word "Voxengo " (with the space) then they will appear to be under a common subfolder. In this instance you will get:
Voxengo > Gliss EQ
(where > represents the appearance of a subfolder)
In Mackie Tracktion or Chainer, folders and subfolders are recognized, so you'll get:
Voxengo > Gliss EQ > Voxengo Gliss EQ
In all Sony Software or MiniHost, there are no child folders at all. This means you would have all your effects listed out without subfolders, so you'll get:
Voxengo Gliss EQ
In all three instances, using the naming scheme I presented will result in an orderly appearance of your VST effects.
Thanks for the quick reply, I'm assured you put a great deal of effort into these plugins and it is deeply appreciated!
Dandruff
on Jul 27, 2006, 4:31am:
i like the way how it is done at the moment. works great as it is! i can point it myself to a "voxengo" main-folder during the installation. the only thing i always do is to rename them (to "GlissEQ.dll" for example) ...
jonathantneal
on Jul 27, 2006, 6:14pm:
Let me illustrate what is happening. The way it is done is already very close to what I'm suggesting.
Image 1
In the image linked above, you will see what a VstPlugins folder looks like after you installed Marquis Compressor and GlissEQ (as it is, currently).
Image 2
In the image linked above, you will see what the GlissEQ subfolder looks like (as it is, currently).
Image 3
In the imagine linked above, here is an example of what my suggested format would produce.
To give one example of how this naming scheme improves the overall experience.
Image 1
In the image linked above, you will see how Marquis Compressor and GlissEQ appear in Cakewalk Sonar (as it is, currently).
Image 2
In the image linked above, here is an example of what my suggested format would produce. You will see how many Voxengo plugins would look in Cakewalk Sonar.
Those sub-directories in the second set of images are not generated by physical folders, but by the .dll names. In other programs, however, the sub-directories ARE generated by physical folders. You can accommodate both, easily. :)
Image 1
In the image linked above, you will see what a VstPlugins folder looks like after you installed Marquis Compressor and GlissEQ (as it is, currently).
Image 2
In the image linked above, you will see what the GlissEQ subfolder looks like (as it is, currently).
Image 3
In the imagine linked above, here is an example of what my suggested format would produce.
To give one example of how this naming scheme improves the overall experience.
Image 1
In the image linked above, you will see how Marquis Compressor and GlissEQ appear in Cakewalk Sonar (as it is, currently).
Image 2
In the image linked above, here is an example of what my suggested format would produce. You will see how many Voxengo plugins would look in Cakewalk Sonar.
Those sub-directories in the second set of images are not generated by physical folders, but by the .dll names. In other programs, however, the sub-directories ARE generated by physical folders. You can accommodate both, easily. :)
Aleksey Vaneev
on Jul 27, 2006, 10:51pm:
I do not think an additional folder after Voxengo is required. Having 'VstPlugins/Voxengo' is enough, and all DLLs will be residing there. Companion files will be in 'Program Files/Voxengo' folder. (your Tracktion example of 'Voxengo > Gliss EQ > Voxengo Gliss EQ' looks odd because of this additional GlissEQ folder).
I wanted to get rid of 'Voxengo' prefix in DLL names, because some hosts have only 24 characters space to diplay plug-in names. So, something like 'Voxengo Vintage Modulator' is going to be shown cut.
Of course, if Cakewalk's VST adapter won't be able to group plug-ins without that prefix I'll have to include 'Voxengo' prefix into DLL names.
I wanted to get rid of 'Voxengo' prefix in DLL names, because some hosts have only 24 characters space to diplay plug-in names. So, something like 'Voxengo Vintage Modulator' is going to be shown cut.
Of course, if Cakewalk's VST adapter won't be able to group plug-ins without that prefix I'll have to include 'Voxengo' prefix into DLL names.
jonathantneal
on Jul 28, 2006, 12:55am, edited 1 time(s), last modified on Jul 28, 2006, 12:57am:
Actually I added the median sub-folder so that there would be space for your plugin help/preferences, ex.:
. Voxengo > GlissEQ > Voxengo GlissEQ.dll
. Voxengo > GlissEQ > Preferences > Help > ...
. Voxengo > GlissEQ > Preferences > Presets > ...
Otherwise, you're going to have one of two things, ex.:
. Voxengo > Voxengo GlissEQ.dll
. Voxengo > GlissEQ > Help > ...
. Voxengo > GlissEQ > Presets > ...
(the subfolder would still be created)
Or, ex.:
. Voxengo > Voxengo GlissEQ.dll
. Voxengo > GlissEQ Help > ...
. Voxengo > GlissEQ Presets > ...
(the subfolder would still be created, only more-so)
I was trying to find the happy median between VST host applications and the way in which your software currently opperates. :) *don't hate me*
. Voxengo > GlissEQ > Voxengo GlissEQ.dll
. Voxengo > GlissEQ > Preferences > Help > ...
. Voxengo > GlissEQ > Preferences > Presets > ...
Otherwise, you're going to have one of two things, ex.:
. Voxengo > Voxengo GlissEQ.dll
. Voxengo > GlissEQ > Help > ...
. Voxengo > GlissEQ > Presets > ...
(the subfolder would still be created)
Or, ex.:
. Voxengo > Voxengo GlissEQ.dll
. Voxengo > GlissEQ Help > ...
. Voxengo > GlissEQ Presets > ...
(the subfolder would still be created, only more-so)
I was trying to find the happy median between VST host applications and the way in which your software currently opperates. :) *don't hate me*
Aleksey Vaneev
on Jul 28, 2006, 2:53am:
I'm not hating you - just letting you know this aspect of plug-ins was already in development for some time.
I was thinking about this storage scheme:
../VstPlugins/Voxengo/Voxengo GlissEQ.dll
/Program Files/Voxengo/GlissEQ/Help/
/Program Files/Voxengo/GlissEQ/Presets/ (although, factory presets won't be stored on disk - I plan to store them in ROM inside the plug-in itself).
Anyway, I'm still worrying about plug-in DLL name length. I do really want to keep it just 'GlissEQ.dll'. If Cakewalk VST support won't recognize Voxengo in this scenario, I'll ask Cakewalk to implement such grouping (Voxengo and many other plug-ins do export 'vendor' name which can be also used for grouping).
I was thinking about this storage scheme:
../VstPlugins/Voxengo/Voxengo GlissEQ.dll
/Program Files/Voxengo/GlissEQ/Help/
/Program Files/Voxengo/GlissEQ/Presets/ (although, factory presets won't be stored on disk - I plan to store them in ROM inside the plug-in itself).
Anyway, I'm still worrying about plug-in DLL name length. I do really want to keep it just 'GlissEQ.dll'. If Cakewalk VST support won't recognize Voxengo in this scenario, I'll ask Cakewalk to implement such grouping (Voxengo and many other plug-ins do export 'vendor' name which can be also used for grouping).
ToneCarver
on Jul 28, 2006, 3:26am:
Aleksey Vaneev: Beside putting companion files into subfolders (e.g. ''Voxengo GlissEQ VST'') in VstPlugins folder I plan to put them into Program Files/Voxengo folder - many plug-ins from other vendors install that way.
Aleksey, Can you have the installer give an option to select a directory to store the companion files, defaulting to "Program Files/Voxengo", but changeable ? I like that approach as I typically select the same directory for the .dll and the companion files so that I only have to remember to go to one place to find the help files.
Just a suggestion. Keep up the good work on your excellent plugs.
-Bill
Aleksey Vaneev
on Jul 28, 2006, 11:08am:
Sure, I do plan to offer folder selection. This will make two folder selections necessary, but I guess it's not much of a deal.
|
This topic was last updated 180 days ago, and thus it can be considered old. Replying is disabled for this topic.
|
Copyright © 2002-2012 Aleksey Vaneev - Terms of Use - Privacy Policy - About Voxengo - Questions & Answers