This is about 2 things that I love that I'd like to see getting along better (sounds like I'm about to have a talk with a buddy about their marriage).
This evening I popped open the UI on an instance of (v. 14.13) MCompressor in my DAW to see if I could set up a custom shape in it to mimic a VCA-type compressor curve.
I checked the box for "custom shape" and the display didn't change to indicate the presence of points or handles, so I tried double-clicking on it to see if I could add some. Couldn't.
Further curious, I noticed that while I could drag and move the Threshold line back and forth, which also updated the Threshold knob, the knee didn't move with it. The Ratio control and Knee controls, while moveable, had no effect on the display.
This persisted in other programs and I finally checked it on my other computer.
I spent a good bit of time trying to figure out what had gone wrong before it dawned on me that I had enabled my favorite new feature, intelligent disable. I wasn't passing audio through the plug-in, so it promptly did its job and disabled itself.
I realize that this behavior is common to simply having the "Bypass" button engaged, it's not specific to having the plug-in disabled "intelligently." But having noticed it, it seems a bit odd. Why can I freely adjust all the knobs but am only seeing visual feedback in the graphical display for the Threshold line? I do like being able to adjust controls with a plug-in bypassed, I don't always want to change settings with them switched in.
My guess is that updating that display might be tied to another function that is too "expensive" in terms of CPU usage to leave on in the bypassed state, but I'll leave it at that and ask: is all of this "expected behavior?" It's not documented as such.
FR: If so, I would like to have the option to "wake" a plug-in by clicking in its UI, like waking a computer from sleep. Aside from that I must remember, and I will warn others: if you find some functions aren't working when the transport is stopped, check to see if you've enabled "intelligent disable."
MCompressor's "intelligent disable" could maybe be more intelligent
-
Starship Krupa Starship Krupa https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=337746
- KVRist
- 303 posts since 13 Sep, 2014
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Yes! Already done for the next update 
. See, this needs to be done plugin by plugin and a few had these issues.
. See, this needs to be done plugin by plugin and a few had these issues.
-
- KVRist
- 308 posts since 11 Jul, 2016
What about a global by-pass type function for the Intelligent Disable - similar to the "Bypass All" button on MAutoAlign? You simply "bypass all" by clicking the Intelligent Disable icon in any plugin which turns it off. Then you can turn it back on for every plugin by clicking it again?
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
I'm afraid I quite don't follow.mibby wrote: Sat Dec 05, 2020 4:52 pm What about a global by-pass type function for the Intelligent Disable - similar to the "Bypass All" button on MAutoAlign? You simply "bypass all" by clicking the Intelligent Disable icon in any plugin which turns it off. Then you can turn it back on for every plugin by clicking it again?
-
- KVRist
- 308 posts since 11 Jul, 2016
Sorry, that wasn't clear. What if the "On/Off" indicator on the upper right of the plugin window was a button that toggles the "Intelligent disable on silence" just like the button in the Settings window? i.e. If the plugin is pulled up without audio running and the indicator is Off (first pic), the user simply clicks the Off button to turn it On and enable the UI? (second pic)
1. Plugin disabled, no audio
2. Toggled setting to enable plugin
Actually, what makes more sense is if the plugins simply enable their UIs if they have focus regardless of whether or not audio is running through them or how the "Intelligent disable on silence" is set. No toggling the setting and no user intervention needed...
PS. FWIW, this plugin, MAutoStereoFix seems to work fine.
1. Plugin disabled, no audio
2. Toggled setting to enable plugin
Actually, what makes more sense is if the plugins simply enable their UIs if they have focus regardless of whether or not audio is running through them or how the "Intelligent disable on silence" is set. No toggling the setting and no user intervention needed...
PS. FWIW, this plugin, MAutoStereoFix seems to work fine.
You do not have the required permissions to view the files attached to this post.
-
Starship Krupa Starship Krupa https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=337746
- KVRist
- Topic Starter
- 303 posts since 13 Sep, 2014
I like both of these ideas. Once I realized that my issue was that intelligent disable was turned on, I tried clicking on the On/Off indicator to see if that would do anything.
My expectation of what would happen if I clicked on it is that it would toggle the setting that is now only accessible in the Settings panel.
I also like the idea of a setting for "always enable plug-in when it has focus."
My expectation of what would happen if I clicked on it is that it would toggle the setting that is now only accessible in the Settings panel.
I also like the idea of a setting for "always enable plug-in when it has focus."
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
The problem is, that disabling this feature also hides the indicator. So you'd have no way to bring it back on 
. Anyways the problems should be all fixed in 14.14!
. Anyways the problems should be all fixed in 14.14!