Saving favorites presets within ~/Lib/Support/uhe == bad idea? / improving db

[Hanz Meyzer]

I would like to suggest to save anything related to presets within the u-he user preset dir and not into ~/Library/Application Support/U-He/product/blabla, for the following reasons:

- Less cluttered data, easier to be copied
- Easier to be synced and backuped
- All preset data is in place (same as 1 )

If you like the idea, why not then change the favorites save data into an human readable format, so we could rename the favorites names for example?

EDIT: Or rename the "Hive_Presets.presetsdb" to a proper, common sqlite database file-ending (i.e. "Hive_Presets.db"), so you could edit any value yourself (including setup values) with db browser for sqlite or similar.

Is the database lacking of a "tag" table completely? Where do these tag ids come from? You already seem to have a n-m-relation using "tagmap", but it only supports 1-n so far... A GUI problem? Or are these tags also the categories etc.?

I think a overhaul of those structures with keeping portability in mind would not hurt. For example, not using unique ids for preset-tag relations or so? This seems to be difficult, string ids are ugly. Sometimes a simple "json" field directly within the presets table might be more practical? At least postgresql directly supports json fields in queries now... sqlite 3.9 introduces the json1 extension: https://www.sqlite.org/json1.html

Thanks for consideration

[Hanz Meyzer]

Also if all presets are getting an unique int id while scanning, the files need to be EXACTLY the same on the computers which you want to sync... This might mess up then your favorites relations. So I would say, keep all the relations within a single table (using json "sub-tables" instead) would improve portability.

[Urs]

I can't answer any of these questions and I don't think that part of the team has made many appearances on KVR I'm afraid. I'll pass it on, but please don't expect a public answer.

[Urs]

Our devs are afraid that we'd have to start near the beginning explaining how things actually work and why decisions were made the way they were (some things work a lot differently than you assume here...).

We're happy to add your feature wishes, e.g. editable Favourite exports, to our list of feature requests and discuss them internally in time.

(I'm sorry if this sounds harsh, but we really can't discuss technical details like this in a public space)

[Urs]

(ah, Favourites export exists and is a JSON File...)

[Hanz Meyzer]

Oh! Nice, sorry then. That helps a lot already. Where do I find the favorites export? Or did you mean it's in the test version?

[Urs]

I think Z2, Bazille and Hive have it in current official versions and everything else in upcoming ones.

[tasmaniandevil]

Plugins with revision 9709 or higher already include export of favourites (it's mentioned in the release notes).

Just hold the Shift key while dragging the main favourites smart folder, or individual favourite folders, out of the plugin.
This creates a file in JSON format.
To import, simply drag it onto the favourite smart folders.

If you drag a favourite (or any other smart folder) out of the plugin without the Shift key, it will simply create a folder with copies of the presets.

[Howard]

I'm currently updating ALL user guides to include / better explain various improvements. More of a slog than I had expected!