Talk:Original ReplayGain specification - Revision history

Skamp: Skamp moved page Talk:ReplayGain 1.0 specification to Talk:Original ReplayGain specification: Confusion about having two distinct, numbered versions of ReplayGain

2026-01-22T19:29:14Z

Skamp moved page Talk:ReplayGain 1.0 specification to Talk:Original ReplayGain specification: Confusion about having two distinct, numbered versions of ReplayGain

← Older revision	Revision as of 19:29, 22 January 2026
(No difference)

Notat: links to threads

2012-01-24T23:50:23Z

links to threads

← Older revision		Revision as of 23:50, 24 January 2012
Line 4:		Line 4:
	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)		[[User:Antonski\|Antonski]] 14:19, 4 May 2011 (UTC)

			==Development discussion threads==
			*[http://www.hydrogenaudio.org/forums/index.php?showtopic=1709 Flaw in ReplayGain spec]
			*[http://www.hydrogenaudio.org/forums/index.php?showtopic=62374 Replay Gain Site, Why does it look like a museum?]
			*[http://www.hydrogenaudio.org/forums/index.php?showtopic=83397 Does Replay gain work differtly in Media monkey, Foobar and Media Monkey given 2 differnt Results]
			*[http://www.hydrogenaudio.org/forums/index.php?showtopic=85536 Replay Gain specification, update in progress]
			*[http://www.hydrogenaudio.org/forums/index.php?showtopic=69568 ReplayGain equal loudness filter]
			*[http://www.hydrogenaudio.org/forums/index.php?showtopic=85834 Replay Gain tagging, ID3, LAME, Others?]
			*[http://www.hydrogenaudio.org/forums/index.php?showtopic=86745 ReplayGain player recommendations]
			*[http://www.hydrogenaudio.org/forums/index.php?showtopic=87442 ReplayGain specification complete, official launch 25 March proposed]

Notat: moved Talk:ReplayGain specification to Talk:ReplayGain 1.0 specification: Add version number

2011-07-23T16:35:37Z

moved Talk:ReplayGain specification to Talk:ReplayGain 1.0 specification: Add version number

← Older revision	Revision as of 16:35, 23 July 2011
(No difference)

Antonski: specification link corrected

2011-05-04T14:20:44Z

specification link corrected

← Older revision		Revision as of 14:20, 4 May 2011
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://~~http://trac.musepack.net/trac/wiki/SV8Specification here]. Actually, this is the first format introducing APEv2 tags and native replaygain support.		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://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)		[[User:Antonski\|Antonski]] 14:19, 4 May 2011 (UTC)

Antonski at 14:19, 4 May 2011

2011-05-04T14:19:46Z

← Older revision		Revision as of 14:19, 4 May 2011
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://~~www~~.~~example~~.~~com~~ here]. Actually, this is the first format introducing APEv2 tags and native replaygain support.		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)

Antonski: 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…"

2011-04-29T00:13:42Z

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…"

New page

== 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.example.com 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.