Okay, so I spent a not so little while on the p-frames following 52 and I got 1 (one!) frame fixed...and I don't even know if I did this right It's really tedious, because there's almost no difference between frames 52 and 53, so there's almost no information for the lower part of the p-frame (which makes sense, but it makes it a lot more difficult to find markers...). In the lower part of the frame, you can just barely make out the shape of the rocket, but it took a while until I realized that I really wish the legs were extended at this point 22:15:36982,30:15:-1,0:16:38358,25:17:-1,41:18:46765Off-topic: Good luck to people who used to make a living out of repairing video files...I guess customers might no longer accept "a 50% chance of recovering one or two frames" as an answer after seeing the latest gifs from this video
Quote from: Untribium on 05/22/2014 01:04 amOkay, so I spent a not so little while on the p-frames following 52 and I got 1 (one!) frame fixed...and I don't even know if I did this right It's really tedious, because there's almost no difference between frames 52 and 53, so there's almost no information for the lower part of the p-frame (which makes sense, but it makes it a lot more difficult to find markers...). In the lower part of the frame, you can just barely make out the shape of the rocket, but it took a while until I realized that I really wish the legs were extended at this point 22:15:36982,30:15:-1,0:16:38358,25:17:-1,41:18:46765Off-topic: Good luck to people who used to make a living out of repairing video files...I guess customers might no longer accept "a 50% chance of recovering one or two frames" as an answer after seeing the latest gifs from this video That's quite good A few general advices:- There are usually easy-to-recover p-frames, it's better to begin with these ones, they will then give a reference for the harder-to-correct ones.- Use the p-frames before and after to edit the actual one, it helps a lot, lots of moving features are at a very close position and help get the MB sequences at the right place.- Before doing any correction, note the first bit position of all sequences of MB that look "good", then try to put them at the right position.- If you are not 100% sure of a MB sequence, it's better to fill with 0:0:-1, as no change from the previous frame is better than a wrong change.
[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:511, End:646, Size:135, dQP:-2[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:512, End:707, Size:195, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:513, End:685, Size:172, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:514, End:690, Size:176, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:515, End:646, Size:131, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:516, End:656, Size:140, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:517, End:646, Size:129, dQP:0
Hi allive added a new option to the custom ffmpeg on github, -debug mb_pos_bruteforceThis will list all bitstream positions, start, end, size for any correctly decodeable MB.With this you can quickly find a MB that ends at a specified position or even perform some statistical analysis on the start/end positions, maybe automating the finding of more likely valid chainsExample:Quote[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:511, End:646, Size:135, dQP:-2[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:512, End:707, Size:195, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:513, End:685, Size:172, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:514, End:690, Size:176, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:515, End:646, Size:131, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:516, End:656, Size:140, dQP:0[mpeg4 @ 0x7f04c0001540] MB pos brute: F#:0, PTS:0, Start:517, End:646, Size:129, dQP:0
How do we download / install the tool from github? Are there instructions for installing that app on a Windows box? Do I need a Linux VM? On a scale of 1 to 10, I am a 2 in Linux.
for i in {8800..9100} ; do ffmpeg.exe -threads 1 -debug mb_pos_size -err_detect ignore_err -s:0 704:480 -mmb X:76768:80,X:22120:80,X:$i:80,0:7:-2:-10:-10:-10:-10:8:-5,2:7:15506,9:7:-1,15:7:16391,17:7:-1, 28:7:16704,35:7:-2:-10:-10:-10:-10:8:-5,29:9:21074,34:9:-1,39:9:21626,5:28:-1,10:28:80196 -i iframe52.mpg4-img -f image2 img-%03d-$i.png 2> output-$i.txt ; done
for i in {8800..9100} ; do ffmpeg.exe -threads 1 -debug mb_pos_size -err_detect ignore_err -s:0 704:480 -mmb X:76768:80,X:22120:80,X:$i:80,X:$(($i+14)):C0,0:7:-2:-10:-10:-10:-10:8:-5,2:7:15506, 9:7:-1,15:7:16391,17:7:-1,28:7:16704,35:7:-2:-10:-10:-10:-10:8:-5,29:9:21074,34:9:-1,39:9:21626,5:28:-1,10:28:80196 -i iframe52.mpg4-img -f image2 img-%03d-$i.png 2> output-$i.txt ; done
So having an issue with the editor atm. Basically the new -3 instead of -1 thing doesn't seem to work... even though it works when I'm running it on my test rig....Makes... no... sense.....
Hi alli updated github with some bugfixes and new features for P frames-1 and -2 should now work like they do for I frames and allow messing with DC values-3 results in a skiped block (this is what -1 was effectively before it worked so you have to replace -1 by -3 in old mmbs for P frames)-4 makes it a inter MB with 1 motion vectorexample: 24:10:-4:1:130:20:-3
Found another bit flip in iframe 52: X:45038:80 relative to iframe52.mpg4-img improves the chroma in the bottom right corner. There are for sure a bunch of other bit flips that are causing the dark spot at bottom right, but it's difficult to find them. I have an idea for potentially automating this search though...maybe on the weekend.