-
-
Notifications
You must be signed in to change notification settings - Fork 130
AllTalk V2 Debug Options
erew123 edited this page Nov 22, 2024
·
3 revisions
-
Function and Component-Specific Debug Options
- debug_func, debug_api, debug_tts, debug_tts_variables, debug_narrator, debug_fullttstext
-
Audio Processing Debug Options
- debug_transcode, debug_concat, debug_rvc, debug_openai
-
Usage Tips and Performance Impact
- Usage Tips
- Tracks function entry points throughout the application
- Shows the execution flow and function call hierarchy
- Essential for understanding the program's execution path
- Example:
[AllTalk TTS] Debug debug_func Function entry: generate_audio
Note: When debugging with debug_func
, remember that functions often call other functions. The debug output shows the most recently entered function, but the actual issue might originate in a parent function. For effective debugging, review the sequence of function entries leading up to an error. For example:
[AllTalk TTS] Debug debug_func Function entry: process_text
[AllTalk TTS] Debug debug_func Function entry: clean_text
[AllTalk TTS] Debug debug_func Function entry: generate_audio
[AllTalk TTS] Error in generate_audio
Here, while the error appears in generate_audio
, the root cause might be in how process_text
or clean_text
prepared the data.
- Logs API endpoint interactions and requests
- Shows incoming request data and response statuses
- Useful for troubleshooting API integrations & calls
- Example:
[AllTalk API] Debug debug_api Successfully retrieved 19 available voices
- Monitors core TTS generation processes
- Shows generation progress, timing, and status updates
- Helps diagnose basic TTS generation issues
- Use
debug_openai
for OpenAI TTS generation - Example:
[AllTalk GEN] Debug debug_tts Starting TTS generation for file: output_12345.wav
- Displays detailed TTS generation parameters
- Shows voice settings, language options, and generation parameters etc
- Useful for verifying correct parameter passing
- Example:
[AllTalk GEN] Debug debug_tts_variables temperature: 0.75, pitch: 1.0
- Tracks narrator mode text processing
- Shows how text is split between narrator and character voices
- Helps debug multi-voice generation issues
- Example:
[AllTalk GEN] Debug debug_narrator Narrator voice: voice_A
- Shows complete text being processed for TTS
- Without this, text is truncated to 90 characters in logs
- Useful when troubleshooting long text processing
- Example:
[AllTalk GEN] Debug debug_fullttstext Full text: [entire text content]
- Monitors URL/IP configuration used by Gradio and environment status
- Shows runtime environment (Docker/Colab) and active AllTalk API endpoint set
- Helps diagnose connection issues between Gradio UI and AllTalk's API server
- Example:
[AllTalk TTS] Debug debug_gradio_IP Base URL is set as : http://127.0.0.1:7851/api/voices
- Monitors audio format conversion processes
- Shows input/output formats and transcoding steps
- Useful for troubleshooting audio format issues
- Use
debug_openai
for OpenAI endpoint transcoding - Example:
[AllTalk TTS] Debug debug_transcode Converting wav to mp3
- Tracks audio file concatenation operations within the Narrator
- Shows files being combined and resulting output
- Helps debug multi-part audio assembly
- Example:
[AllTalk TTS] Debug debug_concat Combining files: [file1.wav, file2.wav]
- Monitors RVC (Retrieval-based Voice Conversion) processes
- Shows model loading, voice conversion steps
- Essential for troubleshooting voice conversion issues
- Example:
[AllTalk GEN] Debug debug_rvc Processing with model: character_voice.pth
- Tracks OpenAI API integration
- Shows OpenAI-specific request parameters and responses
- Useful for troubleshooting OpenAI voice generation
- Example:
[AllTalk TTS] Debug debug_openai Using voice: alloy
- Monitors Whisper transcription processes and audio processing
- Shows model loading, audio levels, processing states
- Tracks silence detection and audio preprocessing
- Indicates file saving operations and GPU memory cleanup
- Example:
[AllTalk TTS] Debug debug_transcribe Model loaded on cuda: large-v3
Key monitoring areas:- Model loading/unloading
- Audio energy levels
- Resampling operations
- Memory cleanup
- File save operations
- Audio processing parameters
- Silent segment detection
- GPU memory usage
- Enable multiple debug options together for comprehensive logging
- Use
debug_func
with other options to track execution flow - Enable
debug_fullttstext
only when necessary to avoid log clutter - Combine related options (e.g.,
debug_tts
+debug_tts_variables
) for detailed troubleshooting