Last edited by a moderator:
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
In an effort to see if the video can be improved further, below are links to both the original data file as well as the repaired source file. The file labeled “raw.ts” is an extraction of the raw MPEG bitstream from the rocket. Our software team attempted to repair the data, resulting in the “repair1.ts” file, and the partial video above. We welcome anyone to download the raw file to make improvements directly—if you are successful, please contact us at
Video is on
First Stage Landing Video | SpaceX
The video is low quality, but still pretty cool.
I'd really like a full length vid, though. I mean real time video from launch, to engine cut, to stage separation, ballistic flight, engine restart, leg deployment, hover, and splashdown all from the save POV.
(Again similar to the videos NASA put out for the Shuttle SRBs.)
Someone needs to buy SpaceX a GoPro! :smile:
Hi guys,
I would like to explain what we are actually doing. Because some of you might not completely grasp it. And I think I can best explain it by an illustration. Otherwise it gets too technical too quickly. I will do it in terms of rockets.
--
Imagine a book. A thick book. It's a book containing very detailed technical instructions on how to build a new type of rocket. It contains 13 chapters. One for each rocket part. Each chapter consists of an introductory paragraph explaining what the part is, how it should look like and how it works. None of the following paragraphs can be understood if this paragraph has not been read. The following paragraphs are highly dependent on each other: if you haven't read them in sequence they will be meaningless since they always refer heavily to the previous one to understand.
All sentences are written in a foreign language. And all punctuation is removed. Also all capitals are made lower case. The letters in the words are coded: each letter can only be decoded if you know the previous letter. For example this code: when reading a letter add the letternumber (a=1, b=2 etc) of the previous letter to this one to get the real letter. All whitespaces are removed. So each paragraph is just a string of seemingly random letters.
Ok. Now you're thinking: "This is insane. Who would read such a book?"
But this book was never intended to be read by a human being! It was supposed to be read by a machine that would also automatically build the rocket parts. Here is the real problem though: the printing machine that printed the book had a major error: it sometimes printed the wrong letter! So the book has thousands of random errors in it! Unsurprisingly when the book is now given to the rocket-part-building-machine it says: "Error". And that's basically it.
Ok it turns out that the rocket-part-building-machine made a few incomplete and defective drawings of parts before giving the error. Mostly useless. So it seems that this is impossible to fix. Trying to figure out which letters are randomized by hand is insanely hard and time consuming.
What we did though was the following: instead of fixing the book we changed the machine so it would (1) give us better errors and (2) allow us to overrule certain instructions. We fed the machine with the first paragraph of a chapter and it started to draw the part. When we thought it went wrong we gave it the instruction to skip that portion of the drawing. Because apparently it had read a wrongly printed letter.
Of course we did not know how far it had to skip. So we guessed several times and hoped it would start drawing something sane again. And each time it was drawing something that looked sensible we knew it was reading uncompromised letters. We got an understanding which parts of the paragraph were wrongly printed and then mostly avoided them. By doing this many times and collaborating with several people we have now been able to let the machine draw several almost complete and fairly accurate parts. We do not know yet if it is going to be possible to let the machine read the other paragraphs in the chapters (they are much harder). But getting these drawings is already very satisfying.
--
I hope this illustration helps you (who might not understand the deeply technical stuff) to understand what the problem really is. How insane it is. And I think it's a quite good representation of what is actually the case.
Regards,
arnezami
---
PS. Below is a translation from the illustration into the real problem.
- Book: Video
- 13 chapters: 13 parts of the video
- First paragraph of each chapter: I-frame (independent picture)
- Other paragraphs: P- and B-frames (all dependent on each other)
- Foreign language: the language of video decoding (things like "discrete cosine transform", "motion vectors", "chrominance and luminance blocks" etc)
- Removal of punctuation and capitals: there are essentially no clear "markers" in the bitstream: no marker to detect the beginning of a horizontal line in the picture.
- Words: macroblocks (16 x 16 pixel blocks)
- Letter coding and removal of whitespaces: the coding of the bits is such that you need every previous bit to know what the current one means withing a word. The words are also variable in length. There is essentially no clear marker between each macroblock.
- Printing errors: random bits that were flipped due to bad reception
- Rocket-part-building-machine: the video decoder (the open source ffmpeg in our case)
- Drawings: the pictures the video decoder makes after trying to decode a frame
The transportstream is not mentioned. But effectively many pages of the book were missing. We mostly fixed that: they were actually "hidden" and we discovered most of them.
..I never realized that the legs deploy so soon before "impact" I would have thought they would be out long before the landing to increase aerodynamic drag.