mirror of
https://github.com/airwindows/airwindows.git
synced 2026-05-15 06:05:55 -06:00
[GH-ISSUE #68] ConsoleX2 (and maybe ConsoleH)'s double-click default value feature #56
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/airwindows#56
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aldoscz on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/airwindows/airwindows/issues/68
Hi, Chris.
As I stated directly on AW, I've been asking for a request:
Could you please add the feature of restoring the default value (with double-click) of the knobs and faders in the GUI version (just like the feature in Consolidated)? It’s annoying having to access the DAW’s sliders —Live, in my case— to restore a default setting; makes me lose some vibe when tweaking parameters.
Also, could you add as well the feature of opening up a numerical editor (I don’t know, maybe with right-click)? In case, say, we want to add a specific value to the knob/slider.
Thank you so much. 🙌🏼
@airwindows commented on GitHub (Apr 25, 2026):
In this case (in this repo) I literally can't :) this repo is the generic-interface, DSP-only form of the plugins, not the ones you're talking about. There's no capacity for doing that within the plugin. You mention GUI-enabled Console versions but these are the generic, DSP-only versions of those. Regarding those repos (which are built on Pamplejuce), that's where I have more control over those behaviors, and for instance I've got knob behavior (like angular/realistic, or vertical) assignable via AirwindowsGlobals.txt. My question would be, how about a 'reset ENTIRE PLUGIN to defaults by clicking on this' button? It'd need to be very tiny to not be accidentally clicked, or some other sort of thing, but that'd be something if I added, I could manage an update where no other behavior was altered and no saved settings got altered. Remember, when I add new behavior it's a new plugin with a new version number, not altering something that's out there. The reason having a tiny reset widget somewhere is more thinkable is, it could be a visible new thing that only does that added thing and could be part of the overall window render.
There is no conversion of knob positions to any numerical value, and that's on purpose: it's deeply damaging to mixing the way I see it. Anywhere I can see the numbers I wish I couldn't: there's never a correlation between any recognizable number and the correct target for any control. Arguably an improvement over the state of affairs is to hardwire slightly randomized offsets to all the settings so that you cannot even reset the plugin to 'flat' and would have to set all the knobs faintly off to find 'flat' by ear. But that would sabotage something else I do, which is bypass sections of the processing if they're set flat…
I'm sorry I can't help you further. In the generic versions I find that some DAWs have a 'reset to default' option even though the direct interface doesn't (Reaper looks like it does but it's just setting controls to 0.5), and I'll try to remember to explore the 'reset button' idea for GUI Console, because I do find 'total reset' to be useful on plugins and use that option in the DAW (for instance, TwistedWave, the two-track editor I use a lot). Reaper can do this for the GUI versions from a popup menu normally used for presets. I don't know what Live does in that scenario. It's really the 'no numbers' aspect that's truly a no-go regarding Console. There would have been numbers on them all along if that was a thing: JUCE is able to do it, the GUI is specifically designed around not having numbers.
@aldoscz commented on GitHub (Apr 28, 2026):
Hi, Chris.
Thank you for replying and for that careful and lovely explanation.
Oh, no, no, I think I explained it wrongly —and I apologize for doing so—, because I don't pretend by any means to reset the whole parameters of the Console as whole, but JUST a knob or fader individually.
What I'm kindly asking is the simple idea of restoring the default value of a parameter when double-clicking it.
For example: on the —GUI version— plugin, you want to restore the Pan fader —that's, let's say, at 1 (or full towards the Right)— again to the C —or "Centered"/0.5— value, or a knob; ergo, its default parameter. To be able to just double-click the fader/knob and turning it back to default —like, in most DAWs, when you double-click a modified parameter and it turns back to its default value— (kindly see images attached).
I anyway thank you for considering a[n] —"unexpected"?— feature that could be implemented in future Consoles/devices (the whole 'reset' button). What I'm asking, though, is just an even simpler feature that all modern devices/plugins/GUIs currently have.
Please, let me know whether —this time— I was clear enough.
Thanks again!