Messages

after looking further it looks like the blue dots were noise, I must have accidentally magnified the window and didnt notice late last night. Sorry guys. It looks like the cs2x2 option is redundant too. Thanks again.

I'll post a frame when I get home from work, thanks guys.

Is there any benefit of doing sharpening or noise removal in acr or lightroom. I always did that in AE with plugins with my h.264 footage. Same with my initial grade.

There are .fpm files there already, any certain ones I need there?

You shouldn't need to use --cs2x2. Focus pixel fixing should be automatic for 650D, but the .fpm files need to be in the current directory (the directory you're launching mlvfs from => so just put them in the same directory as the executable and cd to that directory before launching mlvfs).

Thank you very much. Didn't even know about those files.

Yes I tried MLVFS, just got it working actually but have some blue dots. This was after trying with the --cs2x2 option. I'm still not 100% sure if pinkdotremover is what I need or not. I wanted to try mlrawviewer but couldn't get it working. Thanks for the reply, I promise I did not come asking questions before doing some research.

I am interested in trying RAW with my T4i. What apps do I need to process the video and remove the pink dots? I am running Windows 10.

Thanks Walter. Do you prefer any method yourself? Looks like more than a few options. I am running Windows 10.

I was interested in trying Magic Lantern raw. What is the suggested workflow for processing these files?

i know everyones focused on the module tab right now but i cant figure out how to do quick white balance change i know how to do the iso quck change but the wb is driving me crazy / also way off topic but were all filmmakers here  black and white video in post or in camera?

Im like 98 percent sure there is no WB shortcut but ive been wrong before. I prefer and I think most filmmakers prefer doing anything they can in camera vs doing it in post.

You only need the 2013Aug03 zip for setting the bootflag on your camera.  If that is done, you want to only use the nightly build.  Delete the previous build off of the SD card before putting a new one on.  Do not just overwrite the previous folder.

For the 128GB card...
- format the card with exFat (this is OS specific how to do it.  Use Disk Utility on Mac. If you don't know how to format a card ask specifically for that mentioning OS or better yet google it)
- Set the bootflag on the SD card using EOSCard, MacBoot, ... (search the forum if you are unfamiliar with how to do that)
- Download the nightly
  - Click "Home Page" on top of this page
  - Click "Downloads" at the top of that page
  - Scroll down to and click on "Browse Nightly Builds"
  - Select 650D.104 for the platform (Your camera should be running Canon 1.0.4 firmware)
  - Click "Download"
- Extract the zip file once downloaded
- Move the ML folder and autoexec.bat files to the top-level directory of the newly formatted 128GB SD card
- Insert SD card into 650D
- Turn on 650D
- Push Trashcan button for ML menu
- Select appropriate menu options (too many to list)
- Push Trashcan button to exit ML menu
- press Info button a few times until ML overlays show up

I didn't run diff on the the dir so i'm not sure if any other files are missing but the nightlies I ran were missing the doc files which is why I used overrwrite.

[format]

i dont understand this....i format my SD Card, put the files what is in the zip File of 3 August 2013 is,and then i format after that again the SD Card, and then i put the Files what is in the Nightly?

WHY can i not put directly the Nightlys into the SD Card.


PLEASE make a good Tutorial for that when u give us Nightlys,....and please explain me how can i use a 128 GB Card....thx

Don't format the card after you put the august 3rd files on the SD. Copy the August 3rd files to the SD than copy the nightly files and select overwrite all.

Measure the brightest point with the spotmeter and set the overexposure threshold just a little lower.

Thanks. I found that with cinestyle and iso 160 and multiples of, 97% seems to be the brightest point so I set the threshold to 96% and zebras now work. Is there any way to get histogram warnings to work also with iso 160 and multiples of? thanks again!

Alright guys, the RAW tests are being shot next week, along with many other ML feature tests.

In the meantime, here's a quick showreel of mine, with almost every clip in it being aided by ML in some way. All clips were shot on the 650D with either a 50mm 1.8 or an 18-135mm 3.5-5.6.

Enjoy.

Nice video. You seem pretty familiar with ML. I have a question I have asked a few times but nobody can answer it, maybe you can help me. I am using ML digital iso with a setting of -0.3 so I can gain access to native iso's like 160. The problem is the histogram no longer gives the clip warnings and zebras do not work. I was told I need to change threshold settings but I am not sure what to set them to. If you can answer that it would be great, thanks.

Anyone know what to set the threshold to so zebras and histogram clip warning work with digital iso? I can't seem to figure it out, i'm using digital iso set to -0.3 so I can get iso 160 etc.. Thanks.

Anybody?

Anyone know what to set the threshold to so zebras and histogram clip warning work with digital iso? I can't seem to figure it out, i'm using digital iso set to -0.3 so I can get iso 160 etc.. Thanks.

They do, but it's your job to do the math and change the thresholds.

Thank you, my mistake. I'll check the manual and see if I can set the thresholds.

using ML digital iso with a negative value the histogram does not properly show clipped channels and zebras do not work.

Are zebras supposed to work with ML negative iso? With the latest build zebras don't work with negative iso.

Plzz can any one give me a download link

Read the first page of this post. The links are there.

Anyway to get the help files to work with sitranis latest build? I have the PDF on the root of my SD card.

I think I answered my question.  M at all times I guess.

dave

ML doesn't disable or change the functionality of the canon settings, it simply adds extra features. Your issues seem to be you don't know the camera well enough, i'd suggest reading the manual. I use M all the time but I know three are modes that let you control just one setting like Tv mode I believe is shutter priority, you set shutter speed camera sets iso and aperture. I really suggest looking in the manual a this really isn't ML related.

No. Not in C.  For example we do #include, which includes a file. # indicates a comment in bash scripts usually.

http://www.cprogramming.com/reference/preprocessor/define.html

Thanks for clarifying that and sorry should have googled it first before posting. I have no C experience as you can tell, just a little bash and perl scripting.

Nanomad, what's the procedure I should follow to get the silent_pic_get_name function to be defined?
I decided to do some raw test using the don't click me option (which is what you guys use for debugging I think).

Code Select Expand

static void run_raw_test()
{
    /* Run RAW test to determine the best RAW_TYPE on 650D */
    for (int type = 0; type < 100; type++)
    {
        /* from lv_af_raw -> lv_set_raw_type(arg0 ? 4 : 7) -> MEM(0x2D168) = a bunch of values, default 34 */
        /* RAW value address for 650D is 0x350B4 */
        MEM(0x350B4) = type;
       
        /* this enables a LiveView debug flag that gives us 14-bit RAW data. Cool! */
        raw_lv_request();
        msleep(50);
       
        /* after filling one frame, disable the flag so we can dump the data without tearing */
        raw_lv_release();
        msleep(50);

        /* update raw geometry, autodetect black/white levels etc */
        raw_update_params();

        /* save it to card */
        char* fn = silent_pic_get_name();
        bmp_printf(FONT_MED, 0, 60, "Saving raw type %d", type);
        save_dng(fn);
    }
}

I got the code from a post by a1ex.

This is what I did until now:
1. In the src/debug.c I wrote my custom function which does the test (captures dngs and saves to sd using the silent_pic_get_name function).
2. I changed the function that the Don't Click Me option calls to the custom function I wrote.
3. In the features.h file in the 650D, I defined two options: #define FEATURE_SILENT_PIC and #define FEATURE_SILENT_PIC_RAW which is what I think causes the function to be defined....

But until now, all I get is this when compiling:

Code Select Expand

debug.o: In function `run_raw_test':
debug.c:(.text+0xb90): undefined reference to `silent_pic_get_name'
state-object.o: In function `stateobj_lv_spy':
state-object.c:(.text+0x150): undefined reference to `silent_pic_preview'
state-object.c:(.text+0x1d0): undefined reference to `silent_pic_raw_vsync'

Got any ideas?

Not r a coder myself but wouldn't the # before define make it a comment and be ignored?

Zebras seem to be working for me now after running the firmware update again from a ML card but ML still says it cannot find the help files.