Magic Lantern Forum

Magic Lantern Releases => Camera-specific discussion => Topic started by: SiSS on February 15, 2020, 01:53:06 AM

Title: Canon EOS R5 / R6
Post by: SiSS on February 15, 2020, 01:53:06 AM
"Be the filmmaker" they say
https://www.canon-europe.com/cameras/eos-r5/

EOS R5 mirrorless 5D?
https://global.canon/en/news/2020/20200213.html
Title: Re: Canon R5
Post by: yourboylloyd on February 15, 2020, 04:06:49 AM
Resolution, IBIS, and Dual Pixel Auto focus means nothing. If it can't do internal RAW at least 10bit then the 5D2 is better that crap.
Title: Re: Canon R5
Post by: Stousen on February 15, 2020, 09:21:25 AM
Resolution, IBIS, and Dual Pixel Auto focus means nothing. If it can't do internal RAW at least 10bit then the 5D2 is better that crap.

 :D :P
Title: Re: Canon R5
Post by: kitor on February 15, 2020, 09:57:11 PM
Aside from technical improvements, I'll be switching for sure in future (unless they screw something really bad). Missing thumb wheel was hard for me to live with, even if I got used to after a year ;)
I just fear the pricing, as if those are not just marketing words, I believe it will be more expensive that R was.
Title: Re: Canon R5
Post by: Dmytro_ua on March 04, 2020, 06:03:51 PM
This camera is looking really promising (of course if Canon won't decide to cut rumored functionality).
I won't be a first runner buyer but will definitely save $ to switch from my 5d3 (eye following DPAF and video modes are so lacking in my 5d3 cam..).

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fwww.canonrumors.com%2Fwp-content%2Fuploads%2F2020%2F03%2F12.jpg&hash=32ec23af98a2fa519934efc6816acb3c)
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fwww.canonrumors.com%2Fwp-content%2Fuploads%2F2020%2F03%2F02.jpg&hash=651226716059c36b3ddf3c134894157c)
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fwww.canonrumors.com%2Fwp-content%2Fuploads%2F2020%2F03%2F11.jpg&hash=bde8890be24a59221c6a5dd751f16abf)
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fwww.canonrumors.com%2Fwp-content%2Fuploads%2F2020%2F03%2F10.jpg&hash=8c71306d258a6939bc276a9b04aaac51)
Title: Re: Canon R5
Post by: yourboylloyd on March 05, 2020, 06:14:39 AM
(eye following DPAF and video modes are so lacking in my 5d3 cam..).


The real reason the 5d2 is better than the 5d3 is because the ZOOM button is on the right side. I have no clue why the 5D3 has the zoom button on the left. That's at least one thing this camera has going for it is the correct ZOOM button placement.

But who knows if it will even matter. DPAutoFocus is apparently so amazing you don't ever need to verify your shots anyway.
Title: Re: Canon R5
Post by: Dmytro_ua on March 05, 2020, 10:52:50 AM
The real reason the 5d2 is better than the 5d3 is because the ZOOM button is on the right side.

It's not an issue at all - check the latest Danne's ML build, it has an amazing fast zoom option in LiveView.
Title: Re: Canon R5
Post by: Antony44 on April 10, 2020, 08:42:01 AM
My story is interesting. I bought 5DsR. About a month passed and was horrified. Some kind of imperfection, everything is fuzzy, soap, etc., is sold. I bought 5DMarkIV. I took six months, but still thought what happened to DsR? I purchased 5DsR again. Large files are torture, because I shoot a macro, and there are stacks of frames, and returned to 5DMarkIV again, but only for a week. After a week of testing 5DsR, I apologized,, (https://grilliam.com/) 5DMarkIV passed it to my daughter, and he finally returned to 5DsR and not only returned, but also bought a second 5DsR.  8)
Title: Re: Canon R5
Post by: Sportegan on April 12, 2020, 11:33:00 AM
Thanks to me as a beginner, it's very interesting to read all about the Canon R5. I bought it 2 weeks ago and am trying to figure it out.
Title: Re: Canon R5
Post by: ilia3101 on April 12, 2020, 01:41:06 PM
The real reason the 5d2 is better than the 5d3 is because the ZOOM button is on the right side. I have no clue why the 5D3 has the zoom button on the left. That's at least one thing this camera has going for it is the correct ZOOM button placement.

YES ARGH!

The 5D3 and 5Ds are so much worse than the 5D2 because of this (probably mark 4 as well). You also have to press the zoom button twice to get any zoom (WTF).

I miss the 5D2, such a great experience.
Title: Re: Canon R5
Post by: Dmytro_ua on April 12, 2020, 01:53:30 PM
Thanks to me as a beginner, it's very interesting to read all about the Canon R5. I bought it 2 weeks ago and am trying to figure it out.

You were deceived as R5 is not announced yet
Title: Re: Canon R5
Post by: kitor on April 14, 2020, 09:11:58 PM
I guess our two new colleagues can't see the difference between EOS 5DS R and EOS R5.
Title: Re: Canon R5
Post by: kitor on April 20, 2020, 07:35:30 PM
https://www.usa.canon.com/internet/portal/us/home/explore/product-showcases/cameras-and-lenses/eos-r5
https://www.canonrumors.com/canon-announces-more-mind-blowing-specs-for-the-canon-eos-r5/

Just one quote:
Quote
Internally recorded and uncropped 8K RAW Recording up to 29.97 fps with Dual Pixel CMOS AF, and HDR-PQ Recording (H.265) capability.

Well, price will hurt for sure.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.imgur.com%2FWMKrXDZ.jpg&hash=06a23f41176c6bc8d16e3e8bd519d41a)
Title: Re: Canon R5
Post by: yourboylloyd on April 20, 2020, 10:38:40 PM
10 bit 8k internal NON CROPPED WITH A FLIPPY SCREEN??!?!?!?!?!?!?!?!?!?!?!?!??!?!?!?!? No way.... no freaking way. it doesn't even have 8bit anything....


Sorry guys. This camera is going to pretty much kill ML... unless it's $6,500 body only w/ no batteries, no front cap, no battery cover, no camera strap, no24p, no 25p, and no product box.


Wow... I mean the 120p 4k was good enough to get me. I actually can't believe this. This camera is everything anyone could ever ask for. And look at how small it is!
Title: Re: Canon R5
Post by: ZEEK on April 21, 2020, 01:26:39 AM
Yep, this camera has every spec we could ask for right now (except raw, but meh...).
Awesome 8K with Canon Colour Science should be glorious! 
Title: Re: Canon R5
Post by: yourboylloyd on April 21, 2020, 01:30:10 AM
Yep, this camera has every spec we could ask for right now (except raw, but meh...).
Awesome 8K with Canon Colour Science should be glorious!

except RAW? What were you reading? There is literally an entire tab that says 8K internal RAW Recording
Title: Re: Canon R5
Post by: ZEEK on April 21, 2020, 01:58:12 AM
Just saw the above sample :o. JEEPERS!! This camera is even more nuts!
Title: Re: Canon R5
Post by: IDA_ML on April 21, 2020, 11:13:27 AM
This camera is going to pretty much kill ML...

I don't think so.  If you have to sell your kidney to buy the body and a few lenses for it, especially after the coronavirus crisis, ... I don't think that too many people from the ML community will be able to afford it.
Title: Re: Canon R5
Post by: garry23 on April 21, 2020, 11:20:21 AM
Like others I’ve been reading about the announcement from Canon and, of course, it’s going to be an incredible camera, especially for professionals.

But, and I think these and big buts, it will be expensive for mere mortals, like myself, and, critically, it will not have one ML killer feature, namely in-camera Lua scripting.

I must say, that extending the scripting API remains an area of ML that could continue to take ML to ‘better’ things.

Sadly I remain a non-developer.

Cheers and stay safe

Garry
Title: Re: Canon R5
Post by: IDA_ML on April 21, 2020, 11:42:40 AM
I fully agree with you, Garry.  The creativity that ML offers and will also offer with our old cameras for free in the future is unbeatable by any camera on the market!
Title: Re: Canon R5
Post by: kitor on May 02, 2020, 10:00:43 AM
I just got reminded about CF-to-SATA thread (https://www.magiclantern.fm/forum/index.php?topic=5470.msg177330#msg177330). And I was going to post here that finally we will be able to attach HDDSSD to our cameras, as there are CFast to SATA adapters (CFast is in mostly a fancy connector for SATA).

And then I checked again and it's CFexpress  :o Didn't even notice that there's a new standard already. PCIe v3 x4 / NVME - I wonder if someone will make  m.2 NVME -> CFexpress adapter  ;)
They are a couple of CFexpress -> (m.2 | pcie) adapters, and while I can't find any photo of "the other side" of pcbs, all PCIe traces seems to run directly between connectors.
Title: Re: Canon R5
Post by: Aperture Science on May 03, 2020, 10:40:09 AM
I just got reminded about CF-to-SATA thread (https://www.magiclantern.fm/forum/index.php?topic=5470.msg177330#msg177330). And I was going to post here that finally we will be able to attach HDDSSD to our cameras, as there are CFast to SATA adapters (CFast is in mostly a fancy connector for SATA).

And then I checked again and it's CFexpress  :o Didn't even notice that there's a new standard already. PCIe v3 x4 / NVME - I wonder if someone will make  m.2 NVME -> CFexpress adapter  ;)
They are a couple of CFexpress -> (m.2 | pcie) adapters, and while I can't find any photo of "the other side" of pcbs, all PCIe traces seems to run directly between connectors.

Hold on, ATA133 which is the last version of IDE, only runs at maximum of 133mb/s. Attach to a SSD or HDD seems just save money for the captaincy?
The exposed socket the external power supply seems more dangerous and unstable xD. But it is a cool idea anyway and did you already tried that out? If not, I am glad to work on it.
Title: Re: Canon R5
Post by: Artur77 on May 03, 2020, 11:14:20 AM
The camera focuses quickly, but I can’t control it quickly. You need to change the ISO, you need to change the focus point, the finger reaches for the joystick, but it is not there, you need to go to the cross. As a result, I often used the touch screen to indicate the focus point. The handle is so comfortable. I am sure that anyone who buys this camera will get used to it.
Title: Re: Canon R5
Post by: yokashin on May 03, 2020, 12:04:44 PM
I think it's about sata, not ata ... The last standard of sata is sata3 (750 MB/s)
Title: Re: Canon R5
Post by: Aperture Science on May 03, 2020, 12:13:54 PM
I think it's about sata, not ata ... The last standard of sata is sata3 (750 MB/s)

Oh yeah lol, I miss understood. However there are many examples doing CFexpress to SATA on YouTube. Shouldn't be a big deal.
Title: Re: Canon R5
Post by: kitor on May 04, 2020, 08:10:46 AM
I think it's about sata, not ata ... The last standard of sata is sata3 (750 MB/s)

In case of R5 it's not even SATA (CFast), but Canon skipped directly to PCI Express / NVME (CFexpress).

Oh yeah lol, I miss understood. However there are many examples doing CFexpress to SATA on YouTube. Shouldn't be a big deal.

Are you sure? CFast to SATA do exists, as CFast uses SATA protocol. But CFexpress is NVME (PCI Express), that's why I wonder if there will be similar trick possible.
But even if possible - probably a little harder due to PCIe signalling requirements.


By the way - there are three types of CFexpress cards - A, B, C. They differ in physical dimensions and number of PCIe lines. I can't find any information which one will be supported here, but I bet for type A, which is physically similar to SD card.
Title: Re: Canon R5
Post by: Frayfray on May 04, 2020, 09:22:02 AM
Most likely type b since Canon is using it on c500ll
Title: Re: Canon R5
Post by: Luther on May 04, 2020, 08:00:47 PM
This camera can potentially kill C300 and C500.
Title: Re: Canon R5
Post by: Frayfray on May 04, 2020, 08:25:34 PM
i wish that was true but no canon just announced a new c300 mark3 https://www.canonrumors.com/canon-officially-announces-the-cinema-eos-c300-mark-iii/
they are to clever about the way they market cameras and cine cameras i have been dealing with them since 1980s they want you to buy all the models.. crippling features is canon's speciality
Title: Re: Canon R5
Post by: Aperture Science on August 14, 2020, 07:27:58 AM
In case of R5 it's not even SATA (CFast), but Canon skipped directly to PCI Express / NVME (CFexpress).

Are you sure? CFast to SATA do exists, as CFast uses SATA protocol. But CFexpress is NVME (PCI Express), that's why I wonder if there will be similar trick possible.
But even if possible - probably a little harder due to PCIe signalling requirements.


By the way - there are three types of CFexpress cards - A, B, C. They differ in physical dimensions and number of PCIe lines. I can't find any information which one will be supported here, but I bet for type A, which is physically similar to SD card.

Of course SATA line do not contain the pcie lolololol, I was just saying there are things like that by change pcie into SATA ;)
Title: Re: Canon R5
Post by: Filmmaking_Dude on August 14, 2020, 11:13:26 PM
There's some interesting discoveries on the R5 to suggest that the overheating is actually a software limitation imposed by Canon. I wonder what it would take to develop ML to remove them.

https://www.eoshd.com/news/eoshd-testing-finds-canon-eos-r5-overheating-to-be-fake-with-artificial-timers-deployed-to-lock-out-video-mode/
Title: Re: Canon R5
Post by: Walter Schulz on August 14, 2020, 11:22:19 PM
Yes, thought about creating a topic about this, too.
This could be a great opportunity to make paid ML development work. In my opinion it looks like there are some people willing to donate some amount to disable/bypass artificial software limitations for R5.
On the other hand: Terrible timing. Covid-19 and whole industries in a turmoil.
Really don't know if this could be a way to obtain sustainable cash-flow for upcoming ports.

Another one: I think there might be a niché market for a company modifying R5 with some kind of cooling system. Which could do great for Canon users looking for reliability but would be rather useless if they are unable to bypass said artificial software limitations.
But this is a hen-egg-issue.
Title: Re: Canon R5
Post by: Filmmaking_Dude on August 15, 2020, 12:23:22 AM
Tilta actually announced a cooling system for the R5 already, but the problem is that if the overheating is software based timers it will have no effect. https://tilta.com/2020/07/tiltaing-camera-cage-for-canon-r5/

EOSHD findings do correlate with many reviewers saying that the ambient temperature made no difference to the recording and cooldown times. That they were exactly the same in both hot and cool environments, and removing the battery and even adding ice etc had no effect. I think I even heard that it overheated in Antarctia or somewhere really cold, so the software based timers would actually explain this behavior.
Title: Re: Canon R5
Post by: names_are_hard on August 15, 2020, 01:38:25 AM
This could be a software limit and still not be artificial market separation, but instead a lazy way to pass certification.  For consumer electronic devices, they're not allowed to get too hot to touch (defined as something like external temp of 45 or 50C I think, don't recall all the details).

