OSX Epson RAW workflows & EXIF data

[PaulN]

I've followed the threads in the past on ways to perform a batch conversion, and have settled on using some open source tools & some shell scripts I've cobbled together. The only problem is that EXIF data is not copied over. Does anyone know of any tools to find the EXIF data in a ERF file and print it out? Ideally, it would be a command line tool.

If someone knows of a tool, I'll gladly post related shell scripts to automate the task.

Speaking of automation, anyone using OSX's Automator to perform batch conversions? It seems like it has potential if there was an RD-1 automation module.

Thanks,
-Paul

 

[rweissman]

Lack of EXIF Data is OSX

Lack of EXIF Data is OSX

None of the tools I use, PS CS2, C1, etc. seem to access much if any EXIF data. I can't even see shutter speed or aperture from espon raw files. Anyone know how to get these tools to recognize EXIF data?

 

[PaulN]

GraphicConverter

GraphicConverter

A lot has changed since the last time I've looked at OSX R-D1 workflows. It turns out that LemkeSoft's GraphicConverter tool will import R-D1 files if you change the .ERF extension to .CRW. The tool uses the freeware DC-RAW converter (as does everything else, it seems). You can use GraphicConverter to perform batch conversions, as well. Cost is $35.

In addition, there are now Automator actions that support DC-Raw. You can find them at http://www.i-graph.com/ . DC-Raw converts from the ERF file to a intermediary file (PPM) or a PSD file. I have some shell scripts to take the PPM file and convert it to JPEG using ImageMagick.

Also, for users of iView, I found some Automator actions on the Apple OSX download page specific to iView. It lets you create catalogs, copy annotations, etc.

If I can find a PPM supporting Automator action, in theory, I should be able to cobble an automator script together that will convert from an ERF file to a JPEG file without having to open up any programs.

For those that just want to go from ERF to PSD, check out the above Automator script (i-graph.com). It should do everything you want.

More later..

-Paul

 

[jlw]

dcraw doesn't preserve EXIF data, so none of the tools based on it do so either unless the developer writes additional code. Dave Coffin (the DC in dcraw) says somewhere on his site that the format for this data is only partially standardized, so it would be a huge project to figure out every manufacturer's EXIF quirks.

When I was first starting to work on this, I spent a lot of time looking at the raw text of ERF files, hoping I could figure out how to write an Applescript that would extract the header data -- but didn't have any luck. Somebody with more programming experience might be able to figure it out -- but if it's too big a problem for Dave Coffin, I figured it was too big a problem for me!

The Photoshop products seem to do a pretty good job of extracting EXIF data from ERF files -- it's just scattered around the File Information dialog, so you have to hunt for it.

 

[PaulN]

dcraw doesn't preserve EXIF data, so none of the tools based on it do so either unless the developer writes additional code. Dave Coffin (the DC in dcraw) says somewhere on his site that the format for this data is only partially standardized, so it would be a huge project to figure out every manufacturer's EXIF quirks.

Thanks for reminding me 🙂 I got caught up with the Automator scripts and forgot my original problem, which was copying EXIF data from the ERF to the JPEG.

I bought a license for GraphicConverter and its not too bad. The interface is a bit clunky, and the Automator scripts do not support RAW files, but it does a decent job at converting a file (again, provided it is renamed to CRW) and copying over the EXIF info. $30 verses $80 for Raw Workshop.

 

[jlw]

Does GraphicConverter's conversion produce a linear file (generally looks too dark without additional processing) or a gamma-corrected file? I believe dcraw's default is to produce a linear file.

 

[PaulN]

Does GraphicConverter's conversion produce a linear file (generally looks too dark without additional processing) or a gamma-corrected file? I believe dcraw's default is to produce a linear file.

dcraw's default action is to produce an 8bit image. It looks like GraphicConverter is creating a 16bit linear image though. I'm trying to find an option to have it go back to 8bit mode when it runs dcraw.

Of note for OSX users, when you rename an ERF file to .CRW, the builtin thumbnail will show up. When I have time, I'm going to try and find OSX's list of file types and add .ERF and have it map to .CRW. The builtin thumbnail is _very_ useful. As soon as I figure it out, I'll post a message.

-Paul

 

[dkapp]

This may be a bit off topic, but I've been using some great free tools for quick exif & photo info viewing the past few months on OS X and thought I'd share.

It's called PhotoToolCM, and its a finder plugin giving quick access to info & easy photo changes. The site can do a better job explaining it than I can. They also have some great screenshots.

http://www.pixture.com/macosx.php

Just scroll 3/4 down the page & you'll see it.

Dave

 

[PaulN]

When I was first starting to work on this, I spent a lot of time looking at the raw text of ERF files, hoping I could figure out how to write an Applescript that would extract the header data -- but didn't have any luck. Somebody with more programming experience might be able to figure it out -- but if it's too big a problem for Dave Coffin, I figured it was too big a problem for me!

I don't think it is that big of a problem for us. For Dave it is, as he would have to support EXIF data for every file format dcraw supports. It would be a nightmare. For us, we just have one file format. I started poking around the file with the 'hexdump' command line utility, and noted that the exif data starts at 0x135 in the files. I grabbed 10 ERF files and they all have the data in the same location. If I can find the timestamp, and aperture, I should be all set.

Here's an example:
hexdump -s 0x134 -n 40 -c RAWFILENAME.ERF

It will display 40bytes of data starting at 0x134. You'll see this:
hexdump -s 0x134 -n 40 -c EPSN1693.ERF
0000134 E P S O N D S C P i c t u r
0000144 e \0 S E I K O E P S O N C O
0000154 R P . \0 R - D 1
000015c

------

I just found the timestamp. It starts at 0x17a. Run this command line to pull out the timestamp:

hexdump -s 0x17a -n 20 -c RAWFILENAME.ERF

Example:
hexdump -s 0x17a -n 20 -c EPSN1693.ERF
000017a 2 0 0 5 : 0 7 : 0 9 <space> 1 4 : 3 0
000018a : 5 3 \0

With the format of: Year:Month:date Hour:Minute:Second.

Cool.

I'm hoping that I'll be able to update my dcraw shell scripts to convert an ERF to JPEG with EXIF support in the next hour or two (unless my 8month old wakes up). If people are interested, I'll try and cobble together a writeup or .DMG installer. With some time, I may be able to cobble in some 'Automator' support.

As for Exif info, the only thing that interests me is the timestamp and exposure time. Anyone else need anything more?

-Paul

Edit: for some reason, the timetamp isn't appearing properly in this message. I've added the <space> to denote that the date is separated from the time value.


Moderators: I'm aware that this is a highly technical message for a photography forum, but in the light of getting the most out of our RAW files, I hope that you deem it to be on topic.

 

[jlw]

As for Exif info, the only thing that interests me is the timestamp and exposure time. Anyone else need anything more?

I think that exposure compensation and white-balance settings would be of use to a lot of people. Don't worry about it if I'm the only one, though, as presently I'm pretty happy with Raw Developer (and already forked out for a license for it.)

 

[Dan Lazin]

I don't believe the camera has any way of knowing what the aperture is, since M-mount lenses don't electronically transmit that info to the camera. That's why you only get aperture priority, not shutter priority. Shutter speed should be in the EXIF info, but not aperture.

That's a neat trick, conning OS X into showing the raw previews by changing ERFs to CRWs.

 

[jlw]

That's a neat trick, conning OS X into showing the raw previews by changing ERFs to CRWs.

It works with several other applications, too (such as iView.) The problem sometimes is that once you've changed the extension, you have to change it back to get the Epson plug-in to recognize it as a file it can open.

With iView, you can edit the application's file-type list so it recognizes ERF as an extension it can handle. It can't actually convert the raw data, but can at least display the JPEG preview so you can view a "contact sheet." I wonder if GraphicConverter can be edited similarly...?