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

Fixed not releasing a pipe after fast switching between vave-based tremulant samples and regular pipe samples https://github.com/GrandOrgue/grandorgue/issues/2004 #2041

Merged
merged 4 commits into from
Dec 13, 2024

Conversation

oleg68
Copy link
Contributor

@oleg68 oleg68 commented Nov 9, 2024

Resolves: #2004

It resolves the issue with the midi file from #2004 (comment)

The reason was GOSoundFader: when a sampler was in "increasing" crossfade state and then it was switched to another attack (with the wave-based tremulants on/off), the old attack sample was never released and sounded infinitelly.

@oleg68
Copy link
Contributor Author

oleg68 commented Nov 10, 2024

Seems this change breaks playing release samples. I need more time to work.

@oleg68 oleg68 marked this pull request as draft November 10, 2024 05:38
@oleg68 oleg68 mentioned this pull request Nov 10, 2024
4 tasks
@oleg68
Copy link
Contributor Author

oleg68 commented Nov 11, 2024

I reworked GOSoundFaded and the fix.

Earlier increasing and decreasing the volume were in place together so might interfere and the sample was neve released
After the first my fix decreasing discarded increasing so a release sample (that always started from 0 due the crossfade) was not played if The ReleaseLength was set to any value rather the Max.
Now decreasing becomes "virtual" until the increased and decreased target volumes meet at the new target volume.

@oleg68 oleg68 marked this pull request as ready for review November 11, 2024 20:00
@hnb2907
Copy link

hnb2907 commented Nov 11, 2024

Nice one 👍Your description sounds promising 🙂

Could you point me to the binary please? Hopefully I will be able to try it later today or tomorrow.

Cheers, Chris.

@oleg68
Copy link
Contributor Author

oleg68 commented Nov 11, 2024

Could you point me to the binary please?

https://github.com/oleg68/GrandOrgue-official/actions/runs/11785207053

@oleg68 oleg68 force-pushed the bugfix/trem-release branch from 8db3df1 to b11c777 Compare November 16, 2024 16:48
@oleg68
Copy link
Contributor Author

oleg68 commented Nov 16, 2024

@larspalo @rousseldenis Could you approve this PR?

@oleg68 oleg68 force-pushed the bugfix/trem-release branch 4 times, most recently from 82309e6 to e174f22 Compare November 28, 2024 16:51
@oleg68
Copy link
Contributor Author

oleg68 commented Nov 28, 2024

@larspalo @rousseldenis As talked in #2004, the last intermediate build fixed all pipe-attack and pipe-release isuues mentioned there. The final variant can be taken for tests from https://github.com/oleg68/GrandOrgue-official/actions/runs/12072896654

Could you approve this PR?

@oleg68
Copy link
Contributor Author

oleg68 commented Dec 3, 2024

@rousseldenis Pourriez-vous approuver ce PR? Merci.

@oleg68
Copy link
Contributor Author

oleg68 commented Dec 12, 2024

@rousseldenis I'm going to merge this PR as administrator without your approving. Do you agree or disagree?

@oleg68 oleg68 force-pushed the bugfix/trem-release branch from e174f22 to 3bdc38f Compare December 13, 2024 12:29
@oleg68 oleg68 merged commit a75c498 into GrandOrgue:master Dec 13, 2024
1 check passed
@oleg68 oleg68 deleted the bugfix/trem-release branch December 13, 2024 12:31
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.

Pipe release problem with Barton sampleset on grandorgue-3.15.x-x.linux.x86_64
4 participants