Author Topic: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread  (Read 1201639 times)

Offline beancounter

  • Full Member
  • ****
  • Posts: 1249
  • Perth, Western Australia
  • Liked: 106
  • Likes Given: 172
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1160 on: 05/30/2014 04:36 am »
So we are moving to a society where the line is becoming significantly blurred between technology that appears to be magic to the majority leading to a downplaying of the importance of STEM educcation and eventually society regresses back to the discovery of the wheel.   :)
Beancounter from DownUnder

Offline wronkiew

  • Full Member
  • *
  • Posts: 186
  • 34.502327, -116.971697
  • Liked: 105
  • Likes Given: 125
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1161 on: 05/30/2014 04:56 am »
Digit deltas. They are split into two tables because the p-frames often only show half of the rows. By comparing the pixels to the p-frame, you can determine what digits are being displayed even if the previous frame is missing.

Offline wronkiew

  • Full Member
  • *
  • Posts: 186
  • 34.502327, -116.971697
  • Liked: 105
  • Likes Given: 125
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1162 on: 05/30/2014 05:06 am »
On the subject of recovering the images of the clock in the bottom left corner, I think the TS recovery people might be able to help with that!

Thanks for looking into this. I still think that we will have a lot of illegible clock digits, but this would definitely reduce the number. What tools are you using to inspect the packets?

Offline wronkiew

  • Full Member
  • *
  • Posts: 186
  • 34.502327, -116.971697
  • Liked: 105
  • Likes Given: 125
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1163 on: 05/30/2014 06:48 am »

Ok, the first part of this is done. Unfortunately in PNG format the zip file is 85 MB, so trying to auto-upload it to the wiki is probably pushing it. No pun intended. Instead, I put it on Google Drive at this url:

https://drive.google.com/file/d/0B_wTAwfYg03FQ3p2UVlkZE9MckU/edit?usp=sharing

Also on BTSync at B76OWSNRL5HWE47N7SHT4ZIX2B3B63IXT

This is ~250 frames in PNG format generated by scraping the wiki and then running it through ffmpeg. Why is this useful? Well, you can turn these into a movie file with this command:

ffmpeg -y -start_number 40 -i landing_base_set/frame-%03d.png -c:v libx264 -r 15 -pix_fmt yuv420p out.mp4

Also, you can run a batch process on these images to do post-processing or add annotations.

The zip archive will be regenerated every hour if the wiki has seen any updates.

I updated the auto-build script to renumber the frames to follow the wiki. Frames 181-200 are now taken from rawsplit_final.ts.

Also the BTSync share includes a video version with the frame-rate fixed as SwissCheese suggested.

SwissCheese, can you share a PNG of the title card?

Offline arnezami

  • Full Member
  • **
  • Posts: 285
  • Liked: 267
  • Likes Given: 378
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1164 on: 05/30/2014 07:49 am »
Hi guys,

I've been adding pictures to the wiki where no pictures were uploaded and noticed that if you downsized them the original was gone (you couldnt upscale them anymore).

I've now re-uploaded all images to 100% size in:

http://spacexlanding.wikispaces.com/Frames+Part+10
http://spacexlanding.wikispaces.com/Frames+Part+11
http://spacexlanding.wikispaces.com/Frames+Part+12
http://spacexlanding.wikispaces.com/Frames+Part+13
http://spacexlanding.wikispaces.com/Frames+Part+14
http://spacexlanding.wikispaces.com/Frames+Part+15

While you get less of an overview that way it is way easier for somebody else to check the quality of a frame. And quality is what we need most.

So from now on I think it's a good idea just to keep the pictures their original size.

@IainCole: we could sure use a "Save Image"-link ;)

Regards,

arnezami

[edit] Added Frames Part 11, 12, 14 and 15
« Last Edit: 05/30/2014 09:41 am by arnezami »

Offline Helodriver

  • Full Member
  • ****
  • Posts: 1076
  • Liked: 5971
  • Likes Given: 700
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1165 on: 05/30/2014 08:09 am »
To all you dedicated video archaeologists digging up flipped bits, another by name shoutout by the man himself during the Q&A period after Dragon V2 reveal. Video of this to be posted tomorrow. Your efforts are being appreciated all the way at the highest levels.

Offline mvpel

  • Full Member
  • ****
  • Posts: 1125
  • New Hampshire
  • Liked: 1303
  • Likes Given: 1685
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1166 on: 05/30/2014 10:57 am »
So we are moving to a society where the line is becoming significantly blurred between technology that appears to be magic to the majority leading to a downplaying of the importance of STEM educcation and eventually society regresses back to the discovery of the wheel.   :)


MPEG error. I was able to fix some of them in 185 by random bit flipping.

The uniform character and well-defined scope of the problem may well make it possible to identify a pattern leading to the root cause of the issue and an easy correction of the other pframes short of just ignoring them.
« Last Edit: 05/30/2014 11:08 am by mvpel »
"Ugly programs are like ugly suspension bridges: they're much more liable to collapse than pretty ones, because the way humans (especially engineer-humans) perceive beauty is intimately related to our ability to process and understand complexity. A language that makes it hard to write elegant code makes it hard to write good code." - Eric S. Raymond

Offline arnezami

  • Full Member
  • **
  • Posts: 285
  • Liked: 267
  • Likes Given: 378
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1167 on: 05/30/2014 11:09 am »
One p-frame looks very strange, with "too intense" colors, could anyone come with an explanation and maybe a solution to this?

It's frame 227 / part 12-19

mmb: 0:0:-1,30:1:10681,10:3:-1,31:3:19630

I checked the VOP quants in this section and that frame does look like a bit of an outlier. Here are the VOP quants in fixed_edit8_part_209.ts:
1  00100
2  00010
3  00001
4  00001
5  00010
6  00010
7  00010
8  00001
9  00001
10 00000
11 00001
12 00001
13 00001
14 00001
15 00001
16 00001
17 00001
18 00001
19 00111
20 00001

My first guess is that the correct VOP quant is 00001, and there's a double flip, but other values are possible. I attach a ts file where that VOP quant is set to 00001. It's at offset x43A9B so other values can be tried. I can't check it myself as I'm yet to establish a proper setup for multiframe work. Let me know how it looks.

Thanks to Quialiss (from the wiki) this issue is now fixed with the mmb command:

Quote
X:59:C0

:)

Look at frame 239 over here: http://spacexlanding.wikispaces.com/Frames+Part+12

Offline saliva_sweet

  • Full Member
  • ****
  • Posts: 614
  • Liked: 476
  • Likes Given: 1826
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1168 on: 05/30/2014 12:07 pm »
Quote
X:59:C0

That was me actually ;) My first edit to the wiki.

Offline moralec

Thank you all for the hard work! Plenty of updates in the wiki on the past 8 hours. At this rate we will soon have a new version ready for distribution. 

Offline arnezami

  • Full Member
  • **
  • Posts: 285
  • Liked: 267
  • Likes Given: 378
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1170 on: 05/30/2014 12:53 pm »
Quote
X:59:C0

That was me actually ;) My first edit to the wiki.

Ah Cool! That was you! Nicely done :).

Offline CuddlyRocket

Thank you all for the hard work! Plenty of updates in the wiki on the past 8 hours. At this rate we will soon have a new version ready for distribution. 

I have only one criticism: Please be more quantitative than 'soon' so as to save me from the temptation of updating the thread every 5 minutes! :)

Offline Shanuson

  • Full Member
  • ***
  • Posts: 395
  • Liked: 327
  • Likes Given: 2542
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1172 on: 05/30/2014 01:52 pm »
Thank you all for the hard work! Plenty of updates in the wiki on the past 8 hours. At this rate we will soon have a new version ready for distribution. 

I have only one criticism: Please be more quantitative than 'soon' so as to save me from the temptation of updating the thread every 5 minutes! :)

Soon as in a few days I would say.

Offline saliva_sweet

  • Full Member
  • ****
  • Posts: 614
  • Liked: 476
  • Likes Given: 1826
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1173 on: 05/30/2014 01:58 pm »
Ah Cool! That was you! Nicely done :).

It did not occur to me, but michaelni suggested this could work here: http://forum.nasaspaceflight.com/index.php?topic=34597.msg1206072#msg1206072

All I had to do was find the bits :)


Offline arnezami

  • Full Member
  • **
  • Posts: 285
  • Liked: 267
  • Likes Given: 378
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1174 on: 05/30/2014 02:29 pm »
Hi guys,

Important note to everyone using the wiki/online editor: the online editor has been updated lately. This means you have to use -3s instead of -1s for P-frames. Just keep that in mind.

