-
Notifications
You must be signed in to change notification settings - Fork 84
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
read metadata from udta #77
Conversation
Hey @ririsoft, thanks for taking interest in the project. I will take a look soon, thank you! |
Binary = 0x000000, | ||
Text = 0x000001, | ||
Image = 0x00000D, | ||
TempoCpil = 0x000015, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, what type is this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review !
Those are the type used to format data in an ilst
element. They are pretty obvious but TempoCpil
which I have no idea what it is about. I took it from here: https://xhelmboyx.tripod.com/formats/mp4-layout.txt.
Binary
is raw vector of u8, Image
is the same but you know it is an image, Text
should be valid utf_8 data.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I was referring to the TempoCpil
type, but thanks for the clarification! Looks like it's referring to tmpo/cpil flag = 0x000015
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no clue of what it is for and left it for sake of completeness.
Thanks for the PR. I looked over and I like the approach for the metadata handling. I just had one comment above. Otherwise, feel free to continue. Thanks again! |
Thanks ! |
Ok then I rebased onto master and added two more metadata : poster, description. There are more metadata, but none that I am using currently. Do not hesitate to "@" me in an issue if some users are requesting for a particular metadata not implemented yet. Also there are other form of metadata, using XML, that can be embedded. I have almost never encountered such. We will see if an issue on that come one day. Thanks again for your time and review. |
Sounds good. I'll take a look soon and merge if all is good. Thanks again for your contribution! |
Hi @ririsoft, I tried a few of the examples using some video files I usually test, but getting a constant
Same results for other examples as well, including |
I can see the issue on Linux not on Mac. I am investigating further and will submit a fix asap. |
This introduces the 'Metadata' trait to enable access to common video metadata such title, year, cover art and more. Reading 'title', 'description', 'poster' and 'year' metadata is implemented here.
Problem identified and should be fixed : a |
Thanks for the fix. Will check this out soon. |
All good. Thanks again! |
This introduces the 'Metadata' trait to enable access to common video metadata such title, year, cover art and more. Reading 'title', 'description', 'poster' and 'year' metadata is implemented here.
Hello,
First I would like to thank you for your work on 'mp4'. I built several implementations of the mp4 standard in Go and Rust for private use that I cannot share, but I would like to join forces to your open initiative and start to contribute.
My main focus for now is metadata parsing : title, release year, description, cover art and more.
I am starting with a draft pull request to gather early feedback from you : is the direction I am pushing the right approach for metadata handling in
mp4-rust
?This introduces the 'Metadata' trait to enable access to common video metadata such title, year, cover art and more.
Reading 'title' and 'year' metadata is implemented as a proof of concept.
Using a trait allow's for using deep internal mp4 atom structure and shallow copy (such lossy utf8 conversion) while keeping the access to metadata user friendly at top level
Mp4Reader
.Once agreed on the read part and
Metadata
API I will implement the write part in the pull request before you merge.Last : I added a new sample based on open source video Big Buck Bunny with some encoded metadata.
Your comments and request for changes are more than welcome !
Cheers.