Listening to the Voices in my Head

Something that really irks me

Yesterday, I gave my 'antiquated' EF Prime lenses a test run with the Canon RF. using the control ring adapter.

To those who say the lenses are too slow to focus; pish tosh.  Your humble bragging about selling off your EF lenses so you can get the new RF lenses is humble bragging.  Of course, I have found bargains beyond belief because of such humble bragging.

I do have one RF lens, the 35mm. It's fine. Kind of noisy, but great lens. My 300mm EF L IS works great on the RF body. My 400mm NON is EF L lens works equally great.

Of all the RF lenses I have tried, I wouldn't say no to the 100-500. But no humble bragging here. I am saving for this lens, but I am not humble bragging that I am selling off my EF lenses to do this. Instead I bought an adapter ring, to continue using the excellent EF glass on the RF. And I still have my 7DmkII, that use those same EF lenses.  And I have an adapter ring to use EF lenses on my Olympus OMD EM-1.

Yup, I was right

On November 28, 2020, I posted a rather lengthy blog entry under the title "Canon, you have some 'splainin' to do!" regarding how their new EOS R5 and its' overheating problem when recording video. I even posted link to a video where someone, with a helluva lot more money than I can spare, disassembled the R5, made a water cooling system. Fixed the overheating, but impractical.

Also in the video, he carefully removed the back, removed the ineffectual tiny heat sink, and cleaned off the old thermal paste. He fabricated a larger heat sink that and after a dab of thermal paste, put the new heat sink on, closed up the camera, and TA DA! No more overheating problems.

The reason I type all this out, is I told my hubby that I wouldn't be surprised if Canon, who claimed the EOS R5 was 'future proof' (planned obsolescence) would put out a new version nothing more than a larger heat sink to stop the overheating issue.

Hello new model Canon EOS R5 Cinema!  It's the EOS R5 without the heating problem!

To me, this makes no difference as I am a still photographer, not a videographer.  But if I was someone who bought the EOS R5 with 8K videoing in mind, only to run into the overheating wall, I would politely demand that Canon fix the flaw EOS R5 they already own.

Canon, you have some ‘splainin’ to do!

1: Yes, I have this camera.
2: Yes, I have noticed that it gets hot!
3: Although I have the know-how to do this, I don't have the equipment, nor would I void my warranty by doing this. (but if I had the means and equipment, I would!) 

Many (aka males) have 'explained' to me that the R5 is a STILLS camera. 
Really? Then Canon shouldn't be advertising it the way they do, regarding using it for video.

This is from their own sites (US, UK, AU):
  "Introducing 8K video: how the Canon EOS R5’s flagship filmmaking feature changes the game.  The Canon EOS R5 rigged for filming. Audience expectations are growing, with high-resolution video content in demand across all platforms from streaming services to commercials, and the EOS R5 is poised to deliver, making it a future-proof choice.”

So no, this overheating problem does NOT make it future-proof (planned obsolescence). And my techy-ness makes me just shake my head at how this overheating issue could have been avoided by some proper thermal paste, and a proper heat conducting plate.

The blithe mansplainers saying "People should get the Canon Cine cameras" does NOT negate this problem, especially in light of how Canon itself is advertising this very expensive piece of camera gear. 

Does the R5 take great photographs? Oh hell, yes. They're sharper, cleaner, and overall IQ is heads and tails above the 5DmkIV.

But this heating issue...  This isn't like the futz 'light leak' that could be caused by something no photographer would really do.

I wouldn't be surprised if there will be some sort of recall because of camera bodies warping, melting, or catching fire, when used to record video.

Or a EOS R5mkII? 

It was bizarre

I was so so when I went to bed last night. I have no idea why, but all I know is I couldn't get to sleep because of it. Got up, took some ibuprofen/paracetamol tablets. Must have worked because the next thing I knew, we were being annoyed by three of the cats to get up and feed them.

Picked up a Canon 1DmkIV in immaculate condition, looks brand new, for cheap cheap.  Tested it out and it's ok, and although it does focus faster than the 7DmkII, and has a larger sensor, it's not better than then 7DmkII.  So, plan b: bundle them both together for a trade in. 

Kind of expected this

After a session with a Microsoft Tech regarding not being able to see camera raw files from specific cameras (Olympus OMD EM1mkII and EM5mkII, and Canon 5DmkIV) I was told it was a Canon issue and to contact Canon for 'the fix'.

Three guesses what I got in response... and the first two guesses won't count.

It's a WINDOWS issue.

Meanwhile, some versions of Windows will let you view CR2 files natively (for example, in a folder view). In previous versions of Windows, you needed to download the Microsoft Camera Codec Pack, which provides support for viewing RAW image file format thumbnails and image information in Windows Explorer.  In Windows 10, the default app for opening RAW image files is Windows Photo Viewer. However in some cases, Windows 10 operating system cannot open the RAW files in "preview mode" for images taken using new EOS camera models.

Now the cameras I mentioned aren't 'new'. They are a few years old now.

This was my reply:

Not being snarky here, but I had a feeling this was the answer I was going to get. Microsoft said it was a Canon issue, and Canon saying it was a Microsoft issue. How about you two get together and fixing the problem, rather than fixing the blame.

I don't use DPP, although I do have it installed because I wanted to see if that would install a camera codec in Windows 10 and it didn't. I use On1Photo Raw, which sees the CR2 files just fine. Also, Photoshop CC & bridge with latest camera raw update sees the CR2 images just fine. The problem is OTHER software (Aurora HDR, Luminar, Affinity) rely on Windows 10 native Windows Explorer in program to select and process images.

I will pass this along to Microsoft, and I am going to wager they will once again tell me it's NOT a Windows 10 issue, but a Canon issue.