If this bug exist in both X-T5 and X-T50 I'm 100% sure it will occur on my X-H2 also.
Crap 😑
I will wait, untill Fujifilm (or Cosina) will release firmware with this bug fix.
It's rally shame, as this lens is exclusive for Fuji X mount - so it could attract more people to jump into Fuji X to have this very veristle lens, but You pay premium price for this CV 27/2 mainly for premium features, like full exif data recorded to file, superb build quality, fantastic rendering.
*edit*
Bug in exif data info from lens, where You pay among other premium features - for having aperture value recorded into file, is like.. "Made in China" behavior.
BeatX wrote:
If this bug exist in both X-T5 and X-T50 I'm 100% sure it will occur on my X-H2 also.
Crap 😑
I will wait, untill Fujifilm (or Cosina) will release firmware with this bug fix.
It's rally shame, as this lens is exclusive for Fuji X mount - so it could attract more people to jump into Fuji X to have this very veristle lens, but You pay premium price for this CV 27/2 mainly for premium features, like full exif data recorded to file, superb build quality, fantastic rendering.
*edit*
Bug in exif data info from lens, where You pay among other premium features - for having aperture value recorded into file, is like.. "Made in China" behavior. ...Show more →
Fuji made changes in the latest firmware for the "newer" cameras. I can confirm this issue does not occur on the X-T30 II, X-E4, or X-Pro3. It would be helpful to inform Fujifilm so they can address it in a future firmware update.
In any case, I’ve already notified Cosina about this. Hopefully, they can reach out to Fuji and collaborate on a solution.
I think the issue started to be reported after a firmware update Fujifilm released around May 2024 for their current latest cameras at the time. It never happens on older cameras that didn't receive that or newer firmware updates. My X-S10 is one of those unaffected cameras.
I don't think the lenses can have their firmware updated by users and Cosina hasn't ever released any user-installable firmware updates for their mirrorless lenses. I suppose they could update the firmware back at the factory but it would seem far easier for Fujifilm to do something to revert the problem.
Juha Kannisto wrote:
I think the issue started to be reported after a firmware update Fujifilm released around May 2024 for their current latest cameras at the time. It never happens on older cameras that didn't receive that or newer firmware updates. My X-S10 is one of those unaffected cameras.
I don't think the lenses can have their firmware updated by users and Cosina hasn't ever released any user-installable firmware updates for their mirrorless lenses. I suppose they could update the firmware back at the factory but it would seem far easier for Fujifilm to do something to revert the problem.
That’s right. I reached out to Cosina about this and also asked Stephen at Cameraquest to inform them. If you happen to be around Cosina representatives during the expo, it might be helpful to mention it to them as well.
Guys, I found a temporary solution for wrong aperture value data recorded to exif data from CV 27/2 lens.
This freeware software allows You to edit exif data just by click: https://www.colorpilot.com/exif.html
Even though this solution requires another step in editing, I think this lens is worth it
Anyways fingers crossed for Fuji so they will fix this bug in another firmware update..
BeatX wrote:
Guys, I found a temporary solution for wrong aperture value data recorded to exif data from CV 27/2 lens.
This freeware software allows You to edit exif data just by click: https://www.colorpilot.com/exif.html
Even though this solution requires another step in editing, I think this lens is worth it
Anyways fingers crossed for Fuji so they will fix this bug in another firmware update..
I think exiftool (https://exiftool.org/) would also allow batch processing of files, changing any particular EXIF data as per given parameters with suitable commands. When C1 Pro was slow to bring A7CII support, I did batch processing of my Sony RAW files to change camera model from A7CII to A7IV in EXIF, and it worked well. I'm not sure which specific fields would need to be changed in this case and don't have a suitable command at hand but I think it would probably be another suitable option.
Fred Miranda wrote:
That’s right. I reached out to Cosina about this and also asked Stephen at Cameraquest to inform them. If you happen to be around Cosina representatives during the expo, it might be helpful to mention it to them as well.
I was already back from CP+ after my 2nd round visit when I wrote my previous comment, and I didn't go back for 3rd round, so I didn't have a chance to talk to them about this topic this time...
I suspect they must have received some reports by now but maybe haven't reached any good conclusion.
Anyway, I also hope a future firmware update from Fujifilm would solve it...
I can confirm this issue also occurs with the X-T50 body and the CV 27/2 X-mount. Fujifilm made changes in their latest firmware that conflict with Cosina's previous lens firmware code.
For those using "Lens Tagger", it’s easy to change f/22 to f/2. Simply open Lens Tagger and add -FNumber=2 to the top field:
BeatX wrote:
Probably, they both don't care damn thing about photo nerds, so if lens is working - then, there is nothing wrong lol
The OEM can update whatever they want as long as they maintain full support for their own lenses.
As for Fujifilm making sure that they also cover third party lenses, it depends on the partnership, adherence to the design specs and possibility to fix without breaking something else.
If Cosina did not stick to the specs (assuming they have a full partnership with Fujifilm and have been granted the correct specs) and it can’t be fixed easily by Fujifilm, you are basically stuck, unless Cosina were to offer a call back for a firmware update. Likelihood of the latter is slim. So your main chance is for this to be a minor issue “within Fuji” specs that can be fixed by Fujifilm and that Fujifilm is willing to do. Again, probably also low chance, as it is a third party lens.
