No support for Canon or Nikon?
I've used CO 4.01 for editing and processing rawfiles from Canon 5D but after having downloaded CO 4.1 everything is grayed out in all adjustment tools and processing is also unavailable. I can see the images but unable to do anything. Do I miss something? Best regards Jorgen Andersen
0
-
You might have started CO 4.1 in DB mode. It will only serve Phase One Databacks. Start in regular mode and DSLRs are supported. 0 -
Thanks for your reply. That makes sense but how can I change to regular mode? 0 -
Have you activated the program? If not you get three options now (two in previous release). Choose Try or Activate. 0 -
Good point - but still no luck. It cannot be because that I run it on a G5, can it? It worked perfectly on 4.01 even with a mix of Canon and PhaseOne files in the same folder. 0 -
Hi Jorgen,
If you have activated with a DB license code it will only run in DB mode. If you activate with a Pro key, it will run both DB and DSLR. You can deactivate the software from the Capture One Menu, or by logging into Phaseone.com and accessing license management from the My accout link at the top of the screen.0 -
Thanks for the replies. I have looked at "my account" and it seems that I have 2 licenses - one for DB and one for "CaptureOne legacy". The last mentioned I have used for activation of 3.7.8Pro and for 4.01 with no problems. But using the same license in 4.1 will not solve the problem. Should I get a 3. key? 0 -
I have been in contact with PhaseOne support and my problem is now solved. It turned out to be the license key itself that made the CO4.1. go in DB mode. Here is what support said:
But right now they have release version 4.1.1 and the issue is solved. Great support!
Dear Jørgen,
unfortunately this is an unresolved issue that we know of in Capture One 4.1. When it is unlocked with a specific type of key, that you happen to possess, it will not be able to process DSLR images. We are aware of this problem and are trying to fix it at the moment.
There is currently no known workaround, except to use Capture One PRO 3.7.8 or previous versions of Capture One 4, which will work just fine. We are not currently sure where this issue originates and thus do not know whether the fix will require a re-release, for example Capture One 4.1.1 or Capture One 4.2 or whether it will be possible to be fixed on our license servers only.0
Post ist für Kommentare geschlossen.
Kommentare
7 Kommentare