Olympus e-510 presets

Hi all,
I've found some lightroom presets to develop the olympus ORF's like the camera or olympus studio does, but I'm not quite happy with the results.
Do you know any site or maybe you have any presets to get from lightroom the jpg's developed as in the camera?
thanks

I have made some presets a while ago that mimics the output you get from Olympus Studio when shooting raw. But that is very close to the in camera jpegs.
These are for the E-1 but I know that a few people have used them with raw files from other oly cameras and said that the results were good.
You can always delete them if you don't like them.
Download them from this link
http://www.pixels.nu/files/olye1_lightroomv1.zip
I have a page with info about the presets here:
http://www.pixels.nu/lightroom/
BUT the downloads from that page are NOT up to date, they are pre version 1.
/Andreas

Similar Messages

Adobe Camera Raw 6.2 and Olympus E-510 camera profile

Hi all!
When I open a raw file captured from my Olympus E-510 with Adobe Camera Raw 6.2 and go to Camera Calibration tab, ACR doesn't display any profile for my camera, althouth Adobe (http://www.adobe.com/products/photoshop/cameraraw.html) says it supports my model. The same happens at the Lens Correction tab, it doesn't display any profile for Olympus. If I open a raw file from other Camera (Nikon for example) everything is ok. Does anyone know how I'm going to fix this???
Thanks for your time!

You should see an Adobe Standard profile and perhaps an ACR x.x profile for your camera, but Adobe does not make Camera-centric profiles (landscape, portrait, camera neutral, etc) for most cameras unless they are Canon DSLRs, Nikon DSLRs, one Leica and a few Pentax cameras.
On a Vista/Win7 system you can verify what models of cameras are supported by Adobe by looking for profiles in:
C:\ProgramData\Adobe\CameraRaw\CameraProfiles
The lens profiles are in:
C:\ProgramData\Adobe\CameraRaw\LensProfiles
There are comparable directories on Win XP.

Olympus E-510 Camera Raw support

I've been using and Olympus E-500 and CS2 suite and have had no problem bringing in raw files (ORF) into Photoshop. However, I just started using the new Olympus E-510 and the raw files from this camera cannot be imported into Photoshop.
Does anyone know of a plug-in that will allow me to bring in the E-510's raw files (or does anyone know when an Adobe update will happen to include the E-510)?
Thanks very much.

The E-510 apparently is not yet supported, but probably within a couple of months.
(I had been reading about a magenta cast for near blown highlights for this camera at the DPReview Oly DSLR forum. I seem to remember some users checking these highlights with ACR, but I could be mistaken. Check it out.)
Unfortunately for you, it will only be supported by CS3's ACR version 4.x. You will need convert to DNG to be able to use ACR3.x with CS2. When the 510 is supported, you'll be able to download the DNG converter.

Olympus E-510 Support

Adobe: I have had my Olympus E-510 for over 2 months now, and I am getting weary of waiting for you to support this model with your Camera Raw.

>Adobe: I have had my Olympus E-510 for over 2 months now, and I am getting weary of waiting for
you
to support this model with
your
Camera Raw.
He might argue that it's meant to be implicitly plural, but then it should have been something like
Adobe developers or
Dear Adobe Raw team for clarity ;-)
English all too often allows or leads to imprecision in pronouns and tenses (in fact, modern colloquial American English is turning into Japanese in that sense), even from relatively good writers.
This guy isn't a good writer. He's simply pompous and pontificating. His superfluous use of
your shows that the most clearly. It's simply redundant, pointlessly formal, and hackneyed... ..as is the writer.

DNG cannot convert ORF from Olympus E 510

I have a Olympus E 510. My RAW files are ORF.dn G converter don't suppurt ORF or what do I do?
Leif

The DNG converter does convert ORF files from Olympus cameras. That camera has been supported for years. What makes you believe that you can't convert those files?

Support for Olympus E-510 and E-410

Hi,
Will the upcoming 1.1 update provide support for the new Olympus E-510 and E-410? If not, when can this support be expected?
Jim

This page shows all the supported formats.
Lightroom 1.1 will support all those in ACR 4.1
http://www.adobe.com/products/photoshop/cameraraw.html
Richard Earney
http://inside-lightroom.com

Can't open .orf RAWs from Olympus E-510 - how to install camera-raw?

Hi
i'm new to adobe photoshop cs3 and just wanted to try opening my
RAWs from my olympus.
Adobe always says it can't open these files.
i have already downloaded the "camera raw.8bi" but do not know how to use it.
i tried to give adobe a new plugins-folder but it seems not using it.
any help?

The installation instructions are on the page from which you downloaded it... They do change occasionally, so it's a good idea to pay attention to them.
Cheers,
Art

Olympus E-510 ORF files...

Anyone know if these will be supported some day, or how I can request that be supported?

No one here knows any of Apple's future plans - we're just Users like you. Perhaps if you used the Feedback link (iPhoto Menu) you can let them know.
Regards
TD

Hacking Leopard to support the Olympus E-3

A while back, I tried this hack in an attempt to trick Aperture into supporting my Olympus E-3. I added the following line to Raw.plist:
<key>Olympus E-3</key> <string>Olympus E-510</string>
updated the hash in CodeResources, restarted the machine, and hoped for the best. The result was that E-3 ORFs displayed as gray squares in Aperture.
The missing step was to use Adobe DNG Converter to convert the ORFs to DNGs. Once I did that, the images rendered just fine in Aperture.
I'm still disgusted that I had to resort to this nonsense to display the images from my camera.
Cheers,
Andreas

I stumbled across this thread and understand how you guys feel about cameras not being supported within aperture. For so long we waited for Leica M8 & DMR support only to find the M8 support did not match the colour matrix values in the camera. There is still no DMR support but with the introduction of Leopard Apple finally fixed the matrix values for the M8. We have the DMR working in aperture but we have to reduce the 16bit files to 14bits before it would work.
Anyway I've downloaded a E-3 file from the web, and run it through exiftool to get the matrix values and coded up a raw.plist entry for the E-3. Seeing as I don't have E-3 I can't fully gauge the accuracy of the matrix values I've entered but perhaps you'll try them and see how you get on.
Some things you need to do....
1,First thing to do is download PlistEdit Pro, the trial version is fully functional and will get you going. Download it and install it. The raw.plist file is located inside /System/Library/CoreServices/RawCamera.bundle, when you navigate to rawcamera.bundle you'll need to right click it and select show package contents from the drop down menu. You'll then see a window open up with a contents folder, open that and open resources folder and you'll find raw.plist.
2. You need to make a copy of the raw.plist file in case you make a mess of things. I usually copy it to my desktop.
3. The raw.plist file in the resources folder is a protected system file and you need to change the permissions on it to allow you to edit and save your changes. To do this right click the raw.plist file and select Get Info from the drop down menu. In the new menu down the bottom you'll see sharing and permissions, you'll need to add your username to the list and change all the permissions of the names to read and write. You may need to click the lock and enter your password to change these settings. I also set the open with to use PlistEdit Pro here. Close this Info menu and re-boot your Mac.
4. Go back to the raw.plist as you did in section 1. and double click it and it should open in PlistEdit Pro. Then in the PlistEdit Pro window there are 2 panes, we are going to work in the bottom window, I suggest you maximise the application and drag the window bar up to give yourself as much room as possible. If you scan down the entries you will notice the various camera entries start with a <key>Camera Name</key> and end with a </dict> entry. You need to find a </dict> click your mouse after it and press the enter key. This will insert a blank line into which you paste the text from the bottom of this post. Remove any blank lines before and after your paste. Save the raw.plist and close PlistEdit Pro.
5. Leopard uses a checksum to validate all system files and make sure they have not been damaged by malware. We need to change the checksum for the edited raw.plist file.
Back in the contents folder of the RawCamera.bundle you'll see CodeResources, right clic that and open with PlistEdit Pro. Click the files triangle and you'll see an entry for Resources/Raw.plist and in the value column there is a 20 digit check sum. We need to update this value. Open a treminal window and type the following openssl dgst -sha1 /System/Library/CoreServices/RawCamera.bundle/Contents/Resources/Raw.plist and press enter, this will return a new checksum for the raw.plist file. Cut and paste this value into the value column for the raw.plist entry in the top window section. Save and close the CodeResources file. Reboot your mac once again.
6. Use Adobe's camera raw to batch process your ORF's to DNG's before importing into Aperture. The options for compression and jpeg preview should be de-selected(not ticked). Then import these converted DNG's into aperture and they should work.
7. I know it's not a proper fix but at least it will get you up and running. If you do proceed, keep these instructions because every time Apple update the core image services you'll need to re-apply this patch until proper E-3 support is added.
8. You do this at your own risk, but Enjoy!.
The raw.plist entry to paste.....
<key>Olympus E-3</key>
<dict>
<key>bexp</key>
<real>-0.69999999999999996</real>
<key>black</key>
<integer>1</integer>
<key>black1</key>
<integer>1</integer>
<key>black2</key>
<integer>1</integer>
<key>cnacc</key>
<real>0.0013392</real>
<key>cnadc</key>
<real>0.11158</real>
<key>cnaec</key>
<real>0.029999999999999999</real>
<key>cnat</key>
<integer>0</integer>
<key>cnbcc</key>
<real>0.00044030000000000002</real>
<key>cnbdc</key>
<real>-0.23002</real>
<key>cnbec</key>
<real>21.879000000000001</real>
<key>cnbt</key>
<integer>1</integer>
<key>esein_0</key>
<real>0.0</real>
<key>esein_1</key>
<real>2.5499999999999998</real>
<key>esein_2</key>
<real>2.7000000000000002</real>
<key>eseth</key>
<real>2.3199999999999998</real>
<key>eseth_0</key>
<real>0.0</real>
<key>esint</key>
<real>0.59999999999999998</real>
<key>esint_0</key>
<real>0.0</real>
<key>gresc</key>
<real>2.7000000000000002</real>
<key>gresc_0</key>
<real>0.0</real>
<key>m1</key>
<array>
<real>1.1004</real>
<real>-0.44409999999999999</real>
<real>-0.023199999999999998</real>
<real>-0.62990000000000002</real>
<real>1.4071</real>
<real>0.24279999999999999</real>
<real>-0.086999999999999994</real>
<real>0.1459</real>
<real>0.74219999999999997</real>
</array>
<key>m2</key>
<array>
<real>0.94869999999999999</real>
<real>-0.28749999999999998</real>
<real>-0.1115</real>
<real>-0.75329999999999997</real>
<real>1.5606</real>
<real>0.20100000000000001</real>
<real>-0.1618</real>
<real>0.20999999999999999</real>
<real>0.7389</real>
</array>
<key>max</key>
<integer>3600</integer>
<key>mc</key>
<array>
<real>0.92020000000000002</real>
<real>0.0</real>
<real>0.0</real>
<real>0.0</real>
<real>1</real>
<real>0.0</real>
<real>0.0</real>
<real>0.0</real>
<real>1.0469999999999999</real>
</array>
<key>nek1</key>
<real>0.0097999999999999997</real>
<key>nek2</key>
<real>3.8000000000000002e-05</real>
<key>nek3</key>
<real>1.02e-08</real>
<key>nek4</key>
<real>0.0</real>
<key>nek5</key>
<real>3.0000000000000001e-06</real>
<key>nek6</key>
<real>-3.4999999999999999e-09</real>
<key>otrc</key>
<array>
<real>0.33300000000000002</real>
<real>0.095000000000000001</real>
<real>1.522</real>
<real>0.23999999999999999</real>
<real>1.397</real>
<real>0.61799999999999999</real>
<real>0.998</real>
<real>0.68000000000000005</real>
</array>
<key>scal1</key>
<real>0.35999999999999999</real>
<key>scal2</key>
<real>0.29999999999999999</real>
<key>spknd</key>
<integer>3</integer>
<key>spt1</key>
<real>600</real>
<key>spt2</key>
<real>0.40000000000000002</real>
<key>white</key>
<integer>3600</integer>
</dict>

IPhoto 09 RAW Support for Olympus E-30

Hi,
I already have an Olympus E-510 which is supported & recently got an E-30 body which doesn't appear to be supported by IPhoto.
Does anybody know when & if an update will be released to add the E-30 to the RAW compatibility list?
aTdHvAaNnKcSe

Keep an eye on the Raw compatibility list and hope the E-30 is added soon...
http://www.apple.com/aperture/specs/raw.html
Note: Camera compatibility is the same for iPhoto and Aperture.
Cheers,
Patrick
p.s. I believe the RAW support is in OS X rather than either application, so be sure to check the updates from Apple. I know I occasionally see updates for Raw support offered as a system download for OS X.

In camera raw how large should I open my raw file before converting it to a TIF file?

in camera raw how large should I open my raw file before converting it to a TIF file---2736 x 3648 (10.0 MP), 3072x4096 (12.7 MP) or 3840x5120? (19.7 MP). I want a sharp TIF file. I'm shooting with an Olympus E-510, 10.0 MP camera?
thanks - Ken
[email protected]

rasworth wrote:
There is no advantage to saving or opening other than at the native resolution.
Actually, not entirely true. In the case of Fuji DSLR's you would do better to double the rez in Camera Raw as that matches the interpolation that the Fuji software does in their higher quoted "effective resolutions"(it ain't real resolution mind you but it can benefit certain image types).
If you know for an absolute fact you need more resolution than the native file has, you really might want to test upsampling in Camera Raw as it has a newly tuned upsample (put in in ACR 5.2) that is an adaptive Bicubic algorithm that is either the normal Bicubic or Bicubic Smoother depending on the size–and that's something even Photoshop can't do.
But in general unless you know for a fact you need the image bigger (or have a Fuji camera) processing at the file's native size is the most efficient.

