Make your own features series: Ep2. Flip crop

Make your own features series Every now and again I see feature requests that are very obvious but will probably never be implemented due to the fact the perceived commercial impact doesnt interest the bean counters. This was partly the reason I learned to script Capture One, and why scripting such a valuable facet of Capture One: why wait when you can make solutions yourself. So, (with the best will and time allowing) this series will focus on solving and building for unresolved feature gaps in Capture One. Ep 2. How can… Read More

Output events

This week (though it’s taken nearly a year on and off) I finalised another Capture One app – CheckOut – based on the Output events feature. You can find the app in the store here. Scripting Output events Output events are script objects that record a variants processing history. Basically every time you process a file in C1, the app logs some data about what was done automatically. You can then query the the variant for this data. Without these, the script designer would have to create “watch folder” monitor scripts, or… Read More

Make your own features series: Ep1. Reset Crop

Make your own features series Every now and again I see feature requests that are very obvious but will probably never be implemented due to the fact the perceived commercial impact doesnt interest the bean counters. This was partly the reason I learned to script Capture One, and why scripting such a valuable facet of Capture One: why wait when you can make solutions yourself. So, (with the best will and time allowing) this series will focus on solving and building for unresolved feature gaps in Capture One. Ep 1. How can… Read More

Chicken Nuggets

This week I was working on a commission for a client. In the solution I needed to include a “technical” Style (a Style with certain parameters (meta data, flags) that aren’t necessarily typical of the generic Styles use-case). Then I realised: there was no way to really send Styles in a convenient way. I build a lot of custom install stuff for Capture One, automating the process of setup, shortcuts, dependencies etc, that help simplify and scale installations, but this seemed a little unsuitable for a Style. Then I remembered Style Packs…. Read More

Event Scripting

Events are the coolest way to utlize automation scripting, however the infrastructure for it is complex and pretty impenetrable for the uninitiated, so I wrote this article. The idea of events is that Capture One will initiate scripts automatically and repeatedly when a particular event happens. This means you can develop and extend Capture One’s behaviour to be reactive to certain repetitive conditions. Examples might be: As soon as an image is captured, process it. When I scan this bar code, do a vLookup in Excel and give me all the data… Read More

Get Started With AppleScript – Conditional Processing pt1

The following project/idea I originally produced for the Project Lemonade series for Digital Transitions webinars. The following is a short version of it, if you want to see the full webinar visit and sign up to the DT archive here. Before we get started… For part 1, we will concentrate on writing the script as if we are mirroring the same logic of using Capture One UI and UX concepts. I’m fully aware there are several approaches, model shortcuts, logic and advanced syntax to ultimately achieve the same results. However, this “parity”… Read More

Get Started With AppleScript – Scripting Selections

An intro series to scripting Capture One, with Ben Liddle Splitting hairs: Variants v. Images The thumbnails in Capture One’s browser pane are technically variants. A variant is a unique set of rendering instructions for a given source raw (or TIF, JPG, etc) image file. These instructions are lightweight (few hundred Kb at most), so you can think of these as virtual copies of your image files. Every image file you view in Capture One has at least one variant; unless you objectively create a new variant, there’ll be a 1:1 ratio… Read More

Get Started With AppleScript – Basics

An intro series to scripting Capture One, with Ben Liddle Preamble Years ago, in a warehouse in deep industrial Brooklyn, I was a digital technician on an e-commerce photo shoot struggling to stay awake. It was 3:30 in the afternoon on a crisp winter’s day, and the stylist was diligently stringing up the 80 billionth (by my estimate) crossbody’s strap of the day. The photographer was (probably) retouching his latest editorial job on his laptop in the corner. I was working with Capture One Pro 8 (iirc, maybe it was 7, honestly… Read More

Capture One shortcuts for the terminally curious: part 3 (Final)

We have arrived at the final part of this series: the script! This is a simplified extract of the full installer application I made, as it is simply far too big to break down into a single tutorial. Instead, I have made a fully functional version of the useful part, which does most of the heavy lifting and annoying bit – adding the shortcuts to a set of installed scripts. Prep: Quit C1. Make a folder in ~/Library/Scripts/Capture One/Scripts/ (For my example today: ~/Library/Scripts/Capture One/Scripts/Apply Latitude) Copy your scripts into this folder… Read More

How to make a script applet

Making a script applet is not much harder than actually making a script – from the outside the extension changes to .app, and the app when clicked will “run” rather than open in script editor. Mostly useful. I use Script Debugger for all my AppleScript work. It’s a billion times better than Script Editor. Specifically for applet design, it makes life simpler for adding and removing resources, and you can also add your icons and developer ID easily. You can do this in Apples’ Script Editor but for the uninitiated, it is… Read More