1) There are a lot of possible combination to try. If an error correction code was used then that information could possibly allow us to discard some of them (e.g. if a single-error correcting code was used at the bit level, then any single-bit flips will have already been fixed and don't need to be tried, and there may be a more limited number of combinations of flipped bits to check).
Quote from: arnezami on 05/29/2014 04:12 pmQuote from: Lourens on 05/29/2014 12:39 pmarnezami, could you post a patch? I was about to start doing the exact same thing . Hopefully the additional output will allow a kind of guided bit flipping, where we can quickly discard flips that yield obvious nonsense.@Lourens: I will try but there are still quite a few problems with this version I noticed. For example you can see that bits are missing. Thats not good . It's also very hacky atm. Will keep you updated.Okay, I'll go and have a look at the FFmpeg source myself as well, will post when I have something.
Quote from: Lourens on 05/29/2014 12:39 pmarnezami, could you post a patch? I was about to start doing the exact same thing . Hopefully the additional output will allow a kind of guided bit flipping, where we can quickly discard flips that yield obvious nonsense.@Lourens: I will try but there are still quite a few problems with this version I noticed. For example you can see that bits are missing. Thats not good . It's also very hacky atm. Will keep you updated.
arnezami, could you post a patch? I was about to start doing the exact same thing . Hopefully the additional output will allow a kind of guided bit flipping, where we can quickly discard flips that yield obvious nonsense.
Maybe. Currently the mmb-command work in the "scope" after the VOP-quant etc have been decoded. Maybe/probably we are too late there. So I'm not sure if it's possible using the mmb-commands. But maybe using a different command. @michaelni: do you know how to do this?
@arnesami - should we adopt a numbering convention of PART.FRAME like 10.01 - 10.20? This allows for new pFrames to be found without changing all frames after.
The latest TS files have been added to the online editor
This is why we needed a youtube version Elon Musk @elonmusk 4m More Amazing repair job of Falcon 9 ocean landing vid by @NASASpaceflight forum. Now shows leg deploy http://www.youtubeTotally distracted me during Soyuz docking. I hope he doesn't do that again! ( Joke!)Again, that's all deserved for what you guys are doing. It's direct praise from one of the most important people on the planet right now. You're a motivated bunch, but I'm sure that helps while you dig through all these bytes of data
UPDATE (5/28/2014)Members of NASASpaceFlight.com's forum are continuing to make great progress with the frame by frame repair of the Falcon 9 first stage soft splashdown in the Atlantic Ocean.
Quote from: IainCole on 05/29/2014 06:50 pmThe latest TS files have been added to the online editorIf possible, could you add the new .ts to the older spacex.slapbet.org version of the editor? The "iFrame only" online tool is MUCH faster to work with. I believe we are back to square one on the iFrame mmps.Thank you.
Quote from: mhenderson on 05/29/2014 07:40 pmQuote from: IainCole on 05/29/2014 06:50 pmThe latest TS files have been added to the online editorIf possible, could you add the new .ts to the older spacex.slapbet.org version of the editor? The "iFrame only" online tool is MUCH faster to work with. I believe we are back to square one on the iFrame mmps.Thank you.If someone who knows how to do it can generate the mp4-img files for the iframes then I can add them to the old editor.
./ffmpeg -i fixed_edit8_part_169.ts -vcodec copy -an -f image2 fixed_edit_part_169_%d.mpg4-img
Quote from: IainCole on 05/29/2014 08:09 pmQuote from: mhenderson on 05/29/2014 07:40 pmQuote from: IainCole on 05/29/2014 06:50 pmThe latest TS files have been added to the online editorIf possible, could you add the new .ts to the older spacex.slapbet.org version of the editor? The "iFrame only" online tool is MUCH faster to work with. I believe we are back to square one on the iFrame mmps.Thank you.If someone who knows how to do it can generate the mp4-img files for the iframes then I can add them to the old editor.You can do this:Quote./ffmpeg -i fixed_edit8_part_169.ts -vcodec copy -an -f image2 fixed_edit_part_169_%d.mpg4-imgThis assumes you have fixed_edit8_part_169.ts and produces .mp4-img files. In this case you want the first one "fixed_edit_part_169_1.mpg4-img" since it's the I-frame. You can throw away the other mpg4-img files, since these are the P-frames.And you have to do this for each of the 15 ts-parts.
Quote from: arnezami on 05/29/2014 08:50 pmQuote from: IainCole on 05/29/2014 08:09 pmQuote from: mhenderson on 05/29/2014 07:40 pmQuote from: IainCole on 05/29/2014 06:50 pmThe latest TS files have been added to the online editorIf possible, could you add the new .ts to the older spacex.slapbet.org version of the editor? The "iFrame only" online tool is MUCH faster to work with. I believe we are back to square one on the iFrame mmps.Thank you.If someone who knows how to do it can generate the mp4-img files for the iframes then I can add them to the old editor.You can do this:Quote./ffmpeg -i fixed_edit8_part_169.ts -vcodec copy -an -f image2 fixed_edit_part_169_%d.mpg4-imgThis assumes you have fixed_edit8_part_169.ts and produces .mp4-img files. In this case you want the first one "fixed_edit_part_169_1.mpg4-img" since it's the I-frame. You can throw away the other mpg4-img files, since these are the P-frames.And you have to do this for each of the 15 ts-parts.You may ignore my request. I found a quick fix that makes the newer online editor much more responsive ... null out the pFrames by adding this to the mmb for the full sequence. It quickly redraws the iFrame.=FRAME1:0:0:-1=FRAME2:0:0:-1=FRAME3:0:0:-1=FRAME4:0:0:-1=FRAME5:0:0:-1=FRAME6:0:0:-1=FRAME7:0:0:-1=FRAME8:0:0:-1=FRAME9:0:0:-1=FRAME10:0:0:-1=FRAME11:0:0:-1=FRAME12:0:0:-1=FRAME13:0:0:-1=FRAME14:0:0:-1=FRAME15:0:0:-1=FRAME16:0:0:-1=FRAME17:0:0:-1=FRAME18:0:0:-1=FRAME19:0:0:-1Sorry, I was thinking inside the box. Mike
Quote from: moralec on 05/29/2014 03:40 pmQuote from: Lourens on 05/29/2014 12:39 pmarnezami, could you post a patch? I was about to start doing the exact same thing . Hopefully the additional output will allow a kind of guided bit flipping, where we can quickly discard flips that yield obvious nonsense.Yes we can do that. I'll put the current pages on archive and create new empty ones. @moralec: I think you meant to reply on this post by SwissCheese (quoted below) right? (instead of Laurens post)@moralec/SwissCheese: would it be a good idea to number the I-frames to 1,21,41,61 etc? And the P-frames in between? Since we expect each I-frame to contain exactly 19 P-frames right?
Quote from: Lourens on 05/29/2014 12:39 pmarnezami, could you post a patch? I was about to start doing the exact same thing . Hopefully the additional output will allow a kind of guided bit flipping, where we can quickly discard flips that yield obvious nonsense.Yes we can do that. I'll put the current pages on archive and create new empty ones.
Quote from: Lourens on 05/27/2014 07:11 pm1) There are a lot of possible combination to try. If an error correction code was used then that information could possibly allow us to discard some of them (e.g. if a single-error correcting code was used at the bit level, then any single-bit flips will have already been fixed and don't need to be tried, and there may be a more limited number of combinations of flipped bits to check).You miss that a FEC code capable to fix n bit errors, does fix them for the transmitted packet/message, while the transmitted packet is made up of data and parity symbols in a systematic code or at least more symbols than there are data symbols in the more generic case. Thus for example a 1-3 bit correcting FEC code could fix 3 bits in the transmitted packet but there might be just 1 or eve none of these in the data part. We only have the data part of the packets, not the parity part. Also if in that same example there are 4 bit flips, the FEC decoder might actualy (depending on what type of code and implementation it is) add more errors.
Quote from: Lourens on 05/29/2014 04:50 pmQuote from: arnezami on 05/29/2014 04:12 pmQuote from: Lourens on 05/29/2014 12:39 pmarnezami, could you post a patch? I was about to start doing the exact same thing . Hopefully the additional output will allow a kind of guided bit flipping, where we can quickly discard flips that yield obvious nonsense.@Lourens: I will try but there are still quite a few problems with this version I noticed. For example you can see that bits are missing. Thats not good . It's also very hacky atm. Will keep you updated.Okay, I'll go and have a look at the FFmpeg source myself as well, will post when I have something.Hi Lourens,In that case this will probably help. This is my hacky version based on an older version of h263dec.c Mostly mpeg4videodec.c is changed though. Watch for "BITLOG".For everyone: this is not meant to be merged directly with any repository! It's just experimental stuff.Regards,arnezami
1) Thread currently at >252,000 reads which puts it at 15th most read SpaceX thread of all time and 13th most read SpaceX conversation[1]. See original link for images of the overall ranking.
Quote from: IainCole on 05/29/2014 06:50 pmThe latest TS files have been added to the online editorFollowing this update the wiki now has 16 new (empty) pages for you all to upload your progress on each frame. I followed the same structure as last time (one main page, and 15 secondary pages). Please bookmark http://spacexlanding.wikispaces.com/raw_final_fixedMMB The old pages are still available *look under OLD/ARCHIVED in the homepage*. They have all the MMB codes we were able to obtain from the previous ts files. Many of them should work (specially from those sections that already had 19 p-frames in the previous version). However, please take into account that frame numbers have changed as new p-frames where discovered. A good way to orient yourself is using the 15 I-frames that remain the same. Good luck! And for those anxiously waiting for the Dragon II event tonight, remember that working on p-frames is a fantastic way to kill time.
I filled in this page: http://spacexlanding.wikispaces.com/Frames+Part+10
Never in the history of space flight was a thread read by so many who understood so little... ;-)
Quote from: arnezami on 05/30/2014 03:06 amI filled in this page: http://spacexlanding.wikispaces.com/Frames+Part+10I've been meaning to ask... what's the story behind the big grey rectangles in frames 186-188? Can you tell if it's an MPEG error or an NTSC video camera error?