Error using VAD "none" option

#10
by Robis - opened

When transcribing with VAD "none", recently it started to throw an error.

I'm using Google Colab.

Model: Large
Language: English
Youtube link (tried also mp3, same thing)

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/gradio/routes.py", line 298, in run_predict
    iterators=iterators,
  File "/usr/local/lib/python3.7/dist-packages/gradio/blocks.py", line 1007, in process_api
    result = await self.call_function(fn_index, inputs, iterator, request)
  File "/usr/local/lib/python3.7/dist-packages/gradio/blocks.py", line 849, in call_function
    block_fn.fn, *processed_input, limiter=self.limiter
  File "/usr/local/lib/python3.7/dist-packages/anyio/to_thread.py", line 32, in run_sync
    func, *args, cancellable=cancellable, limiter=limiter
  File "/usr/local/lib/python3.7/dist-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/usr/local/lib/python3.7/dist-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/content/whisper-webui/app.py", line 92, in transcribe_webui
    result = self.transcribe_file(model, source, selectedLanguage, task, vad, vadMergeWindow, vadMaxMergeSize, vadPadding, vadPromptWindow)
  File "/content/whisper-webui/app.py", line 151, in transcribe_file
    result = whisperCallable(audio_path, 0, None, None)
TypeError: 'WhisperCallback' object is not callable

Oops, this is the downside of having so many options (VAD/no VAD, Parallel execution on GPU/CPU, CLI/Web UI, etc.) ... I forgot to test the "None" VAD when the model is not executed in parallel.

But it should be fixed now:

If you run the "Optional: Update Git repository" (git pull origin) command, you should get the fix in your Google Colab instance. Or you can also run "Disconnect and delete runtime", and then run "!git clone" again.

Thanks, I will try to test as soon as I get a chance.

Working as expected. Thank you for the quick fix! ๐Ÿ’Ž

aadnk changed discussion status to closed

Sign up or log in to comment