For example, as I posted earlier, there are spikes in noise level where error rate spikes above 30% for a few thousand bytes. If this occurred in a null packet it might look to you like a mildly corrupt data packet, but in reality it is junk.
The goal of cleaning the raw stream is to give the folks here the very best mpg4-img files to tweak visually.
Here are my I-Frames.
Going to port my iframe8 changes to this new iframe8.
Alpha 3 of my transport stream search and repair tool is finished.
To find out how many different TS-PIDs exists, I counted all different "0x47xxxx" appearances in raw_edit1.ts:This are all which occured 20 times or more:20 471be820 4733e821 470fe825 4703e963 47470374 47402081 474000269 4743e84968 471fff15016 4703e8I think the first 4 are permutations of the last ones by bitflips.4743e8 and 4703e8 have the same PID,When one checks where 474703 is found, one sees that the next byte is E8. So the first 47 is the last byte of a previous packet, and therefore 474703 is not part of a TS-header. So we end up with only 4 PIDs (13 bit long):0x0000, 0x0020, 0x03E8,0x1FFF Each PID has its own continuity counter, which should help deciding which packet is which. With some different flagbits we end with the following TS-headers:0x4740001W0x4740201X0x4703E81Y, 0x4703E83Y and 0x4743E83Y0x471FFF1Zwith the 4 different counters W,X,Y,Z
PID HEX COUNT 1000 x03E8 15592 -- Video 8191 x1FFF 5070 -- Null packet 0 x0000 84 32 x0020 755096 x13E8 49 -- 1 bit off from 10001001 x03E9 48 -- 1 bit off from 1000 904 x0388 40 -- 2 bit off from 10007144 x1BE8 30 -- 2 bit off from 1000 984 x03D8 29 -- 2 bit off from 10001003 x03EB 29 -- 1 bit off from 1000 616 x0268 283048 x0BE8 281512 x05E8 272000 x07D0 27 996 x03E4 261008 x03F0 261002 x03EA 254095 x0FFF 24 500 x01F4 231006 x03EE 234072 x0FE8 238190 x1FFE 23 808 x0328 191004 x03EC 19 992 x03E0 17 232 x00E8 16 488 x01E8 16 968 x03C8 161016 x03F8 162024 x07E8 166120 x17E8 15 872 x0368 14 936 x03A8 144000 x0FA0 14 680 x02A8 13 744 x02E8 131005 x03ED 132047 x07FF 132536 x09E8 128167 x1FE7 118189 x1FFD 117807 x1E7F 10 840 x0348 95119 x13FF 97423 x1CFF 98095 x1F9F 98127 x1FBF 98185 x1FF9 9 125 x007D 8 994 x03E2 8
Quote from: mlindner on 05/12/2014 11:11 pmGoing to port my iframe8 changes to this new iframe8.How do you do that?
I think your 4-PID theory is correct.
Hi guys,I just noticed that there are no B-frames in the file. Only I-frames and P-frames.Quote./ffprobe try1.ts -show_frames > frames.txtNot sure yet what the implications are yet. Hopefully it will get easier that way.Regards,arnezami
./ffprobe try1.ts -show_frames > frames.txt
Quote from: Shanuson on 05/12/2014 07:06 pmTo find out how many different TS-PIDs exists, I counted all different "0x47xxxx" appearances in raw_edit1.ts:...For completeness, I counted PIDs by absolute bit position in the raw.ts, here are the top 50:...I think your 4-PID theory is correct.
To find out how many different TS-PIDs exists, I counted all different "0x47xxxx" appearances in raw_edit1.ts:...
Quote from: theshadow27 on 05/13/2014 12:58 amQuote from: Shanuson on 05/12/2014 07:06 pmTo find out how many different TS-PIDs exists, I counted all different "0x47xxxx" appearances in raw_edit1.ts:...For completeness, I counted PIDs by absolute bit position in the raw.ts, here are the top 50:...I think your 4-PID theory is correct. Out of curiosity, did anyone do the counting (based on absolute bit position) on the streams that were re-aligned to 188 bits? I was under the impression that raw.ts was not, so this might throw off your count if you're doing absolute bit position.How many differenct PID permutations might that produce?Then it might help for Adaptation's tool to be able to display/color based on the PID permutations. That might also help identify what type of PID a corrupted packet is supposed to be.Just a suggestion after digesting all of your work the last few pages.
Quote from: Shanuson on 05/12/2014 10:27 pmHere are my I-Frames.Wow. That iframe 6 is almost perfect.
Quote from: Adaptation on 05/12/2014 06:11 amAlpha 3 of my transport stream search and repair tool is finished. Were you able to find any other sub-byte shifts aside from the one we already know about?
Quote from: saliva_sweet on 05/12/2014 11:28 pmQuote from: mlindner on 05/12/2014 11:11 pmGoing to port my iframe8 changes to this new iframe8.How do you do that?Apparently the new and the old iframe8 are byte identical. Was hoping some of the issues would be fixed, but apparently not.