Jump to content

Recommended Posts

On 5/25/2024 at 6:31 PM, LocalHero1953 said:

I don't have a M11, so have no particular knowledge or experience other than having followed the M11 saga. In your place though, and reading those instructions, I would not have reinserted a card used under the previous firmware. I would have only have used a reformatted card.

But then I never leave and reuse cards with images on them - I download to my PC or laptop daily, and, after backing up (to give me two new copies of my images), format the card before reusing it. SD cards are cheap and convenient means of temporarily storing images after shooting, but I don't trust them for longer term storage than I absolutely have to.

Thanks, LocalHero1953!  I tried what you suggested and used an SD card which I freshly formatted in the M11 with the new firmware, and since then I didn't have any of the previous freezings any more -- after ca. 60 times of waking up the M11 from stand-by mode (i.e. the situation when it sometimes would freeze, typically after ca. 12-20 times of waking up from stand-by).  I still keep my fingers crossed, though:  Also in the past there haven been days during which I didn't experience any freeze as well (the freezing occured irregularly and sporadically), just to happen quite frequently on the next day.  But now I'm optimistic that by exclusively using SD cards freshly formatted in the M11 with the same firmware version my freezing problem might be gone for good.  Thank you!

Edited by ChrisFrick
typo
  • Like 1
Link to post
Share on other sites

For me, today at an event, I used three lenses (one Voigt) and collected around 1100 images on the M11, new firmware 2.1.1, continuous-high, prograde digital 128, no issues at all. No issues previously either, coming up on two years of ownership. 

  • Like 3
  • Thanks 1
Link to post
Share on other sites

On 5/24/2024 at 5:48 PM, jaapv said:

 It adds nothing but introduces the risk of the update failing catastrophically (like here) through a glitch in the WiFi connection.

I don't believe it does.  The update seems to occur in two steps:
1) transfer the file to the camera
2) camera updates from the transferred file

A wifi failure in step 1 will not cause any catastrophic error.  The "lost wifi" message is (IMHO) an error on the part of Leica.  It is telling you that the FOTOS can no longer connect to the camera.  It's an expected error in the update situation because of course the connection will be lost as the camera updates.  Leica does their customers a disservice by scaring them with this error message without explaining that it is normal.

Yeah, 5 minutes was probably not long enough to wait.    I don't know how long it took to update my M11 but is sure felt longer than 5 minutes.

  • Like 4
Link to post
Share on other sites

2 hours ago, dkmoore said:

Would be hilarious if the freeze issue just ends up being people expecting to hear the mechanical shutter but the camera switched to digital shutter. 

Most common “freeze” issue with all M Leicas is forgetting to remove the lens cap.

With electronic shutter you still can access menus, image reviews, so I doubt people would think it is a “freeze.”

  • Haha 2
Link to post
Share on other sites

Advertisement (gone after registration)

Well, casually/unofficially, I feel this firmware HAS addressed the magenta tint as a few others have commented. Prior, unedited RAW files showed a push of 20/21 in the Tint slider in Lightroom

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

In a few test shots this weekend, the push is reduced, on average, 3-5 ticks

 

Quite unscientific, as these are different shots, but both partly cloudy/sunny days with a lot of sky and clouds.

Why there is a push at all I'm unsure, unless this is all on the Lightroom side... 

Both were AWB

More to test...

 

 

Edited by thrang
  • Like 1
Link to post
Share on other sites

On 5/24/2024 at 3:02 PM, Al Brown said:


- You cannot test changes in white balance with AWB on and in jpg mode
- You cannot test for magenta cast AKA purple tint with AWB on and in jpg mode

 

Well, why? I mean, if AWB had errors (that are later fixed), why wouldn't you see the differences in your RAW image (As Shot). AWB does SOMETHING, no? So anything that does SOMETHING has code behind it, and that code can be changed via firmware.

Link to post
Share on other sites

7 hours ago, SrMi said:

Most common “freeze” issue with all M Leicas is forgetting to remove the lens cap.

With electronic shutter you still can access menus, image reviews, so I doubt people would think it is a “freeze.”

I know. Was just making a mediocre to bad joke. I have only experienced the freeze twice and was an earlier adopter of the M11 and M11m. It is real. 

Edited by dkmoore
Link to post
Share on other sites

9 minutes ago, Al Brown said:

It says AWB AND jpg, together.

It does not say AWB and/or jpg.

sorry this part of your original post was left out of my quote:

Quote

For all this you need to use fixed manual WB settings and DNG raws with proper software profiling and development

The post reads as though you could not ascertain differences in how AWB works by using something like Lightroom. Or even your eye. (don't mean to bold this line, but the editor is not letting me deemphasize it)

Not being argumentative, but not understanding what you are really saying. All I'm saying is if they changed how AWB works, you would be able to see it in your As Shot RAW files, else AWB is not doing anything at all

Link to post
Share on other sites

On 5/26/2024 at 8:40 AM, elmars said:

Leica has said in the update instructions: Various errors and causes of freezes have been fixed; Leica has not said that all causes of freezes have been eliminated. So we should not have exaggerated hopes, even if it would be justified to expect that freezes only occur very, very rarely and not shortly after the release of the update.

So there is still a lot for Leica to do.

I think this is quite a harsh parsing of the words of their note. It's not that common for a software release, from most companies, to declaratively state ALL things have been addressed, with absolutism (critical security fixes notwithstanding). For them to state what they did, I would think that they are confident they addressed the known/common reason(s) for the reported freezes. You don't KNOW that there is more to do here. Could be, but really, give it a chance.

Edited by thrang
Link to post
Share on other sites

vor 45 Minuten schrieb thrang:

I think this is quite a harsh parsing of the words of their note. It's not that common for a software release, from most companies, to declaratively state ALL things have been addressed, with absolutism (critical security fixes notwithstanding). For them to state what they did, I would think that they are confident they addressed the known/common reason(s) for the reported freezes. You don't KNOW that there is more to do here. Could be, but really, give it a chance.

I may not have expressed myself well enough because English is not my mother tongue. I just wanted to warn those who were expecting complete freedom from crashes not to have exaggerated hopes.

  • Like 3
Link to post
Share on other sites

38 minutes ago, elmars said:

I may not have expressed myself well enough because English is not my mother tongue. I just wanted to warn those who were expecting complete freedom from crashes not to have exaggerated hopes.

You expressed yourself just fine and understandable. I think you are correct in your assumption that there may be more to do.

  • Like 1
Link to post
Share on other sites

When we take the number of freezes reported before versionn2.1.1 during a week and compare to the actual FW 2.1.1 then see that we have less freezes reported during last seven days. That is probably good news even thow the number of freezes did not go back to zero.

  • Like 3
Link to post
Share on other sites

On 5/23/2024 at 8:46 AM, Photoworks said:

Updated from SD card. the camera still works LOL

initially, it was showing "IN" instead of "SD+IN", I had to take out SD and it was fine when I put it back in.

Thanks. That solved it too. Now SD+IN as I want it.

Link to post
Share on other sites

Just took the plunge and updated my 1.6.1 version M11M to 2.1.1.  I sat out the 2.0 update because of all the negative feedback but I'm hoping that Leica spent their time on this one and got it right.  I never had any issues with 1.6.1 other than a few overexposed frames.  

Edited by mediumformula
  • Like 2
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...