Hydrogenaudio Knowledgebase - User contributions [en]

File:Foobar2000 Logo.png

2008-04-15T17:00:01Z

Kjoonlee: not GFDL

This logo was uploaded by a third party, under a fair-use claim.

Use of this logo is not covered by the GFDL.

The original logo by picmixer is being used to illustrate the program on the [[foobar2000:foobar2000]] page.

User:Kjoonlee/monobook.js

2008-01-02T22:36:23Z

Kjoonlee:

// http://en.wikipedia.org/wiki/User%3ALupin/popups.js

function siteArticlePath(){ return 'index.php?title='; }
function siteBotInterfacePath(){ return ''; }

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js'
+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');

popupDelay=0.7;
popupHideDelay=0.2;

User:Kjoonlee/monobook.js

2008-01-02T22:33:53Z

Kjoonlee: try fix

// http://en.wikipedia.org/wiki/User%3ALupin/popups.js

function siteArticlePath(){ return 'index.php'; }
function siteBotInterfacePath(){ return ''; }

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js'
+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');

popupDelay=0.7;
popupHideDelay=0.2;

User:Kjoonlee/monobook.js

2006-12-27T16:39:09Z

Kjoonlee: mention URL instead

// http://en.wikipedia.org/wiki/User%3ALupin/popups.js

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js'
+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');

popupDelay=0.7;
popupHideDelay=0.2;

User:Kjoonlee/monobook.js

2006-12-27T16:38:23Z

Kjoonlee:

// [[:w:en:User:Lupin/popups.js]]

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js'
+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');

popupDelay=0.7;
popupHideDelay=0.2;

User:Kjoonlee/monobook.js

2006-12-27T16:37:50Z

Kjoonlee: popups tool

// [[User:Lupin/popups.js]]

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js'
+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');

popupDelay=0.7;
popupHideDelay=0.2;

User talk:Kjoonlee

2006-12-27T16:36:57Z

Kjoonlee: notice

<div class="usermessage plainlinks">Please use a [http://wiki.hydrogenaudio.org/index.php?title=User_talk:Kjoonlee&action=edit&section=new new section] or edit a relevant section. Thank you.</div>
This page will be archived when the table of contents fills up my view. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 10:36, 27 December 2006 (CST)
==Hi==
Hi Kjoonlee!

Um, nothing important. I just have an ... irrational dislike of <u style="color:red">redlinks</u> in the [[Special:Wantedpages|Wanted Pages]] specialthing. Heh. {{smiley|)}} --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 16:37, 2 October 2006 (CDT)

Gapless playback

2006-12-22T00:17:43Z

Kjoonlee: /* Alternative solutions */ pseudo-gapless

'''Gapless playback''' is the seamless playback of sequential audio tracks in digital audio formats. It allows live music or consecutive tracks to be heard exactly as they are mastered, without gaps between tracks.

==Why gaps occur==
There are two main reasons why gaps occur during playback.

