Plugin Settings
Last updated
Was this helpful?
Last updated
Was this helpful?
Usually, when you load a plugin in your DAW, it has a few seconds of time to load data in the background. When creating audio previews, the plugin is loaded and a MIDI note is immediately sent, which might not be enough time for the plugin to load data, resulting in an empty audio preview.
This setting controls how many cycles PresetMagician waits between loading the preset and sending the MIDI note event. The empty cycles are not included in the preview.
Note that high values affect the export speed negatively. Setting this to 0 uses the default value from the preset parser module. Unfortunately, some plugins require variable processing time after loading a preset, so you might need to experiment with the values if you encounter empty audio previews.
You can specify additional banks or presets in the FXB (Preset Bank) / FXP (Preset) format.
After either adding individual FXP or FXB files, you can specify a Target Bank Name in which the preset or bank will be represented. By default, FXP (individual presets) are stored in the "User Preset" bank. For FXB (Preset Banks), the filename or the FXB file will be used.
Because FXB files do not contain any information about how many presets are contained and are usually a full dump of all programs, you might end up with duplicates. You can configure which presets you wish to export with the "Range" field. You can either write a comma-separated list of preset numbers to export, or use a range.
For example, to export programs 100 to 300 and program 399, you would write 100-300,399. If you leave this field empty, PresetMagician uses all presets. It also tries to avoid duplicate presets, but this doesn't work with all plugins.
Some plugins display different program numbers in their GUI than the VST programs standard uses. For example, V-Station programs start with 100, where in reality it is VST program 0.
Not all plugins support FXB or FXP files. For example, V-Station loads only FXB files, where FXP files seem to be ignored.
The plugin ID is contained within the FXB/FXP file to ensure that the contained data matches the plugin. PresetMagician verifies this information and displays an error if the plugin ID doesn't match the plugin ID contained in the FXB/FXP file.
The NKS format allows for controller assignments which define which controls are visible in Maschine and Komplete Kontrol.
You can load the controller assignments from a template NKS file. After you have loaded the template NKS file, PresetMagician will display a (crude) representation of the controller assignments so you can verify that you loaded the correct one.
PresetMagician automatically detects duplicate plugins and only displays a single entry. Duplication can happen because you have multiple versions of the same plugin installed in different directories. PresetMagician uses the plugin ID to detect duplicates.
Select the plugin DLL you wish to use for retrieving presets and audio previews.
Plugin IDs should be unique. However, sometimes it happens that different plugin vendors use the same plugin ID, or use the same plugin ID for the instrument/effect variants of the same plugin. As such, PresetMagician can only use one plugin per plugin ID to generate the presets.
Because Maschine and Komplete Kontrol decide upon the plugin ID embedded in the NKS files to select which plugin to load, it is important that you don't use different plugins with the same plugin ID. If you encounter such a case, please report to your plugin vendor.
After you have configured all additional FXP/FXB files, make sure you click the button. PresetMagician loads your plugin, fills it with the information from the FXP/FXB files and retrieves the final preset(s) from the plugin.
Controller Assignments are currently plugin-specific and cannot be set for individual banks or presets. Because documentation is outdated very quickly, you might want to check the if such a feature has been added.
You can read more about the problem at the
