Quote from: gospacex on 05/06/2014 11:28 amQuote from: arnezami on 05/05/2014 04:53 amIn order to fix this you could try to restore the bitstream itself. But this is very hard to do and extremely time consuming (fixing compressed data is no joke!). The worse is: you don't know when the bad bits stop.If data errors are random, if garbled bits are not occurring in bursts, but randomly, then fixing garbled block entails inverting one bit and looking whether image got better in the block and after it. If it got worse, you inverted a "good" bit. If it got better, you inverted a corrupted one.Thankfully, there aren't than many bits in, say, 32 bytes - only 256.Nope. Errors tend to come in bursts I've seen, which makes sense.
Quote from: arnezami on 05/05/2014 04:53 amIn order to fix this you could try to restore the bitstream itself. But this is very hard to do and extremely time consuming (fixing compressed data is no joke!). The worse is: you don't know when the bad bits stop.If data errors are random, if garbled bits are not occurring in bursts, but randomly, then fixing garbled block entails inverting one bit and looking whether image got better in the block and after it. If it got worse, you inverted a "good" bit. If it got better, you inverted a corrupted one.Thankfully, there aren't than many bits in, say, 32 bytes - only 256.
In order to fix this you could try to restore the bitstream itself. But this is very hard to do and extremely time consuming (fixing compressed data is no joke!). The worse is: you don't know when the bad bits stop.
I've started experimenting with I-Frame 12 and doing some automated analysis. better.png was produced with -mmb 0:0:-1,1:0:583Legend for -annotated images:* Red circles annotate the MBs that disappeared from base.png after the modification* Green circles annotate the MBs that appeared in the better.png after -mmb modification* Crossed MBs are ones that considered corrupted by ffmpegI'd be glad to get feedack if anyone sees any additional information from the annotated images.
Just curious, but why is the time stamp so clear? And does it help to know it should be much further to lower left corner?
Hack job on iframe7. I can do better, but probably am calling quits for tonight.-mmb X:18494:01,19:05:-1,19:06:20616,15:12:-1,17:12:44357
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+EditorWhich is really cool and awesome. People don't have to compile anything now.
Quote from: mlindner on 05/06/2014 09:53 pmQuote 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+EditorWhich is really cool and awesome. People don't have to compile anything now.Working like a charm! I got this with iframe 12 and 0:0:1001: