I was thinking about the movie, could someone with some artistic talent (not my case ) make 1-2 title images, and maybe also some credits images at the end (for example a few before/after images, printscreens of the wiki, web application, ...)? It should have the same format as the images, i.e. 704x480.
Hi allive added a new option to the custom ffmpeg on github, -debug mb_pos_bruteforce
I think what would also be very useful is to able to tell ffmpeg only to decode either luminosity, chrom1 or chrom2. So either only the first 4 dc's are decoded or only the fifth or only the sixth.Then we can add 3 checkboxes in the online version. That way you can much more clearly see where things go wrong colorwise or intensity wise. Without our eyes being districated by either the intensity or (one of) the two colors.
for i in {8800..9064} ; do for j in {8801..9065} ; do ffmpeg.exe -debug mb_pos_size -s:0 704:480 -mmb X:76768:80,X:22120:80,X:45038:80,X:42196:80,X:66234:80,X:50298:80,X:$i:80,X:$j: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::63,10:28:80196 -i iframe52.mpg4-img 2> output-$i-$j.txt -f image2 /dev/null -y ; done ; done
I've been attempting to tune this bash script, with an eye towards performance.This script is searching for two bits between 8800 and 9065 on frame 52. It's a lot of combinations, and I am getting roughly 600 frames per minute.Quotefor i in {8800..9064} ; do for j in {8801..9065} ; do ffmpeg.exe -debug mb_pos_size -s:0 704:480 -mmb X:76768:80,X:22120:80,X:45038:80,X:42196:80,X:66234:80,X:50298:80,X:$i:80,X:$j: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::63,10:28:80196 -i iframe52.mpg4-img 2> output-$i-$j.txt -f image2 /dev/null -y ; done ; doneThe output images have been entirely disabled, and the directive to ignore errors has been removed. I am not 100% sure that the latter is "safe" but it does significantly increase the speed of the process.Note that there are spaces in the mmb string that would need to be removed to run this.After the run is done, I first do a grep for 42:03:9061 , then a grep for 00:29:81738 . The second one is just in case the first "known good" position ends up changing due to correctly flipped bits. Edit: This second test is probably worthless.If anybody has suggestions for how to speed this up, I am all ears! The search space can likely be reduced but I'm really unsure of what would be advisable.Just sticking to two bits right now... going for three in a search space this size would take something like 21 days at a rate of 600 tries per minute.
you could pipe output of the for loop to grep so you don't create temp files. dunno how much will this save in terms of performance.
for i in {8800..9009} ; do for j in $(eval echo "{$(($i+1))..9010}") ; do ffmpeg.exe -debug mb_pos_size -s:0 704:480 -mmb X:76768:80,X:22120:80,X:45038:80,X:42196:80,X:66234:80,X:50298:80,X:$i:80,X:$j: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::63,10:28:80196 -i iframe52.mpg4-img 2> output-$i-$j.txt -f image2 /dev/null -y ; done ; done
For what it's worth, I'm running at about 750 calls per minute, with all output to a RAM disk and subsequent call to a separate program to analyse the resulting image. This is on GNU/Linux on a three year old laptop, with ignore errors enabled. Putting intermediate output on a RAM disk may help a bit, since disk writes are slow. Beyond that I think it's probably mostly the overhead of starting up FFmpeg all the time.
<snip>You've also got a fan in Elon. He's been full of praise for the video work.
I was thinking about the movie, could someone with some artistic talent (not my case ) make 1-2 title images, and maybe also some credits images at the end (for example a few before/after images, printscreens of the wiki, web application, ...)? It should have the same format as the images, i.e. 704x480.Edit: a first version of a movie with all recovered frames (the other are not used)
Legs for days....http://spacexlanding.wikispaces.com/Frames+72-91
heyo, seems like theres some sort of small flame event on frames 74 and 75. is from that the engines or perhaps do the legs have some sort of pyrotechnic release system? thought it was odd since it was so brief.
Newbie here - I have experience working with MPEG-TS streams and I've written a few custom tools that can fix corruption at the transport stream layer. Is it worth me working on the split TS files that shanuson created from the raw edit8.ts?I've run his files through the tools, and they fix a lot of stuff like bad PIDs, bad program continuity counters, wrong adaptation field lengths, things like that. The start positions of various badly-corrupted P-frames become visible, but they're still quite damaged.I guess I'm asking, would the recovery effort benefit from this?