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. |
7th February 2014, 21:04 | #521 | Link |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
This is strange, this is how it should be used.
I ran your command without any issues c:\Prj\IntelMedia\_bin\Win32\Release\FRIMDecode -i::mvc SRC_L.h264 SRC_R.h264 -sbs -o - | c:\Prj\IntelMedia\_bin\Win32\Release\FRIMEncode -sbs 2 -i - -o::mvc Z.h264 -w 1920 -h 1080 -f 23.976 -vbr 28000 40000 FRIM Encoder version 1.22 (build: Feb 2 2014) - based on Intel(R) Media SDK Media SDK impl HARDWARE - D3D9 (C:\Program Files\Intel\Media SDK\libmfx hw32.dll) Media SDK version 1.7 Memory type System Input format YUV420 Output video AVC Source picture: Resolution 1920x1088 Crop X,Y,W,H 0,0,1920,1080 Destination picture: Resolution 1920x1088 Crop X,Y,W,H 0,0,1920,1080 Frame rate 23.976 Bitrate control VBR avg,maximum 28000,40000 GOP structure: GOP length 24 I-/P-frame distance 4 IDR-frame interval 0 GOP type Opened Num of slices 6 Target usage 4 (balanced) Processing started Frame number: 276 Processing finished in 3.43 seconds Please try it with FRIMEncode -sw (or maybe also for FRIMDecode) (I faced some issues when running in -hw mode, HW acceleration depends on driver version) Last edited by videofan3d; 7th February 2014 at 21:40. |
7th February 2014, 22:33 | #522 | Link | |
Registered User
Join Date: Nov 2013
Location: Russia
Posts: 61
|
Quote:
P.S. What is your video card?(HD 4000).. And, why -hw not working at all, with first example.. Last edited by sef; 7th February 2014 at 23:27. |
|
7th February 2014, 23:38 | #523 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
I noticed that there are sometimes some limitations (or bugs?) when using -hw mode. In -hw mode Intel Media uses graphic driver and calls GPU accelerated routines. They are "bloody-faster", on decoding 8x(!), but with some limits. I can only guess: In -sw mode each process allocates resources (memory, thread pool, etc.) in regular PC memory, so there are almost no limitations. But in -hw mode each process can use/share resources on the GPU - which are not endless, and probably depend on specific given GPU. Once exhausted (for example when running more processes/threads), each additional process fails. And number of available resources probably depends on specific GPU family. My experience is to play with -hw and -sw, and try to find proper combination. |
|
8th February 2014, 15:36 | #525 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Quote:
Code:
#Created by BD Rebuilder - v0.46.12 (beta) LoadPlugin("C:\APPS\DGDecNV\DGDecodeNV.dll") DGSource("D:\WORKING8\WORKFILES\VID_00000.DGI", fieldop=0).Trim(0,-91203) Spline16Resize(3840,1080) ConvertToYV12().AssumeFPS(24000,1001) Code:
#Created by BD Rebuilder - v0.46.12 (beta) LoadPlugin("C:\APPS\DGDecNV\DGDecodeNV.dll") DGSource("D:\WORKING8\WORKFILES\VID_00000.DGI", fieldop=0).Trim(91203,0) Spline16Resize(3840,1080) ConvertToYV12().AssumeFPS(24000,1001) Code:
"D:\BD_Rebuilder\tools\FRIMEncode.exe" -avi -sbs 2 -i "D:\WORKING8\WORKFILES\VID_00000.1.avs" -viewoutput -o::mvc "D:\WORKING8\WORKFILES\VID_00000.1.264" "D:\WORKING8\WORKFILES\VID_00000.1.mvc" -w 3840 -h 1080 -f 23.976 -u 6 -cpbsize 3750 -l 6 -profile high -level 4.1 -vbr 23376 35000 -gop 24 4 0 S -maxdpb 4 Code:
"D:\BD_Rebuilder\tools\FRIMEncode.exe" -avi -sbs 2 -i "D:\WORKING8\WORKFILES\VID_00000.2.avs" -viewoutput -o::mvc "D:\WORKING8\WORKFILES\VID_00000.2.264" "D:\WORKING8\WORKFILES\VID_00000.2.mvc" -w 3840 -h 1080 -f 23.976 -u 6 -cpbsize 3750 -l 6 -profile high -level 4.1 -vbr 23376 35000 -gop 24 4 0 S -maxdpb 4 If I do a single file with the same settings etc... it will complete with no issues. It's not something critical -- as a single encode always works. The purpose of the experiment is just to save time when encoding. [Edit] Note also, that either of the two specific command lines above will complete successfully if run as a single instance -- but one will fail if run concurrently. Last edited by jdobbs; 8th February 2014 at 22:31. |
|
9th February 2014, 09:42 | #526 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
Maybe try also upgrade video driver - Intel HW library used to be part of it, and I realized it really matters what version you have. |
|
9th February 2014, 09:46 | #527 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
I'll try to simulate it somehow differently ... |
|
9th February 2014, 21:08 | #530 | 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. |
|
10th February 2014, 08:01 | #533 | Link | ||
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Not sure, if this is any help or not. I finish encoding world war z with multiple instance of FRIMEncode (x2) and it finished without a problem, will do Pacific Rim next with two instance and balance setting in FRIM.
(Around 60% done) (100% done) First Instance Quote:
Quote:
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. Last edited by HWK; 10th February 2014 at 16:01. |
||
10th February 2014, 12:13 | #534 | Link |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
I tried to reproduce it .... with mixed results ...
VID.1.avs: Code:
L=DirectShowSource("VIDEO.m2ts").Trim(0,-60000) StackHorizontal(L,L) Code:
L=DirectShowSource("VIDEO.m2ts").Trim(60000, 0) StackHorizontal(L,L) Input video was ~130000 frames long. Encode 1 Code:
FRIMEncode.exe -avi -sbs 2 -sw -i VID.1.avs -viewoutput -o::mvc VID.1.h264 VID.1.mvc -w 3840 -h 1080 -f 23.976 -u 6 -cpbsize 3750 -l 6 -profile high -level 4.1 -vbr 23376 35000 -gop 24 4 0 S -maxdpb 4 Code:
FRIMEncode.exe -avi -sbs 2 -sw -i VID.2.avs -viewoutput -o::mvc VID.2.h264 VID.2.mvc (...same params..) Running on i7 Haswell. And my results: When I run in -sw encoding mode, I faced the same (rather stochastic) failure on one process. When I run in -hw encoding mode, both finished correctly! As you commented, it is very time consuming to reproduce it. .... at this moment I can only add it will be very difficult to investigate the root cause - in order even to try to fix it ...) Last edited by videofan3d; 10th February 2014 at 12:17. |
10th February 2014, 16:08 | #535 | Link |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Did you get a significant speed-up with -hw set? Just wondering... I'm just going to disable multiple instance processing for FRIM in BD-RB, I think it's too unpredictable as to when it will or will not fail. While it was failing on every job before, I've since had a couple shorter jobs that completed successfully. The probability is that the issue is in the library somewhere anyway -- and that would have to be fixed by Intel anyway.
I think it's a lot more likely to happen when BD-RB starts the process and has to make frequent checks for process completion -- although I don't know why that would impact it. But even then it goes through thousands of frames (and a few hours) before it finally trips. Thanks for the look. Last edited by jdobbs; 10th February 2014 at 16:13. |
10th February 2014, 16:16 | #536 | Link |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Jdobbs, so you are dropping the idea of multi-process for time being. I manage to do something which is shown in post # 533 not sure if it is any good.
I am gone try later today with method similar to yours for dgdecnv.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. Last edited by HWK; 10th February 2014 at 16:18. |
10th February 2014, 16:25 | #537 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Quote:
I may just leave it in and use an undocumented hidden option to enable it. Unfortunately when it happens, the encode process never ends and BD-RB just keeps waiting. Eventually you have hit the "Abort" button. Unless you have "show_encoder=1" set in the config file, you don't even know why it's hung. Last edited by jdobbs; 10th February 2014 at 16:30. |
|
10th February 2014, 16:28 | #538 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
At least there is light at end of tunnel Anyways, like I said I will use script posted by you and see if it works at all for information purposes, if it works fine and if not good with me.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. Last edited by HWK; 10th February 2014 at 16:53. |
|
10th February 2014, 16:35 | #539 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Quote:
I see the same speed effect on my system when trying to run more than 2 instances. But that makes sense when there's no available processor bandwidth available. I would expect it to do better with -hw set. Last edited by jdobbs; 10th February 2014 at 16:42. |
|
10th February 2014, 16:38 | #540 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
http://forum.doom9.org/showthread.ph...83#post1667083
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. Last edited by HWK; 10th February 2014 at 16:41. |
|
Tags |
encoders, mvc |
Thread Tools | Search this Thread |
Display Modes | |
|
|