Foobar2000:Components 0.9/Command-Line Decoder Wrapper (foo input exe) - Revision history

DEATH: Added info about foo_input_ffmpeg

2018-01-16T11:19:47Z

Added info about foo_input_ffmpeg

← Older revision		Revision as of 11:19, 16 January 2018
Line 5:		Line 5:

	In certain cases, the Command-Line Decoder Wrapper is a superior alternative to the available native foobar2000 decoders if the native decoders are plagued by bugs; this component is inherently multi-instance safe and makes foobar2000 immune to crashes caused by buggy decoders.		In certain cases, the Command-Line Decoder Wrapper is a superior alternative to the available native foobar2000 decoders if the native decoders are plagued by bugs; this component is inherently multi-instance safe and makes foobar2000 immune to crashes caused by buggy decoders.

			== Using FFmpeg ==
			It is possible to use FFmpeg.exe with this component. However, spin-off of Command-Line Decoder Wrapper - [[Foobar2000:Components 0.9/FFmpeg Decoder Wrapper (foo input ffmpeg)\|FFmpeg Decoder Wrapper]] - is now available as a separate component. It works in similar manner, but was specialized for use with FFmpeg/FFprobe rather than arbitrary command-line decoders; among other things it supports seeking by FFmpeg -ss and reading of tags via FFprobe.

	=Drawbacks=		=Drawbacks=

DEATH: "-f W64" for better handling of very long streams

2017-10-31T14:19:27Z

"-f W64" for better handling of very long streams

← Older revision		Revision as of 14:19, 31 October 2017
Line 26:		Line 26:
	Examples:		Examples:
	* For TAK files: takc -d %s %d		* For TAK files: takc -d %s %d
	* For any format supported by FFmpeg, live decoding (faster but wrong duration shown): ffmpeg -i %s -f ~~WAV~~ -		* For any format supported by FFmpeg, live decoding (faster but wrong duration shown): ffmpeg -i %s -f W64 -
	* For any format supported by FFmpeg, decode whole file first (slower): ffmpeg -i %s %d		* For any format supported by FFmpeg, decode whole file first (slower): ffmpeg -i %s %d
	===File type mask===		===File type mask===

DEATH: Updated for foo_input_exe 0.5

2017-10-20T12:26:23Z

Updated for foo_input_exe 0.5

← Older revision		Revision as of 12:26, 20 October 2017
Line 17:		Line 17:
	Before using, you must configure the component for use with specific decoders.		Before using, you must configure the component for use with specific decoders.
	The decoder configuration page consists of four fields:		The decoder configuration page consists of four fields:
	* Format name		===Format name===
	** The name you wish to refer to the format by. It will be reported in %codec% of relevant files.		The name you wish to refer to the format by. It will be reported in %codec% of relevant files.
	* Decode command		===Decode command===
	** The command line to execute when decoding your files. Refer to the individual decoder's manual for details.		The command line to execute when decoding your files. Refer to the individual decoder's manual for details.
	** Use %s to specify the source file and %d to specify the destination file. If you do not include %d, foobar2000 will expect the decoder to write to stdout.
	** Example command line for decoding TAK files: "takc -d %s %d"		Use %s to specify the source file and %d to specify the destination file. If you do not include %d, foobar2000 will expect the decoder to write to stdout.
	* File type mask
	** A wildcard-pattern that defines what files should be fed to this decoder.		Examples:
	** Example: *.TAK for TAK files.		* For TAK files: takc -d %s %d
	** Multiple patterns may be specified per one decoder, delimited by semicolon.		* For any format supported by FFmpeg, live decoding (faster but wrong duration shown): ffmpeg -i %s -f WAV -
	** This is intentionally kept separate from "format name" to allow alternate extensions and prefix extensions.		* For any format supported by FFmpeg, decode whole file first (slower): ffmpeg -i %s %d
	* Decoder output format		===File type mask===
	** Format (to be exact: file type extension) that this decoder produces.		A wildcard-pattern that defines what files should be fed to this decoder.
	** This value should be set to WAV (the default) in most cases. Some exotic decoders may only support decoding to another format, hence this has been made configurable.
	* Write tag types		Example: *.TAK for TAK files.
	** 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!		Multiple patterns may be specified per one decoder, delimited by semicolon.
	** You do not need to enable this to read tags from your files, the Command-Line Decoder Wrapper component will attempt to read popular tag types (ID3v1/v2, APEv2) from your files regardless of this setting.
			This is intentionally kept separate from "format name" to allow alternate extensions and prefix extensions.

			Since version 0.5 of the component, you can specify protocols, eg. rtmp://*

			===Decoder output format===
			Format (to be exact: file type extension) that this decoder produces.

			This value should be set to WAV (the default) in most cases. Some exotic decoders may only support decoding to another format, hence this has been made configurable.

			===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 Command-Line Decoder Wrapper component will attempt to read popular tag types (ID3v1/v2, APEv2) from your files regardless of this setting.

	Use the bottom pane of the preferences page to specify folders containing your decoder binaries. If your binaries are present in %PATH%, there's no need to do so.		Use the bottom pane of the preferences page to specify folders containing your decoder binaries. If your binaries are present in %PATH%, there's no need to do so.

DEATH: Minor

2012-10-11T09:53:46Z

Minor

← Older revision		Revision as of 09:53, 11 October 2012
Line 9:		Line 9:

	When decoding to temporary files (%d):		When decoding to temporary files (%d):
	Because the whole file is decoded in advance before playback can ~~proceed~~, ~~this component is relatively slow. You~~ might want to increase your playback buffer length (in Preferences / Playback / Output).		Because the whole file is decoded in advance, this component stalls for a while before playback of each file can begin. To avoid playback interruptions when changing songs, you might want to increase your playback buffer length (in Preferences / Playback / Output).

	When decoding via stdout (no %d):		When decoding via stdout (no %d):

