You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In memory-writing mode,
we use gf_isom_open using "_gpac_isobmff_redirect" gf_isom_set_write_callback
after setting callback function
When exactly is the callback function called?
I think that gf_isom_finalize and gf_isom_close_segment call the callback function
And
If I want to call the callback function forcely, how to do that?
My plan is that
After making All segments, I calculate all duration of segments and allocate duration using gf_isom_set_movie_duration
then I want to receive moov box data with a duration value assigned to it through callback function.
Can I use on_last_block_start to handle the above situation?
The text was updated successfully, but these errors were encountered:
I found the solution!
But I have Another Question!
After making dash segments,
I tried gf_isom_set_movie_duration and WriteToFile Function (for making movie box that added movie duration using callback function)
styp box is made twice.
I tried to find what problem it is, but failed.
what is the problem?
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you!
Detailed guidelines: https://gpac.io/bug-reporting/
In memory-writing mode,
we use
gf_isom_open
using"_gpac_isobmff_redirect"
gf_isom_set_write_callback
after setting callback function
When exactly is the callback function called?
I think that
gf_isom_finalize
andgf_isom_close_segment
call the callback functionAnd
If I want to call the callback function forcely, how to do that?
My plan is that
After making All segments, I calculate all duration of segments and allocate duration using
gf_isom_set_movie_duration
then I want to receive moov box data with a duration value assigned to it through callback function.
Can I use
on_last_block_start
to handle the above situation?The text was updated successfully, but these errors were encountered: