Is there a way to write images using the original images source folders as new folder locations?
shot_01 / image 1.raw (—>) shot_01 / image 1.jpg
I think it should look like this. source folder/file name
Thank you
1 Like
It isn’t currently possible, but I can look into it.
I just want to make sure I’m getting this right- you don’t want the images written back to the same folder, you want them written to new folder, which is the same name as the folder the image came from? For example:
/My Originals/Folder A/Image1.raw
to
/Processed/$sourceFolder$/$imageName$.jpg
aka:
Processed/Folder A/Image1.jpg
is that right?
-gus
That is exactly right.
In beta 5, I added “Source Folder” as a token option for text watermarks and file names. So try that out, and let me know if it works for you or not.
1 Like
I just want to write to the same folder 
It’s on the list, and is probably our #1 request right now.
1 Like
Is there any progress on either writing to the same folder or writing to a new folder using the same directory structure? It would significantly improve the workflow for our team.
Not yet. It’s a little tricky and there’s somethings we have to get in place first. Hopefully it’ll happen soon though.
1 Like
From the release notes on the latest build (Latest Builds from Flying Meat):
- New “Source Folder” token for the Write node, can be used to write an image back to the same folder it was read from. The previous token of the same name has been renamed to “Source Folder Name”.
Try it out- let me know what you think!
1 Like
This is great! Exactly what we need. Thank you!
Can you please explain how to use it? I added the token to the File name field but that will only create a subfolder “SourceFolderPath” inside my downloads folder.
The SourceFolderPath bits only kick in when there’s no Folder: option set. This should probably be considered a bug on my part (sorry).
So to fix it, remove your write images node, re-add it, and don’t pick an output folder when prompted. Let me know if that doesn’t do the trick.
1 Like
I can’t get this working at all. Even on an ultra simple workflow test.
What’s the secret to using it?
That should do it. The files aren’t showing up like “test001.jpeg” ?
I wonder if maybe Retrobatch doesn’t have permission to write to the folder you’re reading the images to. Are the images on a remote server, or are they just inside your mac?
Yeah nothing happens. I’ve tried in various ways - converting format - not converting - etc. It works when I direct select the folder for writing, so I don’t think it’s permissions. And it’s local not remote. 
If you launch Retrobatch from the Terminal app (pasting in /Applications/Retrobatch.app/Contents/MacOS/Retrobatch assuming it’s in the Applications folder will do it) and then run the workflow, does anything interesting print out there?
It shows this:
I think I’ve found it tho - Read folder is running on a parent folder with two folders inside. I’ve checked ‘Include images in subfolders’.
If the Read Folder node is a direct folder with images inside it works. But I need to run it on a folder of like 20 folders. I might be just doing it all wrong?
I’m trying to do a workflow that does quite a few outputs - but setting the output folder on all of them is tedious (when I’ll be doing this a lot for a lot of different parent folders.)
I just want it to write to the same source folder for all of them. The ‘Read Folder’ node has many sub folders with images in them.
Oh - OK, I’m seeing that problem on my end now as well. I’ll look into it and see if I can come up with a good solution.
Thanks!! It’s the one thing blocking everything I want to do!
Appreciate it. This software is a masterful work of art.