If you want your camera to work in UAE and Alaska, the lazy way is measure it at highest load in the worst conditions, then put a timer in so it passes certification.  That way you don't need fancy temperature sensors in the cam, or conditional code to check and perform different actions in different conditions.  Timers are simple and reliable.
Title: Re: Canon R5
Post by: Ant123 on August 15, 2020, 09:58:56 AM
About EOSHD findings: who knows, the value of which temperature sensor  is reported by Canon API? Maybe average?

If it's software limit it probably can be resetted by resetting all camera settings. However, timer values can be stored in battery-backed memory (RTC) and not affected by a reset.
Title: Re: Canon R5
Post by: kitor on August 19, 2020, 07:02:19 PM
There's already another post from EOSHD:
https://www.eoshd.com/news/canon-eos-r5-overheated-in-my-fridge-after-just-60-jpegs-4-c-ambient/

This is getting even more interesting.
Title: Re: Canon R5
Post by: Walter Schulz on August 19, 2020, 07:18:35 PM
As I said: IMO this would be *the* opportunity to make transition to pay-for-ML-feature-development work. Alas: Timing is just off the charts.
 
Title: Re: Canon R5
Post by: names_are_hard on August 19, 2020, 07:18:57 PM
Nice testing.  That info makes it sound much more like something that can be patched in software, whatever their reason for putting it in.
Title: Re: Canon R5
Post by: yourboylloyd on August 20, 2020, 07:31:30 PM
Canon took 12 months to enable 24p into the EOS RP. They won't care to fix this in any kind of rush. They just don't care about us.
Title: Re: Canon R5
Post by: names_are_hard on August 20, 2020, 07:47:00 PM
I wasn't saying Canon would be the ones fixing it in software :)  ML is software.
Title: Re: Canon R5
Post by: Avenger 2.0 on August 21, 2020, 08:20:49 AM
Looks like if you take out the backup battery the overheating timer resets and you have full record time :o
Title: Re: Canon R5
Post by: Danne on August 21, 2020, 08:42:59 AM
Info from what source?
Title: Re: Canon R5
Post by: yokashin on August 21, 2020, 09:02:55 AM
Info from what source?

https://www.eoshd.com/8k/removing-internal-battery-resets-eos-r5-overheat-timer-are-canons-pants-now-completely-down/
Title: Re: Canon R5
Post by: Walter Schulz on August 21, 2020, 09:47:51 AM
Begins to look like one of the sloppiest thermal management implementations ever.
Title: Re: Canon R5
Post by: 12georgiadis on August 21, 2020, 11:22:25 AM
there is aa hardware button to reset the timer. Hope we can do something with the software ! And add a thermal pad to get seomething a bit more reliable. I would love so switch to Panasonic, s5 for exemple but they have DFD autofocus. Someone is working on a TOF module, but I think a software timer reset could be more simple =)
Title: Re: Canon R5
Post by: kitor on August 21, 2020, 01:27:25 PM
Oh wow. I really want to know how Canon people thought this will slip. With all the marketing that R5 received.

Thankfully this time I didn't preorder  >:( You know, IBIS, wheel is back, but I'll stay with first R till the prices drop a bit.
Title: Re: Canon R5
Post by: yourboylloyd on August 21, 2020, 01:51:31 PM
This is actually exciting news! I was worried that the camera actually gets too hot. But believe this, I'm going to figure out a way to uncripple my R6 whenever it comes in. If I have to make a battery hack or if I have to learn C for the next couple of weeks I will do it!

I've never been more fired up in my life.
Title: Re: Canon R5
Post by: kitor on August 21, 2020, 03:10:30 PM
With hacking R and up, remember that they changed firmware encryption.
I was running stuff on mine, but had to enable bootflag via serial console first.
Title: Re: Canon R5
Post by: visionrouge.net on August 23, 2020, 04:25:42 AM
I'm wondering how hard it could be to run a very simple hack as magic lantern with only one simple task: Reset the overheating counter?
It seem they are writing it into eeprom as it kept from reset even without battery. Only removing the RTC coin cell reset it for now.


Title: Re: Canon R5
Post by: Walter Schulz on August 23, 2020, 07:45:50 AM
Little update at EOSHD with a little help from a1ex and Horshack:
https://www.eoshd.com/news/canon-eos-r5-so-called-overheat-timer-defeated-by-a-single-screw-in-battery-door/#more-24156

EDIT: Thoughts (better not be discussed at EOSHD for obvious reasons) on
Quote
The 14 minutes and 30 seconds of footage seemed to have vanished from the previous card and was not visible in playback mode when I reinserted that card. It is possible that the abrupt power cut had corrupted the clip.

1) It's logical file won't show up. Hasn't been closed properly by Canon.
Q: Shouldn't it be possible to manipulate the file by adding proper bits and bytes?
Yes, I know: This is not a proper procedure and there is a chance card gets corrupted if battery is pulled during write operations. Still interested if it might be possible. May be useful for critical footage rescue operations in the future.

2) That's one every R5 owner *can* try at home without the battery pull part ...
Does EOS R5 support FAT32 as file system for high-res recording? If so: This would generate chunks that have to be visible. Only last recording leg (up to 4 GB) should be invisible and lost (at least for the moment. See item above ...).
And yes, chance of card corruption exists, too!
Title: Re: Canon R5
Post by: a1ex on August 23, 2020, 09:37:52 AM
Little update at EOSHD with a little help from a1ex and Horshack:
https://www.eoshd.com/news/canon-eos-r5-so-called-overheat-timer-defeated-by-a-single-screw-in-battery-door/#more-24156

LOL, I only pointed Andrew to this link (Horshack's post): https://www.dpreview.com/forums/thread/4513421#forum-post-64281948

Quote from: horshack
Many cameras don't update the values in NVRAM until they're orderly shutdown, ie when the power-switch is turned to off. They keep the values shadowed in SDRAM until then. This is done both for performance and to reduce wear on the NVRAM. You can see evidence of this on Nikon cameras by abruptly pulling the battery and then plugging it back in - any config/exposure changes from the previous session will be lost.

Canon is a little more clever - they have a latch sensor on their battery doors that performs an orderly shutdown whenever the battery door is opened. This prevents an abrupt shutdown. To work around this someone could tape/jig the door sensor so that it's always pushed-in. The experiment would be as follows:

1. Find a way to hold the battery door latch sensor in
2. Power on the camera with the battery door open
3. Record video to the point of thermal cutoff (but not power-off shutdown)
4. Pull the battery
5. Reinsert the battery
6. See what the available video time is

There's a chance Canon periodically updates the NVRAM during the session (or when video recording stops), esp for something as important as thermal management. In that case it may be necessary to pull the battery while the video is actively recording. This may leave the CF/SD card in an indeterminate state so it may require a format when the battery is reinserted.

There are also others who tried this trick in various ways (e.g. in this slightly NSFW clip (https://www.youtube.com/watch?v=ygO64oE5VI0), or this variation with a battery grip (https://www.youtube.com/watch?v=b-qeqNY2Nog)), so credits don't belong to me - I didn't discover anything :D

From what I've seen, the trick works if one removes the battery in the middle of recording, but no longer works if the battery is removed after properly stopping the video. As Canon firmware is pretty much event-based, they probably configure an alarm timer directly on the RTC chip, as soon as video recording is stopped. That could also explain why the camera "forgets" about overheating after removing the clock battery.

A software patch might be relatively easy if one knows where to look, assuming the internals are similar to M50, EOS R and other DIGIC 8 models (I haven't seen the firmware).

However, before attempting to disable these timers, I should get some updated legal advice. If we were to implement this feature, it could raise some eyebrows at Canon :)
Title: Re: Canon R5
Post by: c_joerg on August 23, 2020, 01:27:19 PM
Does the R5 support Canon Basic? 
Title: Re: Canon R5
Post by: Ant123 on August 23, 2020, 05:17:57 PM
However, before attempting to disable these timers, I should get some updated legal advice. If we were to implement this feature, it could raise some eyebrows at Canon :)

Looks like you got legal advice in spring 2019...  ;)
Title: Re: Canon R5
Post by: a1ex on August 23, 2020, 05:46:17 PM
Last time I did was in 2014.
Title: Re: Canon R5
Post by: stillinsane on August 23, 2020, 10:22:41 PM
Last time I did was in 2014.

Please do, there are a lot of people including me who would pay for the hack. I will save a lot money from not buying the same camera internals in 6 months for double the "cinema" price.
Title: Re: Canon R5
Post by: srsa on August 23, 2020, 11:57:36 PM
Does the R5 support Canon Basic?
It's not hard to try if you have access to one. Prepare a script card (confirm that it's working on one of your cameras), copy the script from this post (https://www.magiclantern.fm/forum/index.php?topic=23296.msg227190#msg227190) put it in camera and try starting it. If it writes something on card or crashes, then the answer is yes.

But I doubt that it's the case.
Title: Re: Canon R5
Post by: Lars Steenhoff on August 24, 2020, 01:58:53 AM
new videos about the topic of timers on the r5
Andrew did a timer test, promising results



Title: Re: Canon R5
Post by: Kharak on August 24, 2020, 07:58:13 PM
That Sigma FP almost had it, thought r5 had it. But looks like good internal raw stays with 5d3 for now ;)
Title: Re: Canon R5
Post by: Lars Steenhoff on August 24, 2020, 08:00:43 PM
Sigma fp has good internal raw, I have one and its great. and if you add the ssd you have very nice 12 bit external 4k
Title: Re: Canon R5
Post by: ajay on August 27, 2020, 04:45:30 AM
Firmware 1.1 for the R5 is now available to download.

https://www.canon.com.au/support/sims-content?pid=f0fe77137eb5430daf673363565cec37&cid=7A8E003792624BB7A511CBCD523C53F5&ctype=fa
Title: Re: Canon R5
Post by: Danne on August 27, 2020, 06:10:47 AM
 :P
"7. Temperature detection and shooting time control in video shooting have been improved. In addition, the total shooting time when the short-time recording and power-on/off are performed repeatedly at room temperature is improved."
Title: Re: Canon R5
Post by: a1ex on August 27, 2020, 07:53:13 AM
So, patching these timers is no longer needed? :P

Quick look at the R5 firmware update - apparently the same file format as on EOS R, but different encryption key. That means, I cannot look inside.

If our enhancements are still needed, it might be possible to enable the bootflag via UART (https://www.magiclantern.fm/forum/index.php?topic=22770.msg211964#msg211964) (which requires access to a physical camera, and some familiarity with digital electronics). Assuming Canon didn't disable the UART port, of course.
Title: Re: Canon R5
Post by: Walter Schulz on August 27, 2020, 09:36:45 AM
According to Gordon Laing there are actual some enhancements.
And HDMI streaming/recording without thermal management is gone for good. Declared to be a bug and fixed.
Title: Re: Canon R5
Post by: Nicolai1227 on August 27, 2020, 10:08:57 AM
According to Gordon Laing there are actual some enhancements.
And HDMI streaming/recording without thermal management is gone for good. Declared to be a bug and fixed.

I can´t confirm this, I could record external in 4K HQ up to 3 1/2h untill the SSD was full, with cards in. 
So all external recording modes are absolutely usable.

The CFexpress card seems to produce most of the heat, when recording to SD card I got longer 8K IPB and 4K HQ times.
Looking at some exif data, the camera shuts down consistently at 60°C +/- 1

External cooling improves the recording significantly!

Title: Re: Canon R5
Post by: Walter Schulz on August 27, 2020, 10:18:02 AM
-EDIT-
Title: Re: Canon R5
Post by: Lars Steenhoff on August 27, 2020, 12:27:38 PM
Lets see if the Tilta fan will actuality improve things now with the new firmware
https://tilta.com/2020/07/tiltaing-camera-cage-for-canon-r5/


And the best news of today is that there is a firmware update we can look at :)

Title: Re: Canon R5
Post by: Walter Schulz on August 27, 2020, 12:33:17 PM
And the best news of today is that there is a firmware update we can look at :)

And the bad: No easy way back because you just cannot downgrade to a previous version.
Keep that in mind!
Title: Re: Canon R5
Post by: Levas on August 27, 2020, 01:58:10 PM
Just wondering about what Walter says...the original firmware of the R5, say the version that's on the first batch out in the wild.
It's nowhere available for download I guess, since it's the original first version of the firmware.

So that means, if everybody does the update to the newer version, there might be a chance that nobody will ever find out how the 'temperature video locking' was controlled originally.
So maybe we never will know if Canon did the 8k videolocking on purpose and not for temperature or safety of the hardware...
 ::)

So this whole new firmware update could also be used by Canon to get rid of some nasty evidence  :P
Title: Re: Canon R5
Post by: Walter Schulz on August 27, 2020, 02:04:36 PM
Hanson's razor: Never attribute to malice that which is adequately explained by stupidity.

Everything I read about this thingy points to sloppy engineering.
Title: Re: Canon R5
Post by: Levas on August 27, 2020, 02:17:45 PM
Everything I read about this thingy points to sloppy engineering.
Indeed, probably the most obvious reason.

But if the first firmware is gone...we will never know for sure.
Title: Re: Canon R5
Post by: Danne on August 27, 2020, 02:23:11 PM
I think it´s proven already.
Who knows, the new firmware might even control temperature reports or even change temperature physically with the actual firmware to come clean. If measuring temperatures like was done before it could be this could be compared.
Title: Re: Canon R5
Post by: yourboylloyd on August 27, 2020, 03:25:19 PM
Youtube reviews are looking pretty grim. Only slight improvements.

Good news is that my R6 has shipped! So we'll see first hand
Title: Re: Canon R5
Post by: SKecorius on August 27, 2020, 03:45:22 PM
If what we think is happening, then Canon is walking on rather thin ice.. There will definitely be someone, who will not update Canon software, donate both cameras (with and without software update) to ML, who will compare what was done to new ones in order to hide information and fool customers. I would highly recommend everyone, who has R5 not to update software, instead look reviews on how much improves video, as well as incorporate battery pull method to extend recording times. Meanwhile, ML will come up with something ;)
Title: Re: Canon R5
Post by: Walter Schulz on August 27, 2020, 03:54:26 PM
You may have insights I'm not aware of.
Otherwise trolling.
Title: Re: Canon R5
Post by: Ant123 on August 27, 2020, 06:23:43 PM
Assuming Canon didn't disable the UART port, of course.

At least the connector looks similar to R & RP:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fthumbs2.imagebam.com%2Fc9%2F7c%2F2f%2F876c9f1352504681.jpg&hash=e3ba3ca47ee528804d76f14a6392585f) (http://www.imagebam.com/image/876c9f1352504681)

and there is a hole in the case for it:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fthumbs2.imagebam.com%2F6c%2F63%2Ffa%2Fd4ca971352504673.jpg&hash=feb7f658a0fde2dd43974c93cdd07109) (http://www.imagebam.com/image/d4ca971352504673)

This arc is made of rubber?
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fthumbs2.imagebam.com%2Fd1%2F77%2F22%2F3837c11352504866.jpg&hash=e3e00fa6c7ec9f002be49f8575d2a469) (http://www.imagebam.com/image/3837c11352504866)
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on August 27, 2020, 07:24:44 PM
Proper connector for UART? Accessible when rubber (if any) is removed?
Q: Are those new things or do they exist in other Canon EOS designs?
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on August 27, 2020, 07:39:44 PM
The EOS R & RP have no rubber at the arc.

The rubber is there for a (hopeful) reason on the R5.

The R6 does not have the rubber though :( (https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FRzmdygQ%2Fr6.png&hash=5620b9773373ae041eb7314704df9a49) (https://ibb.co/NZPbSFW)
Title: Re: Canon EOS R5 / R6
Post by: kitor on August 27, 2020, 07:44:16 PM
Yes, I'm almost sure it's UART, same connector as R, RP, and similar location hidden in plain sight (under rubber).

Quote
The EOS R & RP have no rubber at the arc.

Indeed, it's hidden under thumb rubber on R. Similar in RP, just a little higher.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.imgur.com%2FDt8kHcjl.png&hash=1ccd65c37831165b96c2a76bef8d93dc)

And R pinout: https://www.magiclantern.fm/forum/index.php?topic=7531.msg212071#msg212071
and BL dumper: https://www.magiclantern.fm/forum/index.php?topic=22770.msg212069#msg212069

Unfortunately v1.1 means that 1.0 is probably lost for now, considering how many of those were shipped / people wanting to upgrade.
I keep my R v1.0 backup as a relic 8)
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on August 27, 2020, 07:56:33 PM
Thanks! I really wonder why they decided to change design to an easily accessible one (which adds costs). I'm guessing they realized it would reduce costs on the long run. Just a guess, really!
Title: Re: Canon EOS R5 / R6
Post by: kitor on August 27, 2020, 07:59:44 PM
For R6, as there's no teardown yet (?), after a little digging I found this highres render/photo:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.imgur.com%2F7JtVbVFl.jpg&hash=053437d224c9d1f3142fa3aa928bb0e4) (https://i.imgur.com/7JtVbVF.jpg)

I don't see anything that recalls our familiar connector, but there's this FPC 8 pin connector on top left of PCB, which look suspicious to me, with all the testpads around.
Judging from external photos, this would be not accessible without taking whole port cover part of camera case off, so I'm skeptical about this one.
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on August 27, 2020, 08:29:34 PM
You mean this thing?

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FkM2C5FP%2F1.png&hash=fd7369d762467a648f1db2cd2c780a77) (https://imgbb.com/)

It looks too small to be the same thing from the R5's PCB.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2F28dk3wq%2Fr5-r6-PCB.png&hash=522b57c7168f85cded2d7e396892042c) (https://ibb.co/1sTmG3Z)
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on August 27, 2020, 08:50:39 PM
Take a ruler. They are pretty close (y-scale).
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on August 27, 2020, 08:57:45 PM
Unfortunately it looks like you're right... Even the pins line up
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2F6nnGqVt%2F2.png&hash=96d5ebb6a312b505ca881fcdec6faa06) (https://imgbb.com/)

Hopefully it's hidden in plain sight to access like the R and RP.
Title: Re: Canon EOS R5 / R6
Post by: c_joerg on August 28, 2020, 07:52:30 AM
Unfortunately v1.1 means that 1.0 is probably lost for now, considering how many of those were shipped / people wanting to upgrade.
I keep my R v1.0 backup as a relic 8)

I'm not very familiar with ML yet. But from CHDK I know that you can do a dump of the firmware in the camera. Isn't that possible with ML?
If the camera supports Canon Basic, it should be possible ...
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on August 28, 2020, 08:22:34 AM
But it doesn't make life that much easier. You cannot install a ROM dump file like a firmware file just by using Canon's menu ...
Title: Re: Canon EOS R5 / R6
Post by: kitor on August 28, 2020, 12:20:24 PM
@yourboylloyd, Walter - yup, I was talking about this exact connector.

We need to wait for any teardown to see if it's actually used, but I highly doubt. If you check any other one, they have black markings on pcb, showing where ribbon goes. This one has none.
Plus connector just below that is recessed in PCB so ribbon can pass freely. This one is so close to edge that it looks intentional for easy external access.
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on August 28, 2020, 12:49:36 PM
A detailed pic showing an opened HDMI/USB latch should give a hint.
I agree: It doesn't make sense to build it like this without an "easy way out".
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on August 28, 2020, 01:01:00 PM
No hints from what I can see on R6. Unless the screws right there are suspicious. (not to scale, slightly photoshopped to show both rubber ports open).
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2Fp3PtkD9%2F4.png&hash=c3fc6560452e0c8c921506067fe2f097) (https://ibb.co/LCPLsw2)

Edit: The R5 and R6 screws on the right do look a little different though
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on August 28, 2020, 01:07:38 PM
Yes, nothing to be found there. USB- and HDMI-connectors are soldered onto the other side, our UART (or else) should be located slighty to the right (vertically in line with screw?) and well above the top-right screw.
Title: Re: Canon EOS R5 / R6
Post by: kitor on August 28, 2020, 02:07:28 PM
If this trail is correct, it would mean that you need to dismount whole part of case assembly. Looks like 4 screws, unless port cover and entire camera back is one assembly (hopefully not)
What I can tell you is that with patience it was possible to disassemble R to motherboard, without leaving any visible marks ;)
Title: Re: Canon EOS R5 / R6
Post by: ruthenianboy on August 28, 2020, 03:10:48 PM
Aligned R6 connector and PCB photo based on assumption silver pads on PCB are for USB-C and micro HDMI respectively (sorry for low res). Then FFC/FPC connector is evidently hidden above screw if not used for something else.

I am definitelly up for ML developement for R5/R6 without doubts.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FFnjJ7WC%2Fr6-connecors.jpg&hash=e6339f320fd89e39b1a1b136c9cfe4dc) (https://imgbb.com/)
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on August 31, 2020, 11:02:56 PM
So I just got the R6, but unfortunately I noticed that this:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2F0G4ZZvV%2F20200831-135813.jpg&hash=f4b41d21666a20ca7c4e7d6e0af874e2) (https://ibb.co/BCWjjFK)

It looks like Canon probably had a huge liability with ver 1.0.0 and the overheating thing if they're shipping it WITH 1.1.0.

Sucks. Looks like we'll never have the original firmware. Might as well call this one the original.

But anyways, let's look for that bootflag UART port!!

Title: Re: Canon EOS R5 / R6
Post by: Ant123 on September 01, 2020, 06:31:02 AM
But anyways, let's look for that bootflag UART port!!

Have you tried to dump firmware (https://www.magiclantern.fm/forum/index.php?topic=24827.msg230085#msg230085)?
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 01, 2020, 08:56:03 AM
Not yet, will try first thing in the morning! (los angeles time)
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 01, 2020, 07:44:48 PM
There is no ROM dumper for the R6.

I've been getting help from guys on discord. I'm going to try to pop open the side panel (with the hdmi/usb/ port) today and see if I can reach the theorized UART port.
Title: Re: Canon EOS R5 / R6
Post by: kitor on September 01, 2020, 07:55:39 PM
There is no ROM dumper for the R6.

Ant123 linked to test if Canon Basic works. This could lead into dumping rom without opening case.

If not, and you'll find UART, you'd probably be able to enable bootflag through it (if you're brave enough) and then use portable dumper compiled as autoexec.bin - the way we did this with R, after confirming with serial bootloader dump that there are no surprises (IIRC it was identical to M50)

And if you will succeed in any way, remember not to share the rom dump, as it obviously contains Canon's copyrighted code.
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 01, 2020, 08:32:31 PM
Okay sorry. Didn't know that that was a difference. I'll do that now
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 01, 2020, 11:49:20 PM
Okay so I couldn't get EOScard to work. I kept getting the Drive: 1 ERROR Write Failed message so I decided to skip that step after a while and procedded to open up the camera with the help of the guys on discord.

The camera's screws uses a rare "000 phillips screw" that I had to go out and buy a screwdriver set for. I took apart the 4 screws from the side ports and found that the camera actually is accessible on the side like so:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FgTbH0Nb%2Funknown.png&hash=4b42885729a6db65f94cb940dd85e8a3) (https://ibb.co/NjgQ05g)
The green is another screw that I had to take out in order to let that part of plastic come off.

Now when I did that, I was given acess to the board. Unfortunately I tried my hardest but I could not get the entire thing to come off. But it did allow me to see inside where the suspected UART port is:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FLPPdBfp%2F7054f60c9bc74830892c9098ff8aa6d4.jpg&hash=a24e938632d09153ed60a87ea85e6d5c)
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FsQ5cq3R%2F6e0d641e17594f06b61a9532dfafe1ec-1.jpg&hash=1d133d6c6429e304f9b0d51452d40129)(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FQCHnBmg%2F6e0d641e17594f06b61a9532dfafe1ec-1.png&hash=d5b7d7fef61fed072bbd0486d78cd909)
So it looks easy to get to. The problem is that the pins are extremely tiny. I'm going to try to measure the distance between them once I get a good battery for my calipers. But it's so small that I probably won't be able to tell if the pitch was between 0.4mm or 0.3mm or something.

Does anyone have advice on a way to probe the pins? I have an arduino uno, usb host shield,  FTDI USB UART IC ‘FT232RL’ adapter that can run at 3.3V or 5V, and all the accessories that come with an arduino (breadboard, wires etc). But I don't know how to make a connector that could probe pins that are that small.

@names_are_hard and @coon suggested these two (http://www.jst-mfg.com/product/detail_e.php?series=638) links (https://www.mouser.com/Wire-Cable/FFC-FPC-Jumper-Cables/_/N-ad930?P=1z0wx36) to try to make a custom connector. But I have little experience in that.
Title: Re: Canon EOS R5 / R6
Post by: coon on September 02, 2020, 12:48:38 AM
I am going to try out the Jtagulator: http://www.grandideastudio.com/jtagulator/

This device can scan up to 24 pins simultaneously and figures out the pinout of UART or JTAG. You can also set the voltage via software at which the device scans the pins (pretty handy for 1.8V pins).
It is a bit expensive but it is also open source so I will solder it by myself within the next few days.

I will let you let you know once I've tried that out but first the PCB and the parts needs to arrive...
Title: Re: Canon EOS R5 / R6
Post by: Ant123 on September 02, 2020, 06:17:31 AM
Okay so I couldn't get EOScard to work. I kept getting the Drive: 1 ERROR Write Failed message so I decided to skip that step after a while and procedded to open up the camera with the help of the guys on discord.

Good job! But I suggest you to try again with EOScard. Maybe there need to run it as administrator?
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 02, 2020, 06:41:18 AM
I've tried that. I tried FAT16 and FAT32. I even tried running Windows in safe mode. It just won't work. Someone on discord suggested that I should use a smaller card, or that I should somehow trick my CPU into thinking that my card is smaller.

I'm using a 128gb lexar card. I don't have anything smaller nor do I know how to make my card "look smaller."

I don't know how to use Linux, but I do have a Ubuntu VM. I can possibly try to make the card work if I can do it in Linux. I would need a LOT of guidance though.
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 02, 2020, 06:56:09 AM
Canon Basic has a very, very small chance to work on EOS R.  I don't think there are any EOS cams that Canon Basic is known to work on.  UART is the most likely route to dump an R rom.
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 02, 2020, 07:09:44 AM
I'm not sure @names_are_hard. A1ex JUST posted this.
Confirmed working on M50. Very cool!
I have to figure out how to make this work.
Title: Re: Canon EOS R5 / R6
Post by: a1ex on September 02, 2020, 07:14:30 AM
Yeah, today I woke up earlier than usual for some reason, so I've dusted off the M50 and tested the dumper :)

Guess what: the EOS R has some Canon Basic scripts in the firmware, pretty much the same ones as on the M50, so it's definitely worth trying.

If it works, it may provide a way to execute code on newer cameras cameras without hardware hacks, and without us having to break the encryption. Which hopefully keeps us safe(r) from the DMCA as well, but IANAL :)

That is, it might be possible to enable the boot flag directly from a Canon Basic script. At least, the execution context looks relatively safe at first sight (outside LiveView, with GUI locked up).

I'm using a 128gb lexar card. I don't have anything smaller nor do I know how to make my card "look smaller."

You could write our QEMU card image to the card, which will shrink the filesystem to 256MB (FAT16 iirc):

Formatting a larger card at a much lower capacity (e.g. 256MB) does the trick. For example, you can write the SD image that comes with QEMU (https://foss.heptapod.net/magic-lantern/magic-lantern/-/raw/branch/qemu/contrib/qemu/sd.img.xz) to your SD or CF card (follow this guide (https://thepihut.com/blogs/raspberry-pi-tutorials/17789160-backing-up-and-restoring-your-raspberry-pis-sd-card)). This image contains the portable display test (http://www.magiclantern.fm/forum/index.php?topic=14732) and is bootable (so, you can test it in the camera straight away).

To verify it, test the card on any other ML-enabled camera. Once that works, make the card scriptable by following CHDK instructions (EosCard or whatever), then start the camera, go to PLAY mode and press SET. At least, that's what I did on M50.

I can also prepare a scriptable card image with Canon Basic dumper, if needed.
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 02, 2020, 08:03:09 AM
Interesting.  I knew the M50 was hybrid Powershot / EOS, so there it makes sense, but I'm surprised about R!  Maybe they've merged their code bases??  Or maybe all mirrorless use the hybrid code base, that could make sense?

If your suggestions don't work, I've got a Canon Basic disk image confirmed to work on my G15 that I can probably send a script to @yourboylloyd that'll write to a card via Linux VM.
Title: Re: Canon EOS R5 / R6
Post by: kitor on September 02, 2020, 08:06:18 AM
So it looks easy to get to. The problem is that the pins are extremely tiny. I'm going to try to measure the distance between them once I get a good battery for my calipers. But it's so small that I probably won't be able to tell if the pitch was between 0.4mm or 0.3mm or something.

Oh, so looks that my guess was right  8) We just need an confirmation, but the pitch basically confirms that.

Between 0.35 and 0.4mm according to my measurements on R (https://www.magiclantern.fm/forum/index.php?topic=22770.msg212069#msg212069). Thus I'd expect same pinout, as I don't see them having set of identical but differently wired interfaces.

As for EOSCARD, be sure it's not formatted in exfat. I forgot that yesterday when upgrading R to latest FW. Good news is that bootflag persisted, and dumper still works on 1.7.0 (https://www.magiclantern.fm/forum/index.php?topic=22770.msg230323#msg230323)

Guess what: the EOS R has some Canon Basic scripts in the firmware, pretty much the same ones as on the M50, so it's definitely worth trying.
Oh, that's why you asked :) Nope, but I'll try later today.

Interesting.  I knew the M50 was hybrid Powershot / EOS, so there it makes sense, but I'm surprised about R!  Maybe they've merged their code bases??  Or maybe all mirrorless use the hybrid code base, that could make sense?

IIRC R and M50 bootloaders were identical. For the firmware I have no clue.

Title: Re: Canon EOS R5 / R6
Post by: chris_overseas on September 02, 2020, 08:51:08 AM
You could write our QEMU card image to the card, which will shrink the filesystem to 256MB (FAT16 iirc):

To verify it, test the card on any other ML-enabled camera. Once that works, make the card scriptable by following CHDK instructions (EosCard or whatever), then start the camera, go to PLAY mode and press SET. At least, that's what I did on M50.

I can also prepare a scriptable card image with Canon Basic dumper, if needed.

I have an R5 here and just tried to get this working without luck so far. I did the following:
Unfortunately nothing happens. Have I made a mistake or are we out of luck? Maybe there's a different combination required to trigger the script?
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 02, 2020, 08:54:10 AM

To verify it, test the card on any other ML-enabled camera.

Unfortunately I sold my t3i and all I have is a CFcardaccepting 5d2. I won't have a way to verify.
I can also prepare a scriptable card image with Canon Basic dumper, if needed.

That would be awesome probably. Especially since we're in two different time zones and it would be harder to communicate (bedtime was 2 hours ago for me :D ).

I actually do want to learn how to do it though so I'll probably follow your instructions anyway.
Title: Re: Canon EOS R5 / R6
Post by: kitor on September 02, 2020, 10:16:34 AM
Canon basic dumper works on R! Not sure if without bootflag enabled too.

I created the files with Unix line endings (LF only). I made card by using EOScard, with only option "script" selected.
Both files (extend.m and script.req) you can download here: https://kitor.pl/eos_r/cbasic_dumper.zip

Of course credits for dumper goes to @srsa as I took his code directly from this post (https://www.magiclantern.fm/forum/index.php?topic=23296.msg227190#msg227190)

After I put card into camera, I went into playback mode, pressed Q/Set button and red light turned on. A minute later it was done, ROM.txt was saved to card root!
Title: Re: Canon EOS R5 / R6
Post by: c_joerg on September 02, 2020, 11:06:42 AM
Unfortunately nothing happens. Have I made a mistake or are we out of luck? Maybe there's a different combination required to trigger the script?
Sure the SD Card is not exfat?
You need FAT.
Title: Re: Canon EOS R5 / R6
Post by: chris_overseas on September 02, 2020, 11:33:55 AM
Sure the SD Card is not exfat?
You need FAT.

Yes, it's FAT
Title: Re: Canon EOS R5 / R6
Post by: c_joerg on September 02, 2020, 03:01:36 PM
On my M100, the basic scripts only start every second time (on average).
There has to be some kind of temporal behavior.
Title: Re: Canon EOS R5 / R6
Post by: srsa on September 02, 2020, 04:34:57 PM
The R5 and R6 have two card slots. In the firmwares I've seen, the extend.m script is expected to be on drive B: . Single card models seem to map their SD slot to B:
Of course, it's possible that scripting is not available on these models, or, they may have changed something to hinder 3rd party research.

@yourboylloyd
The UART likely uses 1.8V signalling level, your 3.3V and 5V adapters won't work on that. @kitor can probably recommend a compatible hw.

On my M100, the basic scripts only start every second time (on average).
I don't remember seeing that on my cameras. If the script card is prepared correctly, the script can be started reliably.
Title: Re: Canon EOS R5 / R6
Post by: kitor on September 02, 2020, 04:52:40 PM
Quote
The UART likely uses 1.8V signalling level, your 3.3V and 5V adapters won't work on that. @kitor can probably recommend a compatible hw.

I did simple voltage divider on TX of my usual 3v3 UART, RX was able to pick 1v8 leves fine. Judging by old photo, I used my CH341A based UART:
https://twitter.com/_kitor/status/1095729715284008960

Quote
or, they may have changed something to hinder 3rd party research.
That's why I updated R to latest 1.7 - we know that at least there it wasn't removed.
Title: Re: Canon EOS R5 / R6
Post by: a1ex on September 03, 2020, 07:35:22 AM
Does anyone have advice on a way to probe the pins? I have an arduino uno, usb host shield,  FTDI USB UART IC ‘FT232RL’ adapter that can run at 3.3V or 5V, and all the accessories that come with an arduino (breadboard, wires etc). But I don't know how to make a connector that could probe pins that are that small.

I've got the FT232RL adapter, and can confirm it can listen to 1.8V signals via its RX pin, with the jumper set to 3.3V. That's the easiest way to probe for the UART, in my opinion:
- connect the GND pin between FT232 and camera
- use the FT232 RX pin to probe around, while watching the Arduino serial monitor (a needle could be handy)

Expecting a bunch of messages right after camera startup, but also while in LiveView, for example.

TLDR: initial probing can be done with only the GND and RX pins from the FT232 adapter.

For sending messages to the camera, via the FT232 TX pin, you will need a voltage divider, as suggested by Kitor. When you reach this step, you may want to join the chat room :D
Title: Re: Canon EOS R5 / R6
Post by: jack001214 on September 03, 2020, 03:16:40 PM
I am going to try out the Jtagulator: http://www.grandideastudio.com/jtagulator/

This device can scan up to 24 pins simultaneously and figures out the pinout of UART or JTAG. You can also set the voltage via software at which the device scans the pins (pretty handy for 1.8V pins).
It is a bit expensive but it is also open source so I will solder it by myself within the next few days.

I will let you let you know once I've tried that out but first the PCB and the parts needs to arrive...
What about the connectors and the FPC cable itself? any ideas?
Title: Re: Canon EOS R5 / R6
Post by: kitor on September 03, 2020, 03:56:30 PM
I went the hard way with R, and probed testpoints with needle soldered to wire, that was connected to UART TX. Yes, this required removing whole back case.
Later, I used 0.5mm pitch FPC, just removed all unused pins, and tried to slightly shrink those needed ones so they won't short nearby pins.

You can deal with GND by just taking it from any outside connector, like USB case - instead of having it on ribbon. It's easier to deal with two instead of three pins.

Anyway, I'd try Canon Basic again. No disassembly needed, and it's confirmed to work on R and RP... so there's a high hope getting there without disassembly. Just check in both slots, as it was mentioned that it needs to be B:\, which we have no idea how maps two slots to letters in R5/R6.

Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 04, 2020, 03:20:42 AM
I have an R5 here and just tried to get this working without luck so far. I did the following:
  • Low level formatted a 128GB SD card in the R5
  • On my PC I then wrote the QEMU SD card image to it using Win32 Disk Imager, verified the card was showing as 256MB
  • Checked the card worked as expected in my 5D3
  • Used EOScard 1.40 to set the card as scriptable (by ticking SCRIPT, unticking EOS_DEVELOP and BOOTDISK, then choosing "Save")
  • Created a script.req file containing the string "for DC_scriptdisk"
  • Created an extend.m file containing Hello World (https://chdk.fandom.com/wiki/Canon_Basic/Scripts/HelloWorld2)
  • Created an extend.m file containing the dumper script
  • Put the card in the camera, powered up, pressed Play followed by Set (also tried Play followed by Q)
Unfortunately nothing happens.

I tried everything on the R6. I can confirm this isn't working either.

My card is 256mb. I used EOSCARD to make sure it was scriptable. Pressed PLAY and then SET = Nothing. Pull Out battery. Pressed PLAY and then Q = Nothing. Repeat for PLAY and then (EVERY OTHER BUTTON ON THE CAMERA) = Nothing.

I tried Card slot 1 and then card Slot 2.

Maybe I should try having 2 cards with the same script on them in both slots? Any ideas?

Edit: I just counted and found that there is a total of 26 buttons (including dials and joystick directions) on the R6. Assuming that there are 2 input combinations to start the script, there are a possible 26x26 = 676 combinations that are possible to be the solution XD

If no one else has a better idea, I'll get to fingering.

Edit 2:

edit:
It turned out that there are better ways to dump ROM content - I can tell what they are if anyone is interested.

Does anyone know what that "better way" is? I sent srsa a PM asking about it.
Title: Re: Canon EOS R5 / R6
Post by: c_joerg on September 04, 2020, 07:38:29 AM
Edit: I just counted and found that there is a total of 26 buttons (including dials and joystick directions) on the R6. Assuming that there are 2 input combinations to start the script, there are a possible 26x26 = 676 combinations that are possible to be the solution XD

Or a combinaton with touchscreen  ;)

Quote
https://chdk.fandom.com/wiki/Canon_Basic/Card_Setup
Some touchscreen cameras run the script when the focus lever is turned to the left.
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 04, 2020, 08:57:36 AM
Or a combinaton with touchscreen  ;)
You gotta be kidding me... I didn't even think of that.
Quote
Some touchscreen cameras run the script when the focus lever is turned to the left.
What does that even meannn??? A focus lever?? Do I have to focus my lens at infinity? Or close focus? Does it have to be a canon lens? What if the lens is manual focus?

Whatever I'll try whatever I think it's saying and report back.

Edit: I tried focusing at close focus, half way, infinity, infinty and beyond. Multiple lenses. Multiple cardslots. The SET button. The Q button. Nothing.
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 04, 2020, 09:25:09 AM
You may be not aware that most PowerShot code-based cams don't have something like a focus ring but rely solely on remote focus control and this hack srsa most kindly introduced to us is born in the CHDK realm...

And: No, I don't have any idea if this focus thingy applies to R-cameras and (in case it does) how to handle this requirement. ;-) And I suspect he's acturally referring to "zoom lever".
Title: Re: Canon EOS R5 / R6
Post by: srsa on September 04, 2020, 05:01:32 PM
Does anyone know what that "better way" is? I sent srsa a PM asking about it.
Replying here.
I added that edit before making the new thread about scripting. The 'better way' is nothing more than the two short dumper scripts in the first post of the new thread.

As for the lack of success running scripts on R5/R6, I still tend to think that Canon has changed some details in their script related code or even decided to remove it altogether.
So, IMO, the current way to go ahead is the UART.
Title: Re: Canon EOS R5 / R6
Post by: garry23 on September 04, 2020, 05:05:04 PM
 :)

https://www.diyphotography.net/take-a-peek-inside-the-canon-eos-r6-mirrorless-camera-in-this-disassembly-and-teardown/
Title: Re: Canon EOS R5 / R6
Post by: garry23 on September 04, 2020, 07:03:36 PM
 :)

https://petapixel.com/2020/09/04/teardown-reveals-overheating-timer-chip-inside-the-canon-eos-r6/
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 05, 2020, 04:15:10 AM
CANON BASIC DUMPER WORKS ON THE R6!!!! I'VE SUCESSFULLY RAN THE SCRIPT ON THE R6 Firmware 1.1.0

First:

I borrowed my friend's M50. Using Kitor's card image, I tried to run the same script on the 128gb SDXC card that I used for my R6 trials. I found that it wasn't working. So I knew something was up.

Second:

I went to walgreens and bought a $20 16GB SDHC-I card (why was that so expensive for 16 gigabytes?? I mean c'mon!) and I tried to run the script on the M50 again using that card. It worked on the M50!! I was given a boot00.bin file

So I figured it had work on the R6. I deleted the bin file and tried it on my R6. I put the SD card in the second card slot (the one labled 2). Turned it on. Pressed PLAY and then SET. Then the card LED turned RED and Voila! boot00.bin file!!

TLDR: SDXC cards don't work for some reason. The script also DOES NOT WORK in Slot 1 at all. Use SDHC cards to dump rom images. Thanks to Ant123 and Walter for the idea to use a different card! And Kitor for the image.

Edit: I ran the SaveAllRomImageToFile() script that was in srsa's example scripts and I was left with two files. gang100.bin (65,536KB) and gang200.bin (32,768KB).
Title: Re: Canon EOS R5 / R6
Post by: yokashin on September 05, 2020, 06:01:25 AM
Congratulations!
 :)
Title: Re: Canon EOS R5 / R6
Post by: chris_overseas on September 05, 2020, 06:36:05 AM
Very nice - I can confirm it works on the R5 too! I had been using an SDXC card with my previous attempts, worked fine when I tried it with an SDHC. Same combination to activate it, PLAY then SET.
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 05, 2020, 06:42:46 AM
This is awesome!

Does anyone have any idea why SDXC wouldn't work?
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 05, 2020, 07:06:39 AM
It's easy to guess a bunch of reasons why, but it doesn't really matter.

Since SDXC tend to be larger cards, I'd like to test the theory that it's not SDXC, but really the size of the card that matters.  Apparently there are 32GB SDXC cards, so if 64GB SDHC can be shown to work, and 32GB SDXC shown to not work, on the same cam, then it's probably SDXC being the problem.  Again, doing this test isn't important - we know small-ish SDHC works, and that's easy to do.
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 05, 2020, 07:10:43 AM
There is a mixup of terms.
SDHC is limited to card sizes up to 32 GByte. Any larger card is - by definition - SDXC.
I think you meant to talk about partition size and want to experiment with that.
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 05, 2020, 07:14:53 AM
No, I was just making a bad assumption, I thought SDXC was a speed / bus change :)

Could easily be some size check then, if it's done on the disk, not the partition.  Could still test a 32GB version of SDHC and SDXC.
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 05, 2020, 07:25:22 AM
Good luck finding a 32 GB SDXC!  8)
https://www.sdcard.org/consumers/choices/file_system/index.html
I don't say they don't exist ... https://www.dpreview.com/articles/0658120146/pretecsdxc
just hard to find and old GByte vs. GiByte mixup doesn't really help ...
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 05, 2020, 07:33:21 AM
Probably easier to reverse the rom to find out the reason :)
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 05, 2020, 08:17:37 AM
Okay, all this dumping was a lot of fun!
Where to go now? There are some people looking for a solution to deal with R5/R6's timers. And srsa opened the way to run a command set by just pressing 2 keys.
Easy to poke some unwanted registers, too.
Title: Re: Canon EOS R5 / R6
Post by: c_joerg on September 05, 2020, 08:21:41 AM
Canon Basic can do a lot more as you can see from these tread.
https://chdk.setepontos.com/index.php?topic=13522.0

This is a M100 snapshot of a Canon Basic Script that I got from srsa.
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Flive.staticflickr.com%2F7829%2F46750428704_4f3a71e117_c.jpg&hash=900cda153d4390e10f76511bb58ce18f) (https://flic.kr/p/2eebaGd)


Perhaps this could also be used to make the temperatures of the R5 visible
Title: Re: Canon EOS R5 / R6
Post by: Ant123 on September 05, 2020, 08:28:04 AM
Probably easier to reverse the rom to find out the reason :)

I assume that on SDXC cards the system uses a separate driver / library for EXFAT, which is loaded after checking the card for a signature.
I have the opposite situation with the EOS M3: I would not want to buy a SDXC card if it does not work with a CHDK.
Perhaps the same situation will be with ML when (and if) it will be implemented for new cameras.
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 05, 2020, 08:30:47 AM
Perhaps this could also be used to make the temperatures of the R5 visible

What are you waiting for? The string in Canon's code is most likely EFIC_TEMP and there is a script to decompile ROM contents*. I don't have the time right now to do that. I'm not a programmer but this looks like an easy task.

