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

LFO average points algorithm appears confusing by LFO EG attack and Amplitude #2258

Closed
K0rrid0r opened this issue Jun 30, 2020 · 9 comments · Fixed by #3867
Closed

LFO average points algorithm appears confusing by LFO EG attack and Amplitude #2258

K0rrid0r opened this issue Jun 30, 2020 · 9 comments · Fixed by #3867
Labels
Modulation Modulation related issues UI Issues related to UI look&feel
Milestone

Comments

@K0rrid0r
Copy link
Collaborator

Describe the bug
LFO display average points in drawing is exposed broken by LFO EG attack

Example how to see it.
139

Please let us know your surge version
this exist as a thing in the Vector LFO mode.

@baconpaul baconpaul added this to the 1.7.n milestone Jun 30, 2020
@baconpaul baconpaul added Modulation Modulation related issues UI Issues related to UI look&feel labels Jun 30, 2020
@K0rrid0r K0rrid0r changed the title LFO display average points drawing is exposed wierd when applying LFO EG attack LFO display average points drawing is exposed broken by LFO EG attack Jun 30, 2020
@K0rrid0r
Copy link
Collaborator Author

K0rrid0r commented Jul 1, 2020

143
142
141

some pictures showing strange behavior in the lfo draw algo, will comment more about this later on.

@K0rrid0r K0rrid0r changed the title LFO display average points drawing is exposed broken by LFO EG attack LFO average points algorithm appears broken by LFO EG attack and Amplitude Jul 1, 2020
@K0rrid0r K0rrid0r changed the title LFO average points algorithm appears broken by LFO EG attack and Amplitude LFO average points algorithm appears confusing by LFO EG attack and Amplitude Jul 1, 2020
@baconpaul
Copy link
Collaborator

thank you - great use cases for a fix!

@mkruselj mkruselj modified the milestones: 1.8.n, 1.9.0 Oct 8, 2020
@mkruselj mkruselj modified the milestones: 1.9.0, Surge XT Jan 24, 2021
@mkruselj
Copy link
Collaborator

@baconpaul I think I found this one.

if (maxval - minval > 0.2)

It's this check here. Unsure why it's needed, if I just remove the else branch and remove the if it shows up really nicely, and I cannot see any adverse effects. What was the reason behind this condition here?

image

@baconpaul
Copy link
Collaborator

It makes square-ish and other discontinuous waves draw properly on windows 8 and some windows 10 systems

@mkruselj
Copy link
Collaborator

Hm, those seem just fine over here on my two W10 and an old W7 machine...

image

@baconpaul
Copy link
Collaborator

Right so it fixes a problem on windows forever ago. So either that problem has magically disappeared or it hasn’t and I don’t remember what it is. So our choices are

1: remove this, believe in magic, go forth
2: remove this, find the bug, reinstate this before 19
3: remove this, ship 19, have 19 be broken forever or
4: don’t remove this and fix it with juce

I’m neutral but of these think 4 and 2 are the best

@mkruselj
Copy link
Collaborator

Let's go with 2! I scanned all the closed tickets mentioning LFO and no word on drawing issue under certain Windows... If it pops up back again, we will know. But I bet we're on JUCE by then. 🙂

@mkruselj
Copy link
Collaborator

mkruselj commented Feb 11, 2021

Actually just found the issue... #1438

Oh, but your fix is WITHIN the if > 0.2 condition... so that's why it still works even if I remove that condition!

@baconpaul
Copy link
Collaborator

Ok!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Modulation Modulation related issues UI Issues related to UI look&feel
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants