Free H.264 MVC 3D Encoder

[HWK]

Originally Posted by videofan3d

Guys, maybe I got it :-)

I guess you all copied the sample command "FRIMEncode ..." from PDF, right?

Please note, that PDF is generated from MS Word, and MS Word is doing some smart formatting and sometimes replaces character 0x2D (hyphen '-') by 0x96 (which also looks like hyphen!!!), but it is some "pseudo-hyphen" not recognized by cmd.exe

Please retype the command directly and manually in notepad, and it will work

In case anyone needs it here are all available options for encoder and decoder

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

[frencher]

Originally Posted by videofan3d

Just to comment, -u 1 is the highest quality, but also slowest encoding (naturally).
I was positively surprised with Intel Media encoding quality.
In general, I use only high bitrates, 24 mbit/s for 2D and 40 mbit/s for 3D (quality is most important for me).

As for test I encoded so far two of my own "3D-films" recorded by 3D-camcorder Panasonic Z10000 - and I didn't notice any ugly artefacts on this high bitrate.

x264 is probably better but it doesn't support MVC-3D (unfortunately there is no big demand for it... )

Fixed nows thanks

Works fine with this CMD Line:

FRIMDecode mvc -i MVCCombined.h264 -o \.\\pipe\TMP.yuv | FRIMEncode.exe mvc -i \.\\pipe\TMP_L.yuv -i \.\\pipe\TMP_R.yuv -viewoutput -o output_L.h264 -o output_R.h264 -w 1920 -h 1080 -f 23.976 -b 40000 -u 1

[HWK]

Originally Posted by videofan3d

Just to comment, -u 1 is the highest quality, but also slowest encoding (naturally).
I was positively surprised with Intel Media encoding quality.
In general, I use only high bitrates, 24 mbit/s for 2D and 40 mbit/s for 3D (quality is most important for me).

As for test I encoded so far two of my own "3D-films" recorded by 3D-camcorder Panasonic Z10000 - and I didn't notice any ugly artefacts on this high bitrate.

x264 is probably better but it doesn't support MVC-3D (unfortunately there is no big demand for it... )

At least public got the encoder which does MVC for free

[colinhunt]

So if I want to test this, how do I get from a BD3D to a file I can feed to the encoder?

[HWK]

Originally Posted by colinhunt

So if I want to test this, how do I get from a BD3D to a file I can feed to the encoder?

You will require MVC decoder in order to decode files. One which is built in with this release can't decode from SSIF file. Second method is to use Full SBS which require 3840*1080 resolution. Last option require to create yuv file and which are not compressed and will go quite large in size.

[frencher]

Originally Posted by HWK

You will require MVC decoder in order to decode files. One which is built in with this release can't decode from SSIF file. Second method is to use Full SBS which require 3840*1080 resolution. Last option require to create yuv file and which are not compressed and will go quite large in size.

Or use YUV without large size temporary file with this rapid CMD line

FRIMDecode mvc -i MVCCombined.h264 -o \.\\pipe\TMP.yuv | FRIMEncode.exe mvc -i \.\\pipe\TMP_L.yuv -i \.\\pipe\TMP_R.yuv -viewoutput -o output_L.h264 -o output_R.h264 -w 1920 -h 1080 -f 23.976 -b 40000 -u 1

[tymoxa]

frencher
Shouldn't it be \\.\pipe ?

Anyway it doesn't work for me
I can decode combined mvc to couple of yuv's with:

FRIMDecode.exe mvc -i MVCCombined.h264 -o test.yuv

then encode these with

FRIMEncode.exe mvc -i test_L.yuv -i test_R.yuv -o output_L.h264 -o output_R.h264 -viewoutput -w 1920 -h 1080 -f 23.976 -b 20000 -u 4

but with this line

FRIMDecode.exe mvc -i MVCCombined.h264 -o \\.\pipe\test.yuv | FRIMEncode.exe mvc -i \\.\pipe\test_L.yuv -i \\.\pipe\test_R.yuv -o output_L.h264 -o output_R.h264 -viewoutput -w 1920 -h 1080 -f 23.976 -b 20000 -u 4

it gives me an error

ERROR: Cannot open input file \\.\pipe\test_R.yuv
ERROR: File reader initialization failed.
ERROR: Cannot start encoding process.

Am i doing something wrong?

videofan3d
Why bitrate for main and dependent is almost the same? It is limitation of encoder?

[frencher]

Rapid package for test

[tymoxa]

Originally Posted by frencher

