Messages

There is no Liveview.

Yea, it would be great if not every thread that mentioned RAW turned into the endless repetitive when when when.

This thread is about compiling and installing.

So I'm still having issues getting the current source to compile. enabled  the flags for modules, tcc, tinypy, console, and memtest but exits with an error.

Now it says

Code Select Expand

sprintf.c:(.text+0x14): warning: warning: Avoid *sprintf; use *snprintf. It is more secure.
edmac-memcpy.o: In function `edmac_copy_rectangle_adv_start':
edmac-memcpy.c:(.text+0xbc): undefined reference to `RegisterEDmacCompleteCBR'
edmac-memcpy.c:(.text+0xcc): undefined reference to `RegisterEDmacAbortCBR'
edmac-memcpy.c:(.text+0xe0): undefined reference to `RegisterEDmacPopCBR'
edmac-memcpy.c:(.text+0xf0): undefined reference to `RegisterEDmacCompleteCBR'
edmac-memcpy.c:(.text+0x100): undefined reference to `RegisterEDmacAbortCBR'
edmac-memcpy.c:(.text+0x110): undefined reference to `RegisterEDmacPopCBR'
edmac-memcpy.o: In function `edmac_copy_rectangle_adv_finish':
edmac-memcpy.c:(.text+0x1cc): undefined reference to `UnregisterEDmacCompleteCBR'
edmac-memcpy.c:(.text+0x1d4): undefined reference to `UnregisterEDmacAbortCBR'
edmac-memcpy.c:(.text+0x1dc): undefined reference to `UnregisterEDmacPopCBR'
edmac-memcpy.c:(.text+0x1e4): undefined reference to `UnregisterEDmacCompleteCBR'
edmac-memcpy.c:(.text+0x1ec): undefined reference to `UnregisterEDmacAbortCBR'
edmac-memcpy.c:(.text+0x1f4): undefined reference to `UnregisterEDmacPopCBR'
collect2: error: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make: *** [5D2] Error 2

I'm compiling on a Mac using prebuilt tool chain, using 'make 5D2.'

I'm having issues compiling on the 5D2. Enabled all the compilation flags in the makefile, getting this exit error.

Code Select Expand

vsscanf.c:(.text+0x5c): warning: warning: the scanf functions add several kilobytes of bloat.
dietlibc.a(sprintf.o): In function `sprintf':
sprintf.c:(.text+0x14): warning: warning: Avoid *sprintf; use *snprintf. It is more secure.
collect2: error: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make: *** [5D2] Error 2


Suggestions?

It's called Mirror lockup. Turn it off under C.Fns. It is for reducing vibrations for long exposures, macros, etc.

Try a different player, like VLC.

assist beam is only if you have an external speedlight attached. A receptor is when something is received, also called a sensor. Like the thing on the front of your camera is for receiving commands from a IR remote.

There is no assist beam on on any of these cameras. There is an IR receptor on the front.

It is available through the nightly. Follow the normal install instructions. Waiting for a proper release won't make that process any easier.

Take some photos and see what ISO you need to correctly expose highlights and then change to see what you need for the shadows. ISO 100 doesn't seem like it is going to add anything at all in that dark of a situation. In general you are going to want to stay within 2 stops or it will look crazy. Try 400 and 1600 or 800 and 3200.

Any light sources other than that door?

There is work in progress to change the scripting language to TCC for a number of performance issues. It is unlikely that the PicoC API will be updated. Unsure if the DOF button press can be emulated but probably. Sticky DOF seems like it would work like that.

Motion detect is probably too slow to capture droplets.

Read about loops in C and read the API thread on the script writing board. For what you want you really only need 1 'for' loop. Look at the sample scripts.

Code Select Expand

/*
@title Focus stack
*/

wait_pic(); //wait for you to press the shutter to start

for (int i = 0; i < 10; i++) //repeat the stuff in brackets below 10 times
{

focus(1); //moves focus 1 step. can also be a negative
takepic(); //takes a pic duh
//sleep(.5); //wait .5s before starting the loop over

}


You would have to be in Liveview with autofocus enabled to use this.

There is also

Code Select Expand

focus_setup(int stepsize, int delay, int wait);  // see Focus -> Focus Settings menu
to set all those specific settings in the script if you like. You would call it by adding focus_setup(1,2,3); for example, before the loop.

You might have a problem with the script trying to run faster than the camera can take the pics and move focus. If that is the case and you are missing shots then remove the // in front of the '//sleep...' to give it some more time to clear buffer and move focus.

Scripts are not going to really speed up the picture taking part of the process, just maybe the setup.

Does it create an assert log?

1000 lines of startup logs won't help. Even if you can identify the error, still need someone to fix it.

ERR50 is hardware

"50 Malfunctions related to the electric control have been detected."

Is such delay possible to implement?

Scripting it is not difficult. You have to enable Silent-pic burst mode first and be in liveview but then all that is needed is to trigger with the shutter after running script.

Code Select Expand

/*
@title Burst Delay
*/

wait_pic();
sleep(5);
press(SHOOT_HALF);

I understand that it can be intimidating, but I wish that ML users were even 1/4 as savvy as CHDK users. Read a few sample scripts from the Script Writing board and read the API. Trial-and-error is what it is all about, just as with all programming.

edit - actually this wouldn't work because you need to press and hold.

Magic Lantern is not and will not ever be available for any pro-line or cinema-line Canon cameras. This include anything that start with a 1D- or a C-.

Code Select Expand

/*
@title Trap Focus loop
*/


while (TRUE)
{

while (TRUE)
{
press(SHOOT_HALF);
if (get_focus_confirm()) break;
};

takepic();
sleep(30);
}

Something like that should work. No way to stop it though

You definitely can script that.

7D support was added after than v2.3.

Run as the admin account.

Do you have the bitrate turned up or are using FPS override?

Try deleting the config file to reset the defaults and see if that helps.

Not familiar with recording video on 50D personally.

Is it choppy on playback on your computer or choppy while recording?

Try deleting the config file to reset all settings to default. Then turn on the features you normally use, 1 at a time, and record a test clip.

As clear as it seems to you that FPS permanently affected your cameras, it is clear to 1% that after 1 year of FPS override features and 10s of thousands of people using it, no one else has had there camera permanently altered by FPS override. Least of all the developers who push these cameras to the extreme in testing. If FPS override broke your camera, wouldn't it be obvious immediately, not 'within days.' There is something else that has not been revealed in this conversation.

Also asking for help and then telling someone who is responding to you to 'piss off' does little to help your cause.

You are really focused on the amount of memory available, but do you have a comparison to the amount available before using FPS override?