APEv2 specification - Revision history

Electron: added info about placement of the tag

2008-02-24T21:45:42Z

added info about placement of the tag

← Older revision		Revision as of 21:45, 24 February 2008
Line 17:		Line 17:
	\|}		\|}

	APE ~~tags~~ items should be sorted ascending by size. When streaming parts of the APE tags can be dropped to reduce danger of drop outs between titles. This is not a ~~MUST~~, but ~~STRONGLY~~ recommended. Actually the items should be sorted by importance/byte, but this is not feasible. Only break this rule if you add less important small items and you don't want to rewrite the whole tag. An APE tag at the end of a file (strongly recommended) must have at least a footer, a APE tag in the beginning of a file (strongly unrecommended) must have at least a header.		APE tag items should be sorted ascending by size. When streaming, parts of the APE tags can be dropped to reduce danger of drop outs between titles. This is not a ''must'', but ''strongly'' recommended. Actually the items should be sorted by importance/byte, but this is not feasible. Only break this rule if you add less important small items and you don't want to rewrite the whole tag. An APE tag at the end of a file (strongly recommended) must have at least a footer, an APE tag in the beginning of a file (strongly unrecommended) must have at least a header.
			When located at the end of an [[MP3]] file, an APE tag should be placed after the the last frame, just before the [[ID3v1]] tag (if any).

	[[Category:Metadata]]		[[Category:Metadata]]

Pepoluan: Category:Metadata

2006-09-11T21:16:10Z

Category:Metadata

← Older revision		Revision as of 21:16, 11 September 2006
Line 18:		Line 18:

	APE tags items should be sorted ascending by size. When streaming parts of the APE tags can be dropped to reduce danger of drop outs between titles. This is not a MUST, but STRONGLY recommended. Actually the items should be sorted by importance/byte, but this is not feasible. Only break this rule if you add less important small items and you don't want to rewrite the whole tag. An APE tag at the end of a file (strongly recommended) must have at least a footer, a APE tag in the beginning of a file (strongly unrecommended) must have at least a header.		APE tags items should be sorted ascending by size. When streaming parts of the APE tags can be dropped to reduce danger of drop outs between titles. This is not a MUST, but STRONGLY recommended. Actually the items should be sorted by importance/byte, but this is not feasible. Only break this rule if you add less important small items and you don't want to rewrite the whole tag. An APE tag at the end of a file (strongly recommended) must have at least a footer, a APE tag in the beginning of a file (strongly unrecommended) must have at least a header.

			[[Category:Metadata]]

Andrew179 at 21:59, 13 July 2005

2005-07-13T21:59:46Z

← Older revision		Revision as of 21:59, 13 July 2005
Line 17:		Line 17:
	\|}		\|}

	APE tags items should be sorted ascending by size. When streaming parts of the APE tags can be dropped to reduce danger of drop outs between titles. This is not a MUST, but STRONGLY recommended. Actually the items should be sorted by importance/byte, but this is not feasible. Only break this rule if you add less important small items and you don't want to rewrite the whole tag. An APE tag at the end of a file (strongly recommended) must have at least a footer, a APE tag in the beginning of a file (strongly ~~unrcommneded~~) must have at least a header.		APE tags items should be sorted ascending by size. When streaming parts of the APE tags can be dropped to reduce danger of drop outs between titles. This is not a MUST, but STRONGLY recommended. Actually the items should be sorted by importance/byte, but this is not feasible. Only break this rule if you add less important small items and you don't want to rewrite the whole tag. An APE tag at the end of a file (strongly recommended) must have at least a footer, a APE tag in the beginning of a file (strongly unrecommended) must have at least a header.

Rjamorim: Footer actually links to header...

2005-04-26T00:34:45Z

Footer actually links to header...

← Older revision		Revision as of 00:34, 26 April 2005
Line 14:		Line 14:
	\|[[APE Tag Item]] n \|\| 10.. bytes		\|[[APE Tag Item]] n \|\| 10.. bytes
	\|-		\|-
	\|[[APE Tags Footer]] \|\| 32 bytes		\|[[APE Tags Header\|APE Tags Footer]] \|\| 32 bytes
	\|}		\|}

	APE tags items should be sorted ascending by size. When streaming parts of the APE tags can be dropped to reduce danger of drop outs between titles. This is not a MUST, but STRONGLY recommended. Actually the items should be sorted by importance/byte, but this is not feasible. Only break this rule if you add less important small items and you don't want to rewrite the whole tag. An APE tag at the end of a file (strongly recommended) must have at least a footer, a APE tag in the beginning of a file (strongly unrcommneded) must have at least a header.		APE tags items should be sorted ascending by size. When streaming parts of the APE tags can be dropped to reduce danger of drop outs between titles. This is not a MUST, but STRONGLY recommended. Actually the items should be sorted by importance/byte, but this is not feasible. Only break this rule if you add less important small items and you don't want to rewrite the whole tag. An APE tag at the end of a file (strongly recommended) must have at least a footer, a APE tag in the beginning of a file (strongly unrcommneded) must have at least a header.

Rjamorim: Initial commit

2005-04-26T00:33:53Z

Initial commit

New page

This is how information is laid out in an [[APEv2]] tag:

{| border="1" cellspacing="1"
|width="120px"| [[APE Tags Header]] ||width="80px"| 32 bytes
|-
|[[APE Tag Item]] 1 || 10.. bytes
|-
|[[APE Tag Item]] 2 || 10.. bytes
|-
|... || 10.. bytes
|-
|[[APE Tag Item]] n-1 || 10.. bytes
|-
|[[APE Tag Item]] n || 10.. bytes
|-
|[[APE Tags Footer]] || 32 bytes
|}

APE tags items should be sorted ascending by size. When streaming parts of the APE tags can be dropped to reduce danger of drop outs between titles. This is not a MUST, but STRONGLY recommended. Actually the items should be sorted by importance/byte, but this is not feasible. Only break this rule if you add less important small items and you don't want to rewrite the whole tag. An APE tag at the end of a file (strongly recommended) must have at least a footer, a APE tag in the beginning of a file (strongly unrcommneded) must have at least a header.