Crem Posted December 23, 2023 Share #101 Â Posted December 23, 2023 Advertisement (gone after registration) On 12/22/2023 at 2:03 PM, mzbe said: The critical glitches we currently see are likely due to timing, concurrency, or overflow issues (or a combination thereof). Perhaps they 'lifted and shifted' code from the SL2 with different latency assumptions (different components) that should have been changed with the M11? Or added code in the wrong places e.g. for the 'triple res' nonsense ... Or the 60MP data volume, at identical data bandwidth, only works 'most of the time'? What would help: Leica should come clean about the fiasco. Their cryptic release notes don't do the job. I can imagine their lawyers do not permit transparency, but the current attitude is hurting Leica's most precious asset - the perceived integrity of the brand (... together with non-software production defects, wait time for repairs, ...). As a software engineer, my M11 experience has felt like Leica releases M11 firmware on management's schedule. I find it impossible to believe the testing team used v2 for weeks or months and somehow didn't run into random red frame lines and corrupt DNGs. It's way more likely that v2 didn't get much real world testing. I agree that Leica does a poor job of coming clean and communicating. I contacted support, reported bugs, and asked when they would get fixed. I got told that the engineers don't tell the support staff until the firmware is released. That's simply unacceptable. Engineers + support should be working close together on this. Leica really screws up by not permitting firmware downgrades. I think we are all fine with beta quality firmware so long as we can downgrade to the previous good version. Quote Link to post Share on other sites More sharing options...
Advertisement Posted December 23, 2023 Posted December 23, 2023 Hi Crem, Take a look here Occasional unreadable dng. I'm sure you'll find what you were looking for!
lct Posted December 24, 2023 Share #102  Posted December 24, 2023 (edited) • Edited December 24, 2023 by lct Quote Link to post Share on other sites More sharing options...
lct Posted December 24, 2023 Share #103 Â Posted December 24, 2023 (edited) 3 hours ago, UliWer said: I know we discussed this before and I am not looking forward to convince you. For me there is a fundamental contradiction if something is switched off and stays active at the same time so that it can detect a lens code to apply a certain code. The camera does not accept the main function "off" for lens detection. It may be interesting lo look in which context the word "freeze" was first used in connection to the M11. I may have overlooked an early posting but I think it is here: https://www.l-camera-forum.com/topic/329432-m11-will-freeze-when-lens-detection-off-bug/ And then it goes on: https://www.l-camera-forum.com/topic/329232-m11-bug-with-uncoded-lens/ https://www.l-camera-forum.com/topic/338594-lens-selector-off/ https://www.l-camera-forum.com/topic/331172-m11-does-not-detect-lens-intermittent-fault/ https://www.l-camera-forum.com/topic/375926-m11-auto-lens-detection-problems/#comments I don't know if i'm the right person to comment but i haven't had any problems with my M11 since firmware update 1.6.1 so far. I don't use lens detection off for my coded lenses mostly but it works perfectly with uncoded lenses when i don't want to apply a Leica lens profile to them. FWIW. Edited December 24, 2023 by lct Quote Link to post Share on other sites More sharing options...
hjddd Posted January 31, 2024 Share #104  Posted January 31, 2024 We have been waiting for enough time to wait for Leica to release new firmware。 Where is it？ 1 Quote Link to post Share on other sites More sharing options...
jaapv Posted January 31, 2024 Share #105 Â Posted January 31, 2024 In Wetzlar I assume... 1 Quote Link to post Share on other sites More sharing options...
Tailwagger Posted January 31, 2024 Share #106  Posted January 31, 2024 4 hours ago, hjddd said: We have been waiting for enough time to wait for Leica to release new firmware。 Where is it？ Have to agree. Just encountered my 7th corrupted file. Disappointing that this issue has yet to be addressed. All one can hope is that in getting to the bottom of this one, they've finally figured out where the internal collisions are happening, though given the delay, if so, one has to assume that the problem(s) are difficult to address. Either that or their doing far more testing this time around to avoid any further mud in the face.  1 Quote Link to post Share on other sites More sharing options...
Stevejack Posted February 9, 2024 Share #107  Posted February 9, 2024 Advertisement (gone after registration) Did anyone confirm if the corruption still exists when shooting to both internal + SD card (so files are mirrored across both)? The first DNG after turning the camera on is often corrupted for me, shooting to SD only. It's not consistent but it's often. I've switched to IN=SD which is mirroring the DNG files on both the internal storage and the SD card. I'm assuming this means the file is written to the internal drive first, then copied across to the SD card. Can anyone confirm if doing this has solved the problem for them? Quote Link to post Share on other sites More sharing options...
84bravo Posted February 9, 2024 Share #108 Â Posted February 9, 2024 On 12/23/2023 at 6:33 PM, Crem said: Leica really screws up by not permitting firmware downgrades. I don't disagree, but I don't think any manufacturer permits firmware downgrades. That's been my experience with Canon and Nikon. Quote Link to post Share on other sites More sharing options...
Stevejack Posted February 11, 2024 Share #109  Posted February 11, 2024 On 2/9/2024 at 2:55 PM, Stevejack said: Did anyone confirm if the corruption still exists when shooting to both internal + SD card (so files are mirrored across both)? The first DNG after turning the camera on is often corrupted for me, shooting to SD only. It's not consistent but it's often. I've switched to IN=SD which is mirroring the DNG files on both the internal storage and the SD card. I'm assuming this means the file is written to the internal drive first, then copied across to the SD card. Can anyone confirm if doing this has solved the problem for them? After some testing I can confirm that setting the storage to IN=SD has not solved the problem, the first file recorded to the SD card after switching the camera on is still occasionally corrupted. 1 Quote Link to post Share on other sites More sharing options...
mattcheol Posted February 11, 2024 Share #110  Posted February 11, 2024 2 hours ago, Stevejack said: After some testing I can confirm that setting the storage to IN=SD has not solved the problem, the first file recorded to the SD card after switching the camera on is still occasionally corrupted. Agreed. I have since actually sold off my M11 because things were so frustrating. But I can concur with this as I exclusively shot in IN=SD mode and also had the DNG corruption issue. 2 Quote Link to post Share on other sites More sharing options...
Stevejack Posted February 11, 2024 Share #111  Posted February 11, 2024 Just now, mattcheol said: Agreed. I have since actually sold off my M11 because things were so frustrating. But I can concur with this as I exclusively shot in IN=SD mode and also had the DNG corruption issue. It seems the only solution is to use the internal storage and transfer images via the M11 built in USB-C port. Crazy state of affairs that this is the situation we're in. I have an M11 still on firmware 1.2 which doesn't have the issue, but when I purchased the M11M it had the newest firmware already on it so I had no choice in the matter and obviously can't revert to an earlier firmware.   1 Quote Link to post Share on other sites More sharing options...
LeicaR10 Posted February 11, 2024 Share #112 Â Posted February 11, 2024 Mattcheol, Â +1. Â You are not alone. Â I traded my M11s to include the P and went back to the M10-R & M cameras. Â I simply had to make a choice, corrupt DNG files, magenta cast, firmware updates that create issues that were previously fixed or had no issues before. Â Others report no issues and I am happy for them. Â Personally, I could not take further risk with the M11s that simply did not work reliably for me. Â r/ Mark Quote Link to post Share on other sites More sharing options...
pop Posted February 11, 2024 Share #113 Â Posted February 11, 2024 5 hours ago, Stevejack said: obviously can't revert Have you tried? Quote Link to post Share on other sites More sharing options...
Stevejack Posted February 11, 2024 Share #114 Â Posted February 11, 2024 3 hours ago, pop said: Have you tried? Wait - you know a way for the end user to do this? How? I thought it wasn't possible because the camera will deny an older firmware version but if you have the solution I'm all ears. Quote Link to post Share on other sites More sharing options...
pop Posted February 11, 2024 Share #115 Â Posted February 11, 2024 1 hour ago, Stevejack said: Wait - you know a way for the end user to do this? How? I thought it wasn't possible because the camera will deny an older firmware version but if you have the solution I'm all ears. I don't have an M11, but I seem to remember that earlier models accepted quite easily older firmware versions. Hence my question whether you had tried to do so. The opposite would be that you didn't try because you simply assumed that it wasn't possible. Quote Link to post Share on other sites More sharing options...
Stevejack Posted February 11, 2024 Share #116  Posted February 11, 2024 10 minutes ago, pop said: I don't have an M11, but I seem to remember that earlier models accepted quite easily older firmware versions. Hence my question whether you had tried to do so. The opposite would be that you didn't try because you simply assumed that it wasn't possible. Ah, yes sorry I did try and when it didn’t work I went looking and read that it wasn’t possible. when you load an older firmware version onto the SD card the camera doesn’t recognise it so you can’t start the update process. The option to update is blanked out.  Quote Link to post Share on other sites More sharing options...
Edax Posted February 27, 2024 Share #117 Â Posted February 27, 2024 Â Quote Link to post Share on other sites More sharing options...
jaapv Posted February 27, 2024 Share #118  Posted February 27, 2024 The Internet is full of complaints about Windows corrupting SD cards. Frying pan into the fire comes to mind. Just as bad as Mac. The best remedy is to follow best practice by locking the card before inserting it into the reader. Quote Link to post Share on other sites More sharing options...
lct Posted February 27, 2024 Share #119 Â Posted February 27, 2024 (edited) 58 minutes ago, jaapv said: [...]The best remedy is to follow best practice by locking the card before inserting it into the reader. A practice i have never used in 20+ years but if it works for others i have nothing to say against it. Edit: Except that i don't see how backup memory can be done and user profiles exported to a card if it is locked, sorry if i sound negative this way. Edited February 27, 2024 by lct Quote Link to post Share on other sites More sharing options...
Edax Posted February 27, 2024 Share #120  Posted February 27, 2024 14 minutes ago, jaapv said: The Internet is full of complaints about Windows corrupting SD cards. Frying pan into the fire comes to mind. Just as bad as Mac. The best remedy is to follow best practice by locking the card before inserting it into the reader. Works fine until the lock breaks down, happened after only a few actuations with one of my Sandisk Extreme SD cards. I considered modifying a card reader especially for the M11  in such a way that every card seems locked.. Quote Link to post Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.