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
Apparently, any files created from a continuous stream of data lack cues (key frame meta header). This makes ffmpeg choke when trying to create a Dash manifest (error when parsing cues).
I see there are exported structs to work with Cue Points, but I'm not sure how to use them and I don't know much about video encoding and WebM container specification.
Do you have any recommendations on how to add cues initialisation section to make the resulting file dash compatible? Maybe I can add the cue point section with this package after the initial file had been created.
Thanks!
The text was updated successfully, but these errors were encountered:
I will try to implement it myself, but would really appreciate an example of how I can do it. If you don't have time for it, please feel free to close the issue.
Hi,
Thank you for such an amazing package!
I'm trying to write a WebM file from an RTP (webrtc stream) like this: https://github.com/pion/example-webrtc-applications/tree/master/save-to-webm
Apparently, any files created from a continuous stream of data lack cues (key frame meta header). This makes ffmpeg choke when trying to create a Dash manifest (error when parsing cues).
I see there are exported structs to work with Cue Points, but I'm not sure how to use them and I don't know much about video encoding and WebM container specification.
Do you have any recommendations on how to add cues initialisation section to make the resulting file dash compatible? Maybe I can add the cue point section with this package after the initial file had been created.
Thanks!
The text was updated successfully, but these errors were encountered: