PDA

View Full Version : E600 vs. E620 RAW files


Tordan58
14th November 2011, 10:10 AM
Hi,

I have an issue when working with RAW files originating from the E600. The issue is a third party SW package (DXO Optics Pro 6) reporting "cannot be processed because image has no recognized color data"

E600 is not listed as supported body, however the SW is able to interpret the RAW files to quite some extent since thumbnails from the RAWs are generated and look OK. I have raised a support case and am awaiting an answer. I suppose DXO labs have no plans to extend support for a discontinued body but you never know...

My question to this knowledgeable community is - is there a way to patch the E600 RAW files so that they appear to originate from E620? In the RAW file you can find the text string E600, are there any other "magic numbers" or checksums that need to be updated as well?

Background: to my understanding the E600 is essentially the same camera as E620 and based on that I would have assumed they have the same sensor, same ISP and hence very similar RAW (I may be wrong, if that is the case then I guess it is a dead end).

/Tord

snaarman
14th November 2011, 10:28 AM
I had this problem when I started using the E600, but I updated the Adobe DNG converter and then it was OK. Maybe DXO can import DNG, so the Adobe free DNG converter might be a solution for you.

I seem to remember using a Hex editor to patch the "E600" text in the raw file to "E620" and I think that worked, but it's clearly a pain.. Otherwise the file formats are identical as far as I know.

Pete

MotoCroz
14th November 2011, 10:50 AM
Hi Just do a quick search for exiftoolgui It allows you to batch process your files, just change the E600 to e620. If you search on this forum there is information somewhere about it.
good luck

Tordan58
14th November 2011, 11:20 AM
Hi,

Thanks for replies. I modified one of the RAW files, changing from E600 to E620 (using a HEX editor) but still the SW is not able to process the image. There has to be some other information in the header that needs to be changed.

DXO supports DNG, however several features including the noise reduction are supported in RAW files only.

/Tord

meach
14th November 2011, 11:35 AM
Hi,

Thanks for replies. I modified one of the RAW files, changing from E600 to E620 (using a HEX editor) but still the SW is not able to process the image. There has to be some other information in the header that needs to be changed.

DXO supports DNG, however several features including the noise reduction are supported in RAW files only.

/Tord

I had this problem when I had an E600 and tried DXO. If I remember correctly DXO won't accept any file once the EXIF has been edited. I'm afraid I didn't manage to come up with a solution - but I have a vague recollection that someone on here did so a search may be in order.

Tordan58
14th November 2011, 11:57 AM
Hi,

Well DXO still "accepts" the file in the sense that it reads the contents and displays as thumbnail.

How can the SW draw conclusion that a file has been edited since its creation?


/Tord

meach
14th November 2011, 12:01 PM
How can the SW draw conclusion that a file has been edited since its creation?


/Tord

I don't know Tord - but I distinctly remember reading that somewhere and as the E600 wasn't supported I simply gave up using the trial version I'd downloaded.

Dave
14th November 2011, 02:24 PM
Although I have no experience with the DXO software my guess is that the thumbnail you can see is the embedded JPEG that the camera creates and so no processing has taken place. However if the software can read DNG then use that. DNG is still a Raw format and contains all the information that the ORF file contains but now in Adobe's standard format. Hope this helps.

Dave

DekHog
14th November 2011, 03:06 PM
You can try exiftool using my link in post 4 of the thread below. Am on the phone at the moment so can't check it, but think it's all set up and ready to go just by extracting the zip file somewhere...... Nothing ventured and all that....

e-group.uk.net/forum/showthread.php?t=8993

PeterBirder
14th November 2011, 09:12 PM
Hi Tord.
I have been trying to find a way to get DXO Optics Pro to accept E-600 files for ages and it's driven me mad.:mad:

I asked DXO and got no answer.:(

A member called MOLGRIPS who just made 8 posts in April/May said he had found a solution. In his last post said he was going to write a Utility to implement this and post it but since then he has disappeared.:rolleyes:
He found however that as well as changing E-600 to E-620 in the EXIF you need to change the code in the Maker Notes against "Camera Type 2" from S0030 to S0032. ExifTool does not allow you to edit this item, hence the need for a utility. As I have no software writing skills I'm stuck with this (to me) useless information.
It's a great shame as DXO Optics Pro gives me great results with my E510 files and I would love to be able to use it with my E-600

Regards

Tordan58
14th November 2011, 09:15 PM
Although I have no experience with the DXO software my guess is that the thumbnail you can see is the embedded JPEG that the camera creates and so no processing has taken place. However if the software can read DNG then use that. DNG is still a Raw format and contains all the information that the ORF file contains but now in Adobe's standard format. Hope this helps.

Dave
Dave,

Thanks for useful info regarding the embedded JPG.

The software does indeed support DNG but I have no tools for creating it.

/Tord

meach
14th November 2011, 10:08 PM
The software does indeed support DNG but I have no tools for creating it.

/Tord

The Adobe DNG convertor is a free download:

http://www.adobe.com/support/downloads/product.jsp?product=106&platform=Windows

meach
14th November 2011, 10:48 PM
Ok - I've managed to edit one of my old E-600 raw files as per Molgrips guidance. I'll download the DXO trial (if I can) and see if it will recognise it and report back. Unfortunately, writing a utility based on what I've done is beyond my capabilities but perhaps someone else here can take it a stage further if it works.

meach
14th November 2011, 11:14 PM
Ok - I've managed to edit one of my old E-600 raw files as per Molgrips guidance. I'll download the DXO trial (if I can) and see if it will recognise it and report back. Unfortunately, writing a utility based on what I've done is beyond my capabilities but perhaps someone else here can take it a stage further if it works.

Well that worked ok - now we just need to get it into some sort of utility/batch file. Any ideas anyone?

Tordan58
14th November 2011, 11:38 PM
Thanks all others who showed interest in this topic

It seems I managed to resolve the issue. In my first attempt editing the EXIF I did not realize in the first place that the editor I used introduced extra line breaks :o

What I did was to use a proper HEX editor, in this case I used the free editor XVI32 (http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm#download)

I searched for and substituted the string E-620 to E-600 (only one occurrence found, the '0' to become a '2' is at HEX address 9F7, same address for all files I converted), saved the file and reloaded in DXO. Et voila!

I did not substitute S0030 to S0032, I saw Pete's post first after having substituted camera body. In next run I applied this patch as well, both strings seem to equally well accepted, DXO does not complain and the output (JPG) can be opened.

Next will be to find a suitable hex editor that can be run in batch mode, or write such a piece of SW...

/Tord

Tordan58
15th November 2011, 08:46 AM
Hi Tord.
I have been trying to find a way to get DXO Optics Pro to accept E-600 files for ages and it's driven me mad.:mad:

I asked DXO and got no answer.:(


Regards
Hi,

I got a reply from DXO within next working day where they explained politely that they will not add a camera body if there is no business case (I fully understand that).

I provided the technical information back to them and asked them to reconsider their decision, or at a minimum to publish E600 support as an application note or "not officially supported feature". Let's see what they answer.

/Tord

PeterBirder
15th November 2011, 07:18 PM
Hi,

I got a reply from DXO within next working day where they explained politely that they will not add a camera body if there is no business case (I fully understand that).

I provided the technical information back to them and asked them to reconsider their decision, or at a minimum to publish E600 support as an application note or "not officially supported feature". Let's see what they answer.

/Tord

Glad you managed to at least get a reply from DXO Tord. I will be interested to hear their reaction to your suggestion.
Pleased to hear that you have managed to find a way to modify the files that works.

Many thanks.

Tordan58
16th November 2011, 09:03 AM
Hi Peter,

Actually I have an open support case regarding my issue and I get a level of attention on it that exceeds my expectations.

For good reasons DXO are hesitant in supporting a camera that has no sound business case, adding support for E-600 would require a new release of DXO SW since camera support is realized in the main SW and not in the add-on modules.

What worries me is that they seem not to be convinced that the E-600 is the same camera as E-620, the support engineer I am discussing with had a few valid points regarding this. Furthermore they said that Olympus "does not even admit to the existance of the E-600". Could it be that Olympus pushed the camera to the market and then changed their mind, as a consequence of withdrawing from the DSLR market except for the E5?

Anyway, I was offered to submit E600 ORFs samples (I suppose that DXO don't have access to any) so that their engineers could inspect them to see if what is really involved. If it ends up in E-600 support in a future SW release is another story...

/Tord

PeterBirder
16th November 2011, 07:14 PM
Hi Tord.
Thanks for that update,I'm pleased that you are able to at least discuss the problem with a DXO support engineer. If they are at least looking at our problem there is some possibility of a solution.

The E-600 seems to have been another of Olympus' strange marketing strategies but I guess we should be used to that now.:rolleyes:

Regards

Tordan58
17th November 2011, 09:54 AM
Peter,

If Olympus will not provide support for E600 I am considering writing a piece of SW that patches the ORFs in a batch.

/Tord

Tordan58
19th November 2011, 10:23 AM
Hi Peter (and other E-600 users for that matter)

I have written a step-by step description how to proceed to have E-600 ORF files manifest themselves as E-620 so that they can be processed by third-party SW e.d. DXO Optics Pro.

The description is available here (http://goto.glocalnet.net/tordan58-0/Four-thirds/How%20to%20have%20DXO%20accept%20Olympus%20E-600%20ORF.pdf).

Hope some of you will find it useful.


Hi Tord.
Thanks for that update,I'm pleased that you are able to at least discuss the problem with a DXO support engineer. If they are at least looking at our problem there is some possibility of a solution.



I have had a very constructive dialog with DXO technical support and have managed to convince them that E-600 and E-620 are essentially one and same camera and they will file a Feature Request to the engineering team, meaning there is at least a chance we will see E-600 supported in an upcoming release.


A member called MOLGRIPS who just made 8 posts in April/May said he had found a solution. In his last post said he was going to write a Utility to implement this and post it but since then he has disappeared.
He found however that as well as changing E-600 to E-620 in the EXIF you need to change the code in the Maker Notes against "Camera Type 2" from S0030 to S0032.

On this subject I would like to deny this is needed, nor fully true. ORFs created with my E-620 have a different "Camera Type 2" value than S0032.

When patching the files I changed one character only (E-600 to become E-620) and did not bother about the "Camera Type 2"



/Tord

Tordan58
21st November 2011, 11:22 AM
Hi,

This is the latest on this topic.

DxO's Imaging Team has agreed to take a serious look at the E-600/E-620 equivalence. If this checks out to their satisfaction, then a version of DxO Optics Pro with explicit E-600 support will likely be released. Best timing estimate is "during 2012".

Regardless of the outcome, I must say that the level of support and interest for my case exceeds my expectations.

/Tord

PeterBirder
21st November 2011, 08:08 PM
Hi Tord.
Thanks very much for your last two posts.*super*super

Due to your hard work and willingness to share the results I can now at last process my E-600 files in DXO Optics pro and there seems to be a reasonable chance that DXO will upgrade the program.

You are a gentleman sir.
Many thanks.*chr

Lord Minty
21st November 2011, 09:22 PM
Just for the record, I use ExifToolGUI to edit my E-600 ORF files and it works a treat.
I just change E-600 to E-620 and my old copy of Adobe Photoshop Elements 7 will then open them fine.

I'd certainly be interested in some sort of batch solution if anyone manages it but I would have thought ExifTool (the CLI version without the GUI) would be a good starting point.

High jacking the thread slightly, has anyone found a way to fudge the Exif data to impersonate a similar spec PEN model or even another E-series model? It'd be nice to be able to access the extra PEN Art Filters or even the E-5 filters in Olympus Viewer 2. I did have a play around earlier in the year, including changing the Camera Type 2 field but didn't get anywhere... perhaps I need someone to send me some PEN/E-5 ORFs so I can compare them to the E-600s?

meach
21st November 2011, 09:36 PM
Just for the record, I use ExifToolGUI to edit my E-600 ORF files and it works a treat.
I just change E-600 to E-620 and my old copy of Adobe Photoshop Elements 7 will then open them fine.

I'd certainly be interested in some sort of batch solution if anyone manages it but I would have thought ExifTool (the CLI version without the GUI) would be a good starting point.



You can do it in batch mode in ExifToolGui - just highlight all the files you want to edit, then change the camera to E-620 and it'll change all of them. I did this with my E-600 files and it worked fine for Elements - but not DXO

MotoCroz
21st November 2011, 09:38 PM
I too use exiftoolgui and was about to add the comments above..

Lord Minty
21st November 2011, 10:01 PM
You can do it in batch mode in ExifToolGui - just highlight all the files you want to edit, then change the camera to E-620 and it'll change all of them. I did this with my E-600 files and it worked fine for Elements - but not DXO

Ah right, I'll have to remember that. Generally I seem to just do one file at a time anyway as I'm usually a SOOC photographer.
I've got a copy of DXO Optics (v5 or v5.5 I think) and Film Pack sitting in a box unused - I've not installed them as they use Pace Interlok/iLok which is to say the least a dubious (http://www.8x10gallery.com/Wordpress/index.php/2007/02/07/dxo-and-pace-anti-piracy-scandal/) piece of software.

Lord Minty
26th December 2011, 08:37 PM
Well I've finally given in and installed DXO Optics Pro 5 and Film Pack v1 on my old Windows XP laptop.

I've taken a sample .ORF RAW from my E-600 and if I just change the model name in ExifToolGUI to E-620 then DXO says the image has "no recognized color data", and the same happens even if I change the MakerNotes CameraType2 from S0030 to S0032.

So I tried Tordan58's technique on a fresh copy of the file, using the Hex editor and I still get the same error... I'm confused! :confused:

I think I'm goign to have to do a bit more playing :(

Lord Minty
26th December 2011, 08:58 PM
Well I've finally given in and installed DXO Optics Pro 5 and Film Pack v1 on my old Windows XP laptop.

I've taken a sample .ORF RAW from my E-600 and if I just change the model name in ExifToolGUI to E-620 then DXO says the image has "no recognized color data", and the same happens even if I change the MakerNotes CameraType2 from S0030 to S0032.

So I tried Tordan58's technique on a fresh copy of the file, using the Hex editor and I still get the same error... I'm confused! :confused:

I think I'm goign to have to do a bit more playing :(

PeterBirder
26th December 2011, 09:25 PM
So I tried Tordan58's technique on a fresh copy of the file, using the Hex editor and I still get the same error... I'm confused! :confused: :(

I suspect Optics Pro 5 will not support any of the later Oly cameras. Dxo have recently issued Optics Pro 7 and Tord's technique works fine for me for both 6 and 7. Dxo currently have a free download trial of a fully functional Optics Pro 7 which will work for a month.

Regards.

chris
26th December 2011, 09:39 PM
to be honest this thread is mostly gobbledegook to me..... however, I've just been given elements10 for Christmas and would like to get into the raw side of things (never bothered previously). Am I going to need to mess around converting files to appear as E620's or will elements10 be good to go with my E600?

thanks
Chris

PeterBirder
27th December 2011, 10:46 AM
to be honest this thread is mostly gobbledegook to me..... however, I've just been given elements10 for Christmas and would like to get into the raw side of things (never bothered previously). Am I going to need to mess around converting files to appear as E620's or will elements10 be good to go with my E600?

thanks
Chris

Hi Chris
No need to worry, this thread relates to Dxo Optics Pro only which is very picky as to which raw files it will accept. You should be fine with elements 10.

Regards

Lord Minty
27th December 2011, 09:42 PM
I suspect Optics Pro 5 will not support any of the later Oly cameras. Dxo have recently issued Optics Pro 7 and Tord's technique works fine for me for both 6 and 7. Dxo currently have a free download trial of a fully functional Optics Pro 7 which will work for a month.

Regards.

That's not the problem - Optics Pro 5 *does* (or should!) support the E-620 out of the box, it was one of the models I could choose to add when I installed it.
I've just tried again tonight and it's exactly the same despite it clearly recognising the file as from an E-620 and the lens as the 35mm f3.5 macro.

I'll keep fiddling...

Tordan58
27th December 2011, 10:44 PM
That's not the problem - Optics Pro 5 *does* (or should!) support the E-620 out of the box, it was one of the models I could choose to add when I installed it.
I've just tried again tonight and it's exactly the same despite it clearly recognising the file as from an E-620 and the lens as the 35mm f3.5 macro.

I'll keep fiddling...

Hi,

I have written a step-by-step guide how to have DXO (version 6) accept E-600 ORF files, making them appear as originating from E-620.

You can find it here (http://goto.glocalnet.net/tordan58-0/Four-thirds/How_to_have_DXO_accept_Olympus_E-600_ORF.pdf)

HTH
/Tord