hey good people....
i while ago i read a thread on here that discussed how to change a plugins id when it was repeatedly failing using the unsupported install method, does anybody know how to do this or have a link to the thread as i cant seem to find it again.
thanks in advance...... p.
changing a plugins id?
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi Prizzle,
Have you looked at the .XML files associated with the plugin? Usually there is an XXX_info.xml file associated with an unsupported plug (for Atmosphere, the (early USB plugs), etc. there were instructions for creating these XML files to install unsupported). Anyway, you could try changing the Plugin ID within this XML file. Edit it, then refresh the plug-in cache (Hold 'Multi' button, and triple-click power, wait about 10minutes).
Regards,
Kevin L
Have you looked at the .XML files associated with the plugin? Usually there is an XXX_info.xml file associated with an unsupported plug (for Atmosphere, the (early USB plugs), etc. there were instructions for creating these XML files to install unsupported). Anyway, you could try changing the Plugin ID within this XML file. Edit it, then refresh the plug-in cache (Hold 'Multi' button, and triple-click power, wait about 10minutes).
Regards,
Kevin L
-
- KVRAF
- 37439 posts since 14 Sep, 2002 from In teh net
How would that change the plugin ID? Isn't that coded into the dll itself? Changing an xml file is simply going to mean the xml file is no longer associated with that plugin's ID surely?
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
I don't know for sure what this will do with (for example) the plugin's association with it's preset files.
I have edited this to change the 'print' name that shows up for the plugin in the plugin list (for example, to change the default name of "Ultimate Sound Bank Charlie" to "Charlie").
I'm not sure what the original intent Prizzle wanted however (eg. disassociate plug from patches, rename on instrument list, something else?).
Regards,
Kevin L
I have edited this to change the 'print' name that shows up for the plugin in the plugin list (for example, to change the default name of "Ultimate Sound Bank Charlie" to "Charlie").
I'm not sure what the original intent Prizzle wanted however (eg. disassociate plug from patches, rename on instrument list, something else?).
Regards,
Kevin L
-
- KVRAF
- 37439 posts since 14 Sep, 2002 from In teh net
I see. I think by "plugin ID" he is referring to the numerical code that each VST plugin has that identifies it to the host. This is built into the VST. I don't think he means the name or identifiers like that (at least that is what a "plugin ID" is).
That being said not all hosts seem to go by the ID alone.
That being said not all hosts seem to go by the ID alone.
-
- KVRAF
- 37439 posts since 14 Sep, 2002 from In teh net
I don't have receptor but this is a problem in some other hosts too - if they solely rely on the plugin ID to tell them apart sometimes plugins have the same Id and that confuses the host.
In a couple of cases I've managed to get the dev to recompile the dll - afaik that's really the only real solution. However a workaround I've had to use in situations where that wasn't an option is to use a VST wrapper which will not change the actual Id but will overlay it with it's own which is usually enough to fool the host. I've used Wusik VM a few times to do this and also the demo of FX Freeze works pretty well (the demo is free and although it loses it's freezing abilities after 30 days it still functions as a wrapper indefinitely and will allow you to load and save patches). Not sure if wither of these would work in Receptor though.
In a couple of cases I've managed to get the dev to recompile the dll - afaik that's really the only real solution. However a workaround I've had to use in situations where that wasn't an option is to use a VST wrapper which will not change the actual Id but will overlay it with it's own which is usually enough to fool the host. I've used Wusik VM a few times to do this and also the demo of FX Freeze works pretty well (the demo is free and although it loses it's freezing abilities after 30 days it still functions as a wrapper indefinitely and will allow you to load and save patches). Not sure if wither of these would work in Receptor though.
-
- Mr KVR
- 1580 posts since 23 Oct, 2000 from UK
- KVR Audio
No.aMUSEd wrote:How would that change the plugin ID? Isn't that coded into the dll itself? Changing an xml file is simply going to mean the xml file is no longer associated with that plugin's ID surely?
Receptor requires every plug-in to have a Unique ID but some plug-ins use the same ID for different versions, such as an instrument and an effect version (e.g.B4 and B4 FX).
Editing the XML file overrides the id for that plug-in so Receptor can use both plug-ins at the same time.