PiRho Knowledgebase - User contributions [en-gb]

FFmpeg - Encode VP8

2025-03-06T15:58:37Z

Knowledgebaseadmin: Created page with "In addition to the "default" VBR mode, there's a constant quality mode (like in the x264 encoder) that will ensure that every frame gets the number of bits it deserves to achieve a certain quality level, rather than forcing the stream to have an average bit rate. This results in better overall quality and should be your method of choice when you encode video with libvpx. In this case, the target bitrate becomes the maximum allowed bitrate. You enable the constant quality..."

In addition to the "default" VBR mode, there's a constant quality mode (like in the x264 encoder) that will ensure that every frame gets the number of bits it deserves to achieve a certain quality level, rather than forcing the stream to have an average bit rate. This results in better overall quality and should be your method of choice when you encode video with libvpx. In this case, the target bitrate becomes the maximum allowed bitrate. You enable the constant quality mode with the CRF parameter:<br/>
<pre>
ffmpeg -i <input.file> -c:v libvpx -crf 8 -b:v 0 <output.file>
</pre>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/VP8 FFmpeg: VP8]]<br/>
Reference: [[https://superuser.com/questions/1280255/vp8-single-pass-conversion-with-good-quality-in-ffmpeg superuser: VP8 single pass conversion with good quality in ffmpeg]]

Main Page

2025-03-06T15:49:52Z

Knowledgebaseadmin: /* Audio Codecs */

FFmpeg - Encode Opus

2025-03-06T15:49:25Z

Knowledgebaseadmin:

[[Category:FFmpeg]]
[[Category:Opus]]
<pre>
ffmpeg -i <input.file> -c:a libopus -b:a 128 <output.file>
</pre>
Opus at 128 KB/s (VBR) is pretty much transparent<br/>

Reference: [[https://wiki.xiph.org/Opus_Recommended_Settings#:~:text=Opus%20at%20128%20KB/s,VBR)%20is%20pretty%20much%20transparent. xiph.org: Opus Recommended Settings]]<br/>
Further Reading: [[https://trac.ffmpeg.org/wiki/Encode/HighQualityAudio FFmpeg: Guidelines for high quality lossy audio encoding]]

Main Page

2025-03-06T15:46:10Z

Knowledgebaseadmin: /* Audio Codecs */

Main Page

2025-03-06T15:45:48Z

Knowledgebaseadmin: /* Video Codecs */

Main Page

2025-03-06T15:44:32Z

Knowledgebaseadmin: /* Software */

Main Page

2025-03-06T15:43:49Z

Knowledgebaseadmin: /* Audio Codecs */

Main Page

2025-03-06T15:42:58Z

Knowledgebaseadmin: /* Software */

Main Page

2025-03-06T15:40:48Z

Knowledgebaseadmin: /* Audio Codecs */

Internet Explorer - CSS support in Internet Explorer 3

2025-03-06T15:32:10Z

Knowledgebaseadmin:

[[Category:Internet Explorer]]
[[Category:CSS]]
[[Category:Internet Explorer 3]]
While MSIE3 can claim support for CSS, there are bugs and limitations. Below you will find prioritized lists of missing functionality and bugs. Braden N. McDaniel has also published his list of holes.<br/>
<br/>
Missing functionality<br/>
<br/>
* em values (i.e. length units relative to a font size) are not supported. This is important in order to write style sheets that scale from one resolution to another.
* There is no documented way for users to supply their personal style sheets.
* 'margin' (the compound property) and 'margin-bottom' are not supported
* the 'padding' properties are not supported
* the 'border' properties are not supported
* pseudo-elements are not supported (but pseudo-classes are!)
<br/>
Bugs<br/>
<br/>
* The formatting model as implemented in beta 1 diverges from the specification. E.g., the left margins of the BODY and P elements do not add up (example).
* Margins do not collapse as described in the specification. Take a look at the Style Sheets resource page which has a style sheet attached. In order for all lists to be aligned, they are all within an explicit P element. In the case where the P element only has children elements (i.e. UL and LI), the margins belonging to the P element should be collapsed (i.e. take the maximum of) with 'margin-bottom' of the above element (H2) and 'margin-top' of the child element (UL). Since this is not the case (all margins seem to be added), the space between the H2 and the UL element becomes too large.
* 'font-family' declarations must be placed at the end of blocks; they seem to hide trailing declarations (example)
* You cannot set styles on implied tags. For example, if you don't include the BODY tag in your documents, style attached to the BODY element will not have any effect
* Line spacing (as shown in this example) is also added to the last line of a formatted element -- that's why there is so much space around the headlines. Spacing should only be added between lines.
vertical spacing sometimes act weird after lists. Consider the space between the end of the list and the horizontal rule in this example
* inline elements do not inherit the background of their parents correctly. Consider this example where the SPAN element inside the H1 takes the background of BODY, not H1.
* lines with links in them sometimes get extra space above them<br/>
Reference: [[https://www.w3.org/Style/CSS/msie/ CSS support in MS IE 3.0]]<br/>
Further Reading: [[http://endoframe.com/css/ie3.html Endoframe: Support for Cascading Style Sheets, Level 1 in Microsoft Internet Explorer 3.0, Win32 version]]

Internet Explorer - CSS support in Internet Explorer 3

2025-03-06T15:31:53Z

Knowledgebaseadmin:

[[Category:Internet Explorer]]
[[Category:CSS]]
[[Category:Internet Explorer 3]]
While MSIE3 can claim support for CSS, there are bugs and limitations. Below you will find prioritized lists of missing functionality and bugs. Braden N. McDaniel has also published his list of holes.<br/>
<br/>
Missing functionality<br/>
<br/>
* em values (i.e. length units relative to a font size) are not supported. This is important in order to write style sheets that scale from one resolution to another.
* There is no documented way for users to supply their personal style sheets.
* 'margin' (the compound property) and 'margin-bottom' are not supported
* the 'padding' properties are not supported
* the 'border' properties are not supported
* pseudo-elements are not supported (but pseudo-classes are!)
<br/>
Bugs<br/>
<br/>
* The formatting model as implemented in beta 1 diverges from the specification. E.g., the left margins of the BODY and P elements do not add up (example).
* Margins do not collapse as described in the specification. Take a look at the Style Sheets resource page which has a style sheet attached. In order for all lists to be aligned, they are all within an explicit P element. In the case where the P element only has children elements (i.e. UL and LI), the margins belonging to the P element should be collapsed (i.e. take the maximum of) with 'margin-bottom' of the above element (H2) and 'margin-top' of the child element (UL). Since this is not the case (all margins seem to be added), the space between the H2 and the UL element becomes too large.
* 'font-family' declarations must be placed at the end of blocks; they seem to hide trailing declarations (example)
* You cannot set styles on implied tags. For example, if you don't include the BODY tag in your documents, style attached to the BODY element will not have any effect
* Line spacing (as shown in this example) is also added to the last line of a formatted element -- that's why there is so much space around the headlines. Spacing should only be added between lines.
vertical spacing sometimes act weird after lists. Consider the space between the end of the list and the horizontal rule in this example
* inline elements do not inherit the background of their parents correctly. Consider this example where the SPAN element inside the H1 takes the background of BODY, not H1.
* lines with links in them sometimes get extra space above them<br/>
Reference: [[https://www.w3.org/Style/CSS/msie/ CSS support in MS IE 3.0]]
Further Reading: [[http://endoframe.com/css/ie3.html Endoframe: Support for Cascading Style Sheets, Level 1 in Microsoft Internet Explorer 3.0, Win32 version]]

Certbot - Install Certificate in Nginx

2025-03-06T15:23:26Z

Knowledgebaseadmin:

[[Category:certbot]]
[[Category:Nginx]]
<pre>
sudo certbot --nginx
</pre>
Reference: [[https://certbot.eff.org/instructions?ws=nginx&os=snap certbot: Certbot Instructions]]

Certbot - Install Certificate in Nginx

2025-03-06T15:22:51Z

Knowledgebaseadmin: Created page with "Category:certbot Category:Nginx <pre> sudo certbot --nginx </pre>"

[[Category:certbot]]
[[Category:Nginx]]
<pre>
sudo certbot --nginx
</pre>

FFmpeg - Encode AAC

2025-03-06T15:17:46Z

Knowledgebaseadmin: Created page with "Category:FFmpeg Category:AAC <pre> ffmpeg -i <input.file> -c:a libfdk_aac -ac 2 -b:a 128k <output.file> </pre> These settings target a specific bit rate, with less variation between samples. It gives you greater control over file size, and it is compatible with the HE-AAC profile. As a rule of thumb, for audible transparency, use 64 kBit/s for each channel (so 128 kBit/s for stereo, 384 kBit/s for 5.1 surround sound).<br/> Set the bit rate with the <code>-b:a</co..."

[[Category:FFmpeg]]
[[Category:AAC]]
<pre>
ffmpeg -i <input.file> -c:a libfdk_aac -ac 2 -b:a 128k <output.file>
</pre>
These settings target a specific bit rate, with less variation between samples. It gives you greater control over file size, and it is compatible with the HE-AAC profile. As a rule of thumb, for audible transparency, use 64 kBit/s for each channel (so 128 kBit/s for stereo, 384 kBit/s for 5.1 surround sound).<br/>
Set the bit rate with the <code>-b:a</code> option.<br/>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/AAC FFmpeg: AAC]]

FFmpeg - Encode Opus

2025-03-06T15:01:06Z

Knowledgebaseadmin:

<pre>
ffmpeg -i <input.file> -c:a libopus -b:a 128 <output.file>
</pre>
Opus at 128 KB/s (VBR) is pretty much transparent<br/>

Reference: [[https://wiki.xiph.org/Opus_Recommended_Settings#:~:text=Opus%20at%20128%20KB/s,VBR)%20is%20pretty%20much%20transparent. xiph.org: Opus Recommended Settings]]<br/>
Further Reading: [[https://trac.ffmpeg.org/wiki/Encode/HighQualityAudio FFmpeg: Guidelines for high quality lossy audio encoding]]

FFmpeg - Encode Opus

2025-03-06T15:00:17Z

Knowledgebaseadmin: Created page with "<pre> ffmpeg -i <input.file> -c:a libopus -b:a 128 <output.file> </pre> Opus at 128 KB/s (VBR) is pretty much transparent<br/> Reference: https://wiki.xiph.org/Opus_Recommended_Settings#:~:text=Opus%20at%20128%20KB/s,VBR)%20is%20pretty%20much%20transparent. xiph.org: Opus Recommended Settings Further Reading: https://trac.ffmpeg.org/wiki/Encode/HighQualityAudio FFmpeg: Guidelines for high quality lossy audio encoding"

<pre>
ffmpeg -i <input.file> -c:a libopus -b:a 128 <output.file>
</pre>
Opus at 128 KB/s (VBR) is pretty much transparent<br/>

Reference: [[https://wiki.xiph.org/Opus_Recommended_Settings#:~:text=Opus%20at%20128%20KB/s,VBR)%20is%20pretty%20much%20transparent. xiph.org: Opus Recommended Settings]]
Further Reading: [[https://trac.ffmpeg.org/wiki/Encode/HighQualityAudio FFmpeg: Guidelines for high quality lossy audio encoding]]

FFmpeg - Encode Vorbis

2025-03-06T14:48:54Z

Knowledgebaseadmin:

[[Category:FFmpeg]]
[[Category:Vorbis]]
<pre>
ffmpeg -i <input.file> -a:c libvorbis -qscale:a 3 <output.file>
</pre>
"libvorbis" - Usable range ≥ 96 Kbps. Recommended range ≥ 192 Kbps.<br/>
-qscale:a – audio quality. Range is -1.0 to 10.0, where 10.0 is highest quality. Default is -q:a 3 with a target of 112kbps. The formula 16×(q+4) is used below 4, 32×q is used below 8, and 64×(q-4) otherwise. Examples: 112=16×(3+<b>4</b>), 160=32×<b>5</b>, 192=32×<b>6</b>, 384=64×(10-<b>4</b>).<br/>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/HighQualityAudio FFmpeg Guidelines for high quality lossy audio encoding]]<br/>
Reference: [[https://trac.ffmpeg.org/wiki/TheoraVorbisEncodingGuide FFmpeg: A Brief Theora and Vorbis Encoding Guide]]

FFmpeg - Encode Vorbis

2025-03-06T14:47:56Z

Knowledgebaseadmin: Created page with "Category:FFmpeg Category:Vorbis <pre> ffmpeg -i <input.file> -a:c libvorbis -qscale:a 3 <output.file> </pre> "libvorbis" - Usable range ≥ 96 Kbps. Recommended range ≥ 192 Kbps.<br/> -qscale:a – audio quality. Range is -1.0 to 10.0, where 10.0 is highest quality. Default is -q:a 3 with a target of 112kbps. The formula 16×(q+4) is used below 4, 32×q is used below 8, and 64×(q-4) otherwise. Examples: 112=16×(3+<b>4</b>), 160=32×<b>5</b>, 192=32×<b>6</..."

[[Category:FFmpeg]]
[[Category:Vorbis]]
<pre>
ffmpeg -i <input.file> -a:c libvorbis -qscale:a 3 <output.file>
</pre>
"libvorbis" - Usable range ≥ 96 Kbps. Recommended range ≥ 192 Kbps.<br/>
-qscale:a – audio quality. Range is -1.0 to 10.0, where 10.0 is highest quality. Default is -q:a 3 with a target of 112kbps. The formula 16×(q+4) is used below 4, 32×q is used below 8, and 64×(q-4) otherwise. Examples: 112=16×(3+<b>4</b>), 160=32×<b>5</b>, 192=32×<b>6</b>, 384=64×(10-<b>4</b>).<br/>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/HighQualityAudio FFmpeg Guidelines for high quality lossy audio encoding]]
Reference: [[https://trac.ffmpeg.org/wiki/TheoraVorbisEncodingGuide FFmpeg: A Brief Theora and Vorbis Encoding Guide]]

FFmpeg - Encode MP3

2025-03-06T14:34:36Z

Knowledgebaseadmin: Created page with "Category:FFmpeg Category:MP3 <pre> ffmpeg -i <input.file> -codec:a libmp3lame -qscale:a 2 <output.file> </pre> The transparency threshold for MP3 to linear PCM audio is said to be between 175 and 245 kbit/s, at 44.1 kHz, when encoded as VBR MP3…<br/> Reference: https://trac.ffmpeg.org/wiki/Encode/MP3 FFmpeg: FFmpeg MP3 Encoding Guide<br/> Reference: https://trac.ffmpeg.org/wiki/Encode/HighQualityAudio FFmpeg: Guidelines for high quality lossy audio encod..."

[[Category:FFmpeg]]
[[Category:MP3]]
<pre>
ffmpeg -i <input.file> -codec:a libmp3lame -qscale:a 2 <output.file>
</pre>

The transparency threshold for MP3 to linear PCM audio is said to be between 175 and 245 kbit/s, at 44.1 kHz, when encoded as VBR MP3…<br/>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/MP3 FFmpeg: FFmpeg MP3 Encoding Guide]]<br/>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/HighQualityAudio FFmpeg: Guidelines for high quality lossy audio encoding]]<br/>
Reference: [[https://en.wikipedia.org/wiki/Transparency_(data_compression)#:~:text=It%20is%20commonly%20used%20to,highly%20popular%20LAME%20MP3%20encoder). Wikipedia: Transparency (data compression)]]

FFmpeg - VP9

2025-03-06T14:19:20Z

Knowledgebaseadmin: Knowledgebaseadmin moved page FFmpeg - VP9 to FFmpeg - Encode VP9

#REDIRECT [[FFmpeg - Encode VP9]]

FFmpeg - Encode VP9

2025-03-06T14:19:20Z

Knowledgebaseadmin: Knowledgebaseadmin moved page FFmpeg - VP9 to FFmpeg - Encode VP9

[[Category:FFmpeg]]
[[Category:VP9]]
Two-pass is the recommended encoding method for libvpx-vp9 as some quality-enhancing encoder features are only available in 2-pass mode.<br/>
Constant quality 2-pass is invoked by setting <code>-b:v</code> to <code>zero</code> and specifying a quality level using the <code>-crf</code> switch:<br/>
<pre>
ffmpeg -i <input.file> -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 1 -an -f null /dev/null && \
ffmpeg -i <input.file> -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 2 -c:a libopus <output.file>
</pre>
Note: Windows users should use <code>NUL</code> instead of <code>/dev/null</code> and <code>^</code> instead of <code>\</code>.<br/>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/VP9 FFmpeg: FFmpeg and VP9 Encoding Guide]]

FFmpeg - Theora

2025-03-06T14:18:57Z

Knowledgebaseadmin: Knowledgebaseadmin moved page FFmpeg - Theora to FFmpeg - Encode Theora

#REDIRECT [[FFmpeg - Encode Theora]]

FFmpeg - Encode Theora

2025-03-06T14:18:57Z

Knowledgebaseadmin: Knowledgebaseadmin moved page FFmpeg - Theora to FFmpeg - Encode Theora

[[Category:FFmpeg]]
[[Category:Theora]]
<pre>
ffmpeg -i <input.file> -c:v libtheora -qscale:v 10 <output.file>
</pre>
Reference: [[https://trac.ffmpeg.org/wiki/TheoraVorbisEncodingGuide FFmpeg: A Brief Theora and Vorbis Encoding Guide]]

FFmpeg - AVC

2025-03-06T14:18:31Z

Knowledgebaseadmin: Knowledgebaseadmin moved page FFmpeg - AVC to FFmpeg - Encode AVC

#REDIRECT [[FFmpeg - Encode AVC]]

FFmpeg - Encode AVC

2025-03-06T14:18:31Z

Knowledgebaseadmin: Knowledgebaseadmin moved page FFmpeg - AVC to FFmpeg - Encode AVC

[[Category:FFmpeg]]
[[Category:AVC]]
Use this rate control mode if you want to keep the best quality and care less about the file size. This is the recommended rate control mode for most uses.<br/>
This method allows the encoder to attempt to achieve a certain output quality for the whole file when output file size is of less importance. The downside is that you can't tell it to get a specific filesize or not go over a specific size or bitrate, which means that this method is not recommended for encoding videos for streaming.<br/>
The range of the CRF scale is 0–51, where 0 is lossless. Consider 17 or 18 to be visually lossless or nearly so; it should look the same or nearly the same as the input but it isn't technically lossless.<br/>
A preset is a collection of options that will provide a certain encoding speed to compression ratio. A slower preset will provide better compression (compression is quality per filesize).<br/>
<pre>
ffmpeg -i <input.file> -c:v libx264 -crf 23 -preset veryslow <output.file>
</pre>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/H.264 FFmpeg: H.264 Video Encoding Guide]]

FFmpeg - Encode Theora

2025-03-06T13:51:09Z

Knowledgebaseadmin:

FFmpeg - Encode Theora

2025-03-06T13:50:43Z

Knowledgebaseadmin: Created page with "<pre> ffmpeg -i <input.file> -c:v libtheora -qscale:v 10 <output.file> </pre> Reference: https://trac.ffmpeg.org/wiki/TheoraVorbisEncodingGuide FFmpeg: A Brief Theora and Vorbis Encoding Guide"

<pre>
ffmpeg -i <input.file> -c:v libtheora -qscale:v 10 <output.file>
</pre>
Reference: [[https://trac.ffmpeg.org/wiki/TheoraVorbisEncodingGuide FFmpeg: A Brief Theora and Vorbis Encoding Guide]]

FFmpeg - Encode AVC

2025-03-06T13:44:47Z

Knowledgebaseadmin:

FFmpeg - Encode AVC

2025-03-06T13:44:18Z

Knowledgebaseadmin: Created page with "Use this rate control mode if you want to keep the best quality and care less about the file size. This is the recommended rate control mode for most uses.<br/> This method allows the encoder to attempt to achieve a certain output quality for the whole file when output file size is of less importance. The downside is that you can't tell it to get a specific filesize or not go over a specific size or bitrate, which means that this method is not recommended for encoding vi..."

Use this rate control mode if you want to keep the best quality and care less about the file size. This is the recommended rate control mode for most uses.<br/>
This method allows the encoder to attempt to achieve a certain output quality for the whole file when output file size is of less importance. The downside is that you can't tell it to get a specific filesize or not go over a specific size or bitrate, which means that this method is not recommended for encoding videos for streaming.<br/>
The range of the CRF scale is 0–51, where 0 is lossless. Consider 17 or 18 to be visually lossless or nearly so; it should look the same or nearly the same as the input but it isn't technically lossless.<br/>
A preset is a collection of options that will provide a certain encoding speed to compression ratio. A slower preset will provide better compression (compression is quality per filesize).<br/>
<pre>
ffmpeg -i <input.file> -c:v libx264 -crf 23 -preset veryslow <output.file>
</pre>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/H.264 FFmpeg: H.264 Video Encoding Guide]]

FFmpeg - Encode VP9

2025-03-06T13:36:55Z

Knowledgebaseadmin:

FFmpeg - Encode VP9

2025-03-06T13:36:37Z

Knowledgebaseadmin: Created page with "Category:FFmpeg Category:VP9 Two-pass is the recommended encoding method for libvpx-vp9 as some quality-enhancing encoder features are only available in 2-pass mode.<br/> Constant quality 2-pass is invoked by setting <code>-b:v</code> to <code>zero</code> and specifying a quality level using the <code>-crf</code> switch:<br/> <pre> ffmpeg -i <input.file> -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 1 -an -f null /dev/null && \ ffmpeg -i <input.file> -c:v libvpx-vp9 -b:v..."

[[Category:FFmpeg]]
[[Category:VP9]]
Two-pass is the recommended encoding method for libvpx-vp9 as some quality-enhancing encoder features are only available in 2-pass mode.<br/>
Constant quality 2-pass is invoked by setting <code>-b:v</code> to <code>zero</code> and specifying a quality level using the <code>-crf</code> switch:<br/>
<pre>
ffmpeg -i <input.file> -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 1 -an -f null /dev/null && \
ffmpeg -i <input.file> -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 2 -c:a libopus <output.file>
</pre>
Note: Windows users should use <code>NUL</code> instead of <code>/dev/null</code> and <code>^</code> instead of <code>\</code>.
Reference: [[https://trac.ffmpeg.org/wiki/Encode/VP9 FFmpeg: FFmpeg and VP9 Encoding Guide]]

FFmpeg - MP4 Faststart

2025-03-06T13:29:28Z

Knowledgebaseadmin:

[[Category:FFmpeg]]
[[Category:MP4]]
[[Category:MOV]]
Normally, a MOV/MP4 file has all the metadata about all packets stored in one location. This data is usually written at the end of the file, but it can be moved to the start for better playback by adding <code>+faststart</code> to the <code>-movflags</code>…<br/>
<pre>
ffmpeg -i <input.file> -c copy -f mp4 -movflags +faststart <output.file>
</pre>
Depending on the size of your input it can take a few more seconds usually to perform the second pass to move the <code>moov</code> atom to the beginning of the file.<br/>
This will… allow the video to begin playing before it is completely downloaded by the viewer.<br/>
Reference: [[https://ffmpeg.org/ffmpeg-formats.html#Fragmentation FFmpeg: FFmpeg Formats Documentation]]<br/>
Reference: [[https://superuser.com/questions/856025/any-downsides-to-always-using-the-movflags-faststart-parameter superuser: Any downsides to always using the -movflags faststart parameter?]]<br/>
Reference: [[https://trac.ffmpeg.org/wiki/Encode/H.264 FFmpeg: H.264 Video Encoding Guide]]

Main Page

2025-03-06T13:28:24Z

Knowledgebaseadmin:

FFmpeg - MP4 Faststart

2025-03-06T13:26:40Z

Knowledgebaseadmin:

[[Category:FFmpeg]]
[[Category:MP4]]
[[Category:MOV]]
Normally, a MOV/MP4 file has all the metadata about all packets stored in one location. This data is usually written at the end of the file, but it can be moved to the start for better playback by adding <code>+faststart</code> to the <code>-movflags</code>…<br/>
<pre>
ffmpeg -i <input.file> -c copy -f mp4 -movflags +faststart <output.file>
</pre>
Depending on the size of your input it can take a few more seconds usually to perform the second pass to move the <code>moov</code> atom to the beginning of the file.<br/>
This will… allow the video to begin playing before it is completely downloaded by the viewer.<br/>
Reference: [[https://ffmpeg.org/ffmpeg-formats.html#Fragmentation FFmpeg: FFmpeg Formats Documentation]]<br/>
Reference: [[https://superuser.com/questions/856025/any-downsides-to-always-using-the-movflags-faststart-parameter superuser: Any downsides to always using the -movflags faststart parameter?]]
Reference: [[https://trac.ffmpeg.org/wiki/Encode/H.264 FFmpeg: H.264 Video Encoding Guide]]

FFmpeg - MP4 Faststart

2025-03-06T13:26:02Z

Knowledgebaseadmin:

Normally, a MOV/MP4 file has all the metadata about all packets stored in one location. This data is usually written at the end of the file, but it can be moved to the start for better playback by adding <code>+faststart</code> to the <code>-movflags</code>…<br/>
<pre>
ffmpeg -i <input.file> -c copy -f mp4 -movflags +faststart <output.file>
</pre>
Depending on the size of your input it can take a few more seconds usually to perform the second pass to move the <code>moov</code> atom to the beginning of the file.<br/>
This will… allow the video to begin playing before it is completely downloaded by the viewer.<br/>
Reference: [[https://ffmpeg.org/ffmpeg-formats.html#Fragmentation FFmpeg: FFmpeg Formats Documentation]]<br/>
Reference: [[https://superuser.com/questions/856025/any-downsides-to-always-using-the-movflags-faststart-parameter superuser: Any downsides to always using the -movflags faststart parameter?]]
Reference: [[https://trac.ffmpeg.org/wiki/Encode/H.264 FFmpeg: H.264 Video Encoding Guide]]

FFmpeg - MP4 Faststart

2025-03-06T13:17:19Z

Knowledgebaseadmin: Created page with "Normally, a MOV/MP4 file has all the metadata about all packets stored in one location. This data is usually written at the end of the file, but it can be moved to the start for better playback by adding <code>+faststart</code> to the <code>-movflags</code>…<br/> <pre> ffmpeg -i <input.file> -c copy -f mp4 -movflags +faststart <output.file> </pre> Reference: https://ffmpeg.org/ffmpeg-formats.html#Fragmentation FFmpeg: FFmpeg Formats Documentation"

Main Page

2025-03-06T13:06:20Z

Knowledgebaseadmin:

Main Page

2025-03-06T13:02:10Z

Knowledgebaseadmin:

Linux - Synchronise 2 Directories

2025-03-06T12:53:13Z

Knowledgebaseadmin:

[[Category:Linux]]
[[Category:rsync]]
<code>rsync -avu --delete "/home/user/A/" "/home/user/B"</code>
;-a
: archive mode; equals -rlptgoD (no -H, -A, -X)
;-v
: run verbosely
;-u
: only copy files with a newer modification time (or size difference if the times are equal)
;--delete
: delete the files in target folder that do not exist in the source
Reference: [https://unix.stackexchange.com/questions/203846/how-to-sync-two-folders-with-command-line-tools Stack Exchange: How to sync two folders with command line tools?]

Linux - a2enmod command not found

2025-03-06T12:52:55Z

Knowledgebaseadmin:

[[Category:Linux]]
[[Category:apache2]]
[[Category:a2enmod]]
On Debian a2enmod is located at /usr/sbin/a2enmod and sometimes /usr/sbin is not in your PATH.<br/>
Reference: [[https://stackoverflow.com/questions/50022485/a2enmod-command-not-found-in-apache-server-using-cpanel-in-linux-vps stackoverflow: a2enmod command not found in apache server using cpanel in linux vps]]

Kodi - Add-on: TVHeadEnd HTSP Client

2025-03-06T12:51:12Z

Knowledgebaseadmin:

[[Category:Kodi]]
[[Category:TVHeadEnd]]
The TVHeadEnd HTSP Client Add-on allows you to use TVHeadEnd as a Live TV and Radio source. It gives access to all channels (which the user has permission to), EPG and recordings.<br/>
<code>Settings > Add-ons > Install from repository > PVR clients > Tvheadend HTSP Client > Install</code><br/>
Reference: [[https://kodi.wiki/view/Add-on:Tvheadend_HTSP_Client Kodi: Add-on:Tvheadend HTSP Client]]

Kodi - Add-on: Emby for Kodi

2025-03-06T12:50:55Z

Knowledgebaseadmin:

[[Category:Kodi]]
[[Category:Emby]]
<pre>
Settings > File Manager > Add source
Enter the paths or browse for the media locations: http://kodi.emby.media/
Enter a name for this media source: Emby Repository
Settings > Add-ons > Install from zip file > kodi.emby.tv > repository.emby.kodi-1.0.8.zip
For security, installation of add-ons from unknown sources is disabled. > Settings
Unknown sources: Enabled
Add-ons will be given access to personal data stored on this device… > Yes
Settings > Add-ons > Install from repository > Kodi Emby Addons > Video add-ons > Emby for Kodi Next Gen (Video)
</pre>
Reference: [[https://emby.media/support/articles/Emby-for-Kodi.html Emby: Emby for Kodi]]

Internet Explorer - Text Shadow and Glow

2025-03-06T12:50:09Z

Knowledgebaseadmin:

[[Category:Internet Explorer]]
[[Category:DirectX Filter]]
The idea is that first we use Glow to create a halo around the text and then blur it with Blur. The resulting shadow is then placed under the text using absolute positioning. The result is acceptable but slightly rough especially if the shadow is moved relative to the text.<br/>
[[File:https://www.artlebedev.com/tools/technogrette/html/filters-in-ie/i/ie-shadow-1.png]]
<pre>
.shadowed .shadow-1
{
left: -7px;
top: -7px;
filter: progid:DXImageTransform.Microsoft.Glow(Color=#eeeeee,Strength=2)
progid:DXImageTransform.Microsoft.Blur(pixelradius=5, enabled='true');
-ms-filter: "progid:DXImageTransform.Microsoft.Glow(Color=#eeeeee,Strength=2)"
"progid:DXImageTransform.Microsoft.Blur(pixelradius=5, enabled='true')";
}

.shadowed .shadow-2
{
left:-5px;
top:-5px;
filter: progid:DXImageTransform.Microsoft.Glow(Color=#eeeeee,Strength=2)
progid:DXImageTransform.Microsoft.Blur(pixelradius=5, enabled='true');
-ms-filter: "progid:DXImageTransform.Microsoft.Glow(Color=#eeeeee,Strength=2)"
"progid:DXImageTransform.Microsoft.Blur(pixelradius=5, enabled='true')";
}
</pre>
Turns out, the Glow filter is at fault here. To make it nice, let’s turn its strength down to 1, change the color to black (the alternative is to replace Glow by dropShadow which has more understandable parameters) and add another filter, Alpha. Here is the result (Glow on the left, dropShadow on the right, the differences are negligible to the naked eye and can be brought down to zero with further tweaking):<br/>
[[File:https://www.artlebedev.com/tools/technogrette/html/filters-in-ie/i/ie-shadow-2.png]]
<pre>
.shadowed .shadow-3
{
filter: progid:DXImageTransform.Microsoft.Glow(Color=#000000,Strength=1.0)
progid:DXImageTransform.Microsoft.Alpha(opacity=25)
progid:DXImageTransform.Microsoft.Blur(pixelradius=1.75, enabled='true');
-ms-filter: "progid:DXImageTransform.Microsoft.Glow(Color=#000000,Strength=1.0)"
"progid:DXImageTransform.Microsoft.Alpha(opacity=25)"
"progid:DXImageTransform.Microsoft.Blur(pixelradius=1.75, enabled='true')";
color: #111111;
top: -2px;
left: -2px;
}

.shadowed .shadow-4
{
filter: progid:DXImageTransform.Microsoft.dropShadow(color=#000000,offX=1,offY=1)
progid:DXImageTransform.Microsoft.Alpha(opacity=25)
progid:DXImageTransform.Microsoft.Blur(pixelradius=2.15, enabled='true');
-ms-filter: "progid:DXImageTransform.Microsoft.dropShadow(color=#000000,offX=1,offY=1)"
"progid:DXImageTransform.Microsoft.Alpha(opacity=25)"
"progid:DXImageTransform.Microsoft.Blur(pixelradius=2.15, enabled='true')";
color: #111111;
top: -2px;
left: -2px;
}
</pre>
Reference: [[https://www.artlebedev.com/tools/technogrette/html/filters-in-ie/ Artlebedeb: Using filters in IE]]

Internet Explorer - Targeting Older Browsers in CSS

2025-03-06T12:49:12Z

Knowledgebaseadmin:

[[Category:Internet Explorer]]
[[Category:CSS]]
Reference: [[https://front-back.com/how-to-target-old-versions-of-internet-explorer-in-our-css-in-2013/ Front / Back: How to target old versions of Internet Explorer in our CSS in 2013]]

Internet Explorer - CSS support in Internet Explorer 3

2025-03-06T12:48:42Z

Knowledgebaseadmin:

Internet Explorer - Box Shadow

2025-03-06T12:48:10Z

Knowledgebaseadmin:

[[Category:Internet Explorer]]
[[Category:DirectX Filter]]
Reference [[https://www.useragentman.com/blog/2011/08/24/how-to-simulate-css3-box-shadow-in-ie7-8-without-javascript/ User Agent Man: How to Simulate CSS3 box-shadow in IE6-8 Without JavaScript.]]

FFmpeg - Scale and Latterbox

2025-03-06T12:41:17Z

Knowledgebaseadmin: Knowledgebaseadmin moved page FFmpeg - Scale and Latterbox to FFmpeg - Scale and Letterbox

#REDIRECT [[FFmpeg - Scale and Letterbox]]

FFmpeg - Scale and Letterbox

2025-03-06T12:41:17Z

Knowledgebaseadmin: Knowledgebaseadmin moved page FFmpeg - Scale and Latterbox to FFmpeg - Scale and Letterbox

[[Category:FFmpeg]]
[[Category:Video Scaling]]
<pre>
ffmpeg -i <input.file> -c:v libx264 -filter:v "scale=(iw*sar)*min(640/(iw*sar)\,480/ih):ih*min(640/(iw*sar)\,480/ih), pad=640:480:(640-iw*min(640/iw\,480/ih))/2:(480-ih*min(640/iw\,480/ih))/2" -f mp4 <output.file>
</pre>
Reference: [[FFMPEG - Encoding Optimal Videos for Streaming#Change_Resolution_and_add_Letterbox]]<br/>
Reference: [[https://stackoverflow.com/questions/61703587/proper-way-to-letterbox-with-ffmpeg stackoverflow: Proper way to letterbox with ffmpeg]]

FFmpeg - Scale and Letterbox

2025-03-06T12:40:54Z

Knowledgebaseadmin:

FFmpeg - Output Network Stream

2025-03-06T12:39:14Z

Knowledgebaseadmin:

[[Category:FFmpeg]]
[[Category:Streaming]]
All of the examples on this page assume an MPEG Transport Stream container with AVC video and AAC audio.
== RTMP ==
<code>ffmpeg -re -stream_loop -1 -i <input.file> -c copy -flush_packets 0 -f flv rtmp://<destination.address>:1935/<output.file></code>
== RTSP ==
<code>ffmpeg -re -stream_loop -1 -i <input.file> -c copy -f rtsp rtsp://<destination.address>:554/<output.file></code>
== SRT ==
<code>ffmpeg -re -stream_loop -1 -i <input.file> -c copy -f mpegts 'srt://<destination.address>:8890/<output.file>?streamid=publish:big_buck_bunny_480p_h264_stereo_aac&pkt_size=1316'</code>
== IceCast ==
<code>ffmpeg -re -stream_loop -1 -i <input.file> -c copy -f mpegts -content_type 'video/mp4' icecast://<username>:<password>@<destination.address>:8000/<output.file></code>
== References ==
[[http://192.168.1.10/Knowledgebase/Streaming%20Media/ Streaming Media]]