You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Claude d7e2ecd042 fail fast in startup check when ffmpeg executable is missing ... On Windows, when the ffmpeg/ffprobe executable does not exist (e.g. a custom FFmpeg directory pointing to a location without ffmpeg.exe), cross-spawn (used by execa) falls back to running the command through cmd.exe, which fails with exit code 1 and a confusing "'...' is not recognized as an internal or external command" error instead of ENOENT. This bypassed the "FFmpeg executable not found" dialog and instead triggered the error report dialog. Now check that the executables exist as part of the startup check (which also re-runs whenever the custom FFmpeg directory setting changes), so a missing executable yields a proper ENOENT. Also mention the custom FFmpeg directory setting in the error dialog when one is configured. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PE6aFnysh85Ryndeu6zXYG		2 months ago
..
translation.json	fail fast in startup check when ffmpeg executable is missing	2 months ago