Glitch with Win7 64-bit and DG's Nvidia tools???

[laserfan]

I'm seeing a video glitch with my system (see clip and images posted starting at this post (http://forum.doom9.org/showthread.php?p=1303678#post1303678), and I need someone who has 64-bit XP and (obviously) an Nvidia card and DG's tools to confirm or deny that they see the glitch also.

EDIT: Confirmed with XP Pro 64-bit, now wondering if it appears too with Windows 7 RC 64-bit?

When I run DGAVCIndexNV I see the following running along with it (in this case the packaged nvcuvid.dll, tho the one(s) with Nvidia 186.18 show the same glitch). This is found by running Sysinternals ProcExp.exe and clicking on the running DGAVCIndexNV:

Process: DGAVCIndexNV.exe Pid: 1800

Name Description Company Name Version
ADVAPI32.dll Advanced Windows 32 Base API Microsoft Corporation 5.02.3790.3959
CLBCatQ.DLL COM+ Configuration Catalog Microsoft Corporation 2001.12.4720.3959
COMCTL32.dll User Experience Controls Library Microsoft Corporation 6.00.3790.3959
comctl32.dll User Experience Controls Library Microsoft Corporation 6.00.3790.3959
comdlg32.dll Common Dialogs DLL Microsoft Corporation 6.00.3790.3959
COMRes.dll COM+ Resources Microsoft Corporation 2001.12.4720.3959
ctype.nls
d3d8thk.dll Microsoft Direct3D OS Thunk Layer Microsoft Corporation 5.02.3790.1830
d3d9.dll Microsoft Direct3D Microsoft Corporation 5.03.3790.3959
DGAVCIndexNV.exe 1.00.0013.0000
GDI32.dll GDI Client DLL Microsoft Corporation 5.02.3790.4396
iphlpapi.dll IP Helper API Microsoft Corporation 5.02.3790.3959
kernel32.dll Windows NT BASE API Client DLL Microsoft Corporation 5.02.3790.4062
locale.nls
msvcrt.dll Windows NT CRT DLL Microsoft Corporation 7.00.3790.3959
ntdll.dll NT Layer DLL Microsoft Corporation 5.02.3790.3959
ntdll.dll NT Layer DLL Microsoft Corporation 5.02.3790.3959
nvapi.dll
nvcuda.dll NVIDIA Compatible CUDA Driver, Version 186.18 NVIDIA Corporation 6.14.0011.8618
nvcuvid.dll
ole32.dll Microsoft OLE for Windows Microsoft Corporation 5.02.3790.3959
OLEAUT32.dll Microsoft Corporation 5.02.3790.4202
PSAPI.DLL Process Status Helper Microsoft Corporation 5.02.3790.3959
quartz.dll DirectShow Runtime. Microsoft Corporation 6.05.3790.4283
R000000000003.clb
RPCRT4.dll Remote Procedure Call Runtime Microsoft Corporation 5.02.3790.4115
Secur32.dll Security Support Provider Interface Microsoft Corporation 5.02.3790.3959
SETUPAPI.dll Windows Setup API Microsoft Corporation 5.02.3790.3959
SHELL32.dll Windows Shell Common Dll Microsoft Corporation 6.00.3790.4315
SHLWAPI.dll Shell Light-weight Utility Library Microsoft Corporation 6.00.3790.3959
sortkey.nls
sorttbls.nls
unicode.nls
USER32.dll Windows USER API Client DLL Microsoft Corporation 5.02.3790.4033
uxtheme.dll Microsoft UxTheme Library Microsoft Corporation 6.00.3790.3959
VERSION.dll Version Checking and File Installation Libraries Microsoft Corporation 5.02.3790.1830
WINMM.dll MCI API DLL Microsoft Corporation 5.02.3790.3959
wow64.dll Win32 Emulation on NT64 Microsoft Corporation 5.02.3790.3959
wow64cpu.dll AMD64 Wow64 CPU Microsoft Corporation 5.02.3790.1830
wow64win.dll Wow64 Console and Win32 API Logging Microsoft Corporation 5.02.3790.3959
WS2_32.dll Windows Socket 2.0 32-Bit DLL Microsoft Corporation 5.02.3790.3959
WS2HELP.dll Windows Socket 2.0 Helper for Windows NT Microsoft Corporation 5.02.3790.1830

That this is a 64-bit XP problem is just a hunch but it's the only idea I have left to check out. TIA for looking!

[kemuri-_9]

I tried your sample and there's always a random glitch in the frame you denoted (frame 84 or so in that sample).

on xp x64 sp2 with a 8600 GT 512

[laserfan]

I tried your sample and there's always a random glitch in the frame you denoted (frame 84 or so in that sample).

on xp x64 sp2 with a 8600 GT 512Great! Well, not great because it means a problem with some code somewhere, but at least I think I can rest easy about my hardware.

Thanks so much for confirming! Maybe neuron2 can get his friends at Nvidia to take a look... :)

