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

Add Catch Notes feature to CommunityFeatures.md and update feature list. #253

Merged

Conversation

weavermedia
Copy link
Contributor

Added the Catch Notes feature to CommunityFeatures.md. Updated the feature list. Added missing link for MIDI Takeover Mode.

@jamiefaye jamiefaye added this pull request to the merge queue Jul 30, 2023
Merged via the queue into SynthstromAudible:community with commit 2706c0b Jul 30, 2023
2 checks passed
@weavermedia weavermedia deleted the community-features-list branch August 3, 2023 06:21
@sichtbeton
Copy link
Contributor

Can this be set off by default? It interferes with normal operation of the section changes and would be good to have off by default.

@weavermedia
Copy link
Contributor Author

@sichtbeton I'm totally happy for this to be off by default. That was my first instinct since it changes current behavior. I asked the question (in the Discord I think) and there was mention of whether that would actually be considered a bug fix rather than a new feature.

If it interferes with section changes it should definitely be off by default. Have you confirmed this feature is interfering with section changing behavior? What behavior is being altered? Does turning off the feature return the section behavior back to normal?

All this feature does is adds a conditional around the code that attempts to play 'late notes' after changing clips. I'm not sure how it could cut off samples already playing, unless there's some way that carry-over notes are passed from one clip to the next that I haven't seen?

For reference I asked about the playback glitches on Facebook a couple of years ago and Rohan responded basically saying it's a feature not a bug: https://www.facebook.com/groups/DelugeBetaTesters/posts/1677334075806819/

@sichtbeton
Copy link
Contributor

Reference

It came up when legato triggering sections with #251. it double triggered notes and when having long releases, the notes got cutoff.

Toggling this to off made it normal again.

@weavermedia
Copy link
Contributor Author

@sichtbeton What do you mean by 'legato triggering sections'?

@sichtbeton
Copy link
Contributor

its a new mode that was introduced within the new grid view (i linked the PR). but it also did this when doing a normal section change.

@weavermedia
Copy link
Contributor Author

weavermedia commented Aug 6, 2023

@sichtbeton I can't reproduce with normal section changes. Can you give me more details or an example SONG file?

For the samples that get cut off, what mode are they set to? ONCE/CUT/LOOP/STREtch?

@sichtbeton
Copy link
Contributor

Now when trying to replicate it, I fail too. This is strange.

@weavermedia
Copy link
Contributor Author

@sichtbeton OK, let me know if it comes up again. In the meantime I do personally think this feature should be off by default anyway, considering Rohan's reasoning in 2021. I'll submit a PR to update the default to OFF and ask for review.

@sichtbeton
Copy link
Contributor

@sichtbeton OK, let me know if it comes up again. In the meantime I do personally think this feature should be off by default anyway, considering Rohan's reasoning in 2021. I'll submit a PR to update the default to OFF and ask for review.

sorry for stirring the pot here. I should be more careful when testing this stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants