Blue Iris and Windows 11 24H2?
Does Windows 11 24H2 handle hardware decoding(more specifically NVDEC) differently than Windows 10?
I'm using a build of Blue Iris from May 2024, and using 24H2 which came out in October 2024.
Any time I enable NVDEC I get No Signal errors, regardless of camera brand or model.
I'm just trying to narrow down if buying another year of support and updates would possibly solve the issue, or if the issue is 24H2 itself, and maybe go back to Win10.
I've used the same RTX 2060 for years and it's been fine with NVDEC. The issue happened after upgrading to Windows 11 and upgrading from AM4/DDR4 to AM5/DDR5(same RTX 2060 GPU).
I've even made a build using a GTX 1070 and the old AM4 system, NVDEC still doesn't work. It's using the same May 2024 build of Blue Iris, and Windows 11 24H2.
Things I've tried on both systems;
Http and https
Generic settings with default/blank RTSP URI
Camera specific settings with brands RTSP format
Decoder compatability mode
Does Windows 11 24H2 handle hardware decoding(more specifically NVDEC) differently than Windows 10?
I'm using a build of Blue Iris from May 2024, and using 24H2 which came out in October 2024.
Any time I enable NVDEC I get No Signal errors, regardless of camera brand or model.
I'm just trying to narrow down if buying another year of support and updates would possibly solve the issue, or if the issue is 24H2 itself, and maybe go back to Win10.
I've used the same RTX 2060 for years and it's been fine with NVDEC. The issue happened after upgrading to Windows 11 and upgrading from AM4/DDR4 to AM5/DDR5(same RTX 2060 GPU).
I've even made a build using a GTX 1070 and the old AM4 system, NVDEC still doesn't work. It's using the same May 2024 build of Blue Iris, and Windows 11 24H2.
Things I've tried on both systems;
Http and https
Generic settings with default/blank RTSP URI
Camera specific settings with brands RTSP format
Decoder compatability mode