Thanks a lot about thinking into this! I thought about it, too! The first step I would take is the have ‘Presets’ or 'Sets". My use cases for Jaikoz can be categorized like this:
a) On my private file-server I store my own rips as FLAC, with full featured meta-data, album-covers in folders ordered in artist/album/track file-system hierarchy. All others (downloads) get corrected and maximum tagged, too. This is my reference source.
b) From there I may export to Smartphones, MP3 players in the family&friends. Here the needs are different case by case. Some MP3 players do not understand the one or other ID3 revision, have problems displaying album art of a certain raster format, etc.
Doing (a) is easy. I set the preferences and all is good. But a soon I want to share from my collection I need to change the prefs, sometimes just a little. The next time I want to do (a) I must reset them to the way they were before. That takes a lot of time. So, if I could save different preferences-presets, that would be a bliss.
Another feature going along with this would be an ‘Export’ function. Basically a ‘Copy & Save’ instead of ‘Save & Copy’. This way I do not need to copy all the files over to another folder manually, before changing them. It would be even cooler, if a user-task could be inserted here. Like a script, that recodes the stuff to MP3.
Last but not least I wish for a “Wizard” like interface.
page 1: Select the preset, the folder(s)/files to be added, a pre-process hook, a post-process hook (for scripts), and hit “Next”. It could be made so, that the presets also define the complete workflow, which would be presented at the beginning, so the user may change this or that temporarily. This would become especially interesting if one could defince ‘User Actions’ in between any step, meaning execution of a script with Jaikoz passing arguments to it.
page 2: We get the well known table, the info pane at the bottom, a special toggle button, that puts the original file data as read only, ghosted below is the changed track (within the table) or such. Here we ‘apply’ our workflow.
page 3: What to do now? Simply save and quit (session was inplace editing), select volume/path to exort to, save&move, transcode script, upload to cloud, etc.
Basically the problem with usability ATM is the sheer amount of preferences, that can be altered. Comparing the features of Jaikoz is like comparing the cockpit of a Jumbo-Jet to the one of a single propelled sports plane.