Notifications
Clear all

Extract preset/FX info as text to add to description

4 Posts
2 Users
0 Reactions
1,100 Views
(@soundofbcm)
Eminent Member
Joined: 4 years ago
Posts: 11
Topic starter  

Hey, I asked John already, he did mention that it may be difficult to implement but I guess one for the future and if others are interested in this.

So the idea being, if I load a number of VST's to create a new patch, various presets/modify them etc, is it possible to extract all that information - what plugins were used, and what bank/presets were selected - and put it in the comments section of a patch?

Sometimes we upgrade VST's or delete them, this way, if we need to re-create a patch due to a missing plugin, or a preset, we can do so based on the extracted notes by restoring what is necessary. 
When a Unify patch is saved, all that information is saved as part of the preset, so not sure how difficult it would be to extract that information as text. 


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4432
 

The information you're looking for is in the patch database. In the Unify Settings view, you can click the "View Database" button to see the entire database as a table, and click on any column heading to sort on that column. The "instPlugin", "midiPlugins", and "audioPlugins" columns list the plug-in used in the patch.

If you attempt to load a patch when a required plug-in is missing, you'll get an error message indicating what was missing, and then the entire patch will load, but with the names of any missing plug-ins shown in red.

What situations are not already covered by these features?


   
ReplyQuote
(@soundofbcm)
Eminent Member
Joined: 4 years ago
Posts: 11
Topic starter  

The information in the database is limited, just the plugin used and version it seems, but what if you used a preset from a particular preset bank, and if that bank goes missing for whatever reason, then the patch will fail won't it? 

 

The way I've been adding notes when I am nearly done with a track is by adding something like the below to each instrument layer in Cubase:

Spire > BellatrixAudio > Horizon > PD Origin

So it's Instrument > Creator > Bank > Preset

 

I appreciate some of the instruments may behave differently with their preset management, but underneath it, should be the same, you'd know better. 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4432
 

Very few plug-ins provide any useful information to the host about their presets.

In any case it's not necessary, because Unify (like any DAW) saves the entire state of each plug-in. If this happens to include the name of some preset (whether you modified it or not), this will be restored along with all the other data when you re-load the Unify patch.

The state data is provided by the plug-in itself. Some plug-ins provide entirely self-contained state data, others don't. For example, a sampler like Kontakt would provide the settings of all its knobs, but only a reference to the current sample set. Obviously, attempting to restore the state of Kontakt would fail if the reference were invalid, e.g. if the sample set had been moved or didn't exist on the computer, but HOSTS HAVE NO WAY OF KNOWING THIS or doing anything about it. Unify is no different from any other DAW/host in this regard.


   
ReplyQuote
Share: