Hi all
I have done this in all Olympus bodies but have come across an oddity in regard to the OM-1.
For the M1X and previous bodies that metadata is seen by the likes of Fast Raw Viewer and DxO PL but these programs do not "see" these entries for the OM-1
Now, the question.......
Does your editing program and/or DAM of choice see these fields?
If so, have you updated to firmware 1.1 and following the update did you have to reset your date & time settings? Note ~ I had to reset my data & time settings after the firmware update.
I know of one OM-1 user on the DxO forum who says his metadata is showing and I have asked him the same question. I will ask elsewhere too to get some wider feedback as about what seems(?) to be an odd issue with the metadata inclusion setting in the OM-1?
TIA for your insights
Edit ~ well this odd.....I have just (re) reviewed [thought I had looked before at this folder?] at a few test images taken on the 18th June after updating the FW and the fields are showing in FRV.....but the ones taken on 22nd June those fields are not showing
! The one and only difference is that I had swapped the TC from the x2 to the x1.4
Neither the hardware change or other shooting settings, on the 22nd, changes there were nothing that (on the face of it) should or would affected the files to make any fields unreadable !
Edit 2
Right I have found the cause and I would call it a bug.
It appears to be associated with the use of either S-AF or C-AF, in S-AF the Metadata is seen however in C-AF the Metadata is missing.
I tried 3 different shooting settings i.e. Single Shot Silent, Sequence Shooting Silent & SH2 and this did not influence the expression of the issue.
I have emailed Mark Thackara to draw his attention to this bug and will also phone OMDS support on Monday to report it.
If anyone has the time to repeat the same empirical testing that I did to isolate the cause, please feel free to do so and post back here.
Oh, as mentioned above do say whether you had to reset the Date & Time after the firmware update....just in case that is germane to the potential cause of the oddity/bug?
I have done this in all Olympus bodies but have come across an oddity in regard to the OM-1.
For the M1X and previous bodies that metadata is seen by the likes of Fast Raw Viewer and DxO PL but these programs do not "see" these entries for the OM-1
Now, the question.......
Does your editing program and/or DAM of choice see these fields?
If so, have you updated to firmware 1.1 and following the update did you have to reset your date & time settings? Note ~ I had to reset my data & time settings after the firmware update.
I know of one OM-1 user on the DxO forum who says his metadata is showing and I have asked him the same question. I will ask elsewhere too to get some wider feedback as about what seems(?) to be an odd issue with the metadata inclusion setting in the OM-1?
TIA for your insights

Edit ~ well this odd.....I have just (re) reviewed [thought I had looked before at this folder?] at a few test images taken on the 18th June after updating the FW and the fields are showing in FRV.....but the ones taken on 22nd June those fields are not showing
! The one and only difference is that I had swapped the TC from the x2 to the x1.4Neither the hardware change or other shooting settings, on the 22nd, changes there were nothing that (on the face of it) should or would affected the files to make any fields unreadable !
Edit 2
Right I have found the cause and I would call it a bug.
It appears to be associated with the use of either S-AF or C-AF, in S-AF the Metadata is seen however in C-AF the Metadata is missing.
I tried 3 different shooting settings i.e. Single Shot Silent, Sequence Shooting Silent & SH2 and this did not influence the expression of the issue.
I have emailed Mark Thackara to draw his attention to this bug and will also phone OMDS support on Monday to report it.
If anyone has the time to repeat the same empirical testing that I did to isolate the cause, please feel free to do so and post back here.
Oh, as mentioned above do say whether you had to reset the Date & Time after the firmware update....just in case that is germane to the potential cause of the oddity/bug?
Comment