invalid name_: ����
`root@arquivos0:~/tmp/untrunc-master# ./untrunc -a -vv -s anderson.mp4 WARNING: Because of internal decoder changes, using ffmpeg '3.4.6-0ubuntu0.18.04.1' with '-s' can be slow! You are advised to compile untrunc against ffmpeg 3.3! See the README.md on how to do that. Press [ENTER] to continue ... Info: version '' using ffmpeg '3.4.6-0ubuntu0.18.04.1' Info: reading anderson.mp4 Info: parsing healthy moov atom ... requests: 4 at offset : 0 requests: 4 at offset : 4 start_ = 0 length_ = 4294967295 name_ = ����
invalid name_: ����`
Is anyone able to help with what this "invalid name" might mean, and if there's any way to resolve it?
MP4s consist out of atoms. Atoms have fixed names and positions. If at such a position no ascii string is found, it is can't be a valid name.
Have you looked whether the file contains actual information?
If it does try untrunc -f anderson.mp4.
I'm actually using your own fork, as I couldn't get this one to compile on Ubuntu 18.04.
-f doesn't seem to be a valid option...
options: -V - version -s - skip/ignore unknown sequences -a - analyze -i - info -v - verbose -vv - more verbose -q - only errors -n - no interactive
-a & -i both return the same info I supplied above. -V just provides an empty version string, however it's the latest release from your repo from last week.
version '' using ffmpeg '3.4.6-0ubuntu0.18.04.1'
BTW, there are two corrupt files I'm trying to fix, one 1GB & one 4GB. I managed to extract 1 minute of video from the 4GB file at least. Both of them supposedly have the same missing/corrupt moov atom problem.
You should always pull new commits before reporting issues. And you should report issues to the fork you are using, e.g. not here. Update untrunc and then try again.