unittests? about audio-stretch HOT 6 CLOSED

I think including some samples is a good idea. I have a few that I have created in the past, and I also just created an artificial test file to trigger the overflow that you discovered. Assuming GitHub allows (they're big) I will create a folder for them and include them.

from audio-stretch.

@dbry : in case the files are really big, a separate "audio-stretch-data" repository might be appropriate

from audio-stretch.

@hayguen I only made the samples big so that I could also use them for performance testing. I think I can easily make short versions for all other testing.

from audio-stretch.

@dbry : then, i'd suggest short files .. and amending a loop count option as command line argument.

from audio-stretch.

Probably a special benchmark option, which does discard the output samples without saving to file ..
and preloads the input file completely into memory, before repeated processing.

from audio-stretch.

it's not a unittest .. but meanwhile having the build and test scripts as well as the audio sample files.

from audio-stretch.