Plugin Compatibility Fixes (DeviceCompatibility.xml)
Forte tries to make a good decision about how to get and set VST configuration (chunks or FXB/FXP data). However, sometimes a plugin wants something different to get or set its entire state. Forte has a way to override scene capture and recall behavior for individual plugins. A file called "DeviceCompatibility.xml" in the install directory contains plugin-specific settings which can override the default behavior. Plugins are referenced in this file by either CLSID or VST ID. If your favorite plugin does not correctly restore its settings on scene change, add it to this file. Note that this MUST be a valid XML file in order for the feature to work.
An typical example entry would be:
This instructs Forte how to save scenes, not restore them, so you must restart Forte, reload your rack, and recapture your scenes.
The entry is defined by the Device tag. Plugins can be identified in several ways:
|•||Name="<partial case-insensitive plugin name>" - affects any plugin that matches the plugin name|
|•||Name="<partial case-insensitive plugin vendor name>" - affects any plugin by a vendor|
|•||CLSID="<a big string of letters and numbers>" - affects a specific plugin. A CLSID is how Forte unambiguously identifies a plugin. This value matches the value Forte uses to identify the plugin in its plugin cache file (plugins.xml).|
The flags that be used within a Device element include:
|•||saveFXB - if 1, save an FXB chunk with a scene|
|•||saveFXP - if 1, save an FXP chunk with a scene|
|•||saveProgramNumber - if 1, save the VST program number with a scene|
|•||saveParams - if 1 save the VST parameters with a scene (typically only effects would use this option)|
|•||isVSTi - if 1 forces a plugin to be identified as an instrument plugins. This is useful for example with Guitar Rig which is an effect plugin, not an instrument, but since you would typically want it to have its own module and be fed by audio input, you can force it to be treated as an instrument.|