Very good points and very good questions. Thank you. All is possible and everything is on the table.

This thread may be of interest to you:

viewtopic.php?f=8&t=710

Slipstream 183 is released. Thank you again, Guest 2, for notifying us about this matter.

Marking resolved.

I don't understand your further question. Can you give me a specific scenario, with a link to the relevant bluray disk?

DGDecNV slipstream 183:

* Revised to make DGDecNV compatible with the newest nVidia drivers, e.g., 436.xx. Note that the DGSource() parameter 'fulldepth' is now removed. Refer to the DGDecodeNV user manual for details. [Guest 2]

* Updated the DGDecodeNV user manual. [Guest 2]

Humble hint for future release: provide path to DGHDRtoSDR in DGIndexNV.ini and use it to display preview when HDR is found using SDR display (vast majority of us, I think). On a second pass, ability to tweak parameters from DGIndexNV interface. And so for all the great CUDA filters you wrote. It w...

My subconscious mind was throwing up a coder's block and I couldn't figure out why. So I doubled up on the lactobacillus reuteri and the fish oil and a divine spark of creative energy blazed within me.

Thank you bacteria. Thank you fish. You have not lived in vain.

Good news guys! I have it coded and working fine under 436.xx. I did it just as earlier described. As expected, the hardest part was getting the P016->RGB24 CUDA kernel working. Debugging is difficult for kernel development; even doing a printf from kernel code is a nightmare. But I got lucky after ...

You are looking for something like PGCDemux to properly split by episodes. DVD is too ancient for me to get motivated to add PGC parsing funtionality. Use the other popular forums to get help with it as here I support only DG tools.

Guest 2 wrote: ↑

Fri Aug 23, 2019 1:38 am

Why not to expand functionalities of HDR to SDR CUDA to apply transformation with dithering?

Yes, everything is on the table.

hydra3333 wrote: ↑

Thu Aug 22, 2019 11:06 pm

It would be interesting to see if any existing end-user scripts need changing to suit.

Any script that has DGSource() opening a 10-bit stream with explicit or implicit fulldepth=false will need to be changed.

I don't think it is a source filter's job to be doing bit-depth conversions.

Yes, and there are much better dithering options available when converting with Avsynth+/Vapoursynth.

We need a P016->RGB24 kernel for DGIndexNV. DGSource() can always automatically deliver YV12 or P016 depending on the input stream bit depth (no more fulldepth option).

It's all clear now. When 10-bit came along and before nVidia officially supported it, some people discovered that with a little hack you could decode the 10-bit and the driver would downsample it to 8-bit (NV12). The decoder was set up with an NV12 surface and everything worked fine. For DGIndexNV t...

Players and passing HDR to your monitor are outside the scope of the DG forum. What is in scope is opening HDR in DGDecNV and processing it with Avisynth+/Vapoursynth. HDR will appear washed out if played by a non-HDR chain. So it will look washed out in DGIndexNV. However, you can serve the video v...

DGDecNV slipstream 182:

* Fixed regression in MP4 handling (crash on open) introduced in 179->180.

Bummer. First I'll try to run nVidia decode samples under the new driver.

Released as slipstream 181.

DGDecNV slipstream 181:

* Fixed CLI -at option to not depend on the GUI setting for "Enable template". [renols]

* Brought back the DELAY value in the demuxed filenames. [Xunkar]

* Revised DGIndexNV user manual to add an Appendix F describing audio delay reporting notes.

For DGIndex compatibility, the DELAY value in the filenames is returning (thank you divine spirit for source control). Here is an appendix I will add to the DGIndexNV manual. Comments are welcome. It will be included in the next slipstream. Appendix F: Notes on Audio Delay Reporting When demuxing au...

Welcome to the forum Xunkar ! Thank you for your post. Regarding the audio delay in the demuxed filenames, I had removed it after running into some cases where it is inaccurate, and after spending inordinate time analyzing such cases. Perhaps I was hasty. I will look into bringing DELAY back, in con...

You are correct renols. The GUI setting should be irrelevant for CLI operation. It's fixed locally and will be in the next slipstream. Thank you for pointing it out.

Both issues fixed in slipstream 180. Thank you for pointing these out.

Don't see anything interesting there (at least for DG tools).