===Compression scheme artifacts===
Most lossy audio compression schemes add a small amount of silence to the beginning of a track. One reason that this happens is because many such schemes involve a time/frequency domain transform (such as an [[MDCT]]) which can introduce gaps called encoder delay. These gaps can be enlarged at decode time when a reverse-MDCT is performed, because the reverse transform will also introduce gaps (decoder delay) of its own. Another factor is the fact that transforms act on data in units of fixed-size blocks. In order for the audio signal to be encoded in its entirety, small amounts of silence are appended to the input before the transform. If the amount of padded silence is not accounted for, the padding will be decoded together with the audio data, also introducing gaps between tracks. Due to the introduction of such gaps, the playtime of the audio data is often slightly increased. (See [http://lame.sourceforge.net/tech-FAQ.txt LAME Technical FAQ])

This issue is technical but also standards-related. The popular [[MP3]] standard, for example, defines no way to record the amount of delay or padding for later removal. Also, the encoder delay may vary from encoder to encoder, making automatic removal difficult. (See [http://mp3decoders.mp3-tech.org/decoders_lame.html lame v3.81 and 3.87 beta mp3 decoding quality test results] for a table of encoder delay values.) Even if two tracks are decompressed and merged into a single track, a gap will usually remain between them. More recent compressed audio formats have been designed to address this problem, and can therefore produce gapless audio if played back correctly.

===Poor design===
Even when the audio file itself does not contain undesirable gaps, software/firmware/hardware design often adds gaps during playback. In some cases, software closes and re-opens the output stream when switching tracks, causing the hardware to create a very short "click". This problem is solved in more sophisticated designs of gapless playback.

A different design problem relates to software/firmware/hardware which are not ready to seamlessly move to the next track by the time the current track is complete. In this scenario, the listener is left waiting in silence as the player locates the next file, reads it, decodes the first blocks if necessary and then starts loading the buffer for playback. The gap can be as much as half a second, or even more — very noticeable in "continuous" music such as certain classical or dance genres.

Many older audio players on personal computers do not implement the required buffering to play gapless audio. Some of these rely on third-party gapless audio plug-ins to buffer output. Some newer players and newer versions of old players now support gapless playback directly.

==Testing for gapless==
The best way is by using ''Test Samples'' listed at the end of this page.

Some people attempts to detect gapless by generating pure tones, and encoding them into a lossy format. This is not recommended for two reasons:

1. Unless the first tone ends at 0 level and the second tone starts at 0 level, a glitch will be heard during transition.
2. Some decoders chop off the end and/or the start of the audio data. So the playback will be perceived as gapless, while it is actually not.

See the discussion on [http://www.hydrogenaudio.org/forums/index.php?showtopic=40995&st=0&p=360548&#entry360548 this HA thread].

==Optimal solution==
It is possible to store metadata in the audio to explicitly declare the playtime, and/or the amount of padding/delays introduced in the encoding process. This information can be used to ensure that playtime will remain constant after decoding with no added silence. The audio playback software must be able to recognize the metadata, and trim the decoded audio as necessary.

The software can then take care to keep the output stream open between tracks. It must also buffer the beginning of the following track in the same way it buffers the current track during normal playback.

If the compression method supports gapless playback, the software properly decodes the audio data and metadata, the next track is buffered and ready to play, and the output stream remains open between tracks, optimal gapless audio is achieved. A collection of consecutive tracks will then play in the same way they were mastered, allowing the listener to hear their album as the author intended.

==Alternative solutions==
Digital signal processor ([[DSP]]) plugins can be used to detect silence between tracks and trim the audio as necessary on playback. This is not an optimal solution because it does not always produce results identical to the source. Sometimes an artist may intentionally leave silence at track boundaries for dramatic effect; removing this silence also removes that effect.

It can also be difficult to properly implement silence removal. If the silence threshold is too low and the track contains decoder artifacts, the software may not recognise some silences. Conversely, if the threshold is too high, the software may remove entire sections of quiet music at the beginning or end of a track.

DSP plugins can also be used to cross-fade between tracks. This eliminates gaps that some listeners find distracting, but also greatly alters the audio data and is not always desirable. In particular, when tracks are meant to be played together and perform the transition at high volume, cross-fading results in a large volume drop.

Both of these alternate solutions are typically used to address compression methods that do not support the metadata for gapless playback. Like the optimal solution, they still require buffering and not closing the output stream; however, they require more computations, making them less efficient. In portable digital audio players, this can mean a reduced playing time on batteries.

Due to the drawbacks of the alternative solutions above, some listeners dislike their negative effects more than the gap they attempt to remove. Another problem is that the solutions above do nothing to prevent the output stream from being closed and reopened at track boundaries; some measures can be taken to simulate a gapless output stream, but they are not always successful and side-effects may occur.

Another alternative is to ignore track boundaries, encoding a single collection of tracks as a single compressed file, relying on [[cuesheet]]s (or something similar) for navigation. While this method results in gapless playback within the collection of tracks with consecutive playback, it can be unwieldy due to the possibly large size of the resulting compressed file. Furthermore, unless the playback software or hardware can recognize the cue sheets, navigating between tracks may be difficult.

==Format support==
Since [[lossless]] data compression excludes the possibility of the introduction of padding, all lossless audio file formats are inherently gapless. The following [[lossy]] audio file formats have provisions for gapless encoding.

*[[Ogg Vorbis]]
*[[Speex]]

Some other formats do not officially support gapless encoding, but some implementations of encoders or decoders may handle gapless metadata.

*[[LAME]]-encoded MP3 can be gapless with players that support the LAME Mp3 info tag.
*[[AAC]] in [[MP4]] encoded with Nero Digital from [[Nero AG]] can be gapless with [[foobar2000]].
*AAC in MP4 encoded with iTunes 7.0 can be gapless with iTunes 7.0 and latest foobar2000.

==Gapless solutions==
* [[foobar2000]]: Optimal gapless playback
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=18530 Otachan's in_!mpg123]: A gapless [[MP3]] decoder for [[Winamp]]
:'''Note:''' Winamp 5.2 implements gapless playback in its built-in MP3 decoder.

==Test samples==
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=40998]: Samples for testing gapless playback abilities
* [http://guruboolez.free.fr/samples/gapless/gapless_WAVPACK_free_of_right.zip]: 17 very short gapless samples (2 MB)

[[Category:Technical]]

Gapless playback

2006-12-22T00:11:46Z

Kjoonlee: /* Compression scheme artifacts */ minor fix

'''Gapless playback''' is the seamless playback of sequential audio tracks in digital audio formats. It allows live music or consecutive tracks to be heard exactly as they are mastered, without gaps between tracks.

==Why gaps occur==
There are two main reasons why gaps occur during playback.

===Compression scheme artifacts===
Most lossy audio compression schemes add a small amount of silence to the beginning of a track. One reason that this happens is because many such schemes involve a time/frequency domain transform (such as an [[MDCT]]) which can introduce gaps called encoder delay. These gaps can be enlarged at decode time when a reverse-MDCT is performed, because the reverse transform will also introduce gaps (decoder delay) of its own. Another factor is the fact that transforms act on data in units of fixed-size blocks. In order for the audio signal to be encoded in its entirety, small amounts of silence are appended to the input before the transform. If the amount of padded silence is not accounted for, the padding will be decoded together with the audio data, also introducing gaps between tracks. Due to the introduction of such gaps, the playtime of the audio data is often slightly increased. (See [http://lame.sourceforge.net/tech-FAQ.txt LAME Technical FAQ])

This issue is technical but also standards-related. The popular [[MP3]] standard, for example, defines no way to record the amount of delay or padding for later removal. Also, the encoder delay may vary from encoder to encoder, making automatic removal difficult. (See [http://mp3decoders.mp3-tech.org/decoders_lame.html lame v3.81 and 3.87 beta mp3 decoding quality test results] for a table of encoder delay values.) Even if two tracks are decompressed and merged into a single track, a gap will usually remain between them. More recent compressed audio formats have been designed to address this problem, and can therefore produce gapless audio if played back correctly.

===Poor design===
Even when the audio file itself does not contain undesirable gaps, software/firmware/hardware design often adds gaps during playback. In some cases, software closes and re-opens the output stream when switching tracks, causing the hardware to create a very short "click". This problem is solved in more sophisticated designs of gapless playback.

A different design problem relates to software/firmware/hardware which are not ready to seamlessly move to the next track by the time the current track is complete. In this scenario, the listener is left waiting in silence as the player locates the next file, reads it, decodes the first blocks if necessary and then starts loading the buffer for playback. The gap can be as much as half a second, or even more — very noticeable in "continuous" music such as certain classical or dance genres.

Many older audio players on personal computers do not implement the required buffering to play gapless audio. Some of these rely on third-party gapless audio plug-ins to buffer output. Some newer players and newer versions of old players now support gapless playback directly.

==Testing for gapless==
The best way is by using ''Test Samples'' listed at the end of this page.

Some people attempts to detect gapless by generating pure tones, and encoding them into a lossy format. This is not recommended for two reasons:

1. Unless the first tone ends at 0 level and the second tone starts at 0 level, a glitch will be heard during transition.
2. Some decoders chop off the end and/or the start of the audio data. So the playback will be perceived as gapless, while it is actually not.

See the discussion on [http://www.hydrogenaudio.org/forums/index.php?showtopic=40995&st=0&p=360548&#entry360548 this HA thread].

==Optimal solution==
It is possible to store metadata in the audio to explicitly declare the playtime, and/or the amount of padding/delays introduced in the encoding process. This information can be used to ensure that playtime will remain constant after decoding with no added silence. The audio playback software must be able to recognize the metadata, and trim the decoded audio as necessary.

The software can then take care to keep the output stream open between tracks. It must also buffer the beginning of the following track in the same way it buffers the current track during normal playback.

If the compression method supports gapless playback, the software properly decodes the audio data and metadata, the next track is buffered and ready to play, and the output stream remains open between tracks, optimal gapless audio is achieved. A collection of consecutive tracks will then play in the same way they were mastered, allowing the listener to hear their album as the author intended.

==Alternative solutions==
Digital signal processor ([[DSP]]) plugins can be used to detect silence between tracks and trim the audio as necessary on playback. This is not an optimal solution because it does not always produce results identical to the source. Sometimes an artist may intentionally leave silence at track boundaries for dramatic effect; removing this silence also removes that effect.

It can also be difficult to properly implement silence removal. If the silence threshold is too low and the track contains decoder artifacts, the software may not recognise some silences. Conversely, if the threshold is too high, the software may remove entire sections of quiet music at the beginning or end of a track.

DSP plugins can also be used to cross-fade between tracks. This eliminates gaps that some listeners find distracting, but also greatly alters the audio data and is not always desirable. In particular, when tracks are meant to be played together and perform the transition at high volume, cross-fading results in a large volume drop.

Both of these alternate solutions are typically used to address compression methods that do not support the metadata for gapless playback. Like the optimal solution, they still require buffering and not closing the output stream; however, they require more computations, making them less efficient. In portable digital audio players, this can mean a reduced playing time on batteries.

Due to the drawbacks of the alternative solutions above, some listeners dislike their negative effects more than the gap they attempt to remove.

Another alternative is to ignore track boundaries, encoding a single collection of tracks as a single compressed file, relying on [[cuesheet]]s (or something similar) for navigation. While this method results in gapless playback within the collection of tracks, it can be unwieldy due to the possibly large size of the resulting compressed file. Furthermore, unless the playback software or hardware can recognize the cue sheets, navigating between tracks may be difficult.

==Format support==
Since [[lossless]] data compression excludes the possibility of the introduction of padding, all lossless audio file formats are inherently gapless. The following [[lossy]] audio file formats have provisions for gapless encoding.

*[[Ogg Vorbis]]
*[[Speex]]

Some other formats do not officially support gapless encoding, but some implementations of encoders or decoders may handle gapless metadata.

*[[LAME]]-encoded MP3 can be gapless with players that support the LAME Mp3 info tag.
*[[AAC]] in [[MP4]] encoded with Nero Digital from [[Nero AG]] can be gapless with [[foobar2000]].
*AAC in MP4 encoded with iTunes 7.0 can be gapless with iTunes 7.0 and latest foobar2000.

==Gapless solutions==
* [[foobar2000]]: Optimal gapless playback
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=18530 Otachan's in_!mpg123]: A gapless [[MP3]] decoder for [[Winamp]]
:'''Note:''' Winamp 5.2 implements gapless playback in its built-in MP3 decoder.

==Test samples==
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=40998]: Samples for testing gapless playback abilities
* [http://guruboolez.free.fr/samples/gapless/gapless_WAVPACK_free_of_right.zip]: 17 very short gapless samples (2 MB)

[[Category:Technical]]

Gapless playback

2006-12-22T00:11:00Z

Kjoonlee: /* Why gaps occur */ sync with Wikipedia

'''Gapless playback''' is the seamless playback of sequential audio tracks in digital audio formats. It allows live music or consecutive tracks to be heard exactly as they are mastered, without gaps between tracks.

==Why gaps occur==
There are two main reasons why gaps occur during playback.

===Compression scheme artifacts===
Most lossy audio compression schemes add a small amount of silence to the beginning of a track. One reason that this happens is because many such schemes involve a time/frequency domain transform (such as an [[MDCT]]) which can introduce gaps called encoder delay. These gaps can be enlarged at decode time when a reverse-MDCT is performed, because the reverse transform will also introduce gaps (decoder delay) of its own. Another factor is the fact that transforms act on data in units of fixed-size blocks. In order for the audio signal to be encoded in its entirety, small amounts of silence are appended to the input before the transform. If the amount of padded silence is not accounted for, the padding will be decoded together with the audio data, also introducing gaps between tracks. Due to the introduction of such gaps, the playtime of the audio data is often slightly increased. (See [http://lame.sourceforge.net/tech-FAQ.txt LAME Technical FAQ])

This issue is technical but also standards-related. The popular [[MP3]] standard, for example, defines no way to record the amount of delay or padding for later removal. Also, the encoder delay may vary from encoder to encoder, making automatic removal difficult. (See [http://mp3decoders.mp3-tech.org/decoders_lame.html lame v3.81 and 3.87 beta mp3 decoding quality test results] for a table.) Features a table of encoder delay values.</ref) Even if two tracks are decompressed and merged into a single track, a gap will usually remain between them. More recent compressed audio formats have been designed to address this problem, and can therefore produce gapless audio if played back correctly.

===Poor design===
Even when the audio file itself does not contain undesirable gaps, software/firmware/hardware design often adds gaps during playback. In some cases, software closes and re-opens the output stream when switching tracks, causing the hardware to create a very short "click". This problem is solved in more sophisticated designs of gapless playback.

A different design problem relates to software/firmware/hardware which are not ready to seamlessly move to the next track by the time the current track is complete. In this scenario, the listener is left waiting in silence as the player locates the next file, reads it, decodes the first blocks if necessary and then starts loading the buffer for playback. The gap can be as much as half a second, or even more — very noticeable in "continuous" music such as certain classical or dance genres.

Many older audio players on personal computers do not implement the required buffering to play gapless audio. Some of these rely on third-party gapless audio plug-ins to buffer output. Some newer players and newer versions of old players now support gapless playback directly.

==Testing for gapless==
The best way is by using ''Test Samples'' listed at the end of this page.

Some people attempts to detect gapless by generating pure tones, and encoding them into a lossy format. This is not recommended for two reasons:

1. Unless the first tone ends at 0 level and the second tone starts at 0 level, a glitch will be heard during transition.
2. Some decoders chop off the end and/or the start of the audio data. So the playback will be perceived as gapless, while it is actually not.

See the discussion on [http://www.hydrogenaudio.org/forums/index.php?showtopic=40995&st=0&p=360548&#entry360548 this HA thread].

==Optimal solution==
It is possible to store metadata in the audio to explicitly declare the playtime, and/or the amount of padding/delays introduced in the encoding process. This information can be used to ensure that playtime will remain constant after decoding with no added silence. The audio playback software must be able to recognize the metadata, and trim the decoded audio as necessary.

The software can then take care to keep the output stream open between tracks. It must also buffer the beginning of the following track in the same way it buffers the current track during normal playback.

If the compression method supports gapless playback, the software properly decodes the audio data and metadata, the next track is buffered and ready to play, and the output stream remains open between tracks, optimal gapless audio is achieved. A collection of consecutive tracks will then play in the same way they were mastered, allowing the listener to hear their album as the author intended.

==Alternative solutions==
Digital signal processor ([[DSP]]) plugins can be used to detect silence between tracks and trim the audio as necessary on playback. This is not an optimal solution because it does not always produce results identical to the source. Sometimes an artist may intentionally leave silence at track boundaries for dramatic effect; removing this silence also removes that effect.

It can also be difficult to properly implement silence removal. If the silence threshold is too low and the track contains decoder artifacts, the software may not recognise some silences. Conversely, if the threshold is too high, the software may remove entire sections of quiet music at the beginning or end of a track.

DSP plugins can also be used to cross-fade between tracks. This eliminates gaps that some listeners find distracting, but also greatly alters the audio data and is not always desirable. In particular, when tracks are meant to be played together and perform the transition at high volume, cross-fading results in a large volume drop.

Both of these alternate solutions are typically used to address compression methods that do not support the metadata for gapless playback. Like the optimal solution, they still require buffering and not closing the output stream; however, they require more computations, making them less efficient. In portable digital audio players, this can mean a reduced playing time on batteries.

Due to the drawbacks of the alternative solutions above, some listeners dislike their negative effects more than the gap they attempt to remove.

Another alternative is to ignore track boundaries, encoding a single collection of tracks as a single compressed file, relying on [[cuesheet]]s (or something similar) for navigation. While this method results in gapless playback within the collection of tracks, it can be unwieldy due to the possibly large size of the resulting compressed file. Furthermore, unless the playback software or hardware can recognize the cue sheets, navigating between tracks may be difficult.

==Format support==
Since [[lossless]] data compression excludes the possibility of the introduction of padding, all lossless audio file formats are inherently gapless. The following [[lossy]] audio file formats have provisions for gapless encoding.

*[[Ogg Vorbis]]
*[[Speex]]

Some other formats do not officially support gapless encoding, but some implementations of encoders or decoders may handle gapless metadata.

*[[LAME]]-encoded MP3 can be gapless with players that support the LAME Mp3 info tag.
*[[AAC]] in [[MP4]] encoded with Nero Digital from [[Nero AG]] can be gapless with [[foobar2000]].
*AAC in MP4 encoded with iTunes 7.0 can be gapless with iTunes 7.0 and latest foobar2000.

==Gapless solutions==
* [[foobar2000]]: Optimal gapless playback
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=18530 Otachan's in_!mpg123]: A gapless [[MP3]] decoder for [[Winamp]]
:'''Note:''' Winamp 5.2 implements gapless playback in its built-in MP3 decoder.

==Test samples==
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=40998]: Samples for testing gapless playback abilities
* [http://guruboolez.free.fr/samples/gapless/gapless_WAVPACK_free_of_right.zip]: 17 very short gapless samples (2 MB)

[[Category:Technical]]

Gapless playback

2006-10-23T12:25:28Z

Kjoonlee: /* Format support */ iTunes

'''Gapless playback''' is the seamless playback of sequential audio tracks in digital audio formats. It allows live music or consecutive tracks to be heard exactly as they are mastered, without gaps between tracks.

==Why gaps occur==
Most lossy audio compression schemes involve a time/frequency domain transform. Such transforms cannot deal with arbitrary amounts of data, and instead act on blocks of data at a time. In order for the audio signal to be encoded in its entirety, small amounts of silence are prepended and appended to the input before the transform. If the amount of padded silence is not accounted for, the playtime of the audio data may not be equal before and after the compression. In such cases, the silence will be decoded together with the audio data, introducing gaps between tracks.

Most audio playback software will also close the audio output stream when switching tracks, introducing gaps or making existing gaps larger. Unless the beginning of the next track is buffered and introduced immediately when the current track ends, gaps will occur.

Some compression methods such as the popular [[MP3]] can be problematic because the MP3 standard defines no way to record the amount of padding for later removal. Even if two tracks are decompressed and merged into a single track, a gap will remain between them. More recent audio formats have been designed to address this problem, and will produce gapless audio if played back correctly.

==Testing for gapless==
The best way is by using ''Test Samples'' listed at the end of this page.

Some people attempts to detect gapless by generating pure tones, and encoding them into a lossy format. This is not recommended for two reasons:

1. Unless the first tone ends at 0 level and the second tone starts at 0 level, a glitch will be heard during transition.
2. Some decoders chop off the end and/or the start of the audio data. So the playback will be perceived as gapless, while it is actually not.

See the discussion on [http://www.hydrogenaudio.org/forums/index.php?showtopic=40995&st=0&p=360548&#entry360548 this HA thread].

==Optimal solution==
It is possible to store metadata in the audio to explicitly declare the playtime, and/or the amount of padding/delays introduced in the encoding process. This information can be used to ensure that playtime will remain constant after decoding with no added silence. The audio playback software must be able to recognize the metadata, and trim the decoded audio as necessary.

The software can then take care to keep the output stream open between tracks. It must also buffer the beginning of the following track in the same way it buffers the current track during normal playback.

If the compression method supports gapless playback, the software properly decodes the audio data and metadata, the next track is buffered and ready to play, and the output stream remains open between tracks, optimal gapless audio is achieved. A collection of consecutive tracks will then play in the same way they were mastered, allowing the listener to hear their album as the author intended.

==Alternative solutions==
Digital signal processor ([[DSP]]) plugins can be used to detect silence between tracks and trim the audio as necessary on playback. This is not an optimal solution because it does not always produce results identical to the source. Sometimes an artist may intentionally leave silence at track boundaries for dramatic effect; removing this silence also removes that effect.

It can also be difficult to properly implement silence removal. If the silence threshold is too low and the track contains decoder artifacts, the software may not recognise some silences. Conversely, if the threshold is too high, the software may remove entire sections of quiet music at the beginning or end of a track.

DSP plugins can also be used to cross-fade between tracks. This eliminates gaps that some listeners find distracting, but also greatly alters the audio data and is not always desirable. In particular, when tracks are meant to be played together and perform the transition at high volume, cross-fading results in a large volume drop.

Both of these alternate solutions are typically used to address compression methods that do not support the metadata for gapless playback. Like the optimal solution, they still require buffering and not closing the output stream; however, they require more computations, making them less efficient. In portable digital audio players, this can mean a reduced playing time on batteries.

Due to the drawbacks of the alternative solutions above, some listeners dislike their negative effects more than the gap they attempt to remove.

Another alternative is to ignore track boundaries, encoding a single collection of tracks as a single compressed file, relying on [[cuesheet]]s (or something similar) for navigation. While this method results in gapless playback within the collection of tracks, it can be unwieldy due to the possibly large size of the resulting compressed file. Furthermore, unless the playback software or hardware can recognize the cue sheets, navigating between tracks may be difficult.

==Format support==
Since [[lossless]] data compression excludes the possibility of the introduction of padding, all lossless audio file formats are inherently gapless. The following [[lossy]] audio file formats have provisions for gapless encoding.

*[[Ogg Vorbis]]
*[[Speex]]

Some other formats do not officially support gapless encoding, but some implementations of encoders or decoders may handle gapless metadata.

*[[LAME]]-encoded MP3 can be gapless with players that support the LAME Mp3 info tag.
*[[AAC]] in [[MP4]] encoded with Nero Digital from [[Nero AG]] can be gapless with [[foobar2000]].
*AAC in MP4 encoded with iTunes 7.0 can be gapless with iTunes 7.0 and latest foobar2000.

==Gapless solutions==
* [[foobar2000]]: Optimal gapless playback
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=18530 Otachan's in_!mpg123]: A gapless [[MP3]] decoder for [[Winamp]]
:'''Note:''' Winamp 5.2 implements gapless playback in its built-in MP3 decoder.

==Test samples==
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=40998]: Samples for testing gapless playback abilities
* [http://guruboolez.free.fr/samples/gapless/gapless_WAVPACK_free_of_right.zip]: 17 very short gapless samples (2 MB)

[[Category:Technical]]

Cue sheet

2006-10-12T06:33:56Z

Kjoonlee: /* See also */ split, direct links

'''Cuesheets''' (or "cue sheets") are used to provide index information for a large audio file. They are generally used in conjunction with either extracting from, or burning to, [[CD]]. Cuesheets have the file extension ".cue", and are simple plain text files.

The cuesheet may contain [[metadata]] (e.g.: '''TITLE''' and '''PERFORMER''' statements), but must contain information regarding the file(s) referenced by the cuesheet ('''FILE''' command) and the '''TRACK''' and '''INDEX''' points within the file. INDEX points are specified using the '''MM:SS:FF''' format, where MM is the number of minutes, SS the number of seconds, and FF the number of frames (there are seventy five frames to one second).

The cuesheet has become popular thanks to [[EAC]] users who rip [[CD]]s to one image file, with an accompanying cuesheet. [[EAC]] can create four different cuesheet layouts, three for use with separate track files (a cuesheet may reference more than one file), but the single file cuesheet is most likely the more popular.

Cuesheets can be used when writing data to discs, as well as audio [[CD]]s. This document focuses solely on the audio-related commands.

==The Background==
The cuesheet format was invented by Jeff Arnold of [http://www.goldenhawk.com/ GoldenHawk Technology] for use with his [[DAO]] ('''D'''isc '''A'''t '''O'''nce) and [http://www.goldenhawk.com/ CDRWIN] applications. The format has since been adopted as the ''de facto'' standard, and is used by various other applications, including [[foobar2000]]. The official cuesheet specification is widely accepted to be Appendix A of the [http://www.goldenhawk.com/ CDRWIN] User's Guide.

The name is taken from the '''SEND CUE SHEET''' command, when a cuesheet describing the disc layout must be sent to the drive before writing starts in SAO write mode. The drive writes to the disc, using the cuesheet information to generate the P and Q subchannel data, and to retrieve the format and block size of the data transfered with the '''WRITE''' command.

Text adapted from [http://www.hydrogenaudio.org/forums/index.php?showtopic=42485 a post by Martin H].

==Cuesheet Commands==

The following commands are detailed in the Appendix A of the [http://www.goldenhawk.com/ CDRWIN] User's Guide:

*CATALOG
*CDTEXTFILE
*FILE
*FLAGS
*INDEX
*ISRC
*PERFORMER
*POSTGAP
*PREGAP
*REM
*SONGWRITER
*TITLE
*TRACK

The following are those most often used:

{| border="0" cellpadding="0" cellspacing="4"
! style=padding-right:24px| Command || Description
|-style=vertical-align:top
| FILE || The FILE command specifies the file that the cuesheet is currently referencing. Valid file types are WAVE, MP3 and AIFF, although other formats, e.g.: lossless formats like [[WavPack]] and [[FLAC]], can also be used under the WAVE file type.
|-style=vertical-align:top
| INDEX || A number between 00 and 99. Index points are specified in MM:SS:FF format, and are relative to the start of the file currently referenced. INDEX 01 commands specify the beginning of a new track. INDEX 00 commands specify the pre-gap of a track; you may notice your [[CD]] player count up from a negative value before beginning a new track - this is the period between INDEX 00 and INDEX 01.
|-style=vertical-align:top
| PERFORMER || At top-level this will specify the CD artist, while at track-level it specifies the track artist.
|-style=vertical-align:top
| PREGAP || Used to specify the length of a track pre-gap, in MM:SS:FF format.
|-style=vertical-align:top
| REM || Used to record comments in a cuesheet. This command is often used to store additional meta data to TITLE and PERFORMER, e.g.: the date or genre of the disc.
|-style=vertical-align:top
| TITLE || At top-level this will specify the album name, while at track-level it specifies the track name.
|-style=vertical-align:top
| TRACK|| A number between 0 and 99, indicating the track number.
|}

==Example Cuesheet==
<pre>
REM GENRE Ska
REM DATE 1991
REM DISCID D00DA810
REM COMMENT "ExactAudioCopy v0.95b4"
PERFORMER "The Specials"
TITLE "Singles"
FILE "The Specials - Singles.wav" WAVE
TRACK 01 AUDIO
TITLE "Gangsters"
PERFORMER "The Specials"
INDEX 01 00:00:00
TRACK 02 AUDIO
TITLE "Rudi, A Message To You"
PERFORMER "The Specials"
INDEX 00 02:47:74
INDEX 01 02:48:27
TRACK 03 AUDIO
TITLE "Nite Klub"
PERFORMER "The Specials"
INDEX 00 05:41:50
INDEX 01 05:42:27
TRACK 04 AUDIO
TITLE "Too Much Too Young"
PERFORMER "The Specials"
INDEX 00 08:53:47
INDEX 01 08:54:37
TRACK 05 AUDIO
TITLE "Guns Of Navarone"
PERFORMER "The Specials"
INDEX 00 10:59:20
INDEX 01 11:00:17
TRACK 06 AUDIO
TITLE "Rat Race"
PERFORMER "The Specials"
INDEX 00 13:20:55
INDEX 01 13:20:67
TRACK 07 AUDIO
TITLE "Stereotype"
PERFORMER "The Specials"
INDEX 00 16:29:67
INDEX 01 16:30:30
TRACK 08 AUDIO
TITLE "International Jet Set"
PERFORMER "The Specials"
INDEX 00 20:19:27
INDEX 01 20:20:20
TRACK 09 AUDIO
TITLE "Do Nothing"
PERFORMER "The Specials"
INDEX 00 24:30:70
INDEX 01 24:32:27
TRACK 10 AUDIO
TITLE "Ghost Town"
PERFORMER "The Specials"
INDEX 00 28:23:30
INDEX 01 28:23:42
TRACK 11 AUDIO
TITLE "Why?"
PERFORMER "The Specials"
INDEX 00 34:21:37
INDEX 01 34:21:47
TRACK 12 AUDIO
TITLE "Friday Night, Saturday Morning"
PERFORMER "The Specials"
INDEX 00 38:16:50
INDEX 01 38:16:55
TRACK 13 AUDIO
TITLE "War Crimes"
PERFORMER "The Specials"
INDEX 00 41:50:07
INDEX 01 41:51:00
TRACK 14 AUDIO
TITLE "Racist Friend"
PERFORMER "The Specials"
INDEX 00 45:50:55
INDEX 01 45:51:72
TRACK 15 AUDIO
TITLE "Nelson Mandela"
PERFORMER "The Specials"
INDEX 00 49:35:55
INDEX 01 49:38:22
TRACK 16 AUDIO
TITLE "(What I Like Most About You Is Your) Girlfriend"
PERFORMER "The Specials"
INDEX 00 54:11:00
INDEX 01 54:12:40
</pre>

==Useful Applications==
===Playing===
*[[foobar2000]]
===Splitting===
*[[ACDIR]]: http://nyaochi.sakura.ne.jp/xoops/modules/mysoftwares/tc_2.html
*CueProc: http://nyaochi.sakura.ne.jp/xoops/modules/mysoftwares/tc_6.html
*[[foobar2000]]: http://www.foobar2000.org/
*[[shntool]]: http://www.etree.org/shnutils/shntool/
*WavSplit: http://tangerine.uw.hu/prog/
===Joining===
*CueMake
*[[foobar2000]]: http://www.foobar2000.org/
===Creating===
*[[foobar2000]]: http://www.foobar2000.org/
*[[Goldwave]]: http://www.goldwave.com/
*Wave Repair: http://www.waverepair.com/
*CueMaster: http://cuemaster.host.sk/
*[[CueTools]]: http://www.hydrogenaudio.org/forums/index.php?showtopic=41476
===Other===

==See also==
*[[Gap settings]]
*[[EAC CUE Sheets]]

==External links==
*Wikipedia article: http://en.wikipedia.org/wiki/Cue_sheet
*The Goldenhawk website: http://www.goldenhawk.com/

Cue sheet

2006-10-12T05:11:11Z

Kjoonlee: bold title, heading levels

'''Cuesheets''' (or "cue sheets") are used to provide index information for a large audio file. They are generally used in conjunction with either extracting from, or burning to, [[CD]]. Cuesheets have the file extension ".cue", and are simple plain text files.

The cuesheet may contain [[metadata]] (e.g.: '''TITLE''' and '''PERFORMER''' statements), but must contain information regarding the file(s) referenced by the cuesheet ('''FILE''' command) and the '''TRACK''' and '''INDEX''' points within the file. INDEX points are specified using the '''MM:SS:FF''' format, where MM is the number of minutes, SS the number of seconds, and FF the number of frames (there are seventy five frames to one second).

The cuesheet has become popular thanks to [[EAC]] users who rip [[CD]]s to one image file, with an accompanying cuesheet. [[EAC]] can create four different cuesheet layouts, three for use with separate track files (a cuesheet may reference more than one file), but the single file cuesheet is most likely the more popular.

Cuesheets can be used when writing data to discs, as well as audio [[CD]]s. This document focuses solely on the audio-related commands.

==The Background==
The cuesheet format was invented by Jeff Arnold of [http://www.goldenhawk.com/ GoldenHawk Technology] for use with his [[DAO]] ('''D'''isc '''A'''t '''O'''nce) and [http://www.goldenhawk.com/ CDRWIN] applications. The format has since been adopted as the ''de facto'' standard, and is used by various other applications, including [[foobar2000]]. The official cuesheet specification is widely accepted to be Appendix A of the [http://www.goldenhawk.com/ CDRWIN] User's Guide.

The name is taken from the '''SEND CUE SHEET''' command, when a cuesheet describing the disc layout must be sent to the drive before writing starts in SAO write mode. The drive writes to the disc, using the cuesheet information to generate the P and Q subchannel data, and to retrieve the format and block size of the data transfered with the '''WRITE''' command.

Text adapted from [http://www.hydrogenaudio.org/forums/index.php?showtopic=42485 a post by Martin H].

==Cuesheet Commands==

The following commands are detailed in the Appendix A of the [http://www.goldenhawk.com/ CDRWIN] User's Guide:

*CATALOG
*CDTEXTFILE
*FILE
*FLAGS
*INDEX
*ISRC
*PERFORMER
*POSTGAP
*PREGAP
*REM
*SONGWRITER
*TITLE
*TRACK

The following are those most often used:

{| border="0" cellpadding="0" cellspacing="4"
! style=padding-right:24px| Command || Description
|-style=vertical-align:top
| FILE || The FILE command specifies the file that the cuesheet is currently referencing. Valid file types are WAVE, MP3 and AIFF, although other formats, e.g.: lossless formats like [[WavPack]] and [[FLAC]], can also be used under the WAVE file type.
|-style=vertical-align:top
| INDEX || A number between 00 and 99. Index points are specified in MM:SS:FF format, and are relative to the start of the file currently referenced. INDEX 01 commands specify the beginning of a new track. INDEX 00 commands specify the pre-gap of a track; you may notice your [[CD]] player count up from a negative value before beginning a new track - this is the period between INDEX 00 and INDEX 01.
|-style=vertical-align:top
| PERFORMER || At top-level this will specify the CD artist, while at track-level it specifies the track artist.
|-style=vertical-align:top
| PREGAP || Used to specify the length of a track pre-gap, in MM:SS:FF format.
|-style=vertical-align:top
| REM || Used to record comments in a cuesheet. This command is often used to store additional meta data to TITLE and PERFORMER, e.g.: the date or genre of the disc.
|-style=vertical-align:top
| TITLE || At top-level this will specify the album name, while at track-level it specifies the track name.
|-style=vertical-align:top
| TRACK|| A number between 0 and 99, indicating the track number.
|}

==Example Cuesheet==
<pre>
REM GENRE Ska
REM DATE 1991
REM DISCID D00DA810
REM COMMENT "ExactAudioCopy v0.95b4"
PERFORMER "The Specials"
TITLE "Singles"
FILE "The Specials - Singles.wav" WAVE
TRACK 01 AUDIO
TITLE "Gangsters"
PERFORMER "The Specials"
INDEX 01 00:00:00
TRACK 02 AUDIO
TITLE "Rudi, A Message To You"
PERFORMER "The Specials"
INDEX 00 02:47:74
INDEX 01 02:48:27
TRACK 03 AUDIO
TITLE "Nite Klub"
PERFORMER "The Specials"
INDEX 00 05:41:50
INDEX 01 05:42:27
TRACK 04 AUDIO
TITLE "Too Much Too Young"
PERFORMER "The Specials"
INDEX 00 08:53:47
INDEX 01 08:54:37
TRACK 05 AUDIO
TITLE "Guns Of Navarone"
PERFORMER "The Specials"
INDEX 00 10:59:20
INDEX 01 11:00:17
TRACK 06 AUDIO
TITLE "Rat Race"
PERFORMER "The Specials"
INDEX 00 13:20:55
INDEX 01 13:20:67
TRACK 07 AUDIO
TITLE "Stereotype"
PERFORMER "The Specials"
INDEX 00 16:29:67
INDEX 01 16:30:30
TRACK 08 AUDIO
TITLE "International Jet Set"
PERFORMER "The Specials"
INDEX 00 20:19:27
INDEX 01 20:20:20
TRACK 09 AUDIO
TITLE "Do Nothing"
PERFORMER "The Specials"
INDEX 00 24:30:70
INDEX 01 24:32:27
TRACK 10 AUDIO
TITLE "Ghost Town"
PERFORMER "The Specials"
INDEX 00 28:23:30
INDEX 01 28:23:42
TRACK 11 AUDIO
TITLE "Why?"
PERFORMER "The Specials"
INDEX 00 34:21:37
INDEX 01 34:21:47
TRACK 12 AUDIO
TITLE "Friday Night, Saturday Morning"
PERFORMER "The Specials"
INDEX 00 38:16:50
INDEX 01 38:16:55
TRACK 13 AUDIO
TITLE "War Crimes"
PERFORMER "The Specials"
INDEX 00 41:50:07
INDEX 01 41:51:00
TRACK 14 AUDIO
TITLE "Racist Friend"
PERFORMER "The Specials"
INDEX 00 45:50:55
INDEX 01 45:51:72
TRACK 15 AUDIO
TITLE "Nelson Mandela"
PERFORMER "The Specials"
INDEX 00 49:35:55
INDEX 01 49:38:22
TRACK 16 AUDIO
TITLE "(What I Like Most About You Is Your) Girlfriend"
PERFORMER "The Specials"
INDEX 00 54:11:00
INDEX 01 54:12:40
</pre>

==Useful Applications==
===Playing===
*[[foobar2000]]
===Splitting===
*[[ACDIR]]: http://nyaochi.sakura.ne.jp/xoops/modules/mysoftwares/tc_2.html
*CueProc: http://nyaochi.sakura.ne.jp/xoops/modules/mysoftwares/tc_6.html
*[[foobar2000]]: http://www.foobar2000.org/
*[[shntool]]: http://www.etree.org/shnutils/shntool/
*WavSplit: http://tangerine.uw.hu/prog/
===Joining===
*CueMake
*[[foobar2000]]: http://www.foobar2000.org/
===Creating===
*[[foobar2000]]: http://www.foobar2000.org/
*[[Goldwave]]: http://www.goldwave.com/
*Wave Repair: http://www.waverepair.com/
*CueMaster: http://cuemaster.host.sk/
*[[CueTools]]: http://www.hydrogenaudio.org/forums/index.php?showtopic=41476
===Other===

==Links==

*Internal
**[[Gap settings|Gap Settings]]
**[[EAC CUE Sheets|EAC Cuesheets]]
*External
**Wikipedia article: http://en.wikipedia.org/wiki/Cue_sheet
**The Goldenhawk website: http://www.goldenhawk.com/

Cue sheet

2006-10-12T05:09:22Z

Kjoonlee: /* Links */ heading level, listify

Cuesheets (or "cue sheets") are used to provide index information for a large audio file. They are generally used in conjunction with either extracting from, or burning to, [[CD]]. Cuesheets have the file extension ".cue", and are simple plain text files.

The cuesheet may contain [[metadata]] (e.g.: '''TITLE''' and '''PERFORMER''' statements), but must contain information regarding the file(s) referenced by the cuesheet ('''FILE''' command) and the '''TRACK''' and '''INDEX''' points within the file. INDEX points are specified using the '''MM:SS:FF''' format, where MM is the number of minutes, SS the number of seconds, and FF the number of frames (there are seventy five frames to one second).

The cuesheet has become popular thanks to [[EAC]] users who rip [[CD]]s to one image file, with an accompanying cuesheet. [[EAC]] can create four different cuesheet layouts, three for use with separate track files (a cuesheet may reference more than one file), but the single file cuesheet is most likely the more popular.

Cuesheets can be used when writing data to discs, as well as audio [[CD]]s. This document focuses solely on the audio-related commands.

=The Background=
The cuesheet format was invented by Jeff Arnold of [http://www.goldenhawk.com/ GoldenHawk Technology] for use with his [[DAO]] ('''D'''isc '''A'''t '''O'''nce) and [http://www.goldenhawk.com/ CDRWIN] applications. The format has since been adopted as the ''de facto'' standard, and is used by various other applications, including [[foobar2000]]. The official cuesheet specification is widely accepted to be Appendix A of the [http://www.goldenhawk.com/ CDRWIN] User's Guide.

The name is taken from the '''SEND CUE SHEET''' command, when a cuesheet describing the disc layout must be sent to the drive before writing starts in SAO write mode. The drive writes to the disc, using the cuesheet information to generate the P and Q subchannel data, and to retrieve the format and block size of the data transfered with the '''WRITE''' command.

Text adapted from [http://www.hydrogenaudio.org/forums/index.php?showtopic=42485 a post by Martin H].

=Cuesheet Commands=

The following commands are detailed in the Appendix A of the [http://www.goldenhawk.com/ CDRWIN] User's Guide:

*CATALOG
*CDTEXTFILE
*FILE
*FLAGS
*INDEX
*ISRC
*PERFORMER
*POSTGAP
*PREGAP
*REM
*SONGWRITER
*TITLE
*TRACK

The following are those most often used:

{| border="0" cellpadding="0" cellspacing="4"
! style=padding-right:24px| Command || Description
|-style=vertical-align:top
| FILE || The FILE command specifies the file that the cuesheet is currently referencing. Valid file types are WAVE, MP3 and AIFF, although other formats, e.g.: lossless formats like [[WavPack]] and [[FLAC]], can also be used under the WAVE file type.
|-style=vertical-align:top
| INDEX || A number between 00 and 99. Index points are specified in MM:SS:FF format, and are relative to the start of the file currently referenced. INDEX 01 commands specify the beginning of a new track. INDEX 00 commands specify the pre-gap of a track; you may notice your [[CD]] player count up from a negative value before beginning a new track - this is the period between INDEX 00 and INDEX 01.
|-style=vertical-align:top
| PERFORMER || At top-level this will specify the CD artist, while at track-level it specifies the track artist.
|-style=vertical-align:top
| PREGAP || Used to specify the length of a track pre-gap, in MM:SS:FF format.
|-style=vertical-align:top
| REM || Used to record comments in a cuesheet. This command is often used to store additional meta data to TITLE and PERFORMER, e.g.: the date or genre of the disc.
|-style=vertical-align:top
| TITLE || At top-level this will specify the album name, while at track-level it specifies the track name.
|-style=vertical-align:top
| TRACK|| A number between 0 and 99, indicating the track number.
|}

=Example Cuesheet=
<pre>
REM GENRE Ska
REM DATE 1991
REM DISCID D00DA810
REM COMMENT "ExactAudioCopy v0.95b4"
PERFORMER "The Specials"
TITLE "Singles"
FILE "The Specials - Singles.wav" WAVE
TRACK 01 AUDIO
TITLE "Gangsters"
PERFORMER "The Specials"
INDEX 01 00:00:00
TRACK 02 AUDIO
TITLE "Rudi, A Message To You"
PERFORMER "The Specials"
INDEX 00 02:47:74
INDEX 01 02:48:27
TRACK 03 AUDIO
TITLE "Nite Klub"
PERFORMER "The Specials"
INDEX 00 05:41:50
INDEX 01 05:42:27
TRACK 04 AUDIO
TITLE "Too Much Too Young"
PERFORMER "The Specials"
INDEX 00 08:53:47
INDEX 01 08:54:37
TRACK 05 AUDIO
TITLE "Guns Of Navarone"
PERFORMER "The Specials"
INDEX 00 10:59:20
INDEX 01 11:00:17
TRACK 06 AUDIO
TITLE "Rat Race"
PERFORMER "The Specials"
INDEX 00 13:20:55
INDEX 01 13:20:67
TRACK 07 AUDIO
TITLE "Stereotype"
PERFORMER "The Specials"
INDEX 00 16:29:67
INDEX 01 16:30:30
TRACK 08 AUDIO
TITLE "International Jet Set"
PERFORMER "The Specials"
INDEX 00 20:19:27
INDEX 01 20:20:20
TRACK 09 AUDIO
TITLE "Do Nothing"
PERFORMER "The Specials"
INDEX 00 24:30:70
INDEX 01 24:32:27
TRACK 10 AUDIO
TITLE "Ghost Town"
PERFORMER "The Specials"
INDEX 00 28:23:30
INDEX 01 28:23:42
TRACK 11 AUDIO
TITLE "Why?"
PERFORMER "The Specials"
INDEX 00 34:21:37
INDEX 01 34:21:47
TRACK 12 AUDIO
TITLE "Friday Night, Saturday Morning"
PERFORMER "The Specials"
INDEX 00 38:16:50
INDEX 01 38:16:55
TRACK 13 AUDIO
TITLE "War Crimes"
PERFORMER "The Specials"
INDEX 00 41:50:07
INDEX 01 41:51:00
TRACK 14 AUDIO
TITLE "Racist Friend"
PERFORMER "The Specials"
INDEX 00 45:50:55
INDEX 01 45:51:72
TRACK 15 AUDIO
TITLE "Nelson Mandela"
PERFORMER "The Specials"
INDEX 00 49:35:55
INDEX 01 49:38:22
TRACK 16 AUDIO
TITLE "(What I Like Most About You Is Your) Girlfriend"
PERFORMER "The Specials"
INDEX 00 54:11:00
INDEX 01 54:12:40
</pre>

=Useful Applications=
==Playing==
*[[foobar2000]]
==Splitting==
*[[ACDIR]]: http://nyaochi.sakura.ne.jp/xoops/modules/mysoftwares/tc_2.html
*CueProc: http://nyaochi.sakura.ne.jp/xoops/modules/mysoftwares/tc_6.html
*[[foobar2000]]: http://www.foobar2000.org/
*[[shntool]]: http://www.etree.org/shnutils/shntool/
*WavSplit: http://tangerine.uw.hu/prog/
==Joining==
*CueMake
*[[foobar2000]]: http://www.foobar2000.org/
==Creating==
*[[foobar2000]]: http://www.foobar2000.org/
*[[Goldwave]]: http://www.goldwave.com/
*Wave Repair: http://www.waverepair.com/
*CueMaster: http://cuemaster.host.sk/
*[[CueTools]]: http://www.hydrogenaudio.org/forums/index.php?showtopic=41476
==Other==

==Links==

*Internal
**[[Gap settings|Gap Settings]]
**[[EAC CUE Sheets|EAC Cuesheets]]
*External
**Wikipedia article: http://en.wikipedia.org/wiki/Cue_sheet
**The Goldenhawk website: http://www.goldenhawk.com/

Foobar2000:Title Formatting Reference

2006-10-12T04:42:48Z

Kjoonlee: arrows, one typo

{{fb2k}}
This article contains information about built-in titleformatting functions and field references with special meaning. References to documentation about fields and function which can only be used in specific components or which are provided by specific components can be found at the end of this article.

A field reference is a field name enclosed in percent signs, for example ''%artist%''. A function call starts with a dollar sign, followed by the function name and the parameter list. A parameter list can either be empty - denoted as ''()'' - or contain one or more parameters separated by commata, for example ''$abbr(%artist%)''. Note that there must be no whitespace between the dollar sign and the function name, or the function name and the opening parenthesis of the parameter list.

Please see [[Foobar2000:Titleformat_Introduction|Titleformat Introduction]] for a presentation of titleformat syntax in general.

= Field remappings =

Some of the fields accessible through ''%name%'' are remapped to other values to make writing titleformat scripts more convenient.

== Metadata ==

=== %album artist% ===
Defined as ''$if3($meta(album artist),$meta(artist),$meta(composer),$meta(performer))''.

=== %album% ===
Defined as ''$if3($meta(album),$meta(venue))''.

=== %artist% ===
Defined as ''$if3($meta(artist),$meta(album artist),$meta(composer),$meta(performer))''.

=== %disc% ===
Returns the discnumber. The discnumber is taken from the discnumber tag; if that does not exist, it is taken from the disc tag. If neither exist, the field is undefined.

This is equivalent to the %discnumber% remapping.

=== %discnumber% ===
Returns the discnumber. The discnumber is taken from the discnumber tag; if that does not exist, it is taken from the disc tag. If neither exist, the field is undefined.

This is equivalent to the %disc% remapping.

=== %track artist% ===
Defined as ''$meta(artist)'', if ''$meta(album artist)'' is different than ''$meta(artist)'', otherwise this field is empty.

=== %title% ===
Defined as ''$if2($meta(title),%_filename%)''. Returns the ''title'' tag if available, otherwise it returns the filename excluding the extension.

=== %track% ===
Returns the tracknumber padded to two digits from the left with zeroes. The tracknumber is taken from the tracknumber tag; if that does not exist, it is taken from the track tag. If neither exist, this field is undefined.

This is equivalent to the %tracknumber% remapping.

=== %tracknumber% ===
Returns the tracknumber padded to two digits from the left with zeroes. The tracknumber is taken from the tracknumber tag; if that does not exist, it is taken from the track tag. If neither exist, this field is undefined.

This is equivalent to the %track% remapping.

== Technical information ==

=== %bitrate% ===
Defined as ''$if2($info(bitrate_dynamic),$info(bitrate))''. Returns the current bitrate, if available, otherwise it returns the average bitrate. If neither is available, nothing is returned.

=== %channels% ===
Defined as ''$channels()''. Returns the number of channels in text form; returns "mono" and "stereo" instead of "1" and "2".

=== %filesize% ===
Defined as ''%_filesize%''. Returns the filesize in bytes.

=== %samplerate% ===
Defined as ''$info(samplerate)''. Returns the samplerate in Hz.

=== %codec% ===
Defined as ''$codec()''.

== Special fields ==

=== %playlist_number% ===
Defined as ''$num(%_playlist_number%,$len(%_playlist_total%))''. Returns the position of the track as index into the playlist. The first track has index 1. The index is padded from the left with zeroes to the same number of digits as the last track.

= Control flow =

The functions in this section can be used to conditionally execute statements.

=== [...] (conditional section) ===

Evaluates the expression between ''['' and '']''. If it has the truth value ''true'', its string value and the truth value ''true'' are returned. Otherwise an empty string and ''false'' are returned.

Example: ''[%artist%]'' returns the value of the artist tag, if it exists. Otherwise it returns nothing, when ''artist'' would return "?".

=== $if(cond,then) ===

If ''cond'' evaluates to ''true'', the ''then'' part is evaluated and its value returned. Otherwise, ''false'' is returned.

=== $if(cond,then,else) ===

If ''cond'' evaluates to ''true'', the ''then'' part is evaluated and its value returned. Otherwise, the ''else'' part is evaluated and its value returned.

=== $if2(a,else) ===

Like ''$if(a,a,else)'' except that ''a'' is only evaluated once.

=== $if3(a1,a2,...,aN,else) ===

Evaluates arguments ''a1'' ... ''aN'', until one is found that evaluates to ''true''. If that happens, its value is returned. Otherwise the ''else'' part is evaluated and its value returned.

=== $ifequal(n1,n2,then,else) ===

Compares the integer numbers ''n1'' and ''n2'', if ''n1'' is equal to ''n2'', the ''then'' part is evaluated and its value returned. Otherwise the ''else'' part is evaluated and its value returned.

=== $ifgreater(n1,n2,then,else) ===

Compares the integer numbers ''n1'' and ''n2'', if ''n1'' is greater than ''n2'', the ''then'' part is evaluated and its value returned. Otherwise the ''else'' part is evaluated and its value returned.

=== $iflonger(s1,s2,then,else) ===

Compares the length of the strings ''s1'' and ''s2'', if ''s1'' is longer than ''s2'', the ''then'' part is evaluated and its value returned. Otherwise the ''else'' part is evaluated and its value returned.

=== $select(n,a1,...,aN) ===

If the value of ''n'' is between 1 and N, ''an'' is evaluated and its value returned. Otherwise ''false'' is returned.

= Arithmetic functions =

The functions in this section can be used to perform arithmetic on integer numbers. A string will be automatically converted to a number and vice versa. The conversion to a number uses the longest prefix of the string, that can be interpreted as number. Leading whitespace is ignored.

Example: "c3po" → 0, " -12" → -12, but "- 12" → 0

=== $add(a,b) ===

Adds ''a'' and ''b''.

Can be used with an arbitrary number of arguments. ''$add(a,b,...)'' is the same as ''$add($add(a,b),...)''.

=== $div(a,b) ===

Divides ''a'' through ''b''. If ''b'' evaluates to zero, it returns ''a''.

Can be used with an arbitrary number of arguments. ''$div(a,b,...)'' is the same as ''$div($div(a,b),...)''.

=== $greater(a,b) ===

Returns true, if ''a'' is greater than ''b'', otherwise false.

=== $max(a,b) ===

Returns the maximum of ''a'' and ''b''.

Can be used with an arbitrary number of arguments. ''$max(a,b,...)'' is the same as ''$max($max(a,b),...)''.

=== $min(a,b) ===

Returns the minimum of ''a'' and ''b''.

Can be used with an arbitrary number of arguments. ''$min(a,b,...)'' is the same as ''$min($min(a,b),...)''.

=== $mod(a,b) ===

Computes the remainder of dividing ''a'' through ''b''. The result has the same sign as ''a''. If ''b'' evaluates to zero, the result is ''a''.

Can be used with an arbitrary number of arguments. ''$mod(a,b,...)'' is the same as ''$mod($mod(a,b),...)''.

=== $mul(a,b) ===

Multiplies ''a'' and ''b''.

Can be used with an arbitrary number of arguments. ''$mul(a,b,...)'' is the same as ''$mul($mul(a,b),...)''.

=== $muldiv(a,b,c) ===

Multiplies ''a'' and ''b'', then divides by ''c''. The result is rounded to the nearest integer.

=== $rand() ===

Generates a random number in the range from 0 to 2<sup>32</sup>-1.

=== $sub(a,b) ===

Subtracts ''b'' from ''a''.

Can be used with an arbitrary number of arguments. ''$sub(a,b,...)'' is the same as ''$sub($sub(a,b),...)''.

= Boolean functions =

The functions in this section can be used to work with truth values (''true'' and ''false''), which have no explicit representation in titleformat scripts. They do not return a string or number value. You can use them for more complex conditions with ''$if'' and related functions.

=== $and(...) ===

Logical And of an arbitrary number of arguments. Returns ''true'', if and only if all arguments evaluate to ''true''.

Special case: ''$and(x,y)'' is ''true'', if both ''x'' and ''y'' are ''true''. Otherwise it is ''false''.

=== $or(...) ===

Logical Or of an arbitrary number of arguments. Returns ''true'', if at least one argument evaluates to ''true''.

Special case: ''$or(x,y)'' is ''true'', if ''x'' or ''y'' is ''true'', or if both are ''true''. Otherwise it is ''false''.

=== $not(x) ===

Logical Not. Returns ''false'', if ''x'' is ''true'', otherwise it returns ''true''.

=== $xor(...) ===

Logical Exclusive-or of an arbitrary number of arguments. Returns ''true'', if an odd number of arguments evaluate to ''true''.

Special case: ''$xor(x,y)'' is ''true'', if one of ''x'' and ''y'' is ''true'', but not both. Otherwise it is ''false''.

= Color functions =

=== $blend(color1,color2,part,total) ===

Returns a color that is a blend between ''color1'' and ''color2''. If ''part'' is smaller than or equal to zero, ''color1'' is returned. If ''part'' is greater than or equal to ''total'', ''color2'' is returned. Otherwise a blended color is returned that is ''part'' parts ''color1'' and ''total''-''part'' parts ''color2''. The blending is performed in the RGB color space.

=== $hsl() ===

Resets the text color to the default color.

=== $hsl(h,s,l) ===

Sets the color for text in the HSL color space. ''h'', ''s'' and ''l'' are the hue, saturation, and lightness of the color for unselected text. The color for selected text is set to the inverse color.
The ranges of ''h'', ''s'', and ''l'' are from 0 to 240; the function is designed to interpret those values in the same way as the standard Windows color dialog.

=== $hsl(h1,s1,l1,h2,s2,l2) ===

Sets the color for text in the HSL color space. ''h1'', ''s1'' and ''l1'' are the hue, saturation, and lightness of the color for unselected text. ''h2'', ''s2'' and ''l2'' are the hue, saturation, and lightness of the color for selected text.

=== $rgb() ===

Resets the text color to the default color.

=== $rgb(r,g,b) ===

Sets the color for text. ''r'', ''g'' and ''b'' are the red, green and blue component of the color for unselected text. The color for selected text is set to the inverse color.

=== $rgb(r1,g1,b1,r2,g2,b2) ===

Sets the color for text. ''r1'', ''g1'' and ''b1'' are the red, green and blue component of the color for unselected text. ''r2'', ''g2'' and ''b2'' are the red, green and blue component of the color for selected text.

=== $transition(string,color1,color2) ===

Inserts color codes into ''string'', so that the first character has ''color1'', the last character has ''color2'', and intermediate characters have blended colors. The blending is performed in the RGB color space. Note that color codes are additional characters that will also be counted by string manipulation functions. For example, if you need to truncate a string, you should do this before applying ''$transition''.

= Now playing info =
The following functions and fields are usable for scripts used with the currently playing item, for example the status bar, the main window title and the copy command script.

== Special fields ==

=== %playback_time% ===
Returns the elapsed time formatted as [HH:]MM:SS.

=== %playback_time_seconds% ===
Returns elapsed time in seconds.
Old version: <code>%_time_elapsed%</code>

=== %playback_time_remaining% ===
Returns remaining time until track ends, formatted as [HH:]MM:SS.
Old version: <code>%_time_remaining%</code>

=== %playback_time_remaining_seconds% ===
Returns remaining time in seconds.
Old version: <code>%_time_remaining_seconds%</code>

=== %length% ===
Returns the length of the track formatted as hours, minutes, and seconds.
Old version: <code>%_time_total%</code>

=== %length_ex% ===
Returns the length of the track formatted as hours, minutes, seconds, and milliseconds.

=== %length_seconds% ===
Returns the length of the track in seconds.
Old version: <code>%_time_total_seconds%</code>

=== %length_seconds_fp% ===
Returns the length of the track in seconds as floating point number.

=== %length_samples% ===
Returns the length of the track in samples.

= Playlist info =
The following functions and fields are usable for playlist scripts such as masstagger.

== Special fields ==

=== %isplaying% ===

Returns "1" if file is currently playing and empty string otherwise.

The old version <code>%_isplaying%</code> still works.

=== %ispaused% ===

Returns "1" if playback is paused, empty string otherwise.

The old version <code>%_ispaused%</code> still works.

=== %list_index% ===

Returns a zero-padded playlist index of specified item. The first item is at index 1.

Also see [[Foobar2000:Titleformat Reference#%playlist_number%|%playlist_number%]].

The old version <code>%_playlist_number%</code> still works.

=== %list_total% ===

Returns number of items in the playlist.

The old version <code>%_playlist_total%</code> still works.

=== %playlist_name% ===

Returns the name of the playlist containing the specified item.

The old version <code>%_playlist_name%</code> still works.

= String functions =

The functions in this section can be used to manipulate character strings.

=== $abbr(x) ===

Returns abbreviation of ''x''.

=== $abbr(x,len) ===

Returns abbreviation of ''x'', if ''x'' is longer than ''len'' characters, otherwise returns ''x''.

=== $ansi(x) ===

Converts ''x'' to system codepage and back. Any characters that are not present in the system codepage will be removed / replaced. Useful for mass-renaming files to ensure compatibility with non-unicode-capable software.

=== $ascii(x) ===

Converts ''x'' to ASCII. Any characters that are not present in ASCII will be removed / replaced.

=== $caps(x) ===

Converts first letter in every word of x to uppercase, and all other letters to lowercase.

=== $caps2(x) ===

Converts first letter in every word of x to uppercase, and leaves all other letters as they are.

=== $char(x) ===

Inserts Unicode character with code ''x''.

=== $crc32(a) ===

Computes the CRC32 of the string ''a'' as a number. Intended for use in coloring scripts.

Example: $rgb($mod($crc32(%album%),256),128,128)

=== $crlf() ===

Inserts end-of-line marker (carriage return, line feed). Can be used to generate multiple lines in the output, for example for the tooltip of the system notification area ("systray") icon.

=== $cut(a,len) ===

Returns first ''len'' characters on the left of ''a''.

=== $directory(x) ===

Extracts directory name from the file path ''x''.

=== $directory(x,n) ===

Extracts directory name from the file path ''x''; goes up by ''n'' levels.

=== $ext(x) ===

Extracts file extension from ''x'' which must be a file name or path.

=== $filename(x) ===

Extracts file name from full path.

=== $fix_eol(x) ===

If ''x'' contains an end-of-line marker (CR-LF), the end-of-line marker and all text to the right of it is replaced by " (...)". Otherwise ''x'' is returned unaltered.

=== $fix_eol(x,indicator) ===

If ''x'' contains an end-of-line marker (CR-LF), the end-of-line marker and all text to the right of it is replaced by ''indicator''. Otherwise ''x'' is returned unaltered.

=== $hex(n) ===

Formats the integer number ''n'' in hexadecimal notation.

=== $hex(n,len) ===

Formats the integer number ''n'' in hexadecimal notation with ''len'' digits. Pads with zeros from the left if necessary.

=== $insert(a,b,n) ===

Inserts ''b'' into ''a'' after ''n'' characters.

=== $left(a,len) ===

Returns the first ''len'' characters from the left of ''a''.

=== $len(a) ===

Returns length of string ''a'' in characters.

=== $len2(a) ===

Returns length of string x in characters, respecting double-width character rules (double-width characters will be counted as two).

=== $longer(a,b) ===

Returns ''true'', if string ''a'' is longer than string ''b'', false otherwise.

=== $lower(a) ===

Converts ''a'' to lowercase.

=== $longest(a,...) ===

Returns the longest of its arguments. Can be used with an arbitrary number of strings.

=== $num(n,len) ===

Formats the integer number ''n'' in decimal notation with ''len'' digits. Pads with zeros from the left if necessary.

=== $pad(x,len) ===

Pads ''x'' from the left with spaces to ''len'' characters.

=== $pad_right(x,y) ===

Pads ''x'' from the right with spaces to ''len'' characters.

=== $pad(x,len,char) ===

Pads ''x'' from the left with ''char'' to ''len'' characters.

=== $pad_right(x,len,char) ===

Pads ''x'' from the right with ''char'' to ''len'' characters.

=== $padcut(x,len) ===

Returns first ''len'' characters from the left of ''x'', if ''x'' is longer than ''len'' characters. Otherwise pads ''x'' from the left with spaces to ''len'' characters.

=== $padcut_right(x,len) ===

Returns first ''len'' characters from the left of ''x'', if ''x'' is longer than ''len'' characters. Otherwise pads ''x'' from the right with spaces to ''len'' characters.

=== $progress(pos,range,len,a,b) ===

Creates a progress bar: ''pos'' contains position, ''range'' contains range, ''len'' progress bar length in characters, ''a'' and ''b'' are characters to build progress bar with.

Example:''$progress(%_time_elapsed_seconds%, %_time_total_seconds%, 20,'#','=')'' produces "====#===============", the # character is moving with playback position.

=== $progress2(pos,range,len,a,b) ===

Creates a progress bar: ''pos'' contains position, ''range'' contains range, ''len'' progress bar length in characters, ''a'' and ''b'' are characters to build progress bar with. Produces different appearance than ''$progress''.

=== $repeat(a,n) ===

Returns ''n'' copies of ''a''. Note that ''a'' is evaluated once before its value is used, so ''$repeat'' cannot be used for loops.

=== $replace(a,b,c) ===

Replaces all occurrences of string ''b'' in string ''a'' with string ''c''.

Can also be used with an arbitrary number of arguments. Note that ''$replace(a,b1,c1,b2,c2)'' is generally not the same as ''$replace($replace(a,b1,c1),b2,c2)''.

Example: ''$replace(ab,a,b,b,c)'' → "bc", ''$replace($replace(ab,a,b),b,c)'' → "cc"

=== $right(a,len) ===

Returns the first ''len'' characters from the right of ''a''.

=== $roman(n) ===

Formats the integer number ''n'' in roman notation.

=== $rot13() ===

Performs [http://en.wikipedia.org/wiki/ROT13 ROT13] transformation to given string.

Example: ''$rot13('foobar2000')'' → "sbbone2000".

=== $shortest ===

Returns the shortest of its arguments. Can be used with an arbitrary number of strings.

=== $strchr(s,c) ===

Finds first occurence of character ''c'' in string ''s''.

Example: ''$strchr(abca,a)'' → 1

=== $strrchr(s,c) ===

Finds last occurence of character ''c'' in string ''s''.

Example: ''$strrchr(abca,a)'' → 4

=== $strstr(s1,s2) ===

Finds first occurence of string ''s2'' in string ''s1''.

=== $strcmp(s1,s2) ===

Performs a case-sensitive comparison of the strings ''s1'' and ''s2''.

=== $stricmp(s1,s2) ===

Performs a case-insensitive comparison of the strings ''s1'' and ''s2''.

=== $substr(s,m,n) ===

Returns substring of string ''s'', starting from ''m''-th character and ending at ''n''-th character.

=== $trim(s) ===

Removes leading and trailing spaces from string ''s''.

=== $tab() ===

Inserts one tabulator character.

=== $tab(n) ===

Inserts ''n'' tabulator characters.

=== $upper(s) ===

Converts string ''s'' to uppercase.

= Track info =

The functions and fields in this section can be used to access information about tracks.

== Metadata ==

=== $meta(name) ===
Returns value of tag called ''name''. If multiple values of that tag exist, they are concatenated with ", " as separator.

Example: ''$meta(artist)'' → "He, She, It"

=== $meta(name,n) ===
Returns value of ''n''-th (0,1,2 and so on) tag called ''name''.

Example: ''$meta(artist,1)'' → "She"

=== $meta_sep(name,sep) ===
Returns value of tag called ''name''. If multiple values of that tag exist, they are concatenated with ''sep'' as separator.

Example: ''$meta_sep(artist,' + ')'' → "He + She + It"

=== $meta_sep(name,sep,lastsep) ===
Returns value of tag called ''name''. If multiple values of that tag exist, they are concatenated with ''sep'' as separator between all but the last two values which are concatenated with ''lastsep''.

Example: ''$meta_sep(artist,', ',', and ')'' → "He, She, and It"

=== $meta_test(...) ===
Returns ''1'', if all given tags exist, ''undefined'' otherwise.

Example: ''$meta_test(artist,title)'' → true

=== $meta_num(name) ===
Returns the number of values for the tag called ''name''.

Example: ''$meta_num(artist)'' → 3

=== $tracknumber() ===
Returns the tracknumber padded to 2 digits with zeroes.

=== $tracknumber(n) ===
Returns the tracknumber padded to ''n'' digits with zeros.

== Technical information ==

=== $info(name) ===
Returns value of technical information field called ''name''.

For convenience, the '''%__name%''' alias is also available.

Example: ''$info(channels)'' → 2

Here is an '''informative''' list of recognized fields. Some of these depend on the media file type being queried.

(→See also: [[Foobar2000_Talk:Titleformat_Reference#Other_information|Talk page]])

{| border="0" cellspacing="0" cellpadding="2"
! field name
! Description
|-
| colspan="2" style="background-color:#CCF"|'''General'''
|-
|codec
| style="background-color:#EEF"|'''Codec''' (''e.g.'' MP3)
|-
|codec_profile
| style="background-color:#EEF"|'''Codec Profile''' (''e.g.'' CBR)
|-
|samplerate
| style="background-color:#EEF"|'''Sample Rate''', in hertz (''e.g.'' 44100)
|-
|bitrate
| style="background-color:#EEF"|'''Bitrate''', in kilobits per second (''e.g.'' 320)
|-
|tool
| style="background-color:#EEF"|'''Tool''' used to produce the file, possibly guessed (''e.g.'' LAME3.97)
|-
|encoding
| style="background-color:#EEF"|'''Encoding''' lossiness (''e.g.'' lossy)
|-
|channels
| style="background-color:#EEF"|'''Channels''' count (''e.g.'' 2 <nowiki>[for stereo]</nowiki>)
|-
|bitspersample
| style="background-color:#EEF"|'''Bits Per Sample''' (''e.g.'' 16)
|-
|tagtype
| style="background-color:#EEF"|'''Tag Type''', comma-separated list of tag formats (''e.g.'' id3v2|apev2)
|-
|cue_embedded
| style="background-color:#EEF"|'''Embedded Cuesheet''' presence (''e.g.'' no <nowiki>[may be empty!]</nowiki>)
|-
|md5
| style="background-color:#EEF"|'''Audio MD5''' hash, if container defines it (''e.g.'' 1E24A910D91EF09A8CF403C9B6963961)
|-
| colspan="2" style="background-color:#CCF"|'''Other'''
|-
|ENC_DELAY
| style="background-color:#EEF"|LAME proprietary MP3 '''enc_delay''' value (''e.g.'' 576)
|-
|ENC_PADDING
| style="background-color:#EEF"|LAME proprietary MP3 '''enc_padding''' value (''e.g.'' 1536)
|-
|MP3_ACCURATE_LENGTH
| style="background-color:#EEF"|'''mp3_accurate_length''' supported (LAME proprietary header)? (''e.g.'' yes)
|-
|MP3_STEREO_MODE
| style="background-color:#EEF"|Stereo mode used in MP3 file (''e.g.'' mono, stereo, joint stereo, etc.)
|-
|VERSION
| style="background-color:#EEF"|'''Version''' of tool (''e.g.'' 3.99)
|-
|FLAGS
| style="background-color:#EEF"|'''Flags''' of tool (''e.g.'' 22)
|}

=== $codec() ===
Returns codec of track. If no codec field is present, it the uses file extension.

Example: ''$codec()'' → "WavPack"

=== $channels() ===
Returns number of channels in text format.

Example: ''$channels()'' → "stereo"

=== %__replaygain_album_gain% ===
Returns ReplayGain album gain value. //Not available through// ''$info(replaygain_album_gain)''.

=== %__replaygain_album_peak% ===
Returns ReplayGain album peak value. //Not available through// ''$info(replaygain_album_peak)''.

=== %__replaygain_track_gain% ===
Returns ReplayGain track gain value. //Not available through// ''$info(replaygain_track_gain)''.

=== %__replaygain_track_peak% ===
Returns ReplayGain track peak value. //Not available through// ''$info(replaygain_track_peak)''.

== Special fields ==

=== $extra(name) ===
Returns the value of the special field called ''name''. These fields can also be accessed as ''%_name%''; note the additional underscore. This syntax is from an older version of Foobar2000 {{Foobar2000v08}}. The following fields can be used normally.
==== %filename% ====
Returns the filename without directory and extension.
==== %filename_ext% ====
Returns the filename with extension, but without the directory.
==== %directoryname% ====
Returns the name of the parent directory only, not the complete path.
==== %lastmodified% ====
Returns the date and time the file was last modified. Eg: ''2005-12-22 00:04:10''
==== %path% ====
Returns the path.
==== %path_raw% ====
Returns the path as URL including the protocol scheme.
==== %subsong% ====
Returns the subsong index. The subsong index is used to distuingish multiple tracks in a single file, for example for cue sheets, tracker modules and various container formats.
==== $extra(foobar2000_version) ====
Returns a string representing the version of foobar2000.

= Variable operations =

Variables can be used to store strings and number. They cannot store truth values. They are best used to store intermediate results that you need multiple times. Variable names are not case-sensitive.

For example:
{| border="0" cellspacing="0" cellpadding="2"
! code
! output
|-
|<pre>$put(foo,bar)$char(10)
$get(foo)$char(10)
$get(Foo)$char(10)
$puts(foo,2000)$char(10)
$get(foo)$char(10)</pre>
| style="background-color:#EEF" |<pre>bar
bar
bar

2000</pre>
|}
=== $get(name) ===

Returns the value that was last stored in the variable ''name'', if the variable was not defined (yet), it returns nothing. The truth value returned by ''$get'' indicates if the variable ''name'' was defined

=== $put(name,value) ===

Stores ''value'' in the variable ''name'' and returns ''value'' unaltered

=== $puts(name,value) ===

Stores ''value'' in the variable ''name'' and returns nothing

= Component-provided fields and functions on tracks =

This section lists components that provide additional fields and functions that are useable in the context of any track.

== Playback statistics ==

* [http://www.foobar2000.org/beta/components.html Playback statistics homepage]
* [[Foobar2000:Titleformat Playback Statistics|Playback statistics titleformat reference]]

= Component-specific fields and functions =

This section lists components that provide additional fields and functions that are only useable in the context of the particular component.

== Album list ==

The official album list component supports creating multiple tree entries using special commands.

* [http://www.foobar2000.org/ Album list homepage]
* [[Foobar2000:Titleformat Album List|Album list titleformat reference]]

== Columns UI ==

* [http://music.morbo.org/wiki/columns_ui:manual Columns UI homepage]
* [http://music.morbo.org/wiki/columns_ui:config:global_variables Global variables reference]
* [http://music.morbo.org/wiki/columns_ui:config:colour_string Playlist colors reference]
* [http://music.morbo.org/wiki/columns_ui:config:playlist_switcher_titleformatting Playlist switcher reference]

== CwBowron's Title formating (foo cwb hooks) ==
foo_cwb_hooks adds various functions and variables to global title formatting:
* [[Foobar2000:0.9_CwBowron%27s_Title_formating_%28foo_cwb_hooks%29|cwb_hooks title formatting wiki page]]

= Additional Reading =

* [[Foobar2000:Titleformat_Introduction|Introduction to titleformat scripts]]
* '''titleformat_help.html''' in your Foobar2000 directory (ie C:\Program Files\foobar2000\titleformat_help.html) file:///C:/Program%20Files/foobar2000/titleformat_help.html

[[Category:foobar2000 Guides|Titleformat Reference]]

Replay Gain

2006-10-09T02:57:24Z

Kjoonlee: /* foobar2000 replaygain scanner */ wav no longer supported

'''Replaygain''' is the name of a technique invented to achieve the same playback volume of audio files. It specifies the reference level of 89dB and an algorithm to measure the '''perceived''' loudness of audio data.

Replaygain is different from [[Normalization|peak normalization]]. In peak normalization, you merely ensure that the peak amplitude reaches a certain level. This does not ensure equal loudness. The replaygain technique measures the ''effective power'' (i.e. RMS after an ''Equal Loudness Filter'') of the waveform, and amplifies the waveform accordingly. The result is that replaygained waveforms are usually more uniformly amplified that peak-normalized waveforms.

==Implementations==

There are different replaygain implementations, each with its own uses and strength. Most of them use [[metadata]] to indicate the level of the volume change (Volume is adjusted on playback; needs player/decoder support) others modify the audio data itself. Generally it is recommended to use an implementation which uses the metadata and does not touch the audio itself.

In a metadata based solution, information on both types of replaygain can be stored, and the desired playback effect can be switched back and forth in the appropriate player. However, if the audio data is permanently modified, only one type of replaygain can be chosen. Furthermore, if the audio data is modified, you may not be able to restore the original data, especially if the replaygain technique produces a negative amplification.

Replaygain has significant advantages over normalizing. It allows the loudness of a song to be consistant over an entire collection of audio, similar to (but more accurate than) RMS normalizing (this is called 'Track Gain', or 'Radio Gain' in earlier parlance). However, it also allows the loudness of an album to be consistant over a entire music collection, allowing the dynamics of album to remain (This is called 'Album Gain', or 'Audiophile Gain' in earlier parlance). This is usually very important in classical CDs, as there may be quiet segments and loud segments written into different tracks.

===MP3Gain===
[[MP3Gain]] is an implementation of Replaygain. It either modifies target data reversibly, or attaches metadata.

* Format: [[MP3]]
* Method: Audio / Meta
* Limitations: Limited to 1.5dB steps mode, may become irreversible
* http://mp3gain.sourceforge.net/

===[[LAME]]===

* Method: Header ([http://gabriel.mp3-tech.org/mp3infotag.html mp3infotag])
* Notes:
** Tags added during encoding; not supported by any player yet; Track Gain only
** ReplayGaining MP3's are usually done using MP3Gain (see [[Replaygain#MP3Gain|above]]) or [[Replaygain#foobar2000 replaygain scanner|foobar2000]]
* http://lame.sourceforge.net/

===[[MPC]] replaygain===

* Method: Header (similar to Meta data method)
* Notes: Replaygain values are stored in the header and replaygain is part of the Musepack specifications; therefore any Musepack decoder that does not support replaygain can be considered broken.
* http://rarewares.org/mpc.html

===VorbisGain===

* Format: [[Ogg Vorbis]]
* Method: Meta (in [[Vorbis comment]])
* http://www.sjeng.org/vorbisgain.html
:'''''Note:''' Andavari has provided a very useful script to integrate VorbisGain, which is a CLI tool, into Windows Explorer. Please [[Ogg Vorbis#ReplayGain|check this section]].

===FLAC / METAFLAC===

* Format: [[FLAC]]
* Method: Meta (in [[Vorbis comment]])
* http://flac.sf.net

===WavPack / WVGAIN===

* Format: [[WavPack]]
* Method: Meta (in [[APEv2]] tag)
* http://www.wavpack.com

===Wavegain===

* Format: waveform
* Method: Audio
* Limitations: Irreversible
* http://www.rarewares.org/files/others/wavegain.zip

===[[foobar2000]] replaygain scanner===

* Format:
** [[MP3]]: Values written to [[APEv2]] or [[ID3v2]] tags.
** [[MPC]]: Values written to header.
** [[Ogg Vorbis]]: Values written to [[Vorbis comment]].
** [[WavPack]]: Values written to [[APEv2]] tags.
** [[AAC]]: Values written to [[APEv2]] tags.
** [[MP4]]: Uses its own itunes-compatible tagging system (though itunes does not support replaygain).
** [[FLAC]]: Values written to [[Vorbis comment]].
** [[APE]]: Values written to [[APEv2]] tags.
** Modules ([[MOD]] etc.): Optionally saved into [[APEv2]] tags; otherwise the foobar2000 database is used.
** All other formats are supported but the replaygain values are saved to the foobar2000 database.

* You can also choose to only have the replaygain values saved in the foobar2000 database and leave the files untouched.

* http://foobar2000.org

===[[MediaMonkey]]===

* Format:
** [[MP3]]: Values written to [[APEv2]] or [[ID3v2]] tags.
** [[Ogg Vorbis]]: Values written to [[Vorbis comment]].
** [[WMA]]: Values stored in MediaMonkey's MDB database.
** [[FLAC]]: Values written to [[Vorbis comment]].
** [[APE]]: Values written to [[APEv2]] tags.
** [[WAV]]: Values stored in MediaMonkey's MDB database.
* In addition to tags, all ReplayGain values are also stored in MediaMonkey's MDB database
* Does not support Album/Audiophile replaygain
* Also capable of (irreversibly) changing the volume of MP3 tracks, similar to [[MP3Gain]]
* http://www.mediamonkey.com

==Players support==

Replaygain being present in the specs of FLAC, MPC, and APE formats, any player that support those formats usually support replaygain.

The situation with MP3 is rather different, as it was not part of the MP3 specs. The APEv2 tags metadata implementation is somewhat becoming the de-facto standard.

===Windows===

* [[Foobar2000]] supports replaygain in all possible aspects.
* [[Winamp]]
** MP3 replaygain support with adequate plugins (e.g. [http://otachan.com/in_!mpg123.html Otachan's in_!mpg123] - if you can't read japanese, you can find details [http://www.hydrogenaudio.org/forums/index.php?showtopic=18530 in this thread])
** [[Ogg Vorbis]] replaygain support
* [[MediaMonkey]] supports track replaygain only
* [[XMPlay]] recently implemented replaygain

''...and probably others.''

===Linux===

* [[XMMS]]. Reads replaygain from [[FLAC]], [[MPC]], [[Ogg Vorbis]] ..
:For [[MP3]], use the CVS version of the [http://xmms-mad.sourceforge.net/ xmms-mad] mp3 plugin (it's not yet released as binary, furthermore not available in distribs' versions for now. Meanwhile binaries are available here: [http://perso.crans.org/~krempp/xmms-mad/ custom binaries])
* [[amarok]]. By using the amarok-script [http://kde-apps.org/content/show.php?content=26073 ReplayGain]
:And possibly others, since [http://developer.kde.org/~wheeler/taglib.html TagLib] added support for [[APEv2]] tags in [[MP3]] files, players using this library (like [[amaroK]] and [[JuK]]) might support that kind of replaygain tags in the near future.
* [http://www.sacredchao.net/quodlibet Quod Libet] reads replaygain from [[Ogg Vorbis]], [[MP3]], [[FLAC]], and [[MPC]].
:Requires support to be enabled (via the appropriate python bindings and libraries) for the above formats. Does not support replaygain values stored in [[APEv2]] tags in [[MP3]]s. Replaygain values are stored in RVA2 id3v2.4 frames. See the [http://www.sacredchao.net/quodlibet/wiki/Development/ID3Notes Quod Libet RVA2 / ReplayGain notes].
* [http://www.musicpd.org/ Music Player Daemon] (MPD) reads replaygain from [[Ogg Vorbis]], [[FLAC]], and [[MPC]].
:Foobar2000 style TXXX frames in [[MP3]]s are also supported in the latest development releases.

===Portable devices===

Current development builds of [http://www.rockbox.org/ Rockbox] for the iRiver H100 and H300 series players support replaygain for some encoder formats. This is a rapidly evolving feature. There are no other portable players known to support replaygain.

The iPod features ''Soundcheck'', which seems to produce roughly the same normalization gains as replaygain, but doesn't provide an Album Gain.

==Additional reading==
* [http://replaygain.hydrogenaudio.org Original Replay Gain website]
* [http://en.wikipedia.org/wiki/Replay_Gain Replay Gain] at Wikipedia
* [http://www.bobulous.org.uk/misc/Replay-Gain.html Replay Gain using Foobar 2000] (how-to).

[[Category:Signal Processing]]

Hydrogenaudio Knowledgebase:Deletion requests/ID3v2.4.1

2006-09-30T17:25:10Z

Kjoonlee: tweak

'''[[:Category:Pages marked for deletion|Back to deletion requests]]'''

==[[:ID3v2.4.1|ID3v2.4.1]]==
<small>To vote, use this code: {{votecode}}</small><br>
<small>To admins: If a consensus has been reached, add {{endcode}} to the end of this page, and carry out the appropriate action.</small><br><nowiki>

</nowiki>

Why not kill this page altogether, as if people will go looking for ID3v2.4.1 here...? <small>– unsigned comment by [[User:pepoluan|pepoluan]], 18:32, 29 September 2006</small>
*'''Delete''' -- Maybe we should have only one ID3 related page. However depending on the level of detail it might not be a good idea. <small>– unsigned comment by [[User:Beto|Beto]], 21:06, 29 September 2006</small>
*'''Delete''' and '''bonk''' none-singing users on the head with a large hammer {{User:Elliottmobile/sig2}} 09:12, 30 September 2006 (CDT)
*'''Move''' to [[User:DEATH/ID3v2.4.1]]. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 12:23, 30 September 2006 (CDT)
**And create a redirect to [[ID3v2]] in its place. ID3v2 should have a link to the proposal (when and if it becomes publicly available). <del>--'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 12:24, 30 September 2006 (CDT)</del> --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 12:25, 30 September 2006 (CDT)

Hydrogenaudio Knowledgebase:Deletion requests/ID3v2.4.1

2006-09-30T17:24:45Z

Kjoonlee:

'''[[:Category:Pages marked for deletion|Back to deletion requests]]'''

==[[:ID3v2.4.1|ID3v2.4.1]]==
<small>To vote, use this code: {{votecode}}</small><br>
<small>To admins: If a consensus has been reached, add {{endcode}} to the end of this page, and carry out the appropriate action.</small><br><nowiki>

</nowiki>

Why not kill this page altogether, as if people will go looking for ID3v2.4.1 here...? <small>– unsigned comment by [[User:pepoluan|pepoluan]], 18:32, 29 September 2006</small>
*'''Delete''' -- Maybe we should have only one ID3 related page. However depending on the level of detail it might not be a good idea. <small>– unsigned comment by [[User:Beto|Beto]], 21:06, 29 September 2006</small>
*'''Delete''' and '''bonk''' none-singing users on the head with a large hammer {{User:Elliottmobile/sig2}} 09:12, 30 September 2006 (CDT)
*'''Move''' to [[User:DEATH/ID3v2.4.1]]. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 12:23, 30 September 2006 (CDT)
**And create a redirect to [[ID3]] in its place. ID3 should have a link to the proposal (when and if it becomes publicly available). --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 12:24, 30 September 2006 (CDT)

Hydrogenaudio Knowledgebase:Deletion requests/ID3v2.4.1

2006-09-30T17:23:40Z

Kjoonlee: move

APEv2

2006-09-28T07:49:33Z

Kjoonlee: cat 2

APEv2 is a tagging format derived from [[APEv1]] originally developed for [[MPC]] audio files, and is now also used in [[Monkey's Audio]], [[WavPack]] and [[OptimFROG]]. It can also be used with other formats when using programs like [[foobar2000]] or [[Tag.exe|Tag]] (a program that can create and read tags). It is comparable in functionality to [[Vorbis comment]]. Just like Vorbis comment it defines some standard fields, but it also defines some formats for those fields (like what a date should look like).

APEv2 also differs from Vorbis comment in the way lists of values are handled. Suppose a certain song has two artists. In Vorbis comment this will result in two ARTIST entries, but in APEv2 this will result in one Artist field with the two artists separated by a null character (a byte with the value zero).

==Addtional Reading==
* [[APEv2 specification]]

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

Template:Usertalkheader

2006-09-26T19:00:47Z

Kjoonlee: be nice

{| class="messagebox standard-talk" id="talkheader" align="center" style="text-align:center;background-color: #FFFFFF; width: 85%; margin-bottom:30px;"
|-
! colspan="2" style="border:1px solid #C0C090; background-color: #F8EABA;" |
This is the user talk page for <font style="color:blue;">{{{1|{{SUBPAGENAME}}}}}</font>.
|-
| style="background-color: #FFFFFF; text-align:left;" |
*Be nice, and stay civil.
*'''Sign and date your posts''' using two dashes and four tildes (<code><nowiki>--~~~~</nowiki></code>).
*Place new comments after existing ones (but within topic sections).
*Separate topic sections with a '''<code><nowiki>==Descriptive header==</nowiki></code>'''.
*Feel free to use these smilies by embedding their codes:<br /> {{smiley|)}} <code><nowiki>{{smiley|)}}</nowiki></code> {{smiley|D}} <code><nowiki>{{smiley|D}}</nowiki></code> {{smiley|(}} <code><nowiki>{{smiley|(}}</nowiki></code> {{smiley|;}} <code><nowiki>{{smiley|;}}</nowiki></code>

*'''New to Hydrogenaudio Wiki?''' [[Main_Page|Welcome]]! You may want to read our [[FAQ|frequently asked questions]].
|}<noinclude>
== Usage ==
For user talk pages.</noinclude>

User talk:Elliottmobile

2006-09-26T18:40:39Z

Kjoonlee: /* Talk header */

{{talkheader}}

HELLO ELLIOT I AM GREAT HAXOR YOUR WIKI ~[[User:Elliottmobile|Elliottmobile]] <small>'''([[User_talk:Elliottmobile|talk]] | [[Special:Contributions/Elliottmobile|contribs]])'''</small> 03:37, 18 September 2006 (CDT)

== NO ==
I AM USING THIS COMPUTERWEBNET RESPONSORBORLY ~[[User:Elliottmobile|Elliottmobile]] <small>'''([[User_talk:Elliottmobile|talk]] | [[Special:Contributions/Elliottmobile|contribs]])'''</small> 03:37, 18 September 2006 (CDT)

==Eh?==

Welcome Elliott... glad to have someone well-versed with WikiMedia syntax... and what does the above comments supposed to mean? --[[User:Pepoluan|pepoluan]] 09:56, 18 September 2006 (CDT)

I thought you were insane, but apparently you are crazy {{slimey|D}} {{smiley|D}} --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 12:48, 22 September 2006 (CDT)
:Slimey indeed. {{User:Elliottmobile/sig2}} 12:49, 22 September 2006 (CDT)

What about loom(tm)? --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 07:49, 25 September 2006 (CDT)
:<insert blab from MI that I forgot having not played it for years> {{User:Elliottmobile/sig2}} 15:28, 25 September 2006 (CDT)
::LOL... *fires up ScummVM and chucks in the MI CD* --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 15:46, 25 September 2006 (CDT)
:::{{smiley|D}}. Oops, I mean {{slimey}} {{User:Elliottmobile/sig2}} 15:49, 25 September 2006 (CDT)

==Answer to the question on my talk page==
You can find my considerations on your copyright comments [[User_talk:Beto|here]].{{smiley|)}}--[[User:Beto|Beto]] <small>'''([[User_talk:Beto|talk]] | [[Special:Contributions/Beto|contribs]])'''</small> 16:51, 18 September 2006 (CDT)

==Please stop meddling==
There was no reason for you to interfere with the templates on my talk page or the name of the article I am working on that I linked to on my user page. Kindly sod off. -- [[User:Canar|Canar]] 19:37, 24 September 2006 (CDT)

== Talk header ==

Hi, the talk header is not mandatory for all articles; it's only optional, and it's definitely not intended for user talk pages. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:26, 26 September 2006 (CDT)
:iirc, it was intended for all articles and all major contributors use it on their user talk page. {{User:Elliottmobile/sig2}} 13:28, 26 September 2006 (CDT)
::Well, it was copied from Wikipedia, and if you look at the Wikipedia version's "What links here" list, you'll find thousands (really!) of links coming from Talk pages, and a few links from Wikipedia talk and Template talk pages. I bet you can't find one coming from a user talk page.<br />Most major contributors aren't probably familiar with MediaWiki or Wikipedia. Looks like I'm the one who's most familiar with how stuff works over there. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:34, 26 September 2006 (CDT)
:::"Most major contributors aren't probably familiar with MediaWiki or Wikipedia. Looks like I'm the one who's most familiar with how stuff works over there." heh, nope, i'm a very active contributor over there. It's just that this place isn't wikipedia. see [[user_talk:pepoluan]] & [[user_talk:beto]] {{User:Elliottmobile/sig2}} 13:36, 26 September 2006 (CDT)
::::Ah, but pepoluan didn't know that stub templates go at the bottom and cleanup templates go at the top at Wikipedia. Only I knew that SVG files get rendered to PNG files at Wikipedia.<br />You're right that HAK isn't WP, but I still don't think the [[Template:Talkheader|talkheader]] was intended for user pages. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:39, 26 September 2006 (CDT)

User talk:Elliottmobile

2006-09-26T18:39:51Z

Kjoonlee: /* Talk header */

{{talkheader}}

HELLO ELLIOT I AM GREAT HAXOR YOUR WIKI ~[[User:Elliottmobile|Elliottmobile]] <small>'''([[User_talk:Elliottmobile|talk]] | [[Special:Contributions/Elliottmobile|contribs]])'''</small> 03:37, 18 September 2006 (CDT)

== NO ==
I AM USING THIS COMPUTERWEBNET RESPONSORBORLY ~[[User:Elliottmobile|Elliottmobile]] <small>'''([[User_talk:Elliottmobile|talk]] | [[Special:Contributions/Elliottmobile|contribs]])'''</small> 03:37, 18 September 2006 (CDT)

==Eh?==

Welcome Elliott... glad to have someone well-versed with WikiMedia syntax... and what does the above comments supposed to mean? --[[User:Pepoluan|pepoluan]] 09:56, 18 September 2006 (CDT)

I thought you were insane, but apparently you are crazy {{slimey|D}} {{smiley|D}} --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 12:48, 22 September 2006 (CDT)
:Slimey indeed. {{User:Elliottmobile/sig2}} 12:49, 22 September 2006 (CDT)

What about loom(tm)? --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 07:49, 25 September 2006 (CDT)
:<insert blab from MI that I forgot having not played it for years> {{User:Elliottmobile/sig2}} 15:28, 25 September 2006 (CDT)
::LOL... *fires up ScummVM and chucks in the MI CD* --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 15:46, 25 September 2006 (CDT)
:::{{smiley|D}}. Oops, I mean {{slimey}} {{User:Elliottmobile/sig2}} 15:49, 25 September 2006 (CDT)

==Answer to the question on my talk page==
You can find my considerations on your copyright comments [[User_talk:Beto|here]].{{smiley|)}}--[[User:Beto|Beto]] <small>'''([[User_talk:Beto|talk]] | [[Special:Contributions/Beto|contribs]])'''</small> 16:51, 18 September 2006 (CDT)

==Please stop meddling==
There was no reason for you to interfere with the templates on my talk page or the name of the article I am working on that I linked to on my user page. Kindly sod off. -- [[User:Canar|Canar]] 19:37, 24 September 2006 (CDT)

== Talk header ==

Hi, the talk header is not mandatory for all articles; it's only optional, and it's definitely not intended for user talk pages. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:26, 26 September 2006 (CDT)
:iirc, it was intended for all articles and all major contributors use it on their user talk page. {{User:Elliottmobile/sig2}} 13:28, 26 September 2006 (CDT)
::Well, it was copied from Wikipedia, and if you look at the Wikipedia version's "What links here" list, you'll find thousands (really!) of links coming from Talk pages, and a few links from Wikipedia talk and Template talk pages. I bet you can't find one coming from a user talk page.<br />Most major contributors aren't probably familiar with MediaWiki or Wikipedia. Looks like I'm the one who's most familiar with how stuff works over there. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:34, 26 September 2006 (CDT)
:::"Most major contributors aren't probably familiar with MediaWiki or Wikipedia. Looks like I'm the one who's most familiar with how stuff works over there." heh, nope, i'm a very active contributor over there. It's just that this place isn't wikipedia. see [[user_talk:pepoluan]] & [[user_talk:beto]] {{User:Elliottmobile/sig2}} 13:36, 26 September 2006 (CDT)
::::Ah, but pepoluan didn't know that stub templates go at the bottom and cleanup templates go at the top at Wikipedia. Only I knew that SVG files get rendered to PNG files at Wikipedia.<br />You're right that HAK isn't WP, but I still don't think the [[Template:Talk header|talk header]] was intended for user pages. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:39, 26 September 2006 (CDT)

User:Kjoonlee

2006-09-26T18:35:21Z

Kjoonlee:

Hi, please feel free to leave a message on my talk page.

User talk:Elliottmobile

2006-09-26T18:34:05Z

Kjoonlee: /* Talk header */

User talk:Canar

2006-09-26T18:28:29Z

Kjoonlee: /* Removing comments from your talk page */

No more issue. Baleeted. Thanks, Jan. -- [[User:Canar|Canar]] 15:27, 24 September 2006 (CDT)

Please refrain from re-adding the talkheader template to this page. -- [[User:Canar|Canar]] 17:20, 24 September 2006 (CDT)

== In response to you: ==

"There was no reason for you to interfere with the templates on my talk page or the name of the article I am working on that I linked to on my user page. Kindly sod off."

First, talkheader is required to go at the start of all pages. It just does. And I didn't change any article name. In regards to "Kindy sod off," would I be right in thinking that's a personal attack? You obviously canot reason beyond flames thus I will terminate this discussion now. {{User:Elliottmobile/sig2}} 02:16, 25 September 2006 (CDT)

Oh, you meant your incorrect userpage. It means "user page fro a user named Canar:Titl..., not Subpage of Canar's userpage called Titl...". I really don't see how your decisions can override mediawiki conventions. {{User:Elliottmobile/sig2}} 02:22, 25 September 2006 (CDT)

:Your talk page has none. Many users' talk pages have none. Why is mine special? And why do mediawiki "conventions" override a user's wishes? The point of software is to be usable. My user page is quasi-public. I have it there because it's easy for me, and I should be the one whose judgement is used in what goes and what doesn't go on my user page (within obvious reason). As it is, my user page actually has something resembling content, which is more than can be said about yours. As for the "sod off", I was frustrated by your actions. Perhaps it was not required, but you're being a hypocrite about the talkheader. Anyhow, I've wasted enough time on you. Go away. Leave me alone. kthxbye -- [[User:Canar|Canar]] 21:59, 25 September 2006 (CDT)
::My talk page has none because nobody has thought to add one yet. Remember, ''anyone'' can change anything, and that includes your wishes. It is not "your document" at all. And, the software defines Something/page as a subpage and properly handles it. On that note...

@@@ This is a header @@@<br />
*This is bold*. The formatting is my wishes and you shall not change it. {{User:Elliottmobile/sig2}} 03:09, 26 September 2006 (CDT)

== Removing comments from your talk page ==

Hi, at Wikipedia, it's considered bad manners to remove other people's comments from your talk page. If you want, you can move your talk page to a subpage and create a new talk page. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:25, 26 September 2006 (CDT)
:Edited. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:28, 26 September 2006 (CDT)

User talk:Elliottmobile

2006-09-26T18:26:50Z

Kjoonlee: Talk header

HELLO ELLIOT I AM GREAT HAXOR YOUR WIKI ~[[User:Elliottmobile|Elliottmobile]] <small>'''([[User_talk:Elliottmobile|talk]] | [[Special:Contributions/Elliottmobile|contribs]])'''</small> 03:37, 18 September 2006 (CDT)

== NO ==
I AM USING THIS COMPUTERWEBNET RESPONSORBORLY ~[[User:Elliottmobile|Elliottmobile]] <small>'''([[User_talk:Elliottmobile|talk]] | [[Special:Contributions/Elliottmobile|contribs]])'''</small> 03:37, 18 September 2006 (CDT)

==Eh?==

Welcome Elliott... glad to have someone well-versed with WikiMedia syntax... and what does the above comments supposed to mean? --[[User:Pepoluan|pepoluan]] 09:56, 18 September 2006 (CDT)

I thought you were insane, but apparently you are crazy {{slimey|D}} {{smiley|D}} --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 12:48, 22 September 2006 (CDT)
:Slimey indeed. {{User:Elliottmobile/sig2}} 12:49, 22 September 2006 (CDT)

What about loom(tm)? --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 07:49, 25 September 2006 (CDT)
:<insert blab from MI that I forgot having not played it for years> {{User:Elliottmobile/sig2}} 15:28, 25 September 2006 (CDT)
::LOL... *fires up ScummVM and chucks in the MI CD* --[[User:Pepoluan|pepoluan]] <small>'''([[User_talk:pepoluan|talk]] | [[Special:Contributions/pepoluan|contribs]])'''</small> 15:46, 25 September 2006 (CDT)
:::{{smiley|D}}. Oops, I mean {{slimey}} {{User:Elliottmobile/sig2}} 15:49, 25 September 2006 (CDT)

==Answer to the question on my talk page==
You can find my considerations on your copyright comments [[User_talk:Beto|here]].{{smiley|)}}--[[User:Beto|Beto]] <small>'''([[User_talk:Beto|talk]] | [[Special:Contributions/Beto|contribs]])'''</small> 16:51, 18 September 2006 (CDT)

==Please stop meddling==
There was no reason for you to interfere with the templates on my talk page or the name of the article I am working on that I linked to on my user page. Kindly sod off. -- [[User:Canar|Canar]] 19:37, 24 September 2006 (CDT)

== Talk header ==

Hi, the talk header is not mandatory for all articles; it's only optional, and it's definitely not intended for user talk pages. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:26, 26 September 2006 (CDT)

User talk:Canar

2006-09-26T18:25:51Z

Kjoonlee: Removing comments from your talk page

No more issue. Baleeted. Thanks, Jan. -- [[User:Canar|Canar]] 15:27, 24 September 2006 (CDT)

Please refrain from re-adding the talkheader template to this page. -- [[User:Canar|Canar]] 17:20, 24 September 2006 (CDT)

== In response to you: ==

"There was no reason for you to interfere with the templates on my talk page or the name of the article I am working on that I linked to on my user page. Kindly sod off."

First, talkheader is required to go at the start of all pages. It just does. And I didn't change any article name. In regards to "Kindy sod off," would I be right in thinking that's a personal attack? You obviously canot reason beyond flames thus I will terminate this discussion now. {{User:Elliottmobile/sig2}} 02:16, 25 September 2006 (CDT)

Oh, you meant your incorrect userpage. It means "user page fro a user named Canar:Titl..., not Subpage of Canar's userpage called Titl...". I really don't see how your decisions can override mediawiki conventions. {{User:Elliottmobile/sig2}} 02:22, 25 September 2006 (CDT)

:Your talk page has none. Many users' talk pages have none. Why is mine special? And why do mediawiki "conventions" override a user's wishes? The point of software is to be usable. My user page is quasi-public. I have it there because it's easy for me, and I should be the one whose judgement is used in what goes and what doesn't go on my user page (within obvious reason). As it is, my user page actually has something resembling content, which is more than can be said about yours. As for the "sod off", I was frustrated by your actions. Perhaps it was not required, but you're being a hypocrite about the talkheader. Anyhow, I've wasted enough time on you. Go away. Leave me alone. kthxbye -- [[User:Canar|Canar]] 21:59, 25 September 2006 (CDT)
::My talk page has none because nobody has thought to add one yet. Remember, ''anyone'' can change anything, and that includes your wishes. It is not "your document" at all. And, the software defines Something/page as a subpage and properly handles it. On that note...

@@@ This is a header @@@<br />
*This is bold*. The formatting is my wishes and you shall not change it. {{User:Elliottmobile/sig2}} 03:09, 26 September 2006 (CDT)

== Removing comments from your talk page ==

At Wikipedia, it's considered bad manners to remove other people's comments from your talk page. If you want, you can move your talk page to a subpage. --'''[[User:Kjoonlee|Kjoon]]'''[[User talk:Kjoonlee|lee]] 13:25, 26 September 2006 (CDT)

LAME Compiles

2006-09-22T03:09:24Z

Kjoonlee: direct link

#REDIRECT [[LAME]]

Transparency

2006-09-15T04:57:19Z

Kjoonlee: input data matters as well

In [[psychoacoustics]], '''transparency''' is the ideal result of [[lossy]] data compression. If a lossily compressed result is perceptually indistinguishible from the uncompressed input, then the compression can be declared to be transparent. In other words, transparency is the situation where [[artifact]]s are nonexistant or imperceptible.

Transparency, like sound quality, is subjective. It depends most on the listener's familiarity with artifacts, and to a lesser extent, the compression method, [[bitrate]] used, input characteristics, listening conditions, and listening equipment.

Judging transparency can be difficult due to observation bias, in which subjective like/dislike of a certain compression methodology emotionally influences his/her judgment. This bias is commonly referred to as ''placebo,'' although this use is slightly different from the medical use of the term.

There is no way to prove whether a certain compression methodology is transparent. To scientifically prove that a compression method is ''not'' transparent, double-blind tests may be useful. The [[ABX]] method is normally used.

{{stub}}

[[Category:Listening Tests]]

XMplay

2006-09-15T01:59:44Z

Kjoonlee: redirected

#REDIRECT [[XMPlay]]

XMPlay

2006-09-15T01:59:16Z

Kjoonlee: merged

'''XMPlay''' is a freeware audio player developed by Ian Luck (Un4Seen Developments), the creator of the audio library BASS. XMPlay supports Ogg Vorbis, MP1, MP2, MP3, WMA, MO3, IT, XM, S3M, MTM, MOD and UMX audio formats and PLS, M3U, ASX and WAX playlists. Support for additional formats can be achieved by plugins.

When XMPlay was first released in 1998, only the XM format was supported, hence the name "XMPlay".

It has a small footprint, and supports plugins, skins, global hotkeys and much more.

==External Links==
*[http://www.un4seen.com/xmplay.html XMPlay]
*[http://www.un4seen.com un4seen developments]

Block switching

2006-09-11T15:01:30Z

Kjoonlee: Del merge templates

The Psychoacoustic model decides when to '''switch''' to short blocks and back to long blocks (block switching).

In [[MP3]], switching to short blocks will isolate the attack to 192 sample window, so the oscillations are only spread over 192 samples instead of 576. Block switching is also used by [[Ogg Vorbis]] and [[AAC]], ''(except on windows that can be a power of two only)''. [[MPC]], being a [[subband|subband coder]] doesn't make use of block switching, ''(although it is implemented and can be used)''

Switching to short blocks and increasing of the [[bitrate]] to encode a series of [[MDCT]] coefficients of a particular [[transient]] is one way to combat [[Pre echo]].

==Long blocks==
Audio encoding systems will commonly summarise the sound energy in one small stretch of time at a time. The duration of a single summarisation is also called a [[window]] and once a window of sound has been quantised, selected and packed, it can be considered as an individual block of audio information to be finaly stored in a frame.

Available mathematics used to summarise one block at a time can struggle with evenly representing details throughout a window's duration. There may be a tendency to mirror features at the start of the window onto the other end of the window, or the ends of the window might be the most efficient place to have details occur, it will depend on the particular mathematical transformation used.
With such variance in transformation accuracy throughout each block, varying the size of blocks to best fit over the actual details present in the audio stream increases the overall accuracy of the encoding.

[[LAME]] has only two block sizes available, long blocks and short blocks. In Lame's case Short blocks require more data to describe less time than Long blocks so they are only selected when they significantly improve the alignment of transformation windows to audio details.

==Additional reading==

Some Java applets to examine fourier series behaviour (note that [[MDCT]] behaviour is not totally identical):

*; http://www.jhu.edu/~signals/fourier2/ : You can draw a sharp attack here, and use calculate with a large number of coefficients... if you start to reduce the number of coefficients you will see the [[pre echo]] appear.

*; http://www.gac.edu/~huber/fourier : Doesnt seem to work in netscape. iirc this one lets you listen to the sound.

*; http://www.univie.ac.at/future.media/moe/galerie/fourier/fourier.html : Maths online fourier series applet.

Long block

2006-09-11T15:00:28Z

Kjoonlee: #REDIRECT Block switching

#REDIRECT [[Block switching]]

Short block

2006-09-11T15:00:13Z

Kjoonlee: #REDIRECT Block switching

#REDIRECT [[Block switching]]

Block switching

2006-09-11T14:59:44Z

Kjoonlee: simple merge from old version of Long block

{{merge-from|Short block}}
{{merge-from|Long block}}

The Psychoacoustic model decides when to switch to short blocks and back to long blocks (block switching).

In [[MP3]], switching to short blocks will isolate the attack to 192 sample window, so the oscillations are only spread over 192 samples instead of 576. Block switching is also used by [[Ogg Vorbis]] and [[AAC]], ''(except on windows that can be a power of two only)''. [[MPC]], being a [[subband|subband coder]] doesn't make use of block switching, ''(although it is implemented and can be used)''

Switching to short blocks and increasing of the [[bitrate]] to encode a series of [[MDCT]] coefficients of a particular [[transient]] is one way to combat [[Pre echo]].

==Long blocks==
Audio encoding systems will commonly summarise the sound energy in one small stretch of time at a time. The duration of a single summarisation is also called a [[window]] and once a window of sound has been quantised, selected and packed, it can be considered as an individual block of audio information to be finaly stored in a frame.

Available mathematics used to summarise one block at a time can struggle with evenly representing details throughout a window's duration. There may be a tendency to mirror features at the start of the window onto the other end of the window, or the ends of the window might be the most efficient place to have details occur, it will depend on the particular mathematical transformation used.
With such variance in transformation accuracy throughout each block, varying the size of blocks to best fit over the actual details present in the audio stream increases the overall accuracy of the encoding.

[[LAME]] has only two block sizes available, long blocks and short blocks. In Lame's case Short blocks require more data to describe less time than Long blocks so they are only selected when they significantly improve the alignment of transformation windows to audio details.

==Additional reading==

Some Java applets to examine fourier series behaviour (note that [[MDCT]] behaviour is not totally identical):

*; http://www.jhu.edu/~signals/fourier2/ : You can draw a sharp attack here, and use calculate with a large number of coefficients... if you start to reduce the number of coefficients you will see the [[pre echo]] appear.

*; http://www.gac.edu/~huber/fourier : Doesnt seem to work in netscape. iirc this one lets you listen to the sound.

*; http://www.univie.ac.at/future.media/moe/galerie/fourier/fourier.html : Maths online fourier series applet.

Template:Merge-to

2006-09-06T23:42:56Z

Kjoonlee: left

<div class="messagebox merge">[[Image:Merge-to.gif|left]] It has been suggested that this article or section be [[Wikipedia:Merging and moving pages|merged]] into ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. ([[{{{2|:{{NAMESPACE}} talk:{{{1}}}}}}|Discuss]])</div><includeonly>
[[Category:Items to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly>

Template:Merge-from

2006-09-06T23:42:46Z

Kjoonlee: left

<div class="messagebox merge">[[Image:Merge-from.gif|left]] It has been suggested that ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]'' be [[Wikipedia:Merging and moving pages|merged]] into this article or section. ([[{{{2|:{{NAMESPACE}} talk:{{PAGENAMEE}}}}}|Discuss]])</div><includeonly>[[Category:Items to be merged|{{PAGENAME}}]]</includeonly>

Template:Merge

2006-09-06T23:41:51Z

Kjoonlee:

<noinclude></noinclude><div class="messagebox merge">[[Image:Merge.gif|left]] It has been suggested that this article or section be [[Wikipedia:Merging and moving pages|merged]] with ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. ([[{{{2|:{{NAMESPACE}} talk:{{PAGENAMEE}}}}}|Discuss]])</div><includeonly>[[Category:Items to be merged|{{PAGENAME}}]]</includeonly>

File:Merge.gif

2006-09-06T23:40:03Z

Kjoonlee: PD image from Wikipedia

PD image from Wikipedia

Template:Merge-from

2006-09-06T23:39:32Z

Kjoonlee: image

<div class="messagebox merge">[[Image:Merge-from.gif]] It has been suggested that ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]'' be [[Wikipedia:Merging and moving pages|merged]] into this article or section. ([[{{{2|:{{NAMESPACE}} talk:{{PAGENAMEE}}}}}|Discuss]])</div><includeonly>[[Category:Items to be merged|{{PAGENAME}}]]</includeonly>

File:Merge-from.gif

2006-09-06T23:38:20Z

Kjoonlee: PD image from Wikipedia

PD image from Wikipedia

Template:Merge-to

2006-09-06T23:37:30Z

Kjoonlee: image

<div class="messagebox merge">[[Image:Merge-to.gif]] It has been suggested that this article or section be [[Wikipedia:Merging and moving pages|merged]] into ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. ([[{{{2|:{{NAMESPACE}} talk:{{{1}}}}}}|Discuss]])</div><includeonly>
[[Category:Items to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly>

File:Merge-to.gif

2006-09-06T23:37:12Z

Kjoonlee: PD image from Wikipedia

PD image from Wikipedia

Template:Merge-to

2006-09-06T23:32:19Z

Kjoonlee: try items

<div class="messagebox merge">→
It has been suggested that this article or section be [[Wikipedia:Merging and moving pages|merged]] into ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. ([[{{{2|:{{NAMESPACE}} talk:{{{1}}}}}}|Discuss]])</div><includeonly>
[[Category:Items to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly>

Template:Merge-from

2006-09-06T23:31:40Z

Kjoonlee: try items

<div class="messagebox merge">← It has been suggested that ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]'' be [[Wikipedia:Merging and moving pages|merged]] into this article or section. ([[{{{2|:{{NAMESPACE}} talk:{{PAGENAMEE}}}}}|Discuss]])</div><includeonly>[[Category:Items to be merged|{{PAGENAME}}]]</includeonly>

Template:Merge-from

2006-09-06T23:26:40Z

Kjoonlee:

Template:Merge-to

2006-09-06T23:25:32Z

Kjoonlee:

<div class="messagebox merge">→
It has been suggested that this article or section be [[Wikipedia:Merging and moving pages|merged]] into ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. ([[{{{2|:{{NAMESPACE}} talk:{{{1}}}}}}|Discuss]])</div><includeonly>
[[Category:{{#if:{{NAMESPACE}}|Items|Articles}} to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly>

Template:Merge-from

2006-09-06T23:23:22Z

Kjoonlee:

<div class="messagebox merge">← It has been suggested that ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]'' be [[Wikipedia:Merging and moving pages|merged]] into this article or section. ([[{{{2|:{{NAMESPACE}} talk:{{PAGENAMEE}}}}}|Discuss]])</div><includeonly>[[Category:{{#if:{{NAMESPACE}}|Items|Articles}} to be merged|{{PAGENAME}}]]</includeonly><noinclude>
{{/doc}}
</noinclude>

Template:Merge-to

2006-09-06T23:20:48Z

Kjoonlee:

<div class="messagebox merge">←
It has been suggested that this article or section be [[Wikipedia:Merging and moving pages|merged]] into ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. ([[{{{2|:{{NAMESPACE}} talk:{{{1}}}}}}|Discuss]])</div><includeonly>
[[Category:{{#if:{{NAMESPACE}}|Items|Articles}} to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly><noinclude>
{{/doc}}
</noinclude>