Still no scripting for Windows users
I'm wondering whether my euros/dollars have less value because I'm a Windows user. Of course, Applescript doesn't exist under Windows but any skilled Windows developer knows that any Windows application can be made "scriptable" by using the native Windows scripting engines (VBScript/JScript). I can't assume that Phase One voluntarily decided to disadvantage those C1 users running the Windows version. So, my guess is that the development team is lacking the necessary skills. Moreover, they could have chosen a scripting language that is available on both platforms.
By the way, this is not the only feature available in the Mac version that was not implemented in the Windows version.
As a discriminated Windows user, should I ask for a partial refund ?
-
i heartily endorse the need to provide scripting features for Windows 1 -
Samoreen wrote:
By the way, this is not the only feature available in the Mac version that was not implemented in the Windows version.
The opposite is true as well, although these are in general minor differences, apart from scripting.0 -
Samoreen wrote:
As a discriminated Windows user, should I ask for a partial refund ?
Were you promised scripting as part of Capture One's Windows offer?
Has Capture One forced you to stay with an OS that you can't script in?
No?
Then I think we know the answer...
Oh - and if you stop considering yourself to be a victim in every walk of your life, you'd probably be a lot happier.0 -
Keith Reeder wrote:
Samoreen wrote:
As a discriminated Windows user, should I ask for a partial refund ?
Oh - and if you stop considering yourself to be a victim in every walk of your life, you'd probably be a lot happier.
Talking nonsense is certainly not a good way of being happy either. I'm fine with my life. Thanks for caring.0 -
Samoreen wrote:
Keith Reeder wrote:
Samoreen wrote:
As a discriminated Windows user, should I ask for a partial refund ?
Oh - and if you stop considering yourself to be a victim in every walk of your life, you'd probably be a lot happier.
Talking nonsense is certainly not a good way of being happy either. I'm fine with my life. Thanks for caring.
I would avoid interacting with this particular sour sport.
Have you tried looking into the (admittedly limited) Capture One SDK?
Surely you can interact with the SDK using whatever programming/scripting language you desire?
https://www.captureone.com/en/developer
G0 -
Hi,
I'm a mac user, and I also think that the scriptings are a powerful tool which needs an upgrade in Capture One. On Mac, it seems that only AppleScript is supported, which is painful to use. It's a pity because the API which is exposed is nice and (as far as I could tell) much more comprehensive than the SDK.
Also, using the SDK is much more involved than just scripting.
So, if people from Capture One read this, my wish would be to have integrated scripting, based upon a widely used language such as Python or Javascript, identical on both Mac and Windows. Alternatively, enrich the SDK to be able to do the same, with bindings for common languages, so that it's fast to develop.
Ben
1 -
Once again I'm futilely bumping an old thread - but - is there still absolutely no way to extend or modify an export process in Capture One, by means of API or scripting?
I am absolutely desperate to find a way to overwrite existing JPGs on export.
0 -
Oh, man. That would be awesome. The current method blows chunks.
I would LOVE to see a python scripting capability added to C1. That "might" actually convince me to upgrade. 😄
0
Post is closed for comments.
Comments
8 comments