Jump to content

Recommended Posts

Advertisement (gone after registration)

1 hour ago, Smogg said:

I came across this bug today: I shot about 30 frames, pulled out the card and imported the frames to the Mac. Everything went perfectly. I inserted the card back into the camera. But before the next walk, I decided to look at the footage that remained on the memory card. All frames were available for viewing, but when flipping from the last frame to the first, I received the message “File unreadable”. The next swipe led to the first frame and so on in a circle. After the last frame this message always popped up. I'm guessing this is a consequence of the Mac creating service files on the memory card. However, this means that Leica still works with memory cards incorrectly and only in its own way. FORMAT the card after importing it into the Mac, as it is difficult to predict what the consequences of using a non-empty memory card will be for the second and subsequent sessions if you inserted the memory card into the Mac between sessions.

It's clear that Leica still has some work to do to make the M11 flawless

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!

 

I can reproduce this "File unreadable" by simply opening a .DNG file directly from the SD card (e.g.  a file from the DCIM/100LEICA folder on it) by a program like PTGUI. This program writes a hidden "._L100xxxx.DNG" back to the card. The M11 sees this as a picture file, but cannot read it. All what Leica has to do is ignore these files starting with "._". I will write a bug report to them.

So with the affected card inserted in your Mac, in Terminal type "ls -al /Volumes/"LEICA M"/DCIM/100LEICA" and let me know what you see...

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

x

When I travel, I import some of my photos to my iPad using an SD adapter so I can edit and send some photos without waiting until the end of the trip. Does iPad create hidden files too? Is it possible to continue shooting with this memory card while traveling without formatting it? Or will I have to put it aside, avoiding repeated sessions, in order to import it to my computer after the end of the trip?

Link to post
Share on other sites

@Kwesi: I don't *think the slider is glitchy. The card is a SanDisk from a reputable source (by which I mean, not counterfeit).

What got me wondering was the thought whether something gets written to the card that made SD Card Formatter interpret the card as Write Protected, an attribute of some kind or something, apart from the slider position.

It'd be hell to factor in/out all the variables that come with different OS versions, etc. 

I'm happy to see this fear squelched immediately and with dispatch!

  • Thanks 1
Link to post
Share on other sites

2 minutes ago, Smogg said:

When I travel, I import some of my photos to my iPad using an SD adapter so I can edit and send some photos without waiting until the end of the trip. Does iPad create hidden files too? Is it possible to continue shooting with this memory card while traveling without formatting it? Or will I have to put it aside, avoiding repeated sessions, in order to import it to my computer after the end of the trip?

IMHO you can continue shooting on it, but do not try to delete the "File unreadable" entry in the Play menu on camera. That will create problems.

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

7 minutes ago, Smogg said:

Question: what should I do after inserting the card into the Mac? Is it necessary to format? There is no chance to continue shooting with this memory card? 

Unsure if this answers your question but i always format my cards with SD card Formatter.

Link to post
Share on other sites

9 minutes ago, Edax said:

 

I can reproduce this "File unreadable" by simply opening a .DNG file directly from the SD card (e.g.  a file from the DCIM/100LEICA folder on it) by a program like PTGUI. This program writes a hidden "._L100xxxx.DNG" back to the card. The M11 sees this as a picture file, but cannot read it. All what Leica has to do is ignore these files starting with "._". I will write a bug report to them.

So with the affected card inserted in your Mac, in Terminal type "ls -al /Volumes/"LEICA M"/DCIM/100LEICA" and let me know what you see...

 

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!

  • Like 2
Link to post
Share on other sites

5 minutes ago, Edax said:

And there it is, the first file ._11B05683.DNG! The camera cannot display this so-called extended attribute file... 

I realised where this file came from, which begins with the symbol _. If you view any .dng file using Preview on a Mac, it creates one for each file you view.

So don’t use Preview!!!!

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

2 more files because I used Preview

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

Just now, Smogg said:

2 more files because I used Preview

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!

Yes same here with Preview too. My guess is that FW2.1.1 is btw resistant against deleting these files in camera, just to be sure don't do it yet being on the road...

  • Like 1
Link to post
Share on other sites

Very very interesting!

You can also see the OS has added a "@" to the left side of the row of each of the files that was previewed:

"-rwx------@"

R, W, and X - are these file attributes? Read, Write, etc?

Does Windows do something similar?

Edited by DadDadDaddyo
Link to post
Share on other sites

8 minutes ago, Smogg said:

I realised where this file came from, which begins with the symbol _. If you view any .dng file using Preview on a Mac, it creates one for each file you view.

So don’t use Preview!!!!

Best practice IMHO is to never open a .DNG file directly from the SD card... Copy them first to another location.

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

3 minutes ago, DadDadDaddyo said:

Very very interesting!

You can also see the OS has added a "@" to the left side of the row of each of the files that was previewed:

"-rwx------@"

R, W, and X - are these file attributes? Read, Write, etc?

 

Please don’t dig further, otherwise another bug has been found that will be worse than the first😂

Link to post
Share on other sites

It seems to me that this bug is forgivable for the authors of the firmware. It is rare, difficult to come across and easy to avoid in the future. @Edax is absolutely right, you can't do anything with dng files on card before copying them to another location

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

1 hour ago, DadDadDaddyo said:

Now that's interesting. This very afternoon,  I used SD Card Formatter to do a fresh overwrite format of the card that I filled up in my M11 with the pictures of the construction work we're having done. 

SD Card Formatter complained when I hit, "Go" at first, saying that my card was write protected. Huh?

I pulled the card out, double checked the position of the Write Lock slider by clicking it once to Write Protect, and then once again, back again to Writable. 

After that, it formatted as normal. 

Why did SD Card Formatter say my card was Write Protected when the slider was already set to Writable?

Now that I think of it, it's done this before...

What kind of internal OS utility files do Windows, Mac, and Linux write to a Card when reading it?

 

The built-in SD card reader in my 12 year old MacBook does this a lot - sometimes I have to re-insert an SD card several times before write permissions are enabled (as revealed by using "Command-I" or "Control-Get Info" in the Finder.)  Maybe your card wasn't inserted quite correctly in your reader the time you had the problem.  (At some point I ruled out the protection switch on the card as the cause of my problems.)

- Tim

  • Like 1
Link to post
Share on other sites

6 minutes ago, Ecar said:

No freezes or corrupted images as of today, but a couple of upside down images on import. Never encountered this previously.

In this way, those files are highlighted that saved them from damage that threatened them in the previous firmware version😀

  • Haha 1
Link to post
Share on other sites

Am 2.6.2024 um 21:46 schrieb Patech:

Solved for me (knock on wood). Would previously have freezes every session, even after 2 trips to Leica NJ. Happy camper now. 

How/where are you storing the images: on the internal memory or an the SD. Which memory is used as a priority?

Link to post
Share on other sites

vor 19 Stunden schrieb DadDadDaddyo:

Very very interesting!

You can also see the OS has added a "@" to the left side of the row of each of the files that was previewed:

"-rwx------@"

R, W, and X - are these file attributes? Read, Write, etc?

Does Windows do something similar?

Those are POSIX file permissions used on UNIX derivates. You pointed out correctly read and write, x stands for execute. The first dash would be a d in case of a directory. After that rwx corresponds to the owner of the file, next three would be permissions for the group of the owner and the three afterward for everyone else. In this case, the file is readable, writable and executable by th e owner only and nobody else. The @ at the end corresponds to extended file attributes, very often used for ACLs.

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...