p.s. Yes I concur it is frame 84 where the glitch appears, per avs/vdub.

[laserfan]

Can someone with Win7 RC x64 (64-bit) and Nvidia look at this and confirm/deny the glitch?

[Sharc]

No glitch at all here with DGAVCIndexNV.
Vista SP2 / Nvidia 9600 GS / 182.50

[laserfan]

Well, no one here with Win7 64-bit that can confirm the glitch does not appear with it (and therefore is strictly an XP Pro x64 Edition problem)?

FWIW there are new Nvidia drivers 190.38 and I tried those. Still see the problem unfortunately (not that I expected a fix, but wanted to update anyway).

[GibsonXXI]

Cannot get DGTools(NV) to run at all on this PC using Win7 RC1.

CUVIDServer.exe starts when doing an analyze or encode DGM file from within MeGUI, but the whole thing crashes. Both MeGUI and DGMPGDecNV (or whatever process it is that's called by MeGUI).

CUVIDServer.exe does not crash, but everything else does. I'm thinking it may be a permissions issue. But seeing as Win7 isn't THAT different to Vista where permissions are concerned, it's got me stumped.

Unless it's something to do with DEP. I've never had Vista to be able to compare. Came straight from XP to Win7.

Motherboard does have memory execution protection enabled (another DEP-like feature on the MB) so it could also be this. But i'm not alone in having issues with DGToolsNV and Win7. There was another user on here with the same problem, although I forget his hardware setup.

Latest NVIDIA drivers (190.38) in use, and tried every beta of DGTools(NV) with identical results.

[Guest]

What happens if you do things manually outside of MEGUI?

[GibsonXXI]

I'm a newbie with video encoding neuron2. Wouldn't know where to start with the commandline, which is why I am using MeGUI.

Can just about edit a AVS with minimal options to do what I want. Anything above that is beyond me at the moment.

When I get more time I may copy out the commandline from the encoder setting section and have a play and see if I can get it to work like I think it ought to, but seeing as this is a quite powerful computer in it's own right, it's not a major priority for me right now.

DGDecode works fine with D2V files. It's only DGM processing that's not working so far (not tried the other decoders in the package due to lack of appropriate sources).

Anyway, not trying to hijack the thread, just pointing out that the other user may have issues under Windows 7 currently.

[Audionut]

I'm guessing you have a problem unrelated to dgdecode tools.

I have been using dgdecode tools successfully on various Win 7 builds.

What encoder are you using and avisynth version?

[Audionut]

Sorry for the slow reply laserfan. No problems here on Win7 x64.
I successfully encoded that sample with nil errors using dgavcindex.

[laserfan]

Sorry for the slow reply laserfan. No problems here on Win7 x64.
I successfully encoded that sample with nil errors using dgavcindex.
Thank you Audionut; finally I have confirmation that the problem appears to be solely related to XP Pro x64. EDIT: WAIT--Audionut, you didn't say "NV" anywhere in your posts, did you test w/DG's NV tools? We already know the regular tools work fine.

I have been spending the last couple of days and nights (!) trying to download the Win7 RC, to be able to test this myself, but am still only half-way thru the 3Gb file size. :eek:

The joy (NOT!) of satellite internet service.

@GibsonXXI I have never used MeGUI as from my own examination that GUI is every bit as complicated as doing it yourself from the command line! ;)

[Guest]

Wouldn't know where to start with the commandline, which is why I am using MeGUI. I didn't ask for any command line usage.

Can just about edit a AVS with minimal options to do what I want. Anything above that is beyond me at the moment. So make your project and make a simple script with DGSource(). Load the script into VirtualDub and try to play it. Does it work?

DGDecode works fine with D2V files. It's only DGM processing that's not working so far DGDecode does not work with DGM projects! You need DGDecodeNV.

[GibsonXXI]

DGDecode does not work with DGM projects! You need DGDecodeNV.

That's what I meant. DGDecode to create D2V files works. DGDecodeNV to analyse or encode DGM files isn't working for me under Win7 x64 in MeGUI. Which was why I referenced my lack of knowledge with the commandline. i.e: passing the resulting AVS to x264 to actually encode, the step that up till now has been failing for me in MeGUI on this system.

Also, If I try an analysis pass on a DGM file with DGDecodeNV, the progress bar in MeGUI never increments. The process just sits there doing nothing. Same behaviour when trying to encode without analysing. Whether using deinterlace option, or not. I'm not saying it's DGDecodeNV that's at fault. What I AM saying is that something between it and MeGUI isn't working for me in Win7 RC1 x64.

As i only have a licence for DGDecodeNV with this machine, am not able to test with my x32 Win7 machines.

I might as well add, that my current config includes two GTX260's in SLI, and the CPU is a Core-i7. SLi and PhysX is enabled.

i'll double check the paths i've specified for DGDecodeNV just to be sure, but seeing as these files were added to the MeGUI additional files area via the "browse dialog" I doubt it's path related.

I'll also test your other suggestion as I have Virtualdub installed.

