Quote from: John_L on 05/07/2014 08:19 pmAnd to continue the analogy... a new book will be written this Saturday....lolLet's hope they have changed the page layout to contain additional information to help detect sentence boundaries, errors and such. This macroblock necromancy goes only so far.
And to continue the analogy... a new book will be written this Saturday....lol
Quote from: R7 on 05/07/2014 08:39 pmQuote from: John_L on 05/07/2014 08:19 pmAnd to continue the analogy... a new book will be written this Saturday....lolLet's hope they have changed the page layout to contain additional information to help detect sentence boundaries, errors and such. This macroblock necromancy goes only so far. Should let one of us hop on their plane with an SDR with a patchfeed into their radios.
3) make an analog recording of the telemetry stream..
Quote from: mlindner on 05/07/2014 08:40 pmQuote from: R7 on 05/07/2014 08:39 pmQuote from: John_L on 05/07/2014 08:19 pmAnd to continue the analogy... a new book will be written this Saturday....lolLet's hope they have changed the page layout to contain additional information to help detect sentence boundaries, errors and such. This macroblock necromancy goes only so far. Should let one of us hop on their plane with an SDR with a patchfeed into their radios. three important things that should be communicated back to SpaceX:1) turn on the error correction features in their camera/encoder (probably too late for Saturday's launch.. but maybe)2) turn off interlace3) make an analog recording of the telemetry stream..
Quote from: starsilk on 05/07/2014 08:50 pm3) make an analog recording of the telemetry stream..Would this be analog enough?
Why is anything still recorded using Interlaced processing?
One more note. X doesn't behave quite as you think. The bitmask is inverted. X:pos:1 actually flips the bit 8 positions away from pos. It reads the next 8 bits starting from pos with pos being the MSB of those 8 bits. If you want to flip just the target bit, do X:pos:80.
Quote from: mlindner on 05/07/2014 08:33 pmOne more note. X doesn't behave quite as you think. The bitmask is inverted. X:pos:1 actually flips the bit 8 positions away from pos. It reads the next 8 bits starting from pos with pos being the MSB of those 8 bits. If you want to flip just the target bit, do X:pos:80.Ah, boundary conditions/endianness/alignment, how do I love thee. I start doing this manually, 01,02,04,08,10,20,40,80, increment by 8, then decided to automate it without looking at the source. Empirically, it worked fairly well as a semi-targeted brute force search. The correct one should work better. I'm playing with a #define TRACE build, but don't understand quite what I'm doing when twiddling bits yet to narrow the search range smaller than the whole macroblock.-Bob
Ok, so no additional help from SpaceX tonight at least I'm told, as they are all busy bees with the next launch (including a lot in transit to the Cape). Again, this thread is being watched, big time, and by one rather well known name at SpaceX I'm reliably informed! So stay focused as much as you can with what we've got.I'll get more eyeballs on it when I add a few paras and links to here in my F9 v1.1 Static Fire article tomorrow.
Every block has 6 sub-blocks, 4 luma blocks (brightness) and 2 chroma blocks (color). The 4 luma blocks are the 4 squares in a block you often see. Both color blocks cover the entire block and are two different color planes. https://en.wikipedia.org/wiki/YUV There are 4 Y blocks and 1 U and 1 V block. Each one of those sub blocks references either the block above it or the block to the left of it (they all don't have to reference the same block). Which block they reference is determined on-the-fly (not hardcoded) so if a block is screwed up then it could cause blocks that would reference it, to not reference it or vice versa.
Quote from: mlindner on 05/07/2014 04:20 pmEvery block has 6 sub-blocks, 4 luma blocks (brightness) and 2 chroma blocks (color). The 4 luma blocks are the 4 squares in a block you often see. Both color blocks cover the entire block and are two different color planes. https://en.wikipedia.org/wiki/YUV There are 4 Y blocks and 1 U and 1 V block. Each one of those sub blocks references either the block above it or the block to the left of it (they all don't have to reference the same block). Which block they reference is determined on-the-fly (not hardcoded) so if a block is screwed up then it could cause blocks that would reference it, to not reference it or vice versa.Hmmm, I suspect that color is not really important here, has anyone tried stripping/ignoring the chroma information and just generated "black & white"? The human visual system is *MUCH* more sensitive to intensity then color which is part of why the chroma is sampled at half (or less) of luma in most cases.
How would one go about re-encoding the video with the replacement iframes, what's the command line for ffmpeg?