[RESOLVED] 2160p / 4K decoding with DGdecNV ?

[pat357]

I've tried to use DGdecNV 2048 to decode H264 encoded 2160p media, but couldn't get it to work on my GTX-680 (VP5).
Because decoding does work in LAV-video, both for Cuvid and DXVA with this card, it doesn't seem to be a HW restricrion.

Has decoding 2160p maybe (not yet) been implemented in DGdecNV ?
If not implemented yet, are these near feature plans ?
If should work, any idea what I could be doing wrong ??

If I buy a new GTX-960, would H265 decoding be working in DGdecNV ?
Since this card has a full HW inplementation of 8 and 10 bit H265/HEVC decoding (encoding), I would think it's (altough very simply explained) about coying the data to the right place on the card and getting the decoded frames back to PC-memory.
I 'm aware a lot af other stuff comes along the corner and my explanation is serouisly over simplified

Thanks for any aswers !

[admin]

Please see your other thread regarding the frame size limitations.

H.265 is not yet supported and I cannot give you any time frame for it, although I will probably support it some time in the future.

[admin]

DGDecIM beta 21 was released. It supports 2160p.

[admin]

CUVID now supports 4K/UHD and so I have implemented it for DGDecNV. I'll make a new release shortly.

UPDATE: Version 2049 was released.

[Aleron Ives]

Does this mean there is a minimum nVidia driver requirement to use 2049, or is it only if you want to decode a UHD source?

[admin]

I don't know which nVidia driver/CUVID added support for 4K/UHD resolutions. I just decided to try changing DGDecNV to allow it and everything worked. My current installed version is 347.88.

If you have a driver that does not support it, you will quickly find out. But as you suggest it will be a problem only for 4K/UHD sources.

[Aleron Ives]

I have to stay on 326.80 to avoid the OpenCL bug nVidia added in the 330 series of drivers, so I doubt I have whatever UHD support they added. Hopefully the GeForce 1000 series cards will give me enough of a reason to ugrade to a newer chipset that doesn't have the bug.