Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
Originally Posted by videofan3d
|
In case anyone needs it here are all available options for encoder and decoder
Quote:
FRIM Encoder version 1.00 (build: Oct 29 2013)
- based on Intel(R) Media SDK (version: 4.0.760.60435)
Usage:
FRIMEncode.exe mpeg2|h264|mvc|jpeg [options]
-i InputFile -o OutputBitstream
options:
[-avi] - input file is in AVI format,
if not specified then YUV is expected
[-sbs|tab numViews] - input file is in side-by-side or top-above-below
format, valid only for multiview
[-w width] - source picture width (one view), mandatory for YUV
[-h height] - source picture height (one view), mandatory for YUV
[-f frameRate] - video frame rate (frames per second)
[-b bitRate] - encoded bit rate (Kbits per second),
valid for H.264, MPEG2 and MVC encoders
[-tff|bff] - input stream is interlaced, top|bottom fielf first,
if not specified then progressive is expected
[-nv12] - input is in NV12 color format,
if not specified then YUV420 is expected
[-u 1..7] - target usage: between 1(=quality) and 7(=speed),
default is 4(=balanced),
valid for H.264, MPEG2 and MVC encoders
[-q quality] - quality parameter for JPEG encoder,
in range [1,100]. 100 is the best quality.
[-la] - use the look ahead bitrate control algorithm (LA BRC)
for H.264 encoder. Supported only with -hw option
on 4th Generation Intel Core processors.
[-lad depth] - depth parameter for the LA BRC, in range [10,100],
the number of frames to be analyzed before encoding
[-dstw width] - destination picture width, invokes VPP resizing
[-dsth height] - destination picture height, invokes VPP resizing
[-hw] - use platform specific SDK implementation,
if not specified then software implementation is used
[-d3d] - work with d3d9 surfaces
[-d3d11] - work with d3d11 surfaces
[-viewoutput] - instruct the MVC encoder to output each view
in separate bitstream buffer.
Depending on the number of '-o' options
behaves as follows:
1: two views are encoded in single file
2: two views are encoded in separate files
3: behaves like two '-o' were used and then one '-o'
Example: FRIMEncode.exe mvc
-i InputFile_1 -i InputFile_2
-o OutputEncodedFile_1 -o OutputEncodedFile_2
-viewoutput -w width -h height
User module options:
[-angle 180] - enables 180 degrees picture rotation before encoding,
CPU implementation by default.
Rotation requires NV12 input.
Options -tff|bff, -dstw, -dsth, -d3d are not effective
together with this one, -nv12 is required.
[-opencl] - rotation implementation through OPENCL
Example: FRIMEncode.exe h264|mpeg2|mvc|jpeg
-i InputFile -o OutputEncodedFile
-w width -h height -angle 180 -opencl
------------------------------------------------------------------
FRIM Decoder version 1.00 (build: Oct 29 2013)
- based on Intel(R) Media SDK (version: 4.0.760.60435)
Usage:
FRIMDecode.exe mpeg2|h264|vc1|mvc|jpeg [options]
-i InputBitstream -o OutputYUVFile
options:
[-sbs|tab] - output file is in side-by-side or top-above-below
format, valid only for multiview
[-hw] - use platform specific SDK implementation,
if not specified software implementation is used
[-low_latency] - configures decoder for low latency mode
(supported only for H.264 and JPEG codec)
[-calc_latency] - calculates latency during decoding and prints log
(supported only for H.264 and JPEG codec)
[-jpeg_rotate n] - rotate jpeg frame n degrees (n=90,180,270)
[-nv12] - output is in NV12 color format,
if not specified then YUV420 is used
[-d3d] - work with d3d9 surfaces
[-d3d11] - work with d3d11 surfaces
[-r] - render decoded data in a separate window
[-wall w h n m f t tmo] - same as -r, and positioned rendering window
in a particular cell on specific monitor
w ... number of columns of video windows on selected monitor
h ... number of rows of video windows on selected monitor
n(0,.,w*h-1) ... order of video window in table that will be rendered
m(0,1..) ... monitor id
f ... rendering framerate
t(0/1) ... enable/disable window's title
tmo ... timeout for -wall option, in seconds
Press 1 to toggle fullscreen rendering on/off
|
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it.
Last edited by HWK; 30th October 2013 at 23:38.
|