Open jantekb opened 1 year ago
To be precise, raw data displayed for "unknown" areas is currently limited to 16 bytes, for performance reasons.
Just for information, I'm going to provide user_data_registered_itu_t_t35
structure parsing for some well-known types (CC / AFD / Bar data) in the next release (v0.2.5).
For CC data it will look as follows:
@jantekb , would such presentation help you to get the information you need in your use case?
Yes, it would if CC means closed caption in this case. I wonder if at least the byte offset would be shown for raw data in the file. That would let people look at it with a hexeditor in special cases. Thanks a lot for the heads up!
vtc-ivanb @.***> ezt írta (időpont: 2023. aug. 1., K 22:57):
To be precise, raw data displayed for "unknown" areas is currently limited to 16 bytes, for performance reasons.
Just for information, I'm going to provide user_data_registered_itu_t_t35 structure parsing for some well-known types (CC / AFD / Bar data) in the next release (v0.2.5).
For CC data it will look as follows: [image: Screenshot 2023-08-02 at 03 49 54] https://user-images.githubusercontent.com/87360808/257639025-68b89dcf-c924-495b-9727-4dba4c3d4052.png
@jantekb https://github.com/jantekb , would such presentation help you to get the information you need in your use case?
— Reply to this email directly, view it on GitHub https://github.com/vtclab/analyzer-public/issues/18#issuecomment-1661082161, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJJQQE45VIBQKWTTPDRR2LXTFUTHANCNFSM6AAAAAA26MEEMQ . You are receiving this because you were mentioned.Message ID: @.***>
@jantekb , v0.2.5 is out, so new presentation of cc_data is already available. Sometimes it feels to me that it can be too detailed. Probably I need to find an alternative way to display closed caption bytes, I'll think about it.
It would be super useful if I could see the complete raw data for SEI messages, currently they are truncated to 25 bytes.