Quote:
Quote:
Quote:
I would rather want password for presets.
Do you really mean password protection (so someone with the password could view all the settings) or do you mean that you want to be able to give someone a preset without letting them see or change the settings? (load an encoded preset and while it's loaded block saving or viewing/changing settings)? Or do you mean that you want to stop people from changing settings but not from viewing them?
If it's password protected, then not be able to change or view settings. However some settings should be possible to change, like Advanced clipper, MB range, EQ...
I want to start with the password protection as it is now (with some improvements); if that works password protected (or actually, I would prefer completely unreadable) presets would be the next step. So basically: You make a preset and export it to an unreadable format. If someone loads that preset, they can't see or edit the settings. But they can save them, which would then also need to be in an unreadable format. Because this is all a bit tricky let's start with this 'simpler' protection in this version, if that works flawless I can create the preset protection later. (Depending on how long it takes to finish 7.52 I might even add it in anyway... but not now).
There are some problems with this though, among others that if you use a VST plugin you could use the VST interface (which shows every parameters as a float value) to convert it back to a normal preset. So either I must make these presets unavailable in VST plugins, or circumvent using the VST interface, or I need to completely rewrite how VST parameters are saved (there are other methods which I don't currently support), but that would in turn make it impossible to automate things through the VST interface.
Beside this, without a proper encryption method, I can write a preset to a file such that it's hard to read by saving it in binary mode, but it's always possible to reverse engineer the storage format and to decode it. So if for example you want to sell presets I'm not sure if this protection would be enough.
Anyway, enough reasons to not 'rush' towards a solution but to take some time to think about what's needed.
Quote:
Coupling.. Yes i noticed that compressors reacts whenever limiter(s) kick in. I still think that's wrong. At some point i can see B1 compressor kick fast and back for 6dB wich is ofcourse not true.
Tried it to use to "calm" some bands when big range occures, seems it helps.
Well actually the compressors don't react - but the displayed value contains both compressor and limiter. And (and I'm not sure if this is good) if you use band coupling the limiter behavior is coupled also. Actually that IS probably good if there's not much band coupling to avoid sudden big effects in small frequency ranges. But if you use a strong coupling between bands it makes far less sense and might be wrong.
If that's indeed the case, that would mean that I actually need to redesign how the clippers work...