-
Notifications
You must be signed in to change notification settings - Fork 45
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
Conversation
Seems this change breaks playing release samples. I need more time to work. |
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 |
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. |
https://github.com/oleg68/GrandOrgue-official/actions/runs/11785207053 |
8db3df1
to
b11c777
Compare
@larspalo @rousseldenis Could you approve this PR? |
82309e6
to
e174f22
Compare
@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? |
@rousseldenis Pourriez-vous approuver ce PR? Merci. |
@rousseldenis I'm going to merge this PR as administrator without your approving. Do you agree or disagree? |
e174f22
to
3bdc38f
Compare
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.