Template:Mux

??	VLC can decode this container. The module name to use at the command line is unknown.

Usage

{{mux|id= |encoder= |info= |module link= { page, none, <value> } |altid= |altid2= |mod= }}

id is supposed to be what you'd put in the command line, like

--sout='#std{mux=id,url=....}'

If there is more than one shortcut, use altid for the others.

Parameter |module link= defaults to page:

• page
  • mod will link to a particular module while displaying the id given. Use this when altid would not make sense. For example, on the page MOV the code {{Mux|id=mov|mod=mp4}} will link to the mp4 module while prominently displaying the shortcut mov in the box.
• none - ID only, no links
• <value> - URL to the Git file

It will add it to Category:Container (all containers) and Category:Container_Decoder (containers which can be decoded... which is all containers ;-) If you think that's stupid, change it!

If encoder is "y" then it also adds it to Category:Container_Encoder and changes the text a bit.

Info is for extra text in the box.

Examples

Example, avi

{{mux|id=avi|encoder=y}}

becomes

avi	VLC can encode and decode this container. The module name to use at the command line is avi.

Example, asf

{{mux|id=asf|encoder=y|info=This works with mp2v, blah blah}}

becomes

asf	VLC can encode and decode this container. This works with mp2v, blah blah The module name to use at the command line is asf.

Example, mp4

{{mux|id=mp4|encoder=y|altid=mov|altid2=3gp}}

becomes

mp4	VLC can encode and decode this container. The module name to use at the command line is mp4, but you can also use mov, or 3gp.

See also

• {{Codec audio}}
• {{Codec video}}
• {{Mux}}
• {{Protocol}}