DEATH: Typo

2012-10-11T09:06:24Z

Typo

← Older revision		Revision as of 09:06, 11 October 2012
Line 2:		Line 2:
	=Description=		=Description=

	The Command-Line Decoder Wrapper ~~lets~~ allows you to play almost any otherwise unsupported audio format through foobar2000. All you need is a standalone command-line decoder executable that converts your files to one of the supported formats, such as WAV. Such decoders are available for nearly every audio format in existence.		The Command-Line Decoder Wrapper allows you to play almost any otherwise unsupported audio format through foobar2000. All you need is a standalone command-line decoder executable that converts your files to one of the supported formats, such as WAV. Such decoders are available for nearly every audio format in existence.

	In certain cases, the Command-Line Decoder Wrapper is a superior alternative to the available native foobar2000 decoders if the native decoders are plagued by bugs; this component is inherently multi-instance safe and makes foobar2000 immune to crashes caused by buggy decoders.		In certain cases, the Command-Line Decoder Wrapper is a superior alternative to the available native foobar2000 decoders if the native decoders are plagued by bugs; this component is inherently multi-instance safe and makes foobar2000 immune to crashes caused by buggy decoders.

DEATH: Updated

2012-10-10T11:27:47Z

Updated

← Older revision		Revision as of 11:27, 10 October 2012
Line 12:		Line 12:

	When decoding via stdout (no %d):		When decoding via stdout (no %d):
	~~Cannot seek~~ within the decoded ~~stream due to the nature of the process; the file~~ will ~~play as non-seekable (though playback should~~ start instantly in most cases).		Slow seeking within the decoded audio. Playback will start instantly in most cases though.

	=Usage=		=Usage=
Line 31:		Line 31:
	** Format (to be exact: file type extension) that this decoder produces.		** Format (to be exact: file type extension) that this decoder produces.
	** This value should be set to WAV (the default) in most cases. Some exotic decoders may only support decoding to another format, hence this has been made configurable.		** This value should be set to WAV (the default) in most cases. Some exotic decoders may only support decoding to another format, hence this has been made configurable.
			* 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 Command-Line Decoder Wrapper component will attempt to read popular tag types (ID3v1/v2, APEv2) from your files regardless of this setting.

	Use the bottom pane of the preferences page to specify folders containing your decoder binaries. If your binaries are present in %PATH%, there's no need to do so.		Use the bottom pane of the preferences page to specify folders containing your decoder binaries. If your binaries are present in %PATH%, there's no need to do so.

	~~=Tag handling=~~
	~~Only reading of tags is currently supported. Decoded files are examined for popular tag types: ID3v1, ID3v2, APEv2.~~

	~~Tag writing is ''not'' supported or else the component could be configured to damage your files without any further warning.~~

	=Link=		=Link=
	* [http://www.foobar2000.org/components/view/foo_input_exe Official Website]		* [http://www.foobar2000.org/components/view/foo_input_exe Official Website]

DEATH at 11:32, 7 October 2012

2012-10-07T11:32:37Z

← Older revision		Revision as of 11:32, 7 October 2012
Line 1:		Line 1:
	[~~[File~~:~~DEATH~~.~~JPG]~~]		{{fb2k}}
			=Description=

			The Command-Line Decoder Wrapper lets allows you to play almost any otherwise unsupported audio format through foobar2000. All you need is a standalone command-line decoder executable that converts your files to one of the supported formats, such as WAV. Such decoders are available for nearly every audio format in existence.

			In certain cases, the Command-Line Decoder Wrapper is a superior alternative to the available native foobar2000 decoders if the native decoders are plagued by bugs; this component is inherently multi-instance safe and makes foobar2000 immune to crashes caused by buggy decoders.

			=Drawbacks=

			When decoding to temporary files (%d):
			Because the whole file is decoded in advance before playback can proceed, this component is relatively slow. You might want to increase your playback buffer length (in Preferences / Playback / Output).

			When decoding via stdout (no %d):
			Cannot seek within the decoded stream due to the nature of the process; the file will play as non-seekable (though playback should start instantly in most cases).

			=Usage=
			Before using, you must configure the component for use with specific decoders.
			The decoder configuration page consists of four fields:
			* Format name
			** The name you wish to refer to the format by. It will be reported in %codec% of relevant files.
			* Decode command
			** The command line to execute when decoding your files. Refer to the individual decoder's manual for details.
			** Use %s to specify the source file and %d to specify the destination file. If you do not include %d, foobar2000 will expect the decoder to write to stdout.
			** Example command line for decoding TAK files: "takc -d %s %d"
			* 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.
			* Decoder output format
			** Format (to be exact: file type extension) that this decoder produces.
			** This value should be set to WAV (the default) in most cases. Some exotic decoders may only support decoding to another format, hence this has been made configurable.

			Use the bottom pane of the preferences page to specify folders containing your decoder binaries. If your binaries are present in %PATH%, there's no need to do so.

			=Tag handling=
			Only reading of tags is currently supported. Decoded files are examined for popular tag types: ID3v1, ID3v2, APEv2.

			Tag writing is ''not'' supported or else the component could be configured to damage your files without any further warning.

			=Link=
			* [http://www.foobar2000.org/components/view/foo_input_exe Official Website]

DEATH: Created page with "File:DEATH.JPG"

2012-10-06T16:48:27Z

Created page with "File:DEATH.JPG"

New page

[[File:DEATH.JPG]]