Today I threw together a little app that some of you might find useful. If you want to give it a try, let me know and I'll make it available free of charge.
For whatever reason, it didn't occur to me to keep a copy of the RAW file with my processed file until Ned mentioned this habit in one of his posts a year or two ago. even then it's taken me until just recently to actually get into the habit of doing this.
Luckily for me, always maintain the original camera-generated filename and just append my indexing pattern onto that. I did this so that I could go back and find the RAW if I needed to reprocess the file. That habit is what saved my butt here.
The point I'm getting to is that I have a pile of backup media that would take me forever to go through manually to get the RAWs copied to the folders containing the corresponding PSDs. Well since writing test automation is 95% of my job, I decided to throw together a quick little app that searches my RAW backup media (CDs and DVDs) tries to match the filenames with my PSDs. If it finds a match, it copies the RAW file to the PSD's folder.
Anyway, if you're in the same predicament, this thing might be useful to you.
- It's pretty rudimentary, but it is GUI driven.
- It won't overwrite a RAW file if it already exists in the destination folder.
- Only tested on XP. It will probably run on Vista. no reason it shouldn't, but I haven't tested it.
- Written in C#, and requires .NET Framework v3.0 or higher.
- when it finds a match it displays the path and filename of both files.
- you can choose to copy or skip each match, or you can tell it to automatically copy the RAW if it finds a match.
If you have ideas for modifying this app to do more, I'll look into it. If it's an easy feature, I'll make the change. Just bear in mind that my coding skills are those of a Tester, and not those of a professional developer.
Pretty cool, Curtis. I keep my RAW files with my PSDs as well, though in a separate folder for a number of reasons. If your program could allow a user to define the destination folder as an alternative to putting the RAW in the same folder as the PSD, I think that would be beneficial.
I like to keep the RAW files separate from anything that's ever been processed. I use CaptureOne for my RAW processing; when I direct it to a folder, it loads all images in the folder and builds previews. If my processed images are in the same folder as RAW, it takes much longer for CaptureOne to compile the images/previews.
p.s. everyone knows it's the testers that make the software work.
Rick, adding a text box to allow the user to designate an alternate destination would take just a few minutes. so I'll probably do that this weekend, while I'm working through the rest of my backup CDs
Discussion
2 repliesToday I threw together a little app that some of you might find useful. If you want to give it a try, let me know and I'll make it available free of charge.
For whatever reason, it didn't occur to me to keep a copy of the RAW file with my processed file until Ned mentioned this habit in one of his posts a year or two ago. even then it's taken me until just recently to actually get into the habit of doing this.
Luckily for me, always maintain the original camera-generated filename and just append my indexing pattern onto that. I did this so that I could go back and find the RAW if I needed to reprocess the file. That habit is what saved my butt here.
The point I'm getting to is that I have a pile of backup media that would take me forever to go through manually to get the RAWs copied to the folders containing the corresponding PSDs. Well since writing test automation is 95% of my job, I decided to throw together a quick little app that searches my RAW backup media (CDs and DVDs) tries to match the filenames with my PSDs. If it finds a match, it copies the RAW file to the PSD's folder.
Anyway, if you're in the same predicament, this thing might be useful to you.
- It's pretty rudimentary, but it is GUI driven.
- It won't overwrite a RAW file if it already exists in the destination folder.
- Only tested on XP. It will probably run on Vista. no reason it shouldn't, but I haven't tested it.
- Written in C#, and requires .NET Framework v3.0 or higher.
- when it finds a match it displays the path and filename of both files.
- you can choose to copy or skip each match, or you can tell it to automatically copy the RAW if it finds a match.
If you have ideas for modifying this app to do more, I'll look into it. If it's an easy feature, I'll make the change. Just bear in mind that my coding skills are those of a Tester, and not those of a professional developer.
I like to keep the RAW files separate from anything that's ever been processed. I use CaptureOne for my RAW processing; when I direct it to a folder, it loads all images in the folder and builds previews. If my processed images are in the same folder as RAW, it takes much longer for CaptureOne to compile the images/previews.
p.s. everyone knows it's the testers that make the software work.