Opened 5 years ago
#15296 assigned bug
Add support for saving and loading node configuration from media add-ons
| Reported by: | leavengood | Owned by: | leavengood |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Kits/Media Kit | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Right now some media add-ons (like the mixer) have code to save their own settings. But this should actually be handled by the Media Kit by calling GetConfigurationFor before an add-on is unloaded, and then reloading that before instantiating the add-on and its nodes later.
It appears that almost everything is in place for this except calling GetConfigurationFor, saving those settings to disk, and then reloading them later.
Obviously any current add-ons which save their settings themselves should be adjusted to just rely on this method.
It might also make sense to save these settings after seeing changes from BParameters, maybe with some sort of delay. That way the user will not lose settings if the media server crashes, or the computer crashes or otherwise turns off without a normal shutdown process.
