[Bug Report for 3.6.0f] Some slices consistently playing beyond their endpoints

[Someone64]

https://streamable.com/qbqxud

As you can see from that link, a sound is playing beyond its endpoint (you can see they're not overlapping in the Loops/Ranges window below) and this has been happening for every sound I put in that I slice with the transient slicer. Within the wave itself it doesn't happen to all slices but it does happen with about 1 in 10 slices. I haven't tried to see if this also happens if I manually slice up a wave. The linked video only demonstrates it happening when I preview it in the wave editor but it does happen when I lay out the slices and play them through midi, too.

Another very minor issue is that TX16Wx's version still reports as 3.6.0e.

Also as a side note I'd like to make a feature request for more transient slicer options. It seems that the way transient slicer works is really weird and no matter how much I fiddle with it I never get the desired results without manually creating and removing slices (which messes up the drag and drop midi export). I get things like misplaced slices, slices that shouldn't exist, slices being too far left or right of a transient, etc. I think options more similar to those in REAPER's MK Slicer lua script (https://forum.cockos.com/showthread.php?t=232672) for example work better as demonstrated in this screenshot: https://imgur.com/a/sYYa5ta (image tag not working for some reason...)

The more traditional threshold, sensitivity, and retrig options get most of the job done and position the slices perfectly and the filter options to the bottom left fix any remaining issues.
I would actually use MK Slicer and other external methods to import slices into TX16Wx but I can't find a way to get midi export to work as there doesn't seem to be a way to combine multiple waves into one or export midi from multiple waves.

EDIT: I just realized I made a thread regarding the transient detector in Feb 2022 already oops...

[elcallio]

https://streamable.com/qbqxud

As you can see from that link, a sound is playing beyond its endpoint (you can see they're not overlapping in the Loops/Ranges window below) and this has been happening for every sound I put in that I slice with the transient slicer. Within the wave itself it doesn't happen to all slices but it does happen with about 1 in 10 slices. I haven't tried to see if this also happens if I manually slice up a wave. The linked video only demonstrates it happening when I preview it in the wave editor but it does happen when I lay out the slices and play them through midi, too.

Works as it should for me and all my test waves. Very hard to see anything in the video. Please send the offending wave and I will check it out.
Btw, please also provide which OS, bit width, host, audio driver etc you are using.

Another very minor issue is that TX16Wx's version still reports as 3.6.0e.

If the version says 3.6.0e, it is 3.6.0e. Please do a full uninstall and verify that no files are left behind or copied to where they should not be.

Also as a side note I'd like to make a feature request for more transient slicer options. It seems that the way transient slicer works is really weird and no matter how much I fiddle with it I never get the desired results without manually creating and removing slices (which messes up the drag and drop midi export). I get things like misplaced slices, slices that shouldn't exist, slices being too far left or right of a transient, etc. I think options more similar to those in REAPER's MK Slicer lua script (https://forum.cockos.com/showthread.php?t=232672) for example work better as demonstrated in this screenshot: https://imgur.com/a/sYYa5ta (image tag not working for some reason...)

The more traditional threshold, sensitivity, and retrig options get most of the job done and position the slices perfectly and the filter options to the bottom left fix any remaining issues.

The REAPER plug-in uses envelope based detection (afaict). TX uses FFT based transient detection. The latter will produce results that are sometimes a bit off (due to FFT blocks), but handles non-rhythmic material better. As for what controls are "traditional", I would say that just because the REAPER plug uses these (obviously env related controls) does not make them more "traditional".

[Someone64]

I made a mistake and didn't update the CLAP version properly... The bug report for the slice issue still stands, though.

https://drive.google.com/drive/folders/ ... drive_link

Above is a link to a Google Drive folder with example wavs with the bug.

I used these settings for this bug report: https://imgur.com/a/T6lDvbi
cw_amen01_175.wav: Slice 10 and 11
cw_amen03_175.wav: Slice 9
RES_172_Drums_10_Break.wav: Slice 25, 28, 49, 50, 52
16RES PER LP.wav: Slice 18, 19, 26

The list is in no way comprehensive and I just arbitrarily picked random broken slices from each but I can assure you they are consistent.

[elcallio]

The playback issue is indeed real, and caused by the slices being played back in DFD mode, even though the actual slice range is smaller than the initial DFD buffer. The streamer did not really handle this, assuming this should be already checked. Fixed.
As for slicing operations; I completely forgot I actually already added envelope detection slicing (though meant for finding silence - not beat slicing) to the editor. Not super hard to make a variant that uses dual env tracking similar to the above reaper plugs. Won't work as well as FFT based when material has little intensity variation (FFT handles frequency transients as well as "beat" ones), but might be easier and more exact for (some) drum loops.
Added another operating mode for the env tracker with similar parameters.

If you PM me an email (and preferred os etc) I can send you a preview build to test before I do a gold build.