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

Improve FL Studio automation support #118

Closed
jonatandorozco opened this issue Nov 4, 2022 · 13 comments
Closed

Improve FL Studio automation support #118

jonatandorozco opened this issue Nov 4, 2022 · 13 comments
Labels
enhancement New feature or request

Comments

@jonatandorozco
Copy link

I just installed the plugin and I tried to automate the controls without any luck. Is there a way to support it?

If that's the case, I can help testing.

@greatest-ape
Copy link
Owner

It should be supported.. Are you using version 0.8.1? In that case, could you please test with the previous release? https://github.com/greatest-ape/OctaSine/releases/tag/v0.8.0

@greatest-ape greatest-ape added the bug Something isn't working label Nov 5, 2022
@jonatandorozco
Copy link
Author

I'll check it @greatest-ape

@jonatandorozco
Copy link
Author

My bad @greatest-ape, the latest version has automation support, actually. I found the available events.

@jonatandorozco
Copy link
Author

Btw, I found some events are treated as knobs instead of triggers

@jonatandorozco
Copy link
Author

I'll send a video to show you what I mean

@jonatandorozco
Copy link
Author

FL64_4lbpe0FxxH.mp4

As you can see in the video I'm toggling the mute button for the LFO4 but it shows as a knob

@jonatandorozco
Copy link
Author

jonatandorozco commented Nov 5, 2022

FL64_5UtPqPvns8.mp4

I do the same with another plugin and it shows as a toggle. (Legato button)

@jonatandorozco jonatandorozco changed the title FL Studio automation support Improve FL Studio automation support Nov 5, 2022
@greatest-ape greatest-ape added enhancement New feature or request and removed bug Something isn't working labels Nov 6, 2022
@greatest-ape
Copy link
Owner

Thanks for checking and great that it works with 0.8.1.

Is the other thing causing issues when automating or is it just confusing / not pretty? :-) And is the other plugin a vst2 plugin?

@jonatandorozco
Copy link
Author

I think is not intuitive as a switch. The main reason is to avoid intermediate values when automating that can produce misleading effects. Aside that, I don't have any issue with it.

@jonatandorozco
Copy link
Author

And yes, it's a VST 2 plugin

@greatest-ape
Copy link
Owner

Alright, sure, that makes sense.

@bryc
Copy link

bryc commented Nov 28, 2022

That's how VST parameters work in FL Studio or in general. They're basically a decimal between 0 and 1 and developers typically define thresholds to implement toggle buttons. It's always been this way, in fact, the very first VST made (Neon) has a 'octave' selector with a hidden option only available by manually adjusting the raw parameter in the way you're doing it.

So it's a non-issue.

The reason Harmor does the 'snap' thing is because it's an FLi plugin, not a VSTi plugin, and supports 'lists' of options directly on the raw knob control, because it's a native FL thing. This is simply not possible to do with the raw VSTi parameters.

@greatest-ape
Copy link
Owner

Hmm yeah, we’re not going to get snapping widgets in DAWs, and I don’t think it’s a good idea to try to automate parameters when they’re set. So I’m closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants