Skip to content
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

[FEATURE REQUEST] Add a command line parameter to restart the encoding of .mux file after failure #71

Open
AXDOOMER opened this issue Feb 5, 2022 · 1 comment

Comments

@AXDOOMER
Copy link

AXDOOMER commented Feb 5, 2022

Kazam needs a command line parameter to restart the encoding process from a .mux file.

Failure of encoding the final file happens when there isn't enough disk space, when the program crashes or when the computer is shutdown.

Without this, recordings are lost upon failure and there is no way to recover them.

@niknah
Copy link

niknah commented Feb 6, 2022

Go to preferences and change the file format to vp8/webm, the temporary file from that can be used if something goes wrong with it half way.

If you have the .mp4 file but it's truncated. Get the header from that file and put it together with the .mux file. Use a program like "hexdump" to look for the "mdat" string. This was the end of the header in my video at byte 0x7d1 (2001)

Run this (kazam_zb8uew40.movie.mux is the name of the truncated .mux file)
(dd count=1 bs=2001 if=/tmp/TruncatedVideo.mp4; cat ~/Videos/kazam_zb8uew40.movie.mux ) >/tmp/recovered.mp4

The .mux file looks like a .h264 file. If you run the example from https://linux.die.net/man/1/ffmpeg
ffmpeg -i h264.mp4 -vcodec copy -vbsf h264_mp4toannexb -an out.h264
It'll create a .h264 file that has the same header. But unfortunately, I am unable to open aborted .mux files with anything.

Duplicate of #30
Duplicate of #2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants