Jump to content

Problems with firmware 2.1.3


lexffm

Recommended Posts

Advertisement (gone after registration)

Tested it extensively for the first time today. I mostly use the fast burst mode for street photography. Today I set the shutter release to electronic and the problem from firmware 2.1.1 was there again. The camera doesn't stop taking pictures after you let go of the shutter release and basically makes a film of how you move. I took about 120 pictures and in the end there were 368 on the card. This happened to me 3 times in 2 hours. I noticed it on an M 11 Monochrom today.

  • Like 1
Link to post
Share on other sites

1 hour ago, lexffm said:

Tested it extensively for the first time today. I mostly use the fast burst mode for street photography. Today I set the shutter release to electronic and the problem from firmware 2.1.1 was there again. The camera doesn't stop taking pictures after you let go of the shutter release and basically makes a film of how you move. I took about 120 pictures and in the end there were 368 on the card. This happened to me 3 times in 2 hours. I noticed it on an M 11 Monochrom today.

Just tried to replicate your problem on my M11, to no avail (18 shots, 18 pic files). Did you notice the same issue in mechanical or hybrid mode?

Link to post
Share on other sites

1 hour ago, darlesch said:

That's concerning. Especially if in electronic mode when you can't hear the shutter going. I imagine it would go on forever if you had a large SD card!

The M11 series got a secret video mode that was officially eradicated in a few M models before! 😅🤣

  • Haha 8
Link to post
Share on other sites

Advertisement (gone after registration)

vor 3 Stunden schrieb lct:

Just tried to replicate your problem on my M11, to no avail (18 shots, 18 pic files). Did you notice the same issue in mechanical or hybrid mode?

I tested it again this afternoon. In hybrid mode it was not

  • Thanks 1
Link to post
Share on other sites

Am 12.10.2024 um 21:05 schrieb J S H:

I was seeing this issue as well with 2.12 on the M11. Resetting the camera and rebuilding the profiles eliminated the issue for me. 

Today I played back the saved profiles on both cameras (M11M + M 11-P).

Over the next 2 hours I no longer had the "endless loop error". What surprised me, however, is the following. I use the Visioflex2 on both cameras. On the M11M it was completely out of adjustment after loading the profiles, on the M 11-P it was still correctly set.

  • Like 1
Link to post
Share on other sites

Sorry, it's probably just an English-German thing, but I don't understand what you're trying to convey? Did you reset the camera and rebuild the profiles?

Are you saying that the diopter/focus adjustment changed on the Visoflex after moving it between cameras? That doesn't sound likely, unless you accidentally moved the adjustment knob while moving from one camera to another. 

  • Like 2
Link to post
Share on other sites

vor 1 Stunde schrieb J S H:

Sorry, it's probably just an English-German thing, but I don't understand what you're trying to convey? Did you reset the camera and rebuild the profiles?

Are you saying that the diopter/focus adjustment changed on the Visoflex after moving it between cameras? That doesn't sound likely, unless you accidentally moved the adjustment knob while moving from one camera to another. 

I didn't reset the camera, I "only" imported the profiles that I had saved before the update. I have two Visoflexes, one for each camera, so I don't have to change them. So there's no way of accidentally adjusting them. Apparently, setting up the Visioflex isn't a mechanical thing either, but is done via the software. That's why there's no marking or anything like that on the side.

Link to post
Share on other sites

vor 18 Stunden schrieb lct:

Importing the profiles is perhaps the culprit. I would try to modify them into the camera and see what happens.

I just created it again from the saved profiles because it was suggested from @J S H. The problem was already there.

Link to post
Share on other sites

26 minutes ago, lexffm said:

I just created it again from the saved profiles because it was suggested from @J S H. The problem was already there.

Unsure what you mean by created again. It is because the problem was already there, as you say, that i would modify the imported profiles. Happened to me with old "settings.lcse" files already. I would trash that file and create a new "settings.lcse" file with the camera but it's purely empirical.

Link to post
Share on other sites

9 hours ago, lexffm said:

I just created it again from the saved profiles because it was suggested from @J S H. The problem was already there.

I think @lct meant: Don't reuse old profiles at all. Recreate them from scratch. Sometimes this will resolve an odd glitch after a firmware update. 

  • Like 2
Link to post
Share on other sites

I had mine locking up a couple of times using a profile that was allocated to the Zeizz 35mm f/1.4, I use Zeiss lenses and I switched to manual lens coding since then. Never had any issues since then. If my memory serves right, it was the Zeiss 35mm f/1.4 ZM that caused the camera to get stuck a couple of times. 

Link to post
Share on other sites

4 minutes ago, TeeBee said:

If my memory serves right, it was the Zeiss 35mm f/1.4 ZM that caused the camera to get stuck a couple of times.

Difficult to understand why. Was your lens pen coded?

Link to post
Share on other sites

On 10/16/2024 at 12:29 PM, lct said:

Difficult to understand why. Was your lens pen coded?

Oops, I forgot to mention that. Yes, the lens was pen-coded, and I assigned it to a profile. The camera froze a couple of times with the Zeiss 35mm f/1.4 ZM Distagon, and then I did a factory reset and switched to manual coding. Removed pen-coding from all my lenses although I had my camera freezing with the 35mm Zeiss. It is worth noting that mine froze with the Zeiss 35mm f/1.4. 

Link to post
Share on other sites

OK and when you switched to manual coding, did you erase the coding pits you had painted previously? Not sure why you removed pen coding from your lenses BTW. If you did it well, your lenses should be recognized automatically. Did you use a template for pen coding? Just curious as pen coding works perfectly for me and i have several lenses coded this way. Last question, if you don't mind, which lens profile did you use for pen coding your ZM 35/1.4? Sorry for all those questions but i'm just trying to understand...

Link to post
Share on other sites

10 hours ago, lct said:

OK and when you switched to manual coding, did you erase the coding pits you had painted previously?

Yes, I did erase it. I used a template to code it, but I can't recall the value, I'm afraid. Although I owned the 35mm f/1.4 and the 50mm f/1.5 back then, I coded the 35mm 1.4, not the 50mm f/1.5. Then I bought the 21mm f/2.8 and coded that too. Following the lockup/freezing issue with the 35mm Zeiss, I removed coding from both lenses. I have bought several lenses since then and have been using manual coding. Never had any issues since then. I have attached a photo containing the lens profiles being used. The 50mm f/2 and 90mm f/2.8 are Voigtlander, and the rest is Zeiss.

 

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!

Link to post
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...