cayoenrique
Member
- Messages
- 475
Rainbow tables still have it uses. But as time goes by, providers are adjusting sending padded bytes on the clear and the use of the adaptive filed. So RBT are no good some time. That does not necessary means it is not CSA. Tandberg V3 Logs I seen does not seems to me DES-EBC like powervu, as it has been suggested.
I been reading on MPEG_TS and H.264. Uff!! confusing. some one said ( Reference 4):
Some Reference
Go to reference 1) H.264 Standard. Look at Annex B page 304
At top it reads:
See this is not a Standard it is a Recommendation. Then to make it worst even in the recommendation it reads that
a "NALU Start Code" can be 3 or 4 bytes long!! I found of some one else that think like me. See reference 4):
I will not confuse you anymore. Main Point is that Cudabiss is an old program back when the standard was in fact just Mpeg. And start code was known as a fact as to be 3 bytes 000001:
I look at some logs in Tandberg V3, and for what I seen most part video is H.264. Maybe 0x000001 vs 0x00000001 is the reason why Cudabiss and K2TSET PGFA BF failed. And watch does adaptive field that shift data to the end. Hope it help to those working on this.
I been reading on MPEG_TS and H.264. Uff!! confusing. some one said ( Reference 4):
Code:
there is no single standard H.264 elementary bitstream formatSome Reference
Code:
1) https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-H.264-201304-S!!PDF-E&type=items
2) http://ip.hhi.de/imagecom_G1/assets/pdfs/csvt_overview_0305.pdf
3) http://www.thefullwiki.org/Network_Abstraction_Layer
4) https://stackoverflow.com/questions/24884827/possible-locations-for-sequence-picture-parameter-sets-for-h-264-stream/24890903#24890903Go to reference 1) H.264 Standard. Look at Annex B page 304
At top it reads:
Code:
This annex forms an integral part of this Recommendationa "NALU Start Code" can be 3 or 4 bytes long!! I found of some one else that think like me. See reference 4):
Code:
"NALU Start Codes
A NALU does not contain is its size. Therefore simply concatenating the NALUs to create a stream will not work because you will not know where one stops and the next begins.
The Annex B specification solves this by requiring ‘Start Codes’ to precede each NALU. A start code is 2 or 3 0x00 bytes followed with a 0x01 byte. e.g. 0x000001 or 0x00000001.I will not confuse you anymore. Main Point is that Cudabiss is an old program back when the standard was in fact just Mpeg. And start code was known as a fact as to be 3 bytes 000001:
Code:
packet start code prefix: This is a 24 Bit value, which is always set to 0x000001. It marks the beginning of a PES packet.I look at some logs in Tandberg V3, and for what I seen most part video is H.264. Maybe 0x000001 vs 0x00000001 is the reason why Cudabiss and K2TSET PGFA BF failed. And watch does adaptive field that shift data to the end. Hope it help to those working on this.
Last edited: