Help:Standard article - Revision history

Beto at 13:55, 20 September 2006

2006-09-20T13:55:28Z

← Older revision		Revision as of 13:55, 20 September 2006
Line 199:		Line 199:
	* [http://en.wikipedia.org/wiki/ASCII ASCII]		* [http://en.wikipedia.org/wiki/ASCII ASCII]
	\|}		\|}

			[[Category:Help]]
			[[Category:Guideline]]

Beto at 13:52, 20 September 2006

2006-09-20T13:52:29Z

← Older revision		Revision as of 13:52, 20 September 2006
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
			__NOEDITSECTION__
	<!-- This is a standard article guideline. Please use it for creating		<!-- This is a standard article guideline. Please use it for creating
	articles in this wiki.-->		articles in this wiki.-->

Beto at 13:51, 20 September 2006

2006-09-20T13:51:35Z

Show changes

Elliottmobile: /* Credits */

2006-09-20T13:47:24Z

Credits

← Older revision		Revision as of 13:47, 20 September 2006
Line 136:		Line 136:

	<nowiki>===Credits===</nowiki>		<nowiki>===Credits===</nowiki>

	Text © Menno Bakker - <nowiki>[http://www.audiocoding.com/ Audiocoding]</nowiki>		Text © Menno Bakker - <nowiki>[http://www.audiocoding.com/ Audiocoding]</nowiki>

Elliottmobile: /* Credits */

2006-09-20T13:47:05Z

Credits

← Older revision		Revision as of 13:47, 20 September 2006
Line 135:		Line 135:
	<nowiki># ''Inside NT's Object Manager''. Introduction.</nowiki>		<nowiki># ''Inside NT's Object Manager''. Introduction.</nowiki>

	===Credits===		<nowiki>===Credits===</nowiki>
	Text © Menno Bakker - <nowiki>[http://www.audiocoding.com/ Audiocoding]</nowiki>		Text © Menno Bakker - <nowiki>[http://www.audiocoding.com/ Audiocoding]</nowiki>

Beto: /* Style guideline */

2006-09-20T13:13:30Z

Style guideline

← Older revision		Revision as of 13:13, 20 September 2006
Line 42:		Line 42:

	==Style guideline==		==Style guideline==
	~~'''~~Introduction~~'''<br />~~		===Introduction===
	Every article should start with a ''summary of the topic'' detailed in the article. This is the very first thing to be written before any section.		Every article should start with a ''summary of the topic'' detailed in the article. This is the very first thing to be written before any section.

	''Example:''		'''Example:'''
	{\|		{\|
			\|'''wikicode'''\|\|'''page rendereded'''
	\|-		\|-
	\|style="border: 1px solid #777777; font-family:courier new;"\|		\|style="border: 1px solid #777777; font-family:courier new; width:50%;"\|
	<nowiki>'''Joint stereo'''</nowiki> coding methods try to increase the coding efficiency when encoding stereo signals by exploiting commonalties between the left and right channel signal.		<nowiki>'''Joint stereo'''</nowiki> coding methods try to increase the coding efficiency when encoding stereo signals by exploiting commonalties between the left and right channel signal.
			\|style="border: 1px solid #777777; width:50%;"\|
			'''Joint stereo''' coding methods try to increase the coding efficiency when encoding stereo signals by exploiting commonalties between the left and right channel signal.
	\|}		\|}

Line 57:		Line 60:
	''Example:''		''Example:''
	{\|		{\|
			\|'''wikicode'''\|\|'''page rendereded'''
	\|-		\|-
	\|style="border: 1px solid #777777; font-family:courier new;"\|		\|style="border: 1px solid #777777; font-family:courier new;"\|
	<nowiki>==~~Additional information~~==</nowiki>		<nowiki>==History==</nowiki>

			LAME development began around mid-1998. Mike Cheng started it as a patch against the 8hz-MP3 encoder sources. After some quality concerns raised by others, he decided to start from scratch based on the dist10 sources. That branch (a patch against the reference sources) became LAME 2.0, and only on LAME 3.81 they got rid of all dist10 code, making LAME a completely new program-not a mere patch of an existing encoder.

			The project quickly became a team effort. Mike Cheng eventually left leadership and started working on tooLAME, an MP2 encoder. Mark Taylor became leader and released version 3.0 featuring gpsycho, a new psychoacoustic model developed by him.

			Nowadays LAME is considered the best MP3 encoder at mid-high bitrates and features the best VBR model among MP3 implementations, mostly thanks to the dedicated work of talented developers like Takehiro Tominaga, Naoki Shibata, Darin Morrison, Gabriel Bouvigne, Robert Hegemann, etc. And development is still going on...
			\|style="border: 1px solid #777777; width:50%;"\|
			==History==

			LAME development began around mid-1998. Mike Cheng started it as a patch against the 8hz-MP3 encoder sources. After some quality concerns raised by others, he decided to start from scratch based on the dist10 sources. That branch (a patch against the reference sources) became LAME 2.0, and only on LAME 3.81 they got rid of all dist10 code, making LAME a completely new program-not a mere patch of an existing encoder.

	~~Some more details~~, ~~history~~ and ~~examples about joint stereo & mid/side coding:~~		The project quickly became a team effort. Mike Cheng eventually left leadership and started working on tooLAME, an MP2 encoder. Mark Taylor became leader and released version 3.0 featuring gpsycho, a new psychoacoustic model developed by him.

	~~mid/side can be lossless like obviously in Lossless formats Flac, Wavpack, Monkey's Audio (ape) etc., but in lossy encoders~~ the encoder ~~tries to do~~ the best ~~to minimize all losses in perception. And here the encoder has not only to deal with stereo modes, but also with mids, highs etc. etc.~~		Nowadays LAME is considered the best MP3 encoder at mid-high bitrates and features the best VBR model among MP3 implementations, mostly thanks to the dedicated work of talented developers like Takehiro Tominaga, Naoki Shibata, Darin Morrison, Gabriel Bouvigne, Robert Hegemann, etc. And development is still going on...
	~~So, regarding lossy formats like~~ MP3 ~~(Lame~~, ~~Fraunhofer, Xing), Musepack (MPC), Vorbis etc., the mid/side coding might be even mathematical lossless, might be perceptual lossless (=transparent), or not so lossless at all at low bitrates.~~
	~~So, it depends in~~ the ~~lossy formats about the quality~~ of ~~mid/side (js) coding.~~
	~~From obvious bad sounding bugs~~ like ~~in some old Fraunhofer mp3 ("Radium hack")~~, ~~not so optimized perfomance like in mp3-Xing~~, ~~up to the optimized js-modes in mp3-Lame~~, ~~which offer frame-dependent stereo or mid/side coding to achieve maximum qualities. And advanced formats like mp3-lame~~, ~~Musepack-MPC or Vorbis-ogg offer increasing js(mid/side//stereo)qualities in increasing general quality (q) levels~~, ~~examples:~~
	~~Mp3-Lame inside the presets eg~~. ~~-V quality levels, with different -msfix values up to the "nssafejoint" mode in 320 kbit cbr~~.
	~~Musepack-MPC inside the various q-levels/presets and the --ms x switch~~.
	~~Vorbis in its presets, 1 example above q6 the "lossless stereo coupling"~~.
	\|}		\|}

Beto at 13:01, 20 September 2006

2006-09-20T13:01:24Z

@@ Line 1: / Line 1: @@
 <!-- This is a standard article guideline. Please use it for creating
 articles in this wiki.-->
 <font style="color:red; font-weight:bold;">This is a guideline. Please use it for creating articles in this wiki.</font>
 The aim of this guideline is to provide ways to standardize articles in this wiki. Every article should abide to the ''general'' structure below (in wiki code):
@@ Line 39: / Line 41: @@
 </pre>
 '''Introduction'''<br />
 Every article should start with a ''summary of the topic'' detailed in the article. This is the very first thing to be written before any section.
 ''Example:''
-{|style="padding: 3px;"|
+{|
 |-
-|style="border: 1px solid #DDDDDD; font-family:courier new;"|
+|style="border: 1px solid #777777; font-family:courier new;"|
 <nowiki>'''Joint stereo'''</nowiki> coding methods try to increase the coding efficiency when encoding stereo signals by exploiting commonalties between the left and right channel signal.
 |}
@@ Line 53: / Line 56: @@
 ''Example:''
-{|style="padding: 3px;"|
+{|
 |-
-|style="border: 1px solid #DDDDDD; font-family:courier new;"|
+|style="border: 1px solid #777777; font-family:courier new;"|
 <nowiki>==Additional information==</nowiki>
@@ Line 73: / Line 76: @@
 ''Example:''
-{|style="padding: 3px;"|
+{|
 |-
-|style="border: 1px solid #DDDDDD; font-family:courier new;"|
+|style="border: 1px solid #777777; font-family:courier new;"|
 <nowiki>==Recommended encoder settings==</nowiki>
@@ Line 91: / Line 94: @@
 VBR is best used to target a specific quality level, instead of a specific bitrate. The final file size of a VBR encode is less predictable than with ABR, but the quality is usually better.
 |}

Beto at 02:03, 20 September 2006

2006-09-20T02:03:20Z

← Older revision		Revision as of 02:03, 20 September 2006
Line 1:		Line 1:
	<!-- This is a standard article guideline. Please use it for creating		<!-- This is a standard article guideline. Please use it for creating
	articles in this wiki.-->		articles in this wiki.-->
	~~{{stub}}~~
	<font style="color:red; font-weight:bold;">This is a guideline. Please use it for creating articles in this wiki.</font>		<font style="color:red; font-weight:bold;">This is a guideline. Please use it for creating articles in this wiki.</font>

	The aim of this guideline is to provide ways to standardize articles in this wiki. Every article should abide to the ''general'' structure below:		The aim of this guideline is to provide ways to standardize articles in this wiki. Every article should abide to the ''general'' structure below (in wiki code):

	<pre>		<pre>
Line 41:		Line 40:

	'''Introduction'''<br />		'''Introduction'''<br />
	Every article should start with a summary of the topic detailed in the article. This is the very first thing to be written before any section.		Every article should start with a ''summary of the topic'' detailed in the article. This is the very first thing to be written before any section.

	''Example:''		''Example:''
Line 51:		Line 50:

	'''Lead sections'''<br />		'''Lead sections'''<br />
	An article may have any number or lead sections. Within these sections you should put any relevant information about the section topic including pictures, media files, formulas etc.		An article may have any number or ''lead sections''. Within these sections you should put any relevant information about the section topic including pictures, media files, formulas etc.

	''Example:''		''Example:''
Line 68:		Line 67:
	Musepack-MPC inside the various q-levels/presets and the --ms x switch.		Musepack-MPC inside the various q-levels/presets and the --ms x switch.
	Vorbis in its presets, 1 example above q6 the "lossless stereo coupling".		Vorbis in its presets, 1 example above q6 the "lossless stereo coupling".
			\|}

			'''Subsections'''<br />
			Use subsections whenever necessary to make information easily readable.

			''Example:''
			{\|style="padding: 3px;"\|
			\|-
			\|style="border: 1px solid #DDDDDD; font-family:courier new;"\|
			<nowiki>==Recommended encoder settings==</nowiki>

			This section describes the Hydrogenaudio recommended settings to be used with LAME for highest quality MP3 encoding.

			These settings require LAME 3.94 or later. LAME 3.97beta3 is the recommended version.

			Avoid using alpha (a) versions of LAME. More often than not those are exclusively for testing purposes. Use them only if you want to help developers with feedback.

			(...)

			<nowiki>===VBR (variable bitrate) settings===</nowiki>

			<nowiki>'''[[VBR]]:''' ''variable bitrate mode. Use variable bitrate modes when the goal is to achieve a fixed level of quality using the lowest possible bitrate.''</nowiki>

			VBR is best used to target a specific quality level, instead of a specific bitrate. The final file size of a VBR encode is less predictable than with ABR, but the quality is usually better.
	\|}		\|}

Beto at 21:48, 19 September 2006

2006-09-19T21:48:00Z

← Older revision		Revision as of 21:48, 19 September 2006
Line 9:		Line 9:
	Introduction		Introduction

	==Lead section==		==Lead section #1==
	This is the lead section of the article.		This is the lead section of the article.

	===Subsection #1===		===Subsection #1.1===
	This is a subsection of the article.		This is a subsection of the article.

	====Subsection #2====		====Subsection #1.2====
			This is a sub-subsection of the article.

			==Lead section #2==
			This is the lead section of the article.

			===Subsection #2.1===
			This is a subsection of the article.

			====Subsection #2.2====
	This is a sub-subsection of the article.		This is a sub-subsection of the article.

Line 35:		Line 44:

	''Example:''		''Example:''
	{\| style="~~border~~: ~~1px solid #DDDDDD~~;"\|		{\|style="padding: 3px;"\|
	\|-		\|-
	\|style="border: 1px solid #DDDDDD;"\|		\|style="border: 1px solid #DDDDDD; font-family:courier new;"\|
	'''Joint stereo''' coding methods try to increase the coding efficiency when encoding stereo signals by exploiting commonalties between the left and right channel signal.		<nowiki>'''Joint stereo'''</nowiki> coding methods try to increase the coding efficiency when encoding stereo signals by exploiting commonalties between the left and right channel signal.
	\|}		\|}

	~~After~~ the ~~introduction~~		'''Lead sections'''<br />
			An article may have any number or lead sections. Within these sections you should put any relevant information about the section topic including pictures, media files, formulas etc.

	<<~~include a brief summary~~ of the ~~article main topic here~~ (~~this is mandatory~~)>>		''Example:''
			{\|style="padding: 3px;"\|
			\|-
			\|style="border: 1px solid #DDDDDD; font-family:courier new;"\|
			<nowiki>==Additional information==</nowiki>

			Some more details, history and examples about joint stereo & mid/side coding:

			mid/side can be lossless like obviously in Lossless formats Flac, Wavpack, Monkey's Audio (ape) etc., but in lossy encoders the encoder tries to do the best to minimize all losses in perception. And here the encoder has not only to deal with stereo modes, but also with mids, highs etc. etc.
			So, regarding lossy formats like MP3 (Lame, Fraunhofer, Xing), Musepack (MPC), Vorbis etc., the mid/side coding might be even mathematical lossless, might be perceptual lossless (=transparent), or not so lossless at all at low bitrates.
			So, it depends in the lossy formats about the quality of mid/side (js) coding.
			From obvious bad sounding bugs like in some old Fraunhofer mp3 ("Radium hack"), not so optimized perfomance like in mp3-Xing, up to the optimized js-modes in mp3-Lame, which offer frame-dependent stereo or mid/side coding to achieve maximum qualities. And advanced formats like mp3-lame, Musepack-MPC or Vorbis-ogg offer increasing js(mid/side//stereo)qualities in increasing general quality (q) levels, examples:
			Mp3-Lame inside the presets eg. -V quality levels, with different -msfix values up to the "nssafejoint" mode in 320 kbit cbr.
			Musepack-MPC inside the various q-levels/presets and the --ms x switch.
			Vorbis in its presets, 1 example above q6 the "lossless stereo coupling".
			\|}

Beto: complementing

2006-09-19T15:40:48Z

complementing

← Older revision		Revision as of 15:40, 19 September 2006
Line 1:		Line 1:
	<!-- This is a standard article ~~template~~. Please use it for creating		<!-- This is a standard article guideline. Please use it for creating
	articles in this wiki.-->		articles in this wiki.-->
	{{stub}}		{{stub}}
	<font style="color:red; font-weight:bold;">This is a ~~standard article~~ guideline. Please use it for creating articles in this wiki.</font>		<font style="color:red; font-weight:bold;">This is a guideline. Please use it for creating articles in this wiki.</font>

			The aim of this guideline is to provide ways to standardize articles in this wiki. Every article should abide to the ''general'' structure below:

	<~~<include a brief summary of the article main topic here (this is mandatory)>~~>		<pre>
			Introduction

	==Lead section==		==Lead section==
	This is the lead section of the article ~~(mandatory)~~.		This is the lead section of the article.

	===Subsection #1===		===Subsection #1===
	This is a subsection of the article ~~(optional)~~.		This is a subsection of the article.

	====Subsection #2====		====Subsection #2====
	This is a sub-subsection of the article ~~(optional)~~.		This is a sub-subsection of the article.

	==See also==		==See also==
	~~Standard see~~ also section.		See also section.

	==Notes and references==		==Notes and references==
	~~Standard notes~~ and references section.		Notes and references section.

	==Further reading and bibliography==		==Further reading and bibliography==
	~~Standard reading~~ and bibliography section.		Reading and bibliography section.

	==External links==		==External links==
	~~Standard external~~ links section.		External links section.
			</pre>

			'''Introduction'''<br />
			Every article should start with a summary of the topic detailed in the article. This is the very first thing to be written before any section.

			''Example:''
			{\| style="border: 1px solid #DDDDDD;"\|
			\|-
			\|style="border: 1px solid #DDDDDD;"\|
			'''Joint stereo''' coding methods try to increase the coding efficiency when encoding stereo signals by exploiting commonalties between the left and right channel signal.
			\|}

			After the introduction

			<<include a brief summary of the article main topic here (this is mandatory)>>