Camera Raw 5.5 problem?

I upgraded to Lightroom 2.5 yesterday (9/20/09), which includes an upgrade to Adobe Camera Raw 5.5. I started to see a purple artifact appear in highlights after making edits. (I haven't yet investigated enough to identify which editing tool triggers the artifact, or perhaps all of them.) Even when I revert History to the original Import step the purple artifact remains visible on screen.
I'm working with ORF files from the Olympus E-510. ORF is Olympus' RAW format.
When I use the 'Edit in' command in LR to open the same file in Photoshop CS4 11.0.1, with or without LR edits, the highlights artifact remains. LR instructed me to upgrade ACR to 5.5 in Photoshop, for compatibility with LR 2.5, which I did before opening the first file. When I later opened the same ORF file straight from PS, it contained the highlights artifact.
When I saved a JPG from LR, the artifact remained in the JPG file. Opening the JPG in Apple's Preview shows that the artifact is at the pixel level - it is there without using an Adobe product to view the image. Therefore the bug is not restricted to viewing images, but also to processing and saving images.
To test whether the ORF (RAW) file had been altered by LR, I opened it in LightZone 3.8. The highlights artifact is NOT present in the image processed by LightZone. Therefore the Adobe products did not alter the ORF (RAW) file. Because the artifact is present in two Adobe products that depend on ACR 5.5, the bug is probably in ACR 5.5. Perhaps in the calibration for the E-510?
I suspect the bug in ACR 5.5 is caused by improper normalization of the R, G and B channels at the bright end of the histogram, so that color balance is not retained when one channel is blown.
Crops of the LR/ACR 5.5 JPG image and the LightZone JPG can be seen at:
http://flipperty.smugmug.com/Photography/Adobe-Camera-Raw-55-bug/9696232_S7gJS#655241795_R zjVS

The same problem, but with different camera model (Sony) has been reported on Lightroom forum Eric Chan (Camera Raw engineer) is looking into it. You can read more at:
http://forums.adobe.com/thread/492281?tstart=30

CS2- Adobe Updater won't start

I have Photoshop CS2 and have recently started to use it after a long hiatus. When I start it, I get a message that Adobe Updater would not start, and something (the updater?) should be reinstalled. CS2 seems to be working perfectly. What should I do, besides ignoring that message?
Also, can someone tell me what the latest version of the Adobe Raw Converter is which is compatible with CS2?

I'll be happy to answer your questions in the Camera Raw forum or the DNG forum, respectively.
http://forums.adobe.com/community/cameraraw
http://forums.adobe.com/community/dng#
For the list of which camera models are supported in each version of the Adobe Camera Raw plug-in, see:
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb407111&sliceId=2
bobgoldstein wrote:
My raw files come from an Olympus E-510 camera, and are you
suggesting that they might NOT be compatible with ACR 3.7?
Correct, they are NOT. You would need at least ACR 4.1, which does NOT run in CS2.
bobgoldstein wrote:
And that
converting them to DNG would allow further processing in CS2?
Correct again. Use the DNG Converter 5.3. It is a stand-alone application and you should always use the latest version.

Imported photos have error

in Lightroom 1.4 running on Mac OS X v10.5 importing from Olympus E-510,
Out of 113 photos imported, 2 photos have an error in that the whole photo is imported but these 2 photos also have the quarter-size version of the photo in upper left corner. I have deleted these photos and re-imported them and they have the same error. The camera shows the pictures correctly. They are 3648x2736 JPGs.

These 2 erroneous imports were taken a few minutes apart - but they were not adjacent photos - they were taken about 9 shots apart. They have the same resolution. There are numerous other photos taken at the same time that import correctly. All the images are in the 5-7 Mb range - these photos are not the biggest or smallest.
Experiment: I deleted (from library and disk) the 2 erroneous photos. I re-imported them by putting the compact flash card in an external reader (so Olympus E-510 is uninvolved with the import). They came in with the same error. I would note that the preview of the imported images briefly showed correctly and then when the import completely finished - the error showed up.
When I view the JPGs with Preview, the images look fine.
I cannot figure out *anything* about these 2 files that is different from all the others. I will retain the photos if you want copies.

Camera Calibration - Profiles. How To??

I'm very new to Lightroom. I'm using a trial version of 2.6 until I get my full paid version in the mail, hopefully in one or two days.
In the develop module on the CAMERA CALIBRATION tab I have no choices for profiles. The only one there is EMBEDDED. I'm using an Olympus E-510 and have imported ORF's into Lightroom. I've downloaded something called DNG Converter 5.6 and installed it but that obviously isn't what I need because nothing has changed. It appears to be a stand alone program for converting files. Can someone tell me how to get the different profiles into Lightroom? Like I said I'm very new to Lightroom so step by step instructions will be helpful.
Thank you,
lmb

The key to calibrating your camera is the color-target along with software to create the profile from the RAW image of the target shot in the lighting you are profiling for.
If you don't have an x-rite color-checker calibration target, already, or it is quite old, then I'd recommend the X-Rite Colorchecker Passport that Jao linked, already, as a nicely portable version of the target along with some software to create the profiles.
The calibration software, from either Adobe or X-Rite is actually free, so the big expense is the color-checker calibration target, itself, and while the CCPP is a little more than just a regular CC target, the pocket-size and hard-case make is easier to handle and take care of, as compared to the larger one that comes in a plastic bag and cardboard sleeve last I knew.
If you are only doing studio work where you can keep your CC in a controlled environment, then perhaps the larger CC target would be easier to image or a model to hold, but if you are going to be out and about with one, then the Passport is easier to work with.
The profiles can be for a single light source or a special dual-illuminant profile (like all of Adobe's are) that you create with one RAW of the target in incandescent lighting and one RAW of the target in 6500K lighting -- hazy sun, or D65 bulbs. This dual-illuminant profile generally works for lighting in between incandescent and shade by interpolating the profile for the color-temperature of lighting you are in. However, I have found that if the Tint value (the magenta/green balance) is too far off of zero, like it will be for fluorescent and mercury vapor and other such lighting, then you will want a special profile for that.
Even though Adobe has made profiles for my Canon DSLR, I use two of my own most of the time, for my ad hoc outdoor and indoor shooting. I have a dual-illuminant profile using an incandescent shot and a hazy-sunny shot that is close to 6500K, where both Tint values are near zero, and then I have one more profile that I've shoot in indoor fluorescent lighting where the Tint value is closer to +30 (extra purple to counteract the fluorescent greenish cast) and that takes care of almost everything I shoot.
The DNG Profile Editor (and the X-Rite software) only operates on DNG's that you've converted from your calibration-target RAWs, but the profiles you create are for any RAWs or DNGs from the camera, so you only have to worry about DNGs at the point you're creating a profile, not when you use it.
The DNG Profile Editor has the ability to tweak existing profiles as you'd do when photographing for a catalog where the color of the clothes must be as precise as possible, but other aspects can wander a bit, but for creating a profile out of CC-RAW shots, either the Adobe or the X-Rite software works just as well.
The X-Rite software had the ability to use shots that are not exactly 2650K and 6500K like the DNG Profile Editor requires, so in my mind that is better because I don't have access to standardized light workstations, and must take my shots in more natural lighting, so need the extra leeway of the X-Rite software.

Olympus e-510 presets

Similar Messages

Maybe you are looking for