Originally Posted by ron13

no no no xD

You're completely off base. you mix everything ^^
More than 20 years ago, mkv did not exist, and yet other video containers already existed, such as avi, wmv, asf etc..

Just like them, mkv can encapsulate video, audio and subtitle streams. and you're going to tell me: why the mkv when others did the same job before?
well, quite simply because the AVC h264 codec also arrived almost the same year as the mkv, in 2002 or 2003.

It's all a question of technological advancement and industrial needs. It's all about that. the arrival of the H264 codec was hastened with the arrival of HD DVD, Bluray disc, and broadcast TV mainly.

The audio and video industry has taken a big step with this codec. and the mkv goes hand in hand with all that, and this mkv was a godsend, since it is open source. so no need to pay to use your code

and in the end, to answer you regarding WMP, why can't it read the mkv and its subtitles? because at the time well before 2000, WMP was all the rage with DivX Avis with embedded subtitles. We had the 700mb divx or dvdrip, and we looked no further, quite simply because we didn't know that the H264 was going to revolutionize everything. we made do with what we had.

and if you look now, I challenge you to find me more than 5 torrent trackers that only accept movies in avi format xD

Yeah, I still remember DivX was a breakthrough at 2003, 2004 with it's aided subtitles, then the appearance of blueray with it's big size, but I have no idea that DivX was providing with embedded subtitles, now we have a software which could operate many video and audio formats with it's outsider subtitles regardless subtitle format

Originally Posted by ron13

no no no xD

You're completely off base. you mix everything ^^
More than 20 years ago, mkv did not exist, and yet other video containers already existed, such as avi, wmv, asf etc..

Just like them, mkv can encapsulate video, audio and subtitle streams. and you're going to tell me: why the mkv when others did the same job before?
well, quite simply because the AVC h264 codec also arrived almost the same year as the mkv, in 2002 or 2003.

It's all a question of technological advancement and industrial needs. It's all about that. the arrival of the H264 codec was hastened with the arrival of HD DVD, Bluray disc, and broadcast TV mainly.

The audio and video industry has taken a big step with this codec. and the mkv goes hand in hand with all that, and this mkv was a godsend, since it is open source. so no need to pay to use your code

and in the end, to answer you regarding WMP, why can't it read the mkv and its subtitles? because at the time well before 2000, WMP was all the rage with DivX Avis with embedded subtitles. We had the 700mb divx or dvdrip, and we looked no further, quite simply because we didn't know that the H264 was going to revolutionize everything. we made do with what we had.

and if you look now, I challenge you to find me more than 5 torrent trackers that only accept movies in avi format xD

regarding challenge do you them General tracker or movie and HD-oriented

Hey @ron13

