Scripting in the Windows version
Great section!
How do I start working with scripts in my Windows version of Capture One?
-
I don't think it is possible yet. On the Mac operating system we have access to a scripting language, AppleScript, which is not available in Windows. This how scripting control Capture One and numerous other applications on a Mac.
There has been some discussion and experimenting to use Java or Python to access Capture One's AppleScript interface, but I think this will not help a Windows user because the system services required for the AppleScript interfaces do not exist in Windows; I doubt if the Windows version of Capture One even has an AppleScript interface.
0 -
H'mmm how curious?
The price of the software for both platforms is the same, is in not?
And yet Windows users don't get scripting.
Doesn't sound fair to me.
0 -
In the Mac OS AppleScript is a powerful object oriented scripting language capable of generally controlling any application, it has has been developed over a period 25 years and is now fairly rich and mature. Any application can be hooked into it. Capture One just makes use of this, as does Photoshop and many other third party applications.
On Windows, no such system language and services exists. If a developer wants to create a scripting language for his Windows application he has to start from scratch, and it only controls his application. I think Photoshop has done this.
This sucks for Windows users, but its not a cheap or easy problem to fix.
Every operating system (MacOS, Windows, Linux, Unix) has it plusses and minusses, and you (knowingly or unknowingly) choose those when you choose the operating system (and the hardware)
I think the most productive thing you can do is make a feature request for scripting on the Windows version of Capture one.
0 -
H'mm.
So, perhaps the Windows version should be less expensive than the Mac version as it doesn't have the same functionality.
Sorry, I'm not swallowing this line of reasoning. Python can be instantiated into virtually any software application. There are a plethora of GNU tools for doing this.
Just reinforces the evidence that the Windows version of Capture One is the red headed step child of the Mac version.
I have other tools which only run on Windows. And yes, they include native scripting, both VBA and C#.
Unfortunate as scripting would go a long way to help smooth out some of the eccentricities of Capture One.
0 -
You do have a point. Best of luck with your call for a price reduction for the Windows version.
0 -
On the plus side we seem to have fewer issues with compatibility for GPU cards and drivers and, so far, a longer support period available before the operating system updates obsolete the hardware so it's not all bad news! ;)
Plus the buy-in costs can be much lower.
AND frankly I think the idea of using some sort of script, even if an official product with quality controls applied and supported by Microsoft, would be either anathema to the majority of Windows user in the photo editing world or so dangerous to offer them that it should not be considered!
I doubt that more than 10% of users would (or should) be interested and probably most of them would be better off keeping clear of such option for their own sanity and peace of mind.
;)
0 -
Well, firstly, I'd love to create a little macro that would:
a) Select all the images shown in the browser
b) Reset the export renumber.
c) Process the images
Having a macro that I could toggle with a keypress would save me three operations EVERY.TIME.I.EXPORT.IMAGES...
Having a scripting capability would go along way to smoothing out some of the eccentricities of C1.
'nuther one:
a) apply a camera specific user style to a folder of images
b) Do an Auto adjust on those images
c) De-select all the selected images
d) Move the selection to the top image.
I could go on, and on, and on as the eccentricities are voluminous.
0 -
@Christopher You last post would be an excellent example of the user value of a Windows scripting feature.
I that you make a feature request for Windows scripting of Capture One, and include this as an example of how it would be used.
I know that others have requested Windows scripting, but I think without such a clear example.
it is possible that C1 is already working on it, but it is also possible that the decision to start has not yet been made, and your example might well influence the decision and the content.
0 -
Thank you, I make heavy use of automation features in all the apps that support it.
Maybe I'm an outlier, who know.
0 -
I don't see you are an outlier, there are others.
I would ask for what you need, if you don't ask Capture One, they won't know.
0 -
Windows in a second class citizen in PhaseOne Land, simple as that.
And basically scripting is useful to overcome the software shortcomings (es. find all corrupted database references (corrupted by C1 himself))
And yes, we pay the same.
0 -
LOL!
Absolutely true.
I've signed up for the SDK, but unfortunately the library is pretty sparse.
Many cynical thoughts arise, but won't be voiced.....
1 -
For Apple users, Windows has had scripting since it started. And this was improved to the same level as Bash, ksh, Applescript, etc. nearly 15 years ago. It is called PowerShell. And I am not even a Windows fan, but more of one than an Apple fan (which I am not). I started in the IT field as a programmer on Unix and Linux systems. I can tell you that PowerShell is very similar to Unix/Linux scripting languages.
-1 -
Ok, thanks for your enlightenment...
And thanks for changing "For ignorant Apple users, Windows has had scripting since it started." line,
that was clearly rude (first part) and incorrect (I would not call the .bat scripting scripting at all).Now try to script C1 with Posh (this is how we call PowerShell informally, I bet you know it).
Let us know
0 -
@Christopher Pretty sure I can do this with a script like AutoHotkey or AutoIT
0 -
I don't understand where this belief comes from that if the operating system doesn't have a built-in scripting language, the program can't provide such a possibility. There are many programs that work in Windows that have the ability to write scripts. You can use JavaScript, VBS or Python. The first ones that come to mind, which I use every day: Photoshop and InDesign. Whenever I have a problem that bothers me for a long time - I solve it using scripts. I dare say that choosing AppleScript (instead of a universal and platform-independent language) for integration in Capture One is clearly showing the middle finger to a large group of Phase One customers.
0 -
I share your frustration. It would be great to use Python across any platform. Perhaps it was easier to code against the Apple Event System than to create a library that integrates directly Python, or perhaps AppleScript being so easily accessible to learn made it more attractive than supporting a more complex language.
By the way - PhaseOne and Capture One separated into distinct entities 3-4 years ago.
0 -
Re: Poke In the Eye.
I have been a Capture One user since version 7 in about 2015. Capture one was already quite a few years old with well developed AppleScript support. Capture One 5 was released in 2009, and AppleScript support was already part of it.
Up until about 2012 and with somewhat less emphasis since then, AppleScript has been the ubiquitous Scripting Language on MacOS/OSX.
Even Microsoft Excel, Word and PowerPoint for Mac support AppleScript. Its no more a poke in the eye than the use of PowerShell on Windows.
All that said, its about time for Capture One to disclose a scripting interface for its Windows product, Python would be a reasonable choice.
I wonder if Capture One already has a scripting interface for Windows, as its normal these days (and much more thorough and cost effective) to test a SW product through a scripting interface, than to have large staff of testers checking every function. Adobe gave up the manual approach about 15 years ago, if my memory serves correctly.0 -
I imagine Capture One does a fair amount of automated regression testing on their builds. You can't support that many cameras and develop new camera profiles and features without automated testing these days. The world of software development revolves around automated code development and deployment pipelines, agile and DevSecOps. With staff in multiple countries I feel confident Capture One uses tools that enable them to collaborate like other software makers.
As for scripting support Apple makes it fairly straightforward for apps to enable it. You develop interfaces for the Apple Event System to talk to, and provide definition libraries that describe the objects and what actions can be taken on them. We are all familiar with the model of telling a Capture One object to do something.
0
Post is closed for comments.
Comments
19 comments