Jonathan Knights
- Total activity 232
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 40
- Subscriptions 66
Activity overview
Latest activity by Jonathan Knights-
Jonathan Knights commented,
Well I just hope that CaptureOne management dont find out that the ship has sailed and sunk!
-
Jonathan Knights commented,
Got to agree with so many people who have responded. CaptureOne Pro was a unique product that I was happy to pay £150-175 per year and to support the beta test program. Most beta programs give a f...
-
Jonathan Knights commented,
If they offered a future roadmap of enhancements then I would be more tempted but quite honestly this new pricing plan is more likely to drive me to another solution/software.
-
Jonathan Knights commented,
Time to move to Darktable full time I think. Oh and it is free. How good is that!
-
Jonathan Knights commented,
Any further comment from CaptureOne staff would be really good. Is this coming? Is it not possible? Any information would be useful!
-
Jonathan Knights commented,
I agree that the removal of the Process Recipe tab is a disaster. Especially as there is no way for a user to restore this functionality. Please bring back the Process Recipe/Export tab.
-
Jonathan Knights commented,
I am wondering since there has been much comment about this in some of the forums (fora) here and in other parts of the community whether this Feature Enhancement request has been added to the list...
-
Jonathan Knights commented,
@Simon Tregidgo. I have been informed in the past that it is impossible to add Channel Mixer to COP. Since I understand the RAW processing pipeline and how it needs to be implemented for image pro...
-
Jonathan Knights commented,
I dont think that the response I have had from the engineering team or whoever triages these feature requests are satisfactory. I am told on one occasion that Chanel Mixer requires the use of a pix...
-
Jonathan Knights commented,
Hi George, I realised that, as I am also a long term COP user, since v6.x like you. But the removal really breaks my 'visual workflow' (at a tab level) which was my point, previously I would start...