Can't work with .MOV files? #1932
Comments
|
Thanks for sharing the file. I can confirm that Losslesscut is just showing a black video with audio only. What's odd is that the HTML5 video element is not even giving off any error, so there is seemingly no way for LosslessCut to know that the video is unplayable. Unfortunately this is probably a bug in Chrome/Chromium (which is used by Losslescut), so not much I can do about it. I also tried to play the same file in Google Chrome and it just shows a blank video as well: <html>
<body>
<video controls src="SCHD0262.MOV" />
</body>
</htmlI tested in Safari on Mac and it works. So it's definitely a Chromium bug. As a workaround for this file you can convert it to a supported format in LosslessCut: File -> Convert to supported format -> "Fastest: Low playback speed" or "Slow: Low quality encode" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The fewer issues I have to read, the more new features I will have time to implement, so I ask that you please try these things first
Steps to reproduce
Was really enjoying this program trimming clips to exports from my MP4 files, then I came across the MOV files and can only hear the audio. Did I miss something about these not being supported?
Expected behavior
Show me the video
Actual behavior
Only hear audio, blank screen
Provide an error report
No error occurred.
{
"state": {
"ffmpegExperimental": false,
"preserveMovData": false,
"movFastStart": true,
"preserveMetadataOnMerge": false,
"filePath": "",
"externalFilesMeta": {},
"mainStreams": [],
"copyStreamIdsByFile": {},
"cutSegments": [
{}
],
"mainFileFormatData": {},
"rotation": 360,
"shortestFlag": false,
"effectiveExportMode": "separate",
"outSegTemplate": "${FILENAME}-${CUT_FROM}-${CUT_TO}${SEG_SUFFIX}${EXT}"
},
"platform": "win32",
"version": "3.59.1"
}
Share the file
https://drive.google.com/drive/folders/1U4VIVgTJ5q2qcOnTIJst67dY1f3BdKLT?usp=sharing
Share log from developer tools
Don't understand this
The text was updated successfully, but these errors were encountered: