wrong exposure time in Media Pro
Hello
the exposure time in media pro is not correct! When you use BULB Mediapro show you 1/-0 Sek in the metadata window. When you shoot with an 1/50 media pro show you 1/48 !?
Capture One and Bridge show the right exposure time.
Thanks for your help
Patrik
the exposure time in media pro is not correct! When you use BULB Mediapro show you 1/-0 Sek in the metadata window. When you shoot with an 1/50 media pro show you 1/48 !?
Capture One and Bridge show the right exposure time.
Thanks for your help
Patrik
0
-
To get the exact values you need to read out the EXIF data with a tool like EXIFtool, which just exports the original values.
In most applications odd values are rounded due to the fact that the number formats are easier to treat and using integers or bit values do need really less space in a database than double precision or values with higher precision.
All my cameras do usually not exposure fractions like 1/50 and do not use f/stop with precise numbers if I extract the values stored inside the picture file - it is just "representation" in the DAM.
Metadata allow a lot of value representation regarding speed and others:
Portion of data of my Leica M8
---- ExifIFD ----
ExposureTime: 1/60
ExposureProgram: Aperture-priority AE
ISO: 160
ExifVersion: 0220
CreateDate: 2013:01:29 14:24:02
ShutterSpeedValue: 1/64
ExposureCompensation: 0
MaxApertureValue: 2.8
MeteringMode: Center-weighted average
LightSource: Unknown
Flash: Auto, Did not fire
FocalLength: 28.0 mm
FileSource: Digital Camera
SceneType: Directly photographed
DigitalZoomRatio: 0
FocalLengthIn35mmFormat: 38 mm
SceneCaptureType: Standard
ImageUniqueID: 00000000000000000000000000003c43
---- Leica ----
UserProfile: User Profile 0 (Dynamic)
SerialNumber: 3196860
WhiteBalance: Auto or Manual
LensType: Elmarit-M 28mm f/2.8 ASPH.
ExternalSensorBrightnessValue: 3.44
MeasuredLV: 5.26
ApproximateFNumber: 3.0
CameraTemperature: 16 C
ColorTemperature: 0
UV-IRFilterCorrection: Active
CCDVersion: 0
CCDBoardVersion: 1
ControllerBoardVersion: 0
M16CVersion: 0
ImageIDNumber: 15427
---- Composite ----
CFAPattern: [Red,Green][Green,Blue]
ImageSize: 3920x2638
LensID: Elmarit-M 28mm f/2.8 ASPH.
ScaleFactor35efl: 1.4
ShutterSpeed: 1/60
CircleOfConfusion: 0.022 mm
FOV: 50.7 deg
FocalLength35efl: 28.0 mm (35 mm equivalent: 38.0 mm)
Portion of data from my Canon 5D Mkii
ExposureTime: 1/160
FNumber: 4.0
ExposureProgram: Aperture-priority AE
ISO: 100
ExifVersion: 0221
DateTimeOriginal: 2013:01:01 01:23:14
CreateDate: 2013:01:01 01:23:14
ComponentsConfiguration: Y, Cb, Cr, -
ShutterSpeedValue: 1/166
ApertureValue: 4.0
Flash: Off, Did not fire
FocalLength: 50.0 mm
---
---- Canon ----
---
CanonExposureMode: Aperture-priority AE
LensType: Voigtlander or Carl Zeiss Lens
MaxFocalLength: 50 mm
MinFocalLength: 50 mm
FocalUnits: 1/mm
MaxAperture: 1.4
MinAperture: 16
---
AutoISO: 100
BaseISO: 100
MeasuredEV: 13.38
TargetAperture: 4
TargetExposureTime: 1/161
ExposureCompensation: +2
---
MeasuredEV2: 10
BulbDuration: 0
---
---- Composite ----
Aperture: 4.0
DriveMode: Single-frame Shooting
FileNumber: 100-4817
ImageSize: 5616x3744
Lens: 50.0 mm
LensID: Carl Zeiss Distagon T* 18mm f/3.5 ZE + 2.8x
OriginalDecisionData: (Binary data 608 bytes, use -b option to extract)
PreviewImage: (Binary data 1714036 bytes, use -b option to extract)
ScaleFactor35efl: 1.0
ShootingMode: Aperture-priority AE
ShutterSpeed: 1/160
SubSecCreateDate: 2013:01:01 01:23:14.28
SubSecDateTimeOriginal: 2013:01:01 01:23:14.28
SubSecModifyDate: 2013:01:01 01:23:14.28
ThumbnailImage: (Binary data 14204 bytes, use -b option to extract)
WB_RGGBLevels: 2172 1180 1180 2340
BlueBalance: 1.983051
CircleOfConfusion: 0.031 mm
FOV: 40.5 deg
FocalLength35efl: 50.0 mm (35 mm equivalent: 48.8 mm)
HyperfocalDistance: 20.30 m
Lens35efl: 50.0 mm (35 mm equivalent: 48.8 mm)
LightValue: 11.3
RedBalance: 1.840678
So it might be just a flow, because someetimes you do not know which value is really used for displaying reasons.
Another funny thing is what the camera indicates about the used lens (marked blue)
Carl Zeiss Distagon T* 18mm f/3.5 ZE (+ 2.😎
but the lens I used was the
Carl Zeiss Planar T* 50mm f/1.4 ZE
so: 18*2.8 = 50,4 which seems to be correct - but 3,5/2.8 = 1,25 and not 1,4, which is the maximum aperture of the Planar.
I have not checked other camera/lens combinations, but you might see that, regarding EXIF data every camera and lens is different - even camera from the same manufacturer are not using a unique set of in-camera metadata.
Who in the world can build a consistent database out of such a mess of data!
My assumption is that POne uses POne camera related metadata , and due to the fact that these data are called standards, they are not mandatory in use, but the underlying JFIF/TIFF specification is not mandatory in naming, content and calculation but nothing more than "a hint to manufacturers".
So what you think looks like a bug, is just the indication, that the manufacturer of your camera uses different tags-names and entities as POne uses for their bodies.
If I have the time, I will do a check on some Nikons and I am expecting that even with 5 different bodies a lot of possibilities will occur.
saludos redondos -
tom0 -
I think the problem is, that Medio Pro read not the exposure time in the record. It does read the shutter speed. By bulp action is this every time zero. The actual record in media pro doesn't support Exposure Time in the media record 😭
Cheer Patrik
---- ExifIFD ----
Modify Date : 2013:02:28 00:48:09
Exposure Time : 8.6
F Number : 4.0
Exposure Program : Bulb
ISO : 1600
Exif Version : 0220
Date/Time Original : 2013:02:28 00:48:09
Create Date : 2013:02:28 00:48:09
Shutter Speed Value : 0
Aperture Value : 4.0
Exposure Compensation : 0
Subject Distance : 0 m
Metering Mode : Multi-segment
Flash : Off, Did not fire
Focal Length : 16.0 mm
User Comment :
Color Space : Uncalibrated
Exif Image Width : 5184
Exif Image Height : 3456
Focal Plane Resolution Unit : inches
File Source : Digital Camera
Scene Type : Directly photographed
Exposure Mode : Auto
White Balance : Manual0
Post ist für Kommentare geschlossen.
Kommentare
2 Kommentare