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

No Freerun on LFO - Surge XT #5534

Closed
hellerdejanuar opened this issue Nov 30, 2021 · 4 comments · Fixed by #5536
Closed

No Freerun on LFO - Surge XT #5534

hellerdejanuar opened this issue Nov 30, 2021 · 4 comments · Fixed by #5536
Labels
Bug Report Item submitted using the Bug Report template Modulation Modulation related issues
Milestone

Comments

@hellerdejanuar
Copy link

Bug Description:
Voice LFO Freerun doesn't behave as (I) expected. It seems to work almost like retrig, making it impossible to keep it phase synched with tempo.

Surge Version
Surge XT 0.9.nightly.7323973

  • Version:
  • Plugin Type: VST3
  • Bitness: 64-bit

Reproduction Steps:
Steps to reproduce the behavior:

  1. Simple patch with LFO (not SLFO) to cutoff. Optionally set rate to Sync.
  2. Select Freerun
  3. Play two notes spaced half a LFO cycle
  4. The two notes have now different phase. And none is synched to session BPM

Expected Behavior:
In Surge (no XT) it does work as intended.

Computer Information (please complete the following information):

  • OS: Macos Mojave
  • Host: Ableton
  • Version: 11.0.2
@hellerdejanuar hellerdejanuar added the Bug Report Item submitted using the Bug Report template label Nov 30, 2021
@baconpaul baconpaul added this to the Surge XT 1.0 milestone Nov 30, 2021
@baconpaul
Copy link
Collaborator

Ha so, the freerun works as expected if you run transport, but doesn't if transport is paused. (at least in LPX)

Believe it or not, that's a return of #146

Just in JUCE. Note that that bug was one I fixed almost 3 years ago. Funny!

If there's no transport we don't advance ppqpos artificially, and freerun VLFOs use song position.

I'll tag this into the milestone and apply the fix. Thank you for the excellent bug report.

@mkruselj mkruselj added the Modulation Modulation related issues label Nov 30, 2021
@hellerdejanuar
Copy link
Author

hellerdejanuar commented Nov 30, 2021 via email

@baconpaul
Copy link
Collaborator

huh so then live is different than logic, or my test was bad. (Your nightly is also quite a bit older than mine but that's probably OK - I don't think this code has changed much)

I'll dig. Something odd is definitely afoot. Very much appreciate the bug report.

@baconpaul
Copy link
Collaborator

Anyway I found it! Turns out we had an internal counter update which was placed in a block from when we looped by block, not sample, in juce; so it's just moving one line. The reason transport made it 'better' for me in logic was because my buffer size (64) resets the ppqpos really frequently so the drift was not that bad although now i retest it, not perfect; but with long buffers the result would be worse

PR in and this issue will auto close when we merge it, and an hour or so after that there will e a new nightly with the fix.

Thanks for the bug report. Excellent and long standing bug in XT we hadn't identified. Really appreciated.

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 Modulation Modulation related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants