EOS R3 (Discussion Thread)

Stop shaking your cameras!

Those little imps inside that paint the pictures when you press the button are spending all their time re-collecting all their paint brushes and pallet knives after you rattle them around like that!

Ahh, now I get it. We with rattling cameras have activated the Custom function called Psychedelic result - ON.

apersson850 wrote in post #19439399
Mine doesn't rattle with power on. Some people leave the power switch on all the time, and rely on the camera going to sleep when not used.

Just checked mine again, there is a slight noise when the power is on but it's only just noticeable. When the power is off it sounds like there is a brick in there moving around!

CyberDyneSystems wrote in post #19439569
Stop shaking your cameras!

Those little imps inside that paint the pictures when you press the button are spending all their time re-collecting all their paint brushes and pallet knives after you rattle them around like that!

Good point, I forgot all about those important guy's, I'll put the camera down right away!

CyberDyneSystems wrote in post #19439569
Stop shaking your cameras!

Those little imps inside that paint the pictures when you press the button are spending all their time re-collecting all their paint brushes and pallet knives after you rattle them around like that!

Go to custom function 47 in the menu system and set "Pratchett" to off; that'll fix it.

jwcdds wrote in post #19429030
Hm... so I encountered a slight problem (albeit one that probably won't/shouldn't happen too often). So at an airshow today, I managed to fire off 14k images. Being the noob that I was, I didn't think to reset my filename before the shoot, so this ended up spanning over 3 folders. Problem now is I have 2 sets of CR3_#### images with the same name for a few thousand photos, granted they're currently saved in different folders.

This will make my file naming a little more complicated when I import to the PC.

I'm open to suggestions from everyone as to what you do if/when you've taken over 10k shots in a day and with the way the camera names the files and how you organize that later when uploading. (Other than one obvious solution, which is to not shoot over 10k images. )

I realize I'm a little late to this post (been absent for months), but I've been dealing with this issue for years.
Here's an example of my workflow, if this helps.


Canon filename management



I usually shoot with two bodies (up to six for video) and always rename my image filenames when importing to Lightroom, but have also run into the multiple folder issue when shooting a single body.

• Single body, image filenames renamed from "R3A_3877" to "20221105_R3A3877" using the YYYYMMDD rename preset in Lightroom.
  
  
• Two bodies, image filenames renamed from "R3A_3877" to "20221105-123614_R3A3877" and from "R3B_9989" to "20221105-145937_R3B9989" using the YYYYMMDD-HHMMSS rename preset in Lightroom.
  
  
• Single body when the image counter has rolled-over the 9999 mark, I do the same as the "two body" format above: rename the images from "R3A_3877" to "20221105-123614_R3A3877" using the YYYYMMDD-HHMMSS rename preset in Lightroom.
  
  

Pro-tip - Now that Canon finally allows us to save/load camera settings to a card (and will hopefully later allow us to do this with the app on our phones), please know that if you save settings to clone to another camera, the filename will be copied also.
I found this out the hard way when both camera filenames were "R3B" and I didn't realize it until import. Fortunately my cards are labeled for each camera, so it wasn't too hard to fix (see "better file rename" at the end of this post).

Ingesting image files

Cards come out of the camera and are copied to an "IMPORT" drive on my computer (H-drive).
I have three card holders (RED, YELLOW, and GREEN), each slotted for 10 cards (I'm having some made right now to hold 15 cards each).

After a card is copied to the computer (H-drive), it goes in the RED card holder, because it's not ready to be used again.
Once all the cards are on the H-drive, I'll run JPEGmini Pro to compress the JPEGs (yes, I shoot raw+JPEG).
I use Lightroom to import from the H-drive to the B-drive (which is my Lightroom working SSD).
Lightroom is also set to make a copy of the import to the BACKUP drive (F-drive).

Recently I've been having trouble with Lightroom taking way too long to import, so I changed my process and now I don't rename the files until after they're all imported to Lightroom.

When Lightroom is done importing, I select all images, press F2 and rename them as described above.
The only downside to renaming after import, is the backup images (copied to the F-drive) will not get renamed. I haven't needed that backup (yet) so I'm OK with that for now, they're not (usually) renamed on the H-drive anyway, so I can live with it.

After renaming is complete, JPEG images (with new filenames) are uploaded to Google Photos, although Google Photos unfortunately doesn't allow you to sort by filename. This Google Photos flaw only matters when there's a burst of images and it's sorting by "date/time taken" and gets some of the burst out of sequence (please fix this, Google).
The other issue with Google Photos is that the date/time on the images really does matter. Not just date/time, but the time zone you're in, and the DST on/off setting; another thing I learned the hard way (updating my camera and audio recorder clocks tonight). If the time on two cameras is exactly the same, but the time zone or DST on/off is different, Google Photos notices, but Lightroom does not. This means two photos (taken within seconds of each other from two different camera bodies), that have the same time (YYYYMMDD-HHMMSS) but different time zones or DST on/off will be separated by an hour or more in the gallery.

Using JPEGmini Pro helps cut down the file sizes immensely, without affecting the quality (and so much faster to upload too). I have the JPEGmini Pro plugin for Lightroom and use it when exporting images.

When everything is in Lightroom, uploaded to Google Photos, then the Lightroom catalog gets backed up, and I move the card(s) to the YELLOW card holder. This means they're on the computer (three separate drives), and the JPEGs are uploaded to Google Photos; but not fully backed up yet.
After I complete the job and deliver the images (or video), then the entire job folder is copied from the B-drive to my DROBO (J-drive).
Once this copy is complete and verified, the card(s) will be moved to the GREEN card holder, which means they're safe to be formatted for the next job.



If you need to rename files outside of Lightroom, I'd strongly suggest using Better File Rename. I've been using it for years, and it's amazing and super powerful in terms of customization as well as batch renaming.
I actually bought the whole suite, which includes other handy tools like changing the EXIF date/time, changing the "created, modified, and accessed" attributes of a file.

Jules.r wrote in post #19438333
Can any other R3 users out there confirm if their bodies rattle as loudly as mine please?
I have done a forum search but surprisingly didn't find much on the subject.
From what I have read the rattle is the IBIS stabilization and is perfectly normal.
This is the second R3 I have had, and I didn't notice any rattle with the first.... and this one seems really loud to me.

Short You Tube video here:

https://youtu.be/5MGKM​2tdnSo

Both of my R3 bodies do this, and at the same loudness. I always suspected it was the IBIS system, so I don't want to shake it too hard.

The R5 does it too (maybe not quite as loud), and the EOS R makes a sound, but barely noticeable.

I think I remember hearing this on the 5D Mk4, but always thought it was a sensor (not the image sensor) to tell the camera if it's in horizontal or vertical mode. Although those types of sensors are not likely to be mechanical anymore (thank you, smartphone technology), so it's probably something else on the EOS R and the 5D Mk4.




Definitely not the battery, because the sound is there with and without batteries installed.

(With apologies if this link has been posted by anyone beforehand)

I only discovered this 2-month old, 35-minute long review, just the other day.
I feel it is an excellent review/ presentation.
I feel that a person that is considering this camera body, could learn a lot about it.

https://www.youtube.co​m/watch?v=tMjri_ZBg0w

About the reviewer, whom I also had no knowledge of, just those couple of days ago:
https://mirrorlesscomp​arison.com/about-us/

(Update to this post)
The written version of this man's (couple's?) R3 review, is at this site:
https://mirrorlesscomp​arison.com …bird-wildlife/#more-34610

A replacement eyecup for the R3, that I found interesting:

https://www.amazon.com …ref_=lv_ov_lig_​dp_it&th=1

FW 1.3 Released:

Firmware Version 1.3.0 incorporates the following fixes and enhancements:

1. The [User Def.] on [Picture Style] can now be selected in the Cloud Raw image processing settings.
2. Fixes minor issues.

Doesn't sound too exciting, but it is there.

https://www.usa.canon.​com/support/p/eos-r3

Mark A. wrote in post #19448710
(With apologies if this link has been posted by anyone beforehand)

I only discovered this 2-month old, 35-minute long review, just the other day.
I feel it is an excellent review/ presentation.
I feel that a person that is considering this camera body, could learn a lot about it.

https://www.youtube.co​m/watch?v=tMjri_ZBg0w

About the reviewer, whom I also had no knowledge of, just those couple of days ago:
https://mirrorlesscomp​arison.com/about-us/

(Update to this post)
The written version of this man's (couple's?) R3 review, is at this site:
https://mirrorlesscomp​arison.com …bird-wildlife/#more-34610

I like their reviews when I started with Olympus mirrorless....

PinholeR5 wrote in post #19449235
FW 1.3 Released:

Firmware Version 1.3.0 incorporates the following fixes and enhancements:

1. The [User Def.] on [Picture Style] can now be selected in the Cloud Raw image processing settings.
2. Fixes minor issues.

Doesn't sound too exciting, but it is there.

https://www.usa.canon.​com/support/p/eos-r3

My R3 has locked up occasionally. Will be interesting to see if that's among "minor issues".
For Swedish users: Firmware 1.3

apersson850 wrote in post #19449353
My R3 has locked up occasionally. Will be interesting to see if that's among "minor issues".
For Swedish users: Firmware 1.3

My R3 doesn't "lock up", but sometimes it will take like 5-10 seconds to "wake" when I'm using my RF 70-200. I haven't tried replicating the issue but from what I can tell, it seems to somehow coincide with whether I try and wake it while holding it in portrait orientation. (I know, sounds weird.) I never have to turn it off or pull the battery (though that would be quicker to wake it). After awhile (usually around 5 seconds) as I try and press the shutter button, then it'll finally wake up.

It's an annoying quirk that I try to work around for the time being when shooting my kids games.

Doesn't happen when I use my rf50, nor my ef100-400 w/ adapter. Seems to be a 70-200 issue. I don't remember if it used to happen on my ef 70-200... I think it did.

jwcdds wrote in post #19449397
My R3 doesn't "lock up", but sometimes it will take like 5-10 seconds to "wake" when I'm using my RF 70-200. I haven't tried replicating the issue but from what I can tell, it seems to somehow coincide with whether I try and wake it while holding it in portrait orientation. (I know, sounds weird.) I never have to turn it off or pull the battery (though that would be quicker to wake it). After awhile (usually around 5 seconds) as I try and press the shutter button, then it'll finally wake up.

It's an annoying quirk that I try to work around for the time being when shooting my kids games.

Doesn't happen when I use my rf50, nor my ef100-400 w/ adapter. Seems to be a 70-200 issue. I don't remember if it used to happen on my ef 70-200... I think it did.

I also have the RF 70-200 f/2.8 but haven't experienced that phenomenon. For what it's worth, there is also a newish FW for the RF 70-200 f/2.8 from 9/1/22:

Firmware Version 1.1.1 incorporates the following fix:
1. Fixes an issue, in which, in rare instances, "Err60" is displayed if zoom operations are performed when the camera is started.

https://www.usa.canon.​com …rf-70-200mm-f2-8-l-is-usm

Not sure it has anything to do with what you are experiencing (since you see no Err60), but perhaps it might help things.

PinholeR5 wrote in post #19449419
I also have the RF 70-200 f/2.8 but haven't experienced that phenomenon. For what it's worth, there is also a newish FW for the RF 70-200 f/2.8 from 9/1/22:

Firmware Version 1.1.1 incorporates the following fix:
1. Fixes an issue, in which, in rare instances, "Err60" is displayed if zoom operations are performed when the camera is started.

https://www.usa.canon.​com …rf-70-200mm-f2-8-l-is-usm

Not sure it has anything to do with what you are experiencing (since you see no Err60), but perhaps it might help things.

I'll double check but I believe I updated the lens firmware already. I never gotten any Err messages.

Of course it's one of those things that doesn't happen 100% but it does happen with enough frequency where I know it's not some fluke phenomenon.

If memory serves me right, it's usually where I have the camera in landscape orientation and watch the game.. then as I rotate the camera up to my face so I can shoot in portrait orientation (for basketball), then it would hang for several seconds, unresponsive, before I see the EVF wake up and hear the IS kick in.

jwcdds wrote in post #19429030
So at an airshow today, I managed to fire off 14k images.

Holy cow, 14k in one day!

Did you get any keepers?