DG NV tools [Archive] - Page 46

RedDwarf1

27th July 2010, 04:57

Hosed? How so?

It's interesting that you should post this, because I'm getting random BSOD errors when using DGSource() for H.264 content. I have been wondering what's the cause of the BSODs...

Using a Palit GTX 460 Sonic here...

The newer drivers have been reported to cause BSOD's for some people. I tried them myself and experienced a BSOD which mentioned a nVidia file as being the cause so I uninstalled them and went back to 197.45 and since then I haven't had a problem.

I have a GTX 460, and I can do the usual stuff just fine. Creating an index file, encoding using x264 using DGSource with Deinterlace=2...

That said, with all the hype nVidia has piled on Fermi, is there anything special that Fermi cards can do that others can't?

I don't think they can do anything different to the later updated Cores with regard to their decoding capabilities. They do bring improved audio support which some people might find useful.

As to speed, there might be some improvement over some older Cores but without tests is difficult to say how much.

Hit man is on the way. :)

I think we should hold off further reports and do what RedDwarf1 suggested. I will get a sample clip prepared with instructions for playing it in DGIndexNV and then we will report the data above together with our FPS. Stand by...

Any news on this? I have a BBC HD video preview which is broadcast after regular programmes finish which could be used to test lower bitrate and different resolution HD video. It's 1440x1088i 25 fps @ about 9 to 10 Mbit. The recording I made is 6GB so plenty of choice of video to use.

So maybe having a piece from this low bitrate HD video and a high bitrate Blu Ray source to test how big a difference different GPU memory systems make. Questions such as does the memory speed make a difference? How big a difference does the memory bus width make? How much difference does resolution and frame rate make? How big a part does video bitrate play? These might be made clearer.

Or using a Blu Ray source and someone re-encoding it to a lower bitrate(s) and possibly resolution and then using those to test.

What type of clips and lengths do the forum rules allow us to use?

It might be worth starting a new thread for solely testing NVTools and Video cards so it does not clutter up this thread.

Blue_MiSfit

27th July 2010, 06:11

I just ordered a GTX 460, so I'll be happy to report on any issues as soon as it arrives :)

Derek

lych_necross

27th July 2010, 07:15

Hey, don't forget rule 11, all posts must have useful content. Mine didn't but I can't seem to strike myself. So you get to slide too.

I wish lych_necross would come back. I don't want to have to buy a Fermi card. :p
Sorry about the delay (I was working)... It seems to work fine. No error messages. I'm saving a new project right now. If it errors out, I'll update this post.

EDIT: everything went fine with your patch. I can test the 64bit version when you release it.

lych_necross

27th July 2010, 07:22

Ah OK. Guess that means I won't be going to 64 bit anytime soon, since I too use AVISynth.
The speed increase from avisynth 32 to 64 isn't really that great in my experience.

JoeH

27th July 2010, 07:50

It's hard to find a single build of any video driver, NVidia or ATI, that is stable for everyone and for all needs. That's why it's a good idea to include a minimum driver requirement, as Neuron2 has done, and then leave the choice of the exact build used to the needs of each user.

tormento

27th July 2010, 08:12

Do you seriously think I am not keeping myself informed on CUDA developments? :devil:
/me moans.. :p

*** neuron2 sets +b tormento*!*

Ok, not to be kicked in the head too, the multiple license file now works ok. Thanks ;)

P.S: Now that video rendering is GPU made too, is there any specific reason to keep the "original video size" menu voice and not make the window freely resizeable?

Groucho2004

27th July 2010, 08:12

It's hard to find a single build of any video driver, NVidia or ATI, that is stable for everyone and for all needs.

Not to mention that there are 32 and 64 bit versions, Windows 7, WinXP, etc.

MrVideo

27th July 2010, 08:51

The speed increase from avisynth 32 to 64 isn't really that great in my experience.

OK, thanks for the update.

Guest

27th July 2010, 13:06

everything went fine with your patch. I can test the 64bit version when you release it. Great. Thanks for your test results. I will prepare the 64-bit binary now for your further testing.

Guest

27th July 2010, 13:11

Any news on this? No, I've been too busy with development.

What type of clips and lengths do the forum rules allow us to use? We should use a fairly large public-domain sample, such as ElephantsDream.mkv.

It might be worth starting a new thread for solely testing NVTools and Video cards so it does not clutter up this thread. Yes, indeed.

Guest

27th July 2010, 13:14

Now that video rendering is GPU made too, is there any specific reason to keep the "original video size" menu voice and not make the window freely resizeable? Yes, because coordinating it with the cropping would be a nightmare. I have no interest in making complex code that really isn't necessary.

MrScientist

27th July 2010, 13:22

You're missing a proper trouble report. All system details, DG version number, video driver version number, exactly what happens when you open a file.

Is this a licensing issue, i.e., does the file show video? If you have rebuilt your system, you'll have to regenerate your license, because your machine ID will have changed. Did you do that?

If video shows then exactly what happens when you do Save Project?

licensing issue, license regeneration fixed it.

with my rebuilds, i check for new versions of the programs i use. saw this was updated so used new version. didn't realize i had an issue with the license because with the older versions, there was an idiot box that told me if my license was bad, that seems to be absent with this version.

Guest

27th July 2010, 13:35

I'm fearless, so I have just slipstreamed the Fermi support for 32-bit and 64-bit into the 2022 distribution.

@MrScientist

I also slipstreamed a restoration of the "Invalid license" popup, but executed from a delayed thread to confuse the crackers a little. The convenience of licensed users should not be sacrificed.

That's the end of slipstreaming for 2022. ;)

lych_necross

27th July 2010, 14:15

Guest

27th July 2010, 14:28

Good news! Thank you for your testing, lych_necross.

You and Blue_MiSfit are appointed my official Fermi testers!

MrScientist

27th July 2010, 17:50

@MrScientist

I also slipstreamed a restoration of the "Invalid license" popup, but executed from a delayed thread to confuse the crackers a little. The convenience of licensed users should not be sacrificed

thanks, but i learned my lesson anyway.

i get very accustomed to things kinda like pavlov's dog and don't know what to do when things change!

tormento

27th July 2010, 23:11

Yes, because coordinating it with the cropping would be a nightmare. I have no interest in making complex code that really isn't necessary.
Ok, anything more than 1/2 and full size could be possible?

On 1280*1024 1/2 is too small and 1/1 is too big...

Guest

27th July 2010, 23:35

No!

It's an indexer, not a player. You don't need to resize the thing. I added the full sized display only to make it convenient to see combing. An intermediate size would defeat the purpose of that.

View the video via your script if you want full control of sizing.

It's not going to happen so don't bother continuing this debate.

Guest

28th July 2010, 05:50

The cursor behavior discussion was moved to a separate thread. Please follow up there.

http://forum.doom9.org/showthread.php?t=155888

laserfan

28th July 2010, 14:37

That's the end of slipstreaming for 2022.The updates & slipstreaming were making me sorta dizzy & gunshy so I waited to update to 2022 (all the way from 2018). Glad to see still that Everything Works w/my W7 x64 9600GT nvidia 196.21 running x32 Avisynth & DGIndexNV! Whew!

:thanks:

Guest

28th July 2010, 16:55

I'll second that. Whew!

I have found and fixed the problem with crashing at end of file with MKV streams (reported to me in email). I will release 2023 this evening, with that fix and the jittery cursor fix.

tormento

28th July 2010, 21:04

Neuron, I have tried to feed DGNVIndex_x64 with the main M2TS of "From Paris with Love". It gives the following errors (many, random) and then crashes.

http://img30.imageshack.us/img30/9741/fromparis01.png

http://img299.imageshack.us/img299/8089/fromparis02.png

http://img203.imageshack.us/img203/241/fromparis03.png

The BD was ripped with AnyDVDHD and DVDFab, latest versions, same result.

Here I don't have sufficient bandwidth to upload a split, wait until tomorrow morning (CET+1)

UPDATE:

Mmm... I suppose to have some strange bigger problem. Tried to open a VOB and DGIndexNV tells me there is a problem with GPU decoder.

The strangest thing is that I used the same configuration yesterday and everything worked fine. No idea.

Neuron2: any hint on how to debug what has gone wrong on my home pc? I installed nothing since yesterday and suddenly DGNV went south...

UPDATE2:

It was a license issue... Don't know why the older one wasn't accepted. Regenerated it and now everything works ok.

Guest

28th July 2010, 23:36

* Fixed crashing at end of file for some MKV streams.

* Optimized CUDA NV12->RGB24 kernel to gain a few fps.

* Made the seek bar cursor less jittery on dragging.

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

Guest

28th July 2010, 23:38

It was a license issue... Don't know why the older one wasn't accepted. Regenerated it and now everything works ok. Strange. You shouldn't have even been able to load your source without a valid license.

tormento

29th July 2010, 00:07

Strange. You shouldn't have even been able to load your source without a valid license.
The source was not loaded as DGIndexNV did output some strange errors, perhaps protection related, dunno.

Believe me, a new license and now it works. Don't know why but it has changed from 16ba* to 4a61*. The code in the about dialog is the same.

Blue_MiSfit

29th July 2010, 09:06

I Got my GTX 460 today, and decided to take a break from Starcraft 2 and Bad Company 2 for a bit to do some testing :)

I've got DGDecNV 2023 running on Windows 7 x64 with the latest nVidia drivers. Licensing went without a hitch, and I'm currently indexing my MKV remux of the Avatar BluRay at about 62MB per second, while using about half a core on my Q6600 CPU. Not bad, especially considering the 1.5TB drive is almost full (and can do maybe twice that speed when empty). Granted, this has nothing to do with my GPU, but it looks like the cache tweaks neuron2 made a few revisions back certainly didn't BREAK anything :)

... ok now indexing is done, and I'm decoding this high bitrate 1080p24 source at 60fps using less than half a core. Nice!!

Pure software decode via ffmpeg-mt -> x264 (ultrafast) nets me about 50 fps, and gobbles up all 4 cores.

Swapping out ffmpeg-mt for DGDecNV delivers about 57fps, but only uses 2 cores! VERY nice!

Dropping down to more sane x264 settings (--preset faster --tune film) I get the following speeds:
ffmpeg-mt: 18.36 fps
DGDecNV: 21.09 fps

And then at the fast but usable --preset superfast --tune film
ffmpeg-mt: 36.04 fps
DGDecNV: 47.57 fps

Great numbers, especially given the stability of DGDecNV. I'm happy :D

It seems the sweet spot is for high speed transcoding, where a larger portion of time is spent on decode. This makes perfect sense, and the GTX 460's decoder seems to be pretty damned quick!

Looking on wikipedia, I see that the GTX 460 has the VP4 decoder, which is capable of MPEG-4 (A)SP decoding. Any potential to bring this to DGDecNV? I have a lot of my older DVDs ripped using Xvid from a few years back, and haven't bothered to re-rip them using x264... Having ultra fast transcode capabilities for a quick toss on the cell phone seems like a perfect fit. Thoughts?

Derek

Guest

29th July 2010, 13:25

Looking on wikipedia, I see that the GTX 460 has the VP4 decoder, which is capable of MPEG-4 (A)SP decoding. Any potential to bring this to DGDecNV? You mean inside AVI? I'm not too excited about that. Anyway, I don't have a Fermi to do the development.

rack04

29th July 2010, 13:46

I get the following error when I open build 2023:

ERROR: cuModuleLoad C:\Program Files\DGDecNV\NV12ToRGB23_sm_20.cubin failed (300)

Hit Yes to continue notifying this specific error type; hit No to disable it.
Hit Cancel to suppress all further errors.

Guest

29th July 2010, 13:50

What is your card and Nvidia driver version? I have increased the minimum acceptable version.

Did 2022 work OK?

Guest

29th July 2010, 13:52

I Got my GTX 460 today Can you please benchmark it here:

http://forum.doom9.org/showthread.php?p=1421619#post1421619

rack04

29th July 2010, 13:54

What is your Nvidia driver version? I have increased the minimum acceptable version.

That is probably the problem. I am using 195.62. I'll have to see if there is a newer notebook driver for my Quadro NVS 135M.

Did 2022 work OK?

Yes.

Guest

29th July 2010, 13:56

If it worked on 2022, it should work on 2023. Please try using the .cubin files from 2022 and report results.

But, yes, you do need to get to a recommended driver version.

rack04

29th July 2010, 14:04

If it worked on 2022, it should work on 2023. Please try using the .cubin files from 2022 and report results.

But, yes, you do need to get to a recommended driver version.

I just downloaded 2022 and that version doesn't work either. It worked with the 2022 version that I had previously. I don't know if any of the slipstream fixes would have changed this function. Let me update the driver and see if the problem goes away.

kebulek

29th July 2010, 15:08

@neuron2

In GUI I'm able to crop "divided by 4" only. But if I do manual edit in .dgi file, let's say "CLIP 2 2 2 2", what will happen? I've tried that, looks like it working (no green stripes like with Avisynth). So my question is - is it really working with 2s or DG crops 4 pixels anyway? :)

Guest

29th July 2010, 15:20

The CLIP numbers will be honored.

Full cropping granularity is on my to-do list already.

kebulek

29th July 2010, 16:13

The CLIP numbers will be honored.
Full cropping granularity is on my to-do list already.
Nice - good to know.
:thanks:

RedDwarf1

29th July 2010, 18:33

You mean inside AVI? I'm not too excited about that. Anyway, I don't have a Fermi to do the development.

Personally I don't see much point in assisted Mpeg4 ASP decoding because it's so easy for a CPU to do and using a GPU will probably not yield any noticeable speed improvement.

But Mpeg4 ASP decoding is possible on none Fermi cards such as the later last generation cards like GT 210, 220 & 240. They all have the same VP engine.

rack04

29th July 2010, 19:11

If it worked on 2022, it should work on 2023. Please try using the .cubin files from 2022 and report results.

But, yes, you do need to get to a recommended driver version.

Updating to 258.96 solved the problem.

MrScientist

31st July 2010, 01:46

aside from the fact that the license needs to be changed every time i sneeze, megui has been crashing when i try to start encoding with the following...

Problem signature:

Problem Event Name: APPCRASH
Application Name: MeGUI.exe
Application Version: 0.3.5.0
Application Timestamp: 4c1e0f5b
Fault Module Name: nvcuda.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4c379076
Exception Code: c0000005
Exception Offset: 072cc254
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1033
Additional Information 1: 283e
Additional Information 2: 5fc388c7525dd00f04ece9603637a6d3
Additional Information 3: 998e
Additional Information 4: 820d2d63ef86d496544e88262ff9fe61

system information...
[Display]
Processor: AMD Phenom(tm) II X6 1055T Processor (3599 MHz)
Operating System: Windows Vista (TM) Business, 32-bit (Service Pack 2)
DirectX version: 11.0
GPU processor: GeForce GT 240
Driver version: 258.96
CUDA Cores: 96
Core clock: 550 MHz
Shader clock: 1340 MHz
Memory clock: 1700 MHz (3400 MHz data rate)
Memory interface: 128-bit
Total available graphics memory: 1851 MB
Dedicated video memory: 512 MB GDDR5
System video memory: 0 MB
Shared system memory: 1339 MB
Video BIOS version: 70.15.22.00.03
IRQ: 18
Bus: PCI Express x16 Gen2

[Components]

nvCplUI.exe 3.3.532.01 NVIDIA Control Panel
nvWSS.dll 6.14.12.5896 NVIDIA Workstation Server
nvViTvS.dll 6.14.12.5896 NVIDIA Video Server
NVSTVIEW.EXE 7.17.12.5896 NVIDIA GeForce 3D Vision
NVSTTEST.EXE 7.17.12.5896 NVIDIA 3D Vision Test Application
NVSTRES.DLL 7.17.12.5896 NVIDIA 3D Vision Module (0)
NVMCTRAY.DLL 8.17.12.5896 NVIDIA Media Center Library
nvDispS.dll 6.14.12.5896 NVIDIA Display Server
NVCPL.DLL 8.17.12.5896 NVIDIA Compatible Windows7 Display driver, Version 258.96
PhysX 09.10.0224 NVIDIA PhysX
NVCUDA.DLL 8.17.12.5896 NVIDIA CUDA 3.1.1 driver
nvGameS.dll 6.14.12.5896 NVIDIA 3D Settings Server

avs...
LoadPlugin("C:\DGVC\DGDecodeNV.dll")
DGMultiSource("C:\....\name.dgi")

megui works fine when software decoding. thanks.

Guest

31st July 2010, 02:02

aside from the fact that the license needs to be changed every time i sneeze That really motivates me to help you. Send me an email with your Paypal ID and I'll issue you a refund.

Groucho2004

31st July 2010, 09:22

Problem Event Name: APPCRASH
Application Name: MeGUI.exe

I have hunch what the problem might be. I wrote a few programs that interface with Avisynth via the IScriptEnvironment (which Megui is doing as well) and never had any problems until I started using DGDecodeNV. The issue was simply that some objects weren't released properly. After fixing my code I haven't had any problems.

So, if the Avisynth wrapper in megui is borked you're posting your problem in the wrong thread.

dream-lx

31st July 2010, 11:31

First of all many thanks for dgdecodenv. It really works like a charm. There is only one minor problem for hdv m2t files. Audio is detected wrong and a dialog box is displayed asking me how to proceed. In my case, I don't need audio at all, so I would find it nice to have a commandline parameter to disable audio completely and not ask anything about audio as I am calling dgdecodenv for many clips in a script.

Just a comment for people having problems running dgdecodenv: When running it for the first time, I received a message stating that NV12ToRGB24_sm_20.cubin could not be loaded. I saw that a really old version of the NVidia graphics driver was installed. Updating the graphics driver resolved the problem.

stax76

31st July 2010, 11:39

-a demuxes all audio, no -a should not demux any audio but I don't know if it will show a error message since I've never seen such a message. neuron2 usually asks for sample clips, if uploading is a problem please post at least MediaInfo.

Guest

31st July 2010, 12:10

After fixing my code I haven't had any problems.

So, if the Avisynth wrapper in megui is borked you're posting your problem in the wrong thread. Can you please be more specific about what the problem and fix was? This will help the MEGUI guys (and others) to fix this. It also may show me a way to work around it in my code.

Guest

31st July 2010, 12:13

Audio is detected wrong and a dialog box is displayed asking me how to proceed. Please post a link to a sample stream.

In my case, I don't need audio at all, so I would find it nice to have a commandline parameter to disable audio completely and not ask anything about audio as I am calling dgdecodenv for many clips in a script. Doesn't omitting the -a option do the trick? You can also set the AlwaysCancelOnAudioMismatch option in the INI file.

dream-lx

31st July 2010, 13:59

Without -a the dialog box still appears. AlwaysCancelOnAudioMismatch works perfectly.

A sample file can be found at

http://www.prnet.org/audiomismatch.m2t

It was recorded from an HDR-FX1E using a Sony HVR-MRC1 compact flash recorder.

Please tell me when you have downloaded the file as I will remove it afterwards.

Groucho2004

31st July 2010, 15:51

Can you please be more specific about what the problem and fix was? This will help the MEGUI guys (and others) to fix this. It also may show me a way to work around it in my code.

The problem was discussed here (starting on the second page):
http://forum.doom9.org/showthread.php?t=131674

Basically, after setting the pointers to zero instead of using "delete" the crashes, especially during debugging, went away.

Also, I only include avisynth.h and link statically with avisynth.lib.

Here is my sample code:

int _tmain(int argc, TCHAR* argv[], TCHAR* envp[])
{
if (argc < 2)
{
_tprintf(_T("\nUsage:\n\nAVSInfo [scriptfile.avs]\n\n"));
return -1;
}

if (!FileExists(argv[1]))
{
_tprintf(_T("\nFile doesn't exists:\n%s\n\n"), argv[1]);
return -1;
}

IScriptEnvironment *env = CreateScriptEnvironment(AVISYNTH_INTERFACE_VERSION);
AVSValue Arg0 = AVSValue((LPCTSTR)argv[1]);
AVSValue Args = AVSValue(&Arg0, 1);
AVSValue val;
PClip clip;
VideoInfo vidinfo;
PVideoFrame frame;

try
{
val = env->Invoke("Import", Args, 0);
clip= val.AsClip();
vidinfo = clip->GetVideoInfo();
}
catch(AvisynthError err)
{
_tprintf(_T("\n%s\n"), err);
return FALSE;
}

_tprintf(_T("\nFrames: %9u"), vidinfo.num_frames);
_tprintf(_T("\nFrame width: %9u"), vidinfo.width);
_tprintf(_T("\nFrame height: %9u"), vidinfo.height);
_tprintf(_T("\nFramerate: %.3f\n\n"), (double)vidinfo.fps_numerator / (double)vidinfo.fps_denominator);

int iFrames = (int)vidinfo.num_frames;

for (int i = 0; i < iFrames; i++)
{
frame = clip->GetFrame(i, env);
...
...
...
}

frame = 0;
clip = 0;
val = 0;
delete env;

return 0;
}

olapanekala

1st August 2010, 16:26

Hello,

i have three questions

1. is dgindexnv working with geforce 6600
2. is it working with mpeg4 transport streams
3. is it possible to do multiple cutting (remove ads etc)

Thank you

Also is there a way to have a demo licence to test?

Karyudo

1st August 2010, 16:55

Also is there a way to have a demo licence to test?

Considering that this thread is more than 100 pages long, and hardly a few hours goes by without the author (neuron2) showing up to respond to user requests and problems; and considering the license fee is less than the MSRP (retail price) of a single DVD, Blu-Ray, or a month's subscription to any cable, satellite, ISP, or Netflix plan; my recommendation to you is to take the nearly risk-free gamble that DGIndexNV won't do what you want right out of the box, show your support for the customer-centric way neuron2 develops his software, and JUST BUY A LICENSE ALREADY.

(If you read the entire thread -- which I agree is a large investment of time and attention -- you will quickly learn that there is NO WAY you will get a demo licence. Quite rightly, in my opinion.)