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

Global Volume won't modulate. #6424

Closed
Andreya-Autumn opened this issue Jul 26, 2022 · 6 comments · Fixed by #6603
Closed

Global Volume won't modulate. #6424

Andreya-Autumn opened this issue Jul 26, 2022 · 6 comments · Fixed by #6603
Labels
Bug Report Item submitted using the Bug Report template Have A Plan The issue has a description of how we will solve it, just we haven't done it yet Modulation Modulation related issues

Comments

@Andreya-Autumn
Copy link
Collaborator

...even though it looks like it should.

In the UI, the global volume slider accepts modulation input from Macros, SLFO's or MIDI, but none of them will actually affect the output volume at all.

@Andreya-Autumn Andreya-Autumn added the Bug Report Item submitted using the Bug Report template label Jul 26, 2022
@baconpaul baconpaul added this to the Surge XT 1.1.n milestone Jul 26, 2022
@baconpaul
Copy link
Collaborator

This problem has always been there. It is caused by this line

amp.set_target_smoothed(storage.db_to_linear(storage.getPatch().volume.val.f));

which reads the parameter directly rather than the local copy / modulated value.

@mkruselj mkruselj added the Modulation Modulation related issues label Jul 28, 2022
@baconpaul baconpaul added the Have A Plan The issue has a description of how we will solve it, just we haven't done it yet label Aug 7, 2022
@baconpaul
Copy link
Collaborator

The plan is: fix storage.getPatch().volume.val.f to gsobalcopy[storage.getPatch().volume.id].f or similar, based on what's the actually syntax for global modulators in that file :)

@baconpaul
Copy link
Collaborator

oh also we probably want to up the patch version number and clear any modulations onto global volume from old patches which we don't want to suddenly work. I think? @mkruselj your view here valued.

@Andreya-Autumn
Copy link
Collaborator Author

That makes a lot of sense. If the mod didn't work in the first place obviously clearing it is the way to ensure the patches keep sounding the same.

@mkruselj
Copy link
Collaborator

mkruselj commented Aug 8, 2022

Yup upping the patch version makes sense.

@baconpaul
Copy link
Collaborator

I dont want to up the patch version and change streaming response in 1.1.1 and this is neither a regression nor absolutely critical so I'm going to push it back into 1.1.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Item submitted using the Bug Report template Have A Plan The issue has a description of how we will solve it, just we haven't done it yet Modulation Modulation related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants