Anthon Lockwood
Anthon Lockwood
see https://github.com/anthwlock/untrunc/issues/35
Maybe you want to try this [fork](https://github.com/anthwlock/untrunc).
Hey, I am not the maintainer but I think you add more complexity than needed. Keep in mind that this program is only to be used for repairing mp4 files....
I think one loglevel should be dedicated to the the average user, who doesn't know a lot about MP4s. But sometimes untrunc does not work or you are a developer....
Neither verbose nor debug messages are of interest to the average user. So I'd put them into the same log level.
I used `VV` for the output which is not directly related to untrunc or MP4s. For example output about the buffer in `FileRead` is `VV`.
Well, then let's say I use `VV` when I feel like it's too verbose for `V`. Tbh I didn't take too much time to think about which channel I put...
Hi, If you have windows you can try the automated builds available on [this fork](https://github.com/anthwlock/untrunc). Otherwise I recommend [VirtualBox](https://www.virtualbox.org/wiki/Downloads) with [Xubuntu](https://xubuntu.org/download/). Good luck!
Great! I made the fork for this very reason: too many frustrating problems with untrunc. I updated the donation section: [link](https://github.com/anthwlock/untrunc#donation). Have a great remaining trip!
`untrunc -a ` lets you analyze (`Mp4::analyze`) the codecs inside ok.mp4 It should not change the result of `Mp4::repair`. Future readers should try [this fork](https://github.com/anthwlock/untrunc), it even supports GoPro videos!