Common Issues & Known Bugs

Common Errors & Fixes

1. CUDA Not Available

• Symptom: You receive a message about CUDA being unavailable, or notice high CPU usage during ingest.
• Cause: Onset Engine attempts to use an NVIDIA GPU for AI inference (CLIP models). If you don’t have a supported NVIDIA GPU, or if the CUDA toolkit is not properly installed, it will fail to initialize.
• Fix: No action is needed. The application will automatically fall back to CPU inference. While slower, it is fully functional and supports all features.

2. MPV DLL Not Found

• Symptom: DJ Mode fails to launch, crashing with an error related to mpv or libmpv.
• Cause: The real-time playback engine requires the mpv library to be present.
• Fix: Check your installation directory for the mpv/ folder. Ensure that mpv.exe and libmpv-2.dll are present. If missing, re-extract the application from the original download archive.

3. FFmpeg Not Found

• Symptom: Draft renders fail, or you see FileNotFoundError: ffmpeg / ffmpeg is not recognized.
• Cause: FFmpeg is essential for video extraction and rendering. It is bundled with Onset Engine.
• Fix: Verify the ffmpeg/ folder exists in your Onset Engine installation directory. If missing, re-extract the application from the original download archive.

4. Database Locked Error

• Symptom: An error occurs when attempting to ingest new footage or save a project: sqlite3.OperationalError: database is locked.
• Cause: SQLite allows only one process to write to the database (library.db) at a time. Another instance of Onset Engine, DJ Mode, or a background worker might be accessing it.
• Fix: Close all other running instances of Onset Engine, including any hidden background processes. In rare cases, you may need to restart the application or your computer.

5. HuggingFace Warnings

• Symptom: During launch or ingest, the console displays verbose warnings from the huggingface_hub or transformers libraries (e.g., regarding tokenizers or model deprecations).
• Cause: These are informational messages from the underlying AI frameworks used by Onset Engine.
• Fix: These warnings are purely cosmetic and can be safely ignored. They are typically suppressed in finalized production builds, but may appear in development or un-optimized environments.

Known Issues

The following are known behaviors and limitations of the current release (as documented in the Agent Handoff Document):

• Timeline Thumbnails Blank: If you generate an EDL but subsequently delete the original proxy or source video files, the thumbnails on the timeline will appear blank. This is a data availability issue, not a bug in the application logic. The engine cannot render a thumbnail for a file that no longer exists on disk.
• Debug Prints Visible: In some scenarios, developer debug messages ([DEBUG]) may be printed to the console even without passing the --verbose flag. This will be addressed in a future update.
• Lint Errors (Pyre2): Developers running static analysis (Pyre2) may see false positive errors for local module imports (media_utils, library_db, etc.) because they are not installed in the virtual environment. This does not block development or execution.