Preset Browser Tagging System with Custom UI
Casey Kolb last edited by Casey Kolb
I'm trying to work out how to get a custom UI for the preset browser tagging system without using LAF. I think I'd only need three new API calls for getting and setting the current preset tags, and saving tags to the current preset, but I'm struggling to get those working in the Scripting API.
Does anyone have any ideas for how to achieve this? It looks like all of the functionality is already there in the preset browser files like
TagList::toggleTag, but I want some custom UI stuff for the tags so I can more prominently feature them. Also, trying to work out a way to have the tags filter the presets per folder selected, rather than globally. Any help would be much appreciated!
ustk last edited by ustk
@Lunacy-Audio I’m just wondering if it is not possible to just systematically list all available presets in a file as object and associate a list of tags? The file system should allow this I imagine. The only down side is that tags are not embedded in individual presets, so importing/exporting presets is done with no tags. But if you don’t need this it should be doable...
EDIT: of course you’d need your own preset browser if you adopt this solution...
@ustk The only issue is that you'd have to scrap the rest of the preset browser functionality, like the favoriting and searching features.
@Lunacy-Audio If there were a way to change and update tags through the Scripting API, you'd be able to keep all the other awesome preset browser stuff, but have a custom GUI. Just trying to gauge how difficult it is to weave those into the API. Doing some digging right now.
Lindon last edited by
@ustk - exactly the system I built - so yep. possible
I figured out how to hook it up with the API system in order to get and set tags from presets, so all good!