Menu

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.

Show posts Menu

Messages - JohanJ

#51

Quote from: bastien42 on July 03, 2017, 09:12:20 AM
thanks all and if you have any advice (tips and tricks) for this camera feel free :) to share it with us so you know I've been reading the whole thread already so normally the use of this soft is already quite good

bastien.A

All creds go to  @nikfreak who made ML available on 100D😊



#52
Quote from: bastien42 on June 30, 2017, 04:37:24 PM
So i've dowload the following build "magiclantern-lua_fix.2017Jun24.100D101.zip", ... i've the console that boot every time i lauch the camera and some time randomly

There is a newer build on experiments page from today. No console anymore when booting with modules (i.e. all problems causing assert messages and initiating debug mode have been solved).

Are you really using all modules you have activated (thinking in terms of resource consumption)?
#53
Quote from: bastien42 on June 30, 2017, 04:37:24 PM
another wonder is in the user guide it is written "PLAY mode shortcuts

Q (550D), UNLOCK (60D), DISP (600D), LV (500D), FUNC (50D) or Picture Style (5D Mark II): show exposure tools (zebra, false color, histogram, waveform, spotmeter) and cropmarks (as configured from Overlay menu).

Has been discussed here http://www.magiclantern.fm/forum/index.php?topic=16040.msg182467#msg182467. For the moment not available on 100D.
#54
Camera-specific Development / Re: ML on EOS-M2
July 01, 2017, 08:38:32 PM
Quote from: nikfreak on July 01, 2017, 08:16:47 PM
100D is crippled by Canon. It really only has 4 movie modes to select in Canon menu

In fact all 7 modes are available also from canon menu, just that only the ones fitting to the chosen video mode (PAL/NTSC) are shown.

[EDIT] On 60D there are 2 additional VGA modes Crop 640x480 NTSC and Crop 640x480 PAL. So here you get in  total 9. Just an idea (even though it is another cam generation)
#55


Quote from: bastien42 on June 29, 2017, 09:01:57 PM
is there any way that we could change the bpp from 14 to 10 for raw because if so then it could be useful to record with better resolution and still don't override 40Mb/s

Please check experiments download page for 10/12 bit raw video. Now even for 100D, but not tested.

https://builds.magiclantern.fm/experiments.html
#56
Quote from: garfield72 on June 29, 2017, 06:07:12 PM
Ok it's good, I have the menu RAW video(MLV). I had not taken the good build. I set as on attached images, but when I want to REC, I have the message "Threads failed to start" then "OccupĂ© patientez". Is what my setting is good? I have a SD card SanDisk Extreme pro  32GB.
Thanks for your help
I am not an expert on MLV. When using your settings  I get the message "write speed needed: 53.0 MB/s at 25.000 fps". The internal SD bus is limited to write speed at ca 40 MB/s.
An MLV expert should step in here ;)
#57
Scripting Corner / Re: Lua Scripting (lua.mo)
June 29, 2017, 02:36:34 PM
Quote from: a1ex on June 29, 2017, 12:23:12 PM
For the last two, there's no raw_rec module in this branch, and mlv_lite doesn't give any errors. The raw_rec I already had on the card did not trigger any error (it refused to load, with status OldAPI).

Strange! I will check the SD card when returning home tonight. Normally I am deleting ML folders, auto...bin and .fir before loading a new version. No idea how this module came in there otherwise.

[EDIT] @a1ex: downloaded lua_fix for 100D and 60D from experiments page again: raw_rec.mo is definitively included in the modules folder for these builds. Probably a left-ower in makefile? When starting the raw_rec module on 100D I get exactly the same error messages as reported here:  http://www.magiclantern.fm/forum/index.php?topic=16040.msg186543#msg186543
Might be obsolete though when emliminating raw_rec.mo from these builds.

#58
Quote from: garfield72 on June 29, 2017, 11:24:10 AM
Thanks, so if I understand correctly, the build I use is not good. Does anyone have a functional version?

François
The one I have in use is from lua_fix experiment and it really works fine.  The messages I was referring to are under investigation. Module functionality is given even though there seems to be some null pointers floating around.
#59


Quote from: garfield72 on June 28, 2017, 10:45:00 PM
Thanks, I try the latest 100D build and after update firmware, when I turn on, I have 2 different screen depending on whether I'm in photo or video mode (see attached images).

I guess this is related to this:
http://www.magiclantern.fm/forum/index.php?topic=14828.msg186252.msg#186252
#60
Scripting Corner / Re: Lua Scripting (lua.mo)
June 25, 2017, 06:36:50 PM
Quote from: a1ex on June 24, 2017, 11:07:09 PM
That's yet another null pointer issue (likely in one of these modules, during initialization).

