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
How to use BufferCallbackParams with gstreamer #1268
Comments
I even tested with first muxing to mpegts at gstreamer and then fill buffer with the mpegts packets but still getting same error at packager. |
Hi Felibol, Recently I came across this issue, despite is a bit old: are you still trying to solve it? Your code should work perfectly, just be careful your TS stream is standard thus having the necessary tables (PAT, PMT, ...), and in the implementation of the function 'readInputBuffer', respect the TS packet boundary (that is, do not "cut" de buffer in the middle of a TS packet). In consequence, for each input buffer, make sure you are synchronizing to TS packet boundary (start code 0x47) and you are sending entire TS packets (once synchronized, you should fill the buffer with a multiple of 188 bytes). Kind Regards. |
Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including |
System info
Operating System: 18.04.5 LTS (Bionic Beaver)
Shaka Packager Version: main branch cc9a691
Question
I am trying to integrate shaka packager to gstreamer pipeline with using c-api.
I have added gstreamer app sink and receiving encoded H265 video byte data. I have also configured shaka packager like below
Inside read_func, I am filling buffer and expecting packaging to produce fragmented mp4 HLS stream. But I am getting below error
As I understand packager expect already packaged content at the input not the raw encoded data. My question is can I use shaka packager to directly package raw encoded video and encoded audio data? If possible can you also share a minimal example to show buffer callback params usage?
Thanks.
The text was updated successfully, but these errors were encountered: