An interesting thread indeed, for many reasons.
We are like veering towards a philosophic discussion, but this is somehow misleading.
Let's try and establish some outcomes:
- Many users find this feature useful;
- Most users have no idea about how complex implementing it would be;
- Apparently, it would be more complex than most users think;
- Apparently, most resistances by Devs to implement the feature are related to how "expensive" it would be Vs. their perceived convenience.
OTOH, I believe things should be made clearer and simpler.
This is a features request thread. While it's great that Devs investigate in order to understand userbase's needs and approaches to the KPA, and suggest alternative options, the discussion just ceases to make sense beyond a certain threshold: it's up to Devs to determine whether the requested feature is worth being implemented or not (both in terms of costs and KAOS' appeal increase/saleability). Trying any harder to convince the users that the request makes no sense above a point starts to sound weird.
Opinions can be discusses up to a point, beyond which it is not constructive/useful any longer. Thinking for example of the inversion of the Up/Down switches on the Remote, that has been requested (or has at least raised perplexities on several forums on the Net) by literally hundreds (if not thousands) of users in the years: it is clear that, after a while, discussing about the reasons why it's this way and not the other makes no sense: I just know that every time I use those switches my brain has to devote a thread to the operation itself, b/c I have to recall the notion that it's the other way round that my spontaneous approach.
I won't certainly dismiss the Remote just because of this, even tho it doesn't work in a way that makes sense to me
Not sure what are you referring to, but the BROWSE knob will show recently loaded preset, which this request is about. Could you explain more "what it never shows"?
Browse is useful to check the last used preset only. If you load a certain preset in rig A and then another preset in rig B, the information about what preset was used for Rig A will not be shown by the Browse knob.
Hope this clarifies
I still don't understand what the reference to the original preset would help you with.
As I have written in the thread I linked, it is a reference point specially for those effect where
- lots of parameters are available;
- the sonic result may vastly vary depending on parameters' values;
- there's (this is a real issue for me at least) no way to tell it from the way it sounds;
- it' not trivial to tweak by ear in order to try and match a sound.
User may want to use similiar effect in different RIG. Of course he can use LOCK function or copy/paste function.
Yep, Copy is always available. OTOH, it's of no use when for example
- you want to restart from scratch with tweaking a preset you have worked on hours/days ago (so Undo would not be available) because you liked its original sound but you feel you're not going in the right direction;
- You want to have the original preset as a reference point and want all your sounds to move around a certain family of sounds, i.e. to be variations of the same "mother".
I have a band where I use rigs with 2-3 delays and 1-2 revs, and while each rig sounds different I am trying to keep a certain sound consistency, and feel that referring to a same preset is part of that.
For a new song, I'd like to know what I've used in other rigs, so that I can start from the same basic sound every time.
Hope this makes sense
Parameters could be modified to an extent, that this statement "based on preset A" is meaningless or even misleading.
True.
We have already discussed this in the other thread tho: it doesn't seem an outcome that would render the option useless (see above).
You can delete presets, you will be able to modify and replace presets or rename presets in OS 7.0. Rigs can be shared without "their" presets. So, this message "based on presets A" could lead into the woods
Right. it might not, tho. If a specific preset is not on the device the feature would be less immediately useful, but I could nevertheless be able to retrieve it from a backup or from a colleague, if I knew what to search for.
Hope this makes sense.
the comment field comes to mind, you can easily fill this info in using Rig Manager
True.
With 3 delays and 2 revs for each rig this is quite a demanding and long task tho. And, things would need to be edited every time the user changes their mind about what to use.
Hope this makes sense.