I tested all modules booting them separately or in a combination they are required to function (like mlv_snd needs mlv_rec to be activated too) and found the following candidates creating asserts:

dual_iso.mo
ML ASSERT:
a
at ../../src/stdio.c:44 (streq), task module_task
lv:0 mode:2


deflick.mo:

ML ASSERT:
a
at ../../src/stdio.c:44 (streq), task module_task
lv:0 mode:2


raw_rec.mo (2 different ones)

ML ASSERT:
new_entry->name
at ../../src/menu.c:1224 (menu_add), task module_task
lv:0 mode:2


ML ASSERT:
entry->name
at ../../src/menu.c:6430 (check_duplicate_entries), task menu_redraw_task
lv:0 mode:2
#61
Scripting Corner / Re: Lua Scripting (lua.mo)
June 24, 2017, 10:50:22 PM
Did some testing with the latest lua_fix.2017Jun24 both with 60D and 100D.
From a still photography's point of view a stable solution on both cameras, which is great! Did not dig into mlv though.

And the good news is that file manager is solid now. No hanging what ever I tried to provoke.

Still there is one artifact worth to mention. When activating modules and booting the camera I always get a console window with an assert message in the end, see log file below (same for 60D and 100D)

ML ASSERT:
a
at ../../src/stdio.c:44 (streq), task module_task
lv:0 mode:2


Magic Lantern version : lua_fix.2017Jun24.60D111
Mercurial changeset   : fe6b0207f229+744f5868a308+ (lua_fix)
Built on 2017-06-23 22:49:10 UTC by jenkins@nightly.
Free Memory  : 389K + 1546K


I had chosen dual_iso, ettr and file_man modules. The console remains active unless I turn it off in Debug/Module Debug (Off -->ON --> Off).

Strange also that additionally activating lua.mo provokes an assert again on (re)boot and writes an additional assert.log but the console window disappears after a few seconds and remains inactive. Is there any change in the console window handling lua.mo takes advantage of but other modules not (yet)?

Also not clear whether this assert has any consequence besides the console behavior and lots of log files written to the memory card.
#62
Scripting Corner / Re: Lua Scripting (lua.mo)
May 08, 2017, 09:19:08 PM
Just tried lua_fix Build #398 (04-Apr-2017 23:29:58). It has similar issues too as soon as file_man.mo is active! I did not get a total freeze but file_man is behaving odd after a while: when toggling through the folders the entire file structure suddenly disappeared and from this very moment trash/info/menu/q buttons were dead, and so was the back screen. It was still possible to take pictures but you cannot review them, att all. To get out from there I had to pull the battery, re-boot was not enough.

It all comes down to file_man.mo for builds both from 04/04 and 05/01. As long as the module is not activated, both builds seem to work properly (as far I could test it right now, which was not that deep!!).
#63
Scripting Corner / Re: Lua Scripting (lua.mo)
May 07, 2017, 01:06:28 AM
I got some instability with the latest Lua Update and fixes build for 60D magiclantern-lua_fix.2017May01.60D111. Basically my camera is just freezing. It could happen directly after starting up the camera or during shut down. It definitively happens when walking through the card file system using file_man module. Otherwise there is no reproducible reason or pattern. The only way out is pulling the battery.

Unfortunately there is no crash log I could provide for analyzing the circumstances. Did a low level formatting of the SD card but nothing changed. Using the latest nightly instead of the lua_fix build does not show these problems.

Is there anybody else encountering this problem?

#64
Scripting Corner / Re: Lua Scripting (lua.mo)
April 11, 2017, 05:55:53 PM
I would read @dmiligan's answer in another way. Instead of adressing ML specific  variables with a generic call as you suggested there should be the possibility to extend the list of API interfaces delivering the required information independent of the type and name of the variable currently in use for ML. But that would need more programming efforts in Lua of course, right?

Sent from my SM-T719 using Tapatalk

#65
A1ex had included 100D on the experiments page for branches lua_fix and manual_lens_info. The latter 25th of jan 2017. See my posts for the focal lens info problem on 60D xmp files (50mm fixed in Lr) compared to 100D (initial focal length and therefore working fine in Lr)

Sent from my SM-T719 using Tapatalk
#66
100D is missing. Build seems to be broken since merging w lua_fix.

Sent from my SM-T719 using Tapatalk

#67
On 60D the overlays can be activated for picture review by pressing the unlock button. But Rebels do not have this button. One thought for the feature request: adding the overlays to the INFO button when reviewing the pictures might be interesting. Today one can toggle through different review modes. Why not having an additional "overlay" mode? Just thinking aloud..

