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.0] Sustained notes do not loop and are cutoff #646

Closed
benc-uk opened this issue Jan 6, 2021 · 3 comments
Closed

[1.3.0] Sustained notes do not loop and are cutoff #646

benc-uk opened this issue Jan 6, 2021 · 3 comments
Assignees
Milestone

Comments

@benc-uk
Copy link

@benc-uk benc-uk commented Jan 6, 2021

It is impossible to hold a note indefinitely and loop it forever with the Tracker.
This is a severe musical limitation as you are unable to put in a long pad sound, or drone into a track. And makes the Tracker difficult to use with ambient, drone, and experimental music

Steps to reproduce

Sustain a note using a looped sample, after a number of seconds the sustain is released, even without a OFF or other note.
The number of seconds it takes is dependant on tempo, at 200BPM it will release after 18 seconds, lower tempos lasts longer (approx 1min at 120BPM) but it can never hold forever.

This behaviour happens with MIDI notes also.

Attachments and links

A simple project to reproduce the issue it attached
sustain-bug.zip

Other people have verified the issue here
https://www.facebook.com/groups/polyendtracker/permalink/409707253697586

Other important information

  • How often does this bug happen? - Every time

  • Does this bug happen in previous firmware versions? - Unknown

  • Does this bug happen in every project? - Yes

@benc-uk benc-uk added the bug label Jan 6, 2021
@Just-Peter
Copy link

@Just-Peter Just-Peter commented Jan 6, 2021

I agree with @benc-uk Forever looping is crucial for ambient/drone music. Even on a tracker this is a essential feature.

@doomglue
Copy link

@doomglue doomglue commented Jan 7, 2021

+1, switching off envelopes does not help neither as that seemed to be suggested as a fix a few times.

@shuler323
Copy link
Collaborator

@shuler323 shuler323 commented Jan 8, 2021

Thanks for reporting. Next beta (1.3.1b1) should fix this problem, tested on highest tempo for ~10mins. If not please reopen this issue

@shuler323 shuler323 added this to the 1.3.1b1 milestone Jan 8, 2021
@shuler323 shuler323 closed this Jan 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants