Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extra data / SPS and PPS information #756

Closed
tino197 opened this issue Apr 27, 2014 · 3 comments
Closed

extra data / SPS and PPS information #756

tino197 opened this issue Apr 27, 2014 · 3 comments

Comments

@tino197
Copy link

tino197 commented Apr 27, 2014

HI.
Sorry for the beginner question.
I need to send to decoder the "Extra Data" in avcC format.
How can i extract this info from Encoder?
If there is no such option then how do i extract the
"Sequence parameter set"
and the
"Picture parameter set"

for writing the "Extra Data"

Thanks.

@huili2
Copy link
Collaborator

huili2 commented Apr 28, 2014

There is not an interface to extract the parameter set information.
If you can run the encoder, you may set some breakpoints in WelsWriteSpsSyntax(), then you can print each of the members for information.
Or if you can run the decoder, you may get the information similarly by in ParseSps().

@tino197
Copy link
Author

tino197 commented Apr 28, 2014

1)I will try to put BP on WelsWriteSpsSyntax to get SPS.
But what about the PPS?
How can i get the PPS = "Picture parameter set"
for writing the "Extra Data"
?
2) Is there an option to extract these 2 SPS/PPS from the encoder stream?
I use the Console application code to write the encoded stream.
Can i from these 2 in the stream itself - i.e like byte 10 to 100 in the stream for example ...
3)How can i extract the other field i need for the extra data which are:
version
profile
compatibility
level
NAL units length size - 1

Thanks

@huili2
Copy link
Collaborator

huili2 commented Apr 29, 2014

  1. there's a similar func named "WelsWritePpsSyntax()" for PPS.
  2. you can open the encoded ".264" file with MS visual studio, and search 00 00 00 01 67 as the start of SPS, and 00 00 00 01 68 as the start of PPS. You can also try to use some bitstream analysis tools online to look into the bitstream. But they may not be free.
  3. you can modify the decoder with print information on ParseSps(), ParsePps() at specific place to get these information. Better way is to use tools mentioned above.

@tino197 tino197 closed this as completed Apr 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants