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

[1.3.1] Freeze when navigate to Volume Destination after setting Granular LFO #903

Closed
hissbackwards opened this issue Mar 18, 2021 · 5 comments
Labels
bug Something isn't working fixed

Comments

@hissbackwards
Copy link

Freeze when navigate to Volume Destination after setting Granular LFO

Steps to reproduce

  1. In any project (e.g. Create new) and add any sample to Instruments
  2. Open Instrument Parameters and open 2nd page
  3. Goto Granular Position and select LFO
  4. Change step to something fast (e.g. 1/16)
  5. Navigate to Volume Destination.

Results:
Freeze.

Other important information

Firmware: 1.3.1

@hissbackwards hissbackwards added the bug Something isn't working label Mar 18, 2021
@phacya
Copy link

phacya commented Mar 19, 2021

Just tried this on my 1.3.1 machine and I confirm this bug too. Hard freeze as you try to move from "Panning" to "Volume".

@Zeroapr
Copy link

Zeroapr commented Apr 15, 2021

Similar problem with me. I adjust the LFO on the Instrument Parameters/"Instrument Automation 2/2"/"Cutoff". Then if I click up the destination it locks up on the Panning. While it's locked up the sound is stuck on the last pitch and can't shut off the Tracker without pulling the plug.

@x2db
Copy link

x2db commented Apr 16, 2021

I've got my unit frozen on this page twice already. Moving up down around Panning and volume. This problem didn't exist in 1.3.0. But I cannot reproduce this 100%.

@Zeroapr
Copy link

Zeroapr commented Apr 16, 2021

Yep. Has happened at least 3 times in my last session. Just seems to happen when you tweak the envelope or LFO in the bottom sections. My pattern isn’t lost but the hard boot is annoying and takes me out of the flow. I hope this gets priority treatment it is a pain in what is otherwise a very solid 1.3.1 firmware.

@Jacknametrouble
Copy link
Contributor

Fixed in firmware v1.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed
Projects
None yet
Development

No branches or pull requests

6 participants