[Bug] --suppress_tokens: default value wreaking havoc

[misutoneko]

Hi,

Continuation from #928

I've been wondering about various timing issues and hallucinations, such as the ones listed there.
It looks like these kind of problems can happen whenever the sample starts with a non-speech region.
Btw my samples are very short (most are under 30s) and some samples may not have speech at all.

Anyway, I think I've finally found a workaround, which is to always use this option:
--suppress_tokens ""

If this option isn't present it will fall back to its default value -1,
which doesn't seem to be working as intended.
No idea how to fix it, though :(

Do note that some postprocessing may be needed with this option (as nothing is suppressed).
So the default -1 would be nicer from that pov. Well, if it worked, that is...

[rudymohammadbali]

@misutoneko I did not understand, can you please explain to me in an easier way?

[misutoneko]

Well, basically you just add --suppress_tokens "" to your command line. That's the workaround that fixes it for me.

Here's an example I've used for testing:
CUDA_VISIBLE_DEVICES=-1 /usr/local/bin/whisper --threads 2 --language en --device cpu --output_format srt --model small --suppress_tokens "" clip_124_21544.wav

If you're not using the command line, I guess the same thing can be accomplished by changing the default value of suppress_tokens from -1 to "" in code.