EDIT: Creating a simple DGM file and playing it back through Virtualdub works as expected.

[Guest]

EDIT: Creating a simple DGM file and playing it back through Virtualdub works as expected. Then you need to bug the MEGUI folks.

[GibsonXXI]

Thank you Audionut; finally I have confirmation that the problem appears to be solely related to XP Pro x64. EDIT: WAIT--Audionut, you didn't say "NV" anywhere in your posts, did you test w/DG's NV tools? We already know the regular tools work fine.

I have been spending the last couple of days and nights (!) trying to download the Win7 RC, to be able to test this myself, but am still only half-way thru the 3Gb file size. :eek:

The joy (NOT!) of satellite internet service.

@GibsonXXI I have never used MeGUI as from my own examination that GUI is every bit as complicated as doing it yourself from the command line! ;)

I'm beginning to realise that myself. ;)

I came to MeGUI from AutoMKV, because AutoMKV while a fine util, didn't offer the level of customization I was after.

Now with MeGUI, i'm still having to do a lot of things manually because they are extra commands or functions that either aren't present by default in MeGUI, or don't work on the sources i'm working with.

That being the case i'm getting a cold hard brutal lesson in the peculiarities of encoding. Probably not helped by the fact the encodes i'm doing are all anime-related. And from reading some of the threads on here, i'm also beginning to realise this is one of the hardest things to encode well.

I'm learning quite a few things, albeit v.slowly. But some of the terms used in the encoding world makes my head spin, and i'm no idiot. It's a steep learning curve for sure. Not helped by the fact I live in a PAL region. And PAL anime generally means field blends. And those rank down in the 9th layer of suck, lol.

However, onwards & upwards.

[Guest]

The next thing to learn is not to discuss downloaded materials here, per rule 6. I have edited your post to remove all such discussion.

[Audionut]

EDIT: WAIT--Audionut, you didn't say "NV" anywhere in your posts, did you test w/DG's NV tools? We already know the regular tools work fine.

Sorry, yes I meant Don's NV tools.

[Audionut]

i.e: passing the resulting AVS to x264 to actually encode, the step that up till now has been failing for me in MeGUI on this system.

x264 is a whole lot easier to use through the command line these days. Look at the presets,

http://mewiki.project357.com/wiki/X264_Settings

It can be as simple as

x264.exe --preset slow --tune film -o c:\output\ouput.mkv c:\input\input.avs

edit: btw, any of this discussion should be here. http://forum.doom9.org/forumdisplay.php?f=77

Back on topic, I am having a problem with dgtools lately, It just works.

Thanks Don.

[laserfan]

Originally Posted by laserfan
EDIT: WAIT--Audionut, you didn't say "NV" anywhere in your posts, did you test w/DG's NV tools? We already know the regular tools work fine.Sorry, yes I meant Don's NV tools.Thanks for confirming. I think I finally have Win7 x64 in the can, so am only hours (days? weeks?) away from testing it myself! :p

[laserfan]

Ok, I have (finally) installed Win7 RC1 64-bit alongside my XP Pro x64 and the Win7 setup does not show the glitch. So I now see for myself (as Audionut has suggested already) that the problem is XP Pro x64-related and not my system, hardware, or PEBCAK.

Can't imagine myself what it is about MGM's lion that (in this one case) isn't processed properly by XP x64/nvidia/DGTools but there you have it.

For the record I've set myself up with Win7 7100 64-bit, nvidia 190.38 for same, AviSynth 2.5.8, VirtualDub 1.9.0, and NVBeta7. Amazingly this (and the license file from neuron2) was all I needed to check-out this problem.

Win7 is a trip after XP. Guess I will next have to force myself to learn a few tricks beyond "Sit", "Stay", and "Roll Over"! Then I'm gonna shoot XP Pro x64 in the head! :p

[Guest]

Good to hear, because you are a Doom9 old-timer that has been very helpful to me through the years in development of my tools, so I'd hate to see you left in the lurch.

[laserfan]

Good to hear...I should maybe have left well-enough alone, but being the anal sort that I am, I booted-back to XP and compared the old dga vs. the new dga I'd made with Win7/DGToolsbeta7 just to see if they were any different. The new dga (it was beta4 that made the older one) was different by

SIZ 1920 x 1088

where the old had said '1080'. What the hell, I tried your beta7 with XP Pro x64 and there is no glitch! Realizing you'd made numerous betas since I posted back on 12-July, I went-back and found that it was beta5 where the problem goes away. Note that my nvidia is new also, at 190.38.

So even XP Pro x64 seems good now...Sorry for all the bandwidth--after switching my focus from DGTools to XP x64 I didn't keep-up with the betas. Apparently missed the fix by exactly One (maybe something to do with losing D3D9?)... :o

p.s. The 1088 vs 1080 thing is just a distraction (tho it alerted me to try XP x64 again). The "bad" beta4 and the "good" betas 5 & 6 all show 1080.

[Guest]

maybe something to do with losing D3D9? That would be it. Thank you for the update.