[SOLVED] Avs2YUV error with DGDecodeNV

Support forum for DGDecNV
Post Reply
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

[SOLVED] Avs2YUV error with DGDecodeNV

Post by Guest 2 »

It was 2 weeks since my last encoding and today my usual script configuration gives error.

I have tried to change DGDecodeNV versions (137 and 145, indexing with the proper DGIndexNV), reinstall nvidia drivers and whatever came to my mind.

The following script works:

Code: Select all

SetMemoryMax(8000)
SetFilterMTMode("DEFAULT_MT_MODE", 2)
LoadPlugin("D:\eseguibili\media\MeGUI_x64\tools\lsmash\LSMASHSource.dll")
LWLibavVideoSource("E:\in\disaster_lwi.lwi")
crop(0, 140, 0, -140)
CompTest(1)
SMDegrain (tr=4, thSAD=400, refinemotion=false, n16=true, mode=0, contrasharp=false, PreFilter=4, truemotion=false, plane=4, chroma=true)
Prefetch(6)
This one throws me error:

Code: Select all

SetMemoryMax(8000)
SetFilterMTMode("DEFAULT_MT_MODE", 2)
LoadPlugin("D:\eseguibili\media\DGDecNV\x64\DGDecodeNV.dll")
DGSource("E:\in\1_43 disaster artist, The\disaster.dgi")
CompTest(1)
SMDegrain (tr=4, thSAD=400, refinemotion=false, n16=true, mode=0, contrasharp=false, PreFilter=4, truemotion=false, plane=4, chroma=true)
Prefetch(6)
Any idea?

Log follows:

Code: Select all

[2018-04-27][12:37:37] Simple x264 Launcher (Build #1124), built 2018-02-27
[2018-04-27][12:37:37] 
[2018-04-27][12:37:37] Job started at 2018-04-27, 12:37:37.
[2018-04-27][12:37:37] 
[2018-04-27][12:37:37] Source file : E:\in\1_43 disaster artist, The\disaster_4.avs
[2018-04-27][12:37:37] Output file : E:\in\1_43 disaster artist, The\disaster_4.mkv
[2018-04-27][12:37:37] 
[2018-04-27][12:37:37] --- SYSTEMINFO ---
[2018-04-27][12:37:37] 
[2018-04-27][12:37:37] Binary Path : D:\eseguibili\media\x264 launcher
[2018-04-27][12:37:37] Avisynth    : Yes
[2018-04-27][12:37:37] VapourSynth : No
[2018-04-27][12:37:37] 
[2018-04-27][12:37:37] --- SETTINGS ---
[2018-04-27][12:37:37] 
[2018-04-27][12:37:37] Encoder : x264 (AVC/H.264), 64-Bit (x64), 8-Bit
[2018-04-27][12:37:37] Source  : Avisynth (avs)
[2018-04-27][12:37:37] RC Mode : CRF
[2018-04-27][12:37:37] Preset  : slow
[2018-04-27][12:37:37] Tuning  : <None>
[2018-04-27][12:37:37] Profile : High
[2018-04-27][12:37:37] Custom  : --level 4.1 --keyint 240 --aq-mode 2 --sar 1:1
[2018-04-27][12:37:37] 
[2018-04-27][12:37:37] --- CHECK VERSION ---
[2018-04-27][12:37:37] 
[2018-04-27][12:37:37] Detect video encoder version:
[2018-04-27][12:37:37] 
[2018-04-27][12:37:37] Creating process:
[2018-04-27][12:37:37] "D:\eseguibili\media\x264 launcher\toolset\x64\x264_x64.exe" --version
[2018-04-27][12:37:37] 
[2018-04-27][12:37:38] x264 0.155.2901 7d0ff22
[2018-04-27][12:37:38] (libswscale 5.0.101)
[2018-04-27][12:37:38] (libavformat 58.10.100)
[2018-04-27][12:37:38] (ffmpegsource 2.30.0.0)
[2018-04-27][12:37:38] built on Feb 26 2018, gcc: 7.3.0
[2018-04-27][12:37:38] x264 configuration: --chroma-format=all
[2018-04-27][12:37:38] libx264 configuration: --chroma-format=all
[2018-04-27][12:37:38] x264 license: GPL version 2 or later
[2018-04-27][12:37:38] libswscale/libavformat/ffmpegsource license: GPL version 2 or later
[2018-04-27][12:37:38] 
[2018-04-27][12:37:38] Detect video source version:
[2018-04-27][12:37:38] 
[2018-04-27][12:37:38] Creating process:
[2018-04-27][12:37:38] "D:\eseguibili\media\x264 launcher\toolset\x64\avs2yuv_x64.exe"
[2018-04-27][12:37:38] 
[2018-04-27][12:37:38] Avs2YUV 0.24bm5
[2018-04-27][12:37:38] 
[2018-04-27][12:37:38] > x264 revision: 2901 (core #155)
[2018-04-27][12:37:38] > Avs2YUV version: 0.24.5
[2018-04-27][12:37:38] 
[2018-04-27][12:37:38] --- GET SOURCE INFO ---
[2018-04-27][12:37:38] 
[2018-04-27][12:37:38] Creating process:
[2018-04-27][12:37:38] "D:\eseguibili\media\x264 launcher\toolset\x64\avs2yuv_x64.exe" -frames 1 "E:\in\1_43 disaster artist, The\disaster_4.avs" NUL
[2018-04-27][12:37:38] 
[2018-04-27][12:37:39] 
[2018-04-27][12:37:39] PROCESS EXITED WITH ERROR CODE: -1073741819
[2018-04-27][12:37:39] 
[2018-04-27][12:37:39] IMPORTANT: The Avs2YUV process terminated abnormally. This means Avisynth or one of your Avisynth-Plugin's just crashed.
[2018-04-27][12:37:39] IMPORTANT: Please fix your Avisynth script and try again! If you use Avisynth-MT, try using a *stable* Avisynth instead!
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

What happens if you load that script directly in VirtualDub?

What happens if you remove the SetFilterMode call?
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

Post 1722 in the Simple Launcher thread at ??? appears related.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Avs2YUV error with DGDecodeNV

Post by Guest 2 »

admin wrote:
Fri Apr 27, 2018 6:19 am
What happens if you load that script directly in VirtualDub?
It loads and play but VDub2 crashes when exiting.
admin wrote:
Fri Apr 27, 2018 6:19 am
What happens if you remove the SetFilterMode call?
I tried to remove every MT related line and it gives same error.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Avs2YUV error with DGDecodeNV

Post by Guest 2 »

admin wrote:
Fri Apr 27, 2018 6:28 am
Post 1722 in the Simple Launcher thread at ??? appears related.
Thanks for pointing. Same error in MeGUI_x64 who uses same trick to x264.

EDIT: rollback to 391.35 and everything is fine.

Strange interaction between video drivers and avs2yuv :wow:
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

I'll install the bugged driver and check if I can see anything in the debugger. But for now you know the workaround.

I'll also report this to nVidia.

Thank you for bringing this to my attention, Guest 2.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Avs2YUV error with DGDecodeNV

Post by Guest 2 »

admin wrote:
Fri Apr 27, 2018 7:11 am
I'll install the bugged driver and check if I can see anything in the debugger. But for now you know the workaround.
I tried also 397.40-NProfile_geforceweb_win10_64bit_international from Vulcan beta and gives same error.
admin wrote:
Fri Apr 27, 2018 7:11 am
Thank you for bringing this to my attention, Guest 2.
You are always welcome.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

I don't see avs2yuv in my MEGUI folder. It also isn't shown in the update window. Are you sure about your claim it uses avs2yuv? Are you getting crashes in MEGUI?
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Avs2YUV error with DGDecodeNV

Post by Guest 2 »

admin wrote:
Fri Apr 27, 2018 7:17 am
I don't see avs2yuv in my MEGUI folder. It also isn't shown in the update window. Are you sure about your claim it uses avs2yuv? Are you getting crashes in MEGUI?
It uses avs4x26x in \MeGUI_x64\tools\x264. I think they are basically the same, if not correct me.

In the meanwhile:

https://forums.geforce.com/default/topi ... t-install/

Total havoc. :wow:
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

I just installed 397.31. I have 1080Ti. No problems with the install and no restart was required. Ran Simple Launcher 2.86.1124 with this script (all 32-bit):

loadplugin("d:\don\Programming\C++\dgdecnv\DGDecodeNV\x32\release\dgdecodenv.dll") # 2053.0.0.145
dgsource("H:\Streams\AVC\Frame Structure\Alba.dgi",fulldepth=false)

It ran successfully without crashing.

We'll have to wait and see what is going on with this driver. I haven't seen any problems with it so far.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Avs2YUV error with DGDecodeNV

Post by Guest 2 »

admin wrote:
Fri Apr 27, 2018 8:14 am
What is your OS? And what graphics card do you have?
Windows 10 x64 rs5 17655 / GTX 760
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

That's a Kepler so theoretically OK with 397.31.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Avs2YUV error with DGDecodeNV

Post by Guest 2 »

admin wrote:
Fri Apr 27, 2018 9:00 am
That's a Kepler so theoretically OK with 397.31.
Not in real life :lol:
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

So it seems. :cry:
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

I'm having one issue so far. VirtualDub(2) crashes on exit in a cuda module.

Gonna revert the driver.

EDIT: 391.35 does not crash.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Avs2YUV error with DGDecodeNV

Post by Guest 2 »

http://nvidia.custhelp.com/app/answers/detail/a_id/4661

Give them a spin.

P.S: Just discovered that Windows + CTRL + Shift + B restart video driver.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

Does that hotfix driver fix the original issue you had, i.e., crashing on exit in some apps?
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Avs2YUV error with DGDecodeNV

Post by Guest 2 »

admin wrote:
Fri May 04, 2018 10:24 am
Does that hotfix driver fix the original issue you had, i.e., crashing on exit in some apps?
Nope, just tried and same error when using DGSource.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: Avs2YUV error with DGDecodeNV

Post by admin »

Thanks for the testing. Fixed in slipstream 147.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Avs2YUV error with DGDecodeNV

Post by Guest 2 »

admin wrote:
Sat May 05, 2018 7:30 am
Thanks for the testing. Fixed in slipstream 147.
You are always welcome.

What did they change, at the end?
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: [SOLVED] Avs2YUV error with DGDecodeNV

Post by admin »

It was my bug and a change in the driver exposed it. I was freeing some CUDA host memory in a thread without setting the correct CUDA context. Previously it apparently didn't matter. One might think that the address is sufficient, but it is not now true.

Still, nVidia should return a proper error and not crash.
Post Reply