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. |
9th November 2013, 02:00 | #123 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
(Not sure if problem is in .ssif itself, or in combining AVC+MVC, or in FRIM Decoder). This I need to investigate... |
|
9th November 2013, 02:06 | #124 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
I have looked to your issue with DirectShowMVCSource.dll in debugging mode. And very clearly - problem is in DirectShowMVCSource itself. Let me shortly describe you how FRIM Encoder works. FRIM Encoder opens and read avi file using VWF (Video For Windows) API - which is standard part of Windows from version 3.x. Avisynth script "input.avs" behaves like regular AVI and is for FRIM Encoder fully transparent. Once FRIM Encoder opens succesfully avs-script (~avi-file), it reads it frame by frame, and undelaying Avisynth driver does all operations described in the script on background (it is its responsibility). Now specifically: @HWK: In you case, when FRIM Encoder tries to open ENCODE_3D_MOVIE.avs, this operation fails because Avisynth cannot initialize CoreAVCDecoder.dll. It is probably because you are running process from another directory. When I put everything into one directory and ran it within this directory, all worked. Once I moved FRIMEncode.exe into another, or started batch file from outside this directory, underlaying Avisynth could not initialize CoreAVCDecoder.dll and opening failed - consequently FRIM Encoder reported "Cannot read YUV420 frame". Setting PATH properly could help. @frencher: In your case - problem with lost R-eye is caused by the DirectShowMVCSource.dll itself - apparently there is some bug. FRIM Encoder reads frame from VFW-AVI, but it doesn't know what is hidden behind it. VFW-API function AVIStreamGetFrame() simply returns full frame (3840x1080 in your case) If right-eye is black, then it means that SsifSource3 in your .avs script didn't return data correctly File1 = "Q:\BDMV\STREAM\SSIF\00000.ssif;0" Left1 = SsifSource3(File1,avc_view=TRUE,mvc_view=FALSE) Right1 = SsifSource3(File1) Video1 = StackHorizontal(Left1,Right1) Video = Video1 Video = Video.ConvertToYV12() Return Video I expect that the same symptom you will realize when you open and play Preview.avs using Windows Media Player, StereoscopicPlayer, MPC-HC or any other player which uses the same VFW-API. Library DirectShowMVCSource.dll is not official part of Windows, neither provided by any HW vendor. I don't know who is author of DirectShowMVCSource.dll and how does he support it. In the associated readme.txt he himself admits, that "... this as an hack to the original DirectShowSource source code with possible bugs, maybe memory leaks... " So, I recommend to approach author to investigate and fix... |
|
9th November 2013, 03:15 | #125 | Link | |||
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
Also calling application must be inside magic path, which is "STEREOPLAYER.exe" folder in this case. Quote:
Quote:
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. Last edited by HWK; 9th November 2013 at 03:58. |
|||
9th November 2013, 08:35 | #126 | Link |
Registered User
Join Date: May 2006
Posts: 3,997
|
Just in case someone wants to ceck / improve DirectShowMVCSource.dll, here the download link including the source.
|
9th November 2013, 09:23 | #127 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
Please give to FRIM Encoder such environment, that it can find all necessary components, in this case indirectly. Next version of FRIM will have an option to display some error messages reported by AviSynth, this will allow you to see what is wrong in the underlaying avisynth script. |
|
9th November 2013, 09:38 | #128 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
Please accept an axiom: Each and every program has bugs. And in our particular case we are processing whole long chain of components - source data - avisynth script (=its functions written by whoever) - avisynth driver - Windows drivers (VFW, DirectShow) - FRIM Encoder - Intel Media SDK - and user him/ser-self ! Each part HAS some bugs, some of them can be overcome in other part, some need to be fixed on proper place. Number of bugs decrease by time and by support of vendor - but it never drops to zero So never presume some applications to be bug-free. Our SW world is too complex. Just for fun: Oracle published statistics which shows that in average there is one bug on every 10 lines of code! (but it is another discussion belonging to different thread ) |
|
9th November 2013, 10:14 | #129 | Link |
Registered User
Join Date: May 2006
Posts: 3,997
|
Environment which works here:
- Put the FRIM package into a Directory, e.g. FRIM - Create a subdirectory under FRIM with Name stereoplayer.exe which contains the corresponding files plus a copy of FRIMEncode.exe Script directshowMVC.avs (in the FRIM Directory): Code:
LoadPlugin("c:\..your path ...\FRIM\stereoplayer.exe\DirectShowMVCSource.dll") V2=DirectShowMVCSource("F:\BDMV\STREAM\SSIF\xxxxx.SSIF") V1=DirectShowMVCSource("F:\BDMV\STREAM\SSIF\xxxxx.SSIF",decodeleft=true) StackHorizontal(V1,V2) ConvertToYV12().AssumeFPS(24000,1001) Code:
"C:\...your path....\FRIM\stereoplayer.exe\FRIMEncode.exe" mvc -avi -sbs 2 -i directshowMVC.avs -viewoutput -o Base.avc -o Dependent.mvc -w 1920 -h 1080 -l 4 -cpbsize 3750 -vbr 6000 15000 -u 4 -profile high -level 4.0 -gop 24 4 0 O But as I wrote before FRIMEncode crashes after few thousand frames with error: M_Alloc; error allocing 4552128 Last edited by Sharc; 9th November 2013 at 10:23. |
9th November 2013, 10:45 | #130 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
Meaning: how EXACTLY does this error display? There was probably some info in which file/line of code it happened... I need to simulate it first... Last edited by videofan3d; 9th November 2013 at 10:49. |
|
9th November 2013, 11:19 | #131 | Link | |
Registered User
Join Date: May 2006
Posts: 3,997
|
Quote:
However, from the Windows log there is an indication that divX.dll is responsible. Translated from German: Name of the faulty application: FRIMEncode.exe, Version: 0.0.0.0, Time stamp: 0x527b8642 Name of the faulty module: DivX.dll, Version: 6.9.2.26, Time stamp: 0x4b7ee5fa Exception code: 0xc0000005 Error offset: 0x00118a05 ID of the faulty process: 0x15cc Start time of the faulty application: 0x01cedd26bf27d9c1 Path of the faulty application: C:\Program Files Video\FRIM\stereoplayer.exe\FRIMEncode.exe Path of the faulty module: C:\Windows\system32\DivX.dll Why gets DivX.dll involved at all? Update 1: I uninstalled DivX, now everything seems to work as expected ..... no crash ..... continuing testing ..... (I had DivX on my system for trying their HEVC/h265 encoder) Update 2: Now I run into another problem: No crash, but after some 1000 frames the dependent output file silently stops to grow, and only the base view continues encoding/growing. No error message, it happens silently. I guess I stick to the named pipe variant which worked flawlessly for the entire 2:25 hours movie. Update 3: Amazing. After a couple of new attempts with the directshowMVCSource variant I am now at frame 100'000 without a problem..... a miracle or a mystery???? Last edited by Sharc; 9th November 2013 at 19:59. Reason: Added |
|
9th November 2013, 15:51 | #133 | 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. |
|
9th November 2013, 16:12 | #134 | 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. |
|
9th November 2013, 23:39 | #136 | Link | |
Registered User
Join Date: Sep 2013
Location: Czech Republic
Posts: 321
|
Quote:
But you need to have proper HW library libmfxhw32.dll (which might be even HW dependent, I don't know). I cannot test it cause I have nVidia GPU, not Intel GPU... |
|
10th November 2013, 01:39 | #137 | Link | |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Quote:
Code:
ERROR: Cannot initialize Intel Media SDK session. ERROR: Cannot start encoding process. update: Downloaded the latest drivers from Intel's website and installed them. They created a "Media SDK" directory under Program Files (i.e. 64bit), inside which I found a newer version of the dll (actually two, 32bit and 64bit dlls). Replaced the dll in FRIM directory with the new one, added -hw to both decoder and encoder options -- and it works. Both decoding and encoding are now running on HD4000. I've got quality set to "-u 3" and the system did 1000 frames of decode/encode in 100 seconds. Last edited by colinhunt; 10th November 2013 at 02:24. Reason: update |
|
10th November 2013, 01:40 | #138 | Link | |
French Love
Join Date: Oct 2008
Location: France
Posts: 456
|
Quote:
Thank
__________________
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; 10th November 2013 at 01:45. |
|
10th November 2013, 11:41 | #139 | Link |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Ehh, I thought I was being clever by trying to run 2 encodes simultaneously. Decode/encode on HW uses less than 50% CPU so I thought I'll run another encode on the side, on software only. Turns out that can't be done: piping throws up an error message.
|
Tags |
encoders, mvc |
Thread Tools | Search this Thread |
Display Modes | |
|
|