#8711 F5-TTS(Built-in): No audio file was generated during the listening test.self=[F5TTSBuilt]: uuid=None, proxy_str=None, tt

2800**fb33 Posted at: 11 hours ago

F5-TTS(Built-in): No audio file was generated during the listening test.
self=[F5TTSBuilt]: uuid=None, proxy_str=None, tts_type=2, len=1, language='es-419', play=True, volume='+0%', pitch='+0Hz', rate='+0%', speed=1.0, has_done=0, wait_sec=0.0, dub_nums=1, error='No audio file was generated during the listening test.', api_url='', is_cuda=False, local_dir='C:/Users/Jonathan/Music/win-pyvideotrans-v4.08-0802/models/models--jpgallegoar--F5-Spanish', is_redubb=False, model_name='', ainame=None
{'text': '¡Hola, mi querido amigo! ¡Espero que cada uno de tus días sea hermoso y agradable!', 'rate': '+0%', 'role': 'voz_mex_MarioCastaneda.wav', 'filename': 'C:/Users/Jonathan/Music/win-pyvideotrans-v4.08-0802/tmp/45520/listen_voice/2-es-419-1794113907.1048012.wav', 'tts_type': 2, 'language': 'es-419', 'volume': '+0%', 'pitch': '+0Hz'}
Traceback (most recent call last):
File "videotrans\util\ListenVoice.py", line 22, in run
File "videotrans\tts\__init__.py", line 132, in run
File "videotrans\tts\_base.py", line 125, in run
videotrans.configure.excepts.DubbingSrtError: No audio file was generated during the listening test.
self=[F5TTSBuilt]: uuid=None, proxy_str=None, tts_type=2, len=1, language='es-419', play=True, volume='+0%', pitch='+0Hz', rate='+0%', speed=1.0, has_done=0, wait_sec=0.0, dub_nums=1, error='No audio file was generated during the listening test.', api_url='', is_cuda=False, local_dir='C:/Users/Jonathan/Music/win-pyvideotrans-v4.08-0802/models/models--jpgallegoar--F5-Spanish', is_redubb=False, model_name='', ainame=None


=
system:Windows-10-10.0.26300-SP0
version:v4.17
frozen:True
language:en_US
root_dir:C:/Users/Jonathan/Music/win-pyvideotrans-v4.08-0802

1 Replies

#1 DeepSeek reply at 11 hours ago

The "No audio file was generated during the listening test." error means the F5-TTS subprocess ran but produced no wav at tmp/45520/listen_voice/...wav. The traceback is truncated and does not show the underlying cause, but for F5-TTS (Built-in) there are only a few possible reasons, and your log already reveals two concrete red flags:

Red flag 1 — Version/installation mismatch
version:v4.17 but root_dir:...win-pyvideotrans-v4.08-0802. The sp.exe/videotrans files were overwritten by a patch on top of an old v4.08 package, and _internal was almost certainly not fully overwritten. A missing or stale dependency under _internal makes built-in TTS subprocesses exit silently without writing the audio file.

  1. Delete the folder, download the full latest package (not the patch) and extract it fresh to a short English path such as D:/pyvideotrans.
  2. If you must patch, copy every file and folder from the patch (sp.exe, _internal, videotrans), then delete all __pycache__ folders inside _internal before overwriting.

Red flag 2 — Reference audio (role: voz_mex_MarioCastaneda.wav)
The listen test is using a clone-style reference wav. If that file does not meet F5-TTS requirements, the model returns nothing.

  1. Confirm the file exists in software directory/f5-tts/.
  2. It must be mono WAV, 3–10 seconds, clear speech, no background noise.
  3. It must be registered in Menu → TTS Settings → Set Reference Audio in the exact format voz_mex_MarioCastaneda.wav#the text actually spoken in this wav. A wrong/missing text mapping causes the generation to fail silently.
  4. Re-test after temporarily selecting a non-clone voice in the Voices dropdown, to isolate whether the reference audio is the culprit.

Other checks, in order

  1. Model完整性: models/models--jpgalejoar--F5-Spanish is a 5.4GB model. Open the folder and verify all files are present (model.safetensors, config, vocab, etc.) and that no file is 0 bytes or named xxx(2).safetensors. A failed download is the most common cause of "no audio generated". If incomplete, delete the folder and re-download manually from https://huggingface.co/jpgallegoar/F5-Spanish/tree/main into software directory/models/models--jpgallegoar--F5-Spanish.
  2. Language code: you are using es-419 (Latin American Spanish). Try setting Target to plain Spanish (es) so the channel maps to the Spanish model without ambiguity, then re-test the Listen button.
  3. Check the real error: open logs/YYYYMMDD.log in the software directory and look at the lines immediately before the DubbingSrtError — the actual exception (missing file, shape mismatch, CUDA error) will be there. If nothing useful appears, check whether _internal contains the f5/torch libraries.

If after a clean full-package install and a valid reference wav it still produces no audio, send the last ~30 lines of the log file from the logs/ folder so the underlying exception can be identified.

Please refer to the related documentation:

Thinking...
Post Your Reply
If you have more than 50 messages, you will no longer receive an automatic reply. Please ask a new question!
Open source and free maintenance is not easy. If this project is helpful to you, please consider making a small donation to help the project continue to maintain and update.

Dondate via ko-fi.com

Related resource