Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - yourboylloyd

Pages: [1] 2 3 ... 13
What is the advantage of this method?
With eos utility a Downgrade works also...

Does it really? It historically didn't work. I guess I never considered doing that.

Out of the 8 battery door open attempts that I tried, I was unsuccessful on 3 of them. It's almost simultaneous timing with the button push on the update screen.

This method does NOT work on the EOS R6. There is so far a workaround though:

Nevermind it does work. It has to be almost at the same time on the R6 though. Like painfully quick. But the workaround also works as well

The battery door trick that has been used to downgrade the 5D3 and other models so far that we've known does not work on the EOS R6. If you try and open the battery door or the card door, the camera and LCD will stay on: Nevermind it does work. But you have to be EXTREMELY fast to catch it. This method below works though:

Instead, you'll need two SD cards. It won't work if you have only one. Follow these steps:

- copy NEW/CURRENT firmware to the card - insert into camera.
- launch Update Firmware from Canon menu, click OK
- open the CARD door ASAP, but don't remove the card or it won't work and will give an error message
- QUICKLY insert a SECOND card with the older firmware on it into the other card slot
- If done correctly, the above menu should pop up. Select the older firmware and install

I'm not sure if this method works on the R5 or any other camera. I would caution against updating to newer firmware in the future and for other models. Especially if the camera only has one card slot like the EOS RP or R or m50.

The last one seems to be this from 2018? Is this the basic install and do I have to drop the development modules on top of that? Thanks! Martin

Just watch ZEEK's video. He explains everything and he has download links in the description


TODO: I should replace the links with throughout the forum and website. Forum links can be automated, I'll look into it, so... no need to edit the posts manually (I hope).

There are some syntax differences, for example:
- before:
- after:

Hey A1ex, any update on this? There have been multiple users that I've seen trying to get started with ML but because the links are dead, there is no all in one place to learn anymore.


BitBucket is not working anymore...
Is there anywhere else I can get the script to patch QEMU?


You have to do some manual link editing. The QEMU migration solution is here and the first post of that thread is the original tutorial:

Camera-specific discussion / Re: Canon EOS R5 / R6
« 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

Camera-specific discussion / Re: Canon EOS R5 / R6
« 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?

Probably if we knew all of the right stubs and what to enable/disable. Canon basic seems powerful. I'm still learning but don't count on it because I'm noob.

I would just take it to canon at this point.

Share Your Videos / Re: Michelob Ultra Advertisement Shot on Canon EOS M
« on: September 30, 2020, 07:54:25 AM »
I liked it. But everything seemed horizontally stretched. It was distracting at first but I eventually got used to it.

Magic Lantern Forum and Site Discussion / Re: A Magic Lantern Discord?
« on: September 29, 2020, 06:17:58 AM »
I say either go all the way with it and make it the official ML discord, or get rid of it.

There are a lot of people that use discord as communication, and more and more talented developers are using that ML discord to test things everyday. Making it public might actually attract more people.

If it were exclusive then that would define magiclantern as exclusive. Test and chat there - post results on forum seems like a good idea

Camera-specific discussion / Re: Canon EOS R5 / R6
« 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

Hey Srsa that script worked on the R6.

It's a logfile of 170KB. Is this log file publically shareable?

Camera-specific discussion / Re: Canon EOS R5 / R6
« on: September 19, 2020, 01:43:41 AM »

Camera-specific discussion / Re: Canon 5D Mark IV
« on: September 18, 2020, 08:54:54 AM »
still like the new eos R there's a speed booster RF-EF lens available now that reducers 4k crop factor from 1.7 to 1.24
It also works on the R6 in Fullframe!! I'm making an entire video about this. 0.71x Medium Format crop factor on EF lenses!

(Sorry I know it's unrelated but also at the same time related to discussion)

Ran on my R6:
Code: [Select]
<?xml version="1.0"?><Canon><CameraInfo><Serial>XXXXXXXXXXXX</Serial><FirmwareVer><Internal></Internal><Major>1.1.0</Major></FirmwareVer><ErrorList><Kind><ID>E01</ID><Count>2</Count><ErrorLog><BatTemperature>max:0 min:0</BatTemperature><FirstOccurTime>2020.09.17 02:08:57</FirstOccurTime><LastOccurTime>2020.09.17 02:09:15</LastOccurTime><Log><DateTime>2020.09.17 02:09:15</DateTime><Reason>DS-EID:068</Reason><BatTemperature>0</BatTemperature><LensID>0000bc95</LensID><ReleaseCount>528</ReleaseCount></Log><Log><DateTime>2020.09.17 02:08:57</DateTime><Reason>DS-EID:068</Reason><BatTemperature>0</BatTemperature><LensID>0000bc95</LensID><ReleaseCount>527</ReleaseCount></Log></ErrorLog></Kind><Kind><ID>E70</ID><Count>4</Count><ErrorLog><BatTemperature>max:0 min:0</BatTemperature><FirstOccurTime>2020.09.17 13:12:17</FirstOccurTime><LastOccurTime>2020.09.20 12:55:27</LastOccurTime><Log><DateTime>2020.09.20 12:55:27</DateTime><Reason>DS-EID:101</Reason><BatTemperature>0</BatTemperature><LensID>00000000</LensID><ReleaseCount>1171</ReleaseCount></Log><Log><DateTime>2020.09.20 12:51:18</DateTime><Reason>DS-EID:101</Reason><BatTemperature>0</BatTemperature><LensID>00000000</LensID><ReleaseCount>1171</ReleaseCount></Log><Log><DateTime>2020.09.17 13:30:36</DateTime><Reason>DS-EID:101</Reason><BatTemperature>0</BatTemperature><LensID>0000bca9</LensID><ReleaseCount>561</ReleaseCount></Log><Log><DateTime>2020.09.17 13:12:17</DateTime><Reason>DS-EID:101</Reason><BatTemperature>0</BatTemperature><LensID>0000bca9</LensID><ReleaseCount>561</ReleaseCount></Log></ErrorLog></Kind><Kind><ID>E255</ID><Count>2</Count><ErrorLog><BatTemperature>max:0 min:0</BatTemperature><FirstOccurTime>2020.09.20 12:51:15</FirstOccurTime><LastOccurTime>2020.09.20 12:51:15</LastOccurTime><Log><DateTime>2020.09.20 12:51:15</DateTime><Reason>DS-EID:028</Reason><BatTemperature>0</BatTemperature><LensID>00000000</LensID><ReleaseCount>1171</ReleaseCount></Log><Log><DateTime>2020.09.20 12:51:15</DateTime><Reason>DS-EID:028</Reason><BatTemperature>0</BatTemperature><LensID>00000000</LensID><ReleaseCount>1171</ReleaseCount></Log></ErrorLog></Kind></ErrorList><TotalShoot>1471</TotalShoot><TotalShutter>305</TotalShutter><PowerOnCount>311</PowerOnCount><TotalRunningTime>63758</TotalRunningTime></CameraInfo></Canon>
Ran on m50:
Code: [Select]
<?xml version="1.0"?><Canon><CameraInfo><Serial>XXXXXXXXXX</Serial><FirmwareVer><Internal></Internal><Major>1.0.2</Major></FirmwareVer><ErrorList></ErrorList><TotalShoot>1078</TotalShoot><TotalShutter>1078</TotalShutter><TotalSW2>1229</TotalSW2><TotalSW2Long>0</TotalSW2Long><PowerOnCount>690</PowerOnCount><TotalRunningTime>225948</TotalRunningTime></CameraInfo></Canon>
And on R5 is a TotalShoot and TotalShutter count...
It's probably because there is a mechanical shutter and electronic shutter.


mlv_play isn't working and causes no modules to load.

mlv_play hasn't worked in ages on experimental builds. Everyone has this problem. There isn't much that can be done unless you can convince someone to develop mlv_play more.

Camera-specific discussion / Re: Canon 5D Mark IV
« on: September 17, 2020, 05:39:30 PM »
I just asked around for the rom in the discord chat. You should really join it!

General Development Discussion / Power Usage Comparison/Investigation
« on: September 17, 2020, 01:29:46 AM »
Thought that this could be useful for understanding the camera hardware.

Background: A1ex, names_are_hard, and I had a random off topic conversation in the discord chat about overheating on DigicX. We were comparing the 5D to the R6 as far as power draw from the internal battery. Then I realized that I have an accurate way of measuring this and could perform a test!

Test setup:
Using a LP-E6 dummy battery, an AC adapter for the dummy battery, and a TPlink Smart watt-meter. I was able to measure the power of the cameras in their different states. I have the 5D2 and the R6, but this test can be measured on any camera!

  • My AC adapter could only provide 1.7A max. So 1.7A x 7.4V = 12.58W MAX read. After 12.58W, my AC adapter would overload and shut the camera down.
  • The TPlink Smart watt-meter is accurate to 2 decimal places, but has a refresh rate of 1 second. It's work aroundable, but I would of course rather have something that's more time precise

The AC adapter naturally uses 0.3W of power. So subtracting that from the readings I get and getting an average

5D2: (+/- 0.5W on all tests)
Power on (no liveview): 2.56W
Liveview on: 7.21W
Recording H.264: 8.4W
Recording 1044p RAW: 8.59W
Recording 2.7K RAW MLV 24fps: 8.35W

EOS R6: (+/- 0.5W on all tests)
Power on (flipped screen into camera): 1.6W
Liveview on LCD screen: 4.1W
Recording 4K 60fps: 10.6W
Recording 4K 60fps with stabilzation on while shaking cam (IBIS): 11.8W
Recording 4K 60fps with AF on (35mm lens) stabilzation on:OVERLOADED (>12.58A)
Shooting in 20fps photo burst mode: OVERLOADED (>12.58A)
Recording at 4k 24p no usb c charger: 9.8W
Recording at 4k 24p with usb c charger plugged in: 9.82W (basically the same)
[(this confirms that the usb c only charges the battery and does not power the camera at any point)]

So the R6 draws significantly more power from the LPE6 batteries than the 5D2. I can only imagine that a R5 recording 8K RAW to a CF express card could draw closer to 16W.

I would love to see this test performed on other cameras! Even the blackmagic4k would be interesting. I'll update this first post if anyone can post a reliable test of this on a camera.

Camera-specific discussion / Re: Canon 6D
« on: September 16, 2020, 11:33:12 AM »

Find out about a problem with the 2880x1200 at 25 fps preset.
If the foxus box is moved with the cursor arrows, you might get corrupted frames.
When the focus box is dead center, all works well. But if it is slightly moved around, it might cause corrupted frames.
You can see it in the behaviour of the real-time Canon live view. If your focus box is in a wrong place, liveview gets sluggish/jittery.
If you move the focus box around to a place where liveview is normal again, things are probably fine agian. (works for me).

Haven't noticed this behaviour at other presets.

This also happens on the 5D2 3.5K preset!!!!!! I noticed this a few weeks ago.

A lot of work has been done on the M50, but there are no active developers working on the camera. If you have coding experience please help on the m50's development.

Camera-specific discussion / Re: Canon EOS R5 / R6
« 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:

Fullsized image. (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.

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

Camera-specific discussion / Re: Canon EOS R5 / R6
« 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:

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.

Pages: [1] 2 3 ... 13