DG NV tools

[Guest]

Windows returns different information on the system call that I use.

Hey guys, just looking for a little advice or some pointers for anybody that's dealt with troubleshooting the following ...

First, a bit of background:
- Kids have some BDs, and although the claims of "more robust than DVD" are certainly true, they are still not invincible (have lost a couple recently, which has spurred this "backup" kick)

Now come the tricky part ... after ripping to HDD and playing some of the titles, I noticed alot of random "blockiness" when played back with "DXVA/Cuda" applications (tried MPC, KMPlayer, POTPlayer) ... when these players are instructed to use non DXVA/CUDA decoders (like ffms-mt, etc) the blockiness completely vanishes ...

I thought, ok, no biggy, I can just playback without hardware assist ... but then after indexing the files and try to work out "Crop" values in AvsP I noticed DGSource and DGIndex having the same "Blockiness" problem (which kinda shocked me because DGTools has always been my "Gold Standard" for fast, accurate decoding!!!)

Here is a screenshot of the problem:



The issue I have is that the "Blockiness" is not from the DGI file or the ripped source file and it seems to happen "randomly" ... here is what happens if I step 300 frame forward, then re-enter frame "3846" to jump to:



The artifact is completely gone!! Now this wouldn't generally worry me, as I would usually write this sort of thing off as random artifact from random jumping of frames in possibly buggy applications ... HOWEVER, these random "Blockiness" frames actually appear in the encoded file when I feed x264 the direct AVS file from the images above (DGSource filter only) ...

Now the things I have tried to resolve this:
- Update NVidia drivers to latest (they are dated 17-Jul-2010)
- Uninstalled every codec/codec packs on the system
- Updated Haali

So given the problem was first noticed on DXVA playback, and is now only evident with DGSource filters (DSS2, DSS, FFMS2 all work flawlessly - no frame corruption at all), I am kinda assuming it's got something to do with the PureVideo side of things ...

Does anybody have any ideas (or experience) with this type of issue and could give me some ideas on where to proceed from here?

The PC I have free to encode the kids titles is pretty gutless (AMD x3 with GT210 512MB GPU), so any speedups I can get by offloading decode to the GPU, I want to take!!

Due to the randomness of such events, and the fact that the source file appears flawless in other source filters, I haven't provided a snippet of the source file because I believe anybody with a fully functioning system will see all the frames just fine!! Is there a version of the NVidia PureVideo Drivers that's known to be flawless? - I just downloaded the latest ones ...

I also just found this:

The Nvidia GeForce 210 with the current driver, on the contrary, cannot be recommended even as a replacement for an integrated graphics core. The new card cannot play Blu-ray and DVD with high enough quality and does not support GPGPU/CUDA technologies (which means it cannot be used for video transcoding).

May the "low quality" talked about in the article be what I am seeing here?!? Anybody else with a 210 having similar artifacts with hardware decoding?!?

Thanks for anybody taking the time to help,

7ek

[MOS-Marauder]

7ekno:

Maybe u got a PCI/PCIe Card in your System that uses the Same IRQ or something like this. Theck in Your Mainboard Manual.

(I had this on a HTPC before....i had to remove a PCI Card in Order to get it work)


@Neuron

When i woke up today.. my Compi again welcomed me with a Cuviddecodepucture error and crashed NV Driver.

This Time i didnt run GPU-Z ... But when i started it this moment, VP usage was 0, RAM usage allmost zero /77 MB)

Src was from RTL-HD and this was the AVS.

LoadPlugin("C:\Program Files (x86)\megui-Dev-031-1061\tools\dgindexnv\DGDecodeNV.dll")
DGSource("F:\000-CAPTURE-BACKUP\____BluRay-BRENN\HD-Encode\Promi.Kocharena\misfits-karena01.dgi",fieldop=0, deinterlace=1)
crop( 36, 4, -8, 0)
LanczosResize(1280,720) # Lanczos (Sharp)

Src is 1920x1088i (1920x1080i ... due DGindexer cropped that 8 alone)

DGAVCIndexFileNV9 X32
C:\Program Files (x86)\megui-Dev-031-1061\tools\dgindexnv\

F:\000-CAPTURE-BACKUP\____BluRay-BRENN\HD-Encode\Promi.Kocharena\20100822 2009 - VOX HD - Promi Kocharena (Edited).ts 13054029288

STREAM 1
PKTSIZ 188
VPID 511
CLIP 0 0 0 8
RANGE 0 0 13054029287 0
AUDIO 203

SPS 413
PPS 445
SPS 413
PPS 445
RPS 453
I 468

The Crash occurs in Pass 2 after approx 30%

Chris

[Guest]

@7ekno

Try driver version 196.21.

Post a sample of the source with instructions to allow me to reproduce the issue. It could be a random access issue in DGNV but I need your sample to test that. You can use TS trim in DGIndexNV or DGSplit to cut a sample of the M2TS.

@MOS-Marauder

Are you getting this error in MEGUI? If so, does it happen when you do things manually?

Thanks guys for the replies

After reading a bit about the 210's on the Intrawebs it seems there are a few with "quality" type problems ...

Here's exactly how I fixed it:
- Swapped GeForce 210 card for GeForce 9800GT card from an old PC

That is it, no new drivers, no removal of any other codecs, nothing but a straight GPU card swap ...

I get the feeling the artifact is GeForce210 related GT240 ordered for this conversion task, but in the mean time, I will give your versions of the drivers a go Neuron

EDIT: Just for completeness, I swapped back (from the 9800GT) to the GeForce210 and tried a couple different revisions of the drivers including 196.21 (with the standard reboot, etc inbetween), NOTHING fixed it .... the only conclusion I can draw from this experience is there must be something firmware/driver related specific to the GeForce210 series of cards .... wonder how many other 210 owners are currently troubleshooting bizzare macroblocking / pixelation / blocking without suspecting their cards !!

Thanks,
7ek

[MOS-Marauder]

Originally Posted by neuron2

@MOS-Marauder

Are you getting this error in MEGUI? If so, does it happen when you do things manually?

Hm i always use MeGui for 2pass encodes.

Pass 2 was already running and megui is also only executing normal commandlines....

Nothing else grabbed onto the VP during this.

All this only happens on 1080i sources, not on 720p or 576 sources...

(i guess with 64bit wrapper because im using win7 x64)

I can try the same encode again manually @CLI. but this is no real proof because sometimes it works sometimes not. (if i now restart the MeGui Que it my work...)


Chris

[Guest]

Originally Posted by MOS-Marauder

I can try the same encode again manually @CLI. but this is no real proof because sometimes it works sometimes not.

If it never fails manually then it proves something.

[MOS-Marauder]

Originally Posted by neuron2

If it never fails manually then it proves something.

OK well see xD

Trying manually ...


Chris

[MOS-Marauder]

Trying with this line (pass1) and then pass 2....

avs4x264.exe --level 4.1 --ref 4 --no-fast-pskip --subme 6 --bframes 3 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --threads auto --pass 1 --bitrate 3600 --stats "1.stats" --output pass1.mkv misfits-karena01.avs

This time it crashed in pass 1 at 19%.

Killed my Nvidia Driver and stopped encoding.

Edit: 2nd try.. simply started the above line again... atm 33%...still encoding...Video Engine Load approx 70%, RAM unter 300....

Edit2: Now crashed at 50%.. (see Pic)



Chris

[Groucho2004]

Originally Posted by MOS-Marauder

avs4x264.exe

What's that? Did you rename x264.exe?

Just in case you don't understand what Don means by manually:

- Create a DGI and script with DGIndexNV
- Feed the script to x264 (vanilla build)

[Guest]

Originally Posted by MOS-Marauder

This time it crashed in pass 1 at 19%.

Please try to duplicate this with a smaller stream that you can provide to me.

Also, what is avs4x264.exe?

[kemuri-_9]

Originally Posted by neuron2

Also, what is avs4x264.exe?

It is a utility generally used by MeGUI to automatically pipe video frames from 32bit avisynth to 64bit x264.

the codebase for it is mostly...
an outdated version of x264's own avs demuxer,
altered to spawn a process of 64bit x264 and write the avisynth frames to that process's stdin.
(No I didn't write it, but I've seen the source)

[Groucho2004]

Originally Posted by kemuri-_9

It is a utility generally used by MeGUI to automatically pipe video frames from 32bit avisynth to 64bit x264.

Is this the same as avs2yuv from Loren Merrit?

[Guest]

Originally Posted by kemuri-_9

It is a utility generally used by MeGUI to automatically pipe video frames from 32bit avisynth to 64bit x264.

I'd like OP to do it manually using plain vanilla 32-bit components.

We need to eliminate as many variables as possible.

[MOS-Marauder]

Originally Posted by neuron2

I'd like OP to do it manually using plain vanilla 32-bit components.

We need to eliminate as many variables as possible.

Ok i try the same thinggy with x264 32bit... (and 30% less performance)

And yes avs4x264 is a wrapper that handles the Video of Avisynth 32bit to x264_64.exe .


Edit: crashed as well.. (See Picture)

Chris

[kemuri-_9]

Originally Posted by Groucho2004

Is this the same as avs2yuv from Loren Merrit?

No, avs2yuv does not automatically spawn a process of x264 and write to its stdin.
Doing that would defeat its purpose of being able to run avisynth under wine to pipe to a linux binary of x264/ffmpeg.

[MOS-Marauder]

Originally Posted by kemuri-_9

No, avs2yuv does not automatically spawn a process of x264 and write to its stdin.
Doing that would defeat its purpose of being able to run avisynth under wine to pipe to a linux binary of x264/ffmpeg.

I only see "x264_64" in my Tasklist ...


Now i let the DGTools do all... i put the crop parameters into the DGI and Deint + Resize via DGTools W/H parameter... Noticed its gettinig 20 fps slower then default crop/ Lanczos resize..

Crashed my NV driver allmost instantly...1st try after 3 minutes, second one directly....

Chris

[Guest]

Chris, I need a stream to duplicate it.

[krosswindz]

I have a source which requires the field order transition to be fixed. When using DGIndex one could use the built in tool for this purpose. How does one achieve something similar using DG NV tools? Setting varying field order to TFM doesnt help as I still have ghosting. Setting fieldop=1 to force film still leaves some artifacts. Any suggestions?

[MOS-Marauder]

Originally Posted by neuron2

Chris, I need a stream to duplicate it.

The Problem is.... the Src stream is 13 GB xD

I can give u FTP access to it but it will take at least 2 Days foru to download it ....


Chris