Messages

Found some interesting CF card related info in the Rom's(5D2,5D3,6D,7D)

You are aware 6D doesn't actually host CF but SD? ;-)

Unable to help. Archive.org hasn't archived the zip and I don't have backups.

This startup log? https://web.archive.org/web/20210725091001/https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log/
or the mpu one?

Clean HDMI is implemented for all ML cameras supporting Display tab -> Clear overlays. Works for USB streaming, too.
It's been there for about a decade IIRC.
Also https://wiki.magiclantern.fm/faq#how_do_i_record_stream_for_more_than_30_minutes
For the reasons why ML supports 1.1.3 and 1.2.3 and their differences:
https://www.magiclantern.fm/forum/index.php?topic=14704.0

But you need to run firmware 1.2.3 or above for Clean HDMI Output. I recommend you update or downgrade to 1.2.3. and the appropriate ML version

?
Clean HDMI out-of-the-box requires 1.2.x.
Clean HDMI with ML for 1.1.3 and 1.2.3.

Have you tried the anamorphic 3x3 Dannes build? There is no realtime liveview in this mode. Only grayscale at perhaps half fps. I'm pretty sure HDMI output is the same view as the screen on cam.

Arnaud is referring to his enhanced build based on Danne's. See https://www.magiclantern.fm/forum/index.php?topic=26998.0

I'm well aware HDMI has liveview, but we are talking about while using and recording with this particular build.

I'm quite sure Arnaud is aware and so am I.

a) HDMI stream and what the display shows: Not identical. Some overlays are not available. And there are more differences...
b) There is no UVC in 5D3. UVC = USB Video Class = Doesn't need additional drivers to work. Using "the version of UVC which the 5D III has" makes absolutely no sense and just adds confusion.

Only a very small set of Canon gear actually has UVC on board: R50, R8, R10, R6 Mark II, PowerShot V10.
Canon USB inside 5D3 is not UVC but proprietary handled by PC tools like EOS Webcam Utility, EOS Utility, SparkoCam, gphoto2, etc. and some smartphone apps.

That said: You can stream via USB or HDMI. HDMI requires an HDMI capture device (most are actually UVC).
Out-of-the-box 5D3 does true FHD over HDMI. No sound.
Resolutions: 576p for USB, 1080i with HDMI.

And no audio via USB/HDMI for 5D3 (and other Digic 4 and 5 cameras).

Which is actually nice.
Because it indicates cam is prepared for ML.
Now make sure to have Canon firmware 1.1.0 and not 1.0.9 installed.
If so:
Use EOScard to enable EOS_DEVELOP and BOOTDISK. Copy extracted Nightly Build content to card (wipe anything else on card before).
Insert card into cam, startup cam and wait for some time until LED calms down. Then press trashcan button to access ML menu.

Thanks!
Visit https://eoscard.pel.hu and download Canon firmware 1.1.0 for 450D.
Wipe card by formating inside cam.
Extract e5kr4110.fir to card and run firmware update in cam.

After that retry ML installation.

And this time it has the blinking led, its not constantly on

Please clarify!
"And this time" implies you have had other results after installation.
Do you get LED burning constantly in the end?

- Run EOSCard as admin, click refresh, select ML and hit save

Redo from scratch but don't use "ML" icon. Select BOOTDISK and EOS_DEVELOP checkboxes and press SAVE button on top.

I installed ML on a 450D lately.

Use a small card (SD or SDHC) and retry.
First make sure your card is properly prepared:
Run EOScard and make sure both checkboxes are enabled after start. If not: You should run EOScard as admin, enable both boxes (BOOTDISK and EOS_DEVELOP), press SAVE button.

Report back

I recommend to join our Discord (link above) for further instructions.
There you should create a thread for your issue in "Magic Lantern Community" -> "unbricking-and-diagnosis".

There is not any hint your card reader is involved in this error.
IMO you should check UART access and if you get any response from MPU and ICU.
Also checking voltages on lens mount contacts and main board will make more sense.

No budget given ...
No example what "very expensive" means for you.
No indication what kind of handle you want to use.

That is not what names was saying.

All listed video modes are supported for the cams listed in Bilal's post.
You don't need a compatible card.
A compatible card will just allow you to use 240 MHz mode.

It doesn't mean you can get continuous recording in all modes. Card and card interface have limits and there are modes demanding bandwidth rates not able to be delivered by card and cam. Therefore some modes have limited recording durations.

You can easily find "allowed" ML settings where no camera works continuously.

About "Crop Mood" build: https://www.magiclantern.fm/forum/index.php?topic=26851.0
All supported cams can achieve around 80 MByte/s continuous data rate for recording with compatible cards*. Unlimited. As long as card has free storage space and battery supplies energy.

And heat protection doesn't set in which may happen in unforgiving environments.

*Chart with tested cards: https://wiki.magiclantern.fm/cards_240mhz

There are reports of cams locked in states like VGA. Therefore forcing 1080i makes sense.

Sure, but I wanted to get the de-squeezed numbers. Once I had them written down on file, I no longer go through this step.

What is easier?
a) Looking into Bilal's chart. First number x 3 = desqueezed number.
b) Your workflow?

Don't get your drift.

Maybe I have set wrong export settings in my MLV app.

Maybe it would be a good idea to show/examine them? Just a suggestion ...

The original CinemaDNG's are 1020 pixels tall

?
In 4.8k 2:35 your resolution is 1600x2040 which must be expanded to 4800x2040.
I have troubles to understand where your 1020 pixel setting happens.

2. Is unneccessary because Bilal listed all modes and their resolutions. You are re-inventing the wheel.

I took the liberty to splitt topic. Change topic title as needed.

Well, another feature not working with those builds.
Guess who has to do something about it? ;-)

Card has to be bootable.
Can be done by
- ML installation in cam
- PC based tools. EOScard, MacBoot, script (make_bootable.sh), Petabyte's MLinstall.
- Using disk editors to create bootsector byte by byte
First two methods are covered in Install Guide.

Bit about oc doesn't make sense. If you are not using oc you are limited to cam specs and this means 50 MByte/s theoretical bandwidth.