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

Parameter automation not working in Bitwig #90

Closed
kzantow opened this issue Aug 27, 2022 · 6 comments
Closed

Parameter automation not working in Bitwig #90

kzantow opened this issue Aug 27, 2022 · 6 comments
Labels
bug Something isn't working

Comments

@kzantow
Copy link

kzantow commented Aug 27, 2022

Describe the feature
It appears currently there are no parameters exposed for automation. It would be great to add parameter automation for most parameters, as it makes sense for parameters like like: levels, decay/release times, operator frequencies (selecting LFO shape might not make sense, for example).

In case this is a bug:

Software (please complete the following information):

@greatest-ape
Copy link
Owner

Hmm, all parameters should already be automatable. Automating works for me in a variety of DAWs.

@kzantow
Copy link
Author

kzantow commented Aug 28, 2022

I tried this in REAPER and you're right, parameters show up fine there... this seems to be a Bitwig issue (also tried it on my M1 Mac with the same problem). I'll see if I can possibly figure anything out to help/fix. My rust skills are pretty rudimentary, however 😢

@kzantow kzantow changed the title Feature request: parameter automation Parameter automation not working in Bitwig Aug 28, 2022
@greatest-ape
Copy link
Owner

That’s weird. I just downloaded the Bitwig demo and the parameters don’t appear to me either.

@greatest-ape greatest-ape added the bug Something isn't working label Aug 28, 2022
@SpotlightKid
Copy link

SpotlightKid commented Oct 29, 2022

Parameter automation also does not work in Carla (Manjaro Linux). When I asked its author falkTX about it, he said that for each automatable parameter, the "plugin needs to return 1 to effCanBeAutomated opcode".

I don't know enough Rust to check whether that's the case. But it would probably be a good thing to check.

@greatest-ape
Copy link
Owner

@SpotlightKid Thanks a lot, this helped me solve the issue. There was indeed a bug in the logic telling the host which parameters are automatable. The fix has been merged into master and will be part of the next release.

@SpotlightKid
Copy link

SpotlightKid commented Oct 29, 2022

And that's why I love open source! :) Thanks! Looking forward to the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants