Surge: Square LFO spikes in vector rendered waveform
Maybe valid for #1390?
mkruselj
All 32 comments
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
on 16 Jan 2020
Nope. On windows it actually shows that spike. woof.
baconpaul
on 16 Jan 2020
Confirmed. Just got 1.6.3 running and it's still present!
VincyZed
on 16 Jan 2020
Turns out this has been introduced all the way back in 1.6.2, which is when the LFO display has been vectorialized!
VincyZed
on 16 Jan 2020
OK!
Well let me try and reproduce it.
baconpaul
on 16 Jan 2020
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.
esaruoho
on 21 Jan 2020
@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
on 21 Jan 2020
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
on 21 Jan 2020
Yeah so you need to update your source! Or just grab the nightly.
baconpaul
on 21 Jan 2020
Building is all the same
yeah just grab master from refresh your fork and it is all the same.
baconpaul
on 21 Jan 2020
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
sense-amr
on 21 Jan 2020
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.
baconpaul
on 21 Jan 2020
i noticed it goes away if magnitude is under 10%
sense-amr
on 21 Jan 2020
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
on 21 Jan 2020
Oh curious if you put a long attack on do the spikes pop above the envelope during the attack phase?
baconpaul
on 21 Jan 2020
this is 10.1% and magically it appears..
lets try with attack
sense-amr
on 21 Jan 2020
they sure do!
sense-amr
on 21 Jan 2020
hmm its appearing everywhere, as a general out of graphical boundary error..
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
on 21 Jan 2020
Fairly Normal Low Rate.. Not outside of bounds..
Scary Hairy Monster High Rate LFO
sense-amr
on 21 Jan 2020
so i can confirm its NOT just square..
sense-amr
on 21 Jan 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.
VincyZed
on 21 Jan 2020
Very very useful thank you
baconpaul
on 21 Jan 2020
I wonder when I find it what silly mistake it will be! Exciting!
baconpaul
on 21 Jan 2020
Oh and welcome back @sense-amr - hope all is well!!
baconpaul
on 21 Jan 2020
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..
sense-amr
on 21 Jan 2020
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!
baconpaul
on 21 Jan 2020
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..
sense-amr
on 21 Jan 2020
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
on 21 Jan 2020
My bet is I screwed up something here https://github.com/surge-synthesizer/surge/blob/b6134fa4ce2c74958714b368612a6cc8171b5dda/src/common/gui/CLFOGui.cpp#L212 since this branch only kicks in when there’s a big change
baconpaul
on 21 Jan 2020
Found it! Fix incoming.
baconpaul
on 22 Jan 2020
awesome @baconpaul .. great work as always .. im gonna build the new one right now.. and test..
sense-amr
on 23 Jan 2020
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.
baconpaul
on 23 Jan 2020
Related issues
mxmilkiib
·
7Comments
tank-trax
·
9Comments
mortfell
·
8Comments
esaruoho
·
10Comments
baconpaul
·
8Comments