Dr. Neal Krawetz

May be due to a bad build. My build process: ``` rm -f Cargo.lock git pull cargo update cargo build --bin c2patool --target x86_64-unknown-linux-musl --release # Output: # ./target/x86_64-unknown-linux-musl/release/c2patool ./target/x86_64-unknown-linux-musl/release/c2patool...

May be due to a bad build. My build process: ``` rm -f Cargo.lock git pull cargo update cargo build --bin c2patool --target x86_64-unknown-linux-musl --release # Output: # ./target/x86_64-unknown-linux-musl/release/c2patool ./target/x86_64-unknown-linux-musl/release/c2patool...

May be due to a bad build. My build process: ``` rm -f Cargo.lock git pull cargo update cargo build --bin c2patool --target x86_64-unknown-linux-musl --release # Output: # ./target/x86_64-unknown-linux-musl/release/c2patool ./target/x86_64-unknown-linux-musl/release/c2patool...

Agreed, it should. I downloaded and recompiled c2patool 0.25.0 and tested using it. My build code: ``` rm -f Cargo.lock git pull cargo update cargo build --bin c2patool --target x86_64-unknown-linux-musl...

I just built from a new directory, rather than trying to upgrade a previous directory. `c2patool --version` still says "c2patool 0.25.0", but the error is gone. The update and build...

It appears to be fixed. The problem was that a simple update and build was not enough. The update left behind residues that retained the problem.

c2patool fails to recognize .m4v, .3gp, and other common mp4/mov compatible files. Renaming the files to .mp4 or .mov allows them to be processed. If the code used 'magic' to...