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.

Topics - scrax

Pages: [1] 2
Forum and Website / what happened?
« on: May 06, 2019, 09:35:00 PM »
I can't see anymore the developers parts about scripts and modules...

General Chat / Foveon sensor (SIGMA cameras)
« on: April 21, 2019, 05:20:29 PM »
Anybody has some experiences with it?
From what I understood it has only 100 ISO real because of no amplification before A/D
But no bayer and a lot more details than CMOS

It's something new for me, I was aware only of CMOS (ok the foveon is a particular CMOS by the way) and CCD sensors...

With only 100ISO I'm curious about long shutter time noise

General Chat / Canon emulator
« on: April 08, 2019, 10:42:51 PM »
After plaing all day with qemu, was thinking about it and got one curiousity,

canon dev's have some sort of emulator too?

Or better

usually when a firmware is done how it is developed? they test it on real hardware or they use an emulator, or both? Also i think they have special dev boards maybe?

Another silly idea that came into my mind was if, at least in theory, could be possible to use qemu on (don't know, maybe a rasperry) to simuate canon software and use a module for the camera and a keyboard (maybe modded with just the needed buttons) to control it? For some camera qemu can take pic? Is it right?

EDIT: Last... (for now)
What about this: a port of qemu for android if I understood right. Anybody have already tried it for ML?

General Development / 5DC boot cache hacks help to fix it
« on: April 01, 2019, 10:21:56 AM »
I've tried to restore 5DC to build on vxworks_dm_spy branch and got an almost working build with lot of problems.

After tring to understand the differences from 40D and 450D by reading all topic bout those ports and comparing the code there are some part in 5DC that I cant understand. Alex and Coutts did a great in finding lot of stuff but there are some maybe important stubs not found like current_task.
I tried to find some but with my zero understanding of ARM i can only find a couple.

From what I understood of the boot process 5DC is the only one that is using ARM patches to load ML and maybe those are now partially broken by the changes in ML codebase? In past Coutts first and then 0xAF with help from g3gg0 worked to enable cache-hacks on 5DC but still we don't have it working. I've tried to figure out how to mke it work bu I've just figured out that i've no clue on how to go on, so I'm here for help.

I don't know what is needed to be done to fix the boot process or what can I do like boring easy stuff maybe, I can provide dumps if needed. I'm still making my test without qemu because can't figure out how to make it work with 5DC but didn't tried a lot.

I'm also tring to find current_task and in qemu model_list.c there is a note that curent_task_addr is in MEM(0x2D2C4) is it the same?
And how do I look it out?
Actually my build of ML can't show fonts or save seems, so main output I have is blue and red led. But I can build and load the old port based on the last code from 0xAF and so I think I can use that for getting that MEM maybe

I have updated my old PR for Custom Modes and more GUI options for my 600D to a separated module.
Now my 600D has 3 c-modes and more setting to change from the standard dialog canon use for the four arrow button: WB, Drive mode, Focus option and PicStyles.

The module override button presses in photo mode (not LV) of the arrow to open up the GUIMODE_Q of the same dialog screen because it don't need set to pressed to change the value (and I like it better because if you press halfshutter you don't lose the setting).
Then in those dialog screen it show additional seeting to change with arrow, scrollweel and other buttons.

To work on other camera it needs some missing GUIMODE in platform/ and uncomment #define FEATURE_REBEL_GUI  in platform/
If someone with those cameras can find those guimode we can make it work on other camera:
500D, 550D, 650D, 700D, 800D, 1000D, other Rebels? (how to find in second post)

For 500D I can compile the module but Picture Style override option will not work for this two GUIMODE because missing
Code: [Select]
  #define GUIMODE_Q_EXP_COMP_AEB GUIMODE_PICTURE_STYLE // Q Exposition compensation and AEB
  #define GUIMODE_Q_ALO GUIMODE_PICTURE_STYLE // Q Auto Light optimizer settings