*Dang! It is not yet confirmed to work with Digic X! a1ex?
Title: Re: Canon EOS R5 / R6
Post by: Ant123 on September 05, 2020, 08:47:53 AM
Walter Schulz
You should understand that EOS M100 uses PowerShot based firmware and Canon Basic command set could be different for EOS R. Finding a string in a ROM dump doesn't mean that it can be easily accessed with Canon Basic, especially without testing it on a real camera.
Title: Re: Canon EOS R5 / R6
Post by: kitor on September 05, 2020, 10:50:41 AM
I have a feeling that with R5 Canon may have created the spark that this project needed to move forward  :)
Quick break in that we achieved when topic is hot may help that.

Looks that R5 may really become next 5D2.
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 05, 2020, 01:56:54 PM
I found crazy that the RTC is a dedicated chip place in the middle of nothing and so easy to access.
I have a simple question.
The RTC holds the time and day and can be access by the I2C bus. Either to program the time and the alarm and countdown.
But when a alarm is set up, Pin 6 is the IRQ line. Usually, the IRQ adk the processor to check what is happening by reading the I2C.

Is simply cutting the pin 6 signal enough for not triggering the IRQ signal and shoot forever? (and keep time of the day and date active?)

You need to have this pin a High level with a pull up resistor linked to pin 8 if it's not already the case (low level is IRQ Active)
Title: Re: Canon EOS R5 / R6
Post by: 71m363nd3r on September 05, 2020, 04:11:10 PM
I found crazy that the RTC is a dedicated chip place in the middle of nothing and so easy to access.
I have a simple question.
The RTC holds the time and day and can be access by the I2C bus. Either to program the time and the alarm and countdown.
But when a alarm is set up, Pin 6 is the IRQ line. Usually, the IRQ adk the processor to check what is happening by reading the I2C.

Is simply cutting the pin 6 signal enough for not triggering the IRQ signal and shoot forever? (and keep time of the day and date active?)

You need to have this pin a High level with a pull up resistor linked to pin 8 if it's not already the case (low level is IRQ Active)

Thanks for the info & your time that you invested.
Title: Re: Canon EOS R5 / R6
Post by: Ant123 on September 05, 2020, 04:13:06 PM
Is simply cutting the pin 6 signal enough for not triggering the IRQ signal and shoot forever? (and keep time of the day and date active?)

If it was your question my answer is "no".
The processor has enough timers to count the heat and RTC is needed only when camera is powered off.
On EOS R cameras RTC probably can be used to wake up the camera (https://chdk.setepontos.com/index.php?topic=12542.msg137085#msg137085).
Anyway cutting PCB lines is bad idea. It's better to wait for a software solution.
Title: Re: Canon EOS R5 / R6
Post by: stillinsane on September 05, 2020, 07:09:48 PM
If cutting the lines would work I would still mod the Hardware.
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 06, 2020, 04:24:41 AM
Well, it may be a bit more complicated.
If you put some fact together:
-Removing the battery cell reset the fake overheat timer, reset the time and date and few shooting parameters, but keep others as custom functions. So a memory is also powered with this battery. This is very common and few RTC chip also have internal memory to do 2 functions in one (RTC+limited amount of parameters)
This RX8130 do not have a memory register. So it have to be another chip somewhere to do so.

-The amount of chip powered by the 3.3V cell have to be as limited as possible and more likely close to the cell area. This is to keep backup, the power usage should be as tiny as possible. It uses 300 Nano Ampere in sleep mode as reference.

-If it was only a countdown with an IRQ, removing the battery during during the recording and putting back should not affect the countdown. The counter should keep running as soon as the "power good" is restored. So again, it points out to another memory that hold the counter flag.

I still believe a solution as magic lantern is the best way to go.
Either the counter inside the RTC is used for the fake overheat warning, Either it's just a RTC for the time and date.
A chip with a memory along the power line coming from the cell battery is more likely to have a register that can be access and changed by a side software. This software is extremely simple and write time to time a 0 flag in the fake overheat register.

The fake overheat timer starts during the full power state and write a flag when a normal internal timer is reached. This is more likely than using a specific chip for that. Only because the flag is written at the end of the count that removing the battery during shooting allows to restart. So finding this flag and overwriting it will solve this.
I don't see a use of this RTC for overheating purpose as it have very limited alarm feature. (The overheating have 2 steps for example)
I really see a register powered by the 3.3V, so a unique chip alone, not part of any large IC, that holds the key.
That should be also easier to access as it's a dedicated chip, ore likely from a generic brand more than from Canon, so the way to access it should be in a pdf somehow.
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 06, 2020, 06:16:36 AM
Sorry that I can't modify my post.

Ok, here are new thouht after thinking a bit.

Something is bothering me is the recovery time.
Even without regular camera battery, or by pushing the time.
The recovery time is not reduced.

If it was just a flag to a memory that start to count, it will not be able to know how long the camera was actually off.
It have to be a counter, not just a date stamp difference.
This overheat counter IS inside this chip for sure. cause it can't hold 2 different date and the internal counter are quite limited.

Either the current overheat time is written inside a eeprom, and so compare on boot, either there is a timer that keep running even without battery.
After 2 hour of "fake cool down"; the camera is powering again and check the value of this counter. If it reached the end, you can go again. If not, you have to wait.
The second possibility is that the camera compare the time on boot and do a simple subtraction to know if the elapsed time is enough. The various test kind of shows that it is not working.

To make sure about the second possibility and twist it a bit
I would love someone to do a simple test.
Put the camera on overheat and lock (after 20mn recording video) and keep the battery door open with the scerw hack or use dumb battery the entire time
Change the date  or time to move it to the next day.
Now, try 2 different things:

Remove the camera battery with the drop system. Is restarting check the new day? (But not the flag?)

Or simple turn off the camera, remove the battery and start again. is the second restart is able to do the math between both time? (So the overheat time is stored on eeprom/a counter is runnin during no battery time)

Does it makes sense to test this?
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 06, 2020, 06:53:54 AM
I would love someone to do a simple test.
Put the camera on overheat and lock (after 20mn recording video) and keep the battery door open with the scerw hack or use dumb battery the entire time
Change the date  or time to move it to the next day.
Now, try 2 different things:

Remove the camera battery with the drop system. Is restarting check the new day? (But not the flag?)

Or simple turn off the camera, remove the battery and start again. is the second restart is able to do the math between both time? (So the overheat time is stored on eeprom/a counter is runnin during no battery time)

Does it makes sense to test this?

I'll do it now on my R6 and a dummy battery.
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 06, 2020, 08:44:51 AM
GOOD NEWS!!

Results:

TLDR; basically, unlimited record time. All footage saved. If camera is overheating, change date +1 day and immediately pull dummy battery to reset overheating timer.

Thanks visionrouge(dot)net for the idea! This makes using this camera extremely worry free professionally for me. I wonder if we can make a script that can emulate those steps to trick the overheating timer. I encourage someone else to replicate this test on R6 and R5

*It must be noted that I have bootflag enabled on my EOS R6. Not sure if it means anything in relation to this test.

** It also must be noted that the files were split into 4GB files. I'm not sure if that's the default setting because I've never recorded that long. I realized that I formatted my 128GB card as FAT32 instead of exFAT so this makes sense.
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 06, 2020, 08:56:51 AM
I'm so happy!
Thanks for trying.

YES!!!!
Please quote my company for such! :) :) :) :) :)
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 06, 2020, 09:33:42 AM
So, the camera DO a  simple time difference between the actual last overheat and the actual time, but as you drop the battery, the time change bit is not read.
The boot just read the time present in the RTC at this time.

I guess the software engineer have applied a filter to not do a time difference if the day/time is changed, but this is bypassed by this kind of boot.

It also shows the RTC do not run a overheat timer when camera is off.

The compilation of finding are online  https://www.visionrouge.net/canon-r5-overheating-hack-solved/ (please click on the advertising at the botom to offer me 5 cent, I may be able to buy a new SD card !)
(And getting updated right now with pictures and all)
I'm so excited to find such loophole.
We need more R5 test with regular card, but I don't think there are relationship between this and the drop power boot.

I love you all

Title: Re: Canon EOS R5 / R6
Post by: a1ex on September 06, 2020, 03:26:24 PM
Cool hack - it's the clearest proof the "overheating" is timer-based, if you ask me.

As I said: IMO this would be *the* opportunity to make transition to pay-for-ML-feature-development work.

Well, this particular hack is easy enough to automate - I wouldn't be surprised if somebody comes up with a one-click version within the next few days or weeks (also mentioned on Twitter (https://twitter.com/autoexec_bin/status/1302579709683826694)). Motivation is high in the R5/R6 user community - much higher than for porting ML on 5D4, EOS R and the like, in my opinion. So, while it's definitely a low-hanging fruit with high rewards, I don't see anyone paying for a slightly more polished version of this hack. A free one will very likely appear sooner or later, without our involvement.

BTW - I feel a lot safer knowing this hack was discovered by third parties - even if it was documented on our forum. There's no single person behind it - all of the previous iterations paved the way to this version of the hack ("standing on the shoulders of giants"), and I'm pretty sure it will be further refined by the community.

On the other hand, this "overheating" thingie caused quite a stir on the internet, which ended up drawing some of the attention (https://twitter.com/_kitor/status/1302211871651622913) towards our project. That's probably "exploitable" in the sense of "pay-for-development", but primarily for the other models - if I'm not mistaken, the R5 already records 8K raw video (but I haven't touched this camera, so I might be wrong), so the motivation for our enhancements on this model is probably low, besides the overheating timer hack.

Now, back to my (covid-related) research :)
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 06, 2020, 04:04:59 PM
Cool hack - it's the clearest proof the "overheating" is timer-based, if you ask me.

Well, this particular hack is easy enough to automate - I wouldn't be surprised if somebody comes up with a one-click version within the next few days or weeks (also mentioned on Twitter (https://twitter.com/autoexec_bin/status/1302579709683826694)). Motivation is high in the R5/R6 user community - much higher than for porting ML on 5D4, EOS R and the like, in my opinion. So, while it's definitely a low-hanging fruit with high rewards, I don't see anyone paying for a slightly more polished version of this hack. A free one will very likely appear sooner or later, without our involvement.

BTW - I feel a lot safer knowing this hack was discovered by third parties - even if it was documented on our forum. There's no single person behind it - all of the previous iterations paved the way to this version of the hack ("standing on the shoulders of giants"), and I'm pretty sure it will be further refined by the community.

Now, back to my (covid-related) research :)

