It works! I found the problem! I simply have to disable the multi-threading with option -threads 1So yes, it was related to windows...
Quote from: arnezami on 05/19/2014 08:57 pmQuote from: moralec on 05/19/2014 08:42 pmQuote from: arnezami on 05/19/2014 07:29 pmProof of concept time That gif looks awsome! (I'm adding it on the wiki).On other news the table in the wiki is ready, for those that are fixing the headers on the pframes I have difficulty finding stuff in the wiki now. Shouldn't the stuff we are working on be right at the top? Also this pframe pages, how do I find them? I'm really confused atm.Thanks for the feedback. I'm moving that section up now.
Quote from: moralec on 05/19/2014 08:42 pmQuote from: arnezami on 05/19/2014 07:29 pmProof of concept time That gif looks awsome! (I'm adding it on the wiki).On other news the table in the wiki is ready, for those that are fixing the headers on the pframes I have difficulty finding stuff in the wiki now. Shouldn't the stuff we are working on be right at the top? Also this pframe pages, how do I find them? I'm really confused atm.
Quote from: arnezami on 05/19/2014 07:29 pmProof of concept time That gif looks awsome! (I'm adding it on the wiki).On other news the table in the wiki is ready, for those that are fixing the headers on the pframes
Proof of concept time
OK cool, am I right in thinking there's a whole bunch of extra stuff coming out of the log now? Also some things don't seem to be coming out in "order" as far as frame numbers go.Quote[mpeg4 @ 0x60008d3c0] MB pos/size: 0 001:29:08:0 1 dc: 128 128 128 128 - 128 128MB pos/size: 0 006:29:03:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x60009a2a0] , MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000a36a0] MB pos/size: 0 009:31:00:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x60009d440] MB pos/size: 0 007:30:02:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x60008dde0] MB pos/size: 0 002:29:07:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x600090f80] MB pos/size: 0 003:30:06:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000a0500] MB pos/size: 0 008:31:01:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x600094040] MB pos/size: 0 004:28:05:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000971e0] MB pos/size: 0 005:29:04:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x60008d3c0] MB pos/size: 0 001:30:08:0 1 dc: 128 128 128 128 - 128 128, MB_type: 14344, MV: 0 0Is that normal?I also have a few lines that look like this:Quote[mpeg4 @ 0x600090f80] MB pos/size: 0 000:09:20:0 1 dc: 0 0 0 0 - 0 0MB pos/size: 0 000:10:19:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000971e0] MB pos/size: 0 000:11:18:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000971e0] , MB_type: 14344, MV: 0 0There's 2 MB pos/size things on 1 line and a little further down some stuff is missing.
[mpeg4 @ 0x60008d3c0] MB pos/size: 0 001:29:08:0 1 dc: 128 128 128 128 - 128 128MB pos/size: 0 006:29:03:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x60009a2a0] , MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000a36a0] MB pos/size: 0 009:31:00:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x60009d440] MB pos/size: 0 007:30:02:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x60008dde0] MB pos/size: 0 002:29:07:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x600090f80] MB pos/size: 0 003:30:06:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000a0500] MB pos/size: 0 008:31:01:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x600094040] MB pos/size: 0 004:28:05:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000971e0] MB pos/size: 0 005:29:04:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x60008d3c0] MB pos/size: 0 001:30:08:0 1 dc: 128 128 128 128 - 128 128, MB_type: 14344, MV: 0 0
[mpeg4 @ 0x600090f80] MB pos/size: 0 000:09:20:0 1 dc: 0 0 0 0 - 0 0MB pos/size: 0 000:10:19:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000971e0] MB pos/size: 0 000:11:18:0 1 dc: 0 0 0 0 - 0 0, MB_type: 14344, MV: 0 0[mpeg4 @ 0x6000971e0] , MB_type: 14344, MV: 0 0
I've been following this thread and website for some time and have been looking for a way to have a productive first post. This, however, will not be that productive. Fantastic work everyone who's working on this project. I'll keep tooling around with frames but ... holy smokes you guys are good at this. I don't have a lot to bring to the table.
FRAME0:0:0:-1=FRAME1:0:0:-1=FRAME2:0:0:-1=FRAME3:0:0:-1
FRAME0:0:0:-1=FRAME1:0:0:-1=FRAME2:0:0:-1=FRAME3:0:0:-1=FRAME4:<your mmb commands>
Quote from: Untribium on 05/18/2014 01:19 pmNice work on the P-frames guys! The bits (literally ) and pieces are finally coming together!Can someone more knowledgeable than me and has looked into the bitstream have a look at this and tell me whether it's accurate?http://www.cmlab.csie.ntu.edu.tw/cml/dsp/training/coding/h263/format_p.htmlCould be really helpful for bit flipping edit: Also, is it possible to add the bitstream to the online editor?It seems that that is describing the "6.2.5.2 Video Plane with Short Header" from ISO-IEC-14496-2_2001_MPEG4_Visual.pdf. Also see: "6.3.5.2 Video Plane with Short Header". Not entirely sure.I'm actually not sure our video uses the "short header". I have mostly been focused on the macroblock/variable stuff. But it would be good to confirm, because there could definitely be problems in these headers. This is also a little interesting:Quoteshort_video_header: The short_video_header is an internal flag which is set to 1 when an abbreviated header format is used for video content. This indicates video data which begins with a short_video_start_marker rather than a longer start code such as visual_object_ start_code. The short header format is included herein to provide forward compatibility with video codecs designed using the earlier video coding specification ITU-T Recommendation H.263. All decoders which support video objects shall support both header formats (short_video_header equal to 0 or 1) for the subset of video tools that is expressible in either form.
Nice work on the P-frames guys! The bits (literally ) and pieces are finally coming together!Can someone more knowledgeable than me and has looked into the bitstream have a look at this and tell me whether it's accurate?http://www.cmlab.csie.ntu.edu.tw/cml/dsp/training/coding/h263/format_p.htmlCould be really helpful for bit flipping edit: Also, is it possible to add the bitstream to the online editor?
short_video_header: The short_video_header is an internal flag which is set to 1 when an abbreviated header format is used for video content. This indicates video data which begins with a short_video_start_marker rather than a longer start code such as visual_object_ start_code. The short header format is included herein to provide forward compatibility with video codecs designed using the earlier video coding specification ITU-T Recommendation H.263. All decoders which support video objects shall support both header formats (short_video_header equal to 0 or 1) for the subset of video tools that is expressible in either form.
PPs. I've also attached a slightly altered h263dec.c which now logs the frame number too.
So, it seems all the puzzle pieces are finally getting together, a big congratulation to Arnezami for finding how to handle these P-frames Here the best I could quickly get for the same frames:% I-Frame 169<snip>% Frame 170% 6:1:-1,23:3:9697,40:7:-1,37:8:22779 (strange interlace effect)6:1:-1,23:3:9697,40:7:-1,42:7:19526,3:8:-1,4:8:19780,13:8:-1,15:8:20531,28:8:-1,30:8:21401,37:8:22779 (effect less visible)<snip>And also a gif animation!
A version with the dirt spots numbered for better reference in conversationEdit: Added dirt group 14
...
Frame 72: X:4231:01
Quote from: Marams on 05/20/2014 09:25 amFrame 72: X:4231:01This is very good. I was about to xor through that macroblock myself. Added it to full mmb and fixed some sea alignment.PS. The online editor is not showing log data for me.
Hi guys,To kick this off I created all the original frames for 169 - 188. We can put these in a separate wiki page and try to make them better individually. From time to time we can combine them to make a video/animated gif.
Quote from: arnezami on 05/20/2014 04:17 amHi guys,To kick this off I created all the original frames for 169 - 188. We can put these in a separate wiki page and try to make them better individually. From time to time we can combine them to make a video/animated gif.Hi guys. I'm on the process of creating 15 new wiki pages, following the sections of the video arnezami posted above. Each page will contain the i-frame and 19 p-frames of that section. Everything will be organized in a table just like the one we where using to record our progress on the iframes. The table will include a field to to add a preview and to paste the mmb code used. The page for frames 169 - 188 is ready (http://spacexlanding.wikispaces.com/Frames+169-188). I'll add the rest as we progress other parts of the video. I have also created a central page (http://spacexlanding.wikispaces.com/Progress+using+multi+frame+MMBs) with the description of the tasks and links to the each of the 15 new pages.The old page that recorded the progress on iframes it still there. If you are continue working on single iframes, you can continue to post the results there. However, as we move towards fixing p-frames, eventually all modifications will have to be recorded in the new pages.