(this is what I have for 700D for example):
Code: [Select]
#define CURRENT_GUI_MODE (*(int*)0x2658C) // in SetGUIRequestMode
 #define GUIMODE_PLAY 1
 #define GUIMODE_MENU 2
 #define GUIMODE_FOCUS_MODE 0x123456
 // #define GUIMODE_Q_PICQ 0x
 // #define GUIMODE_Q_EXP_COMP_AEB 0x
 // #define GUIMODE_Q_ALO 0x
 // #define GUIMODE_Q_ISO 0x
 // #define GUIMODE_Q_FOCUS_MODE 0x
 // #define GUIMODE_WB 0x
 // #define GUIMODE_Q_WB 0x
 // #define GUIMODE_DRIVE_MODE 0x
 // #define GUIMODE_Q_DRIVE_MODE 0x

The module is hard to explain but once used is hard to work without because it make really faster to change setting without opening menus.
To see some old screenshot: here

Module writing Q&A / use canon icons in module
« on: March 13, 2019, 12:25:35 PM »
I've updatd my old C-Mode feat and Customized GUI to a module, finally. My goal is to make it compatible also with other rebel line cameras, for now it can compile and work good only on 600D and (with some less feat due to GUIMODE missing) for 500D.

But I would like to make it smaller and cleaner by using some canon icons that are not included in bmp.h
one icon is the flash +- shown when setting flash exp. comp.
other icon are the icon for the metering mode (i don't know if they are 4 different icons or only 3 icon for the different states combined)
Also the icon with only the up and down arrow I'm missing from canon.

For now I'm drawing them line by line with draw_line, draw_circle and so on, but is obviously not the best way.
I managed to add the icon.png for the up and down arrow and the play button but I'll prefer to use the one from canon if possible.

Any help or suggestion?

Another doubt is for the option to load some camera setting after stat-up. Actually I'm using the module main task to check if settings are to be loaded and to load them once, but for each loop it will keep checking if settings need to be loaded and if they are already loaded does nothing.
Seems a waste of resource, not? So where should I put the code in the module to make it load once only after startup?

I've attached the icon I' looking for

Convert your magic lantern files to .dng image sequences is a GUI wrapper based on platypus for the command line tools raw2dng by Alex.
I'm developing this to help osx user who are not familiar with command line stuff.
The approach is to have a simple draggable app that will make it easy for anyone to convert raw video file made with Magic Lantern.

To use it simply extract the app from the last .zip package and optionally move it to your Applications folder, I like to have the icon in the finder window as you can see in the video so to have it always ready.
Once extracted drop a ML .raw file on it's icon or double click it and drag the file on the window of the app.

It will convert the file in a new subfolder in the same folder of the raw file converted. The name of the subfolder is same as the .raw file converted

All versions are hosted here: ML Things Downloads
To install: Just delete/overwrite any older version you have with last .zip package contents

Optional Settings
Since 0.13 is possible to set some options. To open up settings dialogs you need to have to drag icon into an open windows (like you do with raw files to convert them).
So far you can set:
  • a working folder were raw files will be copied and then converted (if none selected file will be converted in the same directory the raw is)
  • ProRes generation On/Off
  • Custo or auto White Balance (default auto)

To Do
-Find a way to make bigger file conversion work
-Batch convert all raw file inside a folder

- MLTools integration (half done)

Changes Log
- First test for conversion options like set wb, working folder and optional ProResHQ 4444.
- Updated bin, removed jpg and avi conversion, for now only dng and ProRes.
- Cleanup, updated bin with vertical banding fixes, added jpg and avi conversion too (but slows down the process for multiple files).
- Accepts more than one file or folder dropped at time (from bashi suggestion).
- New way to convert file directly into destination folder, check if it's working or you too.
- Fixed some error in finding raw files in folders
- Updated with source fixes (2013/05/22)
- better handling of generated .dng by Captain Hook (works with 62Gb file too, now)
- fixed 64bit conversions problems by rodobot (confirmed workin for file bigger than 10GB)
- First folder support implementation, same name of the raw file for the generated folder (from swinxx suggestion)
- Can convert more than one raw for minute
- Fixes spaces in folder errors by Captain Hook
- first release

Known issues Wrapper package
- dead pixel problems, (going back to ufraw maybe will solve it)

Known issues osx command line tool
- Folder are not full cinemaDNG (they can't be imported in DaVinci Resolve) - Dedicated Discussion Thread -

Solved issues
- raw2dng not compatible with latest ML nightly recorded raw
- Generate dng directly into dest. folder
- Latest (22/05/2013) compatibility fix from source
- Problems with more than 42 Gb raw  (thank's to Captain Hook for the fix)
- Can't convert more than one file for minute
- Don't works with spaces in folder names for .raw source  (thank's to Captain Hook for the fix)
- Can't convert file bigger than 2Gb. (thank's to rodobot for the fix)

Tip: To being informed about new updates follow this topic

I've made a silly mistake when adding quality pic mode option to my custom mode feature, and that has bricked my 600D.
I've tried to reset it but nothing worked.

What I accidentally set is: PROP_PIC_QUALITY

Actually I got err70 in any mode/ startup combination, with or without card.

Crash log:
Code: [Select]
at DevelopCombination.c:108, task RscMgr
lv:0 mode:0

Magic Lantern version : v2.3.NEXT.2013Apr09.600D102.C-Modes.scrax
Mercurial changeset   : c277177d95c0+ (unified) tip
Built on 2013-04-08 23:47:48 by scrax@MacBook-Pro-di-scrax.local.
Free Memory  : 290K + 1062K

Code: [Select]
Tue Apr  9 00:52:36 2013
     0:     9.267 [STARTUP]
K286 ICU Firmware Version 1.0.2 ( 3.8.3 )
     1:     9.331 [STARTUP]
ICU Release DateTime 2011.11.25 11:00:17
     2:    11.252 [SEQ] seqEventDispatch (Startup, 0)
     3:    11.279 [STARTUP] startupEntry
     4:   113.387 [STARTUP] startupPropAdminMain : End
     5:   113.509 [SEQ] seqEventDispatch (Startup, 1)
     6:   113.541 [STARTUP] startupPrepareProperty
     7:   116.539 [SEQ] seqEventDispatch (Startup, 2)
     8:   117.233 [RSC] hMemoryQueue (0x620010) hStorageQueue (0x640012)
     9:   124.261 [RSC] ERROR SetDevelopImageCondition DevelopCombination.c 107
    10:   125.263 [RTC] !! RTC CHECK ERROR !!

    11:   130.159 [JOB] InitializeJobClass (ID = 19441, Num = 16)
    12:   131.805 [STARTUP] ERROR ASSERT : DevelopCombination.c, Task = RscMgr
    13:   131.891 [STARTUP] ERROR ASSERT : Line 108
    14:   131.938 [STARTUP] ERROR ASSERT : FALSE
    15:   132.028 [STARTUP] ASSERT : Time 1899/12/31 0:0:0
    16:   134.417 [STARTUP] startupErrorRequestChangeCBR (0x1d)
    17:   134.550 [STARTUP] startupErrorRequestChangeCBR : ErrorSend (101, ABORT)
    18:   134.974 [CERES]  RegisterGPSInfoCallback
    19:   135.691 [EM] emLockControl (TYPE_JOBSTATE = 0x0)
    20:   137.106 [JOB] InitializeInnerDevelopJobClass (ID = 19441, Num = 16)
    21:   137.154 [JOB] InitializeMultipleExposureSaveAndEndJobClass ( Num = 10 )
    22:   139.181 [SND] Seq LPC fin
    23:   143.820 [ENG] [ENGIO](Addr:0x4fb40000, Data:0x   30000)
    24:   150.746 [FM] FM_RegisterSpaceNotifyCallback
    25:   150.954 [FM] FM_RegisterSpaceNotifyCallback
    26:   156.878 [SHTP] spsInit
    27:   165.111 [TERMINATE] SHUTDOWN init comp
    28:   165.248 [TERMINATE] Abort init comp
    29:   165.674 [WFT]  PROP_WFT_IMAGE_TRANS (1)
    30:   168.615 [MC] PROP_GUI_STATE 0
    31:   169.620 [MC] JobState 0
    32:   171.319 [MC] PROP_LCD_OFFON_BUTTON : 0
    33:   171.897 [MC] PROP_VARIANGLE_GUICTRL : Enable
    34:   172.367 [MC] regist master CardCover
    35:   173.982 [MC] Disp Error : 70

General Development / [SOLVED] 600D problems to load if self compiled
« on: April 08, 2013, 07:13:08 PM »
I was thinking that my changes was the problem, but it's not.
If I compile myself from source for 600D I need to do make 600D; make clean; make 600D to be able to compile ML (first make 600D fails).
But the compiled autoexec will blink led 3 time slow and then 3 time faster after closing card door even with camera off. Battery pull is needed to reset camera.

I don't know if something has changed that could give me those problems.

Scripting Q&A / QRcode for script import/export?
« on: March 17, 2013, 11:11:36 PM »
I was asking me if it could be possible to use QRcode to send scripts to the camera without using the card, with a QRdecoder in ML working with the liveview stream.
And maybe also generate qrcode incamera from script to share them with other ML body using silent pics on the destination and the display on the source.
Maybe big script are a problem, so far what I've tried to convert to qrcode seems to be short enought:

General Development / High-speed video with timelapse
« on: February 15, 2013, 05:00:22 AM »
That's a feat that I'm thinking about for some time now, but don't know if could work.

The idea is to shoot a constant repetitive fast event like an industrial machine doing his job quickly with a camera triggered by the machine movement at a constant time. After each pic camera will add a 1/n of delay before tacking a pic and wait for another trigger. That way we will have in the end a sequence of the machine states with n being our fps

To trigger camera I think I can make a simple mechanical switch that go in to cable release port.
PicoC will be good I think to implement the delay but is the camera precise enough?
Also was thinking about using audio trigger but don't know a lot on how it could be best way to do it.
We can't go faster than 1/4000 on 600D but i thing that 1/500 will be already interesting.

Reverse Engineering / ML Camera usage log
« on: February 14, 2013, 07:05:04 PM »
I was thinking about a feature that maybe could be useful for collecting feedback, usage patterns and so on during camera use. Those data data can be useful for debuggin problems, finding out what are  the most used features and so on.

I don't know is canon log is doing already this but is probably don't take into consideration ML.

Like a file with data about how long camera went on, how many pics taken, in wich mode, internal temp during operations, card space, and so on... All things that will be useful to make some graphics to see also hour way to use the camera, it will help a user to see which are features he use most, how long battery are lasting, debug problems and so on...
If possible we could add a manual battery management for rebel models, so that log will be useful also for keep track of battery status (my first idea about that is that we can make arrow selecting the battery at startup, like: put new battery called "left" and when switching on camera keep left arrow press will select it in ML battery manager, 4 battery can be managed that way).

Also lens used and focus mode etc will be all interesting thing to keep track. It can also be used in a professional environment to keep track of what your assistants/collaborators are doing with your gear during work ;)

The main question is will it be a battery/CPU killer feat.?

General Chat / Video users please explain me about 24fps vs 30fps
« on: February 13, 2013, 04:37:33 PM »
I don't know how it works that thing that film fps is 24 vs 25fps for EU and 30 for USA...

From what I know here in EU we have 50hz in hour home so all lightbulbs for example are flickering at that frequency, in USA it's 60Hz so the difference in video fps is justify by that. if we record a scene at 60fps lit by a lightbulb powered by a 50Hz current we will record also the fliker since light will be of different intensity each frame, with 25 fps we will record in sync with the current of the lightbulb so frame will get all the same light.

My question is if we record at 24fps in EU will have little off sync, maybe (I don't know) it's not visible, but in USA it will be a problem, or not? So how can a videomaker work with 24fps in 60Hz country? Does he need some particular transformer that changes the current freq for the light used? Or there are light that flickers at 24fps and support both 50 and 60Hz current?

Just curious

This is a little explanation about those two features added to the 500D and 600D

DIALOG TRICKS... (based on code from Greg)

From that menu you can enable more settings in photo dialogs opened by camera buttons like ISO and arrows.

ISO button:

  When enabled will add Flash exp. comp. to ISO dialog (up or down arrow changes value), and toggle HTP with PLAY button;

WB up button:

  When enabled will add Kelvin selection to WB dialog (up or down arrow changes value);

DriveMode left button:

  When enabled will add MeteringMode to DriveMode dialog toggable with PLAY button and UP or DOWN arrows;

FocusMode right button:

  When enabled will add Focus Pattern selection to FocusMode dialog.
PLAY changes central focus patterns;
UP/DOWN arrows changes vertical patterns;
scrollwheel changes horizontal patterns.

PicStyle down button:

  When enabled will open another (user selectable) dialog instead of PicStyle dialog (shown with C-modes enabled);
Options are: Quality, Exp. Comp., Flash Exp. Comp., ALO, OFF (Pic Style)

1) Add focus pattern selection to Focus dialog
2) Make alternative PicStyle dialog selectable (like set button in C.Fn for example)
3) Add max ISO selection for AUTO mode in ISO dialog (with ZoomIn button).
4) Add UniWb to PLAY button when in WB Dialog (it will need to go to LV and back probably for it to work).
5) Add ALO/HTP toggle with PLAY button in ISO dialog added.

