Quote from: wronkiew on 05/27/2014 06:47 pmMy current thinking on this is that rather than putting a duplicate timestamp in a matte, I'll redraw the known timestamps using the bitmap numerals already displayed. No interpolated timestamps added.When I get a chance I also want to put together a system that automatically generates png sequences from the mmbs, zips them up, and uploads them to the wiki. That way anyone can download the frames and do their own batch processing on them.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=sharingAlso on BTSync at B76OWSNRL5HWE47N7SHT4ZIX2B3B63IXTThis 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.mp4Also, 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.
My current thinking on this is that rather than putting a duplicate timestamp in a matte, I'll redraw the known timestamps using the bitmap numerals already displayed. No interpolated timestamps added.When I get a chance I also want to put together a system that automatically generates png sequences from the mmbs, zips them up, and uploads them to the wiki. That way anyone can download the frames and do their own batch processing on them.
Here you have! In the movie, I replaced frames 1 to 40 by the title image.
Don't suppose you can also put a video somewhere on google drive too? If so I can probably automate pushing it to youtube or something.
Quote from: wronkiew on 05/30/2014 06:48 amQuote from: wronkiew on 05/28/2014 05:52 amOk, 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=sharingAlso on BTSync at B76OWSNRL5HWE47N7SHT4ZIX2B3B63IXTThis 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.mp4Also, 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.
Quote from: wronkiew on 05/28/2014 05:52 amOk, 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=sharingAlso on BTSync at B76OWSNRL5HWE47N7SHT4ZIX2B3B63IXTThis 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.mp4Also, 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?
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=sharingAlso on BTSync at B76OWSNRL5HWE47N7SHT4ZIX2B3B63IXTThis 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.mp4Also, 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.
Quote from: IainCole on 05/30/2014 07:26 pmDon't suppose you can also put a video somewhere on google drive too? If so I can probably automate pushing it to youtube or something.I can take care of this tonight.
Sorry if someone already posted this, but your efforts are now linked on the SpaceX website http://www.spacex.com/news/2014/04/29/first-stage-landing-videoAnd we hear Elon specifically mentioned you guys at the post Dragon V2 reveal Q&A!
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. Regards,arnezamiPS. The -1s are actually causing the gray "bands" in the picture...
Quote from: arnezami on 05/30/2014 02:29 pmHi 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. Regards,arnezamiPS. The -1s are actually causing the gray "bands" in the picture...The online editor gives a correct image with the -3 but does not seem to update the macroblock information and errors. Is it on purpose?
Quote from: wronkiew on 05/30/2014 08:01 pmQuote from: IainCole on 05/30/2014 07:26 pmDon't suppose you can also put a video somewhere on google drive too? If so I can probably automate pushing it to youtube or something.I can take care of this tonight.Cool, I think I pretty much have everything set up. All I need is a public accessible URL to hit that has the latest video. Also you need to send a POST to a url when it's uploaded so I know when it's changed, that do-able?
Quote from: SwissCheese on 05/30/2014 09:36 pmQuote from: arnezami on 05/30/2014 02:29 pmHi 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. Regards,arnezamiPS. The -1s are actually causing the gray "bands" in the picture...The online editor gives a correct image with the -3 but does not seem to update the macroblock information and errors. Is it on purpose?I think I know what this might be, I'll take a look in a bit.
Quote from: IainCole on 05/30/2014 09:27 pmQuote from: wronkiew on 05/30/2014 08:01 pmQuote from: IainCole on 05/30/2014 07:26 pmDon't suppose you can also put a video somewhere on google drive too? If so I can probably automate pushing it to youtube or something.I can take care of this tonight.Cool, I think I pretty much have everything set up. All I need is a public accessible URL to hit that has the latest video. Also you need to send a POST to a url when it's uploaded so I know when it's changed, that do-able?Yep. URL?
Quote from: IainCole on 05/30/2014 09:38 pmQuote from: SwissCheese on 05/30/2014 09:36 pmQuote from: arnezami on 05/30/2014 02:29 pmHi 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. Regards,arnezamiPS. The -1s are actually causing the gray "bands" in the picture...The online editor gives a correct image with the -3 but does not seem to update the macroblock information and errors. Is it on purpose?I think I know what this might be, I'll take a look in a bit.Oh and while you are here, would it be possible to add a slider to enhance the image contrast? It helps a lot for repairing the p-frames but I have to use an image viewer to do this currently. Thank you again for your great work!
Quote from: SwissCheese on 05/30/2014 09:44 pmQuote from: IainCole on 05/30/2014 09:38 pmQuote from: SwissCheese on 05/30/2014 09:36 pmQuote from: arnezami on 05/30/2014 02:29 pmHi 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. Regards,arnezamiPS. The -1s are actually causing the gray "bands" in the picture...The online editor gives a correct image with the -3 but does not seem to update the macroblock information and errors. Is it on purpose?I think I know what this might be, I'll take a look in a bit.Oh and while you are here, would it be possible to add a slider to enhance the image contrast? It helps a lot for repairing the p-frames but I have to use an image viewer to do this currently. Thank you again for your great work!If I even had the slightest idea how to do that I'd be all over it =)
Quote from: SwissCheese on 05/30/2014 09:36 pmQuote from: arnezami on 05/30/2014 02:29 pmHi 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. Regards,arnezamiPS. The -1s are actually causing the gray "bands" in the picture...The online editor gives a correct image with the -3 but does not seem to update the macroblock information and errors. Is it on purpose?Can you give me a specific example of what isn't working and what you expect to see?
Quote from: IainCole on 05/30/2014 09:57 pmQuote from: SwissCheese on 05/30/2014 09:36 pmQuote from: arnezami on 05/30/2014 02:29 pmHi 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. Regards,arnezamiPS. The -1s are actually causing the gray "bands" in the picture...The online editor gives a correct image with the -3 but does not seem to update the macroblock information and errors. Is it on purpose?Can you give me a specific example of what isn't working and what you expect to see?Just take any p-frame with errors, and write 0:0:-3 (should discard the whole frame) the yellow squares stay and the information on top of the frame still shows the discarded information. (difficult to write from a mobile phone)
Quote from: mlindner on 05/29/2014 10:29 amJust want to say this is an amazing job you guys have done! I had to drop out from doing it because real life intervened in my ability to have time to assist. Hopefully I'll have time to catch up on the some 30 pages that have been posted since I last helped.Just as a quick question, is there still need to repair I-frames? I notice that many of the I-frames have not advanced much in repair state from when I was last involved.Hi mlindner! Glad you're back There is definitely still a need for work on the I-frames. I think many moved their focus to the P-frames because making video is so tempting and rewarding But improving the I-frames clearly makes the 19 P-frames that follow much better!Your excellent work on frame 169 shows that!Regards,arnezami
Just want to say this is an amazing job you guys have done! I had to drop out from doing it because real life intervened in my ability to have time to assist. Hopefully I'll have time to catch up on the some 30 pages that have been posted since I last helped.Just as a quick question, is there still need to repair I-frames? I notice that many of the I-frames have not advanced much in repair state from when I was last involved.
Quote from: arnezami on 05/29/2014 10:56 amQuote from: mlindner on 05/29/2014 10:29 amJust want to say this is an amazing job you guys have done! I had to drop out from doing it because real life intervened in my ability to have time to assist. Hopefully I'll have time to catch up on the some 30 pages that have been posted since I last helped.Just as a quick question, is there still need to repair I-frames? I notice that many of the I-frames have not advanced much in repair state from when I was last involved.Hi mlindner! Glad you're back There is definitely still a need for work on the I-frames. I think many moved their focus to the P-frames because making video is so tempting and rewarding But improving the I-frames clearly makes the 19 P-frames that follow much better!Your excellent work on frame 169 shows that!Regards,arnezamiWhere's the most recent version of the source code people have been using? Presumably people are no longer using my out-of-date repo anymore?
The Lunar Laser Communication Demonstration (LLCD) transmitted over 384,633 kilometers between here and the moon at a download rate of 622 megabits per second. They also sent data from Earth to the moon at 19.44 megabits per second. That’s 4,800 times faster than the best radio frequency uplink ever used.