Timestamp properties - git merge master #1339
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ut we do not support it (strukturag#1337)
|
What is the current status of the standard? Is it stable? I could move the timestamp API into the experimental header so that it is in the main branch, but not enabled by default until we have the final standard. |
|
Yes, I think using the experimental header for now is a good idea.. |
|
The TAI timestamp standard is currently at the FDAM stage, which is very stable. A final approval is projected for February 2025. |
|
I've merged it into master with the TAI function in heif_experimental. Be aware that I also renamed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Keep the timestamp-properties branch up to date with master.
The bitstream.h started to diverge.