TTA - Revision history

Porcuswiki: two words

2025-12-19T10:45:31Z

two words

← Older revision		Revision as of 10:45, 19 December 2025
Line 13:		Line 13:
	The project itself might be abandoned, but a 3rd party source code rewrite appeared in 2023<ref>[https://github.com/stseelig/libttaR Github home of the 3rd party rewrite]</ref><ref>[https://hydrogenaud.io/index.php/topic,125048.0.html Hydrogenaudio forum post (2023) on codec rewrite]</ref><ref>[https://hydrogenaud.io/index.php/topic,125143.0.html Hydrogenaudio forum post (2023) on codec rewrite (library)] </ref>. The codec sometimes identifies itself as "TTA1", and an announced development of a "TTA2" format has passed with no known updates since 2010.<ref>[https://web.archive.org/web/20100727022032/http://en.true-audio.com:80/TTA_Lossless_Audio_Codec_-_Format_Description Format description], archived 2010-07-27</ref>		The project itself might be abandoned, but a 3rd party source code rewrite appeared in 2023<ref>[https://github.com/stseelig/libttaR Github home of the 3rd party rewrite]</ref><ref>[https://hydrogenaud.io/index.php/topic,125048.0.html Hydrogenaudio forum post (2023) on codec rewrite]</ref><ref>[https://hydrogenaud.io/index.php/topic,125143.0.html Hydrogenaudio forum post (2023) on codec rewrite (library)] </ref>. The codec sometimes identifies itself as "TTA1", and an announced development of a "TTA2" format has passed with no known updates since 2010.<ref>[https://web.archive.org/web/20100727022032/http://en.true-audio.com:80/TTA_Lossless_Audio_Codec_-_Format_Description Format description], archived 2010-07-27</ref>

	TTA has a couple of unique properties: ~~one is~~ encryption with password protection, and that the encoded audio bitstream is uniquely determined by the signal (and if applicable, the password) – not counting the metadata. That is, ''one single setting'' with no encoding options for heavier / lighter compression / CPU load. This property, that "to each audio signal there is a unique TTA encode" has seen some appeal in certain applications, outside which TTA seems to have a limited userbase.		TTA has a couple of unique properties: encryption with password protection, and that the encoded audio bitstream is uniquely determined by the signal (and if applicable, the password) – not counting the metadata. That is, ''one single setting'' with no encoding options for heavier / lighter compression / CPU load. This property, that "to each audio signal there is a unique TTA encode" has seen some appeal in certain applications, outside which TTA seems to have a limited userbase.

	Performance-wise, TTA has been measured around [[WavPack]] between default and <code>-h</code> on CD audio signals<ref>[http://audiograaf.nl/downloads.html Martijn van Beurden's comprehensive lossless comparison, version 6, 2023]</ref> – putting it on what traditionally has been considered on the ''fast encoder'' side rather than the ''heavy compression'' ([[Monkey's Audio]]/[[OptimFROG]]) side. In the most recent edition of the comparison, two codecs ([[TAK]] and, narrowly, [[FLAC]] after its recent performance improvements) could beat TTA simultaneously on all three tested parameters (encoding speed, decoding speed and file size) on the average signal tested. The 3rd party reimplementation claims to be significantly faster<ref>[https://gist.github.com/stseelig/0b9afe795a547b5798587db996694f97 blog post by the author of the rewrite]</ref>, at the expense of some overflow checks, but does not provide executables.		Performance-wise, TTA has been measured around [[WavPack]] between default and <code>-h</code> on CD audio signals<ref>[http://audiograaf.nl/downloads.html Martijn van Beurden's comprehensive lossless comparison, version 6, 2023]</ref> – putting it on what traditionally has been considered on the ''fast encoder'' side rather than the ''heavy compression'' ([[Monkey's Audio]]/[[OptimFROG]]) side. In the most recent edition of the comparison, two codecs ([[TAK]] and, narrowly, [[FLAC]] after its recent performance improvements) could beat TTA simultaneously on all three tested parameters (encoding speed, decoding speed and file size) on the average signal tested. The 3rd party reimplementation claims to be significantly faster<ref>[https://gist.github.com/stseelig/0b9afe795a547b5798587db996694f97 blog post by the author of the rewrite]</ref>, at the expense of some overflow checks, but does not provide executables.

Porcuswiki: Updated info on Case's foo_input_tta (channel count) and the source code rewrite.

2025-12-19T10:44:39Z

Updated info on Case's foo_input_tta (channel count) and the source code rewrite.

Show changes

Porcuswiki: Update with the 2023 comparison, the independent rewrite, and higher precision in some of the text

2024-04-25T17:51:09Z

Update with the 2023 comparison, the independent rewrite, and higher precision in some of the text

Show changes

Porcuswiki: Updated to accommodate Case's component, slightly reorganized.

2023-09-21T21:50:13Z

Updated to accommodate Case's component, slightly reorganized.

← Older revision		Revision as of 21:50, 21 September 2023
Line 9:		Line 9:
	}}		}}

	'''The True Audio''' ('''TTA''') is a [[lossless]] audio [[codec]]. It is distributed as a free open-source (GPL/LGPL) encoder/decoder and library for several operating systems~~. The TTA project also includes~~ DirectShow filters and plugins for several audio players, including [[foobar2000]].		'''The True Audio''' ('''TTA''') is a [[lossless]] audio [[codec]]. It is distributed as a free open-source (GPL/LGPL) encoder/decoder and library for several operating systems, and with DirectShow filters and plugins for several audio players, including [[foobar2000]].

	It is not known whether the project is abandoned~~. ffmpeg has an encoder/decoder that remedies some of the reference encoder/decoder's shortcomings – others, like the lack of channel allocation mask, are limitations of the format~~. An announced development of a "TTA2" format has passed with no known updates since 2010.<ref>[https://web.archive.org/web/20100727022032/http://en.true-audio.com:80/TTA_Lossless_Audio_Codec_-_Format_Description Format description], archived 2010-07-27</ref>		It is not known whether the project is abandoned. An announced development of a "TTA2" format has passed with no known updates since 2010.<ref>[https://web.archive.org/web/20100727022032/http://en.true-audio.com:80/TTA_Lossless_Audio_Codec_-_Format_Description Format description], archived 2010-07-27</ref>

	TTA has a couple of unique properties: one is encryption with password protection, and also TTA chose (since around 2004) not to offer options to tune compression/CPU load; there is ''one'' setting. These properties have some appeal in certain applications, outside which TTA seems to have a fairly limited userbase. ffmpeg's TTA encoder also produces the very same files as the reference encoder does, up to the tags (and, certain signals are accepted only by one of the encoders), and ffmpeg supports the password functionality.		TTA has a couple of unique properties: one is encryption with password protection, and also TTA chose (since around 2004) not to offer options to tune compression/CPU load; there is ''one'' setting. These properties have some appeal in certain applications, outside which TTA seems to have a fairly limited userbase.

	Performance-wise, TTA has been measured around [[WavPack]] between default and -h on CD audio signals<ref>[http://audiograaf.nl/losslesstest Martijn van Beurden's comprehensive lossless comparison, version 5]</ref> – putting it on what traditionally has been considered on the ''fast encoder'' side rather than the ''heavy compression'' ([[Monkey's Audio]]/[[OptimFROG]]) side. One codec ([[TAK]]) could beat TTA simultaneously on both encoding speed, decoding speed and file size.		Performance-wise, TTA has been measured around [[WavPack]] between default and <tt>-h</tt> on CD audio signals<ref>[http://audiograaf.nl/losslesstest Martijn van Beurden's comprehensive lossless comparison, version 5]</ref> – putting it on what traditionally has been considered on the ''fast encoder'' side rather than the ''heavy compression'' ([[Monkey's Audio]]/[[OptimFROG]]) side. One codec ([[TAK]]) could beat TTA simultaneously on both encoding speed, decoding speed and file size.

			There is a third-party implementation through ffmpeg. ffmpeg's TTA encoder seems to produce the very same files as the reference encoder does, up to the tags – and, it also supports a higher channel count and accepts more input files than the official Windows encoder. Also the foobar2000 component at foobar2000.org implements more features than the official version. This wiki article aims at describing the features and limitations in the available end-user applications, rather than what the TTA ''format'' might accommodate (but nobody has implemented).


Line 24:		Line 26:
	* Seekable and streaming playback.		* Seekable and streaming playback.
	* High-resolution audio support: the format supports 24 bits per sample, at any WAVE sampling rate (integers up to 4 GiHz; although the encoders may stop short of the 4 GiHz mark – ffmpeg at 2 GiHz – this limitation is hardly relevant for audio).		* High-resolution audio support: the format supports 24 bits per sample, at any WAVE sampling rate (integers up to 4 GiHz; although the encoders may stop short of the 4 GiHz mark – ffmpeg at 2 GiHz – this limitation is hardly relevant for audio).
	* Multichannel support, however with limitations (see below). Currently the reference encoder supports up to six channels, ~~while~~ the ffmpeg implementation supports 16.		* Multichannel support, however with limitations (see below). Currently the reference encoder supports up to six channels, the ffmpeg implementation supports 16, and the unofficial foobar2000 component can handle 8.
	* Piping support.		* Piping support.
	* Tagging: APEv2 or ID3v1/2.		* Tagging: APEv2 or ID3v1/2.
Line 35:		Line 37:

	=== Limitations ===		=== Limitations ===
	The following list is in part based ~~the format properties as claimed on the official site, and in part~~ on currently (2023) available implementations – some as revealed by tests in the Hydrogenaudio forums. ~~As development~~		The following list is in part based on currently (2023) available implementations – some as revealed by tests in the Hydrogenaudio forums.
	* [https://hydrogenaud.io/index.php/topic,122094 Bad error handling in the available implementations.]<ref>[https://hydrogenaud.io/index.php/topic,122094 HA forum discussion (2022) on codecs' error handling]</ref> Errors will upon playback lead to full-volume static noise played back, at worst for the rest of the file. Only the most severe errors seem to be detected by the reference decoder. Testing reveals that ffmpeg can detect errors the reference decoder cannot, and might drop more defective frames, but ffmpeg might still play back static unmuted. The lack of (MD5) audio checksum is a more severe shortcoming when the capability to detect errors by other means is so limited; there seems to be no reliable way implemented to mass scan a collection for corrupted files, although the ''format'' ~~apparently provides~~ for it.		* [https://hydrogenaud.io/index.php/topic,122094 Bad error handling in the available implementations.]<ref>[https://hydrogenaud.io/index.php/topic,122094 HA forum discussion (2022) on codecs' error handling]</ref> Errors will upon playback lead to full-volume static noise played back, at worst for the rest of the file. Only the most severe errors seem to be detected by the reference decoder. Testing reveals that ffmpeg can detect errors the reference decoder cannot, and might drop more defective frames, but ffmpeg might still play back static unmuted. The lack of (MD5) audio checksum is a more severe shortcoming when the capability to detect errors by other means is so limited; there seems to be no reliable way implemented to mass scan a collection for corrupted files, although the ''format'' claims to provide for it.
	* The existing implementations have limitations for non-CDDA signals:		* The existing implementations have limitations for non-CDDA signals:
	** Bit depth: The format supports 8, 16 or 24 bit files ~~only (32 is not supported, neither integer nor float)~~ – and 8-bit signals are only supported in ffmpeg's implementation, not in the the reference encoder/decoder (nor the official [[foobar2000]] playback component). ~~An earlier incarnation of the format did support~~ floating-point ~~signals~~; that was apparently dropped circa 2004, and it is not known how to decode ~~those~~ files. <br/>Non-integer byte depths (say 20 valid bits in a 24-bit WAVE container) are not well supported. Testing with 20-bit WAVE files has provoked the reference encoder into either of the following three: rejecting the file altogether; producing undecodeable files; silently upconverting to 24 bits, losing any information that it was ever 20 bits (ffmpeg appears to ''always'' do this). In the latter case, TTA will not compress it well, as it is unable to make use of "wasted bits": other codecs can detect that bits 21 to 24 are zero and compress a 20-bit signal virtually without penalty. (See van Beurden's lossless comparison, section 2.3.)		** Bit depth: The format supports 8, 16 or 24 bit files – and 8-bit signals are only supported in ffmpeg's implementation, not in the the reference encoder/decoder (nor the official [[foobar2000]] playback component). Note, some old sources refer to 32-bit (floating-point) support; that was apparently dropped circa 2004, and it is not known how to decode such files, should they even exist. <br/>Non-integer byte depths (say 20 valid bits in a 24-bit WAVE container) are not well supported. Testing with 20-bit WAVE files has provoked the reference encoder into either of the following three: rejecting the file altogether; producing undecodeable files; silently upconverting to 24 bits, losing any information that it was ever 20 bits (ffmpeg appears to ''always'' do this). In the latter case, TTA will not compress it well, as it is unable to make use of "wasted bits": other codecs can detect that bits 21 to 24 are zero and compress a 20-bit signal virtually without penalty. (See van Beurden's lossless comparison, section 2.3.)
	** Limitations in multichannel support: Although the TTA ''format'' claims support for up to 65536 channels, no implementation seems to support more than 16 (ffmpeg), the reference implementation being capped at 6. ~~Furthermore~~, ~~there seems to be no rule (neither~~ [https://docs.microsoft.com/en-us/windows/win32/api/mmreg/ns-mmreg-waveformatextensible WAVEFORMATEXTENSIBLE] ~~nor elsewhere)~~ to interpret what channels are encoded. ~~A player cannot know whether~~ a ~~three-channel~~ TTA file is ~~supposed~~ to be 2.1 or 3.0, or a five-channel file a 5.0 or a 4.1. Also, in van Beurden's comparison, TTA fared worse on multichannel material than on stereo.		** Limitations in multichannel support: Although the TTA ''format'' claims support for up to 65536 channels, no implementation seems to support more than 16 (ffmpeg), the reference implementation being capped at 6. The foobar2000 component repository includes a component version that handles 8 channels (unlike the component provided by the TTA developers), and that component also honours the [https://docs.microsoft.com/en-us/windows/win32/api/mmreg/ns-mmreg-waveformatextensible WAVEFORMATEXTENSIBLE] tag to interpret what channels are encoded. This is an unofficial feature; the format itself offers no channel assignment (e.g., if a TTA file has three channels there is no rule to tell whether it is 2.1 or 3.0, and likewise there is no rule to tell whether a five-channel file a 5.0 or a 4.1). Also, in van Beurden's comparison, TTA fared worse on multichannel material than on stereo.
	** The reference encoder is picky about input ''files,'' only supporting some versions/generations of the WAVE format (no ~~AIFF~~) and requiring workarounds at 2 GiB input size. Also the reference implementation might truncate too large files. These issues can be circumvented by using ffmpeg instead.		** The reference encoder is picky about input ''files,'' only supporting some versions/generations of the WAVE format (and no other format than WAVE) and requiring workarounds at 2 GiB input size. Also the reference implementation might truncate too large files. These issues can be circumvented by using ffmpeg instead.
	* Metadata:		* Metadata:
	** TTA might be the lossless format most likely to suffer from tagging ambiguity. While there are other formats which can (like MP3) accommotate both ID3 and APEv2 tags, applications seem to have converged to APEv2 for other lossless formats which accept it, and both ffmpeg's TTA encoder and [[foobar2000]] will try to enforce APEv2 in TTA. However, a tagger like [https://en.wikipedia.org/wiki/MusicBrainz_Picard MusicBrainz Picard] will treat TTA files as MP3 files, defaulting to ID3v1&ID3v2.3 while ''ignoring'' any APEv2. Apparently [[Mp3tag]] will write ID3 to an ''untagged'' .tta file, but ignore ID3 when APEv2 is already present.		** TTA might be the lossless format most likely to suffer from tagging ambiguity. While there are other formats which can (like MP3) accommotate both ID3 and APEv2 tags, applications seem to have converged to APEv2 for other lossless formats which accept it, and both ffmpeg's TTA encoder and [[foobar2000]] will try to enforce APEv2 in TTA. However, a tagger like [https://en.wikipedia.org/wiki/MusicBrainz_Picard MusicBrainz Picard] will treat TTA files as MP3 files, defaulting to ID3v1&ID3v2.3 while ''ignoring'' any APEv2. Apparently [[Mp3tag]] will write ID3 to an ''untagged'' .tta file, but ignore ID3 when APEv2 is already present.
Line 46:		Line 48:
	** There is no provision for (R)IFF chunks; i.e. TTA cannot store nor recreate ''non-audio'' chunks of the original file. That means that one limitation of ffmpeg – that it drops RIFF chunks – is moot for TTA, which could not store them in any case.		** There is no provision for (R)IFF chunks; i.e. TTA cannot store nor recreate ''non-audio'' chunks of the original file. That means that one limitation of ffmpeg – that it drops RIFF chunks – is moot for TTA, which could not store them in any case.
	* Its unique feature – password protection – seems to be unsupported in ''players''.		* Its unique feature – password protection – seems to be unsupported in ''players''.
	* Just as the lack of options might be useful in specialized applications, other users will find it a limitation. However, one may argue that by 2023, performance differences are less of an issue even if there is no way to speed up neither encoding nor decoding (which takes even more ~~time~~ than encoding~~, a property nowadays only shared by Monkey's Audio~~).		* Just as the lack of options might be useful in specialized applications, other users will find it a limitation. However, one may argue that by 2023, performance differences are less of an issue even if there is no way to speed up neither encoding nor decoding (which takes even more CPU power than encoding).
	* Like most lossless formats, TTA has no functionality for hybrid lossless/lossy encoding. For TTA, there is also no way (for power users!) to hack a hybrid solution by way of [[LossyWAV]].		* Like most lossless formats, TTA has no functionality for hybrid lossless/lossy encoding. For TTA, there is also no way (for power users!) to hack a hybrid solution by way of [[LossyWAV]].

Line 52:		Line 54:

	==Using TTA==		==Using TTA==
	For several purposes, one might rather use ffmpeg than the reference encoder – at least for 16 bit signals.		For several purposes, one might rather use ffmpeg than the reference encoder – at least for 16 bit signals. For foobar2000 playback, the component at the foobar2000 website has more features than the TTA developers' decoding component.

	==Links==		==Links==
Line 59:		Line 61:
	* [http://tausoft.org/wiki/True_Audio_Codec_Overview TTA Lossless Audio Codec – Tau Projects:] Codec overview at the official site.		* [http://tausoft.org/wiki/True_Audio_Codec_Overview TTA Lossless Audio Codec – Tau Projects:] Codec overview at the official site.
	* {{wikipedia\|TTA (codec)}}		* {{wikipedia\|TTA (codec)}}
			* [https://www.foobar2000.org/components/view/foo_input_tta foobar2000 component at foobar2000.org]
	* [[Lossless_comparison\| HA Wiki's Lossless Codec Comparison]] originally by [[User:Rjamorim\|Rjamorim]]		* [[Lossless_comparison\| HA Wiki's Lossless Codec Comparison]] originally by [[User:Rjamorim\|Rjamorim]]

Porcuswiki: "More honest" than my previous rewrite - frankly, I suspect it should be relegated to a "legacy" format. Apart from that, I did hesitate due to some of the sources being my own "original research". Decided to use some of it.

2023-07-07T17:21:13Z

"More honest" than my previous rewrite - frankly, I suspect it should be relegated to a "legacy" format. Apart from that, I did hesitate due to some of the sources being my own "original research". Decided to use some of it.

Show changes

Porcuswiki: The categories at the bottom were hardly in use. Obsoleting them for "Codecs".

2022-01-27T19:31:27Z

The categories at the bottom were hardly in use. Obsoleting them for "Codecs".

← Older revision		Revision as of 19:31, 27 January 2022
Line 45:		Line 45:
	{{navbox audio codecs}}		{{navbox audio codecs}}

	[[Category:~~Audio codecs]]~~		[[Category:Codecs]]
	~~[[Category:Lossless audio codecs~~]]

Porcuswiki at 20:39, 9 January 2022

2022-01-09T20:39:50Z

← Older revision		Revision as of 20:39, 9 January 2022
Line 32:		Line 32:
	* The command-line encoder is picky about .wav files, not supporting all generations of the WAVE format; this can be circumvented by piping stdin to the encoder.		* The command-line encoder is picky about .wav files, not supporting all generations of the WAVE format; this can be circumvented by piping stdin to the encoder.
	* Input must be either 8, 16 or 24 bits. Unlike some other codecs, TTA is not able to make use of "wasted bits": other codecs can fit a 20-bit signal in a 24-bit container without penalty in compression size, but TTA appears unable to make use of the fact that the four least significant bits are zero. Thus certain (non-CD) signals might compress a bit worse than among other formats (see van Beurden's lossless comparison, section 2.3.)		* Input must be either 8, 16 or 24 bits. Unlike some other codecs, TTA is not able to make use of "wasted bits": other codecs can fit a 20-bit signal in a 24-bit container without penalty in compression size, but TTA appears unable to make use of the fact that the four least significant bits are zero. Thus certain (non-CD) signals might compress a bit worse than among other formats (see van Beurden's lossless comparison, section 2.3.)
	* No support for floating-point formats ~~and~~ no hybrid/lossy mode possible (for ~~those~~, use [[WavPack]] or [[OptimFrog]]).		* No support for floating-point formats (for that, use [[WavPack]] or [[OptimFrog]])
			* No no hybrid/lossy mode possible (for that, use [[WavPack]] or [[OptimFrog]]).

	Because TTA - like MP3 ~~and OptimFROG~~ - can accommodate both APE tags and ID3, tagging ambiguity could be an issue: one application might not read another's tags. Users might want to stick to one tag format. [[Mp3tag]] will write the same tagset to .tta files as to .mp3 files, possibly both ID3v1, ID3v2 and APE.		Because TTA - like MP3 - can accommodate both APE tags and ID3, tagging ambiguity could be an issue: one application might not read another's tags. Users might want to stick to one tag format. [[Mp3tag]] will write the same tagset to .tta files as to .mp3 files, possibly both ID3v1, ID3v2 and APE.

	==Links==		==Links==

Porcuswiki: General rewrite.

2022-01-09T20:37:42Z

General rewrite.

← Older revision		Revision as of 20:37, 9 January 2022
Line 1:		Line 1:
	{{~~infobox file format~~		{{Codec Infobox
	\| name = The True Audio		\| purpose =
	\| ~~icon~~ = [[File:TTA-logo.png]]		\| name = The True Audio
	\| ~~extension~~ = ~~{{code\|.tta}}~~		\| logo = [[File:TTA-logo.png]]
	~~\| mime = {{code\|audio/x-tta}}~~		\| type = lossless
	\| ~~developer~~ = Aleksander Djuric<br/>Pavel Zhilin<br/>Tamir Barak<br/>Noam Koenigstein<br/>Kazuki Oikawa		\| maintainer = Aleksander Djuric<br/>Pavel Zhilin<br/>Tamir Barak<br/>Noam Koenigstein<br/>Kazuki Oikawa
	\| released =		\| released = TTA 2.3 (Windows version, 2015-02)
	~~\| latest_release_version~~ = 3~~.4.1~~		\| website = [http://tausoft.org/wiki/True_Audio_Codec_Overview tausoft.org]
	~~\| latest_release_date = {{start date and age\|2007\|07\|26}}~~
	~~\| format_type = Lossless audio codec~~
	~~\| container_for =~~
	~~\| contained_by =~~
	~~\| extended_from =~~
	~~\| extended_to =~~
	~~\| free = Yes~~
	\| ~~url~~ = [http://tausoft.org/wiki/True_Audio_Codec_Overview tausoft.org]
	}}		}}
	'''The True Audio''' ('''TTA''') codec is a free, simple real-time [[lossless]] audio encoder/decoder, based on adaptive prognostic filters which has shown satisfactory results comparing to majority of modern analogs.

	The '''~~recommended encoder~~''' is [[TTA ~~Lossless Audio Codec\|tta-2~~.~~3 (2015~~-~~02-24)]]~~.		'''The True Audio''' ('''TTA''') is a [[lossless]] audio [[codec]]. It is distributed as a free open-source (GPL/LGPL) encoder/decoder and library for several operating systems. The TTA project also DirectShow filters and plugins for several audio players. A third-party encoder/decoder is available through ffmpeg.

	==TTA ~~compressor==~~		TTA has one feature which apparently is unique among lossless codecs available to end-users, namely encryption with password protection. Unlike most other codecs, TTA has chosen not to offer options to tune compression/CPU load; there is ''one'' setting. Performance-wise, it has been measured not far from the default to -hx [[WavPack]] settings on CD audio<ref>http://audiograaf.nl/downloads.html Martijn van Beurden's comprehensive lossless comparison, version 4</ref> - which in the trade-off between size, encoding speed and decoding speed, might be considered rather on the ''fast encoder'' side.
	TTA ~~performs [[lossless]]~~ compression ~~on multichannel 8~~, ~~16 and 24 bit data of~~ the [[~~WAV~~]] audio ~~files~~. ~~Being "~~lossless~~" means that no data~~/~~quality is lost~~ in the ~~compression~~ - ~~when uncompressed~~, ~~the data will~~ be ~~identical to the original. The compression ratios of TTA depend~~ on the type of music file being compressed, but the compression size will generally range between 30–70% of the original. TTA format supports both [[ID3]]v1 and [[ID3]]v2 information tags and also [[APEv2]].

	===Features===		== Features ==
	* Down to 30–60% [[~~lossless~~]] ~~audio data compression~~		For an end-user considering TTA as a an audio format, the following features are quite common among lossless codecs. Some competing formats are lacking certain of these features, and some are free from certain of the limitations listed. To compare TAK with other lossless codecs, see [[Lossless_comparison\| HA Wiki's Lossless Codec Comparison]].
	* Real-time encoding/decoding algorithm
	* Fast decoding and encoding
	* Multiplatform
	* Open source code and documentation
	* Hardware support

	~~==TTA project==~~		* Streaming support
	~~The TTA project provides~~:		* Error handling and
			* High-resolution audio support: up to 4 GHz sampling rate and 24 bits/channel
			* Multichannel support. Currently the reference encoder supports six channels, while the ffmpeg encoder supports 16. (However [https://docs.microsoft.com/en-us/windows/win32/api/mmreg/ns-mmreg-waveformatextensible WAVEFORMATEXTENSIBLE] is not supported.)
			* Piping support
			* Tagging: APEv2 or ID3
			* Embedded CUE sheets support
			* Can be used in the [[Matroska]] container
			* Password protection

	* Free and ~~simple data format~~		TTA has some software support through player plugins (and ffmpeg-based players). There is also certain limited hardware support, most notably through [[Rockbox]], and the TTA website lists a few other hardware players with TTA support.<ref>http://tausoft.org/wiki/True_Audio_Codec_Support</ref>
	* Plugins for the ~~most popular media~~ players
	* TTA ~~DirectShow filters~~
	* Tau Producer - GUI based compressor for Windows
	* Set of the C/~~C++ TTA development libraries~~

	==~~See also~~==		=== Limitations ===
	* [[~~Lossless_comparison\|Lossless Codec Comparison~~]]		* No support for RIFF chunks (i.e., TTA cannot store and recreate ''non-audio'' chunks of the original .wav files).
			* The command-line encoder is picky about .wav files, not supporting all generations of the WAVE format; this can be circumvented by piping stdin to the encoder.
			* Input must be either 8, 16 or 24 bits. Unlike some other codecs, TTA is not able to make use of "wasted bits": other codecs can fit a 20-bit signal in a 24-bit container without penalty in compression size, but TTA appears unable to make use of the fact that the four least significant bits are zero. Thus certain (non-CD) signals might compress a bit worse than among other formats (see van Beurden's lossless comparison, section 2.3.)
			* No support for floating-point formats and no hybrid/lossy mode possible (for those, use [[WavPack]] or [[OptimFrog]]).

	==~~External links~~==		Because TTA - like MP3 and OptimFROG - can accommodate both APE tags and ID3, tagging ambiguity could be an issue: one application might not read another's tags. Users might want to stick to one tag format. [[Mp3tag]] will write the same tagset to .tta files as to .mp3 files, possibly both ID3v1, ID3v2 and APE.

			==Links==
	* [http://tausoft.org/wiki/True_Audio_Codec_Overview TTA Lossless Audio Codec - Tau Projects]		* [http://tausoft.org/wiki/True_Audio_Codec_Overview TTA Lossless Audio Codec - Tau Projects]
	* {{wikipedia\|TTA (codec)}}		* {{wikipedia\|TTA (codec)}}
			* [[Lossless_comparison\| HA Wiki's Lossless Codec Comparison]] originally by [[User:Rjamorim\|Rjamorim]]
			<references/>

	{{navbox audio codecs}}		{{navbox audio codecs}}

Beardgoggles: Added navbox template.

2019-11-27T00:14:01Z

Added navbox template.

← Older revision		Revision as of 00:14, 27 November 2019
Line 46:		Line 46:
	* [http://tausoft.org/wiki/True_Audio_Codec_Overview TTA Lossless Audio Codec - Tau Projects]		* [http://tausoft.org/wiki/True_Audio_Codec_Overview TTA Lossless Audio Codec - Tau Projects]
	* {{wikipedia\|TTA (codec)}}		* {{wikipedia\|TTA (codec)}}

			{{navbox audio codecs}}

	[[Category:Audio codecs]]		[[Category:Audio codecs]]
	[[Category:Lossless audio codecs]]		[[Category:Lossless audio codecs]]

Beardgoggles: Updated infobox.

2019-11-10T15:57:31Z

Updated infobox.

← Older revision		Revision as of 15:57, 10 November 2019
Line 1:		Line 1:
	{{~~codec Infobox~~		{{infobox file format
	\| name = The True Audio		\| name = The True Audio
	\| ~~logo~~ = [[~~Image~~:TTA-logo.png~~\|Official TTA logo~~]]		\| icon = [[File:TTA-logo.png]]
	\| ~~maintainer~~ = Aleksander Djuric / Pavel Zhilin / Tamir Barak / Noam Koenigstein / Kazuki Oikawa		\| extension = {{code\|.tta}}
	\| ~~type~~ = Lossless		\| mime = {{code\|audio/x-tta}}
	\| ~~purpose~~ = ~~Codec~~		\| developer = Aleksander Djuric<br/>Pavel Zhilin<br/>Tamir Barak<br/>Noam Koenigstein<br/>Kazuki Oikawa
	\| ~~recommended_encoder~~ = ~~TTA Lossless Audio Codec~~		\| released =
	\| ~~recommended_text~~ = ~~tta-2.3 (2015-02-24)~~		\| latest_release_version = 3.4.1
	\| ~~website~~ = [http://tausoft.org/wiki/True_Audio_Codec_Overview tausoft.org]		\| latest_release_date = {{start date and age\|2007\|07\|26}}
			\| format_type = Lossless audio codec
			\| container_for =
			\| contained_by =
			\| extended_from =
			\| extended_to =
			\| free = Yes
			\| url = [http://tausoft.org/wiki/True_Audio_Codec_Overview tausoft.org]
	}}		}}
			'''The True Audio''' ('''TTA''') codec is a free, simple real-time [[lossless]] audio encoder/decoder, based on adaptive prognostic filters which has shown satisfactory results comparing to majority of modern analogs.

	~~'''~~The ~~True Audio~~''' ~~('''TTA~~'''~~) codec~~ is ~~a free, simple real-time~~ [[~~lossless~~]] ~~audio encoder/decoder, based on adaptive prognostic filters which has shown satisfactory results comparing to majority of modern analogs~~.		The '''recommended encoder''' is [[TTA Lossless Audio Codec\|tta-2.3 (2015-02-24)]].

	==TTA compressor==		==TTA compressor==