General Development / 600D Photo info display, new layout
« on: December 27, 2012, 06:23:10 AM »
Inspired by Pel, I've moved around something in the photo info display of the 600D to make space for copyright and other info:

Now WB shift will not conflict with WB bracketing icon and bottom space is free for copyright info, need to understand how to add them now.

Feature Requests / Set+MainDial function toggle from play mode
« on: December 27, 2012, 05:58:05 AM »
Is it possible to make SET+UP/DOWN BTN in PLAY mode toggle selected function for Set+MainDial?

Feature Requests / ML MyMenu Idea - could be done?
« on: December 26, 2012, 10:27:44 PM »
Is possible to add a menu in ML filled with the menu items from all other menu loaded, submenu item to?
If yes we can add it so to have a list of all menu item (by default all hidden), when in edit mode user can enable most used items in that list so to unhide them in ML MyMenu.
With that users can chose if having all what they use in one menu (MyMenu) only (hiding all items from the "real/principal" menu), or to keep some at hand in MyMenu and something else less used in other menu.

Reverse Engineering / Flash prop
« on: December 17, 2012, 10:35:07 PM »
I've started to add flash prop to 600D using the 580EXII, any advice on what name to use?

will update this post with what i've found...

800200090004:8300015f00000from 000 to 15f when some setting is confirmed with SET
800200010004:5f00000from 0 to 5f when some setting is confirmed with SET
800400130004:000000Flash Firing: Enable
800400130004:100000Flash Firing: Disable
800400140004:000000E_TTLII Meter: Evalutative
800400140004:100000E_TTLII Meter: Average
800300380022:800448003800001Flash Settings: ETTL-II
800300380022:810448003800003Flash Settings: Manual flash
800300380022:820470123848003800001Flash Settings: Multiflash
800300380022:820470123848003800001Flash Settings: Frequency 199 to 1 = 0xC7 to 0x01
800300380022:820470123848003800001Flash Settings: Flash Count from 1 to 18 maybe more? in hex 0x01 to 0x12
800300380022:800448003800001Flash Settings: 1st curtain
800300380022:80044a003800001Flash Settings: 2nd curtain
800300380022:80044d003800001Flash Settings: Hi-speed
800300380022:1000800448003800001Flash Settings: Flash exp. comp: +2ev
800300380022:d000800448003800001Flash Settings: Flash exp. comp: +1.6ev
800300380022:b000800448003800001Flash Settings: Flash exp. comp: +1.3ev
800300380022:800448003800001Flash Settings: Zoom Auto
800300380022:300448003800001Flash Settings: Zoom 24mm others: 5-7-9-b-d-f
800300380022:80040048003800001Flash Output: 1/1
800300380022:80043848003800001Flash Output: 1/128
800300380022:800448003800001Flash Settings: Wireless func. disable
800300380022:80046830001006003800001Flash Settings: Wireless func. enable
800300380022:80046830000006003800001Flash Settings: Master Flash disabled and Channel All
800300380022:80046830001006003800001Flash Settings: Master Flash enabled and Channel All
800300380022:80046830002006003800001Flash Settings: Master Flash disabled and Channel A:B
800300380022:80046830003006003800001Flash Settings: Master Flash enabled and Channel A:B
800300380022:80046830004006003800001Flash Settings: Master Flash disabled and Channel A:B:C
800300380022:80046830005006003800001Flash Settings: Master Flash enabled and Channel A:B:C
800300380022:4830009006003800001Internal Flash Settings: Wireless Flash enabled EXT:INT
800300380022:483001B006003800001Internal Flash Settings: Custom Wireless enabled EXT:INT
800300380022:4830010006003800001Internal Flash Settings: Wireless Manual Flash enabled EXT
800300380022:4830012006003800001Internal Flash Settings: Wireless ETT-II Flash enabled EXT
800300380022:4830019006003800001Internal Flash Settings: Wirl. en. EXT+INT or Custom Wir. Ext. All and Int.
800300380022:80046830000006003800001Flash Settings: Channel 1
800300380022:80046830100006003800001Flash Settings: Channel 2
800300380022:80046830200006003800001Flash Settings: Channel 3
800300380022:80046830300006003800001Flash Settings: Channel 4
800300380022:80040680000006003800001Flash Settings:  Group A output 1/1
800300380022:8004206820000006003800001Flash Settings:  Group A output 1/16
800300380022:8004386838000006003800001Flash Settings:  Group A output 1/128
800300380022:8004386838000006003800001Flash Settings:  Group B output 1/1
800300380022:8004386838000006003800201Flash Settings:  Group B output 1/16
800300380022:8004386838000006003800381Flash Settings:  Group B output 1/128
800300380022:8004386838000006003800381Flash Settings:  Group C output 1/1
800300380022:8004386838000006003820381Flash Settings:  Group C output 1/16
800300380022:8004386838000006003838381Flash Settings:  Group C output 1/128
800300380022:800468300010006003800001Flash Settings: A:B fire ratio 1:1
800300380022:800468300010000003800001Flash Settings: A:B fire ratio 8:1
800300380022:80046830001000c003800001Flash Settings: A:B fire ratio 1:8
800300380022:8004683000100180c003800001Flash Settings: Grp.C exp.comp +3
800300380022:8004683000100100c003800001Flash Settings: Grp.C exp.comp +2
800300380022:800468300010080c003800001Flash Settings: Grp.C exp.comp +1
800300380022:800468300010000c003800001Flash Settings: Grp.C exp.comp 0
800300380022:8004683000100f80c003800001Flash Settings: Grp.C exp.comp -1
800300380022:8004683000100f00c003800001Flash Settings: Grp.C exp.comp -2
800300380022:8004683000100e80c003800001Flash Settings: Grp.C exp.comp -3
800300380022:4030001006f00f00001Internal Flash Settings: Normal firing
800300380022:4030001016f00f00001Internal Flash Settings: Easy Wireless
800300380022:4030001026f00f00001Internal Flash Settings: CustomWireless
800300380022:4030001016f00f00001Internal Flash Settings: Easy Wireless flash exp. comp.
800300380022:4030001006f00f00001Internal Flash Settings: Wireless custom. External flash exp.comp -2
800300380022:4030001006f00f0f001Internal Flash Settings: Wireless custom. Internal flash exp.comp -2

aa= Flash. Exp.comp.
b = Zoom
c = Flash mode: Ettl-II, Manual, Multiflash
d = Wireless func
e = 1st, 2nd curtain, hi-speed
ff* = Flash power values from 1/1 to 1/128 1/3stop: (2,5,8,a,d,10,12,15,18,1a,1d,20,22,25,28,2a,2d,30,32,35,38)
gg = frequency (199 = 0xc7, 1 = 0x1)
hh = flash count (hex like before 1 = 0x1 18 = 0x12)
ii = Grp.C exp.comp
jj = A:B fire ratio
k = Channels (1,2,3,4)
mm = Master Flash and Channel Groups
nn = Group A output
oo = Group B output
pp = Group C output
qq = Built-in flash mode
rr = Internal Flash Settings: only int. exp.comp
ss = Internal Flash Settings: Easy Wireless flash exp. comp
tt = Internal Flash Settings: Wireless custom. int. flash exp.comp
zz = change only when in manual flash, unknown
*can change if Flash mode changes (saves the value each mode has set and restore it if the mode is recalled back)

Main Builds / New features and documentations
« on: December 09, 2012, 03:37:59 PM »
We should start to document new features added to nightly build so to have an idea about what needs to be added to the documentations.
Is there a way to list all menu items that actually are missing the contextual menu?
I'm doing it by hand so far, but I'm using 2.3 help files, so i'm not sure if something is updated in the repo.

Writing doc is something that all users can do and here you can find what is new and needs to be completed, rewritten or updated and so on.
Those are neW things added since 2.3 that are missing documentations:

- Audio
  - Override Settings
  - Mic Boost
  - Digital Gain
  - Beep and Test tone
  - Sound recorder
- Expo
  - ML Auto ISO
  - Expo.Lock
  - Expo.Presets
- Movie
  - Stop recording
  - Gradual Expo.
  - FPS Ramping
- Shoot
  - AdvBraketing
  - TimelapseRamping
- Focus
  - Stack Focus
  - Focus step settings
  - Focus patterns (new submenu for selecting them)
- Display
  - LV brightness
  - (Display shake)
  - Anamorphic
  - Advanced settings (and submenu items too)
- Prefs
  - Image review (it's there but needs more detailed info)
  - Focus box settings
  - Warning for bad settings
- Debug
  - Benchmarks
  - Show CPU usage
  - Image buffers
  - Snap simulation

Anybody who want's to help ML project fell free to help in expanding the help pages, I'm making a rough scheme but there is the need of someone that is good in writing, so please contribute.

Feature Requests / incamera RAW to JPG theory
« on: December 08, 2012, 02:41:13 AM »
Since canon saves raw and jpg together i suppose that there could be some way to force it to convert already shot raw pic. Even  if the feat is not a lot useful (can be made in post) i think that finding out how fo do it could explain more how pics are tacken and help in finding how to do other things like noise reduction shoot...
Has anybody already investigated this?

General Chat / Warranty and ML - User Reports
« on: December 08, 2012, 12:53:26 AM »
Please guys if you had experience about Canon servicing or not your camera under warranty with ML installed, post about it here so we can have a more clear idea on how ML influences warranties. ;)