what`s audio format FLAC I got it from music library

FLAC (/flæk/; Free Lossless Audio Codec) is an audio coding format for lossless compression of digital audio, developed by the Xiph.Org Foundation, and is also the name of the free software project producing the FLAC tools, the reference software package that includes a codec implementation. Digital audio compressed by FLAC's algorithm can typically be reduced to between 50 and 70 percent of its original size and decompresses to an identical copy of the original audio data.

FLAC is an open format with royalty-free licensing and a reference implementation which is free software. FLAC has support for metadata tagging, album cover art, and fast seeking.

Development was started in 2000 by Josh Coalson. The bitstream format was frozen with the release of version 0.9 of the reference implementation on 31 March 2001. Version 1.0 was released on 20 July 2001.

On 29 January 2003, the Xiph.Org Foundation and the FLAC project announced the incorporation of FLAC under the Xiph.org banner. Xiph.org is home to other free compression formats such as Vorbis, Theora, Speex and Opus.

Version 1.3.0 was released on 26 May 2013, at which point development was moved to the Xiph.org git repository.

In 2019, FLAC was proposed as an IETF standard.[9]

FLAC is a lossless encoding of linear pulse-code modulation data.

A FLAC file consists of the magic number fLaC, metadata, and encoded audio.

The encoded audio is divided into frames, which consists of a header, a data block, and a CRC16 checksum. Each frame is encoded independent of each other. A frame header begins with a sync word, used to identify the beginning of a valid frame. The rest of the header contains the number of samples, position of the frame, channel assignment, and optionally the sample rate and bit depth. The data block contains the audio information.

Metadata in FLAC precedes the audio. Properties like the sample rate and the number of channels are always contained in the metadata. It may also contain other information, the album cover for example. FLAC uses Vorbis comments for textual metadata like track title and artist name.
Encoding and decoding

The FLAC encoding algorithm consists of multiple stages. In the first stage, the input audio is split into blocks. If the audio contains multiple channels, each channel is encoded separately as a subblock. The encoder then tries to find a good mathematical approximation of the block, either by fitting a simple polynomial, or through general linear predictive coding. A description of the approximation, which is only a few bytes in length, is then written. Finally, the difference between the approximation and the input, called residual, is encoded using Rice coding. In many cases, a description of the approximation and the encoded residual takes up less space than using pulse-code modulation.

The decoding process is the reverse of encoding. The compressed residual is first decoded. The description of the mathematical approximation is then used to calculate a waveform. The result is formed by adding the residual and the calculated waveform. As FLAC compresses losslessly, the decoded waveform is identical to the waveform before encoding.

For two-channel stereo, the encoder may choose to joint-encode the audio. The channels are transformed into a side channel, which is the difference between the two input channels, and a mid channel, the sum of the two input channels. In place of a mid channel, the left channel or the right channel may be encoded instead, which is sometimes more space-efficient.

Even though the reference encoder uses a single block size for the whole stream, FLAC allows the block size in samples to vary per block.
Compression

The amount of compression is determined by various parameters, including the order of the linear prediction model and the block size. Regardless of the amount of compression, the original data can always be reconstructed perfectly.

For user's convenience, the reference implementation defines 9 compression levels, which are presets of the more technical parameters to the encoding algorithm. The levels are labeled from 0 to 8, with higher numbers resulting in a higher compression ratio, at the cost of compression speed. The meaning of each compression level varies by implementation.

FLAC is optimized for decoding speed at the expense of encoding speed. A benchmark has shown that, while there is little variation in decoding speed as compression level increases, beyond the default compression level 5, the encoding process takes up considerably more time with little space saved compared to level 5.

Alongside the format, the FLAC project also contains a free and open-source reference implementation of FLAC called libFLAC. libFLAC contains facilities to encode and decode FLAC data and to manipulate the metadata of FLAC files. libFLAC++, an object-oriented wrapper around libFLAC for C++, and the command-line programs flac and metaflac, are also part of the reference implementation.

The FLAC format, along with libFLAC, are not known to be covered by any patents, and anyone is free to write their own implementations of FLAC.
Comparison to other formats

FLAC is specifically designed for efficient packing of audio data, unlike general-purpose lossless algorithms such as DEFLATE, which are used in ZIP and gzip. While ZIP may reduce the size of a CD-quality audio file by 10–20%, FLAC is able to reduce the size of audio data by 40–50% by taking advantage of the characteristics of audio.

The technical strengths of FLAC compared to other lossless formats lie in its ability to be streamed and decoded quickly, independent of compression level.

Since FLAC is a lossless scheme, it is suitable as an archive format for owners of CDs and other media who wish to preserve their audio collections. If the original media are lost, damaged, or worn out, a FLAC copy of the audio tracks ensures that an exact duplicate of the original data can be recovered at any time. An exact restoration from a lossy copy (e.g., MP3) of the same data is impossible. FLAC's being lossless means it is highly suitable for transcoding e.g. to MP3, without the normally associated transcoding quality loss between one lossy format and another. A CUE file can optionally be created when ripping a CD. If a CD is read and ripped perfectly to FLAC files, the CUE file allows later burning of an audio CD that is identical in audio data to the original CD, including track order and pregap, but excluding CD-Text and other additional data such as lyrics and CD+G graphics.
Adoption and implementations

The reference implementation of FLAC is implemented as the libFLAC core encoder & decoder library, with the main distributable program flac being the reference implementation of the libFLAC API. This codec API is also available in C++ as libFLAC++. The reference implementation of FLAC compiles on many platforms, including most Unix (such as Solaris, BSD) and Unix-like (including Linux), Microsoft Windows, BeOS, and OS/2 operating systems. There are build-systems for autoconf/automake, MSVC, Watcom C, and Xcode. There is currently no multicore support in libFLAC, but utilities such as GNU parallel and various graphical frontends can be used to spin up multiple instances of the encoder.

FLAC playback support in portable audio devices and dedicated audio systems is limited compared to formats such as MP3 or uncompressed PCM. FLAC support is included by default in Windows 10, Android, BlackBerry 10 and Jolla devices.

In 2014, several aftermarket mobile electronics companies introduced multimedia solutions that include support for FLAC. These include the NEX series from Pioneer Electronics and the VX404 and NX404 from Clarion.

The European Broadcasting Union (EBU) has adopted the FLAC format for the distribution of high quality audio over its Euroradio network. The Windows operating system has supported native FLAC integration since the introduction of Windows 10. The Android operating system has supported native FLAC playback since version 3.1. macOS High Sierra and iOS 11 add native FLAC playback support.

Among others the Pono music player and streaming service used the FLAC format. Bandcamp insists on a lossless format for uploading, and has FLAC as a download option. The Wikimedia Foundation sponsored a free and open-source online ECMAScript FLAC tool for browsers supporting the required HTML5 features.

Originally Posted by ron13

FLAC (/flæk/; Free Lossless Audio Codec) is an audio coding format for lossless compression of digital audio, developed by the Xiph.Org Foundation, and is also the name of the free software project producing the FLAC tools, the reference software package that includes a codec implementation. Digital audio compressed by FLAC's algorithm can typically be reduced to between 50 and 70 percent of its original size and decompresses to an identical copy of the original audio data.

FLAC is an open format with royalty-free licensing and a reference implementation which is free software. FLAC has support for metadata tagging, album cover art, and fast seeking.

Development was started in 2000 by Josh Coalson. The bitstream format was frozen with the release of version 0.9 of the reference implementation on 31 March 2001. Version 1.0 was released on 20 July 2001.

On 29 January 2003, the Xiph.Org Foundation and the FLAC project announced the incorporation of FLAC under the Xiph.org banner. Xiph.org is home to other free compression formats such as Vorbis, Theora, Speex and Opus.

Version 1.3.0 was released on 26 May 2013, at which point development was moved to the Xiph.org git repository.

In 2019, FLAC was proposed as an IETF standard.[9]

FLAC is a lossless encoding of linear pulse-code modulation data.

A FLAC file consists of the magic number fLaC, metadata, and encoded audio.

The encoded audio is divided into frames, which consists of a header, a data block, and a CRC16 checksum. Each frame is encoded independent of each other. A frame header begins with a sync word, used to identify the beginning of a valid frame. The rest of the header contains the number of samples, position of the frame, channel assignment, and optionally the sample rate and bit depth. The data block contains the audio information.

Metadata in FLAC precedes the audio. Properties like the sample rate and the number of channels are always contained in the metadata. It may also contain other information, the album cover for example. FLAC uses Vorbis comments for textual metadata like track title and artist name.
Encoding and decoding

The FLAC encoding algorithm consists of multiple stages. In the first stage, the input audio is split into blocks. If the audio contains multiple channels, each channel is encoded separately as a subblock. The encoder then tries to find a good mathematical approximation of the block, either by fitting a simple polynomial, or through general linear predictive coding. A description of the approximation, which is only a few bytes in length, is then written. Finally, the difference between the approximation and the input, called residual, is encoded using Rice coding. In many cases, a description of the approximation and the encoded residual takes up less space than using pulse-code modulation.

The decoding process is the reverse of encoding. The compressed residual is first decoded. The description of the mathematical approximation is then used to calculate a waveform. The result is formed by adding the residual and the calculated waveform. As FLAC compresses losslessly, the decoded waveform is identical to the waveform before encoding.

For two-channel stereo, the encoder may choose to joint-encode the audio. The channels are transformed into a side channel, which is the difference between the two input channels, and a mid channel, the sum of the two input channels. In place of a mid channel, the left channel or the right channel may be encoded instead, which is sometimes more space-efficient.

Even though the reference encoder uses a single block size for the whole stream, FLAC allows the block size in samples to vary per block.
Compression

The amount of compression is determined by various parameters, including the order of the linear prediction model and the block size. Regardless of the amount of compression, the original data can always be reconstructed perfectly.

For user's convenience, the reference implementation defines 9 compression levels, which are presets of the more technical parameters to the encoding algorithm. The levels are labeled from 0 to 8, with higher numbers resulting in a higher compression ratio, at the cost of compression speed. The meaning of each compression level varies by implementation.

FLAC is optimized for decoding speed at the expense of encoding speed. A benchmark has shown that, while there is little variation in decoding speed as compression level increases, beyond the default compression level 5, the encoding process takes up considerably more time with little space saved compared to level 5.

Alongside the format, the FLAC project also contains a free and open-source reference implementation of FLAC called libFLAC. libFLAC contains facilities to encode and decode FLAC data and to manipulate the metadata of FLAC files. libFLAC++, an object-oriented wrapper around libFLAC for C++, and the command-line programs flac and metaflac, are also part of the reference implementation.

The FLAC format, along with libFLAC, are not known to be covered by any patents, and anyone is free to write their own implementations of FLAC.
Comparison to other formats

FLAC is specifically designed for efficient packing of audio data, unlike general-purpose lossless algorithms such as DEFLATE, which are used in ZIP and gzip. While ZIP may reduce the size of a CD-quality audio file by 10–20%, FLAC is able to reduce the size of audio data by 40–50% by taking advantage of the characteristics of audio.

The technical strengths of FLAC compared to other lossless formats lie in its ability to be streamed and decoded quickly, independent of compression level.

Since FLAC is a lossless scheme, it is suitable as an archive format for owners of CDs and other media who wish to preserve their audio collections. If the original media are lost, damaged, or worn out, a FLAC copy of the audio tracks ensures that an exact duplicate of the original data can be recovered at any time. An exact restoration from a lossy copy (e.g., MP3) of the same data is impossible. FLAC's being lossless means it is highly suitable for transcoding e.g. to MP3, without the normally associated transcoding quality loss between one lossy format and another. A CUE file can optionally be created when ripping a CD. If a CD is read and ripped perfectly to FLAC files, the CUE file allows later burning of an audio CD that is identical in audio data to the original CD, including track order and pregap, but excluding CD-Text and other additional data such as lyrics and CD+G graphics.
Adoption and implementations

The reference implementation of FLAC is implemented as the libFLAC core encoder & decoder library, with the main distributable program flac being the reference implementation of the libFLAC API. This codec API is also available in C++ as libFLAC++. The reference implementation of FLAC compiles on many platforms, including most Unix (such as Solaris, BSD) and Unix-like (including Linux), Microsoft Windows, BeOS, and OS/2 operating systems. There are build-systems for autoconf/automake, MSVC, Watcom C, and Xcode. There is currently no multicore support in libFLAC, but utilities such as GNU parallel and various graphical frontends can be used to spin up multiple instances of the encoder.

FLAC playback support in portable audio devices and dedicated audio systems is limited compared to formats such as MP3 or uncompressed PCM. FLAC support is included by default in Windows 10, Android, BlackBerry 10 and Jolla devices.

In 2014, several aftermarket mobile electronics companies introduced multimedia solutions that include support for FLAC. These include the NEX series from Pioneer Electronics and the VX404 and NX404 from Clarion.

The European Broadcasting Union (EBU) has adopted the FLAC format for the distribution of high quality audio over its Euroradio network. The Windows operating system has supported native FLAC integration since the introduction of Windows 10. The Android operating system has supported native FLAC playback since version 3.1. macOS High Sierra and iOS 11 add native FLAC playback support.

Among others the Pono music player and streaming service used the FLAC format. Bandcamp insists on a lossless format for uploading, and has FLAC as a download option. The Wikimedia Foundation sponsored a free and open-source online ECMAScript FLAC tool for browsers supporting the required HTML5 features.

good FLAC wiki copy paste