search

christofmuc / KnobKraft-orm

The KnobKraft Orm - The free modern cross-platform MIDI Sysex Librarian
GNU Affero General Public License v3.0
196 stars 25 forks source link

OB-6 patches come with surprising names when they were started from a factory patch #20

Open christofmuc opened 3 years ago

christofmuc commented 3 years ago

This is not really a bug, but a workflow issue - if you create a new patch based on any other patch in the OB-6, and import it into the computer, it will still have the original name. Because the OB-6 has no display for it, and no way to rename it, that can be quite suprising.

What should I do? If there is already a patch with that name, offer to rename? Offer to call it "BasicProgram"? That's the name you get when you start with an init patch on the OB-6.

christofmuc commented 3 years ago

I could build a rename function - if a new patch comes in, but the name is already used, I could generate a new unique name (e.g. appending a number). That would at least show the original patch as it does not contain any postfix?

christofmuc commented 3 years ago

I could allow the user to define his or her short sign to automatically append, marking patches as their own?

markusschloesser commented 3 years ago

I suggest v1, v2, cos short, or for synths that are numerical only .1 .2
Normally I'd like date as well, but that should probably be in meta data

christofmuc commented 3 years ago

Or a settable short sign, like "Hot Factory Patch CR.1" to indicate I changed it and this is the first iteration. Then when you modify and redo get edit buffer you'll get .2 .3 .4...

Short sign I meant like your initials, so you can find the patches you made easier as well.

markusschloesser commented 3 years ago

Settable is a great idea! 😊 But then kk needs to know what a synths is capable of w re to patch names

christofmuc commented 3 years ago

Settable is a great idea! 😊 But then kk needs to know what a synths is capable of w re to patch names

True, or we need to distinguish between database name and patch-internal name. Keeping those in sync currently also does not really work, and ideally patches are identified via fingerprint and not via name, so we could do automatic synth-patch renaming like back in the Windows 8.3 filename days, like automatic shorten. That truly depends on which UI you use most. For the OB-6, it is really hilarious in that you can embed a 20 character name of a patch in the data, but the OB has only the LED 7-segment display :)