Forum and Website / hosting issue?
« on: December 04, 2012, 07:48:35 PM »

This month i had (just twice in a month) that screen when loading the forum, it's not a problem just an information, since after a refresh all worked perfect as usual :)

Feature Requests / Clean card from unused movie log and script
« on: November 10, 2012, 03:01:18 AM »
Could be possible to add an option to delete all unused movie log and script generated by ML?
Unused are for example if i have movie log on and i take some test or wrong shot and then i delete them, i end up having a lot of log file unused.
same thing could happen with script, so I would like an option to automatically delete them best would be when shutting off.

General Chat / what do you all think about the lytro?
« on: November 09, 2012, 09:16:36 AM »

What's your opinion about that camera? I'm not talking about porting ML  :P
but what's the purpose', for having digital focusable pic? Macro maybe could be interesting...
I think i can't understand it well...
Are printable?

Here is the first test version for MLTools bundled with last version of ML 2.3 (for simple install on mac).
Maybe better to have termina off and run it twice first time should be needed...
MLTools is a droppable app that helps with file and script made with ML.
At first start will check and install dependencies, then will show a simple dropdown menu with some options.
First time be sure to check MLTools Preferences button for setting up your working folder (where file will be imported and converted), your import preferences and if you want to rename jpg file with date taken.
File transfer makes a checksum verification before deleting imported files (if you chose to move them).

