Support forum for DG Tools

In the latest iteration Lav Filters 0.57 added:

LAV Video
- Enabled Hardware/GPU Deinterlacing when using the QuickSync decoder

As DGAVCDecDI is IMHO an almost dead project, do you think to interact with the author of Lav Filters to create something that doesn't require a NVidia video card to use your software?

I may support QuickSync at some point, but such an effort cannot start for at least several months.

neuron2 wrote:I may support QuickSync at some point, but such an effort cannot start for at least several months.

sev·er·al
/ˈsev(ə)rəl/
Adjective
More than two but not many: "the author of several books"; "Van Gogh was just one of several artists who gathered at Auvers".
Separate or respective: "their several responsibilities".

So, maybe in 2013?

He he. The important qualifier that you apparently missed was "at least".

But your apparent regard for my hero Vincent compels me to try to elaborate helpfully for you.

I have to give a talk on foundations of QM at a SPIE conference in August and then I am visiting the UK in September. Maybe something could happen in the last quarter of 2013.

Sounds more than reasonable, just got my 4770k so eager to being able to utilize the built-in GPU for offloading the CPU, currently only have a Nvidia card with the VP2, so speed is mediocre with resolutions above 1280x720...

Everytime I open a recording I get a messagebox in front of my with the Encrypted Audio Warning.. is it somehow possible to disable this warning?
Everytime I get this i just click on the No button and everything is fine.

Would it be possible for you to detect the AVC profile of the input file right away and then complain to the user when they try and specify a lossless profile.
Like,
Lossless and/or 4:4:4/4:2:2 chroma is not supported, please convert to a different AVC profile that isn't High 4:4:4 or High 4:2:2.
This would save your DGIndexNV.exe from reading in a probably very very large file and then crashing which in turn leads the end user to post here in the forum about this. I almost posted about this as well until I luckily came across the same issue in at least two of your forum threads. I'm pretty certain you software probably already detects this sort of thing. It not so much your software is broken as the End user, me, is unfamiliar with what profile I just captured to or what profiles your software supports. I take for granted I can throw pretty much any file into your software and it have it perform correctly. AVC Profile supported/unsupported Isn't really mentioned in the downloaded DGIndexNVManual.html or DGDecodeNVManual.dll or Changes.txt (There is actually a mention for Build 2010 about this sort of pop-up, but perhaps this isn't working?)

After writing the above, I started creating sample files to go with these statements, but found these smaller files don't crash DGIndexNV... the first time. I even got the popup mentioned in your changes.txt for one of the encodes! Worse case, it say no frames and the profile and level are not recognized. I tried running these file again through DGIndexNV and this time it crashed. I currently have an index going on in another DGIndexNV, but I've been pausing it while testing these smaller files. I'll try the files again after that finishes.

Hello.

Is there anything useful in the new SDK for DGDecNV??

NVIDIA Video Codec SDK 6.0 adds following new features.

Unified SDK for video encoding and decoding
Windows 10 official support
Support for H.264 Motion Estimation only mode
Support for input surfaces in RGB format
Support for SEI and VUI fields for H.265
Support for Adaptive Quantization for improved subjective visual quality with H.265 (adaptive quantization for H.264 is already supported)
GPUs supported for H.265 (HEVC) encoding
GeForce GTX 960, GTX 980. GTX Titan X
Quadro M4000, M5000, M6000
Tesla M4, M6, M60
Various quality and performance improvements in encoding
SDK samples no longer require the CUDA toolkit installed in order to build.

SDK Updated (NVENC SDK 6.0): November 30, 2015

It appears to be NVENC centric without anything significant for NVCUVID decoding. Correct me if I have missed something.

Maybe but i found this in the Decoder API Documentation section.

NVIDIA Video Decoder (NVCUVID) Interface (Programming Guide): https://developer.nvidia.com/nvidia-decoder

DA-05614-001_v8.0 | November 2015

So I was just curious if there was something useful for DGDecNV.

You can read as well as me, and vice versa. What do you see that there that intrigues you?

KNLMeansCL (Nvidia OpenCL) + DGDecIM = Works on both Win10 and Win8.1

KNLMeansCL (Nvidia OpenCL) + DGDecNV = Freezes on Win10 but works on Win8.1

So I had hoped that there was something new in the SDK that could help on my problem.

I don't see any mention of OpenCL or interoperation of OpenCL with NVCUVID.

What about an email notification/subscription for any updates to the binaries?
Be it silent or new stable.

Would this work: I have a single thread that I post to when I upload something. You subscribe to the thread and the forum automatically notifies you.

That would work!

Excellent. Please subscribe to this thread:

viewtopic.php?f=8&t=463

Subbed. Thanks a lot!

You're welcome, and thank you for the suggestion.

You might want to just lock the thread to prevent people from posting in it and triggering e-mail notifications for all of the subscribers. Administrators and moderators can usually post in locked threads on phpBB forums, while regular users cannot (so you could post updates without anyone else causing interference). That is assuming, though, that users can subscribe to locked threads on this version of phpBB.

That's an interesting idea. I'll lock it now. Then perhaps you can help by unsubscribing and then trying to resubscribe, and let me know the result. Thanks.

The subscription link still works for me, and the binaries update notification thread now appears in my UCP in my list of subscriptions. As for you, you should find that the "LOCKED" image is actually a hyperlink that allows you to post in the thread, whereas for us peons, the link directs us to a page saying that we're not allowed to post in that thread.

OK, sounds good, Aleron. Let's see what happens on the next upload. Thanks again for the suggestion.

FYI, I just got an e-mail that you posted in the binaries update thread, so all seems well on the notification-of-posts-in-locked-threads front.

Great. Thanks, Aleron.