R1 Reviews

I have now turned off all options under the Lens Aberration correction menu.

With Pre-capture enabled and H+ mode at 40 fps buffer is maybe a bit longer at 13-14 seconds.

Hmm.. that seems off. I could never hit the buffer on the R3. Do you have Auto lighting optimizer and highlight tone priority turned off?

I'd turn off the HDR too.
 
Upvote 0
Hmm.. that seems off. I could never hit the buffer on the R3. Do you have Auto lighting optimizer and highlight tone priority turned off?

I'd turn off the HDR too.
All three of those are OFF. When I hit the buffer it pauses for a brief moment and then continues. It is not drastic, but what I have found. Yes I agree that my results are odd, but I wanted to report them.
 
Upvote 0
Hmm.. that seems off. I could never hit the buffer on the R3.
I hit the buffer sometimes on the R3. All jpg-related corrections are off (which is how I set up all my cameras, with the MILC caveat that with some lenses distortion correction can’t be turned off…but I don’t shoot long bursts at 30 fps with those lenses).

I do shoot RAW. cRAW would be different.
 
Upvote 0
I hit the buffer sometimes on the R3. All jpg-related corrections are off (which is how I set up all my cameras, with the MILC caveat that with some lenses distortion correction can’t be turned off…but I don’t shoot long bursts at 30 fps with those lenses).

I do shoot RAW. cRAW would be different.

I couldnt even hit it in crazy electronic shutter bursts
 
Upvote 0
I couldnt even hit it in crazy electronic shutter bursts
Strangely I remember hitting it while shooting birds, but thinking about it, maybe it was my hesitation, if you remove your finger the buffer catches on and you can't continue.

So I have all optimization off, tested it now, and got 606 shots @30 shots/s before it stopping
 
Upvote 0
Turn off all of that and try again. If you're not shooting JPG output, those still take processing power and can affect the buffer speed.
On my R8, R5II and now-sold R5 turning those off didn’t make a difference when using cRAW. And I refuse to use full RAW in H+ mode :)
Formatting the card before each burst did make a small difference, however.
 
  • Like
Reactions: 1 user
Upvote 0
On my R8, R5II and now-sold R5 turning those off didn’t make a difference when using cRAW. And I refuse to use full RAW in H+ mode :)
Formatting the card before each burst did make a small difference, however.
With the R1 I definitely want to be able to use full RAW at 40 fps. I realize that cRAW has an advantage in terms of buffer, but I would like to retain all of the information capture by the sensor. From my testing, I am getting 12-15 seconds of buffer in H+ mode at 40 fps (depending of if pre-capture is engaged and for how long). Overall, I am happy with the buffer which was one area of concern I had.
 
  • Like
Reactions: 1 user
Upvote 0
Revised Buffer Testing for the Canon R1

This morning I must have made some error in my testing, but I don't know what error I made.

This evening I repeated my test using the Canon R1 with all processing turned off in full RAW using the Canon RF 70-200 mm f2.8 Z at aperture f2.8 and ISO set to 6400.

Using Prograde Cobalt cards with Pre-capture enabled I half depressed the shutter until the buffer read 16 (about 3-4 seconds).

With these conditions I was able to record the following number of frames before the viewfinder said BUSY:

40 fps: 380 frames before the camera said BUSY (clearing the buffer)
30 fps: 394 frames before the camera said BUSY (clearing the buffer)
20 fps: 900+ frames and I never had the camera pause. I could have held the shutter down longer, but did not see the point.

For my setup, I will likely set the camera to default at 20 fps and have the AF-ON button assigned to 40 fps so when half-pressed I switch to the higher frame rate.

Overall, I am impressed with the buffer because at 40 fps I have ~ 10 second buffer and at 20 fps the buffer is basically unlimited.

Lastly, my apologies to the community for the erroneous results I posted earlier today.

Addendum: For the test above the file size was 32.2 MB. At lower ISO file size is generally smaller so maybe at lower ISO buffer could be even better? ISO 6400 is quite common for me so it made sense to test the camera buffer in such conditions.
 
Last edited:
  • Like
Reactions: 3 users
Upvote 0
With these conditions I was able to record the following number of frames before the viewfinder said BUSY:

40 fps: 380 frames before the camera said BUSY (clearing the buffer)
30 fps: 394 frames before the camera said BUSY (clearing the buffer)
20 fps: 900+ frames and I never had the camera pause. I could have held the shutter down longer, but did not see the point.

Overall, I am impressed with the buffer because at 40 fps I have ~ 10 second buffer and at 20 fps the buffer is basically unlimited.

Addendum: For the test above the file size was 32.2 MB. At lower ISO file size is generally smaller so maybe at lower ISO buffer could be even better? ISO 6400 is quite common for me so it made sense to test the camera buffer in such conditions.
Thanks for doing the testing! Did you happen to time how long it takes to clear the buffer? This would tell us something about the size of the buffer/write speed.

Overall, this is all good and better than expected. 380 x 32.2 MB = 12.2 GB of data collected at 40 fps, ~10 sec. Combine that with essentially unlimited at 20 fps, and I think this is going to work for most people.
 
Upvote 0
Thanks for doing the testing! Did you happen to time how long it takes to clear the buffer? This would tell us something about the size of the buffer/write speed.

Overall, this is all good and better than expected. 380 x 32.2 MB = 12.2 GB of data collected at 40 fps, ~10 sec. Combine that with essentially unlimited at 20 fps, and I think this is going to work for most people.
I did not time how long it took to clear the buffer.

Once the viewfinder said BUSY I stopped pressing the shutter release. Overall, I found it very good buffer performance. Unlimited buffer at 20 fps is good for 95+% of wildlife photography (in some cases it is likely overkill).

I still have a 10 sec 40 fps buffer at my disposal when high-speed action requires it.
 
Upvote 0
The next wait is for the dedicated RRS L-bracket. Neither the R3 nor the 1D X bracket are a flush fit (close, but not close enough). So it’s the generic BP-CS plate for now. I didn’t bother with their ‘universal’ L plate.
 
Upvote 0
The next wait is for the dedicated RRS L-bracket. Neither the R3 nor the 1D X bracket are a flush fit (close, but not close enough). So it’s the generic BP-CS plate for now. I didn’t bother with their ‘universal’ L plate.
That might take a few months. I pre-ordered the L-bracket for the R5 Mk II mid October, the answer to my question when this would be shipped was “we are not planning to start shipping these out until the beginning of 2025”.
 
Upvote 0
Because they have no L-plate for the R5 Mk II body with BG-R20 grip.
Your next question or recommendation will be: get a cage. I do not need a cage and do not like the additional volume and weight.
Oic.. sorry. I breezed by the bg-r20 thing...

No, we were talking about L-brackets and no one has a cage. There will be L brackets for the grips later this month.

I have a prototype cage and L bracket for the R1... Those will probably be December or January.
 
  • Like
Reactions: 1 users
Upvote 0