Messages

It does get hot while used, but it should not be hot while off though.

What ML build?
What do you do? Pics? H.264 video? RAW video?

[4]

Last version is 1.4.3.

Once MLVFS opens a file, you can copy DNGs from there, basically like exporting them from MLRAWviewer.

Quick question.  Am I able to get audio out from my 5D markiii when using magic lantern in raw MLV mode

For recording sound when recording RAW: be sure to also load the module MLV_SND, restart camera and enable Audio recording
Or did you men something else?

I have MIRawView 1.4.3 installed in my camera

Wat?Not really...

  If so how? Any help would be greatly appreciated.

It should just work

I am having problems to use this.. the Python for like Linux crashes with a gl error
And when I use wine for the windows version.. the dots don really go away..and the dng. Files are pink!?

MLVFS does not cover your needs?

Did you get all the needed stuff? ( GLFW? Scandir? etc )

Had this like forever, not sure if it's ML related though.

I've gotten used to powering down the camera in order to save the battery so it isn't an issue for me.

Umm, it's powered down and it starts here, in case I wasn't clear enough..   

I know it has the 600D mode, though this was a different implementation.

Is anyone else getting the camera starting all by it self when hanging from your neck?

I use the boxed strap either straight down on my belly or on my side, and it happens all the time eating the small battery away. ;(

Tried to repro this and handle it, pressing the buttons, to no avail.
Also, while you could get it in PictureView mode (my first suspect) by long pressing the PLAY button, I DON'T find it in THAT mode but rather in Normal picture shooting mode or ML menu.

...
I will secretly use my SL1 and EOSM with their crop_mode video hack ( 30p in Canon Menu w FPS override set to 45fps @ 1080p  ) w a 6.5mm Opteka Lens which has done its job respectively in the past.

Umm, on my EOSM crop_mode does not actually do anything, it works for you?

I've read it there too, no idea though.
Go back to start, delete everything from card ( ML\ autoexec.bin ML-SETUP.fir ) and retry?

> 4) for some reason, perhaps this is common, when I enable silent pictures two things happen: one, the left arrow on the
> "joystick"/d-pad/whatever triggers a photo;

Custom function for STAR (left arrow) is set to 1 or 3, right? You need to _long press_ for focus, else registers as half-shutter.

> two: when I go to disable silent picture photos can no longer be taken normally. Does this fall under the so-called
> "shutter bug" issue typical to this model?

What card? What lens, zoom?

You need more pics (these don't load now).

You did reset both Canon and ML settings just in case?

To speed up things for other cams one can modify the code from a1ex's post to the values below:
EOSM.202: 0xFF223A94

Thanks

EOS-M log: https://gist.github.com/licaon-kter/a9488b7043ea68dfb13392eb766219b0

[dm-spy-experiments]

dm-spy-experiments branch says it can't load LUA on EOS-M:

Code Select Expand

Will NOT load on:
    EOSM (console_clear)

You've already read: https://nikonhacker.com/viewtopic.php?f=2&t=2316&start=240  ?

And you did restart MLVFS right?

Hi, I'm considering putting ML on my Canon M, the main two features I currently want are Analog Gain, and Headphone monitoring through the AV port. I would like to check first if those features are available for the M, because on one page somewhere on the site I read that the ML Audio features are not available for cameras after the 600D, and I think the M is after the 600D.

Can you confirm if those two features (and the Audio features in general) are available on the Canon M?

Thanks.

Not available, see here: http://builds.magiclantern.fm/#/features

And what's wrong with figuring out why the files don't open in MlRawViewer?

I keep recommending MSVFS to users that keep popping on the MLRAWViewer thread with issues, since it's not developed anymore maybe MLVFS already has their use case covered.
Nothing is wrong with MLVRawViewer, when it works, and if someone can fix it, the better.

[powersave.c]

That originally was on "zebra.c" but now has been moved to "powersave.c" (line 406). 

Yes the powersave move is at fault, some stuff needs to be added I guess.

I've tried some things, like added:

Code Select Expand

static CONFIG_INT( "global.draw",   global_draw, 3 );
static void black_bars_16x9();

#define ZEBRAS_IN_LIVEVIEW (global_draw & 1)

#ifdef CONFIG_KILL_FLICKER // this will block all Canon drawing routines when the camera is idle
extern int kill_canon_gui_mode;
#endif
In powersave.c under #include "lens.h"

And:

Code Select Expand

extern void idle_kill_flicker();

extern void idle_stop_killing_flicker();
Somewhere in powersave.h, which made things move along a bit yet still crash since I id not define them right .

Code Select Expand

[ CC       ]   powersave.o
../../src/powersave.c:11:13: warning: 'black_bars_16x9' used but never defined
static void black_bars_16x9();
             ^
[ CC       ]   ml-cbr.o
[ CC       ]   raw.o
[ CC       ]   chdk-dng.o
[ CC       ]   edmac-memcpy.o
[ CC       ]   console.o
[ CC       ]   tcc-glue.o
make -C ../../tcc
make[2]: Entering directory '/my-magic-lantern-update/tcc'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/my-magic-lantern-update/tcc'
[ CC       ]   module.o
[ CC       ]   misc.o
[ CC       ]   afma.o
[ AR       ]   strrchr.o
[ AR       ]   dietlibc.a
[ AR       ]   lib_a-setjmp.o
[ AR       ]   newlib-libc.a
[ CP       ]   newlib-libm.a
[ CP       ]   gcc-libgcc.a
[ LD       ]   magiclantern
powersave.o:(.config_vars+0x60): multiple definition of `__config_global_draw'
zebra.o:(.config_vars+0x220): first defined here
zebra.o: In function `clearscreen_task':
zebra.c:(.text+0x68a4): undefined reference to `idle_stop_killing_flicker'
zebra.c:(.text+0x6b34): undefined reference to `idle_kill_flicker'
zebra.o: In function `_redraw_do':
zebra.c:(.text+0x703c): undefined reference to `idle_kill_flicker'
powersave.o: In function `idle_kill_flicker':
powersave.c:(.text+0x1bc): undefined reference to `black_bars_16x9'
../../src/Makefile.src:196: recipe for target 'magiclantern' failed
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory '/my-magic-lantern-update/platform/50D.109'
Makefile:18: recipe for target '50D' failed
make: *** [50D] Error 2

So, yeah we need help.

Can't help you with that, you should be able to fix it for your platform, clone the repo and the dependencies, edit that file, re-compile the app.

Now, that being said, any reason not to use MLVFS already?

If there'll be option for lossless exporting to .dng (like via MLVMystic), then MLRV'll be my all-in-one tool

DNG export is lossless.
FYI, DNGs get compressed but with a lossless compression (you can even disable that: http://www.magiclantern.fm/forum/index.php?topic=9560.msg142928#msg142928 )

Now, that being said, any reason not to use MLVFS already?

[6]

Build version: Nightly.2015Mar14.7D203

2015? Retry with Apr 01 2016 build I guess.

Nice work. Waiting for EOSM test code

It turns on w/o the card?

IIRC, it does take a *normal* picture, as expected.