Automation of the time change would be simple - only requires an HTTP GET and PUT over WiFi to "http://<camera ip>:8080/ccapi/ver100/functions/datetime". See my Canomate CCAPI utility at Canomate HomePage (https://www.testcams.com/canomate/) and Canomate GitHub Repository (https://github.com/horshack-dpreview/Canomate) for examples on usage. Canomate's SyncDateTime (https://github.com/horshack-dpreview/Canomate/blob/5123b13e28ca94de727a0ecc252ac456fbc06ffd/canomate.py#L923) does this.

Automation of the battery pull word require scripting to a network-enabled power switch, like a TP-Link Kasa Smart Plug (https://www.amazon.com/TP-LINK-HS103P2-Required-Google-Assistant/dp/B07B8W2KHZ), connected to a dummy battery (https://www.amazon.com/Adapter-Gonine-Coupler-Battery-Replacement/dp/B01D68YXOQ) inside the camera.

Both could be implemented via a simple Smartphone app.
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 06, 2020, 04:14:57 PM
Automation of the time change would be simple - only requires an HTTP GET and PUT over WiFi to "http://<camera ip>:8080/ccapi/ver100/functions/datetime". See my Canomate CCAPI utility at Canomate HomePage (https://www.testcams.com/canomate/) and Canomate GitHub Repository (https://github.com/horshack-dpreview/Canomate) for examples on usage. Canomate's "SyncDateTime" does this.

Automation of the battery pull word require scripting to a network-enabled power switch, like a TP-Link Kasa Smart Plug (https://www.amazon.com/TP-LINK-HS103P2-Required-Google-Assistant/dp/B07B8W2KHZ), connected to a dummy battery (https://www.amazon.com/Adapter-Gonine-Coupler-Battery-Replacement/dp/B01D68YXOQ) inside the camera.

Both could be implemented via a simple Smartphone app.


You can go further.
When overheating.
Put the time front one hour. Do a battery drop.
The overheat timer is gone, so you need to write this flag down by turning off the camera.
When done, you can now change back the real time. As the flag is gone, there is no more check on "how long it is before cooling"
If you know how long each step are taking and add the exact same amount of time, you may actually always record with the real time.

The reset sequence can include a go back in time sequence...
Title: Re: Canon EOS R5 / R6
Post by: kaco on September 06, 2020, 04:16:03 PM
So, while it's definitely a low-hanging fruit with high rewards, I don't see anyone paying for a slightly more polished version of this hack. A free one will very likely appear sooner or later, without our involvement.

a1ex speaking from my experience, I think there are enough users who would be willing to pay for the development. For porting ML to 5Dm4 or even R5/R6. And this would be really the best time for the switch -- there's a lot of interest around R5/R6. And it's not just the timers...

I've been professionally shooting ML raw with 5D3 for years. The 5x3 48p is dated, but there are still not many other options. Blackmagic has BRAW (not raw), cropped sensors, and plastic bodies. Sigma FP is nice but quite limited and the fullHD line-skipped mode is "meh"... Even if I would be willing to spend 10k+ on a Cinema Camera, the C300mk3 is still S35 only. And the C500mk2 is way out of budget of independent filmmakers and high-end documentarists like me.

There really are not many options that are full-frame with raw, sharp full HD and at least 48p. Not to mention that amazing UI of ML.
Recent developments with cropped 4k raw and gray preview are nice, but not so easy to use in a real-world for some serious work.

Maybe it's just me, but I really think focusing on the high-end camera will make much more sense. People who use EOS M are lowe-end hobbyists who most of them already switched to some other cheap cameras. If you will be able to port ML to 5Dmk4 (which is 1500 eur used) every film student and indie artist will use it.
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 06, 2020, 07:31:06 PM
The Canon 5d4 is surpassed by the sigma fp at least for me, I sold the 5dmk3 for the sigma.

I would be most interested in the r5 with magic lantern, because evf and tilting screen and usable autofocus makes it a smaller package not needing extra an extra monitor or evf.

What I would use magic lantern for is writing lens metadata for manual focus lenses and the recording timer automated.
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 06, 2020, 07:42:28 PM
So, while it's definitely a low-hanging fruit with high rewards, I don't see anyone paying for a slightly more polished version of this hack. A free one will very likely appear sooner or later, without our involvement.

I wrote that way back in the days when ML was the only software offering a solution. Good old days, feels like yesterday ... wait ... It was kind of yesterday, wasn't it?

Totally agree! Doesn't make sense to put a price tag on some script.
But that wasn't my intention. ML going payware? Nope but I consider this a good starting point for something like Patreon.
Are there "enough" contributors like kaco wrote? Definitely don't know!
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 06, 2020, 07:48:37 PM
Here's a Canomate (https://www.testcams.com/canomate/) script for automatically changing the camera's clock to +1 day and then back.

Save the contents of the following to a file named DateTimeHack.txt:
Code: [Select]
PrintCameraInfo
SyncDateTime skewsecs=86400
PrintMessageToLog message="Pull battery NOW, wait a few seconds, put battery back in, wait 10 seconds, then press <ENTER>"
WaitForEnterKeyToContinue beep=1
SyncDateTime

To run the script: canomate.py --ip=<camera's IP address> --opfile=DateTimeHack.txt

Output:
Code: [Select]
canomate v0.02 - Automation Utility for Canon cameras (uses Canon Control API via WiFi)
Copyright (c) Horshack, System Time: 09/06/20 10:43:13, Py: 3.8.0, OS: Windows

PrintCameraInfo: Model: Canon EOS RP, S/N: XXXXXXXXXXXX, Firmware: 1.5.0
SyncDateTime: Changed camera time from "Sun, 06 Sep 2020 10:43:13 -0800 DST" to "Mon, 07 Sep 2020 10:43:13 -0800 DST"
PrintMessageToLog: Pull battery NOW, wait a few seconds, put battery back in, wait 10 seconds, then press <ENTER>
WaitForEnterKeyToContinue: Press <Enter> to continue...
SyncDateTime: Changed camera time from "Mon, 07 Sep 2020 10:43:15 -0800 DST" to "Sun, 06 Sep 2020 10:43:16 -0800 DST"
>>>> canomate session over (exit=0), logs at "C:\develop\canomate\canomate-appdata"

I tested this on my Canon RP.

I tried writing a quick JavaScript app that does this in a browser (so we can use portable devices like smartphones) but the Cross-Origin Resource Sharing (CORS) (https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) protections prevents the code from performing requests to the camera. Unfortunately the camera is not sending a permissible Access-Control-Allow-Origin in the HTTP header. A developer has already requested a change here: Could a CORS policy be implemented for the CCAPI? (https://developers.canon-europe.com/developers/s/question/0D50J00005vU25E/could-a-cors-policy-be-implemented-for-the-ccapi). This would have to be written as a Smartphone app instead. Shouldn't be too hard for an enterprising individual  :)
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 06, 2020, 08:44:04 PM
CORS is a client side check.  You can disable / fake it with a browser plugin, or a proxy.
https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf?hl=en

Not a great suggestion long-term as it will decrease your security if you forget and leave it active.  Might work for testing.
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 06, 2020, 08:47:43 PM
CORS is a client side check.  You can disable / fake it with a browser plugin, or a proxy.
https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf?hl=en

Not a great suggestion long-term as it will decrease your security if you forget and leave it active.  Might work for testing.

Not viable for mobile solutions since extensions aren't allowed on those platforms. I'll be testing my Canomate with Pythonista (http://omz-software.com/pythonista/) later today.
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 06, 2020, 09:03:40 PM
True for iPhone, but extensions are allowed on Android.  If you were determined you could also VPN through a MITM proxy to modify the response header to strip CORS, that would work on any phone supporting VPN.  I suspect not a very practical solution for the intended audience :)
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 06, 2020, 09:16:49 PM
True for iPhone, but extensions are allowed on Android.  If you were determined you could also VPN through a MITM proxy to modify the response header to strip CORS, that would work on any phone supporting VPN.  I suspect not a very practical solution for the intended audience :)

Thanks. I can look into Android since I run both iOS and Android. An internet-based MITM proxy wouldn't work since it wont have access to the local phone's IP (unless the port is forwarded through the router and that wont work when away from home network). Running MITM on the phone would work but then you're writing an app anyway to do it. Running MITM on a computer on the local network would work but again not viable when not on home network.

I just tried Canomate with pythonista and it worked on both my iPad and iPhone. Bit of a hassle getting the .py files onto the phone (uploaded them to my Google Drive, then downloaded from Google Drive to Files app, then opened in pythonista). Here's a screenshot from the phone.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fphotos.smugmug.com%2Fphotos%2Fi-gBHnSMn%2F1%2Fdde50d60%2FO%2Fi-gBHnSMn.png&hash=76f0199ac5ccbe34988a030f06b80645)
Title: Re: Canon EOS R5 / R6
Post by: Dmytro_ua on September 06, 2020, 10:11:16 PM
What I would use magic lantern for is writing lens metadata for manual focus lenses and the recording timer automated.

It would also be nice to know the real temperature if you disable a "safety timer".
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 06, 2020, 10:50:44 PM
Yes for sure, it would be good to know when the camera is really overheating based on the sensor and not on the timer.
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 06, 2020, 11:21:57 PM
@horshack - a VPN will look like the same network, you get an additional network interface, with the phone and vpn endpoint being in the same subnet.  Everything is tunneled, so you will see this as one hop, you won't see ISP or phone provider in the middle.  Wireguard or OpenVPN are both free and available on most everything.  Wireguard is supposed to be easier to configure.  You can then configure the VPN to provide DNS, with that DNS server that you control routing whatever names you want to whatever IPs - so you can make the proxy transparent with the only config needed on the phone being the VPN.  Of course, you're trusting the VPN an awful lot!

It looks like your Python works and it's probably easier for people to use.
Title: Re: Canon EOS R5 / R6
Post by: dellfonic on September 07, 2020, 01:41:38 AM
No need for dummy battery boys and girls, just recorded in 8K IPB until the overheating warning came on. Changed the day +1 and pulled the battery. Voila! Canon Cripple Clock obliterated! Great work ppl!
Title: Re: Canon EOS R5 / R6
Post by: EOSHD on September 07, 2020, 02:13:36 AM
I certainly think there would be plenty of interest in ML for the EOS R5 and R6.

The overheating timer patch is the big thing, but the file sizes in 8K RAW aren't really practical and not many people need 8K... So would be good to see what else RAW-related might be hidden in that frame buffer... 4K RAW or 3K crop perhaps....the write speeds to CFexpress would very likely allow 10bit lossless RAW in 4K! And to enable ALL-I and DCI 4K on R6 would be tremendous! And temps monitor in real-time, to check for any dangerous ones on hot days.

Well done to all testers and contributors on here, it's amazing the progress already.

I think ML should invest some Patreon money in useful hardware, non-profit organisation but able to invest in their mission. I'd happily support any Patreon.

And of course I want to play Arkanoid on my EOS R5 ;)
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 07, 2020, 03:23:32 AM
It would also be nice to know the real temperature if you disable a "safety timer".

There is a next step on this hack. I should work, but need one beta tester to be sure.

Follow the previous procedure to push forward the day.
When you see that the "overheat logo" is gone; turn off the camera using power button.
At this time, the "overheat flag" is now written into memory.
Turn back on the power with the power button. The camera is now booting from a regular boot.
So if you have no warning here, the camera is absolute fine with temperature. This not a "special boot" anymore
And the beauty of it, you can now push back the day as the actual day.
So with this extra step, all your clip are even at the right time.

Can someone test this ? Thanks
I will update on visionrouge.net if so.
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 07, 2020, 05:00:29 AM
@horshack - a VPN will look like the same network, you get an additional network interface, with the phone and vpn endpoint being in the same subnet.  Everything is tunneled, so you will see this as one hop, you won't see ISP or phone provider in the middle.  Wireguard or OpenVPN are both free and available on most everything.  Wireguard is supposed to be easier to configure.  You can then configure the VPN to provide DNS, with that DNS server that you control routing whatever names you want to whatever IPs - so you can make the proxy transparent with the only config needed on the phone being the VPN.  Of course, you're trusting the VPN an awful lot!

It looks like your Python works and it's probably easier for people to use.

Thanks. That's probably a bit too much to ask of somebody as a way around the CORS. Btw, how does that create a path between an internet-based CORS proxy and the camera?
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 07, 2020, 05:03:43 AM
Yes for sure, it would be good to know when the camera is really overheating based on the sensor and not on the timer.

A poster on EOSHD got 75C (EXIF temp) after 38 minutes of 4K 120fps using @visionrouge.net's workaround. I think that's probably pushing it. It was hot enough to cause the R5's stills temp warning icon to show. He said the CFE was extremely hot when removed.
Title: Re: Canon EOS R5 / R6
Post by: dellfonic on September 07, 2020, 05:29:26 AM
It works:

15 mins recording 8K ALL-I to CFExpress, overheating icon

Day +1, pulled battery

Inserted battery 30 secs later

No overheating icon

Turn off camera

Turn on camera, change date to current date, no overheating icon.
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 07, 2020, 06:03:27 AM
It works:

15 mins recording 8K ALL-I to CFExpress, overheating icon

Day +1, pulled battery

Inserted battery 30 secs later

No overheating icon

Turn off camera

Turn on camera, change date to current date, no overheating icon.

YES!
I love to be right. 8) 8) 8)
thanks for testing, you will have your name on my wall of fame too!

I'm wondering how Canon feel about a 40+ photographer able to crack their software without even having the camera in hand.
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 07, 2020, 06:12:24 AM
@horshack - I don't know what you mean by a CORS proxy.  CORS is a server value that is sent to the client by whatever route.  The client can choose to honour CORS policy.  Modifying the client means you can ignore the policy, controlling a proxy in the route means you can remove the CORS policy.  If you have VPN on a client, and camera connected to some machine also connected to the VPN, then client and camera are on the same network.  So I *think* the combination means you can remove the parts that are difficult.  But I've never used Canomate so I could easily be misunderstanding something.

Specifically, Wireguard uses TCP-over-UDP.  UDP for low latency, TCP for convenience.  The two endpoints need a route, they *think* they're talking TCP and are next to each other, but the TCP packets are encapsulated in UDP.  At TCP level the client-server looks one hop away, at UDP level it's whatever route your network / ISP / etc has.
Title: Re: Canon EOS R5 / R6
Post by: dellfonic on September 07, 2020, 06:13:39 AM
YES!
I love to be right. 8) 8) 8)
thanks for testing, you will have your name on my wall of fame too!

I'm wondering how Canon feel about a 40+ photographer able to crack their software without even having the camera in hand.

Ha, great work mate, I'm slightly annoyed with myself for not coming up with the solution as it's my natural inclination to bend and push any kind of deliberate cripple! Then again, I have leased it out for the last 3 weeks, so presumed all the tests had been exhausted.
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 07, 2020, 06:31:58 AM
@horshack - I don't know what you mean by a CORS proxy.  CORS is a server value that is sent to the client by whatever route.  The client can choose to honour CORS policy.  Modifying the client means you can ignore the policy, controlling a proxy in the route means you can remove the CORS policy.  If you have VPN on a client, and camera connected to some machine also connected to the VPN, then client and camera are on the same network.  So I *think* the combination means you can remove the parts that are difficult.  But I've never used Canomate so I could easily be misunderstanding something.

Specifically, Wireguard uses TCP-over-UDP.  UDP for low latency, TCP for convenience.  The two endpoints need a route, they *think* they're talking TCP and are next to each other, but the TCP packets are encapsulated in UDP.  At TCP level the client-server looks one hop away, at UDP level it's whatever route your network / ISP / etc has.

I'm not following you. The client in this case is the browser running my test javascript code issuing REST API requests to the camera's REST API server (CCAPI). There is no way to coerce the browser to accept cross-domain requests unless the HTTP header response from the server contains an Access-Control-Allow-Origin response that specifically allows the domain you're requesting from. The only way around that is either an extension running in the browser that hacks an Access-Control-Allow-Origin field in the response header (doesn't work on iOS because extensions aren't allowed) or by issuing the REST API request through a CORS proxy that issues the request to the intended target on your behalf (camera in this case) and returns a response that adds in the Access-Control-Allow-Origin field. I don't see how running a VPN factors into the equation as a solution.

Canomate doesn't have this issue because it runs as a Python app outside the browser. I tried implementing a REST API client as javascript instead for this specific date/time R5/R6 workaround as a lightweight alternative to running Canomate and also because it would be a portable solution that can run in a Smartphone browser.
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 07, 2020, 06:35:44 AM
VPN allows controlling DNS.  So, you say blah.com is at 192.168.2.2, *that* is a MITM proxy, it requests the real page from camera.xxx, relays that response back to the client *but removes the CORS info*, and then the client doesn't see any CORS, so it does what you want.
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 07, 2020, 06:39:31 AM
VPN allows controlling DNS.  So, you say blah.com is at 192.168.2.2, *that* is a MITM proxy, it requests the real page from camera.xxx, relays that response back to the client *but removes the CORS info*, and then the client doesn't see any CORS, so it does what you want.

The only device is the smartphone running in the field. Where is proxy code running that has IP access to the camera?
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 07, 2020, 06:46:28 AM
Oh, direct USB link to the cam from phone?  That's probably what I didn't understand.  In that case you could maybe use the phone as a hotspot, it's VPN'd to some network you control, and then the camera talks to phone via wifi through MITM proxy...  but this is getting ridiculously complicated.
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 07, 2020, 06:57:48 AM
Oh, direct USB link to the cam from phone?  That's probably what I didn't understand.  In that case you could maybe use the phone as a hotspot, it's VPN'd to some network you control, and then the camera talks to phone via wifi through MITM proxy...  but this is getting ridiculously complicated.

Canon's REST API only runs over its WiFi interface. Using the phone as a hotspot so that an external site could gain access to the camera (ie, one of the existing CORS proxies available online) would require the phone to port-forward unsolicited incoming requests to the camera, the same as a router NAT would. iPhone's don't have NAT functionality for their hotspot feature as far as I'm aware. And if it did it wouldn't require a VPN.
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 07, 2020, 07:04:38 AM
Okay, different than I was imagining but there might still be a way: phone VPNs to some server, and phone bridges VPN network and wifi network.  Cam connects to phone wifi, server can transparently see all packets from the phone because the networks are bridged.  No NAT required.

The python local solution still seems easier.
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 07, 2020, 07:27:30 AM
Okay, different than I was imagining but there might still be a way: phone VPNs to some server, and phone bridges VPN network and wifi network.  Cam connects to phone wifi, server can transparently see all packets from the phone because the networks are bridged.  No NAT required.

The python local solution still seems easier.

iOS's hotspot implementation doesn't support that configuration. If the demand is there the easiest solution is a standalone smartphone app. Canon actually provides the source for a fully-functional proof-of-concept CCAPI Android app. I have no interest in developing for Android though. It's likely a small effort to modify the source. Anyone interested can download the Android app source here: https://developercommunity.usa.canon.com/canon?id=sdk_download. You'll need to register on the site to gain access to the download - registration is free.
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 07, 2020, 07:57:46 AM
Ugh, Apple.  They never let you do anything fun.
Title: Re: Canon EOS R5 / R6
Post by: EOSHD on September 07, 2020, 01:48:15 PM
A poster on EOSHD got 75C (EXIF temp) after 38 minutes of 4K 120fps using @visionrouge.net's workaround. I think that's probably pushing it. It was hot enough to cause the R5's stills temp warning icon to show. He said the CFE was extremely hot when removed.

It might be safer to use a fast SD card instead for long 8K and stress test 4K recordings. CFExpress cards do get very hot.
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 07, 2020, 03:04:46 PM
I'm posting here as reference y best guess why my hack is working.
It may be useful for a possible software side app at one point.

Canon do a very simple calculation.
When camera is running, a counter is setup. When the counter reach a certain level, you have a warning logo.
If you keep recording, the Logo will become a shut down. This raise a flag that I will call “Fake Overheating flag”

At each of these step Canon is writing the exact time this occurs. Let’s call it the “overheat start time”.
This is done in an EEPROM that is kept even if you remove the battery. The writing occurs when you shut down with the power button. This is the mistake right there.

There are only one way of getting the camera to work again is to wait extra time.
Canon do a simple calculation between “actual time” and “overheat start time”. This way, even if the camera is off without battery, they can keep the time running with the help of the RTC.
It’s a way of doing coding something very fast.

They also put a conditional test on “Fake Overheating flag” to make sure changing the time during the overheat mode will not change this calculation. My best guess is that they modify the “overheat start time” with the same value the camera time is shifted in this condition only. So each tentative to play this way is not working.

But I have the impression that the new“overheat start time” is written ONLY when the camera is power down. The new real time is written immediately.
So by dropping the battery, you are avoiding the “overheat start time” to be written and only the last one is in the memory.

When the power is restored, there is the calculation to see if you have been waiting enough. But based on the old “overheat start time”, not the one shifted by the time modification. BOOOOM.

So the “Fake Overheating flag” is now remove and the camera can start.
Even better, The camera is writing this new “Fake Overheating flag” value into the EEprom. So you can turn off the right way and it will restart without any problem.

You can now shift the time back, there is no check for a possible “overheat start time” cause we are not supposed to be in overheating mode.

So whatever card you are using, whatever R5 or R6, whatever firmware… it’s working.
That was my idea at first when I noticed that the battery drop do not save all parameters. An yes, it works so beautifully.
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 07, 2020, 04:19:25 PM
It might be safer to use a fast SD card instead for long 8K and stress test 4K recordings. CFExpress cards do get very hot.

Agreed, SD is likely the better choice for video modes that don't require CFE's speed. It would be nice to see a well-controlled temperature comparison test between SD and CFE for a long-run 8K video (comparing EXIF temps).
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 07, 2020, 10:34:36 PM
Someone posted to EOSHD forum that they didn't need a dummy battery or a door closed hack to reset the timer. I can't confirm the test of the regular battery pull on the EOS R6. No matter how many times I try, the overheating light never goes away (even when I take it out super quickly). I have to use a dummy battery or a "battery door close trick hack."

It works:
15 mins recording 8K ALL-I to CFExpress, overheating icon
Day +1, pulled battery
Inserted battery 30 secs later
No overheating icon
Turn off camera
Turn on camera, change date to current date, no overheating icon.

I can confirm this hack on EOS R6. Set date +1 day, then battery disconnect, turn camera back on, date -1 day does work. The timer has officially been reset and I am able to have clips saved on at the correct time.

I was actually at the beach filming 4K 60fps all day. Of course I got the overheating warning but this hack has so far been able to practically save my life haha!
Title: Re: Canon EOS R5 / R6
Post by: 71m363nd3r on September 08, 2020, 02:01:01 AM
Someone posted to EOSHD forum that they didn't need a dummy battery or a door closed hack to reset the timer. I can't confirm the test of the regular battery pull on the EOS R6. No matter how many times I try, the overheating light never goes away (even when I take it out super quickly). I have to use a dummy battery or a "battery door close trick hack."

I can confirm this hack on EOS R6. Set date +1 day, then battery disconnect, turn camera back on, date -1 day does work. The timer has officially been reset and I am able to have clips saved on at the correct time.

I was actually at the beach filming 4K 60fps all day. Of course I got the overheating warning but this hack has so far been able to practically save my life haha!

Firmware version?
Title: Re: Canon EOS R5 / R6
Post by: dellfonic on September 08, 2020, 02:11:16 AM
Firmware version?

Version 1.0
Title: Re: Canon EOS R5 / R6
Post by: EOSHD on September 08, 2020, 02:11:22 AM
I can confirm this as well, no need to defeat the battery door sensor!

Just change the date and pull the battery as normal.

You can put the date back to the correct one upon reinserting battery.

Updated instructions:

https://www.eoshd.com/news/magic-lantern-users-create-practical-canon-eos-r5-overheating-timer-workaround/
Title: Re: Canon EOS R5 / R6
Post by: horshack on September 08, 2020, 08:08:09 AM
I've created a web-based javascript app that lets you quickly set the camera's clock to +1 day and -1 day to help automate visionrouge's workaround. It only works in browsers that allow you to disable CORS Policy Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS). Unfortunately none of the mobile web browsers available support that option, so for now this is limited to home/office/studio use.

Here is the link to the app: http://www.testcams.com/ccapi/datehack.html

Full instructions including how to disable CORS Policy security are in the GitHub repository: https://github.com/horshack-dpreview/canondatehack.html

Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 08, 2020, 08:18:38 AM
Firmware version?

R6 v1.1.0 . That's the only firmware version for the R6 currently

I can confirm this as well, no need to defeat the battery door sensor!

Just change the date and pull the battery as normal.

You can put the date back to the correct one upon reinserting battery.

No I was literally saying that DOESN'T work for me. I CAN'T get that working on the EOS R6 no matter how many times I try or how fast I try it. I NEED a battery door hack or a dummy battery in order for it to work. It doesn't work on a regular battery pull.
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 08, 2020, 08:19:26 AM
I've created a web-based javascript app that lets you quickly set the camera's clock to +1 day and -1 day to help automate visionrouge's workaround. It only works in browsers that allow you to disable CORS Policy Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS). Unfortunately none of the mobile web browsers available support that option, so for now this is limited to home/office/studio use.

Here is the link to the app: http://www.testcams.com/ccapi/datehack.html

Full instructions including how to disable CORS Policy security are in the GitHub repository: https://github.com/horshack-dpreview/canondatehack.html

Thanks Horshack. You're awesome
Title: Re: Canon EOS R5 / R6
Post by: Chainstone on September 08, 2020, 01:14:17 PM
R6 v1.1.0 . That's the only firmware version for the R6 currently


I have checked and my R6 has software version 1.0.0

I am not technically involved in this topic. But if I can do something helpful, I'd love to!
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 08, 2020, 02:13:49 PM
I have checked and my R6 has software version 1.0.0

I am not technically involved in this topic. But if I can do something helpful, I'd love to!

Your PC: Mac or Windows or Linux?

