Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: "Last Tweaked" button in the edit menu #490

Open
TheDichotomist opened this issue Mar 19, 2014 · 9 comments
Open

Feature request: "Last Tweaked" button in the edit menu #490

TheDichotomist opened this issue Mar 19, 2014 · 9 comments

Comments

@TheDichotomist
Copy link

Ok so in other daw's you can move a knob and if the host recognizes it as an automatable control, you can go into a menu somewhere and find a "last tweaked parameter" button... from there it essentially brings up the list of options you see when you right click a normal control. This feature would come in so much handy for automating vst plugins! =D

@Sti2nd
Copy link
Contributor

Sti2nd commented Mar 19, 2014

Ehh, because you always forget what knob you tweaked seconds ago? Sorry, I don't understand this feature.

@TheDichotomist
Copy link
Author

Why has everyone here never designed sound in a professional daw before T_T... here look at this synth

capture

have you ever browsed through the vst automatable parameters window for a synth like that?
it can get really confusing...

capture

See why i want this now? =)

@diizy
Copy link
Contributor

diizy commented Mar 19, 2014

Well, VST's are sort of self-contained black boxes, that handle their
GUI rendering by themselves. LMMS is in no way aware of the VST's GUI,
and can only communicate with the VST via the VST protocol. So I'm not
sure if it's even possible for us to know what controls have been "last
tweaked" in the GUI.

We could do some kind of workaround - since the plugin controls window
has a button to "refresh" the knobs, we could possibly in some way flag
the knobs that change when the user presses the "refresh button". That's
probably about the best we could do about this.

@TheDichotomist
Copy link
Author

something along those lines... i thought lmms automatically refreshed every few minutes/seconds. I also thought lmms would/could have some awareness of the parameters you tweaked in any plugin.
some kind of history that i think would be needed for the undo/redo function.

@diizy
Copy link
Contributor

diizy commented Mar 19, 2014

On 03/20/2014 01:06 AM, TheDichotomist wrote:

something along those lines... i thought lmms automatically refreshed
every few minutes/seconds. I also thought lmms would/could have some
awareness of the parameters you tweaked in any plugin.
some kind of history that i think would be needed for the undo/redo
function.

In normal, native plugins, yes - LMMS has very much awareness of the
parameters. But VST is different. It's a proprietary format, and the
entire VST support we have is based on reverse-engineered headers (which
is probably why some VST's don't work properly).

@TheDichotomist
Copy link
Author

oh..... wel.... great XD ...... wonder if i'll ever request a feature that you guys can actually make XD

@unfa
Copy link
Contributor

unfa commented Mar 27, 2014

Requesting is for sure easier than making ;) But don't stop! It's inspiring
and can show us limitations we were not aware of.
On 20 Mar 2014 02:18, "TheDichotomist" notifications@github.com wrote:

oh..... wel.... great XD ...... wonder if i'll ever request a feature that
you guys can actually make XD

Reply to this email directly or view it on GitHubhttps://github.com//issues/490#issuecomment-38126422
.

@firewall1110
Copy link
Contributor

Is this actual now?
May be should closed?..

@regulus79
Copy link
Contributor

I started implementing this in #7622, but it's not done yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants