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

automation max value changes when loading a saved file #6669

Closed
snorasaur opened this issue Mar 14, 2023 · 5 comments · Fixed by #6670
Closed

automation max value changes when loading a saved file #6669

snorasaur opened this issue Mar 14, 2023 · 5 comments · Fixed by #6670
Labels

Comments

@snorasaur
Copy link

Bug Summary

when i make an automation track with points that have values higher than 1, they will be reverted to 1 upon loading

Steps to reproduce

open organic synth
add automation track
drag harmonic dial to automation track (values are 0-17)
lay points on the track varying from 0-17
save file
load file
check automation track. upper limit will be set back to 1.0, and points with values greater than 1 become 1.

Expected behavior

automation points should stay at the number they were assigned. not truncated down to 1.0

Actual behavior

automation points greater than 1.0, become 1.0

Screenshot

Affected LMMS versions

1.2.2

Logs

Click to expand

@snorasaur snorasaur added the bug label Mar 14, 2023
@snorasaur
Copy link
Author

no sound, but u get the idea.

https://youtu.be/0dfKMKUdcWU

@messmerd
Copy link
Member

I've confirmed that this bug is present in the master branch.

@messmerd
Copy link
Member

messmerd commented Mar 14, 2023

I have a good idea about what is causing this issue and I'm just figuring out how I should fix it. Interestingly, it looks like Organic synth is not the only instrument exhibiting this bug - Kicker's end distortion parameter does the same thing.

I'll try to fix all instances of this bug within the next couple days. EDIT: Or tonight haha

@snorasaur
Copy link
Author

thanks for the quick fix!

@messmerd
Copy link
Member

@snorasaur The PR with the fix hasn't been approved and merged into master yet, so you should keep this issue open until that happens. Usually issues are automatically marked as completed when the PR linked to them is completed and merged.

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

Successfully merging a pull request may close this issue.

2 participants