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. |
21st November 2013, 22:46 | #241 | Link |
Registered User
Join Date: Jul 2009
Posts: 244
|
Here Google Docs : FRIMTranscode GUI
You can click on the picture in the website. |
21st November 2013, 22:52 | #242 | 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. |
|
21st November 2013, 23:00 | #243 | Link | ||
Registered User
Join Date: Jul 2009
Posts: 244
|
Quote:
Quote:
Don't hesitate for others suggestions. |
||
21st November 2013, 23:09 | #244 | Link | |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Quote:
|
|
21st November 2013, 23:25 | #248 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,975
|
Quote:
I've done it and on my 3D BD player it works fine. Last edited by jdobbs; 21st November 2013 at 23:34. |
|
21st November 2013, 23:32 | #249 | Link |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Okay, first 5000 frame-long test encode using FRIMTranscode GUI is done. The result is very nice. I selected VBR, and entered 22000 in the CBR box and 48000 in the VBR box.
Dropped the combined output file into latest tsMuxer, output into BD3D ISO, then mounted ISO in virtual drive and used BDInfo to measure bitrates. Average bitrate for AVC was 12018 kbps and 9962 kbps for MVC. In total that's very close to the 22000 kbps average set in the CBR box. As for max bitrate... I'm not quite sure how to read BDInfo's output. It says 39485 kbps for "Max 1-sec Rate", but that appears to be for AVC only. That's the MVC on top and AVC underneath: Last edited by colinhunt; 21st November 2013 at 23:39. |
21st November 2013, 23:40 | #251 | Link | ||
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
I should also mention I ran them one by one. Quote:
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. Last edited by HWK; 21st November 2013 at 23:57. |
||
21st November 2013, 23:52 | #254 | Link |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
I'm no good at this command line lark, it seems. Transcoding ends with a bunch of error messages when I try to run this:
Code:
frimtranscode -i::mvc t:left.264 t:right.mvc -o::mvc outputcombined.264 -hw -labrc 22000 0 -profile high -level 4.1 FRIM Transcoder version 1.15 (build: Nov 12 2013) - based on Intel(R) Media SDK (version: 4.0.760.60435) MFX HARDWARE Session 0 API ver 1.7 parameters: Input video: AVC Output video: AVC MFX dll: C:\Users\xxxxxxxxxxxx\encoders\libmfxhw32.dll Session 0 was NOT joined with other sessions Transcoding started Return on error: error code -3, .\src\sample_utils.cpp 1472 Return on error: error code -3, .\src\pipeline_transcode.cpp 1783 Return on error: error code -3, .\src\pipeline_transcode.cpp 443 Return on error: error code -3, .\src\pipeline_transcode.cpp 744 Transcoding finished MFX session 0 transcoding FAILED Processing time: 0.11 sec Number of processed frames: 0 Return on error: error code 1, .\src\sample_multi_transcode.cpp 603 edit: Figured it out. When running in -hw mode and using LA BRC (-labrc), Transcode will stop in error if "-level 4.1" is used. Switching from LA BRC to -vbr allows the use of -level 4.1. Last edited by colinhunt; 22nd November 2013 at 00:14. |
21st November 2013, 23:54 | #255 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,975
|
Quote:
Thanks for the info you provided. Last edited by jdobbs; 21st November 2013 at 23:58. |
|
21st November 2013, 23:59 | #256 | Link |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Jdobbs, I am just curious how soon one may expect 3D support. Just rough timeline will do for know.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. Last edited by HWK; 22nd November 2013 at 00:14. |
22nd November 2013, 00:03 | #257 | Link |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Well, poop. Can't use -hw option in FRIMTranscode: output is garbled, just riddled with artefacts. I believe it's the same issue I discovered earlier, i.e. hardware encoding works fine, but hardware decoding is futzed up.
Last edited by colinhunt; 22nd November 2013 at 00:06. |
22nd November 2013, 00:08 | #258 | Link |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Frim 1.16
Hi,
Minor update FRIM 1.16 is available. Key changes: FRIM Encoder 1.16 - workaround for Avisynth error (occasionally Avisynth 2.5.8 doesn't feed R-eye in -sbs mode) - please try if it helped FRIM Encoder and Transcoder 1.16 - allowed bitrate higher than 65000 Kbps (although I personally doubt whether it is reasonable and useful ) (rest is in Release notes) |
22nd November 2013, 00:09 | #259 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
Thank you
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. |
|
22nd November 2013, 00:11 | #260 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
I notice when you mux file with tsmuxer number of frame is different. However if you extract it there are same.
Quote:
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. Last edited by HWK; 22nd November 2013 at 00:15. |
|
Tags |
encoders, mvc |
|
|