Messages

Hello,

I'm sorry, but i've missed your post (and since i've switched to EOS R in February 2020, i can't even enjoy ML on my camera ).
But i'll borrow my old 650D from my son and give it a shot. The fact is, that i've only been using the lens2.lua with my 6D, but if i remember correctly, some failed assertions bit my ass as well..

cheers,

zLOST

Haha, no problem at all!
I have no idea where to start with debugging this sort of thing. Are there any articles or guides for programming and avoiding quirks on certain cameras?
Thanks!
    InACanoe

Hello,

I recently tried to get this working on my EOS Rebel T4i (650D) and ran into some strange problems that caused core dumps relating to malloc.

To absolve any doubt, I tried this on a fresh ML install from the 'Non-CPU lens info' build, (download page is Link1, link to 650D build is Link2).
I'm not using a chipped lens.
The menu for zLOST's lens2.lua script actually pops up. The error only happens when you try to take a photo. Then the script, I guess, crashes and the camera logs that ASSERT.LOG error file.

I tried this two ways, once using the stock lens.lua script that came with the nightly build, and another time using the lens2.lua script that zLOST wrote and publishes at Link3.
Link1: https://builds.magiclantern.fm/experiments.html
Link2: https://builds.magiclantern.fm/jenkins/job/manual_lens_info/23/artifact/platform/650D.104/magiclantern-manual_lens_info.2018Dec23.650D104.zip
Link3: http://ml.zlej.net/

What could be the cause of this error? I would expect other scripts to fail as well like Calculator or Hello World.. Pong... Surely they use Malloc as well. But this fails just here when trying to write lens info to a file.

Any help at all would be appreciated Thanks!



This is the ASSERT00.LOG generated trying to use the lens.lua script that comes with the nightly build.

ML ASSERT:
0
at ../../src/mem.c:799 (__mem_malloc), task PropMgr
lv:0 mode:2

PropMgr stack: 14cdc0 [14cf68-14bf68]
0xUNKNOWN  @ 9b5e8:14ce70
0x00ACEB5C @ aca29c:14ce50
0x00ACE398 @ aceb94:14ce40
0x00081480 @ ace3b8:14ce30
0x0007EB8C @ 814bc:14cdf0
0x0007E478 @ 7ebe8:14cdc0

Magic Lantern version : manual_lens_info.2018Dec23.650D104
Mercurial changeset   : 0de7b671c52c (manual_lens_info) tip
Built on 2018-12-23 22:38:34 UTC by jenkins@nightly.
Free Memory  : 150K + 3092K

This is the ASSERT00.LOG generated trying to use the lens2.lua script that zLOST wrote here http://ml.zlej.net/

ML ASSERT:
0
at ../../src/mem.c:799 (__mem_malloc), task PropMgr
lv:0 mode:2

PropMgr stack: 14c380 [14cf68-14bf68]
0x00AA8E54 @ ab4170:14cd00
0xUNKNOWN  @ aa8f38:14cce0
0x00AB55E8 @ abafd0:14c478
0x00AA4F8C @ ab5604:14c468
0x00AB09A8 @ aa4fbc:14c458
0x00AAACEC @ ab0ae8:14c430
0x00AACC04 @ aaad04:14c420
0xUNKNOWN  @ aacc2c:14c400
0x00081480 @ 8c080:14c3f0
0x0007EB8C @ 814bc:14c3b0
0x0007E478 @ 7ebe8:14c380

Magic Lantern version : manual_lens_info.2018Dec23.650D104
Mercurial changeset   : 0de7b671c52c (manual_lens_info) tip
Built on 2018-12-23 22:38:34 UTC by jenkins@nightly.
Free Memory  : 150K + 3092K

[Canon EOS Rebel T4i]

Hi, this is a question stemming from an existing thread in /r/askphotography, https://www.reddit.com/r/AskPhotography/comments/p2db69/failure_to_preview_brightness_correctly_canon_eos/

My camera is a Canon EOS Rebel T4i
On the latest nightly build (from 2018) https://builds.magiclantern.fm/650D-104.html
And a non-chipped lens adapter for an analog lens

What happens, is in every mode on my camera except for Av, Portrait, (Macro is maybe 1 stop away from being accurate), Sports, Night Portrait, Handheld Night Scene (In dark areas), and HDR Backlight Control..

What I see in Live View is darker than the photo the camera will actually take, by about 5-6 stops.
This makes focusing via the live view very difficult, because it's way too dark. And using M mode while everything is too dark is difficult to say the least.
What's also interesting is that the exposure level bar always shows accurately in M mode, so even if the preview is too dark, I can still accurately judge the photo's brightness with just the exposure level bar. I always view-find with the aperture wide open (lens claims 3.9).


Is there some way to override the aperture settings, even if a non-chipped lens/adapter is being used?
I found this page, https://wiki.magiclantern.fm/camera_help that says you can't, but wanted a second opinion. I checked and it says the same on my camera, maybe there's a way around that?

All the best,
    InACanoe