View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006319 | ardour | bugs | public | 2015-05-12 21:12 | 2015-05-12 21:12 |
| Reporter | linuxdsp | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 4.0 | ||||
| Summary | 0006319: VST plug-in presets not saved | ||||
| Description | Ardour does not save modified presets / program settings for linux VST plug-ins. Example: A plug-in might contain several factory presets, or "programs" in VST speak. These can be selected, and modified by the user. When the session is saved, for plug-ins which don't export these settings as 'Chunks', the host application should cycle through the available presets (silently), in order to interrogate the settings and save them with the session. The converse should happen when the session is loaded, such that the modified presets are automatically restored. If possible the last active preset / program number, should also form part of the plug-in state. Currently Ardour only saves the current plug-in parameters as part of the session and defaults to program zero. Modified presets / programs are not saved / restored unless the plug-in manages this itself via some external mechanism. | ||||
| Additional Information | VST3 specifically mandates that preset management be the responsibility of the host application, in order to ensure a consistent user experience. This would therefore be logical to assume for (linux) VST2.x too. e.g. it should be the host application's responsibility to manage persistence of plug-in settings / state. EnergyXT / Tracktion / Bitwig are a good reference on linux, Cubase (being a Steinberg application) is the best reference for intended / correct behaviour on other OS. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-05-12 21:12 | linuxdsp | New Issue |
