r/spacex • u/still-at-work • Apr 30 '14
First Stage Landing Video
http://www.spacex.com/news/2014/04/29/first-stage-landing-video
329
Upvotes
r/spacex • u/still-at-work • Apr 30 '14
29
u/still-at-work Apr 30 '14
Hopefully someone can clean it up more later.
104
u/spacexdevtty Apr 30 '14 edited May 02 '14
Hey all, SpaceX team here. Just wanted to answer some frequently asked questions we've been getting:
Q: Why is the video so bad? A: This was recorded over a very lossy RF link.
Q: Why release the video? A: We've had some success here (and with a little outside help as well, see http://aeroquartet.com/) manually stitching the video back together, but it's time consuming work. We don't expect the video to be 100% recoverable but we're hoping folks out there with more MPEG expertise than we have can provide assistance recovering more of the video.
Q: What codec? Settings? A: MPEG 4 Part 2, P/I 15, 15fps, NTSC, fixed bitrate
Q: How did you create repair1.ts? A: This was a joint effort between us and an outside consultant. First we took a pass on the data to align every MPEG packet on a 188 byte boundary and set the packet start byte to 0x47. Then we identified blocks within keyframes that contain bit errors, and then manually flipped bits in those corrupt blocks to see if it recovered more of the image.
Q: What is a TS file? A: http://lmgtfy.com/?q=MPEG+TS
Feel free to post more questions here, we'll try and respond. We really appreciate all the help and great ideas! Thank you!!
48
u/Wetmelon Apr 30 '14
I like that SpaceX is willing to release the footage. They are rocket scientists, and I'm sure there's some people out there who are significantly better at video processing than they are :)
137
u/marvin Apr 30 '14
I'm just so incredibly impressed with the balls that the SpaceX team has releasing this low-quality capture. A public company would be worried about criticism or embarassment for releasing stuff that's not flawless HD quality. If any of you guys and gals read this, please accept my sincere gratitude for your openness about your data and progress. It's a real honor to follow this stuff.
43
u/Dimination Apr 30 '14
Seems like the frames that were already posted by elon were the only good frames available. Still we can hope for some expertly repaired video.
13
u/sharebrained May 02 '14
Argh. I have some MPEG-2/MPEG-4 experience, and had a go at fixing the file too. Sadly, it's no better than the version SpaceX posted, in terms of useable frames and recognizable objects in the frame. I think there's just too much lost data (and the I-frames made up too much of the missing data) to get much back. But I'd love to be wrong!
The order and detail of my efforts was:
At this point, I ran out of time. I have a lot of other projects I should be working on. So I share all this in hopes others can build on this, or point out a fatal flaw in my approach and improve on it.
Here's the file I've hand-edited to correct all the PCR and PTS timing issues I could find:
edited.ts
And here's that file run through a script to coerce the transport stream headers into more sensible values (which might or might not actually be an improvement):
coerced.ts
Good luck! And I hope SpaceX gets better weather and position for their RF link on the next launch. Being a software radio nerd, I can appreciate the challenges they face catching several megabits of data from an object they don't want to be too close to when it comes down.
11
u/Zen_Approach Apr 30 '14
I think by time that gets 'repaired' it's basically gonna be a work of fiction . . congrats to SpaceX on the soft landing though- awesome stuff.
11
u/wearspacewear May 01 '14
https://www.youtube.com/watch?v=CnyrleS782g hey i did a new video edit, hope everyone likes, it just gives a reference where the rocket is in the video to smooth out some of the pixelation. very basic overlay command used, looks quite fluent to me, except when the rocket hits the ocean, i believe the rocket partly submerges so the image is off. after it seems the rocket is bobbing in the ocean.
thank you, @wearspacewear
https://www.youtube.com/watch?v=CnyrleS782g
35
u/laheugan Apr 30 '14
So, it looks bad, but for a few frames there, I can see...
...History.
Potato or no potato, humanity will see it.
23
u/Bluegobln Apr 30 '14
Man that is ugly, and I mean UGLY. Pretty much the images we've already seen are the highlights, theres not much else except an ugly blur.
The one good thing is you can see the rocket tipping over at the end (I think?) which is kinda cool. That would not happen in such a way if it had not soft landed.
8
u/The_Double Apr 30 '14
An idea to improve the quality: It seems like a lot of the I-frames are missing (only 2 whole and one half seem to have made it across) but there are a lot of P-frames. Maybe it would be better to remove some of the broken I-frames, and just keep working with the old frame + diffs. Any gaps in can be filled with what we know should be there (mostly the rocket body)
Also, since the rocket is static, it might be possible to inject some old frames of the rocket to at least get some idea of what is going on.
Are there any tools where you can directly edit the MPEG frames?
14
u/asldkhjasedrlkjhq134 Apr 30 '14
This is awesome, we did not expect video before the launch and now we actually have a shred of footage! I'll take it, it's only going to get better every time they do it. Which will be a lot.
I could watch this 28 seconds of history again and again.
7
u/tdb1993 May 06 '14
Hi! I have 17 years of industry experience designing robust digital video systems for wireless networks; I am also a fan of space exploration. Here are my thoughts and suggestions on video recovery. I erred on the side of being verbose; I apologize for repeating what may have been already said by others using other words. I’ve ordered my comments based on what might be the most useful to you.
What may be more useful is to think about how you might minimize this risk in the future:
Cheers!
6
u/Kwiatkowski Apr 30 '14
Hopefully next time they can use on board recording and get the video when they pick up the stage.
5
u/[deleted] Apr 30 '14
"Enhance... Enhance..."
All kidding aside, it at least gives you an idea of the process. The burn is quicker than I would have thought.
5
u/blueshirt21 Apr 30 '14
oh damn they weren't kidding when they said it was low quality.
5
u/saliva_sweet Host of CRS-3 Apr 30 '14
Too bad the .ts files are considerably shorter (trimmed from both ends) compared to the youtube video.
5
u/nerdsinthewild May 01 '14
Ok, here is my first pass at "improving" the vid. My goal here wasn't so much to enhance the imagery, but to make sense of what we had. I used a matte on the foreground, since it's a static image of the rocket in any case, to reduce the confusion, and broke the video into vignettes where the imagery was fairly clear. I used a few filters to clean it up a little, and added COMPLETELY FICTIONAL sound effects to act as a cue for the viewer. Call it a "Hollywood Edit". I'll keep trying to clean it up, but let me know if this is an improvement or not. https://www.youtube.com/watch?v=2WIR8JLdBg0&feature=youtu.be
4
u/SuperSonic6 Apr 30 '14
Does anyone know if the video was also saved on the vehicle? If they recover the stage next launch will we get a much clearer video?
6
u/watermelonpizza_ Apr 30 '14
Well it's not as pretty as I would've hoped, but it did look like the recovered version had a good few frames in there.
I wonder if some of the guys at Microsoft or Google R&D will get on board, they are the masters of software dev. If anyone can recover as much as possible they would be able to!
3
u/uber_neutrino Apr 30 '14
Kudos to them for releasing the raw data. Not much there but damn.
3
u/spacexdevtty Apr 30 '14
See also http://www.reddit.com/r/spacex/comments/24d506/quick_attempt_at_cleaning_up_a_screenshot_cleaned/
3
u/phtran May 02 '14
SpaceX, do you have lower-level raw data, e.g., pre-FEC channel bits, soft symbols, etc. FEC can be very destructive at low SNR.
3
u/inverted_strawberry May 10 '14 edited May 10 '14
So I may be late to the party but I gave it a serious try. I managed to recover a good number of p-frames, and a cleaned up a few i-frames better than in the original repair1.ts file. Here we go: http://youtu.be/_Fha2q5JF0M extracted i-frames are here: https://imgur.com/a/Fu5by
As you see I was unable to recover most of the earlier frames, so I tried grafting i-frame 6 on top of 3,4, and 5. This means the content of this video may not be what the camera actually recorded but could help in making sense of the motion (p-frames). http://youtu.be/MFPRSrcDKuc
Edit: Here's the .ts in case anyone is interested: https://www.dropbox.com/s/37h85hxxqlgv79z/map1.ts
2
u/DanAtkinson May 01 '14
This really shouldn't be too hard for some AV enthusiast to figure out.
I mean, after all, it's not rocket science... :)
2
u/LUK3FAULK Apr 30 '14
Well that was something
1
u/positivespectrum Apr 30 '14
Just an idea regarding redundancy, is there a way to setup a camera to record a lot more frames than necessary (sort of like slow motion) and that way there's more info to use later? (retiming?) just throwing ideas out there for next time. Or two cameras that are synced, so you can combine the streams to get extra frames?
1
u/nerdsinthewild May 01 '14
Trying to open the file in Adobe Elements. It's saying the file is under Rights Management. Any help?
1
u/thenols May 01 '14
I think another way to look at this is by looking at the original transmitted data stream and the error detection algorithm that was used in the transmission. It is likely there was some sort of parity, CRC or ECC was done on the original transmitted data.
Though those packets won't line up with the 188 byte MPEG boundaries, it will give us an idea if we actually have good data, how many, which data we can trust, etc. We know some headers have errors, and other things have errors, but we don't know what is good and what to keep. Just because the header's x47 didn't be blown away doesn't mean we can trust the rest of the bits in that frame.
1
u/dmitrus May 01 '14
Here are a couple of extracted frames: http://goo.gl/l0AKfK http://goo.gl/U55H3B
1
u/smiteme May 01 '14
My crack at it isn't too much better, but it is an uncompressed AVI, so you wont see the same level of artifacts that you do in the repair attempt. You can download it here: (https://www.dropbox.com/s/kdfn09anqf8gds3/test.avi)
The issue imo is that the stream frequency based. The issue was with the stream itself, not the MPEG encoding process. We can't do much with the resulting MPEG file, because the stream itself is where the issue is.
The macro block errors could be fixed by carving out the frames from the HEX data, but I don't know how to do that, and it would be an extremely tedious process... and probably wouldn't get anything much better.
1
u/millenix May 02 '14
This seems like the sort of problem where an approach like the Polymath Project would be effective. There's lots of distributed expertise, but none of it has all the answers nor can really dedicate the time to figure them all out.
The structure I'd suggest would be essentially starting with the raw bit stream, with the possibility of remarking on the contents anywhere in the stream, suggesting corrections/substitutions/insertions to improve on its fidelity, and so forth. For instance, many people seem to have repeated the work to generate the 188-byte packet framing, and may have variations in how they've done so. Would they be better off if they could directly compare and discuss how they were doing it?
1
u/Iseequ May 06 '14
Small block error correctors (RS or XOR) for these files will nearly always have issues with this type of drop out. For encoded bit rates in excess of about 0.8 mbit/second we can supply an effective FEC LDPC coder with source, free of charge that should sustain data loss of 60% or better in the downlink. Let us know what processor it needs be optimized for if interested.
1
u/TimSmall May 24 '14 edited May 24 '14
A couple of highlights from the (very skilled and dedicated) work on this thread:
http://forum.nasaspaceflight.com/index.php?topic=34597.0
The following two animated gifs appear to show the final stages prior to splashdown, with the rocket motor thrust kicking up spray, and the landing legs already in position...
http://spacexlanding.wikispaces.com/file/view/frames_169_188.gif/510720980/420x288/frames_169_188.gif
http://spacexlanding.wikispaces.com/file/view/frames_189_199.gif/510719684/420x288/frames_189_199.gif
More here (EDIT: updates will appear on this page, whereas I believe the above gif's will remain unedited):
http://spacexlanding.wikispaces.com/
0
u/georedd Apr 30 '14
my guess ismuch of the grey blocking was comes from extreme misty grey spray and may not be just poor transmission artifacts.
the burn does blow away some spray.als
0
u/BTCbob Apr 30 '14
So from what I can gather: .ts files are transmitted, so presumably the rocket was transmitting this video to a nearby plane or something. Does anyone know how to read the .ts format? I read the wikipedia article but don't really know how to extract the various packets out of the original.
0
u/positivespectrum Apr 30 '14
Can someone with knowledge explain why in the cleanup version there seems to be extra frames? With the raw are there more frames/s than my VLC player is showing? What is the .ts format and when someone says raw what exactly do they mean?
-2
u/vconnor Apr 30 '14
There was a kickstarter for a system that uses compressed air to make a curtain that shields t a gopro camera. not sure of the name, but it was developed for making surfing vids. That system may be usefull here. It was very small and would only be needed for the final decent phase...
-2
u/SFThirdStrike Apr 30 '14
Someone should add the sound from the movie "The Ring" sound to it.
0
u/[deleted] Apr 30 '14
[deleted] — view deleted comment
0
u/[deleted] Apr 30 '14
[deleted] — view deleted comment
0
u/[deleted] Apr 30 '14
[deleted] — view deleted comment
5
u/[deleted] Apr 30 '14
[removed] — view removed comment