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.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.
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 pmQuote 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.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.This is done. The video is here:http://adama.nocdirect.com/~wronkiew/spx_crs3/landing_base_set.mp4Whenever it is regenerated your URL will get a POST.I added SwissCheese's title card. Frames 161-200 and 281-283 now come from the fixed .ts files.I have noticed some block bugs that aren't showing on the wiki, which might be because my copy of the split .ts files is out of date. Do you have a newer set of split (i + 19p) files?
This is done. The video is here:http://adama.nocdirect.com/~wronkiew/spx_crs3/landing_base_set.mp4Whenever it is regenerated your URL will get a POST.I added SwissCheese's title card. Frames 161-200 and 281-283 now come from the fixed .ts files.I have noticed some block bugs that aren't showing on the wiki, which might be because my copy of the split .ts files is out of date. Do you have a newer set of split (i + 19p) files?
25:1:44861,41:1:-3,38:4:9585,16:16:-3,0:18:45141,18:27:-3,43:27:68567,11:28:-3,17:28:70673,7:29:-3,8:29:71924,43:29:-3unsure about the bottom part (btw43:29:-3 is needed for next frame)
Quote from: wronkiew on 05/31/2014 08:49 amThis is done. The video is here:http://adama.nocdirect.com/~wronkiew/spx_crs3/landing_base_set.mp4Whenever it is regenerated your URL will get a POST.I added SwissCheese's title card. Frames 161-200 and 281-283 now come from the fixed .ts files.I have noticed some block bugs that aren't showing on the wiki, which might be because my copy of the split .ts files is out of date. Do you have a newer set of split (i + 19p) files?Cool I was just wondering though. Sometimes we put real comments combined with actuall mmbs in the wiki like this: (see: frame 63)Quote25:1:44861,41:1:-3,38:4:9585,16:16:-3,0:18:45141,18:27:-3,43:27:68567,11:28:-3,17:28:70673,7:29:-3,8:29:71924,43:29:-3unsure about the bottom part (btw43:29:-3 is needed for next frame)How do you make sure you extract the correct mmb from something like this? Should we adhere to some kind of format? Or should we not post comments at the place we post mmbs?Regards,arnezami
BITLOG:000:00:00:cbpc:550:551:0BITLOG:000:00:00:ac_pred:551:552:1BITLOG:000:00:00:cbpy:552:554:15BITLOG:000:00:00:dc_lum0_size:554:557:4BITLOG:000:00:00:dc_lum0_level:557:561:-13BITLOG:000:00:00:dct561:578:0:3:-6BITLOG:000:00:00:dct578:585:1:1:-1BITLOG:000:00:00:dc_lum1_size:585:588:4BITLOG:000:00:00:dc_lum1_level:588:592:8BITLOG:000:00:00:dct592:602:1:12:-1BITLOG:000:00:00:dc_lum2_size:602:604:1BITLOG:000:00:00:dc_lum2_level:604:605:-1BITLOG:000:00:00:dct605:608:0:0:1BITLOG:000:00:00:dct608:614:0:2:-1BITLOG:000:00:00:dct614:619:0:1:-1BITLOG:000:00:00:dct619:649:0:29:1BITLOG:000:00:00:dct649:659:1:14:-1BITLOG:000:00:00:dc_lum3_size:659:661:1BITLOG:000:00:00:dc_lum3_level:661:662:-1BITLOG:000:00:00:dct662:667:1:0:-1BITLOG:000:00:00:dc_chrom4_size:667:671:4BITLOG:000:00:00:dc_chrom4_level:671:675:13BITLOG:000:00:00:dc_chrom5_size:675:678:3BITLOG:000:00:00:dc_chrom5_level:678:681:-7BITLOG:000:00:00:bits:550:681:11110010010000001100001101110011111001100000001001111101000101111110100000111100111101000000000001100001000111100111100011101001000
<div> <span class="red" title="cbpc:550:551:0">1</span> <span class="red" title="ac_pred:551:552:1">1</span> <span class="red" title="cbpy:552:554:15">11</span> <span class="blue" title="dc_lum0_size:554:557:4">001</span> <span class="blue" title="dc_lum0_level:557:561:-13">0010</span> <span class="green" title="dct561:578:0:3:-6">00000110000110111</span> <span class="green" title="dct578:585:1:1:-1">0011111</span> <span class="blue" title="dc_lum1_size:585:588:4">001</span> <span class="blue" title="dc_lum1_level:588:592:8">1000</span> <div>
Perhaps keeping this file https://github.com/IainCole/SpaceXVideoApp2/blob/master/data.json up to date based off the wiki might be useful, for 2 reasons, it gives us a solid data structure for MMBs so that people can use it to generate videos without having to parse the wiki. Also the online editor will take those values as defaults so people don't have to copy everything across from the wiki to work on one part of a segment.
Quote from: SwissCheese on 05/30/2014 10:13 pmQuote 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)That seems to be what's coming back from the log :/ Dunno if it's specific to the online editor?
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: 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: 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?
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...
Alternatively you could have a centralized database with a little web-app around it where you can enter/edit mmbs.
-mb_bitlog <framenr>:<mb_x>:<mb_y>:<nr_of_mbs_to_log>
-mb_bitlog 0:3:10:20
Ok, so i'm a linux guy with web servers and the works, and would like to help. First of all, i would like to help with recovering the video. Is there an updated guide of where to start? should i use arnezami's latest build?
Cool I was just wondering though. Sometimes we put real comments combined with actuall mmbs in the wiki like this: (see: frame 63)Quote25:1:44861,41:1:-3,38:4:9585,16:16:-3,0:18:45141,18:27:-3,43:27:68567,11:28:-3,17:28:70673,7:29:-3,8:29:71924,43:29:-3unsure about the bottom part (btw43:29:-3 is needed for next frame)How do you make sure you extract the correct mmb from something like this? Should we adhere to some kind of format? Or should we not post comments at the place we post mmbs?Regards,arnezami
Yes, that line would have messed up the scraper, which is why I had not transitioned it yet. I think I will
I doesn't seem like rocket science, but it does seem like a lot of work specially on the online tool side (we don't want you to hate us Iaincole). Ideas?
Youtube video exports seem to be running along nicely https://www.youtube.com/user/spacexlandingrestore
Quote from: wronkiew on 05/31/2014 07:25 pmYes, that line would have messed up the scraper, which is why I had not transitioned it yet. I think I will Can you just use a regexp to ignore any lines that don't match the expected format? Then it should be straightforward to add whatever sort of comment you like, so long as it's obvious isn't not a valid option.