Quote:
Originally Posted by r0lZ
Oh, well, I've just checked the new FRIMSource with the new Intel Lib (both from your latest 32-bit distribution, v1.27) and it crashes! As I wrote above, the new FRIMSource works well with the old Intel Lib, but obviously, it has a bug when used with the new lib.
Can you have a look?
|
I quickly checked FRIMSource (32 and 64, hw and sw - all combinations) with the following .avs script:
Code:
LoadPlugin("c:\Prj\IntelMedia\_exe\win32\Release_v1.27\FRIMSource.dll")
#LoadPlugin("c:\Prj\IntelMedia\_exe\x64\Release_v1.27\FRIMSource64.dll")
FILE3D="c:\Prj\IntelMedia\_testing\PANY.m2ts"
FRIMSource(codec="mvc", filename=FILE3D, filename_dep=FILE3D, container="ts", platform="hw", \
layout="sbs", swaplr=false, cache=0, reload=true, num_frames=120, fastmode=true, log_file="c:\Prj\IntelMedia\_testing\Z1.log").ShowSMPTE(size=128)
No issue, no crash ... (and logfile confirmed activation of Intel 2017 libraries and API version 1.23)
Please check your configuration (PATH and installation) whether - by chance - some old libraries are not activated....
(FRIMDecode and FRIMSource have no functional changes in source code)