View Full Version : Questions About DGIndex etc.
Acid_Reign
17th July 2010, 10:56
Why is DGMPGDec still available but DGAVCDec no longer available? I would assume to either see DGAVCDec left up for archival purposes, or DGMPGDec also taken down due to being superseded by DGDec.
Is it "legal" to distribute or download the old DGAVCDec? If it is, is there a 64-bit binary of the old DGAVCDec available anywhere?
Are the new DGIndex tools no longer FOSS? If they're not, why are there ZIP files provided on neuron2 before buying a license, and why does MeGUI AutoUpdate download those binaries?
What are libmmd.dll and nvcuvid.dll, and should I have them already if I have the latest nVidia drivers installed or are they exclusive to the licensed version of DGIndex?
Guest
17th July 2010, 13:13
Why is DGMPGDec still available but DGAVCDec no longer available? I would assume to either see DGAVCDec left up for archival purposes, or DGMPGDec also taken down due to being superseded by DGDec. DGAVCDec is not available because I am not happy with its functionality (broken PAFF support) and there is no prospect for it being fixed. It will be replaced by a new freeware solution in any case (see below).
Is it "legal" to distribute or download the old DGAVCDec? If it is, is there a 64-bit binary of the old DGAVCDec available anywhere? I am the author and copyright holder and I do not now offer any license for its use, so it should not be distributed. There is no 64-bit version. I am working on a freeware solution that uses DiAVC.
Are the new DGIndex tools no longer FOSS? If they're not, why are there ZIP files provided on neuron2 before buying a license, and why does MeGUI AutoUpdate download those binaries? DGDecNV is not open source and requires a license. The download page clearly states that a license is required. Regarding what MEGUI does, downloading a tool is not the same as invoking it. I suppose it is done for the convenience of licensed users.
What are libmmd.dll and nvcuvid.dll, and should I have them already if I have the latest nVidia drivers installed or are they exclusive to the licensed version of DGIndex? You do not have to install any additional DLLs; everything you need is part of your normal Nvidia driver installation.
There are alternatives to the functionality provided by DGAVCDec, e.g., FFMpegSource, DSS(), etc., if you are unable/unwilling to license DGDecNV.
royia
17th July 2010, 14:13
May I take advantage of the thread and ask something.
What's the difference between DGIndex and DGDecNV?
I read all the thread about it, I see you talk about speed and stuff. Does it encode something? Cause as far as I can see, I've never seen something as fast as DGIndex.
What's DGDecNV advantage? Clearly I miss something (Basic).
Thanks.
Guest
17th July 2010, 14:25
Integrated and consistent support for AVC, VC1, and MPEG video.
GPU deinterlacing (PureVideo) and resizing.
MKV file support.
MPLS file support.
Transport stream trimming.
In some scenarios can free up CPU for encoding.
Better audio demuxing (e.g., all streams from a transport stream at once).
Nicer GUI.
royia
17th July 2010, 15:12
Integrated and consistent support for AVC, VC1, and MPEG video.
GPU deinterlacing (PureVideo) and resizing.
MKV file support.
MPLS file support.
Transport stream trimming.
In some scenarios can free up CPU for encoding.
Better audio demuxing (e.g., all streams from a transport stream at once).
Nicer GUI.
All those above the features of DGIndex I already know?
Could you explain:
1. Transport stream trimming / Better audio demuxing (e.g., all streams from a transport stream at once).
2. In some scenarios can free up CPU for encoding (You mean if I encode in parallel to Indexing, How can I do that?).
Does the interlacing is of better quality then what we see in DGIndex?
Does it create D2V files just like DGIndex (The workflow with Me GUI stays the same)?
Thanks.
Sharktooth
17th July 2010, 15:20
it uses hardware deinterlacing. it has a good quality and doesnt use CPU cycles coz it's done by the videocard.
About the CPU usage, the dgdecnv uses the videocard's decoder unit to decode the video streams so the decoding part is offloaded to the graphic card.
DGIndexNV creates .dgi files but Megui already supports dgdecnv (for now up to ver. 2020 - support for 2021 is being added as we speak) and the workflow is automated.
Guest
17th July 2010, 15:25
All those above the features of DGIndex I already know? Yes. There are some minor features of DGMPGDec that are not present (yet) in DGDecNV, for example, field order transition detection/correction.
Could you explain:
1. Transport stream trimming / Better audio demuxing (e.g., all streams from a transport stream at once). You can cut transport streams. You can demux all the audio streams at once from a transport stream, instead of only one at a time.
2. In some scenarios can free up CPU for encoding (You mean if I encode in parallel to Indexing, How can I do that?). In some scenarios, decoding on the GPU speeds up transcoding by freeing up CPU time for the encoder.
Does the [de]interlacing is of better quality then what we see in DGIndex? DGIndex does not do any deinterlacing. The field operations are the same (honor, force film, ignore).
Does it create D2V files just like DGIndex (The workflow with Me GUI stays the same)? The files are named DGI but the principle is the same. The workflow is the same.
royia
17th July 2010, 15:36
You can cut transport streams. You can demux all the audio streams at once from a transport stream, instead of only one at a time.
I guess I don't know what's a Transport Stream is.
Could you explain?
In some scenarios, decoding on the GPU speeds up transcoding by freeing up CPU time for the encoder.
Yet they must be done in serial, don't they (Decode -> Encode)?
DGIndex does not do any deinterlacing. The field operations are the same (honor, force film, ignore).
When I set in MeGUI: Deinterlace is sets "cpu=4" in the DGIndex plugin. From what I read this is Deinterlacing.
The files are named DGI files but the principle is the same. The workflow is the same.
I'm on the verge of getting nVidia card and your software.
Could you address it s Deinterlacing quality in comparison to other AviSynth Plug Ins?
Thank You for addressing my inquiries.
Sharktooth
17th July 2010, 15:43
DGIndex and DGDecode are different things.
MeGUI uses DGIndex to index the stream and DGDecode to decode the stream. DGDecode has deinterlacing while DGIndex just indexes ...
Also while the stream decoding is done by the GPU, CPU is not used for that task and decoding->encoding is done in parallel or to better explain encoding is done WHILE decoding...
Guest
17th July 2010, 15:43
I guess I don't know what's a Transport Stream is. Could you explain? No, but I can give you a rule 1 strike. :) Seriously, use Google to look it up.
Yet they must be done in serial, don't they (Decode -> Encode)? Of course not. The decoder decodes frames and feeds them to the encoder, which encodes them. The two processes run at the same time.
When I set in MeGUI: Deinterlace is sets "cpu=4" in the DGIndex plugin. From what I read this is Deinterlacing. Nope, that has nothing to do with deinterlacing.
Could you address it s Deinterlacing quality in comparison to other AviSynth Plug Ins? It's been discussed. Search for "PureVideo" both here and on Google.
royia
17th July 2010, 15:59
Of course not. The decoder decodes frames and feeds them to the encoder, which encodes them. The two processes run at the same time.
Really. I guess I should look how to do it in Me GUI.
At the moment I create d2v file and the let MeGUI Transcode it.
Nope, that has nothing to do with deinterlacing.
I could sware when I set in Me GUI Yadif to do Deinterlacing this is what I get:
"DGDecode_mpeg2source("VTS_01_1.d2v",cpu=4,info=3)".
It's been discussed. Search for "PureVideo" both here and on Google.
Couldn't find something which nails it. I'll keep looking.
Moreover, What's your personal opinion? If it's good enough for you, It's good enough for me.
You gave me some stuff to think about.
Thanks.
Sharktooth
17th July 2010, 16:05
Are you READING MY POSTS?!
I already said MeGUI supports DGIndexNV .....
once you have a license you should just select DGIndexNV in the file indexer...
royia
17th July 2010, 16:12
Are you READING MY POSTS?!
I already said MeGUI supports DGIndexNV .....
once you have a license you should just select DGIndexNV in the file indexer...
I did.
All I said is I guess I'm not using it properly in the way utilizing the integration.
I'll look into that (So far all I have is DG Index).
Could you address the "Deinterlacing" feature in MeGUI?
Thanks.
Groucho2004
17th July 2010, 16:29
I suppose reading guides and manuals is not cool any more. It's much more fun pestering other people about these basic things, isn't it?
If you have questions about GUIs, post in the appropriate forum. DGIndex and DGIndexNV come with exellent guides and references, read them.
Guest
17th July 2010, 16:36
Really. I guess I should look how to do it in Me GUI.
At the moment I create d2v file and the let MeGUI Transcode it. It happens automatically. Avisynth runs the decoder and MEGUI invokes the encoder. You don't have to do anything.
I could sware when I set in Me GUI Yadif to do Deinterlacing this is what I get:
"DGDecode_mpeg2source("VTS_01_1.d2v",cpu=4,info=3)". There is NOTHING about deinterlacing in those lines. RTFM!
Couldn't find something which nails it. I'll keep looking.
Moreover, What's your personal opinion? If it's good enough for you, It's good enough for me. For pure video it's "good enough for me".
royia
17th July 2010, 16:36
I suppose reading guides and manuals is not cool any more. It's much more fun pestering other people about these basic things, isn't it?
If you have questions about GUIs, post in the appropriate forum. DGIndex and DGIndexNV come with exellent guides and references, read them.
I did read them.
When there's a check box in the GUI of Deinterlace and all is done to the Avi Synth script cpu=4 and I searched for it and read it says Deinterlacing feature what else could it be?
Anyhow, it's not about Me GUI, I asked for the opinion of the Deinterlacing capability of DGDecNV in comparison to DGIndex.
I was told DGIndex doesn't do any deinterlacing. As a side note I expresses my wondering since the Deinterlace checkbox in MeGUI allegedly uses DGDec to do the Deinterlace.
If I didn't read anything I wouldn't know how to MeGUI along with AVISynth and DGIndex, Would I?
Let's not make it a debate.
My main concern is whether DGDecNV has abilities I need. That's it.
Sharktooth
17th July 2010, 16:56
the checkbox ENABLES the DEINTERLACING OPTIONS... you should check the options below to ENABLE your favourite deinterlacer coz dgdecode doesnt support deinterlacing. the CPU=4 parameter in dgdecode has nothing to do with deinterlacing.
on the other side dgdecodenv has 2 options for hardware deinterlacing. BOTH dgdecode and dgdecodenv (up to ver. 2020 - but 2021 is coming) are supported by megui DEVELOPMENT version as well as dgindex and dgindexnv.
about the deinterlacing capabilities, dgdecodenv has 2 methods for deinterlacing (both supported by megui) and the result is very good (expecially with the second method - bob) is very good.
royia
17th July 2010, 17:05
All clear, Thank you Sharktooth.
I thought when Yadif is chosen (Default, All I did is let it Analyze automatically, it set the Source Type, Field order and checked the Deinterlace checkbox with Yadif, I guess I had to open the menu and manually chose something in order to make it happen) this is it.
I guess I'll get myself an nVidia card.
Thank you all.
Sharktooth
17th July 2010, 17:18
im going to push a MeGUI update that supports the latest version of DGIndexNV/DGDecodeNV in some minutes.
@Royia: i usually dont answer to PMs.
royia
17th July 2010, 18:06
im going to push a MeGUI update that supports the latest version of DGIndexNV/DGDecodeNV in some minutes.
@Roya: i usually dont answer to PMs.
I see.
Just don't like those furious debates, Hence didn't want to open a thread about it.
I'll take experienced guy word anytime.
I'm after good enough, I won't live forever for best :-).
P.S.
It's Royi :-).
Acid_Reign
17th July 2010, 22:23
Thank you for answering my questions. I have some follow-ups…
DGAVCDec is not available because I am not happy with its functionality (broken PAFF support) and there is no prospect for it being fixed. It will be replaced by a new freeware solution in any case (see below).
Does it not make sense to leave it up for the time being then, until the new one is released?
I am the author and copyright holder and I do not now offer any license for its use, so it should not be distributed. There is no 64-bit version. I am working on a freeware solution that uses DiAVC.
OK. That being said, though, is it strictly illegal? Wasn't DGAVCDec released under the GPL, meaning it's inherently freely redistributable?
DGDecNV is not open source and requires a license. The download page clearly states that a license is required. Regarding what MEGUI does, downloading a tool is not the same as invoking it. I suppose it is done for the convenience of licensed users.
I know it does, I was just confused because the binaries are still available for download without purchasing a license—usually with paywalls, you don't get anything until you actually buy the product—which lead me to think that maybe it was only the indexing application that needed a license, and the decoder plugin was still free, or something like that. That not being the case, I think it would be more intuitive from an end-user standpoint not to make anything available until licensing, unless what is available is a trial version. Although I realize that the way it is now is probably also more convenient for licensed users and they need to be catered to first.
You do not have to install any additional DLLs; everything you need is part of your normal Nvidia driver installation.
I have the latest nVidia drivers and when I try to open an AVS with AVCSource in 64-bit VirtualDub/AviSynth, it says those DLLs are missing. Is this because I don't have a license or is there likely something wrong with my driver installation?
There are alternatives to the functionality provided by DGAVCDec, e.g., FFMpegSource, DSS(), etc., if you are unable/unwilling to license DGDecNV.
At the moment, unable. But I appreciate your work and when I can I will have no problem compensating you.
Guest
18th July 2010, 01:37
Does it not make sense to leave it up for the time being then, until the new one is released? It's not up to my standards for quality software so I don't want it out there. I can't fix it because the libavcodec guys (apparently) don't care about the regressions I have reported in random access. There is also some history involved and I don't want to go into all that. I have no interest in doing anything more with libavcodec. It's too frustrating for me.
OK. That being said, though, is it strictly illegal? Wasn't DGAVCDec released under the GPL, meaning it's inherently freely redistributable?
Actually it was not released under GPL. The source code was always closed. Violation of copyright is a civil offense. You can find it on the net. I won't trouble you about it but I won't link it on my web site anymore, because it's not something I can be proud of.
Although I realize that the way it is now is probably also more convenient for licensed users and they need to be catered to first. Bingo! Give that man a cigar.
I have the latest nVidia drivers and when I try to open an AVS with AVCSource in 64-bit VirtualDub/AviSynth, it says those DLLs are missing. Is this because I don't have a license or is there likely something wrong with my driver installation? AVCSource() is the source filter for the withdrawn DGAVCDec. DGDecNV (latest version) uses DGSource().
DGAVCDec does not use those DLLs, so I don't know what to tell you. What does the script look like?
Acid_Reign
18th July 2010, 12:47
DGAVCDec does not use those DLLs, so I don't know what to tell you. What does the script look like?
It's really basic:
v = AVCSource("F:\00001.dga")
a = NicAC3Source("F:\00001.dga PID 1100 3_2ch 48KHz 384Kbps DELAY -83ms.ac3").DelayAudio(-0.083)
AudioDub(v, a)
I have DGDecode.dll, DGDecodeNV.dll, and DGMultiDecodeNV.dll in my plugins64 directory.
When I try to open the script in VirtualDub I get:
The program can't start because libmmd.dll is missing from your computer. Try reinstalling the program to fix this problem.
The program can't start because nvcuvid.dll is missing from your computer. Try reinstalling the program to fix this problem.
Avisynth open failure:
There is no function named "AVCSource"
(F:\00001.avs, line 1)
The third error is expected because there isn't a 64-bit DGAVCDec, but what's causing the first two errors? If I change to DGSource(), I get the first two but the third one becomes:
Avisynth open failure:
DGSource: CUVID Server is not running!
(F:\00001.avs, line 1)
Again, expected because I'm not licensed. I'm not actually trying to get this to work; I'm just curious as to whether licensing would actually fix the first two errors of if there's a separate issue here.
Guest
18th July 2010, 13:06
I checked with depends that DGAVCDecode.dll does not depend on the cited missing DLLs.
The last error is not due to licensing. You need to have the CUVID Server running to use DGSource().
Regretfully I don't have time to help further with a "curiosity" problem. And anyway, I don't support DGAVCDec anymore.
Acid_Reign
18th July 2010, 14:23
Regretfully I don't have time to help further with a "curiosity" problem. And anyway, I don't support DGAVCDec anymore.
Perfectly understandable.
In any event, I tried running the CUVID Server and got:
ERROR: Failed to find CUDA-compatible D3D device.
Seems the GeForce Go 7200, which I have, is below VP2 and thus incompatible with the NV tools. (Sorry! I really should have checked this beforehand. :()
My guess is that AVISynth was not invoking DGAVCDec (how could it, without a 64-bit binary?), but instead DGDecodeNV, which does depend on those two DLLs, despite the fact that they aren't actually needed to decode the DGA file. But, the DLLs are missing because they can't/aren't used by my GPU. I think that solves this "mystery"…
Guest
18th July 2010, 14:34
My guess is that AVISynth was not invoking DGAVCDec (how could it, without a 64-bit binary?), but instead DGDecodeNV, which does depend on those two DLLs, despite the fact that they aren't actually needed to decode the DGA file. But, the DLLs are missing because they can't/aren't used by my GPU. I think that solves this "mystery"… Calling AVCSource() cannot invoke DGDecodeNV because the latter does not contain a function named AVCSource().
Acid_Reign
20th July 2010, 07:39
Looks like the problem was the DLLs I had in my plugins64 directory. I took them out and the error messages stopped.
brencreetle
29th July 2010, 23:03
I just downloaded [spam] sdk , it seems to be a great product and i have tow questions about it :
-can i sell a programm that use this sdk ?
-the program must be open source ?
Thanks.
Guest
29th July 2010, 23:08
OK, dude, your off topic stuff is really irritating me now that you are polluting my threads. I'm issuing strikes. Knock it off.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.