Posts: 2
Threads: 0
Joined: Aug 2017
(07.08.2017, 04:55)Selur Wrote: No, I'm not generalizing. Hybrid looks for 'Device Description' entries below 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video'.
An export of the 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video' might be worth a look.
Cu Selur
Awesome, I hope this helps. I'm not 100% sure I did this right but have a look and let me know if it helps.
Cheers,
Kaz
File is here:
https://file.io/w9NAHi
Posts: 10.987
Threads: 57
Joined: May 2017
The file link gives: {"success":false,"error":404,"message":"Not Found"}
Also I send you a link to a dev version for testing a few days ago,..
Posts: 1
Threads: 0
Joined: Aug 2017
(09.08.2017, 05:10)Selur Wrote: The file link gives: {"success":false,"error":404,"message":"Not Found"}
Also I send you a link to a dev version for testing a few days ago,..
That's what I get too.
Posts: 3
Threads: 0
Joined: Sep 2017
I can confirm this problem is happening with Windows 10 Fall Creators Update, build 16278. I am using an PowerColor (ATI) R9 380 and also PowerColor (ATI) R9 380X Myst Edition. I checked the registry under the specified key and there is no key 'Device Description'. I have tried ATI Radeon software version 17.9.1, dated Sept 7, 2017.
What I am experiencing is that if I set the Video handling to VCEEnc, and then within the VCEEnc tab I select h265, the encodes crash as soon as the VCEEnc.exe starts. I did enable debugging and have the HybridDebugOutput.txt. I checked to be sure the ATI R9 300 series boards have HEVC support and they do, from what I can read.
Doug
Posts: 8
Threads: 2
Joined: Jun 2017
(10.09.2017, 04:16)khun_doug Wrote: I checked to be sure the ATI R9 300 series boards have HEVC support and they do, from what I can read.
The AMD R9 300 doesn't support HEVC.
Polaris, or later support this (RX 460/480...)
You can use VCEEnC in H.264 only
regards
Posts: 3
Threads: 0
Joined: Sep 2017
That's curious because the information I find on the AMD boards is that beginning with the R9 300 series boards, those that are Tonga build, do have H.265 encoder. It could well be that there is misinformation on the various forums. And almost without question the hardware encoder will not benefit from the enhancements being made to an external encoder like x265. But sure would be nice to use all the video board hardware for something
Posts: 3
Threads: 0
Joined: Sep 2017
I can now confirm this bug still exists with Windows 10 build 16288 (Fall Creators Build, test version) and a GeForce 1060 board with NVIDIA chip-set. There are no keys under HKLM\System\CurrentControlSet\Control\Video with a key name of "Device Description". The only key that is close is "DeviceDesc". I manually copied every instance of DeviceDesc as Device Description and added the same string value that is in DeviceDesc. That is a workaround for now.
Douglas
Posts: 2
Threads: 0
Joined: Sep 2017
I am in the same situation but with Windows 7 x64 SP1 - NVIDIA GeForce GTX 1060 3GB
I use Cyberlink Powerdirector 15 and the CUDA encoding works just pefectly, but no choice in the drop down menu in Hybrid.
Hybrid ver. 2017.05.06.1
Link to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video exported file:
https://www.4shared.com/s/fTgrAIFbIca
Posts: 10.987
Threads: 57
Joined: May 2017
Too much hassle to download from somewhere where I need to register first,..
Will send you a link to my current dev version which fixed the issue for the other users, if it doesn't work for you best attach the export to a post here.
Cu Selur
Posts: 2
Threads: 0
Joined: Sep 2017
(20.09.2017, 21:19)Selur Wrote: Too much hassle to download from somewhere where I need to register first,..
Will send you a link to my current dev version which fixed the issue for the other users, if it doesn't work for you best attach the export to a post here.
Cu Selur
Here is the export...
The dev version did not fix the issue