APEv1 specification - Revision history

Synthetic Soul: Noted that APEv1 may not be used at the beginning of a file.

2010-07-30T10:00:07Z

Noted that APEv1 may not be used at the beginning of a file.

← Older revision		Revision as of 10:00, 30 July 2010
Line 17:		Line 17:
	\|}		\|}

	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~~.		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 APEv1 tag at the end of a file must have at least a footer, APEv1 tags may never be used at the beginning of a file (unlike [[APEv2]] tags).
	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).		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]]

Electron at 21:44, 24 February 2008

2008-02-24T21:44:17Z

← Older revision		Revision as of 21:44, 24 February 2008
Line 2:		Line 2:

	The only difference between APEv1 and [[APEv2]] is that APEv1 has no header. Therefore, it is strongly recommended that developers adopt v2 instead of v1 as standard tagging system for their formats.		The only difference between APEv1 and [[APEv2]] is that APEv1 has no header. Therefore, it is strongly recommended that developers adopt v2 instead of v1 as standard tagging system for their formats.


	{\| border="1" cellspacing="1"		{\| border="1" cellspacing="1"
Line 18:		Line 17:
	\|}		\|}

			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.
	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.		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:15:54Z

Category:Metadata

← Older revision		Revision as of 21:15, 11 September 2006
Line 20:		Line 20:

	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]]

Reglib: spelling

2006-04-24T06:59:40Z

spelling

← Older revision		Revision as of 06:59, 24 April 2006
Line 19:		Line 19:


	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 at 15:45, 27 April 2005

2005-04-27T15:45:57Z

← Older revision		Revision as of 15:45, 27 April 2005
Line 2:		Line 2:

	The only difference between APEv1 and [[APEv2]] is that APEv1 has no header. Therefore, it is strongly recommended that developers adopt v2 instead of v1 as standard tagging system for their formats.		The only difference between APEv1 and [[APEv2]] is that APEv1 has no header. Therefore, it is strongly recommended that developers adopt v2 instead of v1 as standard tagging system for their formats.


	{\| border="1" cellspacing="1"		{\| border="1" cellspacing="1"
Line 16:		Line 17:
	\|[[APE Tags Header\|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-27T15:45:30Z

Initial commit

New page

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

The only difference between APEv1 and [[APEv2]] is that APEv1 has no header. Therefore, it is strongly recommended that developers adopt v2 instead of v1 as standard tagging system for their formats.

{| border="1" cellspacing="1"
|width="120px"| [[APE Tag Item]] 1 ||width="80px"| 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 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.