And would you mind testing timer hack following the steps provided by EOSHD (https://www.eoshd.com/news/magic-lantern-users-create-practical-canon-eos-r5-overheating-timer-workaround/)?
Title: Re: Canon EOS R5 / R6
Post by: Chainstone on September 08, 2020, 02:40:26 PM
Your PC: Mac or Windows or Linux?

I have access to both.  Mac and Windows.
Not directly to Linux at the moment, but probably could be changed  if necessary.
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 08, 2020, 05:35:00 PM
No I was literally saying that DOESN'T work for me.

No offence but would you mind recording a video following the steps shown in video provided by EOSHD?
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 08, 2020, 06:09:52 PM
None taken Walter. Will do sometime tonight.
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 08, 2020, 06:53:13 PM
https://www.lensrentals.com/blog/2020/09/taking-apart-the-canon-r5-mirrorless-camera/

Teardown of the R5
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 08, 2020, 07:12:52 PM
I have checked and my R6 has software version 1.0.0

I am not technically involved in this topic. But if I can do something helpful, I'd love to!

Yes you can help if you have firmware version 1.0.0. I'll give you some steps below on how to perform a ROM dump.

1. Get a SD or a SDHC card on standby. An SDXC card won't work.
2. On a PC, download and install this program (https://sourceforge.net/projects/win32diskimager/)
3. Also download this link (https://drive.google.com/file/d/1eMcuERvIoRDS40Z9Iied5pUxLeo0yiHm/view?usp=sharing). It is an card image that you will write to your SD card.
4. Open Win32DiskImager. Insert your SD card and browse to the file that you downloaded.
5. Make sure that you backed up everything on the card. Click 'WRITE' and wait until the status bar finishes.
6. Remove the SD card from your computer and insert it into SLOT 2 of the EOS R6. Turn the camera on. Push the 'PLAY' icon and then push 'SET'. Wait until the RED LED stops flashing.
7. Remove the SD card from your camera and put it back into your computer. You should now have the rom dump files (boot00.bin, gang100.bin, and gang200.bin).
8. DO NOT POST THE ROMS PUBICALLY. Send them to me in a private message.
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 08, 2020, 10:54:47 PM
https://www.lensrentals.com/blog/2020/09/taking-apart-the-canon-r5-mirrorless-camera/

Teardown of the R5

I may be wrong but is there a yellow tape covering at least a small part of the UART port and therefore denying external access without disassembly?
Title: Re: Canon EOS R5 / R6
Post by: Ant123 on September 08, 2020, 11:09:24 PM
This shouldn't be a big problem for people who have decided to remove the rubber.
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 08, 2020, 11:21:12 PM
I have a little bit of trouble with the concept: Let's make a hole in the back, add a rubber plug into it. So we can access the UART and don't have to remove the back. Now add a tape to the back to cover this UART.
Just to confuse the russians? Is it cold war time again? ;-)
Title: Re: Canon EOS R5 / R6
Post by: stillinsane on September 09, 2020, 08:28:54 AM
Yes you can help if you have firmware version 1.0.0. I'll give you some steps below on how to perform a ROM dump.

Do you need 1.0 for the R5 as well or has this already been dumped?
Title: Re: Canon EOS R5 / R6
Post by: visionrouge.net on September 09, 2020, 10:24:34 AM
Canon Just released a Firmware V1.1.1 for R5 and R6

Be aware of possible lock down on my hack finding last Sunday.
Even if I think it will be a very fast answer to roll out a firmware in only 3 days, that's still a possibility.

At least, it may be able to do a file comparison between V1.1.0 et V1.1.1 to see what changed is any.


Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 09, 2020, 10:45:43 AM
No offence but would you mind recording a video following the steps shown in video provided by EOSHD?

https://drive.google.com/file/d/1VUOchC3jeSj9sUlN3IOK36qsiA5N0ysy/view?usp=sharing

It only works with a battery door hack or a dummy battery. I've tried doing this at least 20 times as shown on EOSHD.

Do you need 1.0 for the R5 as well or has this already been dumped?

Yes I believe that would be helpful. I think we only dumped 1.1

Canon Just released a Firmware V1.1.1 for R5 and R6

Be aware of possible lock down on my hack finding last Sunday.
Even if I think it will be a very fast answer to roll out a firmware in only 3 days, that's still a possibility.

At least, it may be able to do a file comparison between V1.1.0 et V1.1.1 to see what changed is any.

Interesting. Keep us updated
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 09, 2020, 10:52:15 AM
Are downgrades possible ? or are they blocked
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 09, 2020, 10:54:23 AM
-Obsolete-
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 09, 2020, 10:57:21 AM
Are downgrades possible ? or are they blocked

There is nothing to downgrade to on the R6. If we had the firmware file for a previous version then maybe this hack (https://www.magiclantern.fm/forum/index.php?topic=24926.0) would work. It may actually work for the R5 since there are multiple firmwares available now.

I wouldn't risk it though. The R6 is a perfect camera for me right now (unless canon implements a better CLog).
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 09, 2020, 11:06:22 AM
Are downgrades possible ? or are they blocked

As yourboylloyd wrote: For R6 it is not possible from within Canon's menu because there is no firmware file available for the version before.
For R5: Requires testing. I doubt they blocked all downgrade options but this is just my very personal opinion not based on actual facts.
Title: Re: Canon EOS R5 / R6
Post by: 71m363nd3r on September 09, 2020, 08:45:01 PM
Canon Just released a Firmware V1.1.1 for R5 and R6

Be aware of possible lock down on my hack finding last Sunday.
Even if I think it will be a very fast answer to roll out a firmware in only 3 days, that's still a possibility.

At least, it may be able to do a file comparison between V1.1.0 et V1.1.1 to see what changed is any.

Thats the reason that I asked on the first post about this issue.
Title: Re: Canon EOS R5 / R6
Post by: VforVideo on September 09, 2020, 08:57:21 PM
I just drew attention to a strange thing, in the video mode on the R6 you cannot transfer the setting to c1 c2 c3, but in the photo mode you can. Firmware 1.1.1. Owner of R5, could you please check if you can transfer video modes to C1, etc?
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 10, 2020, 07:33:09 PM
https://wordpress.lensrentals.com/blog/2020/09/investigating-the-canon-r5-heat-emission/

Another look from lensentals into the  Canon R5 Heat Emission
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 10, 2020, 10:56:00 PM
https://www.cined.com/canon-interview-r5-and-r6-overheating-questions-answered/?fbclid=IwAR3Gcl1dvLQxcXxTcXdhSP5P2lYpAuctorK5X77ATTZXAaZeLePsOHIpfBY

From this interview with canon:

Holding a very warm object for an extended period has the potential to result in what is known as low temperature burns.

This explains the timers, the camera can handle much higher temperatures than are comfortable for the human body.
Put the camera on a tripod or use heat resistant gloves ad you will be fine :)
Title: Re: Canon EOS R5 / R6
Post by: IDA_ML on September 11, 2020, 07:59:39 AM
The R6 is a perfect camera for me right now (unless canon implements a better CLog).

I have a few questions to you or anyone else who can comment on them.  How does R6 4k video filmed in PR 422, 10-bits compare to 5D3 RAW video filmed at 14/12-bits lossless in terms of image quality?  Have you made such comparisons or have you seen them on the net?  What do you mean by "better C-log"?  Is the current one not good enough?  How about the filmic look - doesn't R6 video look too digital?  Now that you have the R6, don't you miss ML RAW video? 

Personally, I think that the R6 will become the "perfect camera" if one day we see ML on it but this is just me and my dreams.
Title: Re: Canon EOS R5 / R6
Post by: wib on September 11, 2020, 10:47:34 AM
I’m curious to find comparisons too. that’s the only step stopping me to switch from
5D3 with MLRAW to R6
Title: Re: Canon EOS R5 / R6
Post by: 70MM13 on September 11, 2020, 11:22:09 AM
there are two kinds of video shooters today (with regard to the topic of raw):
those who love the capabilities and nearly infinite flexibility of working with raw, and those who hate it and get headaches from it.

the limitations of working with log footage will always be inferior to raw for the first category of shooter.

in the end it probably hinges on one's primary motivation.  is it more about ease of use and/or quick turnaround time, or perhaps about achieving a desired (artistic) appearance/evocative effect?

the answer of course is entirely individual, so the chances are you already know for yourself :)

for me the quality of the pixels outweighs their number.

plus, i just love working with magic lantern.  after all these years it just feels like home.  i can't imagine a canon camera without it! ;)
Title: Re: Canon EOS R5 / R6
Post by: EOSHD on September 11, 2020, 05:34:01 PM
If anyone is not seeing the reset happen on EOS R5/R6, try it a second time

https://www.eoshd.com/news/canon-eos-r5-8k-stress-test-1-no-problem-with-timer-reset-so-far/

Most of the time I find it takes two goes.

Maybe you have to pull the battery within a certain amount of time.

A nice reaction game to play in the middle of a shoot  :D
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 11, 2020, 09:23:31 PM
I have a few questions to you or anyone else who can comment on them.         

How does R6 4k video filmed in PR 422, 10-bits compare to 5D3 RAW video filmed at 14/12-bits lossless in terms of image quality? Have you made such comparisons or have you seen them on the net?
I working on a side by side test of this. But honestly, the 10bit on the R6 is pretty amazing. Of course RAW would be better, but it's still 10x better than regular h.264. I am used to grading ML footage in adobe camera raw so the workflows are drastically different. But it's way better to be able to edit the footage right out of camera. And there is extremely good shadow recovery. I've been 4 stops under exposed and there is almost no noise when I bring the image back up to EV0. A huge one is that I can also adjust the white balance of the video in post pretty accurately with the little dropper tool and no quality degradation.

The R6 does not shoot in ProRes though. The R6 uses HEVC instead of Prores.

What do you mean by "better C-log"? Is the current one not good enough?
I've used Clog1 Clog 2 and Clog3 in the past on other cameras. Clog3 better uses the full dynamic range of the sensor. Here is an extreme example taken on clog1 on the R6:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FvsBCkzk%2Fclog1-example.png&hash=9b68245d1b49cca7e34886f44855b41f) (https://ibb.co/q0nLp1p)
I've shot the sun and the ocean in clog1. Now obviously, the sun is going to be completely blown out regardless of what I film at. But in the clip, the highlights only go to about 80% of the highest color information. The shadows only go down to 10%. I call this "too flat" and this is an extreme example. Most of the time, the shadows and highlights are usually within 60% of each other in clog1. When using clog3, these numbers are spread a lot more on the spectrum. Shooting on the c300 mark 3  in clog3, there is NO POINT in shooting RAW via HDMI. Clog 3 is that powerful to me.

But I will say that it is good enough. I've actually never been able to manipulate footage to such quality so fast before.

How about the filmic look - doesn't R6 video look too digital?

It depends on what you mean. When think of "Filmic" look, I think of imperfections. Maybe a little softness on lenses, or maybe random grain. High contrast. Good dynamic range. And stuff like that. But then when I see shows like Breaking Bad that was shot 100% on film, I feel like that is super digital looking with amazing dynamic range. But it was shot on film.

There are a lot of ways to make digital look like film, and film look like digital. The Alexa's and RED's are known for there dynamic range and ability to push to make look like film. But nowadays, that dynamic range exists on basic cams like these. The Sigma FP can produce some amazing footage that can be converted to look like film. I truly believe that with some tinkering, one could make the R6 look like film.

The biggest downside is that the R6 also films in IPB mode though and not ALL-I (which lowers the quality by compression). It's not too noticeable to me, but I'm sure there will be artifacts if I were inches away from an 80" screen. 

Now that you have the R6, don't you miss ML RAW video?
Actually not really (which is surprising me). I thought I would be switching back and forth between my 5D and the R6 on shoots, but you CANNOT beat the autofocus system on the R6. I was shooting a model on an EF 100mm f/2 lens and she was in moving around a lot. BUT SHE WAS IN FOCUS THE ENTIRE TIME! Every single frame, here eyes were sharp. The IBIS also was perfect for handholding 100mm. No matter how good Magic Lantern gets on the old cameras, it can't beat such features.Of course being able to PLAYBACK the footage on set is also huge. The zebras are helpful too, just as helpful as the magic lantern zebras.

Personally, I think that the R6 will become the "perfect camera" if one day we see ML on it but this is just me and my dreams.

Me too. I mean honestly if they can find a way to implement RAW HD on this camera then I would be happy (RAW 4K probably isn't possible due to slow SD card rates). But there is RAW light that can probably handle it. Of course I'm sure MLV can handle it too. I couldn't imagine what you devs could do with a 300MB/s write speed. It would be 100% the perfect camera if it had ALL-I recording with Clog3. Right now it's at about a 95% to me. But for being $2,500 plus a cheap $50 EF adapter (which works perfectly btw) it's basically perfect to me. I'm probably going to be using this camera for the next 10 years comfortably. I'm actually impressed with Canon's new battery too. It def lasts longer then the regular LP-E6 batteries. The new battery even works for my 5D!

TLDR: I would basically call the R6's clog1 9.5bit footage (Not full 10bit if that makes sense). More than double the dynamic range of regular h264, but still not using the camera's full capabilities. The autofocus and ibis are to die for though. I never realized how much I needed autofocus. I can properly look at the footage and see things that shouldn't be there instead of worrying about racking focus at the right time.

Edit: Something that I want to try is making a video in 20fps photo burst mode. The photos are 16bit (a bit overkill but sweet) but still 4fps too slow to make the smooth 24fps. Maybe I can shoot a music video and slow the song down to 0.83x, then interpret the footage as 24fps. Open gate (4:3), 5.4K, and 16bit! I can't imagine what that would look like.
Title: Re: Canon EOS R5 / R6
Post by: IDA_ML on September 12, 2020, 12:05:23 AM
Yourboylloyd,

Thank you so much for taking the time to provide this detailed and very useful information.  I agree that perfect focus and IBIS are much more important for the final result than a slight quality degradation which is the price to pay for not filming in RAW. 

A short comment on your intention to film a RAW video at 20 fps.  You shouldn't worry about the missing 4 fps since Resolve does a hell of a job compensating for them using the optical flow algorithm.  Please check if there is some dead time between the shots because in that case, you may end up with a choppy video.  Also, as far as I understand, you lose the tracking AF at 20 fps.

Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 12, 2020, 04:01:05 AM
Okay so I learned something. I tried to compare the R6 in 1920x1080 mode to the 5D2 1880x1268, but the 5D2 footage was coming out sharper (when I nailed the focus that is). Here is the example video stills all shot on Sigma 35mm 1.4 @f/2:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FS5CG0WF%2Fr6hd-vs-5d2-hd.jpg&hash=a5b52a9e6f07fb06376eae2fcde5232b)
Fullsized image. (https://i.ibb.co/NtBbpQc/r6hd-vs-5d2-hd.jpg) (Note that accidently captioned 1880p, but it's actually 1880width)
The R6 produces random artifacts in 1080p mode for some reason. This is kind of a bummer to me. I don't know what that is but it happens every few frames. I didn't apply any sharpening or anything. I can confirm that this doesn't happen on the R6 in 4K mode though.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FP1CJpyD%2Fzoom-artifacts.jpg&hash=1e04a70980d1f1055a149aa73a71a913)

I can't believe I'm saying this but basically the 5D2 RAW is sharper than the R6 in 1080p mode. And I'm not sure what's going on with the artifacts on the R6.

Otherwise: I'm not a hugely master colorist, but I do feel like the color ranges and dynamic range is roughly the same with a shot that has been exposed correctly.  Will do more tests and report back soon
Title: Re: Canon EOS R5 / R6
Post by: names_are_hard on September 12, 2020, 04:38:32 AM
Could be compression artifacts.  Looks similar to JPEG quantisation.  RAW wouldn't have those.
Title: Re: Canon EOS R5 / R6
Post by: Grognard on September 12, 2020, 10:04:45 AM
Interesting.  Try to compare 3k or 3,5k raw with 4k from R6. Could be surprising.
Basiquely, a camera like R6 with autofocus and ibis should be usefull for low budget corporate film, interviews.. but not an avantage for an artistic short film where magic lantern should be still a good choice.
Title: Re: Canon EOS R5 / R6
Post by: garry23 on September 14, 2020, 10:59:42 AM
https://petapixel.com/2020/09/12/canon-we-dont-cripple-cameras-idea-is-conspiracy-theory/
Title: Re: Canon EOS R5 / R6
Post by: a1ex on September 14, 2020, 08:18:45 PM
Memory map for R5/R6 (see also for DIGIC 7 (https://www.magiclantern.fm/forum/index.php?topic=19737.msg212603#msg212603) and DIGIC 8 (https://www.magiclantern.fm/forum/index.php?topic=22770.msg212090#msg212090)):

Code: [Select]
00001000-00001FFF -> 00000000-00000FFF (-1000) O:NCACH I:WB,WA  P:RW       [ CPU0 only ]
00001000-00001FFF -> 00001000-00001FFF (   +0) O:NCACH I:WB,WA  P:RW       [ CPU1 only ]
00002000-3FFFFFFF -> 00001000-3FFFFFFF (   +0) O:NCACH I:WB,WA  P:RW       [ cacheable RAM - only the first GiB ]
40000000-BEFFFFFF -> 40000000-BEFFFFFF (   +0) O:NCACH I:NCACH  P:RW       [ uncacheable RAM - 2 GiB ]
BF000000-DEFFFFFF -> BF000000-DEFFFFFF (   +0) Device           P:RW XN    [ MMIO area ]
DF000000-DFFFFFFF -> DF000000-DFFFFFFF (   +0) O:NCACH I:WB,WA  P:RW       [ TCM? ]
E0000000-E7FFFFFF -> E0000000-E7FFFFFF (   +0) O:WB,WA I:WB,WA  P:R        [ main ROM ]
E8000000-EFFFFFFF -> E8000000-EFFFFFFF (   +0) Strongly-ordered P:RW XN    [ ? ]
F0000000-F7FFFFFF -> F0000000-F7FFFFFF (   +0) O:WB,WA I:WB,WA  P:R        [ secondary ROM ]
F8000000-FFFFFFFF -> F8000000-FFFFFFFF (   +0) Strongly-ordered P:R  XN    [ ? ]

Created with this script (https://a1ex.magiclantern.fm/bleeding-edge/R5/v7mmap.py) and annotated manually.
Title: Re: Canon EOS R5 / R6
Post by: nikki on September 16, 2020, 08:19:02 PM
Could be compression artifacts.  Looks similar to JPEG quantisation.  RAW wouldn't have those.

Mostly shooting commercials on film

But also have shot with Alexa (this is around where the 5d3 with ml is)
Title: Re: Canon EOS R5 / R6
Post by: lorenzo353 on September 17, 2020, 11:05:42 PM
Hi camera hackers,

Could you please send me a craw file from R6 ?
Optionnally with dust removal option enabled ?
it is to improve my work at:
https://github.com/lclevy/canon_cr3

Kind regards,

Laurent
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 18, 2020, 11:54:09 PM
You can find some raw files from the R6 here:

https://www.dpreview.com/sample-galleries/6671206782/canon-eos-r6-sample-gallery/8454525047
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 19, 2020, 01:43:41 AM
Could you please send me a craw file from R6 ?

I'll send two :) (https://drive.google.com/drive/folders/131JhhH58z_PJHD96N8XnMnCjPkTkCkbA?usp=sharing)
Title: Re: Canon EOS R5 / R6
Post by: lorenzo353 on September 20, 2020, 07:48:54 PM
You can find some raw files from the R6 here:

https://www.dpreview.com/sample-galleries/6671206782/canon-eos-r6-sample-gallery/8454525047
Thank you, Lars, but I need CRAW (compact raw) files, please
Title: Re: Canon EOS R5 / R6
Post by: lorenzo353 on September 20, 2020, 07:49:25 PM
I'll send two :) (https://drive.google.com/drive/folders/131JhhH58z_PJHD96N8XnMnCjPkTkCkbA?usp=sharing)
Thank you!
Title: Re: Canon EOS R5 / R6
Post by: lorenzo353 on September 20, 2020, 08:06:37 PM
Thank you!
you sent me raw, not craw.
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on September 21, 2020, 12:24:45 AM
Ohhhhh sorry. Didn't know that there was a difference. I'll take some in a few
Title: Re: Canon EOS R5 / R6
Post by: wib on September 30, 2020, 03:37:38 PM
did anyone noticed that change in the firmware 1.1.1 of the R6
https://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos-r6.html?type=firmware&firmwaredetailid=tcm:13-2011538&os=macos%2010.15%20%28catalina%29&language=en (https://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos-r6.html?type=firmware&firmwaredetailid=tcm:13-2011538&os=macos%2010.15%20%28catalina%29&language=en)

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.imgur.com%2FKOjivlO.png&hash=ffcd5eef5deb69796c68c5269ba3bdbd)

is it related to the "time hack" ?
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 30, 2020, 03:58:07 PM
seems like a way from canon to prevent the date change timer reset
Title: Re: Canon EOS R5 / R6
Post by: Walter Schulz on September 30, 2020, 03:59:00 PM
Has anyone any facts or are we going EOSHD here?
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 30, 2020, 04:57:57 PM
No facts just assumtions based on that firmware discription
Title: Re: Canon EOS R5 / R6
Post by: whitelight on September 30, 2020, 05:05:02 PM
seems like a way from canon to prevent the date change timer reset
It's been reported the timer reset hack is still working with firmware 1.1.1
Title: Re: Canon EOS R5 / R6
Post by: Lars Steenhoff on September 30, 2020, 06:25:41 PM
Thanks, glad to see my assumption was wrong
Title: Re: Canon EOS R5 / R6
Post by: wib on September 30, 2020, 06:38:17 PM
great ! Sorry to have sounded the alarm :)
Title: Re: Canon EOS R5 / R6
Post by: gravitatemediagroup on October 05, 2020, 04:16:56 AM
any 5d3 w/danne build VS R5 raw videos in the wild? or would anybody be able to make one?  sorry if this has been discussed already.
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on October 05, 2020, 03:39:58 PM
I'm working on an R6 10bit vs 5D2 10bit video. Probably not the same but close enough right?
Title: Re: Canon EOS R5 / R6
Post by: allemyr on October 05, 2020, 04:35:27 PM
I'm working on an R6 10bit vs 5D2 10bit video. Probably not the same but close enough right?

Not close enough for me :) you know why :)

The quality of R6 is outstanding ofcourse

You two should do a collab together. This raw postprocessing and quality at shooting is also outstanding. I post his forumthread here:  https://www.magiclantern.fm/forum/index.php?topic=25312.0
Title: Re: Canon EOS R5 / R6
Post by: garry23 on October 12, 2020, 07:33:40 PM
In case some are interested. https://blog.yifangu.com/2020/10/09/canon-eos-r5-thermal-mod/
Title: Re: Canon EOS R5 / R6
Post by: lorenzo353 on October 12, 2020, 11:57:11 PM
Hi,

could you please send me craw files ?

Lorenzo

Ohhhhh sorry. Didn't know that there was a difference. I'll take some in a few
Title: Re: Canon EOS R5 / R6
Post by: yourboylloyd on October 13, 2020, 01:18:01 AM
could you please send me craw files ?

Wowwww I swore I did that already. Sorry. Check your PM