Upload 48 files

.dockerfile

@@ -0,0 +1,36 @@
+# Use an official Python runtime as a parent image
+FROM python:3.9-slim-bullseye
+
+# Set the working directory in the container
+WORKDIR /app
+
+# Install system dependencies
+# - git: for installing python packages from git
+# - ffmpeg: for audio processing with pydub/librosa
+RUN apt-get update && \
+    apt-get install -y --no-install-recommends git ffmpeg && \
+    rm -rf /var/lib/apt/lists/*
+
+# Copy the requirements file into the container
+COPY requirements.txt .
+
+# Install Python dependencies
+# Using --no-cache-dir to reduce image size
+RUN pip install --no-cache-dir -r requirements.txt
+
+# Copy the rest of the application code into the container
+COPY main.py .
+COPY index.html .
+COPY yamnet_class_map.csv .
+COPY ./models ./models
+
+# Make port 7860 available to the world outside this container
+# Hugging Face Spaces often use this port by default
+EXPOSE 7860
+
+# Define environment variable for the port (optional, uvicorn command below sets it)
+ENV PORT 7860
+
+# Run the application
+# Use 0.0.0.0 to allow external connections
+CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "7860"]

.gitattributes

@@ -1,35 +1,2 @@
-*.7z filter=lfs diff=lfs merge=lfs -text
-*.arrow filter=lfs diff=lfs merge=lfs -text
-*.bin filter=lfs diff=lfs merge=lfs -text
-*.bz2 filter=lfs diff=lfs merge=lfs -text
-*.ckpt filter=lfs diff=lfs merge=lfs -text
-*.ftz filter=lfs diff=lfs merge=lfs -text
-*.gz filter=lfs diff=lfs merge=lfs -text
-*.h5 filter=lfs diff=lfs merge=lfs -text
-*.joblib filter=lfs diff=lfs merge=lfs -text
-*.lfs.* filter=lfs diff=lfs merge=lfs -text
-*.mlmodel filter=lfs diff=lfs merge=lfs -text
-*.model filter=lfs diff=lfs merge=lfs -text
-*.msgpack filter=lfs diff=lfs merge=lfs -text
-*.npy filter=lfs diff=lfs merge=lfs -text
-*.npz filter=lfs diff=lfs merge=lfs -text
-*.onnx filter=lfs diff=lfs merge=lfs -text
-*.ot filter=lfs diff=lfs merge=lfs -text
-*.parquet filter=lfs diff=lfs merge=lfs -text
-*.pb filter=lfs diff=lfs merge=lfs -text
-*.pickle filter=lfs diff=lfs merge=lfs -text
-*.pkl filter=lfs diff=lfs merge=lfs -text
-*.pt filter=lfs diff=lfs merge=lfs -text
-*.pth filter=lfs diff=lfs merge=lfs -text
-*.rar filter=lfs diff=lfs merge=lfs -text
-*.safetensors filter=lfs diff=lfs merge=lfs -text
-saved_model/**/* filter=lfs diff=lfs merge=lfs -text
-*.tar.* filter=lfs diff=lfs merge=lfs -text
-*.tar filter=lfs diff=lfs merge=lfs -text
-*.tflite filter=lfs diff=lfs merge=lfs -text
-*.tgz filter=lfs diff=lfs merge=lfs -text
-*.wasm filter=lfs diff=lfs merge=lfs -text
-*.xz filter=lfs diff=lfs merge=lfs -text
-*.zip filter=lfs diff=lfs merge=lfs -text
-*.zst filter=lfs diff=lfs merge=lfs -text
-*tfevents* filter=lfs diff=lfs merge=lfs -text
+*.exe filter=lfs diff=lfs merge=lfs -text
+models/neural_networks.h5 filter=lfs diff=lfs merge=lfs -text

.gitignore

@@ -0,0 +1,3 @@
+# Ignore virtual environments
+.venv/
+

client_script.py

@@ -0,0 +1,45 @@
+import argparse
+import os
+
+import requests
+
+
+def recognize_song_from_file(server_url: str, file_path: str):
+    """
+    Sends a local audio file to the song recognition server and prints the response.
+
+    Args:
+        server_url (str): The base URL of the FastAPI server (e.g., http://127.0.0.1:8000).
+        file_path (str): The local path to the audio file.
+    """
+    if not os.path.exists(file_path):
+        print(f"Error: File not found at {file_path}")
+        return
+
+    recognize_endpoint = f"{server_url.rstrip('/')}/recognize/"
+    
+    try:
+        with open(file_path, 'rb') as f:
+            files = {
+                'file': (os.path.basename(file_path), f, 'audio/mpeg') # Adjust content type if needed
+            }
+            print(f"Sending {file_path} to {recognize_endpoint}...")
+            response = requests.post(recognize_endpoint, files=files, timeout=30)
+            response.raise_for_status() 
+            
+            print("Response from server:")
+            print(response.json())
+
+    except requests.exceptions.RequestException as e:
+        print(f"Error connecting to server or during request: {e}")
+    except Exception as e:
+        print(f"An unexpected error occurred: {e}")
+
+if __name__ == "__main__":
+    parser = argparse.ArgumentParser(description="Client script to recognize a song by sending an audio file to the recognition server.")
+    parser.add_argument("file_path", type=str, help="The path to the audio file to recognize.")
+    parser.add_argument("--server_url", type=str, default="http://127.0.0.1:8000", help="The base URL of the FastAPI recognition server.")
+    
+    args = parser.parse_args()
+    
+    recognize_song_from_file(args.server_url, args.file_path) 

ffmpeg-master-latest-win64-gpl/LICENSE.txt

@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.

ffmpeg-master-latest-win64-gpl/bin/ffmpeg.exe

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1eefcc4e3a007c1ecf7c9ba4c0e180d83ca264365b56b912d0880dfcfc2ba4bf
+size 133623296

ffmpeg-master-latest-win64-gpl/bin/ffplay.exe

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:645293bb981fd83a291cdab7c753397f3a65e6bb6ab913d585225463d34c4f88
+size 135647744

ffmpeg-master-latest-win64-gpl/bin/ffprobe.exe

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e4a262b1e8793d9047fe336ed3ae792365b8322ba0a794252d961f62740f3da
+size 133434880

ffmpeg-master-latest-win64-gpl/doc/community.html

@@ -0,0 +1,227 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Community
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Community
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Organisation-1" href="#Organisation-1">1 Organisation</a></li>
+  <li><a id="toc-General-Assembly-1" href="#General-Assembly-1">2 General Assembly</a></li>
+  <li><a id="toc-Voting-1" href="#Voting-1">3 Voting</a></li>
+  <li><a id="toc-Technical-Committee-1" href="#Technical-Committee-1">4 Technical Committee</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Resolution-Process-1" href="#Resolution-Process-1">4.1 Resolution Process</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-Seizing" href="#Seizing">4.1.1 Seizing</a></li>
+      <li><a id="toc-Announcement" href="#Announcement">4.1.2 Announcement</a></li>
+      <li><a id="toc-RFC-call" href="#RFC-call">4.1.3 RFC call</a></li>
+      <li><a id="toc-Within-TC" href="#Within-TC">4.1.4 Within TC</a></li>
+      <li><a id="toc-Decisions" href="#Decisions">4.1.5 Decisions</a></li>
+    </ul></li>
+  </ul></li>
+  <li><a id="toc-Community-Committee-1" href="#Community-Committee-1">5 Community Committee</a></li>
+  <li><a id="toc-Code-of-Conduct-1" href="#Code-of-Conduct-1">6 Code of Conduct</a></li>
+</ul>
+</div>
+</div>
+
+<a class="anchor" id="Organisation"></a><a name="Organisation-1"></a>
+<h2 class="chapter">1 Organisation<span class="pull-right"><a class="anchor hidden-xs" href="#Organisation-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Organisation-1" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg project is organized through a community working on global consensus.
+</p>
+<p>Decisions are taken by the ensemble of active members, through voting and are aided by two committees.
+</p>
+<a class="anchor" id="General-Assembly"></a><a name="General-Assembly-1"></a>
+<h2 class="chapter">2 General Assembly<span class="pull-right"><a class="anchor hidden-xs" href="#General-Assembly-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-General-Assembly-1" aria-hidden="true">TOC</a></span></h2>
+
+<p>The ensemble of active members is called the General Assembly (GA).
+</p>
+<p>The General Assembly is sovereign and legitimate for all its decisions regarding the FFmpeg project.
+</p>
+<p>The General Assembly is made up of active contributors.
+</p>
+<p>Contributors are considered &quot;active contributors&quot; if they have authored more than 20 patches in the last 36 months in the main FFmpeg repository, or if they have been voted in by the GA.
+</p>
+<p>The list of active contributors is updated twice each year, on 1st January and 1st July, 0:00 UTC.
+</p>
+<p>Additional members are added to the General Assembly through a vote after proposal by a member of the General Assembly. They are part of the GA for two years, after which they need a confirmation by the GA.
+</p>
+<p>A script to generate the current members of the general assembly (minus members voted in) can be found in &lsquo;tools/general_assembly.pl&lsquo;.
+</p>
+<a class="anchor" id="Voting"></a><a name="Voting-1"></a>
+<h2 class="chapter">3 Voting<span class="pull-right"><a class="anchor hidden-xs" href="#Voting-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Voting-1" aria-hidden="true">TOC</a></span></h2>
+
+<p>Voting is done using a ranked voting system, currently running on https://vote.ffmpeg.org/ .
+</p>
+<p>Majority vote means more than 50% of the expressed ballots.
+</p>
+<a class="anchor" id="Technical-Committee"></a><a name="Technical-Committee-1"></a>
+<h2 class="chapter">4 Technical Committee<span class="pull-right"><a class="anchor hidden-xs" href="#Technical-Committee-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Technical-Committee-1" aria-hidden="true">TOC</a></span></h2>
+
+<p>The Technical Committee (TC) is here to arbitrate and make decisions when technical conflicts occur in the project. They will consider the merits of all the positions, judge them and make a decision.
+</p>
+<p>The TC resolves technical conflicts but is not a technical steering committee.
+</p>
+<p>Decisions by the TC are binding for all the contributors.
+</p>
+<p>Decisions made by the TC can be re-opened after 1 year or by a majority vote of the General Assembly, requested by one of the member of the GA.
+</p>
+<p>The TC is elected by the General Assembly for a duration of 1 year, and is composed of 5 members. Members can be re-elected if they wish. A majority vote in the General Assembly can trigger a new election of the TC.
+</p>
+<p>The members of the TC can be elected from outside of the GA. Candidates for election can either be suggested or self-nominated.
+</p>
+<p>The conflict resolution process is detailed in the resolution process document.
+</p>
+<p>The TC can be contacted at &lt;tc@ffmpeg&gt;.
+</p>
+<a class="anchor" id="Resolution-Process"></a><a name="Resolution-Process-1"></a>
+<h3 class="section">4.1 Resolution Process<span class="pull-right"><a class="anchor hidden-xs" href="#Resolution-Process-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Resolution-Process-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>The Technical Committee (TC) is here to arbitrate and make decisions when technical conflicts occur in the project.
+</p>
+<p>The TC main role is to resolve technical conflicts. It is therefore not a technical steering committee, but it is understood that some decisions might impact the future of the project.
+</p>
+<a name="Seizing"></a>
+<h4 class="subsection">4.1.1 Seizing<span class="pull-right"><a class="anchor hidden-xs" href="#Seizing" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Seizing" aria-hidden="true">TOC</a></span></h4>
+
+<p>The TC can take possession of any technical matter that it sees fit.
+</p>
+<p>To involve the TC in a matter, email tc&nbsp;or CC them on an ongoing discussion.
+</p>
+<p>As members of TC are developers, they also can email tc&nbsp;to raise an issue.
+</p><a name="Announcement"></a>
+<h4 class="subsection">4.1.2 Announcement<span class="pull-right"><a class="anchor hidden-xs" href="#Announcement" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Announcement" aria-hidden="true">TOC</a></span></h4>
+
+<p>The TC, once seized, must announce itself on the main mailing list, with a [TC] tag.
+</p>
+<p>The TC has 2 modes of operation: a RFC one and an internal one.
+</p>
+<p>If the TC thinks it needs the input from the larger community, the TC can call for a RFC. Else, it can decide by itself.
+</p>
+<p>The decision to use a RFC process or an internal discussion is a discretionary decision of the TC.
+</p>
+<p>The TC can also reject a seizure for a few reasons such as: the matter was not discussed enough previously; it lacks expertise to reach a beneficial decision on the matter; or the matter is too trivial.
+</p><a name="RFC-call"></a>
+<h4 class="subsection">4.1.3 RFC call<span class="pull-right"><a class="anchor hidden-xs" href="#RFC-call" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-RFC-call" aria-hidden="true">TOC</a></span></h4>
+
+<p>In the RFC mode, one person from the TC posts on the mailing list the technical question and will request input from the community.
+</p>
+<p>The mail will have the following specification:
+</p>
+<p>a precise title
+    a specific tag [TC RFC]
+    a top-level email
+    contain a precise question that does not exceed 100 words and that is answerable by developers
+    may have an extra description, or a link to a previous discussion, if deemed necessary,
+    contain a precise end date for the answers.
+</p>
+<p>The answers from the community must be on the main mailing list and must have the following specification:
+</p>
+<p>keep the tag and the title unchanged
+    limited to 400 words
+    a first-level, answering directly to the main email
+    answering to the question.
+</p>
+<p>Further replies to answers are permitted, as long as they conform to the community standards of politeness, they are limited to 100 words, and are not nested more than once. (max-depth=2)
+</p>
+<p>After the end-date, mails on the thread will be ignored.
+</p>
+<p>Violations of those rules will be escalated through the Community Committee.
+</p>
+<p>After all the emails are in, the TC has 96 hours to give its final decision. Exceptionally, the TC can request an extra delay, that will be notified on the mailing list.
+</p><a name="Within-TC"></a>
+<h4 class="subsection">4.1.4 Within TC<span class="pull-right"><a class="anchor hidden-xs" href="#Within-TC" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Within-TC" aria-hidden="true">TOC</a></span></h4>
+
+<p>In the internal case, the TC has 96 hours to give its final decision. Exceptionally, the TC can request an extra delay.
+</p><a name="Decisions"></a>
+<h4 class="subsection">4.1.5 Decisions<span class="pull-right"><a class="anchor hidden-xs" href="#Decisions" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Decisions" aria-hidden="true">TOC</a></span></h4>
+
+<p>The decisions from the TC will be sent on the mailing list, with the [TC] tag.
+</p>
+<p>Internally, the TC should take decisions with a majority, or using ranked-choice voting.
+</p>
+<p>Each TC member must vote on such decision according to what is, in their view, best for the project.
+</p>
+<p>If a TC member feels they are affected by a conflict of interest with regards to the case, they should announce it and recuse themselves from the TC
+discussion and vote.
+</p>
+<p>A conflict of interest is presumed to occur when a TC member has a personal interest (e.g. financial) in a specific outcome of the case.
+</p>
+<p>The decision from the TC should be published with a summary of the reasons that lead to this decision.
+</p>
+<p>The decisions from the TC are final, until the matters are reopened after no less than one year.
+</p>
+<a class="anchor" id="Community-Committee"></a><a name="Community-Committee-1"></a>
+<h2 class="chapter">5 Community Committee<span class="pull-right"><a class="anchor hidden-xs" href="#Community-Committee-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Community-Committee-1" aria-hidden="true">TOC</a></span></h2>
+
+<p>The Community Committee (CC) is here to arbitrage and make decisions when inter-personal conflicts occur in the project. It will decide quickly and take actions, for the sake of the project.
+</p>
+<p>The CC can remove privileges of offending members, including removal of commit access and temporary ban from the community.
+</p>
+<p>Decisions made by the CC can be re-opened after 1 year or by a majority vote of the General Assembly. Indefinite bans from the community must be confirmed by the General Assembly, in a majority vote.
+</p>
+<p>The CC is elected by the General Assembly for a duration of 1 year, and is composed of 5 members. Members can be re-elected if they wish. A majority vote in the General Assembly can trigger a new election of the CC.
+</p>
+<p>The members of the CC can be elected from outside of the GA. Candidates for election can either be suggested or self-nominated.
+</p>
+<p>The CC is governed by and responsible for enforcing the Code of Conduct.
+</p>
+<p>The CC can be contacted at &lt;cc@ffmpeg&gt;.
+</p>
+<a class="anchor" id="Code-of-Conduct"></a><a name="Code-of-Conduct-1"></a>
+<h2 class="chapter">6 Code of Conduct<span class="pull-right"><a class="anchor hidden-xs" href="#Code-of-Conduct-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Code-of-Conduct-1" aria-hidden="true">TOC</a></span></h2>
+
+<p>Be friendly and respectful towards others and third parties.
+Treat others the way you yourself want to be treated.
+</p>
+<p>Be considerate. Not everyone shares the same viewpoint and priorities as you do.
+Different opinions and interpretations help the project.
+Looking at issues from a different perspective assists development.
+</p>
+<p>Do not assume malice for things that can be attributed to incompetence. Even if
+it is malice, it&rsquo;s rarely good to start with that as initial assumption.
+</p>
+<p>Stay friendly even if someone acts contrarily. Everyone has a bad day
+once in a while.
+If you yourself have a bad day or are angry then try to take a break and reply
+once you are calm and without anger if you have to.
+</p>
+<p>Try to help other team members and cooperate if you can.
+</p>
+<p>The goal of software development is to create technical excellence, not for any
+individual to be better and &quot;win&quot; against the others. Large software projects
+are only possible and successful through teamwork.
+</p>
+<p>If someone struggles do not put them down. Give them a helping hand
+instead and point them in the right direction.
+</p>
+<p>Finally, keep in mind the immortal words of Bill and Ted,
+&quot;Be excellent to each other.&quot;
+</p>
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/default.css

@@ -0,0 +1,165 @@
+a.summary-letter {
+    text-decoration: none;
+}
+
+a {
+    color: #2D6198;
+}
+
+a:visited {
+    color: #884488;
+}
+
+#banner {
+    background-color: white;
+    position: relative;
+    text-align: center;
+}
+
+#banner img {
+    margin-bottom: 1px;
+    margin-top: 5px;
+}
+
+#body {
+    margin-left: 1em;
+    margin-right: 1em;
+}
+
+body {
+    background-color: #313131;
+    margin: 0;
+    text-align: justify;
+}
+
+.center {
+    margin-left: auto;
+    margin-right: auto;
+    text-align: center;
+}
+
+#container {
+    background-color: white;
+    color: #202020;
+    margin-left: 1em;
+    margin-right: 1em;
+}
+
+#footer {
+    text-align: center;
+}
+
+h1 a, h2 a, h3 a, h4 a {
+    text-decoration: inherit;
+    color: inherit;
+}
+
+h1, h2, h3, h4 {
+    padding-left: 0.4em;
+    border-radius: 4px;
+    padding-bottom: 0.25em;
+    padding-top: 0.25em;
+    border: 1px solid #6A996A;
+}
+
+h1 {
+    background-color: #7BB37B;
+    color: #151515;
+    font-size: 1.2em;
+    padding-bottom: 0.3em;
+    padding-top: 0.3em;
+}
+
+h2 {
+    color: #313131;
+    font-size: 1.0em;
+    background-color: #ABE3AB;
+}
+
+h3 {
+    color: #313131;
+    font-size: 0.9em;
+    margin-bottom: -6px;
+    background-color: #BBF3BB;
+}
+
+h4 {
+    color: #313131;
+    font-size: 0.8em;
+    margin-bottom: -8px;
+    background-color: #D1FDD1;
+}
+
+img {
+    border: 0;
+}
+
+#navbar {
+    background-color: #738073;
+    border-bottom: 1px solid #5C665C;
+    border-top: 1px solid #5C665C;
+    margin-top: 12px;
+    padding: 0.3em;
+    position: relative;
+    text-align: center;
+}
+
+#navbar a, #navbar_secondary a {
+    color: white;
+    padding: 0.3em;
+    text-decoration: none;
+}
+
+#navbar a:hover, #navbar_secondary a:hover {
+    background-color: #313131;
+    color: white;
+    text-decoration: none;
+}
+
+#navbar_secondary {
+    background-color: #738073;
+    border-bottom: 1px solid #5C665C;
+    border-left: 1px solid #5C665C;
+    border-right: 1px solid #5C665C;
+    padding: 0.3em;
+    position: relative;
+    text-align: center;
+}
+
+p {
+    margin-left: 1em;
+    margin-right: 1em;
+}
+
+pre {
+    margin-left: 3em;
+    margin-right: 3em;
+    padding: 0.3em;
+    border: 1px solid #bbb;
+    background-color: #f7f7f7;
+}
+
+dl dt {
+    font-weight: bold;
+}
+
+#proj_desc {
+    font-size: 1.2em;
+}
+
+#repos {
+    margin-left: 1em;
+    margin-right: 1em;
+    border-collapse: collapse;
+    border: solid 1px #6A996A;
+}
+
+#repos th {
+    background-color: #7BB37B;
+    border: solid 1px #6A996A;
+}
+
+#repos td {
+    padding: 0.2em;
+    border: solid 1px #6A996A;
+}

ffmpeg-master-latest-win64-gpl/doc/developer.html

@@ -0,0 +1,1149 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Developer Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Developer Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Introduction" href="#Introduction">1 Introduction</a></li>
+  <li><a id="toc-Coding-Rules-1" href="#Coding-Rules-1">2 Coding Rules</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Language" href="#Language">2.1 Language</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-SIMD_002fDSP-1" href="#SIMD_002fDSP-1">2.1.1 SIMD/DSP</a></li>
+      <li><a id="toc-Other-languages" href="#Other-languages">2.1.2 Other languages</a></li>
+    </ul></li>
+    <li><a id="toc-Code-formatting-conventions" href="#Code-formatting-conventions">2.2 Code formatting conventions</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-Examples" href="#Examples">2.2.1 Examples</a></li>
+      <li><a id="toc-Vim-configuration" href="#Vim-configuration">2.2.2 Vim configuration</a></li>
+      <li><a id="toc-Emacs-configuration" href="#Emacs-configuration">2.2.3 Emacs configuration</a></li>
+    </ul></li>
+    <li><a id="toc-Comments" href="#Comments">2.3 Comments</a></li>
+    <li><a id="toc-Naming-conventions-1" href="#Naming-conventions-1">2.4 Naming conventions</a></li>
+    <li><a id="toc-Miscellaneous-conventions" href="#Miscellaneous-conventions">2.5 Miscellaneous conventions</a></li>
+  </ul></li>
+  <li><a id="toc-Development-Policy-1" href="#Development-Policy-1">3 Development Policy</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Code-behaviour" href="#Code-behaviour">3.1 Code behaviour</a></li>
+    <li><a id="toc-Patches_002fCommitting" href="#Patches_002fCommitting">3.2 Patches/Committing</a></li>
+    <li><a id="toc-Code" href="#Code">3.3 Code</a></li>
+    <li><a id="toc-Library-public-interfaces" href="#Library-public-interfaces">3.4 Library public interfaces</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-Adding-new-interfaces" href="#Adding-new-interfaces">3.4.1 Adding new interfaces</a></li>
+      <li><a id="toc-Removing-interfaces-1" href="#Removing-interfaces-1">3.4.2 Removing interfaces</a></li>
+      <li><a id="toc-Major-version-bumps-1" href="#Major-version-bumps-1">3.4.3 Major version bumps</a></li>
+    </ul></li>
+    <li><a id="toc-Documentation_002fOther" href="#Documentation_002fOther">3.5 Documentation/Other</a></li>
+  </ul></li>
+  <li><a id="toc-Submitting-patches-1" href="#Submitting-patches-1">4 Submitting patches</a></li>
+  <li><a id="toc-New-codecs-or-formats-checklist" href="#New-codecs-or-formats-checklist">5 New codecs or formats checklist</a></li>
+  <li><a id="toc-Patch-submission-checklist" href="#Patch-submission-checklist">6 Patch submission checklist</a></li>
+  <li><a id="toc-Patch-review-process" href="#Patch-review-process">7 Patch review process</a></li>
+  <li><a id="toc-Regression-tests-1" href="#Regression-tests-1">8 Regression tests</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Adding-files-to-the-fate_002dsuite-dataset" href="#Adding-files-to-the-fate_002dsuite-dataset">8.1 Adding files to the fate-suite dataset</a></li>
+    <li><a id="toc-Visualizing-Test-Coverage" href="#Visualizing-Test-Coverage">8.2 Visualizing Test Coverage</a></li>
+    <li><a id="toc-Using-Valgrind" href="#Using-Valgrind">8.3 Using Valgrind</a></li>
+  </ul></li>
+  <li><a id="toc-Maintenance-process" href="#Maintenance-process">9 Maintenance process</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-MAINTAINERS-1" href="#MAINTAINERS-1">9.1 MAINTAINERS</a></li>
+    <li><a id="toc-Becoming-a-maintainer-1" href="#Becoming-a-maintainer-1">9.2 Becoming a maintainer</a></li>
+  </ul></li>
+  <li><a id="toc-Release-process-1" href="#Release-process-1">10 Release process</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Criteria-for-Point-Releases-1" href="#Criteria-for-Point-Releases-1">10.1 Criteria for Point Releases</a></li>
+    <li><a id="toc-Release-Checklist" href="#Release-Checklist">10.2 Release Checklist</a></li>
+  </ul></li>
+</ul>
+</div>
+</div>
+
+<a name="Introduction"></a>
+<h2 class="chapter">1 Introduction<span class="pull-right"><a class="anchor hidden-xs" href="#Introduction" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Introduction" aria-hidden="true">TOC</a></span></h2>
+
+<p>This text is concerned with the development <em class="emph">of</em> FFmpeg itself. Information
+on using the FFmpeg libraries in other programs can be found elsewhere, e.g. in:
+</p><ul class="itemize mark-bullet">
+<li>the installed header files
+</li><li><a class="url" href="http://ffmpeg.org/doxygen/trunk/index.html">the Doxygen documentation</a>
+generated from the headers
+</li><li>the examples under <samp class="file">doc/examples</samp>
+</li></ul>
+
+<p>For more detailed legal information about the use of FFmpeg in
+external programs read the <samp class="file">LICENSE</samp> file in the source tree and
+consult <a class="url" href="https://ffmpeg.org/legal.html">https://ffmpeg.org/legal.html</a>.
+</p>
+<p>If you modify FFmpeg code for your own use case, you are highly encouraged to
+<em class="emph">submit your changes back to us</em>, using this document as a guide. There are
+both pragmatic and ideological reasons to do so:
+</p><ul class="itemize mark-bullet">
+<li>Maintaining external changes to keep up with upstream development is
+time-consuming and error-prone. With your code in the main tree, it will be
+maintained by FFmpeg developers.
+</li><li>FFmpeg developers include leading experts in the field who can find bugs or
+design flaws in your code.
+</li><li>By supporting the project you find useful you ensure it continues to be
+maintained and developed.
+</li></ul>
+
+<p>All proposed code changes should be submitted for review to
+<a class="url" href="mailto:ffmpeg-devel@ffmpeg.org">the development mailing list</a>, as
+described in more detail in the <a class="ref" href="#Submitting-patches">Submitting patches</a> chapter. The code
+should comply with the <a class="ref" href="#Development-Policy">Development Policy</a> and follow the <a class="ref" href="#Coding-Rules">Coding Rules</a>.
+The developer making the commit and the author are responsible for their changes
+and should try to fix issues their commit causes.
+</p>
+<a class="anchor" id="Coding-Rules"></a><a name="Coding-Rules-1"></a>
+<h2 class="chapter">2 Coding Rules<span class="pull-right"><a class="anchor hidden-xs" href="#Coding-Rules-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Coding-Rules-1" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Language"></a>
+<h3 class="section">2.1 Language<span class="pull-right"><a class="anchor hidden-xs" href="#Language" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Language" aria-hidden="true">TOC</a></span></h3>
+
+<p>FFmpeg is mainly programmed in the ISO C11 language, except for the public
+headers which must stay C99 compatible.
+</p>
+<p>Compiler-specific extensions may be used with good reason, but must not be
+depended on, i.e. the code must still compile and work with compilers lacking
+the extension.
+</p>
+<p>The following C99 features must not be used anywhere in the codebase:
+</p><ul class="itemize mark-bullet">
+<li>variable-length arrays;
+
+</li><li>complex numbers;
+</li></ul>
+
+<a name="SIMD_002fDSP-1"></a>
+<h4 class="subsection">2.1.1 SIMD/DSP<span class="pull-right"><a class="anchor hidden-xs" href="#SIMD_002fDSP-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-SIMD_002fDSP-1" aria-hidden="true">TOC</a></span></h4>
+<a class="anchor" id="SIMD_002fDSP"></a>
+<p>As modern compilers are unable to generate efficient SIMD or other
+performance-critical DSP code from plain C, handwritten assembly is used.
+Usually such code is isolated in a separate function. Then the standard approach
+is writing multiple versions of this function – a plain C one that works
+everywhere and may also be useful for debugging, and potentially multiple
+architecture-specific optimized implementations. Initialization code then
+chooses the best available version at runtime and loads it into a function
+pointer; the function in question is then always called through this pointer.
+</p>
+<p>The specific syntax used for writing assembly is:
+</p><ul class="itemize mark-bullet">
+<li>NASM on x86;
+
+</li><li>GAS on ARM and RISC-V.
+</li></ul>
+
+<p>A unit testing framework for assembly called <code class="code">checkasm</code> lives under
+<samp class="file">tests/checkasm</samp>. All new assembly should come with <code class="code">checkasm</code> tests;
+adding tests for existing assembly that lacks them is also strongly encouraged.
+</p>
+<a name="Other-languages"></a>
+<h4 class="subsection">2.1.2 Other languages<span class="pull-right"><a class="anchor hidden-xs" href="#Other-languages" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Other-languages" aria-hidden="true">TOC</a></span></h4>
+
+<p>Other languages than C may be used in special cases:
+</p><ul class="itemize mark-bullet">
+<li>Compiler intrinsics or inline assembly when the code in question cannot be
+written in the standard way described in the <a class="ref" href="#SIMD_002fDSP">SIMD/DSP</a> section. This
+typically applies to code that needs to be inlined.
+
+</li><li>Objective-C where required for interacting with macOS-specific interfaces.
+</li></ul>
+
+<a name="Code-formatting-conventions"></a>
+<h3 class="section">2.2 Code formatting conventions<span class="pull-right"><a class="anchor hidden-xs" href="#Code-formatting-conventions" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Code-formatting-conventions" aria-hidden="true">TOC</a></span></h3>
+
+<p>There are the following guidelines regarding the code style in files:
+</p>
+<ul class="itemize mark-bullet">
+<li>Indent size is 4.
+
+</li><li>The TAB character is forbidden outside of Makefiles as is any
+form of trailing whitespace. Commits containing either will be
+rejected by the git repository.
+
+</li><li>You should try to limit your code lines to 80 characters; however, do so if
+and only if this improves readability.
+
+</li><li>K&amp;R coding style is used.
+</li></ul>
+<p>The presentation is one inspired by &rsquo;indent -i4 -kr -nut&rsquo;.
+</p>
+<a name="Examples"></a>
+<h4 class="subsection">2.2.1 Examples<span class="pull-right"><a class="anchor hidden-xs" href="#Examples" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Examples" aria-hidden="true">TOC</a></span></h4>
+<p>Some notable examples to illustrate common code style in FFmpeg:
+</p>
+<ul class="itemize mark-bullet">
+<li>Space around assignments and after
+<code class="code">if</code>/<code class="code">do</code>/<code class="code">while</code>/<code class="code">for</code> keywords:
+
+<div class="example user-c user-good">
+<pre class="example-preformatted">// Good
+if (condition)
+    av_foo();
+</pre></div>
+
+<div class="example user-c user-good">
+<pre class="example-preformatted">// Good
+for (size_t i = 0; i &lt; len; i++)
+    av_bar(i);
+</pre></div>
+
+<div class="example user-c user-good">
+<pre class="example-preformatted">// Good
+size_t size = 0;
+</pre></div>
+
+<p>However no spaces between the parentheses and condition, unless it helps
+readability of complex conditions, so the following should not be done:
+</p>
+<div class="example user-c user-bad">
+<pre class="example-preformatted">// Bad style
+if ( condition )
+    av_foo();
+</pre></div>
+
+</li><li>No unnecessary parentheses, unless it helps readability:
+
+<div class="example user-c user-good">
+<pre class="example-preformatted">// Good
+int fields = ilace ? 2 : 1;
+</pre></div>
+
+</li><li>Don&rsquo;t wrap single-line blocks in braces. Use braces only if there is an accompanying else statement. This keeps future code changes easier to keep track of.
+
+<div class="example user-c user-good">
+<pre class="example-preformatted">// Good
+if (bits_pixel == 24) {
+    avctx-&gt;pix_fmt = AV_PIX_FMT_BGR24;
+} else if (bits_pixel == 8) {
+    avctx-&gt;pix_fmt = AV_PIX_FMT_GRAY8;
+} else
+    return AVERROR_INVALIDDATA;
+
+</pre></div>
+
+</li><li>Avoid assignments in conditions where it makes sense:
+
+<div class="example user-c user-good">
+<pre class="example-preformatted">// Good
+video_enc-&gt;chroma_intra_matrix = av_mallocz(sizeof(*video_enc-&gt;chroma_intra_matrix) * 64)
+if (!video_enc-&gt;chroma_intra_matrix)
+    return AVERROR(ENOMEM);
+</pre></div>
+
+<div class="example user-c user-bad">
+<pre class="example-preformatted">// Bad style
+if (!(video_enc-&gt;chroma_intra_matrix = av_mallocz(sizeof(*video_enc-&gt;chroma_intra_matrix) * 64)))
+    return AVERROR(ENOMEM);
+</pre></div>
+
+<div class="example user-c user-good">
+<pre class="example-preformatted">// Ok
+while ((entry = av_dict_iterate(options, entry)))
+    av_log(ctx, AV_LOG_INFO, &quot;Item '%s': '%s'\n&quot;, entry-&gt;key, entry-&gt;value);
+</pre></div>
+
+</li><li>When declaring a pointer variable, the <code class="code">*</code> goes with the variable not the type:
+
+<div class="example user-c user-good">
+<pre class="example-preformatted">// Good
+AVStream *stream;
+</pre></div>
+
+<div class="example user-c user-bad">
+<pre class="example-preformatted">// Bad style
+AVStream* stream;
+</pre></div>
+
+</li></ul>
+
+<p>If you work on a file that does not follow these guidelines consistently,
+change the parts that you are editing to follow these guidelines but do
+not make unrelated changes in the file to make it conform to these.
+</p>
+<a name="Vim-configuration"></a>
+<h4 class="subsection">2.2.2 Vim configuration<span class="pull-right"><a class="anchor hidden-xs" href="#Vim-configuration" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Vim-configuration" aria-hidden="true">TOC</a></span></h4>
+<p>In order to configure Vim to follow FFmpeg formatting conventions, paste
+the following snippet into your <samp class="file">.vimrc</samp>:
+</p><div class="example">
+<pre class="example-preformatted">&quot; indentation rules for FFmpeg: 4 spaces, no tabs
+set expandtab
+set shiftwidth=4
+set softtabstop=4
+set cindent
+set cinoptions=(0
+&quot; Allow tabs in Makefiles.
+autocmd FileType make,automake set noexpandtab shiftwidth=8 softtabstop=8
+&quot; Trailing whitespace and tabs are forbidden, so highlight them.
+highlight ForbiddenWhitespace ctermbg=red guibg=red
+match ForbiddenWhitespace /\s\+$\|\t/
+&quot; Do not highlight spaces at the end of line while typing on that line.
+autocmd InsertEnter * match ForbiddenWhitespace /\t\|\s\+\%#\@&lt;!$/
+</pre></div>
+
+<a name="Emacs-configuration"></a>
+<h4 class="subsection">2.2.3 Emacs configuration<span class="pull-right"><a class="anchor hidden-xs" href="#Emacs-configuration" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Emacs-configuration" aria-hidden="true">TOC</a></span></h4>
+<p>For Emacs, add these roughly equivalent lines to your <samp class="file">.emacs.d/init.el</samp>:
+</p><div class="example lisp">
+<pre class="lisp-preformatted">(c-add-style &quot;ffmpeg&quot;
+             '(&quot;k&amp;r&quot;
+               (c-basic-offset . 4)
+               (indent-tabs-mode . nil)
+               (show-trailing-whitespace . t)
+               (c-offsets-alist
+                (statement-cont . (c-lineup-assignments +)))
+               )
+             )
+(setq c-default-style &quot;ffmpeg&quot;)
+</pre></div>
+
+<a name="Comments"></a>
+<h3 class="section">2.3 Comments<span class="pull-right"><a class="anchor hidden-xs" href="#Comments" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Comments" aria-hidden="true">TOC</a></span></h3>
+<p>Use the JavaDoc/Doxygen  format (see examples below) so that code documentation
+can be generated automatically. All nontrivial functions should have a comment
+above them explaining what the function does, even if it is just one sentence.
+All structures and their member variables should be documented, too.
+</p>
+<p>Avoid Qt-style and similar Doxygen syntax with <code class="code">!</code> in it, i.e. replace
+<code class="code">//!</code> with <code class="code">///</code> and similar.  Also @ syntax should be employed
+for markup commands, i.e. use <code class="code">@param</code> and not <code class="code">\param</code>.
+</p>
+<div class="example">
+<pre class="example-preformatted">/**
+ * @file
+ * MPEG codec.
+ * @author ...
+ */
+
+/**
+ * Summary sentence.
+ * more text ...
+ * ...
+ */
+typedef struct Foobar {
+    int var1; /**&lt; var1 description */
+    int var2; ///&lt; var2 description
+    /** var3 description */
+    int var3;
+} Foobar;
+
+/**
+ * Summary sentence.
+ * more text ...
+ * ...
+ * @param my_parameter description of my_parameter
+ * @return return value description
+ */
+int myfunc(int my_parameter)
+...
+</pre></div>
+
+<a class="anchor" id="Naming-conventions"></a><a name="Naming-conventions-1"></a>
+<h3 class="section">2.4 Naming conventions<span class="pull-right"><a class="anchor hidden-xs" href="#Naming-conventions-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Naming-conventions-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>Names of functions, variables, and struct members must be lowercase, using
+underscores (_) to separate words. For example, &lsquo;<samp class="samp">avfilter_get_video_buffer</samp>&rsquo;
+is an acceptable function name and &lsquo;<samp class="samp">AVFilterGetVideo</samp>&rsquo; is not.
+</p>
+<p>Struct, union, enum, and typedeffed type names must use CamelCase. All structs
+and unions should be typedeffed to the same name as the struct/union tag, e.g.
+<code class="code">typedef struct AVFoo { ... } AVFoo;</code>. Enums are typically not
+typedeffed.
+</p>
+<p>Enumeration constants and macros must be UPPERCASE, except for macros
+masquerading as functions, which should use the function naming convention.
+</p>
+<p>All identifiers in the libraries should be namespaced as follows:
+</p><ul class="itemize mark-bullet">
+<li>No namespacing for identifiers with file and lower scope (e.g. local variables,
+static functions), and struct and union members,
+
+</li><li>The <code class="code">ff_</code> prefix must be used for variables and functions visible outside
+of file scope, but only used internally within a single library, e.g.
+&lsquo;<samp class="samp">ff_w64_demuxer</samp>&rsquo;. This prevents name collisions when FFmpeg is statically
+linked.
+
+</li><li>For variables and functions visible outside of file scope, used internally
+across multiple libraries, use <code class="code">avpriv_</code> as prefix, for example,
+&lsquo;<samp class="samp">avpriv_report_missing_feature</samp>&rsquo;.
+
+</li><li>All other internal identifiers, like private type or macro names, should be
+namespaced only to avoid possible internal conflicts. E.g. <code class="code">H264_NAL_SPS</code>
+vs. <code class="code">HEVC_NAL_SPS</code>.
+
+</li><li>Each library has its own prefix for public symbols, in addition to the
+commonly used <code class="code">av_</code> (<code class="code">avformat_</code> for libavformat,
+<code class="code">avcodec_</code> for libavcodec, <code class="code">swr_</code> for libswresample, etc).
+Check the existing code and choose names accordingly.
+
+</li><li>Other public identifiers (struct, union, enum, macro, type names) must use their
+library&rsquo;s public prefix (<code class="code">AV</code>, <code class="code">Sws</code>, or <code class="code">Swr</code>).
+</li></ul>
+
+<p>Furthermore, name space reserved for the system should not be invaded.
+Identifiers ending in <code class="code">_t</code> are reserved by
+<a class="url" href="http://pubs.opengroup.org/onlinepubs/007904975/functions/xsh_chap02_02.html#tag_02_02_02">POSIX</a>.
+Also avoid names starting with <code class="code">__</code> or <code class="code">_</code> followed by an uppercase
+letter as they are reserved by the C standard. Names starting with <code class="code">_</code>
+are reserved at the file level and may not be used for externally visible
+symbols. If in doubt, just avoid names starting with <code class="code">_</code> altogether.
+</p>
+<a name="Miscellaneous-conventions"></a>
+<h3 class="section">2.5 Miscellaneous conventions<span class="pull-right"><a class="anchor hidden-xs" href="#Miscellaneous-conventions" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Miscellaneous-conventions" aria-hidden="true">TOC</a></span></h3>
+
+<ul class="itemize mark-bullet">
+<li>Casts should be used only when necessary. Unneeded parentheses
+should also be avoided if they don&rsquo;t make the code easier to understand.
+</li></ul>
+
+<a class="anchor" id="Development-Policy"></a><a name="Development-Policy-1"></a>
+<h2 class="chapter">3 Development Policy<span class="pull-right"><a class="anchor hidden-xs" href="#Development-Policy-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Development-Policy-1" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Code-behaviour"></a>
+<h3 class="section">3.1 Code behaviour<span class="pull-right"><a class="anchor hidden-xs" href="#Code-behaviour" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Code-behaviour" aria-hidden="true">TOC</a></span></h3>
+
+<a name="Correctness"></a>
+<p>The code must be valid. It must not crash, abort, access invalid pointers, leak
+memory, cause data races or signed integer overflow, or otherwise cause
+undefined behaviour. Error codes should be checked and, when applicable,
+forwarded to the caller.
+</p>
+<a name="Thread_002d-and-library_002dsafety"></a>
+<p>Our libraries may be called by multiple independent callers in the same process.
+These calls may happen from any number of threads and the different call sites
+may not be aware of each other - e.g. a user program may be calling our
+libraries directly, and use one or more libraries that also call our libraries.
+The code must behave correctly under such conditions.
+</p>
+<a name="Robustness"></a>
+<p>The code must treat as untrusted any bytestream received from a caller or read
+from a file, network, etc. It must not misbehave when arbitrary data is sent to
+it - typically it should print an error message and return
+<code class="code">AVERROR_INVALIDDATA</code> on encountering invalid input data.
+</p>
+<a name="Memory-allocation"></a>
+<p>The code must use the <code class="code">av_malloc()</code> family of functions from
+<samp class="file">libavutil/mem.h</samp> to perform all memory allocation, except in special cases
+(e.g. when interacting with an external library that requires a specific
+allocator to be used).
+</p>
+<p>All allocations should be checked and <code class="code">AVERROR(ENOMEM)</code> returned on
+failure. A common mistake is that error paths leak memory - make sure that does
+not happen.
+</p>
+<a name="stdio"></a>
+<p>Our libraries must not access the stdio streams stdin/stdout/stderr directly
+(e.g. via <code class="code">printf()</code> family of functions), as that is not library-safe. For
+logging, use <code class="code">av_log()</code>.
+</p>
+<a name="Patches_002fCommitting"></a>
+<h3 class="section">3.2 Patches/Committing<span class="pull-right"><a class="anchor hidden-xs" href="#Patches_002fCommitting" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Patches_002fCommitting" aria-hidden="true">TOC</a></span></h3>
+<a name="Licenses-for-patches-must-be-compatible-with-FFmpeg_002e"></a>
+<p>Contributions should be licensed under the
+<a class="uref" href="http://www.gnu.org/licenses/lgpl-2.1.html">LGPL 2.1</a>,
+including an &quot;or any later version&quot; clause, or, if you prefer
+a gift-style license, the
+<a class="uref" href="http://opensource.org/licenses/isc-license.txt">ISC</a> or
+<a class="uref" href="http://mit-license.org/">MIT</a> license.
+<a class="uref" href="http://www.gnu.org/licenses/gpl-2.0.html">GPL 2</a> including
+an &quot;or any later version&quot; clause is also acceptable, but LGPL is
+preferred.
+If you add a new file, give it a proper license header. Do not copy and
+paste it from a random place, use an existing file as template.
+</p>
+<a name="You-must-not-commit-code-which-breaks-FFmpeg_0021"></a>
+<p>This means unfinished code which is enabled and breaks compilation,
+or compiles but does not work/breaks the regression tests. Code which
+is unfinished but disabled may be permitted under-circumstances, like
+missing samples or an implementation with a small subset of features.
+Always check the mailing list for any reviewers with issues and test
+FATE before you push.
+</p>
+<a name="Commit-messages"></a>
+<p>Commit messages are highly important tools for informing other developers on
+what a given change does and why. Every commit must always have a properly
+filled out commit message with the following format:
+</p><div class="example">
+<pre class="example-preformatted">area changed: short 1 line description
+
+details describing what and why and giving references.
+</pre></div>
+
+<p>If the commit addresses a known bug on our bug tracker or other external issue
+(e.g. CVE), the commit message should include the relevant bug ID(s) or other
+external identifiers. Note that this should be done in addition to a proper
+explanation and not instead of it. Comments such as &quot;fixed!&quot; or &quot;Changed it.&quot;
+are not acceptable.
+</p>
+<p>When applying patches that have been discussed at length on the mailing list,
+reference the thread in the commit message.
+</p>
+<a name="Testing-must-be-adequate-but-not-excessive_002e"></a>
+<p>If it works for you, others, and passes FATE then it should be OK to commit
+it, provided it fits the other committing criteria. You should not worry about
+over-testing things. If your code has problems (portability, triggers
+compiler bugs, unusual environment etc) they will be reported and eventually
+fixed.
+</p>
+<a name="Do-not-commit-unrelated-changes-together_002e"></a>
+<p>They should be split them into self-contained pieces. Also do not forget
+that if part B depends on part A, but A does not depend on B, then A can
+and should be committed first and separate from B. Keeping changes well
+split into self-contained parts makes reviewing and understanding them on
+the commit log mailing list easier. This also helps in case of debugging
+later on.
+Also if you have doubts about splitting or not splitting, do not hesitate to
+ask/discuss it on the developer mailing list.
+</p>
+<a name="Cosmetic-changes-should-be-kept-in-separate-patches_002e"></a>
+<p>We refuse source indentation and other cosmetic changes if they are mixed
+with functional changes, such commits will be rejected and removed. Every
+developer has his own indentation style, you should not change it. Of course
+if you (re)write something, you can use your own style, even though we would
+prefer if the indentation throughout FFmpeg was consistent (Many projects
+force a given indentation style - we do not.). If you really need to make
+indentation changes (try to avoid this), separate them strictly from real
+changes.
+</p>
+<p>NOTE: If you had to put if(){ .. } over a large (&gt; 5 lines) chunk of code,
+then either do NOT change the indentation of the inner part within (do not
+move it to the right)! or do so in a separate commit
+</p>
+<a name="Credit-the-author-of-the-patch_002e"></a>
+<p>Make sure the author of the commit is set correctly. (see git commit &ndash;author)
+If you apply a patch, send an
+answer to ffmpeg-devel (or wherever you got the patch from) saying that
+you applied the patch.
+</p>
+<a name="Credit-any-researchers"></a>
+<p>If a commit/patch fixes an issues found by some researcher, always credit the
+researcher in the commit message for finding/reporting the issue.
+</p>
+<a name="Always-wait-long-enough-before-pushing-changes"></a>
+<p>Do NOT commit to code actively maintained by others without permission.
+Send a patch to ffmpeg-devel. If no one answers within a reasonable
+time-frame (12h for build failures and security fixes, 3 days small changes,
+1 week for big patches) then commit your patch if you think it is OK.
+Also note, the maintainer can simply ask for more time to review!
+</p>
+<a name="Code"></a>
+<h3 class="section">3.3 Code<span class="pull-right"><a class="anchor hidden-xs" href="#Code" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Code" aria-hidden="true">TOC</a></span></h3>
+<a name="Warnings-for-correct-code-may-be-disabled-if-there-is-no-other-option_002e"></a>
+<p>Compiler warnings indicate potential bugs or code with bad style. If a type of
+warning always points to correct and clean code, that warning should
+be disabled, not the code changed.
+Thus the remaining warnings can either be bugs or correct code.
+If it is a bug, the bug has to be fixed. If it is not, the code should
+be changed to not generate a warning unless that causes a slowdown
+or obfuscates the code.
+</p>
+<a name="Library-public-interfaces"></a>
+<h3 class="section">3.4 Library public interfaces<span class="pull-right"><a class="anchor hidden-xs" href="#Library-public-interfaces" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Library-public-interfaces" aria-hidden="true">TOC</a></span></h3>
+<p>Every library in FFmpeg provides a set of public APIs in its installed headers,
+which are those listed in the variable <code class="code">HEADERS</code> in that library&rsquo;s
+<samp class="file">Makefile</samp>. All identifiers defined in those headers (except for those
+explicitly documented otherwise), and corresponding symbols exported from
+compiled shared or static libraries are considered public interfaces and must
+comply with the API and ABI compatibility rules described in this section.
+</p>
+<p>Public APIs must be backward compatible within a given major version. I.e. any
+valid user code that compiles and works with a given library version must still
+compile and work with any later version, as long as the major version number is
+unchanged. &quot;Valid user code&quot; here means code that is calling our APIs in a
+documented and/or intended manner and is not relying on any undefined behavior.
+Incrementing the major version may break backward compatibility, but only to the
+extent described in <a class="ref" href="#Major-version-bumps">Major version bumps</a>.
+</p>
+<p>We also guarantee backward ABI compatibility for shared and static libraries.
+I.e. it should be possible to replace a shared or static build of our library
+with a build of any later version (re-linking the user binary in the static
+case) without breaking any valid user binaries, as long as the major version
+number remains unchanged.
+</p>
+<a name="Adding-new-interfaces"></a>
+<h4 class="subsection">3.4.1 Adding new interfaces<span class="pull-right"><a class="anchor hidden-xs" href="#Adding-new-interfaces" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Adding-new-interfaces" aria-hidden="true">TOC</a></span></h4>
+<p>Any new public identifiers in installed headers are considered new API - this
+includes new functions, structs, macros, enum values, typedefs, new fields in
+existing structs, new installed headers, etc. Consider the following
+guidelines when adding new APIs.
+</p>
+<a name="Motivation"></a>
+<p>While new APIs can be added relatively easily, changing or removing them is much
+harder due to abovementioned compatibility requirements. You should then
+consider carefully whether the functionality you are adding really needs to be
+exposed to our callers as new public API.
+</p>
+<p>Your new API should have at least one well-established use case outside of the
+library that cannot be easily achieved with existing APIs. Every library in
+FFmpeg also has a defined scope - your new API must fit within it.
+</p>
+<a name="Replacing-existing-APIs"></a>
+<p>If your new API is replacing an existing one, it should be strictly superior to
+it, so that the advantages of using the new API outweight the cost to the
+callers of changing their code. After adding the new API you should then
+deprecate the old one and schedule it for removal, as described in
+<a class="ref" href="#Removing-interfaces">Removing interfaces</a>.
+</p>
+<p>If you deem an existing API deficient and want to fix it, the preferred approach
+in most cases is to add a differently-named replacement and deprecate the
+existing API rather than modify it. It is important to make the changes visible
+to our callers (e.g. through compile- or run-time deprecation warnings) and make
+it clear how to transition to the new API (e.g. in the Doxygen documentation or
+on the wiki).
+</p>
+<a name="API-design"></a>
+<p>The FFmpeg libraries are used by a variety of callers to perform a wide range of
+multimedia-related processing tasks. You should therefore - within reason - try
+to design your new API for the broadest feasible set of use cases and avoid
+unnecessarily limiting it to a specific type of callers (e.g. just media
+playback or just transcoding).
+</p>
+<a name="Consistency"></a>
+<p>Check whether similar APIs already exist in FFmpeg. If they do, try to model
+your new addition on them to achieve better overall consistency.
+</p>
+<p>The naming of your new identifiers should follow the <a class="ref" href="#Naming-conventions">Naming conventions</a>
+and be aligned with other similar APIs, if applicable.
+</p>
+<a name="Extensibility"></a>
+<p>You should also consider how your API might be extended in the future in a
+backward-compatible way. If you are adding a new struct <code class="code">AVFoo</code>, the
+standard approach is requiring the caller to always allocate it through a
+constructor function, typically named <code class="code">av_foo_alloc()</code>. This way new fields
+may be added to the end of the struct without breaking ABI compatibility.
+Typically you will also want a destructor - <code class="code">av_foo_free(AVFoo**)</code> that
+frees the indirectly supplied object (and its contents, if applicable) and
+writes <code class="code">NULL</code> to the supplied pointer, thus eliminating the potential
+dangling pointer in the caller&rsquo;s memory.
+</p>
+<p>If you are adding new functions, consider whether it might be desirable to tweak
+their behavior in the future - you may want to add a flags argument, even though
+it would be unused initially.
+</p>
+<a name="Documentation"></a>
+<p>All new APIs must be documented as Doxygen-formatted comments above the
+identifiers you add to the public headers. You should also briefly mention the
+change in <samp class="file">doc/APIchanges</samp>.
+</p>
+<a name="Bump-the-version"></a>
+<p>Backward-incompatible API or ABI changes require incrementing (bumping) the
+major version number, as described in <a class="ref" href="#Major-version-bumps">Major version bumps</a>. Major
+bumps are significant events that happen on a schedule - so if your change
+strictly requires one you should add it under <code class="code">#if</code> preprocesor guards that
+disable it until the next major bump happens.
+</p>
+<p>New APIs that can be added without breaking API or ABI compatibility require
+bumping the minor version number.
+</p>
+<p>Incrementing the third (micro) version component means a noteworthy binary
+compatible change (e.g. encoder bug fix that matters for the decoder). The third
+component always starts at 100 to distinguish FFmpeg from Libav.
+</p>
+<a class="anchor" id="Removing-interfaces"></a><a name="Removing-interfaces-1"></a>
+<h4 class="subsection">3.4.2 Removing interfaces<span class="pull-right"><a class="anchor hidden-xs" href="#Removing-interfaces-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Removing-interfaces-1" aria-hidden="true">TOC</a></span></h4>
+<p>Due to abovementioned compatibility guarantees, removing APIs is an involved
+process that should only be undertaken with good reason. Typically a deficient,
+restrictive, or otherwise inadequate API is replaced by a superior one, though
+it does at times happen that we remove an API without any replacement (e.g. when
+the feature it provides is deemed not worth the maintenance effort, out of scope
+of the project, fundamentally flawed, etc.).
+</p>
+<p>The removal has two steps - first the API is deprecated and scheduled for
+removal, but remains present and functional. The second step is actually
+removing the API - this is described in <a class="ref" href="#Major-version-bumps">Major version bumps</a>.
+</p>
+<p>To deprecate an API you should signal to our users that they should stop using
+it. E.g. if you intend to remove struct members or functions, you should mark
+them with <code class="code">attribute_deprecated</code>. When this cannot be done, it may be
+possible to detect the use of the deprecated API at runtime and print a warning
+(though take care not to print it too often). You should also document the
+deprecation (and the replacement, if applicable) in the relevant Doxygen
+documentation block.
+</p>
+<p>Finally, you should define a deprecation guard along the lines of
+<code class="code">#define FF_API_&lt;FOO&gt; (LIBAVBAR_VERSION_MAJOR &lt; XX)</code> (where XX is the major
+version in which the API will be removed) in <samp class="file">libavbar/version_major.h</samp>
+(<samp class="file">version.h</samp> in case of <code class="code">libavutil</code>). Then wrap all uses of the
+deprecated API in <code class="code">#if FF_API_&lt;FOO&gt; .... #endif</code>, so that the code will
+automatically get disabled once the major version reaches XX. You can also use
+<code class="code">FF_DISABLE_DEPRECATION_WARNINGS</code> and <code class="code">FF_ENABLE_DEPRECATION_WARNINGS</code>
+to suppress compiler deprecation warnings inside these guards. You should test
+that the code compiles and works with the guard macro evaluating to both true
+and false.
+</p>
+<a class="anchor" id="Major-version-bumps"></a><a name="Major-version-bumps-1"></a>
+<h4 class="subsection">3.4.3 Major version bumps<span class="pull-right"><a class="anchor hidden-xs" href="#Major-version-bumps-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Major-version-bumps-1" aria-hidden="true">TOC</a></span></h4>
+<p>A major version bump signifies an API and/or ABI compatibility break. To reduce
+the negative effects on our callers, who are required to adapt their code,
+backward-incompatible changes during a major bump should be limited to:
+</p><ul class="itemize mark-bullet">
+<li>Removing previously deprecated APIs.
+
+</li><li>Performing ABI- but not API-breaking changes, like reordering struct contents.
+</li></ul>
+
+<a name="Documentation_002fOther"></a>
+<h3 class="section">3.5 Documentation/Other<span class="pull-right"><a class="anchor hidden-xs" href="#Documentation_002fOther" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Documentation_002fOther" aria-hidden="true">TOC</a></span></h3>
+<a name="Subscribe-to-the-ffmpeg_002ddevel-mailing-list_002e"></a>
+<p>It is important to be subscribed to the
+<a class="uref" href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel">ffmpeg-devel</a>
+mailing list. Almost any non-trivial patch is to be sent there for review.
+Other developers may have comments about your contribution. We expect you see
+those comments, and to improve it if requested. (N.B. Experienced committers
+have other channels, and may sometimes skip review for trivial fixes.) Also,
+discussion here about bug fixes and FFmpeg improvements by other developers may
+be helpful information for you. Finally, by being a list subscriber, your
+contribution will be posted immediately to the list, without the moderation
+hold which messages from non-subscribers experience.
+</p>
+<p>However, it is more important to the project that we receive your patch than
+that you be subscribed to the ffmpeg-devel list. If you have a patch, and don&rsquo;t
+want to subscribe and discuss the patch, then please do send it to the list
+anyway.
+</p>
+<a name="Subscribe-to-the-ffmpeg_002dcvslog-mailing-list_002e"></a>
+<p>Diffs of all commits are sent to the
+<a class="uref" href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-cvslog">ffmpeg-cvslog</a>
+mailing list. Some developers read this list to review all code base changes
+from all sources. Subscribing to this list is not mandatory.
+</p>
+<a name="Keep-the-documentation-up-to-date_002e"></a>
+<p>Update the documentation if you change behavior or add features. If you are
+unsure how best to do this, send a patch to ffmpeg-devel, the documentation
+maintainer(s) will review and commit your stuff.
+</p>
+<a name="Important-discussions-should-be-accessible-to-all_002e"></a>
+<p>Try to keep important discussions and requests (also) on the public
+developer mailing list, so that all developers can benefit from them.
+</p>
+<a name="Check-your-entries-in-MAINTAINERS_002e"></a>
+<p>Make sure that no parts of the codebase that you maintain are missing from the
+<samp class="file">MAINTAINERS</samp> file. If something that you want to maintain is missing add it with
+your name after it.
+If at some point you no longer want to maintain some code, then please help in
+finding a new maintainer and also don&rsquo;t forget to update the <samp class="file">MAINTAINERS</samp> file.
+</p>
+<p>We think our rules are not too hard. If you have comments, contact us.
+</p>
+<a class="anchor" id="Submitting-patches"></a><a name="Submitting-patches-1"></a>
+<h2 class="chapter">4 Submitting patches<span class="pull-right"><a class="anchor hidden-xs" href="#Submitting-patches-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Submitting-patches-1" aria-hidden="true">TOC</a></span></h2>
+
+<p>First, read the <a class="ref" href="#Coding-Rules">Coding Rules</a> above if you did not yet, in particular
+the rules regarding patch submission.
+</p>
+<p>When you submit your patch, please use <code class="code">git format-patch</code> or
+<code class="code">git send-email</code>. We cannot read other diffs :-).
+</p>
+<p>Also please do not submit a patch which contains several unrelated changes.
+Split it into separate, self-contained pieces. This does not mean splitting
+file by file. Instead, make the patch as small as possible while still
+keeping it as a logical unit that contains an individual change, even
+if it spans multiple files. This makes reviewing your patches much easier
+for us and greatly increases your chances of getting your patch applied.
+</p>
+<p>Use the patcheck tool of FFmpeg to check your patch.
+The tool is located in the tools directory.
+</p>
+<p>Run the <a class="ref" href="#Regression-tests">Regression tests</a> before submitting a patch in order to verify
+it does not cause unexpected problems.
+</p>
+<p>It also helps quite a bit if you tell us what the patch does (for example
+&rsquo;replaces lrint by lrintf&rsquo;), and why (for example &rsquo;*BSD isn&rsquo;t C99 compliant
+and has no lrint()&rsquo;)
+</p>
+<p>Also please if you send several patches, send each patch as a separate mail,
+do not attach several unrelated patches to the same mail.
+</p>
+<p>Patches should be posted to the
+<a class="uref" href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel">ffmpeg-devel</a>
+mailing list. Use <code class="code">git send-email</code> when possible since it will properly
+send patches without requiring extra care. If you cannot, then send patches
+as base64-encoded attachments, so your patch is not trashed during
+transmission. Also ensure the correct mime type is used
+(text/x-diff or text/x-patch or at least text/plain) and that only one
+patch is inline or attached per mail.
+You can check <a class="url" href="https://patchwork.ffmpeg.org">https://patchwork.ffmpeg.org</a>, if your patch does not show up, its mime type
+likely was wrong.
+</p>
+<a name="How-to-setup-git-send_002demail_003f"></a>
+
+<p>Please see <a class="url" href="https://git-send-email.io/">https://git-send-email.io/</a>.
+For gmail additionally see <a class="url" href="https://shallowsky.com/blog/tech/email/gmail-app-passwds.html">https://shallowsky.com/blog/tech/email/gmail-app-passwds.html</a>.
+</p>
+<a name="Sending-patches-from-email-clients"></a>
+<p>Using <code class="code">git send-email</code> might not be desirable for everyone. The
+following trick allows to send patches via email clients in a safe
+way. It has been tested with Outlook and Thunderbird (with X-Unsent
+extension) and might work with other applications.
+</p>
+<p>Create your patch like this:
+</p>
+<pre class="verbatim">git format-patch -s -o &quot;outputfolder&quot; --add-header &quot;X-Unsent: 1&quot; --suffix .eml --to ffmpeg-devel@ffmpeg.org -1 1a2b3c4d
+</pre>
+<p>Now you&rsquo;ll just need to open the eml file with the email application
+and execute &rsquo;Send&rsquo;.
+</p>
+<a name="Reviews"></a>
+<p>Your patch will be reviewed on the mailing list. You will likely be asked
+to make some changes and are expected to send in an improved version that
+incorporates the requests from the review. This process may go through
+several iterations. Once your patch is deemed good enough, some developer
+will pick it up and commit it to the official FFmpeg tree.
+</p>
+<p>Give us a few days to react. But if some time passes without reaction,
+send a reminder by email. Your patch should eventually be dealt with.
+</p>
+
+<a name="New-codecs-or-formats-checklist"></a>
+<h2 class="chapter">5 New codecs or formats checklist<span class="pull-right"><a class="anchor hidden-xs" href="#New-codecs-or-formats-checklist" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-New-codecs-or-formats-checklist" aria-hidden="true">TOC</a></span></h2>
+
+<ol class="enumerate">
+<li> Did you use av_cold for codec initialization and close functions?
+
+</li><li> Did you add a long_name under NULL_IF_CONFIG_SMALL to the AVCodec or
+AVInputFormat/AVOutputFormat struct?
+
+</li><li> Did you bump the minor version number (and reset the micro version
+number) in <samp class="file">libavcodec/version.h</samp> or <samp class="file">libavformat/version.h</samp>?
+
+</li><li> Did you register it in <samp class="file">allcodecs.c</samp> or <samp class="file">allformats.c</samp>?
+
+</li><li> Did you add the AVCodecID to <samp class="file">codec_id.h</samp>?
+When adding new codec IDs, also add an entry to the codec descriptor
+list in <samp class="file">libavcodec/codec_desc.c</samp>.
+
+</li><li> If it has a FourCC, did you add it to <samp class="file">libavformat/riff.c</samp>,
+even if it is only a decoder?
+
+</li><li> Did you add a rule to compile the appropriate files in the Makefile?
+Remember to do this even if you&rsquo;re just adding a format to a file that is
+already being compiled by some other rule, like a raw demuxer.
+
+</li><li> Did you add an entry to the table of supported formats or codecs in
+<samp class="file">doc/general_contents.texi</samp>?
+
+</li><li> Did you add an entry in the Changelog?
+
+</li><li> If it depends on a parser or a library, did you add that dependency in
+configure?
+
+</li><li> Did you <code class="code">git add</code> the appropriate files before committing?
+
+</li><li> Did you make sure it compiles standalone, i.e. with
+<code class="code">configure --disable-everything --enable-decoder=foo</code>
+(or <code class="code">--enable-demuxer</code> or whatever your component is)?
+</li></ol>
+
+
+<a name="Patch-submission-checklist"></a>
+<h2 class="chapter">6 Patch submission checklist<span class="pull-right"><a class="anchor hidden-xs" href="#Patch-submission-checklist" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Patch-submission-checklist" aria-hidden="true">TOC</a></span></h2>
+
+<ol class="enumerate">
+<li> Does <code class="code">make fate</code> pass with the patch applied?
+
+</li><li> Was the patch generated with git format-patch or send-email?
+
+</li><li> Did you sign-off your patch? (<code class="code">git commit -s</code>)
+See <a class="uref" href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/process/submitting-patches.rst">Sign your work</a> for the meaning
+of <em class="dfn">sign-off</em>.
+
+</li><li> Did you provide a clear git commit log message?
+
+</li><li> Is the patch against latest FFmpeg git master branch?
+
+</li><li> Are you subscribed to ffmpeg-devel?
+(the list is subscribers only due to spam)
+
+</li><li> Have you checked that the changes are minimal, so that the same cannot be
+achieved with a smaller patch and/or simpler final code?
+
+</li><li> If the change is to speed critical code, did you benchmark it?
+
+</li><li> If you did any benchmarks, did you provide them in the mail?
+
+</li><li> Have you checked that the patch does not introduce buffer overflows or
+other security issues?
+
+</li><li> Did you test your decoder or demuxer against damaged data? If no, see
+tools/trasher, the noise bitstream filter, and
+<a class="uref" href="http://caca.zoy.org/wiki/zzuf">zzuf</a>. Your decoder or demuxer
+should not crash, end in a (near) infinite loop, or allocate ridiculous
+amounts of memory when fed damaged data.
+
+</li><li> Did you test your decoder or demuxer against sample files?
+Samples may be obtained at <a class="url" href="https://samples.ffmpeg.org">https://samples.ffmpeg.org</a>.
+
+</li><li> Does the patch not mix functional and cosmetic changes?
+
+</li><li> Did you add tabs or trailing whitespace to the code? Both are forbidden.
+
+</li><li> Is the patch attached to the email you send?
+
+</li><li> Is the mime type of the patch correct? It should be text/x-diff or
+text/x-patch or at least text/plain and not application/octet-stream.
+
+</li><li> If the patch fixes a bug, did you provide a verbose analysis of the bug?
+
+</li><li> If the patch fixes a bug, did you provide enough information, including
+a sample, so the bug can be reproduced and the fix can be verified?
+Note please do not attach samples &gt;100k to mails but rather provide a
+URL, you can upload to <a class="url" href="https://streams.videolan.org/upload/">https://streams.videolan.org/upload/</a>.
+
+</li><li> Did you provide a verbose summary about what the patch does change?
+
+</li><li> Did you provide a verbose explanation why it changes things like it does?
+
+</li><li> Did you provide a verbose summary of the user visible advantages and
+disadvantages if the patch is applied?
+
+</li><li> Did you provide an example so we can verify the new feature added by the
+patch easily?
+
+</li><li> If you added a new file, did you insert a license header? It should be
+taken from FFmpeg, not randomly copied and pasted from somewhere else.
+
+</li><li> You should maintain alphabetical order in alphabetically ordered lists as
+long as doing so does not break API/ABI compatibility.
+
+</li><li> Lines with similar content should be aligned vertically when doing so
+improves readability.
+
+</li><li> Consider adding a regression test for your code. All new modules
+should be covered by tests. That includes demuxers, muxers, decoders, encoders
+filters, bitstream filters, parsers. If its not possible to do that, add
+an explanation why to your patchset, its ok to not test if theres a reason.
+
+</li><li> If you added NASM code please check that things still work with &ndash;disable-x86asm.
+
+</li><li> Test your code with valgrind and or Address Sanitizer to ensure it&rsquo;s free
+of leaks, out of array accesses, etc.
+</li></ol>
+
+<a name="Patch-review-process"></a>
+<h2 class="chapter">7 Patch review process<span class="pull-right"><a class="anchor hidden-xs" href="#Patch-review-process" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Patch-review-process" aria-hidden="true">TOC</a></span></h2>
+
+<p>All patches posted to ffmpeg-devel will be reviewed, unless they contain a
+clear note that the patch is not for the git master branch.
+Reviews and comments will be posted as replies to the patch on the
+mailing list. The patch submitter then has to take care of every comment,
+that can be by resubmitting a changed patch or by discussion. Resubmitted
+patches will themselves be reviewed like any other patch. If at some point
+a patch passes review with no comments then it is approved, that can for
+simple and small patches happen immediately while large patches will generally
+have to be changed and reviewed many times before they are approved.
+After a patch is approved it will be committed to the repository.
+</p>
+<p>We will review all submitted patches, but sometimes we are quite busy so
+especially for large patches this can take several weeks.
+</p>
+<p>If you feel that the review process is too slow and you are willing to try to
+take over maintainership of the area of code you change then just clone
+git master and maintain the area of code there. We will merge each area from
+where its best maintained.
+</p>
+<p>When resubmitting patches, please do not make any significant changes
+not related to the comments received during review. Such patches will
+be rejected. Instead, submit significant changes or new features as
+separate patches.
+</p>
+<p>Everyone is welcome to review patches. Also if you are waiting for your patch
+to be reviewed, please consider helping to review other patches, that is a great
+way to get everyone&rsquo;s patches reviewed sooner.
+</p>
+<a class="anchor" id="Regression-tests"></a><a name="Regression-tests-1"></a>
+<h2 class="chapter">8 Regression tests<span class="pull-right"><a class="anchor hidden-xs" href="#Regression-tests-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Regression-tests-1" aria-hidden="true">TOC</a></span></h2>
+
+<p>Before submitting a patch (or committing to the repository), you should at least
+test that you did not break anything.
+</p>
+<p>Running &rsquo;make fate&rsquo; accomplishes this, please see <a class="url" href="fate.html">fate.html</a> for details.
+</p>
+<p>[Of course, some patches may change the results of the regression tests. In
+this case, the reference results of the regression tests shall be modified
+accordingly].
+</p>
+<a name="Adding-files-to-the-fate_002dsuite-dataset"></a>
+<h3 class="section">8.1 Adding files to the fate-suite dataset<span class="pull-right"><a class="anchor hidden-xs" href="#Adding-files-to-the-fate_002dsuite-dataset" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Adding-files-to-the-fate_002dsuite-dataset" aria-hidden="true">TOC</a></span></h3>
+
+<p>If you need a sample uploaded send a mail to samples-request.
+</p>
+<p>When there is no muxer or encoder available to generate test media for a
+specific test then the media has to be included in the fate-suite.
+First please make sure that the sample file is as small as possible to test the
+respective decoder or demuxer sufficiently. Large files increase network
+bandwidth and disk space requirements.
+Once you have a working fate test and fate sample, provide in the commit
+message or introductory message for the patch series that you post to
+the ffmpeg-devel mailing list, a direct link to download the sample media.
+</p>
+<a name="Visualizing-Test-Coverage"></a>
+<h3 class="section">8.2 Visualizing Test Coverage<span class="pull-right"><a class="anchor hidden-xs" href="#Visualizing-Test-Coverage" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Visualizing-Test-Coverage" aria-hidden="true">TOC</a></span></h3>
+
+<p>The FFmpeg build system allows visualizing the test coverage in an easy
+manner with the coverage tools <code class="code">gcov</code>/<code class="code">lcov</code>.  This involves
+the following steps:
+</p>
+<ol class="enumerate">
+<li> Configure to compile with instrumentation enabled:
+    <code class="code">configure --toolchain=gcov</code>.
+
+</li><li> Run your test case, either manually or via FATE. This can be either
+    the full FATE regression suite, or any arbitrary invocation of any
+    front-end tool provided by FFmpeg, in any combination.
+
+</li><li> Run <code class="code">make lcov</code> to generate coverage data in HTML format.
+
+</li><li> View <code class="code">lcov/index.html</code> in your preferred HTML viewer.
+</li></ol>
+
+<p>You can use the command <code class="code">make lcov-reset</code> to reset the coverage
+measurements. You will need to rerun <code class="code">make lcov</code> after running a
+new test.
+</p>
+<a name="Using-Valgrind"></a>
+<h3 class="section">8.3 Using Valgrind<span class="pull-right"><a class="anchor hidden-xs" href="#Using-Valgrind" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Using-Valgrind" aria-hidden="true">TOC</a></span></h3>
+
+<p>The configure script provides a shortcut for using valgrind to spot bugs
+related to memory handling. Just add the option
+<code class="code">--toolchain=valgrind-memcheck</code> or <code class="code">--toolchain=valgrind-massif</code>
+to your configure line, and reasonable defaults will be set for running
+FATE under the supervision of either the <strong class="strong">memcheck</strong> or the
+<strong class="strong">massif</strong> tool of the valgrind suite.
+</p>
+<p>In case you need finer control over how valgrind is invoked, use the
+<code class="code">--target-exec='valgrind &lt;your_custom_valgrind_options&gt;</code> option in
+your configure line instead.
+</p>
+<a class="anchor" id="Maintenance"></a><a name="Maintenance-process"></a>
+<h2 class="chapter">9 Maintenance process<span class="pull-right"><a class="anchor hidden-xs" href="#Maintenance-process" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Maintenance-process" aria-hidden="true">TOC</a></span></h2>
+
+<a class="anchor" id="MAINTAINERS"></a><a name="MAINTAINERS-1"></a>
+<h3 class="section">9.1 MAINTAINERS<span class="pull-right"><a class="anchor hidden-xs" href="#MAINTAINERS-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-MAINTAINERS-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>The developers maintaining each part of the codebase are listed in <samp class="file">MAINTAINERS</samp>.
+Being listed in <samp class="file">MAINTAINERS</samp>, gives one the right to have git write access to
+the specific repository.
+</p>
+<a class="anchor" id="Becoming-a-maintainer"></a><a name="Becoming-a-maintainer-1"></a>
+<h3 class="section">9.2 Becoming a maintainer<span class="pull-right"><a class="anchor hidden-xs" href="#Becoming-a-maintainer-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Becoming-a-maintainer-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>People add themselves to <samp class="file">MAINTAINERS</samp> by sending a patch like any other code
+change. These get reviewed by the community like any other patch. It is expected
+that, if someone has an objection to a new maintainer, she is willing to object
+in public with her full name and is willing to take over maintainership for the area.
+</p>
+
+<a class="anchor" id="Release-process"></a><a name="Release-process-1"></a>
+<h2 class="chapter">10 Release process<span class="pull-right"><a class="anchor hidden-xs" href="#Release-process-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Release-process-1" aria-hidden="true">TOC</a></span></h2>
+
+<p>FFmpeg maintains a set of <strong class="strong">release branches</strong>, which are the
+recommended deliverable for system integrators and distributors (such as
+Linux distributions, etc.). At regular times, a <strong class="strong">release
+manager</strong> prepares, tests and publishes tarballs on the
+<a class="url" href="https://ffmpeg.org">https://ffmpeg.org</a> website.
+</p>
+<p>There are two kinds of releases:
+</p>
+<ol class="enumerate">
+<li> <strong class="strong">Major releases</strong> always include the latest and greatest
+features and functionality.
+
+</li><li> <strong class="strong">Point releases</strong> are cut from <strong class="strong">release</strong> branches,
+which are named <code class="code">release/X</code>, with <code class="code">X</code> being the release
+version number.
+</li></ol>
+
+<p>Note that we promise to our users that shared libraries from any FFmpeg
+release never break programs that have been <strong class="strong">compiled</strong> against
+previous versions of <strong class="strong">the same release series</strong> in any case!
+</p>
+<p>However, from time to time, we do make API changes that require adaptations
+in applications. Such changes are only allowed in (new) major releases and
+require further steps such as bumping library version numbers and/or
+adjustments to the symbol versioning file. Please discuss such changes
+on the <strong class="strong">ffmpeg-devel</strong> mailing list in time to allow forward planning.
+</p>
+<a class="anchor" id="Criteria-for-Point-Releases"></a><a name="Criteria-for-Point-Releases-1"></a>
+<h3 class="section">10.1 Criteria for Point Releases<span class="pull-right"><a class="anchor hidden-xs" href="#Criteria-for-Point-Releases-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Criteria-for-Point-Releases-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>Changes that match the following criteria are valid candidates for
+inclusion into a point release:
+</p>
+<ol class="enumerate">
+<li> Fixes a security issue, preferably identified by a <strong class="strong">CVE
+number</strong> issued by <a class="url" href="http://cve.mitre.org/">http://cve.mitre.org/</a>.
+
+</li><li> Fixes a documented bug in <a class="url" href="https://trac.ffmpeg.org">https://trac.ffmpeg.org</a>.
+
+</li><li> Improves the included documentation.
+
+</li><li> Retains both source code and binary compatibility with previous
+point releases of the same release branch.
+</li></ol>
+
+<p>The order for checking the rules is (1 OR 2 OR 3) AND 4.
+</p>
+
+<a name="Release-Checklist"></a>
+<h3 class="section">10.2 Release Checklist<span class="pull-right"><a class="anchor hidden-xs" href="#Release-Checklist" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Release-Checklist" aria-hidden="true">TOC</a></span></h3>
+
+<p>The release process involves the following steps:
+</p>
+<ol class="enumerate">
+<li> Ensure that the <samp class="file">RELEASE</samp> file contains the version number for
+the upcoming release.
+
+</li><li> Add the release at <a class="url" href="https://trac.ffmpeg.org/admin/ticket/versions">https://trac.ffmpeg.org/admin/ticket/versions</a>.
+
+</li><li> Announce the intent to do a release to the mailing list.
+
+</li><li> Make sure all relevant security fixes have been backported. See
+<a class="url" href="https://ffmpeg.org/security.html">https://ffmpeg.org/security.html</a>.
+
+</li><li> Ensure that the FATE regression suite still passes in the release
+branch on at least <strong class="strong">i386</strong> and <strong class="strong">amd64</strong>
+(cf. <a class="ref" href="#Regression-tests">Regression tests</a>).
+
+</li><li> Prepare the release tarballs in <code class="code">bz2</code> and <code class="code">gz</code> formats, and
+supplementing files that contain <code class="code">gpg</code> signatures
+
+</li><li> Publish the tarballs at <a class="url" href="https://ffmpeg.org/releases">https://ffmpeg.org/releases</a>. Create and
+push an annotated tag in the form <code class="code">nX</code>, with <code class="code">X</code>
+containing the version number.
+
+</li><li> Propose and send a patch to the <strong class="strong">ffmpeg-devel</strong> mailing list
+with a news entry for the website.
+
+</li><li> Publish the news entry.
+
+</li><li> Send an announcement to the mailing list.
+</li></ol>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/faq.html

@@ -0,0 +1,821 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      FFmpeg FAQ
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      FFmpeg FAQ
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-General-Questions" href="#General-Questions">1 General Questions</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Why-doesn_0027t-FFmpeg-support-feature-_005bxyz_005d_003f" href="#Why-doesn_0027t-FFmpeg-support-feature-_005bxyz_005d_003f">1.1 Why doesn&rsquo;t FFmpeg support feature [xyz]?</a></li>
+    <li><a id="toc-FFmpeg-does-not-support-codec-XXX_002e-Can-you-include-a-Windows-DLL-loader-to-support-it_003f" href="#FFmpeg-does-not-support-codec-XXX_002e-Can-you-include-a-Windows-DLL-loader-to-support-it_003f">1.2 FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it?</a></li>
+    <li><a id="toc-I-cannot-read-this-file-although-this-format-seems-to-be-supported-by-ffmpeg_002e" href="#I-cannot-read-this-file-although-this-format-seems-to-be-supported-by-ffmpeg_002e">1.3 I cannot read this file although this format seems to be supported by ffmpeg.</a></li>
+    <li><a id="toc-Which-codecs-are-supported-by-Windows_003f" href="#Which-codecs-are-supported-by-Windows_003f">1.4 Which codecs are supported by Windows?</a></li>
+  </ul></li>
+  <li><a id="toc-Compilation" href="#Compilation">2 Compilation</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-error_003a-can_0027t-find-a-register-in-class-_0027GENERAL_005fREGS_0027-while-reloading-_0027asm_0027" href="#error_003a-can_0027t-find-a-register-in-class-_0027GENERAL_005fREGS_0027-while-reloading-_0027asm_0027">2.1 <code class="code">error: can't find a register in class 'GENERAL_REGS' while reloading 'asm'</code></a></li>
+    <li><a id="toc-I-have-installed-this-library-with-my-distro_0027s-package-manager_002e-Why-does-configure-not-see-it_003f" href="#I-have-installed-this-library-with-my-distro_0027s-package-manager_002e-Why-does-configure-not-see-it_003f">2.2 I have installed this library with my distro&rsquo;s package manager. Why does <code class="command">configure</code> not see it?</a></li>
+    <li><a id="toc-How-do-I-make-pkg_002dconfig-find-my-libraries_003f" href="#How-do-I-make-pkg_002dconfig-find-my-libraries_003f">2.3 How do I make <code class="command">pkg-config</code> find my libraries?</a></li>
+    <li><a id="toc-How-do-I-use-pkg_002dconfig-when-cross_002dcompiling_003f" href="#How-do-I-use-pkg_002dconfig-when-cross_002dcompiling_003f">2.4 How do I use <code class="command">pkg-config</code> when cross-compiling?</a></li>
+  </ul></li>
+  <li><a id="toc-Usage" href="#Usage">3 Usage</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-ffmpeg-does-not-work_003b-what-is-wrong_003f" href="#ffmpeg-does-not-work_003b-what-is-wrong_003f">3.1 ffmpeg does not work; what is wrong?</a></li>
+    <li><a id="toc-How-do-I-encode-single-pictures-into-movies_003f" href="#How-do-I-encode-single-pictures-into-movies_003f">3.2 How do I encode single pictures into movies?</a></li>
+    <li><a id="toc-How-do-I-encode-movie-to-single-pictures_003f" href="#How-do-I-encode-movie-to-single-pictures_003f">3.3 How do I encode movie to single pictures?</a></li>
+    <li><a id="toc-Why-do-I-see-a-slight-quality-degradation-with-multithreaded-MPEG_002a-encoding_003f" href="#Why-do-I-see-a-slight-quality-degradation-with-multithreaded-MPEG_002a-encoding_003f">3.4 Why do I see a slight quality degradation with multithreaded MPEG* encoding?</a></li>
+    <li><a id="toc-How-can-I-read-from-the-standard-input-or-write-to-the-standard-output_003f" href="#How-can-I-read-from-the-standard-input-or-write-to-the-standard-output_003f">3.5 How can I read from the standard input or write to the standard output?</a></li>
+    <li><a id="toc-_002df-jpeg-doesn_0027t-work_002e" href="#g_t_002df-jpeg-doesn_0027t-work_002e">3.6 -f jpeg doesn&rsquo;t work.</a></li>
+    <li><a id="toc-Why-can-I-not-change-the-frame-rate_003f" href="#Why-can-I-not-change-the-frame-rate_003f">3.7 Why can I not change the frame rate?</a></li>
+    <li><a id="toc-How-do-I-encode-Xvid-or-DivX-video-with-ffmpeg_003f" href="#How-do-I-encode-Xvid-or-DivX-video-with-ffmpeg_003f">3.8 How do I encode Xvid or DivX video with ffmpeg?</a></li>
+    <li><a id="toc-Which-are-good-parameters-for-encoding-high-quality-MPEG_002d4_003f" href="#Which-are-good-parameters-for-encoding-high-quality-MPEG_002d4_003f">3.9 Which are good parameters for encoding high quality MPEG-4?</a></li>
+    <li><a id="toc-Which-are-good-parameters-for-encoding-high-quality-MPEG_002d1_002fMPEG_002d2_003f" href="#Which-are-good-parameters-for-encoding-high-quality-MPEG_002d1_002fMPEG_002d2_003f">3.10 Which are good parameters for encoding high quality MPEG-1/MPEG-2?</a></li>
+    <li><a id="toc-Interlaced-video-looks-very-bad-when-encoded-with-ffmpeg_002c-what-is-wrong_003f" href="#Interlaced-video-looks-very-bad-when-encoded-with-ffmpeg_002c-what-is-wrong_003f">3.11 Interlaced video looks very bad when encoded with ffmpeg, what is wrong?</a></li>
+    <li><a id="toc-How-can-I-read-DirectShow-files_003f" href="#How-can-I-read-DirectShow-files_003f">3.12 How can I read DirectShow files?</a></li>
+    <li><a id="toc-How-can-I-join-video-files_003f" href="#How-can-I-join-video-files_003f">3.13 How can I join video files?</a></li>
+    <li><a id="toc-How-can-I-concatenate-video-files_003f" href="#How-can-I-concatenate-video-files_003f">3.14 How can I concatenate video files?</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-Concatenating-using-the-concat-filter" href="#Concatenating-using-the-concat-filter">3.14.1 Concatenating using the concat <em class="emph">filter</em></a></li>
+      <li><a id="toc-Concatenating-using-the-concat-demuxer" href="#Concatenating-using-the-concat-demuxer">3.14.2 Concatenating using the concat <em class="emph">demuxer</em></a></li>
+      <li><a id="toc-Concatenating-using-the-concat-protocol-_0028file-level_0029" href="#Concatenating-using-the-concat-protocol-_0028file-level_0029">3.14.3 Concatenating using the concat <em class="emph">protocol</em> (file level)</a></li>
+      <li><a id="toc-Concatenating-using-raw-audio-and-video" href="#Concatenating-using-raw-audio-and-video">3.14.4 Concatenating using raw audio and video</a></li>
+    </ul></li>
+    <li><a id="toc-Using-_002df-lavfi_002c-audio-becomes-mono-for-no-apparent-reason_002e" href="#Using-_002df-lavfi_002c-audio-becomes-mono-for-no-apparent-reason_002e">3.15 Using <samp class="option">-f lavfi</samp>, audio becomes mono for no apparent reason.</a></li>
+    <li><a id="toc-Why-does-FFmpeg-not-see-the-subtitles-in-my-VOB-file_003f" href="#Why-does-FFmpeg-not-see-the-subtitles-in-my-VOB-file_003f">3.16 Why does FFmpeg not see the subtitles in my VOB file?</a></li>
+    <li><a id="toc-Why-was-the-ffmpeg-_002dsameq-option-removed_003f-What-to-use-instead_003f" href="#Why-was-the-ffmpeg-_002dsameq-option-removed_003f-What-to-use-instead_003f">3.17 Why was the <code class="command">ffmpeg</code> <samp class="option">-sameq</samp> option removed? What to use instead?</a></li>
+    <li><a id="toc-I-have-a-stretched-video_002c-why-does-scaling-not-fix-it_003f" href="#I-have-a-stretched-video_002c-why-does-scaling-not-fix-it_003f">3.18 I have a stretched video, why does scaling not fix it?</a></li>
+    <li><a id="toc-How-do-I-run-ffmpeg-as-a-background-task_003f" href="#How-do-I-run-ffmpeg-as-a-background-task_003f">3.19 How do I run ffmpeg as a background task?</a></li>
+    <li><a id="toc-How-do-I-prevent-ffmpeg-from-suspending-with-a-message-like-suspended-_0028tty-output_0029_003f" href="#How-do-I-prevent-ffmpeg-from-suspending-with-a-message-like-suspended-_0028tty-output_0029_003f">3.20 How do I prevent ffmpeg from suspending with a message like <em class="emph">suspended (tty output)</em>?</a></li>
+  </ul></li>
+  <li><a id="toc-Development" href="#Development">4 Development</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Are-there-examples-illustrating-how-to-use-the-FFmpeg-libraries_002c-particularly-libavcodec-and-libavformat_003f" href="#Are-there-examples-illustrating-how-to-use-the-FFmpeg-libraries_002c-particularly-libavcodec-and-libavformat_003f">4.1 Are there examples illustrating how to use the FFmpeg libraries, particularly libavcodec and libavformat?</a></li>
+    <li><a id="toc-Can-you-support-my-C-compiler-XXX_003f" href="#Can-you-support-my-C-compiler-XXX_003f">4.2 Can you support my C compiler XXX?</a></li>
+    <li><a id="toc-Is-Microsoft-Visual-C_002b_002b-supported_003f" href="#Is-Microsoft-Visual-C_002b_002b-supported_003f">4.3 Is Microsoft Visual C++ supported?</a></li>
+    <li><a id="toc-Can-you-add-automake_002c-libtool-or-autoconf-support_003f" href="#Can-you-add-automake_002c-libtool-or-autoconf-support_003f">4.4 Can you add automake, libtool or autoconf support?</a></li>
+    <li><a id="toc-Why-not-rewrite-FFmpeg-in-object_002doriented-C_002b_002b_003f" href="#Why-not-rewrite-FFmpeg-in-object_002doriented-C_002b_002b_003f">4.5 Why not rewrite FFmpeg in object-oriented C++?</a></li>
+    <li><a id="toc-Why-are-the-ffmpeg-programs-devoid-of-debugging-symbols_003f" href="#Why-are-the-ffmpeg-programs-devoid-of-debugging-symbols_003f">4.6 Why are the ffmpeg programs devoid of debugging symbols?</a></li>
+    <li><a id="toc-I-do-not-like-the-LGPL_002c-can-I-contribute-code-under-the-GPL-instead_003f" href="#I-do-not-like-the-LGPL_002c-can-I-contribute-code-under-the-GPL-instead_003f">4.7 I do not like the LGPL, can I contribute code under the GPL instead?</a></li>
+    <li><a id="toc-I_0027m-using-FFmpeg-from-within-my-C-application-but-the-linker-complains-about-missing-symbols-from-the-libraries-themselves_002e" href="#I_0027m-using-FFmpeg-from-within-my-C-application-but-the-linker-complains-about-missing-symbols-from-the-libraries-themselves_002e">4.8 I&rsquo;m using FFmpeg from within my C application but the linker complains about missing symbols from the libraries themselves.</a></li>
+    <li><a id="toc-I_0027m-using-FFmpeg-from-within-my-C_002b_002b-application-but-the-linker-complains-about-missing-symbols-which-seem-to-be-available_002e" href="#I_0027m-using-FFmpeg-from-within-my-C_002b_002b-application-but-the-linker-complains-about-missing-symbols-which-seem-to-be-available_002e">4.9 I&rsquo;m using FFmpeg from within my C++ application but the linker complains about missing symbols which seem to be available.</a></li>
+    <li><a id="toc-I_0027m-using-libavutil-from-within-my-C_002b_002b-application-but-the-compiler-complains-about-_0027UINT64_005fC_0027-was-not-declared-in-this-scope" href="#I_0027m-using-libavutil-from-within-my-C_002b_002b-application-but-the-compiler-complains-about-_0027UINT64_005fC_0027-was-not-declared-in-this-scope">4.10 I&rsquo;m using libavutil from within my C++ application but the compiler complains about &rsquo;UINT64_C&rsquo; was not declared in this scope</a></li>
+    <li><a id="toc-I-have-a-file-in-memory-_002f-a-API-different-from-_002aopen_002f_002aread_002f-libc-how-do-I-use-it-with-libavformat_003f" href="#I-have-a-file-in-memory-_002f-a-API-different-from-_002aopen_002f_002aread_002f-libc-how-do-I-use-it-with-libavformat_003f">4.11 I have a file in memory / a API different from *open/*read/ libc how do I use it with libavformat?</a></li>
+    <li><a id="toc-Where-is-the-documentation-about-ffv1_002c-msmpeg4_002c-asv1_002c-4xm_003f" href="#Where-is-the-documentation-about-ffv1_002c-msmpeg4_002c-asv1_002c-4xm_003f">4.12 Where is the documentation about ffv1, msmpeg4, asv1, 4xm?</a></li>
+    <li><a id="toc-How-do-I-feed-H_002e263_002dRTP-_0028and-other-codecs-in-RTP_0029-to-libavcodec_003f" href="#How-do-I-feed-H_002e263_002dRTP-_0028and-other-codecs-in-RTP_0029-to-libavcodec_003f">4.13 How do I feed H.263-RTP (and other codecs in RTP) to libavcodec?</a></li>
+    <li><a id="toc-AVStream_002er_005fframe_005frate-is-wrong_002c-it-is-much-larger-than-the-frame-rate_002e" href="#AVStream_002er_005fframe_005frate-is-wrong_002c-it-is-much-larger-than-the-frame-rate_002e">4.14 AVStream.r_frame_rate is wrong, it is much larger than the frame rate.</a></li>
+    <li><a id="toc-Why-is-make-fate-not-running-all-tests_003f" href="#Why-is-make-fate-not-running-all-tests_003f">4.15 Why is <code class="code">make fate</code> not running all tests?</a></li>
+    <li><a id="toc-Why-is-make-fate-not-finding-the-samples_003f" href="#Why-is-make-fate-not-finding-the-samples_003f">4.16 Why is <code class="code">make fate</code> not finding the samples?</a></li>
+  </ul></li>
+</ul>
+</div>
+</div>
+
+<a name="General-Questions"></a>
+<h2 class="chapter">1 General Questions<span class="pull-right"><a class="anchor hidden-xs" href="#General-Questions" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-General-Questions" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Why-doesn_0027t-FFmpeg-support-feature-_005bxyz_005d_003f"></a>
+<h3 class="section">1.1 Why doesn&rsquo;t FFmpeg support feature [xyz]?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-doesn_0027t-FFmpeg-support-feature-_005bxyz_005d_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-doesn_0027t-FFmpeg-support-feature-_005bxyz_005d_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Because no one has taken on that task yet. FFmpeg development is
+driven by the tasks that are important to the individual developers.
+If there is a feature that is important to you, the best way to get
+it implemented is to undertake the task yourself or sponsor a developer.
+</p>
+<a name="FFmpeg-does-not-support-codec-XXX_002e-Can-you-include-a-Windows-DLL-loader-to-support-it_003f"></a>
+<h3 class="section">1.2 FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it?<span class="pull-right"><a class="anchor hidden-xs" href="#FFmpeg-does-not-support-codec-XXX_002e-Can-you-include-a-Windows-DLL-loader-to-support-it_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-FFmpeg-does-not-support-codec-XXX_002e-Can-you-include-a-Windows-DLL-loader-to-support-it_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>No. Windows DLLs are not portable, bloated and often slow.
+Moreover FFmpeg strives to support all codecs natively.
+A DLL loader is not conducive to that goal.
+</p>
+<a name="I-cannot-read-this-file-although-this-format-seems-to-be-supported-by-ffmpeg_002e"></a>
+<h3 class="section">1.3 I cannot read this file although this format seems to be supported by ffmpeg.<span class="pull-right"><a class="anchor hidden-xs" href="#I-cannot-read-this-file-although-this-format-seems-to-be-supported-by-ffmpeg_002e" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-I-cannot-read-this-file-although-this-format-seems-to-be-supported-by-ffmpeg_002e" aria-hidden="true">TOC</a></span></h3>
+
+<p>Even if ffmpeg can read the container format, it may not support all its
+codecs. Please consult the supported codec list in the ffmpeg
+documentation.
+</p>
+<a name="Which-codecs-are-supported-by-Windows_003f"></a>
+<h3 class="section">1.4 Which codecs are supported by Windows?<span class="pull-right"><a class="anchor hidden-xs" href="#Which-codecs-are-supported-by-Windows_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Which-codecs-are-supported-by-Windows_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Windows does not support standard formats like MPEG very well, unless you
+install some additional codecs.
+</p>
+<p>The following list of video codecs should work on most Windows systems:
+</p><dl class="table">
+<dt><samp class="option">msmpeg4v2</samp></dt>
+<dd><p>.avi/.asf
+</p></dd>
+<dt><samp class="option">msmpeg4</samp></dt>
+<dd><p>.asf only
+</p></dd>
+<dt><samp class="option">wmv1</samp></dt>
+<dd><p>.asf only
+</p></dd>
+<dt><samp class="option">wmv2</samp></dt>
+<dd><p>.asf only
+</p></dd>
+<dt><samp class="option">mpeg4</samp></dt>
+<dd><p>Only if you have some MPEG-4 codec like ffdshow or Xvid installed.
+</p></dd>
+<dt><samp class="option">mpeg1video</samp></dt>
+<dd><p>.mpg only
+</p></dd>
+</dl>
+<p>Note, ASF files often have .wmv or .wma extensions in Windows. It should also
+be mentioned that Microsoft claims a patent on the ASF format, and may sue
+or threaten users who create ASF files with non-Microsoft software. It is
+strongly advised to avoid ASF where possible.
+</p>
+<p>The following list of audio codecs should work on most Windows systems:
+</p><dl class="table">
+<dt><samp class="option">adpcm_ima_wav</samp></dt>
+<dt><samp class="option">adpcm_ms</samp></dt>
+<dt><samp class="option">pcm_s16le</samp></dt>
+<dd><p>always
+</p></dd>
+<dt><samp class="option">libmp3lame</samp></dt>
+<dd><p>If some MP3 codec like LAME is installed.
+</p></dd>
+</dl>
+
+
+<a name="Compilation"></a>
+<h2 class="chapter">2 Compilation<span class="pull-right"><a class="anchor hidden-xs" href="#Compilation" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Compilation" aria-hidden="true">TOC</a></span></h2>
+
+<a name="error_003a-can_0027t-find-a-register-in-class-_0027GENERAL_005fREGS_0027-while-reloading-_0027asm_0027"></a>
+<h3 class="section">2.1 <code class="code">error: can't find a register in class 'GENERAL_REGS' while reloading 'asm'</code><span class="pull-right"><a class="anchor hidden-xs" href="#error_003a-can_0027t-find-a-register-in-class-_0027GENERAL_005fREGS_0027-while-reloading-_0027asm_0027" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-error_003a-can_0027t-find-a-register-in-class-_0027GENERAL_005fREGS_0027-while-reloading-_0027asm_0027" aria-hidden="true">TOC</a></span></h3>
+
+<p>This is a bug in gcc. Do not report it to us. Instead, please report it to
+the gcc developers. Note that we will not add workarounds for gcc bugs.
+</p>
+<p>Also note that (some of) the gcc developers believe this is not a bug or
+not a bug they should fix:
+<a class="url" href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11203">https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11203</a>.
+Then again, some of them do not know the difference between an undecidable
+problem and an NP-hard problem...
+</p>
+<a name="I-have-installed-this-library-with-my-distro_0027s-package-manager_002e-Why-does-configure-not-see-it_003f"></a>
+<h3 class="section">2.2 I have installed this library with my distro&rsquo;s package manager. Why does <code class="command">configure</code> not see it?<span class="pull-right"><a class="anchor hidden-xs" href="#I-have-installed-this-library-with-my-distro_0027s-package-manager_002e-Why-does-configure-not-see-it_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-I-have-installed-this-library-with-my-distro_0027s-package-manager_002e-Why-does-configure-not-see-it_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Distributions usually split libraries in several packages. The main package
+contains the files necessary to run programs using the library. The
+development package contains the files necessary to build programs using the
+library. Sometimes, docs and/or data are in a separate package too.
+</p>
+<p>To build FFmpeg, you need to install the development package. It is usually
+called <samp class="file">libfoo-dev</samp> or <samp class="file">libfoo-devel</samp>. You can remove it after the
+build is finished, but be sure to keep the main package.
+</p>
+<a name="How-do-I-make-pkg_002dconfig-find-my-libraries_003f"></a>
+<h3 class="section">2.3 How do I make <code class="command">pkg-config</code> find my libraries?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-make-pkg_002dconfig-find-my-libraries_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-make-pkg_002dconfig-find-my-libraries_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Somewhere along with your libraries, there is a <samp class="file">.pc</samp> file (or several)
+in a <samp class="file">pkgconfig</samp> directory. You need to set environment variables to
+point <code class="command">pkg-config</code> to these files.
+</p>
+<p>If you need to <em class="emph">add</em> directories to <code class="command">pkg-config</code>&rsquo;s search list
+(typical use case: library installed separately), add it to
+<code class="code">$PKG_CONFIG_PATH</code>:
+</p>
+<div class="example">
+<pre class="example-preformatted">export PKG_CONFIG_PATH=/opt/x264/lib/pkgconfig:/opt/opus/lib/pkgconfig
+</pre></div>
+
+<p>If you need to <em class="emph">replace</em> <code class="command">pkg-config</code>&rsquo;s search list
+(typical use case: cross-compiling), set it in
+<code class="code">$PKG_CONFIG_LIBDIR</code>:
+</p>
+<div class="example">
+<pre class="example-preformatted">export PKG_CONFIG_LIBDIR=/home/me/cross/usr/lib/pkgconfig:/home/me/cross/usr/local/lib/pkgconfig
+</pre></div>
+
+<p>If you need to know the library&rsquo;s internal dependencies (typical use: static
+linking), add the <code class="code">--static</code> option to <code class="command">pkg-config</code>:
+</p>
+<div class="example">
+<pre class="example-preformatted">./configure --pkg-config-flags=--static
+</pre></div>
+
+<a name="How-do-I-use-pkg_002dconfig-when-cross_002dcompiling_003f"></a>
+<h3 class="section">2.4 How do I use <code class="command">pkg-config</code> when cross-compiling?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-use-pkg_002dconfig-when-cross_002dcompiling_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-use-pkg_002dconfig-when-cross_002dcompiling_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>The best way is to install <code class="command">pkg-config</code> in your cross-compilation
+environment. It will automatically use the cross-compilation libraries.
+</p>
+<p>You can also use <code class="command">pkg-config</code> from the host environment by
+specifying explicitly <code class="code">--pkg-config=pkg-config</code> to <code class="command">configure</code>.
+In that case, you must point <code class="command">pkg-config</code> to the correct directories
+using the <code class="code">PKG_CONFIG_LIBDIR</code>, as explained in the previous entry.
+</p>
+<p>As an intermediate solution, you can place in your cross-compilation
+environment a script that calls the host <code class="command">pkg-config</code> with
+<code class="code">PKG_CONFIG_LIBDIR</code> set. That script can look like that:
+</p>
+<div class="example">
+<pre class="example-preformatted">#!/bin/sh
+PKG_CONFIG_LIBDIR=/path/to/cross/lib/pkgconfig
+export PKG_CONFIG_LIBDIR
+exec /usr/bin/pkg-config &quot;$@&quot;
+</pre></div>
+
+<a name="Usage"></a>
+<h2 class="chapter">3 Usage<span class="pull-right"><a class="anchor hidden-xs" href="#Usage" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Usage" aria-hidden="true">TOC</a></span></h2>
+
+<a name="ffmpeg-does-not-work_003b-what-is-wrong_003f"></a>
+<h3 class="section">3.1 ffmpeg does not work; what is wrong?<span class="pull-right"><a class="anchor hidden-xs" href="#ffmpeg-does-not-work_003b-what-is-wrong_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-ffmpeg-does-not-work_003b-what-is-wrong_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Try a <code class="code">make distclean</code> in the ffmpeg source directory before the build.
+If this does not help see
+(<a class="url" href="https://ffmpeg.org/bugreports.html">https://ffmpeg.org/bugreports.html</a>).
+</p>
+<a name="How-do-I-encode-single-pictures-into-movies_003f"></a>
+<h3 class="section">3.2 How do I encode single pictures into movies?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-encode-single-pictures-into-movies_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-encode-single-pictures-into-movies_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>First, rename your pictures to follow a numerical sequence.
+For example, img1.jpg, img2.jpg, img3.jpg,...
+Then you may run:
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -f image2 -i img%d.jpg /tmp/a.mpg
+</pre></div>
+
+<p>Notice that &lsquo;<samp class="samp">%d</samp>&rsquo; is replaced by the image number.
+</p>
+<p><samp class="file">img%03d.jpg</samp> means the sequence <samp class="file">img001.jpg</samp>, <samp class="file">img002.jpg</samp>, etc.
+</p>
+<p>Use the <samp class="option">-start_number</samp> option to declare a starting number for
+the sequence. This is useful if your sequence does not start with
+<samp class="file">img001.jpg</samp> but is still in a numerical order. The following
+example will start with <samp class="file">img100.jpg</samp>:
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -f image2 -start_number 100 -i img%d.jpg /tmp/a.mpg
+</pre></div>
+
+<p>If you have large number of pictures to rename, you can use the
+following command to ease the burden. The command, using the bourne
+shell syntax, symbolically links all files in the current directory
+that match <code class="code">*jpg</code> to the <samp class="file">/tmp</samp> directory in the sequence of
+<samp class="file">img001.jpg</samp>, <samp class="file">img002.jpg</samp> and so on.
+</p>
+<div class="example">
+<pre class="example-preformatted">x=1; for i in *jpg; do counter=$(printf %03d $x); ln -s &quot;$i&quot; /tmp/img&quot;$counter&quot;.jpg; x=$(($x+1)); done
+</pre></div>
+
+<p>If you want to sequence them by oldest modified first, substitute
+<code class="code">$(ls -r -t *jpg)</code> in place of <code class="code">*jpg</code>.
+</p>
+<p>Then run:
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -f image2 -i /tmp/img%03d.jpg /tmp/a.mpg
+</pre></div>
+
+<p>The same logic is used for any image format that ffmpeg reads.
+</p>
+<p>You can also use <code class="command">cat</code> to pipe images to ffmpeg:
+</p>
+<div class="example">
+<pre class="example-preformatted">cat *.jpg | ffmpeg -f image2pipe -c:v mjpeg -i - output.mpg
+</pre></div>
+
+<a name="How-do-I-encode-movie-to-single-pictures_003f"></a>
+<h3 class="section">3.3 How do I encode movie to single pictures?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-encode-movie-to-single-pictures_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-encode-movie-to-single-pictures_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Use:
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i movie.mpg movie%d.jpg
+</pre></div>
+
+<p>The <samp class="file">movie.mpg</samp> used as input will be converted to
+<samp class="file">movie1.jpg</samp>, <samp class="file">movie2.jpg</samp>, etc...
+</p>
+<p>Instead of relying on file format self-recognition, you may also use
+</p><dl class="table">
+<dt><samp class="option">-c:v ppm</samp></dt>
+<dt><samp class="option">-c:v png</samp></dt>
+<dt><samp class="option">-c:v mjpeg</samp></dt>
+</dl>
+<p>to force the encoding.
+</p>
+<p>Applying that to the previous example:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i movie.mpg -f image2 -c:v mjpeg menu%d.jpg
+</pre></div>
+
+<p>Beware that there is no &quot;jpeg&quot; codec. Use &quot;mjpeg&quot; instead.
+</p>
+<a name="Why-do-I-see-a-slight-quality-degradation-with-multithreaded-MPEG_002a-encoding_003f"></a>
+<h3 class="section">3.4 Why do I see a slight quality degradation with multithreaded MPEG* encoding?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-do-I-see-a-slight-quality-degradation-with-multithreaded-MPEG_002a-encoding_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-do-I-see-a-slight-quality-degradation-with-multithreaded-MPEG_002a-encoding_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>For multithreaded MPEG* encoding, the encoded slices must be independent,
+otherwise thread n would practically have to wait for n-1 to finish, so it&rsquo;s
+quite logical that there is a small reduction of quality. This is not a bug.
+</p>
+<a name="How-can-I-read-from-the-standard-input-or-write-to-the-standard-output_003f"></a>
+<h3 class="section">3.5 How can I read from the standard input or write to the standard output?<span class="pull-right"><a class="anchor hidden-xs" href="#How-can-I-read-from-the-standard-input-or-write-to-the-standard-output_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-can-I-read-from-the-standard-input-or-write-to-the-standard-output_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Use <samp class="file">-</samp> as file name.
+</p>
+<a name="g_t_002df-jpeg-doesn_0027t-work_002e"></a>
+<h3 class="section">3.6 -f jpeg doesn&rsquo;t work.<span class="pull-right"><a class="anchor hidden-xs" href="#_002df-jpeg-doesn_0027t-work_002e" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-_002df-jpeg-doesn_0027t-work_002e" aria-hidden="true">TOC</a></span></h3>
+
+<p>Try &rsquo;-f image2 test%d.jpg&rsquo;.
+</p>
+<a name="Why-can-I-not-change-the-frame-rate_003f"></a>
+<h3 class="section">3.7 Why can I not change the frame rate?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-can-I-not-change-the-frame-rate_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-can-I-not-change-the-frame-rate_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Some codecs, like MPEG-1/2, only allow a small number of fixed frame rates.
+Choose a different codec with the -c:v command line option.
+</p>
+<a name="How-do-I-encode-Xvid-or-DivX-video-with-ffmpeg_003f"></a>
+<h3 class="section">3.8 How do I encode Xvid or DivX video with ffmpeg?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-encode-Xvid-or-DivX-video-with-ffmpeg_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-encode-Xvid-or-DivX-video-with-ffmpeg_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Both Xvid and DivX (version 4+) are implementations of the ISO MPEG-4
+standard (note that there are many other coding formats that use this
+same standard). Thus, use &rsquo;-c:v mpeg4&rsquo; to encode in these formats. The
+default fourcc stored in an MPEG-4-coded file will be &rsquo;FMP4&rsquo;. If you want
+a different fourcc, use the &rsquo;-vtag&rsquo; option. E.g., &rsquo;-vtag xvid&rsquo; will
+force the fourcc &rsquo;xvid&rsquo; to be stored as the video fourcc rather than the
+default.
+</p>
+<a name="Which-are-good-parameters-for-encoding-high-quality-MPEG_002d4_003f"></a>
+<h3 class="section">3.9 Which are good parameters for encoding high quality MPEG-4?<span class="pull-right"><a class="anchor hidden-xs" href="#Which-are-good-parameters-for-encoding-high-quality-MPEG_002d4_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Which-are-good-parameters-for-encoding-high-quality-MPEG_002d4_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>&rsquo;-mbd rd -flags +mv4+aic -trellis 2 -cmp 2 -subcmp 2 -g 300 -pass 1/2&rsquo;,
+things to try: &rsquo;-bf 2&rsquo;, &rsquo;-mpv_flags qp_rd&rsquo;, &rsquo;-mpv_flags mv0&rsquo;, &rsquo;-mpv_flags skip_rd&rsquo;.
+</p>
+<a name="Which-are-good-parameters-for-encoding-high-quality-MPEG_002d1_002fMPEG_002d2_003f"></a>
+<h3 class="section">3.10 Which are good parameters for encoding high quality MPEG-1/MPEG-2?<span class="pull-right"><a class="anchor hidden-xs" href="#Which-are-good-parameters-for-encoding-high-quality-MPEG_002d1_002fMPEG_002d2_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Which-are-good-parameters-for-encoding-high-quality-MPEG_002d1_002fMPEG_002d2_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>&rsquo;-mbd rd -trellis 2 -cmp 2 -subcmp 2 -g 100 -pass 1/2&rsquo;
+but beware the &rsquo;-g 100&rsquo; might cause problems with some decoders.
+Things to try: &rsquo;-bf 2&rsquo;, &rsquo;-mpv_flags qp_rd&rsquo;, &rsquo;-mpv_flags mv0&rsquo;, &rsquo;-mpv_flags skip_rd&rsquo;.
+</p>
+<a name="Interlaced-video-looks-very-bad-when-encoded-with-ffmpeg_002c-what-is-wrong_003f"></a>
+<h3 class="section">3.11 Interlaced video looks very bad when encoded with ffmpeg, what is wrong?<span class="pull-right"><a class="anchor hidden-xs" href="#Interlaced-video-looks-very-bad-when-encoded-with-ffmpeg_002c-what-is-wrong_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Interlaced-video-looks-very-bad-when-encoded-with-ffmpeg_002c-what-is-wrong_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>You should use &rsquo;-flags +ilme+ildct&rsquo; and maybe &rsquo;-flags +alt&rsquo; for interlaced
+material, and try &rsquo;-top 0/1&rsquo; if the result looks really messed-up.
+</p>
+<a name="How-can-I-read-DirectShow-files_003f"></a>
+<h3 class="section">3.12 How can I read DirectShow files?<span class="pull-right"><a class="anchor hidden-xs" href="#How-can-I-read-DirectShow-files_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-can-I-read-DirectShow-files_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>If you have built FFmpeg with <code class="code">./configure --enable-avisynth</code>
+(only possible on MinGW/Cygwin platforms),
+then you may use any file that DirectShow can read as input.
+</p>
+<p>Just create an &quot;input.avs&quot; text file with this single line ...
+</p><div class="example">
+<pre class="example-preformatted">DirectShowSource(&quot;C:\path to your file\yourfile.asf&quot;)
+</pre></div>
+<p>... and then feed that text file to ffmpeg:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i input.avs
+</pre></div>
+
+<p>For ANY other help on AviSynth, please visit the
+<a class="uref" href="http://www.avisynth.org/">AviSynth homepage</a>.
+</p>
+<a name="How-can-I-join-video-files_003f"></a>
+<h3 class="section">3.13 How can I join video files?<span class="pull-right"><a class="anchor hidden-xs" href="#How-can-I-join-video-files_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-can-I-join-video-files_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>To &quot;join&quot; video files is quite ambiguous. The following list explains the
+different kinds of &quot;joining&quot; and points out how those are addressed in
+FFmpeg. To join video files may mean:
+</p>
+<ul class="itemize mark-bullet">
+<li>To put them one after the other: this is called to <em class="emph">concatenate</em> them
+(in short: concat) and is addressed
+<a class="ref" href="#How-can-I-concatenate-video-files">in this very faq</a>.
+
+</li><li>To put them together in the same file, to let the user choose between the
+different versions (example: different audio languages): this is called to
+<em class="emph">multiplex</em> them together (in short: mux), and is done by simply
+invoking ffmpeg with several <samp class="option">-i</samp> options.
+
+</li><li>For audio, to put all channels together in a single stream (example: two
+mono streams into one stereo stream): this is sometimes called to
+<em class="emph">merge</em> them, and can be done using the
+<a class="url" href="ffmpeg-filters.html#amerge"><code class="code">amerge</code></a> filter.
+
+</li><li>For audio, to play one on top of the other: this is called to <em class="emph">mix</em>
+them, and can be done by first merging them into a single stream and then
+using the <a class="url" href="ffmpeg-filters.html#pan"><code class="code">pan</code></a> filter to mix
+the channels at will.
+
+</li><li>For video, to display both together, side by side or one on top of a part of
+the other; it can be done using the
+<a class="url" href="ffmpeg-filters.html#overlay"><code class="code">overlay</code></a> video filter.
+
+</li></ul>
+
+<a class="anchor" id="How-can-I-concatenate-video-files"></a><a name="How-can-I-concatenate-video-files_003f"></a>
+<h3 class="section">3.14 How can I concatenate video files?<span class="pull-right"><a class="anchor hidden-xs" href="#How-can-I-concatenate-video-files_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-can-I-concatenate-video-files_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>There are several solutions, depending on the exact circumstances.
+</p>
+<a name="Concatenating-using-the-concat-filter"></a>
+<h4 class="subsection">3.14.1 Concatenating using the concat <em class="emph">filter</em><span class="pull-right"><a class="anchor hidden-xs" href="#Concatenating-using-the-concat-filter" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Concatenating-using-the-concat-filter" aria-hidden="true">TOC</a></span></h4>
+
+<p>FFmpeg has a <a class="url" href="ffmpeg-filters.html#concat"><code class="code">concat</code></a> filter designed specifically for that, with examples in the
+documentation. This operation is recommended if you need to re-encode.
+</p>
+<a name="Concatenating-using-the-concat-demuxer"></a>
+<h4 class="subsection">3.14.2 Concatenating using the concat <em class="emph">demuxer</em><span class="pull-right"><a class="anchor hidden-xs" href="#Concatenating-using-the-concat-demuxer" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Concatenating-using-the-concat-demuxer" aria-hidden="true">TOC</a></span></h4>
+
+<p>FFmpeg has a <a class="url" href="ffmpeg-formats.html#concat"><code class="code">concat</code></a> demuxer which you can use when you want to avoid a re-encode and
+your format doesn&rsquo;t support file level concatenation.
+</p>
+<a name="Concatenating-using-the-concat-protocol-_0028file-level_0029"></a>
+<h4 class="subsection">3.14.3 Concatenating using the concat <em class="emph">protocol</em> (file level)<span class="pull-right"><a class="anchor hidden-xs" href="#Concatenating-using-the-concat-protocol-_0028file-level_0029" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Concatenating-using-the-concat-protocol-_0028file-level_0029" aria-hidden="true">TOC</a></span></h4>
+
+<p>FFmpeg has a <a class="url" href="ffmpeg-protocols.html#concat"><code class="code">concat</code></a> protocol designed specifically for that, with examples in the
+documentation.
+</p>
+<p>A few multimedia containers (MPEG-1, MPEG-2 PS, DV) allow one to concatenate
+video by merely concatenating the files containing them.
+</p>
+<p>Hence you may concatenate your multimedia files by first transcoding them to
+these privileged formats, then using the humble <code class="code">cat</code> command (or the
+equally humble <code class="code">copy</code> under Windows), and finally transcoding back to your
+format of choice.
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i input1.avi -qscale:v 1 intermediate1.mpg
+ffmpeg -i input2.avi -qscale:v 1 intermediate2.mpg
+cat intermediate1.mpg intermediate2.mpg &gt; intermediate_all.mpg
+ffmpeg -i intermediate_all.mpg -qscale:v 2 output.avi
+</pre></div>
+
+<p>Additionally, you can use the <code class="code">concat</code> protocol instead of <code class="code">cat</code> or
+<code class="code">copy</code> which will avoid creation of a potentially huge intermediate file.
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i input1.avi -qscale:v 1 intermediate1.mpg
+ffmpeg -i input2.avi -qscale:v 1 intermediate2.mpg
+ffmpeg -i concat:&quot;intermediate1.mpg|intermediate2.mpg&quot; -c copy intermediate_all.mpg
+ffmpeg -i intermediate_all.mpg -qscale:v 2 output.avi
+</pre></div>
+
+<p>Note that you may need to escape the character &quot;|&quot; which is special for many
+shells.
+</p>
+<p>Another option is usage of named pipes, should your platform support it:
+</p>
+<div class="example">
+<pre class="example-preformatted">mkfifo intermediate1.mpg
+mkfifo intermediate2.mpg
+ffmpeg -i input1.avi -qscale:v 1 -y intermediate1.mpg &lt; /dev/null &amp;
+ffmpeg -i input2.avi -qscale:v 1 -y intermediate2.mpg &lt; /dev/null &amp;
+cat intermediate1.mpg intermediate2.mpg |\
+ffmpeg -f mpeg -i - -c:v mpeg4 -c:a libmp3lame output.avi
+</pre></div>
+
+<a name="Concatenating-using-raw-audio-and-video"></a>
+<h4 class="subsection">3.14.4 Concatenating using raw audio and video<span class="pull-right"><a class="anchor hidden-xs" href="#Concatenating-using-raw-audio-and-video" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Concatenating-using-raw-audio-and-video" aria-hidden="true">TOC</a></span></h4>
+
+<p>Similarly, the yuv4mpegpipe format, and the raw video, raw audio codecs also
+allow concatenation, and the transcoding step is almost lossless.
+When using multiple yuv4mpegpipe(s), the first line needs to be discarded
+from all but the first stream. This can be accomplished by piping through
+<code class="code">tail</code> as seen below. Note that when piping through <code class="code">tail</code> you
+must use command grouping, <code class="code">{  ;}</code>, to background properly.
+</p>
+<p>For example, let&rsquo;s say we want to concatenate two FLV files into an
+output.flv file:
+</p>
+<div class="example">
+<pre class="example-preformatted">mkfifo temp1.a
+mkfifo temp1.v
+mkfifo temp2.a
+mkfifo temp2.v
+mkfifo all.a
+mkfifo all.v
+ffmpeg -i input1.flv -vn -f u16le -c:a pcm_s16le -ac 2 -ar 44100 - &gt; temp1.a &lt; /dev/null &amp;
+ffmpeg -i input2.flv -vn -f u16le -c:a pcm_s16le -ac 2 -ar 44100 - &gt; temp2.a &lt; /dev/null &amp;
+ffmpeg -i input1.flv -an -f yuv4mpegpipe - &gt; temp1.v &lt; /dev/null &amp;
+{ ffmpeg -i input2.flv -an -f yuv4mpegpipe - &lt; /dev/null | tail -n +2 &gt; temp2.v ; } &amp;
+cat temp1.a temp2.a &gt; all.a &amp;
+cat temp1.v temp2.v &gt; all.v &amp;
+ffmpeg -f u16le -c:a pcm_s16le -ac 2 -ar 44100 -i all.a \
+       -f yuv4mpegpipe -i all.v \
+       -y output.flv
+rm temp[12].[av] all.[av]
+</pre></div>
+
+<a name="Using-_002df-lavfi_002c-audio-becomes-mono-for-no-apparent-reason_002e"></a>
+<h3 class="section">3.15 Using <samp class="option">-f lavfi</samp>, audio becomes mono for no apparent reason.<span class="pull-right"><a class="anchor hidden-xs" href="#Using-_002df-lavfi_002c-audio-becomes-mono-for-no-apparent-reason_002e" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Using-_002df-lavfi_002c-audio-becomes-mono-for-no-apparent-reason_002e" aria-hidden="true">TOC</a></span></h3>
+
+<p>Use <samp class="option">-dumpgraph -</samp> to find out exactly where the channel layout is
+lost.
+</p>
+<p>Most likely, it is through <code class="code">auto-inserted aresample</code>. Try to understand
+why the converting filter was needed at that place.
+</p>
+<p>Just before the output is a likely place, as <samp class="option">-f lavfi</samp> currently
+only support packed S16.
+</p>
+<p>Then insert the correct <code class="code">aformat</code> explicitly in the filtergraph,
+specifying the exact format.
+</p>
+<div class="example">
+<pre class="example-preformatted">aformat=sample_fmts=s16:channel_layouts=stereo
+</pre></div>
+
+<a name="Why-does-FFmpeg-not-see-the-subtitles-in-my-VOB-file_003f"></a>
+<h3 class="section">3.16 Why does FFmpeg not see the subtitles in my VOB file?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-does-FFmpeg-not-see-the-subtitles-in-my-VOB-file_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-does-FFmpeg-not-see-the-subtitles-in-my-VOB-file_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>VOB and a few other formats do not have a global header that describes
+everything present in the file. Instead, applications are supposed to scan
+the file to see what it contains. Since VOB files are frequently large, only
+the beginning is scanned. If the subtitles happen only later in the file,
+they will not be initially detected.
+</p>
+<p>Some applications, including the <code class="code">ffmpeg</code> command-line tool, can only
+work with streams that were detected during the initial scan; streams that
+are detected later are ignored.
+</p>
+<p>The size of the initial scan is controlled by two options: <code class="code">probesize</code>
+(default ~5&nbsp;Mo) and <code class="code">analyzeduration</code> (default 5,000,000&nbsp;µs = 5&nbsp;s). For
+the subtitle stream to be detected, both values must be large enough.
+</p>
+<a name="Why-was-the-ffmpeg-_002dsameq-option-removed_003f-What-to-use-instead_003f"></a>
+<h3 class="section">3.17 Why was the <code class="command">ffmpeg</code> <samp class="option">-sameq</samp> option removed? What to use instead?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-was-the-ffmpeg-_002dsameq-option-removed_003f-What-to-use-instead_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-was-the-ffmpeg-_002dsameq-option-removed_003f-What-to-use-instead_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>The <samp class="option">-sameq</samp> option meant &quot;same quantizer&quot;, and made sense only in a
+very limited set of cases. Unfortunately, a lot of people mistook it for
+&quot;same quality&quot; and used it in places where it did not make sense: it had
+roughly the expected visible effect, but achieved it in a very inefficient
+way.
+</p>
+<p>Each encoder has its own set of options to set the quality-vs-size balance,
+use the options for the encoder you are using to set the quality level to a
+point acceptable for your tastes. The most common options to do that are
+<samp class="option">-qscale</samp> and <samp class="option">-qmax</samp>, but you should peruse the documentation
+of the encoder you chose.
+</p>
+<a name="I-have-a-stretched-video_002c-why-does-scaling-not-fix-it_003f"></a>
+<h3 class="section">3.18 I have a stretched video, why does scaling not fix it?<span class="pull-right"><a class="anchor hidden-xs" href="#I-have-a-stretched-video_002c-why-does-scaling-not-fix-it_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-I-have-a-stretched-video_002c-why-does-scaling-not-fix-it_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>A lot of video codecs and formats can store the <em class="emph">aspect ratio</em> of the
+video: this is the ratio between the width and the height of either the full
+image (DAR, display aspect ratio) or individual pixels (SAR, sample aspect
+ratio). For example, EGA screens at resolution 640×350 had 4:3 DAR and 35:48
+SAR.
+</p>
+<p>Most still image processing work with square pixels, i.e. 1:1 SAR, but a lot
+of video standards, especially from the analogic-numeric transition era, use
+non-square pixels.
+</p>
+<p>Most processing filters in FFmpeg handle the aspect ratio to avoid
+stretching the image: cropping adjusts the DAR to keep the SAR constant,
+scaling adjusts the SAR to keep the DAR constant.
+</p>
+<p>If you want to stretch, or “unstretch”, the image, you need to override the
+information with the
+<a class="url" href="ffmpeg-filters.html#setdar_002c-setsar"><code class="code">setdar or setsar filters</code></a>.
+</p>
+<p>Do not forget to examine carefully the original video to check whether the
+stretching comes from the image or from the aspect ratio information.
+</p>
+<p>For example, to fix a badly encoded EGA capture, use the following commands,
+either the first one to upscale to square pixels or the second one to set
+the correct aspect ratio or the third one to avoid transcoding (may not work
+depending on the format / codec / player / phase of the moon):
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i ega_screen.nut -vf scale=640:480,setsar=1 ega_screen_scaled.nut
+ffmpeg -i ega_screen.nut -vf setdar=4/3 ega_screen_anamorphic.nut
+ffmpeg -i ega_screen.nut -aspect 4/3 -c copy ega_screen_overridden.nut
+</pre></div>
+
+<a class="anchor" id="background-task"></a><a name="How-do-I-run-ffmpeg-as-a-background-task_003f"></a>
+<h3 class="section">3.19 How do I run ffmpeg as a background task?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-run-ffmpeg-as-a-background-task_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-run-ffmpeg-as-a-background-task_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>ffmpeg normally checks the console input, for entries like &quot;q&quot; to stop
+and &quot;?&quot; to give help, while performing operations. ffmpeg does not have a way of
+detecting when it is running as a background task.
+When it checks the console input, that can cause the process running ffmpeg
+in the background to suspend.
+</p>
+<p>To prevent those input checks, allowing ffmpeg to run as a background task,
+use the <a class="url" href="ffmpeg.html#stdin-option"><code class="code">-nostdin</code> option</a>
+in the ffmpeg invocation. This is effective whether you run ffmpeg in a shell
+or invoke ffmpeg in its own process via an operating system API.
+</p>
+<p>As an alternative, when you are running ffmpeg in a shell, you can redirect
+standard input to <code class="code">/dev/null</code> (on Linux and macOS)
+or <code class="code">NUL</code> (on Windows). You can do this redirect either
+on the ffmpeg invocation, or from a shell script which calls ffmpeg.
+</p>
+<p>For example:
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -nostdin -i INPUT OUTPUT
+</pre></div>
+
+<p>or (on Linux, macOS, and other UNIX-like shells):
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT OUTPUT &lt;/dev/null
+</pre></div>
+
+<p>or (on Windows):
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT OUTPUT &lt;NUL
+</pre></div>
+
+<a name="How-do-I-prevent-ffmpeg-from-suspending-with-a-message-like-suspended-_0028tty-output_0029_003f"></a>
+<h3 class="section">3.20 How do I prevent ffmpeg from suspending with a message like <em class="emph">suspended (tty output)</em>?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-prevent-ffmpeg-from-suspending-with-a-message-like-suspended-_0028tty-output_0029_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-prevent-ffmpeg-from-suspending-with-a-message-like-suspended-_0028tty-output_0029_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>If you run ffmpeg in the background, you may find that its process suspends.
+There may be a message like <em class="emph">suspended (tty output)</em>. The question is how
+to prevent the process from being suspended.
+</p>
+<p>For example:
+</p>
+<div class="example">
+<pre class="example-preformatted">% ffmpeg -i INPUT OUTPUT &amp;&gt; ~/tmp/log.txt &amp;
+[1] 93352
+%
+[1]  + suspended (tty output)  ffmpeg -i INPUT OUTPUT &amp;&gt;
+</pre></div>
+
+<p>The message &quot;tty output&quot; notwithstanding, the problem here is that
+ffmpeg normally checks the console input when it runs. The operating system
+detects this, and suspends the process until you can bring it to the
+foreground and attend to it.
+</p>
+<p>The solution is to use the right techniques to tell ffmpeg not to consult
+console input. You can use the
+<a class="url" href="ffmpeg.html#stdin-option"><code class="code">-nostdin</code> option</a>,
+or redirect standard input with <code class="code">&lt; /dev/null</code>.
+See FAQ
+<a class="ref" href="#background-task"><em class="emph">How do I run ffmpeg as a background task?</em></a>
+for details.
+</p>
+<a name="Development"></a>
+<h2 class="chapter">4 Development<span class="pull-right"><a class="anchor hidden-xs" href="#Development" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Development" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Are-there-examples-illustrating-how-to-use-the-FFmpeg-libraries_002c-particularly-libavcodec-and-libavformat_003f"></a>
+<h3 class="section">4.1 Are there examples illustrating how to use the FFmpeg libraries, particularly libavcodec and libavformat?<span class="pull-right"><a class="anchor hidden-xs" href="#Are-there-examples-illustrating-how-to-use-the-FFmpeg-libraries_002c-particularly-libavcodec-and-libavformat_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Are-there-examples-illustrating-how-to-use-the-FFmpeg-libraries_002c-particularly-libavcodec-and-libavformat_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Yes. Check the <samp class="file">doc/examples</samp> directory in the source
+repository, also available online at:
+<a class="url" href="https://github.com/FFmpeg/FFmpeg/tree/master/doc/examples">https://github.com/FFmpeg/FFmpeg/tree/master/doc/examples</a>.
+</p>
+<p>Examples are also installed by default, usually in
+<code class="code">$PREFIX/share/ffmpeg/examples</code>.
+</p>
+<p>Also you may read the Developers Guide of the FFmpeg documentation. Alternatively,
+examine the source code for one of the many open source projects that
+already incorporate FFmpeg at (<a class="url" href="projects.html">projects.html</a>).
+</p>
+<a name="Can-you-support-my-C-compiler-XXX_003f"></a>
+<h3 class="section">4.2 Can you support my C compiler XXX?<span class="pull-right"><a class="anchor hidden-xs" href="#Can-you-support-my-C-compiler-XXX_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Can-you-support-my-C-compiler-XXX_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>It depends. If your compiler is C99-compliant, then patches to support
+it are likely to be welcome if they do not pollute the source code
+with <code class="code">#ifdef</code>s related to the compiler.
+</p>
+<a name="Is-Microsoft-Visual-C_002b_002b-supported_003f"></a>
+<h3 class="section">4.3 Is Microsoft Visual C++ supported?<span class="pull-right"><a class="anchor hidden-xs" href="#Is-Microsoft-Visual-C_002b_002b-supported_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Is-Microsoft-Visual-C_002b_002b-supported_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Yes. Please see the <a class="uref" href="platform.html">Microsoft Visual C++</a>
+section in the FFmpeg documentation.
+</p>
+<a name="Can-you-add-automake_002c-libtool-or-autoconf-support_003f"></a>
+<h3 class="section">4.4 Can you add automake, libtool or autoconf support?<span class="pull-right"><a class="anchor hidden-xs" href="#Can-you-add-automake_002c-libtool-or-autoconf-support_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Can-you-add-automake_002c-libtool-or-autoconf-support_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>No. These tools are too bloated and they complicate the build.
+</p>
+<a name="Why-not-rewrite-FFmpeg-in-object_002doriented-C_002b_002b_003f"></a>
+<h3 class="section">4.5 Why not rewrite FFmpeg in object-oriented C++?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-not-rewrite-FFmpeg-in-object_002doriented-C_002b_002b_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-not-rewrite-FFmpeg-in-object_002doriented-C_002b_002b_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>FFmpeg is already organized in a highly modular manner and does not need to
+be rewritten in a formal object language. Further, many of the developers
+favor straight C; it works for them. For more arguments on this matter,
+read <a class="uref" href="https://web.archive.org/web/20111004021423/http://kernel.org/pub/linux/docs/lkml/#s15">&quot;Programming Religion&quot;</a>.
+</p>
+<a name="Why-are-the-ffmpeg-programs-devoid-of-debugging-symbols_003f"></a>
+<h3 class="section">4.6 Why are the ffmpeg programs devoid of debugging symbols?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-are-the-ffmpeg-programs-devoid-of-debugging-symbols_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-are-the-ffmpeg-programs-devoid-of-debugging-symbols_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>The build process creates <code class="command">ffmpeg_g</code>, <code class="command">ffplay_g</code>, etc. which
+contain full debug information. Those binaries are stripped to create
+<code class="command">ffmpeg</code>, <code class="command">ffplay</code>, etc. If you need the debug information, use
+the *_g versions.
+</p>
+<a name="I-do-not-like-the-LGPL_002c-can-I-contribute-code-under-the-GPL-instead_003f"></a>
+<h3 class="section">4.7 I do not like the LGPL, can I contribute code under the GPL instead?<span class="pull-right"><a class="anchor hidden-xs" href="#I-do-not-like-the-LGPL_002c-can-I-contribute-code-under-the-GPL-instead_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-I-do-not-like-the-LGPL_002c-can-I-contribute-code-under-the-GPL-instead_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Yes, as long as the code is optional and can easily and cleanly be placed
+under #if CONFIG_GPL without breaking anything. So, for example, a new codec
+or filter would be OK under GPL while a bug fix to LGPL code would not.
+</p>
+<a name="I_0027m-using-FFmpeg-from-within-my-C-application-but-the-linker-complains-about-missing-symbols-from-the-libraries-themselves_002e"></a>
+<h3 class="section">4.8 I&rsquo;m using FFmpeg from within my C application but the linker complains about missing symbols from the libraries themselves.<span class="pull-right"><a class="anchor hidden-xs" href="#I_0027m-using-FFmpeg-from-within-my-C-application-but-the-linker-complains-about-missing-symbols-from-the-libraries-themselves_002e" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-I_0027m-using-FFmpeg-from-within-my-C-application-but-the-linker-complains-about-missing-symbols-from-the-libraries-themselves_002e" aria-hidden="true">TOC</a></span></h3>
+
+<p>FFmpeg builds static libraries by default. In static libraries, dependencies
+are not handled. That has two consequences. First, you must specify the
+libraries in dependency order: <code class="code">-lavdevice</code> must come before
+<code class="code">-lavformat</code>, <code class="code">-lavutil</code> must come after everything else, etc.
+Second, external libraries that are used in FFmpeg have to be specified too.
+</p>
+<p>An easy way to get the full list of required libraries in dependency order
+is to use <code class="code">pkg-config</code>.
+</p>
+<div class="example">
+<pre class="example-preformatted">c99 -o program program.c $(pkg-config --cflags --libs libavformat libavcodec)
+</pre></div>
+
+<p>See <samp class="file">doc/example/Makefile</samp> and <samp class="file">doc/example/pc-uninstalled</samp> for
+more details.
+</p>
+<a name="I_0027m-using-FFmpeg-from-within-my-C_002b_002b-application-but-the-linker-complains-about-missing-symbols-which-seem-to-be-available_002e"></a>
+<h3 class="section">4.9 I&rsquo;m using FFmpeg from within my C++ application but the linker complains about missing symbols which seem to be available.<span class="pull-right"><a class="anchor hidden-xs" href="#I_0027m-using-FFmpeg-from-within-my-C_002b_002b-application-but-the-linker-complains-about-missing-symbols-which-seem-to-be-available_002e" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-I_0027m-using-FFmpeg-from-within-my-C_002b_002b-application-but-the-linker-complains-about-missing-symbols-which-seem-to-be-available_002e" aria-hidden="true">TOC</a></span></h3>
+
+<p>FFmpeg is a pure C project, so to use the libraries within your C++ application
+you need to explicitly state that you are using a C library. You can do this by
+encompassing your FFmpeg includes using <code class="code">extern &quot;C&quot;</code>.
+</p>
+<p>See <a class="url" href="http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html#faq-32.3">http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html#faq-32.3</a>
+</p>
+<a name="I_0027m-using-libavutil-from-within-my-C_002b_002b-application-but-the-compiler-complains-about-_0027UINT64_005fC_0027-was-not-declared-in-this-scope"></a>
+<h3 class="section">4.10 I&rsquo;m using libavutil from within my C++ application but the compiler complains about &rsquo;UINT64_C&rsquo; was not declared in this scope<span class="pull-right"><a class="anchor hidden-xs" href="#I_0027m-using-libavutil-from-within-my-C_002b_002b-application-but-the-compiler-complains-about-_0027UINT64_005fC_0027-was-not-declared-in-this-scope" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-I_0027m-using-libavutil-from-within-my-C_002b_002b-application-but-the-compiler-complains-about-_0027UINT64_005fC_0027-was-not-declared-in-this-scope" aria-hidden="true">TOC</a></span></h3>
+
+<p>FFmpeg is a pure C project using C99 math features, in order to enable C++
+to use them you have to append -D__STDC_CONSTANT_MACROS to your CXXFLAGS
+</p>
+<a name="I-have-a-file-in-memory-_002f-a-API-different-from-_002aopen_002f_002aread_002f-libc-how-do-I-use-it-with-libavformat_003f"></a>
+<h3 class="section">4.11 I have a file in memory / a API different from *open/*read/ libc how do I use it with libavformat?<span class="pull-right"><a class="anchor hidden-xs" href="#I-have-a-file-in-memory-_002f-a-API-different-from-_002aopen_002f_002aread_002f-libc-how-do-I-use-it-with-libavformat_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-I-have-a-file-in-memory-_002f-a-API-different-from-_002aopen_002f_002aread_002f-libc-how-do-I-use-it-with-libavformat_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>You have to create a custom AVIOContext using <code class="code">avio_alloc_context</code>,
+see <samp class="file">libavformat/aviobuf.c</samp> in FFmpeg and <samp class="file">libmpdemux/demux_lavf.c</samp> in MPlayer or MPlayer2 sources.
+</p>
+<a name="Where-is-the-documentation-about-ffv1_002c-msmpeg4_002c-asv1_002c-4xm_003f"></a>
+<h3 class="section">4.12 Where is the documentation about ffv1, msmpeg4, asv1, 4xm?<span class="pull-right"><a class="anchor hidden-xs" href="#Where-is-the-documentation-about-ffv1_002c-msmpeg4_002c-asv1_002c-4xm_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Where-is-the-documentation-about-ffv1_002c-msmpeg4_002c-asv1_002c-4xm_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>see <a class="url" href="https://www.ffmpeg.org/~michael/">https://www.ffmpeg.org/~michael/</a>
+</p>
+<a name="How-do-I-feed-H_002e263_002dRTP-_0028and-other-codecs-in-RTP_0029-to-libavcodec_003f"></a>
+<h3 class="section">4.13 How do I feed H.263-RTP (and other codecs in RTP) to libavcodec?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-feed-H_002e263_002dRTP-_0028and-other-codecs-in-RTP_0029-to-libavcodec_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-feed-H_002e263_002dRTP-_0028and-other-codecs-in-RTP_0029-to-libavcodec_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Even if peculiar since it is network oriented, RTP is a container like any
+other. You have to <em class="emph">demux</em> RTP before feeding the payload to libavcodec.
+In this specific case please look at RFC 4629 to see how it should be done.
+</p>
+<a name="AVStream_002er_005fframe_005frate-is-wrong_002c-it-is-much-larger-than-the-frame-rate_002e"></a>
+<h3 class="section">4.14 AVStream.r_frame_rate is wrong, it is much larger than the frame rate.<span class="pull-right"><a class="anchor hidden-xs" href="#AVStream_002er_005fframe_005frate-is-wrong_002c-it-is-much-larger-than-the-frame-rate_002e" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-AVStream_002er_005fframe_005frate-is-wrong_002c-it-is-much-larger-than-the-frame-rate_002e" aria-hidden="true">TOC</a></span></h3>
+
+<p><code class="code">r_frame_rate</code> is NOT the average frame rate, it is the smallest frame rate
+that can accurately represent all timestamps. So no, it is not
+wrong if it is larger than the average!
+For example, if you have mixed 25 and 30 fps content, then <code class="code">r_frame_rate</code>
+will be 150 (it is the least common multiple).
+If you are looking for the average frame rate, see <code class="code">AVStream.avg_frame_rate</code>.
+</p>
+<a name="Why-is-make-fate-not-running-all-tests_003f"></a>
+<h3 class="section">4.15 Why is <code class="code">make fate</code> not running all tests?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-is-make-fate-not-running-all-tests_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-is-make-fate-not-running-all-tests_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Make sure you have the fate-suite samples and the <code class="code">SAMPLES</code> Make variable
+or <code class="code">FATE_SAMPLES</code> environment variable or the <code class="code">--samples</code>
+<code class="command">configure</code> option is set to the right path.
+</p>
+<a name="Why-is-make-fate-not-finding-the-samples_003f"></a>
+<h3 class="section">4.16 Why is <code class="code">make fate</code> not finding the samples?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-is-make-fate-not-finding-the-samples_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-is-make-fate-not-finding-the-samples_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Do you happen to have a <code class="code">~</code> character in the samples path to indicate a
+home directory? The value is used in ways where the shell cannot expand it,
+causing FATE to not find files. Just replace <code class="code">~</code> by the full path.
+</p>
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/fate.html

@@ -0,0 +1,390 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      FFmpeg Automated Testing Environment
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      FFmpeg Automated Testing Environment
+      </h1>
+
+
+<a name="Top"></a>
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Introduction" href="#Introduction">1 Introduction</a></li>
+  <li><a id="toc-Using-FATE-from-your-FFmpeg-source-directory" href="#Using-FATE-from-your-FFmpeg-source-directory">2 Using FATE from your FFmpeg source directory</a></li>
+  <li><a id="toc-Submitting-the-results-to-the-FFmpeg-result-aggregation-server" href="#Submitting-the-results-to-the-FFmpeg-result-aggregation-server">3 Submitting the results to the FFmpeg result aggregation server</a></li>
+  <li><a id="toc-Uploading-new-samples-to-the-fate-suite" href="#Uploading-new-samples-to-the-fate-suite">4 Uploading new samples to the fate suite</a></li>
+  <li><a id="toc-FATE-makefile-targets-and-variables" href="#FATE-makefile-targets-and-variables">5 FATE makefile targets and variables</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Makefile-targets" href="#Makefile-targets">5.1 Makefile targets</a></li>
+    <li><a id="toc-Makefile-variables" href="#Makefile-variables">5.2 Makefile variables</a></li>
+    <li><a id="toc-Examples" href="#Examples">5.3 Examples</a></li>
+  </ul></li>
+</ul>
+</div>
+</div>
+
+<a name="Introduction"></a>
+<h2 class="chapter">1 Introduction<span class="pull-right"><a class="anchor hidden-xs" href="#Introduction" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Introduction" aria-hidden="true">TOC</a></span></h2>
+
+<p>FATE is an extended regression suite on the client-side and a means
+for results aggregation and presentation on the server-side.
+</p>
+<p>The first part of this document explains how you can use FATE from
+your FFmpeg source directory to test your ffmpeg binary. The second
+part describes how you can run FATE to submit the results to FFmpeg&rsquo;s
+FATE server.
+</p>
+<p>In any way you can have a look at the publicly viewable FATE results
+by visiting this website:
+</p>
+<p><a class="url" href="http://fate.ffmpeg.org/">http://fate.ffmpeg.org/</a>
+</p>
+<p>This is especially recommended for all people contributing source
+code to FFmpeg, as it can be seen if some test on some platform broke
+with their recent contribution. This usually happens on the platforms
+the developers could not test on.
+</p>
+<p>The second part of this document describes how you can run FATE to
+submit your results to FFmpeg&rsquo;s FATE server. If you want to submit your
+results be sure to check that your combination of CPU, OS and compiler
+is not already listed on the above mentioned website.
+</p>
+<p>In the third part you can find a comprehensive listing of FATE makefile
+targets and variables.
+</p>
+
+<a name="Using-FATE-from-your-FFmpeg-source-directory"></a>
+<h2 class="chapter">2 Using FATE from your FFmpeg source directory<span class="pull-right"><a class="anchor hidden-xs" href="#Using-FATE-from-your-FFmpeg-source-directory" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Using-FATE-from-your-FFmpeg-source-directory" aria-hidden="true">TOC</a></span></h2>
+
+<p>If you want to run FATE on your machine you need to have the samples
+in place. You can get the samples via the build target fate-rsync.
+Use this command from the top-level source directory:
+</p>
+<div class="example">
+<pre class="example-preformatted">make fate-rsync SAMPLES=fate-suite/
+make fate       SAMPLES=fate-suite/
+</pre></div>
+
+<p>The above commands set the samples location by passing a makefile
+variable via command line. It is also possible to set the samples
+location at source configuration time by invoking configure with
+<samp class="option">--samples=&lt;path to the samples directory&gt;</samp>. Afterwards you can
+invoke the makefile targets without setting the <var class="var">SAMPLES</var> makefile
+variable. This is illustrated by the following commands:
+</p>
+<div class="example">
+<pre class="example-preformatted">./configure --samples=fate-suite/
+make fate-rsync
+make fate
+</pre></div>
+
+<p>Yet another way to tell FATE about the location of the sample
+directory is by making sure the environment variable FATE_SAMPLES
+contains the path to your samples directory. This can be achieved
+by e.g. putting that variable in your shell profile or by setting
+it in your interactive session.
+</p>
+<div class="example">
+<pre class="example-preformatted">FATE_SAMPLES=fate-suite/ make fate
+</pre></div>
+
+<div class="info">
+<p>Do not put a &rsquo;~&rsquo; character in the samples path to indicate a home
+directory. Because of shell nuances, this will cause FATE to fail.
+</p></div>
+<p>Beware that some assertions are disabled by default, so mind setting
+<samp class="option">--assert-level=&lt;level&gt;</samp> at configuration time, e.g. when seeking
+the highest possible test coverage:
+</p><div class="example">
+<pre class="example-preformatted">./configure --assert-level=2
+</pre></div>
+<p>Note that raising the assert level could have a performance impact.
+</p>
+<p>To get the complete list of tests, run the command:
+</p><div class="example">
+<pre class="example-preformatted">make fate-list
+</pre></div>
+
+<p>You can specify a subset of tests to run by specifying the
+corresponding elements from the list with the <code class="code">fate-</code> prefix,
+e.g. as in:
+</p><div class="example">
+<pre class="example-preformatted">make fate-ffprobe_compact fate-ffprobe_xml
+</pre></div>
+
+<p>This makes it easier to run a few tests in case of failure without
+running the complete test suite.
+</p>
+<p>To use a custom wrapper to run the test, pass <samp class="option">--target-exec</samp> to
+<code class="command">configure</code> or set the <var class="var">TARGET_EXEC</var> Make variable.
+</p>
+
+<a name="Submitting-the-results-to-the-FFmpeg-result-aggregation-server"></a>
+<h2 class="chapter">3 Submitting the results to the FFmpeg result aggregation server<span class="pull-right"><a class="anchor hidden-xs" href="#Submitting-the-results-to-the-FFmpeg-result-aggregation-server" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Submitting-the-results-to-the-FFmpeg-result-aggregation-server" aria-hidden="true">TOC</a></span></h2>
+
+<p>To submit your results to the server you should run fate through the
+shell script <samp class="file">tests/fate.sh</samp> from the FFmpeg sources. This script needs
+to be invoked with a configuration file as its first argument.
+</p>
+<div class="example">
+<pre class="example-preformatted">tests/fate.sh /path/to/fate_config
+</pre></div>
+
+<p>A configuration file template with comments describing the individual
+configuration variables can be found at <samp class="file">doc/fate_config.sh.template</samp>.
+</p>
+<p>The mentioned configuration template is also available here:
+</p><pre class="verbatim">slot=                                    # some unique identifier
+repo=https://git.ffmpeg.org/ffmpeg.git   # the source repository
+#branch=release/2.6                       # the branch to test
+samples=                                 # path to samples directory
+workdir=                                 # directory in which to do all the work
+#fate_recv=&quot;ssh -T fate@fate.ffmpeg.org&quot; # command to submit report
+comment=                                 # optional description
+build_only=     # set to &quot;yes&quot; for a compile-only instance that skips tests
+ignore_tests=
+
+# the following are optional and map to configure options
+arch=
+cpu=
+cross_prefix=
+as=
+cc=
+ld=
+target_os=
+sysroot=
+target_exec=
+target_path=
+target_samples=
+extra_cflags=
+extra_ldflags=
+extra_libs=
+extra_conf=     # extra configure options not covered above
+
+#make=          # name of GNU make if not 'make'
+makeopts=       # extra options passed to 'make'
+#makeopts_fate= # extra options passed to 'make' when running tests,
+                # defaulting to makeopts above if this is not set
+#tar=           # command to create a tar archive from its arguments on stdout,
+                # defaults to 'tar c'
+#fate_targets=  # targets to make when running fate; defaults to &quot;fate&quot;,
+                # can be set to run a subset of tests, e.g. &quot;fate-checkasm&quot;.
+
+#fate_environments=  # a list of names of configurations to run tests for;
+                     # each round is run with variables from ${${name}_env} set.
+
+# One example of using fate_environments:
+
+# target_exec=&quot;qemu-aarch64-static&quot;
+# fate_targets=&quot;fate-checkasm fate-cpu&quot;
+# fate_environments=&quot;sve128 sve256&quot;
+# sve128_env=&quot;QEMU_CPU=max,sve128=on&quot;
+# sve256_env=&quot;QEMU_CPU=max,sve256=on&quot;
+
+# The variables set by fate_environments can also be used explicitly
+# by target_exec, e.g. like this:
+
+# target_exec=&quot;qemu-aarch64-static -cpu \$(MY_CPU)&quot;
+# fate_targets=&quot;fate-checkasm fate-cpu&quot;
+# fate_environments=&quot;sve128 sve256&quot;
+# sve128_env=&quot;MY_CPU=max,sve128=on&quot;
+# sve256_env=&quot;MY_CPU=max,sve256=on&quot;
+</pre>
+<p>Create a configuration that suits your needs, based on the configuration
+template. The <code class="env">slot</code> configuration variable can be any string that is not
+yet used, but it is suggested that you name it adhering to the following
+pattern &lsquo;<samp class="samp"><var class="var">arch</var>-<var class="var">os</var>-<var class="var">compiler</var>-<var class="var">compiler version</var></samp>&rsquo;. The
+configuration file itself will be sourced in a shell script, therefore all
+shell features may be used. This enables you to setup the environment as you
+need it for your build.
+</p>
+<p>For your first test runs the <code class="env">fate_recv</code> variable should be empty or
+commented out. This will run everything as normal except that it will omit
+the submission of the results to the server. The following files should be
+present in $workdir as specified in the configuration file:
+</p>
+<ul class="itemize mark-bullet">
+<li>configure.log
+    </li><li>compile.log
+    </li><li>test.log
+    </li><li>report
+    </li><li>version
+</li></ul>
+
+<p>When you have everything working properly you can create an SSH key pair
+and send the public key to the FATE server administrator who can be contacted
+at the email address <a class="email" href="mailto:fate-admin@ffmpeg.org">fate-admin@ffmpeg.org</a>.
+</p>
+<p>Configure your SSH client to use public key authentication with that key
+when connecting to the FATE server. Also do not forget to check the identity
+of the server and to accept its host key. This can usually be achieved by
+running your SSH client manually and killing it after you accepted the key.
+The FATE server&rsquo;s fingerprint is:
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">RSA</samp>&rsquo;</dt>
+<dd><p>d3:f1:83:97:a4:75:2b:a6:fb:d6:e8:aa:81:93:97:51
+</p></dd>
+<dt>&lsquo;<samp class="samp">ECDSA</samp>&rsquo;</dt>
+<dd><p>76:9f:68:32:04:1e:d5:d4:ec:47:3f:dc:fc:18:17:86
+</p></dd>
+</dl>
+
+<p>If you have problems connecting to the FATE server, it may help to try out
+the <code class="command">ssh</code> command with one or more <samp class="option">-v</samp> options. You should
+get detailed output concerning your SSH configuration and the authentication
+process.
+</p>
+<p>The only thing left is to automate the execution of the fate.sh script and
+the synchronisation of the samples directory.
+</p>
+<a name="Uploading-new-samples-to-the-fate-suite"></a>
+<h2 class="chapter">4 Uploading new samples to the fate suite<span class="pull-right"><a class="anchor hidden-xs" href="#Uploading-new-samples-to-the-fate-suite" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Uploading-new-samples-to-the-fate-suite" aria-hidden="true">TOC</a></span></h2>
+
+<p>If you need a sample uploaded send a mail to samples-request.
+</p>
+<p>This is for developers who have an account on the fate suite server.
+If you upload new samples, please make sure they are as small as possible,
+space on each client, network bandwidth and so on benefit from smaller test cases.
+Also keep in mind older checkouts use existing sample files, that means in
+practice generally do not replace, remove or overwrite files as it likely would
+break older checkouts or releases.
+Also all needed samples for a commit should be uploaded, ideally 24
+hours, before the push.
+If you need an account for frequently uploading samples or you wish to help
+others by doing that send a mail to ffmpeg-devel.
+</p>
+<div class="example">
+<pre class="example-preformatted">#First update your local samples copy:
+rsync -vauL --chmod=Dg+s,Duo+x,ug+rw,o+r,o-w,+X fate-suite.ffmpeg.org:/home/samples/fate-suite/ ~/fate-suite
+
+#Then do a dry run checking what would be uploaded:
+rsync -vanL --no-g --chmod=Dg+s,Duo+x,ug+rw,o+r,o-w,+X ~/fate-suite/ fate-suite.ffmpeg.org:/home/samples/fate-suite
+
+#Upload the files:
+rsync -vaL  --no-g --chmod=Dg+s,Duo+x,ug+rw,o+r,o-w,+X ~/fate-suite/ fate-suite.ffmpeg.org:/home/samples/fate-suite
+</pre></div>
+
+
+<a name="FATE-makefile-targets-and-variables"></a>
+<h2 class="chapter">5 FATE makefile targets and variables<span class="pull-right"><a class="anchor hidden-xs" href="#FATE-makefile-targets-and-variables" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-FATE-makefile-targets-and-variables" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Makefile-targets"></a>
+<h3 class="section">5.1 Makefile targets<span class="pull-right"><a class="anchor hidden-xs" href="#Makefile-targets" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Makefile-targets" aria-hidden="true">TOC</a></span></h3>
+
+<dl class="table">
+<dt><samp class="option">fate-rsync</samp></dt>
+<dd><p>Download/synchronize sample files to the configured samples directory.
+</p>
+</dd>
+<dt><samp class="option">fate-list</samp></dt>
+<dd><p>Will list all fate/regression test targets.
+</p>
+</dd>
+<dt><samp class="option">fate-list-failing</samp></dt>
+<dd><p>List the fate tests that failed the last time they were executed.
+</p>
+</dd>
+<dt><samp class="option">fate-clear-reports</samp></dt>
+<dd><p>Remove the test reports from previous test executions (getting rid of
+potentially stale results from fate-list-failing).
+</p>
+</dd>
+<dt><samp class="option">fate</samp></dt>
+<dd><p>Run the FATE test suite (requires the fate-suite dataset).
+</p></dd>
+</dl>
+
+<a name="Makefile-variables"></a>
+<h3 class="section">5.2 Makefile variables<span class="pull-right"><a class="anchor hidden-xs" href="#Makefile-variables" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Makefile-variables" aria-hidden="true">TOC</a></span></h3>
+
+<dl class="table">
+<dt><code class="env">V</code></dt>
+<dd><p>Verbosity level, can be set to 0, 1 or 2.
+    </p><ul class="itemize mark-bullet">
+<li>0: show just the test arguments
+        </li><li>1: show just the command used in the test
+        </li><li>2: show everything
+    </li></ul>
+
+</dd>
+<dt><code class="env">SAMPLES</code></dt>
+<dd><p>Specify or override the path to the FATE samples at make time, it has a
+meaning only while running the regression tests.
+</p>
+</dd>
+<dt><code class="env">THREADS</code></dt>
+<dd><p>Specify how many threads to use while running regression tests, it is
+quite useful to detect thread-related regressions.
+</p>
+<p>This variable may be set to the string &quot;random&quot;, optionally followed by a
+number, like &quot;random99&quot;, This will cause each test to use a random number of
+threads. If a number is specified, it is used as a maximum number of threads,
+otherwise 16 is the maximum.
+</p>
+<p>In case a test fails, the thread count used for it will be written into the
+errfile.
+</p>
+</dd>
+<dt><code class="env">THREAD_TYPE</code></dt>
+<dd><p>Specify which threading strategy test, either &lsquo;<samp class="samp">slice</samp>&rsquo; or &lsquo;<samp class="samp">frame</samp>&rsquo;,
+by default &lsquo;<samp class="samp">slice+frame</samp>&rsquo;
+</p>
+</dd>
+<dt><code class="env">CPUFLAGS</code></dt>
+<dd><p>Specify CPU flags.
+</p>
+</dd>
+<dt><code class="env">TARGET_EXEC</code></dt>
+<dd><p>Specify or override the wrapper used to run the tests.
+The <code class="env">TARGET_EXEC</code> option provides a way to run FATE wrapped in
+<code class="command">valgrind</code>, <code class="command">qemu-user</code> or <code class="command">wine</code> or on remote targets
+through <code class="command">ssh</code>.
+</p>
+</dd>
+<dt><code class="env">GEN</code></dt>
+<dd><p>Set to &lsquo;<samp class="samp">1</samp>&rsquo; to generate the missing or mismatched references.
+</p>
+</dd>
+<dt><code class="env">HWACCEL</code></dt>
+<dd><p>Specify which hardware acceleration to use while running regression tests,
+by default &lsquo;<samp class="samp">none</samp>&rsquo; is used.
+</p>
+</dd>
+<dt><code class="env">KEEP</code></dt>
+<dd><p>Set to &lsquo;<samp class="samp">1</samp>&rsquo; to keep temp files generated by fate test(s) when test is successful.
+Default is &lsquo;<samp class="samp">0</samp>&rsquo;, which removes these files. Files are always kept when a test
+fails.
+</p>
+</dd>
+</dl>
+
+<a name="Examples"></a>
+<h3 class="section">5.3 Examples<span class="pull-right"><a class="anchor hidden-xs" href="#Examples" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Examples" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">make V=1 SAMPLES=/var/fate/samples THREADS=2 CPUFLAGS=mmx fate
+</pre></div>
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/ffmpeg-bitstream-filters.html

@@ -0,0 +1,1290 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      FFmpeg Bitstream Filters Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      FFmpeg Bitstream Filters Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-Bitstream-Filters" href="#Bitstream-Filters">2 Bitstream Filters</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-aac_005fadtstoasc" href="#aac_005fadtstoasc">2.1 aac_adtstoasc</a></li>
+    <li><a id="toc-av1_005fmetadata" href="#av1_005fmetadata">2.2 av1_metadata</a></li>
+    <li><a id="toc-chomp" href="#chomp">2.3 chomp</a></li>
+    <li><a id="toc-dca_005fcore" href="#dca_005fcore">2.4 dca_core</a></li>
+    <li><a id="toc-dovi_005frpu" href="#dovi_005frpu">2.5 dovi_rpu</a></li>
+    <li><a id="toc-dump_005fextra" href="#dump_005fextra">2.6 dump_extra</a></li>
+    <li><a id="toc-dv_005ferror_005fmarker" href="#dv_005ferror_005fmarker">2.7 dv_error_marker</a></li>
+    <li><a id="toc-eac3_005fcore" href="#eac3_005fcore">2.8 eac3_core</a></li>
+    <li><a id="toc-extract_005fextradata" href="#extract_005fextradata">2.9 extract_extradata</a></li>
+    <li><a id="toc-filter_005funits" href="#filter_005funits">2.10 filter_units</a></li>
+    <li><a id="toc-hapqa_005fextract" href="#hapqa_005fextract">2.11 hapqa_extract</a></li>
+    <li><a id="toc-h264_005fmetadata" href="#h264_005fmetadata">2.12 h264_metadata</a></li>
+    <li><a id="toc-h264_005fmp4toannexb" href="#h264_005fmp4toannexb">2.13 h264_mp4toannexb</a></li>
+    <li><a id="toc-h264_005fredundant_005fpps" href="#h264_005fredundant_005fpps">2.14 h264_redundant_pps</a></li>
+    <li><a id="toc-hevc_005fmetadata" href="#hevc_005fmetadata">2.15 hevc_metadata</a></li>
+    <li><a id="toc-hevc_005fmp4toannexb" href="#hevc_005fmp4toannexb">2.16 hevc_mp4toannexb</a></li>
+    <li><a id="toc-imxdump" href="#imxdump">2.17 imxdump</a></li>
+    <li><a id="toc-mjpeg2jpeg" href="#mjpeg2jpeg">2.18 mjpeg2jpeg</a></li>
+    <li><a id="toc-mjpegadump" href="#mjpegadump">2.19 mjpegadump</a></li>
+    <li><a id="toc-mov2textsub-1" href="#mov2textsub-1">2.20 mov2textsub</a></li>
+    <li><a id="toc-mpeg2_005fmetadata" href="#mpeg2_005fmetadata">2.21 mpeg2_metadata</a></li>
+    <li><a id="toc-mpeg4_005funpack_005fbframes" href="#mpeg4_005funpack_005fbframes">2.22 mpeg4_unpack_bframes</a></li>
+    <li><a id="toc-noise" href="#noise">2.23 noise</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-Examples" href="#Examples">2.23.1 Examples</a></li>
+    </ul></li>
+    <li><a id="toc-null" href="#null">2.24 null</a></li>
+    <li><a id="toc-pcm_005frechunk" href="#pcm_005frechunk">2.25 pcm_rechunk</a></li>
+    <li><a id="toc-pgs_005fframe_005fmerge" href="#pgs_005fframe_005fmerge">2.26 pgs_frame_merge</a></li>
+    <li><a id="toc-prores_005fmetadata" href="#prores_005fmetadata">2.27 prores_metadata</a></li>
+    <li><a id="toc-remove_005fextra" href="#remove_005fextra">2.28 remove_extra</a></li>
+    <li><a id="toc-setts" href="#setts">2.29 setts</a></li>
+    <li><a id="toc-showinfo" href="#showinfo">2.30 showinfo</a></li>
+    <li><a id="toc-text2movsub-1" href="#text2movsub-1">2.31 text2movsub</a></li>
+    <li><a id="toc-trace_005fheaders" href="#trace_005fheaders">2.32 trace_headers</a></li>
+    <li><a id="toc-truehd_005fcore" href="#truehd_005fcore">2.33 truehd_core</a></li>
+    <li><a id="toc-vp9_005fmetadata" href="#vp9_005fmetadata">2.34 vp9_metadata</a></li>
+    <li><a id="toc-vp9_005fsuperframe" href="#vp9_005fsuperframe">2.35 vp9_superframe</a></li>
+    <li><a id="toc-vp9_005fsuperframe_005fsplit" href="#vp9_005fsuperframe_005fsplit">2.36 vp9_superframe_split</a></li>
+    <li><a id="toc-vp9_005fraw_005freorder" href="#vp9_005fraw_005freorder">2.37 vp9_raw_reorder</a></li>
+  </ul></li>
+  <li><a id="toc-See-Also" href="#See-Also">3 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">4 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>This document describes the bitstream filters provided by the
+libavcodec library.
+</p>
+<p>A bitstream filter operates on the encoded stream data, and performs
+bitstream level modifications without performing decoding.
+</p>
+
+<a name="Bitstream-Filters"></a>
+<h2 class="chapter">2 Bitstream Filters<span class="pull-right"><a class="anchor hidden-xs" href="#Bitstream-Filters" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Bitstream-Filters" aria-hidden="true">TOC</a></span></h2>
+
+<p>When you configure your FFmpeg build, all the supported bitstream
+filters are enabled by default. You can list all available ones using
+the configure option <code class="code">--list-bsfs</code>.
+</p>
+<p>You can disable all the bitstream filters using the configure option
+<code class="code">--disable-bsfs</code>, and selectively enable any bitstream filter using
+the option <code class="code">--enable-bsf=BSF</code>, or you can disable a particular
+bitstream filter using the option <code class="code">--disable-bsf=BSF</code>.
+</p>
+<p>The option <code class="code">-bsfs</code> of the ff* tools will display the list of
+all the supported bitstream filters included in your build.
+</p>
+<p>The ff* tools have a -bsf option applied per stream, taking a
+comma-separated list of filters, whose parameters follow the filter
+name after a &rsquo;=&rsquo;.
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c:v copy -bsf:v filter1[=opt1=str1:opt2=str2][,filter2] OUTPUT
+</pre></div>
+
+<p>Below is a description of the currently available bitstream filters,
+with their parameters, if any.
+</p>
+<a name="aac_005fadtstoasc"></a>
+<h3 class="section">2.1 aac_adtstoasc<span class="pull-right"><a class="anchor hidden-xs" href="#aac_005fadtstoasc" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-aac_005fadtstoasc" aria-hidden="true">TOC</a></span></h3>
+
+<p>Convert MPEG-2/4 AAC ADTS to an MPEG-4 Audio Specific Configuration
+bitstream.
+</p>
+<p>This filter creates an MPEG-4 AudioSpecificConfig from an MPEG-2/4
+ADTS header and removes the ADTS header.
+</p>
+<p>This filter is required for example when copying an AAC stream from a
+raw ADTS AAC or an MPEG-TS container to MP4A-LATM, to an FLV file, or
+to MOV/MP4 files and related formats such as 3GP or M4A. Please note
+that it is auto-inserted for MP4A-LATM and MOV/MP4 and related formats.
+</p>
+<a name="av1_005fmetadata"></a>
+<h3 class="section">2.2 av1_metadata<span class="pull-right"><a class="anchor hidden-xs" href="#av1_005fmetadata" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-av1_005fmetadata" aria-hidden="true">TOC</a></span></h3>
+
+<p>Modify metadata embedded in an AV1 stream.
+</p>
+<dl class="table">
+<dt><samp class="option">td</samp></dt>
+<dd><p>Insert or remove temporal delimiter OBUs in all temporal units of the
+stream.
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">insert</samp>&rsquo;</dt>
+<dd><p>Insert a TD at the beginning of every TU which does not already have one.
+</p></dd>
+<dt>&lsquo;<samp class="samp">remove</samp>&rsquo;</dt>
+<dd><p>Remove the TD from the beginning of every TU which has one.
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">color_primaries</samp></dt>
+<dt><samp class="option">transfer_characteristics</samp></dt>
+<dt><samp class="option">matrix_coefficients</samp></dt>
+<dd><p>Set the color description fields in the stream (see AV1 section 6.4.2).
+</p>
+</dd>
+<dt><samp class="option">color_range</samp></dt>
+<dd><p>Set the color range in the stream (see AV1 section 6.4.2; note that
+this cannot be set for streams using BT.709 primaries, sRGB transfer
+characteristic and identity (RGB) matrix coefficients).
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">tv</samp>&rsquo;</dt>
+<dd><p>Limited range.
+</p></dd>
+<dt>&lsquo;<samp class="samp">pc</samp>&rsquo;</dt>
+<dd><p>Full range.
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">chroma_sample_position</samp></dt>
+<dd><p>Set the chroma sample location in the stream (see AV1 section 6.4.2).
+This can only be set for 4:2:0 streams.
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">vertical</samp>&rsquo;</dt>
+<dd><p>Left position (matching the default in MPEG-2 and H.264).
+</p></dd>
+<dt>&lsquo;<samp class="samp">colocated</samp>&rsquo;</dt>
+<dd><p>Top-left position.
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">tick_rate</samp></dt>
+<dd><p>Set the tick rate (<em class="emph">time_scale / num_units_in_display_tick</em>) in
+the timing info in the sequence header.
+</p></dd>
+<dt><samp class="option">num_ticks_per_picture</samp></dt>
+<dd><p>Set the number of ticks in each picture, to indicate that the stream
+has a fixed framerate.  Ignored if <samp class="option">tick_rate</samp> is not also set.
+</p>
+</dd>
+<dt><samp class="option">delete_padding</samp></dt>
+<dd><p>Deletes Padding OBUs.
+</p>
+</dd>
+</dl>
+
+<a name="chomp"></a>
+<h3 class="section">2.3 chomp<span class="pull-right"><a class="anchor hidden-xs" href="#chomp" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-chomp" aria-hidden="true">TOC</a></span></h3>
+
+<p>Remove zero padding at the end of a packet.
+</p>
+<a name="dca_005fcore"></a>
+<h3 class="section">2.4 dca_core<span class="pull-right"><a class="anchor hidden-xs" href="#dca_005fcore" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-dca_005fcore" aria-hidden="true">TOC</a></span></h3>
+
+<p>Extract the core from a DCA/DTS stream, dropping extensions such as
+DTS-HD.
+</p>
+<a name="dovi_005frpu"></a>
+<h3 class="section">2.5 dovi_rpu<span class="pull-right"><a class="anchor hidden-xs" href="#dovi_005frpu" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-dovi_005frpu" aria-hidden="true">TOC</a></span></h3>
+
+<p>Manipulate Dolby Vision metadata in a HEVC/AV1 bitstream, optionally enabling
+metadata compression.
+</p>
+<dl class="table">
+<dt><samp class="option">strip</samp></dt>
+<dd><p>If enabled, strip all Dolby Vision metadata (configuration record + RPU data
+blocks) from the stream.
+</p></dd>
+<dt><samp class="option">compression</samp></dt>
+<dd><p>Which compression level to enable.
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">none</samp>&rsquo;</dt>
+<dd><p>No metadata compression.
+</p></dd>
+<dt>&lsquo;<samp class="samp">limited</samp>&rsquo;</dt>
+<dd><p>Limited metadata compression scheme. Should be compatible with most devices.
+This is the default.
+</p></dd>
+<dt>&lsquo;<samp class="samp">extended</samp>&rsquo;</dt>
+<dd><p>Extended metadata compression. Devices are not required to support this. Note
+that this level currently behaves the same as &lsquo;<samp class="samp">limited</samp>&rsquo; in libavcodec.
+</p></dd>
+</dl>
+</dd>
+</dl>
+
+<a name="dump_005fextra"></a>
+<h3 class="section">2.6 dump_extra<span class="pull-right"><a class="anchor hidden-xs" href="#dump_005fextra" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-dump_005fextra" aria-hidden="true">TOC</a></span></h3>
+
+<p>Add extradata to the beginning of the filtered packets except when
+said packets already exactly begin with the extradata that is intended
+to be added.
+</p>
+<dl class="table">
+<dt><samp class="option">freq</samp></dt>
+<dd><p>The additional argument specifies which packets should be filtered.
+It accepts the values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">k</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">keyframe</samp>&rsquo;</dt>
+<dd><p>add extradata to all key packets
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">e</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">all</samp>&rsquo;</dt>
+<dd><p>add extradata to all packets
+</p></dd>
+</dl>
+</dd>
+</dl>
+
+<p>If not specified it is assumed &lsquo;<samp class="samp">k</samp>&rsquo;.
+</p>
+<p>For example the following <code class="command">ffmpeg</code> command forces a global
+header (thus disabling individual packet headers) in the H.264 packets
+generated by the <code class="code">libx264</code> encoder, but corrects them by adding
+the header stored in extradata to the key packets:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -map 0 -flags:v +global_header -c:v libx264 -bsf:v dump_extra out.ts
+</pre></div>
+
+<a name="dv_005ferror_005fmarker"></a>
+<h3 class="section">2.7 dv_error_marker<span class="pull-right"><a class="anchor hidden-xs" href="#dv_005ferror_005fmarker" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-dv_005ferror_005fmarker" aria-hidden="true">TOC</a></span></h3>
+
+<p>Blocks in DV which are marked as damaged are replaced by blocks of the specified color.
+</p>
+<dl class="table">
+<dt><samp class="option">color</samp></dt>
+<dd><p>The color to replace damaged blocks by
+</p></dd>
+<dt><samp class="option">sta</samp></dt>
+<dd><p>A 16 bit mask which specifies which of the 16 possible error status values are
+to be replaced by colored blocks. 0xFFFE is the default which replaces all non 0
+error status values.
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">ok</samp>&rsquo;</dt>
+<dd><p>No error, no concealment
+</p></dd>
+<dt>&lsquo;<samp class="samp">err</samp>&rsquo;</dt>
+<dd><p>Error, No concealment
+</p></dd>
+<dt>&lsquo;<samp class="samp">res</samp>&rsquo;</dt>
+<dd><p>Reserved
+</p></dd>
+<dt>&lsquo;<samp class="samp">notok</samp>&rsquo;</dt>
+<dd><p>Error or concealment
+</p></dd>
+<dt>&lsquo;<samp class="samp">notres</samp>&rsquo;</dt>
+<dd><p>Not reserved
+</p></dd>
+<dt>&lsquo;<samp class="samp">Aa, Ba, Ca, Ab, Bb, Cb, A, B, C, a, b, erri, erru</samp>&rsquo;</dt>
+<dd><p>The specific error status code
+</p></dd>
+</dl>
+<p>see page 44-46 or section 5.5 of
+<a class="url" href="http://web.archive.org/web/20060927044735/http://www.smpte.org/smpte_store/standards/pdf/s314m.pdf">http://web.archive.org/web/20060927044735/http://www.smpte.org/smpte_store/standards/pdf/s314m.pdf</a>
+</p>
+</dd>
+</dl>
+
+<a name="eac3_005fcore"></a>
+<h3 class="section">2.8 eac3_core<span class="pull-right"><a class="anchor hidden-xs" href="#eac3_005fcore" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-eac3_005fcore" aria-hidden="true">TOC</a></span></h3>
+
+<p>Extract the core from a E-AC-3 stream, dropping extra channels.
+</p>
+<a name="extract_005fextradata"></a>
+<h3 class="section">2.9 extract_extradata<span class="pull-right"><a class="anchor hidden-xs" href="#extract_005fextradata" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-extract_005fextradata" aria-hidden="true">TOC</a></span></h3>
+
+<p>Extract the in-band extradata.
+</p>
+<p>Certain codecs allow the long-term headers (e.g. MPEG-2 sequence headers,
+or H.264/HEVC (VPS/)SPS/PPS) to be transmitted either &quot;in-band&quot; (i.e. as a part
+of the bitstream containing the coded frames) or &quot;out of band&quot; (e.g. on the
+container level). This latter form is called &quot;extradata&quot; in FFmpeg terminology.
+</p>
+<p>This bitstream filter detects the in-band headers and makes them available as
+extradata.
+</p>
+<dl class="table">
+<dt><samp class="option">remove</samp></dt>
+<dd><p>When this option is enabled, the long-term headers are removed from the
+bitstream after extraction.
+</p></dd>
+</dl>
+
+<a name="filter_005funits"></a>
+<h3 class="section">2.10 filter_units<span class="pull-right"><a class="anchor hidden-xs" href="#filter_005funits" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-filter_005funits" aria-hidden="true">TOC</a></span></h3>
+
+<p>Remove units with types in or not in a given set from the stream.
+</p>
+<dl class="table">
+<dt><samp class="option">pass_types</samp></dt>
+<dd><p>List of unit types or ranges of unit types to pass through while removing
+all others.  This is specified as a &rsquo;|&rsquo;-separated list of unit type values
+or ranges of values with &rsquo;-&rsquo;.
+</p>
+</dd>
+<dt><samp class="option">remove_types</samp></dt>
+<dd><p>Identical to <samp class="option">pass_types</samp>, except the units in the given set
+removed and all others passed through.
+</p></dd>
+</dl>
+
+<p>The types used by pass_types and remove_types correspond to NAL unit types
+(nal_unit_type) in H.264, HEVC and H.266 (see Table 7-1 in the H.264
+and HEVC specifications or Table 5 in the H.266 specification), to
+marker values for JPEG (without 0xFF prefix) and to start codes without
+start code prefix (i.e. the byte following the 0x000001) for MPEG-2.
+For VP8 and VP9, every unit has type zero.
+</p>
+<p>Extradata is unchanged by this transformation, but note that if the stream
+contains inline parameter sets then the output may be unusable if they are
+removed.
+</p>
+<p>For example, to remove all non-VCL NAL units from an H.264 stream:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=pass_types=1-5' OUTPUT
+</pre></div>
+
+<p>To remove all AUDs, SEI and filler from an H.265 stream:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=35|38-40' OUTPUT
+</pre></div>
+
+<p>To remove all user data from a MPEG-2 stream, including Closed Captions:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=178' OUTPUT
+</pre></div>
+
+<p>To remove all SEI from a H264 stream, including Closed Captions:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=6' OUTPUT
+</pre></div>
+
+<p>To remove all prefix and suffix SEI from a HEVC stream, including Closed Captions and dynamic HDR:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=39|40' OUTPUT
+</pre></div>
+
+<a name="hapqa_005fextract"></a>
+<h3 class="section">2.11 hapqa_extract<span class="pull-right"><a class="anchor hidden-xs" href="#hapqa_005fextract" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-hapqa_005fextract" aria-hidden="true">TOC</a></span></h3>
+
+<p>Extract Rgb or Alpha part of an HAPQA file, without recompression, in order to create an HAPQ or an HAPAlphaOnly file.
+</p>
+<dl class="table">
+<dt><samp class="option">texture</samp></dt>
+<dd><p>Specifies the texture to keep.
+</p>
+<dl class="table">
+<dt><samp class="option">color</samp></dt>
+<dt><samp class="option">alpha</samp></dt>
+</dl>
+
+</dd>
+</dl>
+
+<p>Convert HAPQA to HAPQ
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i hapqa_inputfile.mov -c copy -bsf:v hapqa_extract=texture=color -tag:v HapY -metadata:s:v:0 encoder=&quot;HAPQ&quot; hapq_file.mov
+</pre></div>
+
+<p>Convert HAPQA to HAPAlphaOnly
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i hapqa_inputfile.mov -c copy -bsf:v hapqa_extract=texture=alpha -tag:v HapA -metadata:s:v:0 encoder=&quot;HAPAlpha Only&quot; hapalphaonly_file.mov
+</pre></div>
+
+<a name="h264_005fmetadata"></a>
+<h3 class="section">2.12 h264_metadata<span class="pull-right"><a class="anchor hidden-xs" href="#h264_005fmetadata" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-h264_005fmetadata" aria-hidden="true">TOC</a></span></h3>
+
+<p>Modify metadata embedded in an H.264 stream.
+</p>
+<dl class="table">
+<dt><samp class="option">aud</samp></dt>
+<dd><p>Insert or remove AUD NAL units in all access units of the stream.
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">pass</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">insert</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">remove</samp>&rsquo;</dt>
+</dl>
+
+<p>Default is pass.
+</p>
+</dd>
+<dt><samp class="option">sample_aspect_ratio</samp></dt>
+<dd><p>Set the sample aspect ratio of the stream in the VUI parameters.
+See H.264 table E-1.
+</p>
+</dd>
+<dt><samp class="option">overscan_appropriate_flag</samp></dt>
+<dd><p>Set whether the stream is suitable for display using overscan
+or not (see H.264 section E.2.1).
+</p>
+</dd>
+<dt><samp class="option">video_format</samp></dt>
+<dt><samp class="option">video_full_range_flag</samp></dt>
+<dd><p>Set the video format in the stream (see H.264 section E.2.1 and
+table E-2).
+</p>
+</dd>
+<dt><samp class="option">colour_primaries</samp></dt>
+<dt><samp class="option">transfer_characteristics</samp></dt>
+<dt><samp class="option">matrix_coefficients</samp></dt>
+<dd><p>Set the colour description in the stream (see H.264 section E.2.1
+and tables E-3, E-4 and E-5).
+</p>
+</dd>
+<dt><samp class="option">chroma_sample_loc_type</samp></dt>
+<dd><p>Set the chroma sample location in the stream (see H.264 section
+E.2.1 and figure E-1).
+</p>
+</dd>
+<dt><samp class="option">tick_rate</samp></dt>
+<dd><p>Set the tick rate (time_scale / num_units_in_tick) in the VUI
+parameters.  This is the smallest time unit representable in the
+stream, and in many cases represents the field rate of the stream
+(double the frame rate).
+</p></dd>
+<dt><samp class="option">fixed_frame_rate_flag</samp></dt>
+<dd><p>Set whether the stream has fixed framerate - typically this indicates
+that the framerate is exactly half the tick rate, but the exact
+meaning is dependent on interlacing and the picture structure (see
+H.264 section E.2.1 and table E-6).
+</p></dd>
+<dt><samp class="option">zero_new_constraint_set_flags</samp></dt>
+<dd><p>Zero constraint_set4_flag and constraint_set5_flag in the SPS. These
+bits were reserved in a previous version of the H.264 spec, and thus
+some hardware decoders require these to be zero. The result of zeroing
+this is still a valid bitstream.
+</p>
+</dd>
+<dt><samp class="option">crop_left</samp></dt>
+<dt><samp class="option">crop_right</samp></dt>
+<dt><samp class="option">crop_top</samp></dt>
+<dt><samp class="option">crop_bottom</samp></dt>
+<dd><p>Set the frame cropping offsets in the SPS.  These values will replace
+the current ones if the stream is already cropped.
+</p>
+<p>These fields are set in pixels.  Note that some sizes may not be
+representable if the chroma is subsampled or the stream is interlaced
+(see H.264 section 7.4.2.1.1).
+</p>
+</dd>
+<dt><samp class="option">sei_user_data</samp></dt>
+<dd><p>Insert a string as SEI unregistered user data.  The argument must
+be of the form <em class="emph">UUID+string</em>, where the UUID is as hex digits
+possibly separated by hyphens, and the string can be anything.
+</p>
+<p>For example, &lsquo;<samp class="samp">086f3693-b7b3-4f2c-9653-21492feee5b8+hello</samp>&rsquo; will
+insert the string &ldquo;hello&rdquo; associated with the given UUID.
+</p>
+</dd>
+<dt><samp class="option">delete_filler</samp></dt>
+<dd><p>Deletes both filler NAL units and filler SEI messages.
+</p>
+</dd>
+<dt><samp class="option">display_orientation</samp></dt>
+<dd><p>Insert, extract or remove Display orientation SEI messages.
+See H.264 section D.1.27 and D.2.27 for syntax and semantics.
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">pass</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">insert</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">remove</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">extract</samp>&rsquo;</dt>
+</dl>
+
+<p>Default is pass.
+</p>
+<p>Insert mode works in conjunction with <code class="code">rotate</code> and <code class="code">flip</code> options.
+Any pre-existing Display orientation messages will be removed in insert or remove mode.
+Extract mode attaches the display matrix to the packet as side data.
+</p>
+</dd>
+<dt><samp class="option">rotate</samp></dt>
+<dd><p>Set rotation in display orientation SEI (anticlockwise angle in degrees).
+Range is -360 to +360. Default is NaN.
+</p>
+</dd>
+<dt><samp class="option">flip</samp></dt>
+<dd><p>Set flip in display orientation SEI.
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">horizontal</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">vertical</samp>&rsquo;</dt>
+</dl>
+
+<p>Default is unset.
+</p>
+</dd>
+<dt><samp class="option">level</samp></dt>
+<dd><p>Set the level in the SPS.  Refer to H.264 section A.3 and tables A-1
+to A-5.
+</p>
+<p>The argument must be the name of a level (for example, &lsquo;<samp class="samp">4.2</samp>&rsquo;), a
+level_idc value (for example, &lsquo;<samp class="samp">42</samp>&rsquo;), or the special name &lsquo;<samp class="samp">auto</samp>&rsquo;
+indicating that the filter should attempt to guess the level from the
+input stream properties.
+</p>
+</dd>
+</dl>
+
+<a name="h264_005fmp4toannexb"></a>
+<h3 class="section">2.13 h264_mp4toannexb<span class="pull-right"><a class="anchor hidden-xs" href="#h264_005fmp4toannexb" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-h264_005fmp4toannexb" aria-hidden="true">TOC</a></span></h3>
+
+<p>Convert an H.264 bitstream from length prefixed mode to start code
+prefixed mode (as defined in the Annex B of the ITU-T H.264
+specification).
+</p>
+<p>This is required by some streaming formats, typically the MPEG-2
+transport stream format (muxer <code class="code">mpegts</code>).
+</p>
+<p>For example to remux an MP4 file containing an H.264 stream to mpegts
+format with <code class="command">ffmpeg</code>, you can use the command:
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT.mp4 -codec copy -bsf:v h264_mp4toannexb OUTPUT.ts
+</pre></div>
+
+<p>Please note that this filter is auto-inserted for MPEG-TS (muxer
+<code class="code">mpegts</code>) and raw H.264 (muxer <code class="code">h264</code>) output formats.
+</p>
+<a name="h264_005fredundant_005fpps"></a>
+<h3 class="section">2.14 h264_redundant_pps<span class="pull-right"><a class="anchor hidden-xs" href="#h264_005fredundant_005fpps" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-h264_005fredundant_005fpps" aria-hidden="true">TOC</a></span></h3>
+
+<p>This applies a specific fixup to some Blu-ray BDMV H264 streams
+which contain redundant PPSs. The PPSs modify irrelevant parameters
+of the stream, confusing other transformations which require
+the correct extradata.
+</p>
+<p>The encoder used on these impacted streams adds extra PPSs throughout
+the stream, varying the initial QP and whether weighted prediction
+was enabled. This causes issues after copying the stream into
+a global header container, as the starting PPS is not suitable
+for the rest of the stream. One side effect, for example,
+is seeking will return garbled output until a new PPS appears.
+</p>
+<p>This BSF removes the extra PPSs and rewrites the slice headers
+such that the stream uses a single leading PPS in the global header,
+which resolves the issue.
+</p>
+<a name="hevc_005fmetadata"></a>
+<h3 class="section">2.15 hevc_metadata<span class="pull-right"><a class="anchor hidden-xs" href="#hevc_005fmetadata" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-hevc_005fmetadata" aria-hidden="true">TOC</a></span></h3>
+
+<p>Modify metadata embedded in an HEVC stream.
+</p>
+<dl class="table">
+<dt><samp class="option">aud</samp></dt>
+<dd><p>Insert or remove AUD NAL units in all access units of the stream.
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">insert</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">remove</samp>&rsquo;</dt>
+</dl>
+
+</dd>
+<dt><samp class="option">sample_aspect_ratio</samp></dt>
+<dd><p>Set the sample aspect ratio in the stream in the VUI parameters.
+</p>
+</dd>
+<dt><samp class="option">video_format</samp></dt>
+<dt><samp class="option">video_full_range_flag</samp></dt>
+<dd><p>Set the video format in the stream (see H.265 section E.3.1 and
+table E.2).
+</p>
+</dd>
+<dt><samp class="option">colour_primaries</samp></dt>
+<dt><samp class="option">transfer_characteristics</samp></dt>
+<dt><samp class="option">matrix_coefficients</samp></dt>
+<dd><p>Set the colour description in the stream (see H.265 section E.3.1
+and tables E.3, E.4 and E.5).
+</p>
+</dd>
+<dt><samp class="option">chroma_sample_loc_type</samp></dt>
+<dd><p>Set the chroma sample location in the stream (see H.265 section
+E.3.1 and figure E.1).
+</p>
+</dd>
+<dt><samp class="option">tick_rate</samp></dt>
+<dd><p>Set the tick rate in the VPS and VUI parameters (time_scale /
+num_units_in_tick). Combined with <samp class="option">num_ticks_poc_diff_one</samp>, this can
+set a constant framerate in the stream.  Note that it is likely to be
+overridden by container parameters when the stream is in a container.
+</p>
+</dd>
+<dt><samp class="option">num_ticks_poc_diff_one</samp></dt>
+<dd><p>Set poc_proportional_to_timing_flag in VPS and VUI and use this value
+to set num_ticks_poc_diff_one_minus1 (see H.265 sections 7.4.3.1 and
+E.3.1).  Ignored if <samp class="option">tick_rate</samp> is not also set.
+</p>
+</dd>
+<dt><samp class="option">crop_left</samp></dt>
+<dt><samp class="option">crop_right</samp></dt>
+<dt><samp class="option">crop_top</samp></dt>
+<dt><samp class="option">crop_bottom</samp></dt>
+<dd><p>Set the conformance window cropping offsets in the SPS.  These values
+will replace the current ones if the stream is already cropped.
+</p>
+<p>These fields are set in pixels.  Note that some sizes may not be
+representable if the chroma is subsampled (H.265 section 7.4.3.2.1).
+</p>
+</dd>
+<dt><samp class="option">width</samp></dt>
+<dt><samp class="option">height</samp></dt>
+<dd><p>Set width and height after crop.
+</p>
+</dd>
+<dt><samp class="option">level</samp></dt>
+<dd><p>Set the level in the VPS and SPS.  See H.265 section A.4 and tables
+A.6 and A.7.
+</p>
+<p>The argument must be the name of a level (for example, &lsquo;<samp class="samp">5.1</samp>&rsquo;), a
+<em class="emph">general_level_idc</em> value (for example, &lsquo;<samp class="samp">153</samp>&rsquo; for level 5.1),
+or the special name &lsquo;<samp class="samp">auto</samp>&rsquo; indicating that the filter should
+attempt to guess the level from the input stream properties.
+</p>
+</dd>
+</dl>
+
+<a name="hevc_005fmp4toannexb"></a>
+<h3 class="section">2.16 hevc_mp4toannexb<span class="pull-right"><a class="anchor hidden-xs" href="#hevc_005fmp4toannexb" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-hevc_005fmp4toannexb" aria-hidden="true">TOC</a></span></h3>
+
+<p>Convert an HEVC/H.265 bitstream from length prefixed mode to start code
+prefixed mode (as defined in the Annex B of the ITU-T H.265
+specification).
+</p>
+<p>This is required by some streaming formats, typically the MPEG-2
+transport stream format (muxer <code class="code">mpegts</code>).
+</p>
+<p>For example to remux an MP4 file containing an HEVC stream to mpegts
+format with <code class="command">ffmpeg</code>, you can use the command:
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT.mp4 -codec copy -bsf:v hevc_mp4toannexb OUTPUT.ts
+</pre></div>
+
+<p>Please note that this filter is auto-inserted for MPEG-TS (muxer
+<code class="code">mpegts</code>) and raw HEVC/H.265 (muxer <code class="code">h265</code> or
+<code class="code">hevc</code>) output formats.
+</p>
+<a name="imxdump"></a>
+<h3 class="section">2.17 imxdump<span class="pull-right"><a class="anchor hidden-xs" href="#imxdump" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-imxdump" aria-hidden="true">TOC</a></span></h3>
+
+<p>Modifies the bitstream to fit in MOV and to be usable by the Final Cut
+Pro decoder. This filter only applies to the mpeg2video codec, and is
+likely not needed for Final Cut Pro 7 and newer with the appropriate
+<samp class="option">-tag:v</samp>.
+</p>
+<p>For example, to remux 30 MB/sec NTSC IMX to MOV:
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i input.mxf -c copy -bsf:v imxdump -tag:v mx3n output.mov
+</pre></div>
+
+<a name="mjpeg2jpeg"></a>
+<h3 class="section">2.18 mjpeg2jpeg<span class="pull-right"><a class="anchor hidden-xs" href="#mjpeg2jpeg" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-mjpeg2jpeg" aria-hidden="true">TOC</a></span></h3>
+
+<p>Convert MJPEG/AVI1 packets to full JPEG/JFIF packets.
+</p>
+<p>MJPEG is a video codec wherein each video frame is essentially a
+JPEG image. The individual frames can be extracted without loss,
+e.g. by
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i ../some_mjpeg.avi -c:v copy frames_%d.jpg
+</pre></div>
+
+<p>Unfortunately, these chunks are incomplete JPEG images, because
+they lack the DHT segment required for decoding. Quoting from
+<a class="url" href="http://www.digitalpreservation.gov/formats/fdd/fdd000063.shtml">http://www.digitalpreservation.gov/formats/fdd/fdd000063.shtml</a>:
+</p>
+<p>Avery Lee, writing in the rec.video.desktop newsgroup in 2001,
+commented that &quot;MJPEG, or at least the MJPEG in AVIs having the
+MJPG fourcc, is restricted JPEG with a fixed &ndash; and *omitted* &ndash;
+Huffman table. The JPEG must be YCbCr colorspace, it must be 4:2:2,
+and it must use basic Huffman encoding, not arithmetic or
+progressive. . . . You can indeed extract the MJPEG frames and
+decode them with a regular JPEG decoder, but you have to prepend
+the DHT segment to them, or else the decoder won&rsquo;t have any idea
+how to decompress the data. The exact table necessary is given in
+the OpenDML spec.&quot;
+</p>
+<p>This bitstream filter patches the header of frames extracted from an MJPEG
+stream (carrying the AVI1 header ID and lacking a DHT segment) to
+produce fully qualified JPEG images.
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i mjpeg-movie.avi -c:v copy -bsf:v mjpeg2jpeg frame_%d.jpg
+exiftran -i -9 frame*.jpg
+ffmpeg -i frame_%d.jpg -c:v copy rotated.avi
+</pre></div>
+
+<a name="mjpegadump"></a>
+<h3 class="section">2.19 mjpegadump<span class="pull-right"><a class="anchor hidden-xs" href="#mjpegadump" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-mjpegadump" aria-hidden="true">TOC</a></span></h3>
+
+<p>Add an MJPEG A header to the bitstream, to enable decoding by
+Quicktime.
+</p>
+<a class="anchor" id="mov2textsub"></a><a name="mov2textsub-1"></a>
+<h3 class="section">2.20 mov2textsub<span class="pull-right"><a class="anchor hidden-xs" href="#mov2textsub-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-mov2textsub-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>Extract a representable text file from MOV subtitles, stripping the
+metadata header from each subtitle packet.
+</p>
+<p>See also the <a class="ref" href="#text2movsub">text2movsub</a> filter.
+</p>
+<a name="mpeg2_005fmetadata"></a>
+<h3 class="section">2.21 mpeg2_metadata<span class="pull-right"><a class="anchor hidden-xs" href="#mpeg2_005fmetadata" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-mpeg2_005fmetadata" aria-hidden="true">TOC</a></span></h3>
+
+<p>Modify metadata embedded in an MPEG-2 stream.
+</p>
+<dl class="table">
+<dt><samp class="option">display_aspect_ratio</samp></dt>
+<dd><p>Set the display aspect ratio in the stream.
+</p>
+<p>The following fixed values are supported:
+</p><dl class="table">
+<dt><samp class="option">4/3</samp></dt>
+<dt><samp class="option">16/9</samp></dt>
+<dt><samp class="option">221/100</samp></dt>
+</dl>
+<p>Any other value will result in square pixels being signalled instead
+(see H.262 section 6.3.3 and table 6-3).
+</p>
+</dd>
+<dt><samp class="option">frame_rate</samp></dt>
+<dd><p>Set the frame rate in the stream.  This is constructed from a table
+of known values combined with a small multiplier and divisor - if
+the supplied value is not exactly representable, the nearest
+representable value will be used instead (see H.262 section 6.3.3
+and table 6-4).
+</p>
+</dd>
+<dt><samp class="option">video_format</samp></dt>
+<dd><p>Set the video format in the stream (see H.262 section 6.3.6 and
+table 6-6).
+</p>
+</dd>
+<dt><samp class="option">colour_primaries</samp></dt>
+<dt><samp class="option">transfer_characteristics</samp></dt>
+<dt><samp class="option">matrix_coefficients</samp></dt>
+<dd><p>Set the colour description in the stream (see H.262 section 6.3.6
+and tables 6-7, 6-8 and 6-9).
+</p>
+</dd>
+</dl>
+
+<a name="mpeg4_005funpack_005fbframes"></a>
+<h3 class="section">2.22 mpeg4_unpack_bframes<span class="pull-right"><a class="anchor hidden-xs" href="#mpeg4_005funpack_005fbframes" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-mpeg4_005funpack_005fbframes" aria-hidden="true">TOC</a></span></h3>
+
+<p>Unpack DivX-style packed B-frames.
+</p>
+<p>DivX-style packed B-frames are not valid MPEG-4 and were only a
+workaround for the broken Video for Windows subsystem.
+They use more space, can cause minor AV sync issues, require more
+CPU power to decode (unless the player has some decoded picture queue
+to compensate the 2,0,2,0 frame per packet style) and cause
+trouble if copied into a standard container like mp4 or mpeg-ps/ts,
+because MPEG-4 decoders may not be able to decode them, since they are
+not valid MPEG-4.
+</p>
+<p>For example to fix an AVI file containing an MPEG-4 stream with
+DivX-style packed B-frames using <code class="command">ffmpeg</code>, you can use the command:
+</p>
+<div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT.avi -codec copy -bsf:v mpeg4_unpack_bframes OUTPUT.avi
+</pre></div>
+
+<a name="noise"></a>
+<h3 class="section">2.23 noise<span class="pull-right"><a class="anchor hidden-xs" href="#noise" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-noise" aria-hidden="true">TOC</a></span></h3>
+
+<p>Damages the contents of packets or simply drops them without damaging the
+container. Can be used for fuzzing or testing error resilience/concealment.
+</p>
+<p>Parameters:
+</p><dl class="table">
+<dt><samp class="option">amount</samp></dt>
+<dd><p>Accepts an expression whose evaluation per-packet determines how often bytes in that
+packet will be modified. A value below 0 will result in a variable frequency.
+Default is 0 which results in no modification. However, if neither amount nor drop is specified,
+amount will be set to <var class="var">-1</var>. See below for accepted variables.
+</p></dd>
+<dt><samp class="option">drop</samp></dt>
+<dd><p>Accepts an expression evaluated per-packet whose value determines whether that packet is dropped.
+Evaluation to a positive value results in the packet being dropped. Evaluation to a negative
+value results in a variable chance of it being dropped, roughly inverse in proportion to the magnitude
+of the value. Default is 0 which results in no drops. See below for accepted variables.
+</p></dd>
+<dt><samp class="option">dropamount</samp></dt>
+<dd><p>Accepts a non-negative integer, which assigns a variable chance of it being dropped, roughly inverse
+in proportion to the value. Default is 0 which results in no drops. This option is kept for backwards
+compatibility and is equivalent to setting drop to a negative value with the same magnitude
+i.e. <code class="code">dropamount=4</code> is the same as <code class="code">drop=-4</code>. Ignored if drop is also specified.
+</p></dd>
+</dl>
+
+<p>Both <code class="code">amount</code> and <code class="code">drop</code> accept expressions containing the following variables:
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">n</samp>&rsquo;</dt>
+<dd><p>The index of the packet, starting from zero.
+</p></dd>
+<dt>&lsquo;<samp class="samp">tb</samp>&rsquo;</dt>
+<dd><p>The timebase for packet timestamps.
+</p></dd>
+<dt>&lsquo;<samp class="samp">pts</samp>&rsquo;</dt>
+<dd><p>Packet presentation timestamp.
+</p></dd>
+<dt>&lsquo;<samp class="samp">dts</samp>&rsquo;</dt>
+<dd><p>Packet decoding timestamp.
+</p></dd>
+<dt>&lsquo;<samp class="samp">nopts</samp>&rsquo;</dt>
+<dd><p>Constant representing AV_NOPTS_VALUE.
+</p></dd>
+<dt>&lsquo;<samp class="samp">startpts</samp>&rsquo;</dt>
+<dd><p>First non-AV_NOPTS_VALUE PTS seen in the stream.
+</p></dd>
+<dt>&lsquo;<samp class="samp">startdts</samp>&rsquo;</dt>
+<dd><p>First non-AV_NOPTS_VALUE DTS seen in the stream.
+</p></dd>
+<dt>&lsquo;<samp class="samp">duration</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">d</samp>&rsquo;</dt>
+<dd><p>Packet duration, in timebase units.
+</p></dd>
+<dt>&lsquo;<samp class="samp">pos</samp>&rsquo;</dt>
+<dd><p>Packet position in input; may be -1 when unknown or not set.
+</p></dd>
+<dt>&lsquo;<samp class="samp">size</samp>&rsquo;</dt>
+<dd><p>Packet size, in bytes.
+</p></dd>
+<dt>&lsquo;<samp class="samp">key</samp>&rsquo;</dt>
+<dd><p>Whether packet is marked as a keyframe.
+</p></dd>
+<dt>&lsquo;<samp class="samp">state</samp>&rsquo;</dt>
+<dd><p>A pseudo random integer, primarily derived from the content of packet payload.
+</p></dd>
+</dl>
+
+<a name="Examples"></a>
+<h4 class="subsection">2.23.1 Examples<span class="pull-right"><a class="anchor hidden-xs" href="#Examples" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Examples" aria-hidden="true">TOC</a></span></h4>
+<p>Apply modification to every byte but don&rsquo;t drop any packets.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c copy -bsf noise=1 output.mkv
+</pre></div>
+
+<p>Drop every video packet not marked as a keyframe after timestamp 30s but do not
+modify any of the remaining packets.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c copy -bsf:v noise=drop='gt(t\,30)*not(key)' output.mkv
+</pre></div>
+
+<p>Drop one second of audio every 10 seconds and add some random noise to the rest.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c copy -bsf:a noise=amount=-1:drop='between(mod(t\,10)\,9\,10)' output.mkv
+</pre></div>
+
+<a name="null"></a>
+<h3 class="section">2.24 null<span class="pull-right"><a class="anchor hidden-xs" href="#null" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-null" aria-hidden="true">TOC</a></span></h3>
+<p>This bitstream filter passes the packets through unchanged.
+</p>
+<a name="pcm_005frechunk"></a>
+<h3 class="section">2.25 pcm_rechunk<span class="pull-right"><a class="anchor hidden-xs" href="#pcm_005frechunk" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-pcm_005frechunk" aria-hidden="true">TOC</a></span></h3>
+
+<p>Repacketize PCM audio to a fixed number of samples per packet or a fixed packet
+rate per second. This is similar to the <a data-manual="ffmpeg-filters" href="ffmpeg-filters.html#asetnsamples">asetnsamples audio
+filter</a> but works on audio packets instead of audio frames.
+</p>
+<dl class="table">
+<dt><samp class="option">nb_out_samples, n</samp></dt>
+<dd><p>Set the number of samples per each output audio packet. The number is intended
+as the number of samples <em class="emph">per each channel</em>. Default value is 1024.
+</p>
+</dd>
+<dt><samp class="option">pad, p</samp></dt>
+<dd><p>If set to 1, the filter will pad the last audio packet with silence, so that it
+will contain the same number of samples (or roughly the same number of samples,
+see <samp class="option">frame_rate</samp>) as the previous ones. Default value is 1.
+</p>
+</dd>
+<dt><samp class="option">frame_rate, r</samp></dt>
+<dd><p>This option makes the filter output a fixed number of packets per second instead
+of a fixed number of samples per packet. If the audio sample rate is not
+divisible by the frame rate then the number of samples will not be constant but
+will vary slightly so that each packet will start as close to the frame
+boundary as possible. Using this option has precedence over <samp class="option">nb_out_samples</samp>.
+</p></dd>
+</dl>
+
+<p>You can generate the well known 1602-1601-1602-1601-1602 pattern of 48kHz audio
+for NTSC frame rate using the <samp class="option">frame_rate</samp> option.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -f lavfi -i sine=r=48000:d=1 -c pcm_s16le -bsf pcm_rechunk=r=30000/1001 -f framecrc -
+</pre></div>
+
+<a name="pgs_005fframe_005fmerge"></a>
+<h3 class="section">2.26 pgs_frame_merge<span class="pull-right"><a class="anchor hidden-xs" href="#pgs_005fframe_005fmerge" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-pgs_005fframe_005fmerge" aria-hidden="true">TOC</a></span></h3>
+
+<p>Merge a sequence of PGS Subtitle segments ending with an &quot;end of display set&quot;
+segment into a single packet.
+</p>
+<p>This is required by some containers that support PGS subtitles
+(muxer <code class="code">matroska</code>).
+</p>
+<a name="prores_005fmetadata"></a>
+<h3 class="section">2.27 prores_metadata<span class="pull-right"><a class="anchor hidden-xs" href="#prores_005fmetadata" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-prores_005fmetadata" aria-hidden="true">TOC</a></span></h3>
+
+<p>Modify color property metadata embedded in prores stream.
+</p>
+<dl class="table">
+<dt><samp class="option">color_primaries</samp></dt>
+<dd><p>Set the color primaries.
+Available values are:
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">auto</samp>&rsquo;</dt>
+<dd><p>Keep the same color primaries property (default).
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">unknown</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bt709</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bt470bg</samp>&rsquo;</dt>
+<dd><p>BT601 625
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">smpte170m</samp>&rsquo;</dt>
+<dd><p>BT601 525
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">bt2020</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">smpte431</samp>&rsquo;</dt>
+<dd><p>DCI P3
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">smpte432</samp>&rsquo;</dt>
+<dd><p>P3 D65
+</p>
+</dd>
+</dl>
+
+</dd>
+<dt><samp class="option">transfer_characteristics</samp></dt>
+<dd><p>Set the color transfer.
+Available values are:
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">auto</samp>&rsquo;</dt>
+<dd><p>Keep the same transfer characteristics property (default).
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">unknown</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bt709</samp>&rsquo;</dt>
+<dd><p>BT 601, BT 709, BT 2020
+</p></dd>
+<dt>&lsquo;<samp class="samp">smpte2084</samp>&rsquo;</dt>
+<dd><p>SMPTE ST 2084
+</p></dd>
+<dt>&lsquo;<samp class="samp">arib-std-b67</samp>&rsquo;</dt>
+<dd><p>ARIB STD-B67
+</p></dd>
+</dl>
+
+
+</dd>
+<dt><samp class="option">matrix_coefficients</samp></dt>
+<dd><p>Set the matrix coefficient.
+Available values are:
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">auto</samp>&rsquo;</dt>
+<dd><p>Keep the same colorspace property (default).
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">unknown</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bt709</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">smpte170m</samp>&rsquo;</dt>
+<dd><p>BT 601
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">bt2020nc</samp>&rsquo;</dt>
+</dl>
+</dd>
+</dl>
+
+<p>Set Rec709 colorspace for each frame of the file
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c copy -bsf:v prores_metadata=color_primaries=bt709:color_trc=bt709:colorspace=bt709 output.mov
+</pre></div>
+
+<p>Set Hybrid Log-Gamma parameters for each frame of the file
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c copy -bsf:v prores_metadata=color_primaries=bt2020:color_trc=arib-std-b67:colorspace=bt2020nc output.mov
+</pre></div>
+
+<a name="remove_005fextra"></a>
+<h3 class="section">2.28 remove_extra<span class="pull-right"><a class="anchor hidden-xs" href="#remove_005fextra" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-remove_005fextra" aria-hidden="true">TOC</a></span></h3>
+
+<p>Remove extradata from packets.
+</p>
+<p>It accepts the following parameter:
+</p><dl class="table">
+<dt><samp class="option">freq</samp></dt>
+<dd><p>Set which frame types to remove extradata from.
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">k</samp>&rsquo;</dt>
+<dd><p>Remove extradata from non-keyframes only.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">keyframe</samp>&rsquo;</dt>
+<dd><p>Remove extradata from keyframes only.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">e, all</samp>&rsquo;</dt>
+<dd><p>Remove extradata from all frames.
+</p>
+</dd>
+</dl>
+</dd>
+</dl>
+
+<a name="setts"></a>
+<h3 class="section">2.29 setts<span class="pull-right"><a class="anchor hidden-xs" href="#setts" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-setts" aria-hidden="true">TOC</a></span></h3>
+<p>Set PTS and DTS in packets.
+</p>
+<p>It accepts the following parameters:
+</p><dl class="table">
+<dt><samp class="option">ts</samp></dt>
+<dt><samp class="option">pts</samp></dt>
+<dt><samp class="option">dts</samp></dt>
+<dd><p>Set expressions for PTS, DTS or both.
+</p></dd>
+<dt><samp class="option">duration</samp></dt>
+<dd><p>Set expression for duration.
+</p></dd>
+<dt><samp class="option">time_base</samp></dt>
+<dd><p>Set output time base.
+</p></dd>
+</dl>
+
+<p>The expressions are evaluated through the eval API and can contain the following
+constants:
+</p>
+<dl class="table">
+<dt><samp class="option">N</samp></dt>
+<dd><p>The count of the input packet. Starting from 0.
+</p>
+</dd>
+<dt><samp class="option">TS</samp></dt>
+<dd><p>The demux timestamp in input in case of <code class="code">ts</code> or <code class="code">dts</code> option or presentation
+timestamp in case of <code class="code">pts</code> option.
+</p>
+</dd>
+<dt><samp class="option">POS</samp></dt>
+<dd><p>The original position in the file of the packet, or undefined if undefined
+for the current packet
+</p>
+</dd>
+<dt><samp class="option">DTS</samp></dt>
+<dd><p>The demux timestamp in input.
+</p>
+</dd>
+<dt><samp class="option">PTS</samp></dt>
+<dd><p>The presentation timestamp in input.
+</p>
+</dd>
+<dt><samp class="option">DURATION</samp></dt>
+<dd><p>The duration in input.
+</p>
+</dd>
+<dt><samp class="option">STARTDTS</samp></dt>
+<dd><p>The DTS of the first packet.
+</p>
+</dd>
+<dt><samp class="option">STARTPTS</samp></dt>
+<dd><p>The PTS of the first packet.
+</p>
+</dd>
+<dt><samp class="option">PREV_INDTS</samp></dt>
+<dd><p>The previous input DTS.
+</p>
+</dd>
+<dt><samp class="option">PREV_INPTS</samp></dt>
+<dd><p>The previous input PTS.
+</p>
+</dd>
+<dt><samp class="option">PREV_INDURATION</samp></dt>
+<dd><p>The previous input duration.
+</p>
+</dd>
+<dt><samp class="option">PREV_OUTDTS</samp></dt>
+<dd><p>The previous output DTS.
+</p>
+</dd>
+<dt><samp class="option">PREV_OUTPTS</samp></dt>
+<dd><p>The previous output PTS.
+</p>
+</dd>
+<dt><samp class="option">PREV_OUTDURATION</samp></dt>
+<dd><p>The previous output duration.
+</p>
+</dd>
+<dt><samp class="option">NEXT_DTS</samp></dt>
+<dd><p>The next input DTS.
+</p>
+</dd>
+<dt><samp class="option">NEXT_PTS</samp></dt>
+<dd><p>The next input PTS.
+</p>
+</dd>
+<dt><samp class="option">NEXT_DURATION</samp></dt>
+<dd><p>The next input duration.
+</p>
+</dd>
+<dt><samp class="option">TB</samp></dt>
+<dd><p>The timebase of stream packet belongs.
+</p>
+</dd>
+<dt><samp class="option">TB_OUT</samp></dt>
+<dd><p>The output timebase.
+</p>
+</dd>
+<dt><samp class="option">SR</samp></dt>
+<dd><p>The sample rate of stream packet belongs.
+</p>
+</dd>
+<dt><samp class="option">NOPTS</samp></dt>
+<dd><p>The AV_NOPTS_VALUE constant.
+</p></dd>
+</dl>
+
+<p>For example, to set PTS equal to DTS (not recommended if B-frames are involved):
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -c:a copy -bsf:a setts=pts=DTS out.mkv
+</pre></div>
+
+<a name="showinfo"></a>
+<h3 class="section">2.30 showinfo<span class="pull-right"><a class="anchor hidden-xs" href="#showinfo" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-showinfo" aria-hidden="true">TOC</a></span></h3>
+<p>Log basic packet information. Mainly useful for testing, debugging,
+and development.
+</p>
+<a class="anchor" id="text2movsub"></a><a name="text2movsub-1"></a>
+<h3 class="section">2.31 text2movsub<span class="pull-right"><a class="anchor hidden-xs" href="#text2movsub-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-text2movsub-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>Convert text subtitles to MOV subtitles (as used by the <code class="code">mov_text</code>
+codec) with metadata headers.
+</p>
+<p>See also the <a class="ref" href="#mov2textsub">mov2textsub</a> filter.
+</p>
+<a name="trace_005fheaders"></a>
+<h3 class="section">2.32 trace_headers<span class="pull-right"><a class="anchor hidden-xs" href="#trace_005fheaders" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-trace_005fheaders" aria-hidden="true">TOC</a></span></h3>
+
+<p>Log trace output containing all syntax elements in the coded stream
+headers (everything above the level of individual coded blocks).
+This can be useful for debugging low-level stream issues.
+</p>
+<p>Supports AV1, H.264, H.265, (M)JPEG, MPEG-2 and VP9, but depending
+on the build only a subset of these may be available.
+</p>
+<a name="truehd_005fcore"></a>
+<h3 class="section">2.33 truehd_core<span class="pull-right"><a class="anchor hidden-xs" href="#truehd_005fcore" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-truehd_005fcore" aria-hidden="true">TOC</a></span></h3>
+
+<p>Extract the core from a TrueHD stream, dropping ATMOS data.
+</p>
+<a name="vp9_005fmetadata"></a>
+<h3 class="section">2.34 vp9_metadata<span class="pull-right"><a class="anchor hidden-xs" href="#vp9_005fmetadata" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-vp9_005fmetadata" aria-hidden="true">TOC</a></span></h3>
+
+<p>Modify metadata embedded in a VP9 stream.
+</p>
+<dl class="table">
+<dt><samp class="option">color_space</samp></dt>
+<dd><p>Set the color space value in the frame header.  Note that any frame
+set to RGB will be implicitly set to PC range and that RGB is
+incompatible with profiles 0 and 2.
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">unknown</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bt601</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bt709</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">smpte170</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">smpte240</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bt2020</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">rgb</samp>&rsquo;</dt>
+</dl>
+
+</dd>
+<dt><samp class="option">color_range</samp></dt>
+<dd><p>Set the color range value in the frame header.  Note that any value
+imposed by the color space will take precedence over this value.
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">tv</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">pc</samp>&rsquo;</dt>
+</dl>
+</dd>
+</dl>
+
+<a name="vp9_005fsuperframe"></a>
+<h3 class="section">2.35 vp9_superframe<span class="pull-right"><a class="anchor hidden-xs" href="#vp9_005fsuperframe" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-vp9_005fsuperframe" aria-hidden="true">TOC</a></span></h3>
+
+<p>Merge VP9 invisible (alt-ref) frames back into VP9 superframes. This
+fixes merging of split/segmented VP9 streams where the alt-ref frame
+was split from its visible counterpart.
+</p>
+<a name="vp9_005fsuperframe_005fsplit"></a>
+<h3 class="section">2.36 vp9_superframe_split<span class="pull-right"><a class="anchor hidden-xs" href="#vp9_005fsuperframe_005fsplit" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-vp9_005fsuperframe_005fsplit" aria-hidden="true">TOC</a></span></h3>
+
+<p>Split VP9 superframes into single frames.
+</p>
+<a name="vp9_005fraw_005freorder"></a>
+<h3 class="section">2.37 vp9_raw_reorder<span class="pull-right"><a class="anchor hidden-xs" href="#vp9_005fraw_005freorder" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-vp9_005fraw_005freorder" aria-hidden="true">TOC</a></span></h3>
+
+<p>Given a VP9 stream with correct timestamps but possibly out of order,
+insert additional show-existing-frame packets to correct the ordering.
+</p>
+
+<a name="See-Also"></a>
+<h2 class="chapter">3 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="libavcodec.html">libavcodec</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">4 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/ffmpeg-resampler.html

@@ -0,0 +1,350 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      FFmpeg Resampler Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      FFmpeg Resampler Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-Resampler-Options" href="#Resampler-Options">2 Resampler Options</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">3 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">4 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg resampler provides a high-level interface to the
+libswresample library audio resampling utilities. In particular it
+allows one to perform audio resampling, audio channel layout rematrixing,
+and convert audio format and packing layout.
+</p>
+
+<a name="Resampler-Options"></a>
+<h2 class="chapter">2 Resampler Options<span class="pull-right"><a class="anchor hidden-xs" href="#Resampler-Options" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Resampler-Options" aria-hidden="true">TOC</a></span></h2>
+
+<p>The audio resampler supports the following named options.
+</p>
+<p>Options may be set by specifying -<var class="var">option</var> <var class="var">value</var> in the
+FFmpeg tools, <var class="var">option</var>=<var class="var">value</var> for the aresample filter,
+by setting the value explicitly in the
+<code class="code">SwrContext</code> options or using the <samp class="file">libavutil/opt.h</samp> API for
+programmatic use.
+</p>
+<dl class="table">
+<dt><samp class="option">uchl, used_chlayout</samp></dt>
+<dd><p>Set used input channel layout. Default is unset. This option is
+only used for special remapping.
+</p>
+</dd>
+<dt><samp class="option">isr, in_sample_rate</samp></dt>
+<dd><p>Set the input sample rate. Default value is 0.
+</p>
+</dd>
+<dt><samp class="option">osr, out_sample_rate</samp></dt>
+<dd><p>Set the output sample rate. Default value is 0.
+</p>
+</dd>
+<dt><samp class="option">isf, in_sample_fmt</samp></dt>
+<dd><p>Specify the input sample format. It is set by default to <code class="code">none</code>.
+</p>
+</dd>
+<dt><samp class="option">osf, out_sample_fmt</samp></dt>
+<dd><p>Specify the output sample format. It is set by default to <code class="code">none</code>.
+</p>
+</dd>
+<dt><samp class="option">tsf, internal_sample_fmt</samp></dt>
+<dd><p>Set the internal sample format. Default value is <code class="code">none</code>.
+This will automatically be chosen when it is not explicitly set.
+</p>
+</dd>
+<dt><samp class="option">ichl, in_chlayout</samp></dt>
+<dt><samp class="option">ochl, out_chlayout</samp></dt>
+<dd><p>Set the input/output channel layout.
+</p>
+<p>See <a data-manual="ffmpeg-utils" href="ffmpeg-utils.html#channel-layout-syntax">the Channel Layout section in the ffmpeg-utils(1) manual</a>
+for the required syntax.
+</p>
+</dd>
+<dt><samp class="option">clev, center_mix_level</samp></dt>
+<dd><p>Set the center mix level. It is a value expressed in deciBel, and must be
+in the interval [-32,32].
+</p>
+</dd>
+<dt><samp class="option">slev, surround_mix_level</samp></dt>
+<dd><p>Set the surround mix level. It is a value expressed in deciBel, and must
+be in the interval [-32,32].
+</p>
+</dd>
+<dt><samp class="option">lfe_mix_level</samp></dt>
+<dd><p>Set LFE mix into non LFE level. It is used when there is a LFE input but no
+LFE output. It is a value expressed in deciBel, and must
+be in the interval [-32,32].
+</p>
+</dd>
+<dt><samp class="option">rmvol, rematrix_volume</samp></dt>
+<dd><p>Set rematrix volume. Default value is 1.0.
+</p>
+</dd>
+<dt><samp class="option">rematrix_maxval</samp></dt>
+<dd><p>Set maximum output value for rematrixing.
+This can be used to prevent clipping vs. preventing volume reduction.
+A value of 1.0 prevents clipping.
+</p>
+</dd>
+<dt><samp class="option">flags, swr_flags</samp></dt>
+<dd><p>Set flags used by the converter. Default value is 0.
+</p>
+<p>It supports the following individual flags:
+</p><dl class="table">
+<dt><samp class="option">res</samp></dt>
+<dd><p>force resampling, this flag forces resampling to be used even when the
+input and output sample rates match.
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">dither_scale</samp></dt>
+<dd><p>Set the dither scale. Default value is 1.
+</p>
+</dd>
+<dt><samp class="option">dither_method</samp></dt>
+<dd><p>Set dither method. Default value is 0.
+</p>
+<p>Supported values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">rectangular</samp>&rsquo;</dt>
+<dd><p>select rectangular dither
+</p></dd>
+<dt>&lsquo;<samp class="samp">triangular</samp>&rsquo;</dt>
+<dd><p>select triangular dither
+</p></dd>
+<dt>&lsquo;<samp class="samp">triangular_hp</samp>&rsquo;</dt>
+<dd><p>select triangular dither with high pass
+</p></dd>
+<dt>&lsquo;<samp class="samp">lipshitz</samp>&rsquo;</dt>
+<dd><p>select Lipshitz noise shaping dither.
+</p></dd>
+<dt>&lsquo;<samp class="samp">shibata</samp>&rsquo;</dt>
+<dd><p>select Shibata noise shaping dither.
+</p></dd>
+<dt>&lsquo;<samp class="samp">low_shibata</samp>&rsquo;</dt>
+<dd><p>select low Shibata noise shaping dither.
+</p></dd>
+<dt>&lsquo;<samp class="samp">high_shibata</samp>&rsquo;</dt>
+<dd><p>select high Shibata noise shaping dither.
+</p></dd>
+<dt>&lsquo;<samp class="samp">f_weighted</samp>&rsquo;</dt>
+<dd><p>select f-weighted noise shaping dither
+</p></dd>
+<dt>&lsquo;<samp class="samp">modified_e_weighted</samp>&rsquo;</dt>
+<dd><p>select modified-e-weighted noise shaping dither
+</p></dd>
+<dt>&lsquo;<samp class="samp">improved_e_weighted</samp>&rsquo;</dt>
+<dd><p>select improved-e-weighted noise shaping dither
+</p>
+</dd>
+</dl>
+
+</dd>
+<dt><samp class="option">resampler</samp></dt>
+<dd><p>Set resampling engine. Default value is swr.
+</p>
+<p>Supported values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">swr</samp>&rsquo;</dt>
+<dd><p>select the native SW Resampler; filter options precision and cheby are not
+applicable in this case.
+</p></dd>
+<dt>&lsquo;<samp class="samp">soxr</samp>&rsquo;</dt>
+<dd><p>select the SoX Resampler (where available); compensation, and filter options
+filter_size, phase_shift, exact_rational, filter_type &amp; kaiser_beta, are not
+applicable in this case.
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">filter_size</samp></dt>
+<dd><p>For swr only, set resampling filter size, default value is 32.
+</p>
+</dd>
+<dt><samp class="option">phase_shift</samp></dt>
+<dd><p>For swr only, set resampling phase shift, default value is 10, and must be in
+the interval [0,30].
+</p>
+</dd>
+<dt><samp class="option">linear_interp</samp></dt>
+<dd><p>Use linear interpolation when enabled (the default). Disable it if you want
+to preserve speed instead of quality when exact_rational fails.
+</p>
+</dd>
+<dt><samp class="option">exact_rational</samp></dt>
+<dd><p>For swr only, when enabled, try to use exact phase_count based on input and
+output sample rate. However, if it is larger than <code class="code">1 &lt;&lt; phase_shift</code>,
+the phase_count will be <code class="code">1 &lt;&lt; phase_shift</code> as fallback. Default is enabled.
+</p>
+</dd>
+<dt><samp class="option">cutoff</samp></dt>
+<dd><p>Set cutoff frequency (swr: 6dB point; soxr: 0dB point) ratio; must be a float
+value between 0 and 1.  Default value is 0.97 with swr, and 0.91 with soxr
+(which, with a sample-rate of 44100, preserves the entire audio band to 20kHz).
+</p>
+</dd>
+<dt><samp class="option">precision</samp></dt>
+<dd><p>For soxr only, the precision in bits to which the resampled signal will be
+calculated.  The default value of 20 (which, with suitable dithering, is
+appropriate for a destination bit-depth of 16) gives SoX&rsquo;s &rsquo;High Quality&rsquo;; a
+value of 28 gives SoX&rsquo;s &rsquo;Very High Quality&rsquo;.
+</p>
+</dd>
+<dt><samp class="option">cheby</samp></dt>
+<dd><p>For soxr only, selects passband rolloff none (Chebyshev) &amp; higher-precision
+approximation for &rsquo;irrational&rsquo; ratios. Default value is 0.
+</p>
+</dd>
+<dt><samp class="option">async</samp></dt>
+<dd><p>For swr only, simple 1 parameter audio sync to timestamps using stretching,
+squeezing, filling and trimming. Setting this to 1 will enable filling and
+trimming, larger values represent the maximum amount in samples that the data
+may be stretched or squeezed for each second.
+Default value is 0, thus no compensation is applied to make the samples match
+the audio timestamps.
+</p>
+</dd>
+<dt><samp class="option">first_pts</samp></dt>
+<dd><p>For swr only, assume the first pts should be this value. The time unit is 1 / sample rate.
+This allows for padding/trimming at the start of stream. By default, no
+assumption is made about the first frame&rsquo;s expected pts, so no padding or
+trimming is done. For example, this could be set to 0 to pad the beginning with
+silence if an audio stream starts after the video stream or to trim any samples
+with a negative pts due to encoder delay.
+</p>
+</dd>
+<dt><samp class="option">min_comp</samp></dt>
+<dd><p>For swr only, set the minimum difference between timestamps and audio data (in
+seconds) to trigger stretching/squeezing/filling or trimming of the
+data to make it match the timestamps. The default is that
+stretching/squeezing/filling and trimming is disabled
+(<samp class="option">min_comp</samp> = <code class="code">FLT_MAX</code>).
+</p>
+</dd>
+<dt><samp class="option">min_hard_comp</samp></dt>
+<dd><p>For swr only, set the minimum difference between timestamps and audio data (in
+seconds) to trigger adding/dropping samples to make it match the
+timestamps.  This option effectively is a threshold to select between
+hard (trim/fill) and soft (squeeze/stretch) compensation. Note that
+all compensation is by default disabled through <samp class="option">min_comp</samp>.
+The default is 0.1.
+</p>
+</dd>
+<dt><samp class="option">comp_duration</samp></dt>
+<dd><p>For swr only, set duration (in seconds) over which data is stretched/squeezed
+to make it match the timestamps. Must be a non-negative double float value,
+default value is 1.0.
+</p>
+</dd>
+<dt><samp class="option">max_soft_comp</samp></dt>
+<dd><p>For swr only, set maximum factor by which data is stretched/squeezed to make it
+match the timestamps. Must be a non-negative double float value, default value
+is 0.
+</p>
+</dd>
+<dt><samp class="option">matrix_encoding</samp></dt>
+<dd><p>Select matrixed stereo encoding.
+</p>
+<p>It accepts the following values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">none</samp>&rsquo;</dt>
+<dd><p>select none
+</p></dd>
+<dt>&lsquo;<samp class="samp">dolby</samp>&rsquo;</dt>
+<dd><p>select Dolby
+</p></dd>
+<dt>&lsquo;<samp class="samp">dplii</samp>&rsquo;</dt>
+<dd><p>select Dolby Pro Logic II
+</p></dd>
+</dl>
+
+<p>Default value is <code class="code">none</code>.
+</p>
+</dd>
+<dt><samp class="option">filter_type</samp></dt>
+<dd><p>For swr only, select resampling filter type. This only affects resampling
+operations.
+</p>
+<p>It accepts the following values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">cubic</samp>&rsquo;</dt>
+<dd><p>select cubic
+</p></dd>
+<dt>&lsquo;<samp class="samp">blackman_nuttall</samp>&rsquo;</dt>
+<dd><p>select Blackman Nuttall windowed sinc
+</p></dd>
+<dt>&lsquo;<samp class="samp">kaiser</samp>&rsquo;</dt>
+<dd><p>select Kaiser windowed sinc
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">kaiser_beta</samp></dt>
+<dd><p>For swr only, set Kaiser window beta value. Must be a double float value in the
+interval [2,16], default value is 9.
+</p>
+</dd>
+<dt><samp class="option">output_sample_bits</samp></dt>
+<dd><p>For swr only, set number of used output sample bits for dithering. Must be an integer in the
+interval [0,64], default value is 0, which means it&rsquo;s not used.
+</p>
+</dd>
+</dl>
+
+
+<a name="See-Also"></a>
+<h2 class="chapter">3 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="libswresample.html">libswresample</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">4 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/ffmpeg-scaler.html

@@ -0,0 +1,254 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      FFmpeg Scaler Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      FFmpeg Scaler Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-Scaler-Options" href="#Scaler-Options">2 Scaler Options</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">3 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">4 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg rescaler provides a high-level interface to the libswscale
+library image conversion utilities. In particular it allows one to perform
+image rescaling and pixel format conversion.
+</p>
+
+<a class="anchor" id="scaler_005foptions"></a><a name="Scaler-Options"></a>
+<h2 class="chapter">2 Scaler Options<span class="pull-right"><a class="anchor hidden-xs" href="#Scaler-Options" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Scaler-Options" aria-hidden="true">TOC</a></span></h2>
+
+<p>The video scaler supports the following named options.
+</p>
+<p>Options may be set by specifying -<var class="var">option</var> <var class="var">value</var> in the
+FFmpeg tools, with a few API-only exceptions noted below.
+For programmatic use, they can be set explicitly in the
+<code class="code">SwsContext</code> options or through the <samp class="file">libavutil/opt.h</samp> API.
+</p>
+<dl class="table">
+<dd>
+<a class="anchor" id="sws_005fflags"></a></dd>
+<dt><samp class="option">sws_flags</samp></dt>
+<dd><p>Set the scaler flags. This is also used to set the scaling
+algorithm. Only a single algorithm should be selected. Default
+value is &lsquo;<samp class="samp">bicubic</samp>&rsquo;.
+</p>
+<p>It accepts the following values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">fast_bilinear</samp>&rsquo;</dt>
+<dd><p>Select fast bilinear scaling algorithm.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">bilinear</samp>&rsquo;</dt>
+<dd><p>Select bilinear scaling algorithm.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">bicubic</samp>&rsquo;</dt>
+<dd><p>Select bicubic scaling algorithm.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">experimental</samp>&rsquo;</dt>
+<dd><p>Select experimental scaling algorithm.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">neighbor</samp>&rsquo;</dt>
+<dd><p>Select nearest neighbor rescaling algorithm.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">area</samp>&rsquo;</dt>
+<dd><p>Select averaging area rescaling algorithm.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">bicublin</samp>&rsquo;</dt>
+<dd><p>Select bicubic scaling algorithm for the luma component, bilinear for
+chroma components.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">gauss</samp>&rsquo;</dt>
+<dd><p>Select Gaussian rescaling algorithm.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">sinc</samp>&rsquo;</dt>
+<dd><p>Select sinc rescaling algorithm.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">lanczos</samp>&rsquo;</dt>
+<dd><p>Select Lanczos rescaling algorithm. The default width (alpha) is 3 and can be
+changed by setting <code class="code">param0</code>.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">spline</samp>&rsquo;</dt>
+<dd><p>Select natural bicubic spline rescaling algorithm.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">print_info</samp>&rsquo;</dt>
+<dd><p>Enable printing/debug logging.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">accurate_rnd</samp>&rsquo;</dt>
+<dd><p>Enable accurate rounding.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">full_chroma_int</samp>&rsquo;</dt>
+<dd><p>Enable full chroma interpolation.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">full_chroma_inp</samp>&rsquo;</dt>
+<dd><p>Select full chroma input.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">bitexact</samp>&rsquo;</dt>
+<dd><p>Enable bitexact output.
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">srcw <var class="var">(API only)</var></samp></dt>
+<dd><p>Set source width.
+</p>
+</dd>
+<dt><samp class="option">srch <var class="var">(API only)</var></samp></dt>
+<dd><p>Set source height.
+</p>
+</dd>
+<dt><samp class="option">dstw <var class="var">(API only)</var></samp></dt>
+<dd><p>Set destination width.
+</p>
+</dd>
+<dt><samp class="option">dsth <var class="var">(API only)</var></samp></dt>
+<dd><p>Set destination height.
+</p>
+</dd>
+<dt><samp class="option">src_format <var class="var">(API only)</var></samp></dt>
+<dd><p>Set source pixel format (must be expressed as an integer).
+</p>
+</dd>
+<dt><samp class="option">dst_format <var class="var">(API only)</var></samp></dt>
+<dd><p>Set destination pixel format (must be expressed as an integer).
+</p>
+</dd>
+<dt><samp class="option">src_range <var class="var">(boolean)</var></samp></dt>
+<dd><p>If value is set to <code class="code">1</code>, indicates source is full range. Default value is
+<code class="code">0</code>, which indicates source is limited range.
+</p>
+</dd>
+<dt><samp class="option">dst_range <var class="var">(boolean)</var></samp></dt>
+<dd><p>If value is set to <code class="code">1</code>, enable full range for destination. Default value
+is <code class="code">0</code>, which enables limited range.
+</p>
+<a class="anchor" id="sws_005fparams"></a></dd>
+<dt><samp class="option">param0, param1</samp></dt>
+<dd><p>Set scaling algorithm parameters. The specified values are specific of
+some scaling algorithms and ignored by others. The specified values
+are floating point number values.
+</p>
+</dd>
+<dt><samp class="option">sws_dither</samp></dt>
+<dd><p>Set the dithering algorithm. Accepts one of the following
+values. Default value is &lsquo;<samp class="samp">auto</samp>&rsquo;.
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">auto</samp>&rsquo;</dt>
+<dd><p>automatic choice
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">none</samp>&rsquo;</dt>
+<dd><p>no dithering
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">bayer</samp>&rsquo;</dt>
+<dd><p>bayer dither
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">ed</samp>&rsquo;</dt>
+<dd><p>error diffusion dither
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">a_dither</samp>&rsquo;</dt>
+<dd><p>arithmetic dither, based using addition
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">x_dither</samp>&rsquo;</dt>
+<dd><p>arithmetic dither, based using xor (more random/less apparent patterning that
+a_dither).
+</p>
+</dd>
+</dl>
+
+</dd>
+<dt><samp class="option">alphablend</samp></dt>
+<dd><p>Set the alpha blending to use when the input has alpha but the output does not.
+Default value is &lsquo;<samp class="samp">none</samp>&rsquo;.
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">uniform_color</samp>&rsquo;</dt>
+<dd><p>Blend onto a uniform background color
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">checkerboard</samp>&rsquo;</dt>
+<dd><p>Blend onto a checkerboard
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">none</samp>&rsquo;</dt>
+<dd><p>No blending
+</p>
+</dd>
+</dl>
+
+</dd>
+</dl>
+
+
+<a name="See-Also"></a>
+<h2 class="chapter">3 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="libswscale.html">libswscale</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">4 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/ffmpeg-utils.html

@@ -0,0 +1,1547 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      FFmpeg Utilities Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      FFmpeg Utilities Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-Syntax" href="#Syntax">2 Syntax</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Quoting-and-escaping" href="#Quoting-and-escaping">2.1 Quoting and escaping</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-Examples" href="#Examples">2.1.1 Examples</a></li>
+    </ul></li>
+    <li><a id="toc-Date" href="#Date">2.2 Date</a></li>
+    <li><a id="toc-Time-duration" href="#Time-duration">2.3 Time duration</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-Examples-1" href="#Examples-1">2.3.1 Examples</a></li>
+    </ul></li>
+    <li><a id="toc-Video-size" href="#Video-size">2.4 Video size</a></li>
+    <li><a id="toc-Video-rate" href="#Video-rate">2.5 Video rate</a></li>
+    <li><a id="toc-Ratio" href="#Ratio">2.6 Ratio</a></li>
+    <li><a id="toc-Color" href="#Color">2.7 Color</a></li>
+    <li><a id="toc-Channel-Layout" href="#Channel-Layout">2.8 Channel Layout</a></li>
+  </ul></li>
+  <li><a id="toc-Expression-Evaluation" href="#Expression-Evaluation">3 Expression Evaluation</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">4 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">5 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>This document describes some generic features and utilities provided
+by the libavutil library.
+</p>
+
+<a name="Syntax"></a>
+<h2 class="chapter">2 Syntax<span class="pull-right"><a class="anchor hidden-xs" href="#Syntax" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Syntax" aria-hidden="true">TOC</a></span></h2>
+
+<p>This section documents the syntax and formats employed by the FFmpeg
+libraries and tools.
+</p>
+<a class="anchor" id="quoting_005fand_005fescaping"></a><a name="Quoting-and-escaping"></a>
+<h3 class="section">2.1 Quoting and escaping<span class="pull-right"><a class="anchor hidden-xs" href="#Quoting-and-escaping" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Quoting-and-escaping" aria-hidden="true">TOC</a></span></h3>
+
+<p>FFmpeg adopts the following quoting and escaping mechanism, unless
+explicitly specified. The following rules are applied:
+</p>
+<ul class="itemize mark-bullet">
+<li>&lsquo;<samp class="samp">'</samp>&rsquo; and &lsquo;<samp class="samp">\</samp>&rsquo; are special characters (respectively used for
+quoting and escaping). In addition to them, there might be other
+special characters depending on the specific syntax where the escaping
+and quoting are employed.
+
+</li><li>A special character is escaped by prefixing it with a &lsquo;<samp class="samp">\</samp>&rsquo;.
+
+</li><li>All characters enclosed between &lsquo;<samp class="samp">''</samp>&rsquo; are included literally in the
+parsed string. The quote character &lsquo;<samp class="samp">'</samp>&rsquo; itself cannot be quoted,
+so you may need to close the quote and escape it.
+
+</li><li>Leading and trailing whitespaces, unless escaped or quoted, are
+removed from the parsed string.
+</li></ul>
+
+<p>Note that you may need to add a second level of escaping when using
+the command line or a script, which depends on the syntax of the
+adopted shell language.
+</p>
+<p>The function <code class="code">av_get_token</code> defined in
+<samp class="file">libavutil/avstring.h</samp> can be used to parse a token quoted or
+escaped according to the rules defined above.
+</p>
+<p>The tool <samp class="file">tools/ffescape</samp> in the FFmpeg source tree can be used
+to automatically quote or escape a string in a script.
+</p>
+<a name="Examples"></a>
+<h4 class="subsection">2.1.1 Examples<span class="pull-right"><a class="anchor hidden-xs" href="#Examples" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Examples" aria-hidden="true">TOC</a></span></h4>
+
+<ul class="itemize mark-bullet">
+<li>Escape the string <code class="code">Crime d'Amour</code> containing the <code class="code">'</code> special
+character:
+<div class="example">
+<pre class="example-preformatted">Crime d\'Amour
+</pre></div>
+
+</li><li>The string above contains a quote, so the <code class="code">'</code> needs to be escaped
+when quoting it:
+<div class="example">
+<pre class="example-preformatted">'Crime d'\''Amour'
+</pre></div>
+
+</li><li>Include leading or trailing whitespaces using quoting:
+<div class="example">
+<pre class="example-preformatted">'  this string starts and ends with whitespaces  '
+</pre></div>
+
+</li><li>Escaping and quoting can be mixed together:
+<div class="example">
+<pre class="example-preformatted">' The string '\'string\'' is a string '
+</pre></div>
+
+</li><li>To include a literal &lsquo;<samp class="samp">\</samp>&rsquo; you can use either escaping or quoting:
+<div class="example">
+<pre class="example-preformatted">'c:\foo' can be written as c:\\foo
+</pre></div>
+</li></ul>
+
+<a class="anchor" id="date-syntax"></a><a name="Date"></a>
+<h3 class="section">2.2 Date<span class="pull-right"><a class="anchor hidden-xs" href="#Date" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Date" aria-hidden="true">TOC</a></span></h3>
+
+<p>The accepted syntax is:
+</p><div class="example">
+<pre class="example-preformatted">[(YYYY-MM-DD|YYYYMMDD)[T|t| ]]((HH:MM:SS[.m...]]])|(HHMMSS[.m...]]]))[Z]
+now
+</pre></div>
+
+<p>If the value is &quot;now&quot; it takes the current time.
+</p>
+<p>Time is local time unless Z is appended, in which case it is
+interpreted as UTC.
+If the year-month-day part is not specified it takes the current
+year-month-day.
+</p>
+<a class="anchor" id="time-duration-syntax"></a><a name="Time-duration"></a>
+<h3 class="section">2.3 Time duration<span class="pull-right"><a class="anchor hidden-xs" href="#Time-duration" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Time-duration" aria-hidden="true">TOC</a></span></h3>
+
+<p>There are two accepted syntaxes for expressing time duration.
+</p>
+<div class="example">
+<pre class="example-preformatted">[-][<var class="var">HH</var>:]<var class="var">MM</var>:<var class="var">SS</var>[.<var class="var">m</var>...]
+</pre></div>
+
+<p><var class="var">HH</var> expresses the number of hours, <var class="var">MM</var> the number of minutes
+for a maximum of 2 digits, and <var class="var">SS</var> the number of seconds for a
+maximum of 2 digits. The <var class="var">m</var> at the end expresses decimal value for
+<var class="var">SS</var>.
+</p>
+<p><em class="emph">or</em>
+</p>
+<div class="example">
+<pre class="example-preformatted">[-]<var class="var">S</var>+[.<var class="var">m</var>...][s|ms|us]
+</pre></div>
+
+<p><var class="var">S</var> expresses the number of seconds, with the optional decimal part
+<var class="var">m</var>.  The optional literal suffixes &lsquo;<samp class="samp">s</samp>&rsquo;, &lsquo;<samp class="samp">ms</samp>&rsquo; or &lsquo;<samp class="samp">us</samp>&rsquo;
+indicate to interpret the value as seconds, milliseconds or microseconds,
+respectively.
+</p>
+<p>In both expressions, the optional &lsquo;<samp class="samp">-</samp>&rsquo; indicates negative duration.
+</p>
+<a name="Examples-1"></a>
+<h4 class="subsection">2.3.1 Examples<span class="pull-right"><a class="anchor hidden-xs" href="#Examples-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Examples-1" aria-hidden="true">TOC</a></span></h4>
+
+<p>The following examples are all valid time duration:
+</p>
+<dl class="table">
+<dt>&lsquo;<samp class="samp">55</samp>&rsquo;</dt>
+<dd><p>55 seconds
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">0.2</samp>&rsquo;</dt>
+<dd><p>0.2 seconds
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">200ms</samp>&rsquo;</dt>
+<dd><p>200 milliseconds, that&rsquo;s 0.2s
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">200000us</samp>&rsquo;</dt>
+<dd><p>200000 microseconds, that&rsquo;s 0.2s
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">12:03:45</samp>&rsquo;</dt>
+<dd><p>12 hours, 03 minutes and 45 seconds
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">23.189</samp>&rsquo;</dt>
+<dd><p>23.189 seconds
+</p></dd>
+</dl>
+
+<a class="anchor" id="video-size-syntax"></a><a name="Video-size"></a>
+<h3 class="section">2.4 Video size<span class="pull-right"><a class="anchor hidden-xs" href="#Video-size" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Video-size" aria-hidden="true">TOC</a></span></h3>
+<p>Specify the size of the sourced video, it may be a string of the form
+<var class="var">width</var>x<var class="var">height</var>, or the name of a size abbreviation.
+</p>
+<p>The following abbreviations are recognized:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">ntsc</samp>&rsquo;</dt>
+<dd><p>720x480
+</p></dd>
+<dt>&lsquo;<samp class="samp">pal</samp>&rsquo;</dt>
+<dd><p>720x576
+</p></dd>
+<dt>&lsquo;<samp class="samp">qntsc</samp>&rsquo;</dt>
+<dd><p>352x240
+</p></dd>
+<dt>&lsquo;<samp class="samp">qpal</samp>&rsquo;</dt>
+<dd><p>352x288
+</p></dd>
+<dt>&lsquo;<samp class="samp">sntsc</samp>&rsquo;</dt>
+<dd><p>640x480
+</p></dd>
+<dt>&lsquo;<samp class="samp">spal</samp>&rsquo;</dt>
+<dd><p>768x576
+</p></dd>
+<dt>&lsquo;<samp class="samp">film</samp>&rsquo;</dt>
+<dd><p>352x240
+</p></dd>
+<dt>&lsquo;<samp class="samp">ntsc-film</samp>&rsquo;</dt>
+<dd><p>352x240
+</p></dd>
+<dt>&lsquo;<samp class="samp">sqcif</samp>&rsquo;</dt>
+<dd><p>128x96
+</p></dd>
+<dt>&lsquo;<samp class="samp">qcif</samp>&rsquo;</dt>
+<dd><p>176x144
+</p></dd>
+<dt>&lsquo;<samp class="samp">cif</samp>&rsquo;</dt>
+<dd><p>352x288
+</p></dd>
+<dt>&lsquo;<samp class="samp">4cif</samp>&rsquo;</dt>
+<dd><p>704x576
+</p></dd>
+<dt>&lsquo;<samp class="samp">16cif</samp>&rsquo;</dt>
+<dd><p>1408x1152
+</p></dd>
+<dt>&lsquo;<samp class="samp">qqvga</samp>&rsquo;</dt>
+<dd><p>160x120
+</p></dd>
+<dt>&lsquo;<samp class="samp">qvga</samp>&rsquo;</dt>
+<dd><p>320x240
+</p></dd>
+<dt>&lsquo;<samp class="samp">vga</samp>&rsquo;</dt>
+<dd><p>640x480
+</p></dd>
+<dt>&lsquo;<samp class="samp">svga</samp>&rsquo;</dt>
+<dd><p>800x600
+</p></dd>
+<dt>&lsquo;<samp class="samp">xga</samp>&rsquo;</dt>
+<dd><p>1024x768
+</p></dd>
+<dt>&lsquo;<samp class="samp">uxga</samp>&rsquo;</dt>
+<dd><p>1600x1200
+</p></dd>
+<dt>&lsquo;<samp class="samp">qxga</samp>&rsquo;</dt>
+<dd><p>2048x1536
+</p></dd>
+<dt>&lsquo;<samp class="samp">sxga</samp>&rsquo;</dt>
+<dd><p>1280x1024
+</p></dd>
+<dt>&lsquo;<samp class="samp">qsxga</samp>&rsquo;</dt>
+<dd><p>2560x2048
+</p></dd>
+<dt>&lsquo;<samp class="samp">hsxga</samp>&rsquo;</dt>
+<dd><p>5120x4096
+</p></dd>
+<dt>&lsquo;<samp class="samp">wvga</samp>&rsquo;</dt>
+<dd><p>852x480
+</p></dd>
+<dt>&lsquo;<samp class="samp">wxga</samp>&rsquo;</dt>
+<dd><p>1366x768
+</p></dd>
+<dt>&lsquo;<samp class="samp">wsxga</samp>&rsquo;</dt>
+<dd><p>1600x1024
+</p></dd>
+<dt>&lsquo;<samp class="samp">wuxga</samp>&rsquo;</dt>
+<dd><p>1920x1200
+</p></dd>
+<dt>&lsquo;<samp class="samp">woxga</samp>&rsquo;</dt>
+<dd><p>2560x1600
+</p></dd>
+<dt>&lsquo;<samp class="samp">wqsxga</samp>&rsquo;</dt>
+<dd><p>3200x2048
+</p></dd>
+<dt>&lsquo;<samp class="samp">wquxga</samp>&rsquo;</dt>
+<dd><p>3840x2400
+</p></dd>
+<dt>&lsquo;<samp class="samp">whsxga</samp>&rsquo;</dt>
+<dd><p>6400x4096
+</p></dd>
+<dt>&lsquo;<samp class="samp">whuxga</samp>&rsquo;</dt>
+<dd><p>7680x4800
+</p></dd>
+<dt>&lsquo;<samp class="samp">cga</samp>&rsquo;</dt>
+<dd><p>320x200
+</p></dd>
+<dt>&lsquo;<samp class="samp">ega</samp>&rsquo;</dt>
+<dd><p>640x350
+</p></dd>
+<dt>&lsquo;<samp class="samp">hd480</samp>&rsquo;</dt>
+<dd><p>852x480
+</p></dd>
+<dt>&lsquo;<samp class="samp">hd720</samp>&rsquo;</dt>
+<dd><p>1280x720
+</p></dd>
+<dt>&lsquo;<samp class="samp">hd1080</samp>&rsquo;</dt>
+<dd><p>1920x1080
+</p></dd>
+<dt>&lsquo;<samp class="samp">2k</samp>&rsquo;</dt>
+<dd><p>2048x1080
+</p></dd>
+<dt>&lsquo;<samp class="samp">2kflat</samp>&rsquo;</dt>
+<dd><p>1998x1080
+</p></dd>
+<dt>&lsquo;<samp class="samp">2kscope</samp>&rsquo;</dt>
+<dd><p>2048x858
+</p></dd>
+<dt>&lsquo;<samp class="samp">4k</samp>&rsquo;</dt>
+<dd><p>4096x2160
+</p></dd>
+<dt>&lsquo;<samp class="samp">4kflat</samp>&rsquo;</dt>
+<dd><p>3996x2160
+</p></dd>
+<dt>&lsquo;<samp class="samp">4kscope</samp>&rsquo;</dt>
+<dd><p>4096x1716
+</p></dd>
+<dt>&lsquo;<samp class="samp">nhd</samp>&rsquo;</dt>
+<dd><p>640x360
+</p></dd>
+<dt>&lsquo;<samp class="samp">hqvga</samp>&rsquo;</dt>
+<dd><p>240x160
+</p></dd>
+<dt>&lsquo;<samp class="samp">wqvga</samp>&rsquo;</dt>
+<dd><p>400x240
+</p></dd>
+<dt>&lsquo;<samp class="samp">fwqvga</samp>&rsquo;</dt>
+<dd><p>432x240
+</p></dd>
+<dt>&lsquo;<samp class="samp">hvga</samp>&rsquo;</dt>
+<dd><p>480x320
+</p></dd>
+<dt>&lsquo;<samp class="samp">qhd</samp>&rsquo;</dt>
+<dd><p>960x540
+</p></dd>
+<dt>&lsquo;<samp class="samp">2kdci</samp>&rsquo;</dt>
+<dd><p>2048x1080
+</p></dd>
+<dt>&lsquo;<samp class="samp">4kdci</samp>&rsquo;</dt>
+<dd><p>4096x2160
+</p></dd>
+<dt>&lsquo;<samp class="samp">uhd2160</samp>&rsquo;</dt>
+<dd><p>3840x2160
+</p></dd>
+<dt>&lsquo;<samp class="samp">uhd4320</samp>&rsquo;</dt>
+<dd><p>7680x4320
+</p></dd>
+</dl>
+
+<a class="anchor" id="video-rate-syntax"></a><a name="Video-rate"></a>
+<h3 class="section">2.5 Video rate<span class="pull-right"><a class="anchor hidden-xs" href="#Video-rate" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Video-rate" aria-hidden="true">TOC</a></span></h3>
+
+<p>Specify the frame rate of a video, expressed as the number of frames
+generated per second. It has to be a string in the format
+<var class="var">frame_rate_num</var>/<var class="var">frame_rate_den</var>, an integer number, a float
+number or a valid video frame rate abbreviation.
+</p>
+<p>The following abbreviations are recognized:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">ntsc</samp>&rsquo;</dt>
+<dd><p>30000/1001
+</p></dd>
+<dt>&lsquo;<samp class="samp">pal</samp>&rsquo;</dt>
+<dd><p>25/1
+</p></dd>
+<dt>&lsquo;<samp class="samp">qntsc</samp>&rsquo;</dt>
+<dd><p>30000/1001
+</p></dd>
+<dt>&lsquo;<samp class="samp">qpal</samp>&rsquo;</dt>
+<dd><p>25/1
+</p></dd>
+<dt>&lsquo;<samp class="samp">sntsc</samp>&rsquo;</dt>
+<dd><p>30000/1001
+</p></dd>
+<dt>&lsquo;<samp class="samp">spal</samp>&rsquo;</dt>
+<dd><p>25/1
+</p></dd>
+<dt>&lsquo;<samp class="samp">film</samp>&rsquo;</dt>
+<dd><p>24/1
+</p></dd>
+<dt>&lsquo;<samp class="samp">ntsc-film</samp>&rsquo;</dt>
+<dd><p>24000/1001
+</p></dd>
+</dl>
+
+<a class="anchor" id="ratio-syntax"></a><a name="Ratio"></a>
+<h3 class="section">2.6 Ratio<span class="pull-right"><a class="anchor hidden-xs" href="#Ratio" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Ratio" aria-hidden="true">TOC</a></span></h3>
+
+<p>A ratio can be expressed as an expression, or in the form
+<var class="var">numerator</var>:<var class="var">denominator</var>.
+</p>
+<p>Note that a ratio with infinite (1/0) or negative value is
+considered valid, so you should check on the returned value if you
+want to exclude those values.
+</p>
+<p>The undefined value can be expressed using the &quot;0:0&quot; string.
+</p>
+<a class="anchor" id="color-syntax"></a><a name="Color"></a>
+<h3 class="section">2.7 Color<span class="pull-right"><a class="anchor hidden-xs" href="#Color" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Color" aria-hidden="true">TOC</a></span></h3>
+
+<p>It can be the name of a color as defined below (case insensitive match) or a
+<code class="code">[0x|#]RRGGBB[AA]</code> sequence, possibly followed by @ and a string
+representing the alpha component.
+</p>
+<p>The alpha component may be a string composed by &quot;0x&quot; followed by an
+hexadecimal number or a decimal number between 0.0 and 1.0, which
+represents the opacity value (&lsquo;<samp class="samp">0x00</samp>&rsquo; or &lsquo;<samp class="samp">0.0</samp>&rsquo; means completely
+transparent, &lsquo;<samp class="samp">0xff</samp>&rsquo; or &lsquo;<samp class="samp">1.0</samp>&rsquo; completely opaque). If the alpha
+component is not specified then &lsquo;<samp class="samp">0xff</samp>&rsquo; is assumed.
+</p>
+<p>The string &lsquo;<samp class="samp">random</samp>&rsquo; will result in a random color.
+</p>
+<p>The following names of colors are recognized:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">AliceBlue</samp>&rsquo;</dt>
+<dd><p>0xF0F8FF
+</p></dd>
+<dt>&lsquo;<samp class="samp">AntiqueWhite</samp>&rsquo;</dt>
+<dd><p>0xFAEBD7
+</p></dd>
+<dt>&lsquo;<samp class="samp">Aqua</samp>&rsquo;</dt>
+<dd><p>0x00FFFF
+</p></dd>
+<dt>&lsquo;<samp class="samp">Aquamarine</samp>&rsquo;</dt>
+<dd><p>0x7FFFD4
+</p></dd>
+<dt>&lsquo;<samp class="samp">Azure</samp>&rsquo;</dt>
+<dd><p>0xF0FFFF
+</p></dd>
+<dt>&lsquo;<samp class="samp">Beige</samp>&rsquo;</dt>
+<dd><p>0xF5F5DC
+</p></dd>
+<dt>&lsquo;<samp class="samp">Bisque</samp>&rsquo;</dt>
+<dd><p>0xFFE4C4
+</p></dd>
+<dt>&lsquo;<samp class="samp">Black</samp>&rsquo;</dt>
+<dd><p>0x000000
+</p></dd>
+<dt>&lsquo;<samp class="samp">BlanchedAlmond</samp>&rsquo;</dt>
+<dd><p>0xFFEBCD
+</p></dd>
+<dt>&lsquo;<samp class="samp">Blue</samp>&rsquo;</dt>
+<dd><p>0x0000FF
+</p></dd>
+<dt>&lsquo;<samp class="samp">BlueViolet</samp>&rsquo;</dt>
+<dd><p>0x8A2BE2
+</p></dd>
+<dt>&lsquo;<samp class="samp">Brown</samp>&rsquo;</dt>
+<dd><p>0xA52A2A
+</p></dd>
+<dt>&lsquo;<samp class="samp">BurlyWood</samp>&rsquo;</dt>
+<dd><p>0xDEB887
+</p></dd>
+<dt>&lsquo;<samp class="samp">CadetBlue</samp>&rsquo;</dt>
+<dd><p>0x5F9EA0
+</p></dd>
+<dt>&lsquo;<samp class="samp">Chartreuse</samp>&rsquo;</dt>
+<dd><p>0x7FFF00
+</p></dd>
+<dt>&lsquo;<samp class="samp">Chocolate</samp>&rsquo;</dt>
+<dd><p>0xD2691E
+</p></dd>
+<dt>&lsquo;<samp class="samp">Coral</samp>&rsquo;</dt>
+<dd><p>0xFF7F50
+</p></dd>
+<dt>&lsquo;<samp class="samp">CornflowerBlue</samp>&rsquo;</dt>
+<dd><p>0x6495ED
+</p></dd>
+<dt>&lsquo;<samp class="samp">Cornsilk</samp>&rsquo;</dt>
+<dd><p>0xFFF8DC
+</p></dd>
+<dt>&lsquo;<samp class="samp">Crimson</samp>&rsquo;</dt>
+<dd><p>0xDC143C
+</p></dd>
+<dt>&lsquo;<samp class="samp">Cyan</samp>&rsquo;</dt>
+<dd><p>0x00FFFF
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkBlue</samp>&rsquo;</dt>
+<dd><p>0x00008B
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkCyan</samp>&rsquo;</dt>
+<dd><p>0x008B8B
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkGoldenRod</samp>&rsquo;</dt>
+<dd><p>0xB8860B
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkGray</samp>&rsquo;</dt>
+<dd><p>0xA9A9A9
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkGreen</samp>&rsquo;</dt>
+<dd><p>0x006400
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkKhaki</samp>&rsquo;</dt>
+<dd><p>0xBDB76B
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkMagenta</samp>&rsquo;</dt>
+<dd><p>0x8B008B
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkOliveGreen</samp>&rsquo;</dt>
+<dd><p>0x556B2F
+</p></dd>
+<dt>&lsquo;<samp class="samp">Darkorange</samp>&rsquo;</dt>
+<dd><p>0xFF8C00
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkOrchid</samp>&rsquo;</dt>
+<dd><p>0x9932CC
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkRed</samp>&rsquo;</dt>
+<dd><p>0x8B0000
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkSalmon</samp>&rsquo;</dt>
+<dd><p>0xE9967A
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkSeaGreen</samp>&rsquo;</dt>
+<dd><p>0x8FBC8F
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkSlateBlue</samp>&rsquo;</dt>
+<dd><p>0x483D8B
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkSlateGray</samp>&rsquo;</dt>
+<dd><p>0x2F4F4F
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkTurquoise</samp>&rsquo;</dt>
+<dd><p>0x00CED1
+</p></dd>
+<dt>&lsquo;<samp class="samp">DarkViolet</samp>&rsquo;</dt>
+<dd><p>0x9400D3
+</p></dd>
+<dt>&lsquo;<samp class="samp">DeepPink</samp>&rsquo;</dt>
+<dd><p>0xFF1493
+</p></dd>
+<dt>&lsquo;<samp class="samp">DeepSkyBlue</samp>&rsquo;</dt>
+<dd><p>0x00BFFF
+</p></dd>
+<dt>&lsquo;<samp class="samp">DimGray</samp>&rsquo;</dt>
+<dd><p>0x696969
+</p></dd>
+<dt>&lsquo;<samp class="samp">DodgerBlue</samp>&rsquo;</dt>
+<dd><p>0x1E90FF
+</p></dd>
+<dt>&lsquo;<samp class="samp">FireBrick</samp>&rsquo;</dt>
+<dd><p>0xB22222
+</p></dd>
+<dt>&lsquo;<samp class="samp">FloralWhite</samp>&rsquo;</dt>
+<dd><p>0xFFFAF0
+</p></dd>
+<dt>&lsquo;<samp class="samp">ForestGreen</samp>&rsquo;</dt>
+<dd><p>0x228B22
+</p></dd>
+<dt>&lsquo;<samp class="samp">Fuchsia</samp>&rsquo;</dt>
+<dd><p>0xFF00FF
+</p></dd>
+<dt>&lsquo;<samp class="samp">Gainsboro</samp>&rsquo;</dt>
+<dd><p>0xDCDCDC
+</p></dd>
+<dt>&lsquo;<samp class="samp">GhostWhite</samp>&rsquo;</dt>
+<dd><p>0xF8F8FF
+</p></dd>
+<dt>&lsquo;<samp class="samp">Gold</samp>&rsquo;</dt>
+<dd><p>0xFFD700
+</p></dd>
+<dt>&lsquo;<samp class="samp">GoldenRod</samp>&rsquo;</dt>
+<dd><p>0xDAA520
+</p></dd>
+<dt>&lsquo;<samp class="samp">Gray</samp>&rsquo;</dt>
+<dd><p>0x808080
+</p></dd>
+<dt>&lsquo;<samp class="samp">Green</samp>&rsquo;</dt>
+<dd><p>0x008000
+</p></dd>
+<dt>&lsquo;<samp class="samp">GreenYellow</samp>&rsquo;</dt>
+<dd><p>0xADFF2F
+</p></dd>
+<dt>&lsquo;<samp class="samp">HoneyDew</samp>&rsquo;</dt>
+<dd><p>0xF0FFF0
+</p></dd>
+<dt>&lsquo;<samp class="samp">HotPink</samp>&rsquo;</dt>
+<dd><p>0xFF69B4
+</p></dd>
+<dt>&lsquo;<samp class="samp">IndianRed</samp>&rsquo;</dt>
+<dd><p>0xCD5C5C
+</p></dd>
+<dt>&lsquo;<samp class="samp">Indigo</samp>&rsquo;</dt>
+<dd><p>0x4B0082
+</p></dd>
+<dt>&lsquo;<samp class="samp">Ivory</samp>&rsquo;</dt>
+<dd><p>0xFFFFF0
+</p></dd>
+<dt>&lsquo;<samp class="samp">Khaki</samp>&rsquo;</dt>
+<dd><p>0xF0E68C
+</p></dd>
+<dt>&lsquo;<samp class="samp">Lavender</samp>&rsquo;</dt>
+<dd><p>0xE6E6FA
+</p></dd>
+<dt>&lsquo;<samp class="samp">LavenderBlush</samp>&rsquo;</dt>
+<dd><p>0xFFF0F5
+</p></dd>
+<dt>&lsquo;<samp class="samp">LawnGreen</samp>&rsquo;</dt>
+<dd><p>0x7CFC00
+</p></dd>
+<dt>&lsquo;<samp class="samp">LemonChiffon</samp>&rsquo;</dt>
+<dd><p>0xFFFACD
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightBlue</samp>&rsquo;</dt>
+<dd><p>0xADD8E6
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightCoral</samp>&rsquo;</dt>
+<dd><p>0xF08080
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightCyan</samp>&rsquo;</dt>
+<dd><p>0xE0FFFF
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightGoldenRodYellow</samp>&rsquo;</dt>
+<dd><p>0xFAFAD2
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightGreen</samp>&rsquo;</dt>
+<dd><p>0x90EE90
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightGrey</samp>&rsquo;</dt>
+<dd><p>0xD3D3D3
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightPink</samp>&rsquo;</dt>
+<dd><p>0xFFB6C1
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightSalmon</samp>&rsquo;</dt>
+<dd><p>0xFFA07A
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightSeaGreen</samp>&rsquo;</dt>
+<dd><p>0x20B2AA
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightSkyBlue</samp>&rsquo;</dt>
+<dd><p>0x87CEFA
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightSlateGray</samp>&rsquo;</dt>
+<dd><p>0x778899
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightSteelBlue</samp>&rsquo;</dt>
+<dd><p>0xB0C4DE
+</p></dd>
+<dt>&lsquo;<samp class="samp">LightYellow</samp>&rsquo;</dt>
+<dd><p>0xFFFFE0
+</p></dd>
+<dt>&lsquo;<samp class="samp">Lime</samp>&rsquo;</dt>
+<dd><p>0x00FF00
+</p></dd>
+<dt>&lsquo;<samp class="samp">LimeGreen</samp>&rsquo;</dt>
+<dd><p>0x32CD32
+</p></dd>
+<dt>&lsquo;<samp class="samp">Linen</samp>&rsquo;</dt>
+<dd><p>0xFAF0E6
+</p></dd>
+<dt>&lsquo;<samp class="samp">Magenta</samp>&rsquo;</dt>
+<dd><p>0xFF00FF
+</p></dd>
+<dt>&lsquo;<samp class="samp">Maroon</samp>&rsquo;</dt>
+<dd><p>0x800000
+</p></dd>
+<dt>&lsquo;<samp class="samp">MediumAquaMarine</samp>&rsquo;</dt>
+<dd><p>0x66CDAA
+</p></dd>
+<dt>&lsquo;<samp class="samp">MediumBlue</samp>&rsquo;</dt>
+<dd><p>0x0000CD
+</p></dd>
+<dt>&lsquo;<samp class="samp">MediumOrchid</samp>&rsquo;</dt>
+<dd><p>0xBA55D3
+</p></dd>
+<dt>&lsquo;<samp class="samp">MediumPurple</samp>&rsquo;</dt>
+<dd><p>0x9370D8
+</p></dd>
+<dt>&lsquo;<samp class="samp">MediumSeaGreen</samp>&rsquo;</dt>
+<dd><p>0x3CB371
+</p></dd>
+<dt>&lsquo;<samp class="samp">MediumSlateBlue</samp>&rsquo;</dt>
+<dd><p>0x7B68EE
+</p></dd>
+<dt>&lsquo;<samp class="samp">MediumSpringGreen</samp>&rsquo;</dt>
+<dd><p>0x00FA9A
+</p></dd>
+<dt>&lsquo;<samp class="samp">MediumTurquoise</samp>&rsquo;</dt>
+<dd><p>0x48D1CC
+</p></dd>
+<dt>&lsquo;<samp class="samp">MediumVioletRed</samp>&rsquo;</dt>
+<dd><p>0xC71585
+</p></dd>
+<dt>&lsquo;<samp class="samp">MidnightBlue</samp>&rsquo;</dt>
+<dd><p>0x191970
+</p></dd>
+<dt>&lsquo;<samp class="samp">MintCream</samp>&rsquo;</dt>
+<dd><p>0xF5FFFA
+</p></dd>
+<dt>&lsquo;<samp class="samp">MistyRose</samp>&rsquo;</dt>
+<dd><p>0xFFE4E1
+</p></dd>
+<dt>&lsquo;<samp class="samp">Moccasin</samp>&rsquo;</dt>
+<dd><p>0xFFE4B5
+</p></dd>
+<dt>&lsquo;<samp class="samp">NavajoWhite</samp>&rsquo;</dt>
+<dd><p>0xFFDEAD
+</p></dd>
+<dt>&lsquo;<samp class="samp">Navy</samp>&rsquo;</dt>
+<dd><p>0x000080
+</p></dd>
+<dt>&lsquo;<samp class="samp">OldLace</samp>&rsquo;</dt>
+<dd><p>0xFDF5E6
+</p></dd>
+<dt>&lsquo;<samp class="samp">Olive</samp>&rsquo;</dt>
+<dd><p>0x808000
+</p></dd>
+<dt>&lsquo;<samp class="samp">OliveDrab</samp>&rsquo;</dt>
+<dd><p>0x6B8E23
+</p></dd>
+<dt>&lsquo;<samp class="samp">Orange</samp>&rsquo;</dt>
+<dd><p>0xFFA500
+</p></dd>
+<dt>&lsquo;<samp class="samp">OrangeRed</samp>&rsquo;</dt>
+<dd><p>0xFF4500
+</p></dd>
+<dt>&lsquo;<samp class="samp">Orchid</samp>&rsquo;</dt>
+<dd><p>0xDA70D6
+</p></dd>
+<dt>&lsquo;<samp class="samp">PaleGoldenRod</samp>&rsquo;</dt>
+<dd><p>0xEEE8AA
+</p></dd>
+<dt>&lsquo;<samp class="samp">PaleGreen</samp>&rsquo;</dt>
+<dd><p>0x98FB98
+</p></dd>
+<dt>&lsquo;<samp class="samp">PaleTurquoise</samp>&rsquo;</dt>
+<dd><p>0xAFEEEE
+</p></dd>
+<dt>&lsquo;<samp class="samp">PaleVioletRed</samp>&rsquo;</dt>
+<dd><p>0xD87093
+</p></dd>
+<dt>&lsquo;<samp class="samp">PapayaWhip</samp>&rsquo;</dt>
+<dd><p>0xFFEFD5
+</p></dd>
+<dt>&lsquo;<samp class="samp">PeachPuff</samp>&rsquo;</dt>
+<dd><p>0xFFDAB9
+</p></dd>
+<dt>&lsquo;<samp class="samp">Peru</samp>&rsquo;</dt>
+<dd><p>0xCD853F
+</p></dd>
+<dt>&lsquo;<samp class="samp">Pink</samp>&rsquo;</dt>
+<dd><p>0xFFC0CB
+</p></dd>
+<dt>&lsquo;<samp class="samp">Plum</samp>&rsquo;</dt>
+<dd><p>0xDDA0DD
+</p></dd>
+<dt>&lsquo;<samp class="samp">PowderBlue</samp>&rsquo;</dt>
+<dd><p>0xB0E0E6
+</p></dd>
+<dt>&lsquo;<samp class="samp">Purple</samp>&rsquo;</dt>
+<dd><p>0x800080
+</p></dd>
+<dt>&lsquo;<samp class="samp">Red</samp>&rsquo;</dt>
+<dd><p>0xFF0000
+</p></dd>
+<dt>&lsquo;<samp class="samp">RosyBrown</samp>&rsquo;</dt>
+<dd><p>0xBC8F8F
+</p></dd>
+<dt>&lsquo;<samp class="samp">RoyalBlue</samp>&rsquo;</dt>
+<dd><p>0x4169E1
+</p></dd>
+<dt>&lsquo;<samp class="samp">SaddleBrown</samp>&rsquo;</dt>
+<dd><p>0x8B4513
+</p></dd>
+<dt>&lsquo;<samp class="samp">Salmon</samp>&rsquo;</dt>
+<dd><p>0xFA8072
+</p></dd>
+<dt>&lsquo;<samp class="samp">SandyBrown</samp>&rsquo;</dt>
+<dd><p>0xF4A460
+</p></dd>
+<dt>&lsquo;<samp class="samp">SeaGreen</samp>&rsquo;</dt>
+<dd><p>0x2E8B57
+</p></dd>
+<dt>&lsquo;<samp class="samp">SeaShell</samp>&rsquo;</dt>
+<dd><p>0xFFF5EE
+</p></dd>
+<dt>&lsquo;<samp class="samp">Sienna</samp>&rsquo;</dt>
+<dd><p>0xA0522D
+</p></dd>
+<dt>&lsquo;<samp class="samp">Silver</samp>&rsquo;</dt>
+<dd><p>0xC0C0C0
+</p></dd>
+<dt>&lsquo;<samp class="samp">SkyBlue</samp>&rsquo;</dt>
+<dd><p>0x87CEEB
+</p></dd>
+<dt>&lsquo;<samp class="samp">SlateBlue</samp>&rsquo;</dt>
+<dd><p>0x6A5ACD
+</p></dd>
+<dt>&lsquo;<samp class="samp">SlateGray</samp>&rsquo;</dt>
+<dd><p>0x708090
+</p></dd>
+<dt>&lsquo;<samp class="samp">Snow</samp>&rsquo;</dt>
+<dd><p>0xFFFAFA
+</p></dd>
+<dt>&lsquo;<samp class="samp">SpringGreen</samp>&rsquo;</dt>
+<dd><p>0x00FF7F
+</p></dd>
+<dt>&lsquo;<samp class="samp">SteelBlue</samp>&rsquo;</dt>
+<dd><p>0x4682B4
+</p></dd>
+<dt>&lsquo;<samp class="samp">Tan</samp>&rsquo;</dt>
+<dd><p>0xD2B48C
+</p></dd>
+<dt>&lsquo;<samp class="samp">Teal</samp>&rsquo;</dt>
+<dd><p>0x008080
+</p></dd>
+<dt>&lsquo;<samp class="samp">Thistle</samp>&rsquo;</dt>
+<dd><p>0xD8BFD8
+</p></dd>
+<dt>&lsquo;<samp class="samp">Tomato</samp>&rsquo;</dt>
+<dd><p>0xFF6347
+</p></dd>
+<dt>&lsquo;<samp class="samp">Turquoise</samp>&rsquo;</dt>
+<dd><p>0x40E0D0
+</p></dd>
+<dt>&lsquo;<samp class="samp">Violet</samp>&rsquo;</dt>
+<dd><p>0xEE82EE
+</p></dd>
+<dt>&lsquo;<samp class="samp">Wheat</samp>&rsquo;</dt>
+<dd><p>0xF5DEB3
+</p></dd>
+<dt>&lsquo;<samp class="samp">White</samp>&rsquo;</dt>
+<dd><p>0xFFFFFF
+</p></dd>
+<dt>&lsquo;<samp class="samp">WhiteSmoke</samp>&rsquo;</dt>
+<dd><p>0xF5F5F5
+</p></dd>
+<dt>&lsquo;<samp class="samp">Yellow</samp>&rsquo;</dt>
+<dd><p>0xFFFF00
+</p></dd>
+<dt>&lsquo;<samp class="samp">YellowGreen</samp>&rsquo;</dt>
+<dd><p>0x9ACD32
+</p></dd>
+</dl>
+
+<a class="anchor" id="channel-layout-syntax"></a><a name="Channel-Layout"></a>
+<h3 class="section">2.8 Channel Layout<span class="pull-right"><a class="anchor hidden-xs" href="#Channel-Layout" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Channel-Layout" aria-hidden="true">TOC</a></span></h3>
+
+<p>A channel layout specifies the spatial disposition of the channels in
+a multi-channel audio stream. To specify a channel layout, FFmpeg
+makes use of a special syntax.
+</p>
+<p>Individual channels are identified by an id, as given by the table
+below:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">FL</samp>&rsquo;</dt>
+<dd><p>front left
+</p></dd>
+<dt>&lsquo;<samp class="samp">FR</samp>&rsquo;</dt>
+<dd><p>front right
+</p></dd>
+<dt>&lsquo;<samp class="samp">FC</samp>&rsquo;</dt>
+<dd><p>front center
+</p></dd>
+<dt>&lsquo;<samp class="samp">LFE</samp>&rsquo;</dt>
+<dd><p>low frequency
+</p></dd>
+<dt>&lsquo;<samp class="samp">BL</samp>&rsquo;</dt>
+<dd><p>back left
+</p></dd>
+<dt>&lsquo;<samp class="samp">BR</samp>&rsquo;</dt>
+<dd><p>back right
+</p></dd>
+<dt>&lsquo;<samp class="samp">FLC</samp>&rsquo;</dt>
+<dd><p>front left-of-center
+</p></dd>
+<dt>&lsquo;<samp class="samp">FRC</samp>&rsquo;</dt>
+<dd><p>front right-of-center
+</p></dd>
+<dt>&lsquo;<samp class="samp">BC</samp>&rsquo;</dt>
+<dd><p>back center
+</p></dd>
+<dt>&lsquo;<samp class="samp">SL</samp>&rsquo;</dt>
+<dd><p>side left
+</p></dd>
+<dt>&lsquo;<samp class="samp">SR</samp>&rsquo;</dt>
+<dd><p>side right
+</p></dd>
+<dt>&lsquo;<samp class="samp">TC</samp>&rsquo;</dt>
+<dd><p>top center
+</p></dd>
+<dt>&lsquo;<samp class="samp">TFL</samp>&rsquo;</dt>
+<dd><p>top front left
+</p></dd>
+<dt>&lsquo;<samp class="samp">TFC</samp>&rsquo;</dt>
+<dd><p>top front center
+</p></dd>
+<dt>&lsquo;<samp class="samp">TFR</samp>&rsquo;</dt>
+<dd><p>top front right
+</p></dd>
+<dt>&lsquo;<samp class="samp">TBL</samp>&rsquo;</dt>
+<dd><p>top back left
+</p></dd>
+<dt>&lsquo;<samp class="samp">TBC</samp>&rsquo;</dt>
+<dd><p>top back center
+</p></dd>
+<dt>&lsquo;<samp class="samp">TBR</samp>&rsquo;</dt>
+<dd><p>top back right
+</p></dd>
+<dt>&lsquo;<samp class="samp">DL</samp>&rsquo;</dt>
+<dd><p>downmix left
+</p></dd>
+<dt>&lsquo;<samp class="samp">DR</samp>&rsquo;</dt>
+<dd><p>downmix right
+</p></dd>
+<dt>&lsquo;<samp class="samp">WL</samp>&rsquo;</dt>
+<dd><p>wide left
+</p></dd>
+<dt>&lsquo;<samp class="samp">WR</samp>&rsquo;</dt>
+<dd><p>wide right
+</p></dd>
+<dt>&lsquo;<samp class="samp">SDL</samp>&rsquo;</dt>
+<dd><p>surround direct left
+</p></dd>
+<dt>&lsquo;<samp class="samp">SDR</samp>&rsquo;</dt>
+<dd><p>surround direct right
+</p></dd>
+<dt>&lsquo;<samp class="samp">LFE2</samp>&rsquo;</dt>
+<dd><p>low frequency 2
+</p></dd>
+</dl>
+
+<p>Standard channel layout compositions can be specified by using the
+following identifiers:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">mono</samp>&rsquo;</dt>
+<dd><p>FC
+</p></dd>
+<dt>&lsquo;<samp class="samp">stereo</samp>&rsquo;</dt>
+<dd><p>FL+FR
+</p></dd>
+<dt>&lsquo;<samp class="samp">2.1</samp>&rsquo;</dt>
+<dd><p>FL+FR+LFE
+</p></dd>
+<dt>&lsquo;<samp class="samp">3.0</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC
+</p></dd>
+<dt>&lsquo;<samp class="samp">3.0(back)</samp>&rsquo;</dt>
+<dd><p>FL+FR+BC
+</p></dd>
+<dt>&lsquo;<samp class="samp">4.0</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+BC
+</p></dd>
+<dt>&lsquo;<samp class="samp">quad</samp>&rsquo;</dt>
+<dd><p>FL+FR+BL+BR
+</p></dd>
+<dt>&lsquo;<samp class="samp">quad(side)</samp>&rsquo;</dt>
+<dd><p>FL+FR+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">3.1</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE
+</p></dd>
+<dt>&lsquo;<samp class="samp">5.0</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+BL+BR
+</p></dd>
+<dt>&lsquo;<samp class="samp">5.0(side)</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">4.1</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BC
+</p></dd>
+<dt>&lsquo;<samp class="samp">5.1</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR
+</p></dd>
+<dt>&lsquo;<samp class="samp">5.1(side)</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">6.0</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+BC+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">6.0(front)</samp>&rsquo;</dt>
+<dd><p>FL+FR+FLC+FRC+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">3.1.2</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+TFL+TFR
+</p></dd>
+<dt>&lsquo;<samp class="samp">hexagonal</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+BL+BR+BC
+</p></dd>
+<dt>&lsquo;<samp class="samp">6.1</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BC+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">6.1</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+BC
+</p></dd>
+<dt>&lsquo;<samp class="samp">6.1(front)</samp>&rsquo;</dt>
+<dd><p>FL+FR+LFE+FLC+FRC+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">7.0</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+BL+BR+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">7.0(front)</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+FLC+FRC+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">7.1</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">7.1(wide)</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+FLC+FRC
+</p></dd>
+<dt>&lsquo;<samp class="samp">7.1(wide-side)</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+FLC+FRC+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">5.1.2</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+TFL+TFR
+</p></dd>
+<dt>&lsquo;<samp class="samp">octagonal</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+BL+BR+BC+SL+SR
+</p></dd>
+<dt>&lsquo;<samp class="samp">cube</samp>&rsquo;</dt>
+<dd><p>FL+FR+BL+BR+TFL+TFR+TBL+TBR
+</p></dd>
+<dt>&lsquo;<samp class="samp">5.1.4</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+TFL+TFR+TBL+TBR
+</p></dd>
+<dt>&lsquo;<samp class="samp">7.1.2</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+SL+SR+TFL+TFR
+</p></dd>
+<dt>&lsquo;<samp class="samp">7.1.4</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+SL+SR+TFL+TFR+TBL+TBR
+</p></dd>
+<dt>&lsquo;<samp class="samp">7.2.3</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+SL+SR+TFL+TFR+TBC+LFE2
+</p></dd>
+<dt>&lsquo;<samp class="samp">9.1.4</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+FLC+FRC+SL+SR+TFL+TFR+TBL+TBR
+</p></dd>
+<dt>&lsquo;<samp class="samp">9.1.6</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+FLC+FRC+SL+SR+TFL+TFR+TBL+TBR+TSL+TSR
+</p></dd>
+<dt>&lsquo;<samp class="samp">hexadecagonal</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+BL+BR+BC+SL+SR+WL+WR+TBL+TBR+TBC+TFC+TFL+TFR
+</p></dd>
+<dt>&lsquo;<samp class="samp">binaural</samp>&rsquo;</dt>
+<dd><p>BIL+BIR
+</p></dd>
+<dt>&lsquo;<samp class="samp">downmix</samp>&rsquo;</dt>
+<dd><p>DL+DR
+</p></dd>
+<dt>&lsquo;<samp class="samp">22.2</samp>&rsquo;</dt>
+<dd><p>FL+FR+FC+LFE+BL+BR+FLC+FRC+BC+SL+SR+TC+TFL+TFC+TFR+TBL+TBC+TBR+LFE2+TSL+TSR+BFC+BFL+BFR
+</p></dd>
+</dl>
+
+<p>A custom channel layout can be specified as a sequence of terms, separated by &rsquo;+&rsquo;.
+Each term can be:
+</p><ul class="itemize mark-bullet">
+<li>the name of a single channel (e.g. &lsquo;<samp class="samp">FL</samp>&rsquo;, &lsquo;<samp class="samp">FR</samp>&rsquo;, &lsquo;<samp class="samp">FC</samp>&rsquo;, &lsquo;<samp class="samp">LFE</samp>&rsquo;, etc.),
+each optionally containing a custom name after a &rsquo;@&rsquo;, (e.g. &lsquo;<samp class="samp">FL@Left</samp>&rsquo;,
+&lsquo;<samp class="samp">FR@Right</samp>&rsquo;, &lsquo;<samp class="samp">FC@Center</samp>&rsquo;, &lsquo;<samp class="samp">LFE@Low_Frequency</samp>&rsquo;, etc.)
+</li></ul>
+
+<p>A standard channel layout can be specified by the following:
+</p><ul class="itemize mark-bullet">
+<li>the name of a single channel (e.g. &lsquo;<samp class="samp">FL</samp>&rsquo;, &lsquo;<samp class="samp">FR</samp>&rsquo;, &lsquo;<samp class="samp">FC</samp>&rsquo;, &lsquo;<samp class="samp">LFE</samp>&rsquo;, etc.)
+
+</li><li>the name of a standard channel layout (e.g. &lsquo;<samp class="samp">mono</samp>&rsquo;,
+&lsquo;<samp class="samp">stereo</samp>&rsquo;, &lsquo;<samp class="samp">4.0</samp>&rsquo;, &lsquo;<samp class="samp">quad</samp>&rsquo;, &lsquo;<samp class="samp">5.0</samp>&rsquo;, etc.)
+
+</li><li>a number of channels, in decimal, followed by &rsquo;c&rsquo;, yielding the default channel
+layout for that number of channels (see the function
+<code class="code">av_channel_layout_default</code>). Note that not all channel counts have a
+default layout.
+
+</li><li>a number of channels, in decimal, followed by &rsquo;C&rsquo;, yielding an unknown channel
+layout with the specified number of channels. Note that not all channel layout
+specification strings support unknown channel layouts.
+
+</li><li>a channel layout mask, in hexadecimal starting with &quot;0x&quot; (see the
+<code class="code">AV_CH_*</code> macros in <samp class="file">libavutil/channel_layout.h</samp>.
+</li></ul>
+
+<p>Before libavutil version 53 the trailing character &quot;c&quot; to specify a number of
+channels was optional, but now it is required, while a channel layout mask can
+also be specified as a decimal number (if and only if not followed by &quot;c&quot; or &quot;C&quot;).
+</p>
+<p>See also the function <code class="code">av_channel_layout_from_string</code> defined in
+<samp class="file">libavutil/channel_layout.h</samp>.
+</p>
+<a name="Expression-Evaluation"></a>
+<h2 class="chapter">3 Expression Evaluation<span class="pull-right"><a class="anchor hidden-xs" href="#Expression-Evaluation" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Expression-Evaluation" aria-hidden="true">TOC</a></span></h2>
+
+<p>When evaluating an arithmetic expression, FFmpeg uses an internal
+formula evaluator, implemented through the <samp class="file">libavutil/eval.h</samp>
+interface.
+</p>
+<p>An expression may contain unary, binary operators, constants, and
+functions.
+</p>
+<p>Two expressions <var class="var">expr1</var> and <var class="var">expr2</var> can be combined to form
+another expression &quot;<var class="var">expr1</var>;<var class="var">expr2</var>&quot;.
+<var class="var">expr1</var> and <var class="var">expr2</var> are evaluated in turn, and the new
+expression evaluates to the value of <var class="var">expr2</var>.
+</p>
+<p>The following binary operators are available: <code class="code">+</code>, <code class="code">-</code>,
+<code class="code">*</code>, <code class="code">/</code>, <code class="code">^</code>.
+</p>
+<p>The following unary operators are available: <code class="code">+</code>, <code class="code">-</code>.
+</p>
+<p>Some internal variables can be used to store and load intermediary
+results. They can be accessed using the <code class="code">ld</code> and <code class="code">st</code>
+functions with an index argument varying from 0 to 9 to specify which
+internal variable to access.
+</p>
+<p>The following functions are available:
+</p><dl class="table">
+<dt><samp class="option">abs(x)</samp></dt>
+<dd><p>Compute absolute value of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">acos(x)</samp></dt>
+<dd><p>Compute arccosine of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">asin(x)</samp></dt>
+<dd><p>Compute arcsine of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">atan(x)</samp></dt>
+<dd><p>Compute arctangent of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">atan2(y, x)</samp></dt>
+<dd><p>Compute principal value of the arc tangent of <var class="var">y</var>/<var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">between(x, min, max)</samp></dt>
+<dd><p>Return 1 if <var class="var">x</var> is greater than or equal to <var class="var">min</var> and lesser than or
+equal to <var class="var">max</var>, 0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">bitand(x, y)</samp></dt>
+<dt><samp class="option">bitor(x, y)</samp></dt>
+<dd><p>Compute bitwise and/or operation on <var class="var">x</var> and <var class="var">y</var>.
+</p>
+<p>The results of the evaluation of <var class="var">x</var> and <var class="var">y</var> are converted to
+integers before executing the bitwise operation.
+</p>
+<p>Note that both the conversion to integer and the conversion back to
+floating point can lose precision. Beware of unexpected results for
+large numbers (usually 2^53 and larger).
+</p>
+</dd>
+<dt><samp class="option">ceil(expr)</samp></dt>
+<dd><p>Round the value of expression <var class="var">expr</var> upwards to the nearest
+integer. For example, &quot;ceil(1.5)&quot; is &quot;2.0&quot;.
+</p>
+</dd>
+<dt><samp class="option">clip(x, min, max)</samp></dt>
+<dd><p>Return the value of <var class="var">x</var> clipped between <var class="var">min</var> and <var class="var">max</var>.
+</p>
+</dd>
+<dt><samp class="option">cos(x)</samp></dt>
+<dd><p>Compute cosine of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">cosh(x)</samp></dt>
+<dd><p>Compute hyperbolic cosine of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">eq(x, y)</samp></dt>
+<dd><p>Return 1 if <var class="var">x</var> and <var class="var">y</var> are equivalent, 0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">exp(x)</samp></dt>
+<dd><p>Compute exponential of <var class="var">x</var> (with base <code class="code">e</code>, the Euler&rsquo;s number).
+</p>
+</dd>
+<dt><samp class="option">floor(expr)</samp></dt>
+<dd><p>Round the value of expression <var class="var">expr</var> downwards to the nearest
+integer. For example, &quot;floor(-1.5)&quot; is &quot;-2.0&quot;.
+</p>
+</dd>
+<dt><samp class="option">gauss(x)</samp></dt>
+<dd><p>Compute Gauss function of <var class="var">x</var>, corresponding to
+<code class="code">exp(-x*x/2) / sqrt(2*PI)</code>.
+</p>
+</dd>
+<dt><samp class="option">gcd(x, y)</samp></dt>
+<dd><p>Return the greatest common divisor of <var class="var">x</var> and <var class="var">y</var>. If both <var class="var">x</var> and
+<var class="var">y</var> are 0 or either or both are less than zero then behavior is undefined.
+</p>
+</dd>
+<dt><samp class="option">gt(x, y)</samp></dt>
+<dd><p>Return 1 if <var class="var">x</var> is greater than <var class="var">y</var>, 0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">gte(x, y)</samp></dt>
+<dd><p>Return 1 if <var class="var">x</var> is greater than or equal to <var class="var">y</var>, 0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">hypot(x, y)</samp></dt>
+<dd><p>This function is similar to the C function with the same name; it returns
+&quot;sqrt(<var class="var">x</var>*<var class="var">x</var> + <var class="var">y</var>*<var class="var">y</var>)&quot;, the length of the hypotenuse of a
+right triangle with sides of length <var class="var">x</var> and <var class="var">y</var>, or the distance of the
+point (<var class="var">x</var>, <var class="var">y</var>) from the origin.
+</p>
+</dd>
+<dt><samp class="option">if(x, y)</samp></dt>
+<dd><p>Evaluate <var class="var">x</var>, and if the result is non-zero return the result of
+the evaluation of <var class="var">y</var>, return 0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">if(x, y, z)</samp></dt>
+<dd><p>Evaluate <var class="var">x</var>, and if the result is non-zero return the evaluation
+result of <var class="var">y</var>, otherwise the evaluation result of <var class="var">z</var>.
+</p>
+</dd>
+<dt><samp class="option">ifnot(x, y)</samp></dt>
+<dd><p>Evaluate <var class="var">x</var>, and if the result is zero return the result of the
+evaluation of <var class="var">y</var>, return 0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">ifnot(x, y, z)</samp></dt>
+<dd><p>Evaluate <var class="var">x</var>, and if the result is zero return the evaluation
+result of <var class="var">y</var>, otherwise the evaluation result of <var class="var">z</var>.
+</p>
+</dd>
+<dt><samp class="option">isinf(x)</samp></dt>
+<dd><p>Return 1.0 if <var class="var">x</var> is +/-INFINITY, 0.0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">isnan(x)</samp></dt>
+<dd><p>Return 1.0 if <var class="var">x</var> is NAN, 0.0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">ld(idx)</samp></dt>
+<dd><p>Load the value of the internal variable with index <var class="var">idx</var>, which was
+previously stored with st(<var class="var">idx</var>, <var class="var">expr</var>).
+The function returns the loaded value.
+</p>
+</dd>
+<dt><samp class="option">lerp(x, y, z)</samp></dt>
+<dd><p>Return linear interpolation between <var class="var">x</var> and <var class="var">y</var> by amount of <var class="var">z</var>.
+</p>
+</dd>
+<dt><samp class="option">log(x)</samp></dt>
+<dd><p>Compute natural logarithm of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">lt(x, y)</samp></dt>
+<dd><p>Return 1 if <var class="var">x</var> is lesser than <var class="var">y</var>, 0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">lte(x, y)</samp></dt>
+<dd><p>Return 1 if <var class="var">x</var> is lesser than or equal to <var class="var">y</var>, 0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">max(x, y)</samp></dt>
+<dd><p>Return the maximum between <var class="var">x</var> and <var class="var">y</var>.
+</p>
+</dd>
+<dt><samp class="option">min(x, y)</samp></dt>
+<dd><p>Return the minimum between <var class="var">x</var> and <var class="var">y</var>.
+</p>
+</dd>
+<dt><samp class="option">mod(x, y)</samp></dt>
+<dd><p>Compute the remainder of division of <var class="var">x</var> by <var class="var">y</var>.
+</p>
+</dd>
+<dt><samp class="option">not(expr)</samp></dt>
+<dd><p>Return 1.0 if <var class="var">expr</var> is zero, 0.0 otherwise.
+</p>
+</dd>
+<dt><samp class="option">pow(x, y)</samp></dt>
+<dd><p>Compute the power of <var class="var">x</var> elevated <var class="var">y</var>, it is equivalent to
+&quot;(<var class="var">x</var>)^(<var class="var">y</var>)&quot;.
+</p>
+</dd>
+<dt><samp class="option">print(t)</samp></dt>
+<dt><samp class="option">print(t, l)</samp></dt>
+<dd><p>Print the value of expression <var class="var">t</var> with loglevel <var class="var">l</var>. If <var class="var">l</var> is not
+specified then a default log level is used.
+Return the value of the expression printed.
+</p>
+</dd>
+<dt><samp class="option">random(idx)</samp></dt>
+<dd><p>Return a pseudo random value between 0.0 and 1.0. <var class="var">idx</var> is the
+index of the internal variable used to save the seed/state, which can be
+previously stored with <code class="code">st(idx)</code>.
+</p>
+<p>To initialize the seed, you need to store the seed value as a 64-bit
+unsigned integer in the internal variable with index <var class="var">idx</var>.
+</p>
+<p>For example, to store the seed with value <code class="code">42</code> in the internal
+variable with index <code class="code">0</code> and print a few random values:
+</p><div class="example">
+<pre class="example-preformatted">st(0,42); print(random(0)); print(random(0)); print(random(0))
+</pre></div>
+
+</dd>
+<dt><samp class="option">randomi(idx, min, max)</samp></dt>
+<dd><p>Return a pseudo random value in the interval between <var class="var">min</var> and
+<var class="var">max</var>. <var class="var">idx</var> is the index of the internal variable which will be used to
+save the seed/state, which can be previously stored with <code class="code">st(idx)</code>.
+</p>
+<p>To initialize the seed, you need to store the seed value as a 64-bit
+unsigned integer in the internal variable with index <var class="var">idx</var>.
+</p>
+</dd>
+<dt><samp class="option">root(expr, max)</samp></dt>
+<dd><p>Find an input value for which the function represented by <var class="var">expr</var>
+with argument <var class="var">ld(0)</var> is 0 in the interval 0..<var class="var">max</var>.
+</p>
+<p>The expression in <var class="var">expr</var> must denote a continuous function or the
+result is undefined.
+</p>
+<p><var class="var">ld(0)</var> is used to represent the function input value, which means that the
+given expression will be evaluated multiple times with various input values that
+the expression can access through <code class="code">ld(0)</code>. When the expression evaluates to
+0 then the corresponding input value will be returned.
+</p>
+</dd>
+<dt><samp class="option">round(expr)</samp></dt>
+<dd><p>Round the value of expression <var class="var">expr</var> to the nearest integer. For example,
+&quot;round(1.5)&quot; is &quot;2.0&quot;.
+</p>
+</dd>
+<dt><samp class="option">sgn(x)</samp></dt>
+<dd><p>Compute sign of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">sin(x)</samp></dt>
+<dd><p>Compute sine of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">sinh(x)</samp></dt>
+<dd><p>Compute hyperbolic sine of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">sqrt(expr)</samp></dt>
+<dd><p>Compute the square root of <var class="var">expr</var>. This is equivalent to
+&quot;(<var class="var">expr</var>)^.5&quot;.
+</p>
+</dd>
+<dt><samp class="option">squish(x)</samp></dt>
+<dd><p>Compute expression <code class="code">1/(1 + exp(4*x))</code>.
+</p>
+</dd>
+<dt><samp class="option">st(idx, expr)</samp></dt>
+<dd><p>Store the value of the expression <var class="var">expr</var> in an internal
+variable. <var class="var">idx</var> specifies the index of the variable where to store
+the value, and it is a value ranging from 0 to 9. The function returns
+the value stored in the internal variable.
+</p>
+<p>The stored value can be retrieved with <code class="code">ld(var)</code>.
+</p>
+<p>Note: variables are currently not shared between expressions.
+</p>
+</dd>
+<dt><samp class="option">tan(x)</samp></dt>
+<dd><p>Compute tangent of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">tanh(x)</samp></dt>
+<dd><p>Compute hyperbolic tangent of <var class="var">x</var>.
+</p>
+</dd>
+<dt><samp class="option">taylor(expr, x)</samp></dt>
+<dt><samp class="option">taylor(expr, x, idx)</samp></dt>
+<dd><p>Evaluate a Taylor series at <var class="var">x</var>, given an expression representing
+the <code class="code">ld(idx)</code>-th derivative of a function at 0.
+</p>
+<p>When the series does not converge the result is undefined.
+</p>
+<p><var class="var">ld(idx)</var> is used to represent the derivative order in <var class="var">expr</var>,
+which means that the given expression will be evaluated multiple times
+with various input values that the expression can access through
+<code class="code">ld(idx)</code>. If <var class="var">idx</var> is not specified then 0 is assumed.
+</p>
+<p>Note, when you have the derivatives at y instead of 0,
+<code class="code">taylor(expr, x-y)</code> can be used.
+</p>
+</dd>
+<dt><samp class="option">time(0)</samp></dt>
+<dd><p>Return the current (wallclock) time in seconds.
+</p>
+</dd>
+<dt><samp class="option">trunc(expr)</samp></dt>
+<dd><p>Round the value of expression <var class="var">expr</var> towards zero to the nearest
+integer. For example, &quot;trunc(-1.5)&quot; is &quot;-1.0&quot;.
+</p>
+</dd>
+<dt><samp class="option">while(cond, expr)</samp></dt>
+<dd><p>Evaluate expression <var class="var">expr</var> while the expression <var class="var">cond</var> is
+non-zero, and returns the value of the last <var class="var">expr</var> evaluation, or
+NAN if <var class="var">cond</var> was always false.
+</p></dd>
+</dl>
+
+<p>The following constants are available:
+</p><dl class="table">
+<dt><samp class="option">PI</samp></dt>
+<dd><p>area of the unit disc, approximately 3.14
+</p></dd>
+<dt><samp class="option">E</samp></dt>
+<dd><p>exp(1) (Euler&rsquo;s number), approximately 2.718
+</p></dd>
+<dt><samp class="option">PHI</samp></dt>
+<dd><p>golden ratio (1+sqrt(5))/2, approximately 1.618
+</p></dd>
+</dl>
+
+<p>Assuming that an expression is considered &quot;true&quot; if it has a non-zero
+value, note that:
+</p>
+<p><code class="code">*</code> works like AND
+</p>
+<p><code class="code">+</code> works like OR
+</p>
+<p>For example the construct:
+</p><div class="example">
+<pre class="example-preformatted">if (A AND B) then C
+</pre></div>
+<p>is equivalent to:
+</p><div class="example">
+<pre class="example-preformatted">if(A*B, C)
+</pre></div>
+
+<p>In your C code, you can extend the list of unary and binary functions,
+and define recognized constants, so that they are available for your
+expressions.
+</p>
+<p>The evaluator also recognizes the International System unit prefixes.
+If &rsquo;i&rsquo; is appended after the prefix, binary prefixes are used, which
+are based on powers of 1024 instead of powers of 1000.
+The &rsquo;B&rsquo; postfix multiplies the value by 8, and can be appended after a
+unit prefix or used alone. This allows using for example &rsquo;KB&rsquo;, &rsquo;MiB&rsquo;,
+&rsquo;G&rsquo; and &rsquo;B&rsquo; as number postfix.
+</p>
+<p>The list of available International System prefixes follows, with
+indication of the corresponding powers of 10 and of 2.
+</p><dl class="table">
+<dt><samp class="option">y</samp></dt>
+<dd><p>10^-24 / 2^-80
+</p></dd>
+<dt><samp class="option">z</samp></dt>
+<dd><p>10^-21 / 2^-70
+</p></dd>
+<dt><samp class="option">a</samp></dt>
+<dd><p>10^-18 / 2^-60
+</p></dd>
+<dt><samp class="option">f</samp></dt>
+<dd><p>10^-15 / 2^-50
+</p></dd>
+<dt><samp class="option">p</samp></dt>
+<dd><p>10^-12 / 2^-40
+</p></dd>
+<dt><samp class="option">n</samp></dt>
+<dd><p>10^-9 / 2^-30
+</p></dd>
+<dt><samp class="option">u</samp></dt>
+<dd><p>10^-6 / 2^-20
+</p></dd>
+<dt><samp class="option">m</samp></dt>
+<dd><p>10^-3 / 2^-10
+</p></dd>
+<dt><samp class="option">c</samp></dt>
+<dd><p>10^-2
+</p></dd>
+<dt><samp class="option">d</samp></dt>
+<dd><p>10^-1
+</p></dd>
+<dt><samp class="option">h</samp></dt>
+<dd><p>10^2
+</p></dd>
+<dt><samp class="option">k</samp></dt>
+<dd><p>10^3 / 2^10
+</p></dd>
+<dt><samp class="option">K</samp></dt>
+<dd><p>10^3 / 2^10
+</p></dd>
+<dt><samp class="option">M</samp></dt>
+<dd><p>10^6 / 2^20
+</p></dd>
+<dt><samp class="option">G</samp></dt>
+<dd><p>10^9 / 2^30
+</p></dd>
+<dt><samp class="option">T</samp></dt>
+<dd><p>10^12 / 2^40
+</p></dd>
+<dt><samp class="option">P</samp></dt>
+<dd><p>10^15 / 2^50
+</p></dd>
+<dt><samp class="option">E</samp></dt>
+<dd><p>10^18 / 2^60
+</p></dd>
+<dt><samp class="option">Z</samp></dt>
+<dd><p>10^21 / 2^70
+</p></dd>
+<dt><samp class="option">Y</samp></dt>
+<dd><p>10^24 / 2^80
+</p></dd>
+</dl>
+
+
+<a name="See-Also"></a>
+<h2 class="chapter">4 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="libavutil.html">libavutil</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">5 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/ffplay.html

@@ -0,0 +1,914 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      ffplay Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      ffplay Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Synopsis" href="#Synopsis">1 Synopsis</a></li>
+  <li><a id="toc-Description" href="#Description">2 Description</a></li>
+  <li><a id="toc-Options" href="#Options">3 Options</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Stream-specifiers-1" href="#Stream-specifiers-1">3.1 Stream specifiers</a></li>
+    <li><a id="toc-Generic-options" href="#Generic-options">3.2 Generic options</a></li>
+    <li><a id="toc-AVOptions" href="#AVOptions">3.3 AVOptions</a></li>
+    <li><a id="toc-Main-options" href="#Main-options">3.4 Main options</a></li>
+    <li><a id="toc-Advanced-options" href="#Advanced-options">3.5 Advanced options</a></li>
+    <li><a id="toc-While-playing" href="#While-playing">3.6 While playing</a></li>
+  </ul></li>
+  <li><a id="toc-See-Also" href="#See-Also">4 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">5 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Synopsis"></a>
+<h2 class="chapter">1 Synopsis<span class="pull-right"><a class="anchor hidden-xs" href="#Synopsis" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Synopsis" aria-hidden="true">TOC</a></span></h2>
+
+<p>ffplay [<var class="var">options</var>] [<samp class="file">input_url</samp>]
+</p>
+<a name="Description"></a>
+<h2 class="chapter">2 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>FFplay is a very simple and portable media player using the FFmpeg
+libraries and the SDL library. It is mostly used as a testbed for the
+various FFmpeg APIs.
+</p>
+<a name="Options"></a>
+<h2 class="chapter">3 Options<span class="pull-right"><a class="anchor hidden-xs" href="#Options" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Options" aria-hidden="true">TOC</a></span></h2>
+
+<p>All the numerical options, if not specified otherwise, accept a string
+representing a number as input, which may be followed by one of the SI
+unit prefixes, for example: &rsquo;K&rsquo;, &rsquo;M&rsquo;, or &rsquo;G&rsquo;.
+</p>
+<p>If &rsquo;i&rsquo; is appended to the SI unit prefix, the complete prefix will be
+interpreted as a unit prefix for binary multiples, which are based on
+powers of 1024 instead of powers of 1000. Appending &rsquo;B&rsquo; to the SI unit
+prefix multiplies the value by 8. This allows using, for example:
+&rsquo;KB&rsquo;, &rsquo;MiB&rsquo;, &rsquo;G&rsquo; and &rsquo;B&rsquo; as number suffixes.
+</p>
+<p>Options which do not take arguments are boolean options, and set the
+corresponding value to true. They can be set to false by prefixing
+the option name with &quot;no&quot;. For example using &quot;-nofoo&quot;
+will set the boolean option with name &quot;foo&quot; to false.
+</p>
+<p>Options that take arguments support a special syntax where the argument given on
+the command line is interpreted as a path to the file from which the actual
+argument value is loaded. To use this feature, add a forward slash &rsquo;/&rsquo;
+immediately before the option name (after the leading dash). E.g.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -/filter:v filter.script OUTPUT
+</pre></div>
+<p>will load a filtergraph description from the file named <samp class="file">filter.script</samp>.
+</p>
+<a class="anchor" id="Stream-specifiers"></a><a name="Stream-specifiers-1"></a>
+<h3 class="section">3.1 Stream specifiers<span class="pull-right"><a class="anchor hidden-xs" href="#Stream-specifiers-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Stream-specifiers-1" aria-hidden="true">TOC</a></span></h3>
+<p>Some options are applied per-stream, e.g. bitrate or codec. Stream specifiers
+are used to precisely specify which stream(s) a given option belongs to.
+</p>
+<p>A stream specifier is a string generally appended to the option name and
+separated from it by a colon. E.g. <code class="code">-codec:a:1 ac3</code> contains the
+<code class="code">a:1</code> stream specifier, which matches the second audio stream. Therefore, it
+would select the ac3 codec for the second audio stream.
+</p>
+<p>A stream specifier can match several streams, so that the option is applied to all
+of them. E.g. the stream specifier in <code class="code">-b:a 128k</code> matches all audio
+streams.
+</p>
+<p>An empty stream specifier matches all streams. For example, <code class="code">-codec copy</code>
+or <code class="code">-codec: copy</code> would copy all the streams without reencoding.
+</p>
+<p>Possible forms of stream specifiers are:
+</p><dl class="table">
+<dt><samp class="option"><var class="var">stream_index</var></samp></dt>
+<dd><p>Matches the stream with this index. E.g. <code class="code">-threads:1 4</code> would set the
+thread count for the second stream to 4. If <var class="var">stream_index</var> is used as an
+additional stream specifier (see below), then it selects stream number
+<var class="var">stream_index</var> from the matching streams. Stream numbering is based on the
+order of the streams as detected by libavformat except when a stream group
+specifier or program ID is also specified. In this case it is based on the
+ordering of the streams in the group or program.
+</p></dd>
+<dt><samp class="option"><var class="var">stream_type</var>[:<var class="var">additional_stream_specifier</var>]</samp></dt>
+<dd><p><var class="var">stream_type</var> is one of following: &rsquo;v&rsquo; or &rsquo;V&rsquo; for video, &rsquo;a&rsquo; for audio, &rsquo;s&rsquo;
+for subtitle, &rsquo;d&rsquo; for data, and &rsquo;t&rsquo; for attachments. &rsquo;v&rsquo; matches all video
+streams, &rsquo;V&rsquo; only matches video streams which are not attached pictures, video
+thumbnails or cover arts. If <var class="var">additional_stream_specifier</var> is used, then
+it matches streams which both have this type and match the
+<var class="var">additional_stream_specifier</var>. Otherwise, it matches all streams of the
+specified type.
+</p></dd>
+<dt><samp class="option">g:<var class="var">group_specifier</var>[:<var class="var">additional_stream_specifier</var>]</samp></dt>
+<dd><p>Matches streams which are in the group with the specifier <var class="var">group_specifier</var>.
+if <var class="var">additional_stream_specifier</var> is used, then it matches streams which both
+are part of the group and match the <var class="var">additional_stream_specifier</var>.
+<var class="var">group_specifier</var> may be one of the following:
+</p><dl class="table">
+<dt><samp class="option"><var class="var">group_index</var></samp></dt>
+<dd><p>Match the stream with this group index.
+</p></dd>
+<dt><samp class="option">#<var class="var">group_id</var> or i:<var class="var">group_id</var></samp></dt>
+<dd><p>Match the stream with this group id.
+</p></dd>
+</dl>
+</dd>
+<dt><samp class="option">p:<var class="var">program_id</var>[:<var class="var">additional_stream_specifier</var>]</samp></dt>
+<dd><p>Matches streams which are in the program with the id <var class="var">program_id</var>. If
+<var class="var">additional_stream_specifier</var> is used, then it matches streams which both
+are part of the program and match the <var class="var">additional_stream_specifier</var>.
+</p>
+</dd>
+<dt><samp class="option">#<var class="var">stream_id</var> or i:<var class="var">stream_id</var></samp></dt>
+<dd><p>Match the stream by stream id (e.g. PID in MPEG-TS container).
+</p></dd>
+<dt><samp class="option">m:<var class="var">key</var>[:<var class="var">value</var>]</samp></dt>
+<dd><p>Matches streams with the metadata tag <var class="var">key</var> having the specified value. If
+<var class="var">value</var> is not given, matches streams that contain the given tag with any
+value. The colon character &rsquo;:&rsquo; in <var class="var">key</var> or <var class="var">value</var> needs to be
+backslash-escaped.
+</p></dd>
+<dt><samp class="option">disp:<var class="var">dispositions</var>[:<var class="var">additional_stream_specifier</var>]</samp></dt>
+<dd><p>Matches streams with the given disposition(s). <var class="var">dispositions</var> is a list of
+one or more dispositions (as printed by the <samp class="option">-dispositions</samp> option)
+joined with &rsquo;+&rsquo;.
+</p></dd>
+<dt><samp class="option">u</samp></dt>
+<dd><p>Matches streams with usable configuration, the codec must be defined and the
+essential information such as video dimension or audio sample rate must be present.
+</p>
+<p>Note that in <code class="command">ffmpeg</code>, matching by metadata will only work properly for
+input files.
+</p></dd>
+</dl>
+
+<a name="Generic-options"></a>
+<h3 class="section">3.2 Generic options<span class="pull-right"><a class="anchor hidden-xs" href="#Generic-options" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Generic-options" aria-hidden="true">TOC</a></span></h3>
+
+<p>These options are shared amongst the ff* tools.
+</p>
+<dl class="table">
+<dt><samp class="option">-L</samp></dt>
+<dd><p>Show license.
+</p>
+</dd>
+<dt><samp class="option">-h, -?, -help, --help [<var class="var">arg</var>]</samp></dt>
+<dd><p>Show help. An optional parameter may be specified to print help about a specific
+item. If no argument is specified, only basic (non advanced) tool
+options are shown.
+</p>
+<p>Possible values of <var class="var">arg</var> are:
+</p><dl class="table">
+<dt><samp class="option">long</samp></dt>
+<dd><p>Print advanced tool options in addition to the basic tool options.
+</p>
+</dd>
+<dt><samp class="option">full</samp></dt>
+<dd><p>Print complete list of options, including shared and private options
+for encoders, decoders, demuxers, muxers, filters, etc.
+</p>
+</dd>
+<dt><samp class="option">decoder=<var class="var">decoder_name</var></samp></dt>
+<dd><p>Print detailed information about the decoder named <var class="var">decoder_name</var>. Use the
+<samp class="option">-decoders</samp> option to get a list of all decoders.
+</p>
+</dd>
+<dt><samp class="option">encoder=<var class="var">encoder_name</var></samp></dt>
+<dd><p>Print detailed information about the encoder named <var class="var">encoder_name</var>. Use the
+<samp class="option">-encoders</samp> option to get a list of all encoders.
+</p>
+</dd>
+<dt><samp class="option">demuxer=<var class="var">demuxer_name</var></samp></dt>
+<dd><p>Print detailed information about the demuxer named <var class="var">demuxer_name</var>. Use the
+<samp class="option">-formats</samp> option to get a list of all demuxers and muxers.
+</p>
+</dd>
+<dt><samp class="option">muxer=<var class="var">muxer_name</var></samp></dt>
+<dd><p>Print detailed information about the muxer named <var class="var">muxer_name</var>. Use the
+<samp class="option">-formats</samp> option to get a list of all muxers and demuxers.
+</p>
+</dd>
+<dt><samp class="option">filter=<var class="var">filter_name</var></samp></dt>
+<dd><p>Print detailed information about the filter named <var class="var">filter_name</var>. Use the
+<samp class="option">-filters</samp> option to get a list of all filters.
+</p>
+</dd>
+<dt><samp class="option">bsf=<var class="var">bitstream_filter_name</var></samp></dt>
+<dd><p>Print detailed information about the bitstream filter named <var class="var">bitstream_filter_name</var>.
+Use the <samp class="option">-bsfs</samp> option to get a list of all bitstream filters.
+</p>
+</dd>
+<dt><samp class="option">protocol=<var class="var">protocol_name</var></samp></dt>
+<dd><p>Print detailed information about the protocol named <var class="var">protocol_name</var>.
+Use the <samp class="option">-protocols</samp> option to get a list of all protocols.
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">-version</samp></dt>
+<dd><p>Show version.
+</p>
+</dd>
+<dt><samp class="option">-buildconf</samp></dt>
+<dd><p>Show the build configuration, one option per line.
+</p>
+</dd>
+<dt><samp class="option">-formats</samp></dt>
+<dd><p>Show available formats (including devices).
+</p>
+</dd>
+<dt><samp class="option">-demuxers</samp></dt>
+<dd><p>Show available demuxers.
+</p>
+</dd>
+<dt><samp class="option">-muxers</samp></dt>
+<dd><p>Show available muxers.
+</p>
+</dd>
+<dt><samp class="option">-devices</samp></dt>
+<dd><p>Show available devices.
+</p>
+</dd>
+<dt><samp class="option">-codecs</samp></dt>
+<dd><p>Show all codecs known to libavcodec.
+</p>
+<p>Note that the term &rsquo;codec&rsquo; is used throughout this documentation as a shortcut
+for what is more correctly called a media bitstream format.
+</p>
+</dd>
+<dt><samp class="option">-decoders</samp></dt>
+<dd><p>Show available decoders.
+</p>
+</dd>
+<dt><samp class="option">-encoders</samp></dt>
+<dd><p>Show all available encoders.
+</p>
+</dd>
+<dt><samp class="option">-bsfs</samp></dt>
+<dd><p>Show available bitstream filters.
+</p>
+</dd>
+<dt><samp class="option">-protocols</samp></dt>
+<dd><p>Show available protocols.
+</p>
+</dd>
+<dt><samp class="option">-filters</samp></dt>
+<dd><p>Show available libavfilter filters.
+</p>
+</dd>
+<dt><samp class="option">-pix_fmts</samp></dt>
+<dd><p>Show available pixel formats.
+</p>
+</dd>
+<dt><samp class="option">-sample_fmts</samp></dt>
+<dd><p>Show available sample formats.
+</p>
+</dd>
+<dt><samp class="option">-layouts</samp></dt>
+<dd><p>Show channel names and standard channel layouts.
+</p>
+</dd>
+<dt><samp class="option">-dispositions</samp></dt>
+<dd><p>Show stream dispositions.
+</p>
+</dd>
+<dt><samp class="option">-colors</samp></dt>
+<dd><p>Show recognized color names.
+</p>
+</dd>
+<dt><samp class="option">-sources <var class="var">device</var>[,<var class="var">opt1</var>=<var class="var">val1</var>[,<var class="var">opt2</var>=<var class="var">val2</var>]...]</samp></dt>
+<dd><p>Show autodetected sources of the input device.
+Some devices may provide system-dependent source names that cannot be autodetected.
+The returned list cannot be assumed to be always complete.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -sources pulse,server=192.168.0.4
+</pre></div>
+
+</dd>
+<dt><samp class="option">-sinks <var class="var">device</var>[,<var class="var">opt1</var>=<var class="var">val1</var>[,<var class="var">opt2</var>=<var class="var">val2</var>]...]</samp></dt>
+<dd><p>Show autodetected sinks of the output device.
+Some devices may provide system-dependent sink names that cannot be autodetected.
+The returned list cannot be assumed to be always complete.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -sinks pulse,server=192.168.0.4
+</pre></div>
+
+</dd>
+<dt><samp class="option">-loglevel [<var class="var">flags</var>+]<var class="var">loglevel</var> | -v [<var class="var">flags</var>+]<var class="var">loglevel</var></samp></dt>
+<dd><p>Set logging level and flags used by the library.
+</p>
+<p>The optional <var class="var">flags</var> prefix can consist of the following values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">repeat</samp>&rsquo;</dt>
+<dd><p>Indicates that repeated log output should not be compressed to the first line
+and the &quot;Last message repeated n times&quot; line will be omitted.
+</p></dd>
+<dt>&lsquo;<samp class="samp">level</samp>&rsquo;</dt>
+<dd><p>Indicates that log output should add a <code class="code">[level]</code> prefix to each message
+line. This can be used as an alternative to log coloring, e.g. when dumping the
+log to file.
+</p></dd>
+<dt>&lsquo;<samp class="samp">time</samp>&rsquo;</dt>
+<dd><p>Indicates that log lines should be prefixed with time information.
+</p></dd>
+<dt>&lsquo;<samp class="samp">datetime</samp>&rsquo;</dt>
+<dd><p>Indicates that log lines should be prefixed with date and time information.
+</p></dd>
+</dl>
+<p>Flags can also be used alone by adding a &rsquo;+&rsquo;/&rsquo;-&rsquo; prefix to set/reset a single
+flag without affecting other <var class="var">flags</var> or changing <var class="var">loglevel</var>. When
+setting both <var class="var">flags</var> and <var class="var">loglevel</var>, a &rsquo;+&rsquo; separator is expected
+between the last <var class="var">flags</var> value and before <var class="var">loglevel</var>.
+</p>
+<p><var class="var">loglevel</var> is a string or a number containing one of the following values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">quiet, -8</samp>&rsquo;</dt>
+<dd><p>Show nothing at all; be silent.
+</p></dd>
+<dt>&lsquo;<samp class="samp">panic, 0</samp>&rsquo;</dt>
+<dd><p>Only show fatal errors which could lead the process to crash, such as
+an assertion failure. This is not currently used for anything.
+</p></dd>
+<dt>&lsquo;<samp class="samp">fatal, 8</samp>&rsquo;</dt>
+<dd><p>Only show fatal errors. These are errors after which the process absolutely
+cannot continue.
+</p></dd>
+<dt>&lsquo;<samp class="samp">error, 16</samp>&rsquo;</dt>
+<dd><p>Show all errors, including ones which can be recovered from.
+</p></dd>
+<dt>&lsquo;<samp class="samp">warning, 24</samp>&rsquo;</dt>
+<dd><p>Show all warnings and errors. Any message related to possibly
+incorrect or unexpected events will be shown.
+</p></dd>
+<dt>&lsquo;<samp class="samp">info, 32</samp>&rsquo;</dt>
+<dd><p>Show informative messages during processing. This is in addition to
+warnings and errors. This is the default value.
+</p></dd>
+<dt>&lsquo;<samp class="samp">verbose, 40</samp>&rsquo;</dt>
+<dd><p>Same as <code class="code">info</code>, except more verbose.
+</p></dd>
+<dt>&lsquo;<samp class="samp">debug, 48</samp>&rsquo;</dt>
+<dd><p>Show everything, including debugging information.
+</p></dd>
+<dt>&lsquo;<samp class="samp">trace, 56</samp>&rsquo;</dt>
+</dl>
+
+<p>For example to enable repeated log output, add the <code class="code">level</code> prefix, and set
+<var class="var">loglevel</var> to <code class="code">verbose</code>:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -loglevel repeat+level+verbose -i input output
+</pre></div>
+<p>Another example that enables repeated log output without affecting current
+state of <code class="code">level</code> prefix flag or <var class="var">loglevel</var>:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg [...] -loglevel +repeat
+</pre></div>
+
+<p>By default the program logs to stderr. If coloring is supported by the
+terminal, colors are used to mark errors and warnings. Log coloring
+can be disabled setting the environment variable
+<code class="env">AV_LOG_FORCE_NOCOLOR</code>, or can be forced setting
+the environment variable <code class="env">AV_LOG_FORCE_COLOR</code>.
+</p>
+</dd>
+<dt><samp class="option">-report</samp></dt>
+<dd><p>Dump full command line and log output to a file named
+<code class="code"><var class="var">program</var>-<var class="var">YYYYMMDD</var>-<var class="var">HHMMSS</var>.log</code> in the current
+directory.
+This file can be useful for bug reports.
+It also implies <code class="code">-loglevel debug</code>.
+</p>
+<p>Setting the environment variable <code class="env">FFREPORT</code> to any value has the
+same effect. If the value is a &rsquo;:&rsquo;-separated key=value sequence, these
+options will affect the report; option values must be escaped if they
+contain special characters or the options delimiter &rsquo;:&rsquo; (see the
+&ldquo;Quoting and escaping&rdquo; section in the ffmpeg-utils manual).
+</p>
+<p>The following options are recognized:
+</p><dl class="table">
+<dt><samp class="option">file</samp></dt>
+<dd><p>set the file name to use for the report; <code class="code">%p</code> is expanded to the name
+of the program, <code class="code">%t</code> is expanded to a timestamp, <code class="code">%%</code> is expanded
+to a plain <code class="code">%</code>
+</p></dd>
+<dt><samp class="option">level</samp></dt>
+<dd><p>set the log verbosity level using a numerical value (see <code class="code">-loglevel</code>).
+</p></dd>
+</dl>
+
+<p>For example, to output a report to a file named <samp class="file">ffreport.log</samp>
+using a log level of <code class="code">32</code> (alias for log level <code class="code">info</code>):
+</p>
+<div class="example">
+<pre class="example-preformatted">FFREPORT=file=ffreport.log:level=32 ffmpeg -i input output
+</pre></div>
+
+<p>Errors in parsing the environment variable are not fatal, and will not
+appear in the report.
+</p>
+</dd>
+<dt><samp class="option">-hide_banner</samp></dt>
+<dd><p>Suppress printing banner.
+</p>
+<p>All FFmpeg tools will normally show a copyright notice, build options
+and library versions. This option can be used to suppress printing
+this information.
+</p>
+</dd>
+<dt><samp class="option">-cpuflags flags (<em class="emph">global</em>)</samp></dt>
+<dd><p>Allows setting and clearing cpu flags. This option is intended
+for testing. Do not use it unless you know what you&rsquo;re doing.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -cpuflags -sse+mmx ...
+ffmpeg -cpuflags mmx ...
+ffmpeg -cpuflags 0 ...
+</pre></div>
+<p>Possible flags for this option are:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">x86</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">mmx</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">mmxext</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse2slow</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse3slow</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">ssse3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">atom</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse4.1</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse4.2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">avx</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">avx2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">xop</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">fma3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">fma4</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">3dnow</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">3dnowext</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bmi1</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bmi2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">cmov</samp>&rsquo;</dt>
+</dl>
+</dd>
+<dt>&lsquo;<samp class="samp">ARM</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">armv5te</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">armv6</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">armv6t2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">vfp</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">vfpv3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">neon</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">setend</samp>&rsquo;</dt>
+</dl>
+</dd>
+<dt>&lsquo;<samp class="samp">AArch64</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">armv8</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">vfp</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">neon</samp>&rsquo;</dt>
+</dl>
+</dd>
+<dt>&lsquo;<samp class="samp">PowerPC</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">altivec</samp>&rsquo;</dt>
+</dl>
+</dd>
+<dt>&lsquo;<samp class="samp">Specific Processors</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">pentium2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">pentium3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">pentium4</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">k6</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">k62</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">athlon</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">athlonxp</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">k8</samp>&rsquo;</dt>
+</dl>
+</dd>
+</dl>
+
+</dd>
+<dt><samp class="option">-cpucount <var class="var">count</var> (<em class="emph">global</em>)</samp></dt>
+<dd><p>Override detection of CPU count. This option is intended
+for testing. Do not use it unless you know what you&rsquo;re doing.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -cpucount 2
+</pre></div>
+
+</dd>
+<dt><samp class="option">-max_alloc <var class="var">bytes</var></samp></dt>
+<dd><p>Set the maximum size limit for allocating a block on the heap by ffmpeg&rsquo;s
+family of malloc functions. Exercise <strong class="strong">extreme caution</strong> when using
+this option. Don&rsquo;t use if you do not understand the full consequence of doing so.
+Default is INT_MAX.
+</p></dd>
+</dl>
+
+<a name="AVOptions"></a>
+<h3 class="section">3.3 AVOptions<span class="pull-right"><a class="anchor hidden-xs" href="#AVOptions" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-AVOptions" aria-hidden="true">TOC</a></span></h3>
+
+<p>These options are provided directly by the libavformat, libavdevice and
+libavcodec libraries. To see the list of available AVOptions, use the
+<samp class="option">-help</samp> option. They are separated into two categories:
+</p><dl class="table">
+<dt><samp class="option">generic</samp></dt>
+<dd><p>These options can be set for any container, codec or device. Generic options
+are listed under AVFormatContext options for containers/devices and under
+AVCodecContext options for codecs.
+</p></dd>
+<dt><samp class="option">private</samp></dt>
+<dd><p>These options are specific to the given container, device or codec. Private
+options are listed under their corresponding containers/devices/codecs.
+</p></dd>
+</dl>
+
+<p>For example to write an ID3v2.3 header instead of a default ID3v2.4 to
+an MP3 file, use the <samp class="option">id3v2_version</samp> private option of the MP3
+muxer:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i input.flac -id3v2_version 3 out.mp3
+</pre></div>
+
+<p>All codec AVOptions are per-stream, and thus a stream specifier
+should be attached to them:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i multichannel.mxf -map 0:v:0 -map 0:a:0 -map 0:a:0 -c:a:0 ac3 -b:a:0 640k -ac:a:1 2 -c:a:1 aac -b:2 128k out.mp4
+</pre></div>
+
+<p>In the above example, a multichannel audio stream is mapped twice for output.
+The first instance is encoded with codec ac3 and bitrate 640k.
+The second instance is downmixed to 2 channels and encoded with codec aac. A bitrate of 128k is specified for it using
+absolute index of the output stream.
+</p>
+<p>Note: the <samp class="option">-nooption</samp> syntax cannot be used for boolean
+AVOptions, use <samp class="option">-option 0</samp>/<samp class="option">-option 1</samp>.
+</p>
+<p>Note: the old undocumented way of specifying per-stream AVOptions by
+prepending v/a/s to the options name is now obsolete and will be
+removed soon.
+</p>
+<a name="Main-options"></a>
+<h3 class="section">3.4 Main options<span class="pull-right"><a class="anchor hidden-xs" href="#Main-options" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Main-options" aria-hidden="true">TOC</a></span></h3>
+
+<dl class="table">
+<dt><samp class="option">-x <var class="var">width</var></samp></dt>
+<dd><p>Force displayed width.
+</p></dd>
+<dt><samp class="option">-y <var class="var">height</var></samp></dt>
+<dd><p>Force displayed height.
+</p></dd>
+<dt><samp class="option">-fs</samp></dt>
+<dd><p>Start in fullscreen mode.
+</p></dd>
+<dt><samp class="option">-an</samp></dt>
+<dd><p>Disable audio.
+</p></dd>
+<dt><samp class="option">-vn</samp></dt>
+<dd><p>Disable video.
+</p></dd>
+<dt><samp class="option">-sn</samp></dt>
+<dd><p>Disable subtitles.
+</p></dd>
+<dt><samp class="option">-ss <var class="var">pos</var></samp></dt>
+<dd><p>Seek to <var class="var">pos</var>. Note that in most formats it is not possible to seek
+exactly, so <code class="command">ffplay</code> will seek to the nearest seek point to
+<var class="var">pos</var>.
+</p>
+<p><var class="var">pos</var> must be a time duration specification,
+see <a data-manual="ffmpeg-utils" href="ffmpeg-utils.html#time-duration-syntax">the Time duration section in the ffmpeg-utils(1) manual</a>.
+</p></dd>
+<dt><samp class="option">-t <var class="var">duration</var></samp></dt>
+<dd><p>Play <var class="var">duration</var> seconds of audio/video.
+</p>
+<p><var class="var">duration</var> must be a time duration specification,
+see <a data-manual="ffmpeg-utils" href="ffmpeg-utils.html#time-duration-syntax">the Time duration section in the ffmpeg-utils(1) manual</a>.
+</p></dd>
+<dt><samp class="option">-bytes</samp></dt>
+<dd><p>Seek by bytes.
+</p></dd>
+<dt><samp class="option">-seek_interval</samp></dt>
+<dd><p>Set custom interval, in seconds, for seeking using left/right keys. Default is 10 seconds.
+</p></dd>
+<dt><samp class="option">-nodisp</samp></dt>
+<dd><p>Disable graphical display.
+</p></dd>
+<dt><samp class="option">-noborder</samp></dt>
+<dd><p>Borderless window.
+</p></dd>
+<dt><samp class="option">-alwaysontop</samp></dt>
+<dd><p>Window always on top. Available on: X11 with SDL &gt;= 2.0.5, Windows SDL &gt;= 2.0.6.
+</p></dd>
+<dt><samp class="option">-volume</samp></dt>
+<dd><p>Set the startup volume. 0 means silence, 100 means no volume reduction or
+amplification. Negative values are treated as 0, values above 100 are treated
+as 100.
+</p></dd>
+<dt><samp class="option">-f <var class="var">fmt</var></samp></dt>
+<dd><p>Force format.
+</p></dd>
+<dt><samp class="option">-window_title <var class="var">title</var></samp></dt>
+<dd><p>Set window title (default is the input filename).
+</p></dd>
+<dt><samp class="option">-left <var class="var">title</var></samp></dt>
+<dd><p>Set the x position for the left of the window (default is a centered window).
+</p></dd>
+<dt><samp class="option">-top <var class="var">title</var></samp></dt>
+<dd><p>Set the y position for the top of the window (default is a centered window).
+</p></dd>
+<dt><samp class="option">-loop <var class="var">number</var></samp></dt>
+<dd><p>Loops movie playback &lt;number&gt; times. 0 means forever.
+</p></dd>
+<dt><samp class="option">-showmode <var class="var">mode</var></samp></dt>
+<dd><p>Set the show mode to use.
+Available values for <var class="var">mode</var> are:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">0, video</samp>&rsquo;</dt>
+<dd><p>show video
+</p></dd>
+<dt>&lsquo;<samp class="samp">1, waves</samp>&rsquo;</dt>
+<dd><p>show audio waves
+</p></dd>
+<dt>&lsquo;<samp class="samp">2, rdft</samp>&rsquo;</dt>
+<dd><p>show audio frequency band using RDFT ((Inverse) Real Discrete Fourier Transform)
+</p></dd>
+</dl>
+
+<p>Default value is &quot;video&quot;, if video is not present or cannot be played
+&quot;rdft&quot; is automatically selected.
+</p>
+<p>You can interactively cycle through the available show modes by
+pressing the key <kbd class="key">w</kbd>.
+</p>
+</dd>
+<dt><samp class="option">-vf <var class="var">filtergraph</var></samp></dt>
+<dd><p>Create the filtergraph specified by <var class="var">filtergraph</var> and use it to
+filter the video stream.
+</p>
+<p><var class="var">filtergraph</var> is a description of the filtergraph to apply to
+the stream, and must have a single video input and a single video
+output. In the filtergraph, the input is associated to the label
+<code class="code">in</code>, and the output to the label <code class="code">out</code>. See the
+ffmpeg-filters manual for more information about the filtergraph
+syntax.
+</p>
+<p>You can specify this parameter multiple times and cycle through the specified
+filtergraphs along with the show modes by pressing the key <kbd class="key">w</kbd>.
+</p>
+</dd>
+<dt><samp class="option">-af <var class="var">filtergraph</var></samp></dt>
+<dd><p><var class="var">filtergraph</var> is a description of the filtergraph to apply to
+the input audio.
+Use the option &quot;-filters&quot; to show all the available filters (including
+sources and sinks).
+</p>
+</dd>
+<dt><samp class="option">-i <var class="var">input_url</var></samp></dt>
+<dd><p>Read <var class="var">input_url</var>.
+</p></dd>
+</dl>
+
+<a name="Advanced-options"></a>
+<h3 class="section">3.5 Advanced options<span class="pull-right"><a class="anchor hidden-xs" href="#Advanced-options" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Advanced-options" aria-hidden="true">TOC</a></span></h3>
+<dl class="table">
+<dt><samp class="option">-stats</samp></dt>
+<dd><p>Print several playback statistics, in particular show the stream
+duration, the codec parameters, the current position in the stream and
+the audio/video synchronisation drift. It is shown by default, unless the
+log level is lower than <code class="code">info</code>. Its display can be forced by manually
+specifying this option. To disable it, you need to specify <code class="code">-nostats</code>.
+</p>
+</dd>
+<dt><samp class="option">-fast</samp></dt>
+<dd><p>Non-spec-compliant optimizations.
+</p></dd>
+<dt><samp class="option">-genpts</samp></dt>
+<dd><p>Generate pts.
+</p></dd>
+<dt><samp class="option">-sync <var class="var">type</var></samp></dt>
+<dd><p>Set the master clock to audio (<code class="code">type=audio</code>), video
+(<code class="code">type=video</code>) or external (<code class="code">type=ext</code>). Default is audio. The
+master clock is used to control audio-video synchronization. Most media
+players use audio as master clock, but in some cases (streaming or high
+quality broadcast) it is necessary to change that. This option is mainly
+used for debugging purposes.
+</p></dd>
+<dt><samp class="option">-ast <var class="var">audio_stream_specifier</var></samp></dt>
+<dd><p>Select the desired audio stream using the given stream specifier. The stream
+specifiers are described in the <a class="ref" href="#Stream-specifiers">Stream specifiers</a> chapter. If this option
+is not specified, the &quot;best&quot; audio stream is selected in the program of the
+already selected video stream.
+</p></dd>
+<dt><samp class="option">-vst <var class="var">video_stream_specifier</var></samp></dt>
+<dd><p>Select the desired video stream using the given stream specifier. The stream
+specifiers are described in the <a class="ref" href="#Stream-specifiers">Stream specifiers</a> chapter. If this option
+is not specified, the &quot;best&quot; video stream is selected.
+</p></dd>
+<dt><samp class="option">-sst <var class="var">subtitle_stream_specifier</var></samp></dt>
+<dd><p>Select the desired subtitle stream using the given stream specifier. The stream
+specifiers are described in the <a class="ref" href="#Stream-specifiers">Stream specifiers</a> chapter. If this option
+is not specified, the &quot;best&quot; subtitle stream is selected in the program of the
+already selected video or audio stream.
+</p></dd>
+<dt><samp class="option">-autoexit</samp></dt>
+<dd><p>Exit when video is done playing.
+</p></dd>
+<dt><samp class="option">-exitonkeydown</samp></dt>
+<dd><p>Exit if any key is pressed.
+</p></dd>
+<dt><samp class="option">-exitonmousedown</samp></dt>
+<dd><p>Exit if any mouse button is pressed.
+</p>
+</dd>
+<dt><samp class="option">-codec:<var class="var">media_specifier</var> <var class="var">codec_name</var></samp></dt>
+<dd><p>Force a specific decoder implementation for the stream identified by
+<var class="var">media_specifier</var>, which can assume the values <code class="code">a</code> (audio),
+<code class="code">v</code> (video), and <code class="code">s</code> subtitle.
+</p>
+</dd>
+<dt><samp class="option">-acodec <var class="var">codec_name</var></samp></dt>
+<dd><p>Force a specific audio decoder.
+</p>
+</dd>
+<dt><samp class="option">-vcodec <var class="var">codec_name</var></samp></dt>
+<dd><p>Force a specific video decoder.
+</p>
+</dd>
+<dt><samp class="option">-scodec <var class="var">codec_name</var></samp></dt>
+<dd><p>Force a specific subtitle decoder.
+</p>
+</dd>
+<dt><samp class="option">-autorotate</samp></dt>
+<dd><p>Automatically rotate the video according to file metadata. Enabled by
+default, use <samp class="option">-noautorotate</samp> to disable it.
+</p>
+</dd>
+<dt><samp class="option">-framedrop</samp></dt>
+<dd><p>Drop video frames if video is out of sync. Enabled by default if the master
+clock is not set to video. Use this option to enable frame dropping for all
+master clock sources, use <samp class="option">-noframedrop</samp> to disable it.
+</p>
+</dd>
+<dt><samp class="option">-infbuf</samp></dt>
+<dd><p>Do not limit the input buffer size, read as much data as possible from the
+input as soon as possible. Enabled by default for realtime streams, where data
+may be dropped if not read in time. Use this option to enable infinite buffers
+for all inputs, use <samp class="option">-noinfbuf</samp> to disable it.
+</p>
+</dd>
+<dt><samp class="option">-filter_threads <var class="var">nb_threads</var></samp></dt>
+<dd><p>Defines how many threads are used to process a filter pipeline. Each pipeline
+will produce a thread pool with this many threads available for parallel
+processing. The default is 0 which means that the thread count will be
+determined by the number of available CPUs.
+</p>
+</dd>
+<dt><samp class="option">-enable_vulkan</samp></dt>
+<dd><p>Use vulkan renderer rather than SDL builtin renderer. Depends on libplacebo.
+</p>
+</dd>
+<dt><samp class="option">-vulkan_params</samp></dt>
+<dd>
+<p>Vulkan configuration using a list of <var class="var">key</var>=<var class="var">value</var> pairs separated by
+&quot;:&quot;.
+</p>
+</dd>
+<dt><samp class="option">-hwaccel</samp></dt>
+<dd><p>Use HW accelerated decoding. Enable this option will enable vulkan renderer
+automatically.
+</p>
+</dd>
+</dl>
+
+<a name="While-playing"></a>
+<h3 class="section">3.6 While playing<span class="pull-right"><a class="anchor hidden-xs" href="#While-playing" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-While-playing" aria-hidden="true">TOC</a></span></h3>
+
+<dl class="table">
+<dt><kbd class="key">q, ESC</kbd></dt>
+<dd><p>Quit.
+</p>
+</dd>
+<dt><kbd class="key">f</kbd></dt>
+<dd><p>Toggle full screen.
+</p>
+</dd>
+<dt><kbd class="key">p, SPC</kbd></dt>
+<dd><p>Pause.
+</p>
+</dd>
+<dt><kbd class="key">m</kbd></dt>
+<dd><p>Toggle mute.
+</p>
+</dd>
+<dt><kbd class="key">9, 0</kbd></dt>
+<dt><kbd class="key">/, *</kbd></dt>
+<dd><p>Decrease and increase volume respectively.
+</p>
+</dd>
+<dt><kbd class="key">a</kbd></dt>
+<dd><p>Cycle audio channel in the current program.
+</p>
+</dd>
+<dt><kbd class="key">v</kbd></dt>
+<dd><p>Cycle video channel.
+</p>
+</dd>
+<dt><kbd class="key">t</kbd></dt>
+<dd><p>Cycle subtitle channel in the current program.
+</p>
+</dd>
+<dt><kbd class="key">c</kbd></dt>
+<dd><p>Cycle program.
+</p>
+</dd>
+<dt><kbd class="key">w</kbd></dt>
+<dd><p>Cycle video filters or show modes.
+</p>
+</dd>
+<dt><kbd class="key">s</kbd></dt>
+<dd><p>Step to the next frame.
+</p>
+<p>Pause if the stream is not already paused, step to the next video
+frame, and pause.
+</p>
+</dd>
+<dt><kbd class="key">left/right</kbd></dt>
+<dd><p>Seek backward/forward 10 seconds.
+</p>
+</dd>
+<dt><kbd class="key">down/up</kbd></dt>
+<dd><p>Seek backward/forward 1 minute.
+</p>
+</dd>
+<dt><kbd class="key">page down/page up</kbd></dt>
+<dd><p>Seek to the previous/next chapter.
+or if there are no chapters
+Seek backward/forward 10 minutes.
+</p>
+</dd>
+<dt><kbd class="key">right mouse click</kbd></dt>
+<dd><p>Seek to percentage in file corresponding to fraction of width.
+</p>
+</dd>
+<dt><kbd class="key">left mouse double-click</kbd></dt>
+<dd><p>Toggle full screen.
+</p>
+</dd>
+</dl>
+
+
+
+<a name="See-Also"></a>
+<h2 class="chapter">4 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffplay-all.html">ffmpeg-all</a>,
+<a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="ffmpeg-utils.html">ffmpeg-utils</a>,
+<a class="url" href="ffmpeg-scaler.html">ffmpeg-scaler</a>,
+<a class="url" href="ffmpeg-resampler.html">ffmpeg-resampler</a>,
+<a class="url" href="ffmpeg-codecs.html">ffmpeg-codecs</a>,
+<a class="url" href="ffmpeg-bitstream-filters.html">ffmpeg-bitstream-filters</a>,
+<a class="url" href="ffmpeg-formats.html">ffmpeg-formats</a>,
+<a class="url" href="ffmpeg-devices.html">ffmpeg-devices</a>,
+<a class="url" href="ffmpeg-protocols.html">ffmpeg-protocols</a>,
+<a class="url" href="ffmpeg-filters.html">ffmpeg-filters</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">5 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/ffprobe.html

@@ -0,0 +1,1267 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      ffprobe Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      ffprobe Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Synopsis" href="#Synopsis">1 Synopsis</a></li>
+  <li><a id="toc-Description" href="#Description">2 Description</a></li>
+  <li><a id="toc-Options" href="#Options">3 Options</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Stream-specifiers-1" href="#Stream-specifiers-1">3.1 Stream specifiers</a></li>
+    <li><a id="toc-Generic-options" href="#Generic-options">3.2 Generic options</a></li>
+    <li><a id="toc-AVOptions" href="#AVOptions">3.3 AVOptions</a></li>
+    <li><a id="toc-Main-options" href="#Main-options">3.4 Main options</a></li>
+  </ul></li>
+  <li><a id="toc-Writers" href="#Writers">4 Writers</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-default" href="#default">4.1 default</a></li>
+    <li><a id="toc-compact_002c-csv" href="#compact_002c-csv">4.2 compact, csv</a></li>
+    <li><a id="toc-flat" href="#flat">4.3 flat</a></li>
+    <li><a id="toc-ini" href="#ini">4.4 ini</a></li>
+    <li><a id="toc-json" href="#json">4.5 json</a></li>
+    <li><a id="toc-xml" href="#xml">4.6 xml</a></li>
+  </ul></li>
+  <li><a id="toc-Timecode" href="#Timecode">5 Timecode</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">6 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">7 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Synopsis"></a>
+<h2 class="chapter">1 Synopsis<span class="pull-right"><a class="anchor hidden-xs" href="#Synopsis" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Synopsis" aria-hidden="true">TOC</a></span></h2>
+
+<p>ffprobe [<var class="var">options</var>] <samp class="file">input_url</samp>
+</p>
+<a name="Description"></a>
+<h2 class="chapter">2 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>ffprobe gathers information from multimedia streams and prints it in
+human- and machine-readable fashion.
+</p>
+<p>For example it can be used to check the format of the container used
+by a multimedia stream and the format and type of each media stream
+contained in it.
+</p>
+<p>If a url is specified in input, ffprobe will try to open and
+probe the url content. If the url cannot be opened or recognized as
+a multimedia file, a positive exit code is returned.
+</p>
+<p>If no output is specified as output with <samp class="option">o</samp> ffprobe will write
+to stdout.
+</p>
+<p>ffprobe may be employed both as a standalone application or in
+combination with a textual filter, which may perform more
+sophisticated processing, e.g. statistical processing or plotting.
+</p>
+<p>Options are used to list some of the formats supported by ffprobe or
+for specifying which information to display, and for setting how
+ffprobe will show it.
+</p>
+<p>ffprobe output is designed to be easily parsable by a textual filter,
+and consists of one or more sections of a form defined by the selected
+writer, which is specified by the <samp class="option">output_format</samp> option.
+</p>
+<p>Sections may contain other nested sections, and are identified by a
+name (which may be shared by other sections), and an unique
+name. See the output of <samp class="option">sections</samp>.
+</p>
+<p>Metadata tags stored in the container or in the streams are recognized
+and printed in the corresponding &quot;FORMAT&quot;, &quot;STREAM&quot;, &quot;STREAM_GROUP_STREAM&quot;
+or &quot;PROGRAM_STREAM&quot; section.
+</p>
+
+<a name="Options"></a>
+<h2 class="chapter">3 Options<span class="pull-right"><a class="anchor hidden-xs" href="#Options" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Options" aria-hidden="true">TOC</a></span></h2>
+
+<p>All the numerical options, if not specified otherwise, accept a string
+representing a number as input, which may be followed by one of the SI
+unit prefixes, for example: &rsquo;K&rsquo;, &rsquo;M&rsquo;, or &rsquo;G&rsquo;.
+</p>
+<p>If &rsquo;i&rsquo; is appended to the SI unit prefix, the complete prefix will be
+interpreted as a unit prefix for binary multiples, which are based on
+powers of 1024 instead of powers of 1000. Appending &rsquo;B&rsquo; to the SI unit
+prefix multiplies the value by 8. This allows using, for example:
+&rsquo;KB&rsquo;, &rsquo;MiB&rsquo;, &rsquo;G&rsquo; and &rsquo;B&rsquo; as number suffixes.
+</p>
+<p>Options which do not take arguments are boolean options, and set the
+corresponding value to true. They can be set to false by prefixing
+the option name with &quot;no&quot;. For example using &quot;-nofoo&quot;
+will set the boolean option with name &quot;foo&quot; to false.
+</p>
+<p>Options that take arguments support a special syntax where the argument given on
+the command line is interpreted as a path to the file from which the actual
+argument value is loaded. To use this feature, add a forward slash &rsquo;/&rsquo;
+immediately before the option name (after the leading dash). E.g.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i INPUT -/filter:v filter.script OUTPUT
+</pre></div>
+<p>will load a filtergraph description from the file named <samp class="file">filter.script</samp>.
+</p>
+<a class="anchor" id="Stream-specifiers"></a><a name="Stream-specifiers-1"></a>
+<h3 class="section">3.1 Stream specifiers<span class="pull-right"><a class="anchor hidden-xs" href="#Stream-specifiers-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Stream-specifiers-1" aria-hidden="true">TOC</a></span></h3>
+<p>Some options are applied per-stream, e.g. bitrate or codec. Stream specifiers
+are used to precisely specify which stream(s) a given option belongs to.
+</p>
+<p>A stream specifier is a string generally appended to the option name and
+separated from it by a colon. E.g. <code class="code">-codec:a:1 ac3</code> contains the
+<code class="code">a:1</code> stream specifier, which matches the second audio stream. Therefore, it
+would select the ac3 codec for the second audio stream.
+</p>
+<p>A stream specifier can match several streams, so that the option is applied to all
+of them. E.g. the stream specifier in <code class="code">-b:a 128k</code> matches all audio
+streams.
+</p>
+<p>An empty stream specifier matches all streams. For example, <code class="code">-codec copy</code>
+or <code class="code">-codec: copy</code> would copy all the streams without reencoding.
+</p>
+<p>Possible forms of stream specifiers are:
+</p><dl class="table">
+<dt><samp class="option"><var class="var">stream_index</var></samp></dt>
+<dd><p>Matches the stream with this index. E.g. <code class="code">-threads:1 4</code> would set the
+thread count for the second stream to 4. If <var class="var">stream_index</var> is used as an
+additional stream specifier (see below), then it selects stream number
+<var class="var">stream_index</var> from the matching streams. Stream numbering is based on the
+order of the streams as detected by libavformat except when a stream group
+specifier or program ID is also specified. In this case it is based on the
+ordering of the streams in the group or program.
+</p></dd>
+<dt><samp class="option"><var class="var">stream_type</var>[:<var class="var">additional_stream_specifier</var>]</samp></dt>
+<dd><p><var class="var">stream_type</var> is one of following: &rsquo;v&rsquo; or &rsquo;V&rsquo; for video, &rsquo;a&rsquo; for audio, &rsquo;s&rsquo;
+for subtitle, &rsquo;d&rsquo; for data, and &rsquo;t&rsquo; for attachments. &rsquo;v&rsquo; matches all video
+streams, &rsquo;V&rsquo; only matches video streams which are not attached pictures, video
+thumbnails or cover arts. If <var class="var">additional_stream_specifier</var> is used, then
+it matches streams which both have this type and match the
+<var class="var">additional_stream_specifier</var>. Otherwise, it matches all streams of the
+specified type.
+</p></dd>
+<dt><samp class="option">g:<var class="var">group_specifier</var>[:<var class="var">additional_stream_specifier</var>]</samp></dt>
+<dd><p>Matches streams which are in the group with the specifier <var class="var">group_specifier</var>.
+if <var class="var">additional_stream_specifier</var> is used, then it matches streams which both
+are part of the group and match the <var class="var">additional_stream_specifier</var>.
+<var class="var">group_specifier</var> may be one of the following:
+</p><dl class="table">
+<dt><samp class="option"><var class="var">group_index</var></samp></dt>
+<dd><p>Match the stream with this group index.
+</p></dd>
+<dt><samp class="option">#<var class="var">group_id</var> or i:<var class="var">group_id</var></samp></dt>
+<dd><p>Match the stream with this group id.
+</p></dd>
+</dl>
+</dd>
+<dt><samp class="option">p:<var class="var">program_id</var>[:<var class="var">additional_stream_specifier</var>]</samp></dt>
+<dd><p>Matches streams which are in the program with the id <var class="var">program_id</var>. If
+<var class="var">additional_stream_specifier</var> is used, then it matches streams which both
+are part of the program and match the <var class="var">additional_stream_specifier</var>.
+</p>
+</dd>
+<dt><samp class="option">#<var class="var">stream_id</var> or i:<var class="var">stream_id</var></samp></dt>
+<dd><p>Match the stream by stream id (e.g. PID in MPEG-TS container).
+</p></dd>
+<dt><samp class="option">m:<var class="var">key</var>[:<var class="var">value</var>]</samp></dt>
+<dd><p>Matches streams with the metadata tag <var class="var">key</var> having the specified value. If
+<var class="var">value</var> is not given, matches streams that contain the given tag with any
+value. The colon character &rsquo;:&rsquo; in <var class="var">key</var> or <var class="var">value</var> needs to be
+backslash-escaped.
+</p></dd>
+<dt><samp class="option">disp:<var class="var">dispositions</var>[:<var class="var">additional_stream_specifier</var>]</samp></dt>
+<dd><p>Matches streams with the given disposition(s). <var class="var">dispositions</var> is a list of
+one or more dispositions (as printed by the <samp class="option">-dispositions</samp> option)
+joined with &rsquo;+&rsquo;.
+</p></dd>
+<dt><samp class="option">u</samp></dt>
+<dd><p>Matches streams with usable configuration, the codec must be defined and the
+essential information such as video dimension or audio sample rate must be present.
+</p>
+<p>Note that in <code class="command">ffmpeg</code>, matching by metadata will only work properly for
+input files.
+</p></dd>
+</dl>
+
+<a name="Generic-options"></a>
+<h3 class="section">3.2 Generic options<span class="pull-right"><a class="anchor hidden-xs" href="#Generic-options" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Generic-options" aria-hidden="true">TOC</a></span></h3>
+
+<p>These options are shared amongst the ff* tools.
+</p>
+<dl class="table">
+<dt><samp class="option">-L</samp></dt>
+<dd><p>Show license.
+</p>
+</dd>
+<dt><samp class="option">-h, -?, -help, --help [<var class="var">arg</var>]</samp></dt>
+<dd><p>Show help. An optional parameter may be specified to print help about a specific
+item. If no argument is specified, only basic (non advanced) tool
+options are shown.
+</p>
+<p>Possible values of <var class="var">arg</var> are:
+</p><dl class="table">
+<dt><samp class="option">long</samp></dt>
+<dd><p>Print advanced tool options in addition to the basic tool options.
+</p>
+</dd>
+<dt><samp class="option">full</samp></dt>
+<dd><p>Print complete list of options, including shared and private options
+for encoders, decoders, demuxers, muxers, filters, etc.
+</p>
+</dd>
+<dt><samp class="option">decoder=<var class="var">decoder_name</var></samp></dt>
+<dd><p>Print detailed information about the decoder named <var class="var">decoder_name</var>. Use the
+<samp class="option">-decoders</samp> option to get a list of all decoders.
+</p>
+</dd>
+<dt><samp class="option">encoder=<var class="var">encoder_name</var></samp></dt>
+<dd><p>Print detailed information about the encoder named <var class="var">encoder_name</var>. Use the
+<samp class="option">-encoders</samp> option to get a list of all encoders.
+</p>
+</dd>
+<dt><samp class="option">demuxer=<var class="var">demuxer_name</var></samp></dt>
+<dd><p>Print detailed information about the demuxer named <var class="var">demuxer_name</var>. Use the
+<samp class="option">-formats</samp> option to get a list of all demuxers and muxers.
+</p>
+</dd>
+<dt><samp class="option">muxer=<var class="var">muxer_name</var></samp></dt>
+<dd><p>Print detailed information about the muxer named <var class="var">muxer_name</var>. Use the
+<samp class="option">-formats</samp> option to get a list of all muxers and demuxers.
+</p>
+</dd>
+<dt><samp class="option">filter=<var class="var">filter_name</var></samp></dt>
+<dd><p>Print detailed information about the filter named <var class="var">filter_name</var>. Use the
+<samp class="option">-filters</samp> option to get a list of all filters.
+</p>
+</dd>
+<dt><samp class="option">bsf=<var class="var">bitstream_filter_name</var></samp></dt>
+<dd><p>Print detailed information about the bitstream filter named <var class="var">bitstream_filter_name</var>.
+Use the <samp class="option">-bsfs</samp> option to get a list of all bitstream filters.
+</p>
+</dd>
+<dt><samp class="option">protocol=<var class="var">protocol_name</var></samp></dt>
+<dd><p>Print detailed information about the protocol named <var class="var">protocol_name</var>.
+Use the <samp class="option">-protocols</samp> option to get a list of all protocols.
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">-version</samp></dt>
+<dd><p>Show version.
+</p>
+</dd>
+<dt><samp class="option">-buildconf</samp></dt>
+<dd><p>Show the build configuration, one option per line.
+</p>
+</dd>
+<dt><samp class="option">-formats</samp></dt>
+<dd><p>Show available formats (including devices).
+</p>
+</dd>
+<dt><samp class="option">-demuxers</samp></dt>
+<dd><p>Show available demuxers.
+</p>
+</dd>
+<dt><samp class="option">-muxers</samp></dt>
+<dd><p>Show available muxers.
+</p>
+</dd>
+<dt><samp class="option">-devices</samp></dt>
+<dd><p>Show available devices.
+</p>
+</dd>
+<dt><samp class="option">-codecs</samp></dt>
+<dd><p>Show all codecs known to libavcodec.
+</p>
+<p>Note that the term &rsquo;codec&rsquo; is used throughout this documentation as a shortcut
+for what is more correctly called a media bitstream format.
+</p>
+</dd>
+<dt><samp class="option">-decoders</samp></dt>
+<dd><p>Show available decoders.
+</p>
+</dd>
+<dt><samp class="option">-encoders</samp></dt>
+<dd><p>Show all available encoders.
+</p>
+</dd>
+<dt><samp class="option">-bsfs</samp></dt>
+<dd><p>Show available bitstream filters.
+</p>
+</dd>
+<dt><samp class="option">-protocols</samp></dt>
+<dd><p>Show available protocols.
+</p>
+</dd>
+<dt><samp class="option">-filters</samp></dt>
+<dd><p>Show available libavfilter filters.
+</p>
+</dd>
+<dt><samp class="option">-pix_fmts</samp></dt>
+<dd><p>Show available pixel formats.
+</p>
+</dd>
+<dt><samp class="option">-sample_fmts</samp></dt>
+<dd><p>Show available sample formats.
+</p>
+</dd>
+<dt><samp class="option">-layouts</samp></dt>
+<dd><p>Show channel names and standard channel layouts.
+</p>
+</dd>
+<dt><samp class="option">-dispositions</samp></dt>
+<dd><p>Show stream dispositions.
+</p>
+</dd>
+<dt><samp class="option">-colors</samp></dt>
+<dd><p>Show recognized color names.
+</p>
+</dd>
+<dt><samp class="option">-sources <var class="var">device</var>[,<var class="var">opt1</var>=<var class="var">val1</var>[,<var class="var">opt2</var>=<var class="var">val2</var>]...]</samp></dt>
+<dd><p>Show autodetected sources of the input device.
+Some devices may provide system-dependent source names that cannot be autodetected.
+The returned list cannot be assumed to be always complete.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -sources pulse,server=192.168.0.4
+</pre></div>
+
+</dd>
+<dt><samp class="option">-sinks <var class="var">device</var>[,<var class="var">opt1</var>=<var class="var">val1</var>[,<var class="var">opt2</var>=<var class="var">val2</var>]...]</samp></dt>
+<dd><p>Show autodetected sinks of the output device.
+Some devices may provide system-dependent sink names that cannot be autodetected.
+The returned list cannot be assumed to be always complete.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -sinks pulse,server=192.168.0.4
+</pre></div>
+
+</dd>
+<dt><samp class="option">-loglevel [<var class="var">flags</var>+]<var class="var">loglevel</var> | -v [<var class="var">flags</var>+]<var class="var">loglevel</var></samp></dt>
+<dd><p>Set logging level and flags used by the library.
+</p>
+<p>The optional <var class="var">flags</var> prefix can consist of the following values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">repeat</samp>&rsquo;</dt>
+<dd><p>Indicates that repeated log output should not be compressed to the first line
+and the &quot;Last message repeated n times&quot; line will be omitted.
+</p></dd>
+<dt>&lsquo;<samp class="samp">level</samp>&rsquo;</dt>
+<dd><p>Indicates that log output should add a <code class="code">[level]</code> prefix to each message
+line. This can be used as an alternative to log coloring, e.g. when dumping the
+log to file.
+</p></dd>
+<dt>&lsquo;<samp class="samp">time</samp>&rsquo;</dt>
+<dd><p>Indicates that log lines should be prefixed with time information.
+</p></dd>
+<dt>&lsquo;<samp class="samp">datetime</samp>&rsquo;</dt>
+<dd><p>Indicates that log lines should be prefixed with date and time information.
+</p></dd>
+</dl>
+<p>Flags can also be used alone by adding a &rsquo;+&rsquo;/&rsquo;-&rsquo; prefix to set/reset a single
+flag without affecting other <var class="var">flags</var> or changing <var class="var">loglevel</var>. When
+setting both <var class="var">flags</var> and <var class="var">loglevel</var>, a &rsquo;+&rsquo; separator is expected
+between the last <var class="var">flags</var> value and before <var class="var">loglevel</var>.
+</p>
+<p><var class="var">loglevel</var> is a string or a number containing one of the following values:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">quiet, -8</samp>&rsquo;</dt>
+<dd><p>Show nothing at all; be silent.
+</p></dd>
+<dt>&lsquo;<samp class="samp">panic, 0</samp>&rsquo;</dt>
+<dd><p>Only show fatal errors which could lead the process to crash, such as
+an assertion failure. This is not currently used for anything.
+</p></dd>
+<dt>&lsquo;<samp class="samp">fatal, 8</samp>&rsquo;</dt>
+<dd><p>Only show fatal errors. These are errors after which the process absolutely
+cannot continue.
+</p></dd>
+<dt>&lsquo;<samp class="samp">error, 16</samp>&rsquo;</dt>
+<dd><p>Show all errors, including ones which can be recovered from.
+</p></dd>
+<dt>&lsquo;<samp class="samp">warning, 24</samp>&rsquo;</dt>
+<dd><p>Show all warnings and errors. Any message related to possibly
+incorrect or unexpected events will be shown.
+</p></dd>
+<dt>&lsquo;<samp class="samp">info, 32</samp>&rsquo;</dt>
+<dd><p>Show informative messages during processing. This is in addition to
+warnings and errors. This is the default value.
+</p></dd>
+<dt>&lsquo;<samp class="samp">verbose, 40</samp>&rsquo;</dt>
+<dd><p>Same as <code class="code">info</code>, except more verbose.
+</p></dd>
+<dt>&lsquo;<samp class="samp">debug, 48</samp>&rsquo;</dt>
+<dd><p>Show everything, including debugging information.
+</p></dd>
+<dt>&lsquo;<samp class="samp">trace, 56</samp>&rsquo;</dt>
+</dl>
+
+<p>For example to enable repeated log output, add the <code class="code">level</code> prefix, and set
+<var class="var">loglevel</var> to <code class="code">verbose</code>:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -loglevel repeat+level+verbose -i input output
+</pre></div>
+<p>Another example that enables repeated log output without affecting current
+state of <code class="code">level</code> prefix flag or <var class="var">loglevel</var>:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg [...] -loglevel +repeat
+</pre></div>
+
+<p>By default the program logs to stderr. If coloring is supported by the
+terminal, colors are used to mark errors and warnings. Log coloring
+can be disabled setting the environment variable
+<code class="env">AV_LOG_FORCE_NOCOLOR</code>, or can be forced setting
+the environment variable <code class="env">AV_LOG_FORCE_COLOR</code>.
+</p>
+</dd>
+<dt><samp class="option">-report</samp></dt>
+<dd><p>Dump full command line and log output to a file named
+<code class="code"><var class="var">program</var>-<var class="var">YYYYMMDD</var>-<var class="var">HHMMSS</var>.log</code> in the current
+directory.
+This file can be useful for bug reports.
+It also implies <code class="code">-loglevel debug</code>.
+</p>
+<p>Setting the environment variable <code class="env">FFREPORT</code> to any value has the
+same effect. If the value is a &rsquo;:&rsquo;-separated key=value sequence, these
+options will affect the report; option values must be escaped if they
+contain special characters or the options delimiter &rsquo;:&rsquo; (see the
+&ldquo;Quoting and escaping&rdquo; section in the ffmpeg-utils manual).
+</p>
+<p>The following options are recognized:
+</p><dl class="table">
+<dt><samp class="option">file</samp></dt>
+<dd><p>set the file name to use for the report; <code class="code">%p</code> is expanded to the name
+of the program, <code class="code">%t</code> is expanded to a timestamp, <code class="code">%%</code> is expanded
+to a plain <code class="code">%</code>
+</p></dd>
+<dt><samp class="option">level</samp></dt>
+<dd><p>set the log verbosity level using a numerical value (see <code class="code">-loglevel</code>).
+</p></dd>
+</dl>
+
+<p>For example, to output a report to a file named <samp class="file">ffreport.log</samp>
+using a log level of <code class="code">32</code> (alias for log level <code class="code">info</code>):
+</p>
+<div class="example">
+<pre class="example-preformatted">FFREPORT=file=ffreport.log:level=32 ffmpeg -i input output
+</pre></div>
+
+<p>Errors in parsing the environment variable are not fatal, and will not
+appear in the report.
+</p>
+</dd>
+<dt><samp class="option">-hide_banner</samp></dt>
+<dd><p>Suppress printing banner.
+</p>
+<p>All FFmpeg tools will normally show a copyright notice, build options
+and library versions. This option can be used to suppress printing
+this information.
+</p>
+</dd>
+<dt><samp class="option">-cpuflags flags (<em class="emph">global</em>)</samp></dt>
+<dd><p>Allows setting and clearing cpu flags. This option is intended
+for testing. Do not use it unless you know what you&rsquo;re doing.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -cpuflags -sse+mmx ...
+ffmpeg -cpuflags mmx ...
+ffmpeg -cpuflags 0 ...
+</pre></div>
+<p>Possible flags for this option are:
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">x86</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">mmx</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">mmxext</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse2slow</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse3slow</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">ssse3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">atom</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse4.1</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">sse4.2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">avx</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">avx2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">xop</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">fma3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">fma4</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">3dnow</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">3dnowext</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bmi1</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">bmi2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">cmov</samp>&rsquo;</dt>
+</dl>
+</dd>
+<dt>&lsquo;<samp class="samp">ARM</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">armv5te</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">armv6</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">armv6t2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">vfp</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">vfpv3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">neon</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">setend</samp>&rsquo;</dt>
+</dl>
+</dd>
+<dt>&lsquo;<samp class="samp">AArch64</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">armv8</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">vfp</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">neon</samp>&rsquo;</dt>
+</dl>
+</dd>
+<dt>&lsquo;<samp class="samp">PowerPC</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">altivec</samp>&rsquo;</dt>
+</dl>
+</dd>
+<dt>&lsquo;<samp class="samp">Specific Processors</samp>&rsquo;</dt>
+<dd><dl class="table">
+<dt>&lsquo;<samp class="samp">pentium2</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">pentium3</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">pentium4</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">k6</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">k62</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">athlon</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">athlonxp</samp>&rsquo;</dt>
+<dt>&lsquo;<samp class="samp">k8</samp>&rsquo;</dt>
+</dl>
+</dd>
+</dl>
+
+</dd>
+<dt><samp class="option">-cpucount <var class="var">count</var> (<em class="emph">global</em>)</samp></dt>
+<dd><p>Override detection of CPU count. This option is intended
+for testing. Do not use it unless you know what you&rsquo;re doing.
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -cpucount 2
+</pre></div>
+
+</dd>
+<dt><samp class="option">-max_alloc <var class="var">bytes</var></samp></dt>
+<dd><p>Set the maximum size limit for allocating a block on the heap by ffmpeg&rsquo;s
+family of malloc functions. Exercise <strong class="strong">extreme caution</strong> when using
+this option. Don&rsquo;t use if you do not understand the full consequence of doing so.
+Default is INT_MAX.
+</p></dd>
+</dl>
+
+<a name="AVOptions"></a>
+<h3 class="section">3.3 AVOptions<span class="pull-right"><a class="anchor hidden-xs" href="#AVOptions" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-AVOptions" aria-hidden="true">TOC</a></span></h3>
+
+<p>These options are provided directly by the libavformat, libavdevice and
+libavcodec libraries. To see the list of available AVOptions, use the
+<samp class="option">-help</samp> option. They are separated into two categories:
+</p><dl class="table">
+<dt><samp class="option">generic</samp></dt>
+<dd><p>These options can be set for any container, codec or device. Generic options
+are listed under AVFormatContext options for containers/devices and under
+AVCodecContext options for codecs.
+</p></dd>
+<dt><samp class="option">private</samp></dt>
+<dd><p>These options are specific to the given container, device or codec. Private
+options are listed under their corresponding containers/devices/codecs.
+</p></dd>
+</dl>
+
+<p>For example to write an ID3v2.3 header instead of a default ID3v2.4 to
+an MP3 file, use the <samp class="option">id3v2_version</samp> private option of the MP3
+muxer:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i input.flac -id3v2_version 3 out.mp3
+</pre></div>
+
+<p>All codec AVOptions are per-stream, and thus a stream specifier
+should be attached to them:
+</p><div class="example">
+<pre class="example-preformatted">ffmpeg -i multichannel.mxf -map 0:v:0 -map 0:a:0 -map 0:a:0 -c:a:0 ac3 -b:a:0 640k -ac:a:1 2 -c:a:1 aac -b:2 128k out.mp4
+</pre></div>
+
+<p>In the above example, a multichannel audio stream is mapped twice for output.
+The first instance is encoded with codec ac3 and bitrate 640k.
+The second instance is downmixed to 2 channels and encoded with codec aac. A bitrate of 128k is specified for it using
+absolute index of the output stream.
+</p>
+<p>Note: the <samp class="option">-nooption</samp> syntax cannot be used for boolean
+AVOptions, use <samp class="option">-option 0</samp>/<samp class="option">-option 1</samp>.
+</p>
+<p>Note: the old undocumented way of specifying per-stream AVOptions by
+prepending v/a/s to the options name is now obsolete and will be
+removed soon.
+</p>
+<a name="Main-options"></a>
+<h3 class="section">3.4 Main options<span class="pull-right"><a class="anchor hidden-xs" href="#Main-options" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Main-options" aria-hidden="true">TOC</a></span></h3>
+
+<dl class="table">
+<dt><samp class="option">-f <var class="var">format</var></samp></dt>
+<dd><p>Force format to use.
+</p>
+</dd>
+<dt><samp class="option">-unit</samp></dt>
+<dd><p>Show the unit of the displayed values.
+</p>
+</dd>
+<dt><samp class="option">-prefix</samp></dt>
+<dd><p>Use SI prefixes for the displayed values.
+Unless the &quot;-byte_binary_prefix&quot; option is used all the prefixes
+are decimal.
+</p>
+</dd>
+<dt><samp class="option">-byte_binary_prefix</samp></dt>
+<dd><p>Force the use of binary prefixes for byte values.
+</p>
+</dd>
+<dt><samp class="option">-sexagesimal</samp></dt>
+<dd><p>Use sexagesimal format HH:MM:SS.MICROSECONDS for time values.
+</p>
+</dd>
+<dt><samp class="option">-pretty</samp></dt>
+<dd><p>Prettify the format of the displayed values, it corresponds to the
+options &quot;-unit -prefix -byte_binary_prefix -sexagesimal&quot;.
+</p>
+</dd>
+<dt><samp class="option">-output_format, -of, -print_format <var class="var">writer_name</var>[=<var class="var">writer_options</var>]</samp></dt>
+<dd><p>Set the output printing format.
+</p>
+<p><var class="var">writer_name</var> specifies the name of the writer, and
+<var class="var">writer_options</var> specifies the options to be passed to the writer.
+</p>
+<p>For example for printing the output in JSON format, specify:
+</p><div class="example">
+<pre class="example-preformatted">-output_format json
+</pre></div>
+
+<p>For more details on the available output printing formats, see the
+Writers section below.
+</p>
+</dd>
+<dt><samp class="option">-sections</samp></dt>
+<dd><p>Print sections structure and section information, and exit. The output
+is not meant to be parsed by a machine.
+</p>
+</dd>
+<dt><samp class="option">-select_streams <var class="var">stream_specifier</var></samp></dt>
+<dd><p>Select only the streams specified by <var class="var">stream_specifier</var>. This
+option affects only the options related to streams
+(e.g. <code class="code">show_streams</code>, <code class="code">show_packets</code>, etc.).
+</p>
+<p>For example to show only audio streams, you can use the command:
+</p><div class="example">
+<pre class="example-preformatted">ffprobe -show_streams -select_streams a INPUT
+</pre></div>
+
+<p>To show only video packets belonging to the video stream with index 1:
+</p><div class="example">
+<pre class="example-preformatted">ffprobe -show_packets -select_streams v:1 INPUT
+</pre></div>
+
+</dd>
+<dt><samp class="option">-show_data</samp></dt>
+<dd><p>Show payload data, as a hexadecimal and ASCII dump. Coupled with
+<samp class="option">-show_packets</samp>, it will dump the packets&rsquo; data. Coupled with
+<samp class="option">-show_streams</samp>, it will dump the codec extradata.
+</p>
+<p>The dump is printed as the &quot;data&quot; field. It may contain newlines.
+</p>
+</dd>
+<dt><samp class="option">-show_data_hash <var class="var">algorithm</var></samp></dt>
+<dd><p>Show a hash of payload data, for packets with <samp class="option">-show_packets</samp> and for
+codec extradata with <samp class="option">-show_streams</samp>.
+</p>
+</dd>
+<dt><samp class="option">-show_error</samp></dt>
+<dd><p>Show information about the error found when trying to probe the input.
+</p>
+<p>The error information is printed within a section with name &quot;ERROR&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_format</samp></dt>
+<dd><p>Show information about the container format of the input multimedia
+stream.
+</p>
+<p>All the container format information is printed within a section with
+name &quot;FORMAT&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_entries <var class="var">section_entries</var></samp></dt>
+<dd><p>Set list of entries to show.
+</p>
+<p>Entries are specified according to the following
+syntax. <var class="var">section_entries</var> contains a list of section entries
+separated by <code class="code">:</code>. Each section entry is composed by a section
+name (or unique name), optionally followed by a list of entries local
+to that section, separated by <code class="code">,</code>.
+</p>
+<p>If section name is specified but is followed by no <code class="code">=</code>, all
+entries are printed to output, together with all the contained
+sections. Otherwise only the entries specified in the local section
+entries list are printed. In particular, if <code class="code">=</code> is specified but
+the list of local entries is empty, then no entries will be shown for
+that section.
+</p>
+<p>Note that the order of specification of the local section entries is
+not honored in the output, and the usual display order will be
+retained.
+</p>
+<p>The formal syntax is given by:
+</p><div class="example">
+<pre class="example-preformatted"><var class="var">LOCAL_SECTION_ENTRIES</var> ::= <var class="var">SECTION_ENTRY_NAME</var>[,<var class="var">LOCAL_SECTION_ENTRIES</var>]
+<var class="var">SECTION_ENTRY</var>         ::= <var class="var">SECTION_NAME</var>[=[<var class="var">LOCAL_SECTION_ENTRIES</var>]]
+<var class="var">SECTION_ENTRIES</var>       ::= <var class="var">SECTION_ENTRY</var>[:<var class="var">SECTION_ENTRIES</var>]
+</pre></div>
+
+<p>For example, to show only the index and type of each stream, and the PTS
+time, duration time, and stream index of the packets, you can specify
+the argument:
+</p><div class="example">
+<pre class="example-preformatted">packet=pts_time,duration_time,stream_index : stream=index,codec_type
+</pre></div>
+
+<p>To show all the entries in the section &quot;format&quot;, but only the codec
+type in the section &quot;stream&quot;, specify the argument:
+</p><div class="example">
+<pre class="example-preformatted">format : stream=codec_type
+</pre></div>
+
+<p>To show all the tags in the stream and format sections:
+</p><div class="example">
+<pre class="example-preformatted">stream_tags : format_tags
+</pre></div>
+
+<p>To show only the <code class="code">title</code> tag (if available) in the stream
+sections:
+</p><div class="example">
+<pre class="example-preformatted">stream_tags=title
+</pre></div>
+
+</dd>
+<dt><samp class="option">-show_packets</samp></dt>
+<dd><p>Show information about each packet contained in the input multimedia
+stream.
+</p>
+<p>The information for each single packet is printed within a dedicated
+section with name &quot;PACKET&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_frames</samp></dt>
+<dd><p>Show information about each frame and subtitle contained in the input
+multimedia stream.
+</p>
+<p>The information for each single frame is printed within a dedicated
+section with name &quot;FRAME&quot; or &quot;SUBTITLE&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_log <var class="var">loglevel</var></samp></dt>
+<dd><p>Show logging information from the decoder about each frame according to
+the value set in <var class="var">loglevel</var>, (see <code class="code">-loglevel</code>). This option requires <code class="code">-show_frames</code>.
+</p>
+<p>The information for each log message is printed within a dedicated
+section with name &quot;LOG&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_streams</samp></dt>
+<dd><p>Show information about each media stream contained in the input
+multimedia stream.
+</p>
+<p>Each media stream information is printed within a dedicated section
+with name &quot;STREAM&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_programs</samp></dt>
+<dd><p>Show information about programs and their streams contained in the input
+multimedia stream.
+</p>
+<p>Each media stream information is printed within a dedicated section
+with name &quot;PROGRAM_STREAM&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_stream_groups</samp></dt>
+<dd><p>Show information about stream groups and their streams contained in the
+input multimedia stream.
+</p>
+<p>Each media stream information is printed within a dedicated section
+with name &quot;STREAM_GROUP_STREAM&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_chapters</samp></dt>
+<dd><p>Show information about chapters stored in the format.
+</p>
+<p>Each chapter is printed within a dedicated section with name &quot;CHAPTER&quot;.
+</p>
+</dd>
+<dt><samp class="option">-count_frames</samp></dt>
+<dd><p>Count the number of frames per stream and report it in the
+corresponding stream section.
+</p>
+</dd>
+<dt><samp class="option">-count_packets</samp></dt>
+<dd><p>Count the number of packets per stream and report it in the
+corresponding stream section.
+</p>
+</dd>
+<dt><samp class="option">-read_intervals <var class="var">read_intervals</var></samp></dt>
+<dd>
+<p>Read only the specified intervals. <var class="var">read_intervals</var> must be a
+sequence of interval specifications separated by &quot;,&quot;.
+<code class="command">ffprobe</code> will seek to the interval starting point, and will
+continue reading from that.
+</p>
+<p>Each interval is specified by two optional parts, separated by &quot;%&quot;.
+</p>
+<p>The first part specifies the interval start position. It is
+interpreted as an absolute position, or as a relative offset from the
+current position if it is preceded by the &quot;+&quot; character. If this first
+part is not specified, no seeking will be performed when reading this
+interval.
+</p>
+<p>The second part specifies the interval end position. It is interpreted
+as an absolute position, or as a relative offset from the current
+position if it is preceded by the &quot;+&quot; character. If the offset
+specification starts with &quot;#&quot;, it is interpreted as the number of
+packets to read (not including the flushing packets) from the interval
+start. If no second part is specified, the program will read until the
+end of the input.
+</p>
+<p>Note that seeking is not accurate, thus the actual interval start
+point may be different from the specified position. Also, when an
+interval duration is specified, the absolute end time will be computed
+by adding the duration to the interval start point found by seeking
+the file, rather than to the specified start value.
+</p>
+<p>The formal syntax is given by:
+</p><div class="example">
+<pre class="example-preformatted"><var class="var">INTERVAL</var>  ::= [<var class="var">START</var>|+<var class="var">START_OFFSET</var>][%[<var class="var">END</var>|+<var class="var">END_OFFSET</var>]]
+<var class="var">INTERVALS</var> ::= <var class="var">INTERVAL</var>[,<var class="var">INTERVALS</var>]
+</pre></div>
+
+<p>A few examples follow.
+</p><ul class="itemize mark-bullet">
+<li>Seek to time 10, read packets until 20 seconds after the found seek
+point, then seek to position <code class="code">01:30</code> (1 minute and thirty
+seconds) and read packets until position <code class="code">01:45</code>.
+<div class="example">
+<pre class="example-preformatted">10%+20,01:30%01:45
+</pre></div>
+
+</li><li>Read only 42 packets after seeking to position <code class="code">01:23</code>:
+<div class="example">
+<pre class="example-preformatted">01:23%+#42
+</pre></div>
+
+</li><li>Read only the first 20 seconds from the start:
+<div class="example">
+<pre class="example-preformatted">%+20
+</pre></div>
+
+</li><li>Read from the start until position <code class="code">02:30</code>:
+<div class="example">
+<pre class="example-preformatted">%02:30
+</pre></div>
+</li></ul>
+
+</dd>
+<dt><samp class="option">-show_private_data, -private</samp></dt>
+<dd><p>Show private data, that is data depending on the format of the
+particular shown element.
+This option is enabled by default, but you may need to disable it
+for specific uses, for example when creating XSD-compliant XML output.
+</p>
+</dd>
+<dt><samp class="option">-show_program_version</samp></dt>
+<dd><p>Show information related to program version.
+</p>
+<p>Version information is printed within a section with name
+&quot;PROGRAM_VERSION&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_library_versions</samp></dt>
+<dd><p>Show information related to library versions.
+</p>
+<p>Version information for each library is printed within a section with
+name &quot;LIBRARY_VERSION&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_versions</samp></dt>
+<dd><p>Show information related to program and library versions. This is the
+equivalent of setting both <samp class="option">-show_program_version</samp> and
+<samp class="option">-show_library_versions</samp> options.
+</p>
+</dd>
+<dt><samp class="option">-show_pixel_formats</samp></dt>
+<dd><p>Show information about all pixel formats supported by FFmpeg.
+</p>
+<p>Pixel format information for each format is printed within a section
+with name &quot;PIXEL_FORMAT&quot;.
+</p>
+</dd>
+<dt><samp class="option">-show_optional_fields <var class="var">value</var></samp></dt>
+<dd><p>Some writers viz. JSON and XML, omit the printing of fields with invalid or non-applicable values,
+while other writers always print them. This option enables one to control this behaviour.
+Valid values are <code class="code">always</code>/<code class="code">1</code>, <code class="code">never</code>/<code class="code">0</code> and <code class="code">auto</code>/<code class="code">-1</code>.
+Default is <var class="var">auto</var>.
+</p>
+</dd>
+<dt><samp class="option">-analyze_frames</samp></dt>
+<dd><p>Analyze frames and/or their side data up to the provided read interval,
+providing additional information that may be useful at a stream level.
+Must be paired with the <samp class="option">-show_streams</samp> option or it will have no effect.
+</p>
+<p>Currently, the additional fields provided by this option when enabled are the
+<code class="code">closed_captions</code> and <code class="code">film_grain</code> fields.
+</p>
+<p>For example, to analyze the first 20 seconds and populate these fields:
+</p><div class="example">
+<pre class="example-preformatted">ffprobe -show_streams -analyze_frames -read_intervals &quot;%+20&quot; INPUT
+</pre></div>
+
+</dd>
+<dt><samp class="option">-bitexact</samp></dt>
+<dd><p>Force bitexact output, useful to produce output which is not dependent
+on the specific build.
+</p>
+</dd>
+<dt><samp class="option">-i <var class="var">input_url</var></samp></dt>
+<dd><p>Read <var class="var">input_url</var>.
+</p>
+</dd>
+<dt><samp class="option">-o <var class="var">output_url</var></samp></dt>
+<dd><p>Write output to <var class="var">output_url</var>. If not specified, the output is sent
+to stdout.
+</p>
+</dd>
+</dl>
+
+<a name="Writers"></a>
+<h2 class="chapter">4 Writers<span class="pull-right"><a class="anchor hidden-xs" href="#Writers" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Writers" aria-hidden="true">TOC</a></span></h2>
+
+<p>A writer defines the output format adopted by <code class="command">ffprobe</code>, and will be
+used for printing all the parts of the output.
+</p>
+<p>A writer may accept one or more arguments, which specify the options
+to adopt. The options are specified as a list of <var class="var">key</var>=<var class="var">value</var>
+pairs, separated by &quot;:&quot;.
+</p>
+<p>All writers support the following options:
+</p>
+<dl class="table">
+<dt><samp class="option">string_validation, sv</samp></dt>
+<dd><p>Set string validation mode.
+</p>
+<p>The following values are accepted.
+</p><dl class="table">
+<dt>&lsquo;<samp class="samp">fail</samp>&rsquo;</dt>
+<dd><p>The writer will fail immediately in case an invalid string (UTF-8)
+sequence or code point is found in the input. This is especially
+useful to validate input metadata.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">ignore</samp>&rsquo;</dt>
+<dd><p>Any validation error will be ignored. This will result in possibly
+broken output, especially with the json or xml writer.
+</p>
+</dd>
+<dt>&lsquo;<samp class="samp">replace</samp>&rsquo;</dt>
+<dd><p>The writer will substitute invalid UTF-8 sequences or code points with
+the string specified with the <samp class="option">string_validation_replacement</samp>.
+</p></dd>
+</dl>
+
+<p>Default value is &lsquo;<samp class="samp">replace</samp>&rsquo;.
+</p>
+</dd>
+<dt><samp class="option">string_validation_replacement, svr</samp></dt>
+<dd><p>Set replacement string to use in case <samp class="option">string_validation</samp> is
+set to &lsquo;<samp class="samp">replace</samp>&rsquo;.
+</p>
+<p>In case the option is not specified, the writer will assume the empty
+string, that is it will remove the invalid sequences from the input
+strings.
+</p></dd>
+</dl>
+
+<p>A description of the currently available writers follows.
+</p>
+<a name="default"></a>
+<h3 class="section">4.1 default<span class="pull-right"><a class="anchor hidden-xs" href="#default" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-default" aria-hidden="true">TOC</a></span></h3>
+<p>Default format.
+</p>
+<p>Print each section in the form:
+</p><div class="example">
+<pre class="example-preformatted">[SECTION]
+key1=val1
+...
+keyN=valN
+[/SECTION]
+</pre></div>
+
+<p>Metadata tags are printed as a line in the corresponding FORMAT, STREAM,
+STREAM_GROUP_STREAM or PROGRAM_STREAM section, and are prefixed by the
+string &quot;TAG:&quot;.
+</p>
+<p>A description of the accepted options follows.
+</p>
+<dl class="table">
+<dt><samp class="option">nokey, nk</samp></dt>
+<dd><p>If set to 1 specify not to print the key of each field. Default value
+is 0.
+</p>
+</dd>
+<dt><samp class="option">noprint_wrappers, nw</samp></dt>
+<dd><p>If set to 1 specify not to print the section header and footer.
+Default value is 0.
+</p></dd>
+</dl>
+
+<a name="compact_002c-csv"></a>
+<h3 class="section">4.2 compact, csv<span class="pull-right"><a class="anchor hidden-xs" href="#compact_002c-csv" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-compact_002c-csv" aria-hidden="true">TOC</a></span></h3>
+<p>Compact and CSV format.
+</p>
+<p>The <code class="code">csv</code> writer is equivalent to <code class="code">compact</code>, but supports
+different defaults.
+</p>
+<p>Each section is printed on a single line.
+If no option is specified, the output has the form:
+</p><div class="example">
+<pre class="example-preformatted">section|key1=val1| ... |keyN=valN
+</pre></div>
+
+<p>Metadata tags are printed in the corresponding &quot;format&quot; or &quot;stream&quot;
+section. A metadata tag key, if printed, is prefixed by the string
+&quot;tag:&quot;.
+</p>
+<p>The description of the accepted options follows.
+</p>
+<dl class="table">
+<dt><samp class="option">item_sep, s</samp></dt>
+<dd><p>Specify the character to use for separating fields in the output line.
+It must be a single printable character, it is &quot;|&quot; by default (&quot;,&quot; for
+the <code class="code">csv</code> writer).
+</p>
+</dd>
+<dt><samp class="option">nokey, nk</samp></dt>
+<dd><p>If set to 1 specify not to print the key of each field. Its default
+value is 0 (1 for the <code class="code">csv</code> writer).
+</p>
+</dd>
+<dt><samp class="option">escape, e</samp></dt>
+<dd><p>Set the escape mode to use, default to &quot;c&quot; (&quot;csv&quot; for the <code class="code">csv</code>
+writer).
+</p>
+<p>It can assume one of the following values:
+</p><dl class="table">
+<dt><samp class="option">c</samp></dt>
+<dd><p>Perform C-like escaping. Strings containing a newline (&lsquo;<samp class="samp">\n</samp>&rsquo;), carriage
+return (&lsquo;<samp class="samp">\r</samp>&rsquo;), a tab (&lsquo;<samp class="samp">\t</samp>&rsquo;), a form feed (&lsquo;<samp class="samp">\f</samp>&rsquo;), the escaping
+character (&lsquo;<samp class="samp">\</samp>&rsquo;) or the item separator character <var class="var">SEP</var> are escaped
+using C-like fashioned escaping, so that a newline is converted to the
+sequence &lsquo;<samp class="samp">\n</samp>&rsquo;, a carriage return to &lsquo;<samp class="samp">\r</samp>&rsquo;, &lsquo;<samp class="samp">\</samp>&rsquo; to &lsquo;<samp class="samp">\\</samp>&rsquo; and
+the separator <var class="var">SEP</var> is converted to &lsquo;<samp class="samp">\<var class="var">SEP</var></samp>&rsquo;.
+</p>
+</dd>
+<dt><samp class="option">csv</samp></dt>
+<dd><p>Perform CSV-like escaping, as described in RFC4180.  Strings
+containing a newline (&lsquo;<samp class="samp">\n</samp>&rsquo;), a carriage return (&lsquo;<samp class="samp">\r</samp>&rsquo;), a double quote
+(&lsquo;<samp class="samp">&quot;</samp>&rsquo;), or <var class="var">SEP</var> are enclosed in double-quotes.
+</p>
+</dd>
+<dt><samp class="option">none</samp></dt>
+<dd><p>Perform no escaping.
+</p></dd>
+</dl>
+
+</dd>
+<dt><samp class="option">print_section, p</samp></dt>
+<dd><p>Print the section name at the beginning of each line if the value is
+<code class="code">1</code>, disable it with value set to <code class="code">0</code>. Default value is
+<code class="code">1</code>.
+</p>
+</dd>
+</dl>
+
+<a name="flat"></a>
+<h3 class="section">4.3 flat<span class="pull-right"><a class="anchor hidden-xs" href="#flat" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-flat" aria-hidden="true">TOC</a></span></h3>
+<p>Flat format.
+</p>
+<p>A free-form output where each line contains an explicit key=value, such as
+&quot;streams.stream.3.tags.foo=bar&quot;. The output is shell escaped, so it can be
+directly embedded in sh scripts as long as the separator character is an
+alphanumeric character or an underscore (see <var class="var">sep_char</var> option).
+</p>
+<p>The description of the accepted options follows.
+</p>
+<dl class="table">
+<dt><samp class="option">sep_char, s</samp></dt>
+<dd><p>Separator character used to separate the chapter, the section name, IDs and
+potential tags in the printed field key.
+</p>
+<p>Default value is &lsquo;<samp class="samp">.</samp>&rsquo;.
+</p>
+</dd>
+<dt><samp class="option">hierarchical, h</samp></dt>
+<dd><p>Specify if the section name specification should be hierarchical. If
+set to 1, and if there is more than one section in the current
+chapter, the section name will be prefixed by the name of the
+chapter. A value of 0 will disable this behavior.
+</p>
+<p>Default value is 1.
+</p></dd>
+</dl>
+
+<a name="ini"></a>
+<h3 class="section">4.4 ini<span class="pull-right"><a class="anchor hidden-xs" href="#ini" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-ini" aria-hidden="true">TOC</a></span></h3>
+<p>INI format output.
+</p>
+<p>Print output in an INI based format.
+</p>
+<p>The following conventions are adopted:
+</p>
+<ul class="itemize mark-bullet">
+<li>all key and values are UTF-8
+</li><li>&lsquo;<samp class="samp">.</samp>&rsquo; is the subgroup separator
+</li><li>newline, &lsquo;<samp class="samp">\t</samp>&rsquo;, &lsquo;<samp class="samp">\f</samp>&rsquo;, &lsquo;<samp class="samp">\b</samp>&rsquo; and the following characters are
+escaped
+</li><li>&lsquo;<samp class="samp">\</samp>&rsquo; is the escape character
+</li><li>&lsquo;<samp class="samp">#</samp>&rsquo; is the comment indicator
+</li><li>&lsquo;<samp class="samp">=</samp>&rsquo; is the key/value separator
+</li><li>&lsquo;<samp class="samp">:</samp>&rsquo; is not used but usually parsed as key/value separator
+</li></ul>
+
+<p>This writer accepts options as a list of <var class="var">key</var>=<var class="var">value</var> pairs,
+separated by &lsquo;<samp class="samp">:</samp>&rsquo;.
+</p>
+<p>The description of the accepted options follows.
+</p>
+<dl class="table">
+<dt><samp class="option">hierarchical, h</samp></dt>
+<dd><p>Specify if the section name specification should be hierarchical. If
+set to 1, and if there is more than one section in the current
+chapter, the section name will be prefixed by the name of the
+chapter. A value of 0 will disable this behavior.
+</p>
+<p>Default value is 1.
+</p></dd>
+</dl>
+
+<a name="json"></a>
+<h3 class="section">4.5 json<span class="pull-right"><a class="anchor hidden-xs" href="#json" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-json" aria-hidden="true">TOC</a></span></h3>
+<p>JSON based format.
+</p>
+<p>Each section is printed using JSON notation.
+</p>
+<p>The description of the accepted options follows.
+</p>
+<dl class="table">
+<dt><samp class="option">compact, c</samp></dt>
+<dd><p>If set to 1 enable compact output, that is each section will be
+printed on a single line. Default value is 0.
+</p></dd>
+</dl>
+
+<p>For more information about JSON, see <a class="url" href="http://www.json.org/">http://www.json.org/</a>.
+</p>
+<a name="xml"></a>
+<h3 class="section">4.6 xml<span class="pull-right"><a class="anchor hidden-xs" href="#xml" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-xml" aria-hidden="true">TOC</a></span></h3>
+<p>XML based format.
+</p>
+<p>The XML output is described in the XML schema description file
+<samp class="file">ffprobe.xsd</samp> installed in the FFmpeg datadir.
+</p>
+<p>An updated version of the schema can be retrieved at the url
+<a class="url" href="http://www.ffmpeg.org/schema/ffprobe.xsd">http://www.ffmpeg.org/schema/ffprobe.xsd</a>, which redirects to the
+latest schema committed into the FFmpeg development source code tree.
+</p>
+<p>Note that the output issued will be compliant to the
+<samp class="file">ffprobe.xsd</samp> schema only when no special global output options
+(<samp class="option">unit</samp>, <samp class="option">prefix</samp>, <samp class="option">byte_binary_prefix</samp>,
+<samp class="option">sexagesimal</samp> etc.) are specified.
+</p>
+<p>The description of the accepted options follows.
+</p>
+<dl class="table">
+<dt><samp class="option">fully_qualified, q</samp></dt>
+<dd><p>If set to 1 specify if the output should be fully qualified. Default
+value is 0.
+This is required for generating an XML file which can be validated
+through an XSD file.
+</p>
+</dd>
+<dt><samp class="option">xsd_strict, x</samp></dt>
+<dd><p>If set to 1 perform more checks for ensuring that the output is XSD
+compliant. Default value is 0.
+This option automatically sets <samp class="option">fully_qualified</samp> to 1.
+</p></dd>
+</dl>
+
+<p>For more information about the XML format, see
+<a class="url" href="https://www.w3.org/XML/">https://www.w3.org/XML/</a>.
+</p>
+<a name="Timecode"></a>
+<h2 class="chapter">5 Timecode<span class="pull-right"><a class="anchor hidden-xs" href="#Timecode" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Timecode" aria-hidden="true">TOC</a></span></h2>
+
+<p><code class="command">ffprobe</code> supports Timecode extraction:
+</p>
+<ul class="itemize mark-bullet">
+<li>MPEG1/2 timecode is extracted from the GOP, and is available in the video
+stream details (<samp class="option">-show_streams</samp>, see <var class="var">timecode</var>).
+
+</li><li>MOV timecode is extracted from tmcd track, so is available in the tmcd
+stream metadata (<samp class="option">-show_streams</samp>, see <var class="var">TAG:timecode</var>).
+
+</li><li>DV, GXF and AVI timecodes are available in format metadata
+(<samp class="option">-show_format</samp>, see <var class="var">TAG:timecode</var>).
+
+</li></ul>
+
+
+<a name="See-Also"></a>
+<h2 class="chapter">6 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffprobe-all.html">ffprobe-all</a>,
+<a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>,
+<a class="url" href="ffmpeg-utils.html">ffmpeg-utils</a>,
+<a class="url" href="ffmpeg-scaler.html">ffmpeg-scaler</a>,
+<a class="url" href="ffmpeg-resampler.html">ffmpeg-resampler</a>,
+<a class="url" href="ffmpeg-codecs.html">ffmpeg-codecs</a>,
+<a class="url" href="ffmpeg-bitstream-filters.html">ffmpeg-bitstream-filters</a>,
+<a class="url" href="ffmpeg-formats.html">ffmpeg-formats</a>,
+<a class="url" href="ffmpeg-devices.html">ffmpeg-devices</a>,
+<a class="url" href="ffmpeg-protocols.html">ffmpeg-protocols</a>,
+<a class="url" href="ffmpeg-filters.html">ffmpeg-filters</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">7 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/git-howto.html

@@ -0,0 +1,562 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Using Git to develop FFmpeg
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Using Git to develop FFmpeg
+      </h1>
+
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Introduction" href="#Introduction">1 Introduction</a></li>
+  <li><a id="toc-Basics-Usage" href="#Basics-Usage">2 Basics Usage</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Get-Git" href="#Get-Git">2.1 Get Git</a></li>
+    <li><a id="toc-Cloning-the-source-tree" href="#Cloning-the-source-tree">2.2 Cloning the source tree</a></li>
+    <li><a id="toc-Updating-the-source-tree-to-the-latest-revision-1" href="#Updating-the-source-tree-to-the-latest-revision-1">2.3 Updating the source tree to the latest revision</a></li>
+    <li><a id="toc-Rebasing-your-local-branches" href="#Rebasing-your-local-branches">2.4 Rebasing your local branches</a></li>
+    <li><a id="toc-Adding_002fremoving-files_002fdirectories" href="#Adding_002fremoving-files_002fdirectories">2.5 Adding/removing files/directories</a></li>
+    <li><a id="toc-Showing-modifications" href="#Showing-modifications">2.6 Showing modifications</a></li>
+    <li><a id="toc-Inspecting-the-changelog" href="#Inspecting-the-changelog">2.7 Inspecting the changelog</a></li>
+    <li><a id="toc-Checking-source-tree-status" href="#Checking-source-tree-status">2.8 Checking source tree status</a></li>
+    <li><a id="toc-Committing" href="#Committing">2.9 Committing</a></li>
+    <li><a id="toc-Writing-a-commit-message" href="#Writing-a-commit-message">2.10 Writing a commit message</a></li>
+    <li><a id="toc-Preparing-a-patchset" href="#Preparing-a-patchset">2.11 Preparing a patchset</a></li>
+    <li><a id="toc-Sending-patches-for-review" href="#Sending-patches-for-review">2.12 Sending patches for review</a></li>
+    <li><a id="toc-Renaming_002fmoving_002fcopying-files-or-contents-of-files" href="#Renaming_002fmoving_002fcopying-files-or-contents-of-files">2.13 Renaming/moving/copying files or contents of files</a></li>
+  </ul></li>
+  <li><a id="toc-Git-configuration" href="#Git-configuration">3 Git configuration</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Personal-Git-installation" href="#Personal-Git-installation">3.1 Personal Git installation</a></li>
+    <li><a id="toc-Repository-configuration" href="#Repository-configuration">3.2 Repository configuration</a></li>
+  </ul></li>
+  <li><a id="toc-FFmpeg-specific" href="#FFmpeg-specific">4 FFmpeg specific</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Reverting-broken-commits" href="#Reverting-broken-commits">4.1 Reverting broken commits</a></li>
+    <li><a id="toc-Pushing-changes-to-remote-trees" href="#Pushing-changes-to-remote-trees">4.2 Pushing changes to remote trees</a></li>
+    <li><a id="toc-Finding-a-specific-svn-revision" href="#Finding-a-specific-svn-revision">4.3 Finding a specific svn revision</a></li>
+  </ul></li>
+  <li><a id="toc-gpg-key-generation" href="#gpg-key-generation">5 gpg key generation</a></li>
+  <li><a id="toc-Pre_002dpush-checklist" href="#Pre_002dpush-checklist">6 Pre-push checklist</a></li>
+  <li><a id="toc-Server-Issues" href="#Server-Issues">7 Server Issues</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Introduction"></a>
+<h2 class="chapter">1 Introduction<span class="pull-right"><a class="anchor hidden-xs" href="#Introduction" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Introduction" aria-hidden="true">TOC</a></span></h2>
+
+<p>This document aims in giving some quick references on a set of useful Git
+commands. You should always use the extensive and detailed documentation
+provided directly by Git:
+</p>
+<div class="example">
+<pre class="example-preformatted">git --help
+man git
+</pre></div>
+
+<p>shows you the available subcommands,
+</p>
+<div class="example">
+<pre class="example-preformatted">git &lt;command&gt; --help
+man git-&lt;command&gt;
+</pre></div>
+
+<p>shows information about the subcommand &lt;command&gt;.
+</p>
+<p>Additional information could be found on the
+<a class="url" href="http://gitref.org">Git Reference</a> website.
+</p>
+<p>For more information about the Git project, visit the
+<a class="url" href="http://git-scm.com/">Git website</a>.
+</p>
+<p>Consult these resources whenever you have problems, they are quite exhaustive.
+</p>
+<p>What follows now is a basic introduction to Git and some FFmpeg-specific
+guidelines to ease the contribution to the project.
+</p>
+<a name="Basics-Usage"></a>
+<h2 class="chapter">2 Basics Usage<span class="pull-right"><a class="anchor hidden-xs" href="#Basics-Usage" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Basics-Usage" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Get-Git"></a>
+<h3 class="section">2.1 Get Git<span class="pull-right"><a class="anchor hidden-xs" href="#Get-Git" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Get-Git" aria-hidden="true">TOC</a></span></h3>
+
+<p>You can get Git from <a class="url" href="http://git-scm.com/">http://git-scm.com/</a>
+Most distribution and operating system provide a package for it.
+</p>
+
+<a name="Cloning-the-source-tree"></a>
+<h3 class="section">2.2 Cloning the source tree<span class="pull-right"><a class="anchor hidden-xs" href="#Cloning-the-source-tree" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Cloning-the-source-tree" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git clone https://git.ffmpeg.org/ffmpeg.git &lt;target&gt;
+</pre></div>
+
+<p>This will put the FFmpeg sources into the directory <var class="var">&lt;target&gt;</var>.
+</p>
+<div class="example">
+<pre class="example-preformatted">git clone git@source.ffmpeg.org:ffmpeg &lt;target&gt;
+</pre></div>
+
+<p>This will put the FFmpeg sources into the directory <var class="var">&lt;target&gt;</var> and let
+you push back your changes to the remote repository.
+</p>
+<div class="example">
+<pre class="example-preformatted">git clone git@ffmpeg.org:ffmpeg-web &lt;target&gt;
+</pre></div>
+
+<p>This will put the source of the FFmpeg website into the directory
+<var class="var">&lt;target&gt;</var> and let you push back your changes to the remote repository.
+</p>
+<p>If you don&rsquo;t have write-access to the ffmpeg-web repository, you can
+create patches after making a read-only ffmpeg-web clone:
+</p>
+<div class="example">
+<pre class="example-preformatted">git clone git://ffmpeg.org/ffmpeg-web &lt;target&gt;
+</pre></div>
+
+<p>Make sure that you do not have Windows line endings in your checkouts,
+otherwise you may experience spurious compilation failures. One way to
+achieve this is to run
+</p>
+<div class="example">
+<pre class="example-preformatted">git config --global core.autocrlf false
+</pre></div>
+
+
+<a class="anchor" id="Updating-the-source-tree-to-the-latest-revision"></a><a name="Updating-the-source-tree-to-the-latest-revision-1"></a>
+<h3 class="section">2.3 Updating the source tree to the latest revision<span class="pull-right"><a class="anchor hidden-xs" href="#Updating-the-source-tree-to-the-latest-revision-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Updating-the-source-tree-to-the-latest-revision-1" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git pull (--rebase)
+</pre></div>
+
+<p>pulls in the latest changes from the tracked branch. The tracked branch
+can be remote. By default the master branch tracks the branch master in
+the remote origin.
+</p>
+<div class="warning">
+<p><code class="command">--rebase</code> (see below) is recommended.
+</p></div>
+<a name="Rebasing-your-local-branches"></a>
+<h3 class="section">2.4 Rebasing your local branches<span class="pull-right"><a class="anchor hidden-xs" href="#Rebasing-your-local-branches" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Rebasing-your-local-branches" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git pull --rebase
+</pre></div>
+
+<p>fetches the changes from the main repository and replays your local commits
+over it. This is required to keep all your local changes at the top of
+FFmpeg&rsquo;s master tree. The master tree will reject pushes with merge commits.
+</p>
+
+<a name="Adding_002fremoving-files_002fdirectories"></a>
+<h3 class="section">2.5 Adding/removing files/directories<span class="pull-right"><a class="anchor hidden-xs" href="#Adding_002fremoving-files_002fdirectories" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Adding_002fremoving-files_002fdirectories" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git add [-A] &lt;filename/dirname&gt;
+git rm [-r] &lt;filename/dirname&gt;
+</pre></div>
+
+<p>Git needs to get notified of all changes you make to your working
+directory that makes files appear or disappear.
+Line moves across files are automatically tracked.
+</p>
+
+<a name="Showing-modifications"></a>
+<h3 class="section">2.6 Showing modifications<span class="pull-right"><a class="anchor hidden-xs" href="#Showing-modifications" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Showing-modifications" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git diff &lt;filename(s)&gt;
+</pre></div>
+
+<p>will show all local modifications in your working directory as unified diff.
+</p>
+
+<a name="Inspecting-the-changelog"></a>
+<h3 class="section">2.7 Inspecting the changelog<span class="pull-right"><a class="anchor hidden-xs" href="#Inspecting-the-changelog" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Inspecting-the-changelog" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git log &lt;filename(s)&gt;
+</pre></div>
+
+<p>You may also use the graphical tools like <code class="command">gitview</code> or <code class="command">gitk</code>
+or the web interface available at <a class="url" href="https://git.ffmpeg.org/ffmpeg.git">https://git.ffmpeg.org/ffmpeg.git</a>.
+</p>
+<a name="Checking-source-tree-status"></a>
+<h3 class="section">2.8 Checking source tree status<span class="pull-right"><a class="anchor hidden-xs" href="#Checking-source-tree-status" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Checking-source-tree-status" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git status
+</pre></div>
+
+<p>detects all the changes you made and lists what actions will be taken in case
+of a commit (additions, modifications, deletions, etc.).
+</p>
+
+<a name="Committing"></a>
+<h3 class="section">2.9 Committing<span class="pull-right"><a class="anchor hidden-xs" href="#Committing" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Committing" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git diff --check
+</pre></div>
+
+<p>to double check your changes before committing them to avoid trouble later
+on. All experienced developers do this on each and every commit, no matter
+how small.
+</p>
+<p>Every one of them has been saved from looking like a fool by this many times.
+It&rsquo;s very easy for stray debug output or cosmetic modifications to slip in,
+please avoid problems through this extra level of scrutiny.
+</p>
+<p>For cosmetics-only commits you should get (almost) empty output from
+</p>
+<div class="example">
+<pre class="example-preformatted">git diff -w -b &lt;filename(s)&gt;
+</pre></div>
+
+<p>Also check the output of
+</p>
+<div class="example">
+<pre class="example-preformatted">git status
+</pre></div>
+
+<p>to make sure you don&rsquo;t have untracked files or deletions.
+</p>
+<div class="example">
+<pre class="example-preformatted">git add [-i|-p|-A] &lt;filenames/dirnames&gt;
+</pre></div>
+
+<p>Make sure you have told Git your name, email address and GPG key
+</p>
+<div class="example">
+<pre class="example-preformatted">git config --global user.name &quot;My Name&quot;
+git config --global user.email my@email.invalid
+git config --global user.signingkey ABCDEF0123245
+</pre></div>
+
+<p>Enable signing all commits or use -S
+</p>
+<div class="example">
+<pre class="example-preformatted">git config --global commit.gpgsign true
+</pre></div>
+
+<p>Use <samp class="option">--global</samp> to set the global configuration for all your Git checkouts.
+</p>
+<p>Git will select the changes to the files for commit. Optionally you can use
+the interactive or the patch mode to select hunk by hunk what should be
+added to the commit.
+</p>
+
+<div class="example">
+<pre class="example-preformatted">git commit
+</pre></div>
+
+<p>Git will commit the selected changes to your current local branch.
+</p>
+<p>You will be prompted for a log message in an editor, which is either
+set in your personal configuration file through
+</p>
+<div class="example">
+<pre class="example-preformatted">git config --global core.editor
+</pre></div>
+
+<p>or set by one of the following environment variables:
+<var class="var">GIT_EDITOR</var>, <var class="var">VISUAL</var> or <var class="var">EDITOR</var>.
+</p>
+<a name="Writing-a-commit-message"></a>
+<h3 class="section">2.10 Writing a commit message<span class="pull-right"><a class="anchor hidden-xs" href="#Writing-a-commit-message" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Writing-a-commit-message" aria-hidden="true">TOC</a></span></h3>
+
+<p>Log messages should be concise but descriptive.
+</p>
+<p>The first line must contain the context, a colon and a very short
+summary of what the commit does. Details can be added, if necessary,
+separated by an empty line. These details should not exceed 60-72 characters
+per line, except when containing code.
+</p>
+<p>Example of a good commit message:
+</p>
+<div class="example">
+<pre class="example-preformatted">avcodec/cbs: add a helper to read extradata within packet side data
+
+Using ff_cbs_read() on the raw buffer will not parse it as extradata,
+resulting in parsing errors for example when handling ISOBMFF avcC.
+This helper works around that.
+</pre></div>
+
+<div class="example">
+<pre class="example-preformatted">ptr might be NULL
+</pre></div>
+
+<p>If the summary on the first line is not enough, in the body of the message,
+explain why you made a change, what you did will be obvious from the changes
+themselves most of the time. Saying just &quot;bug fix&quot; or &quot;10l&quot; is bad. Remember
+that people of varying skill levels look at and educate themselves while
+reading through your code. Don&rsquo;t include filenames in log messages except in
+the context, Git provides that information.
+</p>
+<p>If the commit fixes a registered issue, state it in a separate line of the
+body: <code class="code">Fix Trac ticket #42.</code>
+</p>
+<p>The first line will be used to name
+the patch by <code class="command">git format-patch</code>.
+</p>
+<p>Common mistakes for the first line, as seen in <code class="command">git log --oneline</code>
+include: missing context at the beginning; description of what the code did
+before the patch; line too long or wrapped to the second line.
+</p>
+<a name="Preparing-a-patchset"></a>
+<h3 class="section">2.11 Preparing a patchset<span class="pull-right"><a class="anchor hidden-xs" href="#Preparing-a-patchset" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Preparing-a-patchset" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git format-patch &lt;commit&gt; [-o directory]
+</pre></div>
+
+<p>will generate a set of patches for each commit between <var class="var">&lt;commit&gt;</var> and
+current <var class="var">HEAD</var>. E.g.
+</p>
+<div class="example">
+<pre class="example-preformatted">git format-patch origin/master
+</pre></div>
+
+<p>will generate patches for all commits on current branch which are not
+present in upstream.
+A useful shortcut is also
+</p>
+<div class="example">
+<pre class="example-preformatted">git format-patch -n
+</pre></div>
+
+<p>which will generate patches from last <var class="var">n</var> commits.
+By default the patches are created in the current directory.
+</p>
+<a name="Sending-patches-for-review"></a>
+<h3 class="section">2.12 Sending patches for review<span class="pull-right"><a class="anchor hidden-xs" href="#Sending-patches-for-review" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Sending-patches-for-review" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git send-email &lt;commit list|directory&gt;
+</pre></div>
+
+<p>will send the patches created by <code class="command">git format-patch</code> or directly
+generates them. All the email fields can be configured in the global/local
+configuration or overridden by command line.
+Note that this tool must often be installed separately (e.g. <var class="var">git-email</var>
+package on Debian-based distros).
+</p>
+
+<a name="Renaming_002fmoving_002fcopying-files-or-contents-of-files"></a>
+<h3 class="section">2.13 Renaming/moving/copying files or contents of files<span class="pull-right"><a class="anchor hidden-xs" href="#Renaming_002fmoving_002fcopying-files-or-contents-of-files" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Renaming_002fmoving_002fcopying-files-or-contents-of-files" aria-hidden="true">TOC</a></span></h3>
+
+<p>Git automatically tracks such changes, making those normal commits.
+</p>
+<div class="example">
+<pre class="example-preformatted">mv/cp path/file otherpath/otherfile
+git add [-A] .
+git commit
+</pre></div>
+
+
+<a name="Git-configuration"></a>
+<h2 class="chapter">3 Git configuration<span class="pull-right"><a class="anchor hidden-xs" href="#Git-configuration" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Git-configuration" aria-hidden="true">TOC</a></span></h2>
+
+<p>In order to simplify a few workflows, it is advisable to configure both
+your personal Git installation and your local FFmpeg repository.
+</p>
+<a name="Personal-Git-installation"></a>
+<h3 class="section">3.1 Personal Git installation<span class="pull-right"><a class="anchor hidden-xs" href="#Personal-Git-installation" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Personal-Git-installation" aria-hidden="true">TOC</a></span></h3>
+
+<p>Add the following to your <samp class="file">~/.gitconfig</samp> to help <code class="command">git send-email</code>
+and <code class="command">git format-patch</code> detect renames:
+</p>
+<div class="example">
+<pre class="example-preformatted">[diff]
+        renames = copy
+</pre></div>
+
+<a name="Repository-configuration"></a>
+<h3 class="section">3.2 Repository configuration<span class="pull-right"><a class="anchor hidden-xs" href="#Repository-configuration" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Repository-configuration" aria-hidden="true">TOC</a></span></h3>
+
+<p>In order to have <code class="command">git send-email</code> automatically send patches
+to the ffmpeg-devel mailing list, add the following stanza
+to <samp class="file">/path/to/ffmpeg/repository/.git/config</samp>:
+</p>
+<div class="example">
+<pre class="example-preformatted">[sendemail]
+        to = ffmpeg-devel@ffmpeg.org
+</pre></div>
+
+<a name="FFmpeg-specific"></a>
+<h2 class="chapter">4 FFmpeg specific<span class="pull-right"><a class="anchor hidden-xs" href="#FFmpeg-specific" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-FFmpeg-specific" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Reverting-broken-commits"></a>
+<h3 class="section">4.1 Reverting broken commits<span class="pull-right"><a class="anchor hidden-xs" href="#Reverting-broken-commits" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Reverting-broken-commits" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git reset &lt;commit&gt;
+</pre></div>
+
+<p><code class="command">git reset</code> will uncommit the changes till <var class="var">&lt;commit&gt;</var> rewriting
+the current branch history.
+</p>
+<div class="example">
+<pre class="example-preformatted">git commit --amend
+</pre></div>
+
+<p>allows one to amend the last commit details quickly.
+</p>
+<div class="example">
+<pre class="example-preformatted">git rebase -i origin/master
+</pre></div>
+
+<p>will replay local commits over the main repository allowing to edit, merge
+or remove some of them in the process.
+</p>
+<div class="info">
+<p><code class="command">git reset</code>, <code class="command">git commit --amend</code> and <code class="command">git rebase</code>
+rewrite history, so you should use them ONLY on your local or topic branches.
+The main repository will reject those changes.
+</p></div>
+<div class="example">
+<pre class="example-preformatted">git revert &lt;commit&gt;
+</pre></div>
+
+<p><code class="command">git revert</code> will generate a revert commit. This will not make the
+faulty commit disappear from the history.
+</p>
+<a name="Pushing-changes-to-remote-trees"></a>
+<h3 class="section">4.2 Pushing changes to remote trees<span class="pull-right"><a class="anchor hidden-xs" href="#Pushing-changes-to-remote-trees" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Pushing-changes-to-remote-trees" aria-hidden="true">TOC</a></span></h3>
+
+<div class="example">
+<pre class="example-preformatted">git push origin master --dry-run
+</pre></div>
+
+<p>Will simulate a push of the local master branch to the default remote
+(<var class="var">origin</var>). And list which branches and ranges or commits would have been
+pushed.
+Git will prevent you from pushing changes if the local and remote trees are
+out of sync. Refer to <a class="ref" href="#Updating-the-source-tree-to-the-latest-revision">Updating the source tree to the latest revision</a>.
+</p>
+<div class="example">
+<pre class="example-preformatted">git remote add &lt;name&gt; &lt;url&gt;
+</pre></div>
+
+<p>Will add additional remote with a name reference, it is useful if you want
+to push your local branch for review on a remote host.
+</p>
+<div class="example">
+<pre class="example-preformatted">git push &lt;remote&gt; &lt;refspec&gt;
+</pre></div>
+
+<p>Will push the changes to the <var class="var">&lt;remote&gt;</var> repository.
+Omitting <var class="var">&lt;refspec&gt;</var> makes <code class="command">git push</code> update all the remote
+branches matching the local ones.
+</p>
+<a name="Finding-a-specific-svn-revision"></a>
+<h3 class="section">4.3 Finding a specific svn revision<span class="pull-right"><a class="anchor hidden-xs" href="#Finding-a-specific-svn-revision" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Finding-a-specific-svn-revision" aria-hidden="true">TOC</a></span></h3>
+
+<p>Since version 1.7.1 Git supports &lsquo;<samp class="samp">:/foo</samp>&rsquo; syntax for specifying commits
+based on a regular expression. see man gitrevisions
+</p>
+<div class="example">
+<pre class="example-preformatted">git show :/'as revision 23456'
+</pre></div>
+
+<p>will show the svn changeset &lsquo;<samp class="samp">r23456</samp>&rsquo;. With older Git versions searching in
+the <code class="command">git log</code> output is the easiest option (especially if a pager with
+search capabilities is used).
+</p>
+<p>This commit can be checked out with
+</p>
+<div class="example">
+<pre class="example-preformatted">git checkout -b svn_23456 :/'as revision 23456'
+</pre></div>
+
+<p>or for Git &lt; 1.7.1 with
+</p>
+<div class="example">
+<pre class="example-preformatted">git checkout -b svn_23456 $SHA1
+</pre></div>
+
+<p>where <var class="var">$SHA1</var> is the commit hash from the <code class="command">git log</code> output.
+</p>
+
+<a name="gpg-key-generation"></a>
+<h2 class="chapter">5 gpg key generation<span class="pull-right"><a class="anchor hidden-xs" href="#gpg-key-generation" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-gpg-key-generation" aria-hidden="true">TOC</a></span></h2>
+
+<p>If you have no gpg key yet, we recommend that you create a ed25519 based key as it
+is small, fast and secure. Especially it results in small signatures in git.
+</p>
+<div class="example">
+<pre class="example-preformatted">gpg --default-new-key-algo &quot;ed25519/cert,sign+cv25519/encr&quot; --quick-generate-key &quot;human@server.com&quot;
+</pre></div>
+
+<p>When generating a key, make sure the email specified matches the email used in git as some sites like
+github consider mismatches a reason to declare such commits unverified. After generating a key you
+can add it to the MAINTAINER file and upload it to a keyserver.
+</p>
+<a name="Pre_002dpush-checklist"></a>
+<h2 class="chapter">6 Pre-push checklist<span class="pull-right"><a class="anchor hidden-xs" href="#Pre_002dpush-checklist" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Pre_002dpush-checklist" aria-hidden="true">TOC</a></span></h2>
+
+<p>Once you have a set of commits that you feel are ready for pushing,
+work through the following checklist to doublecheck everything is in
+proper order. This list tries to be exhaustive. In case you are just
+pushing a typo in a comment, some of the steps may be unnecessary.
+Apply your common sense, but if in doubt, err on the side of caution.
+</p>
+<p>First, make sure that the commits and branches you are going to push
+match what you want pushed and that nothing is missing, extraneous or
+wrong. You can see what will be pushed by running the git push command
+with <samp class="option">--dry-run</samp> first. And then inspecting the commits listed with
+<code class="command">git log -p 1234567..987654</code>. The <code class="command">git status</code> command
+may help in finding local changes that have been forgotten to be added.
+</p>
+<p>Next let the code pass through a full run of our test suite.
+</p>
+<ul class="itemize mark-bullet">
+<li><code class="command">make distclean</code>
+</li><li><code class="command">/path/to/ffmpeg/configure</code>
+</li><li><code class="command">make fate</code>
+</li><li>if fate fails due to missing samples run <code class="command">make fate-rsync</code> and retry
+</li></ul>
+
+<p>Make sure all your changes have been checked before pushing them, the
+test suite only checks against regressions and that only to some extend. It does
+obviously not check newly added features/code to be working unless you have
+added a test for that (which is recommended).
+</p>
+<p>Also note that every single commit should pass the test suite, not just
+the result of a series of patches.
+</p>
+<p>Once everything passed, push the changes to your public ffmpeg clone and post a
+merge request to ffmpeg-devel. You can also push them directly but this is not
+recommended.
+</p>
+<a name="Server-Issues"></a>
+<h2 class="chapter">7 Server Issues<span class="pull-right"><a class="anchor hidden-xs" href="#Server-Issues" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Server-Issues" aria-hidden="true">TOC</a></span></h2>
+
+<p>Contact the project admins at <a class="email" href="mailto:root@ffmpeg.org">root@ffmpeg.org</a> if you have technical
+problems with the Git server.
+</p>      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/libavcodec.html

@@ -0,0 +1,74 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Libavcodec Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Libavcodec Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">2 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">3 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>The libavcodec library provides a generic encoding/decoding framework
+and contains multiple decoders and encoders for audio, video and
+subtitle streams, and several bitstream filters.
+</p>
+<p>The shared architecture provides various services ranging from bit
+stream I/O to DSP optimizations, and makes it suitable for
+implementing robust and fast codecs as well as for experimentation.
+</p>
+
+<a name="See-Also"></a>
+<h2 class="chapter">2 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="ffmpeg-codecs.html">ffmpeg-codecs</a>, <a class="url" href="ffmpeg-bitstream-filters.html">bitstream-filters</a>,
+<a class="url" href="libavutil.html">libavutil</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">3 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/libavdevice.html

@@ -0,0 +1,71 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Libavdevice Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Libavdevice Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">2 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">3 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>The libavdevice library provides a generic framework for grabbing from
+and rendering to many common multimedia input/output devices, and
+supports several input and output devices, including Video4Linux2,
+VfW, DShow, and ALSA.
+</p>
+
+<a name="See-Also"></a>
+<h2 class="chapter">2 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="ffmpeg-devices.html">ffmpeg-devices</a>,
+<a class="url" href="libavutil.html">libavutil</a>, <a class="url" href="libavcodec.html">libavcodec</a>, <a class="url" href="libavformat.html">libavformat</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">3 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/libavfilter.html

@@ -0,0 +1,70 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Libavfilter Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Libavfilter Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">2 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">3 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>The libavfilter library provides a generic audio/video filtering
+framework containing several filters, sources and sinks.
+</p>
+
+<a name="See-Also"></a>
+<h2 class="chapter">2 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="ffmpeg-filters.html">ffmpeg-filters</a>,
+<a class="url" href="libavutil.html">libavutil</a>, <a class="url" href="libswscale.html">libswscale</a>, <a class="url" href="libswresample.html">libswresample</a>,
+<a class="url" href="libavcodec.html">libavcodec</a>, <a class="url" href="libavformat.html">libavformat</a>, <a class="url" href="libavdevice.html">libavdevice</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">3 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/libavformat.html

@@ -0,0 +1,74 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Libavformat Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Libavformat Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">2 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">3 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>The libavformat library provides a generic framework for multiplexing
+and demultiplexing (muxing and demuxing) audio, video and subtitle
+streams. It encompasses multiple muxers and demuxers for multimedia
+container formats.
+</p>
+<p>It also supports several input and output protocols to access a media
+resource.
+</p>
+
+<a name="See-Also"></a>
+<h2 class="chapter">2 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="ffmpeg-formats.html">ffmpeg-formats</a>, <a class="url" href="ffmpeg-protocols.html">ffmpeg-protocols</a>,
+<a class="url" href="libavutil.html">libavutil</a>, <a class="url" href="libavcodec.html">libavcodec</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">3 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/libavutil.html

@@ -0,0 +1,93 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Libavutil Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Libavutil Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">2 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">3 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>The libavutil library is a utility library to aid portable
+multimedia programming. It contains safe portable string functions,
+random number generators, data structures, additional mathematics
+functions, cryptography and multimedia related functionality (like
+enumerations for pixel and sample formats). It is not a library for
+code needed by both libavcodec and libavformat.
+</p>
+<p>The goals for this library is to be:
+</p>
+<dl class="table">
+<dt><strong class="strong">Modular</strong></dt>
+<dd><p>It should have few interdependencies and the possibility of disabling individual
+parts during <code class="command">./configure</code>.
+</p>
+</dd>
+<dt><strong class="strong">Small</strong></dt>
+<dd><p>Both sources and objects should be small.
+</p>
+</dd>
+<dt><strong class="strong">Efficient</strong></dt>
+<dd><p>It should have low CPU and memory usage.
+</p>
+</dd>
+<dt><strong class="strong">Useful</strong></dt>
+<dd><p>It should avoid useless features that almost no one needs.
+</p></dd>
+</dl>
+
+
+<a name="See-Also"></a>
+<h2 class="chapter">2 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="ffmpeg-utils.html">ffmpeg-utils</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">3 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/libswresample.html

@@ -0,0 +1,93 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Libswresample Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Libswresample Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">2 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">3 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>The libswresample library performs highly optimized audio resampling,
+rematrixing and sample format conversion operations.
+</p>
+<p>Specifically, this library performs the following conversions:
+</p>
+<ul class="itemize mark-bullet">
+<li><em class="emph">Resampling</em>: is the process of changing the audio rate, for
+example from a high sample rate of 44100Hz to 8000Hz. Audio
+conversion from high to low sample rate is a lossy process. Several
+resampling options and algorithms are available.
+
+</li><li><em class="emph">Format conversion</em>: is the process of converting the type of
+samples, for example from 16-bit signed samples to unsigned 8-bit or
+float samples. It also handles packing conversion, when passing from
+packed layout (all samples belonging to distinct channels interleaved
+in the same buffer), to planar layout (all samples belonging to the
+same channel stored in a dedicated buffer or &quot;plane&quot;).
+
+</li><li><em class="emph">Rematrixing</em>: is the process of changing the channel layout, for
+example from stereo to mono. When the input channels cannot be mapped
+to the output streams, the process is lossy, since it involves
+different gain factors and mixing.
+</li></ul>
+
+<p>Various other audio conversions (e.g. stretching and padding) are
+enabled through dedicated options.
+</p>
+
+<a name="See-Also"></a>
+<h2 class="chapter">2 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="ffmpeg-resampler.html">ffmpeg-resampler</a>,
+<a class="url" href="libavutil.html">libavutil</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">3 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/libswscale.html

@@ -0,0 +1,87 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Libswscale Documentation
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Libswscale Documentation
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-See-Also" href="#See-Also">2 See Also</a></li>
+  <li><a id="toc-Authors" href="#Authors">3 Authors</a></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+
+<p>The libswscale library performs highly optimized image scaling and
+colorspace and pixel format conversion operations.
+</p>
+<p>Specifically, this library performs the following conversions:
+</p>
+<ul class="itemize mark-bullet">
+<li><em class="emph">Rescaling</em>: is the process of changing the video size. Several
+rescaling options and algorithms are available. This is usually a
+lossy process.
+
+</li><li><em class="emph">Pixel format conversion</em>: is the process of converting the image
+format and colorspace of the image, for example from planar YUV420P to
+RGB24 packed. It also handles packing conversion, that is converts
+from packed layout (all pixels belonging to distinct planes
+interleaved in the same buffer), to planar layout (all samples
+belonging to the same plane stored in a dedicated buffer or &quot;plane&quot;).
+
+<p>This is usually a lossy process in case the source and destination
+colorspaces differ.
+</p></li></ul>
+
+
+<a name="See-Also"></a>
+<h2 class="chapter">2 See Also<span class="pull-right"><a class="anchor hidden-xs" href="#See-Also" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-See-Also" aria-hidden="true">TOC</a></span></h2>
+
+<p><a class="url" href="ffmpeg.html">ffmpeg</a>, <a class="url" href="ffplay.html">ffplay</a>, <a class="url" href="ffprobe.html">ffprobe</a>,
+<a class="url" href="ffmpeg-scaler.html">ffmpeg-scaler</a>,
+<a class="url" href="libavutil.html">libavutil</a>
+</p>
+
+<a name="Authors"></a>
+<h2 class="chapter">3 Authors<span class="pull-right"><a class="anchor hidden-xs" href="#Authors" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Authors" aria-hidden="true">TOC</a></span></h2>
+
+<p>The FFmpeg developers.
+</p>
+<p>For details about the authorship, see the Git history of the project
+(https://git.ffmpeg.org/ffmpeg), e.g. by typing the command
+<code class="command">git log</code> in the FFmpeg source directory, or browsing the
+online repository at <a class="url" href="https://git.ffmpeg.org/ffmpeg">https://git.ffmpeg.org/ffmpeg</a>.
+</p>
+<p>Maintainers for the specific components are listed in the file
+<samp class="file">MAINTAINERS</samp> in the source code tree.
+</p>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/mailing-list-faq.html

@@ -0,0 +1,443 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      FFmpeg Mailing List FAQ
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      FFmpeg Mailing List FAQ
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-General-Questions" href="#General-Questions">1 General Questions</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-What-is-a-mailing-list_003f" href="#What-is-a-mailing-list_003f">1.1 What is a mailing list?</a></li>
+    <li><a id="toc-What-type-of-questions-can-I-ask_003f" href="#What-type-of-questions-can-I-ask_003f">1.2 What type of questions can I ask?</a></li>
+    <li><a id="toc-How-do-I-ask-a-question-or-send-a-message-to-a-mailing-list_003f-1" href="#How-do-I-ask-a-question-or-send-a-message-to-a-mailing-list_003f-1">1.3 How do I ask a question or send a message to a mailing list?</a></li>
+  </ul></li>
+  <li><a id="toc-Subscribing-_002f-Unsubscribing" href="#Subscribing-_002f-Unsubscribing">2 Subscribing / Unsubscribing</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-How-do-I-subscribe_003f-1" href="#How-do-I-subscribe_003f-1">2.1 How do I subscribe?</a></li>
+    <li><a id="toc-How-do-I-unsubscribe_003f" href="#How-do-I-unsubscribe_003f">2.2 How do I unsubscribe?</a></li>
+  </ul></li>
+  <li><a id="toc-Moderation-Queue" href="#Moderation-Queue">3 Moderation Queue</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Why-is-my-message-awaiting-moderator-approval_003f-1" href="#Why-is-my-message-awaiting-moderator-approval_003f-1">3.1 Why is my message awaiting moderator approval?</a></li>
+    <li><a id="toc-How-long-does-it-take-for-my-message-in-the-moderation-queue-to-be-approved_003f" href="#How-long-does-it-take-for-my-message-in-the-moderation-queue-to-be-approved_003f">3.2 How long does it take for my message in the moderation queue to be approved?</a></li>
+    <li><a id="toc-How-do-I-delete-my-message-in-the-moderation-queue_003f-1" href="#How-do-I-delete-my-message-in-the-moderation-queue_003f-1">3.3 How do I delete my message in the moderation queue?</a></li>
+  </ul></li>
+  <li><a id="toc-Archives" href="#Archives">4 Archives</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Where-are-the-archives_003f-1" href="#Where-are-the-archives_003f-1">4.1 Where are the archives?</a></li>
+    <li><a id="toc-How-do-I-reply-to-a-message-in-the-archives_003f" href="#How-do-I-reply-to-a-message-in-the-archives_003f">4.2 How do I reply to a message in the archives?</a></li>
+    <li><a id="toc-How-do-I-search-the-archives_003f" href="#How-do-I-search-the-archives_003f">4.3 How do I search the archives?</a></li>
+  </ul></li>
+  <li><a id="toc-Other" href="#Other">5 Other</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Is-there-an-alternative-to-the-mailing-list_003f" href="#Is-there-an-alternative-to-the-mailing-list_003f">5.1 Is there an alternative to the mailing list?</a></li>
+    <li><a id="toc-What-is-top_002dposting_003f-1" href="#What-is-top_002dposting_003f-1">5.2 What is top-posting?</a></li>
+    <li><a id="toc-What-is-the-message-size-limit_003f-1" href="#What-is-the-message-size-limit_003f-1">5.3 What is the message size limit?</a></li>
+    <li><a id="toc-Where-can-I-upload-sample-files_003f" href="#Where-can-I-upload-sample-files_003f">5.4 Where can I upload sample files?</a></li>
+    <li><a id="toc-Will-I-receive-spam-if-I-send-and_002for-subscribe-to-a-mailing-list_003f" href="#Will-I-receive-spam-if-I-send-and_002for-subscribe-to-a-mailing-list_003f">5.5 Will I receive spam if I send and/or subscribe to a mailing list?</a></li>
+    <li><a id="toc-How-do-I-filter-mailing-list-messages_003f" href="#How-do-I-filter-mailing-list-messages_003f">5.6 How do I filter mailing list messages?</a></li>
+    <li><a id="toc-How-do-I-disable-mail-delivery-without-unsubscribing_003f-1" href="#How-do-I-disable-mail-delivery-without-unsubscribing_003f-1">5.7 How do I disable mail delivery without unsubscribing?</a></li>
+    <li><a id="toc-Why-is-the-mailing-list-munging-my-address_003f-1" href="#Why-is-the-mailing-list-munging-my-address_003f-1">5.8 Why is the mailing list munging my address?</a></li>
+  </ul></li>
+  <li><a id="toc-Rules-and-Etiquette" href="#Rules-and-Etiquette">6 Rules and Etiquette</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-What-are-the-rules-and-the-proper-etiquette_003f" href="#What-are-the-rules-and-the-proper-etiquette_003f">6.1 What are the rules and the proper etiquette?</a></li>
+  </ul></li>
+  <li><a id="toc-Help" href="#Help">7 Help</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Why-am-I-not-receiving-any-messages_003f" href="#Why-am-I-not-receiving-any-messages_003f">7.1 Why am I not receiving any messages?</a></li>
+    <li><a id="toc-Why-are-my-sent-messages-not-showing-up_003f" href="#Why-are-my-sent-messages-not-showing-up_003f">7.2 Why are my sent messages not showing up?</a></li>
+    <li><a id="toc-Why-do-I-keep-getting-unsubscribed-from-ffmpeg_002ddevel_003f-1" href="#Why-do-I-keep-getting-unsubscribed-from-ffmpeg_002ddevel_003f-1">7.3 Why do I keep getting unsubscribed from ffmpeg-devel?</a></li>
+    <li><a id="toc-Who-do-I-contact-if-I-have-a-problem-with-the-mailing-list_003f-1" href="#Who-do-I-contact-if-I-have-a-problem-with-the-mailing-list_003f-1">7.4 Who do I contact if I have a problem with the mailing list?</a></li>
+  </ul></li>
+</ul>
+</div>
+</div>
+
+<a name="General-Questions"></a>
+<h2 class="chapter">1 General Questions<span class="pull-right"><a class="anchor hidden-xs" href="#General-Questions" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-General-Questions" aria-hidden="true">TOC</a></span></h2>
+
+<a name="What-is-a-mailing-list_003f"></a>
+<h3 class="section">1.1 What is a mailing list?<span class="pull-right"><a class="anchor hidden-xs" href="#What-is-a-mailing-list_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-What-is-a-mailing-list_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>A mailing list is not much different than emailing someone, but the
+main difference is that your message is received by everyone who
+subscribes to the list. It is somewhat like a forum but in email form.
+</p>
+<p>See the <a class="url" href="https://lists.ffmpeg.org/pipermail/ffmpeg-user/">ffmpeg-user archives</a>
+for examples.
+</p>
+<a name="What-type-of-questions-can-I-ask_003f"></a>
+<h3 class="section">1.2 What type of questions can I ask?<span class="pull-right"><a class="anchor hidden-xs" href="#What-type-of-questions-can-I-ask_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-What-type-of-questions-can-I-ask_003f" aria-hidden="true">TOC</a></span></h3>
+
+<ul class="itemize mark-bullet">
+<li><a class="url" href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-user/">ffmpeg-user</a>:
+For questions involving unscripted usage or compilation of the FFmpeg
+command-line tools (<code class="command">ffmpeg</code>, <code class="command">ffprobe</code>, <code class="command">ffplay</code>).
+
+</li><li><a class="url" href="https://lists.ffmpeg.org/mailman/listinfo/libav-user/">libav-user</a>:
+For questions involving the FFmpeg libav* libraries (libavcodec,
+libavformat, libavfilter, etc).
+
+</li><li><a class="url" href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel/">ffmpeg-devel</a>:
+For discussions involving the development of FFmpeg and for submitting
+patches. User questions should be asked at ffmpeg-user or libav-user.
+</li></ul>
+
+<p>To report a bug see <a class="url" href="https://ffmpeg.org/bugreports.html">https://ffmpeg.org/bugreports.html</a>.
+</p>
+<p>We cannot provide help for scripts and/or third-party tools.
+</p>
+<a class="anchor" id="How-do-I-ask-a-question-or-send-a-message-to-a-mailing-list_003f"></a><a name="How-do-I-ask-a-question-or-send-a-message-to-a-mailing-list_003f-1"></a>
+<h3 class="section">1.3 How do I ask a question or send a message to a mailing list?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-ask-a-question-or-send-a-message-to-a-mailing-list_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-ask-a-question-or-send-a-message-to-a-mailing-list_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>First you must <a class="ref" href="#How-do-I-subscribe_003f">subscribe</a>. Then all you have to do is
+send an email:
+</p>
+<ul class="itemize mark-bullet">
+<li>Email <a class="email" href="mailto:ffmpeg-user@ffmpeg.org">ffmpeg-user@ffmpeg.org</a> to send a message to the
+ffmpeg-user mailing list.
+
+</li><li>Email <a class="email" href="mailto:libav-user@ffmpeg.org">libav-user@ffmpeg.org</a> to send a message to the
+libav-user mailing list.
+
+</li><li>Email <a class="email" href="mailto:ffmpeg-devel@ffmpeg.org">ffmpeg-devel@ffmpeg.org</a> to send a message to the
+ffmpeg-devel mailing list.
+</li></ul>
+
+<a name="Subscribing-_002f-Unsubscribing"></a>
+<h2 class="chapter">2 Subscribing / Unsubscribing<span class="pull-right"><a class="anchor hidden-xs" href="#Subscribing-_002f-Unsubscribing" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Subscribing-_002f-Unsubscribing" aria-hidden="true">TOC</a></span></h2>
+
+<a class="anchor" id="How-do-I-subscribe_003f"></a><a name="How-do-I-subscribe_003f-1"></a>
+<h3 class="section">2.1 How do I subscribe?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-subscribe_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-subscribe_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>Email <a class="email" href="mailto:ffmpeg-user-request@ffmpeg.org">ffmpeg-user-request@ffmpeg.org</a> with the subject
+<em class="emph">subscribe</em>.
+</p>
+<p>Or visit the <a class="url" href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-user/">ffmpeg-user mailing list info page</a>
+and refer to the <em class="emph">Subscribing to ffmpeg-user</em> section.
+</p>
+<p>The process is the same for the other mailing lists.
+</p>
+<a name="How-do-I-unsubscribe_003f"></a>
+<h3 class="section">2.2 How do I unsubscribe?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-unsubscribe_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-unsubscribe_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Email <a class="email" href="mailto:ffmpeg-user-request@ffmpeg.org">ffmpeg-user-request@ffmpeg.org</a> with subject <em class="emph">unsubscribe</em>.
+</p>
+<p>Or visit the <a class="url" href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-user/">ffmpeg-user mailing list info page</a>,
+scroll to bottom of page, enter your email address in the box, and click
+the <em class="emph">Unsubscribe or edit options</em> button.
+</p>
+<p>The process is the same for the other mailing lists.
+</p>
+<p>Please avoid asking a mailing list admin to unsubscribe you unless you
+are absolutely unable to do so by yourself. See <a class="ref" href="#Who-do-I-contact-if-I-have-a-problem-with-the-mailing-list_003f">Who do I contact if I have a problem with the mailing list?</a>
+</p>
+<p>Note that it is possible to temporarily halt message delivery (vacation mode).
+See <a class="ref" href="#How-do-I-disable-mail-delivery-without-unsubscribing_003f">How do I disable mail delivery without unsubscribing?</a>
+</p>
+<a name="Moderation-Queue"></a>
+<h2 class="chapter">3 Moderation Queue<span class="pull-right"><a class="anchor hidden-xs" href="#Moderation-Queue" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Moderation-Queue" aria-hidden="true">TOC</a></span></h2>
+<a class="anchor" id="Why-is-my-message-awaiting-moderator-approval_003f"></a><a name="Why-is-my-message-awaiting-moderator-approval_003f-1"></a>
+<h3 class="section">3.1 Why is my message awaiting moderator approval?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-is-my-message-awaiting-moderator-approval_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-is-my-message-awaiting-moderator-approval_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>Some messages are automatically held in the <em class="emph">moderation queue</em> and
+must be manually approved by a mailing list admin:
+</p>
+<p>These are:
+</p>
+<ul class="itemize mark-bullet">
+<li>Messages that exceed the <a class="ref" href="#What-is-the-message-size-limit_003f">message size limit</a>.
+
+</li><li>Messages from users whose accounts have been set with the <em class="emph">moderation flag</em>
+(very rarely occurs, but may if a user repeatedly ignores the rules
+or is abusive towards others).
+</li></ul>
+
+<a name="How-long-does-it-take-for-my-message-in-the-moderation-queue-to-be-approved_003f"></a>
+<h3 class="section">3.2 How long does it take for my message in the moderation queue to be approved?<span class="pull-right"><a class="anchor hidden-xs" href="#How-long-does-it-take-for-my-message-in-the-moderation-queue-to-be-approved_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-long-does-it-take-for-my-message-in-the-moderation-queue-to-be-approved_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>The queue is not checked on a regular basis. You can ask on the
+<code class="t">#ffmpeg-devel</code> IRC channel on Libera Chat for someone to approve your message.
+</p>
+<a class="anchor" id="How-do-I-delete-my-message-in-the-moderation-queue_003f"></a><a name="How-do-I-delete-my-message-in-the-moderation-queue_003f-1"></a>
+<h3 class="section">3.3 How do I delete my message in the moderation queue?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-delete-my-message-in-the-moderation-queue_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-delete-my-message-in-the-moderation-queue_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>You should have received an email with the subject <em class="emph">Your message to &lt;mailing list name&gt; awaits moderator approval</em>.
+A link is in the message that will allow you to delete your message
+unless a mailing list admin already approved or rejected it.
+</p>
+<a name="Archives"></a>
+<h2 class="chapter">4 Archives<span class="pull-right"><a class="anchor hidden-xs" href="#Archives" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Archives" aria-hidden="true">TOC</a></span></h2>
+
+<a class="anchor" id="Where-are-the-archives_003f"></a><a name="Where-are-the-archives_003f-1"></a>
+<h3 class="section">4.1 Where are the archives?<span class="pull-right"><a class="anchor hidden-xs" href="#Where-are-the-archives_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Where-are-the-archives_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>See the <em class="emph">Archives</em> section on the <a class="url" href="https://ffmpeg.org/contact.html">FFmpeg Contact</a>
+page for links to all FFmpeg mailing list archives.
+</p>
+<p>Note that the archives are split by month. Discussions that span
+several months will be split into separate months in the archives.
+</p>
+<a name="How-do-I-reply-to-a-message-in-the-archives_003f"></a>
+<h3 class="section">4.2 How do I reply to a message in the archives?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-reply-to-a-message-in-the-archives_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-reply-to-a-message-in-the-archives_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Click the email link at the top of the message just under the subject
+title. The link will provide the proper headers to keep the message
+within the thread.
+</p>
+<p>Note that you must be subscribed to send a message to the ffmpeg-user or
+libav-user mailing lists.
+</p>
+<a name="How-do-I-search-the-archives_003f"></a>
+<h3 class="section">4.3 How do I search the archives?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-search-the-archives_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-search-the-archives_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Perform a site search using your favorite search engine. Example:
+</p>
+<p><code class="t">site:lists.ffmpeg.org/pipermail/ffmpeg-user/ &quot;search term&quot;</code>
+</p>
+<a name="Other"></a>
+<h2 class="chapter">5 Other<span class="pull-right"><a class="anchor hidden-xs" href="#Other" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Other" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Is-there-an-alternative-to-the-mailing-list_003f"></a>
+<h3 class="section">5.1 Is there an alternative to the mailing list?<span class="pull-right"><a class="anchor hidden-xs" href="#Is-there-an-alternative-to-the-mailing-list_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Is-there-an-alternative-to-the-mailing-list_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>You can ask for help in the official <code class="t">#ffmpeg</code> IRC channel on Libera Chat.
+</p>
+<p>There are also numerous third-party help sites such as
+<a class="url" href="https://superuser.com/tags/ffmpeg">Super User</a> and
+<a class="url" href="https://www.reddit.com/r/ffmpeg/">r/ffmpeg on reddit</a>.
+</p>
+<a class="anchor" id="What-is-top_002dposting_003f"></a><a name="What-is-top_002dposting_003f-1"></a>
+<h3 class="section">5.2 What is top-posting?<span class="pull-right"><a class="anchor hidden-xs" href="#What-is-top_002dposting_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-What-is-top_002dposting_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>See <a class="url" href="https://en.wikipedia.org/wiki/Posting_style#Top-posting">https://en.wikipedia.org/wiki/Posting_style#Top-posting</a>.
+</p>
+<p>Instead, use trimmed interleaved/inline replies (<a class="url" href="https://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-April/035849.html">example</a>).
+</p>
+<a class="anchor" id="What-is-the-message-size-limit_003f"></a><a name="What-is-the-message-size-limit_003f-1"></a>
+<h3 class="section">5.3 What is the message size limit?<span class="pull-right"><a class="anchor hidden-xs" href="#What-is-the-message-size-limit_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-What-is-the-message-size-limit_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>The message size limit is 1000 kilobytes. Please provide links to larger files
+instead of attaching them.
+</p>
+<a name="Where-can-I-upload-sample-files_003f"></a>
+<h3 class="section">5.4 Where can I upload sample files?<span class="pull-right"><a class="anchor hidden-xs" href="#Where-can-I-upload-sample-files_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Where-can-I-upload-sample-files_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Anywhere that is not too annoying for us to use.
+</p>
+<p>Google Drive and Dropbox are acceptable if you need a file host, and
+<a class="url" href="https://0x0.st/">0x0.st</a> is good for files under 256 MiB.
+</p>
+<p>Small, short samples are preferred if possible.
+</p>
+<a name="Will-I-receive-spam-if-I-send-and_002for-subscribe-to-a-mailing-list_003f"></a>
+<h3 class="section">5.5 Will I receive spam if I send and/or subscribe to a mailing list?<span class="pull-right"><a class="anchor hidden-xs" href="#Will-I-receive-spam-if-I-send-and_002for-subscribe-to-a-mailing-list_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Will-I-receive-spam-if-I-send-and_002for-subscribe-to-a-mailing-list_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Highly unlikely.
+</p>
+<ul class="itemize mark-bullet">
+<li>The list of subscribed users is not public.
+
+</li><li>Email addresses in the archives are obfuscated.
+
+</li><li>Several unique test email accounts were utilized and none have yet
+received any spam.
+</li></ul>
+
+<p>However, you may see a spam in the mailing lists on rare occasions:
+</p>
+<ul class="itemize mark-bullet">
+<li>Spam in the moderation queue may be accidentally approved due to human
+error.
+
+</li><li>There have been a few messages from subscribed users who had their own
+email addresses hacked and spam messages from (or appearing to be from)
+the hacked account were sent to their contacts (a mailing list being a
+contact in these cases).
+
+</li><li>If you are subscribed to the bug tracker mailing list (ffmpeg-trac) you
+may see the occasional spam as a false bug report, but we take measures
+to try to prevent this.
+</li></ul>
+
+<a name="How-do-I-filter-mailing-list-messages_003f"></a>
+<h3 class="section">5.6 How do I filter mailing list messages?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-filter-mailing-list-messages_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-filter-mailing-list-messages_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Use the <em class="emph">List-Id</em>. For example, the ffmpeg-user mailing list is
+<code class="t">ffmpeg-user.ffmpeg.org</code>. You can view the List-Id in the raw message
+or headers.
+</p>
+<p>You can then filter the mailing list messages to their own folder.
+</p>
+<a class="anchor" id="How-do-I-disable-mail-delivery-without-unsubscribing_003f"></a><a name="How-do-I-disable-mail-delivery-without-unsubscribing_003f-1"></a>
+<h3 class="section">5.7 How do I disable mail delivery without unsubscribing?<span class="pull-right"><a class="anchor hidden-xs" href="#How-do-I-disable-mail-delivery-without-unsubscribing_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-How-do-I-disable-mail-delivery-without-unsubscribing_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>Sometimes you may want to temporarily stop receiving all mailing list
+messages. This &quot;vacation mode&quot; is simple to do:
+</p>
+<ol class="enumerate">
+<li> Go to the <a class="url" href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-user/">ffmpeg-user mailing list info page</a>
+
+</li><li> Enter your email address in the box at very bottom of the page and click the
+<em class="emph">Unsubscribe or edit options</em> box.
+
+</li><li> Enter your password and click the <em class="emph">Log in</em> button.
+
+</li><li> Look for the <em class="emph">Mail delivery</em> option. Here you can disable/enable mail
+delivery. If you check <em class="emph">Set globally</em> it will apply your choice to all
+other FFmpeg mailing lists you are subscribed to.
+</li></ol>
+
+<p>Alternatively, from your subscribed address, send a message to <a class="email" href="mailto:ffmpeg-user-request@ffmpeg.org">ffmpeg-user-request@ffmpeg.org</a>
+with the subject <em class="emph">set delivery off</em>. To re-enable mail delivery send a
+message to <a class="email" href="mailto:ffmpeg-user-request@ffmpeg.org">ffmpeg-user-request@ffmpeg.org</a> with the subject
+<em class="emph">set delivery on</em>.
+</p>
+<a class="anchor" id="Why-is-the-mailing-list-munging-my-address_003f"></a><a name="Why-is-the-mailing-list-munging-my-address_003f-1"></a>
+<h3 class="section">5.8 Why is the mailing list munging my address?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-is-the-mailing-list-munging-my-address_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-is-the-mailing-list-munging-my-address_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>This is due to subscribers that use an email service with a DMARC reject policy
+which adds difficulties to mailing list operators.
+</p>
+<p>The mailing list must re-write (munge) the <em class="emph">From:</em> header for such users;
+otherwise their email service will reject and bounce the message resulting in
+automatic unsubscribing from the mailing list.
+</p>
+<p>When sending a message these users will see <em class="emph">via &lt;mailing list name&gt;</em>
+added to their name and the <em class="emph">From:</em> address munged to the address of
+the particular mailing list.
+</p>
+<p>If you want to avoid this then please use a different email service.
+</p>
+<p>Note that ffmpeg-devel does not apply any munging as it causes issues with
+patch authorship. As a result users with an email service with a DMARC reject
+policy may be automatically unsubscribed due to rejected and bounced messages.
+</p>
+<a name="Rules-and-Etiquette"></a>
+<h2 class="chapter">6 Rules and Etiquette<span class="pull-right"><a class="anchor hidden-xs" href="#Rules-and-Etiquette" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Rules-and-Etiquette" aria-hidden="true">TOC</a></span></h2>
+
+<a name="What-are-the-rules-and-the-proper-etiquette_003f"></a>
+<h3 class="section">6.1 What are the rules and the proper etiquette?<span class="pull-right"><a class="anchor hidden-xs" href="#What-are-the-rules-and-the-proper-etiquette_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-What-are-the-rules-and-the-proper-etiquette_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>There may seem to be many things to remember, but we want to help and
+following these guidelines will allow you to get answers more quickly
+and help avoid getting ignored.
+</p>
+<ul class="itemize mark-bullet">
+<li>Always show your actual, unscripted <code class="command">ffmpeg</code> command and the
+complete, uncut console output from your command.
+
+</li><li>Use the most simple and minimal command that still shows the issue you
+are encountering.
+
+</li><li>Provide all necessary information so others can attempt to duplicate
+your issue. This includes the actual command, complete uncut console
+output, and any inputs that are required to duplicate the issue.
+
+</li><li>Use the latest <code class="command">ffmpeg</code> build you can get. See the <a class="url" href="https://ffmpeg.org/download.html">FFmpeg Download</a>
+page for links to recent builds for Linux, macOS, and Windows. Or
+compile from the current git master branch.
+
+</li><li>Avoid <a class="url" href="https://en.wikipedia.org/wiki/Posting_style#Top-posting">top-posting</a>.
+Also see <a class="ref" href="#What-is-top_002dposting_003f">What is top-posting?</a>
+
+</li><li>Avoid hijacking threads. Thread hijacking is replying to a message and
+changing the subject line to something unrelated to the original thread.
+Most email clients will still show the renamed message under the
+original thread. This can be confusing and these types of messages are
+often ignored.
+
+</li><li>Do not send screenshots. Copy and paste console text instead of making
+screenshots of the text.
+
+</li><li>Avoid sending email disclaimers and legalese if possible as this is a
+public list.
+
+</li><li>Avoid using the <code class="code">-loglevel debug</code>, <code class="code">-loglevel quiet</code>, and
+<code class="command">-hide_banner</code> options unless requested to do so.
+
+</li><li>If you attach files avoid compressing small files. Uncompressed is
+preferred.
+
+</li><li>Please do not send HTML-only messages. The mailing list will ignore the
+HTML component of your message. Most mail clients will automatically
+include a text component: this is what the mailing list will use.
+
+</li><li>Configuring your mail client to break lines after 70 or so characters is
+recommended.
+
+</li><li>Avoid sending the same message to multiple mailing lists.
+
+</li><li>Please follow our <a class="url" href="https://ffmpeg.org/community.html#Code-of-conduct">Code of Conduct</a>.
+</li></ul>
+
+<a name="Help"></a>
+<h2 class="chapter">7 Help<span class="pull-right"><a class="anchor hidden-xs" href="#Help" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Help" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Why-am-I-not-receiving-any-messages_003f"></a>
+<h3 class="section">7.1 Why am I not receiving any messages?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-am-I-not-receiving-any-messages_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-am-I-not-receiving-any-messages_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Some email providers have blacklists or spam filters that block or mark
+the mailing list messages as false positives. Unfortunately, the user is
+often not aware of this and is often out of their control.
+</p>
+<p>When possible we attempt to notify the provider to be removed from the
+blacklists or filters.
+</p>
+<a name="Why-are-my-sent-messages-not-showing-up_003f"></a>
+<h3 class="section">7.2 Why are my sent messages not showing up?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-are-my-sent-messages-not-showing-up_003f" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-are-my-sent-messages-not-showing-up_003f" aria-hidden="true">TOC</a></span></h3>
+
+<p>Excluding <a class="ref" href="#Why-is-my-message-awaiting-moderator-approval_003f">messages that are held in the moderation queue</a>
+there are a few other reasons why your messages may fail to appear:
+</p>
+<ul class="itemize mark-bullet">
+<li>HTML-only messages are ignored by the mailing lists. Most mail clients
+automatically include a text component alongside HTML email: this is what
+the mailing list will use. If it does not then consider your client to be
+broken, because sending a text component along with the HTML component to
+form a multi-part message is recommended by email standards.
+
+</li><li>Check your spam folder.
+</li></ul>
+
+<a class="anchor" id="Why-do-I-keep-getting-unsubscribed-from-ffmpeg_002ddevel_003f"></a><a name="Why-do-I-keep-getting-unsubscribed-from-ffmpeg_002ddevel_003f-1"></a>
+<h3 class="section">7.3 Why do I keep getting unsubscribed from ffmpeg-devel?<span class="pull-right"><a class="anchor hidden-xs" href="#Why-do-I-keep-getting-unsubscribed-from-ffmpeg_002ddevel_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Why-do-I-keep-getting-unsubscribed-from-ffmpeg_002ddevel_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>Users with an email service that has a DMARC reject or quarantine policy may be
+automatically unsubscribed from the ffmpeg-devel mailing list due to the mailing
+list messages being continuously rejected and bounced back.
+</p>
+<p>Consider using a different email service.
+</p>
+<a class="anchor" id="Who-do-I-contact-if-I-have-a-problem-with-the-mailing-list_003f"></a><a name="Who-do-I-contact-if-I-have-a-problem-with-the-mailing-list_003f-1"></a>
+<h3 class="section">7.4 Who do I contact if I have a problem with the mailing list?<span class="pull-right"><a class="anchor hidden-xs" href="#Who-do-I-contact-if-I-have-a-problem-with-the-mailing-list_003f-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Who-do-I-contact-if-I-have-a-problem-with-the-mailing-list_003f-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>Send a message to <a class="email" href="mailto:ffmpeg-user-owner@ffmpeg.org">ffmpeg-user-owner@ffmpeg.org</a>.
+</p>
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/nut.html

@@ -0,0 +1,214 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      NUT
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      NUT
+      </h1>
+
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Description" href="#Description">1 Description</a></li>
+  <li><a id="toc-Modes" href="#Modes">2 Modes</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-BROADCAST" href="#BROADCAST">2.1 BROADCAST</a></li>
+    <li><a id="toc-PIPE" href="#PIPE">2.2 PIPE</a></li>
+  </ul></li>
+  <li><a id="toc-Container_002dspecific-codec-tags" href="#Container_002dspecific-codec-tags">3 Container-specific codec tags</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Generic-raw-YUVA-formats" href="#Generic-raw-YUVA-formats">3.1 Generic raw YUVA formats</a></li>
+    <li><a id="toc-Raw-Audio" href="#Raw-Audio">3.2 Raw Audio</a></li>
+    <li><a id="toc-Subtitles" href="#Subtitles">3.3 Subtitles</a></li>
+    <li><a id="toc-Raw-Data" href="#Raw-Data">3.4 Raw Data</a></li>
+    <li><a id="toc-Codecs" href="#Codecs">3.5 Codecs</a></li>
+  </ul></li>
+</ul>
+</div>
+</div>
+
+<a name="Description"></a>
+<h2 class="chapter">1 Description<span class="pull-right"><a class="anchor hidden-xs" href="#Description" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Description" aria-hidden="true">TOC</a></span></h2>
+<p>NUT is a low overhead generic container format. It stores audio, video,
+subtitle and user-defined streams in a simple, yet efficient, way.
+</p>
+<p>It was created by a group of FFmpeg and MPlayer developers in 2003
+and was finalized in 2008.
+</p>
+<p>The official nut specification is at svn://svn.mplayerhq.hu/nut
+In case of any differences between this text and the official specification,
+the official specification shall prevail.
+</p>
+<a name="Modes"></a>
+<h2 class="chapter">2 Modes<span class="pull-right"><a class="anchor hidden-xs" href="#Modes" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Modes" aria-hidden="true">TOC</a></span></h2>
+<p>NUT has some variants signaled by using the flags field in its main header.
+</p>
+<table class="multitable">
+<tbody><tr><td width="40%">BROADCAST</td><td width="40%">Extend the syncpoint to report the sender wallclock</td></tr>
+<tr><td width="40%">PIPE</td><td width="40%">Omit completely the syncpoint</td></tr>
+</tbody>
+</table>
+
+<a name="BROADCAST"></a>
+<h3 class="section">2.1 BROADCAST<span class="pull-right"><a class="anchor hidden-xs" href="#BROADCAST" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-BROADCAST" aria-hidden="true">TOC</a></span></h3>
+
+<p>The BROADCAST variant provides a secondary time reference to facilitate
+detecting endpoint latency and network delays.
+It assumes all the endpoint clocks are synchronized.
+To be used in real-time scenarios.
+</p>
+<a name="PIPE"></a>
+<h3 class="section">2.2 PIPE<span class="pull-right"><a class="anchor hidden-xs" href="#PIPE" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-PIPE" aria-hidden="true">TOC</a></span></h3>
+
+<p>The PIPE variant assumes NUT is used as non-seekable intermediate container,
+by not using syncpoint removes unneeded overhead and reduces the overall
+memory usage.
+</p>
+<a name="Container_002dspecific-codec-tags"></a>
+<h2 class="chapter">3 Container-specific codec tags<span class="pull-right"><a class="anchor hidden-xs" href="#Container_002dspecific-codec-tags" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Container_002dspecific-codec-tags" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Generic-raw-YUVA-formats"></a>
+<h3 class="section">3.1 Generic raw YUVA formats<span class="pull-right"><a class="anchor hidden-xs" href="#Generic-raw-YUVA-formats" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Generic-raw-YUVA-formats" aria-hidden="true">TOC</a></span></h3>
+
+<p>Since many exotic planar YUVA pixel formats are not considered by
+the AVI/QuickTime FourCC lists, the following scheme is adopted for
+representing them.
+</p>
+<p>The first two bytes can contain the values:
+Y1 = only Y
+Y2 = Y+A
+Y3 = YUV
+Y4 = YUVA
+</p>
+<p>The third byte represents the width and height chroma subsampling
+values for the UV planes, that is the amount to shift the luma
+width/height right to find the chroma width/height.
+</p>
+<p>The fourth byte is the number of bits used (8, 16, ...).
+</p>
+<p>If the order of bytes is inverted, that means that each component has
+to be read big-endian.
+</p>
+<a name="Raw-Audio"></a>
+<h3 class="section">3.2 Raw Audio<span class="pull-right"><a class="anchor hidden-xs" href="#Raw-Audio" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Raw-Audio" aria-hidden="true">TOC</a></span></h3>
+
+<table class="multitable">
+<tbody><tr><td width="40%">ALAW</td><td width="40%">A-LAW</td></tr>
+<tr><td width="40%">ULAW</td><td width="40%">MU-LAW</td></tr>
+<tr><td width="40%">P&lt;type&gt;&lt;interleaving&gt;&lt;bits&gt;</td><td width="40%">little-endian PCM</td></tr>
+<tr><td width="40%">&lt;bits&gt;&lt;interleaving&gt;&lt;type&gt;P</td><td width="40%">big-endian PCM</td></tr>
+</tbody>
+</table>
+
+<p>&lt;type&gt; is S for signed integer, U for unsigned integer, F for IEEE float
+&lt;interleaving&gt; is D for default, P is for planar.
+&lt;bits&gt; is 8/16/24/32
+</p>
+<div class="example">
+<pre class="example-preformatted">PFD[32]   would for example be signed 32 bit little-endian IEEE float
+</pre></div>
+
+<a name="Subtitles"></a>
+<h3 class="section">3.3 Subtitles<span class="pull-right"><a class="anchor hidden-xs" href="#Subtitles" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Subtitles" aria-hidden="true">TOC</a></span></h3>
+
+<table class="multitable">
+<tbody><tr><td width="40%">UTF8</td><td width="40%">Raw UTF-8</td></tr>
+<tr><td width="40%">SSA[0]</td><td width="40%">SubStation Alpha</td></tr>
+<tr><td width="40%">DVDS</td><td width="40%">DVD subtitles</td></tr>
+<tr><td width="40%">DVBS</td><td width="40%">DVB subtitles</td></tr>
+</tbody>
+</table>
+
+<a name="Raw-Data"></a>
+<h3 class="section">3.4 Raw Data<span class="pull-right"><a class="anchor hidden-xs" href="#Raw-Data" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Raw-Data" aria-hidden="true">TOC</a></span></h3>
+
+<table class="multitable">
+<tbody><tr><td width="40%">UTF8</td><td width="40%">Raw UTF-8</td></tr>
+</tbody>
+</table>
+
+<a name="Codecs"></a>
+<h3 class="section">3.5 Codecs<span class="pull-right"><a class="anchor hidden-xs" href="#Codecs" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Codecs" aria-hidden="true">TOC</a></span></h3>
+
+<table class="multitable">
+<tbody><tr><td width="40%">3IV1</td><td width="40%">non-compliant MPEG-4 generated by old 3ivx</td></tr>
+<tr><td width="40%">ASV1</td><td width="40%">Asus Video</td></tr>
+<tr><td width="40%">ASV2</td><td width="40%">Asus Video 2</td></tr>
+<tr><td width="40%">CVID</td><td width="40%">Cinepak</td></tr>
+<tr><td width="40%">CYUV</td><td width="40%">Creative YUV</td></tr>
+<tr><td width="40%">DIVX</td><td width="40%">non-compliant MPEG-4 generated by old DivX</td></tr>
+<tr><td width="40%">DUCK</td><td width="40%">Truemotion 1</td></tr>
+<tr><td width="40%">FFV1</td><td width="40%">FFmpeg video 1</td></tr>
+<tr><td width="40%">FFVH</td><td width="40%">FFmpeg Huffyuv</td></tr>
+<tr><td width="40%">H261</td><td width="40%">ITU H.261</td></tr>
+<tr><td width="40%">H262</td><td width="40%">ITU H.262</td></tr>
+<tr><td width="40%">H263</td><td width="40%">ITU H.263</td></tr>
+<tr><td width="40%">H264</td><td width="40%">ITU H.264</td></tr>
+<tr><td width="40%">HFYU</td><td width="40%">Huffyuv</td></tr>
+<tr><td width="40%">I263</td><td width="40%">Intel H.263</td></tr>
+<tr><td width="40%">IV31</td><td width="40%">Indeo 3.1</td></tr>
+<tr><td width="40%">IV32</td><td width="40%">Indeo 3.2</td></tr>
+<tr><td width="40%">IV50</td><td width="40%">Indeo 5.0</td></tr>
+<tr><td width="40%">LJPG</td><td width="40%">ITU JPEG (lossless)</td></tr>
+<tr><td width="40%">MJLS</td><td width="40%">ITU JPEG-LS</td></tr>
+<tr><td width="40%">MJPG</td><td width="40%">ITU JPEG</td></tr>
+<tr><td width="40%">MPG4</td><td width="40%">MS MPEG-4v1 (not ISO MPEG-4)</td></tr>
+<tr><td width="40%">MP42</td><td width="40%">MS MPEG-4v2</td></tr>
+<tr><td width="40%">MP43</td><td width="40%">MS MPEG-4v3</td></tr>
+<tr><td width="40%">MP4V</td><td width="40%">ISO MPEG-4 Part 2 Video (from old encoders)</td></tr>
+<tr><td width="40%">mpg1</td><td width="40%">ISO MPEG-1 Video</td></tr>
+<tr><td width="40%">mpg2</td><td width="40%">ISO MPEG-2 Video</td></tr>
+<tr><td width="40%">MRLE</td><td width="40%">MS RLE</td></tr>
+<tr><td width="40%">MSVC</td><td width="40%">MS Video 1</td></tr>
+<tr><td width="40%">RT21</td><td width="40%">Indeo 2.1</td></tr>
+<tr><td width="40%">RV10</td><td width="40%">RealVideo 1.0</td></tr>
+<tr><td width="40%">RV20</td><td width="40%">RealVideo 2.0</td></tr>
+<tr><td width="40%">RV30</td><td width="40%">RealVideo 3.0</td></tr>
+<tr><td width="40%">RV40</td><td width="40%">RealVideo 4.0</td></tr>
+<tr><td width="40%">SNOW</td><td width="40%">FFmpeg Snow</td></tr>
+<tr><td width="40%">SVQ1</td><td width="40%">Sorenson Video 1</td></tr>
+<tr><td width="40%">SVQ3</td><td width="40%">Sorenson Video 3</td></tr>
+<tr><td width="40%">theo</td><td width="40%">Xiph Theora</td></tr>
+<tr><td width="40%">TM20</td><td width="40%">Truemotion 2.0</td></tr>
+<tr><td width="40%">UMP4</td><td width="40%">non-compliant MPEG-4 generated by UB Video MPEG-4</td></tr>
+<tr><td width="40%">VCR1</td><td width="40%">ATI VCR1</td></tr>
+<tr><td width="40%">VP30</td><td width="40%">VP 3.0</td></tr>
+<tr><td width="40%">VP31</td><td width="40%">VP 3.1</td></tr>
+<tr><td width="40%">VP50</td><td width="40%">VP 5.0</td></tr>
+<tr><td width="40%">VP60</td><td width="40%">VP 6.0</td></tr>
+<tr><td width="40%">VP61</td><td width="40%">VP 6.1</td></tr>
+<tr><td width="40%">VP62</td><td width="40%">VP 6.2</td></tr>
+<tr><td width="40%">VP70</td><td width="40%">VP 7.0</td></tr>
+<tr><td width="40%">WMV1</td><td width="40%">MS WMV7</td></tr>
+<tr><td width="40%">WMV2</td><td width="40%">MS WMV8</td></tr>
+<tr><td width="40%">WMV3</td><td width="40%">MS WMV9</td></tr>
+<tr><td width="40%">WV1F</td><td width="40%">non-compliant MPEG-4 generated by ?</td></tr>
+<tr><td width="40%">WVC1</td><td width="40%">VC-1</td></tr>
+<tr><td width="40%">XVID</td><td width="40%">non-compliant MPEG-4 generated by old Xvid</td></tr>
+<tr><td width="40%">XVIX</td><td width="40%">non-compliant MPEG-4 generated by old Xvid with interlacing bug</td></tr>
+</tbody>
+</table>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/platform.html

@@ -0,0 +1,390 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!-- Created by , GNU Texinfo 7.1 -->
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Platform Specific Information
+    </title>
+    <meta name="viewport" content="width=device-width,initial-scale=1.0">
+    <link rel="stylesheet" type="text/css" href="bootstrap.min.css">
+    <link rel="stylesheet" type="text/css" href="style.min.css">
+  </head>
+  <body>
+    <div class="container">
+      <h1>
+      Platform Specific Information
+      </h1>
+
+
+<a name="SEC_Top"></a>
+
+<div class="element-contents" id="SEC_Contents">
+<h2 class="contents-heading">Table of Contents</h2>
+
+<div class="contents">
+
+<ul class="toc-numbered-mark">
+  <li><a id="toc-Unix_002dlike" href="#Unix_002dlike">1 Unix-like</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Advanced-linking-configuration" href="#Advanced-linking-configuration">1.1 Advanced linking configuration</a></li>
+    <li><a id="toc-BSD" href="#BSD">1.2 BSD</a></li>
+    <li><a id="toc-_0028Open_0029Solaris" href="#g_t_0028Open_0029Solaris">1.3 (Open)Solaris</a></li>
+    <li><a id="toc-Darwin-_0028Mac-OS-X_002c-iPhone_0029" href="#Darwin-_0028Mac-OS-X_002c-iPhone_0029">1.4 Darwin (Mac OS X, iPhone)</a></li>
+  </ul></li>
+  <li><a id="toc-DOS" href="#DOS">2 DOS</a></li>
+  <li><a id="toc-OS_002f2" href="#OS_002f2">3 OS/2</a></li>
+  <li><a id="toc-Windows" href="#Windows">4 Windows</a>
+  <ul class="toc-numbered-mark">
+    <li><a id="toc-Native-Windows-compilation-using-MinGW-or-MinGW_002dw64" href="#Native-Windows-compilation-using-MinGW-or-MinGW_002dw64">4.1 Native Windows compilation using MinGW or MinGW-w64</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-Native-Windows-compilation-using-MSYS2" href="#Native-Windows-compilation-using-MSYS2">4.1.1 Native Windows compilation using MSYS2</a></li>
+    </ul></li>
+    <li><a id="toc-Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows" href="#Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows">4.2 Microsoft Visual C++ or Intel C++ Compiler for Windows</a>
+    <ul class="toc-numbered-mark">
+      <li><a id="toc-Linking-to-FFmpeg-with-Microsoft-Visual-C_002b_002b" href="#Linking-to-FFmpeg-with-Microsoft-Visual-C_002b_002b">4.2.1 Linking to FFmpeg with Microsoft Visual C++</a></li>
+    </ul></li>
+    <li><a id="toc-Cross-compilation-for-Windows-with-Linux-1" href="#Cross-compilation-for-Windows-with-Linux-1">4.3 Cross compilation for Windows with Linux</a></li>
+    <li><a id="toc-Compilation-under-Cygwin" href="#Compilation-under-Cygwin">4.4 Compilation under Cygwin</a></li>
+    <li><a id="toc-Crosscompilation-for-Windows-under-Cygwin" href="#Crosscompilation-for-Windows-under-Cygwin">4.5 Crosscompilation for Windows under Cygwin</a></li>
+  </ul></li>
+</ul>
+</div>
+</div>
+
+<a name="Unix_002dlike"></a>
+<h2 class="chapter">1 Unix-like<span class="pull-right"><a class="anchor hidden-xs" href="#Unix_002dlike" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Unix_002dlike" aria-hidden="true">TOC</a></span></h2>
+
+<p>Some parts of FFmpeg cannot be built with version 2.15 of the GNU
+assembler which is still provided by a few AMD64 distributions. To
+make sure your compiler really uses the required version of gas
+after a binutils upgrade, run:
+</p>
+<div class="example">
+<pre class="example-preformatted">$(gcc -print-prog-name=as) --version
+</pre></div>
+
+<p>If not, then you should install a different compiler that has no
+hard-coded path to gas. In the worst case pass <code class="code">--disable-asm</code>
+to configure.
+</p>
+<a name="Advanced-linking-configuration"></a>
+<h3 class="section">1.1 Advanced linking configuration<span class="pull-right"><a class="anchor hidden-xs" href="#Advanced-linking-configuration" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Advanced-linking-configuration" aria-hidden="true">TOC</a></span></h3>
+
+<p>If you compiled FFmpeg libraries statically and you want to use them to
+build your own shared library, you may need to force PIC support (with
+<code class="code">--enable-pic</code> during FFmpeg configure) and add the following option
+to your project LDFLAGS:
+</p>
+<div class="example">
+<pre class="example-preformatted">-Wl,-Bsymbolic
+</pre></div>
+
+<p>If your target platform requires position independent binaries, you should
+pass the correct linking flag (e.g. <code class="code">-pie</code>) to <code class="code">--extra-ldexeflags</code>.
+</p>
+<a name="BSD"></a>
+<h3 class="section">1.2 BSD<span class="pull-right"><a class="anchor hidden-xs" href="#BSD" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-BSD" aria-hidden="true">TOC</a></span></h3>
+
+<p>BSD make will not build FFmpeg, you need to install and use GNU Make
+(<code class="command">gmake</code>).
+</p>
+<a name="g_t_0028Open_0029Solaris"></a>
+<h3 class="section">1.3 (Open)Solaris<span class="pull-right"><a class="anchor hidden-xs" href="#_0028Open_0029Solaris" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-_0028Open_0029Solaris" aria-hidden="true">TOC</a></span></h3>
+
+<p>GNU Make is required to build FFmpeg, so you have to invoke (<code class="command">gmake</code>),
+standard Solaris Make will not work. When building with a non-c99 front-end
+(gcc, generic suncc) add either <code class="code">--extra-libs=/usr/lib/values-xpg6.o</code>
+or <code class="code">--extra-libs=/usr/lib/64/values-xpg6.o</code> to the configure options
+since the libc is not c99-compliant by default. The probes performed by
+configure may raise an exception leading to the death of configure itself
+due to a bug in the system shell. Simply invoke a different shell such as
+bash directly to work around this:
+</p>
+<div class="example">
+<pre class="example-preformatted">bash ./configure
+</pre></div>
+
+<a class="anchor" id="Darwin"></a><a name="Darwin-_0028Mac-OS-X_002c-iPhone_0029"></a>
+<h3 class="section">1.4 Darwin (Mac OS X, iPhone)<span class="pull-right"><a class="anchor hidden-xs" href="#Darwin-_0028Mac-OS-X_002c-iPhone_0029" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Darwin-_0028Mac-OS-X_002c-iPhone_0029" aria-hidden="true">TOC</a></span></h3>
+
+<p>The toolchain provided with Xcode is sufficient to build the basic
+unaccelerated code.
+</p>
+<p>Mac OS X on PowerPC or ARM (iPhone) requires a preprocessor from
+<a class="url" href="https://github.com/FFmpeg/gas-preprocessor">https://github.com/FFmpeg/gas-preprocessor</a> or
+<a class="url" href="https://github.com/yuvi/gas-preprocessor">https://github.com/yuvi/gas-preprocessor</a>(currently outdated) to build the optimized
+assembly functions. Put the Perl script somewhere
+in your PATH, FFmpeg&rsquo;s configure will pick it up automatically.
+</p>
+<p>Mac OS X on amd64 and x86 requires <code class="command">nasm</code> to build most of the
+optimized assembly functions. <a class="uref" href="http://www.finkproject.org/">Fink</a>,
+<a class="uref" href="https://wiki.gentoo.org/wiki/Project:Prefix">Gentoo Prefix</a>,
+<a class="uref" href="https://mxcl.github.com/homebrew/">Homebrew</a>
+or <a class="uref" href="http://www.macports.org">MacPorts</a> can easily provide it.
+</p>
+
+<a name="DOS"></a>
+<h2 class="chapter">2 DOS<span class="pull-right"><a class="anchor hidden-xs" href="#DOS" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-DOS" aria-hidden="true">TOC</a></span></h2>
+
+<p>Using a cross-compiler is preferred for various reasons.
+<a class="url" href="http://www.delorie.com/howto/djgpp/linux-x-djgpp.html">http://www.delorie.com/howto/djgpp/linux-x-djgpp.html</a>
+</p>
+
+<a name="OS_002f2"></a>
+<h2 class="chapter">3 OS/2<span class="pull-right"><a class="anchor hidden-xs" href="#OS_002f2" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-OS_002f2" aria-hidden="true">TOC</a></span></h2>
+
+<p>For information about compiling FFmpeg on OS/2 see
+<a class="url" href="http://www.edm2.com/index.php/FFmpeg">http://www.edm2.com/index.php/FFmpeg</a>.
+</p>
+
+<a name="Windows"></a>
+<h2 class="chapter">4 Windows<span class="pull-right"><a class="anchor hidden-xs" href="#Windows" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Windows" aria-hidden="true">TOC</a></span></h2>
+
+<a name="Native-Windows-compilation-using-MinGW-or-MinGW_002dw64"></a>
+<h3 class="section">4.1 Native Windows compilation using MinGW or MinGW-w64<span class="pull-right"><a class="anchor hidden-xs" href="#Native-Windows-compilation-using-MinGW-or-MinGW_002dw64" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Native-Windows-compilation-using-MinGW-or-MinGW_002dw64" aria-hidden="true">TOC</a></span></h3>
+
+<p>FFmpeg can be built to run natively on Windows using the MinGW-w64
+toolchain. Install the latest versions of MSYS2 and MinGW-w64 from
+<a class="url" href="http://msys2.github.io/">http://msys2.github.io/</a> and/or <a class="url" href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>.
+You can find detailed installation instructions in the download section and
+the FAQ.
+</p>
+<p>Notes:
+</p>
+<ul class="itemize mark-bullet">
+<li>Building for the MSYS environment is discouraged, MSYS2 provides a full
+MinGW-w64 environment through <samp class="file">mingw64_shell.bat</samp> or
+<samp class="file">mingw32_shell.bat</samp> that should be used instead of the environment
+provided by <samp class="file">msys2_shell.bat</samp>.
+
+</li><li>Building using MSYS2 can be sped up by disabling implicit rules in the
+Makefile by calling <code class="code">make -r</code> instead of plain <code class="code">make</code>. This
+speed up is close to non-existent for normal one-off builds and is only
+noticeable when running make for a second time (for example during
+<code class="code">make install</code>).
+
+</li><li>In order to compile FFplay, you must have the MinGW development library
+of <a class="uref" href="http://www.libsdl.org/">SDL</a> and <code class="code">pkg-config</code> installed.
+
+</li><li>By using <code class="code">./configure --enable-shared</code> when configuring FFmpeg,
+you can build the FFmpeg libraries (e.g. libavutil, libavcodec,
+libavformat) as DLLs.
+
+</li></ul>
+
+<a name="Native-Windows-compilation-using-MSYS2"></a>
+<h4 class="subsection">4.1.1 Native Windows compilation using MSYS2<span class="pull-right"><a class="anchor hidden-xs" href="#Native-Windows-compilation-using-MSYS2" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Native-Windows-compilation-using-MSYS2" aria-hidden="true">TOC</a></span></h4>
+
+<p>The MSYS2 MinGW-w64 environment provides ready to use toolchains and dependencies
+through <code class="command">pacman</code>.
+</p>
+<p>Make sure to use <samp class="file">mingw64_shell.bat</samp> or <samp class="file">mingw32_shell.bat</samp> to have
+the correct MinGW-w64 environment. The default install provides shortcuts to
+them under <code class="command">MinGW-w64 Win64 Shell</code> and <code class="command">MinGW-w64 Win32 Shell</code>.
+</p>
+<div class="example">
+<pre class="example-preformatted"># normal msys2 packages
+pacman -S make pkgconf diffutils
+
+# mingw-w64 packages and toolchains
+pacman -S mingw-w64-x86_64-nasm mingw-w64-x86_64-gcc mingw-w64-x86_64-SDL2
+</pre></div>
+
+<p>To target 32 bits replace <code class="code">x86_64</code> with <code class="code">i686</code> in the command above.
+</p>
+<a name="Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows"></a>
+<h3 class="section">4.2 Microsoft Visual C++ or Intel C++ Compiler for Windows<span class="pull-right"><a class="anchor hidden-xs" href="#Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows" aria-hidden="true">TOC</a></span></h3>
+
+<p>FFmpeg can be built with MSVC 2013 or later.
+</p>
+<p>You will need the following prerequisites:
+</p>
+<ul class="itemize mark-bullet">
+<li><a class="uref" href="http://msys2.github.io/">MSYS2</a>
+</li><li><a class="uref" href="http://www.nasm.us/">NASM</a>
+(Also available via MSYS2&rsquo;s package manager.)
+</li></ul>
+
+<p>To set up a proper environment in MSYS2, you need to run <code class="code">msys_shell.bat</code> from
+the Visual Studio or Intel Compiler command prompt.
+</p>
+<p>Place <code class="code">nasm.exe</code> somewhere in your <code class="code">PATH</code>.
+</p>
+<p>Next, make sure any other headers and libs you want to use, such as zlib, are
+located in a spot that the compiler can see. Do so by modifying the <code class="code">LIB</code>
+and <code class="code">INCLUDE</code> environment variables to include the <strong class="strong">Windows-style</strong>
+paths to these directories. Alternatively, you can try to use the
+<code class="code">--extra-cflags</code>/<code class="code">--extra-ldflags</code> configure options.
+</p>
+<p>Finally, run:
+</p>
+<div class="example">
+<pre class="example-preformatted">For MSVC:
+./configure --toolchain=msvc
+
+For ICL:
+./configure --toolchain=icl
+
+make
+make install
+</pre></div>
+
+<p>If you wish to compile shared libraries, add <code class="code">--enable-shared</code> to your
+configure options. Note that due to the way MSVC and ICL handle DLL imports and
+exports, you cannot compile static and shared libraries at the same time, and
+enabling shared libraries will automatically disable the static ones.
+</p>
+<p>Notes:
+</p>
+<ul class="itemize mark-bullet">
+<li>If you wish to build with zlib support, you will have to grab a compatible
+zlib binary from somewhere, with an MSVC import lib, or if you wish to link
+statically, you can follow the instructions below to build a compatible
+<code class="code">zlib.lib</code> with MSVC. Regardless of which method you use, you must still
+follow step 3, or compilation will fail.
+<ol class="enumerate">
+<li> Grab the <a class="uref" href="http://zlib.net/">zlib sources</a>.
+</li><li> Edit <code class="code">win32/Makefile.msc</code> so that it uses -MT instead of -MD, since
+this is how FFmpeg is built as well.
+</li><li> Edit <code class="code">zconf.h</code> and remove its inclusion of <code class="code">unistd.h</code>. This gets
+erroneously included when building FFmpeg.
+</li><li> Run <code class="code">nmake -f win32/Makefile.msc</code>.
+</li><li> Move <code class="code">zlib.lib</code>, <code class="code">zconf.h</code>, and <code class="code">zlib.h</code> to somewhere MSVC
+can see.
+</li></ol>
+
+</li><li>FFmpeg has been tested with the following on i686 and x86_64:
+<ul class="itemize mark-bullet">
+<li>Visual Studio 2013 Pro and Express
+</li><li>Intel Composer XE 2013
+</li><li>Intel Composer XE 2013 SP1
+</li></ul>
+<p>Anything else is not officially supported.
+</p>
+</li></ul>
+
+<a name="Linking-to-FFmpeg-with-Microsoft-Visual-C_002b_002b"></a>
+<h4 class="subsection">4.2.1 Linking to FFmpeg with Microsoft Visual C++<span class="pull-right"><a class="anchor hidden-xs" href="#Linking-to-FFmpeg-with-Microsoft-Visual-C_002b_002b" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Linking-to-FFmpeg-with-Microsoft-Visual-C_002b_002b" aria-hidden="true">TOC</a></span></h4>
+
+<p>If you plan to link with MSVC-built static libraries, you will need
+to make sure you have <code class="code">Runtime Library</code> set to
+<code class="code">Multi-threaded (/MT)</code> in your project&rsquo;s settings.
+</p>
+<p>You will need to define <code class="code">inline</code> to something MSVC understands:
+</p><div class="example">
+<pre class="example-preformatted">#define inline __inline
+</pre></div>
+
+<p>Also note, that as stated in <strong class="strong">Microsoft Visual C++</strong>, you will need
+an MSVC-compatible <a class="uref" href="http://code.google.com/p/msinttypes/">inttypes.h</a>.
+</p>
+<p>If you plan on using import libraries created by dlltool, you must
+set <code class="code">References</code> to <code class="code">No (/OPT:NOREF)</code> under the linker optimization
+settings, otherwise the resulting binaries will fail during runtime.
+This is not required when using import libraries generated by <code class="code">lib.exe</code>.
+This issue is reported upstream at
+<a class="url" href="http://sourceware.org/bugzilla/show_bug.cgi?id=12633">http://sourceware.org/bugzilla/show_bug.cgi?id=12633</a>.
+</p>
+<p>To create import libraries that work with the <code class="code">/OPT:REF</code> option
+(which is enabled by default in Release mode), follow these steps:
+</p>
+<ol class="enumerate">
+<li> Open the <em class="emph">Visual Studio Command Prompt</em>.
+
+<p>Alternatively, in a normal command line prompt, call <samp class="file">vcvars32.bat</samp>
+which sets up the environment variables for the Visual C++ tools
+(the standard location for this file is something like
+<samp class="file">C:\Program Files (x86_\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat</samp>).
+</p>
+</li><li> Enter the <samp class="file">bin</samp> directory where the created LIB and DLL files
+are stored.
+
+</li><li> Generate new import libraries with <code class="command">lib.exe</code>:
+
+<div class="example">
+<pre class="example-preformatted">lib /machine:i386 /def:..\lib\foo-version.def  /out:foo.lib
+</pre></div>
+
+<p>Replace <code class="code">foo-version</code> and <code class="code">foo</code> with the respective library names.
+</p>
+</li></ol>
+
+<a class="anchor" id="Cross-compilation-for-Windows-with-Linux"></a><a name="Cross-compilation-for-Windows-with-Linux-1"></a>
+<h3 class="section">4.3 Cross compilation for Windows with Linux<span class="pull-right"><a class="anchor hidden-xs" href="#Cross-compilation-for-Windows-with-Linux-1" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Cross-compilation-for-Windows-with-Linux-1" aria-hidden="true">TOC</a></span></h3>
+
+<p>You must use the MinGW cross compilation tools available at
+<a class="url" href="http://www.mingw.org/">http://www.mingw.org/</a>.
+</p>
+<p>Then configure FFmpeg with the following options:
+</p><div class="example">
+<pre class="example-preformatted">./configure --target-os=mingw32 --cross-prefix=i386-mingw32msvc-
+</pre></div>
+<p>(you can change the cross-prefix according to the prefix chosen for the
+MinGW tools).
+</p>
+<p>Then you can easily test FFmpeg with <a class="uref" href="http://www.winehq.com/">Wine</a>.
+</p>
+<a name="Compilation-under-Cygwin"></a>
+<h3 class="section">4.4 Compilation under Cygwin<span class="pull-right"><a class="anchor hidden-xs" href="#Compilation-under-Cygwin" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Compilation-under-Cygwin" aria-hidden="true">TOC</a></span></h3>
+
+<p>Please use Cygwin 1.7.x as the obsolete 1.5.x Cygwin versions lack
+llrint() in its C library.
+</p>
+<p>Install your Cygwin with all the &quot;Base&quot; packages, plus the
+following &quot;Devel&quot; ones:
+</p><div class="example">
+<pre class="example-preformatted">binutils, gcc4-core, make, git, mingw-runtime, texinfo
+</pre></div>
+
+<p>In order to run FATE you will also need the following &quot;Utils&quot; packages:
+</p><div class="example">
+<pre class="example-preformatted">diffutils
+</pre></div>
+
+<p>If you want to build FFmpeg with additional libraries, download Cygwin
+&quot;Devel&quot; packages for Ogg and Vorbis from any Cygwin packages repository:
+</p><div class="example">
+<pre class="example-preformatted">libogg-devel, libvorbis-devel
+</pre></div>
+
+<p>These library packages are only available from
+<a class="uref" href="http://sourceware.org/cygwinports/">Cygwin Ports</a>:
+</p>
+<div class="example">
+<pre class="example-preformatted">libSDL-devel, libgsm-devel, libmp3lame-devel,
+speex-devel, libtheora-devel, libxvidcore-devel
+</pre></div>
+
+<p>The recommendation for x264 is to build it from source, as it evolves too
+quickly for Cygwin Ports to be up to date.
+</p>
+<a name="Crosscompilation-for-Windows-under-Cygwin"></a>
+<h3 class="section">4.5 Crosscompilation for Windows under Cygwin<span class="pull-right"><a class="anchor hidden-xs" href="#Crosscompilation-for-Windows-under-Cygwin" aria-hidden="true">#</a> <a class="anchor hidden-xs"href="#toc-Crosscompilation-for-Windows-under-Cygwin" aria-hidden="true">TOC</a></span></h3>
+
+<p>With Cygwin you can create Windows binaries that do not need the cygwin1.dll.
+</p>
+<p>Just install your Cygwin as explained before, plus these additional
+&quot;Devel&quot; packages:
+</p><div class="example">
+<pre class="example-preformatted">gcc-mingw-core, mingw-runtime, mingw-zlib
+</pre></div>
+
+<p>and add some special flags to your configure invocation.
+</p>
+<p>For a static build run
+</p><div class="example">
+<pre class="example-preformatted">./configure --target-os=mingw32 --extra-cflags=-mno-cygwin --extra-libs=-mno-cygwin
+</pre></div>
+
+<p>and for a build with shared libraries
+</p><div class="example">
+<pre class="example-preformatted">./configure --target-os=mingw32 --enable-shared --disable-static --extra-cflags=-mno-cygwin --extra-libs=-mno-cygwin
+</pre></div>
+
+      <p style="font-size: small;">
+        This document was generated using <a class="uref" href="https://www.gnu.org/software/texinfo/"><em class="emph">makeinfo</em></a>.
+      </p>
+    </div>
+  </body>
+</html>

ffmpeg-master-latest-win64-gpl/doc/style.min.css

@@ -0,0 +1,23 @@
+/*!
+The MIT License (MIT)
+
+Copyright (c) 2014 Barbara Lepage <db0company@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+ */body{background-color:#313131;color:#e6e6e6;text-align:justify}body, h1, h2, h3, h4, h5, h6{font-family:"Lucida Grande","Lucida Sans Unicode","Lucida Sans","Helvetica Neue",Helvetica,Verdana,Tahoma,sans-serif}a{color:#4cae4c}a strong{color:#e6e6e6}a:hover{color:#7fc77f}a:hover strong{color:#4cae4c}main{width:100% ! important;min-height:600px;margin:auto}h1, h2, h3, h4{font-weight:bold;text-align:left}h1, h2, h3{color:#bebebe}h1 strong, h2 strong, h3 strong{color:#e6e6e6}h4, h5, h6{color:#3c8b3c}h1{border-bottom:4px #bebebe solid;padding:20px 2%}h3{border-bottom:2px #bebebe solid;padding:15px 1%}h4{border-bottom:1px solid #e6e6e6;padding:10px 0;margin:20px 0;color:#e6e6e6}.list-group .list-group-item{background-color:#3e3e3e;border-color:black}.list-group.list-group-big .list-group-item{padding:25px}.list-group a.list-group-item{color:#7fc77f}.list-group a.list-group-item:hover{background-color:#313131;color:#4cae4c}.well{background-color:#242424;border-color:black;color:#bebebe}.well strong{color:#e6e6e6}.well code{background-color:#313131}.well hr{border-color:#3c8b3c}.well h3{margin:5px 0 15px 0;border:0;padding:0}.well a{color:#4cae4c}.well a.btn{color:white}.well small{display:block;padding:0 10px;font-style:italic}.well.example{padding-top:40px;margin-bottom:130px}.well.example pre{margin:50px;margin-bottom:30px;font-size:1.5em}.well.example .btn{margin-right:50px;margin-bottom:20px}.well.well-with-icon{min-height:136px}.well.well-with-icon .pull-right,.well.well-with-icon .pull-left{background-color:#4cae4c;color:#e6e6e6;padding:10px;border-radius:5px;margin:5px}.well.well-with-icon .pull-right{margin-left:20px}.well.well-with-icon .pull-left{margin-right:20px}a.well{display:block}a.well:hover{text-decoration:none;opacity:0.8}.info, .warning{margin:10px;padding:10px;background-color:#3e3e3e;color:#e6e6e6}.info code, .warning code{background-color:#313131}.info{border-left:10px #4cae4c solid}.warning{border-left:10px #ae4c4c solid}.with-icon{padding:30px}.with-icon .pull-left{padding-right:30px}.with-icon .pull-right{padding-left:30px}dd{margin-left:20px}code{background-color:#242424;color:#7fc77f;display:inline-block;margin:5px}.table{margin:20px 0;border-radius:4px}.table th,.table td,.table tr{border:1px solid #171717}.table tr th{background-color:#3e3e3e;border-bottom:2px solid #e6e6e6}.table tr:nth-child(odd){background-color:#242424}#sidebar-wrapper, .navbar{background-color:#171717;overflow-x:hidden}#sidebar-wrapper .sidebar-brand img,#sidebar-wrapper .navbar-brand img, .navbar .sidebar-brand img, .navbar .navbar-brand img{opacity:0.6;margin-right:8px}#sidebar-wrapper .sidebar-brand:hover,#sidebar-wrapper .navbar-brand:hover, .navbar .sidebar-brand:hover, .navbar .navbar-brand:hover{color:#fff}#sidebar-wrapper .sidebar-brand:hover img,#sidebar-wrapper .navbar-brand:hover img, .navbar .sidebar-brand:hover img, .navbar .navbar-brand:hover img{opacity:1}#sidebar-wrapper .sidebar-nav li ul, .navbar .sidebar-nav li ul{list-style-type:none;padding:0}#sidebar-wrapper .sidebar-nav li ul li, .navbar .sidebar-nav li ul li{line-height:20px}#sidebar-wrapper .sidebar-nav li ul li a, .navbar .sidebar-nav li ul li a{padding-left:20px}.content-header{height:auto;background-color:#242424}.content-header h1{color:#e6e6e6;display:block;margin:0;margin-bottom:20px;line-height:normal;border-bottom:none}#download h4, #index h4{margin-top:180px}#download h4.first, #index h4.first{margin-top:20px}#download h4.first small, #index h4.first small{color:inherit;font-size:1em}#download .btn-download-wrapper, #index .btn-download-wrapper{text-align:center;margin:160px auto}#download .btn-download-wrapper .btn, #index .btn-download-wrapper .btn{font-size:3em;padding:3%;display:inline-block;margin-bottom:5px}#download .btn-download-wrapper small, #index .btn-download-wrapper small{display:block;font-size:0.4em}#download h2.description, #index h2.description{color:#e6e6e6;font-size:2em;font-weight:bold;margin:120px 50px;line-height:2em}#download h2.description .label, #index h2.description .label{font-size:0.5em}#download .btn-download-wrapper{margin:40px auto}#download .os-selector{text-align:center;color:#e6e6e6;margin:30px 0}#download .os-selector a.btn-build{color:#e6e6e6;display:block;padding:20px;border-radius:2px}#download .os-selector .btn-build[href="#build-linux"]{background-color:#e43}#download .os-selector .btn-build[href="#build-linux"]:hover{color:#e43;background-color:#e6e6e6}#download .os-selector .btn-build[href="#build-windows"]{background-color:#06a}#download .os-selector .btn-build[href="#build-windows"]:hover{color:#06a;background-color:#e6e6e6}#download .os-selector .btn-build[href="#build-mac"]{background-color:darkgrey}#download .os-selector .btn-build[href="#build-mac"]:hover{color:darkgrey;background-color:#e6e6e6}#download .os-selector .tab-content{margin-top:20px}#download .os-selector #build-linux h3{color:#e43}#download .os-selector #build-windows h3{color:#06a}#download .os-selector #build-mac h3{color:darkgrey}footer{background-color:#242424;border-top:1px #101010 solid;padding:20px 0%}footer a{display:block}footer img[alt="FFmpeg"]{width:50%;display:block;margin:auto}.example.user-good pre{color:#bfbfbf;border:1px solid #357735;border-left:10px solid #357735;background-color:#242424}.example.user-bad pre{color:#bfbfbf;border:1px solid #ae4c4c;border-left:10px solid #ae4c4c;background-color:#242424}

index.html

@@ -0,0 +1,615 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Audio Classification Workstation</title>
+    <script src="https://cdn.tailwindcss.com"></script>
+    <style>
+        /* Custom scrollbar for history (WebKit browsers) */
+        .history-scrollbar::-webkit-scrollbar {
+            width: 8px;
+        }
+        .history-scrollbar::-webkit-scrollbar-track {
+            background: #1f2937; /* bg-gray-800 */
+        }
+        .history-scrollbar::-webkit-scrollbar-thumb {
+            background: #4b5563; /* bg-gray-600 */
+            border-radius: 4px;
+        }
+        .history-scrollbar::-webkit-scrollbar-thumb:hover {
+            background: #6b7280; /* bg-gray-500 */
+        }
+        /* Icon styling */
+        .icon {
+            width: 1.25rem; /* 20px */
+            height: 1.25rem; /* 20px */
+            display: inline-block;
+            vertical-align: middle;
+        }
+        .status-dot {
+            width: 8px;
+            height: 8px;
+            border-radius: 50%;
+            display: inline-block;
+            margin-right: 0.5rem;
+        }
+        .tag {
+            display: inline-block;
+            background-color: #374151; /* bg-gray-700 */
+            color: #d1d5db; /* text-gray-300 */
+            padding: 0.25rem 0.75rem;
+            border-radius: 9999px; /* rounded-full */
+            font-size: 0.75rem; /* text-xs */
+            margin: 0.25rem;
+        }
+    </style>
+</head>
+<body class="bg-gray-900 text-gray-200 min-h-screen flex flex-col">
+
+    <!-- Header -->
+    <header class="bg-gray-800 shadow-md">
+        <div class="container mx-auto px-6 py-3 flex justify-between items-center">
+            <h1 class="text-xl font-semibold text-white">Audio Classification Workstation</h1>
+            <div class="flex items-center space-x-3">
+                <button title="Help" class="text-gray-400 hover:text-white">
+                    <svg class="icon" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
+                        <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M8.228 9c.549-1.165 2.03-2 3.772-2 2.21 0 4 1.79 4 4s-1.79 4-4 4c-1.742 0-3.223-.835-3.772-2M9 12l3 3m0 0l3-3m-3 3v6m-1.732-8.066A8.969 8.969 0 015.34 6.309m13.42 2.592a8.969 8.969 0 01-2.888 2.592m0 0A8.968 8.968 0 0112 21c-2.485 0-4.733-.985-6.364-2.592m12.728 0A8.969 8.969 0 0121.66 9.63m-16.022-.098A8.969 8.969 0 013.34 6.309m1.991 11.808A8.969 8.969 0 015.34 17.69m13.42-2.592a8.969 8.969 0 012.888-2.592M9 12a3 3 0 11-6 0 3 3 0 016 0z" />
+                    </svg>
+                </button>
+                <button title="Settings" class="text-gray-400 hover:text-white">
+                    <svg class="icon" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
+                        <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M10.325 4.317c.426-1.756 2.924-1.756 3.35 0a1.724 1.724 0 002.573 1.066c1.543-.94 3.31.826 2.37 2.37a1.724 1.724 0 001.065 2.572c1.756.426 1.756 2.924 0 3.35a1.724 1.724 0 00-1.066 2.573c.94 1.543-.826 3.31-2.37 2.37a1.724 1.724 0 00-2.572 1.065c-.426 1.756-2.924 1.756-3.35 0a1.724 1.724 0 00-2.573-1.066c-1.543.94-3.31-.826-2.37-2.37a1.724 1.724 0 00-1.065-2.572c-1.756-.426-1.756-2.924 0-3.35a1.724 1.724 0 001.066-2.573c-.94-1.543.826-3.31 2.37-2.37.996.608 2.296.07 2.572-1.065z" />
+                        <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M15 12a3 3 0 11-6 0 3 3 0 016 0z" />
+                    </svg>
+                </button>
+            </div>
+        </div>
+    </header>
+
+    <!-- Main Content Area -->
+    <main class="flex-grow container mx-auto px-6 py-4 grid grid-cols-1 md:grid-cols-3 gap-6">
+        
+        <!-- Left Column -->
+        <div class="md:col-span-1 space-y-6">
+            <!-- Audio Input -->
+            <div class="bg-gray-800 p-5 rounded-lg shadow-lg">
+                <h2 class="text-lg font-semibold text-gray-100 mb-4">Audio Input</h2>
+                <div class="space-y-3">
+                    <div>
+                        <label for="audioSource" class="block text-sm font-medium text-gray-300 mb-1">Input Device</label>
+                        <select id="audioSource" name="audioSource" class="w-full bg-gray-700 border border-gray-600 text-gray-200 rounded-md p-2 focus:ring-green-500 focus:border-green-500 text-sm">
+                            <option>Default Microphone</option>
+                            <!-- More options could be populated by JS -->
+                        </select>
+                    </div>
+                    <div>
+                        <label class="block text-sm font-medium text-gray-300 mb-1">Audio Level</label>
+                        <div class="w-full bg-gray-700 rounded-full h-2.5">
+                            <div class="bg-green-500 h-2.5 rounded-full" style="width: 45%"></div> <!-- Placeholder level -->
+                        </div>
+                    </div>
+                    <button id="toggleRecordButton" class="w-full bg-gradient-to-br from-green-500 to-green-700 hover:from-green-600 hover:to-green-800 text-white font-bold py-2.5 px-4 rounded-lg shadow-md transition duration-150 ease-in-out transform hover:scale-105 focus:outline-none focus:ring-2 focus:ring-green-500 focus:ring-offset-2 focus:ring-offset-gray-800 flex items-center justify-center space-x-2">
+                        <svg class="icon" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
+                            <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M19 11a7 7 0 01-7 7m0 0a7 7 0 01-7-7m7 7v4m0 0H8m4 0h4m-4-8a3 3 0 01-3-3V5a3 3 0 116 0v6a3 3 0 01-3 3z" />
+                        </svg>
+                        <span>Start Recording</span>
+                    </button>
+                    <p class="text-xs text-gray-400 text-center">Recording Time: <span id="timer">0s</span></p>
+                </div>
+            </div>
+
+            <!-- Upload Audio File -->
+            <div class="bg-gray-800 p-5 rounded-lg shadow-lg">
+                <h2 class="text-lg font-semibold text-gray-100 mb-4">Upload Audio File</h2>
+                <div class="space-y-3">
+                    <div class="border-2 border-dashed border-gray-600 rounded-lg p-6 text-center cursor-pointer hover:border-gray-500">
+                        <svg class="icon mx-auto mb-2 text-gray-500" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
+                            <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M7 16a4 4 0 01-.88-7.903A5 5 0 1115.9 6L16 6a5 5 0 011 9.9M15 13l-3-3m0 0l-3 3m3-3v12" />
+                        </svg>
+                        <p class="text-sm text-gray-400">Drag & drop an audio file or</p>
+                        <input type="file" id="audioFile" accept="audio/*" class="hidden">
+                        <button id="browseButton" class="mt-2 text-sm text-green-400 hover:text-green-300 font-semibold">Browse Files</button>
+                        <p class="text-xs text-gray-500 mt-1">Supported formats: MP3, WAV, OGG, FLAC</p>
+                    </div>
+                    <button id="uploadButton" class="w-full bg-gradient-to-br from-blue-500 to-blue-700 hover:from-blue-600 hover:to-blue-800 text-white font-bold py-2.5 px-4 rounded-lg shadow-md transition duration-150 ease-in-out transform hover:scale-105 focus:outline-none focus:ring-2 focus:ring-blue-500 focus:ring-offset-2 focus:ring-offset-gray-800 flex items-center justify-center space-x-2">
+                        <svg class="icon" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor" style="width:18px; height:18px;">
+                           <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M4 16v1a3 3 0 003 3h10a3 3 0 003-3v-1m-4-8l-4-4m0 0L8 8m4-4v12" />
+                        </svg>
+                        <span>Upload and Recognize</span>
+                    </button>
+                </div>
+            </div>
+
+            <!-- Model Information -->
+            <div class="bg-gray-800 p-5 rounded-lg shadow-lg">
+                <h2 class="text-lg font-semibold text-gray-100 mb-4">Model Information</h2>
+                <div class="space-y-2 text-sm">
+                    <p><strong class="text-gray-300">Current Model:</strong> <span class="text-gray-400">Deep Learning Model</span></p>
+                    <div class="flex flex-wrap items-center">
+                        <strong class="text-gray-300 mr-2">Supported Categories:</strong>
+                        <span class="tag">Music</span><span class="tag">Humming</span><span class="tag">Custom Audio</span>
+                    </div>
+                    <p><strong class="text-gray-300">Status:</strong> <span class="status-dot bg-green-500"></span><span class="text-green-400">Ready for processing</span></p>
+                    <button class="mt-2 text-sm text-green-400 hover:text-green-300 font-semibold">View Model Details</button>
+                </div>
+            </div>
+        </div>
+
+        <!-- Middle Column -->
+        <div class="md:col-span-1 bg-gray-800 p-5 rounded-lg shadow-lg flex flex-col">
+            <h2 class="text-lg font-semibold text-gray-100 mb-4 flex items-center">
+                <svg class="icon mr-2" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
+                    <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M9 19V6l12-3v13M9 19c0 1.105-1.343 2-3 2s-3-.895-3-2 1.343-2 3-2 3 .895 3 2zm12-3c0 1.105-1.343 2-3 2s-3-.895-3-2 1.343-2 3-2 3 .895 3 2zM9 10l12-3" />
+                </svg>
+                Classification Results
+                <span id="classificationStatus" class="ml-auto text-xs py-1 px-2.5 rounded-full bg-gray-700 text-gray-300">Ready</span>
+            </h2>
+            <div id="results" class="flex-grow bg-gray-700 p-4 rounded-md min-h-[200px] text-gray-300 overflow-auto">
+                <p class="italic text-gray-400">Record or upload audio to start classification.</p>
+            </div>
+        </div>
+
+        <!-- Right Column -->
+        <div class="md:col-span-1 bg-gray-800 p-5 rounded-lg shadow-lg flex flex-col">
+            <div class="flex justify-between items-center mb-4">
+                <h2 class="text-lg font-semibold text-gray-100">Chat with AI</h2>
+                <button title="Clear Chat" id="clearChatButton" class="text-gray-400 hover:text-white">
+                    <svg class="icon" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
+                        <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M19 7l-.867 12.142A2 2 0 0116.138 21H7.862a2 2 0 01-1.995-1.858L5 7m5 4v6m4-6v6m1-10V4a1 1 0 00-1-1h-4a1 1 0 00-1 1v3M4 7h16" />
+                    </svg>
+                </button>
+            </div>
+            <div id="chatContainer" class="flex-grow space-y-3 overflow-y-auto history-scrollbar pr-1 min-h-[200px] mb-4">
+                <div class="text-center text-gray-500 pt-10">
+                    <svg class="icon mx-auto mb-2 text-gray-500 w-10 h-10" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
+                        <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M8 10h.01M12 10h.01M16 10h.01M9 16H5a2 2 0 01-2-2V6a2 2 0 012-2h14a2 2 0 012 2v8a2 2 0 01-2 2h-5l-5 5v-5z" />
+                    </svg>
+                    <p>Start a conversation about the classification results.</p>
+                </div>
+            </div>
+            <div class="flex items-center space-x-2">
+                <input type="text" id="chatInput" placeholder="Type your message..." class="flex-grow bg-gray-700 border border-gray-600 text-gray-200 rounded-md p-2 focus:ring-green-500 focus:border-green-500 text-sm">
+                <button id="sendMessageButton" class="p-2 text-gray-400 hover:text-white bg-gray-700 rounded-md hover:bg-gray-600">
+                    <svg class="icon" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
+                        <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 19l9 2-9-18-9 18 9-2zm0 0v-8" />
+                    </svg>
+                </button>
+            </div>
+        </div>
+    </main>
+
+    <script>
+        // DOM Elements
+        const toggleRecordButton = document.getElementById('toggleRecordButton');
+        const timerDisplay = document.getElementById('timer');
+        const resultsDiv = document.getElementById('results');
+        const classificationStatus = document.getElementById('classificationStatus');
+        
+        const audioFileInput = document.getElementById('audioFile');
+        const uploadButton = document.getElementById('uploadButton');
+        const browseButton = document.getElementById('browseButton');
+
+        const chatContainer = document.getElementById('chatContainer');
+        const chatInput = document.getElementById('chatInput');
+        const sendMessageButton = document.getElementById('sendMessageButton');
+        const clearChatButton = document.getElementById('clearChatButton');
+
+        // Recording state and logic
+        let mediaRecorder;
+        let audioChunks = [];
+        let recognitionIntervalMs = 5000; 
+        let periodicRecognitionTimer;
+        let recordingStartTime;
+        let durationUpdateTimer;
+        let isRecording = false;
+
+        let currentClassificationResult = null;
+
+        // --- Existing Helper Functions (Slightly Modified) ---
+        function updateTimerDisplay() {
+            if (!recordingStartTime) return;
+            const secondsElapsed = Math.floor((Date.now() - recordingStartTime) / 1000);
+            timerDisplay.textContent = String(secondsElapsed) + 's';
+        }
+
+        function setButtonState(recording) {
+            isRecording = recording;
+            const iconSVG = toggleRecordButton.querySelector('svg');
+            const textSpan = toggleRecordButton.querySelector('span');
+
+            if (isRecording) {
+                toggleRecordButton.classList.remove('from-green-500', 'to-green-700', 'hover:from-green-600', 'hover:to-green-800', 'focus:ring-green-500');
+                toggleRecordButton.classList.add('from-red-500', 'to-red-700', 'hover:from-red-600', 'hover:to-red-800', 'focus:ring-red-500');
+                textSpan.textContent = 'Stop Recording';
+                iconSVG.innerHTML = '<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M21 12v0a9 9 0 01-9 9m0-9a9 9 0 00-9 9m9-9V3m0 0a9 9 0 00-9 9m9-9h1.5M3 12h1.5m15 0V3m0 0a9 9 0 00-9-9m9 9c1.657 0 3-4.03 3-9" transform="matrix(1 0 0 1 0 0) rotate(0 12 12)" style="display: none;"></path><path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M6 18L18 6M6 6l12 12" transform="matrix(1 0 0 1 0 0) rotate(0 12 12)"></path>'; // Stop Icon (X)
+                resultsDiv.innerHTML = '<p class="italic text-gray-400">Listening...</p>';
+                classificationStatus.textContent = 'Listening';
+                classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-yellow-600 text-yellow-100';
+                
+                recordingStartTime = Date.now();
+                updateTimerDisplay();
+                durationUpdateTimer = setInterval(updateTimerDisplay, 1000);
+            } else {
+                toggleRecordButton.classList.remove('from-red-500', 'to-red-700', 'hover:from-red-600', 'hover:to-red-800', 'focus:ring-red-500');
+                toggleRecordButton.classList.add('from-green-500', 'to-green-700', 'hover:from-green-600', 'hover:to-green-800', 'focus:ring-green-500');
+                textSpan.textContent = 'Start Recording';
+                iconSVG.innerHTML = '<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M19 11a7 7 0 01-7 7m0 0a7 7 0 01-7-7m7 7v4m0 0H8m4 0h4m-4-8a3 3 0 01-3-3V5a3 3 0 116 0v6a3 3 0 01-3 3z" />'; // Mic Icon
+                
+                clearInterval(durationUpdateTimer);
+                recordingStartTime = null;
+                timerDisplay.textContent = '0s';
+                if (periodicRecognitionTimer) clearInterval(periodicRecognitionTimer);
+            }
+        }
+        
+        async function startLiveRecording() {
+            if (isRecording) return; // Should not happen if button state is managed
+            try {
+                const stream = await navigator.mediaDevices.getUserMedia({ audio: true });
+                setButtonState(true);
+
+                const options = { 
+                    mimeType: 'audio/webm;codecs=opus',
+                    audioBitsPerSecond: 128000 
+                };
+                try {
+                    mediaRecorder = new MediaRecorder(stream, options);
+                } catch (e1) {
+                    console.warn('Failed to create MediaRecorder with audio/webm;codecs=opus: ' + e1.message + '. Trying with default.');
+                    options.mimeType = ''; 
+                    mediaRecorder = new MediaRecorder(stream, options);
+                }
+                console.log('Using mimeType:', mediaRecorder.mimeType);
+
+                audioChunks = []; 
+                mediaRecorder.addEventListener('dataavailable', event => {
+                    audioChunks.push(event.data);
+                });
+
+                mediaRecorder.addEventListener('stop', async () => {
+                    stream.getTracks().forEach(track => track.stop());
+                    setButtonState(false); // Reset button state
+                    
+                    if (audioChunks.length > 0) {
+                        await sendAudioChunkForRecognition(true); // isFinalChunk = true
+                    } else {
+                        resultsDiv.innerHTML = '<p class="italic text-gray-400">Recording stopped. No audio data.</p>';
+                        classificationStatus.textContent = 'Ready';
+                        classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-gray-700 text-gray-300';
+                    }
+                });
+
+                mediaRecorder.start(); 
+                
+                // Send first chunk after a short delay
+                setTimeout(async () => {
+                     if (mediaRecorder.state === 'recording') await sendAudioChunkForRecognition();
+                }, 2000); 
+
+                // Setup periodic recognition
+                periodicRecognitionTimer = setInterval(async () => {
+                    if (mediaRecorder.state === 'recording' && audioChunks.length > 0) {
+                        await sendAudioChunkForRecognition();
+                    }
+                }, recognitionIntervalMs);
+
+            } catch (err) {
+                console.error('Error accessing microphone:', err);
+                resultsDiv.innerHTML = '<p class="text-red-400">Could not access microphone. Please ensure permission is granted.</p>';
+                classificationStatus.textContent = 'Error';
+                classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-red-700 text-red-100';
+                setButtonState(false); // Reset button state on error
+            }
+        }
+
+        function stopLiveRecording() {
+            if (mediaRecorder && mediaRecorder.state === 'recording') {
+                mediaRecorder.stop();
+            }
+            // setButtonState(false) is called by mediaRecorder 'stop' event listener
+            if (periodicRecognitionTimer) clearInterval(periodicRecognitionTimer);
+            if (durationUpdateTimer) clearInterval(durationUpdateTimer);
+            // recordingStartTime will be reset by setButtonState via mediaRecorder 'stop'
+        }
+
+        toggleRecordButton.addEventListener('click', () => {
+            if (!isRecording) {
+                startLiveRecording();
+            } else {
+                stopLiveRecording();
+            }
+        });
+        
+        async function sendAudioChunkForRecognition(isFinalChunk = false) {
+            if (audioChunks.length === 0 && !isFinalChunk) return;
+
+            const audioBlob = new Blob(audioChunks, { type: mediaRecorder.mimeType || 'audio/webm;codecs=opus' });
+            let tempAudioChunks = [...audioChunks]; 
+            audioChunks = []; 
+
+            if (!isFinalChunk && tempAudioChunks.length === 0) return; 
+
+            // Update status for intermediate chunks if not already showing success
+            if (!isFinalChunk && !resultsDiv.querySelector('.text-green-400')) {
+               resultsDiv.innerHTML = '<p class="italic text-gray-400">Processing audio...</p>';
+               classificationStatus.textContent = 'Processing';
+               classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-blue-600 text-blue-100';
+            }
+            
+            const formData = new FormData();
+            const fileExtension = (mediaRecorder.mimeType.split('/')[1]?.split(';')[0]) || 'webm';
+            formData.append('file', audioBlob, 'live_audio_chunk.' + fileExtension);
+
+            try {
+                const response = await fetch('/recognize-live-chunk/', {
+                    method: 'POST',
+                    body: formData,
+                });
+                const result = await response.json();
+                displayCombinedResults(result, isFinalChunk);
+                
+            } catch (error) {
+                console.error('Error sending audio chunk:', error);
+                resultsDiv.innerHTML = 
+                    '<p class="text-red-400">Error sending audio data.</p>' +
+                    '<p class="text-xs text-gray-500">' + error.message + '</p>';
+                classificationStatus.textContent = 'Error';
+                classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-red-700 text-red-100';
+            }
+        }
+
+        function displayCombinedResults(result, isFinalChunk) {
+            let html = '';
+            
+            if (result.success) {
+                currentClassificationResult = result; // Store the current classification result
+                
+                if (result.type === 'music') {
+                    // Display song recognition results
+                    const musicResult = result.music_result;
+                    html += '<div class="mb-4">';
+                    html += '<p class="text-green-400 font-semibold text-lg mb-2">Song Match Found!</p>';
+                    if (musicResult.song_name) {
+                        html += '<div class="mb-1"><strong class="text-gray-300">Title:</strong> <span class="text-gray-100">' + musicResult.song_name + '</span></div>';
+                    }
+                    if (musicResult.artists) {
+                        html += '<div class="mb-1"><strong class="text-gray-300">Artists:</strong> <span class="text-gray-100">' + musicResult.artists + '</span></div>';
+                    }
+                    if (musicResult.album) {
+                        html += '<div class="mb-1"><strong class="text-gray-300">Album:</strong> <span class="text-gray-100">' + musicResult.album + '</span></div>';
+                    }
+                    html += '</div>';
+                    
+                    // Add initial AI message about the song
+                    addAIMessage(`I've detected a song! It's "${musicResult.song_name}" by ${musicResult.artists}. Would you like to know more about this song or artist?`);
+                    
+                    classificationStatus.textContent = 'Music Found';
+                    classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-green-600 text-green-100';
+                } else if (result.type === 'vehicle') {
+                    // Display vehicle classification results with model and make
+                    const vehicleResult = result.vehicle_result;
+                    const vehicleInfo = {
+                        'Car': {
+                            make: 'Toyota',
+                            model: 'Camry'
+                        },
+                        'Truck': {
+                            make: 'Ford',
+                            model: 'F-150'
+                        }
+                    };
+                    
+                    const info = vehicleInfo[vehicleResult.vehicle_type] || { make: 'Unknown', model: 'Unknown' };
+                    
+                    html += '<div class="mb-4">';
+                    html += '<p class="text-purple-400 font-semibold text-lg mb-2">Vehicle Detected:</p>';
+                    html += '<div class="bg-gray-700 p-4 rounded-lg">';
+                    html += '<div class="mb-2"><span class="text-gray-100 text-xl font-medium">' + vehicleResult.vehicle_type + '</span></div>';
+                    html += '<div class="text-gray-300 text-sm">';
+                    html += '<div class="mb-1"><strong>Make:</strong> ' + info.make + '</div>';
+                    html += '<div><strong>Model:</strong> ' + info.model + '</div>';
+                    html += '</div></div></div>';
+                    
+                    // Add initial AI message about the vehicle
+                    addAIMessage(`I've detected a ${info.make} ${info.model} ${vehicleResult.vehicle_type.toLowerCase()}. Would you like to know more about this vehicle?`);
+                    
+                    classificationStatus.textContent = 'Vehicle Detected';
+                    classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-purple-600 text-purple-100';
+                } else if (result.type === 'sound') {
+                    // Display only the top YAMNet classification result
+                    const soundResult = result.sound_result;
+                    const [topLabel] = soundResult.top_classes[0];
+                    
+                    html += '<div class="mb-4">';
+                    html += '<p class="text-blue-400 font-semibold text-lg mb-2">Sound Classification:</p>';
+                    html += '<div class="bg-gray-700 p-4 rounded-lg">';
+                    html += '<span class="text-gray-100 text-xl font-medium">' + topLabel + '</span>';
+                    html += '</div></div>';
+                    
+                    // Add initial AI message about the sound
+                    addAIMessage(`I've detected a ${topLabel} sound. Would you like to know more about this type of sound?`);
+                    
+                    classificationStatus.textContent = 'Sound Classified';
+                    classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-blue-600 text-blue-100';
+                }
+            } else {
+                // No results from any classification
+                if (isFinalChunk) {
+                    html = '<p class="italic text-gray-400">Recording stopped. No matches found.</p>';
+                    classificationStatus.textContent = 'No Match';
+                    classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-yellow-600 text-yellow-100';
+                } else if (mediaRecorder && mediaRecorder.state === 'recording') {
+                    const isCurrentlyDisplayingSuccess = resultsDiv.querySelector('.text-green-400, .text-blue-400, .text-purple-400');
+                    if (!isCurrentlyDisplayingSuccess) {
+                        html = '<p class="italic text-gray-400">No match yet. Keep recording...</p>';
+                        classificationStatus.textContent = 'Listening';
+                        classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-yellow-600 text-yellow-100';
+                    }
+                }
+            }
+            
+            resultsDiv.innerHTML = html;
+        }
+
+        // Chat functionality
+        function addUserMessage(message) {
+            const messageDiv = document.createElement('div');
+            messageDiv.className = 'bg-blue-600 p-3 rounded-lg ml-4';
+            messageDiv.innerHTML = `<p class="text-white">${message}</p>`;
+            chatContainer.appendChild(messageDiv);
+            chatContainer.scrollTop = chatContainer.scrollHeight;
+        }
+
+        function addAIMessage(message) {
+            const messageDiv = document.createElement('div');
+            messageDiv.className = 'bg-gray-700 p-3 rounded-lg mr-4';
+            messageDiv.innerHTML = `<p class="text-gray-100">${message}</p>`;
+            chatContainer.appendChild(messageDiv);
+            chatContainer.scrollTop = chatContainer.scrollHeight;
+        }
+
+        async function sendMessageToMistral(message) {
+            if (!currentClassificationResult) {
+                addAIMessage("I don't have any classification results to discuss yet. Please record or upload some audio first.");
+                return;
+            }
+
+            let systemPrompt = "You are a helpful assistant discussing audio classification results. ";
+            
+            if (currentClassificationResult.type === 'music') {
+                const music = currentClassificationResult.music_result;
+                systemPrompt += `The user is asking about a song: "${music.song_name}" by ${music.artists} from the album "${music.album}". `;
+            } else if (currentClassificationResult.type === 'vehicle') {
+                const vehicle = currentClassificationResult.vehicle_result;
+                systemPrompt += `The user is asking about a ${vehicle.vehicle_type}. `;
+            } else if (currentClassificationResult.type === 'sound') {
+                const sound = currentClassificationResult.sound_result;
+                systemPrompt += `The user is asking about a sound classified as "${sound.top_classes[0][0]}". `;
+            }
+
+            try {
+                const response = await fetch('/chat-with-mistral/', {
+                    method: 'POST',
+                    headers: {
+                        'Content-Type': 'application/json',
+                    },
+                    body: JSON.stringify({
+                        system_prompt: systemPrompt,
+                        user_message: message
+                    })
+                });
+
+                const data = await response.json();
+                if (data.success) {
+                    addAIMessage(data.response);
+                } else {
+                    addAIMessage("I'm sorry, I encountered an error while processing your request.");
+                }
+            } catch (error) {
+                console.error('Error sending message to Mistral:', error);
+                addAIMessage("I'm sorry, I encountered an error while processing your request.");
+            }
+        }
+
+        sendMessageButton.addEventListener('click', async () => {
+            const message = chatInput.value.trim();
+            if (message) {
+                addUserMessage(message);
+                chatInput.value = '';
+                await sendMessageToMistral(message);
+            }
+        });
+
+        chatInput.addEventListener('keypress', (e) => {
+            if (e.key === 'Enter') {
+                sendMessageButton.click();
+            }
+        });
+
+        clearChatButton.addEventListener('click', () => {
+            chatContainer.innerHTML = `
+                <div class="text-center text-gray-500 pt-10">
+                    <svg class="icon mx-auto mb-2 text-gray-500 w-10 h-10" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
+                        <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M8 10h.01M12 10h.01M16 10h.01M9 16H5a2 2 0 01-2-2V6a2 2 0 012-2h14a2 2 0 012 2v8a2 2 0 01-2 2h-5l-5 5v-5z" />
+                    </svg>
+                    <p>Start a conversation about the classification results.</p>
+                </div>`;
+        });
+
+        // --- File Upload Logic (Slightly Modified) ---
+        browseButton.addEventListener('click', () => audioFileInput.click());
+
+        audioFileInput.addEventListener('change', () => {
+            if (audioFileInput.files.length > 0) {
+                // Optionally display file name or trigger upload automatically
+                // For now, user still needs to click "Upload and Recognize"
+                console.log("File selected:", audioFileInput.files[0].name);
+            }
+        });
+
+        uploadButton.addEventListener('click', async () => {
+            const file = audioFileInput.files[0];
+            if (!file) {
+                resultsDiv.innerHTML = '<p class="text-red-400">Please select an audio file first.</p>';
+                classificationStatus.textContent = 'Error';
+                classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-red-700 text-red-100';
+                return;
+            }
+
+            resultsDiv.innerHTML = '<p class="text-gray-400 italic">Uploading and analyzing...</p>';
+            classificationStatus.textContent = 'Uploading';
+            classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-blue-600 text-blue-100';
+            const formData = new FormData();
+            formData.append('file', file);
+
+            try {
+                const response = await fetch('/classify/', {
+                    method: 'POST',
+                    body: formData
+                });
+
+                const result = await response.json();
+                displayCombinedResults(result, true);
+
+            } catch (error) {
+                console.error("Error during file upload:", error);
+                resultsDiv.innerHTML = '<p class="text-red-400">Error during file upload. Check console for details.</p>';
+                classificationStatus.textContent = 'Error';
+                classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-red-700 text-red-100';
+            }
+        });
+
+        function displayFileUploadResult(data) { 
+            resultsDiv.innerHTML = ''; 
+
+            if (data.success === true) {
+                const title = data.song_name || 'Unknown Title';
+                const artists = data.artists || 'Unknown Artist';
+                const album = data.album || 'Unknown Album';
+
+                resultsDiv.innerHTML =
+                    '<h3 class="text-xl font-semibold text-green-400 mb-2">Song Recognized!</h3>' +
+                    '<p class="mb-1"><strong class="text-gray-300">Title:</strong> <span class="text-gray-100">' + title + '</span></p>' +
+                    '<p class="mb-1"><strong class="text-gray-300">Artist(s):</strong> <span class="text-gray-100">' + artists + '</span></p>' +
+                    '<p class="mb-1"><strong class="text-gray-300">Album:</strong> <span class="text-gray-100">' + album + '</span></p>';
+                classificationStatus.textContent = 'Success';
+                classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-green-600 text-green-100';
+
+            } else { 
+                let errorMessage = data.message || "Could not recognize the song.";
+                resultsDiv.innerHTML = '<p class="text-yellow-400">' + errorMessage + '</p>';
+                
+                if (data.raw_acr_response) {
+                    resultsDiv.innerHTML += '<p class="text-xs text-gray-500 mt-2">Details:</p><pre class="text-xs text-gray-600 bg-gray-800 p-2 rounded">' + JSON.stringify(data.raw_acr_response, null, 2) + '</pre>';
+                } else {
+                     resultsDiv.innerHTML += '<p class="text-xs text-gray-500 mt-2">Full Response:</p><pre class="text-xs text-gray-600 bg-gray-800 p-2 rounded">' + JSON.stringify(data, null, 2) + '</pre>';
+                }
+                classificationStatus.textContent = 'No Match';
+                classificationStatus.className = 'ml-auto text-xs py-1 px-2.5 rounded-full bg-yellow-600 text-yellow-100';
+            }
+        }
+
+    </script>
+</body>
+</html> 

main.py

@@ -0,0 +1,500 @@
+import json
+import logging
+import os
+import shutil
+import tempfile
+from pathlib import Path
+
+import librosa
+import numpy as np
+import requests
+import tensorflow as tf
+import tensorflow_hub as hub
+from acrcloud.recognizer import ACRCloudRecognizer
+from fastapi import FastAPI, File, Form, HTTPException, Request, UploadFile
+from fastapi.middleware.cors import CORSMiddleware
+from fastapi.responses import HTMLResponse
+from fastapi.templating import Jinja2Templates
+from pydantic import BaseModel
+from pydub import AudioSegment
+from tensorflow.keras.models import load_model
+
+app = FastAPI()
+
+# Add CORS middleware
+app.add_middleware(
+    CORSMiddleware,
+    allow_origins=["*"],
+    allow_credentials=True,
+    allow_methods=["*"],
+    allow_headers=["*"],
+)
+
+templates = Jinja2Templates(directory=".")
+model = load_model('./models/neural_networks.h5')
+# ACRCloud Configuration using SDK
+ACRCLOUD_CONFIG = {
+    'host': 'identify-ap-southeast-1.acrcloud.com',
+    'access_key': 'c529996b7457352ca72e2ccb1fcbc4dd',
+    'access_secret': 'MQitmw327GTfkoLhCzk90Uwcf2dL0DGhUvQvQwS0',
+    'timeout': 1  # seconds
+}
+acr_recognizer = ACRCloudRecognizer(ACRCLOUD_CONFIG) 
+
+# Load YAMNet model and labels
+yamnet_model_handle = 'https://tfhub.dev/google/yamnet/1'
+yamnet_model = hub.load(yamnet_model_handle)
+
+with open("yamnet_class_map.csv", "r") as f:
+    yamnet_classes = [line.strip().split(",")[2] for line in f.readlines()[1:]]
+
+# # Set up ffmpeg path
+# FFMPEG_PATH = os.path.join(os.path.dirname(os.path.abspath(__file__)), "ffmpeg-master-latest-win64-gpl", "bin")
+# if os.path.exists(FFMPEG_PATH):
+#     os.environ["PATH"] = FFMPEG_PATH + os.pathsep + os.environ["PATH"]
+#     AudioSegment.converter = os.path.join(FFMPEG_PATH, "ffmpeg.exe")
+#     AudioSegment.ffmpeg = os.path.join(FFMPEG_PATH, "ffmpeg.exe")
+#     AudioSegment.ffprobe = os.path.join(FFMPEG_PATH, "ffprobe.exe")
+
+# Comment out or remove the Windows-specific FFMPEG_PATH setup
+# In Docker, ffmpeg will be installed via apt-get and should be in the PATH
+# pydub should find it automatically.
+# If issues arise, one might need to set AudioSegment.converter explicitly,
+# but without the Windows-specific path.
+# For example:
+# AudioSegment.converter = "/usr/bin/ffmpeg" # or wherever ffmpeg is installed
+# AudioSegment.ffmpeg = "/usr/bin/ffmpeg"
+# AudioSegment.ffprobe = "/usr/bin/ffprobe"
+# However, this is often not needed if ffmpeg is in the system PATH.
+
+def extract_features(audio_path, max_length=100):
+    y, sr = librosa.load(audio_path, sr=None)
+    y_normalized = librosa.util.normalize(y)
+    segments = librosa.effects.split(y_normalized, top_db=20)
+
+    mfccs = []
+    for start, end in segments:
+        segment = y[start:end]
+        mfcc = librosa.feature.mfcc(y=segment, sr=sr, n_mfcc=13)
+        if mfcc.shape[1] > max_length:
+            mfcc = mfcc[:, :max_length]
+        else:
+            pad_width = max_length - mfcc.shape[1]
+            mfcc = np.pad(mfcc, pad_width=((0, 0), (0, pad_width)), mode='constant')
+        mfccs.append(mfcc)
+    
+    return mfccs
+
+def predict_vehicle_class(audio_path):
+    features = extract_features(audio_path)
+    
+    # Normalize using training distribution (consider saving stats during training if accuracy matters)
+    features = np.array(features)
+    features = (features - np.mean(features)) / np.std(features)
+
+    # Average predictions across all segments
+    predictions = model.predict(features)
+    averaged_prediction = np.mean(predictions, axis=0)
+    predicted_class = int(np.argmax(averaged_prediction))  # Convert numpy.int64 to Python int
+
+    return predicted_class
+
+def convert_audio_to_wav(src_path: str, dst_path: str) -> bool:
+    """Convert any audio file to WAV format using pydub."""
+    try:
+        # Get the file extension
+        ext = os.path.splitext(src_path)[1].lower().lstrip('.')
+        
+        # Load the audio file with specific parameters
+        audio = AudioSegment.from_file(
+            src_path,
+            format=ext,
+            parameters=["-ar", "16000", "-ac", "1"]  # Set sample rate to 16kHz and mono
+        )
+        
+        # Export as WAV with specific parameters
+        audio.export(
+            dst_path,
+            format="wav",
+            parameters=["-ar", "16000", "-ac", "1", "-acodec", "pcm_s16le"]
+        )
+        return True
+    except Exception as e:
+        logging.error(f"Error converting audio file: {str(e)}")
+        return False
+
+def classify_audio_with_yamnet(file_path):
+    try:
+        # Create a temporary WAV file
+        with tempfile.NamedTemporaryFile(suffix='.wav', delete=False) as temp_wav:
+            temp_wav_path = temp_wav.name
+
+        # Convert the input file to WAV if needed
+        if not convert_audio_to_wav(file_path, temp_wav_path):
+            return {
+                "success": False,
+                "message": "Failed to convert audio file to WAV format"
+            }
+
+        try:
+            # Load and process the audio
+            waveform, sr = librosa.load(temp_wav_path, sr=16000)  # YAMNet expects 16kHz
+            scores, embeddings, spectrogram = yamnet_model(waveform)
+            scores_np = scores.numpy().mean(axis=0)  # average over time
+
+            top5_i = np.argsort(scores_np)[::-1][:5]
+            top_labels = [(yamnet_classes[i], float(scores_np[i])) for i in top5_i]  # Convert scores to Python float
+
+            return {
+                "success": True,
+                "top_classes": top_labels
+            }
+        finally:
+            # Clean up the temporary file
+            if os.path.exists(temp_wav_path):
+                os.unlink(temp_wav_path)
+
+    except Exception as e:
+        logging.exception("YAMNet classification failed:")
+        return {
+            "success": False,
+            "message": f"Audio classification failed: {str(e)}"
+        }
+
+def is_vehicle_sound(yamnet_classes):
+    """
+    Check if any of the top YAMNet classifications are vehicle-related.
+    Returns True if a vehicle sound is detected, along with the matched class and score.
+    """
+    vehicle_keywords = [
+        # General vehicle terms
+        'vehicle', 'automobile', 'motor vehicle',
+        # Specific vehicle types
+        'car', 'truck', 'bus', 'van', 'motorcycle', 'scooter',
+        # Vehicle components
+        'engine', 'motor', 'horn', 'siren', 'tire', 'wheel',
+        # Vehicle sounds
+        'revving', 'acceleration', 'braking', 'idling',
+        # Transportation
+        'transport', 'traffic', 'road'
+    ]
+    
+    # Log the top classifications for debugging
+    logging.info("Top YAMNet classifications:")
+    for class_name, score in yamnet_classes:
+        logging.info(f"- {class_name}: {score:.2f}")
+    
+    # Check each classification against vehicle keywords
+    for class_name, score in yamnet_classes:
+        class_name_lower = class_name.lower()
+        for keyword in vehicle_keywords:
+            if keyword in class_name_lower:
+                logging.info(f"Vehicle sound detected: '{class_name}' (score: {score:.2f})")
+                return True, class_name, score
+    
+    logging.info("No vehicle sounds detected in the audio")
+    return False, None, 0.0
+
+@app.post("/classify/")
+async def classify_audio(file: UploadFile = File(...)):
+    temp_filename = f"temp_classify_{file.filename}"
+    file_content = await file.read()
+
+    try:
+        with open(temp_filename, "wb") as f:
+            f.write(file_content)
+
+        # First try music recognition
+        result_json_str = acr_recognizer.recognize_by_file(temp_filename, 0)
+        music_result = format_acrcloud_response(result_json_str)
+
+        if music_result["success"]:
+            # If music recognition was successful, return that result
+            return {
+                "success": True,
+                "type": "music",
+                "music_result": music_result
+            }
+        else:
+            # If music recognition failed, try YAMNet classification
+            yamnet_result = classify_audio_with_yamnet(temp_filename)
+            if yamnet_result["success"]:
+                # Check if the sound is vehicle-related
+                is_vehicle, vehicle_class, vehicle_score = is_vehicle_sound(yamnet_result["top_classes"])
+                if is_vehicle:
+                    # If it's a vehicle sound, use the neural network for specific classification
+                    vehicle_class = predict_vehicle_class(temp_filename)
+                    vehicle_type = "Car" if vehicle_class == 0 else "Truck"
+                    
+                    return {
+                        "success": True,
+                        "type": "vehicle",
+                        "vehicle_result": {
+                            "vehicle_type": vehicle_type,
+                            "detected_sound": vehicle_class,
+                            "confidence": float(vehicle_score) * 100
+                        }
+                    }
+                
+                # If not a vehicle sound, return YAMNet classification
+                return {
+                    "success": True,
+                    "type": "sound",
+                    "sound_result": yamnet_result
+                }
+            else:
+                return {
+                    "success": False,
+                    "message": "No music, vehicle, or sound patterns recognized."
+                }
+
+    except Exception as e:
+        logging.exception("Error during classification:")
+        return {"success": False, "message": str(e)}
+
+    finally:
+        if os.path.exists(temp_filename):
+            os.remove(temp_filename)
+
+@app.get("/", response_class=HTMLResponse)
+async def read_root(request: Request):
+    return templates.TemplateResponse("index.html", {"request": request})
+
+@app.post("/recognize/")
+async def recognize_song_acr(file: UploadFile = File(...)):
+    temp_filename = f"temp_recognize_{file.filename}"
+    file_content = await file.read()
+
+    try:
+        with open(temp_filename, "wb") as buffer:
+            buffer.write(file_content)
+        
+        result_json_str = acr_recognizer.recognize_by_file(temp_filename, 0) 
+        
+        return format_acrcloud_response(result_json_str)
+    except Exception as e:
+        logging.exception("Error during SDK ACRCloud recognition:")
+        return {"success": False, "message": f"Recognition failed: {str(e)}"}
+    finally:
+        # Changed: Ensure temp file is cleaned up
+        if os.path.exists(temp_filename):
+            os.remove(temp_filename)
+
+@app.post("/upload/")
+async def upload_song_acr(file: UploadFile = File(...), song_name: str = Form(None)): 
+    temp_filename = f"temp_upload_{file.filename}"
+    file_content = await file.read()
+
+    try:
+        with open(temp_filename, "wb") as buffer:
+            buffer.write(file_content)
+            
+        result_json_str = acr_recognizer.recognize_by_file(temp_filename, 0)
+        
+        response_data = format_acrcloud_response(result_json_str)
+        if song_name and response_data.get("success"):
+            response_data["message_context"] = f"Recognition for (originally uploaded as '{song_name}')"
+        elif song_name and not response_data.get("success"):
+             response_data["message"] = f"Recognition for (originally uploaded as '{song_name}') failed: {response_data.get('message')}"
+
+        return response_data
+    except Exception as e:
+        logging.exception("Error during SDK ACRCloud upload/recognition:")
+        return {"success": False, "message": f"Upload/Recognition failed: {str(e)}"}
+    finally:
+        if os.path.exists(temp_filename):
+            os.remove(temp_filename)
+
+@app.post("/recognize-live-chunk/")
+async def recognize_live_chunk(file: UploadFile = File(...)):
+    file_content = await file.read()
+
+    if not file_content:
+        return {"success": False, "message": "Empty audio chunk received."}
+
+    try:
+        logging.info(f"Received live chunk, size: {len(file_content)} bytes, filename: {file.filename}")
+        
+        # First try music recognition
+        result_json_str = acr_recognizer.recognize_by_filebuffer(file_content, 0)
+        music_result = format_acrcloud_response(result_json_str)
+
+        # Check if we got a valid music result
+        if music_result["success"] and music_result.get("song_name"):
+            # If we have a valid song name, return the music result
+            return {
+                "success": True,
+                "type": "music",
+                "music_result": music_result
+            }
+        
+        # If no valid music result, try YAMNet classification
+        with tempfile.NamedTemporaryFile(suffix='.webm', delete=False) as temp_file:
+            temp_filename = temp_file.name
+            temp_file.write(file_content)
+
+        try:
+            # Convert to WAV first
+            wav_filename = temp_filename.replace('.webm', '.wav')
+            if convert_audio_to_wav(temp_filename, wav_filename):
+                yamnet_result = classify_audio_with_yamnet(wav_filename)
+                
+                if yamnet_result["success"]:
+                    # Check if the sound is vehicle-related
+                    is_vehicle, vehicle_class, vehicle_score = is_vehicle_sound(yamnet_result["top_classes"])
+                    if is_vehicle:
+                        # If it's a vehicle sound, use the neural network for specific classification
+                        vehicle_class = predict_vehicle_class(wav_filename)
+                        vehicle_type = "Car" if vehicle_class == 0 else "Truck"
+                        
+                        return {
+                            "success": True,
+                            "type": "vehicle",
+                            "vehicle_result": {
+                                "vehicle_type": vehicle_type,
+                                "detected_sound": str(vehicle_class),  # Convert to string
+                                "confidence": float(vehicle_score) * 100  # Convert to Python float
+                            }
+                        }
+                    
+                    # If not a vehicle sound, return YAMNet classification
+                    return {
+                        "success": True,
+                        "type": "sound",
+                        "sound_result": {
+                            "top_classes": [(str(label), float(score)) for label, score in yamnet_result["top_classes"]]
+                        }
+                    }
+            
+            # If we get here, all recognition attempts failed
+            return {
+                "success": False,
+                "message": "No music, vehicle, or sound patterns recognized."
+            }
+        finally:
+            # Clean up temporary files
+            if os.path.exists(temp_filename):
+                os.remove(temp_filename)
+            if os.path.exists(wav_filename):
+                os.remove(wav_filename)
+
+    except Exception as e:
+        logging.exception("Error during audio processing:")
+        return {"success": False, "message": f"Processing failed: {str(e)}"}
+
+def format_acrcloud_response(result_json_str: str):
+    """
+    Parses the JSON string response from ACRCloud and formats it.
+    """
+    try:
+        result = json.loads(result_json_str)
+        logging.info(f"ACRCloud raw response: {result}")
+        
+        # Check if we have a valid music result
+        if result.get("status", {}).get("code") == 0 and "metadata" in result and "music" in result["metadata"]:
+            # Ensure 'music' list is not empty
+            if not result["metadata"]["music"]:
+                return {"success": False, "message": "No music metadata found in response."}
+            
+            music_info = result["metadata"]["music"][0]
+            title = music_info.get("title")
+            
+            # If no title, it's not a valid music result
+            if not title:
+                return {"success": False, "message": "No song title found in response."}
+            
+            artists_list = music_info.get("artists", [])
+            artists = ", ".join([artist["name"] for artist in artists_list if "name" in artist])
+            album = music_info.get("album", {}).get("name")
+            
+            offset_seconds = music_info.get("play_offset_ms", 0) / 1000.0
+            if offset_seconds == 0 and "sample_begin_time_offset_ms" in music_info:
+                 offset_seconds = music_info.get("sample_begin_time_offset_ms", 0) / 1000.0
+            
+            confidence = music_info.get("score", 0)
+            if confidence == 0 and "result_type" in result: 
+                 confidence = result.get("result_type",0) * 25 
+
+            return {
+                "success": True,
+                "song_name": title,
+                "artists": artists,
+                "album": album,
+                "confidence": confidence,
+                "offset_seconds": offset_seconds,
+                "raw_acr_response": result
+            }
+        else:
+            return {"success": False, "message": result.get("status", {}).get("msg", "Song not recognized or error in response.")}
+    except json.JSONDecodeError:
+        logging.error(f"Failed to decode ACRCloud JSON response: {result_json_str}")
+        return {"success": False, "message": "Error parsing recognition server response."}
+    except Exception as e:
+        logging.error(f"Error processing ACRCloud response: {e} -- Response was: {result_json_str}")
+        return {"success": False, "message": f"An unexpected error occurred: {str(e)}"}
+
+@app.post("/predict/")
+async def predict_audio(file: UploadFile = File(...)):
+    # Save uploaded file temporarily
+    with tempfile.NamedTemporaryFile(delete=False, suffix=".mp3") as tmp:
+        shutil.copyfileobj(file.file, tmp)
+        tmp_path = tmp.name
+
+    try:
+        # Predict using the neural network
+        predicted_class = predict_vehicle_class(tmp_path)
+        return {"filename": file.filename, "predicted_class": int(predicted_class)}
+    finally:
+        os.remove(tmp_path)
+
+# Mistral AI configuration
+MISTRAL_API_KEY = "SDV5ynlJBEs0n15l2PDvO9eor1ki4dTI"
+MISTRAL_API_URL = "https://api.mistral.ai/v1/chat/completions"
+
+class ChatRequest(BaseModel):
+    system_prompt: str
+    user_message: str
+
+@app.post("/chat-with-mistral/")
+async def chat_with_mistral(request: ChatRequest):
+    try:
+        headers = {
+            "Authorization": f"Bearer {MISTRAL_API_KEY}",
+            "Content-Type": "application/json"
+        }
+
+        data = {
+            "model": "mistral-small",
+            "messages": [
+                {
+                    "role": "system",
+                    "content": request.system_prompt
+                },
+                {
+                    "role": "user",
+                    "content": request.user_message
+                }
+            ]
+        }
+
+        response = requests.post(MISTRAL_API_URL, headers=headers, json=data)
+
+        if response.status_code == 200:
+            ai_response = response.json()["choices"][0]["message"]["content"]
+            return {
+                "success": True,
+                "response": ai_response
+            }
+        else:
+            raise HTTPException(
+                status_code=500,
+                detail=f"Error from Mistral API: {response.status_code} - {response.text}"
+            )
+
+    except Exception as e:
+        raise HTTPException(
+            status_code=500,
+            detail=str(e)
+        )
+
+logging.basicConfig(level=logging.INFO)

models/neural_networks.h5

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fc6f4d76bc4c3673954f31dd5051e74affa44fdc33ed6613e12a81e29508972
+size 4024184

readme.md

@@ -0,0 +1,3 @@
+# Install ACRCloud SDK
+pip install git+https://github.com/acrcloud/acrcloud_sdk_python.git
+

requirements.txt

@@ -0,0 +1,10 @@
+fastapi
+uvicorn[standard]
+Jinja2
+requests
+pydub
+librosa
+tensorflow
+tensorflow_hub
+numpy
+git+https://github.com/acrcloud/acrcloud_sdk_python.git

yamnet_class_map.csv

@@ -0,0 +1,522 @@
+index,mid,display_name
+0,/m/09x0r,Speech
+1,/m/0ytgt,"Child speech, kid speaking"
+2,/m/01h8n0,Conversation
+3,/m/02qldy,"Narration, monologue"
+4,/m/0261r1,Babbling
+5,/m/0brhx,Speech synthesizer
+6,/m/07p6fty,Shout
+7,/m/07q4ntr,Bellow
+8,/m/07rwj3x,Whoop
+9,/m/07sr1lc,Yell
+10,/t/dd00135,Children shouting
+11,/m/03qc9zr,Screaming
+12,/m/02rtxlg,Whispering
+13,/m/01j3sz,Laughter
+14,/t/dd00001,Baby laughter
+15,/m/07r660_,Giggle
+16,/m/07s04w4,Snicker
+17,/m/07sq110,Belly laugh
+18,/m/07rgt08,"Chuckle, chortle"
+19,/m/0463cq4,"Crying, sobbing"
+20,/t/dd00002,"Baby cry, infant cry"
+21,/m/07qz6j3,Whimper
+22,/m/07qw_06,"Wail, moan"
+23,/m/07plz5l,Sigh
+24,/m/015lz1,Singing
+25,/m/0l14jd,Choir
+26,/m/01swy6,Yodeling
+27,/m/02bk07,Chant
+28,/m/01c194,Mantra
+29,/t/dd00005,Child singing
+30,/t/dd00006,Synthetic singing
+31,/m/06bxc,Rapping
+32,/m/02fxyj,Humming
+33,/m/07s2xch,Groan
+34,/m/07r4k75,Grunt
+35,/m/01w250,Whistling
+36,/m/0lyf6,Breathing
+37,/m/07mzm6,Wheeze
+38,/m/01d3sd,Snoring
+39,/m/07s0dtb,Gasp
+40,/m/07pyy8b,Pant
+41,/m/07q0yl5,Snort
+42,/m/01b_21,Cough
+43,/m/0dl9sf8,Throat clearing
+44,/m/01hsr_,Sneeze
+45,/m/07ppn3j,Sniff
+46,/m/06h7j,Run
+47,/m/07qv_x_,Shuffle
+48,/m/07pbtc8,"Walk, footsteps"
+49,/m/03cczk,"Chewing, mastication"
+50,/m/07pdhp0,Biting
+51,/m/0939n_,Gargling
+52,/m/01g90h,Stomach rumble
+53,/m/03q5_w,"Burping, eructation"
+54,/m/02p3nc,Hiccup
+55,/m/02_nn,Fart
+56,/m/0k65p,Hands
+57,/m/025_jnm,Finger snapping
+58,/m/0l15bq,Clapping
+59,/m/01jg02,"Heart sounds, heartbeat"
+60,/m/01jg1z,Heart murmur
+61,/m/053hz1,Cheering
+62,/m/028ght,Applause
+63,/m/07rkbfh,Chatter
+64,/m/03qtwd,Crowd
+65,/m/07qfr4h,"Hubbub, speech noise, speech babble"
+66,/t/dd00013,Children playing
+67,/m/0jbk,Animal
+68,/m/068hy,"Domestic animals, pets"
+69,/m/0bt9lr,Dog
+70,/m/05tny_,Bark
+71,/m/07r_k2n,Yip
+72,/m/07qf0zm,Howl
+73,/m/07rc7d9,Bow-wow
+74,/m/0ghcn6,Growling
+75,/t/dd00136,Whimper (dog)
+76,/m/01yrx,Cat
+77,/m/02yds9,Purr
+78,/m/07qrkrw,Meow
+79,/m/07rjwbb,Hiss
+80,/m/07r81j2,Caterwaul
+81,/m/0ch8v,"Livestock, farm animals, working animals"
+82,/m/03k3r,Horse
+83,/m/07rv9rh,Clip-clop
+84,/m/07q5rw0,"Neigh, whinny"
+85,/m/01xq0k1,"Cattle, bovinae"
+86,/m/07rpkh9,Moo
+87,/m/0239kh,Cowbell
+88,/m/068zj,Pig
+89,/t/dd00018,Oink
+90,/m/03fwl,Goat
+91,/m/07q0h5t,Bleat
+92,/m/07bgp,Sheep
+93,/m/025rv6n,Fowl
+94,/m/09b5t,"Chicken, rooster"
+95,/m/07st89h,Cluck
+96,/m/07qn5dc,"Crowing, cock-a-doodle-doo"
+97,/m/01rd7k,Turkey
+98,/m/07svc2k,Gobble
+99,/m/09ddx,Duck
+100,/m/07qdb04,Quack
+101,/m/0dbvp,Goose
+102,/m/07qwf61,Honk
+103,/m/01280g,Wild animals
+104,/m/0cdnk,"Roaring cats (lions, tigers)"
+105,/m/04cvmfc,Roar
+106,/m/015p6,Bird
+107,/m/020bb7,"Bird vocalization, bird call, bird song"
+108,/m/07pggtn,"Chirp, tweet"
+109,/m/07sx8x_,Squawk
+110,/m/0h0rv,"Pigeon, dove"
+111,/m/07r_25d,Coo
+112,/m/04s8yn,Crow
+113,/m/07r5c2p,Caw
+114,/m/09d5_,Owl
+115,/m/07r_80w,Hoot
+116,/m/05_wcq,"Bird flight, flapping wings"
+117,/m/01z5f,"Canidae, dogs, wolves"
+118,/m/06hps,"Rodents, rats, mice"
+119,/m/04rmv,Mouse
+120,/m/07r4gkf,Patter
+121,/m/03vt0,Insect
+122,/m/09xqv,Cricket
+123,/m/09f96,Mosquito
+124,/m/0h2mp,"Fly, housefly"
+125,/m/07pjwq1,Buzz
+126,/m/01h3n,"Bee, wasp, etc."
+127,/m/09ld4,Frog
+128,/m/07st88b,Croak
+129,/m/078jl,Snake
+130,/m/07qn4z3,Rattle
+131,/m/032n05,Whale vocalization
+132,/m/04rlf,Music
+133,/m/04szw,Musical instrument
+134,/m/0fx80y,Plucked string instrument
+135,/m/0342h,Guitar
+136,/m/02sgy,Electric guitar
+137,/m/018vs,Bass guitar
+138,/m/042v_gx,Acoustic guitar
+139,/m/06w87,"Steel guitar, slide guitar"
+140,/m/01glhc,Tapping (guitar technique)
+141,/m/07s0s5r,Strum
+142,/m/018j2,Banjo
+143,/m/0jtg0,Sitar
+144,/m/04rzd,Mandolin
+145,/m/01bns_,Zither
+146,/m/07xzm,Ukulele
+147,/m/05148p4,Keyboard (musical)
+148,/m/05r5c,Piano
+149,/m/01s0ps,Electric piano
+150,/m/013y1f,Organ
+151,/m/03xq_f,Electronic organ
+152,/m/03gvt,Hammond organ
+153,/m/0l14qv,Synthesizer
+154,/m/01v1d8,Sampler
+155,/m/03q5t,Harpsichord
+156,/m/0l14md,Percussion
+157,/m/02hnl,Drum kit
+158,/m/0cfdd,Drum machine
+159,/m/026t6,Drum
+160,/m/06rvn,Snare drum
+161,/m/03t3fj,Rimshot
+162,/m/02k_mr,Drum roll
+163,/m/0bm02,Bass drum
+164,/m/011k_j,Timpani
+165,/m/01p970,Tabla
+166,/m/01qbl,Cymbal
+167,/m/03qtq,Hi-hat
+168,/m/01sm1g,Wood block
+169,/m/07brj,Tambourine
+170,/m/05r5wn,Rattle (instrument)
+171,/m/0xzly,Maraca
+172,/m/0mbct,Gong
+173,/m/016622,Tubular bells
+174,/m/0j45pbj,Mallet percussion
+175,/m/0dwsp,"Marimba, xylophone"
+176,/m/0dwtp,Glockenspiel
+177,/m/0dwt5,Vibraphone
+178,/m/0l156b,Steelpan
+179,/m/05pd6,Orchestra
+180,/m/01kcd,Brass instrument
+181,/m/0319l,French horn
+182,/m/07gql,Trumpet
+183,/m/07c6l,Trombone
+184,/m/0l14_3,Bowed string instrument
+185,/m/02qmj0d,String section
+186,/m/07y_7,"Violin, fiddle"
+187,/m/0d8_n,Pizzicato
+188,/m/01xqw,Cello
+189,/m/02fsn,Double bass
+190,/m/085jw,"Wind instrument, woodwind instrument"
+191,/m/0l14j_,Flute
+192,/m/06ncr,Saxophone
+193,/m/01wy6,Clarinet
+194,/m/03m5k,Harp
+195,/m/0395lw,Bell
+196,/m/03w41f,Church bell
+197,/m/027m70_,Jingle bell
+198,/m/0gy1t2s,Bicycle bell
+199,/m/07n_g,Tuning fork
+200,/m/0f8s22,Chime
+201,/m/026fgl,Wind chime
+202,/m/0150b9,Change ringing (campanology)
+203,/m/03qjg,Harmonica
+204,/m/0mkg,Accordion
+205,/m/0192l,Bagpipes
+206,/m/02bxd,Didgeridoo
+207,/m/0l14l2,Shofar
+208,/m/07kc_,Theremin
+209,/m/0l14t7,Singing bowl
+210,/m/01hgjl,Scratching (performance technique)
+211,/m/064t9,Pop music
+212,/m/0glt670,Hip hop music
+213,/m/02cz_7,Beatboxing
+214,/m/06by7,Rock music
+215,/m/03lty,Heavy metal
+216,/m/05r6t,Punk rock
+217,/m/0dls3,Grunge
+218,/m/0dl5d,Progressive rock
+219,/m/07sbbz2,Rock and roll
+220,/m/05w3f,Psychedelic rock
+221,/m/06j6l,Rhythm and blues
+222,/m/0gywn,Soul music
+223,/m/06cqb,Reggae
+224,/m/01lyv,Country
+225,/m/015y_n,Swing music
+226,/m/0gg8l,Bluegrass
+227,/m/02x8m,Funk
+228,/m/02w4v,Folk music
+229,/m/06j64v,Middle Eastern music
+230,/m/03_d0,Jazz
+231,/m/026z9,Disco
+232,/m/0ggq0m,Classical music
+233,/m/05lls,Opera
+234,/m/02lkt,Electronic music
+235,/m/03mb9,House music
+236,/m/07gxw,Techno
+237,/m/07s72n,Dubstep
+238,/m/0283d,Drum and bass
+239,/m/0m0jc,Electronica
+240,/m/08cyft,Electronic dance music
+241,/m/0fd3y,Ambient music
+242,/m/07lnk,Trance music
+243,/m/0g293,Music of Latin America
+244,/m/0ln16,Salsa music
+245,/m/0326g,Flamenco
+246,/m/0155w,Blues
+247,/m/05fw6t,Music for children
+248,/m/02v2lh,New-age music
+249,/m/0y4f8,Vocal music
+250,/m/0z9c,A capella
+251,/m/0164x2,Music of Africa
+252,/m/0145m,Afrobeat
+253,/m/02mscn,Christian music
+254,/m/016cjb,Gospel music
+255,/m/028sqc,Music of Asia
+256,/m/015vgc,Carnatic music
+257,/m/0dq0md,Music of Bollywood
+258,/m/06rqw,Ska
+259,/m/02p0sh1,Traditional music
+260,/m/05rwpb,Independent music
+261,/m/074ft,Song
+262,/m/025td0t,Background music
+263,/m/02cjck,Theme music
+264,/m/03r5q_,Jingle (music)
+265,/m/0l14gg,Soundtrack music
+266,/m/07pkxdp,Lullaby
+267,/m/01z7dr,Video game music
+268,/m/0140xf,Christmas music
+269,/m/0ggx5q,Dance music
+270,/m/04wptg,Wedding music
+271,/t/dd00031,Happy music
+272,/t/dd00033,Sad music
+273,/t/dd00034,Tender music
+274,/t/dd00035,Exciting music
+275,/t/dd00036,Angry music
+276,/t/dd00037,Scary music
+277,/m/03m9d0z,Wind
+278,/m/09t49,Rustling leaves
+279,/t/dd00092,Wind noise (microphone)
+280,/m/0jb2l,Thunderstorm
+281,/m/0ngt1,Thunder
+282,/m/0838f,Water
+283,/m/06mb1,Rain
+284,/m/07r10fb,Raindrop
+285,/t/dd00038,Rain on surface
+286,/m/0j6m2,Stream
+287,/m/0j2kx,Waterfall
+288,/m/05kq4,Ocean
+289,/m/034srq,"Waves, surf"
+290,/m/06wzb,Steam
+291,/m/07swgks,Gurgling
+292,/m/02_41,Fire
+293,/m/07pzfmf,Crackle
+294,/m/07yv9,Vehicle
+295,/m/019jd,"Boat, Water vehicle"
+296,/m/0hsrw,"Sailboat, sailing ship"
+297,/m/056ks2,"Rowboat, canoe, kayak"
+298,/m/02rlv9,"Motorboat, speedboat"
+299,/m/06q74,Ship
+300,/m/012f08,Motor vehicle (road)
+301,/m/0k4j,Car
+302,/m/0912c9,"Vehicle horn, car horn, honking"
+303,/m/07qv_d5,Toot
+304,/m/02mfyn,Car alarm
+305,/m/04gxbd,"Power windows, electric windows"
+306,/m/07rknqz,Skidding
+307,/m/0h9mv,Tire squeal
+308,/t/dd00134,Car passing by
+309,/m/0ltv,"Race car, auto racing"
+310,/m/07r04,Truck
+311,/m/0gvgw0,Air brake
+312,/m/05x_td,"Air horn, truck horn"
+313,/m/02rhddq,Reversing beeps
+314,/m/03cl9h,"Ice cream truck, ice cream van"
+315,/m/01bjv,Bus
+316,/m/03j1ly,Emergency vehicle
+317,/m/04qvtq,Police car (siren)
+318,/m/012n7d,Ambulance (siren)
+319,/m/012ndj,"Fire engine, fire truck (siren)"
+320,/m/04_sv,Motorcycle
+321,/m/0btp2,"Traffic noise, roadway noise"
+322,/m/06d_3,Rail transport
+323,/m/07jdr,Train
+324,/m/04zmvq,Train whistle
+325,/m/0284vy3,Train horn
+326,/m/01g50p,"Railroad car, train wagon"
+327,/t/dd00048,Train wheels squealing
+328,/m/0195fx,"Subway, metro, underground"
+329,/m/0k5j,Aircraft
+330,/m/014yck,Aircraft engine
+331,/m/04229,Jet engine
+332,/m/02l6bg,"Propeller, airscrew"
+333,/m/09ct_,Helicopter
+334,/m/0cmf2,"Fixed-wing aircraft, airplane"
+335,/m/0199g,Bicycle
+336,/m/06_fw,Skateboard
+337,/m/02mk9,Engine
+338,/t/dd00065,Light engine (high frequency)
+339,/m/08j51y,"Dental drill, dentist's drill"
+340,/m/01yg9g,Lawn mower
+341,/m/01j4z9,Chainsaw
+342,/t/dd00066,Medium engine (mid frequency)
+343,/t/dd00067,Heavy engine (low frequency)
+344,/m/01h82_,Engine knocking
+345,/t/dd00130,Engine starting
+346,/m/07pb8fc,Idling
+347,/m/07q2z82,"Accelerating, revving, vroom"
+348,/m/02dgv,Door
+349,/m/03wwcy,Doorbell
+350,/m/07r67yg,Ding-dong
+351,/m/02y_763,Sliding door
+352,/m/07rjzl8,Slam
+353,/m/07r4wb8,Knock
+354,/m/07qcpgn,Tap
+355,/m/07q6cd_,Squeak
+356,/m/0642b4,Cupboard open or close
+357,/m/0fqfqc,Drawer open or close
+358,/m/04brg2,"Dishes, pots, and pans"
+359,/m/023pjk,"Cutlery, silverware"
+360,/m/07pn_8q,Chopping (food)
+361,/m/0dxrf,Frying (food)
+362,/m/0fx9l,Microwave oven
+363,/m/02pjr4,Blender
+364,/m/02jz0l,"Water tap, faucet"
+365,/m/0130jx,Sink (filling or washing)
+366,/m/03dnzn,Bathtub (filling or washing)
+367,/m/03wvsk,Hair dryer
+368,/m/01jt3m,Toilet flush
+369,/m/012xff,Toothbrush
+370,/m/04fgwm,Electric toothbrush
+371,/m/0d31p,Vacuum cleaner
+372,/m/01s0vc,Zipper (clothing)
+373,/m/03v3yw,Keys jangling
+374,/m/0242l,Coin (dropping)
+375,/m/01lsmm,Scissors
+376,/m/02g901,"Electric shaver, electric razor"
+377,/m/05rj2,Shuffling cards
+378,/m/0316dw,Typing
+379,/m/0c2wf,Typewriter
+380,/m/01m2v,Computer keyboard
+381,/m/081rb,Writing
+382,/m/07pp_mv,Alarm
+383,/m/07cx4,Telephone
+384,/m/07pp8cl,Telephone bell ringing
+385,/m/01hnzm,Ringtone
+386,/m/02c8p,"Telephone dialing, DTMF"
+387,/m/015jpf,Dial tone
+388,/m/01z47d,Busy signal
+389,/m/046dlr,Alarm clock
+390,/m/03kmc9,Siren
+391,/m/0dgbq,Civil defense siren
+392,/m/030rvx,Buzzer
+393,/m/01y3hg,"Smoke detector, smoke alarm"
+394,/m/0c3f7m,Fire alarm
+395,/m/04fq5q,Foghorn
+396,/m/0l156k,Whistle
+397,/m/06hck5,Steam whistle
+398,/t/dd00077,Mechanisms
+399,/m/02bm9n,"Ratchet, pawl"
+400,/m/01x3z,Clock
+401,/m/07qjznt,Tick
+402,/m/07qjznl,Tick-tock
+403,/m/0l7xg,Gears
+404,/m/05zc1,Pulleys
+405,/m/0llzx,Sewing machine
+406,/m/02x984l,Mechanical fan
+407,/m/025wky1,Air conditioning
+408,/m/024dl,Cash register
+409,/m/01m4t,Printer
+410,/m/0dv5r,Camera
+411,/m/07bjf,Single-lens reflex camera
+412,/m/07k1x,Tools
+413,/m/03l9g,Hammer
+414,/m/03p19w,Jackhammer
+415,/m/01b82r,Sawing
+416,/m/02p01q,Filing (rasp)
+417,/m/023vsd,Sanding
+418,/m/0_ksk,Power tool
+419,/m/01d380,Drill
+420,/m/014zdl,Explosion
+421,/m/032s66,"Gunshot, gunfire"
+422,/m/04zjc,Machine gun
+423,/m/02z32qm,Fusillade
+424,/m/0_1c,Artillery fire
+425,/m/073cg4,Cap gun
+426,/m/0g6b5,Fireworks
+427,/g/122z_qxw,Firecracker
+428,/m/07qsvvw,"Burst, pop"
+429,/m/07pxg6y,Eruption
+430,/m/07qqyl4,Boom
+431,/m/083vt,Wood
+432,/m/07pczhz,Chop
+433,/m/07pl1bw,Splinter
+434,/m/07qs1cx,Crack
+435,/m/039jq,Glass
+436,/m/07q7njn,"Chink, clink"
+437,/m/07rn7sz,Shatter
+438,/m/04k94,Liquid
+439,/m/07rrlb6,"Splash, splatter"
+440,/m/07p6mqd,Slosh
+441,/m/07qlwh6,Squish
+442,/m/07r5v4s,Drip
+443,/m/07prgkl,Pour
+444,/m/07pqc89,"Trickle, dribble"
+445,/t/dd00088,Gush
+446,/m/07p7b8y,Fill (with liquid)
+447,/m/07qlf79,Spray
+448,/m/07ptzwd,Pump (liquid)
+449,/m/07ptfmf,Stir
+450,/m/0dv3j,Boiling
+451,/m/0790c,Sonar
+452,/m/0dl83,Arrow
+453,/m/07rqsjt,"Whoosh, swoosh, swish"
+454,/m/07qnq_y,"Thump, thud"
+455,/m/07rrh0c,Thunk
+456,/m/0b_fwt,Electronic tuner
+457,/m/02rr_,Effects unit
+458,/m/07m2kt,Chorus effect
+459,/m/018w8,Basketball bounce
+460,/m/07pws3f,Bang
+461,/m/07ryjzk,"Slap, smack"
+462,/m/07rdhzs,"Whack, thwack"
+463,/m/07pjjrj,"Smash, crash"
+464,/m/07pc8lb,Breaking
+465,/m/07pqn27,Bouncing
+466,/m/07rbp7_,Whip
+467,/m/07pyf11,Flap
+468,/m/07qb_dv,Scratch
+469,/m/07qv4k0,Scrape
+470,/m/07pdjhy,Rub
+471,/m/07s8j8t,Roll
+472,/m/07plct2,Crushing
+473,/t/dd00112,"Crumpling, crinkling"
+474,/m/07qcx4z,Tearing
+475,/m/02fs_r,"Beep, bleep"
+476,/m/07qwdck,Ping
+477,/m/07phxs1,Ding
+478,/m/07rv4dm,Clang
+479,/m/07s02z0,Squeal
+480,/m/07qh7jl,Creak
+481,/m/07qwyj0,Rustle
+482,/m/07s34ls,Whir
+483,/m/07qmpdm,Clatter
+484,/m/07p9k1k,Sizzle
+485,/m/07qc9xj,Clicking
+486,/m/07rwm0c,Clickety-clack
+487,/m/07phhsh,Rumble
+488,/m/07qyrcz,Plop
+489,/m/07qfgpx,"Jingle, tinkle"
+490,/m/07rcgpl,Hum
+491,/m/07p78v5,Zing
+492,/t/dd00121,Boing
+493,/m/07s12q4,Crunch
+494,/m/028v0c,Silence
+495,/m/01v_m0,Sine wave
+496,/m/0b9m1,Harmonic
+497,/m/0hdsk,Chirp tone
+498,/m/0c1dj,Sound effect
+499,/m/07pt_g0,Pulse
+500,/t/dd00125,"Inside, small room"
+501,/t/dd00126,"Inside, large room or hall"
+502,/t/dd00127,"Inside, public space"
+503,/t/dd00128,"Outside, urban or manmade"
+504,/t/dd00129,"Outside, rural or natural"
+505,/m/01b9nn,Reverberation
+506,/m/01jnbd,Echo
+507,/m/096m7z,Noise
+508,/m/06_y0by,Environmental noise
+509,/m/07rgkc5,Static
+510,/m/06xkwv,Mains hum
+511,/m/0g12c5,Distortion
+512,/m/08p9q4,Sidetone
+513,/m/07szfh9,Cacophony
+514,/m/0chx_,White noise
+515,/m/0cj0r,Pink noise
+516,/m/07p_0gm,Throbbing
+517,/m/01jwx6,Vibration
+518,/m/07c52,Television
+519,/m/06bz3,Radio
+520,/m/07hvw1,Field recording