I’m trying to modernize my video library, and ran into a crash when rendering a zone with one of the clips.
Is this intended behavior? Can it be fixed in kdenlive? Or, what would be the proper way to fix this?
Rendering of /mnt/Home/Videos/video.mp4 crashed
Qt: Session management error: Could not open network socket
[matroska,webm @ 0x7f7cdc658900] File extends beyond end of segment.
[matroska,webm @ 0x7f7cdc0a9b40] File extends beyond end of segment.
[mp4 @ 0x7f7cd8000f40] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [mp4 @ 0x7f7cd8000f40] Encoder did not produce proper pts, making some up.
QThreadStorage: Thread 0x555a98554650 exited after QThreadStorage 8 destroyed QThreadStorage: Thread 0x555a98554650 exited after QThreadStorage 6 destroyed QThreadStorage: Thread 0x555a98554650 exited after QThreadStorage 1 destroyed
Rendering of /mnt/Home/Videos/video.mp4 aborted, resulting video will probably be corrupted.
I haven’t looked in detail at how the render server works yet, but I don’t think that’s a ‘crash’ in kdenlive (despite the kdenlive error message using that word), or anything that can (or “needs to be”) be fixed in kdenlive …
That’s just kdenlive, handling mlt, handling ffmpeg choking on your original source file, as best as they each can in that case. There’s not much else we can do at this level - unless in future we also become a wrapper around various file repair tools, but that’s probably a bit out of scope.
How was this file recorded? My first guess would be that it was a streaming capture that ended abnormally without updating the file metadata. You probably want to look at what mkv/webm repair tools are available for your platform and see what they can do to fix this issue with the file.