Log in

View Full Version : DG NV tools


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 [51] 52 53 54 55 56 57 58 59 60 61 62 63

Guest
27th August 2010, 21:36
Windows returns different information on the system call that I use.

7ekno
28th August 2010, 06:11
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:

http://www.users.on.net/~tekno/AVC/KFP_artifact_frame3846.png

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:

http://www.users.on.net/~tekno/AVC/KFP_nonartifact_frame3846.png

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 (http://www.xbitlabs.com/articles/video/display/gf-210-gt220_9.html#sect0):
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
28th August 2010, 11:09
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
28th August 2010, 13:12
@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?

7ekno
28th August 2010, 13:41
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
28th August 2010, 13:42
@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
28th August 2010, 14:42
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
28th August 2010, 14:58
If it never fails manually then it proves something.

OK well see xD

Trying manually ...


Chris

MOS-Marauder
28th August 2010, 15:10
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
28th August 2010, 17:33
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
28th August 2010, 17:45
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
28th August 2010, 17:59
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
28th August 2010, 18:04
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
28th August 2010, 18:33
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
28th August 2010, 18:52
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
28th August 2010, 18:54
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
28th August 2010, 22:53
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
29th August 2010, 02:13
Chris, I need a stream to duplicate it.

krosswindz
29th August 2010, 06:15
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
29th August 2010, 10:24
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

Guest
29th August 2010, 12:40
@MOS

Cut it using the TS trim function.

@krosswindz

Adding handling for that is on my to-do list. For now, use DGIndex.

PzSniper
30th August 2010, 02:15
Is there any possibility to work with a Sky HD stream like this?

http://img594.imageshack.us/img594/5782/capturexq.jpg

Or we can't coz says MPEG/AVC Video [Scrambled]

LigH
30th August 2010, 09:21
No matter if a descrambler was legal or not - it would surely not be the purpose of DGDecNV.

But theoretically, CUDA might have some brute-force power to do it...

Groucho2004
30th August 2010, 13:38
I wonder how relevant the scores from this (http://www.xbitlabs.com/articles/video/display/htpc-graphics-cards.html) review are for the plain decoding duties that DGDecNV provides? Could the deinterlacing and/or resizing quality be different depending on the card (i.e. 210/220/240)?

Sharktooth
1st September 2010, 16:15
maybe depending on the driver optimizations for each card...

PzSniper
3rd September 2010, 01:23
No matter if a descrambler was legal or not - it would surely not be the purpose of DGDecNV.

But theoretically, CUDA might have some brute-force power to do it...

Ah ok, but i've just asked hints on how to move to get this file readable, didn't said DGDecNV is good for that, so, can you tell me if there's any hope to open this .trp file aired from Sky HD and save hrs of googling? :thanks:

Guest
3rd September 2010, 03:06
It's off topic for this thread.

gahz
3rd September 2010, 08:23
Can anyone please help me out with a problem I seem to be having using megui and dgnv. I can't seem to get megui to have more than 1 item in the que or else it will crash. Maybe I'm doing something wrong but have no clue as to what I'm doing wrong. I have this same problem on 3 diff computers all with diff hardware. Anyway here are the steps I have taken.

1. reinstall win7 x64 (I have all 3 diff types of win 7, one type for each computer)
2. install windows patches, most current drivers, etc.
3. install haali and ffdshow tryouts beta + 64bit version also (though i have tried it without the 64 bit ffdshow and it made no diff)
4. install and patch megui.
5. load 1088 source into dgindexnv (auto crop to 1080), hit f4. dgindexnv spits out a script from the simple template I use:

LoadPlugin("c:\dgdecnv\DGDecodeNV.dll")
dgsource("__vid__")

ok here's where the magic begins. There are a couple scenario's here:
1. if i uncheck "open preview after avisynth script selection", and then try to load my script megui will immidiatly crash

but if i put a check on that option so it does open a preview window megui will not crash and I will be able to hit enque without a hitch (99% of the time). The problem lies in if I want more than 1 job in the que. When hitting enque on the 2nd job i want to put in the batch megui will crash.

The reason why I'm asking on this post instead of the megui one (though I have pm'd zathor but I think he's busy lately as I have not gotten a reply) is because if I use megui's script creator I don't have these crash problems. I can load as many in the batch as I want that way. Again, I don't know what the problem is and I'm not saying that it's dgtools that is causing my frustrations. I just want some help from you bigger brain types :)

gahz
5th September 2010, 07:30
*update on my problem

I tore one of my computer's down again to try and solve my problem. This time I didnt install haali or ffdshow. Seems to have partially fixed my problem. It still crashes when I have the open preview window checked off but if I have it on all my problems are gone. Now to figure out why I'm having issues after I install ffdshow and/or haali.

Groucho2004
5th September 2010, 09:36
@gahz

DGDecodeNV has a peculiar behaviour when it comes to its interaction with AVISynth.
Reading the video properties either through VFW or the native AVISynth API without reading at least one frame can lead to a crash.

I don't know megui but my guess is that megui just reads the properties of a video without reading a single frame.
When you use the preview feature it obviously has to read at least one frame in which case it wouldn't crash.

I'm guessing here but this could certainly be the problem.

Zathor
5th September 2010, 14:22
*update on my problem

I tore one of my computer's down again to try and solve my problem. This time I didnt install haali or ffdshow. Seems to have partially fixed my problem. It still crashes when I have the open preview window checked off but if I have it on all my problems are gone. Now to figure out why I'm having issues after I install ffdshow and/or haali.

I cannot reproduce the problem but I have added as suggested above the reading of one frame.

Please try this build:
http://www.mediafire.com/?ncguc91wl326bxw
and report back if the problem is still there.

Guest
5th September 2010, 15:01
Thank you, Zathor, for your willingness to address possible incompatibilities. I'll test this build also, though I too have not had any problems.

May I ask if you tracked the process that Hank and I went through to get HCEnc working well with DGNV?

Specifically, are you following the rules for interacting with Avisynth as they have emerged as a result of that process? You can find technical details here:

http://forum.doom9.org/showthread.php?p=1422187#post1422187

and in the HCEnc thread.

kemuri-_9
5th September 2010, 15:27
@gahz

DGDecodeNV has a peculiar behaviour when it comes to it's interaction with AVISynth.
Reading the video properties either through VFW or the native AVISynth API without reading at least one frame can lead to a crash.

I'm guessing here but this could certainly be the problem.

This is highly unprobable: x264 reads the video properties before decoding any frames.
(I'm talking about x264's own avs demuxer, not any of those misc vfw4x264 or avs4x264 utilities that MeGUI plagues itself with)
by your logic here, x264 would ALWAYS crash when being used directly with DGNV.
as I have not seen any reports of behavior along these terms all this time, the problem likely lies within MeGUI.

Groucho2004
5th September 2010, 15:34
the problem likely lies within MeGUI.

I thought it was clear that I was referring to megui (I didn't even mention x264).

I never had any problems feeding scripts that use DGDecodeNV to x264.

Sharktooth
5th September 2010, 15:35
@kemuri-_9: i cant reproduce as well. however your logic is faulty. the problem has appened before with other softwares too. so megui is not directly responsible. however, if it's a problem in the avisynth interaction, as i said i cant reproduce so i cant fix it. but still other plugins work as expected... so, before saying it's a megui problem, check your logic, coz is COMPLETELY faulty.

Zathor
5th September 2010, 15:52
@neuron2:
I have tried to follow that discussion and had read the thread linked by Groucho2004. In my opinion the AviSynthWrapper.dll seems to be ok, but frankly speaking this part is out of my scope. I have only limited C++ knowledge and this is not enough to mess with the code. If you or someone else is willingly to have a look at the code it would be highly appreciated. This should be the required file:
http://megui.svn.sourceforge.net/viewvc/megui/AvisynthWrapper/trunk/AvisynthWrapper.cpp?revision=1415&view=markup

@kemuri /Groucho2004 (and a little bit OT here):
I know that MeGUI has still several problems. Over the past months I have been able to fix some of them without introducing hopefully too much new problems. I have never said that I am a professional developer or that I claim to know everything. I am doing things within my scope in order to help the community and I won’t mess with things I do not understand (ok, in some cases I thought I understand it...). So if you have any advice (like get rid of avs4x264 for 64bit and do it with other methods) please do not hesitate. Without addressing problems it is impossible to evolve. In this specific case only addressing the problem is sadly not sufficient because – as said above – it is out of my scope.

Guest
5th September 2010, 17:40
Thanks, Zathor, I'll have a look. That's exactly what Hank did too, BTW, i.e., referred his code to me for review and I modified it for him.

Your candid attitude about development and your capabilities is refreshing. Keep on, it's the only way to reach the level you'd like to attain. Surely, you will find only support and appreciation for what you (and Sharktooth) are doing.

Sharktooth
5th September 2010, 19:18
probably the issue is OS/settings/drivers/something dependant. otherwise it would be inexplicable. however it's too easy to point the finger and judge... until we dont find what's causing it i suggest everyone to think twice before speaking. this is the second time i have to speak about ppl saying "it's megui's fault"... megui is still open source and some of the ppl yelling against megui are even programmers... enough said.
there wont be a third time...

Rodger
7th September 2010, 12:16
Is there any possibility to work with a Sky HD stream like this?

http://img594.imageshack.us/img594/5782/capturexq.jpg

Or we can't coz says MPEG/AVC Video [Scrambled]

IŽd like to pick that up. I just found out, that there must have been changes in the Audio-Stream recognition.

In one and the same file build 2024 doesnt find anything and an older build (2009) easily finds two dolby digital audio streams.

So IŽd say changes made are not really good.....at least when it comes to this theme.
See the screenshot:
http://www.bilder-space.de/show_img.php?img=7ec92a-1283858056.jpg&size=thumb (http://www.bilder-space.de/bilder/7ec92a-1283858056.jpg)

Any idea how to fix this in newer builds?

btw. source is a LEGAL RECORDING via Vantage HD7100s from Sky television GERMANY. (HD channel obviously)

Guest
7th September 2010, 14:48
Any idea how to fix this in newer builds? Sure. You give me a link to a stream that does that and then I fix it. Thank you for bringing it to my attention.

crasus
7th September 2010, 23:37
Dear neuron2,

It so happens that sometimes after demuxing the .h264 from a Bluray with eac3to (latest) I see a certain number of frames in the log (say 128540) and after indexing with dgdecnv 2024 (and other versions in the past) I see another number in its log (say 128526).

May I ask what's the source of this and I am doing something wrong somewhere? I do apologize if it's already been answered or asked.

All the very best and warmest for your excellent software (which saved me time ... more than once!)

Guest
7th September 2010, 23:42
DGNV will discard frames at the end that cannot be displayed due to missing references. It's normally caused by a bad edit. If it occurs for streams that have not been cut, then please specify the BluRay disk and I will buy it to investigate.

And thanks for the kind words! I am happy that you find my work useful.

Rodger
8th September 2010, 01:44
Sure. You give me a link to a stream that does that and then I fix it. Thank you for bringing it to my attention.

Thank you! IŽve just uploaded a "sample Directory" with all files created when recording.

Here is the link: http://www.megaupload.com/?d=7TH4QVZZ

crasus
8th September 2010, 12:25
DGNV will discard frames at the end that cannot be displayed due to missing references. It's normally caused by a bad edit. If it occurs for streams that have not been cut, then please specify the BluRay disk and I will buy it to investigate.

And thanks for the kind words! I am happy that you find my work useful.

I very much appreciate your quick reply.

It always occured from streams demuxed straight from the Bluray.

In this case, here's the BluRay we're talking about : http://www.amazon.fr/aventures-rabbi-jacob-Blu-ray/dp/B001GMY9NK/ref=sr_1_2?ie=UTF8&s=dvd&qid=1283945127&sr=8-2

Guest
8th September 2010, 15:02
@crasus

OK, I will investigate.

@Rodger

See the next post.

Guest
8th September 2010, 15:03
* Fixed a GUI bug that could cause the first frame to be displayed wrong just once on
initial open in DGIndexNV.

* Fixed missing detection of audio streams with stream_id 0xbd when PAT/PMT is not present.

* Fixed the broken CLI option -od (save project and demux video).

http://neuron2.net/dgdecnv/dgdecnv.html

Rodger
8th September 2010, 19:42
WOW! Now that was a quick bugfixing :D

THANK YOU for that!

gahz
9th September 2010, 14:25
I cannot reproduce the problem but I have added as suggested above the reading of one frame.

Please try this build:
http://www.mediafire.com/?ncguc91wl326bxw
and report back if the problem is still there.

can you believe the main cause of my problem was that i had not set ffdshow to handle raw files?

i was getting zero crashes without ffdshow installed and i suddenly got them back right as soon as i installed ffdshow. i realized i had forgotten to enable raw file handling, ticked it and now the major part of my problem is gone.

every now and then i'll get a very odd hickup. after say i put in 8 jobs in the que i'll go to add another and megui will fade out and crash. i just restart megui and everything is fine again. regardless i am very happy to report that it was my mess up an no one elses that caused this big pain in my...

though what i dont understand is how ffdshow 32 bit broke megui 64 bit? can someone enlighten me on this?

Fotis_Greece
9th September 2010, 15:48
Hello, yesterday I sold my GTX 260 and bought a new GTX 470 card. Installed the latest Nvidia drivers in my Windows 7 64bit system and all ok. It works perfect with Premiere CS5.
Today I tried to use DG NV2025 and I get an error about "GPU decoder failed to create video decoder [1]" . Is there a problem with the GTX 470 card? It is not yet supported by your application?
I uploaded a small clip for you to try also (in case there is something wrong with the video file but I don't think so as I managed to do my job using VideoRedo)
http://rapidshare.com/files/418064383/Test.mpg.html

Edit: I tried now with both the x64 and x86 version of DG NV with various video files that I know previously worked and all of them give me the same error. It's definatelly something to do with the GTX 470

Guest
9th September 2010, 16:14
Please try Nvidia driver version 258.96. Everything works fine on my 460.

Also, always tell your revision when making a report. Thank you.