Sent from my SM-T719 using Tapatalk

#68
Scripting Corner / Re: Lua Scripting (lua.mo)
April 05, 2017, 09:39:29 AM
@nikfreak  @a1ex
Just recognised that 100D disappeared from experimentals for lua_fix and manual_lens_info. Probably broken build?

Sent from my SM-T719 using Tapatalk

#69
Scripting Corner / Re: Lua Scripting (lua.mo)
April 05, 2017, 08:47:04 AM
Thx a1ex. Much appreciated. I know there is a lot ongoing. Exciting times. Thx again.

Sent from my SM-T719 using Tapatalk
#70
Scripting Corner / Re: Lua Scripting (lua.mo)
April 04, 2017, 09:51:56 PM
Last weekend I was testing magiclantern-lua_fix.2017Mar26.60D111 mainly for stability of standard ML functions for still shooting. Looks good to me on my 60D. Especially the dynamic ML menu is much appreciated! Next weekend I will do similar tests w/ 100D.

The only Lua script I have in use so far is lens.lua from the manual_lens_info branch which was not running successfully on this build. I had to realize that certain changes  from manual_lens_info branch are not included in lua_fix, like moving common ui code into lib/ui.lua (bdcd13e) or introduction of  xmp.lua metadata library (ed6b260).

@dmilligan @dfort
Wouldn't it be useful to combine these two branches into one as both are providing useful Lua improvements (and much more of course)?
#71
@wizbrewery
Regarding trap focus on 100D please follow the link below
http://www.magiclantern.fm/forum/index.php?topic=16040.msg166383.msg#166383

Sent from my SM-T719 using Tapatalk

#72
Quote from: dfort on January 30, 2017, 06:27:35 AM
I would have thought that the xmp file would take precedence over the EXIF tags in the CR2 file. Just in case that modifying a CR2 with exiftool doesn't give the same results could you please upload a sample CR2 with the manual lens xmp from the 60D so we can take a look at it?

I can confirm that EXIF tag FocalLength = 50 set by 60D is the reason for the wrong focal length in Lr. Modifying a sample CR2 using exiftool -FocalLength=0 did the trick. Import to Lr showed the correct value from the xmp file.

Conclusions
1. Lr chooses EXIF tags from CR2 files over xmp values if not initial (=0)
2. There are different default values for different models. For 60D it is 50mm for 100D it is initial. I checked even som older pics taken with a 350D and there it was initial too.

Sample shots (w/ and w/o modified EXIF) for 60D and 100D, as well as a modified Lr lens profile for Samyang 8 mm can be found here (see File_info.txt for details):
https://drive.google.com/open?id=0B7N2Wbxd7m2gS293V1Z3a2hqYVk
#73
@dfort
QuoteStrange thing you got going on with the 8mm fisheye showing up as a 50mm.

Today I found the reason for it: the 60D writes 50mm into EXIF:FocalLength embedded in the CR2 file

EXIF info from a sample picture using magiclantern-manual_lens_info.2017Jan26.60D111:

exiftool - FocalLength IMG_6397.CR2 ======== IMG_6397.CR2  Focal Length                    : 50.0 mm



I also tested the latest magiclantern-manual_lens_info.2017Jan26.100D101 using a 100D instead of the 60D.

exiftool - FocalLength IMG_3743.CR2 ======== IMG_3743.CR2  Focal Length                    : 0.0 mm


For the 100D everything just worked as expected: XMP file contained all necessary information of the manual lens, import to Lr (6.8 on Win10) had no problem at all, and my proper lens profile for this lens was found immediately. And even  FocalLength 8 mm was shown and used correctly in the processed xmp!

Now the remaining question is how to make Lr use FocalLength from the xmp file created by ML instead of existing (but dummy) information embedded in the CR2 file?
#74
Quote from: a1ex on January 26, 2017, 01:30:06 AM
Added to experimental builds.

While you are at it, please run the stubs API test from the selftest module, from the latest lua_fix build.
@nikfreak is already on it for the latest lua_fix build. I ran another stubs API test for latest manual_lens_info.2017Jan26.100D101. 2 Fails only. Log can be found here https://drive.google.com/file/d/0B7N2Wbxd7m2gVEpUdjFCQUc2MzA/view?usp=sharing

#75
Quote from: Rossik on January 29, 2017, 12:25:42 AM
sorry for such a basic question, but I am super keen to start learning how to use my camera and to install Magic Lantern but my 100D seems to be missing the 4th Setup screen - the one which shows what Firmware you are running.....

Is there something obvious that I am missing ????

Help !!
I guess your camera is in auto mode or similar. Chose one of  M/Av/Tv or P mode and you will find your missing menu [emoji6]