-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while cuting an MKV video file in Windows 10 #14
Comments
Can you open developer tools using CTRL+SHIFT+I or F12 before triggering the error, and include the output from the Console? |
I can not share the video, it's too big (200MB). Output from the Console: C:\Users\srmp\Desktop\LosslessCut-win32-x64\resources\app.asar\renderer.js:81 Load C:\Users\srmp\Desktop\video.mkv |
Can you open CMD and run: ...And show the output? I will add this ffmpeg output to javascript console in a later release 📝 |
C:\Users\srmp>C:\Users\srmp\Desktop\LosslessCut-win32-x64\resources\app.asar.unpacked\ffmpeg\ffmpeg.exe -i C:\Users\srmp\Desktop\video.mkv -y -vcodec copy -acodec copy -ss 107.085721 -t 42.508196999999996 -f webm C:\Users\srmp\Desktop\video.mkv-00.01.47.085-00.02.29.593..mkv |
Thanks. It seems FFMPEG doesn't want to put H264 video with AAC audio into a WebM file. As far as I understand that is outside the spec of the WebM format (which only supports VP8 or VP9 video.) |
Torrent for download of sample video attached. |
I have investigated and found out that the library that I'm using to detect file type detects mistakenly detects this file as webm. |
Fixed in 2189871 and in 1.3.0 |
E:\Downloads\LosslessCut-win32-x64\resources\app.asar\ffmpeg.js:18 Error: spawn undefined ENOENT
at notFoundError (E:\Downloads\LosslessCut-win32-x64\resources\app.asar\node_modules\cross-spawn\lib\enoent.js:11)
at verifyENOENT (E:\Downloads\LosslessCut-win32-x64\resources\app.asar\node_modules\cross-spawn\lib\enoent.js:46)
at ChildProcess.cp.emit (E:\Downloads\LosslessCut-win32-x64\resources\app.asar\node_modules\cross-spawn\lib\enoent.js:33)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215)
The text was updated successfully, but these errors were encountered: