DG NV tools - Page 136

kypec · 2nd December 2010, 10:41

Build 2037
----------

* Fixed use of an uninitialized variable that could cause crashes
and/or bad hinting for MPEG2 and VC1 files.

* Added a string to the first line of the DGI file that identifies the version of DGIndexNV
used to generate the index.

* Fixed counting of leading B frames for AVC streams.

* Improved the accuracy and robustness of the audio delay calculation.

* Revised DGDecodeNV so that serious CUDA errors do not cause the parent application to crash.
These errors now simply cause return of invalid video. Also, CUDA error popups now
time out after 5 seconds so that unattended applications do not hang.

* Added cropping parameters to DGSource(). This gives you the flexibility to define GPU cropping
either in DGIndexNV or in the DGSource() parameters.

* Added my current to-do list to the distribution (also available online).

* Backed out the mod 2 cropping granularity change because the Nvidia driver does not
honor it.

SubJunk · 5th December 2010, 11:00

Starting with build 2037 several of my files aren't indexing. It was OK with 2036.
When the file doesn't work, what happens is:
I load it via DGIndexNV, I can use the GDIndexNV video player to skip to different positions, but when I try to save the file it gets stuck partway through.
One I'm looking at now won't go past frame 120, and remuxing it using MKVToolnix doesn't fix it either.
The files are fine, I am able to load and convert them using DSSource2 with no problem.

LigH · 5th December 2010, 13:36

Please register in Donald Graft's forum and post your bug report there. He won't look in here much more...

5th December 2010, 22:30

Quote:

Originally Posted by SubJunk

One I'm looking at now won't go past frame 120,

Same for me, I get the first 2.5 seconds and that is it ....

7ek

Guest · 6th December 2010, 15:36

Quote:

Originally Posted by 7ekno

Same for me, I get the first 2.5 seconds and that is it ....

Is that with MKV files only? If so, I've slipstreamed the fix. Re-download 2037 and test again.

If it is happening with files other than MKV, please post a link to a source file that fails?

7th December 2010, 08:39

Yeah, I just realised it was MKV only (the GUI tool was dumping to MKV from M2TS!) ...

Thanks, will test 2037 now

*EDIT* Yep, new build works fine now on MKVs, great job Don!

7ek

Hagbard23 · 7th December 2010, 16:59

Same for me - had the bug of crashed mkv-index-jobs - now FIXED with the newest 2037 Build.

Thanks Donald...keep up the good work...

rica · 10th December 2010, 02:31

neuron,

happy to see you here again.

Let's go on.

I'm trying to make 3D avisynth scripts but i need your help, will you?

hydra3333 · 10th December 2010, 03:51

Hey, great to see you Neuron2 ! Cheers !

palwan · 30th December 2010, 22:42

Hi!
I have replaced megui's dgindexnv with build 2037, after I made my dgi file and wanted to open it with meui's script creator I get

, than I get dgmultiDecodenv from megui's update server and put dgindexnv folder, but I get missmatch error

What would be the solution for my problem?

Thanks in advance.

Zathor · 30th December 2010, 23:02

I assume you are using MeGUI 0.3.5.0? Please switch to the development build if you want to use the recent DGIndexNV. You can change the update server in the MeGUI settings.

Dogway · 1st January 2011, 09:24

I normally use ffvideo for loading sources but I just felt I needed something faster if possible, and an elegant way to load AVC streams at the same time, that's when I discover DGNV.

My question is about performance benefits, is there any kind of comparison with different frame accurate AVC decoders?
I know that since its GPU based its gonna defintely be faster, but with a near future $15 in mind I would like to know how faster, in say simple decoder comparison, and another one comparing GPU decoding,cropping,resizing against usual ways in avisynth. Now I just thought whether there is any kind of trial version?

cweb · 1st January 2011, 09:33

Quote:

Originally Posted by Dogway

I normally use ffvideo for loading sources but I just felt I needed something faster if possible, and an elegant way to load AVC streams at the same time, that's when I discover DGNV.

My question is about performance benefits, is there any kind of comparison with different frame accurate AVC decoders?
I know that since its GPU based its gonna defintely be faster, but with a near future $15 in mind I would like to know how faster, in say simple decoder comparison, and another one comparing GPU decoding,cropping,resizing against usual ways in avisynth. Now I just thought whether there is any kind of trial version?

There's no trial as far as I know.. Just do the right thing and give your donation! It will be worth it even in terms of future development.

RiCON · 1st January 2011, 16:12

Quote:

Originally Posted by Dogway

My question is about performance benefits, is there any kind of comparison with different frame accurate AVC decoders?

According to some quick tests I made a few weeks ago, it probably depends on what board you have. With my 9500GT, ffms (using ffmpeg-mt, obv) seemed faster than both coreavc with cuda and dgnv. Might try again one day.

Dogway · 1st January 2011, 23:24

Its 9600MGT on laptop, Quadro 4600 on x64 Desktop they both should work if Im not wrong.

TheRyuu · 2nd January 2011, 02:36

cpu decoding will probably be faster than gpu decoding if it's threaded (ffmpeg-mt, diavc) unless your cpu is absolutely terrible.

Didée · 2nd January 2011, 05:56

Quote:

Originally Posted by Dogway

I know that since its GPU based its gonna defintely be faster,

Interesting things you know.

- If you're encoding to x264 with some "very fast" settings, chances are you'll go faster with CPU decoding. GPUs basically decode "as fast as needed", not "as fast as possible". (It's not even the GPU, but a separate ASIC that does the decoding.)

- If your encoding with some "very slow" settings (x264 and/or Avisynth), then ... it basically doesn't matter. There's the theoretical advantage "CPU cycles not used for DEcoding can be used for ENcoding and/or filtering", but ... if the whole chain is very slow (single-digit FPS speed), then the fraction of CPU used for decoding is very low. In a low-fps encoding scenario, the CPU usage needed for decoding can easily be as low as 1-2%. Now imagine you fully unleash that 1-2% for filtering/encoding. W00t, what a speed boost!!

Despite of that, I definetly like DGDecNV for versatility, ease-of-use, reliability, convenience, ... I like to use it for a bunch of reasons, only "speed advantage" is not a member of the bunch.

Dogway · 2nd January 2011, 07:27

I see, well most .avs I process are <=1fps so I guess no benefit there, I thought it was going to be quite a speed booster. Actually in ffmpegsource2 indexing is conveniently automatic, so I just asked out of curiosity if its worth the cash related to speed gain, since except (or not) that, Im happy with the rest, talking about .h264. Thanks for the insight Didée.

hajj_3 · 3rd January 2011, 13:36

I believe DG NV can now add ATI support now that Ati Stream SDK 2.3 is out? http://developer.amd.com/gpu/atistre...s/default.aspx

Adub · 8th January 2011, 20:27

If that is true, then he may have to change the name. DGGPUTools anyone?

2nd December 2010, 10:41	#2701 \| Link
kypec User of free A/V tools Join Date: Jul 2006 Location: SK Posts: 826	DGDecNV 2037 [Dec 02, 2010] Build 2037 ---------- * Fixed use of an uninitialized variable that could cause crashes and/or bad hinting for MPEG2 and VC1 files. * Added a string to the first line of the DGI file that identifies the version of DGIndexNV used to generate the index. * Fixed counting of leading B frames for AVC streams. * Improved the accuracy and robustness of the audio delay calculation. * Revised DGDecodeNV so that serious CUDA errors do not cause the parent application to crash. These errors now simply cause return of invalid video. Also, CUDA error popups now time out after 5 seconds so that unattended applications do not hang. * Added cropping parameters to DGSource(). This gives you the flexibility to define GPU cropping either in DGIndexNV or in the DGSource() parameters. * Added my current to-do list to the distribution (also available online). * Backed out the mod 2 cropping granularity change because the Nvidia driver does not honor it.

5th December 2010, 13:36	#2703 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 7,439	Please register in Donald Graft's forum and post your bug report there. He won't look in here much more... __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid

7th December 2010, 08:39	#2706 \| Link
7ekno Guest Posts: n/a	Yeah, I just realised it was MKV only (the GUI tool was dumping to MKV from M2TS!) ... Thanks, will test 2037 now EDIT Yep, new build works fine now on MKVs, great job Don! 7ek Last edited by 7ekno; 7th December 2010 at 10:51.

10th December 2010, 02:31	#2708 \| Link
rica Registered User Join Date: Mar 2008 Posts: 2,021	neuron, happy to see you here again. Let's go on. I'm trying to make 3D avisynth scripts but i need your help, will you? Last edited by rica; 10th December 2010 at 02:42.

30th December 2010, 22:42	#2710 \| Link
palwan Registered User Join Date: Nov 2010 Posts: 9	Hi! I have replaced megui's dgindexnv with build 2037, after I made my dgi file and wanted to open it with meui's script creator I get , than I get dgmultiDecodenv from megui's update server and put dgindexnv folder, but I get missmatch error What would be the solution for my problem? Thanks in advance. Last edited by palwan; 30th December 2010 at 22:58.

5th December 2010, 11:00	#2702 \| Link
SubJunk Registered User Join Date: Jun 2010 Posts: 442	Starting with build 2037 several of my files aren't indexing. It was OK with 2036. When the file doesn't work, what happens is: I load it via DGIndexNV, I can use the GDIndexNV video player to skip to different positions, but when I try to save the file it gets stuck partway through. One I'm looking at now won't go past frame 120, and remuxing it using MKVToolnix doesn't fix it either. The files are fine, I am able to load and convert them using DSSource2 with no problem.

7th December 2010, 16:59	#2707 \| Link
Hagbard23 23sKiDdOo! Join Date: May 2010 Location: Germany Posts: 182	Same for me - had the bug of crashed mkv-index-jobs - now FIXED with the newest 2037 Build. Thanks Donald...keep up the good work...

10th December 2010, 03:51	#2709 \| Link
hydra3333 Registered User Join Date: Oct 2009 Location: crow-land Posts: 544	Hey, great to see you Neuron2 ! Cheers !

30th December 2010, 23:02	#2711 \| Link
Zathor Registered User Join Date: Nov 2009 Posts: 2,405	I assume you are using MeGUI 0.3.5.0? Please switch to the development build if you want to use the recent DGIndexNV. You can change the update server in the MeGUI settings.

1st January 2011, 09:24	#2712 \| Link
Dogway Registered User Join Date: Nov 2009 Posts: 2,375	I normally use ffvideo for loading sources but I just felt I needed something faster if possible, and an elegant way to load AVC streams at the same time, that's when I discover DGNV. My question is about performance benefits, is there any kind of comparison with different frame accurate AVC decoders? I know that since its GPU based its gonna defintely be faster, but with a near future $15 in mind I would like to know how faster, in say simple decoder comparison, and another one comparing GPU decoding,cropping,resizing against usual ways in avisynth. Now I just thought whether there is any kind of trial version? __________________ i7-4790K@Stock::GTX 1070] AviSynth+ filters and mods on GitHub + Discussion thread

1st January 2011, 23:24	#2715 \| Link
Dogway Registered User Join Date: Nov 2009 Posts: 2,375	Its 9600MGT on laptop, Quadro 4600 on x64 Desktop they both should work if Im not wrong. __________________ i7-4790K@Stock::GTX 1070] AviSynth+ filters and mods on GitHub + Discussion thread

2nd January 2011, 02:36	#2716 \| Link
TheRyuu warpsharpened Join Date: Feb 2007 Posts: 787	cpu decoding will probably be faster than gpu decoding if it's threaded (ffmpeg-mt, diavc) unless your cpu is absolutely terrible.

2nd January 2011, 07:27	#2718 \| Link
Dogway Registered User Join Date: Nov 2009 Posts: 2,375	I see, well most .avs I process are <=1fps so I guess no benefit there, I thought it was going to be quite a speed booster. Actually in ffmpegsource2 indexing is conveniently automatic, so I just asked out of curiosity if its worth the cash related to speed gain, since except (or not) that, Im happy with the rest, talking about .h264. Thanks for the insight Didée. __________________ i7-4790K@Stock::GTX 1070] AviSynth+ filters and mods on GitHub + Discussion thread

3rd January 2011, 13:36	#2719 \| Link
hajj_3 Registered User Join Date: Mar 2004 Posts: 1,232	I believe DG NV can now add ATI support now that Ati Stream SDK 2.3 is out? http://developer.amd.com/gpu/atistre...s/default.aspx

8th January 2011, 20:27	#2720 \| Link
Adub Fighting spam with a fish Join Date: Sep 2005 Posts: 2,754	If that is true, then he may have to change the name. DGGPUTools anyone? __________________ Flawless Media - Digitizing and Restoration Zsmooth - Cross-platform smoothing for Vapoursynth Zscene - Scene change detection for Vapoursynth Old Site:Adubvideo

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode