Pop/click noise in 808 - FL Studio Sampler vs TX16Wx

[elcallio]

Set mode to poly and add a bit of release. Consider tweaking the release curve shape depending on the type of sound you are playing.
Oneshot means the sample plays from start to end of either sample or AEG. Attack and release applies as expected.
Choke hard-kills samples. Choke fade makes the kill less harsh. Self-choke regulates whether the group kills itself.
Mono effectively plays the group on a single voice, replacing the sample if different, or playing the same if not. Difference from choke is that _start_ of sample will be "where we are now" currently.

[dunadan]

Thing is: If I was to set it to poly to make it work, I'd have to perfectly cut the loops, which is an annoyance. Consider this use case: I sample a loop from a song. Usually I would define a start point, but not the end point. Because it's set to mono I can make the loop start at bar 1 and then set the tune or project time so that that it cuts/restarts the loop at the perfect time. Thus no need to cut the loop perfectly at the end.

In this example: What would be my options to achieve a pop/click free loop fade out? I've tried keeping the sample poly, but setting a choke group with self choke and a fade out, sadly with no success.

Ableton's Simpler for example in oneshot mode does also choke the voice, meaning it works as I explained in my use case above. AFAIK it's not set to poly, yet no pops/clicks. What does it do different from TX?

[elcallio]

In this case, tuning your choke fade-out should do the trick. But even this cannot handle suddenly stopping playback at some point with to "loud" audio data. You will most likely create discontinuities in the sound (which causes the click).
AS might be doing additional low-pass filtering of the fade-out, don't know.

[elcallio]

All that being said, I just found a weird regression in the choke-fade. It is clearly not working as intended. Seems to be yet another merge issue... Ugh...

[elcallio]

No, sorry, it is a pure logic error for when using choke-fade within a single group. The feature was designed for drum kits, and mainly tested against them. Ugh.

[dunadan]

So the regression relates to my issues? Because that's what I was doing I think

[elcallio]

Update with fix for self-choke-fade available. Your use case: set group to poly, oneshot, choke=1 (not zero), fade=100

[dunadan]

Thank you btw, works perfectly now!

[robert_p]

Update with fix for self-choke-fade available. Your use case: set group to poly, oneshot, choke=1 (not zero), fade=100

Hi, I had my choke groups working fine with version 3.5.0s,

Choke Fade.jpg

however, after updating to 3.5.0z, I found out that choke fade doesn't seems to work any more - the samples are cut immediately. I use Vst2 on Win.10 64-bit. Downgrading to ver. 3.5.0s fixed the issue.

P.S. I checked the latest beta and it's even worse:

Choke Fade 2.jpg

"Cfd" parameter delays the trigger instead of fading out the sample

[elcallio]

Ugh. Just shows that you can never fix one thing without breaking something else. :-/
Regression caused by improvements to mono/legato mode management (back merged from 3.6 beta).
Now, I have fixed the choke management, and even improved on its latency behaviour a bit. For the moment, I've updated the 3.6 beta build with this fix/improvement. Please test the latest version of it. If it seems ok, and my additional testing seems to not show any unwanted side effects I'll drop a fix build for 3.5 as well.

[elcallio]

Some more tweaking + tests. Updated again.

[robert_p]

Some more tweaking + tests. Updated again.

Hi, thanks for the update! I'll load it with my drum samples and I'll post the report tomorrow, fingers crossed:))

UPDATE: The latest 3.6 beta works beautifully for me now, thanks for the fix! I just purchased a Pro Non-commercial licence to have all advanced features available for my acoustic drum kit:))