If autoimport is off you can use MLTools simply by selecting an option and then pressing next button.
Options are:
-Write Magic Lantern settings on card: It will write previously saved settings from MLcard on a new card (to have same MLsettings on multiplecard, works also for cropmarks)
-Save Magic Lantern settings from card: Saves to your working folder ML settings and cropmarks from the actually mounted ML card
-Delete  saved Magic Lantern settings: deletes ML settings and cropmarks from the disk
-Toggle Autoimport feat.: Activate or deactivate autoimport feat. When active autoimport will automatically check ML card for file to import and convert, if no card preset it will show an import dialog asking for files or folder to process
-Install ML on card with saved settings: Installs ML 2.3 and saved settings on a new card (it needs to be formatted on camera before this step)
-Scan card for ML generated file (default): Automatically scans ML card for files, scripts to import and convert into the working folder.
-Toggle Unmount after import: Option to unmount card after file import (useful with autoimport option)

You can use manual mode for preparing multiple card with same ML settings and cropmarks,
After setting up all your cards, turn autoimport on, unmount on and with Image Capture set MLTools to start when the card is inserted.
That way MLTools will start and import your file in the working folder you chose and the it will convert MLscripts, 422 file and so on if needed.

If you want to convert scripts or files from a folder you can just drop them on the MLTools icon. MLTools can convert RAW, HDR script, HDR video (if video log is on in ML), 422 file, Focus stack script (to be tested more).

From here you can chose to set up various options of MLTools like:

Working Folder: where to save your imported and converted files (default ~/MLTools/),

File Import: import files by copy, move or nothing (default copy).

Rename by date: if you want to rename file by date taken (default no renaming)

It's tested so far only on my system with osx Lion 10.7.5 so report all your experiences what works and what not please. Make backup of your data on card or use test shot before using it for important files.
Some functions like script conversion may not work right cause recent changes in ML, they should be updated maybe.


MLTools 0.8 fixes: manually close to debug better, smaller size.

MLTools 0.7 fixes: added video RAW import and conversion, fixes to md5 check and folders checks.
MLTools 0.6 Alpha test: fixed some error and folder scan not always working.
MLTools 0.5 Alpha test: more cleanup, waiting feedback
MLTools 0.3 Alpha test: clean up a little, feedback needed).
MLTools 0.2 Alpha test: New version with most of dependencies integrated to reduce install problems and errors, only PIL needs to be installed (seems there are some problem with that, more feedback needed).
MLTools 0.1 Alpha test: First test version to test, waiting for feedback.
REQUIRED: command_line_tools_for_xcode_june_2012.dmg (154,6MB) from Apple here (is free but needs registration first) or you can install 1.83GB for XCode

Pages: [1] 2