Please implement in the next Dune release, the label differences between the original state of the preset and its altered state (as is usually done - is marked by a sign "*" on lcd panel, next to the name preset in the upper right corner).
Or - provides a simple command Recall (Reload) the preset. Quite uncomfortable every time reload the entire plug-in to see again the original state of the preset.
I apologize for my English. (I use translator)
Anatolyj
DUNE: About convenience when editing a preset.Moderators: Christophe, Mark
13 posts
• Page 1 of 1
Re: DUNE: About convenience when editing a preset.change presets
Windows 11 Home - 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz -32GB RAM
250GB SSD - 1TB HDD | M-Audio Oxygen 25 V
Re: DUNE: About convenience when editing a preset.It's true. I even get the same behaviour with Microsoft Word. If I close the program without saving any changes, it opens up the original document without the changes that I made. Sooooo annoying.
Re: DUNE: About convenience when editing a preset.Huh? Maybe I'm misunderstanding but I think he wants an indication that a preset has been edited? Some synths will give a * symbol in the name area when a patch has been changed..........
Re: DUNE: About convenience when editing a preset.
Do I detect the ever so slightest tinge of sarcasm ?
Re: DUNE: About convenience when editing a preset.
Yes, he wants that and/or the possibility to reload the original state of an edited preset (kind of Undo), without the reloading of the plugin or bank. These may be handy things, though I don't find them in most of the other products either, but certainly they could add more comfort to preset editing/usage.
Re: DUNE: About convenience when editing a preset.
Moi? Sarcasme? Mais non, mon ami!
Re: DUNE: About convenience when editing a preset.
Sorry - forgot to mention about changing preset. If I edited the original preset (in Dune) a change in some other preset, and return back to the discussion preset, does not return to its "original" state. How can help change the preset? (Perhaps this is a mistake DAW? and preset must be returned in original condition with this situation? Correct if wrong.)
Sorry, did not understand the analogy.
It is quite true. In general - if when you change presets, it is not initialized (and it's not a bug), then I do not understand why my wish seems strange.
Re: DUNE: About convenience when editing a preset.If I understand your wish correctly I do not think it's strange at all and in fact I think it's a good idea to have the * when a patch has been changed.
I see what you are saying....I think....Say you start DUNE with the Alpha Glider patch and change for example it's cutoff amount. Then you go to the next patch which is Amnesia 89 then go back to Alpha Glider the changes are still there. The patch is still in it's edited state. If I understand you correctly you want the patch to return to it's normal state not it's edited state when you come back to it? Having the * would let you know the patch has been edited and is not in it's original form........Is this correct?
Re: DUNE: About convenience when editing a preset.
Nooooo not you........ Anyway if I understand correctly exactly the opposite is happening. Say you edit a Word document but don't save the changes. Yet the next time you open it the changes are still there.....I believe this is what is happening with DUNE and the reason for the OP's posts...... So something like this when a patch is edited (* taken from the Korg Wavestation which does exactly this)
Re: DUNE: About convenience when editing a preset.Ah, I understood that he wanted any changes he'd made to remain when he opened a new instance and that wasn't happening. I don't understand why one would want that. If you make any changes that you want to keep then save them. If he means that he'd like a marker (like your asterisk) to say that a patch has changed then I'd be all for that.
Re: DUNE: About convenience when editing a preset.
Perhaps that is indeed what he is asking but I'm reading it differently. Yes of course any edits could not possibly be remembered when opening a new instance of Dune....... I'm kind of on the fence about the way Dune currently handles patch edits. Some synths forget any edits to a patch after another patch has been selected if no save was done. Dune remembers the edit until a new bank or new instance is loaded. I can see advantages to both methods. I do agree that since Dune does remember it's edits even when changing patches the * would be a good addition.
Re: DUNE: About convenience when editing a preset.
It's true. Clarify just in case, to avoid confusion: 1) When editing the original preset, there is a "*" (you're absolutely right of the images ) 2) When you switch to editing the preset (which has the symbol "*") to the next preset, and a return to the edited preset, it must be the original state (and hence the "*" is missing) Note: Why (For What) keep the changes in the preset, even after we moved to the next preset? If we want to not lose the result of editing, we simply save the current state of a preset command "Save Preset"! and 3) In order to be able to return to the original state a preset, and it was convenient, need (as I mentioned earlier) a special funktion (such as Reload preset) That's it. This is a classic version of the action, friends, agree? To Mark I'm sorry Mark, maybe I do not understand what you're getting at. ) The analogy with the work of any kind of documents is simple: If we changed the original state of the file, then when you close it, he asks us - "Do we want to save changes?" If we refuse, then the next time we see the original state of the document. What I suggest, in no way contradicts the classical principle of editing.
13 posts
• Page 1 of 1
Return to Plugin Support (VST/AU) Who is onlineUsers browsing this forum: No registered users and 455 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |