Wish Add a Favorites menu

yek

yek

Contact Fractal for your Custom Title
Currently the only way to "bookmark" favorite presets is to assign a color in the Preset Picker and then filter by color. Too many steps for fast operation.

A Favorites menu in the main editor window would allow us to quickly jump to favorite presets.

There's sufficient space to add this to the main window, between Settings and Help.
 
yek said:
Currently the only way to "bookmark" favorite presets is to assign a color in the Preset Picker and then filter by color. Too many steps for fast operation.

A Favorites menu in the main editor window would allow us to quickly jump to favorite presets.

There's sufficient space to add this to the main window.
Click to expand...
+1
 
Admin M@ said:
Would FAVORITES be any preset with any color assigned to it?
Click to expand...
This’ll break down when people are using color coding to differentiate amp and cab models, like Fender vs. Marshall vs. Vox, or 1x12 vs 2x12, etc., which people have reported doing.

Of course, setting a flag to specify how they want to use the color coding, either grouping by types, or only as favorites….
 
Admin M@ said:
Would FAVORITES be any preset with any color assigned to it?
Click to expand...
Maybe, but that might not be the best solution... since like @Greg Ferguson said, people might want to flag other things (all Vox, for example) but not have all of them be favorites.

I'd prefer either another way to mark favorites - either something like an asterisk or the letter F that isn't a color - or at least be able to tell it "any preset marked <specific color> is a favorite." Then it would ignore the rest, and you could still have other colors for other groups like amps, cabs, high-gain/low-gain, etc.
 
Admin M@ said:
Maybe a 1-bit "FAVORITES" flag could be set in the preset file itself.
Click to expand...
That would work, but a simple asterisk in the name would accomplish the same thing and wouldn’t require programming.

Different punctuation characters would work as long as they don’t already exist in the factory presets.

And if we wanted multiple categories of favorites using punctuation characters, it’d result in some presets’ names looking like we’re swearing.
 
Greg Ferguson said:
That would work, but a simple asterisk in the name would accomplish the same thing and wouldn’t require programming.
Click to expand...

In both cases (bit or asterisk) preset creators would be able to manipulate the contents of the Favorites menu by adding the bit or asterisk to the distributed presets. Not desirable. Leave it to the users, just like bookmarks in browsers.
 
Last edited:
Greg Ferguson said:
That would work, but a simple asterisk in the name would accomplish the same thing and wouldn’t require programming.

Different punctuation characters would work as long as they don’t already exist in the factory presets.

And if we wanted multiple categories of favorites using punctuation characters, it’d result in some presets’ names looking like we’re swearing.
Click to expand...
Good lord no. The word kludge would be insulted if you used it to describe that idea :). It's not that difficult to implement proper tags, favorites, and ratings.
 
yek said:
In both cases preset creators would be able to manipulate the contents of the Favorites menu by adding the bit or asterisk to the distributed preset. Not desirable.
Click to expand...
I see the potential for third-party preset developers doing that to monkey with the list, which would be an annoyance. It’d be easy to clear/fix but still, we shouldn’t have to.

It needs to be something that can only be set by the owner and can’t be transferred to other machines, but needs to accommodate those of us who have multiple devices and share our own presets among them.
 
  • Like
Reactions: yek
GlennO said:
Good lord no. The word kludge would be insulted if you used it to describe that idea :). It's not that difficult to implement proper tags, favorites, and ratings.
Click to expand...
Of course it’s a kludge and the logical conclusion is the third sentence. It’s humor.

A sidecar file using SQLite, or maybe YAML, generated by the editor would allow persistence but then they’d have to program that capability in. There’s probably already an open source library or code-base out there somewhere.
 
Last edited:
Greg Ferguson said:
I see the potential for third-party preset developers doing that to monkey with the list, which would be an annoyance. It’d be easy to clear/fix but still, we shouldn’t have to.

It needs to be something that can only be set by the owner and can’t be transferred to other machines, but needs to accommodate those of us who have multiple devices and share our own presets among them.
Click to expand...
Something involving a hash table file on the OS that the various *Edit proggies could be configured to share (or not), perhaps even with a radio button list of three choices for easy switching between favorites hash tables for each type of device once they are located in the FS?
 
If only the editor had hooks so we could extend certain capabilities with a scripting language. Don’t let it have access to the raw .syx data, but maybe metadata about the presets, their contents and parameter settings and order, grid positions, enabled state, presets and cabs in the libraries….
 
You must log in or register to reply here.
Back
Top Bottom