Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
30th October 2013, 10:33 | #1 | Link |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Free H.264 MVC 3D Encoder
(Project is mirrored on site videofan3d)
Intel Media SDK provides framework for MPEG2, H.264 AVC/MVC-3D, and H.265 HEVC encoding and decoding. SDK is supported on Windows 7, Windows 8.x, Windows 10 and it can be freely distributed and used. Intel Media SDK is probably the only platform providing free MVC-3D encoding capabilities (end of 2013). FRIM is free SW package based on patterns and examples from this SDK. FRIM Encoder (command-line tool) converts planar-yuv file, named pipe, uncompressed avi or Avisynth script into elementary MPEG2, H.264 AVC/MVC-3D or H.265 HEVC streams. Resulting elementary video streams can be then multiplexed into transport stream (.ts, .m2ts) or Blu-ray directory structure. tsMuxeR 2.1.2 (and higher) is needed for 3D Blu-ray multiplexing. FRIM Decoder (command-line tool) converts elementary or transport streams (MPEG2, H.264 AVC/MVC-3D, H.265 HEVC, VC1) into planar-yuv. Output can be either regular file or Windows named pipe. Output to a pipe allows further YUV processing without consumption of enormous diskspace. FRIM Source is Avisynth plugin for sequential reading of elementary or transport streams (MPEG2, H.264 AVC/MVC-3D, H.265 HEVC, VC1) in Avisynth scripts. FRIM Export is plugin for Adobe Premiere Pro (CS6) for direct export and encoding to MPEG2, H.264 AVC/MVC-3D or H.265 HEVC elementary streams FRIM Import is plugin for Adobe Premiere Pro (CS6) for import of 3D-material recorded in AVCHD-3D format (produced by camcorders like Sony HXR-NX3D1 or Panasonic Z10000). FRIM Import and FRIM Export together support rendering workflow without re-encoding to any intermediate format. FRIM executables and documentation can be downloaded from: 2020-03-08: FRIM version 1.31 (x86) - suitable for direct decoding/encoding and Avisynth 2.6.0 (Intel Media SDK 2019 R1) 2020-03-08: FRIM version 1.31 (x64) - suitable for direct decoding/encoding (also HEVC), Adobe Premiere Pro and Avisynth+ (Intel Media SDK 2019 R1) - HEVC 10-bit support 2019-04-16: FRIM version 1.30 (x86) - suitable for direct decoding/encoding and Avisynth 2.6.0 (Intel Media SDK 2018 R2) - maintenance release 2019-04-16: FRIM version 1.30 (x64) - suitable for direct decoding/encoding (also HEVC), Adobe Premiere Pro and Avisynth+ (Intel Media SDK 2018 R2) - maintenance release 2018-07-09: FRIM version 1.29 (x86) - suitable for direct decoding/encoding and Avisynth 2.6.0 (Intel Media SDK 2018 R1) 2018-07-09: FRIM version 1.29 (x64) - suitable for direct decoding/encoding (also HEVC), Adobe Premiere Pro and Avisynth+ (Intel Media SDK 2018 R1) 2017-07-08: FRIM version 1.27 (x86) - suitable for direct decoding/encoding and Avisynth 2.6.0 (Intel Media SDK 2017 R1) 2017-07-08: FRIM version 1.27 (x64) - suitable for Adobe Premiere Pro and Avisynth+ (Intel Media SDK 2017 R1) 2016-01-16: FRIM version 1.26 (x86) - suitable for direct decoding/encoding and Avisynth 2.6.0 (Intel Media SDK 2016) 2016-01-16: FRIM version 1.26 (x64) - suitable for Adobe Premiere Pro and Avisynth+ (Intel Media SDK 2016) 2015-05-10: FRIMSource64.dll (x64) - 64-bit version of FRIM decoder (FRIMSource) for AviSynth+ (64-bit). 2015-03-28: FRIM version 1.25 (x86) - suitable for direct decoding/encoding and Avisynth (Intel Media SDK - INDE 2015 Update 1) 2015-03-28: FRIM version 1.25 (x64) - suitable for Adobe Premiere Pro (Intel Media SDK - INDE 2015 Update 1) 2015-02-28: FRIM version 1.24 (withdrawn) 2014-03-22: FRIM version 1.23 (x86) - suitable for direct decoding/encoding and Avisynth 2014-03-22: FRIM version 1.23 (x64) - suitable for Adobe Premiere Pro 2014-03-22: FRIM version 1.23 - Premiere - example of Adobe Premiere project 2014-02-02: FRIM version 1.22 (withdrawn) 2014-01-25: FRIM version 1.21 (withdrawn) 2014-01-13: FRIM version 1.20 (withdrawn) 2014-01-03: FRIM version 1.19 (withdrawn) 2013-11-26: FRIM version 1.18 (withdrawn) 2013-11-21: FRIM version 1.16 (withdrawn) 2013-11-12: FRIM version 1.15 (withdrawn) 2013-11-07: FRIM version 1.11 (withdrawn) 2013-11-05: FRIM version 1.10 (withdrawn) 2013-10-29: FRIM version 1.00 (withdrawn) Last edited by videofan3d; 8th March 2020 at 12:11. Reason: FRIM 1.31 - (Intel Media SDK 2019 R1) |
30th October 2013, 11:49 | #2 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. Last edited by HWK; 30th October 2013 at 11:57. |
|
30th October 2013, 11:53 | #3 | Link |
Registered User
Join Date: Oct 2006
Location: Kyiv, Ukraine
Posts: 117
|
videofan3d
Thanks for your effort. FRIM Decoder seems to work, but FRIM Encoder gives me an "Unknown codec" error (h264/mpeg2/mvc codec with .yuv/.avi/.avs/.pipe input). My Cpu is an old Core2Duo. |
30th October 2013, 12:00 | #5 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
You probably need to have installed proper codecs for VFW API. e.g. K-Lite Mega Codec Pack (10.0.5). |
|
30th October 2013, 12:03 | #6 | Link |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Just wanted to ask what kind of speed you get when encoding. Also post system specs as well.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. |
30th October 2013, 12:10 | #8 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
What kind of OS are you using.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. |
|
30th October 2013, 21:56 | #15 | Link | |
French Love
Join Date: Oct 2008
Location: France
Posts: 456
|
Hi very good news videofan3d
Same problem for me with batch file Code:
FRIMDecode mvc -i MVCCombined.h264 -o input.yuv Code:
FRIMEncode.exe mvc -i input_L.yuv -i input_R.yuv –viewoutput -o output_L.h264 -o output_R.h264 -w 1920 –h 1080 –f 23.976 -b 40000 –u 1 Quote:
__________________
2013-11-29 MVC Player Free v0.0.2.6 BD & 3D BD's Player, Demuxer v0.0.0.8b, Recoder. Tutorial Demo for MVC Player Free: Trailer 3D 3DBD's Free - v0.0.0.0005.exe Old Programing free for all. Last edited by frencher; 30th October 2013 at 22:22. |
|
30th October 2013, 22:29 | #16 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
I have Win8/64 and this command works - this is how I did all my tests... Can you send me the batch file itself to check it? |
|
30th October 2013, 22:34 | #17 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
I had failure as well with uncompressed out put with YV12 color space. I couldn't create h264 or mvc file. Also side by side didn't work for me either. I just noticed those who are having problem are on win7 including me and you are on win 8. Could it be OS or some dependency.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. |
|
30th October 2013, 22:48 | #18 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
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 Last edited by videofan3d; 30th October 2013 at 23:04. |
|
30th October 2013, 23:20 | #19 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. |
|
30th October 2013, 23:23 | #20 | Link |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
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... ) |
Tags |
encoders, mvc |
Thread Tools | Search this Thread |
Display Modes | |
|
|