I am currently replacing all -1s with -3s for all P-frames on the wiki and re-uploading all those images. Again. :o

Regards,

arnezami

PS. The -1s are actually causing the gray "bands" in the picture...
« Last Edit: 05/30/2014 02:33 pm by arnezami »

Offline mvpel

  • Full Member
  • ****
  • Posts: 1125
  • New Hampshire
  • Liked: 1303
  • Likes Given: 1685
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1175 on: 05/30/2014 03:12 pm »
All I had to do was find the bits :)

Perhaps we can prevail upon @Shanuson to document the VOP header bits on the Wiki, if he hasn't already.  ;)
"Ugly programs are like ugly suspension bridges: they're much more liable to collapse than pretty ones, because the way humans (especially engineer-humans) perceive beauty is intimately related to our ability to process and understand complexity. A language that makes it hard to write elegant code makes it hard to write good code." - Eric S. Raymond

Offline Comga

  • Senior Member
  • *****
  • Posts: 6466
  • Liked: 4572
  • Likes Given: 5136
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1176 on: 05/30/2014 03:14 pm »
To all you dedicated video archaeologists digging up flipped bits, another by name shoutout by the man himself during the Q&A period after Dragon V2 reveal. Video of this to be posted tomorrow. Your efforts are being appreciated all the way at the highest levels.

helodriver also posted this in the event thread. 
"The telemetry from the CRS-3 booster splashdown was collected by an antenna made from a pizza dish stuck in his plane's window."

You are making an exquisite silk purse out of a sow's ear.
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Offline mhenderson

  • Member
  • Posts: 71
  • USA
  • Liked: 101
  • Likes Given: 18
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1177 on: 05/30/2014 04:24 pm »
iFrame 12 mmb and png



Hi guys,

I've been adding pictures to the wiki where no pictures were uploaded and noticed that if you downsized them the original was gone (you couldnt upscale them anymore).

I've now re-uploaded all images to 100% size in:

http://spacexlanding.wikispaces.com/Frames+Part+10
http://spacexlanding.wikispaces.com/Frames+Part+11
http://spacexlanding.wikispaces.com/Frames+Part+12
http://spacexlanding.wikispaces.com/Frames+Part+13
http://spacexlanding.wikispaces.com/Frames+Part+14
http://spacexlanding.wikispaces.com/Frames+Part+15

While you get less of an overview that way it is way easier for somebody else to check the quality of a frame. And quality is what we need most.

So from now on I think it's a good idea just to keep the pictures their original size.

@IainCole: we could sure use a "Save Image"-link ;)

Regards,

arnezami

[edit] Added Frames Part 11, 12, 14 and 15

Added the save link. Tested in FF and Chrome

Offline SwissCheese

  • Full Member
  • *
  • Posts: 166
  • Liked: 256
  • Likes Given: 107
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1179 on: 05/30/2014 07:09 pm »

Ok, the first part of this is done. Unfortunately in PNG format the zip file is 85 MB, so trying to auto-upload it to the wiki is probably pushing it. No pun intended. Instead, I put it on Google Drive at this url:

https://drive.google.com/file/d/0B_wTAwfYg03FQ3p2UVlkZE9MckU/edit?usp=sharing

Also on BTSync at B76OWSNRL5HWE47N7SHT4ZIX2B3B63IXT

This is ~250 frames in PNG format generated by scraping the wiki and then running it through ffmpeg. Why is this useful? Well, you can turn these into a movie file with this command:

ffmpeg -y -start_number 40 -i landing_base_set/frame-%03d.png -c:v libx264 -r 15 -pix_fmt yuv420p out.mp4

Also, you can run a batch process on these images to do post-processing or add annotations.

The zip archive will be regenerated every hour if the wiki has seen any updates.

I updated the auto-build script to renumber the frames to follow the wiki. Frames 181-200 are now taken from rawsplit_final.ts.

Also the BTSync share includes a video version with the frame-rate fixed as SwissCheese suggested.

SwissCheese, can you share a PNG of the title card?

Here you have! In the movie, I replaced frames 1 to 40 by the title image.

Tags:
 

Advertisement NovaTech
Advertisement Northrop Grumman
Advertisement
Advertisement Margaritaville Beach Resort South Padre Island
Advertisement Brady Kenniston
Advertisement NextSpaceflight
Advertisement Nathan Barker Photography
1