Difference between revisions of "Foobar2000:Components 0.9/FFmpeg Decoder Wrapper (foo input ffmpeg)"

From Hydrogenaudio Knowledgebase
Jump to: navigation, search
(Created page with "{{fb2k}} =Description= The FFmpeg Decoder Wrapper allows you to play any FFmpeg-supported audio format through foobar2000. You need standalone FFmpeg binaries (ffmpeg.exe, ff...")
 
m (Added gallery)
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{fb2k}}
+
{{infobox foobar2000 component
=Description=
+
| name                = FFmpeg Decoder Wrapper
 +
| module_name          = foo_input_ffmpeg
 +
| developer            = Peter
 +
| repository          =
 +
| released            =
 +
| released_ref        =
 +
| stable_release      = 0.7
 +
| stable_release_date  = 2021-11-12
 +
| preview_release      =
 +
| preview_release_date =
 +
| foobar2000_minimum  = 1.5
 +
| foobar2000_maximum  =
 +
| foobar2000_ui_module = N/A
 +
| use                  = Output
 +
| license              =
 +
}}
 +
The '''FFmpeg Decoder Wrapper''' allows you to play any FFmpeg-supported audio format through foobar2000.
  
The FFmpeg Decoder Wrapper allows you to play any FFmpeg-supported audio format through foobar2000. You need standalone FFmpeg binaries (ffmpeg.exe, ffprobe.exe) on your system in order to use it.
+
You need standalone FFmpeg binaries (ffmpeg.exe, ffprobe.exe) on your system in order to use it.
  
=Drawbacks=
+
==Getting FFmpeg binaries==
  
No embedded cuesheet support.
+
Compatible FFmpeg binaries for Windows can be obtained from:
  
Not sample accurate seeking and length reporting.
+
https://github.com/BtbN/FFmpeg-Builds/releases (64-bit builds)
  
=Usage=
+
https://www.gyan.dev/ffmpeg/builds  (64-bit builds)
Before using, you must configure the component for use with specific decoders.
+
  
The decoder list comes pre-populated with most common format configurations; however all of them are unchecked by default.
+
https://github.com/sudo-nautilus/FFmpeg-Builds-Win32/releases (32-bit builds)
 +
 
 +
No specific requirement about 64bit/32bit/static/shared builds, either should work as long as it runs on your computer.
 +
 
 +
After downloading and extracting FFmpeg package, use the bottom editbox of the preferences page to specify the folder containing your FFmpeg binaries - ffmpeg.exe and ffprobe.exe are required. If your FFmpeg binaries are present in %PATH%, there's no need to do so.
 +
 
 +
=Configuration=
 +
Before using, you must configure the component for use with specific file formats, as well as point the component at the location of FFmpeg binaries on your system.
 +
 
 +
The format list comes pre-populated with most common format configurations; however all of them are unchecked by default.
  
The per-decoder configuration page consists of four fields:
 
 
===Format name===
 
===Format name===
 
The name you wish to refer to the format by - shown in open file dialog etc.
 
The name you wish to refer to the format by - shown in open file dialog etc.
 +
 
===File type mask===
 
===File type mask===
 
A wildcard-pattern that defines what files should be fed to this decoder.
 
A wildcard-pattern that defines what files should be fed to this decoder.
Line 28: Line 52:
  
 
You can also specify protocols, e.g. rtmp://* - or combine file types and protocols, e.g. http://*.m3u8
 
You can also specify protocols, e.g. rtmp://* - or combine file types and protocols, e.g. http://*.m3u8
 +
 +
===Additional arguments===
 +
Additional command-line arguments for ffmpeg. The extra arguments are injected before -i %s. To inject arguments after -i %s, include -i %s in arguments, -i %s will not be inserted again.[https://hydrogenaud.io/index.php/topic,114855.msg946957.html#msg946957]
 +
 +
===Show codec names from FFmpeg===
 +
By default, the format name specified above is shown in "codec" info.
 +
 +
Check this to take "codec" info from FFmpeg. Note that since FFmpeg reports short codec names in lowercase, the codec name will be uppercased to match foobar2000 conventions.
 +
===Support chapters===
 +
Controls whether chapters reported by FFprobe should be presented as separate playlist entries.
 +
 +
This is checked by default. Uncheck to suppress chapter support.
  
 
===Write tag types===
 
===Write tag types===
Line 36: Line 72:
 
You do not need to enable this to read tags from your files, the component will attempt to read popular tag types (ID3v1/v2, APEv2) from your files regardless of this setting.
 
You do not need to enable this to read tags from your files, the component will attempt to read popular tag types (ID3v1/v2, APEv2) from your files regardless of this setting.
  
Use the bottom editbox of the preferences page to specify folder containing your FFmpeg binaries - ffmpeg.exe and ffprobe.exe are required. If your FFmpeg binaries are present in %PATH%, there's no need to do so.
+
==Gallery==
 +
<gallery>
 +
foo input ffmpeg preferences.png|Preferences
 +
</gallery>
  
=Link=
+
==Links==
* [http://www.foobar2000.org/components/view/foo_input_ffmpeg Official Website]
+
* {{foobar2000|https://www.foobar2000.org/components/view/foo_input_ffmpeg|FFmpeg Decoder Wrapper}}
 +
* [http://ffmpeg.org FFmpeg website]

Revision as of 18:32, 28 May 2022

FFmpeg Decoder Wrapper

foo_input_ffmpeg
Developer(s) Peter
Repository
Release information
Initial release
Stable release 0.7 (November 12, 2021)
Preview release
foobar2000 compatibility
Architecture {{{foobar2000_architecture}}}
Minimum version 1.5
Maximum version
UI module(s) N/A
Additional information
Use Output
License
Discussion thread {{{discussion_thread}}}
View all components

The FFmpeg Decoder Wrapper allows you to play any FFmpeg-supported audio format through foobar2000.

You need standalone FFmpeg binaries (ffmpeg.exe, ffprobe.exe) on your system in order to use it.

Getting FFmpeg binaries

Compatible FFmpeg binaries for Windows can be obtained from:

https://github.com/BtbN/FFmpeg-Builds/releases (64-bit builds)

https://www.gyan.dev/ffmpeg/builds (64-bit builds)

https://github.com/sudo-nautilus/FFmpeg-Builds-Win32/releases (32-bit builds)

No specific requirement about 64bit/32bit/static/shared builds, either should work as long as it runs on your computer.

After downloading and extracting FFmpeg package, use the bottom editbox of the preferences page to specify the folder containing your FFmpeg binaries - ffmpeg.exe and ffprobe.exe are required. If your FFmpeg binaries are present in %PATH%, there's no need to do so.

Configuration

Before using, you must configure the component for use with specific file formats, as well as point the component at the location of FFmpeg binaries on your system.

The format list comes pre-populated with most common format configurations; however all of them are unchecked by default.

Format name

The name you wish to refer to the format by - shown in open file dialog etc.

File type mask

A wildcard-pattern that defines what files should be fed to this decoder.

Example: *.TAK for TAK files.

Multiple patterns may be specified per one decoder, delimited by semicolon.

This is intentionally kept separate from "format name" to allow alternate extensions and prefix extensions.

You can also specify protocols, e.g. rtmp://* - or combine file types and protocols, e.g. http://*.m3u8

Additional arguments

Additional command-line arguments for ffmpeg. The extra arguments are injected before -i %s. To inject arguments after -i %s, include -i %s in arguments, -i %s will not be inserted again.[1]

Show codec names from FFmpeg

By default, the format name specified above is shown in "codec" info.

Check this to take "codec" info from FFmpeg. Note that since FFmpeg reports short codec names in lowercase, the codec name will be uppercased to match foobar2000 conventions.

Support chapters

Controls whether chapters reported by FFprobe should be presented as separate playlist entries.

This is checked by default. Uncheck to suppress chapter support.

Write tag types

Tag types to write to when the user attempts to edit tags on the file.

USE WITH CAUTION - this feature may damage your files if used incorrectly; enable only after checking file format specifications for the file format you're dealing with!

You do not need to enable this to read tags from your files, the component will attempt to read popular tag types (ID3v1/v2, APEv2) from your files regardless of this setting.

Gallery

Links