I ran a Retrobatch job earlier today and noticed a warning while it ran. Clicking the “!” icon after the job finished, I can see the text message “Change Color Profile: The file couldn’t be opened because it isn’t in the correct format.” It does not tell me which file did this. There’s nothing useful in the Console:
ℹ Switching to JavaScript runtime <FJSRuntime: 0x600000f774e0>. ❤ 2026-01-21 16:08:16 +0000 Starting process ❤ 2026-01-21 16:08:51 +0000 Finished process - 35.41 seconds, 343,030,854 pixels processed ❤ 2026-01-21 16:10:52 +0000 Starting process ❤ 2026-01-21 16:43:20 +0000 Finished process - 1948.65 seconds, 116,812,800 pixels processed
Do I need to enable more verbose logging somehow?
I’m not too concerned in this particular case, but I might have more serious warnings or errors in future and I’d want to know more about what’s happening than just “started” and “finished”.
I’ve updated the warning for the next build so it’s more descriptive. In short, the path for the color profile you’re wanting to change it to can’t be resolved.
Thanks, Gus! I’ll make a note somewhere about this batch of original files, and when the next release comes along, I’ll try the workflow again.
All the files were HEIC, photos exported from my iPhone. (Or they should have been… hmm, maybe I also selected something else erroneously at the start of the run.)
I’m strongly in favour of verbose logging out the wazoo being an option, by the way. I’ve never looked into the Console before in Retrobatch. Does much happen there? Or just start/finish times, and maybe something like a stack trace if a JavaScript thing breaks?
It’s mostly JS things, start and stop times, and random output if things go wrong. If you’re working on a JS plugin, then console.log("") will show up in the console.
In the past I haven’t had a good way to show errors, so lately I’ve been using that to throw up more descriptive errors.