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_id3v2 cannot read chapter markers from file #16
Comments
Was this ever implemented? |
Hi @SeanOMik, sorry, this hasn't been fixed yet. It's a bit tedious to fix so it's been low priority. I'll probably loop back around to it after v0.5 is published. |
Tommoa
added a commit
to Tommoa/symphonia
that referenced
this issue
Oct 8, 2022
These were standardised in https://id3.org/id3v2-chapters-1.0. Something I initially considered (and did) was to use `Cue`s and `CuePoint`s instead of creating new types, but decided against it because: - `Cue` is tied to the format, whereas these are tied to the metadata. - According to the spec, chapters can overlap, and so must have a duration. - It is unclear to me what the index should be. - `CuePoint`s cannot have another `CuePoint` within them, which may be an issue for multi-level tables of content. - Chapters and tables of contents would end up mixed as `Cue`s despite being different types. Resolves: pdeljanov#16
Tommoa
added a commit
to Tommoa/symphonia
that referenced
this issue
Oct 10, 2022
These were standardised in https://id3.org/id3v2-chapters-1.0. Something I initially considered (and did) was to use `Cue`s and `CuePoint`s instead of creating new types, but decided against it because: - `Cue` is tied to the format, whereas these are tied to the metadata. - According to the spec, chapters can overlap, and so must have a duration. - It is unclear to me what the index should be. - `CuePoint`s cannot have another `CuePoint` within them, which may be an issue for multi-level tables of content. - Chapters and tables of contents would end up mixed as `Cue`s despite being different types. Resolves: pdeljanov#16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I could have missed where this data might show up, but taking some sample podcasts from Mac Power Users. (e.g. https://www.podtrac.com/pts/redirect.mp3/traffic.libsyn.com/secure/relaympu/mpu554.mp3)
Dumping out tags from the
Metadata
gives me thisWhereas ffprobe on the same file will output:
The text was updated successfully, but these errors were encountered: