I often use predefined mu.lab modules (synths, effects), and sometimes I change some controls of a module. After several weeks I neither do know if I have made changes to a module nor what changes I have made.
Does mu.lab help me in this case, except from manually compare the settings in two different slots?
A colour change of the module name would help at least, or a textual list function of all settings incl. changes.
Nice weekend.
Changes in settings of modules
-
- KVRist
- 409 posts since 26 Jul, 2010 from Germany
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
There is no such function. Not yet planned either. I do understand your request though. When making music i sometimes also would like to have an object comparer so i can know if sequence A and B are equal etc.
I wonder: are there any vst plugins that have such function?
I mean: if you edit a preset and you save the host project, then you open it lateron and you look at the vst gui, that you still can see it has been changed compared to the original preset. And what if you overwrite that preset in another project? Does everything stay in sync then??
An object comparer is not that simple: Even for comparing texts (text diff app), such app has to take a lot into account.
I think it's not a simple thing.
I wonder: are there any vst plugins that have such function?
I mean: if you edit a preset and you save the host project, then you open it lateron and you look at the vst gui, that you still can see it has been changed compared to the original preset. And what if you overwrite that preset in another project? Does everything stay in sync then??
An object comparer is not that simple: Even for comparing texts (text diff app), such app has to take a lot into account.
I think it's not a simple thing.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
It's easy enough to say "the user changed this preset". What's hard is to say "and then changed it back so it's exactly the same". I don't know any normal app that does it - only version control software (i.e. when it does a compare on files and see if there's any change to commit).
But it really would be handy to know if a patch really was untouched, so I could say "just load up the preset called...".
An alternative might be the ability to get all the parameters displayed (and copyable?) numerically (then you could do your own compare with the original values).
But it really would be handy to know if a patch really was untouched, so I could say "just load up the preset called...".
An alternative might be the ability to get all the parameters displayed (and copyable?) numerically (then you could do your own compare with the original values).
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Note that there are plugins that not only rely on float parameters.
Sometimes there also is audio data, complex envelopes, ...
Also: Imagine (vst) plug X loads preset A from disk.
User does not change the loaded preset, and saves it with the host project Y.
Sometime later preset A is changed on disk.
Sometime later user loads host project Y.
Now should the plugin gui say the preset A has changed or not?
Preset A will be different. But it was equal when saved with the host project.
That's an ambiguous situation i think.
Sometimes there also is audio data, complex envelopes, ...
Also: Imagine (vst) plug X loads preset A from disk.
User does not change the loaded preset, and saves it with the host project Y.
Sometime later preset A is changed on disk.
Sometime later user loads host project Y.
Now should the plugin gui say the preset A has changed or not?
Preset A will be different. But it was equal when saved with the host project.
That's an ambiguous situation i think.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Totally agreed - you can only ever make a "best estimate" of change. But a record that the UI in "this project" was used to change a loaded preset would still be better than nothing, I think. (It's not "this project"'s job to know what happens in the wider world, after all.) It's far from important for me, though.mutools wrote:That's an ambiguous situation i think.
Go worry about something else 
-
- KVRist
- Topic Starter
- 409 posts since 26 Jul, 2010 from Germany
Interesting discussion. Thank you. I see a bit of the complexity. What I - at least - would like to know:
I mean, my wish is simple, (possibly) not the solution.
Any idea?
But can I be sure to hear everything? With any velocity, any key, ...
- Will the reload of a preset have any effect?
I mean, my wish is simple, (possibly) not the solution.
Any idea?
What??? Ah, yes, sometimes. Hearing gets difficult at my advanced age> DiGiT < wrote:can you hear changes?
But can I be sure to hear everything? With any velocity, any key, ...
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
At the moment i don't find an answer for your request.
Even when you would save the current patch as a temp file and binary compare it towards the original patch file could give differences while the patches are the same because they may be saved with different versions of MuLab.
I'll keep the topic in mind. I have encountered also other situations where compare functions would be handy. And/or more textual file formats so you can use text compare apps to zoom in on the differences. But it's all still on brainstorming level, no concrete plans yet.
Even when you would save the current patch as a temp file and binary compare it towards the original patch file could give differences while the patches are the same because they may be saved with different versions of MuLab.
I'll keep the topic in mind. I have encountered also other situations where compare functions would be handy. And/or more textual file formats so you can use text compare apps to zoom in on the differences. But it's all still on brainstorming level, no concrete plans yet.