Messages

Also, I noticed that in C2 I can not enter the settings menu, because when I hold the trash button, the Canon ISO selection comes up.

Go to Canon Menu C.FnIV Operation/Others (6) "Trash Can button" and change your setting from 2:ISO speed to 0:Normal
This should do the trick to enter ML menu.

Have you tried other compression settings? Maybe uncompressed 14-bit? See if you get a different assert log.

You are right dfort. I did not check the default settings, just kicked on mlv_lite to see what would happen.

Default was 14 bit loosless which explains the error message. Changing to 10 /12 / 14 bit uncompressed does not create any assert. 12 and 14 bit uncompressed  freezes LV instantly, but creates a file. 10 bits uncompressed seems to work w/ liveview.
Unfortunately I do not have the time to dig into it more deeply right now (posting all settings and so on).  So this is the right moment where all MLV_LITE experts should join the party. There is defenitivley a good base for intensive testing.

I would be so happy to just get focus peaking.  I have a lot of old M42 mount lenses and they are hard to focus quickly on the screen.  can't wait for a bit more progress here!  Thanks again!

You should test the latest build Critix published today. Focus peaking seems stable to me.

Is raw recording working as well?

Well, mlv_lite creates an .MLV file but you get the the following assert

Code Select Expand


ML ASSERT:
0
at mlv_lite.c:2697 (compress_task), task compress_task
lv:1 mode:0

compress_task stack: 216b88 [216c18-215c18]
0x0044C9B0 @ af2fc8:216bb8
0x0044C478 @ 44ca0c:216b88

Magic Lantern version : Nightly.2018Dec07.EOSM2103
Mercurial changeset   : 061afdbde1ad+ (crop_rec_4k_mlv_snd_isogain_1x3_presets) tip
Built on 2018-12-07 09:42:05 UTC by root@cristi.
Free Memory  : 383K + 1846K



I did not look into the file as such.

[(10.) (---) Adding "Histogram" in RAW RGB, Log and BANG! LV freezes when panning!]

And there is definitively progress! Great work @critix and @dfort!

Critix, your test build does not include a FIR file. I picket the one from dforts latest M2 version on his download page and that worked fine to activate bootflag in the cam. Since I am mostly into still photography I quickly made some test only in this area. Here are some very simple results. My set-up is M2 w/ EF-M 22mm, SanDisk ExtremePro 95 MB/s

NB: (+) positive (-) negative remark

1. (+) ML is able to boot in any shooting mode A+, C1, C2, movie. I used C2 for my quick tests.
2. (-) The ML default config makes live view freeze when panning. I mannaged to revive Liveview by pressing some buttons (no pattern), but it hung again after a while.
3. (+) Entering ML menu by holding trash can button works fine, also from frozen LV
4. (+) After inactivating all ML functions no more hanging in LiveView. I chose that method to activate ML functions one by one to narrow down the problem
5. (-) Leaving ML menu with "shoot" or "Menue" button brings you back to LV but there are no standard Canon overlays any more, not even AF indicators, just a clean LV. Pressing INFO button multiple times to switch between Canon LV modes does not change anything.
(6.) (+) BUT taking still pictures works fine
(7.) (+) Entering Canon Menu with Menu button and returning to LV brings back all stock overlays
(8.) (+) Activating "Global Draw in all modes" together with "Focus Peaking" works fine. Same behaviour when leaving ML menu described in (7.)
(9.) (+) Adding "Zebras" works fine too but brings up the known error messag "Raw error, falling back to YUV Overlays"
(10.) (---) Adding "Histogram" in RAW RGB, Log and BANG! LV freezes when panning!

(11.) (---) Same freezing LV when only "Histogram" is activated in "Global Draw in all modes". So histogram seems to be the bad guy.
So far my simple tests. I hope I can contribute more later on.

ML 2.3 is outdated...
You did already extract all files so copy the entire structure to your SD card. there is a .FIR file in the root directory which is to be used for ML installation by processing a firmware update.

Sent from my SM-G930F using Tapatalk

please check this link https://www.magiclantern.fm/forum/index.php?topic=18941.msg179807#msg179807.
@dfort made a very good documentation about upgrading and downgrading (Original post: Firmware update/downdate?) specifically for 5DMKIII 1.3.3 and newer releases. (I guess it works for all EOS models).

However, XMPs are named nil0004.XMP, rather than IMG_0004.CR2. Does this happen for you?

Yes. IMG_6764.CR2 got a sidecar file named nil6764.XMP

ML/SETTINGS can be found here https://drive.google.com/open?id=1uW_69RLXEnGiBBSmZIaSUbGOvb-Z5GDv:
I added an nil...xmp as well as the latet ASSERT.LOG to this folder.

Did the following steps (nothing fancy)
1. Activated lua.mo (no other module was active in parallel!)
2. restarted cam
3. Started lens.lua manually
4. Chose one of the 3 lenses suggested
5. Took a picture --> no assert
6. Changed script to autorun
7. restarted cam
8. took a picture --> ASSERT
9. Changed script setting from autrun back to manual
10. restarted cam
11. stared script manually
12. took a picture --> ASSERT

My first impression was that the assert was caused by a the autorun setting. But that was proven wrong as the assert also triggert when changing back to manual start. There was no logic explanation, I fear

[magiclantern-manual_lens_info.2018Feb02.60D111]

@a1ex
Ran my first test with magiclantern-manual_lens_info.2018Feb02.60D111 in photomode Av using the included lens.lua script together with my Samyang 8mm Fishey. Since 60D is not on 4K I thought it should not be a problem but unfurtunately I got the following assert after taking a picture.

Code Select Expand


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

PropMgr stack: 110c68 [110f68-10ff68]
0x00BA1C9C @ bacfb8:110d00
0xUNKNOWN  @ ba1d80:110ce0
0xUNKNOWN  @ bb13d0:110cd0
0x00BC8754 @ bb14c4:110cc8
0x00B9D0FC @ bc87c0:110cb8
0x1FE00CB8 @ 1fe036ac:110c98
0x1FE00378 @ 1fe00d14:110c68

Magic Lantern version : manual_lens_info.2018Feb02.60D111
Mercurial changeset   : e7ca98e11cd4 (manual_lens_info)
Built on 2018-02-02 19:26:24 UTC by jenkins@nightly.
Free Memory  : 313K + 1320K


Still both .CR2 and .xmp files got written to the card. 

Congratulations to this breakthrough - and happy birthday dfort!!


Sent from my SM-G930F using Tapatalk

Current nightly for 60D is made for firmware version 1.1.1 only. Hard to see how you got ML installed on 1.1.2 in the first place. Try to start your cam w/o ML using a fresh non bootable SD card. If this is successful downgrade Canon firmware to 1.1.1 if you intend to use ML again.

Sent from my SM-G930F using Tapatalk

Thanks for the new builds. Any reason why 100D is not listed (anymore)? Tx

If you are both in still photography and filming than the M2 is definitively the better choice over the M due to a better hybrid CMOS AF II - in the near future hopefully even with ML capability. @dfort and @a1ex have put a lot of energy in porting ML to this model, lots of things can be emulated already in QEMU. There are some new DryOS settings to be identified to make it happen. If you are eager to develop maybe you can assist to finalise the port?

Sent from my SM-T719 using Tapatalk

Now Selftest.mo got included in latest build magiclantern-Nightly.2017Sep29.100D101. But silent.mo is not. Is there a specific reason or can I just reuse the module from an older build as @OlRivrRat suggested?

If any of you is able to run the latest build, can you run the stubs API test from selftest.mo? Might give some clues.

I really would like to but the latest build magiclantern-Nightly.2017Sep27.100D101 does not include selftest.mo anymore, nor does magiclantern-lua_fix.2017Sep11.100D101. Just checked the zip files again, the module is simply missing.

silent.mo is missing too, by the way.

Both modules were included in magiclantern-Nightly.2017Jul12.100D101.

Does nightly boot for you? For me only running version is the one from Jul 12.

I have tried disabling, reinstalling, and newer builds simply dont boot the camera. O_o

Strange thing. Works like a charm here, both nightly 2017-09-15 and lua_fix 2017-09-11.

Sent from my SM-T719 using Tapatalk

@Walter. Your approach is really appreciated. Automating translations would reach many more people and lower the threshold for active contribution.
Personally I would prefer a WIKI like platform. Forum threats are built for discussions and that  makes it often difficult to  keep  "first post" up to date. So how about combining both methods (even though I have no clue how auto translated wiki should work in a consistent way, as manual alternations could be done in any  of the provided languages)

Sent from my SM-G930F using Tapatalk

@AOK
Are you aware of that ML is a project based in voluntary contribution? Feel free to participate in the process of porting ML to a new platform
Fresh resources and ideas are certainly welcome.

Sent from my SM-G930F using Tapatalk

In case you did not notice yet. @a1ex placed a pull request to merge lens_info into lua_fix which is probably the easiest and fastest way to get this function into nightly and also different experimental branches. Might be  good to comment this PR.

Shutter bug problems answered here http://www.magiclantern.fm/forum/index.php?topic=9741.msg189269.msg#189269

Sent from my SM-T719 using Tapatalk

My top 3 for stills
* focus peaking, especially for manual lenses
* dual ISO w/ ETTR (especially when you are used to dynamic range from FF like your 6D)
* advanced bracketing



Sent from my SM-T719 using Tapatalk

The internal SD bus is the limitation. Use a fast CF card instead.

Sent from my SM-G930F using Tapatalk

This is all very exciting progress so far and keep them rolling along!

+1

Sent from my SM-G930F using Tapatalk

Anyone here that explain these options in plain ENGLISH please as I asked in the OP. Many Thanks. Russ

for better understanding of diffraction effects please have a look at
http://www.cambridgeincolour.com/tutorials/diffraction-photography.htm

In general DOF calculation tries to approximate inifinite problems by using finite formulas. There are simpler formulas which deliver good results in most cases. Option "defraction aware" takes into consideration difraction effects and it leads to a more complex formula. However whether you benefit from the result is depending on your shooting scenario.

Sent from my SM-T719 using Tapatalk

Great news. Tx a lot

Sent from my SM-T719 using Tapatalk