[ID3 Dev] ID3v2.5
Michal Vician
id3v2 at audiott.com
Mon Feb 27 15:27:40 PST 2006
Nice attempt :-) Some things sounds really good and I think the new tag
version should be done this way - quote: "Simplicity is a good thing...".
------------
My comments:
>- no extended header
>- no padding
>- no footer
* agreed
>- encoding is apply to all metadata (all frames)
* I don't think this is good idea. I think that encoding should be
declared for each frame separately.
>- all metadata are syncronized or codified in such format that this will
> not alter mp3 frames, including ID3v2.5 Metadata Identifier
* Agreed. But there sould be preserved the way of synchonizing v2.4. I
mean, it should be possible to synchronize each frame and header
separately (don't do the same mistake as in v2.3)...
>- there is only text and objects (binary) frames, put in it what you wont
> and name it how you wont. For text frames will be apply metadata encoding,
> for binary not.
* OK
>- structure version (tag version), will be in ID3v2.5 Identifier
* What Identifier?
>- encoding is applying only on frames, text frames!
>- no tag restrictions
>- no syncsafe integers, no!
* agreed
> ID3v2.5 Frame:
>
> - Full Frame Size
> - Frame Name (at end is a null terminated char, so frame name is not
> fixed)
> - IsBinary
> - Content
* amazing :-)
> Thats all, from my perspective. Simplicity is a good thing, is you think
> that thi is a good idea or not please comment. Anyway i thinking about
> sizes... and native frames.
Yes. I think that the idea is really good. I hope others think the same.
However, there is much to discuss about.
I also think that simplicity is the way :-)
Best regards
Miso
> D:\Music\Albums\Electronica\Goa Trance\The History Of Goa Trance\09. The
> Muses Rapt - Spiritual Healing.mp3 :
>
> -----------------------------------------------------------------------------------------------
> content metadata
> -----------------------------------------------------------------------------------------------
> audio content
> -----------------------------------------------------------------------------------------------
>
> content metadata:
>
> -----------------------------------------------------------------------------------------------
> ID3v2.5 Identifier | Full Metadata Size | Text Frames Encoding
> ->
> --------------------------- -------------------------------
> -----------------------------
>
> Changes (from ID3v2.4):
>
> - no extended header
> - no padding
> - no footer
> - encoding is apply to all metadata (all frames)
> - all metadata are syncronized or codified in such format that this
> will not alter
> mp3 frames, including ID3v2.5 Metadata Identifier
> - there is only text and objects (binary) frames, put in it what you
> wont and name it
> how you wont. For text frames will be apply metadata encoding, for
> binary not.
> - structure version (tag version), will be in ID3v2.5 Identifier.
> - encoding is applying only on frames, text frames!
> - no tag restrictions
> - no syncsafe integers, no!
> -
>
>
> -------------------------------------------------------------------------------------------
> -> Frames ...
> -----------------------------------------------------------------------------------------------
>
> ID3v2.5 Frame:
>
> Full Frame Size
> Frame Name (at end is a null terminated char, so frame name is not
> fixed)
> IsBinary
> Content
>
>
> Thats all, from my perspective. Simplicity is a good thing, is you think
> that thi is a good idea or not please comment. Anyway i thinking about
> sizes... and native frames.
>
>
> ---------------------------------
> To help you stay safe and secure online, we've developed the all new
> Yahoo! Security Centre.
---
Michal Vician
id3v2 at audiott.com
http://www.audiott.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org
More information about the ID3v2
mailing list