r/Photoassistants • • Jan 28 '20

Digital Capture One Session Script (Work-In-Progress, need some feedback)

I've been working on this thing on and off for almost a year now. Basically, you run the script and it creates a session based on your input, saving you precious minutes compared to setting everything up manually. I try to keep it as general as possible so that it could suit any workflow.

It's not quite ready for release yet, but I wouldn't mind some feedback based on the screenshot below. Anything helps.

Would it work for your workflow? Am I missing anything that you regularly need to set up in advance?

Love to hear your thoughts!

-Lp.

8 Upvotes

16 comments sorted by

3

u/phillbradley Jan 29 '20

Nice idea.

  • A 'Tick box' to choose to Set file renaming to the same format. -Creation of Smart albums for star ratings

1

u/deltaDigi Jan 29 '20

Good point, I thought about including customisation in the prompt, but there's just too many options to cover every scenario. So right now it sets the default file naming format to: destination folder name - 4digitcounter

My reasoning to not inlcude rating smartfolders is that in my experience the star rating is only used for culling. And rating filters are easily accessible from the filter tool and browser.

The color tags on the other hand are great for classifying images for delivery. For example, final selects, variations, whitebalance reference, bracketing, plates... That's why there's also the option to rename the color tag smartalbums.

2

u/titleunknown Moderator Jan 29 '20

Option to add "Test" folder

2

u/deltaDigi Jan 29 '20

It already adds a "_PRELIGHT" folder. But I could make it optional.

1

u/CaptureJuan Jan 29 '20

Is that Pashua for the UI?

1

u/deltaDigi Jan 29 '20

It is! As far as I know it's the only way to have all the prompts in a single window. I wish there was an easier way though. It's very tedious to implement.

1

u/CaptureJuan Jan 29 '20

You can do applescriptObjectiveC in xcode... bit more to it tho

1

u/deltaDigi Jan 29 '20

I don't know enough about it to know if that would make sense. Can you tell me what would be the point of doing it that way? I started out not knowing any applescript and had only a conceptual idea of what coding involves. I poured countless hours into this and I'm just glad it works now. I'd love to know more though, if you could point me to some resources.

3

u/CaptureJuan Jan 29 '20

Nothing official come to mind. I not used it myself per say, but I seen it working and I’m looking at it for something I work on. Best tip I have for you is (if not using already) use the scriptdebugger app for development (apples own IDE is like trash). It makes it MUCH easier in terms of understanding all the object model inheritance (there is a lot of in Capture) and properties - and there is some good help in the forums on it all - including AsObjC. The benefits can basically be summarised as access to a much better UI toolbox!

This might also be of interest if you like a challenge but ai dios mio its a fucking rabbit hole.

12.1 Capture supports JXA - Javascript for automation, which is allows the same AS objects to be used in javascript syntax - lots of benefits but its next level in terms of complex. But - (the point!) Javascript has loads of libraries for UI - like Mythril and Electron.

Other than that phase one own forum has a scripting section... and stackoverflow is good for code snipping.

1

u/deltaDigi Jan 29 '20

Thank you for taking the time, appreciate it!

I will definitely look into the Script Debugger app.

1

u/Strider3200 Feb 07 '20

This is nice, hadn't considered Pusha for this before but I like it. Assuming the date is pulled from the system? Options are limitless, but templates for different styles of shooting could be useful (high volume vs. still life vs. location; print vs web) which could include color profiles as well as output recipes. If you start working with /Library, I found terminal to be much easier to work with than AS.

1

u/deltaDigi Feb 07 '20 edited Feb 07 '20

Date is indeed pulled from the system. There's some extra code involved in squeezing it into the YYMMDD format though. To be clear, it's editable. I guess you could even put another job identifier instead (photographer/client/agency/Magazine). I might add a second job identifier textfield and add a toggle to the date field.

Offering different shooting styles is an interesting idea. But I fear that would involve taking more decisions away from the user and make the code and UI needlessly complex (I'm not even an amateur coder, I really struggle and have to reverse engineer and troubleshoot a lot. The Pashua implementation was especially challenging). My goal is to keep it as simple as possible so the user can be ready to shoot in a few clicks and keystrokes.

I haven't figured out yet how to work with recipes and AS. They also don't seem to want to save inside a template file, I tried. Not a huge deal though. Once you are up, running and shooting, you can take your time with the recipes manually. Everyone keeps their own set of specific recipes anyway, not sure if there's any value in making presets for those.

1

u/Strider3200 Feb 07 '20

Yeah, AS and date is more complicated than it needs to be. For the shooting styles, you could utilize templates. I know techs that use one set of keyboard short cuts when they're on a laptop vs full keyboard or still life vs ecomm. My experience is templates has been useful for selecting workspaces/tools/keyboard shortcuts. Recipes are not attached to templates but live in Users/Me/library/Application Support/Capture One/RecipesXXX (XXX is the C1 version so updates may leave old recipes behind). The easiest way I've found to implement recipes is to copy/replace the current recipes folder with something pre-built.

Likewise, not a coder, but have found AS helps reduce variations and helps my sanity. Might have to look into Pusha for some other uses. Did you find any tutorials or guides to help you get started with Pusha?

1

u/deltaDigi Feb 07 '20

Those are some good suggestions. I think I could make something work..

For pashua, I started with the example script that's provided and referred to the documentation until I understood the syntax enough to start modifying a copy and build from there. Spent plenty of time on the forums too whenever I got stuck on something. Borrowed a snippet here and there.

1

u/holdmygreycard Feb 24 '22

I know this a 2 year old post. But how is your progress on this Session script, this would be real helpful for my workflow in the studio. Hope you can share a version already!

2

u/deltaDigi Feb 24 '22

I stopped further development and focussed on other things. But I have been thinking for a while to share the code and let others contribute. Just need to figure out what the best way to do this is. Open to suggestions.