Ha, i found one!
In the sample loader, when importing a sample and changing the start point, tracker will crash when you repeatedly hitting the preview button.
Steps to Reproduce
Start a new project
Go to sample loader
load the attached testsample (res tom.wav)
Press import, you see the import screen.
Scroll the start point to the middle of the sample.
With a constant fast freqency hit the preview button while slowly scrolling backwards.
If it is not crashing the first time, scroll to the middle and try again.
Edit: interestingly i had only success with the test sample, perhaps because there’s silence at the beginning? Sample is sane, correct riff format.
I’ve tried twice tonight to replicate this with a couple random samples, and still can get it to trigger.
It’s possible that this particular file has a couple of lines of corruption which is what a lot of codecs are meant to deal with; it sounds fine when we play it back because the codec can mask very minor errors in the file, but when we go out and try to address the moments where the error occurs on the file, that’s where all hell breaks loose.
Would you mind sharing the process of the life and processing this file went through?
Hey first a big thanks for investigating with me!
Yes, i also blame the sample here is what i have done:
The original sample on my server was 48khz 24bit stereo. No idea what treatment it was put through the last 20 years but the last hour was hard😅
I converted it to mp3 128kb into a new file.
I reconverted this new file to 44.1khz wav.
I renamed it hard-crash.wav though its a tom.
I loaded it into the tracker.
It crashed.
I zipped it for you.
For my understanding its nearly impossible that the binary is corrupt. The codec should deal with it, mmh..
Maybe i’ll make a sample pack. Toms of doom.
The last thing i’ve done, i truncated the sample start and endpoint (had to get rid of the silence anyway) and rendered it to a new file in my daw.
So far, i cant get it to crash anymore.
My suggestion, delete this report. Maybe it will be interesting what the debugger spits out in this particular case, but after all its an anomaly.
