Talk:ReplayGain 1.0 specification: Difference between revisions
(Created page with "== Musepack == Hi, there is an inaccuracy about Musepack files. Although they use APEv2 for metadata, replaygain is stored in the file header by specification, see [http://www.e…") |
No edit summary |
||
| Line 1: | Line 1: | ||
== Musepack == | == Musepack == | ||
Hi, there is an inaccuracy about Musepack files. Although they use APEv2 for metadata, replaygain is stored in the file header by specification, see [http:// | Hi, there is an inaccuracy about Musepack files. Although they use APEv2 for metadata, replaygain is stored in the file header by specification, see [http://http://trac.musepack.net/trac/wiki/SV8Specification here]. Actually, this is the first format introducing APEv2 tags and native replaygain support. | ||
So, every musepack compliant player must read the RG data from the header rather then APEv2. | So, every musepack compliant player must read the RG data from the header rather then APEv2. | ||
[[User:Antonski|Antonski]] 14:19, 4 May 2011 (UTC) | |||
Revision as of 14:19, 4 May 2011
Musepack
Hi, there is an inaccuracy about Musepack files. Although they use APEv2 for metadata, replaygain is stored in the file header by specification, see here. Actually, this is the first format introducing APEv2 tags and native replaygain support. So, every musepack compliant player must read the RG data from the header rather then APEv2. Antonski 14:19, 4 May 2011 (UTC)