Problems with Filterscape
-
- KVRian
- 571 posts since 14 Oct, 2004 from UK
Hi,
I've installed the Filterscape demo on my Receptor and there are a few problems.
1- By default, it creates a u-he folder inside Program Files, which is not good for Receptor use as unsupported plugins are supposed to go to the Unsupported Plugins folder. I couldn't find any registry key to specify a folder to store the presets. Can the presets be stored in the same folder as that of install ? It would be useful to have the option to do so.Francois Rossi
2- Checking with VST scanner to make sure it was not a bug on Receptor, it seems that the ID for filterscape is AMEQ whilst the other two are FSQ6 and FSVA. Why does Filterscape use AMEQ ? It's a problem as AMEQ is also used by Electri-Q from AIXcoustic Creations and so since Receptor needs unique IDs, you cannot have Filterscape and Electri-Q installed at the same time. Could you change the ID to FS something for Filterscape so it follows the model used by the other two dll ?
I've installed the Filterscape demo on my Receptor and there are a few problems.
1- By default, it creates a u-he folder inside Program Files, which is not good for Receptor use as unsupported plugins are supposed to go to the Unsupported Plugins folder. I couldn't find any registry key to specify a folder to store the presets. Can the presets be stored in the same folder as that of install ? It would be useful to have the option to do so.Francois Rossi
2- Checking with VST scanner to make sure it was not a bug on Receptor, it seems that the ID for filterscape is AMEQ whilst the other two are FSQ6 and FSVA. Why does Filterscape use AMEQ ? It's a problem as AMEQ is also used by Electri-Q from AIXcoustic Creations and so since Receptor needs unique IDs, you cannot have Filterscape and Electri-Q installed at the same time. Could you change the ID to FS something for Filterscape so it follows the model used by the other two dll ?
- u-he
- 30213 posts since 8 Aug, 2002 from Berlin
Hmmm, I don't know much about the specifics of Receptor. But I'm working on having all data files required for my plugins going to C:\Program Files\u-he\, with the possibility to use shortcuts to other directories. I have no plans to write anything into the Registry.Kermit Jagger wrote:Hi,
I've installed the Filterscape demo on my Receptor and there are a few problems.
1- By default, it creates a u-he folder inside Program Files, which is not good for Receptor use as unsupported plugins are supposed to go to the Unsupported Plugins folder. I couldn't find any registry key to specify a folder to store the presets. Can the presets be stored in the same folder as that of install ? It would be useful to have the option to do so.Francois Rossi
AMEQ is historical, because the plugin was created long before its name was set in stone. AM is the name of my engine, EQ is, well, EQKermit Jagger wrote:2- Checking with VST scanner to make sure it was not a bug on Receptor, it seems that the ID for filterscape is AMEQ whilst the other two are FSQ6 and FSVA. Why does Filterscape use AMEQ ? It's a problem as AMEQ is also used by Electri-Q from AIXcoustic Creations and so since Receptor needs unique IDs, you cannot have Filterscape and Electri-Q installed at the same time. Could you change the ID to FS something for Filterscape so it follows the model used by the other two dll ?
I have officially registered AMEQ with Steinberg and I have no plans to change that. It would break compatibility for existing projects for more than a thousand musicians.
Please inform that other company to choose a free Unique ID, available from Steinbergs website. And please contact Muse about this, no modern host should rely on Unique IDs alone.
Cheers,
-
- KVRAF
- 2734 posts since 15 Apr, 2004 from Capital City, UK
Plogue Bidule uses this method for identification which has caused me a number of problems (Tone2's Firebird is currently unusable in Bidule), but Urs is right - developers should determine a unique id which won't conflict with any from the Steinberg list, and then register that name for future reference. Unfortunately some vst developers don't do this because, as Urs insinuates, developers do not expect vst hosts to use this alone to identify each plugin.Urs wrote:no modern host should rely on Unique IDs alone.
Which is a shame.
Strangly enough I had considered purchasing that highly acclaimed Electri-Q, but have resisted since Voxengo's are good to me for the time being
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
Thanks for the reply.
It would be good to be able to select the folder where the data goes. It would certainly simplify using your plug on Receptor as the Program Files folder is locked by default.
It would be good to be able to select the folder where the data goes. It would certainly simplify using your plug on Receptor as the Program Files folder is locked by default.
- u-he
- 30213 posts since 8 Aug, 2002 from Berlin
Yeah, that's something I do have in the back of my mind.
As you might know, I'm very happy that my stuff runs on Windows at all (and with even less problems than the Mac versions - wheww)... thus I'm a bit reluctant to commit any changes in the running setup...
However, I've got that external developer who's now into thinking about installers. If I had the right installer, it should be no big deal to make folders choosable.
Hmmm... how does Receptor present you with the gui anyways? - If the gui is more like a remote plugin on another computer or if it's some kind of generic view, then all these files (including presets) are technically not needed on Receptor.
Cheers,
Urs
As you might know, I'm very happy that my stuff runs on Windows at all (and with even less problems than the Mac versions - wheww)... thus I'm a bit reluctant to commit any changes in the running setup...
However, I've got that external developer who's now into thinking about installers. If I had the right installer, it should be no big deal to make folders choosable.
Hmmm... how does Receptor present you with the gui anyways? - If the gui is more like a remote plugin on another computer or if it's some kind of generic view, then all these files (including presets) are technically not needed on Receptor.
Cheers,
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
Yes, technically the files are not needed, but that would mean not being able to use the presets and the Filterscape VA seems to have lots of good ones.
It would be simpler to have the presets folder in the same directory or folder as where the dll was installed.
It would be simpler to have the presets folder in the same directory or folder as where the dll was installed.
- u-he
- 30213 posts since 8 Aug, 2002 from Berlin
Yes, but I just learned that hosts start slower if the Vstplugins folder is cluttered with a lot of files that are no plugins.Kermit Jagger wrote:Yes, technically the files are not needed, but that would mean not being able to use the presets and the Filterscape VA seems to have lots of good ones.
It would be simpler to have the presets folder in the same directory or folder as where the dll was installed.
I'll work that out soonishly, but my priority now is Zebra2 of course...
Later,
