Micro 4/3 Advice wanted: Olympus OM-D E-M5 III resetting its frame counter at random intervals ...

[MoonMind]

If someone had a) an explanation, i.e. could tell me what to avoid, or b) a solution, i.e. a way to finally stop this, I'd be much obliged.

It's a major annoyance - to the point of me wanting to hurl the camera at the wall (I won't, but it *does* wreak havoc with cataloguing the images).

M.

 

[RAH]

Do you mean that it resets its filenames or do you mean its shutter activations (or something else that I cannot figure)?
Edit:
OK, I'm realizing that frame counter is probably a video thing (I never do video). But I'm wondering if your seemingly random resets is related to a kind-of similar problem I had with filenaming. It involves the use of Custom modes. Here is what I posted on the other m43 forum:

I think that using Custom Modes was in fact the problem. Basically, what seems to happen is: say you have your camera set to use standard filenames. Then you set Custom Mode 1 to do say HHHR. So you start getting regular filenames on your HHHR shots. You then later set your camera to use special filenaming, say beginning with OM (as I did). Well, that apparently does NOT ripple thru and change the settings stored for Custom Mode 1 (for HHHR in this example). So when you use C-mode-1 you revert to the standard names. When you turn the dial to regular shooting, you are back to getting the special naming.

In that case I was getting what looked like random filenames, some starting with "OM" when I was in regular mode, and some starting with the default naming whenever I switched to Custom Mode 1. It can appear to be totally random, for sure.

Maybe this is what is happening with your frame counter? Custom Modes retain EVERYTHING, it seems, so if you make some important camera-wide setting (like how it assigns filenames), you need to reestablish (redo) all your Custom Modes or you will revert to whatever was set earlier every time you use one.

This might not account for your problem, of course, but it sounds like it might.

 

[MoonMind]

Thanks for the reply. My custom file name contains a "fixed" part and a counter; the counter should count from 0001 to 9999, the custom part ist something along the lines of "EM53". The second four digits reset themselves at random intervals and start again at 0001. Depending on when I realise this, I tend to overwrite existing files with the same name - it's a real nuisance.

I don't know why and how it happens. It's really irritating.

M.

 

[gryphon1911]

I believe there is an option in the file naming menu that you can have the file name counter be continuous until it hits the max number, then resets to 0000, or you can have it reset back. Can't remember the criteria on when it would do that, could be during file delete or formatting.

 

[DeeJayK]

I believe there is an option in the file naming menu that you can have the file name counter be continuous until it hits the max number, then resets to 0000, or you can have it reset back. Can't remember the criteria on when it would do that, could be during file delete or formatting.

This seems like a good possibility, although I also suspect you've already looked at this setting, Matt.

The setting lives in [MENU] / <Gear> / H1. For your desired functionality, you'll want it set to "Auto" rather than "Reset".

- K

 

[RAH]

I believe there is an option in the file naming menu that you can have the file name counter be continuous until it hits the max number, then resets to 0000, or you can have it reset back. Can't remember the criteria on when it would do that, could be during file delete or formatting.

This seems like a good possibility, although I also suspect you've already looked at this setting, Matt.

The setting lives in [MENU] / <Gear> / H1. For your desired functionality, you'll want it set to "Auto" rather than "Reset".

- K

Yes, this is the setting that controls this, but I kind of assumed he already knows about this. However, @MoonMind , this resetting problem sounds almost exactly what happened to me with the filenaming change combined with using Custom modes that were established earlier. Are you using any Custom modes while encountering this reset problem? If so, I recommend you use each one (set the camera to each one) and go into the menu and check the setting of that "auto"/"reset" option for the counter. You may find that one of the C modes has "reset". Worth a look.

 

[DeeJayK]

Yes, this is the setting that controls this, but I kind of assumed he already knows about this. However, @MoonMind , this resetting problem sounds almost exactly what happened to me with the filenaming change combined with using Custom modes that were established earlier. Are you using any Custom modes while encountering this reset problem? If so, I recommend you use each one (set the camera to each one) and go into the menu and check the setting of that "auto"/"reset" option for the counter. You may find that one of the C modes has "reset". Worth a look.

