pcas1986 wrote:Sorry, I just noticed you are a Linux user but maybe your expertise includes Windows as well?
My prime imaging box is Windows
But it currently only has an old GeForce card with no OpenCL support.
Amazon should deliver a FirePro tomorrow, then I can check on the windows box.
I want a 27" screen. With display port connection. So if I have to buy a new card anyway, I might as well get one with OpenCL support and a 10bit data path (future proofing...). C1 supports OpenCL for example.....
My Linux Laptop supports OpenCL, but there I turned it off as it makes AS slower....
Ok, the FirePro V4900 arrived, so far a noticeable speed increase (13 vs 18s for 26 D700 NEFs in default mode, the others being slower), no real benchmarking done yet.
For those where AS will not start because of the OpenCL driver, try to add the following registry keys:
Navigate to
Computer\HKEY_CURRENT_USER\Software\Corel\AfterShot Pro\Preferences
If there is no OpenCL entry, add a new key with that name.
CLUtilization REG_DWORD 0
DeviceEndabled REG_SZ Turks
Enabled REG_SZ false
PreferredPlatform REG_SZ AMD
Theoretically only Enabled should be needed, but I did not really test that out.
OK, I tried those settings but with no luck. Curiously, ASP is not creating crash dumps as before. This occurred a couple of days ago and then they suddenly appeared.
I played with some of those settings including setting Enabled to true, etc, but same result. I'm being to think the problem is elsewhere.
Thanks to you and all who replied. Guess I'm going to forego AS Pro, as I'm not about to upgrade my video card. Every other piece of photo-editing/cataloging software on my system works perfectly well (even PSP X4, when I call it up on occasion) with no need to edit the Registry or upgrade hardware. I'll stick with Lightroom and Photoshop. Just wanted to give ASP a shot - didn't work. Oh, well.
Good and absolutely unexpected news. Seems that version 1.2x works with my Quadro 2000 (and supports the Panasonic Lumix FZ200 and Canon 700D). So Corel has, wittingly or not, solved my problem, and I have no technical clue as to how. There wasn't even the usual blurb in version notes to the effect of "addressed several known hardware issues."
