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
While working a little bit with some VP8-based streams, I have noticed something interesting related to IVF writers. Is it possible that the value written for the IVF frame timestamp is incorrect?
With these changes, I can handle variable stream framerate when reading frames.
I can provide a PR, if this change is acceptable.
Your environment.
Version: Release or SHA
Browser: include version
Other Information - stacktraces, related issues, suggestions how to fix, links for us to have context
What did you do?
What did you expect?
What happened?
The text was updated successfully, but these errors were encountered:
radekg
changed the title
IVF writer writing invalid value into frame header?
IVF writer writing invalid timestamp value into frame headers?
Jan 10, 2023
Are you still interested in doing this! Anything we can do to improve the timing handling with IVF would be greatly appreciated. I haven't looked into it lately, but is a common complaint.
Hey maintainers, thank you for this awesome work.
While working a little bit with some VP8-based streams, I have noticed something interesting related to IVF writers. Is it possible that the value written for the IVF frame timestamp is incorrect?
And, of course, Duck IVF says that 8 bytes at offset 4 are 64-bit presentation timestamp: https://wiki.multimedia.cx/index.php/Duck_IVF.
Shouldn't the writer write the RTP header timestamp value into the IVF frame header?
I would propose the following:
with the following call-site changes:
With these changes, I can handle variable stream framerate when reading frames.
I can provide a PR, if this change is acceptable.
Your environment.
What did you do?
What did you expect?
What happened?
The text was updated successfully, but these errors were encountered: