My favorites | Sign in
Project Logo
                
Search
for
Updated Oct 21, 2008 by jon.keys
Labels: start, help, faq
GettingStarted  

License

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/.

Support

SonyDADC offers no support for jFlvTool whatsoever. Bug reports can be submitted to dwsystems at sonydadc.com

Building

jFlvTool depends on the commons-cli library from apache. You'll need to download a copy of cli v1.1 and place the file named "commons-cli-1.1.jar" in the jFlvTool/lib directory in order to build the application. http://commons.apache.org/downloads/download_cli.cgi
You'll also need java 1.5 or higher to compile/use the application.
jFlvTool was written using netbeans 5.5 which uses ant for building. Assuming you have ant properly installed and configured, enter the jFlvTool directory (which contains a file called build.xml) and type "ant". The build process will begin and if everything goes well, you should have a new directory called "dist" containing the jFlvTool jar and a "lib" directory.

Using

Once you've built the application, you can test it by typing the following on the command line (command prompt):
        java -jar jFlvTool.jar
Assuming you have java 1.5 or higher in your path and commons-cli v1.1 in your classpath you should see some usage options printed to the screen. The commons-cli library will be copied into a lib directory relative to the jFlvTool.jar file and will be automatically placed in the classpath. If the lib directory is not present, you'll have to manually place the commons-cli library v1.1 in your classpath.
The following switches are currently supported:
        -debug
        -destfile <file>
        -embed <var=value>
        -help
        -metacreator <name>
        -metafile <file>
        -metaname <name>
        -print
        -srcfile <file>
'debug' is an optional switch which toggles printing of a stack trace when an exception is caught.
'destfile' is the desired location for your output file. If you do not specify a location then it defaults to the same location as the original file with a 'out' prefix. The path may be relative or absolute.
'embed' accepts a comma-separated list of key-value pairs to embed into the flv. For example if you wanted to embed your full name as three separate variables the 'embed' switch would look like this:
        -embed fname=john,middle=q,lname=public
'metacreator' is an optional switch which allows you to specify a string (Company name, Artist name, etc...) in the 'metacreator' field
'metafile' is the location of a plain text file containing metadata you would like to embed. The variable name can be defined using the 'metaname' switch. The path may be relative or absolute.
'metaname' is the variable name used for the metadata embeded using the 'metafile' switch.
'print' is an optional switch which will print the existing metadata of the specified 'srcfile'.
'srcfile' if the full or relative path to the source flv - it must always be set.

Sign in to add a comment
Hosted by Google Code