Improvement on Frame 9. You can sort of see part of the rocket body now, but if I try to shift it left it goes all green blocks on me again.The null MMBs help a lot.20:04:-1:0:0:-5:0:0:0,26:04:16025,21:07:-1,22:07:27346,05:15:-1,09:15:73077,12:15:-1,20:15:73574,24:15:-1,32:15:74745,1:16:-1,4:16:77775,8:16:-1,9:16:78463,26:16:-1,27:16:81473,28:16:-1,29:16:82604,31:16:82767,36:16:-1,37:16:83144-Bob
Quote from: wronkiew on 05/05/2014 08:18 amI think I got a bit more of iframe 8, hard to tell what the correct alignment is.ffmpeg -mmb 07:14:17233,14:14:57111,08:15:17233,09:15:63546,19:16:17233,21:16:73568,08:21:17233,00:22:111664 -debug mb_pos_size -err_detect ignore_err -s:0 704:480 -i iframe_8.mpg4-img -f image2 img-%03d.pngWorking from yours combining with mine I have this so far.-mmb 08:14:-1:15:-15:1:14:-2:1,09:14:56683,21:16:73568,08:21:17233,00:22:111664,01:28:139511,05:28:143051I need more information on what's at the bottom so going to work on one of the other iframes now. I'm moving on to working on iframe7.Edit: I think part of the problem is that we're seeing remnants of that darn dirty water that they splashed all over the rocket... So we have these dark and light splotches.
I think I got a bit more of iframe 8, hard to tell what the correct alignment is.ffmpeg -mmb 07:14:17233,14:14:57111,08:15:17233,09:15:63546,19:16:17233,21:16:73568,08:21:17233,00:22:111664 -debug mb_pos_size -err_detect ignore_err -s:0 704:480 -i iframe_8.mpg4-img -f image2 img-%03d.png
Frame 12 calls me.
[edit] Is that a piece of the leg broken off right-above the right leg? Is that the piece of the leg they found? That would be cool
Quote[edit] Is that a piece of the leg broken off right-above the right leg? Is that the piece of the leg they found? That would be cool My guess is that it is a splotch on the lens from the dirty water bath at launch. Maybe it is from some other source but it shows up in the same spot in a lot of the frames so I think it is on the lens.
Good morning chaps. This is such an impressive effort - and a big welcome to the new people who have helped push this forward.We've got SpaceX people watching this thread, but I think we're close to asking PAO to make Elon and the top brass aware of the progress. Will send out some e-mails today.
Quote from: Chris Bergin on 05/07/2014 06:34 amGood morning chaps. This is such an impressive effort - and a big welcome to the new people who have helped push this forward.We've got SpaceX people watching this thread, but I think we're close to asking PAO to make Elon and the top brass aware of the progress. Will send out some e-mails today.It would be great if you could get someone, anyone, to give us any screenshot from this camera of the stage from when they had signal from it, like just after separation. It would help greatly to know the dark/light patterns on the lower part of the image.
We created a way of doing some of the work through a mini web app. You can find it here: http://spacexlanding.wikispaces.com/Online+Editor
Quote from: IainCole on 05/06/2014 09:50 pmWe created a way of doing some of the work through a mini web app. You can find it here: http://spacexlanding.wikispaces.com/Online+EditorHi,What would be really useful is when you click somewhere on the generated pixel it would put the x and y of the corresponding block in your clipboard (or show it somewhere on the page so yuu can copy-paste it from there.Even more useful would be if you could parse the log on the serverside and when you click on the image you get x,y and bitposition in your clipboard! Or maybe simply the line from the log corresponding with the x and y you just clicked.Just an idea.Regards,arnezami
Ive added 2 features to https://github.com/michaelni/FFmpeg/tree/spacexdebug1first, you can now use syntax like -mmb 40:03:-1to fill the image with "blank" blocks starting from 40:03 and until the next specified commandand-mmb X:20009:1Bto xor 0x1B at bit position 20009 of the frame, that is this allows to flip some bits without the need to edit the file(atm this is limited to max 8bit per command)
Quote from: michaelni on 05/06/2014 01:01 amIve added 2 features to https://github.com/michaelni/FFmpeg/tree/spacexdebug1first, you can now use syntax like -mmb 40:03:-1to fill the image with "blank" blocks starting from 40:03 and until the next specified commandand-mmb X:20009:1Bto xor 0x1B at bit position 20009 of the frame, that is this allows to flip some bits without the need to edit the file(atm this is limited to max 8bit per command)Hi Michael,I've been looking at a lot of frames that were "fixed" with the blank blocks. I think they are useful. But what would be better is a block that cancels/negates all information coming from the left and upper block. In other words a block that if you would place one of its kind above (and one its kind to the left) of a block with content it would be as if that block with content would be at 0,0: no disturbance at all. Of course this would also remove all good information from the left and top but I think that might in many cases to better than the blank-block. Maybe choose to cancel only the top information or only the left information.Do you think this can be done?So like this:-1 : let info through from left and top-2 : let info through from left, cancel from top-3 : cancel info from left, let it through from top-4 : cancel info from left and topRegards,arnezami