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

Square LFO spikes in vector rendered waveform #1438

Closed
mkruselj opened this issue Dec 20, 2019 · 32 comments · Fixed by #1497
Closed

Square LFO spikes in vector rendered waveform #1438

mkruselj opened this issue Dec 20, 2019 · 32 comments · Fixed by #1497
Labels
UI Issues related to UI look&feel

Comments

@mkruselj
Copy link
Collaborator

image

Maybe valid for #1390?

@baconpaul baconpaul added this to the 1.6.5 milestone Dec 20, 2019
@baconpaul baconpaul added the UI Issues related to UI look&feel label Dec 20, 2019
@baconpaul
Copy link
Collaborator

Ha it's not an LFO spike; it's the axis tick marks. Licecap doesn't work on catalina for me right now but trust me. I will lighten that tick color and close this issue.

@baconpaul
Copy link
Collaborator

Nope. On windows it actually shows that spike. woof.

@VincyZed
Copy link
Collaborator

Confirmed. Just got 1.6.3 running and it's still present!

@VincyZed
Copy link
Collaborator

Turns out this has been introduced all the way back in 1.6.2, which is when the LFO display has been vectorialized!

@baconpaul
Copy link
Collaborator

OK!
Well let me try and reproduce it.

@esaruoho
Copy link
Collaborator

Ha it's not an LFO spike; it's the axis tick marks. Licecap doesn't work on catalina for me right now but trust me. I will lighten that tick color and close this issue.

Protip: get newest licecap and dont forget to type .gif by hand at the end of the filename when setting gif recording filename.

@baconpaul
Copy link
Collaborator

@sense-amr that looks like the bitmap display not the vector one. Are you on a recent version of surge? Also sometimes with slower renders it falls back to bitmap.

@baconpaul
Copy link
Collaborator

Look in "Menu / UI Options" - Do you see a choice like "use vector LFO display"? If so click that. If not then you aren't fully up to date yeah

@baconpaul
Copy link
Collaborator

Yeah so you need to update your source! Or just grab the nightly.

@baconpaul
Copy link
Collaborator

Building is all the same
yeah just grab master from refresh your fork and it is all the same.

@sense-amr
Copy link
Contributor

ok . sorry about all that.. now i have the latest build .. oh and yes i see this very strange anomoly .. on the square LFO .. using bitmap LFO display
LFOsq_BitmapUI

@baconpaul
Copy link
Collaborator

Yeah ok so it is real for sure. I need to get a windows environment running again to figure it out since Mac doesn’t do it.

@sense-amr
Copy link
Contributor

sense-amr commented Jan 21, 2020

i noticed it goes away if magnitude is under 10%

sqLFOanomoly_10

@baconpaul
Copy link
Collaborator

Yeah I bet it is just some dumb rounding thing when I make the waveform by pulling the lfo that is compiled dependent or some such. The hardest part of fixing is going to be setting up windows! But I have to do that anyway so

@baconpaul
Copy link
Collaborator

Oh curious if you put a long attack on do the spikes pop above the envelope during the attack phase?

@sense-amr
Copy link
Contributor

sqLFO10_1
this is 10.1% and magically it appears..

lets try with attack

@sense-amr
Copy link
Contributor

sense-amr commented Jan 21, 2020

sqLFO_withatt
they sure do!

@sense-amr
Copy link
Contributor

sense-amr commented Jan 21, 2020

hmm its appearing everywhere, as a general out of graphical boundary error..
S HtooLFO
RAMPtooLFO
TRItooLFO
corresponding to high rate LFO .. and not occuring at low rates.. for these other LFO types..
square still seems to show it .. even at low rates..

@sense-amr
Copy link
Contributor

RampFairlynormalLOrateLFO
Fairly Normal Low Rate.. Not outside of bounds..
hairmonsterLFO_highRate
Scary Hairy Monster High Rate LFO

@sense-amr
Copy link
Contributor

so i can confirm its NOT just square..

@VincyZed
Copy link
Collaborator

VincyZed commented Jan 21, 2020

If you take the square wave (or the other ones that do this), and change the frequency precisely ever so slowly using shift, they will actually pop in and out.

LFO

@baconpaul
Copy link
Collaborator

Very very useful thank you

@baconpaul
Copy link
Collaborator

I wonder when I find it what silly mistake it will be! Exciting!

@baconpaul
Copy link
Collaborator

Oh and welcome back @sense-amr - hope all is well!!

@sense-amr
Copy link
Contributor

Thanks @baconpaul good to see you and happy to be able to give some more time to surge ! ..great to see its still growing.. if i remember we ALWAYS had funny things with the LFO gui..

@baconpaul
Copy link
Collaborator

Yeah but then I rewrote it and I thought fixed all of them. But apparently fixed almost all of them.

For fun temposync the rate and you can see musical time axis too!

@sense-amr
Copy link
Contributor

yeh i noticed that and the (T|S) on the slider.. :) .. interesting .. with the tempo sync now displayed in time.. over the waveform.

im wondering .. if this is just graphical .. or if the way it looks in the lfo with the spikes etc.. .. corresponds to the actual used shape of the lfo when routed to a parameter..

@baconpaul
Copy link
Collaborator

That was first thing I checked but you can pull it up in rack and the lfo has no spike. It’s just something in my path creation code with downsamoling for graphics

@baconpaul
Copy link
Collaborator

My bet is I screwed up something here

if( maxval - minval > 0.2 )
since this branch only kicks in when there’s a big change

baconpaul added a commit to baconpaul/surge that referenced this issue Jan 22, 2020
Windows VSTGUI with the ordering we chose for points
drew specious spikes. Re-order the points to avoid this
potential bug.

Closes surge-synthesizer#1438
@baconpaul
Copy link
Collaborator

Found it! Fix incoming.

baconpaul added a commit that referenced this issue Jan 22, 2020
Windows VSTGUI with the ordering we chose for points
drew specious spikes. Re-order the points to avoid this
potential bug.

Closes #1438
@sense-amr
Copy link
Contributor

awesome @baconpaul .. great work as always .. im gonna build the new one right now.. and test..

@baconpaul
Copy link
Collaborator

Yeah this fix is so 10 hours ago - wait until you see the other goodies in the new build! Try modulating some stuff and say “ooh” “ahh”. Chuckle.

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

Successfully merging a pull request may close this issue.

5 participants