@koolkeys
as it operates as a full host, unfortunately you need the registry at all and also a path in your app data folder. so it will run only on windows systems.
new "EffectChainer" plugin (update: v1.01 released!)
-
- KVRist
- Topic Starter
- 33 posts since 14 Jul, 2006 from Karlsruhe / Germany
-
- KVRAF
- 16154 posts since 2 Dec, 2003 from Nashville, TN
Well, is it possible to just be able to copy the vst version over to the flash drive? What does it need the registry for?
I say this because there are actually alot of apps that can run this way. Not able to run on non-Windows systems, but rather just being able to be loaded as a plugin inside a host that DOES run on a flash drive.
Does this make sense?
Brent
I say this because there are actually alot of apps that can run this way. Not able to run on non-Windows systems, but rather just being able to be loaded as a plugin inside a host that DOES run on a flash drive.
Does this make sense?
Brent
My host is better than your host
-
- KVRAF
- 16154 posts since 2 Dec, 2003 from Nashville, TN
I know that Reaper, for instance, uses the Application Data folder, but if you copy the ini file to the install directory on the flash drive, it will use it from there automatically. Although, it works for me just fine without using it. Just doesn't remember my settings unless I copy that file. Also, EXT2 is going to be totally portable, and use an ini file inside the install directory. I have a sticky thread in the Hardware, etc forum that has a growing list of apps that can do this, and would love to be able to add yours to that list!
Brent
Brent
My host is better than your host
-
- Banned
- 264 posts since 29 Jul, 2006
Some suggestions:
DO NOT SCAN. This process drives me crazy. Only scan when I want to actually use a plugin
Make the plugin selection faster. I have 100's. (Ok, I'm lazy, I never uninstall, including demos + one offs, etc .... I might use them someday
)
You should be able to route the FX in parallel and series and add splits
Thanks
DO NOT SCAN. This process drives me crazy. Only scan when I want to actually use a plugin
Make the plugin selection faster. I have 100's. (Ok, I'm lazy, I never uninstall, including demos + one offs, etc .... I might use them someday
)You should be able to route the FX in parallel and series and add splits
Thanks
-
- KVRian
- 1298 posts since 11 Jun, 2004 from dublin
sounds great! downloading now 
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
Hi N.I.C,
just tried the latest beta and it seems to me that the preset system has still some minor problems.
For example, if I save a simple project in energyXT with a EffectChainer loaded, then loading some plugins into it and after next time loading the project, there's an error that the datasize of the preset doesn't match the saved preset size.
The best way to reproduce is probably if you load the chainer into your host, load some plugins into the EC, and just save the host project and reload it and see what it does - i.e. if it loads the last plugin state.
Maybe you could test this already by just loading EC into itself and saving ?
My guess would be that it has either something to do with the default plugin program, or saving/loading correctly related chunks.
just tried the latest beta and it seems to me that the preset system has still some minor problems.
For example, if I save a simple project in energyXT with a EffectChainer loaded, then loading some plugins into it and after next time loading the project, there's an error that the datasize of the preset doesn't match the saved preset size.
The best way to reproduce is probably if you load the chainer into your host, load some plugins into the EC, and just save the host project and reload it and see what it does - i.e. if it loads the last plugin state.
Maybe you could test this already by just loading EC into itself and saving ?
My guess would be that it has either something to do with the default plugin program, or saving/loading correctly related chunks.
-
- KVRian
- 1372 posts since 3 Dec, 2002
Have not had a chance to really go over this new beta but...
Effects Chainer scanned Cakewalk's Vst adapter and scanned in all of the Vst plug's that it has. When these open they are in the Cakewalk wrapper.
I would kind of like the ability select the plugins I want to use with Chainer.
This ver. seems much better. Thanks
Effects Chainer scanned Cakewalk's Vst adapter and scanned in all of the Vst plug's that it has. When these open they are in the Cakewalk wrapper.
I would kind of like the ability select the plugins I want to use with Chainer.
This ver. seems much better. Thanks
-
- KVRist
- Topic Starter
- 33 posts since 14 Jul, 2006 from Karlsruhe / Germany
@koolkeys
the registry is needed for the complete directx stuff the plugin lists some options and so on..
although it could be possible to get it run on a flash drive (with lots of not minor changes) it was not intended for it.
maybe we can consider it in a possible future version.
@all
check out your findings now and give response as soon as i have results
thx!
the registry is needed for the complete directx stuff the plugin lists some options and so on..
although it could be possible to get it run on a flash drive (with lots of not minor changes) it was not intended for it.
maybe we can consider it in a possible future version.
@all
check out your findings now and give response as soon as i have results
thx!
-
- KVRist
- Topic Starter
- 33 posts since 14 Jul, 2006 from Karlsruhe / Germany
hi, a short update:
i could not figure out problems with saving / loading presets / banks in normal use (datasize of chunks should be correct), but yes, there have been problems when you restore a host's project with effectchainer in it. In this case the state of the first program (VST version) was not restored at all.
i already fixed the error and after some testing we put the new version online.
thx.
i could not figure out problems with saving / loading presets / banks in normal use (datasize of chunks should be correct), but yes, there have been problems when you restore a host's project with effectchainer in it. In this case the state of the first program (VST version) was not restored at all.
i already fixed the error and after some testing we put the new version online.
thx.
-
- KVRian
- 529 posts since 7 Apr, 2003 from Nashville
-
- KVRist
- Topic Starter
- 33 posts since 14 Jul, 2006 from Karlsruhe / Germany
Here is the new 0.3 beta version of EffectChainer.
http://www.acondigital.com/software/ec03Beta.exe
You are welcome to test the new features.
Please give feedback if you encounter bugs or problems with EffectChainer.
major changes version 03Beta (11.08.06):
---------------------------------
- restoring a host's project shoud now restore EffectChainer's state correctly
- you can now decide wheter to perform the initial scan for plugins on EffectChainer's first use
- removed the "Rescan Plugin List" from options menu
- added option "Rescan DirectX Plugins"
- added a "VST Folders Manager" to specify more than one VST Folder and scan them selective
- added a "Recent Plugins" list to effect menu which stores up to ten last used plugins
- the accumulated initial delay of VST plugs is now updated and transmitted to the host (right before playback starts!)
- added a manual which is accessible in the help menu
-----------------------------------
Have fun.
regards N.I.C
http://www.acondigital.com/software/ec03Beta.exe
You are welcome to test the new features.
Please give feedback if you encounter bugs or problems with EffectChainer.
major changes version 03Beta (11.08.06):
---------------------------------
- restoring a host's project shoud now restore EffectChainer's state correctly
- you can now decide wheter to perform the initial scan for plugins on EffectChainer's first use
- removed the "Rescan Plugin List" from options menu
- added option "Rescan DirectX Plugins"
- added a "VST Folders Manager" to specify more than one VST Folder and scan them selective
- added a "Recent Plugins" list to effect menu which stores up to ten last used plugins
- the accumulated initial delay of VST plugs is now updated and transmitted to the host (right before playback starts!)
- added a manual which is accessible in the help menu
-----------------------------------
Have fun.
regards N.I.C
-
- KVRAF
- 10286 posts since 17 Sep, 2004 from Austin, TX
Ah, now you can choose whether to scan the VST folder!?
Bravo!
Bravo!
N.I.C wrote:Here is the new 0.3 beta version of EffectChainer.
http://www.acondigital.com/software/ec03Beta.exe
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
Yay 
Presets are remembered correctly now. The scanning is very convenient now as well.
A problem is still to be found in the gui handling of plugins, i.e. it seems that the EC doesn't correctly check or tell if a plugin's child window(s) need to be refreshed/redrawn (probably best reproduced with eXT and a few plugins loaded).
Presets are remembered correctly now. The scanning is very convenient now as well.
A problem is still to be found in the gui handling of plugins, i.e. it seems that the EC doesn't correctly check or tell if a plugin's child window(s) need to be refreshed/redrawn (probably best reproduced with eXT and a few plugins loaded).
-
- KVRer
- 7 posts since 28 Feb, 2006
First of all thanx. As it happens I have been "auditioning" chainers and trying to find the one that I want to work with. I just saw this so of course I downloaded it. After installing a few of these things I am finding out that the main place where any of them has problems is on the install and especially the initial plugin scan. Once they are up and running then it's usually just a matter of finding the one that suits your needs. So I can make the following observations/suggestions about the install.
1 - The EffectChainer.dll should not just install itself in the Steinberg vst folder without letting the user know this and without giving them the chance to change it. Especially when it does not even install in the same place as the rest of the files. I for one don't even use the Steinberg folder and consequently I had no idea how to open the Chainer. Fortunately I saw the answer here on this thread but many people would not see that and not be able to make use of the Chainer and probably just give up and uninstall it.
2 - The plugin scan should not just start automatically and again without giving the user a chance to have it scan only certain folders. Consequently I had to sit and cancel popups for things such as my Cakewalk plugins, saying that they are not licensed for use outside of Cakewalk. Which is correct, but I don't generally have host programs scan the Cakewalk folder.Another reason why it should give you the option to specify the location is because many people such as myself will only want to have a small selection of plugins to use with a chainer. For example, I want to use mine as a guitar effects processor. In order to keep it lean and mean I will only want to have the plugins that I need for the guitar available to the chainer. If I am going to be playing live and using a laptop as a DSP then I don't want 500 plugins there to bog everything down. I mean - I don't need a mastering plugin in my live guitar effects chain. And to take this a step further, I may have a few small groups of plugins to use in this manner, for example I might want a four plug basic mastering chain to be available for when I don't want hundreds of plugins sitting there creating chances for slow behavior or crashing as there will be when I use a DAW. I don't think that too many people want a chainer to be scanning hundreds of plugins every time it fires up. We already have that - they are called workstations. The chainer, to me anyway, should be a lean and mean stripped down affair with onlt the controls that are needed. Soooo...a lot of words but the basic point of them all is to give the user a chance to specify folders before doing anything.
3 - I am not sure if this has been addressed so it is not an observation of your chainer, but there should be an option as to how the chainer behaves when opened, with regards to plugin scanning. Should it a)scan all plugins again or b)look for new or changed plugins only or 3)not scan for plugins at all. The last option being for use when you have your plugins set up the way you want them because again, most people are going to use the chainer for specialized arrangements of just a few plugins. Of course there will always be the option for a manual scan too.
So far so good after that, I'll post again after I've used it for a while.
1 - The EffectChainer.dll should not just install itself in the Steinberg vst folder without letting the user know this and without giving them the chance to change it. Especially when it does not even install in the same place as the rest of the files. I for one don't even use the Steinberg folder and consequently I had no idea how to open the Chainer. Fortunately I saw the answer here on this thread but many people would not see that and not be able to make use of the Chainer and probably just give up and uninstall it.
2 - The plugin scan should not just start automatically and again without giving the user a chance to have it scan only certain folders. Consequently I had to sit and cancel popups for things such as my Cakewalk plugins, saying that they are not licensed for use outside of Cakewalk. Which is correct, but I don't generally have host programs scan the Cakewalk folder.Another reason why it should give you the option to specify the location is because many people such as myself will only want to have a small selection of plugins to use with a chainer. For example, I want to use mine as a guitar effects processor. In order to keep it lean and mean I will only want to have the plugins that I need for the guitar available to the chainer. If I am going to be playing live and using a laptop as a DSP then I don't want 500 plugins there to bog everything down. I mean - I don't need a mastering plugin in my live guitar effects chain. And to take this a step further, I may have a few small groups of plugins to use in this manner, for example I might want a four plug basic mastering chain to be available for when I don't want hundreds of plugins sitting there creating chances for slow behavior or crashing as there will be when I use a DAW. I don't think that too many people want a chainer to be scanning hundreds of plugins every time it fires up. We already have that - they are called workstations. The chainer, to me anyway, should be a lean and mean stripped down affair with onlt the controls that are needed. Soooo...a lot of words but the basic point of them all is to give the user a chance to specify folders before doing anything.
3 - I am not sure if this has been addressed so it is not an observation of your chainer, but there should be an option as to how the chainer behaves when opened, with regards to plugin scanning. Should it a)scan all plugins again or b)look for new or changed plugins only or 3)not scan for plugins at all. The last option being for use when you have your plugins set up the way you want them because again, most people are going to use the chainer for specialized arrangements of just a few plugins. Of course there will always be the option for a manual scan too.
So far so good after that, I'll post again after I've used it for a while.
-
- KVRer
- 7 posts since 28 Feb, 2006
PS - I noticed the above posts about changes to the scan processes. I am not sure but I think that I downloaded the latest revision since I got it from the link in this thread and it did not give me the option to abort the scan during the install process. It just started scanning.
Also - the main point to take away from my long post above is not to give in to the temptation to fill your chainer with features. It starts innocuosly enough - you think, well I'll just add a little sampler, or a little arpeggiator, etc. and the next thing you know you have a workstation. And we already have plenty of those. My advice is to keep it a simple rack and then make it the best and most stable rack that you possibly can. Pay attention to making it work with as many brands of plugins as you can. I can tell you that I have not yet tried a chainer that can use Waves plugins. I am not saying that yours should be able to do this but it would be nice if it could.
The GUI. For me, the GUI is very important. A nice looking GUI inspires me to use it. A bland GUI, no matter how well it works, simply does not get me fired up. I know that it should not matter, but it does. This does not have to mean overdone and gimmicky. As a "real" musician, ie. I have been playing for 25 years, before digital - I prefer that any software that is emulating hardware to look somewhat like hardware. I think that a lot of people do too - not just us old analog guys. For one thing - the hardware interfaces evolved over decades to look the way that they do because they are the most logical ways to make the controls work. So following the hw model will insure a plugin that is easy for the user to learn and to operate.
Finally, my ideal chainer would have two views of operation. One, as a rack with the basic controls (plugin on/off, volume, etc) viewable. Pretty much like the basic view of your rack so far, or something like Xlutop. And the other would be a full plug view, where the plugin interfaces would be resized all to one size and be vertically scrollable (since racks are usually vertical in construction). Of course there would be the option to mix views, so when scrolling you can only keep open the interfaces that you want open and the rest would be the small rack view. I don't know if it is possible to have your software resize each interface to a common size, but that would be nice. The difference in sizes betwen plugins can sometimes be very annoying when trying to work with a chain.
Also - the main point to take away from my long post above is not to give in to the temptation to fill your chainer with features. It starts innocuosly enough - you think, well I'll just add a little sampler, or a little arpeggiator, etc. and the next thing you know you have a workstation. And we already have plenty of those. My advice is to keep it a simple rack and then make it the best and most stable rack that you possibly can. Pay attention to making it work with as many brands of plugins as you can. I can tell you that I have not yet tried a chainer that can use Waves plugins. I am not saying that yours should be able to do this but it would be nice if it could.
The GUI. For me, the GUI is very important. A nice looking GUI inspires me to use it. A bland GUI, no matter how well it works, simply does not get me fired up. I know that it should not matter, but it does. This does not have to mean overdone and gimmicky. As a "real" musician, ie. I have been playing for 25 years, before digital - I prefer that any software that is emulating hardware to look somewhat like hardware. I think that a lot of people do too - not just us old analog guys. For one thing - the hardware interfaces evolved over decades to look the way that they do because they are the most logical ways to make the controls work. So following the hw model will insure a plugin that is easy for the user to learn and to operate.
Finally, my ideal chainer would have two views of operation. One, as a rack with the basic controls (plugin on/off, volume, etc) viewable. Pretty much like the basic view of your rack so far, or something like Xlutop. And the other would be a full plug view, where the plugin interfaces would be resized all to one size and be vertically scrollable (since racks are usually vertical in construction). Of course there would be the option to mix views, so when scrolling you can only keep open the interfaces that you want open and the rest would be the small rack view. I don't know if it is possible to have your software resize each interface to a common size, but that would be nice. The difference in sizes betwen plugins can sometimes be very annoying when trying to work with a chain.