Rapid package for test

Nope. Same error with your batch file:

C:\temp\Demo FRIM version 1.00>FRIMDecode mvc -i MVCCombined.h264 -o \.\\pipe\FR
IM_TMP.yuv   | FRIMEncode.exe mvc -i \.\\pipe\FRIM_TMP_L.yuv -i \.\\pipe\FRIM_TM
P_R.yuv -viewoutput -o output_L.h264 -o output_R.h264 -w 1920 -h 1080 -f 23.976
-b 40000 -u 1

ERROR: Cannot open input file \.\\pipe\FRIM_TMP_L.yuv

ERROR: File reader initialization failed.

ERROR: Cannot start encoding process.

C:\temp\Demo FRIM version 1.00>pause
Press any key to continue . . .

[HWK]

Originally Posted by tymoxa

videofan3d
Why bitrate for main and dependent is almost the same? It is limitation of encoder?

You specify bitrate which is sum up of both streams and encoder will automatically choose bitrate for each file based on scene demand. Example if I set 20MB/s it may choose 13 for base view and 7 for dependent view or other way around depending on complexity of source also it will vary from one frame to another.

Set the bitrate and let encoder decide how to distribute between files and how much.

[videofan3d]

Originally Posted by tymoxa

Windows named pipes

Windows named pipe must have a specific name:

\\.\pipe\somename

Also try this batch file:


start FRIMDecode mvc -i MVCCombined.h264 -o \\.\pipe\FRIM_TMP.yuv (new command window will be opened)

pause (here you have to press any key when prompted)

FRIMEncode.exe mvc -i \\.\pipe\FRIM_TMP_L.yuv -i \\.\pipe\FRIM_TMP_R.yuv -viewoutput -o output_L.h264 -o output_R.h264 -w 1920 -h 1080 -f 23.976 -b 40000 -u 4


Remark: selecting -u 1 is highest quality, but also slowest. For first testing choose -u 4, or even -u 7 (fastest)

[frencher]

Why dont use FRIMTranscode.exe with both output: output_L.h264 and output_R.h264

[tymoxa]

Originally Posted by frencher

Why dont use FRIMTranscode.exe with both output: output_L.h264 and output_R.h264

How is that possible? Transcoder doesn't have -viewoutput option. It transcode to combined mvc. Is there any tool that can divide combined mvc into elementary streams?

[videofan3d]

Originally Posted by tymoxa

How is that possible? Transcoder doesn't have -viewoutput option. It transcode to combined mvc. Is there any tool that can divide combined mvc into elementary streams?

Current version of Intel Media SDK doesn't provide support for processing of basic and dependent views in separate files in FRIM Decode and FRIM Transcoder (unfortunately).

It provides "only" support for their creation in FRIM Encoder (fortunately) - hence we can create and multiplex our own 3D films in standard Blu-ray 3D format.

[tymoxa]

Originally Posted by videofan3d

Current version of Intel Media SDK doesn't provide support for processing of basic and dependent views in separate files in FRIM Decode and FRIM Transcoder (unfortunately).

That's why i asked about tool that can divide combined mvc into separate files. Is that kind of tool exist?

[Sharc]

Originally Posted by tymoxa

That's why i asked about tool that can divide combined mvc into separate files. Is that kind of tool exist?

http://www.3dtv.at/Products/MvcConverter/Index_en.aspx

[tymoxa]

Originally Posted by Sharc

http://www.3dtv.at/Products/MvcConverter/Index_en.aspx

Sorry, not exactly what i need.
MVCCombined.h264 is sum of .avc + .mvc created with MVCCombine.exe.
I asked about a tool that can divide MVCCombined.h264 into separate .avc + .mvc. without decoding.

[videofan3d]

Originally Posted by tymoxa

Sorry, not exactly what i need.
MVCCombined.h264 is sum of .avc + .mvc created with MVCCombine.exe.
I asked about a tool that can divide MVCCombined.h264 into separate .avc + .mvc. without decoding.

I'm not aware of any such tools. Such process is probably not simple (if it would have to reliable) - it would require deeper .h264 stream analysis.

Btw. where can I get MVCCombine.exe which you mentioned?

[physic]

tymoxa provide me combined AVC+MVC track example. I am going to support such tracks in tsMuxeR during weekend.

[videofan3d]

Originally Posted by physic

tymoxa provide me combined AVC+MVC track example. I am going to support such tracks in tsMuxeR during weekend.

I will send you both tonight with some further info - thanks!