I also presume that Matt was well aware of this setting from his description, but I've learned that when troubleshooting odd problems it pays to make no assumptions and start with the most basic possible explanation first and only move on to others once that one has been ruled out.

It sounds like you may be on the right track with your explanation, but I've wasted countless hours in my career when someone failed to rule out the most basic possibility before diving into the more complex one.

- K

 

[MoonMind]

I also presume that Matt was well aware of this setting from his description, but I've learned that when troubleshooting odd problems it pays to make no assumptions and start with the most basic possible explanation first and only move on to others once that one has been ruled out.

It sounds like you may be on the right track with your explanation, but I've wasted countless hours in my career when someone failed to rule out the most basic possibility before diving into the more complex one.

- K

Thanks, everyone, for your thoughts and insights so far. I wouldn't find the whole thing so upsetting if I *hadn't* set up things the way they ought to be, though. I've been there, done that as far as menu settings are concerned. That's why I called the incidents "random". They're completely counter-intuitive in the light of how the camera appears to be set up. And I tried with different cards, with formatting or deleting, different procedures ... I so far was completely unable to cause this on purpose (apart from of course "resetting" the numbering - but I'm loathe to do this again at this point).

I guess, irritating though it is, that I'll have to put up with it and watch my file names/numbers like a hawk in order to prevent further losses. *Not* a good thing ... but just about manageable.

Makes me wonder if this only happens on my body - in this case, I might want to have it checked by Olympus/OM System. Or maybe not - it may cost an arm and a leg here in Switzerland if they decide it's not their fault ... I might as well swap the body for an OM-5 ...

M.

 

[drd1135]

It's a major annoyance - to the point of me wanting to hurl the camera at the wall (I won't, but it *does* wreak havoc with cataloguing the images).

M.

I’ve considered buying an inoperable ugly-grade old camera from KEH just to throw at the wall in anger. I think of it as an emotional back-up body.

 

[MoonMind]

I’ve considered buying an inoperable ugly-grade old camera from KEH just to throw at the wall in anger. I think of it as an emotional back-up body.

Sometimes, being protective of one's gear is really quite irritating in and of itself. The idea appeals greatly. If I think of cameras with enough annoying properties to qualify, I pick ... let's not go there, or this'll end in one wild row

M.

 

[John King]

Sometimes, being protective of one's gear is really quite irritating in and of itself. The idea appeals greatly. If I think of cameras with enough annoying properties to qualify, I pick ... let's not go there, or this'll end in one wild row

M.

It's always worth remembering the concept of 'reasonableness' in law, IMO.

In over 60 years, I've never broken a camera or lens by mishandling them.
That having been said, I look after my gear, without particularly mollycoddling it. I treat it with the care and respect that delicate and finely made things deserve.

 

[John King]

Thanks, everyone, for your thoughts and insights so far. I wouldn't find the whole thing so upsetting if I *hadn't* set up things the way they ought to be, though. I've been there, done that as far as menu settings are concerned. That's why I called the incidents "random". They're completely counter-intuitive in the light of how the camera appears to be set up. And I tried with different cards, with formatting or deleting, different procedures ... I so far was completely unable to cause this on purpose (apart from of course "resetting" the numbering - but I'm loathe to do this again at this point).

I guess, irritating though it is, that I'll have to put up with it and watch my file names/numbers like a hawk in order to prevent further losses. *Not* a good thing ... but just about manageable.

Makes me wonder if this only happens on my body - in this case, I might want to have it checked by Olympus/OM System. Or maybe not - it may cost an arm and a leg here in Switzerland if they decide it's not their fault ... I might as well swap the body for an OM-5 ...

M.

A quick way to reset numbering in Olympus cameras if it gets screwed up.

1. Copy an original image with your last correct file number onto a blank card, in the normal image folder/directory for your camera.
2. Ensure camera numbering mode is set to AUTO.
3. Insert card into camera.
4. Take one photo (of the floor, or anything inconsequential).
5. Remove card and either format it or erase it, depending on your normal practice.
6. Camera should now be reset at the next consecutive file number.

This method can also be used to set the next number to anything you like, thereby allowing you to create file number 'space' to fix an indeterminate number of incorrectly numbered files. Just renumber the copied file to whatever number fixes your problem.

This has happened to me, a couple of times.
Worked out the fix above after the first time.

HTH.

 

[RAH]

Rob Trek has an interesting video on using button assignments for C Modes on the OM-1:

It kind of clarifies how these button assignments work while the dial is in normal PASM modes and when the dial is in a C-mode. Even on the OM-1, you cannot use a C-mode BUTTON to go to a different C-mode. So, for example, if you turn the dial to say C1, you CANNOT then use any assigned BUTTON to get to another C-mode (C2-C4). You MUST use the dial.

This essentially is what I was running into when I tried to use a button assignment on the OM-5 while the mode dial was in the C mode position. The camera ignored the button push, but it turns out it does on the OM-1 too.

The video does show how you can, while in PASM, jump directly from one C-mode to another without first toggling out of the button's C-mode. In other words, jump from button1's C-mode DIRECTLY to button2's C-mode, without going back and forth to normal (toggling out) between them. How he does it is kind of instructive (if you don't mind getting your mind blown) about how button assignments work within the C-modes themselves. In other words, it is a variation of the filenaming problem I ran into - a C-mode will retain earlier settings unless you reprogram it, even for button assignments that are assigned to C-modes. Yikes! (but it does make sense).

Too bad we haven't started a separate thread on button assignments, huh!

 

[MoonMind]

Too bad we haven't started a separate thread on button assignments, huh!

Feel free to start one! In fact, I'll help move relevant posts - not because I think they're misplaced here, but because I think it'd be a good thing to have!

M.

 

[RAH]

Feel free to start one! In fact, I'll help move relevant posts - not because I think they're misplaced here, but because I think it'd be a good thing to have!

M.

I'd forgotten you are a moderator. Cool! I have set up a new thread:

Micro 4/3 - button assignments with oly and OMDS cameras

I am setting up this thread to address how to use button assignments, especially on the newest OMDS cameras, and also especially how they relate to C-mode settings.

cameraderie.org

I wasn't sure whether it should be titled "C-Modes" or "button assignments", but I guess button assignments is good. I think that only one of my posts above is completely independent and appropriate for it - the one above that cites Rob Trek's video and what I said about it. If you feel other posts (by me or anyone else) are appropriate too, that's fine, of course. Thanks for the offer!

 

[MoonMind]

I'd forgotten you are a moderator. Cool! I have set up a new thread:

Micro 4/3 - button assignments with oly and OMDS cameras

I am setting up this thread to address how to use button assignments, especially on the newest OMDS cameras, and also especially how they relate to C-mode settings.

cameraderie.org

I wasn't sure whether it should be titled "C-Modes" or "button assignments", but I guess button assignments is good. I think that only one of my posts above is completely independent and appropriate for it - the one above that cites Rob Trek's video and what I said about it. If you feel other posts (by me or anyone else) are appropriate too, that's fine, of course. Thanks for the offer!

I didn't move the post, but copied it to the new thread; I guess it'd be a good thing to kind of merge your two posts in order to clean things up and remove unnecessary pointers. Just edit the first post in your thread accordingly and delete the second post (the Rob Trek post is older, so appears as new first post in your thread).

M.

 

[MoonMind]

A quick way to reset numbering in Olympus cameras if it gets screwed up.

1. Copy an original image with your last correct file number onto a blank card, in the normal image folder/directory for your camera.
2. Ensure camera numbering mode is set to AUTO.
3. Insert card into camera.
4. Take one photo (of the floor, or anything inconsequential).
5. Remove card and either format it or erase it, depending on your normal practice.
6. Camera should now be reset at the next consecutive file number.

This method can also be used to set the next number to anything you like, thereby allowing you to create file number 'space' to fix an indeterminate number of incorrectly numbered files. Just renumber the copied file to whatever number fixes your problem.

This has happened to me, a couple of times.
Worked out the fix above after the first time.

HTH.

This works!

The only problem is that you have to notice the problem early, which is pretty difficult because it invariably happens while shooting, and I obviously don't have access to all tools and files I'd need to fix such problems when out and about. But if you notice the issue before import (not a problem for me anymore, somewhat irritatingly - I know I *have* to check), you can always do some kind of bulk-rename for the problematic files and after that sort of mend the issue through the recipe John shared above! The numbering won't be continuous, but at least you'll not overwrite any files by accident.

One little addendum: Use a RAW file for restoring the numbering cache; this should have been obvious (it was for me), but it may be worth mentioning.

Thanks a lot, John! Impressive bit of technical research there!

M.

 

[John King]

This works!

Thanks a lot, John! Impressive bit of technical research there!

You are welcome, mate. Worked it out in about 2009, or thereabouts. Your advice about using a RAW file is good. To cover all bases, a RAW+JPEG pair is probably best.

One thing that I missed out, Matt.

Set your image ingester s/w to NEVER OVERWRITE FILES.

If it doesn't have this option, change your image ingester to one that does have it! IIRC Adobe Bridge has this option, or just won't do it. I can't remember which at this time of night here (2200H). Too late to boot my PC and check, and I'm too knackered, anyway.

Batch renaming is a lot easier than trying to recover files, if you really mess up. Which, I might add, I have done on a few occasions ...

 

[MoonMind]

You are welcome, mate. Worked it out in about 2009, or thereabouts. Your advice about using a RAW file is good. To cover all bases, a RAW+JPEG pair is probably best.

One thing that I missed out, Matt.

Set your image ingester s/w to NEVER OVERWRITE FILES.

If it doesn't have this option, change your image ingester to one that does have it! IIRC Adobe Bridge has this option, or just won't do it. I can't remember which at this time of night here (2200H). Too late to boot my PC and check, and I'm too knackered, anyway.

Batch renaming is a lot easier than trying to recover files, if you really mess up. Which, I might add, I have done on a few occasions ...

I know you're right about that - but the problem is that my favourite editor *can't* be set not to overwrite files! It's the only (though quite a big) nuisance at times. Once that's happened, my *edited* files are overwritten (the originals are intact, all of them - but a pain to keep apart; I had to add another folder whenever the number reset happened).

I guess I've lost about 100 edits to this issue overall ....

It's a major oversight by the makers - just adding an index ("_1") to every new copy of a file of the same name would remedy the problem. But the app (Polarr Pro) doesn't do that on batch export. It wasn't fun finding that out "post festum".

... (time passes) ...

Gosh.

Just found a solution for Polarr. Not the one I'd have favoured (suffix, automated), but I *can* add a custom prefix manually. In short, the issue is manageable now!

Thanks again, John. You made me get off my butt and actually look for a way ...

M.

 

[John King]

I know you're right about that - but the problem is that my favourite editor *can't* be set not to overwrite files! It's the only (though quite a big) nuisance at times. Once that's happened, my *edited* files are overwritten (the originals are intact, all of them - but a pain to keep apart; I had to add another folder whenever the number reset happened).

I guess I've lost about 100 edits to this issue overall ....

It's a major oversight by the makers - just adding an index ("_1") to every new copy of a file of the same name would remedy the problem. But the app (Polarr Pro) doesn't do that on batch export. It wasn't fun finding that out "post festum".

... (time passes) ...

Gosh.

Just found a solution for Polarr. Not the one I'd have favoured (suffix, automated), but I *can* add a custom prefix manually. In short, the issue is manageable now!

Thanks again, John. You made me get off my butt and actually look for a way ...

M.

Glad to be of help, Matt. I too bought Polarr Pro. Then they dropped the text module, so I cannot add an explicit copyright notice to my images. I've written to them, but still just full of silly frames instead. They've lost me, Matt. Pisses me off greatly.

I now use my Adobe licence on my mobile devices. So, using Photoshop Express. It is far more inclusive of the practical things, even though well hidden, like most mobile apps are prone to be ... .

I also licensed several image managers, a proper file manager (File Manager Plus), and an FTP client (FtpCafe Pro) that's identical to FileZilla on my desktops.