It would be nice to save that particular project's preset files for how I've altered each of those multi's while they're frozen without having to wait sometimes upwards of minutes for plugins to respond and call up their window to save the presets and then bounce again (which could take up to an hour or more on some of these sessions I've worked on). The beautiful part about Project Bones export was that it takes a preset snapshot and saves out these files with appropriate naming conventions and sub-folders for the tracks and groups they're attached to even when the asset is frozen.Ĭurrently, If I'm busy iterating a project with a large VSTi Loadout (20+ instances of kontakt in my most recent strings portion alone) I may have tweaked my multi's a bit. I'm aware that many plugins have different ways of saving preset files internally to themselves - Waves saves to an XPS format but can also save and load settings to recall from within Sonar's container with FXP (vst2) etc. I know the Mix Scenes recall offers some of this functionality but only within the opened session and then it's also a global state save that can affect many things (depending on how much you've tweaked between snapshots).Ĭonsider it a redundancy feature, a backup option for creating local preset files saved next to your project externally so in the event for whatever reason a session cannot be opened or a plugin can no longer recall when being activated within that session (I've had instances where the VST3 version trying to replace a VST2 version of the same plugin stalls out or crashes because they don't yet support the preset translation). I find it more useful to have settings I've dialed in during previous projects saved out and instantly recallable than to have to manually go back later to completed sessions and deconstruct and save out FX Chains, Presets, and track templates.īeing able to get entire session state snapshots as individual preset files to only load up what you want later can save a TON of time. At this point, it's really more of a backup and redundancy process than for anything that could be considered a librarian service (unless this is also able to capture ProChannel.
Reaktor also allows for saving local versions of ensembles, and I save native presets and FXP/FXB's out locally too just to have redundancy in place.
I already do this myself to save local copies / backup presets. The settings folder I manually create folders based on tracks and busses, and number them according to the track and bus # (may end up renaming on occasion as sessions grow and get moved around, though it's rare). Then once the project is created, I manually create a Settings folder, and a video folder if I'm Importing video to build audio/music to. I already add a sub-folder called Resources to the project structure when creating new projects. I imagine it would have to be after a project has been created the standard way - when saving the project to a folder and including it's own sub-folder for audio data (per project).
0 kommentar(er)
