Magic Lantern Forum

Experimental builds (WIP) => Tragic Lantern => Topic started by: coutts on April 17, 2013, 01:43:28 AM

Title: Tragic Lantern for EOS M
Post by: coutts on April 17, 2013, 01:43:28 AM
Today I shipped my M to 1%, he will be taking over from here. I decided I just don't have the time right now to figure out some of the problems.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 18, 2013, 04:13:34 AM
Got the EOSM, going to start messing with it. Prop LV lens is different yet again... the filters dont work... how do you even activate MZ?


Lots of work on this one, going to be a PITA but might make something of EOSM yet.

Yep... hard to get those fancy vsync features working... but a question:

Why is vignetting correction applied twice? Once from Vsync and then again from state 4->5


Can beep now... Needs patching going to try to do a better job and jump the asserts instead of no-oping them. I was doing little endian before it wasn't working.

Audio *MIGHT* be easier on this camera... the audio IC writes/reads look more like they are sending commands not loading a struct and shooting it all at once. There are 2 headphone powerup commands and a monitoring command.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 18, 2013, 10:02:39 AM
It would be nice if you figure out the IC protocol, the 650D has the same one
Title: Re: Tragic Lantern for EOS M
Post by: coutts on April 18, 2013, 02:33:04 PM
Got the EOSM, going to start messing with it. Prop LV lens is different yet again... the filters dont work... how do you even activate MZ?


Lots of work on this one, going to be a PITA but might make something of EOSM yet.

Yep... hard to get those fancy vsync features working... but a question:

Why is vignetting correction applied twice? Once from Vsync and then again from state 4->5


Can beep now... Needs patching going to try to do a better job and jump the asserts instead of no-oping them. I was doing little endian before it wasn't working.

Audio *MIGHT* be easier on this camera... the audio IC writes/reads look more like they are sending commands not loading a struct and shooting it all at once. There are 2 headphone powerup commands and a monitoring command.
vsync is tough on this camera, it will take some tweaking.

- good job on beep! i didn't even look at audio, i was too busy getting menu and stuff working.
- for MZ, it's best to just set it to always on, because i was yet to find some indicator that focus was changing (I found one status register in memory that changed when focus was changed a lot, but nothing very accurate / fine).
- vignetting, idk (happened during random commits? haven't really really worked on this since the fall)
- display filters, not sure - like you said the prop is changed now.

Ask me questions and i'll bring you up to speed. Glad someone is at least working on it now :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 18, 2013, 03:33:09 PM
I'm not up to speed on the touch screen yet but I think this thing seriously needs support for it.

So there has to be an X/Y register or location somewhere.  Once that can be read my idea is:

1. Hijack Touch input from canon so we can intercept events.
2. Make hot corners... like windows 8. Seems simple and one could be ml menu, one could be mz, etc.
3. The junkie menu should already have X/y for the buttons since it draws them all on 1 screen. I think this would be a good way to interact with ML menus via touch.


For vsync, evf state is pretty good. 60P MZ is pretty much flicker free. Maybe use that to sync anamorphic,etc. I'm getting original problem like 6D where the overlays don't draw and F/S mz doesn't work. I'll have to look and see if display state sends anything usable.

BTW; not seeing lines on EOS_M when using FPS override with timer B.... also the videos are baseline profile... this is digic V?

Title: Re: Tragic Lantern for EOS M
Post by: coutts on April 18, 2013, 03:45:40 PM
I'm not up to speed on the touch screen yet but I think this thing seriously needs support for it.

So there has to be an X/Y register or location somewhere.  Once that can be read my idea is:

1. Hijack Touch input from canon so we can intercept events.
2. Make hot corners... like windows 8. Seems simple and one could be ml menu, one could be mz, etc.
3. The junkie menu should already have X/y for the buttons since it draws them all on 1 screen. I think this would be a good way to interact with ML menus via touch.


For vsync, evf state is pretty good. 60P MZ is pretty much flicker free. Maybe use that to sync anamorphic,etc. I'm getting original problem like 6D where the overlays don't draw and F/S mz doesn't work. I'll have to look and see if display state sends anything usable.

BTW; not seeing lines on EOS_M when using FPS override with timer B.... also the videos are baseline profile... this is digic V?

M is digic 5 yes, as far as touch goes, here's some testing I did:

lines are present, here's a 9 hour timelapse showing them getting worse over time:
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 18, 2013, 04:51:35 PM
You used timer A only so of course.
Title: Re: Tragic Lantern for EOS M
Post by: DTSET123 on April 18, 2013, 08:59:29 PM
Have you guys tried to utilize mjpeg on this one yet? If full frame can do 20fps (i think it was) maybe this one can do 24? I know it is easy to say then done but at least in theory - would it be possible?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 19, 2013, 01:38:15 AM
Just got it yesterday but did think of it... Also some new stuff got found that might give access to raw data.
Title: Re: Tragic Lantern for EOS M
Post by: DTSET123 on April 19, 2013, 03:11:03 AM
Dont mean to be annoying but you know I got to ask now: what you mean by RAW data? Also, wanted to say thanks to Coutts for sending his cam to 1%- that was nice of you!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 19, 2013, 04:17:23 AM
Like for the histogram and maybe movies... we'll see.

Yea, EOS-M isn't going to be doing much overcranking... also:

FPS timer B and A need to be limited I think. Too much A = Lines. Too much B = overheating.

I'm trying B000 as a B limit, the overheating was real obvious with M.

Need to find some sane limits.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 20, 2013, 11:54:15 PM
No luck with FPS limits... if I limit too much then it doesn't work right... Reverse is overheating tho.

Flush rate is working though, I tried down to 2 frames. "CBR" 9x and not a hickup... only 72Mb/s tho... this camera will have to set slice and/or digic parameters.

Another bit of news... the videos have an M=1 for ref frames so I'm going to look at video paramters and see if  M setting is present. Then can set it to 3 and have IPB, etc. I still have to throw videos in my analysis tools and see what its really writing, be it IP/IPB/etc.

Bad news for beep... stopping DMA DAC causes freeze and not error. I tried some patching but its not working. Weird that recording is seemingly working and so is playback... just after initiial play /rec camera locks up :(

Looks bad for syncing overlays have 26 and 27 display state event but neither is in sync.... too far down the line and you cant see the others.

I really hope for the audio to work as then this camera can be a run and gun on a steadicam. That way you save the weight of the body and just have to balance the lens. The adapter is conveniently centered.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 23, 2013, 06:10:09 PM
Well its still freezing after beep and I don't see anything in the logs.

For menu while recording:

Redraw flood needs to be disabled. It can't open the canon dialog in the backround. Also guirequestmode of 0 means the buttons don't work. Setting gui request mode to ML mode like 90 fixes the buttons but when you come out of the menu it doesn't go back to 0 right, you lose all events and if lucky can press play mode to get them back after stopping recording.

Is assert working on this camera?
Title: Re: Tragic Lantern for EOS M
Post by: coutts on April 24, 2013, 02:24:46 AM
Well its still freezing after beep and I don't see anything in the logs.

For menu while recording:

Redraw flood needs to be disabled. It can't open the canon dialog in the backround. Also guirequestmode of 0 means the buttons don't work. Setting gui request mode to ML mode like 90 fixes the buttons but when you come out of the menu it doesn't go back to 0 right, you lose all events and if lucky can press play mode to get them back after stopping recording.

Is assert working on this camera?
ML assert? should be
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 24, 2013, 02:38:29 AM
It dumps the assert message to where the dumpf log would normally go. I've only gotten hangs and never err 70.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 25, 2013, 04:31:44 AM
Synced MZ on EOSM... input 15 old state 5 on evf state fires every frame... unfortunately this doesn't work for display filters.

For image parameters we are catching Display state just one state too late. It is firing right at the end. On 6D it would fire one transition before. They are both state 1 but on 6D there is also a state 0 that comes after it.

On 600D we can't sync because both input 3 and 5 happen on old state 5. The sync function would have to  run at 1/2 speed somehow. Fires twice as much as needed.
Title: Re: Tragic Lantern for EOS M
Post by: coutts on April 25, 2013, 03:48:54 PM
Synced MZ on EOSM... input 15 old state 5 on evf state fires every frame... unfortunately this doesn't work for display filters.

For image parameters we are catching Display state just one state too late. It is firing right at the end. On 6D it would fire one transition before. They are both state 1 but on 6D there is also a state 0 that comes after it.

On 600D we can't sync because both input 3 and 5 happen on old state 5. The sync function would have to  run at 1/2 speed somehow. Fires twice as much as needed.

int skip = 0;


skip = !skip, to toggle it on/off?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 25, 2013, 03:59:51 PM
Skip? You can't see the correct state, it never showed on the screen. For 600D would have to be 3->5->sync. I'll have to see where the other cameras land which use it.

The audio meters only work while recording :) Buffer isn't too bad while recording either... I'll have to hack it to be big all the time.

ML menu works while recording now. I used guimode 99 and set it back to 0 when exiting the menu.... sometimes it fucks up the first time so press down first I guess.
Title: Re: Tragic Lantern for EOS M
Post by: tractorFactor on April 26, 2013, 03:44:06 AM
Am I being blind or are Focus Menu items unavailable on EOS-M?
I'm using the Alpha version for Eos-m.

Trap Focus,
Follow Focus,
Focus End Point,
Etc.

appear to be unavailable.

Thanks
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 26, 2013, 04:10:02 AM
Those don't really work because there is no focus confirmation.. There is only the crappy LV focus... ever have trap focus in LV mode?

I plan on screwing with AF with some of the 6D props to see if I can speed it up but not sure how that would work for trap focus as its slooooooooow. Follow focus needs some sort of on screen short-cuts.

Right now got MZ synced and ml menu working along with flush rate.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 26, 2013, 11:19:05 AM
Quick question, what are you using to debug state transition ?
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on April 26, 2013, 11:38:20 AM
For simple stuff you can use bmp_printf. For more complex logs, I use dm-spy and DryosDebugMsg.

Or, custom logging code like this: http://www.magiclantern.fm/forum/index.php?topic=1915
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 26, 2013, 03:59:15 PM
I used consoleprintf like coutts and notifybox. Notifybox seems good for seeing what will get to the screen and how often... dunno about this approach but it seems to work for MZ at least. I'm going to try to sync 600D with face or one of the other stateobj I looked at on M.

Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 27, 2013, 01:45:24 AM
Uhm that state transition didn't work on the 650D
Alex gave me an idea that hopefully will help us automatically find suitable vsync transitions by analyzing the FPS of a set of candidates
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 27, 2013, 01:58:37 AM
Input 15 is missing?
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 27, 2013, 01:59:26 AM
It's there but the overlay flickers so fast it's almost like it's getting triggered at half the fps
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 27, 2013, 02:04:51 AM
Like 600D where sync should be working from either Display State or the regular EVF sync but doesn't.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 27, 2013, 04:26:48 AM
The raw pics come out half height in EOS-M... also lv rec doesn't want to load. Just sits with no messages after hitting load.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 27, 2013, 08:48:41 AM
I've done a bit of digging and found a couple of vsync functions in the firmware... Maybe it's worth exploring them (of know Alex already tried but couldn't understand them)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 27, 2013, 09:11:28 AM
Would be cool to have sync... where should I look. I still need to decompile EOSM and 113 of 6D. Actually probably a new decompile for all fw because I named a bunch.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 27, 2013, 01:59:57 PM
Vsynced the 650D with the same transitions as the EOSM.
God knows why it didn't work properly yesterday
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 27, 2013, 05:26:42 PM
Same reason SSS state not working on M and the transitions are the same.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 27, 2013, 10:23:52 PM
I'm able to dump something on EeKo encoder... found more of its functions.

http://www.qfpost.com/file/d?g=wM6kJbGrQ (http://www.qfpost.com/file/d?g=wM6kJbGrQ)

Maybe we should compare with 6D in Eeko mode and 650D.

call("DumpEeko");


EeKo appears to use Jpcore2 vs Jp62 like the DigicIV encoder. Debugmsg content is poor :(


Eeko supports ALL-I, IPP and IPB... takes it all from video params .
LV is always 30fps until encode starts... also the qscale scale is wrong I think
There is a test function to set the input buffer.. so I guess can feed it something else.

The LV size is so small because it goes Raw->Sraw->YUV
Title: Re: Tragic Lantern for EOS M
Post by: kazeone on April 28, 2013, 09:59:55 AM
not to side track but since some of you have this camera would you say its a good secondary camera to have a long with someone that owns the T4i? I can get the body for around $350 so that seems pretty good but I can get the T3i for about that too...
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 28, 2013, 10:11:41 AM
Its really small... that's about it tho. T3i is a more usable camera for normal applications.

EOS-M seems more of a camera to mount to stuff where a DSLR is too big but a P&S would provide insufficient image quality.
Title: Re: Tragic Lantern for EOS M
Post by: kazeone on April 28, 2013, 10:15:59 AM
thats a good point at half the weight of the T4i, it would make for a better choice for mounting to places and similar and for tight spaces or like hiking. I think I will go that route down the road. Thanks
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 28, 2013, 12:38:41 PM
If only the M had a tilty screen the combo M + ML + Gorillapod would be one of the best around
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 28, 2013, 04:40:02 PM
Interesting state transitions on the 650D, maybe it's worth checking them out on the EOSM too for vsync

Code: [Select]
old_state input ticks_in_10_seconds
05 03 603
05 04 604
05 05 604
05 15 603
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 28, 2013, 06:07:04 PM
I think I tried all evf + face + display state states for syncing stuff like anamorphic. Everything is too late to the party.MZ was easy... replacing display state 27 does not appear to be. Only works in photo mode just like 6D did originally.

15 doesn't work for digic functions like fps or image effects but great for syncing. 5 and 4 are great for image effects but didn't sync magic zoom.

So we need to find a state that happens just before drawing so the buffer can be hijacked.

Why don't modules/console work? No text displays and it won't turn off once enabled (so no other ml overlays draw). I think lv recorder has a chance on M with the reduced width 422 buffer.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 28, 2013, 06:22:04 PM
I'll check them on the 650D.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 28, 2013, 07:50:14 PM
5d3 + 650D can probably boot with 640K bins. I have 3mb of ram even on eos M.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 28, 2013, 08:34:23 PM
Modules are working fine on the 650D assuming you have all the stubs for lvrec
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 28, 2013, 09:47:51 PM
Yes... even the test module won't load... I get nothing in console and I can't make it go away so its like console is broken?

Yep, tried to check sig of EOS M and console comes up with no text, menu stops drawing.


Very impressive FPS... lol was seeing all these frames go by... it was set to end trigger :)

only 7!!! yes, 7 frames of raw can be saved..... aaaand that is about equivalent to the real raw rate.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 29, 2013, 04:35:57 AM
Fixed prop LV lens... If its not the right focus distance I'll have to move to next one... there are 2 .. 0049 and 004a different by +1. Focal lenght also is doubled both for 6D and M 0023 and 0023 (35mm)
Title: Re: Tragic Lantern for EOS M
Post by: libertykite on April 30, 2013, 01:58:53 PM
I try to put a Samyang 8mm fisheye (Manual lense with no electronics) with the EF adapter, but impossible to take a photo or start a video.


Are the ML could solve it?
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on April 30, 2013, 02:14:06 PM
Go to canon custom functions, it's there already
Title: Re: Tragic Lantern for EOS M
Post by: Eisland on April 30, 2013, 06:57:59 PM
Hi guys,

with great interest I am reading this thread, and I read nearly all pages of it, sometimes I had difficulties to understand, but am quite amazed by the possibilities given with ML (especially because I am a long time Pentax - user and miss many of these possibilites ;(...

Trying to capture video on a professional level, I want to buy 4+ Canon M Cameras, with various lenses, and record 'concerts' 'music videos' etc. So I need to have great video quality, long video clip duration, and sync.-possibilites, external monitor-possibilites... (also Using a DIY Camera Crane with 4m range)... (basically I want to use the M, as it is quite cheap and veery light for 'DSLR-video-quality')

I have a few questions (if this is not the right place to ask these, I am sorry & pleas direct me to the right position ... Thank you!)

1.  What is the longest video duration with no single frame missing in 1080p,25fps?
2.  Is it possible to use a "China-Full manual" Mount adapter for 15bucks from the bay if I want to only use ''manual ooold glass" or Samyang 85 1.4 with no AF-contacts and so on... (M42 lenses?) (I want to only use kit lens & old manual glass, as the Focus throw is longer than with modern zoom and AF-lenses, so manual focusing is a lot easier while recording video...)
3.  Is it possible to synchronize the 4 (or more cameras) with a sort of wireless audio transmitter (as Audio is recorded separately) that can be plugged in the audio or other external sockets in the EOS M somewhere??
4. Is it possible to have an auto movie restart function where camera restarts video after the 29minutes...  (I know there generally is in ML, but I don't know if it is working on the EOS M).
5. Is there Liveview-output via HDMI and what is the highest resolution while recording 1080p being transferred to an external screen?

If this might work out, I will be very thankful to you helpers and contribute to the ML-research group ;)

Thanks in advance for answers!
Kevin
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 30, 2013, 07:07:09 PM
Hmm.. I don't know how that will work out. The highest rates I got out of M were 70Mb/s with flush rate and CBR function cranked all the way. I still have to analyze.

Soon IPB and IPP and ALL-I will be possible.. I don't know how to change the profile away from baseline yet.

I have to check HDMI  to see what happens. I have adapters so I will see what they do. There is no focus confirmation.

Movie restart should work already. Sync between the 4 probably impossible although you can do the shutter tuning thing for LCD screens etc, it may at least sync shutter.

Title: Re: Tragic Lantern for EOS M
Post by: Eisland on April 30, 2013, 07:33:02 PM
So by that, you mean that 70Mb/s are too low? So quality will not be very good for professional video productions?

"There is no focus confirmation" ... focus peaking with these false colour flickering will work, right?

Does the movie restart function mean that it will restart the video after 29.xx minutes?? Or does it have to restart the video after the 4GB file size limit? (so basically, what will be the longest video duration possible w.o. frame loss (it is essential for classic concert-recordings no to loose too much time in these breaks... )

i don't get what you mean with the shutter tuning thing for LCD screens...

Thank you,
Kevin
Title: Re: Tragic Lantern for EOS M
Post by: 1% on April 30, 2013, 08:15:25 PM
The image effect to sync the electronic shutter with LCDs/TVs/LIGHTS


The crappy focus peaking works, the good one with display filters does not.

All digic V cut the big file into 4gb chunks after 30 minutes. So it only needs to restart every 30

*I just checked the adapter. It doesn't help you focus. Just shows an aperture.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 03, 2013, 05:01:16 PM
Added raw histogram.  Fixed adapter ring expo. Turns out there is a zoom box and you can move it around with your finger... the mz flickers once when the zoom box position changes but its kinda cool. Also works to have mz on 1/2 shutter and when it focuses it zooms in on the area its looking.

Console still not working, no characters show up even when I enable console debug.

Title: Re: Tragic Lantern for EOS M
Post by: coutts on May 03, 2013, 05:13:54 PM
Added raw histogram.  Fixed adapter ring expo. Turns out there is a zoom box and you can move it around with your finger... the mz flickers once when the zoom box position changes but its kinda cool. Also works to have mz on 1/2 shutter and when it focuses it zooms in on the area its looking.

Console still not working, no characters show up even when I enable console debug.
i think it's a backend bug, i can't make it work on the 6D (from main repo not yours).
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 03, 2013, 05:22:29 PM
6D it always worked... i'm building EOSM off the 6D repo so the bug must be unique to M. 650D apparently works.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 05, 2013, 05:28:00 PM
Oh man... wtf are these dots:

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F4OXEnh5.jpg&hash=6917d9401854538e273fba9a65a3f596)

They are in DNGs
Title: Re: Tragic Lantern for EOS M
Post by: Hydron on May 08, 2013, 10:48:33 AM
I was going to suggest that they might be something to do with the phase detect pixels (which I believe give a different response, and are compensated for during image processing), but this suggests that they may be more random than the dots in your image:
http://image-sensors-world.blogspot.co.nz/2012/07/chipworks-shows-phase-detection-pixels.html (http://image-sensors-world.blogspot.co.nz/2012/07/chipworks-shows-phase-detection-pixels.html)
Keep up the good work, am looking forward to more capabilities (especially the focus peaking) for my camera!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 08, 2013, 05:04:22 PM
Ha! that explains it.. wish there was a way to hide it, those dots are very annoying


Things that don't work right now:

*Advanced peaking/processing - ie. anamorphic, alpha blend, etc
*Asif hangs camera... dunno why tried several ways. Just beeps once and then hang the second time
*MZ flickers while recording... buffer changes and sync changes i bet.
*Console broken so no LV_rec/tinypy yet... going to try to use malloc again(maybe memory issue) there is 700kb there like 5d3.
*focus confirmation (have to look at how its done for burst, since thats in LV) maybe we'll get trap focus out of it
*mraw/sraw - needs more investigation, turns off camera

Things that do work:
Menus while recording.
Audio Meters while recording
Raw DNG
Flush rate
Probably IPB/ALLI/IPP - have to make menus for them
fps override
focus distance/focal length/exposure meter
edmac stuff
raw histogram/zebras/spotmeter
Title: Re: Tragic Lantern for EOS M
Post by: Chuckwagon on May 08, 2013, 09:18:10 PM
I was reading through the thread and I couldn't find an answer with certainty about shooting tethered with the M.  With ML installed on the M, can it shoot via USB tethered like the T4i can?

Thanks.  :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 08, 2013, 09:33:28 PM
Like connected to EOS utility you mean? I have to try it.
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on May 08, 2013, 11:06:48 PM
Thank you for your great works, guys!

I got my M last week and used it for a small commercial video. Too bad I didn't find this thread, kelvin WB would help a lot. haha

I'm so glad you guys did release this Alpha for M. Now my M is on the fly!


Now I'm just being curious about the shutter count. How do we count this in M?

ML reports 2K of shutter count. And that would be 758 + 942. But I'm sure I've never shot with my M more than 700-800 shots, counted by RAW files stored on my harddrive plus deleted ones. It shouldn't have been more than the front number, which is 758. How did 942 come?

Thank you for the release!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 08, 2013, 11:28:25 PM
Well with M every start is a LV actuation and so that counts "against" you... also every shutter click is a shutter click... add the 2 together on a normal camera and you would have shutter count. With M I guess it doesn't matter so much..

Ok, boots successfully via cache hack to malloc pool.... but... malloc pool doesn't reflect the "hit" from ML binary. Would it show it through the copy&restart method? Should I fixup start and end address somehow or leave as is... or go back to allocate?


Console still doesn't want to work. I dunno WTF is wrong with it.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on May 09, 2013, 12:16:43 AM
Ha! that explains it.. wish there was a way to hide it, those dots are very annoying

Well, it depends on what you want to do :P
On the 650D you can clearly see the focus point types (cross, H , V)
You can mark them as bad pixels (alex suggested to have a look at the dng converter code)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 09, 2013, 12:42:35 AM
Wouldn't it be the same as getting rid of the dots in post? Wouldn't they just show black if marked bad... they're pretty big.

PROP_LV_FOCUSDATA dead on EOSM too :(
Title: Re: Tragic Lantern for EOS M
Post by: Hydron on May 09, 2013, 04:07:58 AM
I'm assuming that if bad pixels marking is part of the DNG spec, then a DNG RAW converter will deal with them in a smart way by interpolating from surrounding good pixels. While they look big, you may find that they have little effect on the image. The canon firmware might still use these pixels for imaging, with knowledge of the different light response they could scale them differently for demosaicing (for JPEG) or when writing the raw CR2.
This is all assuming however that these dots are indeed related to the phase detect - I have no experience with this stuff, it was just an educated guess.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 09, 2013, 05:06:34 PM
They're in different places so I'm assuming they have to be for AF. I don't think they're dead pixels or something as they don't show up in YUV or photos.
Title: Re: Tragic Lantern for EOS M
Post by: Chuckwagon on May 10, 2013, 06:56:58 PM
Like connected to EOS utility you mean? I have to try it.

Yes, that was what I meant, sorry I wasn't specific.  :)  The lack of the ability to shoot tethered via USB (with stuff like EOS Utility) the way my T2i does is what kept me from getting an M.  But if ML makes that possible, then the M becomes more interesting to me.

Thanks,
Chuck
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 10, 2013, 07:02:06 PM
Well T3i and 6D work with EOS utility just fine.
Title: Re: Tragic Lantern for EOS M
Post by: Chuckwagon on May 10, 2013, 07:42:49 PM
Well T3i and 6D work with EOS utility just fine.

Yeah, I think all of the other current EOS cameras work with EOS Utility, it's just the M that Canon decided to cripple and remove the tethered shooting ability.  Why is beyond me.  I guess they felt if they made the M too good they'd steal sales from the more expensive models and cut into their profits.  :)

Chuck
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 10, 2013, 08:36:33 PM
Hmmm... will have to see, the issue could be eos utility too. A little bit speculation till I hook it up and try it.

I don't know if anything here was intentional crippling... this camera has ~50MB of shoot malloc, even less w/ raw quality selected. Very low memory and underpowered. CPU load for this and 650D is very high in LV with nothing running. I think they are ditching these platforms because they are too slow.
Title: Re: Tragic Lantern for EOS M
Post by: salsasepp on May 11, 2013, 07:08:00 PM
I noticed the EOSM build is currently broken. Error message: undefined reference to `GetNextMemoryChunk', being used in exmem.c and debug.c. The problem seems to be a missing GetNextMemoryChunk in stubs.S.

I am getting an EOS M next week for testing. Should I try to learn how to add missing stubs or can exmem/debug be disabled somehow? I feel like going the easier route first....

Thanks, Stefan.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 11, 2013, 07:31:10 PM
You can build off my 6D repo... working fine there.

BTW:

Code: [Select]
NSTUB(0xFF0EA0E4, AllocateMemoryResourceForSingleChunck) //caller
NSTUB(0xFF13B7DC, FreeMemoryResource) // m_pfFreeMemoryCBR
NSTUB(0xFFA723E4 - RAM_OFFSET, GetFirstChunkFromSuite) // AJ_PackMemory_PackMem_p3
NSTUB(0xFFA71DBC - RAM_OFFSET, GetMemoryAddressOfMemoryChunk)

NSTUB(0xFFA72B80 - RAM_OFFSET, GetNextMemoryChunk)
Title: Re: Tragic Lantern for EOS M
Post by: salsasepp on May 12, 2013, 06:29:19 AM
Thanks 1%, works as advertised.

Regarding EOS Utility / remote control: In any case, we should be able to use ptpcam or roll our own PTP command that does what we need, right?
Title: Re: Tragic Lantern for EOS M
Post by: Eisland on May 12, 2013, 01:30:49 PM
Hey guys,


I have few more questions, before I buy 5 EOS M cameras to do video work...

- old FD lenses with China adapters will work with manual exposure and manual focus?
- will it work with automatic exposure too?
- will movie restart function work (so I can record up to 29.xx minutes?
- the simple AF-Help/color flickering while manual focusing?
- Recording on Class 10 SDXC, 64GB cards...?
- setting the same WhiteBalance and colour modes on all cameras?
- Does it have Live HDMI-output in what resolution while recording??

If you could answer me these questions I would be really happy and very thankful!! (which will definetely result in donation to ML!)
Thank you,
Kevin

Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on May 12, 2013, 02:33:44 PM
Hey guys,


I have few more questions, before I buy 5 EOS M cameras to do video work...

- old FD lenses with China adapters will work with manual exposure and manual focus?
- will it work with automatic exposure too?
- will movie restart function work (so I can record up to 29.xx minutes?
- the simple AF-Help/color flickering while manual focusing?
- Recording on Class 10 SDXC, 64GB cards...?
- setting the same WhiteBalance and colour modes on all cameras?
- Does it have Live HDMI-output in what resolution while recording??

If you could answer me these questions I would be really happy and very thankful!! (which will definetely result in donation to ML!)
Thank you,
Kevin

I can partially answer your post.

FD lenses should work. I have a China adapter for Pentax K mount, it works. Set Custom Function 7 to Enable, enable shutter w/o lens.

Automatic exposure will work, obviously its like an aperture priority since your lens has the aperture ring. Camera reports aperture as "00"

I have not tested the movie restart function. However, I did use it as an "a" camera at a live performance and next time I will not. The battery is about the size of a cell phone battery. The battery was about to run out so I had to change it. Problem is even though I had the QR plate for the tripod head mounted to the EF lens adapter I still had trouble getting the battery out and the lens would not come off either without removing the QR plate first. Lesson learned, next time its the "b" camera so starting and stopping is no big deal. In summary, I don't know how many minutes of recording you will get before you need to change the battery.

Are you talking about focus peaking? It works.

I don't know about the card I am using SDHC class 10 32 GB, no problems.

Yes the camera has manual white balance and picture styles. I mix mine with a 7d and a GoPro 3, can't tell a difference in color.

Yes it has live HDMI output while recording, the screen on the camera blacks out like the 7d and I can't tell you the resolution.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 12, 2013, 03:58:06 PM
one thing up in the alpha is that it doesn't have the manual adapter patch so expo sim will be incorrect in photo mode.
I'm using it this way now because I hate the AF.

Peaking and all that stuff works but not the fancy peaking/filter. Movie restart works... The battery is terrible.

Title: Re: Tragic Lantern for EOS M
Post by: Eisland on May 12, 2013, 04:45:32 PM
Hi guys,

thank you so much for your responses!! We are using 5 cameras, so we will be able to cut from here to there... We plan to use AC-Power adapters to keep them running aaaall concert long ;)
I will soon buy the equipment needed and will try ML the very first time (being a long time Pentax User, I wish you start hacking my K-5 ;)

Thank you so mcuh!
Kevin
Title: Re: Tragic Lantern for EOS M
Post by: vstrglv on May 12, 2013, 05:50:54 PM
But I found that after installing ML on EOS M the 18-55mm couldn't release the shutter, I have to dismount and put it back in order to shoot.
Same for me for autoexec.bin compiled on 20.04.2013, but there is no problem for autoexec.bin on 10.12.2012
I have tried compile autoexec.bin today but got an error:

[spoiler][ CC       ]   picoc.o
[ CC       ]   chdk-gui_script.o
[ AR       ]   lib_a-memcpy.o
[ AR       ]   newlib-libc.a
[ LD       ]   magiclantern
exmem.o: In function `exmem_save_buffer':
exmem.c:(.text+0x1fc): undefined reference to `GetNextMemoryChunk'
exmem.o: In function `exmem_clear':
exmem.c:(.text+0x268): undefined reference to `GetNextMemoryChunk'
exmem.o: In function `shoot_malloc_suite_contig':
exmem.c:(.text+0x504): undefined reference to `GetNextMemoryChunk'
debug.o: In function `guess_free_mem_task':
debug.c:(.text+0x9c8): undefined reference to `GetNextMemoryChunk'
debug.o: In function `stub_test_task':
debug.c:(.text+0x6970): undefined reference to `GetNextMemoryChunk'
debug.o:debug.c:(.text+0x70c4): more undefined references to `GetNextMemoryChunk                                                                   ' follow
collect2.exe: error: ld returned 1 exit status
../../Makefile.inc:441: recipe for target `magiclantern' failed
make: *** [magiclantern] Error 1
make: Leaving directory `/home/vstrglv/magic-lantern/platform/EOSM.106'[/spoiler]
No problem for compiling autoexec.bin for5d3 today (but dated  5th of May)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 12, 2013, 06:16:32 PM
Haven't seen the shutter bug yet on my builds. Will have to try to reproduce it.
Title: Re: Tragic Lantern for EOS M
Post by: min on May 14, 2013, 06:41:41 PM
Congrats to the ML team on the recent success with raw on the 5D mark 3! I read that you guys will try to port it over to the mark 2 and 6D next. Do you think this feature will be possible on the M eventually, particularly the 1:1 crop? Thanks.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 14, 2013, 06:57:19 PM
Well its already ported to those cameras... on M it *should* work for very tiny video... Only 50MB buffer.  the silent pic dngs already work and you get 7.

For some reason no module will load and console is broken. That's what is holding it up.
Title: Re: Tragic Lantern for EOS M
Post by: oscillian on May 16, 2013, 10:32:10 AM
So what kind of buffer is considered minimum to have 1080x1980?
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on May 16, 2013, 12:11:50 PM
A fast CF card and around 100MB of buffer
Title: Re: Tragic Lantern for EOS M
Post by: Jupiter55 on May 16, 2013, 05:08:11 PM
Hi there,
thanks for porting ML to EOS-M! I use it on my 5D2 and 7D also.

I have also the shutter bug as user jasonwhk (Dec 15) and vstrglv (May 12) mentioned.
My EF-M 18-55 STM is well recognized by the EOS-M, only taking pictures does not function. All other functions like zooming, AF and so on are ok.
If I just remove ML (FW Update, turn mode dial, reboot) all is normal, the 18-55 behaves 100% ok.
Cam and lens are new, no dirt on lens contacts, no wrong installation.
So the error is related to the ML Alpha1 .
My other lens EF-M 22 2.0 STM works well, shutter function in ML full ok, also other Canon lenses with the mount adapter.
If I run the ML internal tests, 4 errors are found, what can I provide to aid in fixing the errors?

Q: Is there a better version than the ALPHA1 from the download page? I tried the last nightly build, but that obviously works not for the EOS-M as stated.

Please help...


Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 16, 2013, 05:24:24 PM
Try:

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/EOS-M.zip

Does the issue remain?
Title: Re: Tragic Lantern for EOS M
Post by: Jupiter55 on May 16, 2013, 09:26:51 PM
 :D
Great! It works, with the new autoexec.bin 538.302 bytes  my 18-55 and shutter works.

Thank you!

regards,
Jupiter
Title: Re: Tragic Lantern for EOS M
Post by: Eisland on May 29, 2013, 07:43:09 AM
Hey guys,

I bought the M, installed ML (very exciting for me being a Canon & ML newbie)...

now I see a EFIC Chip temperature and am wondering which temperatures it should have. Mine says after about 2minutes of liveview ~108°C. That seems pretty high to me and so I am wondering, if ML will switch the camera off if it might fail due to temperature rising.

What temperatures are normal?????

Please give me a hint, as I don't want to kill my brandnew camera...

Thank you!
Kevin
Title: Re: Tragic Lantern for EOS M
Post by: Masheen on May 29, 2013, 04:45:32 PM
I keep running into this error. I could brute force it and eliminate the line, but I have no idea the repercussions of that.

Where in the code should FEATURE_SILENT_PIC_RAW or FEATURE_SILENT_PIC_RAW_BURST be defined?

Code: [Select]
../../src/shoot.c:1045:6: error: #error FEATURE_SILENT_PIC requires FEATURE_SILENT_PIC_RAW or FEATURE_SILENT_PIC_RAW_BURST
make[1]: *** [shoot.o] Error 1

Edit: Thank you Nanomad!

Although now it's throwing another error. It's the EABI version mismatch issue. Time to try and download a different arm compiler.  :(
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on May 29, 2013, 05:05:27 PM
#undef FEATURE_SILENT_PIC inside features.h
Title: Re: Tragic Lantern for EOS M
Post by: thaihl on May 29, 2013, 06:18:27 PM
i wait firmware update in the long time.... :'(  thanks everyone !
Title: Re: Tragic Lantern for EOS M
Post by: 1% on May 29, 2013, 07:47:46 PM
Have to check the silent pic sizes and make sure there are no regressions then I'll build a new one. Had no luck with raw video still.. console is broken.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 01, 2013, 03:54:23 PM
Console is unbroken... thanks a1ex. Now raw recording works. Hint: Its pathetic

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5D%20Raw%20Recording.zip

Caveats:

*Hacked Mode may not return LV or GD... turn camera on/off
*Turn on frame skip.. there is no way to record continuously
*Previews don't work, playback only works in photo mode
*Modules only load from cold boot in movie mode

Otherwise without modules operation should be normal (check and makes sure nothing broke)
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 02, 2013, 02:45:40 PM
Console is unbroken... thanks a1ex. Now raw recording works. Hint: Its pathetic

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5D%20Raw%20Recording.zip

Caveats:

*Hacked Mode may not return LV or GD... turn camera on/off
*Turn on frame skip.. there is no way to record continuously
*Previews don't work, playback only works in photo mode
*Modules only load from cold boot in movie mode

Otherwise without modules operation should be normal (check and makes sure nothing broke)

I've loaded up the raw module from your link. It won't record at all, even on the lowest resolution. I get the error "Memory error  Alloc: 18M".

The card benchmarks i consistently get over 36 MB/sec write speeds on the 32GB Sandisk Extreme card in the camera.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 03, 2013, 02:46:39 AM
Try update... Should load. It is loading on mine. Cold boot in movie mode.

Make sure photo is L... there is some way to get 95MB... I was messing with noise reduction and it freed it in photo mode. Otherwise you get like 55M

Shit! Found a hot method to record on EOS-M... photo mode (after loading modules in movie mode) -> High ISO Noise, Multi Shot... now have the 95MB but can't trigger raw_rec (LV button is dead)

I added menu to trigger and seems to be working... just like 600D. 32*32*29

Ok it is gangster right now... not good for other cameras with the menu thing tho. Hopefully g3gg0's input modules solve this.

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5D%20UsableRaw.zip


Remember:

Movie Cold boot -> load -> photo mode -> canon menu -> nr -> multi shot.
Make sure you don't turn on raw_rec before doing that or it will start recording.. menu key
Quality still should be L, won't let you pick anything else anyway.

Squeeze factor may be off, no pinkies so far. FPS override is your friend. Should be 4gb proof with exfat...

650D try this NR trick!
Title: Re: Tragic Lantern for EOS M
Post by: Achimogata on June 03, 2013, 01:34:24 PM
Hi everybody,

I have found last day this website. I was looking around for focus peaking on nex and eventually other mirorless cameras.

Let's explain. It is time for me to buy a mirorless camera. I am still doing film photography with my canon new F1 and T90 with some FD lenses and I plan to keep on film for B&W shots and to go with digital camera for color ones. The deal is to use my FD lenses on the digital camera so a mirorless one is what to be choosen I think.
The question is : is the focus peaking fully and reliably available on EOS M using Magic Lantern right now ? Quickly thought, I don't really need other feature at this time.

Thanks for your good advises.
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 03, 2013, 01:53:55 PM
Thanks 1% I got it working. I don't have time to mess with it now but at 960 x 544 @ 24 fps I captured like 670 frames until live view shut off automatically need to change that setting to never and try again...


Try update... Should load. It is loading on mine. Cold boot in movie mode.

Make sure photo is L... there is some way to get 95MB... I was messing with noise reduction and it freed it in photo mode. Otherwise you get like 55M

Shit! Found a hot method to record on EOS-M... photo mode (after loading modules in movie mode) -> High ISO Noise, Multi Shot... now have the 95MB but can't trigger raw_rec (LV button is dead)

I added menu to trigger and seems to be working... just like 600D. 32*32*29

Ok it is gangster right now... not good for other cameras with the menu thing tho. Hopefully g3gg0's input modules solve this.

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5D%20UsableRaw.zip


Remember:

Movie Cold boot -> load -> photo mode -> canon menu -> nr -> multi shot.
Make sure you don't turn on raw_rec before doing that or it will start recording.. menu key
Quality still should be L, won't let you pick anything else anyway.

Squeeze factor may be off, no pinkies so far. FPS override is your friend. Should be 4gb proof with exfat...

650D try this NR trick!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 03, 2013, 02:13:47 PM
Only blinking dots focus peaking works. Haven't found a fix for display filters yet.
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 03, 2013, 05:04:42 PM
With frame skipping turned off I get continuous 24fps with a Sandisk 45 MB/sec card at 1024 x 576. The resolution right above it 1088x640 stops after 41 frames. The highest resolution 1728x672 stops after 24 frames, again at 24fps.

I have not read anything on workflow so I will research further but I used raw2dng then imported to Lightroom 5 beta, adjusted, exported to TIFF, imported to FCPX, created an image sequence, changed duration to 1 frame each in a 720p @ 24fps project, then exported to youtube.



I don't know why there are red dots in the middle but they are in the dng files right out of raw2dng. Like I said I will research this further maybe this is a known issue in other cameras since I only have the M and the 7d this is my first attempt at raw video.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 04, 2013, 09:30:26 AM
 :) I also make it work on my EOS M but since my card is only 30MB/s max resolution is 880x496. I have those red dots as @mdwhaley

Can't wait for next update.

Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 04, 2013, 11:10:44 AM
When I import DNG into Photoshop, my image looks too wide or squeezed:

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ff.cl.ly%2Fitems%2F2e0i2o0d2Q0e3f041L2A%2F000008.jpg&hash=5c96607b365844f3a62fdd04a24d9d7e)

Am I missing some option in ML?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 05, 2013, 07:25:40 AM
Dots and stuff are from af.. have to experiment with turning them off.. they are a problem on all cameras in a few different forms.

Have to see what is up with the squeezing... big problem with EOS-M is its pretty much 720P mode all the time without the fps..
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 05, 2013, 02:22:35 PM
I figured the dots were from AF. I put an M lens on and turned AF mode to MF in the menu, then put an EF lens back on switched to MF and still get dots. The AF sensor must be on all the time even when MF is set all around.

Dots and stuff are from af.. have to experiment with turning them off.. they are a problem on all cameras in a few different forms.

Have to see what is up with the squeezing... big problem with EOS-M is its pretty much 720P mode all the time without the fps..
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 05, 2013, 03:58:19 PM
Its phase detection AF... will have to try different types or af_raw and see if it gives peaking sprinkles or if its ok.

There are 3 more blue work units when multi shot NR is turned on... the 6D trick of putting bvram into shoot malloc to get them to free doesn't work... just shuts down LV.

So total theoretical memory is 6*~32 unless its just a mirror.
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 05, 2013, 09:42:52 PM
I am now getting 1280x480 continuously. The aspect ratio is 2.5:1. Go up to 2.39:1 and stops at 44 frames. I am currently processing a clip but the squeeze and pink dots are still there but 1280x480 is pretty nice.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 05, 2013, 10:16:59 PM
Battery is charging... I'll see if I can do anything w/ pink dots or MZ while recording H264.

Zoom mode its not stretched... but its hella hard to get into when the memory thing is done and menu nor rec work..

Are dots gone?

EOSM getting an update... hopefully they improved the software. We'll have to start the fun all over again.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 06, 2013, 09:35:55 PM
Is there a new version with the dots bug fixed? I think the squeeze is even more annoying, because as long as it's squeezed there is no chance to test how much quality is possible with the eos m.
Anyone tested lower framerates (maybe 18 or 16) and then strech it to 24fps with slowmovideo or any similar software? If there isn't to fast motion this may work.
Is 1728 the absolute maximum possible horizontal resolution?
There is a bug with the zoom, if fps override is active. After zooming in it works for a moment and then the screen doesn't get updated anymore, until you zoom out again. Don't know if this bug is already known.
Anyone ever tried what the limit of the sd-controller in the eos m is? Will it be possible to get more than 24-26MB/s with a faster sd-card like the Sandisk Extreme Pro?

I hope they improved the autofocus in the new firmware as much as they say. Since the update seems to mainly change stuff at the autofocus system it shouldn't interfere that much with magic lantern, or do you think it will?
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 07, 2013, 11:35:19 AM
Is there a new version with the dots bug fixed? I think the squeeze is even more annoying, because as long as it's squeezed there is no chance to test how much quality is possible with the eos m.
Anyone tested lower framerates (maybe 18 or 16) and then strech it to 24fps with slowmovideo or any similar software? If there isn't to fast motion this may work.
Is 1728 the absolute maximum possible horizontal resolution?
There is a bug with the zoom, if fps override is active. After zooming in it works for a moment and then the screen doesn't get updated anymore, until you zoom out again. Don't know if this bug is already known.
Anyone ever tried what the limit of the sd-controller in the eos m is? Will it be possible to get more than 24-26MB/s with a faster sd-card like the Sandisk Extreme Pro?

I hope they improved the autofocus in the new firmware as much as they say. Since the update seems to mainly change stuff at the autofocus system it shouldn't interfere that much with magic lantern, or do you think it will?

hello there, I've just got my M yesterday and begin testing a few minute ago.

first experiences like yours. I've expected more with digic5, because I already got 20MB/s with 550D (I've sold one of my 550D's to get M) a bit disappointed when I open DNGs on Photoshop, all red-pink-magenta-blue dots random at the scene... tried lots and lots of combinations but no luck, still gettin them, really annoying.

I've tested lower frame-rates even down to 2,5fps, if you adjust sth lower than 20fps image turns to pinkenta, I don't like it, but after effects corrects it nicely. another problem is frame stretched, 2:1 image looks like 3:1 its a bit annoying too, but software handles that too.

I've never experienced the zoom-bug problem, had trouble on 550D when RAW video module on, but M works fine.

I'm using Sandisk Extreme 45MB/s version and got stable 29,7MB/s recording rate. I don't think sandisk extreme pro 95MB/s helps, because its controllers max output rate (if its same as 650D) 50MB/s and on video you can get max 31MB/s peak. (you have to low level format to get max performance out of sandisk extreme series)

if/when they release the new firmware for AF speed and other stuff (new lens I think) we have to start all over again to crack the codes of canon.

M is a nice compact camera but gets too hot in short time (experimented about 30minutes and it was 38^C).

I've found a 2 bugs, one on sensor temp, my sensor always shows level above 100^C, I hope you can fix it. another on modules folder, if you put more than 1 module, camera never loads RAW module.

focus points
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Ffbcdn-sphotos-f-a.akamaihd.net%2Fhphotos-ak-prn1%2Fp480x480%2F943788_659327730749325_1038439508_n.jpg&hash=bf73025e36391c9b53ef930386e00290)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 07, 2013, 02:30:15 PM
The sheet on http://www.magiclantern.fm/forum/index.php?topic=6215 says, that the eos m sd-controller can handle up to 40mb/s. Is that real with a fast enough sd card, or more a theoretical value?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 07, 2013, 03:15:54 PM
Its like 6D controller.. so sandisk 45MB/s is the fastest.. Still getting the dots? I'll try some more thinks. I think it needs a custom module with unsqueeze all the time..


So it will load a single module all the time? The only way all modules load for me is cold boot in video mode.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 07, 2013, 03:43:51 PM
Is the version from June 03 the most recent version? If yes in that version are still dots.

I use a sandisk 45MB/s and get ~26mb/s.

If i start recording while in zoomed (5x or 10x), or zoom while recording, the recording stops.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 07, 2013, 03:53:21 PM
June 5th is the latest.... look for updates in the repo.

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5D%20Less%20Lag%20Fileman.zip

I thought you guys new to look there.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 07, 2013, 04:00:24 PM
I saw that there was another zip, but since the name didn't contain the word raw, like the others, i thought, that it doesn't address any raw video bugs.
I'll try the new version.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 07, 2013, 04:04:41 PM
All contain raw and latest raw commits pushed and at least slightly tested. So if no raw commits to main or TL6D then probably no raw related changes.. otherwise raw related changes.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 07, 2013, 04:09:33 PM
Dots are gone in that version, nice!
Still squeezed and zoom still stops recording.

Oh, not be able to record while zoomed was my fault. I switched back to movie mode before i started to record. Recording zoomed in photo mode does work.

I did some more tests and now, as i didn't use it the wrong way anymore ;), it records 30p 1280x544 without dots and not sqeezed. It continously writes ~ 35mb/s on the sd-card (tested 2 times with 1000 frames each, buffer is manly 1 * sometimes the secound * shows up for a moment, Sandisk 45MB/s sd-card used).
FPS override still doesn't work for me? Any hints? If i activate fps override zoom won't work at all. It just freezes the screen. If that would work even higher resolutions should be possible, shouldn't they?

30p 1280x592 (2.20:1) seems to be the absolute maximum for continous recording on the eos m (37 mb/s).

Okey, if i zoom in first and then activate raw video and fps override i can start recording, but the results are weird (preview is freezed while recording, but the raw video info refrehes)...
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F7n58ggvkcz2nb7i%2F000000.jpg&hash=a936b189d6514cf071c8d46147df728d)

Is there any way to get an unsqueezed image with fps override, for recording 24p, so far? And is there any way to preview what is actually recorded, while it's recording?

1280x592 30p fills slowly the buffer, so 1280x544 30p seems to be the maximum.
I added the possible values to:
http://www.magiclantern.fm/forum/index.php?topic=6215
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 07, 2013, 08:32:23 PM
Don't do 30P... do high jello fast TV until I figure out the timings for zooooom mode. First digicV camera that has different ones...  we won't get better image until I figure out how to turn LV into recording LV all the time.

Dots are gone but no sprinkles, right?
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 07, 2013, 08:54:03 PM
1280x544 resized to 1280x720 looks fine but there are some red dots on the edges of white objects:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ff.cl.ly%2Fitems%2F1T1K3r1v0f2w3F262v3v%2F000000.jpg&hash=87d5681814309893cb25704c0ff93e19)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 07, 2013, 09:12:48 PM
high jello works great, thx.

don't know what you exactly with sprinkles mean. everything looks quite correct. i can upload some examples if they help.

Is there any way to get the unzoomed result while recording in 5x zoom, so far? Or has to squeeze bug to be solved first?
Title: Re: Tragic Lantern for EOS M
Post by: hercules85 on June 08, 2013, 02:27:16 AM
Great work guys.
I think canon give us a new firmware.  :D


http://www.canon.co.nz/About-Canon/News-Events/News-Press-Releases/EOS-M-Firmware?cid=scfbnz1306004 (http://www.canon.co.nz/About-Canon/News-Events/News-Press-Releases/EOS-M-Firmware?cid=scfbnz1306004)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 08, 2013, 04:05:50 AM
What aspect ratio should it be? I think handling normal lv like 720P mode will kinda fix this.
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 08, 2013, 05:43:40 AM
At a glance I have no dots, just the squeeze at 1280x480. Again, only a glance, short on time this weekend
Title: Re: Tragic Lantern for EOS M
Post by: Achimogata on June 08, 2013, 05:54:53 AM
I think canon give us a new firmware. 

http://www.canon.co.nz/About-Canon/News-Events/News-Press-Releases/EOS-M-Firmware?cid=scfbnz1306004 (http://www.canon.co.nz/About-Canon/News-Events/News-Press-Releases/EOS-M-Firmware?cid=scfbnz1306004)

Sounds very good news  :)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 08, 2013, 09:26:23 AM
What aspect ratio should it be? I think handling normal lv like 720P mode will kinda fix this.

16:9 video is also squeezed without zoom. this is a 16:9 setting (even if magic lantern doesn't exactly record 16:9):
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fdl.dropbox.com%2Fs%2Fx0vucfyb2b2hfxv%2F16-9.jpg&hash=19460bb408786be2bc653b12bdb96e64)

the pattern on the floor should be quadratic.

same resolution (nearly 16:9), but with 5x zoom:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fdl.dropbox.com%2Fs%2F1yamm5yeklh9c1n%2F16-9_5x.jpg&hash=06f68d5e7b15b67ae19fc3f32ead0a54)

result is not squeezed, but a very narrow angle of view (like 5x digital zoom).
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on June 08, 2013, 11:13:13 AM
1280x544 resized to 1280x720 looks fine but there are some red dots on the edges of white objects:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ff.cl.ly%2Fitems%2F1T1K3r1v0f2w3F262v3v%2F000000.jpg&hash=87d5681814309893cb25704c0ff93e19)

Pink/Green dots = edge detection debug stuff still enabled  >:(
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 08, 2013, 04:54:24 PM
Yea and we have to find a different raw type.. I turn this off and its much much worse.

*Did you find a good rawtype for 650D? Or did MD_visible take out the af dots?

BTW, new build is up hopefully set to unseqeeze all the time (not zoom)... dunno if it helps.


Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 08, 2013, 09:14:20 PM
Maybe it's my fault, but i still get squeezed results without zoom. Do i have to use a special resolution or aspect ratio. Or do i have to activate any special option?

Oh and i asked it on the other thread, but here again: May it be possible in far future to get interlaced recording. For example 1728x992 24i. With not to fast motion, that may lead to better results than 1216x672 24p if it's converted to 1080p.

I did some more tests and it seems that the vertical resolution is reduced by the factor ~1,65 all the time (maybe that information helps to find the bug). So in post, just strech the image by factor 1,65 in the vertical and you'll get an unsqueezed image. So for 16:9 it's at the moment best to record 3:1. And then strech it to 16:9 in post. For example recording 1664x560 and then unsqueeze it to 1920x1080.

Now, that i know the factor to unsqueeze in post i did a small comparison to see if the current quality you can get with the eos m is already better than h.264. It was quite dark, so quality of all 3 is not at it's maximum.
The first is standard profile, with just some sharpening in post. The second is technicolor cinestyle with s-curve, increased saturation and bit more sharpening. The third is the raw video recorded in 1664x560 24p, unsqueezed and scaled up to 1920x1080. Added some noise filtering and other stuff in darktable to reduce noise and pink dots at the edges.
https://dl.dropboxusercontent.com/s/eeuvfx47y0qktif/compare.webm

The postprocessing isn't optimal, since i'm not at the pc i've the correct video editing software installed (that's also the reason why i removed the noise in the raw images instead of the video, etc). I'll do a better testvideo tomorrow.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 09, 2013, 06:10:27 AM

Now, that i know the factor to unsqueeze in post i did a small comparison to see if the current quality you can get with the eos m is already better than h.264. It was quite dark, so quality of all 3 is not at it's maximum.
The first is standard profile, with just some sharpening in post. The second is technicolor cinestyle with s-curve, increased saturation and bit more sharpening. The third is the raw video recorded in 1664x560 24p, unsqueezed and scaled up to 1920x1080. Added some noise filtering and other stuff in darktable to reduce noise and pink dots at the edges.
https://dl.dropboxusercontent.com/s/eeuvfx47y0qktif/compare.webm

The postprocessing isn't optimal, since i'm not at the pc i've the correct video editing software installed (that's also the reason why i removed the noise in the raw images instead of the video, etc). I'll do a better testvideo tomorrow.

Which card you are using when you can record 1664x560 24p? The best I can do is 1280x544 with SONY 94 MB/s - 16GB card
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 09, 2013, 06:41:50 AM
Did squeeze change though... it should "unsqueeze" all the time... but not sure if thats just a meta data setting. I'll have to experiment some more. So its like 5:3 ratio?
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 09, 2013, 07:14:26 AM
Hi could someone guide me on how to load ML raw capability on my EOS M.

My workflow till now:

1. I copied Alpha 1 on the SD card.
2. Replaced it autoexe file and pasted the module from the latest upgrade available.

Now can do HDR and other stuff but cannot figure out the RAW workflow.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 09, 2013, 07:22:04 AM
Did squeeze change though... it should "unsqueeze" all the time... but not sure if thats just a meta data setting. I'll have to experiment some more. So its like 5:3 ratio?

[EOSM] Better I hope.zip:

- it's still squeezed

- it's more like 3:1 ratio
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 09, 2013, 09:54:12 AM
xpstudio sounds like you've not activated multishot nr, or you're not in photomode. i did the same mistake.
read this post from 1% and do exactly what he wrote (and don't switch back to movie mode afterwards, raw video recording has to be done in photo mode):
http://www.magiclantern.fm/forum/index.php?topic=3648.msg45050#msg45050

"Canon eos m"... just read that post too, it's explained there how it works.

1% it's squeezed by 5:3, yes. 1664/5:560/3 = 333:187 ~ 16:9. What exactly does "it should "unsqueeze" all the time... but not sure if that's just a meta data setting." mean? isn't it recording the correct aspect ratio anyways, but it's streched in the raw2dng converter? isn't it possible to just record the correct pixels, that it doesn't have to get "unsqueezed"?
any comments about if interleaved recording might be possible in far future? Of course this might lead to some trouble with the bayer matrix, since each line contains only blue or red color info. But this information can be calculated in the deinterlacing process. Alternativly recording 2 lines and then skipping two lines should solve the problem. Or don't you think we can get better results with an interlaced feature? i think with not or slow moving objects we can just get double of the resolution.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 09, 2013, 10:05:50 AM
720P mode on other cameras is the same (but 30P vs 60P).. the image in the raw buffer is really squeezed like that (not square pixels).. something has to unsqueeze it.. right now unsqueezing for 16*9 so thats why its still wrong.


Interlaced I doubt.. i guess it could move the zoom box, but no way is it fast enough.. 60P on SD cameras sucks all around. Only hope is switching LV to another mode.. I did it on 600D and got a big YUV buffer in photo mode for a while just have to find out how (not that easy).
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 09, 2013, 10:29:34 AM
Sorry, i can just guess, since i don't know anything about canon firmware internals. Just thought you read it anyway bit-by-bit or pixel-by-pixel from the buffer and it might be possible to just modify the index that it skips some pixels. But that seems not to be the case.
So best chance to get more pixels without fast motion is to record less fps and interpolate the missing frames with slowmovideo in post.

So quality won't improve by solving the squeezing bug anyways? Then the only bug that reduces quality at the moment is the edge detection stuff, isn't it? As soon as that is resolved we will see the maximum of quality we can get out of the eos-m.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 09, 2013, 10:49:03 AM
Thanks mixer2, I was in video mode all the time.

I'm wondering how you managed to record in 1600x540? I'm using SONY 94MB/s and can't write more than 33MB/s - 1280x544 (with a few skipped frames) is max I can get in 23.976 frames.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 09, 2013, 11:00:11 AM
Have you activated multishot nr? When you start recording, you'll see one of the messages "Alloc 29+21" or "Alloc 32+32+29" at the bottom left for a moment. Which one do you get?

1280x544 doesn't need 33mb/s, just ~ 27mb/s. Do you have raw sound recording activated, which does cause additional data?
I do use a Sandisk 45mb/s, but i don't think that your card speed is the problem.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 09, 2013, 11:07:48 AM
Have you activated multishot nr? When you start recording, you'll see one of the messages "Alloc 29+21" or "Alloc 32+32+29" at the bottom left for a moment. Which one do you get?

1280x544 doesn't need 33mb/s, just ~ 27mb/s. Do you have raw sound recording activated, which does cause additional data?
I do use a Sandisk 45mb/s, but i don't think that your card speed is the problem.

Not sure where to activate 'multishot nr'? I see "Alloc 29+21"
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 09, 2013, 11:19:14 AM
found it  ;)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 09, 2013, 12:02:14 PM
Okey, nice...
I made a small video, that shows the steps to start recording, maybe this will help someone. I think it's easier to understand than in text form, since recording video in photo mode is not what you would expect first. I'm not sure, if the battery has to be removed every time, but i always start with removing battery to get a clean starting point and avoid problems.
https://dl.dropboxusercontent.com/s/s3o76x7h0t7u0s3/startrawrec.webm
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 09, 2013, 03:52:25 PM
Wow I feel stupid, I had the wrong noise reduction set. Now I am getting 1408x608 @ 23.976 continuous on a Sandisk 45MB/sec card. Really though since vertical resolution is maxed at 688 I like 1280x688 and it seems to not even use much of the buffer on that resolution
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 09, 2013, 05:20:40 PM
When I turn on the power on my EOS M, I get the error "scripts dir missing". Is this of any concern.

Second, I have installed Alpha 1 and the Modules with the upgraded autoexe file on the EOS M. Any idea on how to use this combo for recording RAW video.

Whatever you folks discuss on this forum is technically challenging for me to understand. Is there a simple workflow video where I could learn to do this?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 09, 2013, 05:48:10 PM
For raw recording you've to download this file:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM]%20Better%20I%20hope.zip
Overwrite the autoexec.bin on your sd-card with the one from the zip.
Then copy the two directories "SCRIPTS" and "MODULES" from the zip into the "ML" directory on your sd-card. (This will also solve the missing scripts dir warning)
Put the sd-card in your camera and you're ready to go. For activating raw recording check the video i posted 2 posts above.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on June 09, 2013, 06:11:38 PM
I've install ML on my new EOS-M. When i enable touch shutter, the camera froze and now normal shutter button don't work. Focusing work on half-press but camera don't take any picture when full press. Can anyone help me. I read all the thread in this post and i've install the new autoexec.bin but nothing work. I'm freaking out.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 09, 2013, 06:42:44 PM
Thank you Mixer2.

Error sorted and ML updated to latest. Now will try and follow you other instructions to see if I can manage to run RAW video on the EOS M.

Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 09, 2013, 06:44:29 PM
Hi Escaperoute,

Follow the instructions here:

http://www.magiclantern.fm/forum/index.php?topic=5520.0

This link provides a checklist of files that should be on the SD card to run ML trouble free.

Hope this helps.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on June 09, 2013, 06:49:49 PM
After a scaring period, now my 22mm eos m lens work, but only after i format the memory card and remove magic latern. By the way i can't uninstall ML. I follow the instruction but ML just install again.

But i can't get the 18-55 mm lens to work. It focus in half press but i can't take any shot with it. I saw something similar problem in this post but i've install the newest autoexec.bin but i can't get 18-55 mm lens to work.
Is there something happen to my lens.

With 22mm lens touch shutter work but with 18-55 m lens camera froze. Power button don't seem to work. Only after removing the battery camera seem to work. Can anyone HELP ME.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 09, 2013, 07:04:02 PM
For raw recording you've to download this file:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM]%20Better%20I%20hope.zip
Overwrite the autoexec.bin on your sd-card with the one from the zip.
Then copy the two directories "SCRIPTS" and "MODULES" from the zip into the "ML" directory on your sd-card. (This will also solve the missing scripts dir warning)
Put the sd-card in your camera and you're ready to go. For activating raw recording check the video i posted 2 posts above.

Not sure how I can get to the Modules on my EOS M.
When I two finger tap the touch screen, the complete ML menu comes up but the Modules screen is nowhere to be seen. What am I doing wrong?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 09, 2013, 07:27:32 PM
Heh, shutter release bug is a canon bug... thats why they are push a new firmware.

22mm and lots of other lenses working here like normal.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 09, 2013, 07:34:02 PM
Has the latest version any interesting changes? Disabled edge detection dots or fixed unsqueeze?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 09, 2013, 07:36:35 PM
Yea, I set it to 5:3 and tried 5d3 rawtype.. hopefully it worked, if not we'll look for another ratio/rawtype.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on June 09, 2013, 07:49:03 PM
I not thinking that shutter release bug is canon's coz when i remove the battery for 30 min or so and format the memory card, clear the camera setting with 22 mm attach and again clear the setting with 18-55 mm attach then shutter work fine for 18-55.

But i want to know what the bug is so i just install ML again and same thing happen. Right now i'm repeating the process all over again. Hope my 18-55 mm work again.

I'm gonna try the ML only after firmware 2.0 release and ML for EOS-M gets a new release. I sincerely hope canon and you guys can squash the bug and make a good camera perfect.

I'm greatful for all the dev hardwork and i'm enjoying my raw video for my 550D.

I hope after the much needed firmware update get release, ML devs gonna pay much needed attention for EOS-M.

Anyway you guys rock. Because of you guys i'm loving canon.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 09, 2013, 07:50:06 PM
Hi Mixer2 & 1%,

How do I activate the Modules on my screen for RAW video activation. The two finger tap does not bring up the modules window.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 09, 2013, 07:52:59 PM
@"Canon eos m" the modules window is the last tap on the normal ML menu. So just click "right" in ML menu, till you get to it.

@1%: Nice, i'll try as soon as i'm at home and report.
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 09, 2013, 07:57:29 PM
Dots on this one are back

Yea, I set it to 5:3 and tried 5d3 rawtype.. hopefully it worked, if not we'll look for another ratio/rawtype.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 09, 2013, 08:15:29 PM
according to my last tests and your advices, I can get 25fps @ 1728x576 with frame skipping on, it skips 20 frames on 400, records at about 37.8MB/s continuously to Sandisk Extreme 45MB/s (low-level formatted) card. I'm now processing the files, I'll share the results if I have AF dots on the frames.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 09, 2013, 08:19:34 PM
yup, dots are back:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ff.cl.ly%2Fitems%2F400E292P3R1W2s2X2T35%2FScreen%2520Shot%25202013-06-09%2520at%252011.10.11%2520AM.png&hash=0109a860f1c5c4d5de66fbcb38c07581)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 09, 2013, 08:20:13 PM
Heh, so will have to try something else... stupid phase detection. Damned if you do, damned if you don't.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 09, 2013, 08:27:19 PM
do you think we can mask that dots on after effects with 2nd layer and some sharpening?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 09, 2013, 09:00:22 PM
You can try.. I'm going to run the rawtype test and see if any have no detection and no dots.. what is better tho, assuming we can't turn it off, the outlines or the dots.. .to me the outlines seem better/easier to mask.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 09, 2013, 09:05:01 PM
just did, its killing the cpu and results still suck. you're right, we have to seek another option.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 09, 2013, 09:11:10 PM
So raw_type is causing high cpu usage? Did all 100 types go through?
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 09, 2013, 09:17:45 PM
no no, after effects killing the cpu :) it really doesn't worth to wait 1hour render for 15sec video
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 09, 2013, 09:25:12 PM
I see...the dots are really hard to mask, the edge detection usually comes out with noise removal.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 09, 2013, 11:54:32 PM
I found this to be the best settings at the moment:

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ff.cl.ly%2Fitems%2F2z1V2g0w1M3n1e2L0E07%2Fcam-settings.jpg&hash=0804441700d001d1b5a602c5327d390f)

and then in AE, I resized it to 1600X900. Looks fine but there are green/red dots around edges of the subject and I'm not sure how to remove them in AE. Tried with Magic Bullet Denoiser but without luck.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 12:57:13 AM
I do force left.. thought about switching it on by default.. dunno what people are using though. GD off I dunno if people need on digic V. Did it increase write speed any.

Frame skipping I don't use, I'd rather it stop than randomly stutter.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 01:38:56 AM
..GD off I dunno if people need on digic V. Did it increase write speed any...

with GD off I'm getting almost 18,5MB/s continuous write rates on same memory card (sandisk extreme 45MB/s 16GB) on 550D, but now I can see it can almost make 37MB/s average write rate on EOS M.. %100 performance increase if you ask me.

but I think I have to sell my all equipment and wait for 5D Mark III prices go down a bit. because 550D stuck at 20MB/s level and have to use twixtor to upscale frame rate from 12-17 to 24fps, and EOS M has little AF dots middle of video and takes forever to mask them on After Effects..
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 10, 2013, 03:10:13 AM
@"Canon eos m" the modules window is the last tap on the normal ML menu. So just click "right" in ML menu, till you get to it.

@1%: Nice, i'll try as soon as i'm at home and report.

I don't see the normal ML menu on my screen. After loading the latest upgrades of the autoexe.bin and modules I only see an excel sheet like menu with no modules section.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 03:51:39 AM
You hit junkie mode.. hit menu again.

I wouldn't give up on M yet, still have a chance at fixing some of this + new firmware update from canon.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 08:06:43 AM
I wouldn't give up on M yet, still have a chance at fixing some of this + new firmware update from canon.

of course, its just a 5 day old camera :) not selling it before it takes 50000 photos. I wonder if it has that problem on 550D, mirror-curtain (of course it doesn't have the mirror but, there is still a curtain inside) wearing with highspeed continuous photo shooting.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 10, 2013, 10:16:09 AM
You hit junkie mode.. hit menu again.

I wouldn't give up on M yet, still have a chance at fixing some of this + new firmware update from canon.

Thanks again 1%. Looks like now I am all set to proceed to the next phase of my journey. Will keep you posted of any issues during this phase.

For all those that need to learn the basics of RAW / HDR video the EOS M can be a deadly companion waiting to be exploited. Being able to do even 50% of those $4000++ devices out there says a lot.

The ML team and developers have just taken the whole Canon ecosystem by the horns and made photography so much more fun. And now Canon has promised an update to fix the focusing issues.

This is the best time to be alive! The best thing for me was joining the ecosystem and be able to draw and draw till my brain cannot take anymore.

These recent days, I figured out a way to make my 5D Mark 3 RAW capable using the ML upgrade. I tried taking a few videos with it using a Class 10 95MB/s Scandisk SD Card. I now manage to capture about 100 frames before the buffer runs out. Don't know why and don't know what it means not to be able to do more .... but .... the fact that I recorded RAW has got me loving it and wanting more.

God knows how I want to learn to take better videos and show these off to the world.

I also feel a part of the ML team in some strange way. Feels like everyone involved has one aim - to make everyone else more equipped so that the world can come as one to produce amazing pictures and films.

The day in not far when ML will be spoken about as a team that changed the world forever!

The day is not far when some of us will produce their first full length feature film and release it to commercial success and possibly win an OSCAR!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 12:37:22 PM
sd-cards (at least the controllers in the cameras for the sd-cards) are to slow for the high resolutions you can get with 5d mark iii. so use a fast cf-card to get continuous recording...
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 10, 2013, 01:20:31 PM
Ordered the Komputerbay CF 128GB 1000x. Should be delivered any day now.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 02:42:42 PM
Ordered the Komputerbay CF 128GB 1000x. Should be delivered any day now.

to use on EOS M? or just kidding?
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 04:18:03 PM
anyone experienced frame drops on HDR video at high-bitrate (I'm using 9.0x now with sandisk extreme 45MB/s) ?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 04:31:49 PM
This might be a problem with sync being different while recording.. ie MZ isn't in sync anymore so HDR might not be either. Did you try with normal rates? All I've gotten from EOS-M is way under max write of the card. Find an easily reproducible way to make it fail and I'll be able to test. Also does it have the problem with HDR raw?
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 05:00:45 PM
This might be a problem with sync being different while recording.. ie MZ isn't in sync anymore so HDR might not be either. Did you try with normal rates? All I've gotten from EOS-M is way under max write of the card. Find an easily reproducible way to make it fail and I'll be able to test. Also does it have the problem with HDR raw?

yeah, I've forgot to ask, where I can get that module. because I only have raw_rec.mo and MAGIC.SYM.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 05:48:18 PM
Had no time to test the version from yesterday until now. As others said before, the dots are back. And it's still squeezed.
I think the problem is, that 16/9 (~1,77) is nearly the same as 5/3 (1,66) so we don't see much difference. The 5/3 is the relative squeeze factor for the already unsqueezed 16/9. 16/9 has to be unsqueezed by factor 5/3 not 1/1.
9*5/3 = 15... => the correct absolute unsqueeze factor should be 16/15.
let's assume the measurement wasn't perfect and we additionally lost some accuracy with rounding i think it's just 16/16 => 1/1.
I think it doesn't have to be unsqueezed at all. The problem was the unsqueeze factor of 16/9 which squeezed it to nearly 50% height.
Just a guess.... but that's  how it looks like for me.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 06:01:06 PM
the real question is, how canon manages to record video without AF dots.

because you know, there must be an optical shift.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 10, 2013, 06:27:47 PM
anyone experienced frame drops on HDR video at high-bitrate (I'm using 9.0x now with sandisk extreme 45MB/s) ?

On my 5D M3.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 07:04:41 PM
I did unsqueeze of 5:3 so it would be multiplied by 3/5... I'll try 16:15 next I guess. I'll go back to af_raw if none of the raw types remove the dots.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 07:15:19 PM
Try 1/1, i think 16/15 is a measurement inaccuracy... I just took a video of a circle and measured, how much it's squeezed. It's not a very accurate way of getting the squeeze factor. And 16/15 is so near to 16/16 or 1/1, that i can't imagine, that the difference doesn't come from inaccuracy because of the measurement.
Title: Re: Tragic Lantern for EOS M
Post by: coutts on June 10, 2013, 07:20:47 PM
to use on EOS M? or just kidding?
hope he knows eos m uses sd not cf
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 07:22:52 PM
read the posts above... he wondered why his 5d3 wasn't able to record continuously in high resolution, while using sd-card. it was just OT.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 07:37:33 PM
1:1 is no unsqueze at all, just like default.

So no raw type helps.. dots come on. AF_RAW gets rid of dots but causes the "peaking" effect.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 07:46:41 PM
exactly... i think the unsqueezing was the reason why it was squeezed. The current factor is 5/3. if i take a frame (1280x688) and undo the 5/3 squeezing i get 688*5/3 ~= 1146. If i resize it to 1280x1146, it looks just perfectly unsqueezed.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 08:04:39 PM
read the posts above... he wondered why his 5d3 wasn't able to record continuously in high resolution, while using sd-card. it was just OT.

I don't have a 5D.III troll. read my signature.

this is an EOS M thread and I'm talking about it. you're the one writing about your 5D.III. go that thread and write you've ordered whatever for your camera.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 08:08:43 PM
You quoted "Canon eos m" and he has. I just gave him an answer to his question, even if it was OT...

These recent days, I figured out a way to make my 5D Mark 3 RAW capable using the ML upgrade. I tried taking a few videos with it using a Class 10 95MB/s Scandisk SD Card. I now manage to capture about 100 frames before the buffer runs out. Don't know why and don't know what it means not to be able to do more .... but .... the fact that I recorded RAW has got me loving it and wanting more.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 08:14:30 PM
I've quoted %1 and asked about modules, read the post, again, and again, then again.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 08:18:30 PM
Ordered the Komputerbay CF 128GB 1000x. Should be delivered any day now.
to use on EOS M? or just kidding?

Are you kidding now?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 08:32:43 PM
Original was not unsqueezed and it still had to be resized to be fixed.

Some new hope in the dead pixel remover that just got committed. Next one I guess I'll just do no unsqueeze and fix it in post.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 08:40:03 PM
hurm, then i really don't understand it at all.
what's in the source:
int correct_height = max_res_x * 3 / 5;

and we get a squeezed 1280x688 what looks perfectly unsqueezed when resized to 1280x1146.
correct_height = 688
max_res_x => 688/3*5 ~= 1147
if you use:
int correct_height = max_res_x;
correct_height should be 1147 or 1146, depends how it's rounded.
and 1280x1146 (or 1280x1147) should be the result, which should look perfectly unsqueezed. what exactly is wrong in my calculation?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 08:49:40 PM
Will try it and see what  happens.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 08:53:32 PM
I hope it will work. As said before, i don't know anything about how all the stuff works... just playing around with the numbers and guess a solution :D
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on June 10, 2013, 09:00:31 PM
Shouldn't be int correct_height = max_res_x * 2 / 3 ?

The image covers usually a 3:2 or a 16:9 area. I don't see why Canon would have designed it for 5:3... and from the dng posted a while ago, with the square floor pattern, it should be 3:2.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 09:09:44 PM
The image was 1152x656, but it was already unsqueezed by factor 16/9.
To undo that 656*16/9 = 1166
Then do the 3/2 unsqueeze:
1166*2/3 = 777

But if you resize it to 1152x777 it still looks squeezed.

What's a bit strange is, that if i use the undone 1166 height, it's minimal vertically streched. But, if i do the undo calculation with 5/3:
656*5/3 = 1093 and i resize the image to 1152x1093 and it's perfectly unsqueezed. So 1:1 might be not perfect.
So i'm back at the:
int correct_height = max_res_x * 15 / 16;

still just guessing, sorry...
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on June 10, 2013, 09:16:58 PM
It's 1728x672, resize to 3:2 (1728x1152) and it looks OK to me.

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2Fraw%2Feosm.jpg&hash=9ffdbfedb7c460098303fe4df09e6326)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 09:21:51 PM
Ok, got it.. so its 3:2...
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 09:29:04 PM
hurm... that does look correct... but how have you exactly calculated the 1728x1152?
672*16/9*2/3 = 796

don't know what i do wrong... but... if you know the solution everything is good xD

is one of you in the irc, to discuss that more directly than in the forum. would love to understand what i did wrong.
Ah, i see. you calculated it with the width:
1728/3*2.... but... when the source, at the time the frame was taken, was:
int correct_height = max_res_x * 9 / 16;
why was the resulting vertical resolution 672???
1728*9/16 = 972

If it was 5/3 that time it wouldn't result in 672 too.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 09:49:57 PM
Okey, tested the new version.
2 things are annoying:
1. have to disable and reenable "Use photo mode", to enable raw recording
2. the guessing mb/s guess in the menu is completely different from the one mb/s it shows while recording (22mb/s vs ~37mb/s). don't know which one is correct.

The dngs we get are still squeezed, but it tells in the menu that it has to be unsqueezed in post (with the correct ratio). Is that how it should be. Will the unsqueezing never be done automatically and has to be done in post all the time?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 09:52:16 PM
Heh, set it on by default.. .will have to fix it so it actually switches to fake movie mode.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on June 10, 2013, 10:12:21 PM
Hi,
I just can't seem to uninstall ML on my camera completely, i follow all the instruction completely.

I have some experience with ML, it run smoothly on my 550D but on my EOS-M 18-55 mm shutter release bug is really annoying.
When i install the ML on my camera. it run smoothly, but when i enter the Menu setting i can't seem to find firmware update option with ML signature like on my 550D, when i update with ML memory card installed it just install ML again, Maybe bootflag cannot be remove.

22mm lens work fine. But i use 18-55 mm mostly, can anyone help me. i've read all the post but nothing seem to help me. I'm freaking out again since my 18-55 mm lens work sometime and sometime it just don't with or without ML on SD card.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 10:16:31 PM
Hi,
I just can't seem to uninstall ML on my camera completely, i follow all the instruction completely.

I have some experience with ML, it run smoothly on my 550D but on my EOS-M 18-55 mm shutter release bug is really annoying.
When i install the ML on my camera. it run smoothly, but when i enter the Menu setting i can't seem to find firmware update option with ML signature like on my 550D, when i update with ML memory card installed it just install ML again, Maybe bootflag cannot be remove.

22mm lens work fine. But i use 18-55 mm mostly, can anyone help me. i've read all the post but nothing seem to help me. I'm freaking out again since my 18-55 mm lens work sometime and sometime it just don't with or without ML on SD card.

copy all the files on your card to your computer,
format the card (if exfat) to fat32, (if fat32) to exfat,
move all the files again to the card,
use EOSCard utility to make your card bootable for magic lantern,
insert the card to the camera, use firmware update option, when you see the green text just switch to movie or photo mode.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on June 10, 2013, 10:36:36 PM
Thanks for the fast reply,

But what i'm trying to do is to get the ML loaded on my camera with 18-55 mm lens working, i've successfully uninstalled it but i can't seem to get it work with 18-55 mm attached.
Any comment??
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 10:41:53 PM
The lens thing is a bug I think.. hence canon update... all of my normal lenses work with the adapter and so does the pancake... btw modules seem to load up in photo mode now.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 10, 2013, 10:50:02 PM
Thanks for the fast reply,

But what i'm trying to do is to get the ML loaded on my camera with 18-55 mm lens working, i've successfully uninstalled it but i can't seem to get it work with 18-55 mm attached.
Any comment??

no problem, I don't have 18-55 and don't have any idea what you are experiencing on EOS M, you have to wait for the update end-of-june from canon. maybe they'll fix it.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 10, 2013, 10:56:12 PM
1% is it how it should be, that unsqueezing has to be done manually in post?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 11:02:47 PM
It appears so.. I guess not much use then :(

How is edge detection + new "dead" pixel removing chdk-dng.c Does it do anything... it didn't fix the dots I think so its back to outlines.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on June 10, 2013, 11:05:18 PM
You need to mark the af dots first for it to work (set them to 0 in raw buffer).
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 10, 2013, 11:26:54 PM
Problem is not sure if they show up in the same spot every time.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on June 11, 2013, 01:12:02 PM
Looks like the EOS-M has a dedicated movie mode: http://www.dpreview.com/previews/canon-eos-m/images/top.jpg

What's wrong with it? why do you have to record in photo mode?

I want to get rid of this hack, because it's giving me lots of trouble on the other cameras.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 11, 2013, 01:13:03 PM
Thanks Mixer2, 1% and A1ex - I finally managed my first workable RAW video with my EOS M running ML.

I notice the red dots you folks have been discussing since the past few days. Doesn't bother me yet since I am on the learning curve and enjoying every moment.


Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 11, 2013, 01:28:48 PM
As far as I can tell it's the only way to get the largest buffer possible. Maybe I'm wrong


Looks like the EOS-M has a dedicated movie mode: http://www.dpreview.com/previews/canon-eos-m/images/top.jpg

What's wrong with it? why do you have to record in photo mode?

I want to get rid of this hack, because it's giving me lots of trouble on the other cameras.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on June 11, 2013, 01:31:11 PM
How big is the buffer in movie mode and how big is in photo mode?

Also the max resolution, does it change?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 11, 2013, 01:44:18 PM
29+21 in movie mode and 32+32+29 with the multishot nr trick in photo mode.
resolution seems to be the same. I get exactly the same values in photo or movie mode, if nr is not multishot. the only difference is, that if multishot nr is active the buffer is nearly double the size. and that's not possible in movie mode.

may it help to check some option configurations in movie mode, if there is also something that frees up some space?
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on June 11, 2013, 01:48:28 PM
Okay... the biggest problem is that exposure in photo mode is not using the parameters you have set in menu, but something with equivalent brightness and usually wide-open.

Sure, you may say you don't care about that, but in that case you can just record H.264.

Another trouble is that I don't like the code complexity increase because of this; on the cameras that don't need it, I want to keep things simple and just record in movie mode.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 11, 2013, 01:56:28 PM
hurm... is there no way to permanently activate dof-preview? the exposure settings should be correct then, shouldn't they?
what's with exp override, anyone said, that this solves the problem.
i never checked, if it uses the correct settings so far, since the quality isn't usable anyways so far.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on June 11, 2013, 02:00:52 PM
Yes, expo override helps. If ML says Mv in the bottom-left corner, it should be OK.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 11, 2013, 02:57:40 PM
Expo override should close down the aperture.

50D too.. doesn't really seem like movie mode. On M in movie mode you can barely record anything because of the memory. The 1 buffer and a few MB actually makes a big difference.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 11, 2013, 07:51:37 PM
I'm not sure but, it seems its possible to hack RAW buffer, because camera can take 5 RAW images, if you count each of them 25MB then you'll have 125MB buffer, seems enough to keep some data and capture more frames. anyone working on that?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 11, 2013, 09:44:38 PM
A quality comparison of the current version:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fdl.dropbox.com%2Fs%2F4ehwn2rrv8jmrjl%2Fdetail_comparison.png&hash=64385c1f0c8a78a27a207901da9a8d5c)
raw at the top and h.264 at the bottom. i think with eos-m raw video it will not be possible to get more details than with h.264, will it? are there still things left, that may increase the quality that much? Or is there something wrong with my post?
so raw video on eos-m will make sense if there is need for a lot of dynamic range or to extend the focal length with the digital zoom. but results doesn't look very pleasant, so far.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 11, 2013, 10:16:02 PM
to me, even this is a huge step.
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ffc07.deviantart.net%2Ffs70%2Ff%2F2013%2F162%2F0%2Fd%2Fcomp_compare_by_weraqs-d68njig.jpg&hash=5106c6003264533c3cb347cca13cf456)
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 11, 2013, 11:09:38 PM
processed a 1280x544 Total 542 Frame RAW Video. I like it, but still, there are some problems with framerate.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 12, 2013, 12:00:55 AM
Yea, there is a chance for more buffer if the blue blocks can be recovered.
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on June 12, 2013, 02:55:16 AM
Hello great people,

Even with the help of nanomad (thx btw), I wasn't able to get 'make zip' to go through on the nightly repo. The makefile simply doesn't have an "x:" instruction. I want to try this stuff out on my new EOS M but the Alpha posted in the original post doesn't bring up a menu. From what I understand, the trash button should bring up the ML menu, right? Anyway, could someone comment on how newbies such as myself could follow along, and report bugs, with the latest and greatest from ML?

Ciao!
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 12, 2013, 03:12:17 AM
2 finger tap the lcd screen to bring up ML menu on EOS M

Hello great people,

Even with the help of nanomad (thx btw), I wasn't able to get 'make zip' to go through on the nightly repo. The makefile simply doesn't have an "x:" instruction. I want to try this stuff out on my new EOS M but the Alpha posted in the original post doesn't bring up a menu. From what I understand, the trash button should bring up the ML menu, right? Anyway, could someone comment on how newbies such as myself could follow along, and report bugs, with the latest and greatest from ML?

Ciao!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 12, 2013, 03:31:09 AM
@jerrykil, you have to use the current version and install the raw module. Download the following file:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM]%20Check%20unsquee.zip

Extract the "autoexec.bin" and copy it to the root of your sd-card (overwrite the one that already exists). Then extract the two directories and put them in the ML directory of your sd-card.
Remember that you have to shoot video in photo mode and! set nr to multishot. I've posted a video how to start raw recording there:
http://www.magiclantern.fm/forum/index.php?topic=3648.msg48585#msg48585

There is one difference in the current version to the video. You've additionally to turn the "Use photo mode" option in the raw video submenu off and on again, to enable raw recording in photo mode.

@1%:
Shouldn't the "Use photo mode"-Bug be fixed by [EOSM] raw_rec.mo -Fixed Photo Mode? Doesn't seem to work for me. Any ideas, if we may get clean edges in raw video in future? still something to do with the edge detection?
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on June 12, 2013, 03:35:44 AM
Perfect! Thanks guys, can't wait to set it up.

Thanks for the quick reply
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 12, 2013, 04:32:28 AM
It should be working, it did when I tested it. The 6D module is the newest and in theory the EOS-M stuf is in there and  should work. Dunno if it has all the symbols.

I'll make a whole new build soon anyway.


Nothing good with edge detection yet.. its dots or outlines atm
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on June 12, 2013, 05:32:11 AM
Using it now. I'm speechless! Good thing I can still type
=D
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 12, 2013, 11:15:41 AM
am I the only one having problem with "[EOSM] 5D3 Rawtype" and "[EOSM] Check unsquee"? camera freezes, touch doesn't work, and more important thing is its not recording anything. "better hope" versions seems working just fine.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 12, 2013, 12:15:11 PM
Canon EOS M + 22mm f/2 RAW upscaled to FULL-HD Video Test (better hope version)

Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 12, 2013, 07:32:12 PM
What i don't understand is, if the unclean edges are only caused by the edge detection stuff. Will the edges be clean as soon as this gets fixed? Or is that caused by aliasing?
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 13, 2013, 02:56:21 AM
At this point I find the HDR Video option serving me better than the RAW Vido option on the EOSM. I have decided to hang my boots for RAW on my EOSM and leave that for later on my 5DM3 when my Komputerbay card arrives. Will be fishing this thread on and off though.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 13, 2013, 03:38:17 AM
If edges are red or something like that then its outlining.

I think unhack isnt running on EOSM for some reason.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 13, 2013, 10:37:05 AM
okey, then the stair step effect is just because canon skips a lot of pixels when scaling down from 18mp to 1664x560, right?
but the camera does use the exact same data when it encodes the h.264. So it's mainly a postprocessing problem. using the correct filters should solve the extreme stair step effect.
I showed comparison pictures (h.264 vs raw) to some people and even with the stair step effect they like the raw stuff more, because they look sharper and it's possible to get much more harmonious color correction. That surprised me, because, as i wrote a few posts above, i prefere the h.264 so far. For me the stair step effect is very disturbing for the image harmony.
I'll check what's the best way to get good results in post.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 13, 2013, 10:55:20 AM
I'm getting this, whats causing it? over heated sensor, cpu, card?

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fth05.deviantart.net%2Ffs71%2FPRE%2Ff%2F2013%2F164%2F5%2Fd%2Fframe_by_weraqs-d68u659.jpg&hash=acdf8f2b05d93913c11ad1a87a2ceadb)
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 13, 2013, 11:15:38 AM
edit: AF dots, no luck, they are still visible.
Title: Re: Tragic Lantern for EOS M
Post by: gamentine on June 13, 2013, 05:14:32 PM
This is my first experience with Magic Lantern and it's great!

Just one minor hiccup that I've encountered.

After power-off or powersave shutoff the shutter will not release.

I am using the EOS-M with 18-55mm lens.
Removal of battery & SD Card does not solve the issue, only Removal and Reattachment of the lens.

Thanks for all the hard work!
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 13, 2013, 08:55:56 PM
we're all having the same issue with 18-55 EF-M lens.. 22mm is the best lens to use for now (or using other lenses with adapters).
Title: Re: Tragic Lantern for EOS M
Post by: vstrglv on June 13, 2013, 09:19:32 PM
But there is no this issue with 18-55 EF-M lens for ML autoexec.bin from original Alpha1 until at least Mach 2013.
Title: Re: Tragic Lantern for EOS M
Post by: gamentine on June 13, 2013, 09:32:42 PM
I can verify that I don't have the issue with the Alpha 1 build linked in the first post.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 13, 2013, 09:33:14 PM
But there is no this issue with 18-55 EF-M lens for ML autoexec.bin from original Alpha1 until at least Mach 2013.

use that version then.
Title: Re: Tragic Lantern for EOS M
Post by: Iain1986 on June 14, 2013, 10:43:57 AM
Hi, not sure if this is the right place to post this but I was wondering, will Magic Latern allow the EOS M to now use Remote Capture functionality?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 14, 2013, 11:16:18 AM
Did some more tests about how much of the stair stepping effect is caused by the edge detection. I made a video with the old version, that has the af-dots and another with the current version, that has the edgedetection dots.
One problem with this test is, that it's recorded in different angles. So it may not be completely trustable. I'll redo the test with a tripod later.
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F1inv4vdjc0pjx49%2Fcompare_old_vs_new_version.png&hash=4cdac68e8ee2578f067bfcaf4d3ac9fc)
It seems that most of the distortion is caused by edge detection. At the top nearly perfect edges (with the old version) and at the bottom the extreme stair stepping effect with the current version. I hope and don't think that the difference is only caused by the different angle.
So, in contrast to what i believed and wrote a few days ago, if there is a way to record without edge detection and without af-dots, it may be possible to get really high quality video, also better in sharpness and detail than h.264.

Another thing that i realized while testing:
1. Booting camera in video mode isn't needed anymore to be able to load the module.
2. In fact it causes problems in the current version if you boot in video mode, since "Use photo mode" seems to be activated but isn't. So it has to be disabled and reenabled, to get raw recording work. @1%: That's the reason why i still had the bug with the current version. I still used the outdated flow to boot in videomode -> load module -> photo mode -> multishot nr -> activate raw video. Then "Use photo mode" seems to be enabled but isn't. boot in photo mode -> load module -> multishot nr -> activate raw video works great with current version.

@1%: Is there any chance at all, that there is a raw type or other setting that it's possible to get an image without af-dots and without edge detection? If yes, can i help anything to find it?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 14, 2013, 07:47:20 PM
I hope there is a way.. I guess you'd have to look at fw disassembly. should be no more use photo mode option, it should just do fake movie mode in photo mode.

I had no issues recording in either mode.. just video mode doesn't have enough buffer. I got it to unhack again so no more freezing/dead keys. AEWB disable causes AF to stop working, etc.

We have a new firmware coming, I hope some of these issues are addressed.. ie the dots, 30fps LV, etc.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 14, 2013, 08:44:42 PM
I hope there is a way.. I guess you'd have to look at fw disassembly. should be no more use photo mode option, it should just do fake movie mode in photo mode.

I had no issues recording in either mode.. just video mode doesn't have enough buffer. I got it to unhack again so no more freezing/dead keys. AEWB disable causes AF to stop working, etc.

We have a new firmware coming, I hope some of these issues are addressed.. ie the dots, 30fps LV, etc.

this is great! I'm looking forward to it. btw, I'm considering of selling my other 550D to get another EOS M, that way I hope I can test new fw from canon (I hope they'll release it soon)

I don't know if you noticed or not but, you can record 1728x512 @ 25fps on HDR (scene) and HandHeld Night Scene (scene) modes. records continuously at 38MB/s to sandisk extreme 45MB/s. build version : [EOSM] FixUnhack.zip from "otheronepercent"
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 15, 2013, 03:14:18 AM
Don't know if it is just me but I notice a visible better quality of video with the latest hack update with using the video button to record. Of course the frames that the buffer can handle have gone down by half on the same settings but the quality is certainly an improvement with the pink dots and all that stuff no more an issue.
Title: Re: Tragic Lantern for EOS M
Post by: gamentine on June 15, 2013, 06:14:50 AM
With the latest update, my EOS M does not have the 18-55mm lens lockup.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 15, 2013, 10:47:32 AM
@Canon eos m: What exactly do you do, that you don't get the stair stepping effect and edge detection dots at the edges? can you post an example image, for the quality you get?

@1%: is there any benefit of the movie mode? the edge detection seems to be also enabled in movie mode. and that's imho the only issue that stops raw video to be really used on the eos m. so waiting for the new firmware from canon, till there is a chance for any further progress?
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 15, 2013, 11:08:38 AM
Don't know if it is just me but I notice a visible better quality of video with the latest hack update with using the video button to record. Of course the frames that the buffer can handle have gone down by half on the same settings but the quality is certainly an improvement with the pink dots and all that stuff no more an issue.

I'm still using photo mode, at Manual with multiple frame noise reduce, and on HDR (scene mode) there are no AF dots and quality looks amazing after you resize 1.71 or 1.67, I like the latest build. it seems to work fine.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 15, 2013, 11:34:49 AM
@Canon eos m: What exactly do you do, that you don't get the stair stepping effect and edge detection dots at the edges? can you post an example image, for the quality you get?

@1%: is there any benefit of the movie mode? the edge detection seems to be also enabled in movie mode. and that's imho the only issue that stops raw video to be really used on the eos m. so waiting for the new firmware from canon, till there is a chance for any further progress?

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fth08.deviantart.net%2Ffs71%2FPRE%2Ff%2F2013%2F166%2F3%2F5%2Fdng001_00000_00362_00160_by_weraqs-d693wyy.jpg&hash=13e6e0748cd0ae21597854f1418b2a3f)
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 15, 2013, 12:26:44 PM
Will post picture tonight. Did nothing great - just used the new build on movie mode - instead on picture mode on the eos m. No dots and better rendition overall. Even the grey scale review on the eos m live view in replay looks less jerker than when recorded on the picture mode.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 15, 2013, 04:06:26 PM
Maybe placebo... if you have no sharp edges then no edge detection. Preview could work better but image should be pretty much the same.

I can't record much with those 2 buffer stars but use what works for you.

Handheld night is good: 95MB free. But expo override didn't work for some reason.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 15, 2013, 05:37:43 PM
Maybe placebo... if you have no sharp edges then no edge detection. Preview could work better but image should be pretty much the same.

I can't record much with those 2 buffer stars but use what works for you.

Handheld night is good: 95MB free. But expo override didn't work for some reason.

how about HDR mode, any override works?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 15, 2013, 05:57:27 PM
Didn't work for me. Dot problem might have a solution from 650D
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 15, 2013, 06:00:55 PM
Didn't work for me. Dot problem might have a solution from 650D

in my last tests I'm not getting any AF dots on frames, are there other kind a dots that I'm not aware of?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 15, 2013, 06:03:56 PM
This would kill dots without enabling af_raw and ruining sharp edges.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 15, 2013, 06:38:51 PM
do i understand it correct, that the solution from 650d might work for eos m to get best from both raw types? no dots and no edge detection? that would be great, hope there is soon a version to try.
btw with handheld night i still get the same 32+32+29 = 93, as with multishot nr. but few MB more or less don't make a difference anyway. and handheld night is also just available in photo mode. as long as you get continuous recording on maximum card speed, the benefit is some stability (but don't think few mb make a big difference) and some more frames when recording at a rate that exceeds your card (or controller) speed.
the bug with photo mode raw rec activation, when switching from video to photo mode is nearly fixed in the current version. but there are some combinations, that still cause problems, i'll make a video to demonstrate later. hope that helps to reproduce the bug.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 15, 2013, 07:11:33 PM
There is one bug I caught this morning that fake movie mode wasn't turning off. Maybe related to that.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 15, 2013, 07:59:43 PM
in addition to that bug, anyone experienced a problem with EOS M power-off? because when I turn off the camera, it still stays hot until I remove the battery.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 15, 2013, 08:08:06 PM
Weird.. I have been powering off and on and no drain or heat.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 15, 2013, 08:38:42 PM
mine maybe a faulty camera..
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 15, 2013, 08:41:06 PM
I wouldn't say that yet, maybe some setting or bug.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 15, 2013, 08:49:40 PM
@1% I'm testing [EOSM] BugfixNewSystem.zip

In photo mode: load modules -> nr -> enable raw (1600x544, 24 frames), camera turn off after 2 seconds of recording

Works fine with [EOSM] FixUnhack.zip and frame rate 24
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 15, 2013, 10:07:54 PM
I tested on 29MB/s card and it stops/runs out of buffer then unhacks. BTW, need to tweak timer A a little I think.. 510 is too low, screen goes black.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on June 15, 2013, 10:46:22 PM
Is there any option to automatically restart recording after 4GB? I tried "Movie restart' but it doesn't work.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 15, 2013, 10:50:34 PM
Is there any option to automatically restart recording after 4GB? I tried "Movie restart' but it doesn't work.

format your card as exfat, use cardtools to make it bootable, it can record over 4GB
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 16, 2013, 01:55:04 AM
I'm still using FixUnhack. The max at 23.976fps I can get is 2.35:1 1728x448 continuous. 1728x512 2:1 said it would work and worked for awhile but eventually stopped itself after maybe 2 minutes. This is on a Sandisk 45 MB/sec card.

A problem I am having now though is the files I got are 4.29 GB and raw2dng says they aren't valid. RAWMagic doesn't like them either. They add .R00 files when they go over 4GB. Am I missing something here
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 16, 2013, 02:11:18 AM
have you tried eyeframeconverter or batchelor ?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 16, 2013, 02:40:07 AM
Its supposed to split after 4gb on fat32 cards.
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 16, 2013, 04:23:51 AM
have you tried eyeframeconverter or batchelor ?

I'm on MAC
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on June 16, 2013, 05:33:38 AM
Edge artifacts aside, there is a shocking amount of dynamic range

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ffarm6.staticflickr.com%2F5530%2F9055470534_4fcb0187d8_b.jpg&hash=b0ab77459982abfcda50bcf553e0cb76)
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 16, 2013, 10:16:52 AM
Edge artifacts aside, there is a shocking amount of dynamic range

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ffarm6.staticflickr.com%2F5530%2F9055470534_4fcb0187d8_b.jpg&hash=b0ab77459982abfcda50bcf553e0cb76)

well, yeah, it is raw.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 16, 2013, 10:30:32 AM
i can confirm, that the edges seem to be much smoother. (Edit: edges are not smoother, was just the angle) but i still have small edge detection dots, which are much less disturbing than the unclean edges. looks nice already! have to do some videos and test around with postprocessing to check how good the dots can be removed in post and how disturbing they are. but i think this may be the first version were eos m raw video quality may be better than h.264 in all points.
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2Foccy37w9zjz8042%2Fclean_edges.png&hash=a56c8db98668362435372935a0838a41)
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 16, 2013, 10:45:58 AM
i can confirm, that the edges seem to be much smoother. but i still have small edge detection dots, which are much less disturbing than the unclean edges. looks nice already! have to do some videos and test around with postprocessing to check how good the dots can be removed in post and how disturbing they are. but i think this may be the first version were eos m raw video quality may be better than h.264 in all points.
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2Foccy37w9zjz8042%2Fclean_edges.png&hash=a56c8db98668362435372935a0838a41)

it was always better than h.264! what are you really comparing here? h264 is  50mbit/s RAW is 300mbit/s! just think about the amount of data!
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 16, 2013, 10:48:16 AM
I'm on MAC

I'm on PC, sorry. you can virtualize windows if you have mac PRO.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 16, 2013, 11:06:43 AM
the amount of data isn't a qualified factor for judging quality at all. the amount of data says nothing about the amount of information. and especially it doesn't say anything about the amount of useful information.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 16, 2013, 12:06:04 PM
the amount of data isn't a qualified factor for judging quality at all. the amount of data says nothing about the amount of information. and especially it doesn't say anything about the amount of useful information.

oh really, extract frames on h264 video and try editing them as RAW :) I'm waiting.

and to answer your further posts, please watch this then try to talk again about h.264

Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 16, 2013, 12:57:12 PM
i never said. that you can't get better quality with raw, i just said, that recording more data doesn't directly lead to better image quality. and the image quality of the raw video possible on eos m just wasn't better than h.264 so far, because of the distorted edges and the af-dots.

hurm, i'm still not completely sure about the edges in the current version. made a test with the table edge yesterday and got cleaner edges as in the test before. but today tested with a flower the edges wasn't really cleaner than with the "[EOSM] FixUnhack.zip"-Version.
have to do some more tests to see if the quality improved or just anything in the test went wrong.

i did the test with the table edge again and the stair step effect does seem to depend more on the angle than on the used version.
versions i used from top to bottom: [EOSM] BugfixNewSystem.zip, [EOSM] FixUnhack.zip, [EOSM] UsableRaw.zip
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2Fm3s422m5j7ouwii%2Fcompare2.png&hash=b1028e4886cd316d0436f0e511e7654c)

all 3 seem to have an identical amount of stair step effect. But it's not as strong as the bottom image of my last test and not as weak as on the top image:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F1inv4vdjc0pjx49%2Fcompare_old_vs_new_version.png&hash=4cdac68e8ee2578f067bfcaf4d3ac9fc)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 17, 2013, 01:34:46 AM
I've only had it 5d3 raw type, no af_raw or anything and af_raw. I guess next thing to try would be marking the "bad" pixels and doing it that way.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 17, 2013, 01:25:00 PM
well, I've tried all the combinations, permutations etc. but no luck for higher cache on EOS M. still recording good RAW video though. I'll record more tomorrow.
Title: Re: Tragic Lantern for EOS M
Post by: gamentine on June 18, 2013, 07:43:14 AM
Fiddling with the intervalometer and I have a question,

Is there a way to force the screen off while it takes pictures?
I have the intervalometer set to 10 seconds start at 30 seconds
powersave lcd and global draw off after 5 seconds

Canon menu lcd powersave at 15 seconds
and Canon power off at 5 minutes.

The lcd turns off after 5 seconds, and then powers up to take a picture, and repeats.
Title: Re: Tragic Lantern for EOS M
Post by: vstrglv on June 18, 2013, 09:05:42 AM
Quote from: gamentine link=topic=3648.msg51131#msg51131 date=
1371269690
Wit
h the latest update, my EOS M does not have the 18-55mm lens lockup.
Please upload your autoexec.bin and Modules dir somewhere. I got an error for updating
.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on June 18, 2013, 09:13:52 AM
gamentine: this was fixed a few days ago: the display turns on, takes the picture, then turns off right away. Image review should be off.

Can you upload a video?
Title: Re: Tragic Lantern for EOS M
Post by: vstrglv on June 18, 2013, 03:47:00 PM
Today ML for EOSM updated successfully on WIN7. Will test.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 18, 2013, 04:39:48 PM
I'll have to test the dot remover in the other thread an then maybe we can have no raw type or anything again and remove dots that way. Also might work to mark them bad in raw file since there is supposed to be a mechanism, raw2dng might take them out automatically then.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on June 18, 2013, 04:49:55 PM
Set them as 0 in the raw data, this means "bad pixel".
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 18, 2013, 04:56:50 PM
Yup, need to make the list like on 650D or just use 650D list because the sensors appear to be the same.
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on June 18, 2013, 11:18:55 PM
I am really enjoying HDR video right now w/ a ffmpeg + enfuse workflow. 720p/60hz with 3.5x CBR seems pretty stable and looks great IMO. I haven't worked out a workflow for raw yet, but the menu says 1152x400 will shoot continuous at 23MB/s at ~29.9FPS on my class 10 UHC 1 95MB/s card.

Overall this is totally usable and enjoyable, but ML menu shuts down randomly and canon LV sprites pop up while in ML menu, particularly the EV meter graphic.

I am very grateful for the work you guys have put into this. My HDR videos look phenomenal!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 18, 2013, 11:23:15 PM
Yea, the sprites draw on the menu sometimes. Canon really made this camera annoying.

Before the menu was disabled while recording even.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 19, 2013, 05:44:54 AM
anyway to keep ML menu open longer? it takes sometimes 3-5sec to go live-view, I'm no longer able to use screenshot for settings, using my other camera to capture the setting I'm recording on.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 19, 2013, 12:58:06 PM
noticed something yesterday, recovering from low-lights can be really noisy even at ISO100, have we changed anything on the code :\

RAW Frame

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ffc07.deviantart.net%2Ffs71%2Ff%2F2013%2F170%2Fc%2Fa%2Fdng007_000000_by_weraqs-d69p4kk.jpg&hash=30e7a82111130c211b95b124732214a5)

Result

Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 19, 2013, 02:24:46 PM
I think ML menu times out with the canon dialog, I'll have to check. Nothing changed in regard to noise... its all the camera.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 19, 2013, 03:28:24 PM
I see, I've tried both photo & video mode, its all noisy. try to capture scenes with more light from now on. thanks.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 19, 2013, 04:05:25 PM
Hi everyone!

So, I just got an EOS M and read this entire thread, but I got a bit confused. Basically, I want to try the latest ML for EOS-M.

I tried downloading the alpha 1 and overwrite some files from: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM]%20Check%20unsquee.zip

But the camera wouldn't recognize the .fir

I think I'm doing it wrong. Is the alpha 1 the latest ML? (if not where can I find it? It doesn't seem to be on the nightly, do I need to compile my own?)

Thanks in advance
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 19, 2013, 04:11:21 PM
Boot flag it with alpha 1 first to where that boots and then replace files.

So where do I mark the pixels as bad?

Code: [Select]
ifd1[BADPIXEL_OPCODE_INDEX].type &= ~T_SKIP;
        // Set CFAPattern value
        switch (camera_sensor.cfa_pattern)
        {
        case 0x02010100:
            badpixel_opcode[BADPIX_CFA_INDEX] = BE(1);              // BayerPhase = 1 (top left pixel is green in a green/red row)
            break;
        case 0x01020001:
            badpixel_opcode[BADPIX_CFA_INDEX] = BE(0);              // BayerPhase = 0 (top left pixel is red)
            break;
        case 0x01000201:
            badpixel_opcode[BADPIX_CFA_INDEX] = BE(3);              // BayerPhase = 3 (top left pixel is blue)
            break;
        case 0x00010102:
            badpixel_opcode[BADPIX_CFA_INDEX] = BE(2);              // BayerPhase = 2 (top left pixel is green in a green/blue row)
            break;
        }

Here?


Any way to get them by color instead of listing them all?


Also no bad pixels in zoom mode... I'll add an enter zoom mode button to force it.. but preview is missing display filter sync so its lacking.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on June 19, 2013, 04:52:21 PM
Any way to get them by color instead of listing them all?

That would be a really bad idea. Altough you can hack the bad pixels check to support it
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 19, 2013, 04:53:36 PM
Can anyone please tell me how to change the aperture directly from the camera when the camera is in M mode. Can only manage to change using the ML menu. Making me mad.

Is there any way to override the ML menu?

How do I get to record at 4000-8000 fps on the EOS M?

Responses appreciated.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on June 19, 2013, 05:11:07 PM
Press SET -> Turn wheel
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 19, 2013, 05:11:34 PM
Boot flag it with alpha 1 first to where that boots and then replace files.

Hmm... I think I did something stupid.

I used EOScard to bootflag the card, and copied Alpha 1 to it. Then I pop the card to my camera, and update firmware. It loads up and says it's bootflagged and I can turn off the camera. I turn it off, and it loads up just fine, but no ML. (two finger tapped)

I then copied the check unsquee.zip files in and my camera wouldn't power up now even with a different card. The green light blinks repeatedly. Any ideas on what to do?

Thanks in advance.


EDIT: Nevermind. It's back alive and running alpha 1! :D Thanks for the instructions
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 19, 2013, 08:00:49 PM
I don't know if you're following other threads like me or not but someone actually partitioned the buffer of 550D and made it capable of recording more frames with same resolution, here is the post;


To be honest :), I also thought, that the more buffers are better, even if the overall size isn't bigger, I don't know why I haven't tried so far: D, but here it is:

Some really quick test results here, on 550D with SanDisk ExtremePro 16GB, 1280x426 @ 24fps:

SortingBuffers                                               FramesSeconds
asc8Mb+31Mb+31Mb317~13
desc16Mb+16Mb+15Mb+15Mb+8Mb1326~55
asc8Mb+15Mb+15Mb+16Mb+16Mb1395~58
none15Mb+15Mb+16Mb+16Mb+8Mb1326~55

Try and let me know:
http://www.mediafire.com/download/rkq9kh63po8xxg4/ML_550D_Xaint.rar (http://www.mediafire.com/download/rkq9kh63po8xxg4/ML_550D_Xaint.rar)

Great findings by the way a1ex, I'm still experimenting with this, and with your speedsym.py script.. looks like it worth the try :) thanks!



EDIT (9 x 8Mb):

SortingBuffers                                                                         FramesSeconds
-8Mb+8Mb+8Mb+8Mb+8Mb+8Mb+8Mb+8Mb+8Mb1565~65

do you think it is possible on EOS M?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 19, 2013, 11:19:56 PM
I already sort the buffers... I dunno how he cut them up, will check. I think it works opposite for us, larger is better, but needs more testing.

If I can split them up I'll try some diff configs.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 20, 2013, 12:16:50 AM
@%1, according to your post about 50D, maybe it fell on EOS M too. worth to try though.
Title: Re: Tragic Lantern for EOS M
Post by: GizmoWu on June 20, 2013, 03:38:15 AM
I just bought the EOS M and looking forward to some great hacks on this. I have ML and donated for usage on my 550D in the past and loved it.

I wonder if there will be hack to increase the autobracketing feature from 3 frames up to 5 or 7?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 20, 2013, 03:49:28 AM
I have to look, the setup is probably different.

Heh, its not.. dunno what it will do to LV only camera... but don't hold your breath.. .6D max is only 41MB/s.. you at best get a few MB.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 20, 2013, 04:04:40 AM
Hey guize! :D

Canon Korea posted some videos of the Firmware 2.0.2. The firmware can be downloaded if you're registered with Canon Korea.

http://www.canonwatch.com/more-canon-eos-m-firmware-2-0-2-test-clips/

http://www.canonwatch.com/canon-eos-m-firmware-version-2-0-in-action-videos/
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 20, 2013, 04:14:04 AM
Did they fix the 720P crap lv?
Title: Re: Tragic Lantern for EOS M
Post by: GizmoWu on June 20, 2013, 05:22:37 AM
Hey guize! :D

Canon Korea posted some videos of the Firmware 2.0.2. The firmware can be downloaded if you're registered with Canon Korea.

http://www.canonwatch.com/more-canon-eos-m-firmware-2-0-2-test-clips/

http://www.canonwatch.com/canon-eos-m-firmware-version-2-0-in-action-videos/

Hey feureau,

I went to the website but don't speak Korean. Do you have a copy you can share? Would love to have this before I go on my trip this weekend. Thanks.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 20, 2013, 05:43:35 AM
I'm not in Korea and I don't speak korean.

I clicked around but I can't seem to get to the firmware download page. It's supposed to be in here somewhere: http://support-kr.canon-ci.co.kr/

All I know is the filename: C3319920.FIR

Any korean EOS-M user around?
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 20, 2013, 11:16:19 AM
I've just checked the whole site and they removed the firmware, if you have can you upload to some file sharing site?

btw there is a blog http://canonblogs.com/1268
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 20, 2013, 03:17:24 PM
That's too bad. I didn't find/have the file either. :(

Did the blogger managed to get the file?
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 20, 2013, 03:45:46 PM
That's too bad. I didn't find/have the file either. :(

Did the blogger managed to get the file?

I think so because there are a lot of videos on youtube http://www.youtube.com/user/theCHZy/videos

I'll ask them later.
Title: Re: Tragic Lantern for EOS M
Post by: GizmoWu on June 20, 2013, 04:21:54 PM
I followed the instructions on the Korean website and the firmware page popped up but however, no M firmware listed. :(

If anyone gets a copy, please share. I will do the same.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 21, 2013, 12:07:48 PM
%1, will u release an update for eos m about new mem hack? because I'm getting much much more frames on 550D with latest hack. I don't know how to adjust that buffer. especially alex'.
Title: Re: Tragic Lantern for EOS M
Post by: alexgloss on June 21, 2013, 12:37:30 PM
The new firmware 2.0.2 will be released on Thursday 27th of June 2013.
This information is from the japanese homepage

http://cweb.canon.jp/eos/lineup/m/info/news/index.html

The new lens EF-M 11-22mm F4-5.6 IS STM will be available end of July 2013.

Greetings from Germany

Alex (EOS 30D and EOS M user)
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 21, 2013, 01:44:39 PM
The new firmware 2.0.2 will be released on Thursday 27th of June 2013.
This information is from the japanese homepage

http://cweb.canon.jp/eos/lineup/m/info/news/index.html

The new lens EF-M 11-22mm F4-5.6 IS STM will be available end of July 2013.

Greetings from Germany

Alex (EOS 30D and EOS M user)

thanks for the update.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 21, 2013, 04:25:56 PM
I'm able to record 1728x736@30 for 430 frames with 6D's raw_rec.mo to Sandisk Extreme 45MB/s on EOS M.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 21, 2013, 05:56:22 PM
Can anyone confirm if this crashes your EOS M:

1. Turn on camera

2. set to photo mode (central switch on the shutter button)

3. switch to HDR Backlight control

4. Take HDR pic

5. switch to Av mode.

6. go to menu > creative filters (fifth tab from the left (first blue tab), second option from the bottom)

7. hit set

8. make sure grainy B/W is selected.

9. hit set.

10. EOS M locks up or you get an ML crash display.

Remove battery to unlock.

EDIT: Apparently simply applying creative filter after the fact crashes my EOS M with ML.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 21, 2013, 05:57:59 PM
I'm able to record 1728x736@30 for 430 frames with 6D's raw_rec.mo to Sandisk Extreme 45MB/s on EOS M.

That's some good numbers. Is it still squeezed?
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 21, 2013, 06:14:19 PM
That's some good numbers. Is it still squeezed?

no, corrected image size, I like the results, but still I hate the aliasing on EOS M.. Using 550D for RAW, M for HDR video only.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 21, 2013, 07:17:39 PM
Ooh! Neat! I should try that out. Thanks for the find.
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 21, 2013, 07:32:13 PM
almost no difference at all with 550D's new RAW recording module on EOS M with 6D's RAW recording module

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ffc07.deviantart.net%2Ffs70%2Ff%2F2013%2F172%2F2%2Fb%2Fvram1_21_by_weraqs-d6a0p04.jpg&hash=c94145846164b7e425d98e997141f9f6)

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ffc08.deviantart.net%2Ffs71%2Ff%2F2013%2F172%2Fe%2F2%2F212_by_weraqs-d6a0p2g.jpg&hash=5a12021581f21a701d4ee1599446b6ea)

I put both modules on the card and can start them one from movie rec key, another with menu button. don't have to replace card or rename files, only problem is, you have to keep track of files. otherwise you don't remember which one you've used to record :)
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 21, 2013, 09:05:43 PM
no, corrected image size, I like the results, but still I hate the aliasing on EOS M.. Using 550D for RAW, M for HDR video only.

You are right the M is good for HDR but cannot handle RAW video.
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on June 21, 2013, 10:46:43 PM
Hey yall,

I'm using HDR a lot, also. I think it looks great, but I'm getting occasional flickering w/ 720p 60hz HDR. I'm not sure if its my script. Are you guys using the wine/windows workflow? Are you guys experiencing flickering (some bright frames, some dim)

My workflow
Code: [Select]
#!/bin/bash
for q in $(ls *.MOV); do
rm -rf audio.mp3
#mv video.avi video.`date "+%d.%m.%y-%H.%M"`.avi
rm -rf png1/
rm -rf png2/
rm -rf output/
mkdir png1/
mkdir png2/
set -e
ffmpeg -r 59.94 -i ${q} -filter:v select="not(mod(n\,2))",setpts="N/(59.94*TB)" png2/%06d.png
ffmpeg -r 59.94 -i ${q} -filter:v select="not(mod(n-1\,2))",setpts="N/(59.94*TB)" png1/%06d.png
mkdir output/
cnt=0;
cd png1/
for f in $(ls *.png); do
    echo $f "(+)" ../png2/${f} "=>" ../merged${f}; 
    #wine ../enfuse/enfuse -o C${f:1} $f ${f:1};
    #enfuse -m 6000 -o ../merged${f} $f ../2/${f};   
      let cnt=cnt+1;
  if [ $cnt -eq 1 ];
    then echo One $f;
    enfuse -m 6000 -o ../output/merged${f} $f ../png2/${f}>>log1&                                 
  fi;
    if [ $cnt -eq 2 ];
    then echo Two $f;
    enfuse -m 6000 -o ../output/merged${f} $f ../png2/${f}>>log2&               
  fi;
    if [ $cnt -eq 3 ];
    then echo Three $f;
    enfuse -m 6000 -o ../output/merged${f} $f ../png2/${f}>>log3&                                   
  fi;
    if [ $cnt -eq 4 ];
    then echo Four $f;
    enfuse -m 6000 -o ../output/merged${f} $f ../png2/${f}>>log4&                                   
  fi;
    if [ $cnt -eq 5 ];
    then echo Five $f;
    enfuse -m 6000 -o ../output/merged${f} $f ../png2/${f}>>log5&                                   
  fi;
      if [ $cnt -eq 6 ];
    then echo Six $f;
    enfuse -m 6000 -o ../output/merged${f} $f ../png2/${f}>>log6&                                   
  fi;
    if [ $cnt -eq 7 ];
    then echo Seven $f;
     enfuse -m 6000 -o ../output/merged${f} $f ../png2/${f}>>log7             
    cnt=0;                         
  fi;
done
ffmpeg -i ../${q} -vn -ar 44100 -ac 2 -ab 192k -f mp3 ../audio.mp3
#ffmpeg  -i ../audio.mp3 -r 29.97 -f image2 -i ../output/merged%06d.png -r 29.97 -acodec ac3 -vcodec mpeg4 -vb 80M  -qp 0 ../video.avi
#ffmpeg  -i ../audio.mp3 -r 29.97 -f image2 -i ../output/merged%06d.png -r 29.97 -c:a ac3 -c:v libx264 -pix_fmt yuv720p -preset ultrafast -qp 0 ../video.avi
ffmpeg  -i ../audio.mp3 -r 29.97 -f image2 -i ../output/merged%06d.png -r 29.97 -c:a ac3 -c:v libx264 -pix_fmt yuv420p -preset veryslow -qp 15 ../${q}.avi
cd ..
mv $q converted/
done
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 21, 2013, 11:18:55 PM
I'm using just vegas pro for HDR videos, works like a charm on 720p videos, at 1080p it is really hard to make it work with my GPU.

capture a HDR scene 720p fps override (exact 60) then drag the video to vegas pro, adjust composition settings as 720p30, then hit render, if you want to make color adjustments just use the tools. here are some examples created with vegas pro and with after effects;


took almost a month to render this short clip.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 22, 2013, 01:20:05 AM
Heheh.. I guess we'll see what happens with the dialog hack.

Yea... I dunno if any better for EOSM

http://www.qfpost.com/file/d?g=gyGwDYIUQ (http://www.qfpost.com/file/d?g=gyGwDYIUQ)
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 22, 2013, 01:41:07 AM
Heheh.. I guess we'll see what happens with the dialog hack.

I don't get it?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 22, 2013, 01:59:15 AM
Dialog timer hack gave 50D like 10 extra MB/s
Title: Re: Tragic Lantern for EOS M
Post by: qsara on June 22, 2013, 02:19:47 AM
well, just tried,

23,976fps

1728x564 = 1728x934 464 frames
1728x586 = 1728x972 280 frames

my old combination of 6D & 550D with M's firmware

6D      1728x576 = 1728x961 324 frames
550D   1728x576 = 1728x991 376 frames

works fine but seems a bit late on flushing buffer to the card, maybe card gets older. as a1ex said, some cards must die in the name of science :)
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on June 22, 2013, 05:41:10 AM
I'm using just vegas pro for HDR videos, works like a charm on 720p videos, at 1080p it is really hard to make it work with my GPU.

Very nice, qsara! Can I ask what CBR you are using? Is there a way to tell if i'm losing frames due to increased bitrate?
Thanks for sharing
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 22, 2013, 03:32:02 PM
Hi it's very exciting to see the ml firmware for eos m. Just wondering if we can add screen off function in the next update for the 2.0 version firmware. The eos m currently doesn't provide evf but I would like to use a ovf for my 22mm and 50 mm lens. Therefore a screen off function would be very useful. Maybe we can make it by long pressing the info button.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 22, 2013, 04:45:04 PM
BTW, the crash log from the creative filter crash:

Code: [Select]
ASSERT: IsSuiteSignature( hSuite )
at ./PackMemory/PackMem.c:577, task InnerDevelopMgr
lv:0 mode:2


Magic Lantern version : v2.3.NEXT.2013Jun15.EOSM106
Mercurial changeset   : 57cd362ac2f5 (unified) tip
Built on 2013-06-15 17:17:36 by user@D610.
Free Memory  : 247K + 2024K
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 22, 2013, 07:37:55 PM
Ok, will have to check on this and see why... looks like a memory issue.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 22, 2013, 09:25:12 PM
Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 22, 2013, 10:09:55 PM
oh, nice... i tested the latest version and now it's possible to write 36-37mb/s in videomode (without multishot nr), too.
any progress on the dot removal?

if there are linux users, we may discuss the used workflows. what i do is Raw2Dng via wine => convert dng to exr via darktable cli => unsqueeze exr with imagemagick mogrify => open exr in darktable for postprocessing => export to jpeg => import to video software.
i wrote a simple bash script for the first 3 steps to get unsqueezed exr frames from raw with a single command.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 23, 2013, 12:12:39 AM
Hi I am using the ML firmware for my EOS M with the FD 50mm f1.4 len. It's really a great tool for manual focusing. But I am wondering whether I can disable the addition information display on the shooting mode and just show the peak focusing? I think the stock display of Canon is already enough and the ML display will cover those Canon display and settings.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 23, 2013, 12:13:57 AM
oh, nice... i tested the latest version and now it's possible to write 36-37mb/s in videomode (without multishot nr), too.
any progress on the dot removal?

if there are linux users, we may discuss the used workflows. what i do is Raw2Dng via wine => convert dng to exr via darktable cli => unsqueeze exr with imagemagick mogrify => open exr in darktable for postprocessing => export to jpeg => import to video software.
i wrote a simple bash script for the first 3 steps to get unsqueezed exr frames from raw with a single command.

Do you mean the latest ML alpha firmware for EOS M? I only find one in the OP~
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 23, 2013, 12:34:22 AM
I think for dot removal we need to take both sizes and edit the 650D dot remover... unless someone knows how to add them to chdk-dng.c correctly.

Its on the list along with enabling actual shutters in eosM.. the ones right now aren't correct (not using shutter_timer.)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 23, 2013, 01:50:01 AM
i tested how to get the dot positions, it's not perfect, but this is the result so far:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F9dp7bn71vdvdnhd%2F000000-hdr.png&hash=9c0e9d7f05889dfd3fbcaf56dabcd1b3)
it's a mask for 1600x542 (16:9)
i used this image as base, maybe anyone can find better settings to seperate noise from the dots.
http://dl.dropbox.com/s/mow4swn06j3ojck/000000-hdr.dng

to generate the image i recorded ~180 completely underexposed frames with 100 iso, then combined all to a hdr image to eliminate the noise. maybe i should try more frames to get even better seperation of frames to the noise. i've to check what you exactly have in the dng and how to mask the images with the result. do you have and documentation about what's exactly in the dng container?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 23, 2013, 02:18:16 AM
Try silent pic of the whole thing in normal and zoom (shouldn't have them, but check). They shouldn't change based on what you crop from the image.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 23, 2013, 03:19:23 AM
oh, that's correct, if we've the data for the maximum resolutions, we can just crop on the center for the resolution we need.

EDIT: played a bit around with the dotremover sourcecode (the logging lib dependency was missing -.- ) and tested the data from the png i posted above. it's not perfect so far but removes most of the dots. i've to check how to improve the removal data. i wrote a pm to foorgol and asked him to put the source into a repository. maybe he can also give me some tipps on how to improve the removal data.

Before:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F6vp6rhld9haj5i2%2Fbefore_dot_removal.jpg&hash=faafb40ded8283bc84d002d380a67120)

After:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F5ysu6oz4zpqgn7a%2Fdots_removed.jpg&hash=f2dc61099abe3827dd42710cb79e955d)


EDIT: updated the example images. in this images the dots are much better visible. marking the dots as dead pixels doesn't work for me. when i use this setting i get black pixels (what does make sense, if it's set to 0). are you sure, that setting it to 0 is the correct way? i don't know anything about dng, but the "FixBadPixelsList" in the specification looks more complex than just setting a pixel to 0.

EDIT: optimized the data which pixels have to be removed and updated the example images. the data is now for 1734x695 silent dng. this should work (with correct pixel offset) for all non zoomed video resolutions. the dot remover app has to be modified, that it handles the offsets correct for all resolutions. and there should be a setting to seperate eos m from 650d. i don't want to modify to much, till there is a repository. it would just be hard to merge the source together, without a version control system.
i think the data should work better than the result is, but the way the interpolation works isn't perfect so far. have to discuss that with foorgol, as soon as he responds to my pm.

EDIT: used the 1734x695 removal data for an 1600x542 image and it worked just fine. the correct offset for x is 70 and for y 76. i don't calculate them automatically so far. have to check how the center crop has to be caculated, becuse it's not completly in the center, but shifted few pixels because of the bayer pattern.

Before:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2Flrvrlvry5asjhxi%2Fbefore_dot_removal_1600.jpg&hash=a0e4d1a895405ed60087d2f20e88c247)
After:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2Fbj8jnzl2sf987l2%2Fdots_removed_1600.jpg&hash=961900d6e4edfa0bb53875e72b505f5b)

EDIT: i asked in the dt irc how that dng setting to 0 stuff works and why those pixels are black in dt. if i understand it correct the FixBadPixelsConstant is set to 0 in the dngs generated by ml. that's why setting to 0 marks them as bad pixels.
dt doesn't seem to support dng 1.3.0.0, that's why the pixels are black.

EDIT: 1% can you explain me, why center crop of 1600 doesn't start at pixel (1734-1600)/2 = 67, but at 70? 68 would make sense for me , because maybe it should be even because of the bayer pattern. but i don't know why it should be 70. in the ml source there is some other stuff in the calulation like raw_info.active_area.x1. don't know what that exactly does. can you tell me how to reliably calculate the offset. is this possible with just the image size or do we need some additional information?

EDIT: did a small videotest.
http://dl.dropboxusercontent.com/s/lincex5op3relr7/dotremoval.mp4
- first is h.264
- secound is raw
- third is based on the same data as the secound but with dot removal

EDIT: one more question. is there any information in the header from wich camera the dng is? if not, may it be possible to add it?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 24, 2013, 05:43:49 PM
Header should say EOSM.. it does for 6D/5d3. Also don't forget frame skips... probably why coordinates are off.

[EOSM] Raw TypeTest.zip
https://mega.co.nz/#!o94RTLQZ!FHLUZkjExsOTg7_Rc8foRCJHEVMd1nHZ3Olt9j0I8Fs

Have another chance at raw types I was off by 0x4. See if any of them don't damage edges + have no dots/other defects.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 24, 2013, 06:02:59 PM
how do skipped frames change the crop offset of non skipped frames?
can you write me why exactly from the maximum resolution 1734x695 the horizontal offset is 70. 70px border 1600px image 64px border. how is it exactly calulated?

new raw type doesn't work well... i get edge detection and focus dots on this one. but... if there is one with edge detection, one with focus dots and one with both, maybe there is also one with none ;)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 24, 2013, 06:05:41 PM
You should get 100 of them to check. Test is on don't click me.

I think its total size - skips. So if you do raw video its a crop of that and relative to center?
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 24, 2013, 07:05:18 PM
BTW, the crash log from the creative filter crash:

Code: [Select]
ASSERT: IsSuiteSignature( hSuite )
at ./PackMemory/PackMem.c:577, task InnerDevelopMgr
lv:0 mode:2


Magic Lantern version : v2.3.NEXT.2013Jun15.EOSM106
Mercurial changeset   : 57cd362ac2f5 (unified) tip
Built on 2013-06-15 17:17:36 by user@D610.
Free Memory  : 247K + 2024K

OMG! Where can I download the June 15 version? Please tell me the address.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 24, 2013, 07:23:55 PM
ah, ok, i checked all the 100 images. 81 were completly distorted.
from the 19 remaining:
4 had af dots all over the image. we've to check if this will lead to better or worse quality after removal. the difference is, that the af pixels are just red and blue pixels instead of the other type, were most of them were on the green pixels. on the one hand bayer has already a lot more green than red and blue pixels, but on the other hand the green are more significant for the human vision. i'll make a test, which leads to better results after dot removal.
13 had center af points (and some additional edge detection)
the 2 remaining (20 and 84) do have edge detection dots...

i still don't understand why a skipped frame should move the crop position. and the offset is also not completely centered without any skipped frames. i'll check if it's always just 2 pixels more to the right, or if it varies from resolution to resolution.
as soon as i have a working version for all resolutions i'll upload it.

@haomuch:
you find nearly all versions at https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/
just the version from 22. june (which is imho best so far) isn't there... but you can find that at:
http://www.qfpost.com/file/d?g=gyGwDYIUQ
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 24, 2013, 07:34:00 PM

@haomuch:
you find nearly all versions at https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/
just the version from 22. june (which is imho best so far) isn't there... but you can find that at:
http://www.qfpost.com/file/d?g=gyGwDYIUQ

Thanks for that links very much. But as I found out they are like patches instead of a whole fireware file. Could you tell me how can I use them?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 24, 2013, 07:51:05 PM
Do you have ML (from the first post in this thread) already installed?
Then just extract the ZIP of the update and copy the autoexec.bin to the root of your sd-card (overwrite the existing one).
Then copy the MODULES directory into the ML directory on your sd-card. If there is not a "SETTINGS" directory in your ML directory you may create one (you don't have to, but it will show a warning if it isn't there).
Turn your camera on (in movie mode) tap with both fingers on the screen to get into ml menu. switch to the "M" tab (last tab).  select "Load modules now..." you should see some green dots in front of each module listed below after that.
switch to video tab and activate raw video. there are some things you should know:
1. you can use fps override to record less than 30fps and get continuous recording on higher resolutions
2. 1600x542 is imho highest resolution for continuous recording
3. you can switch to photo mode and activate multishot nr to get larger buffer (more recording time with resolutions that are to high for continuous recording). if you do that you've to use menu key to start recording. set first multishot nr and then activate raw video and configure the options to use menu key to start recording. and you may have to use expo override to get correct exposure (i think you still have to).
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 24, 2013, 08:02:54 PM
Thanks for that explanation, very clear now
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 24, 2013, 08:26:39 PM
P.S. all creative filters crash for me... but why in the world would you use these... I think actually need to find the regs they use and have them real time for H264 if possible.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 25, 2013, 09:46:43 AM
1%: The camera model header information in the dng isn't correct. EOS-M says "Canikon" for both, the silent dng and the dng converted from raw video. 650d says "Canikon" for dng converted from raw video and the correct model for silent dngs.
Can you check if it's possible to get always the correct model name?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 25, 2013, 07:17:46 PM
Will have to look... plus all our raw types seem to have the dots.. I looked through the 100 DNG and everything was F'd.
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on June 26, 2013, 04:35:47 PM
Hi - thanks for working hard on the EOS M which acts very good together with my 600d. :D
Will there be audio funktions too, like external/internal mic and audio out for example? Do you have any idea when the next official ML Version incl EOS M will be available?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 26, 2013, 04:48:19 PM
Beeping/wav caused lockups... dunno about other functions yet, should have the same chip as 650D but not reading/writing registers correctly yet. At the least hope to find monitoring.

Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 27, 2013, 02:19:26 AM
@1%: forgool created a repository for the pink dot removal tool at https://github.com/Foorgol/PinkDotRemover
i made a pull request for the eos m dot removal data. only the resolutions 1734x695 and 1600x542 are working so far, we still discuss how to support all resolutions without defining the data for each seperatly.
that all the 100 DNGs have any kind of distortion is what i already wrote some posts above. but i still think that it may worth to give the raw type with the dots all over the image, but only on red and blue pixels, a chance. can you upload me a version with that raw type enabled? oh... for that raw type the name PinkDotRemover wasn't the best choice ;)
any news about the model name in the dng header? would be nice if it wouldn't be necessary to choose the model from a dropdown in the dot removal tool.
Title: Re: Tragic Lantern for EOS M
Post by: jimijam on June 27, 2013, 04:25:23 AM
The new EOS-M Firmware is now out ! (http://www.usa.canon.com/cusa/consumer/products/cameras/slr_cameras/eos_m_ef_m_22mm_stm_kit?selectedName=DriversAndSoftware)

Can someone(?) confirm if there'll be any risk installing this new Canon FW directly onto a camera that has ML on it? Do I need to uninstall ML first, or will the new firmware wipe it out (safely) during the upgrade?

Thanks

EDIT:
Flash went OK but you'll need to nuke your card that has ML on it (I used a 2nd blank card).
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 27, 2013, 04:39:07 AM
Well it will keep the boot flag which is good... but you should make your card not bootable and be aware there is no update for ML yet. I don't know if there is an older firmware to downgrade with either.
Title: Re: Tragic Lantern for EOS M
Post by: jimijam on June 27, 2013, 04:46:54 AM
^^ yup looks like the boot flag is still set and your card with ML on it won't work, but the camera's fine.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 27, 2013, 10:26:32 AM
oh, i checked again and silent dng does say "Canon EOS M" in meta... but not dngs generated from raw video. don't know if it's missing in the raw video information, or if raw2dng does just ignore it.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 27, 2013, 07:25:13 PM
I fixed this today.. .I think it needed some config function set. Didn't seem to be writing otherwise. Dunno if it will show in movie.

But... aparently eos M has a 120fps path and some other debug functions I'm trying now.
Title: Re: Tragic Lantern for EOS M
Post by: hpi on June 27, 2013, 07:37:33 PM
look forward to Magic Lantern update for EOS M 2.0.2 firmware  :) :) :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 27, 2013, 07:53:26 PM
That has to be decrypted/decompiled first. Hopefully soonish.

I'm able to use 60fps in photo mode LV.

I have enabled full time crop mode in EOS-M.. 24fps native.. no more stupidity. Raw image is full sized too. Only 55M tho... fuck.

Also... guess where the fun starts... if you do this while in a bad mode.. ie photo mode or 1080p you fuck the camera and have to clear all settings.


The dots are MUCH tinier in this mode.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 27, 2013, 09:01:35 PM
Wait, are you saying you can record at 60fps in photo mode?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 27, 2013, 09:04:09 PM
Yea.. but raw only and write speed is you know... but I can also record full sized raw 24p in video mode now. It needs more help so you don't have to clear your settings and something broke MZ so I have to fix it.

No more squish either.. just limited by write speed. Still no display filters even @ native 24P tho... I need to find something else to sync to.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 27, 2013, 09:25:27 PM
so it doesn't has to be streched vertically anymore? more vertical resolution should decrease stair step effect at the edges, which would be really nice.

what do you mean with dots are much tinier? each dot consisted of 2 af pixels. is it now just 1 pixel?
when can we expect a version to test?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 27, 2013, 09:48:25 PM
Heh, you can have it now but fire it in the wrong mode and you'll be clearing all settings and booting to black screen in movie.


Hit don't click me.. but NEVER in photo mode or 720P60...
only in

1080P24/30/640P

tap around in black "regular" info > where it says movie size > where all the settings would normally be to get back into a regular mode.

it stays through reboots and if you enable it in an unsupported mode you will lose all camera settings + will not be able to boot in movie mode until clearing

[EOSM] MZ is broken.zip
https://mega.co.nz/#!QtBSUI5Z!QHUh7hjaWIgxNbxskcKsk0HQMAkwPsZVXxYlsazsEZU

yes, big text for a reason
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 27, 2013, 10:23:42 PM
lol...
it does stay through reboot even if it's correct enabled in 1080p? have to check what "tap around in black "regular" info" may mean before i try it. do i have to hit any special option, or is the tapping in the regular info what does the trick? and it shouldn't to any permanent harm, should it? losing settings is just what i expect that it could happen while using (pre-)alpha stuff.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 27, 2013, 10:55:29 PM
No, its a normal function.

You know where you select video mode normally, that is the same place you reset it. Options aren't visible but if you tap they are there.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 27, 2013, 11:16:02 PM
don't know if i did it correct, but i saw the menu...
i think the mode was correct, since it was slightly zoomed after "don't click" and the option to select movie size in "info" just said 1920x1080 30p and there wasn't the multiple options, which are normally there. after turning the wheel in the menu they reappeared and i could select a normal mode.
have to check the results...
EDIT: result isn't sqeezed, so i think i was in the correct mode. have to do more tests about the dots and quality, since it's quite dark at the moment i had to much noise to check the quality. it does seem to have a totally different dot pattern Oo

at least on black there doesn't seem to be any dot's at all. i created the dot pattern with a hdr of multiple images to get rid of the noise. with this build i don't see any dots with 280 combined dngs at all. with the old build they were more than clearly visible. have to check on white next.

it does have dots on bright areas, but totally different pattern than before. i'm going to create a pattern config to remove the dots with the dot removal tool.
edges look very clean so far, but hard to judge without a useable light source. but i think they are clean.... i'll do a direct comparison later.
that it's more cropped sucks a bit, but seems less zoomed than with the 5x zoom before. and it's great that it doesn't have to be unsqueezed.
still didn't got any black menu...
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 27, 2013, 11:46:21 PM
Yup, thats it. Kills the zoom tho. wont be a problem if there is some way to sync and have MZ.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 27, 2013, 11:52:27 PM
zoom (or MZ) would be nice, but focus peaking works, which should do the job most of the time.
really fantastic work 1%! can't wait to do some test shots tomorrow, to compare the current quality to h.264. already lost the hope that eos m may get better quality with raw than with h.264 ;)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 28, 2013, 12:03:13 AM
This is the mode we should have had from the start tho.. Also have to do something with 60fps LV. If I figure out the 120 it will be great tho.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 28, 2013, 12:06:05 AM
the extra crop is the most annyoing thing i think... it's just more than the complete zoom range of the 18-55mm kit lense. -.-
it's would be hard to record anything nearly wide angle in this mode.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 28, 2013, 12:12:13 AM
Didn't notice it till I played the files back. Need to see how its doing what its doing.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 28, 2013, 12:24:19 AM
it's hard to do a correct comparison, because of the different field of view. since the edge of the table is captured in different angles it doesn't allow to judge about the stair step effect. but in all tests i did i hadn't seen any problems at the edges.
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2Fyi0r2fy38ww60ih%2Foldvsnew.png&hash=c57d883edab16c179c70b3e37def18ba)
both images are upscaled to 1920x1080 and 100% crops. it seems that the new version doesn't have any distortion beside the dots. edges look very clean, no strange color or aliasing effects. but it also seems to be a bit softer.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 28, 2013, 06:50:50 AM
Whoah! Amazing development, 1% :D

Btw, has anyone ever investigated plugging the raw feed to the h.264 encoder? (if that is even possible) Perhaps we could get 60fps and less-soft video that way?
Title: Re: Tragic Lantern for EOS M
Post by: poeticdragon on June 28, 2013, 07:15:45 AM
Hi guys, I am new to ML specifically I came here looking for some help with my EOS M. This is a really long topic (22 pages currently) so I'm sorry if this has already been covered. Will this software allow me to completely disable LCD auto off or will it enable LiveView for my EOS M?

I am trying to send live video from my camera to my computer and from there out into the wilds of the Internet. I have discovered to my chagrin that the EOS M does not have Remove LiveView like my larger Canon DSLR camera has. However, the HDMI output shows some promise, until the LCD auto off proved to be another stumbling block. It will stream for a maximum of 30 minutes before turning off the display/HDMI even though the camera is still on and its plugged into an AC adapter.

* I would like to enable LiveView for the camera and use it as a virtual webcam with a program like SparkoCam or
* I would like to be able to stream indefinitely through an HDMI capture device hooked up to my laptop and do the same or
* I would like to find another solution that will let me stream video for more than 30 minutes

If this software can help me in my endeavor I'd greatly appreciate the info.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 28, 2013, 10:24:38 AM
just to show how much it is cropped:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropbox.com%2Fs%2Fegkc9jxrsdfrc0u%2Fcropfactor.jpg&hash=426bf8f2a62fa4b1eb9817029c69cc67)

the image is a h.264 frame and the red framed part is a downsized (to match scale) raw frame with same focal length and distance.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 28, 2013, 02:34:39 PM
it's hard to do a correct comparison, because of the different field of view. since the edge of the table is captured in different angles it doesn't allow to judge about the stair step effect. but in all tests i did i hadn't seen any problems at the edges.
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2Fyi0r2fy38ww60ih%2Foldvsnew.png&hash=c57d883edab16c179c70b3e37def18ba)
both images are upscaled to 1920x1080 and 100% crops. it seems that the new version doesn't have any distortion beside the dots. edges look very clean, no strange color or aliasing effects. but it also seems to be a bit softer.

I agree with Mixer2. The dots are smaller and no distortion seen at the fringes. I shot RAW 1600X542 using photo mode for more buffer range. Then expanded the reso to 1600X900 on AECS6. Landed up with some very workable video.

Uploaded on YouTube:
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 28, 2013, 02:58:01 PM
it says: "This video is private."

oh and the dots are not really smaller... the dots that appeared larger where 2 neighboring af pixels. in the old mode some lines and rows got dropped to scale it down. now it's not scaled down but cropped, so the lines between the pixels that were dropped are now still there which leads to some space between the two pixels.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 28, 2013, 03:06:04 PM
You can record h264 with the crop too.. but whoa thats a zoooooom.

I should try this with 200MM and see how far it will reach.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 28, 2013, 04:18:44 PM
more interessting is, if we can get raw without the crop and with clean edges. but i think no crop = unclean edges, since the downscaling via skipping lines seems to be the reason.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 28, 2013, 04:38:55 PM
Normal LV is pretty much 720P60 cut to 30fps.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 28, 2013, 05:54:48 PM
Hi guys I just updated to the 2.0.2 firmware yesterday an the AF speed now is really fast! Therefore I have lost the ML functions, which is a pitty. However I then realized that I can't use the eye-fi card that I bought days ago on the camera anymore since the bootflag have been changed. And I also can't do a uninstall by apply the ML firmware upgrade. Could anyone tell me what to do now? Thanks very much!
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 28, 2013, 05:57:03 PM
Could anyone tell me what to do now? Thanks very much!

Format the eye-fi card. (low level format)

Then wait for Greater Intelligence to port ML to EOS M 2.0.2
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 28, 2013, 06:02:59 PM
I think you can bootflag most of the eyefi cards. They work on 600D, why not here?
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on June 28, 2013, 08:15:09 PM
Dear Great Intelligencies (nice one, feureau) and stuff,

So, about that 18-55mm shutter bug. I was finally able to reproduce it while trying to take a pciture with ML installed with one of the most recent autoexec.bins. Basically you hit the shutter release, the camera focuses, the rectangle turns green, but then nothing happens and your friends get really annoyed with you. In order to take the shot and avoid pissing off my subjects even further, I had to set the bootflag off. With ML off, everything shot fine. I'm not sure if anyone had described this bug like this before. Lens FW: 2.0.0 Camera FW: 1.0.6. It worked fine for a long time before. Maybe its some sort of config bug. I tried turning off ML functions to get it to work, but I had no luck.

Thanks for reading,
Jerry
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 28, 2013, 08:27:57 PM
Heh, thats still not good because I can't have set path to reproduce that bug. I took tons of pics without it... plus new FW coming soon. Just waiting on a decrypted version to start.. hopefully its better for more than just AF.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 28, 2013, 08:45:58 PM
"Normal LV" is what we had before last version, isn't it?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 28, 2013, 09:05:35 PM
Before was just the non cropped LV, you can go back and forth, its like crop mode we discovered.. works on 650D too, but I want to start on new FW to fix MZ and maybe get display filters working.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 28, 2013, 10:03:22 PM
"Normal LV" = non croped, isn't it?
is there any mode with less crop and clean borders?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 28, 2013, 10:05:52 PM
Not that I can see :(

I tried reducing crop but didn't work thus far.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 28, 2013, 10:28:07 PM
with that crop it's just to narrow for most situations. but, it's nice if you need some extra zoom range.
did a small video test with a 100-400mm and the 18-55mm:
http://dl.dropboxusercontent.com/s/2vp9uowa6jjy1jk/compare.mp4

have still dots in the raw videos, had no time to create the pattern to remove it so far, but i'll do that now.

btw.. the videos have no post at all. just whitebalance and upscaling on the raw videos. but no sharpening, contrast, noisefilter, saturation or something like that. just straight from the camera.

the detail you still get with 400mm and digital zoom is unbelievable. you can see single hairs of the bee.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 28, 2013, 11:36:30 PM
The little 22mm focuses pretty close too.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 29, 2013, 12:29:55 AM
oh, it was not nearest it could focus. haven't tried to get as close as possible.
i don't like the 22mm for movies, because of the missing IS. of couse with a tripod that wouldn't make a difference, but it's just... not the lense for videos xD
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 29, 2013, 01:28:10 AM
Its tiny tho, still not bad with a real lens attached, lighter than 600d.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 29, 2013, 01:48:37 AM
just finished the dot removal meta data for the new mode:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2Fpe2hneejjx0wzbw%2Fbefore_dot_remove_crop.jpg&hash=1f5236b82eee1bbe107b33b43fb286f6)
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2Ffqot72vdoehqea4%2Fafter_dot_remove_crop.jpg&hash=edbbcd817c1544d75c92f96a6afa2126)

i will add it soon to that branch:
https://github.com/Foorgol/PinkDotRemover/tree/DngFreeGrid

dot removal data for full time crop can be downloaded there, till pullrequest is merged:
https://github.com/mixer2/PinkDotRemover/blob/DngFreeGrid/dotData/EOSM_Crop.txt

it will only work with the DngFreeGrid branch!
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 29, 2013, 10:00:07 AM
I think you can bootflag most of the eyefi cards. They work on 600D, why not here?

Maybe it's because of my eye-fi card is produced by other manufacturer. And also because I have upgraded to the 2.0.2 firmware, the old ML on the card won't work anyway. Currently I can't boot the camera with the eye-fi card's wifi function turned on. So basically I am just wondering a method to restore the bootflag and wait for the future 2.0.2 ML port that works with eye-fi.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on June 29, 2013, 10:19:47 AM
I am just wondering a method to restore the bootflag

Low level format the card.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 29, 2013, 12:57:46 PM
it says: "This video is private."

oh and the dots are not really smaller... the dots that appeared larger where 2 neighboring af pixels. in the old mode some lines and rows got dropped to scale it down. now it's not scaled down but cropped, so the lines between the pixels that were dropped are now still there which leads to some space between the two pixels.

Any idea why I keep getting the flicker screen towards the end of almost all my videos rendering with AF CS6. Example:

Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 29, 2013, 01:48:51 PM
one part of the video from yesterday with complete postprocessing. removed dots, noisefilter, sharpening, saturation, etc
http://dl.dropboxusercontent.com/s/r6rw17td3w4v2s9/with_post.mp4
you can see the hair on the flys legs. it's filmed at a distance where it was hard to see the fly at all.
it's the first time i really got imho usable result with eos m raw video. the only thing that i don't like is the ghosting effect of the flower, but i think this is caused by the lense. shouldn't have anything to do with raw video. but of course it wouldn't be as much visible if it wouldn't be filmed at 100% crop.
have to try what's possible with a real macro shot.

@Canon eos m: is this already in the dng, before you load them to AF?

@1%: is there a reason why it doesn't record exactly 16:9 in full time crop mode? it says that it has to be streched by 1.16%, but that doesn't look correct.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 29, 2013, 05:39:21 PM
@mixer2: yes, I first convert the footage to individual dng's with raw2dng and then import to After Effects CS6. I discovered this beautiful way to convert my rendered footage to low file sizes using hand break. It's free. Loving the whole experience. I am beginning to give up on shooting raw with the eos m. Will keep that for my 5DM3. But one thing that I love about the ML + EOS M combo is the exposure override - this is keeping my from upgrading the firmware. In fact this feature beats the 5DM3 for stills. But the 5DM3 is a beast when it comes to video.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 29, 2013, 05:42:23 PM
The stretch was on EOSM all the time until I found the crop mode. Should just be text.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 29, 2013, 07:19:14 PM
the text is not the problem... when you select 16:9 it records ~16:7,76 (1344x652) unsqueezed, but it should record 1344x756.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 29, 2013, 07:19:17 PM
Low level format the card.

Thanks for the reply but I mean the bootflag in the camera. It can't be restored by formatting the card.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on June 29, 2013, 08:24:30 PM
1% can you please upload the latest version for EOS-M after reading this thread for a while i don't know which one is the most stable and which one to use with firmware 2.0.2. And can you please explain the work flow for removing red dots. Thanks u in advance
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 29, 2013, 09:30:19 PM
1% can you please upload the latest version for EOS-M after reading this thread for a while i don't know which one is the most stable and which one to use with firmware 2.0.2. And can you please explain the work flow for removing red dots. Thanks u in advance

there is no version for 2.0.2 so far. if you have updated your camera you've to wait till there is support for 2.0.2.
you find the latest versions at (it's ordered chronological):
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/

at the moment there is a newer version, which is not listed there, because it's a bit dangerous to use it. if you want to try read this post:
http://www.magiclantern.fm/forum/index.php?topic=3648.msg55591#msg55591

for dot removal read this topic:
http://www.magiclantern.fm/forum/index.php?topic=6658.0

the dot remover version you find in this post is the most recent and should work for you (you need to have java installed):
http://www.magiclantern.fm/forum/index.php?topic=6658.msg55693#msg55693

if you use the latest (dangerous) version in full time crop mode (which you're in after hitting "don't click me") you've to download the dot removal data for this mode (only for vertical resolutions <= 652px so far):
https://raw.github.com/mixer2/PinkDotRemover/DngFreeGrid/dotData/EOSM_Crop.txt

this file has to be placed in the dotData directory of the dotremover you downloaded before. then you have the new option "EOSM_Crop" in the dropdown. So for full time crop use this option to remove dots and for all other modes use "EOSM".
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 29, 2013, 10:29:32 PM
I think there are dots at 10X/5x too.. I wast testing the crop/zoom and there they are. The 5x looks slightly further than crop @ 2kx1k. Module needs an exception for crop mode to stop unsqueezing.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on June 29, 2013, 10:50:16 PM
Thanks for your fast reply...
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 30, 2013, 02:10:17 AM
the dots aren't really a problem. the detail loss caused by removing dots is minimal. they look worse than they are, because a single af dot causes distortion in 5 dots after demosaicing, but just the information of the single pixel is really lost.
the clean edges are the most important thing imho. but i think that less crop = more edge distortion. the fast way the image is scaled down (by just skipping lines) is fatal for quality. and the loss in vertical resolution because of the squeeze makes it even worse.
does anyone know how canon solves that with h.264. do they use other data to encode h.264 or is it just a postprocessing thing?
would love to see a version with less crop and the quality of the full time crop mode. but... the full time crop mode is already really nice.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 30, 2013, 03:13:38 AM
one part of the video from yesterday with complete postprocessing. removed dots, noisefilter, sharpening, saturation, etc
http://dl.dropboxusercontent.com/s/r6rw17td3w4v2s9/with_post.mp4
you can see the hair on the flys legs. it's filmed at a distance where it was hard to see the fly at all.
it's the first time i really got imho usable result with eos m raw video. the only thing that i don't like is the ghosting effect of the flower, but i think this is caused by the lense. shouldn't have anything to do with raw video. but of course it wouldn't be as much visible if it wouldn't be filmed at 100% crop.
have to try what's possible with a real macro shot.

@Canon eos m: is this already in the dng, before you load them to AF?

@1%: is there a reason why it doesn't record exactly 16:9 in full time crop mode? it says that it has to be streched by 1.16%, but that doesn't look correct.

Awesome! Never know the EOS M was capable of such high quality video!
Title: Re: Tragic Lantern for EOS M
Post by: jaybean on June 30, 2013, 12:55:27 PM
Dear Great Intelligencies (nice one, feureau) and stuff,

So, about that 18-55mm shutter bug. I was finally able to reproduce it while trying to take a pciture with ML installed with one of the most recent autoexec.bins. Basically you hit the shutter release, the camera focuses, the rectangle turns green, but then nothing happens and your friends get really annoyed with you. In order to take the shot and avoid pissing off my subjects even further, I had to set the bootflag off. With ML off, everything shot fine. I'm not sure if anyone had described this bug like this before. Lens FW: 2.0.0 Camera FW: 1.0.6. It worked fine for a long time before. Maybe its some sort of config bug. I tried turning off ML functions to get it to work, but I had no luck.

Thanks for reading,
Jerry

I've experiencing the same problem with the 18-55 lens.  I bought my EOS M with 22 prime here in China about a month ago and installed ML on it right away, have shot lots of timelapses and HDRs with no problems on 22 prime lens and other Canon lenses mounted with adapter.  Then last week I bought the 18-55 (got it for about $75 new... gotta love Taobao.com!) and when I went to take my first picture nothing happened!  My first reaction was that I had been sent a fake lens, then I remembered someone mentioning a bug here on the EOS M forum.  So I erased ML off the card and sure enough the lens worked fine.  I was using the June 10 "[EOSM] Check unsquee.zip" build.  I just reinstalled ML with the June 15 “[EOSM] BugfixNewSystem.zip”, but my 18-55 doesn't work with that either.  My lens and camera FW are same as Jerry's: 2.0.0 and 1.0.6.

A few quick questions:
1) How do you turn the bootflag off?  I'm assuming this allows me to keep ML on the card but not boot the camera with it so that I can use the 18-55, right?
2) How likely is it that there will be a version of ML released for the new 2.0.2 firmware?  Will this possibly fix the bug?
3) How do guys like 1% and mixer2 handle being such badasses?  Seriously guys, you are awesome!!

Thanks to everyone who has made the EOS M port possible.  You've given my poor, undersized camera a massive p***s enlargement, and I'm enjoying strutting him around town!

Title: Re: Tragic Lantern for EOS M
Post by: haomuch on June 30, 2013, 01:03:37 PM
If you have not upgraded to the 2.0.2 version firmware, you can just flash the ml again the turn of the boot flag.

I am also eagerly waiting for the 2.0.2 version ml that could support eyefi card.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 30, 2013, 04:40:54 PM
there is a new dot removal testversion special for full time crop mode. all video resolutions should work with that version. however you can't remove dots from silent dng pics, because of wrong meta data in that files.
http://dl.dropbox.com/s/f3uj5ttwwuvind6/PinkDotRemover_eosm_full_time_crop.zip

there is no support for the non crop mode in that version, since the quality isn't usable anyways. but i'll update that data soon, if anyone may need it. until then the old version, with support for normal mode, should work, too.

@1%:
if i take a silent dng pic in full time crop i get wrong meta data. image size is 1798x1028 and meta data says 1872x1060. can anyone confirm that?
it would be nice if you could check that.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on June 30, 2013, 04:46:58 PM
Hmm, thats weird, says is 1798... maybe this is from the unsqueeze.. .I'll check in a sec. Would be nice if it was larger. Also frame skips... they look right but are they.

Yea, thats frame skips... the other part is blak.. 1028+28 skip = 1056

1798 + skip = 1872
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 30, 2013, 05:15:59 PM
are the skip values in the meta data?

ah found it... okey, meta info is correct... it just used the normal width and height, instead of active area for calculations.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 30, 2013, 06:05:02 PM
New video: purposely downsized to upload on you tube:
Tried to hide the pink dots using the Adobe Raw but could only succeed up to a point. Am getting better at the workflow though. Must admit that I try to follow the discussion between you both (Mixer2 and 1%) but cannot understand much.

Having fun learning new stuff nonetheless!

Thanks.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 30, 2013, 06:10:31 PM
The previous file did not upload since the file size was more than 4GB. Redone the size and upload can be found here:

Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 30, 2013, 06:16:49 PM
the video looks nice on my comp but horrible on youtube - will keep that in mind next time!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 30, 2013, 06:28:20 PM
the topic stays much more readable if you modify your post, instead of posting multiple in a row.

why is the video downscaled to such a low resolution? you may just upload the file to any cloud storage service like dropbox, to keep the quality as it is.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 30, 2013, 06:31:19 PM
Any place where I could learn to do that? The full file is about 48MB.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on June 30, 2013, 06:42:51 PM
lern how to upload to a cloud storage service? they are really easy to use, just google for "google drive", "dropbox", "box.com", "microsoft skydrive" or something like that.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 30, 2013, 07:05:31 PM
done already. have a dropbox account now. the file is loading on the dropbox server. will send the link once done. cheers!
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 30, 2013, 07:18:29 PM
@mixer2: dropbox link: https://www.dropbox.com/s/vr6gsij6bl1uzek/eos%20m%20video%20raw.mp4

Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on June 30, 2013, 07:36:08 PM
@mixer2: another video in my dropbox: https://www.dropbox.com/s/ar70hkyttuw0qjs/fountain%20raw%20eos%20m%20quality%2020.m4v
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 01, 2013, 11:45:58 AM
it may be a good idea to upscale it and then do some resharpening, etc. and you should do some noise filtering.
is there a reason, why you haven't removed the dots?

but the flat look you can get with the raw is just nice...
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on July 01, 2013, 04:29:37 PM
it may be a good idea to upscale it and then do some resharpening, etc. and you should do some noise filtering.
is there a reason, why you haven't removed the dots?

but the flat look you can get with the raw is just nice...

not sure how to remove dots or upscale. any links to learn from?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 01, 2013, 05:12:52 PM
Yea, it didn't seem to work when I used pink dot remover. Dots were still there on a full sized crop still.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on July 01, 2013, 05:31:51 PM
Hi,

I noticed that a very weird thing while rendering:

When I render using the "Generate video with selected RAW processor" on RAWanizer ver 0.5.0, I get these huge pink dots across the screen.

But, when I render using the "Only extract dng from RAW" on RAWanzer and then combine the stills on After Effects CS6, magically, the dots are much smaller - much more invisible to the naked eye. 

Will post samples once the rendering is done.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 01, 2013, 05:44:06 PM
Yea, it seems to do that. Straight to cineform... if I have those colored outlines on 6D they pop up.. if I do it with DNG and use process 2003 or 2012 its much less noticeable.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 01, 2013, 05:53:55 PM
ah, the dot remover tool doesn't work with RAWanizer so far. have to talk to foorgol if he plans to add support or if i should. it will just work with the raw2dng tool so far.
RAWnizer is only available for windows? anyone knows if it will work with wine? i'll try later, what exactly the difference between the RAWnizer and raw2dng DNG files is and how much work it is to make the dot remover compatible.
until then try raw2dng => dot remover => after effects.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 01, 2013, 06:09:38 PM
Rawanizer is a batch processor... processes .RAW to dng w/dcraw/raw2dng.. or straight to cineform... or dng -> video.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on July 01, 2013, 06:42:03 PM
ah, the dot remover tool doesn't work with RAWanizer so far. have to talk to foorgol if he plans to add support or if i should. it will just work with the raw2dng tool so far.
RAWnizer is only available for windows? anyone knows if it will work with wine? i'll try later, what exactly the difference between the RAWnizer and raw2dng DNG files is and how much work it is to make the dot remover compatible.
until then try raw2dng => dot remover => after effects.

Footage direct from RAWanizer: https://www.dropbox.com/s/sp4ekaiug4in9cr/M29-1605.proxy.mp4
Footage RAW2DNG: After Effects: https://www.dropbox.com/s/uf55x94j1wpcux9/M.mp4
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 01, 2013, 09:41:09 PM
can you upload the raw file you directly get from camera?
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on July 02, 2013, 08:04:25 AM
can you upload the raw file you directly get from camera?


RAW file uploaded: https://www.dropbox.com/s/y9v3ka63xmo6b17/M29-1605.RAW
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 02, 2013, 10:59:13 AM
thx, i'll play with that, just to see how much quality i can get out of it.
is a nice comparison of different workflows.

Still have to look at the RAWanizer output images. Thought that it's the same tool than anyone had problems with in the dot removal tool thread, but that was RAWMagic. foorgol added support for 16bit DNG from RAWMagic last night. Maybe this will help with RAWanizer also.

1%: can you send me a dng you had problems with to remove dots?

EDIT @Canon eos m:
i've tested your footage and dot removal works great with it. here is the first frame before and after:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F5tczptayin9ec6z%2Fcanon_eos_m_test_video_before.jpg&hash=11f202b3e7a446bbf376ff94b7ff4eed)
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F6pvjb2v13oxgiol%2Fcanon_eos_m_test_video_after.jpg&hash=003a98b1e949252e96dfd87177151cd8)

complete video (color corrected, upscaled to 1080p, denoised, sharpened, some saturation added). complete workflow:
raw2dng -> dot remover -> import to aftereffects (only whitebalance in cameraraw) -> noise filter -> sharpening -> brightened dark areas via levels -> added some saturation:
http://dl.dropbox.com/s/snzo2b7o0urjy43/canon_eos_m_test_video.mp4

your footage was quite soft, shaky and noisy. what were your camera settings and wich lense? looks like very high aperture... like 22 (=> softness) 1600 iso (because of the high aperture => noise) and 22mm (=> no IS => shaky).
i really hope that the softness is because of the camera settings and not caused by the 100% crop of the raw video. have to find some time to do a testvideo.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 02, 2013, 01:05:33 PM
Btw, is anyone working on putting ML on the 2.0.2 firmware? :P
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on July 02, 2013, 01:42:54 PM
Btw, is anyone working on putting ML on the 2.0.2 firmware? :P

Good question- I´m still acting with 1.0.6 because I need zebra and focus peak all the time but would love to have the faster focus too. Anyway - the day will come I guess. :)
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on July 02, 2013, 01:51:10 PM
Good question- I´m still acting with 1.0.6 because I need zebra and focus peak all the time but would love to have the faster focus too. Anyway - the day will come I guess. :)

Me too. I was dying to get me hands on the 2.0.2 update but refuse to give up on the benefits that ML brings - especially Exposure Override.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 02, 2013, 03:03:39 PM
I was dying to get me hands on the 2.0.2 update but refuse to give up on the benefits that ML brings

Yeah, me too... that af speed looks great though
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on July 02, 2013, 03:19:04 PM
thx, i'll play with that, just to see how much quality i can get out of it.
is a nice comparison of different workflows.

Still have to look at the RAWanizer output images. Thought that it's the same tool than anyone had problems with in the dot removal tool thread, but that was RAWMagic. foorgol added support for 16bit DNG from RAWMagic last night. Maybe this will help with RAWanizer also.

1%: can you send me a dng you had problems with to remove dots?

EDIT @Canon eos m:
i've tested your footage and dot removal works great with it. here is the first frame before and after:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F5tczptayin9ec6z%2Fcanon_eos_m_test_video_before.jpg&hash=11f202b3e7a446bbf376ff94b7ff4eed)
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F6pvjb2v13oxgiol%2Fcanon_eos_m_test_video_after.jpg&hash=003a98b1e949252e96dfd87177151cd8)

complete video (color corrected, upscaled to 1080p, denoised, sharpened, some saturation added). complete workflow:
raw2dng -> dot remover -> import to aftereffects (only whitebalance in cameraraw) -> noise filter -> sharpening -> brightened dark areas via levels -> added some saturation:
http://dl.dropbox.com/s/snzo2b7o0urjy43/canon_eos_m_test_video.mp4

your footage was quite soft, shaky and noisy. what were your camera settings and wich lense? looks like very high aperture... like 22 (=> softness) 1600 iso (because of the high aperture => noise) and 22mm (=> no IS => shaky).
i really hope that the softness is because of the camera settings and not caused by the 100% crop of the raw video. have to find some time to do a testvideo.

@Mixer2 - You have to teach me this stuff  ... all of it.

I will keep an eye on the camera next time ... for the shake and the rest.

This time the lens was 22mm f2.0. I have the Sigma 35mm f1.4; the Canon 24-105mm f4.0; the Minolta 50mm f1.2 (manual focus); the Canon 28mm f2.8; the Canon 18-55mm f3.5-4.5 (EOS M version). Which one would be best considering that the sensor is 1.6X and the crop is magnified. I guess the 18-55 or 24-105 should be good for the job.

Please teach me how to upscale to 1080p and also to use RAWMagic. Is the workflow for RAWMagic similar to that of RAWnizer? Is there no way to get this done with RAWnizer since I really love the interface. One of the easiest I have used in a long time. 

Will shoot another video tomorrow or maybe dayafter. Send you the RAW to play with while I learn how to remove the dots using RAWMagic. 

Right now my tools are:

Photoshop RAW Version 8.1 - learing how to use it
After Effects CS 6.1 - super learing how to get the best from it
RAWnizer 0.5.0 - Cannot live without it
Resolve Davinci Resolve 9 Lite (free download from the Blackmagic website) - learing how to play with it
Handbrake - use it to resize the videos for youtube

Super loving the whole experience. Don't understand the technical stuff 1% and you talk about but just wait when you guys come out with stuff that is easy to use and I just grab it.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 02, 2013, 07:22:54 PM
This time the lens was 22mm f2.0. I have the Sigma 35mm f1.4; the Canon 24-105mm f4.0; the Minolta 50mm f1.2 (manual focus); the Canon 28mm f2.8; the Canon 18-55mm f3.5-4.5 (EOS M version). Which one would be best considering that the sensor is 1.6X and the crop is magnified. I guess the 18-55 or 24-105 should be good for the job.


Go with the 18-55 IS STM. The IS helps the shake.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on July 03, 2013, 07:12:06 PM
@Mixer2 - I cannot use the RAWMagic.dmg on my windows PC! Is there any place where I could get hold of a windows compliant version of RAWMagic?

RAWanizer still remains my best bet. However, dots remain an issue and there is no way to get rid of these with RAWanizer, RAW2dng, etc.

The crop magification does not appeal to me. So, I now record most of my video on picture mode with the Menu button. This gives me a better buffer and the real actual magification of 1.6X. Is there any way to turn off the crop on video mode?
Title: Re: Tragic Lantern for EOS M
Post by: whatever7 on July 03, 2013, 07:46:54 PM
Hello, first time poster here.

I just got a EOS M for cheap.

What I want to know is can I install this alpha firmware and get time lapse function?  Whats the shortest internal for time lapse photo in manual everything mode, 1 second?

Thanks for you reply.  I am farely familiar with CHDK so hopeful ML is not harder to installer than CHDK.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 03, 2013, 09:22:45 PM
@Canon eos m: sorry, had no time to write you a detailed description how to remove dots etc. you really don't have to use rawmagic. i haven't tried RAWanizer so far, but if it can convert to dng via raw2dng, like 1% said, it should work just fine. else just try to convert it with the raw2dng.exe. just drag your raw file and drop it onto the raw2dng.exe file. this should give you working dng files. to remove dots download the latest dot removal tool:
https://dl.dropboxusercontent.com/u/22843507/MagicLantern/PinkDotRemover_debug.zip
you just have to unzip the file. if you've already installed java jre it should start if you doubleclick on the PinkDotRemover.jar. if it doesn't start and windows tells you, that it doesn't know how to open the file then install java jre and try again (http://www.java.com/de/download/).
in the dot remover tool click on "add files" and select all the dng files (no other files, just the dngs). select from the dropdown "EOSM" if you've not recorded in full time crop (everything you get without clicking on "don't click me" in the latest ml version). if you've recorded in full time crop mode select "EOSM_crop". then just click on "convert files". after the conversion you'll find for each dng file another one with a "_" prepended. in that files the dots should be gone. if one of the converted dngs still contains dots send it to me with the information if you selected "EOSM" or "EOSM_crop" and i'll check what's wrong.
the most simple postprocessing is to just load the dngs directly into after effects. it will automatically open cameraraw as you add the files. it's a good idea to do the whitebalance in cameraraw and do all other postprocessing in after effects. the most important thing in after effects is to add a noise filter, because raw data is always noisy, even with iso 100. i really like neat video. it's not free, but you can download a free demo version to check if it fits your needs. but there are also a lot of other good free noise filters out there.
next thing is the upscaling. open the composition settings and set it to width 1920 and height 1080 for a 1080p video. after that you'll see a black border around your video, because it's smaller than the composition. just drag the edge of the video to fit the width of the composition (no black borders at the left and the right). hold shift while dragging to keep the correct aspect ratio.
after that you've a solid base for all the other postprocessing. just play with colors, saturation, levels, curves, sharpening, etc. i can do a short screencast if this may help you.
about the lenses... as feureau said the ef-m 18-55 IS STM is nice, because it has IS. you should use IS lenses if you don't shoot with a tripod. the 24-105 also has IS and is one of the most used lenses for dslr video. but seriously it's just to large for the eos m in most cases. if you've such a large and heavy lense with you, you can also use your primary camera. if you use the 22mm without tripod you'll get shaky video.

about the crop... yes, the extra crop does suck. with the 18mm you've a slightly narrower field of view than with 55mm and much more dof. but in all other modes you can't get high quality raw video from the eos m so far. i think it just doesn't make any sense to record raw video in any other mode than full time crop at the moment. you won't get better results than with h.264 in the normal mode. the only reason may be if you really need the extra dynamic range. but you can also get some extra dynamic range with a flat profile.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 03, 2013, 11:36:32 PM
Quote
extra dynamic range with a flat profile.

Well more like an illusion of extra dynamic range.

Maybe the new firmware will help some of this, nanomad was supposed to upgrade his M and then maybe I'll finally get a dump.
Title: Re: Tragic Lantern for EOS M
Post by: 350D on July 04, 2013, 03:53:04 AM
Maybe the new firmware will help some of this, nanomad was supposed to upgrade his M and then maybe I'll finally get a dump.

I'm on 2.0.2 right now and i can help with testing if needed.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 04, 2013, 06:52:27 AM
nanomad was supposed to upgrade his M and then maybe I'll finally get a dump.

Yay! \o/
Title: Re: Tragic Lantern for EOS M
Post by: lofty on July 04, 2013, 03:22:52 PM
Hi,

If I have 2.0.2 firmware version will the current version of Magic Lantern work ? 
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on July 04, 2013, 03:57:44 PM
Hi,

If I have 2.0.2 firmware version will the current version of Magic Lantern work ?

No - you have to wait till 2.0.2 is supported. We all hope it wont take long.
Title: Re: Tragic Lantern for EOS M
Post by: lofty on July 04, 2013, 04:31:54 PM
cheers for the reply, thanks
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on July 04, 2013, 05:31:17 PM
@mixer2 - got the neat video plug-in but cannot get it to work. a screencast would be welcome.
Title: Re: Tragic Lantern for EOS M
Post by: 1drey on July 04, 2013, 06:25:35 PM
Hello everyone, my first post here  - I just ordered an EOS M :)
Sorry if my question will sound stupid.

Is there any option to trigger EOS M without getting into guts and soldering wires? Can it be done with the aid of software modification (through ML)? 

Thank you!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 04, 2013, 07:21:21 PM
@1%: i don't think that it's just an illusion of more dynamic range, because i definitely got better results with flat profile than without it.
and it also does totally make sense. if you add contrast to an image, it streches the values to get a higher difference. on an image that already uses the hole range some values at the borders go beyond the limits. and that information is lost. and canon does add a lot of contrast by default, since the videos look more appealing straight out of the camera, if they are contrasty. and that's also what i see on the histogram when i do a video in same conditions with flat profile and with standard profile. when there are already a lot of pixels under- and overexposed with standard profile i'm still in the range with flat profile.
can you explain, why you exactly think, that it's just an illusion?

@canon eos m:
i'll do a screencast tomorrow.

@1drey:
what exactly do you want to do? simple remote triggering? you can trigger eos m via ir remote. there is afaik no way to remote control via pc, tablet, smartphone, etc. and there is also no way to trigger via cable... not without serious modification of the camera.
ml has some features like motion detection and trap focus. i don't know if they are available on eos m so far and i doubt that they fit your needs, because they are very special.
Title: Re: Tragic Lantern for EOS M
Post by: 1drey on July 04, 2013, 07:47:55 PM


@1drey:
what exactly do you want to do? simple remote triggering? you can trigger eos m via ir remote. there is afaik no way to remote control via pc, tablet, smartphone, etc. and there is also no way to trigger via cable... not without serious modification of the camera.
ml has some features like motion detection and trap focus. i don't know if they are available on eos m so far and i doubt that they fit your needs, because they are very special.

Unfortunately ir remote is not very reliable unless you keep a transmitter very close to the sensor
I plan to use EOS M as a travel/backup camera for shooting spherical panoramas - sometimes the photographer can significantly influence the light making the subsequent stitching of panoramas problematic, or camera can be mounted on the top of the high pole... I use radio trigger with my main camera 5DMkII and find it necessary feature...
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 04, 2013, 07:54:32 PM
hurm... don't know, but radio trigger may work with eos m. i don't see any reason why the hotshoe shouldn't support it...
one of the first google results say it does support, but ... don't know if it's trustable.
http://www.lightandmatter.org/2012/equipment-reviews/canon-eos-m-new-canon-eos-mirrorless-system/

if you have a radio trigger anyways just try it, as soon as your eosm arrived... i think there is a good chance that it just works.
Title: Re: Tragic Lantern for EOS M
Post by: lofty on July 04, 2013, 08:10:07 PM
Hmmm this is interesting, I am hoping that when ML comes out for 2.0.2 for the EOS M, I will use the intervalometer setting to take photos for time lapse.

Is this not possible then ?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 04, 2013, 08:45:25 PM
intervalometer does work on eos m... if that is what you need, it should work for you.

@1%: i still never got any black screen with the full time crop mode btw. even after accidentally activating in photo mode or switching to photo mode while it's activated. is there any reason to leave the full time crop mode, except for h.264 video recordings?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 04, 2013, 10:34:33 PM
Its fine going between photo/video. Might be luck if it didn't cause problems starting it in photo mode.

720P mode will black it out for sure.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 04, 2013, 10:49:05 PM
ok... nice. i'm not often in 720p anyways... rarely need more than 25fps...
any more detailed information, why you don't think that flat profiles increase dynamic range?
Title: Re: Tragic Lantern for EOS M
Post by: daemorhedron on July 04, 2013, 11:05:52 PM
Great work guys, I'm a bit of a geek and hope that I can help out in some fashion (just reading docs/apis/source now, be a while before I can really contribute) but I admit I sure hope to get remote control/tethered shooting working.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 04, 2013, 11:20:12 PM
Because they don't, they just lift your shadows a bit. They are applied after the data is lost already in the chain (post 8 bit conversion). Still not bad to use but you're not really gaining anything.

BTW, pink dot didn't work on this series:

http://www.qfpost.com/file/d?g=AlGJJSBsG (http://www.qfpost.com/file/d?g=AlGJJSBsG)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 04, 2013, 11:36:29 PM
it is 8bit and there is data lost already... but if you increase the contrast before you get it out of the camera, you'll lose even more information.

the dng is a silent dng, isn't it? still had no time to fix the silent dngs. there is something wrong with the calculation because of the frame skip. all video dngs should work, i planned to do the silent dng at the weekend. but... i'll check if i can do it now ;)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 04, 2013, 11:55:21 PM
The low contrast is better, I use marvels for H264 for that reason.. but increased range it is not.

The silent DNGs are nice for time lapse, etc. I figured they would be the easiest to do since its just 3 resolutions but I guess not.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 05, 2013, 12:18:50 AM
silent dngs do use the active area, which the video frames don't. they should be easy to support (they do work for 650d), but the active area just confused me. i got even more confused by the term "frame skip" since i thought about skipped video frames.
since the calculation of the dots is center based and the active area crop is not, it has to be corrected with the correct offset. is not really complicated at all, was just my fault -.-

EDIT:
try this one for silent dngs (select EOSM not EOSM_Crop from the dropdown):
http://dl.dropboxusercontent.com/s/j727o0iaho4i3vd/EOSM.txt

i'll add it to the repository tomorrow.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on July 05, 2013, 04:28:55 AM
So as someone thinking about getting an EOS M...

Where does it stand in terms of the RAW video capabilities? I skimmed through and saw it has a faster write speed than my 60D, so I'm excited to at least get 1280x720 or crop versions of this resolution in RAW. Is this already possible or does it seem likely in the near future?

Thanks y'all!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 05, 2013, 06:31:39 AM
1280x720 should work in crop mode and not be all stretched. 6D can handle this, I only tried the 30Mb/s card in EOSM.

Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 05, 2013, 08:44:08 AM
@1%:
did the new dot removal data work for you?

@handbanana:
i can upload you some sample data later if you like?
Title: Re: Tragic Lantern for EOS M
Post by: lofty on July 05, 2013, 11:23:09 AM
intervalometer does work on eos m... if that is what you need, it should work for you.


Cheers, I will wait for the 2.0.2 firmware version then :)
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on July 05, 2013, 03:23:04 PM
@mixer2: That would be awesome, thanks! EOS M is on sale now, so if I can get better continuous RAW than the 60D (960 wide) for $300 I'd be pretty happy :3
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 05, 2013, 04:52:03 PM
The dot remover worked. The files I have are clean now. Failed on just marking the pixels but interpolate worked great.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on July 06, 2013, 12:39:21 PM
@1% You can extract the ROM from the .fir, no need to upgrade your camera. You can ask the usual guy for help :P
Title: Re: Tragic Lantern for EOS M
Post by: GizmoWu on July 06, 2013, 04:58:37 PM
Thank you all so much for working on the ML software. As a new owner of the EOS M, this camera is awesome with the new firmware upgrade. I don't do as much video as you all do in a professional mode, however, I do more photography. If you are taking requests from photographers, I would like to ask for these features.

1) More shot options for auto bracketing. Currently, you are limited to 3. Having 5 or 7 would be great.
2) Increasing the bracketing EV range from +-2 to +-3 or more
3) Create a function where you can prevent accident menu changes from touches to the screen. This is an annoying flaw.

Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 06, 2013, 05:37:10 PM
@Canon eos m:
i found some time to create the screencast for you. most is simply the same as in all the other ml raw workflow videos on youtube, but there are 2 steps that may help you especially.
1. it shows how to remove dots
2. it shows how to scale it to 1080p in after effects
one problem is, that i accidentally didn't record the mouse cursor. i usually don't do screencasts on windows, so i didn't know the screencast software. i hope it's understandable anyways. the other thing is, that i recorded it without sound. but i'll write you a description here:
https://dl.dropboxusercontent.com/s/9tetcfem6qb43nz/post_processing_dotremoval_ae_neatvideo.webm

1. droped the raw video onto raw2dng.exe to extract the dngs (i canceled it after 76 frames to keep the video short)
2. moved the raw out of the dng directory
3. opened the first frame to show that there are dots
4. opened the dot removal tool and added the files to the list
5. changed the dropdown in dot remover to EOSM_Crop
6. got sure, that mode is "interpolate"
7. converted files (it shows an error for the last frame, this is because i interrupted the dng extraction at frame 76 before... it wasn't completly extracted)
8. removed the old dngs (with dots), all files without "_" prefix in the directory
9. showed that the new first frame doesn't has dots anymore
10. opened after effects
11. imported multiple files (selected the first dng)
12. whitebalance in camera raw (camera raw opens automatically while importing dng to after effects)
13. clicked onto done to close the import dialog
14. created new composition
15. changed composition settings to my target resolution. (lock aspect ratio has to be disabled)
16. dragged the edge of the video to match the size of the new composition (hold shift while dragging to keep aspect ratio)
17. added neat video
18. opened neat video options
19. selected an area where neat video should create a profile from. that way wouldn't lead to the best results, you should do noise profiles for different iso values with extra footage and then just use them instead of creating a new noise profile. but if no noise profile is available this should work to.
20. adjusted noise filter settings... i do a lot of sharpening with the noise filter... just try which way of sharpening works best for you
21. added unsharpen mask to do even more sharpening
22. added levels and curves to increase contrast, midtones and light in dark areas
23. added a photo filter to bringt back a bit more of the pinkish tone of the down going sun
24. checked the video and noticed the wrong frame rate.
25. changed composition options again to match the correct frame rate.

hope this helps you to get dotless and noiseless videos in post ;)

@handbanana:
i tried to create some demo videos for you yesterday, but after work it was to late and to dark.. the videos just sucked ;)
i'll do some demo stuff now and upload it for you in few hours.
the main problem with raw video on eosm is the extreme crop... so i doubt, that it may be more usable than 60d. the faster sd controller let you record more pixels, but you're limited to the tele range. and the quality of 100% crops is just not as good as properly downscaled data.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on July 06, 2013, 09:02:31 PM
@mixer2:

Thanks I appreciate it! Why exactly is the M limited to extreme crop? Isn't it basically a 650D in a smaller body anyways? I just ordered one yesterday b/c at $300 it seemed a no-brainer as a 3rd camera, but I've also been harboring hope that it would make a decent upgrade in the RAW video department (a used 50D seemed a good option also but useless for anything besides films).

What are the chances that this could be fixed in the future? At 40mb/s we should theoretically get at least 720p RAW video (even if cinemascope cropped) which would be enough for me since upscaled 720p looks almost as sharp as the 1080p (as per tests on my 60D).

Anyways, thanks again, and sorry for the questions, I'm joining the EOS M party pretty late.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 06, 2013, 10:38:31 PM
if you record video with eos m without crop mode you'll get very unclean edges. there is an example video h.264 first, then raw.
http://dl.dropbox.com/s/lincex5op3relr7/dotremoval.mp4
there are imho 2 reasons that cause this problem:
1. you get less vertical resolution than horizontal and has to strech it vertically
2. the way the 18megapixels get scaled down to the ~2 megapixels used for video isn't high quality. i think they just skip the pixels they don't need, instead of any interpolation

today i did some new shots... they really suck, because i focused on doing shots with the different settings, instead of what i shoot. but... it's good enough to judge quality, imho.
here's the description why i added that setting to the demo video, for each setting:
1. h.264 normal 18mm, to compare the angle of view to 18mm crop
2. there it is... 18mm crop that's how it's magnified at crop mode
3. raw 1280x662. that's the closest you can get to 720p for continuous recording
4. raw 1600x576. this is imho one of the best resolutions for raw recording. it doesn't has to be as much upscaled as the 1280x662 and has an acceptable aspect ratio
5. 1728x496. the highest horizontal resolution you can get. to get continuous recording the aspect ratio is very extreme... but it shows what the maximum quality is.
6. again h.264 18mm for angle of view comparison
7. h.264 55mm to compare the angle of view, sharpness and dof to 18mm crop
8. h.264 18mm crop
9. h.264 55mm and crop mode

http://dl.dropbox.com/s/06dgg2nfkqa0jgf/raw_h264_comparison.mp4

hope this helps you to judge the quality you can get and if raw video on eos m makes sense for you. if you want any raw files directly from the camera, just tell me which ones, then i'll upload it.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on July 06, 2013, 11:41:31 PM
@mixer2: Wow thanks for the videos! I see that the resolution you recommend seems to be the best bet, how extreme is the crop on the M? Is it a 1:1 crop?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 07, 2013, 12:07:52 AM
the 18mp are 5184x3456 and the magification is bit more than factor 3 (18mm on crop is bit closer than 55mm without, as you can see in the videos), so i guess it is just a 100% crop, yes. then the factor should theoretically be 3,24 with 1600x576. and exactly 3 with 1728.
the more often i watch the video the more i like the 1728x496 :D the aspect ratio is extreme... but it really looks clean and sharp... compared to h.264 the 1600x576 is also much sharper, but it's just not as clean as the 1728... hurm have to do more videos with both resolutions and check which one i like more.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on July 07, 2013, 06:02:24 AM
They both looked really nice. Too bad for that crop, although I'm sure there will be useful moments for it. Hopefully we can get the non-crop to not be all stretched, or does that seem impossible?
Title: Re: Tragic Lantern for EOS M
Post by: 350D on July 07, 2013, 07:43:24 AM
Guys, i'm not sure, but did you made any research about dot removal via simple color overlay?
I have tried to create couple layers with different overlay modes here:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ff.cl.ly%2Fitems%2F2V250n0u2t2f3Z3U2L3d%2Fcanon_eos_m_dots_overlay.gif&hash=12937f5735c7db17bdd63662a15b590e)
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 07, 2013, 09:25:02 AM
Guys, i'm not sure, but did you made any research about dot removal via simple color overlay?
I have tried to create couple layers with different overlay modes here:
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Ff.cl.ly%2Fitems%2F2V250n0u2t2f3Z3U2L3d%2Fcanon_eos_m_dots_overlay.gif&hash=12937f5735c7db17bdd63662a15b590e)

Novel idea, but it looks like it has black dots all over now. Maybe a less powerful overlay?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 07, 2013, 12:43:43 PM
@handbanana: i wouldn't have to much hope, that eos m will ever record clean raw video without crop. but i don't know... maybe 1% can say anything about that. maybe anything has changed with the new firmware?

@1%: i noticed, that af works with crop mode and even while raw recording. i really don't need it while recording, but it's quite handy before i start recording, since zoom doesn't work and that's the fastest way to get good initial focus. btw, you can only focus once while recording, then it won't work, until you stop the record, if anyone needs af while recording. my problem is, what i hated at the eos m af anyways, that the mixed auto+m focus mode doesn't allow manual focus, if you didn't let it do af first. so if i use af for initial focus i can't focus manually while recording. is there any way to change the behavior of that mode, that it always uses manual focus if you turn the focus ring. that would be great also for other situations... like the mz enables while turning the af ring it should also switch to manual focus.. and if you don't turn the focus ring for 2-3 secounds switch back to af+m. don't know if you can switch af mode and if it's possible to detect focus ring changes while not in manual focus mode.
another thing i noticed is that it is possible to record h.264 digitally zoomed in full time crop. that's really nice.
Title: Re: Tragic Lantern for EOS M
Post by: 350D on July 07, 2013, 03:16:15 PM
Novel idea, but it looks like it has black dots all over now. Maybe a less powerful overlay?

For better result i need original image (png24 for example) and dots map on black and white backgrounds. Anyone can help with that?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 07, 2013, 03:50:35 PM
what's wrong with the method of the dot removal tool for removing dots? if you need a dot map, you can directly use the dot grid data from the dot remover, if that helps:
https://github.com/Foorgol/PinkDotRemover/blob/master/dotData/EOSM_Crop.txt

first value is horizontal offset (center based), secound is vertical offset (center based), third is vertical limit (center based), fourth is horizontal step size and fifth is vertical step size. this grid data should work for video recordings in full time crop.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 07, 2013, 03:52:39 PM
The low contrast is better, I use marvels for H264 for that reason.. but increased range it is not.

The silent DNGs are nice for time lapse, etc. I figured they would be the easiest to do since its just 3 resolutions but I guess not.

Does shooting with HTP on Raw helps with DR?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 07, 2013, 04:03:25 PM
no it doesn't. the only effect you may get is underexposed footage. that's what htp does, underexposing and brighten shadows.
Title: Re: Tragic Lantern for EOS M
Post by: 350D on July 07, 2013, 07:51:56 PM
what's wrong with the method of the dot removal tool for removing dots?

The difference is that dot removal tool - interpolate nearest pixels (right?), that means data lost in this area. Overlay method use color data from real pixel. After that you can use interpolation only for center pixel, to restore red channel value (for red pixels).
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 07, 2013, 08:11:29 PM
it's always just the center pixel. the 4 pixels around get distorted by demosaicing, if the wrong pixel isn't corrected before. and i don't think the center pixel does contain any useful data, does it?
Title: Re: Tragic Lantern for EOS M
Post by: 350D on July 07, 2013, 08:24:53 PM
it's always just the center pixel. the 4 pixels around get distorted by demosaicing, if the wrong pixel isn't corrected before. and i don't think the center pixel does contain any useful data, does it?

Can you send a real 1:1 photo with pixel grid to me? I thinking that red pixels contains real green and blue channels data.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 07, 2013, 08:45:53 PM
on bayer data each pixel contains only color information of one color channel.
what data do you exactly need? a dng file without removed dots?
Title: Re: Tragic Lantern for EOS M
Post by: 350D on July 07, 2013, 08:49:05 PM
right, photo without removed dots.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 07, 2013, 09:16:29 PM
with dots:
http://dl.dropbox.com/s/738xtis2y8b621j/with_dots.dng
and without:
http://dl.dropbox.com/s/pzbrwho0vasche7/without_dots.dng

hope they help...
Title: Re: Tragic Lantern for EOS M
Post by: 350D on July 07, 2013, 09:23:36 PM
@Mixer2: can you please shoot something with a real world scene to control overlay/mask quality?
Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 07, 2013, 09:38:11 PM
oh, ok... thought taking a photo of a white surface is good, because the dots are very clear on that.
there are the new ones:
http://dl.dropbox.com/s/xmq2n463udces23/with_dots_2.dng
http://dl.dropbox.com/s/attqx24gkkvrg88/without_dots_2.dng

hope they are correct now..

this is a mask of the dot grid the dot remover uses. the black pixels get interpolated. maybe this will help too.
http://dl.dropboxusercontent.com/s/o3qe0i1swnp47i1/dot_mask_1536.png
Title: Re: Tragic Lantern for EOS M
Post by: millernet on July 08, 2013, 04:19:23 PM
Hi--sorry for the question, searched, but could not find the answer.

Just received the EOS-M and it had the new firmware--is it possible to revert to the older firmware so I can use ML?  If so, can someone point me to the download file?
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 08, 2013, 04:23:00 PM
Hi--sorry for the question, searched, but could not find the answer.

Just received the EOS-M and it had the new firmware--is it possible to revert to the older firmware so I can use ML?  If so, can someone point me to the download file?

Someone mentioned that it's impossible to downgrade to the older firmware because canon doesn't provide downloads of the .fir.

However, I wonder if the firmware dumped to make the ML can be used for firmware upgrades? if so, the devs could provide you with that I guess. But I'd probably rather wait until they updated the alpha for the new firmware.
Title: Re: Tragic Lantern for EOS M
Post by: Pelican on July 08, 2013, 10:11:59 PM
Crazy deal:
Canon EOS M w/22mm f/2 kit for $299. (http://www.bhphotovideo.com/c/product/883304-REG/Canon_6609b033_EOS_M_Digital_Camera_with.html/bi/2466/kbid/3296)

More :
http://www.canonrumors.com/2013/07/crazy-deal-canon-eos-m-w22mm-f2-299-at-bh/
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 09, 2013, 02:56:07 PM
That's a really good deal. I suppose the next iteration of the EOS-M is coming out in a short while, then.

EDIT: Welp, the next post on CR pretty much speculate that, also:

Quote
Also in development is a focal length reducer for EF lenses, this will be announced with the 20mp EOS M camera.

... wait, a speed booster-like adapter? HOLY SHIT! WANT!
Title: Re: Tragic Lantern for EOS M
Post by: DavidFell on July 11, 2013, 12:14:08 PM
The $299 price at Amazon makes sense now. Adorama says its no longer available. B&H now has it with either lens for $349. And there's this: http://www.geeky-gadgets.com/canon-eos-m-refresh-arriving-towards-the-end-of-this-year-rumour-08-07-2013/ (http://www.geeky-gadgets.com/canon-eos-m-refresh-arriving-towards-the-end-of-this-year-rumour-08-07-2013/)

Crazy deal:
Canon EOS M w/22mm f/2 kit for $299. (http://www.bhphotovideo.com/c/product/883304-REG/Canon_6609b033_EOS_M_Digital_Camera_with.html/bi/2466/kbid/3296)

More :
http://www.canonrumors.com/2013/07/crazy-deal-canon-eos-m-w22mm-f2-299-at-bh/
Title: Re: Tragic Lantern for EOS M
Post by: DavidFell on July 11, 2013, 12:16:16 PM
Oh, and although Amazon said the $299 EOS M would ship in 6 to 8 weeks when I ordered it Sunday, UPS already has it, and it will be in my hands tomorrow.
Title: Re: Tragic Lantern for EOS M
Post by: jstanley0 on July 12, 2013, 05:36:59 PM
just received my $299 EOS M, which shipped with firmware 2.0.2.

I want to perch this thing on my telescope and take some wide-sky astrophotos with the 22mm f/2 lens, and ML's intervalometer and bulb control are just what I need.

Is there anything I can do to help port ML to the new firmware?  I contributed a few commits to the ELPH 300 HS port of CHDK, so I have a little (hopefully related) experience.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on July 12, 2013, 10:17:42 PM
Is it possible to support eyefi card in the next version? I don't understand why it's not supported since the eyefi card just work within its own internal control parts and only needs the camera provide the battery.
Title: Re: Tragic Lantern for EOS M
Post by: tmophoto on July 13, 2013, 12:26:59 AM
would love to see a super basic firmware for 2.0.2 cameras that has timelapse, focus peaking and bulb control

Hope you guys can decode the new firmware or someone finds a way to get the old firmware on the new cameras.

super interested if someone can get usb camera control to work.  the lack of a proper remote is a huge drawback that i had not realized before buying the camera last week.

is there any way to get the camera to function in intervalometer mode with the rear screen off?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 13, 2013, 12:48:43 AM
My rear screen turns off and it keeps taking pictures.

As for eye-fi, if you can boot flag the card then it will work. I don't exactly have a card to try.
Title: Re: Tragic Lantern for EOS M
Post by: tmophoto on July 13, 2013, 02:28:19 AM
cool thanks,  cant wait to get the ML on the EOS M with 2.0.2 firmware

Title: Re: Tragic Lantern for EOS M
Post by: handbanana on July 13, 2013, 02:59:01 AM
Mine also came with 2.0.2 firmware. The expanded ISOs and some cropmarks are all I'd really really want. What would happen if I tried to install the older firmware onto an M with 2.0.2?
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 13, 2013, 04:44:25 AM
What would happen if I tried to install the older firmware onto an M with 2.0.2?

You'll get arrested by the firmware police for version violation.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on July 13, 2013, 05:05:17 PM
Is that possible that we can disable the basic information display of ML over the stock UI while still keeps the peek focus or other functions display? I prefer the stock UI much more when it comes to showing the settings.
Title: Re: Tragic Lantern for EOS M
Post by: Michael L on July 13, 2013, 11:06:13 PM
I just received one of the $299 EOS-M's yesterday, and got it airborne on my kite aerial photography camera rig today! 

I was planning to trigger the camera with ML's intervalometer, but didn't realize that ML is not working with the new firmware version yet.  Luckily I was able to trigger via infrared remote.  Hoping ML is working with the EOS-M again soon!

Here's my first aerial keeper shot with the EOS-M earlier today:

http://www.flickr.com/photos/ml_kap/9276239883/
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 14, 2013, 01:23:49 AM
Ok, I have the firmware so now just have to crunch it. First hurdle is gone tho.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on July 14, 2013, 03:20:09 AM
@1%: I just want you to know that I love and appreciate you so much. :3
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 14, 2013, 05:50:00 AM
Ok, I have the firmware so now just have to crunch it. First hurdle is gone tho.

Hooray! :D
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 14, 2013, 05:51:25 AM
I just received one of the $299 EOS-M's yesterday, and got it airborne on my kite aerial photography camera rig today! 

I was planning to trigger the camera with ML's intervalometer, but didn't realize that ML is not working with the new firmware version yet.  Luckily I was able to trigger via infrared remote.  Hoping ML is working with the EOS-M again soon!

Here's my first aerial keeper shot with the EOS-M earlier today:

http://www.flickr.com/photos/ml_kap/9276239883/

Whoah! That's some really good shot. Mind sharing what your kite rig looks like? How far was it to still be able to trigger with the IR?
Title: Re: Tragic Lantern for EOS M
Post by: jaybean on July 14, 2013, 06:10:36 AM
@1%: I just want you to know that I love and appreciate you so much. :3

I second that!  Keep up the amazing work 1%!!

And Michael L, yes please do share more info about your kite rig.  I've thought of getting one for my s100 for some time, but now that I have the EOS M I'm even more interested in shooting photos and video from above!

I know this is a forum for the technical aspects of getting ML working on the EOS M, but it would be great to hear from any other people out there who are using their EOS M (with ML) for interesting purposes.  One of the main reasons I got it was to do more HDR timelapses with it and save the shutter on my 5D2 (shooting five exposures for each frame burns through your shutter pretty darn fast!).  To that end, I also bought the Sigma 12-24 full frame lens so I could use it for wider timelapses on the EOS M but also still use it on the 5D2.  Problem is I don't want to take it off my 5D2 because 12mm rectilinear on a full frame camera gets some AMAZING photos (and for the record it works great on the EOS M also).  Of course when they announced the EF-M 11-22 lens a week after I bought the 12-24, I was kicking myself, but since I'm so happy with the 12-24 on my 5D2 I think I'll also get the 11-22 specifically for timelapses on my EOS M, assuming I can get my hands on that lens.  It's supposed to start selling tomorrow in Japan (according to Yodobashi's website), but won't be sold or supported in North America according to CanonRumors.  DOH!  Canon has also stated that it may not work properly on the old 1.0.6 EOS M firmware, and will need the new 2.0.2 firmware to work properly.  Which brings me back to the original statement above about how much we all love and appreciate you 1%!!!!
Title: Re: Tragic Lantern for EOS M
Post by: Michael L on July 14, 2013, 08:00:37 AM
Thanks, guys!

Whoah! That's some really good shot. Mind sharing what your kite rig looks like? How far was it to still be able to trigger with the IR?

The remote only had to travel about a millimeter....an LED coming out of a controller was velcroed right in front of the remote sensor.

Here's a photo of the rig with a NEX-5 on it.  Things have been swapped out and repositioned, but it is quite similar to this original configuration:

http://www.flickr.com/photos/kyteman/5485199056/

Hey jaybean, can you post a link or two to your timelapses?

Yeah 1%, thank you so much for your efforts to get the EOS-M wired for all our creative uses!


Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 14, 2013, 08:09:08 AM
That's a nice lookin' rig. Did you build it yourself? Or did you get it from somewhere? How does a kite handle the weight? (do you need a special kind of kite/line?)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 14, 2013, 04:10:21 PM
@1%:
can you tell me the exact vertical pixel offsets of the crop frame for the resolutions 1536x562 and 1600x576?
Sensor resolution is 5184×3456, so i guess they should be (3456-562)/2 = 1447 and (3456-576)/2 = 1440.
if i calculate the center for each resolution 1536/2 = 768, 562/2 = 281 => 768,281 and 1600/2 = 800, 576/2 = 288 => 800,288 and add the offsets, i should get the exact same sensor pixel, and that should be the one left top of the 4 center pixels (5184/2 = 2592, 3456/2 = 1728 => 2592,1728). if i use the calculated values it works: 281+1447 = 1728, 288+1440 = 1728.
but if i read the pixels from the dng it's 1 pixel vertically shifted. it seems that the vertical crop offset of 1600x576 is 1439 (instead of 1440) or the vertical crop offset of 1536x562 is 1448 (instead of 1447). can you check that and tell me which exact offsets are calculated in ml.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 14, 2013, 05:26:46 PM
The offsets have to be even, they may be different in crop mode. My plan is to re-check skips once new version is up and running.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 14, 2013, 05:35:45 PM
ah, ok, then i guess you round 1447 up to 1448, is that correct? i'll try that, thx!

EDIT:
it works... just finished a dot removal test for 73 different resolutions and they all do work perfect now.
Title: Re: Tragic Lantern for EOS M
Post by: Michael L on July 14, 2013, 08:45:25 PM
@Mixer2, thank you for your efforts also!  I have no idea what you guys are talking about, but I can tell good progress is being made.

@feureau,  I had that particular camera rig made custom for me, since it had to be as lightweight as possible to be lifted by a 5-foot diameter helium balloon.  Regular camera rigs that are not as weight sensitive can be purchased as reasonably priced, easy to build kits here:  http://www.brooxes.com/newsite/BBKK/KITS.html

If you decide to try it, I recommend that you use a cheap, light Canon point and shoot that runs CHDK (such as the A2200 or A2300) before you send your EOS-M skyward  ;-)

Lots more info at the Kite Aerial Photography discussion forum:  http://arch.ced.berkeley.edu/kap/discuss/

Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 14, 2013, 09:08:54 PM
Thank you very much!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 14, 2013, 11:35:45 PM
Crop mode toggle is in from nanomad but for some reason now I'm booting with a solid light. Bin from 6/27 works, compiling today doesn't.  :o
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 15, 2013, 12:44:07 AM
the most recent version of the dot remover:
https://dl.dropbox.com/s/77bkw4u9nh7dt4d/PinkDotRemover_2013_07_15.zip

@1%:
it would be great if camera model and if it's recorded in crop mode could be stored in the raw footer. maybe you can use some bits from reserved3 or reserved4? what are the reserved bits for? maybe this info should be generally added to the raw footer. at least the camera model would totally make sense to be stored in the meta information.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 15, 2013, 02:28:53 AM
Its supposed to be for silent DNG, guess not for raw video? Rawanizer seems to have the model.

EOSM in main is broken too, so not just me.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on July 15, 2013, 09:30:11 AM
The silent DNG contains the correct model, yes. But the raw video files doesn't contain the model information. Where does rawanizer get the model from? the raw footer contains:
magic, xRes, yRes, frameSize,  frameCount, frameSkip, sourceFpsx1000, reserved3, reserved4, raw_info
(https://bitbucket.org/hudson/magic-lantern/src/aa2ba85342faf956e8c85f514ca967ffb6f4a880/modules/lv_rec/lv_rec.h?at=unified)

char magic[4] is RAWM for all models. and raw_info contains:
api_version, buffer, height, width, pitch, frame_size, bits_per_pixel, black_level, white_level, crop (x, y, width, height), active_area (y1, x1, y2, x2), exposure_bias, cfa_pattern, calibration_illuminant1, color_matrix1, dynamic_range.
(https://bitbucket.org/hudson/magic-lantern/src/tip/src/raw.h)

really don't know where i should get the info about model out of that meta data. and  both silent dng and raw doesn't contain any information if it's recorded in crop mode or not.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on July 15, 2013, 09:51:57 AM
Its supposed to be for silent DNG, guess not for raw video? Rawanizer seems to have the model.

EOSM in main is broken too, so not just me.

We should really merge your changes then.  ::)
Either for the current fw or for the new 2.0.2
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 15, 2013, 02:51:28 PM
Some commit since 6/27 broke it, I pulled it from main. I can still load the latest released version.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on July 15, 2013, 08:15:06 PM
You can load ML on 2.0.2? I tried using the firmware in the first post on this thread but it didn't work
Title: Re: Tragic Lantern for EOS M
Post by: fand4ngo on July 15, 2013, 10:12:26 PM
You can load ML on 2.0.2? I tried using the firmware in the first post on this thread but it didn't work

ML for 2.0.2 sounds close, but not released yet.   Be patient.  My EOS M arrived today with 2.0.2, so there's plenty of people in the same boat.

On that note, I would be happy to test a pre-release if that were available.  *wink wink*
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on July 16, 2013, 02:22:08 AM
I'm new to the Magic Lantern community.

First, thanks to all of the people who have contributed to make this project a huge success!  Where would we be without you folks?

I just received the EOS-M with firmware 2.0.2 installed.  I am hoping that ML is ported to this firmware release as I too would like to:

"I want to perch this thing on my telescope and take some wide-sky astrophotos with the 22mm f/2 lens, and ML's intervalometer and bulb control are just what I need."

Question:  Did the original ML port for the previous firmware release support tethered shooting?  This is a very important missing piece of functionality from the EOS-M.  It would be GREAT if tethered shooting (e.g. camera controlled remotely via USB cable from a computer) could be made to work.

Again, thanks so much for all of your efforts...  they are truly appreciated!
Title: Re: Tragic Lantern for EOS M
Post by: Eisland on July 16, 2013, 01:30:40 PM
Hey guys,

I bought 5 EOS M to record classical concerts... but with me, the automatic movie restart stopps after about 20min. recording time.
I use a Sandisk 64GB memory card. Could anybody help me with that issue?? I have 2 weeks, and then it should work... and I am losing hope right now, as I tried everything to prevent the video from stopping...

Best regards,
Kevin
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 16, 2013, 01:58:38 PM
Hey guys,

I bought 5 EOS M to record classical concerts... but with me, the automatic movie restart stopps after about 20min. recording time.
I use a Sandisk 64GB memory card. Could anybody help me with that issue?? I have 2 weeks, and then it should work... and I am losing hope right now, as I tried everything to prevent the video from stopping...

Best regards,
Kevin

Hi, Kev.
Without ML, it should record up to 29.59. Have you tried this?

The movie restart with ML wouldn't go past 29.59.  They found the way to do make continuously record past 29.59 (no gaps in recording) it was on one of the older builds,  but the team decided that they won't have an ML that lets you bypass the 29.59.
Title: Re: Tragic Lantern for EOS M
Post by: cafaidy on July 16, 2013, 02:52:24 PM
Hey guys,

I bought 5 EOS M to record classical concerts... but with me, the automatic movie restart stopps after about 20min. recording time.
I use a Sandisk 64GB memory card. Could anybody help me with that issue?? I have 2 weeks, and then it should work... and I am losing hope right now, as I tried everything to prevent the video from stopping...

Best regards,
Kevin

Hi

The best solution I can find is (if ML don't work): deferred record of 3 eos-m for editing the film (multicam) and switch a camera to another when it stops
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 16, 2013, 03:13:16 PM
I found my bug so I'll start working on upgrading to 2.0.2 soon.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 16, 2013, 03:40:57 PM
I found my bug so I'll start working on upgrading to 2.0.2 soon.

Have I told you lately that I love you? :D
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 16, 2013, 03:43:26 PM
Hi

The best solution I can find is (if ML don't work): deferred record of 3 eos-m for editing the film (multicam) and switch a camera to another when it stops

I think it's the best solution so far. Shoot without ML for such an important event.

I had EOS-M ML crashed on me in the middle of a forest. The screen would just purple'd and I had to pull out the battery. Then it'd happen again and again in the middle of shooting. Ended up formatting the card and shooting without ML. There's still some bugs in there to iron out, but no biggie. It's the risk of running nightly.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 16, 2013, 04:03:16 PM
What version? And how to reproduce that.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 16, 2013, 06:39:48 PM
What version? And how to reproduce that.

It was from tragic lantern. I don't remember which version. It was like, from 2-3 days before firmware 2.0.2 came out.

It happened in the field at a critical time. I was time-pressed to get a shot.

Turn it on, focused, and the live view froze with a purple image stretched/warped/interlaced looking. The camera just froze entirely, nothing works, pushing the on/off button wouldn't turn off. Pulled out the battery, put it back in. Boots up like usual. Half-press focus, camera focuses. Takes shot, purple stretched-image-interlaced screen.

Tried this like 5 times. Happens every time. Had to pop in a non-ML card. Works fine like normal.

When I got back, I looked for error logs, but nothing wrong with it. Tried booting, took a shot, works fine like normal ML. Couldn't reproduce it. Formatted the card and reinstalled ML to make sure. Haven't had that since.

Not sure what happened there.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on July 17, 2013, 05:45:07 AM
I found my bug so I'll start working on upgrading to 2.0.2 soon.

You're the BEST!  Thanks!   :)
Title: Re: Tragic Lantern for EOS M
Post by: cafaidy on July 17, 2013, 11:01:20 AM
I found my bug so I'll start working on upgrading to 2.0.2 soon.

The best of the world of universe of of ..... : 1%
Title: Re: Tragic Lantern for EOS M
Post by: HoveyWanKenobi on July 18, 2013, 03:31:50 AM
I found my bug so I'll start working on upgrading to 2.0.2 soon.
Hey 1% I'm new to Magic Lantern and the Forums here but I'm interested in helping out if I can. Just got an EOS M and would like to get ML installed but also running on 2.0.2. I work in the Comp Sci field and would be happy to lend a hand at trying to work out the bugs for a 2.0.2 release. Let me know how I can help out.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 18, 2013, 03:42:38 AM
Heh, I have a whole building to install systems in so this is on the back burner a bit for next 2 weeks. I'll try to get what I can done when I'm not working though. I'm out there like 10 hours so its kinda hard to get lunch, much less code :(

Here is how its going to go:

1. Stubs
2. Consts
3. Figure out an installer so you can boot flag 2.0.2 cameras since there is no downgrade.
If you already had ML it will be easy as the boot flag stays an you just update and get new bins.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on July 18, 2013, 06:11:24 AM
I haven't been active on this spot for very long since I have been traveling. The first thing I did on my return was to update the firmware to 2.0.2 since I wanted to feel the difference in AF capabilities in real time. I am disappointed to say the least. The lens does latch on faster but still struggles in low contrast situations - pulling focus but not struggling to find the sweet spot. If this is all the Canon staff was able to come up with in so many months - not sure where the entire mirror less adventure is heading.

Plus, I now don't have ML for this version. 1% will eventually come up with the right stuff. The one thing I really miss not having is the focus peaking advantage. My manual focus Minolta Rokkor 50mm f1.2 just is not good just no good without the peaking facility.

So, I am taking a few days off the EoS M and gogin back to my 5DMIII for now. A bit of disappointing news here too. I ordered the most expensive Komputerbay CF card money can buy only to find that the cheaper option is better. The 128GB card cannot handle 1920p video. Max 130 frames with 1 -2 dropped frames.

I think there is still a way to go with the RAW on DSLR's thing and The EoS M is not even an SLR.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on July 18, 2013, 09:25:25 AM
I haven't been active on this spot for very long since I have been traveling. The first thing I did on my return was to update the firmware to 2.0.2 since I wanted to feel the difference in AF capabilities in real time. I am disappointed to say the least. The lens does latch on faster but still struggles in low contrast situations - pulling focus but not struggling to find the sweet spot. If this is all the Canon staff was able to come up with in so many months - not sure where the entire mirror less adventure is heading.

Plus, I now don't have ML for this version. 1% will eventually come up with the right stuff. The one thing I really miss not having is the focus peaking advantage. My manual focus Minolta Rokkor 50mm f1.2 just is not good just no good without the peaking facility.

So, I am taking a few days off the EoS M and gogin back to my 5DMIII for now. A bit of disappointing news here too. I ordered the most expensive Komputerbay CF card money can buy only to find that the cheaper option is better. The 128GB card cannot handle 1920p video. Max 130 frames with 1 -2 dropped frames.

I think there is still a way to go with the RAW on DSLR's thing and The EoS M is not even an SLR.

I just don't understand why canon can't provide the peaking focus and auto focus area magnifier in their firmware. Olympus is pushing great firmware upgradings again and again with all the necessary functions. What is canon doing?
Title: Re: Tragic Lantern for EOS M
Post by: cafaidy on July 18, 2013, 10:01:18 AM
Heh, I have a whole building to install systems in so this is on the back burner a bit for next 2 weeks. I'll try to get what I can done when I'm not working though. I'm out there like 10 hours so its kinda hard to get lunch, much less code :(

Here is how its going to go:

1. Stubs
2. Consts
3. Figure out an installer so you can boot flag 2.0.2 cameras since there is no downgrade.
If you already had ML it will be easy as the boot flag stays an you just update and get new bins.

Thanks and good luck!
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on July 18, 2013, 03:02:11 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Rush on July 19, 2013, 10:11:46 AM
Sorry if I'm stating bug that is known:
Jun27 build, if I use fps override and it is not = 23.976 fps - it will produce black border from right side.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 19, 2013, 03:38:45 PM
Maybe the image shifts? I saw this on 6D early on. Skips would change with fps override. No point in messing with it too much as it might behave differently depending on what the new fw changed.
Title: Re: Tragic Lantern for EOS M
Post by: Rush on July 19, 2013, 04:35:22 PM
Maybe the image shifts? I saw this on 6D early on. Skips would change with fps override. No point in messing with it too much as it might behave differently depending on what the new fw changed.
Just checked - no, it looks like overlay border (which is recorded too).
If I turn off to mode without border - border place become like pink "lightup/add/screen/you name it" semi-transparent overlay for a few seconds, slowly disappearing...

(sorry again if it is known but:)
little bug in latest experimental 3x crop-mode raw recording - in 3x crop mode it thinks that it need to be unsqueezed and sets wrong resolution (it don't need unsqueezing for real).
Title: Re: Tragic Lantern for EOS M
Post by: Henrik on July 20, 2013, 02:04:38 PM
Hello everyone!

I bought an Eos M about a month ago, upgrading from a 450D, mainly for the video feature. I found out about ML, and have been reading here pretty much daily ever since. Thank you for a great job!

I've done my homework, and I would say I understand most of the features provided by ML, with a few exceptions. And thats what Im about to ask about!

Ive searched the forum and the rest of the internet for how to capture HDR-video with the Eos M, without any result. Or am I just stupid?!
If someone could reveal this well hidden secret, I would be a very happy man.

Thanks in advance, and again, good job!

Henrik
Sweden
Title: Re: Tragic Lantern for EOS M
Post by: Digital Guy on July 20, 2013, 03:36:12 PM
Ive searched the forum and the rest of the internet for how to capture HDR-video with the Eos M, without any result.
If someone could reveal this well hidden secret, I would be a very happy man.

You'll see there is no stable release for the EOS-M. The latest Canon firmware 2.0.2 is installed with all new EOS-M sold so there's no Alpha build for it at the moment. I really like the HDR video feature as well as intervelometer function on my Canon 60D. I'm waiting with baited breath for the ML for the EOS-M ::)
Title: Re: Tragic Lantern for EOS M
Post by: Henrik on July 20, 2013, 04:26:15 PM
You'll see there is no stable release for the EOS-M. The latest Canon firmware 2.0.2 is installed with all new EOS-M sold so there's no Alpha build for it at the moment. I really like the HDR video feature as well as intervelometer function on my Canon 60D. I'm waiting with baited breath for the ML for the EOS-M ::)

I've got the old firware with the alpha build installed already. Sorry for being fuzzy.
I've found videos on Youtube ( ) showing HDR video footage shot with the Eos M, but I cant find anything about it in the ML menus, even though I've spent hours just trying out the different settings.
There are several youtube tutorials for how to shoot HDR video with ML, but none of them are for Eos M, and all of the others seem to have a "HDR video"-option under the movie tab in ML.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 20, 2013, 05:12:01 PM
HDR video option is there in the movie menu.
Title: Re: Tragic Lantern for EOS M
Post by: Henrik on July 20, 2013, 05:45:55 PM
HDR video option is there in the movie menu.

I've got the following in the movie menu:
Bit Rate (CBR)
Time indicator
Movie logging
Movie restart
Stop recording
REC/STBY key
Shutter lock
Image effects...
FPS override
FPS ramping

 :-\
Title: Re: Tragic Lantern for EOS M
Post by: fand4ngo on July 21, 2013, 04:36:19 AM
Could someone post all of the main options in each menu from the ML firmware that are turned on in the EOS M?  I'd like to know (specifically) if the intervalometer is in before my return window runs out.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on July 21, 2013, 09:17:02 AM
such a great news for us. THANKS 1% with all my heart...
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 21, 2013, 03:20:27 PM
Don't know if its in alpha 1 but its in my builds.
Title: Re: Tragic Lantern for EOS M
Post by: Henrik on July 21, 2013, 07:01:07 PM
Found the link to the newer versions in post #507. Awesome!

Thanks man!
Title: Re: Tragic Lantern for EOS M
Post by: Digital Guy on July 22, 2013, 06:21:34 AM
Found the link to the newer versions in post #507. Awesome!

Where exactly is the "newer version"? Are you talking about the EOS-M?
Title: Re: Tragic Lantern for EOS M
Post by: merp on July 22, 2013, 10:09:43 AM
fand4ngo,

The intervalometer function in ML is supported on the EOSM. It was the main reason I installed ML on mine :)
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on July 22, 2013, 02:57:15 PM
@1% Could you consider adding disable touch screen wake up function in the next ML version? I often hang the EOS M on my neck and it is always waked up because my stomach touched the LCD.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 22, 2013, 03:58:25 PM
@1% Could you consider adding disable touch screen wake up function in the next ML version? I often hang the EOS M on my neck and it is always waked up because my stomach touched the LCD.

That is a ... weird behavior. I hang my EOS-M around my neck too, but mine doesn't wake up when the LCD gets touched...
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on July 22, 2013, 03:59:45 PM
That is a ... weird behavior. I hang my EOS-M around my neck too, but mine doesn't wake up when the LCD gets touched...

It's may because I only wear one T shirt
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 22, 2013, 05:53:46 PM
It's may because I only wear one T shirt

Oh, I completely get that part. If I leave the LCD on while wearing thin garments, it would get detect touch events. But if the EOS-M is asleep, it wouldn't wake up just because the LCD senses a touch.

Also, do you have the sensitivity set to sensitive or default?
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on July 22, 2013, 06:26:49 PM
Oh, I completely get that part. If I leave the LCD on while wearing thin garments, it would get detect touch events. But if the EOS-M is asleep, it wouldn't wake up just because the LCD senses a touch.

Also, do you have the sensitivity set to sensitive or default?

Yes I set it to default. But still very sensitive. Especially with the 22mm lenses because it's too light and thus the camera hangs to the stomach.
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on July 22, 2013, 10:10:08 PM
I'm new here.  This is quite interesting.  It's my first Canon EOS mirrorless (except my Panasonic GF2), and I just purchased a brand new  body today for $240 - hoping to use my legacy lens w/ adapter.  I like to know what are the benefits of ML in terms of image quality and better low light capabilities.  Shocked to find out that it has the sensor of T4i/7D.

I will check back here for developments.
Title: Re: Tragic Lantern for EOS M
Post by: Drizzt321 on July 22, 2013, 11:07:41 PM
Just got my EOS-M, and wouldn't you know it, it's firmware v2.0.2 :(   Hopefully 1% can get the alpha loading up on it soon. I need to start learning the timelapse/intervalometer on this camera so I can use it at the end of August.
Title: Re: Tragic Lantern for EOS M
Post by: Henrik on July 23, 2013, 07:30:53 PM
Where exactly is the "newer version"? Are you talking about the EOS-M?

Yes, Eos M. Newer than the one in the first post. If you go back to page 21 in this thread you'll find a link in post #507.
Title: Re: Tragic Lantern for EOS M
Post by: Eisland on July 26, 2013, 03:23:02 PM
Hi guys,

first of all, thank you for your responses that helped me a lot...!!!

I am the guy who wants to use the EOS M with automatic movie restart function.... but as somebody pointed out (thank you!) this does not work with newer versons of ML... Is it possible to use an older version where this function is not disabled with the EOS M yet?
If yes, could you point me towards a downloadlocation?
That woul really be great!

Thank you,
all the best to you helpful guys!!!!!
Title: Re: Tragic Lantern for EOS M
Post by: jgrauman on July 26, 2013, 06:06:19 PM
Hello all,

I'm completely new to ML and was thinking of getting a EOS M camera. The main thing I want it for is to shoot 1080p video with an external mic. The only feature I need that is different than the stock firmware is to get rid of the 29 minute recording limit (I need to record around 1 hr). Would ML get rid of this? Is it pretty stable for the EOS M? Thanks so much!

Josh
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 26, 2013, 07:13:06 PM
EOS-M Does have external mic input.

ML did discover a way to circumvent the 29.59 recording limit, however the dev team decided that this is not a feature they want in ML and scrapped that ability. EOS-M ML is still limited to 29.59. For continuous long recording time, you're better off with a proper camcorder.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on July 26, 2013, 07:17:16 PM
This thread has been muted for more than a week and finally see some buzz today. Any news for the 2.0 firmware?
Title: Re: Tragic Lantern for EOS M
Post by: thegunshow101 on July 27, 2013, 12:39:18 AM
Hello all,

I'm completely new to ML and was thinking of getting a EOS M camera. The main thing I want it for is to shoot 1080p video with an external mic. The only feature I need that is different than the stock firmware is to get rid of the 29 minute recording limit (I need to record around 1 hr). Would ML get rid of this? Is it pretty stable for the EOS M? Thanks so much!

Josh

I use ML to record long periods but via the HDMI output.. ML gives me a clean output and stay on forever, then I use a HDMI recorder with a Hard Drive.. (currently Atomos Ninja) to record 7-8 hour events..  It effective but more parts and cost than a single device.

Its a little weird that ML took off the ability to record longer than 30 minutes direct to card. There has to be an untold reason.. (Although this still wouldn't work for me as SD card sizes would be far too limiting for multi hour events)
Title: Re: Tragic Lantern for EOS M
Post by: jgrauman on July 27, 2013, 01:16:14 AM
That makes sense and I'm glad to hear you can get clean hdmi out with this camera. I don't need to record too long, only 60 minutes. Maybe they left in the 30 min limit due to overheating concerns? In any case, getting rid of the limit would be super nice for me, so if anyone has more info and there is a possibility of the limit being removed again, that would be great.

Josh

I use ML to record long periods but via the HDMI output.. ML gives me a clean output and stay on forever, then I use a HDMI recorder with a Hard Drive.. (currently Atomos Ninja) to record 7-8 hour events..  It effective but more parts and cost than a single device.

Its a little weird that ML took off the ability to record longer than 30 minutes direct to card. There has to be an untold reason.. (Although this still wouldn't work for me as SD card sizes would be far too limiting for multi hour events)
Title: Re: Tragic Lantern for EOS M
Post by: DaveNYC on July 27, 2013, 04:01:40 AM
Maybe they left in the 30 min limit due to overheating concerns? In any case, getting rid of the limit would be super nice for me, so if anyone has more info and there is a possibility of the limit being removed again, that would be great.


+1

I don't know why the limit is there but would really appreciate removing it (when the 2.0.2 firmware is running ML). I have successfully triggered several consecutive 29 minute recording sessions in a row (starting the next as soon as the prior one ends) so I don't see overheating being the issue.  I only need it for 45 minutes to an hour at a stretch but it's going to be in a location I won't be able to get to easily and I'm going to be shooting stills independently so it's going to be a pain to have to track how long the M has been recording video for as well.

Please allow the option. It's a major reason why I got the M.
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on July 27, 2013, 05:28:41 AM
That makes sense and I'm glad to hear you can get clean hdmi out with this camera. I don't need to record too long, only 60 minutes. Maybe they left in the 30 min limit due to overheating concerns? In any case, getting rid of the limit would be super nice for me, so if anyone has more info and there is a possibility of the limit being removed again, that would be great.

Josh


So it's possible to use the HDMI out and put a monitor like a Liliput or SmallHD in it?  Just asking.  :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on July 27, 2013, 09:39:49 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 27, 2013, 09:08:45 PM
I hope they put back removing the 30 minute limit record time. I would love to hear the reason why it was removed. Some major technical reason? Make it a user pref to have it on off.

does anyone know the status on getting ml working on the M firmware 2.0.2?

gary

Not for technical reasons. They got it working smoothly across several bodies. It's out on some older nightly build.

Devs working on 2.0.2. We're just waiting for a building to get wired. :D *sits patiently*
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on July 27, 2013, 09:22:01 PM
Not for technical reasons. They got it working smoothly across several bodies. It's out on some older nightly build.

Devs working on 2.0.2. We're just waiting for a building to get wired. :D *sits patiently*

That's good to know.  I just got my Minolta MD/EOS M adapter today and did some video shots pre ML.  Really impressive so far.  Can't wait to see what comes up next.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 27, 2013, 09:56:25 PM
Oh, you're gonna love shooting videos with ML on this baby. :D Just wait.
Title: Re: Tragic Lantern for EOS M
Post by: mountain_drew on July 28, 2013, 01:08:52 AM
Just created an account to say that I'm looking forward to ML for the newest firmware! I wish I could help somehow...
Title: Re: Tragic Lantern for EOS M
Post by: Digital Guy on July 28, 2013, 07:27:28 AM
Did some video test shoots with my FD-EOSM adapter using an FD 85-300mm and Canon standard FD 50 1.8. I'm really impressed with this mirrorless camera. With ML install on the EOSM I'll be walking on the clouds.
Title: Re: Tragic Lantern for EOS M
Post by: jgrauman on July 28, 2013, 09:28:29 AM
Another question, this time about using a DSLR controller over USB such as the one at dslrcontroller.com. It lists a bunch of newer cameras as compatible, but the EOS M as not compatible. Does anyone know if this is a firmware issue? Would there be any chance that ML would fix this? Thanks!

Josh
Title: Re: Tragic Lantern for EOS M
Post by: waters on July 28, 2013, 10:50:32 AM
With the AF lens,I can touch the screen and move the red focus box. at this time the ML magic zoom is so useful.
When i use the adopter with the M42 MF len on my eos m , I can't find the litte focus box on screen.I think CANON locks the red focus box when the body can't find the Af lens.
Now, Ml magic zoom can only focus the center of screen.

when we use the MF Lens, Can the ml develop group unlock the CANON program and let the focus box out  ?


Thanks  a lot
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on July 28, 2013, 04:32:02 PM
With the AF lens,I can touch the screen and move the red focus box. at this time the ML magic zoom is so useful.
When i use the adopter with the M42 MF len on my eos m , I can't find the litte focus box on screen.I think CANON locks the red focus box when the body can't find the Af lens.
Now, Ml magic zoom can only focus the center of screen.

when we use the MF Lens, Can the ml develop group unlock the CANON program and let the focus box out  ?


Thanks  a lot

You can actually use a focus box with manual focus lenses without AF information in ML
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 28, 2013, 05:48:08 PM
I think you have to be in single zone focus to use the focus box. Either way MZ is off sync. Hopefully canon changed something about this. It should have something done to it as M was focusing at 60FPS.
Title: Re: Tragic Lantern for EOS M
Post by: Eisland on July 29, 2013, 11:17:59 AM
is it possible to use an older magic lantern build where automatic movie restart is not yet disabled together with the eosm106.fir? or are the version of ml and the eosm106.fir codependent? I neeeed the automatic movie restart... nothing else of ML   ;(

thank you!
kevin
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 29, 2013, 02:56:10 PM
Its not disabled in latest bins. Hasn't been for months.
Title: Re: Tragic Lantern for EOS M
Post by: millernet on July 29, 2013, 04:23:03 PM
You can actually use a focus box with manual focus lenses without AF information in ML

Do you get the green focus confirm bars on EOS-M?
Title: Re: Tragic Lantern for EOS M
Post by: waters on July 29, 2013, 05:38:19 PM
You can actually use a focus box with manual focus lenses without AF information in ML

Please tell me how to active the focus box and move it.  :)
Title: Re: Tragic Lantern for EOS M
Post by: waters on July 29, 2013, 05:39:53 PM
Do you get the green focus confirm bars on EOS-M?

With the MF lens, never see the focus box ,never see the green focus confirm bars.
Title: Re: Tragic Lantern for EOS M
Post by: waters on July 29, 2013, 05:48:26 PM
I think you have to be in single zone focus to use the focus box. Either way MZ is off sync. Hopefully canon changed something about this. It should have something done to it as M was focusing at 60FPS.

Can i move the focus box any where just like Canon 5d ii liveview funcation?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 30, 2013, 02:55:48 AM
You can move it around with your finger, it was nice when MZ worked (use slightly older version, its in sync).

I didn't try on manual lenses tho. On other cameras there are UD/LR keys an you can force moving it, here that doesn't work.

Maybe a work around will be drawing ML graphics over 1x mode which has a focus box always.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on July 31, 2013, 07:43:37 PM
I have taken more than 200 photos today by my EOS M fireware 2.0 with the FD 50mm f/1.4 but unfortunately more than 20% of them are not accurately focused. It is really very hard to focus fast and accurately with the MF lense. We need ML for the 2.0 firmware so bad!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 31, 2013, 07:45:16 PM
Yep, soon as I can. Early adopters will be able to go from 1.x-> 2.0 and have ML. 2.0 people will have to wait for an installer :(

I'll try to find more stubs tonight.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on July 31, 2013, 08:07:23 PM
If you can port to the 2.0.2 firmware release and also unlock Remote Shooting via the EOS Utility you will be considered a God!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 31, 2013, 08:12:45 PM
Don't think its locked, probably not supported because eos M LV is 60P sized at 30fps.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on July 31, 2013, 08:20:34 PM
If the EOS-M LiveView is 60P sized at 30fps what would it need to be in order to work?  (What does 60P mean?)
Title: Re: Tragic Lantern for EOS M
Post by: feureau on July 31, 2013, 08:24:48 PM
Don't think its locked, probably not supported because eos M LV is 60P sized at 30fps.

Speaking of remote shooting. Is the EOS-M the only one without this feature? (can the 650D shoot remotely?)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 31, 2013, 08:31:19 PM
60P is the 60FPS mode on other cameras. What would be needed to make it work is probably support for this gimpy mode in eos utility. That is likely the reason its disabled, also it may not be making the preview stream to send to eos utility at all since its underpowered and they made every effort to skimp on processing (ie, not having a real idle LV at 24fps except crop mode).

Check on 650D ( I dont have one).
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on July 31, 2013, 08:45:10 PM
60P is the 60FPS mode on other cameras. What would be needed to make it work is probably support for this gimpy mode in eos utility. That is likely the reason its disabled, also it may not be making the preview stream to send to eos utility at all since its underpowered and they made every effort to skimp on processing (ie, not having a real idle LV at 24fps except crop mode).

Do you think it could be made to work on the EOS-M?  How much effort would it take?

I'm sure more than just a few people would love the capability to shoot remotely, particularly those who are into astrophotography.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 31, 2013, 09:13:07 PM
Depends whats up with 2.02.. if it still has jacked up LV and doesn't work without any other usb live preview, probably not.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on July 31, 2013, 09:43:19 PM
Depends whats up with 2.02.. if it still has jacked up LV and doesn't work without any other usb live preview, probably not.
Gotcha.  Where does this fit in the list of priorities?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on July 31, 2013, 10:58:17 PM
Below MZ working well again.
Title: Re: Tragic Lantern for EOS M
Post by: fand4ngo on August 01, 2013, 12:58:47 AM
2.0 people will have to wait for an installer :(

If you need someone to test an installer, just let me know.
Title: Re: Tragic Lantern for EOS M
Post by: Drizzt321 on August 01, 2013, 02:03:23 AM
Below MZ working well again.

If you've got a prototype build for 2.0.2 I'll be happy to test for you. I've got 48 hour film festival this weekend, and it'd be cool to add EOS-M to my 5d2/5d3 for shooting, and ML would really help with that. I'm willing to risk bricking it.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 01, 2013, 03:01:34 AM
Yea, its not going to take 1 day. I just reorganised stubs and found adtg shutter, it cleans up FPS sprinkles/lines but timings are too loose, have to set manually. So one bug down, can get some time lapse out of this thing finally.

Next up porting. Fingers crossed for display filters/mz.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 01, 2013, 07:10:11 AM
Hooray!

*crosses finger*
Title: Re: Tragic Lantern for EOS M
Post by: manly on August 01, 2013, 07:25:41 AM
Hi! I'm one of the many who bought an EOS M with last months 300$ deal and is just getting started in photography. I've been following this thread ever since. I understand ML is mostly geared towards recording enthousiasts moreso than people looking forward a more configurable firmware. I was wondering if by any luck ML can be used to fix the (forgive my french) god-awful EOS M AF speed (for pictures)?

I could be wrong but I do often have the impression from the stock 2.02 firmware that even in single-target focus mode it keeps on going too far to determine something is beginning to get out of focus and loses a lot of time there. As such, I assume the slow AF is in major part slowed down by the firmware. In any case, thanks again for any response from the more knowledgeable people.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 01, 2013, 08:16:13 AM
I understand ML is mostly geared towards recording enthousiasts moreso than people looking forward a more configurable firmware.

Not exactly. It's just that the photography features of ML so mature that most of the talk tends to gyrate towards the rather newly developed video features such as fps, hdr, and raw vids.

I was wondering if by any luck ML can be used to fix the (forgive my french) god-awful EOS M AF speed (for pictures)?

I could be wrong but I do often have the impression from the stock 2.02 firmware that even in single-target focus mode it keeps on going too far to determine something is beginning to get out of focus and loses a lot of time there. As such, I assume the slow AF is in major part slowed down by the firmware. In any case, thanks again for any response from the more knowledgeable people.

Upgrade to 2.0.2. This fixes the slow AF problem. Don't expect DSLR AF speed, nothing on this planet beats OVF phase detection. Yet.

But I can tell you this anecdote: it's a lot more sensitive in low light than the 60D. I was at a birthday party a few weeks ago, I had my EOS-M with adapter and a friend used the 60D. There's this one group shot that the 60D just wouldn't autofocus because it was too damn dark. They handed me the 60D, I played around with it, it just wouldn't lock focus. Instead of switching to manual, I decided to pop the lens to my EOS-M, and it immediately locks focus and fired. Switched to multishot NR and the resulting pic looks as good as it was shot on ISO100.

Couldn't be happier.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 01, 2013, 01:11:23 PM
@1% fingers on my hands and toes are crossed  :)
Title: Re: Tragic Lantern for EOS M
Post by: whohitme on August 01, 2013, 06:04:39 PM
I'm just getting into using ML for my 5DII, and would love it on the M I just bought. Thanks for the hard work. Would love to see the EOS utility work if possible as well. Watching this closely.
Title: Re: Tragic Lantern for EOS M
Post by: wuxiekeji on August 01, 2013, 07:00:48 PM
If you've got a prototype build for 2.0.2 I'll be happy to test for you. I've got 48 hour film festival this weekend, and it'd be cool to add EOS-M to my 5d2/5d3 for shooting, and ML would really help with that. I'm willing to risk bricking it.

+1 I just got in on the EOS-M deal and using it mostly for fooling with alt MF lenses. Hoping to get the zoom box back that I am so used to on the 60D
Title: Re: Tragic Lantern for EOS M
Post by: Drizzt321 on August 02, 2013, 01:48:53 AM
Yea, its not going to take 1 day. I just reorganised stubs and found adtg shutter, it cleans up FPS sprinkles/lines but timings are too loose, have to set manually. So one bug down, can get some time lapse out of this thing finally.

Next up porting. Fingers crossed for display filters/mz.

Ah well. A person can hope, right? Anyway, awesome, keep up the great work and do what you gotta do!


+1 I just got in on the EOS-M deal and using it mostly for fooling with alt MF lenses. Hoping to get the zoom box back that I am so used to on the 60D

Yea, I actually have 2 adapters coming for tomorrow, an MD mount (no corrective optics FTW!) and m42 mount adapters so that I can use some of my old lenses. I've got a nice 28mm f/2.8 MD lens that'll probably look pretty sweet, and a 55mm f/2.8 Macro in m42, and a 135 f/3.5 in m42 along with my bellows and I could have a pretty sweet Macro setup that's relatively light and puts a lot of pixels right on target :)
Title: Re: Tragic Lantern for EOS M
Post by: manly on August 02, 2013, 07:45:30 AM
[...]
Upgrade to 2.0.2. This fixes the slow AF problem. Don't expect DSLR AF speed, nothing on this planet beats OVF phase detection. Yet.
[...]
But I can tell you this anecdote: it's a lot more sensitive in low light than the 60D.
I might not have the experience of a professional photographer but I did also note that the 22mm pancake was amazing at taking good pictures even in really low lighting with no flash. One of the reasons I am fairly certain I will resell the speedlight flash that came with the kit (selling for half the price I paid the entire kit?!)

I did upgrade to 2.0.2. I was simply pointing out that it feels like it over/under focuses before coming back to the 'optimal' focus. If the in-focus detection settings were set more aggressively it could save valuable focus time. Additionally, such a setting could also help with the 'couldn't find anything to focus on' problem I seem to have every now and then. I'd be welcome to see/hear if you would agree with that.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 03, 2013, 07:29:43 PM
Dose anyone use tapatalk to follow this topic? Why it recently says I don't have the permission necessary to get notifications from this topic?

Besides, any news about the 2.0 version?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 03, 2013, 08:01:38 PM
I booted it today... I have some memory problems, exmem doesn't work and allocate has an extra 0 at the end.

Fixed MZ.. I wonder if I can sync display filters from this.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 03, 2013, 08:19:46 PM
I booted it today...
Fixed MZ.. I wonder if I can sync display filters from this.

Yay! \o/
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 03, 2013, 09:55:28 PM
New to this board but have been following for awhile. Just bought the EOS-M deal to add to my Canon camera collection and am following keenly on 2.02 ML firmware update for EOS-M as I want the timeplapse function.

Keep up the good work @1% and looking forward to 2.02
Title: Re: Tragic Lantern for EOS M
Post by: vadim_s on August 04, 2013, 01:22:37 AM
Been following this thread for weeks and itching to get ML on my eos-m.  Wanted to post up and say thanks to 1% and the ML team for everything and that I would be happy to pitch in a bit for all yours guys time whenever this is ready or even now.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 02:07:05 AM
Its usable now, needs a few more stubs and of course the installer.

I'm on 2.0.2 now and can't go back... still same issues with display filter but MZ is good except for crop mode.. canon really did fix the focusing.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 04, 2013, 02:27:59 AM
Hooray!!! :D

Congrats, 1%!!!

We the 99% salutes you!
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 04, 2013, 03:16:00 AM
Its usable now, needs a few more stubs and of course the installer.

I'm on 2.0.2 now and can't go back... still same issues with display filter but MZ is good except for crop mode.. canon really did fix the focusing.

Hope we can use it this weekend
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 03:20:38 AM
If you boot flagged, you can compile already/upgrade/use it.

Whats missing right now is stubs for TP log/audio (giving it another go) and bitrate, also raw rec/display timer needs some addys changed.
Title: Re: Tragic Lantern for EOS M
Post by: KSphoto on August 04, 2013, 03:46:31 AM
Thanks 1%! I'm really excited to get ML on my new EOS M.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 04, 2013, 06:15:13 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 07:04:16 AM
No installer yet for 2.02.. if you had v1 you could upgrade and just compile ATM.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 04, 2013, 07:19:54 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 04, 2013, 07:36:47 AM
Thank you so much, 1%.

 :)

I upgraded to 2.0.2 because it really focuses faster & better than before.

Now waiting for ML. More possibilities just like before... :D
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 04, 2013, 03:27:58 PM
No installer yet for 2.02.. if you had v1 you could upgrade and just compile ATM.

Checked out from bitbucket. is this the same as the EOSM.106?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 03:58:11 PM
Almost every address is different: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/src/dad2c62000306bf9eb887f10e54dbcd76837e2d1/platform/EOSM.202?at=unified
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 04, 2013, 04:10:01 PM
1%, can you upload a precompiled version. don't want to install more than a gig of dependencies just for a single compilation.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 04:47:14 PM
Yep, just let me make sure the video stuff works.

It does, prop browser is hanging things for some reason so took it out:

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 04, 2013, 04:49:30 PM
Yep, just let me make sure the video stuff works.
Awesome!  Does that mean we're within a few days of the first "alpha" release for the firmware 2.0.2 update?

Keep up the great work!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 04, 2013, 04:51:54 PM
ah, ok nice! thx
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 04, 2013, 05:14:40 PM
ah, ok nice! thx

This is a "no-installer" version, right?  How do we "install" it on our cameras?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 05:16:43 PM
Try this from <32gb card... may or may not be detected:

http://www.qfpost.com/file/d?g=7z9GGGKZk (http://www.qfpost.com/file/d?g=7z9GGGKZk)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 04, 2013, 05:52:32 PM
update worked fine. there is no full time crop mode so far, is it?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 05:53:53 PM
Movie menu: video crop mode: on.

Someone let me know if the boot flag firmware is good.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 04, 2013, 06:05:45 PM
Someone let me know if the boot flag firmware is good.

I can load it through firmware, but as soon as theupdate screen loads, the screen goes blank and the green indicator light blinks rapidly.
Had to battery pull or it would just green-light-blinking-rapidly every time I start up the camera.


I don't think any flag was set. Couldn't boot to ML.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 06:09:08 PM
Sucks, 6D does something similar. Maybe the signing server isn't right?
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 04, 2013, 06:11:42 PM
I can load it through firmware, but as soon as theupdate screen loads, the screen goes blank and the green indicator light blinks rapidly.
Had to battery pull or it would just green-light-blinking-rapidly every time I start up the camera.


I don't think any flag was set. Couldn't boot to ML.

Same for me. The screen goes blank and the green light keeps blinking. Have to pull the battery out. Tried everything and more no success yet.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 04, 2013, 06:22:26 PM
ah hadn't noticed, that full time crop moved from "don't click me" to an extra menu item. thx!
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 04, 2013, 06:25:20 PM
@mixer2 how do you boot to your card btw?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 04, 2013, 06:33:32 PM
bootflag is still set from prior version...
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 04, 2013, 06:37:43 PM
bootflag is still set from prior version...

I knew I shouldn't've formatted my cards :/
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 07:07:26 PM
If you had a normal ML on 1.0 then your boot flag in the camera is still set. But new people that started at 2.02 are out of luck at the moment till I figure out wtf is wrong with the installers.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on August 04, 2013, 07:09:21 PM
make build_fir, then upload updater.bin to the signing server. This worked for 650D.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 04, 2013, 07:17:00 PM
If you had a normal ML on 1.0 then your boot flag in the camera is still set. But new people that started at 2.02 are out of luck at the moment till I figure out wtf is wrong with the installers.

Thank you! \o/

I EOSCard'd my SD card and it loads.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 07:29:59 PM
I did make; make installer...
get 40K bin that doesn't work.

make buid_fir produced autoexec sized fir:

http://www.qfpost.com/file/d?g=NzBmhwaBK
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 04, 2013, 08:35:55 PM
I did make; make installer...
get 40K bin that doesn't work.

make buid_fir produced autoexec sized fir:

http://www.qfpost.com/file/d?g=NzBmhwaBK

I have to compile ML myself to use this, right?  :o
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 08:39:31 PM
I dunno try it on a non-boot flagged camera. For me the big fir just re-loads ML. The build was posted up above if you're already boot flagged from before.
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 04, 2013, 08:52:45 PM
I dunno try it on a non-boot flagged camera. For me the big fir just re-loads ML. The build was posted up above if you're already boot flagged from before.

Thanks!

My M are already boot flagged from the first firmware version.

I'm curious. I just downloaded "[EOSM202] FirstVersion-NoInstaller.zip". Does this work as an update for any build of ML? Nightly?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 09:01:51 PM
Its the whole binary. So its just like a 1.0 version except for 2.02
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 04, 2013, 09:22:32 PM
Its the whole binary. So its just like a 1.0 version except for 2.02

With "UpDaterM.fir". Now my camera booted with ML w/ all the files from "[EOSM202] FirstVersion-NoInstaller.zip". I tried turn my camera off and on but ML still boots and I can get into the menu. So this does work.

It's just that ML tells me to get FONTS and copy all the files to the card. Which ML build should I use?

------------------------
I just got all required files from nightly build. Now ML is working.

Thank you!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 09:28:03 PM
Pull fonts and all that from the nightly or what you had before.

If you already were boot flagged, you dont need a fir.
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 04, 2013, 09:32:39 PM
Pull fonts and all that from the nightly or what you had before.

If you already were boot flagged, you dont need a fir.

Seems like I have to re-flash "UpDaterM.fir" every time I pull the battery out.

Now sometimes when I turn the camera off too...
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 09:34:02 PM
Otherwise it doesn't boot?

Did you have alpha before or a normal bin?
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 04, 2013, 09:38:11 PM
Otherwise it doesn't boot?

Did you have alpha before or a normal bin?

Yes, otherwise ML doesn't boot.

I had ML installed on my M since Alpha1 on the previous version of firmware.
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 04, 2013, 09:45:25 PM
This



Is it bad for the ROM if I oftenly flash it?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 10:15:19 PM
I think its working like the alpha. At least the signing works. So I guess good news for people with no boot flag?

Something is wrong with the updater code? Only visible when canon firmare is on the card and then says file not found after updating 5%.

My camera was bootflagged previously and doesn't behave like in the video. You get ML from the get go.

So people with no ML before, does it work like the video?


Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 04, 2013, 10:24:41 PM
I'm exciting!

http://instagram.com/p/cmpkbsjnwK/

~35MB/s FOR THE WIN!

My 60D actually flushes the buffer @ ~20MB/s. :o
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 04, 2013, 10:27:41 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 10:32:25 PM
I think it will only load the bin attached to the .fir file this way. i.e. it should run without autoexec. on card.

Kinda sucks, need to figure out what's up with updater.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 04, 2013, 10:38:03 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 04, 2013, 10:41:59 PM
my cam timed out while writing here. I woke it and ML was gone. Turned it off, then on and ML was gone. I reinstalled the update firmware and it worked. I shut the cam off and then on and ML is gone again?? I have now installed it three times.

gary

Seems like we are in the same boat...
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 04, 2013, 10:48:19 PM
Yep, installer is messed up and its like the alpha. Needs more research.

At least people who got a 2.0.2 camera can try it.

If you had 1.0 firmware and used the rolling releases then your boot flag is still on and can use autoexec.bin.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 04, 2013, 11:56:57 PM
Btw, does anyone else's ML show a 16:9 rectangle in the middle? Mine keeps popping a 16:9 rectangle after the ML overlays load, and it's not from the cropmarks. Any ideas what that is?

Since I'm asking about EOS-M ML, might as well ask: does anyone know if ETTR can be switched to modify the aperture or ISO instead of shutter?

Thanks in advance.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on August 05, 2013, 12:08:51 AM
In movie mode, ML shows 16:9 cropmarks.

Normally they should disappear when you turn off raw video, but I have no idea if it actually works.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 05, 2013, 12:17:56 AM
Thanks. It's not the regular 16:9 cropmarks though. It's a white-border square inside the flexi-zone AF corners.

It shows up on everything. Even on regular canon layout. And photo mode, too.

Had to disable raw_rec from loading to make it go away. It shows up again as soon as I load raw_rec. Also, does raw_rec supposed to work yet? The screen goes purple haywire when I start recording.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on August 05, 2013, 12:29:59 AM
Without screenshot, I'm not sure what you are talking about.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 05, 2013, 12:31:02 AM
Flexizone multi puts a box on the screen, then there is the focus box. It also pops up things it wants to focus on and highlights them.. use single zone to stop that.

Nothing should be purple but the screen can freeze if you have on of the hacked previews. Otherwise its working like before.

Beep still freezes :(
Title: Re: Tragic Lantern for EOS M
Post by: biggles on August 05, 2013, 04:56:42 AM
Hello I have ML working on my 500D after some help from this site, thank you.

A question about ML on the Canon M, a camera I also have - is it already planned or can it be planned to add a feature of 'minimum shutter speed'? Setting it globally would be good, so that it applies to any mode. One of the big problems of the M is that it likes to auto set shutter speed to 1/30 in most modes (when light is low, obviously), whereas 1/30 is not appropriate for people photos, and I would like to set it to at least 1/60. Particularly when my wife or kids are using the camera and not so experienced, this issue is a pain for them. So a global setting of minimum shutter speed would be great. I cannot believe Canon leaves this out of their cameras, even from their high end point and shoot like the S100. So will this feature be implemented in ML for Canon M? Thank you.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 05, 2013, 05:13:15 AM
Not really possible to set it globally, you could do expo override/expo lock.

The auto expo module would be good here but it only works in non LV and that doesn't exist here.
Title: Re: Tragic Lantern for EOS M
Post by: biggles on August 05, 2013, 05:35:36 AM
Thanks for the reply. Not really sure what expo override/lock/auto expo module means or how it influences min shutter speed.

It wouldn't matter if it couldn't be set globally, at least if in a certain mode or two. e.g. Full auto or Av mode.

Are you saying there is no chance of that?

Thanks.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 05, 2013, 05:47:27 AM
exposure override.. exposure lock, features that may do what you want or shoot photos in TV mode
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 05, 2013, 08:48:11 AM
The rectangle in the middle.

http://i.imgur.com/RW9240q.jpg

http://i.imgur.com/oCesC2F.jpg

I figured this is the mark for framing the raw_rec. Is there a way to disable this without having to turn off and turn on the camera with the raw_rec unloaded?
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 05, 2013, 09:05:18 AM
Any solution to get rid of the dots in RAW video yet?
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 05, 2013, 09:33:57 AM
Yep, just let me make sure the video stuff works.

It does, prop browser is hanging things for some reason so took it out:

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip

I finally managed to get ML running on my EOS M 2.0.2.

Took me a few tries but figured it out. Still has issues but is very useable.

Workflow:


First soft format your SD card on your computer.
Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
Next download files from the bitbucket.org link provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
Next copy the updaterM202.fir (link on page 33 of this thread) on your SD card.
Open the EOSCard link from the installation section of the 5DMarkIII home page.
With the SD card in the card reader open the EOSCard utility.
Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
Then copy the ML directory from the Alpha 1 version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.org link (above) and copy it into the ML folder that you got from Alpha 1. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. 

Place the card in the EOS M and it should be ready to rock. 
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on August 05, 2013, 10:20:57 AM
I figured this is the mark for framing the raw_rec. Is there a way to disable this without having to turn off and turn on the camera with the raw_rec unloaded?

Huh? it should turn off as soon as you turn off raw video from movie menu. At least with my version of raw_rec (try the one from 5D3)
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 05, 2013, 11:21:25 AM
Huh? it should turn off as soon as you turn off raw video from movie menu. At least with my version of raw_rec (try the one from 5D3)

My bad. It's gone if you turn off raw video.

Thanks for this. :D
Title: Re: Tragic Lantern for EOS M
Post by: Stedda on August 05, 2013, 11:54:17 AM
Thanks a lot for all your hard work!

Now all 3 cameras run ML!  8)
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 05, 2013, 12:58:11 PM
I managed boot the camera with the 2.0 ML but has the same problem after reboot. I have to update the firmware again to make it work. However the good news is that my eye-fi card works again! At least now we can play with the new ML for some time. Thanks very much and we are waiting for a stable update.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 05, 2013, 03:30:06 PM
That looks like the raw box + the multi zone box together.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 05, 2013, 06:08:56 PM
Yeah, and it turns out the raw box goes away when the raw is turned off. LOL :D My bad.. Thanks anyway.

btw, the screen error thingy. Sometimes it's purple, tt's green this time:

>
I'm not sure how to reproduce this. It seems to happen randomly, and sometimes the liveview will stay purple.

The RAW came out okay though:

>http://www.mediafire.com/?12i1csw2juw9q8i
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 05, 2013, 09:02:42 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 05, 2013, 09:08:49 PM
Er, seems I was happy too early. The eyefi card doesn't work again after some time use. I found that the 5d3 ml actually works with eyefi card now. Can we also get that feature?
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 05, 2013, 09:31:27 PM
Intervalometer doesn't seem to work. It just freezes when it tries to take the first pic and the camera is also frozen so you have to take battery out to reset.
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 05, 2013, 09:52:44 PM
Auto Bracketing doesn't seem to work either. Seems like anything that uses ML to trigger the shutter or am I doing something wrong?

On the good side. RAW Video seems to work pretty good though works best at lower res (1472x500 continuous, 1536x522 526 frames). I'm getting 36.7 MB/s on Sandisk Extreme 64GB. Wohoo!

Camera does get a little hot doing RAW Video though.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 05, 2013, 10:00:08 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 05, 2013, 10:35:27 PM
gamerblot,
can you help me? I just posted here a request for help to do raw video on t5he M. I have a Komputerbay 128GB SDXC Secure Digital Extended Capacity Speed Class 10 600X UHS-I Ultra High Speed Flash Memory Card 60MB/s Write 90MB/s Read 128 GB. will this card work with our M ML we have here now? I have not tried using this card yet cus I thought we needed a 32gb card to boot ML.

hey gary2013,

What I found with the SDXC cards in general is that they don't work out of the box and formatted directly in camera. You have to use the EOSCard utility to write the MBR so that they can be properly read by the camera. I don't have your particular KomputerBay 128GB SDXC (though I have a 128GB CF or my 5DM2) so I can't say but you can try to format to run EOSCard. Format it first on your computer, then format it in the camera to get the DCIM/MISC folders, then run EOSCard clicking EOS_DEVELOP, BOOTDISK and the big ML button, then click Save. Then load up the ML files onto the card and try. It worked for my Sandisk Extreme 64GB.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 05, 2013, 10:42:06 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 05, 2013, 11:11:41 PM
Ok, will check full shutter press consts, etc. Possible that its wrong.

Well.. its all working here on a normally booted camera :(

This means that loading it like the alpha is causing issues.

As for raw, with a normally booting camera it should work with the 128gb. Try the "alpha" style boot and see what happens. BTW, shoot in photo mode JPG with multi shot NR to get the most free buffer.

I guess everything hinges on getting the bootflag updater to work correctly.
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 05, 2013, 11:30:57 PM
gamer, i understand. but what do i do after that to record raw? what menus and settings do I use? As far as my card, I think what is important is the write speed and mine shows it has 60 MB/s and I think the other people with 5DM3 were saying they needed 90MB/s. I just want to see if it works on the M. I was returning this card and maybe getting a 90Mb/s card if the M can record Raw.

Make sure you have the raw_rec.mo module in your /ML/MODULES folder. Turn on your camera, Firmware Update to load ML. Turn your M to Video mode, click Load Modules in ML Config Menu, now go to the ML Video menu, find RAW Video at the bottom of the menu and tap it on the touchscreen. Options will appear such as Resolution, Aspect Ratio. Change it to the setting you want. Hit the Shutter to go back to Live View. You will see a white letterbox indicating the shooting window that you selected with your Resolution and Aspect Ratio settings. Hit the MENU button to record and again to stop. If the buffer fills up, then it will stop automatically.

I found that the max EOS-M goes is 36.7Mb/s regardless of how fast your SD card is so the Komputerbay 90MB/s is overkill on this camera and probably for all SD-based EOS cameras. This is because the SD read speed on the EOS-M probably maxes out there. It's still better than the 60D where I was only getting about 20Mb/s which meant shooting at even lower resolutions to get enough usable footage. Only the CF-capable EOS are getting better throughputs. That's why 5DM3 is so great and 5DM2, 50D and 7Ds are getting more attention in terms of RAW video.

I honestly want to use the EOS-M for timelapse only, and not RAW video, as it is so cheap, I can throw a few of them everywhere to get different timelapse perspectives or settings of the same scene. There so light you can throw a few of them in the bag compared to a full size DSLR and they have the same sensor as the 7D/60D. But had to try the RAW video out on this cheap bad boy and it does work if you need it in a pinch.

 
Title: Re: Tragic Lantern for EOS M
Post by: thegunshow101 on August 06, 2013, 12:16:29 AM
ML RAW Rec on 2.02.. quick on the run findings

1728x522 - continuous
1728x564 - 2000+ frames (ends unexpectedly though and once dumped out of ML.. best to use mode that's continuous for stability)

Nice but very unstable though, lots of battery pulls.. half shutter press to focus during raw freezes camera.. as do so many other things. If you use it in movie mode you can focus with screen presses

(sandisk 32gb extreme pro card)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 06, 2013, 12:44:25 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 06, 2013, 12:46:54 AM
Yep, I can confirm the .fir version is about as stable as a 70yo crackhead.

Intervalometer freezes... for me modules don't even load. And no its not flashing your firmware every time, just hijacking the fw update code (like an xbox dashboard exploit, etc). Maybe its worse going from boot flagged autoexec.bin -> hijacked fir but from what you guys are saying doesn't sound like it.

Title: Re: Tragic Lantern for EOS M
Post by: neoyoli on August 06, 2013, 01:19:50 AM
Dear Developers,

It's an awesome initiative, I'm eager to try it especially because of the flawed stock firmware.
A couple of things that would be supernice to have, if they are possible:

- faster AF (without any steering)
- remap buttons (especially the rec button in photo mode)
- menu options (for delete, rotate, etc.) on tapping the screen during playback (like on Android)
- zoom with smaller increments (it zooms almost in the middle of the image right away)
- smoother slide animation when swiping through images
- direct MF, not just after AF lock

Thank you for your hard work, this will be irreplaceable.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on August 06, 2013, 02:46:59 AM
I get 1600x410 2.35 @ 24fps running continuously with the hacks on.

Edit: Mine came with 2.0.2 installed
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 06, 2013, 03:17:05 AM
Quote
remap buttons (especially the rec button in photo mode)

The rec button doesn't produce any events in photo mode, fuckers turned it off.. hence the raw module lets you change it to menu.

The touch stuff has to be implemented in general. A prime target is the junkie menu since its all buttons.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 06, 2013, 03:39:45 AM
I finally managed to get ML running on my EOS M 2.0.2.

Took me a few tries but figured it out. Still has issues but is very useable.

Workflow:


First soft format your SD card on your computer.
Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
Next download files from the bitbucket.org link provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
Next copy the updaterM202.fir (link on page 33 of this thread) on your SD card.
Open the EOSCard link from the installation section of the 5DMarkIII home page.
With the SD card in the card reader open the EOSCard utility.
Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
Then copy the ML directory from the Alpha 1 version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.org link (above) and copy it into the ML folder that you got from Alpha 1. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. 

Place the card in the EOS M and it should be ready to rock.

Just for the record the combo is running stable on my EOSM - intervalometer and all that. Will try video raw on photo mode today.

1% you really are a superhero. The Canon guys need to take a lesson or two from A1ex, you and other ML developers. Thank you for all the GOOD work.
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 06, 2013, 03:48:55 AM
gamer, i understand. but what do i do after that to record raw? what menus and settings do I use? As far as my card, I think what is important is the write speed and mine shows it has 60 MB/s and I think the other people with 5DM3 were saying they needed 90MB/s. I just want to see if it works on the M. I was returning this card and maybe getting a 90Mb/s card if the M can record Raw.

Get it here:

http://www.qfpost.com/file/d?g=NzBmhwaBK

Copy the MODULE directory into the ML directory of the Alpha 1.06 build and copy AUTOEXEC.BIN over the Alpha 1.06 version in the main directory.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 04:24:05 AM
Just for the record the combo is running stable on my EOSM - intervalometer and all that. Will try video raw on photo mode today.

1% you really are a superhero. The Canon guys need to take a lesson or two from A1ex, you and other ML developers. Thank you for all the GOOD work.

Can you make it work after reboot without reflash?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 06, 2013, 04:35:51 AM
That's the way to go. 650D just worked.So i dunno why this doesn't.

when I make installer it makes an autoexec.bin.. trying this bin; it boots with a solid light.. so the installer boot process isn't working?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 06, 2013, 05:16:46 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 06, 2013, 05:34:29 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 06, 2013, 05:35:38 AM
@Canon eos m: sorry, had no time to write you a detailed description how to remove dots etc. you really don't have to use rawmagic. i haven't tried RAWanizer so far, but if it can convert to dng via raw2dng, like 1% said, it should work just fine. else just try to convert it with the raw2dng.exe. just drag your raw file and drop it onto the raw2dng.exe file. this should give you working dng files. to remove dots download the latest dot removal tool:
https://dl.dropboxusercontent.com/u/22843507/MagicLantern/PinkDotRemover_debug.zip

Hi Mixer2 - Know where I can fetch a latest copy of pinkdot remover. Mine got corrupted and the link above does not have a copy anymore. Cheers!
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 06, 2013, 05:52:20 AM
Anyone out there that can also help me get the MODULE directory so I can get those files installed to try out raw video stuff on my M? Gamerblot has been helpful and I have been trying to get this working all day today. searching, reading and I can't find it anywhere. I don't understand why I don't have it like everyone else seems to do. Can anyone just email the files and folder?   garyalan24  at yahoo dot com

when i try Load Modules now, I always get two error messages saying 'B:/ML/Modules/eosm_202.sym'  ; File does not exist


My bad, too many different download links. Needs to be consolidated. This is the right one:

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip

Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 06, 2013, 06:10:07 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Digital Guy on August 06, 2013, 06:12:47 AM
Shooting at 1280 x 720 25fps what would be the max card speed needed by EOS-M? I think many EOS-M users would be happy with 1280x720P if that's at all possible. If 20 MB/s is the fastest the EOS-M is capable of what is max video resolution we can get from that?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 06, 2013, 06:18:36 AM
Well you can crop 720P from crop mode or shoot in zoom mode.

I think it needs a menu item to force zoom mode on so its easier to get into.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 07:21:07 AM
The current magic room is a good feature for MF lenses. But it still has some shortages. Once it was triggered by the half shutter, it won't disappear after releasing the shutter until half pressing it again. That is kind of a little annoying. But most importantly is that the enlarged image is just a simple magnification of the focus box area and the definition is very low, which is different from the liveview room effect. Is that possible to improve this function to make it more usable?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 06, 2013, 07:28:26 AM
Its full screen if/when the display filter syncs.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 07:47:19 AM
Its full screen if/when the display filter syncs.

So it's impossible to change that? I know the Sony nex has that function as default and my another canon ixus camera also has it.
Title: Re: Tragic Lantern for EOS M
Post by: Indianac on August 06, 2013, 07:59:15 AM
Just for the record the combo is running stable on my EOSM - intervalometer and all that. Will try video raw on photo mode today.

1% you really are a superhero. The Canon guys need to take a lesson or two from A1ex, you and other ML developers. Thank you for all the GOOD work.

Quick question. Thought I read that there's no installer for those starting off in 2.02, but then read a post that said someone got it to work. Do these instructions work for new non-bootflagged 2.02? I only get the flashing green lights and have to battery pull.  If these are the right instructions, can you update with a quick link to the bitbucket files? Thanks guys.
Title: Re: Tragic Lantern for EOS M
Post by: Drizzt321 on August 06, 2013, 08:08:00 AM
I finally managed to get ML running on my EOS M 2.0.2.

Took me a few tries but figured it out. Still has issues but is very useable.

Workflow:


First soft format your SD card on your computer.
Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
Next download files from the bitbucket.org link provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
Next copy the updaterM202.fir (link on page 33 of this thread) on your SD card.
Open the EOSCard link from the installation section of the 5DMarkIII home page.
With the SD card in the card reader open the EOSCard utility.
Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
Then copy the ML directory from the Alpha 1 version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.org link (above) and copy it into the ML folder that you got from Alpha 1. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. 

Place the card in the EOS M and it should be ready to rock.

I followed this, used the UpDaterM.fir instead of updaterM202.fir which I couldn't find. Got it to install and run fine, although like others it isn't booting right into ML after turning it off/on. Other than that, don't have more time to play with it tonight, but great job 1%!!
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on August 06, 2013, 08:30:03 AM
For photo, try the x5/x10 zoom triggered by half-shutter. Of course, it won't work for video.

I've implemented it after playing with a NEX.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 06, 2013, 10:24:12 AM
Hi Mixer2 - Know where I can fetch a latest copy of pinkdot remover. Mine got corrupted and the link above does not have a copy anymore. Cheers!

Hi, it's not the most recent, but that's still the version i use (still the same link. it should work...):
https://dl.dropbox.com/s/77bkw4u9nh7dt4d/PinkDotRemover_2013_07_15.zip

there is a newer version, but there were changes for the 650d which aren't optimized for eos m so far. since i'm very busy right now and the old version works great i didn't spent much time for the dot remover development. but there will be a new version soon.
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 06, 2013, 10:25:51 AM
1%

I figured out why my M behaved like that. I forgot to check EOS_DEVELOP in EOSCard.

Shame on me haha. :P
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 01:08:49 PM
1%

I figured out why my M behaved like that. I forgot to check EOS_DEVELOP in EOSCard.

Shame on me haha. :P

So what does that mean?
Title: Re: Tragic Lantern for EOS M
Post by: Indianac on August 06, 2013, 04:46:34 PM
I followed this, used the UpDaterM.fir instead of updaterM202.fir which I couldn't find. Got it to install and run fine, although like others it isn't booting right into ML after turning it off/on. Other than that, don't have more time to play with it tonight, but great job 1%!!

I didn't see a zip file in the bitbucket. Am I missing somthing?
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 06, 2013, 04:56:48 PM
So what does that mean?

I did not set the card up properly. So ML didn't boot and the camera needed to be flashed every time I want to use ML.

Then I tried again from scratch and then I found out that I didn't set my sdcard up properly.

My camera has been boot flagged since Alpla 1.
Title: Re: Tragic Lantern for EOS M
Post by: millernet on August 06, 2013, 05:01:04 PM
@1% -- I AM GIVING YOU A STANDING OVATION.  WELL DONE!  THANK YOU

@Canon eos m - GREAT INSTRUCTIONS, thank you. 

Who cares about the AF issues when you have vintage glass and focus peaking/MZ, and zoom on half shutter...This literally fixes every issue i had with this camera.  WELL, WELL DONE.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 06, 2013, 05:13:51 PM
Yea, I think people without boot flag are still stuck re "fashing" tho.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 05:21:23 PM
I did not set the card up properly. So ML didn't boot and the camera needed to be flashed every time I want to use ML.

Then I tried again from scratch and then I found out that I didn't set my sdcard up properly.

My camera has been boot flagged since Alpla 1.

Thanks very much! I also got it work now!
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 05:29:14 PM
@1% -- I AM GIVING YOU A STANDING OVATION.  WELL DONE!  THANK YOU

@Canon eos m - GREAT INSTRUCTIONS, thank you. 

Who cares about the AF issues when you have vintage glass and focus peaking/MZ, and zoom on half shutter...This literally fixes every issue i had with this camera.  WELL, WELL DONE.

Focus peaking is very good. But the magic zoom still need to be improved. I hope it can enlarge the focus area as clear as the liveview full screen room and auto hide after releasing the shutter. The liveview auto zoom on shutter function is also very good. But it is not very suitable for composition of pictures and the shutter also has some obvious delay after the view is zoomed. So it will be best to improve the magic zoom.
Title: Re: Tragic Lantern for EOS M
Post by: thegunshow101 on August 06, 2013, 05:33:22 PM
Shooting at 1280 x 720 25fps what would be the max card speed needed by EOS-M? I think many EOS-M users would be happy with 1280x720P if that's at all possible. If 20 MB/s is the fastest the EOS-M is capable of what is max video resolution we can get from that?

See my last post for resolutions but at 24fps I'm getting 38mb/s on a sandisk extreme pro card (rated for 90mb/s)
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 05:36:49 PM
BTW, still wondering is it possible to disable the touch screen after it was turned off and only turn it on by hard keys. It could help avoid unintended touch between body and screen when hanging the camera on the neck.
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 06, 2013, 05:44:48 PM
Is there any solution to get rid of the dots in RAW video yet?

I tried "PinkDotRemover_2013_07_15.zip" with the DNGs. But it doesn't seem to work. I'm not sure if I did something wrong.

Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 06, 2013, 05:51:33 PM
Is there any solution to get rid of the dots in RAW video yet?

I tried "PinkDotRemover_2013_07_15.zip" with the DNGs. But it doesn't seem to work. I'm not sure if I did something wrong.

I had the same experience. Googled and found the 2013-07-15 version of PDR but does not seem to work. It goes through the routine pretty smoothly but does not seem to remove the dots.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 06, 2013, 06:21:55 PM
BTW, still wondering is it possible to disable the touch screen after it was turned off and only turn it on by hard keys. It could help avoid unintended touch between body and screen when hanging the camera on the neck.

This is really strange behavior. My EOS-M doesn't turn on when I touch it after it's turned off...

Check your power saving options. I suspect your LCD auto off is faster than your camera auto off. I usually set them to  the same value.
Title: Re: Tragic Lantern for EOS M
Post by: millernet on August 06, 2013, 06:26:07 PM
Focus peaking is very good. But the magic zoom still need to be improved....

...it's 1 million times better than the stock firmware already. Thank you 1%!
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 06:27:51 PM
This is really strange behavior. My EOS-M doesn't turn on when I touch it after it's turned off...

Check your power saving options. I suspect your LCD auto off is faster than your camera auto off. I usually set them to  the same value.

Well I Tried to set both of them auto off after 30 sec. But the screen still turn on after it was touched.......
Title: Re: Tragic Lantern for EOS M
Post by: wuxiekeji on August 06, 2013, 07:21:00 PM
...it's 1 million times better than the stock firmware already. Thank you 1%!

Is there any reason by the way that the magic zoom (at least on 60D) seems to only zoom in the LCD screen resolution image and not the actual high-res 5X or 10X image that you get when you use the stock firmware zoom?

I wish I could get the stock firmware 5X but in a magic zoom box that I can move around.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 06, 2013, 07:28:36 PM
@Dark-Master & Canon eos m:
about pink dot removal:
do you use "Movie crop mode"? there isn't dot removal data for non crop mode at the moment. since non crop mode videos do have totally useless quality. if anyone really want to use non crop mode raw video i can add the dot removal data for it.
Just send me a dng that doesn't work and i'll check what's going wrong.
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 06, 2013, 07:43:57 PM
I had the same experience. Googled and found the 2013-07-15 version of PDR but does not seem to work. It goes through the routine pretty smoothly but does not seem to remove the dots.

Same here.

The application seems to be working fine. And it did converted all my files. But the dots are still there.  :o
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 06, 2013, 08:05:37 PM
@Dark-Master:
please read the post just above your last post.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 06, 2013, 08:50:01 PM
Well I Tried to set both of them auto off after 30 sec. But the screen still turn on after it was touched.......


My bad. Set the turn camera off to 0 Sec.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 08:59:33 PM
My bad. Set the turn camera off to 0 Sec.

Sorry I didn't get your point as I know the minimum auto turn LCD off time is 5 second.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 06, 2013, 09:42:32 PM
Sorry I didn't get your point as I know the minimum auto turn LCD off time is 5 second.

What version is your firmware? I'm on 2.0.2

I see two power saving options:

LCD Auto Off: With minimum setting 15 sec.

and Camera auto off: With minimum setting at 0 Sec.  < After turning off LCD, this is how long the camera waits until it turns itself off.

TL;DR - RTFM
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 06, 2013, 09:47:09 PM
What version is your firmware? I'm on 2.0.2

I see two power saving options:

LCD Auto Off: With minimum setting 15 sec.

and Camera auto off: With minimum setting at 0 Sec.  < After turning off LCD, this is how long the camera waits until it turns itself off.

TL;DR - RTFM

I understand what you mean. But what I want is not auto turn off the whole camera but just the LCD and sensor, and disable the touch screen afterwards. Currently the touch screen still work after the screen off. That's why I suggest this function.

BTW is there actually any difference between the camera auto turn off LCD and the ML auto turn off LCD? Does the former also turn off the sensor?
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 06, 2013, 11:51:54 PM
@1% when using movie crop mode, at 24p settings, when I go to movie rec size it says it's shooting at 30p but the ML LV display on the upper corner says it's 23.976, the recorded movie also says 23.976, but I'm not sure if it is, because you  know, 24p and 30p don't look that much different. Maybe there's a bug or something in there?
Title: Re: Tragic Lantern for EOS M
Post by: Drizzt321 on August 07, 2013, 12:14:04 AM
I didn't see a zip file in the bitbucket. Am I missing somthing?

There are 3 files to download from this thread (plus the EOSCard app).

[EOSM202] (need to rename to have .zip extension): https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip)
UpDaterM.fir: http://www.qfpost.com/file/d?g=NzBmhwaBK (http://www.qfpost.com/file/d?g=NzBmhwaBK)
magiclantern-EOSM.106.Alpha1.zip: http://bit.ly/UP7Avg (http://bit.ly/UP7Avg)

So, here are the steps that I took, a slight modification along with correct links on Canon eos m instructions.

1. First soft format your SD card on your computer.
2. Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
3. Next download files from the bitbucket.org link (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip)) provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
4. Next copy the updaterM202.fir (link on page 33 of this thread) UpDaterM.fir (http://www.qfpost.com/file/d?g=NzBmhwaBK (http://www.qfpost.com/file/d?g=NzBmhwaBK)) on your SD card.
5. Open the EOSCard link from the installation section of the 5DMarkIII home page.
6. With the SD card in the card reader open the EOSCard utility.
7. Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
8. Then copy the ML directory from the Alpha 1 (http://bit.ly/UP7Avg (http://bit.ly/UP7Avg)) version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.
9. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. (step 3)
Title: Re: Tragic Lantern for EOS M
Post by: Indianac on August 07, 2013, 12:41:11 AM
Awesome Drizzt321!  I was just rereading through the thread and about to try to answer my own question, so you've saved me some time. Now onto the tests.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 07, 2013, 12:58:00 AM
Quote
Maybe there's a bug or something in there?

Yep, in canon code. This camera really likes 30P. Maybe in the future I can cache hack the normal 24p while recording over that stupid 720P30.

Also should note:
had boot flag -> just load autoexec.bin and alpha1 or nightly support files

no boot flag before: probably only loads the bin burned into the fir file.
Title: Re: Tragic Lantern for EOS M
Post by: Drizzt321 on August 07, 2013, 01:21:38 AM
Awesome Drizzt321!  I was just rereading through the thread and about to try to answer my own question, so you've saved me some time. Now onto the tests.

You're welcome :) 
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 07, 2013, 02:30:38 AM
OK, I installed ML no problem.

I turned on GlobalView: Live View. Set zebras on and histogram on. But I do not see them on the screen.

I turned on REC/Standby for video: I do not see them on the screen. Again, no ML overlays at all.

What is working (for me):

In video, I can up the bitrate - got it up to 63 Mbps.

I got the log working. But, no report of ISO (just = 0). It does report time, shutter speed, focus distance (I moved that around to check), and aperture. Why no ISO?

There is no audio in video mode. Will this be fixed?

I understand there are limitations, but let's fix the overlay issue (which may be me, but I can follow instructions and they should show as far as I can tell).

I of course appreciate very much the work that went into this and the supposed feature set, so these are not complaints, just questions.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 07, 2013, 03:31:55 AM
There are 3 files to download from this thread (plus the EOSCard app).

Thanks for posting the workflow with links ;D
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 07, 2013, 03:36:14 AM

4. Next copy the updaterM202.fir (link on page 33 of this thread) UpDaterM.fir (http://www.qfpost.com/file/d?g=NzBmhwaBK (http://www.qfpost.com/file/d?g=NzBmhwaBK)) on your SD card.


Question: Is the updater.fir a newer version than the updaterm202.fir?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 07, 2013, 05:22:57 AM
One is a normal autoexec.bin signed, the other is supposed to be the installer(40KB).
Title: Re: Tragic Lantern for EOS M
Post by: Indianac on August 07, 2013, 06:57:32 AM
Darn, followed the instructions and got further but I'm getting a "missing symbol file b:/ML/Modules" error right after the firmware update screen pops up.  I checked and I have the EOSM_202.sym in the folder. What am I doing wrong here?

note: I was on a out of box 2.02, not upgraded. Did I jump the gun?
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 07, 2013, 07:24:29 AM
@Dark-Master:
please read the post just above your last post.

Sorry, I missed the post.

I used 1472x500.
Is what you mean by crop mode the big white rectangle? I always record with white rectangle on.

Thank you.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 07, 2013, 09:53:34 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: daduke on August 07, 2013, 10:04:16 AM
Darn, followed the instructions and got further but I'm getting a "missing symbol file b:/ML/Modules" error right after the firmware update screen pops up.  I checked and I have the EOSM_202.sym in the folder. What am I doing wrong here?
I had this problem too: you need to copy the modules directory into the ML directory, not on the root level.

-Christian
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 07, 2013, 10:32:41 AM
Currently I use the liveview auto zoom to help MF give the magic room is not clear enough. But the half press trigger method is really a little annoying as it prevent immediate shutter sometime. I noticed that we can also use the exposure lock key to zoom. So can we only use this key to trigger this function?
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 07, 2013, 10:32:54 AM
Intervalometer doesn't seem to work. It just freezes when it tries to take the first pic and the camera is also frozen so you have to take battery out to reset.

HDR doesn't seem to work either. Seems like anything that use ML to trigger the shutter automatically.

I got Intervalometer and HDR Auto Bracketing to work finally. After futzing around with it for awhile, this is what I found...

Basically, you have to turn on Intervalometer. The camera gets stuck and the shutter doesn't release. But then you hit the Power Off button and then again to Power On right away (if you wait more than a few seconds, ML disappears). The camera then turns back on and immediately starts taking pictures using the Intervalometer setting you set. You hit PLAY button to stop the Intervalometer, go back into the ML menu and now Intervalometer and Auto Bracketing works (or at least until you turn the camera off and ML disappears) and you can change your settings and use Intervalometer and Auto Bracketing.

This is obviously not ideal but it is a workaround for all you timelapsers out there like me.

Hope %1 and A1ex can figure out how to fix this Intervalometer/Auto Bracketing bug and make it so you don't have to Update Firmware every time you want to use ML on EOS-M 2.02. Keep up the great work!

Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 07, 2013, 10:48:29 AM
Sorry, I missed the post.

I used 1472x500.
Is what you mean by crop mode the big white rectangle? I always record with white rectangle on.

Thank you.

you'll find the crop mode option in the ml movie menu "Movie crop mode". what sucks is that you'll get an additional crop factor of  ~3 (it's a 100% crop on the sensor), therefore you'll get with 18mm a slightly narrower view than with 55mm. so you can't do wide angle shots with that option. but without that option the raw videos do have a imho useless quality. with that option enabled the quality is quite nice.
i'll create the dot removal data for non crop mode, but i don't think that anyone wants to use it.
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 07, 2013, 02:44:09 PM
you'll find the crop mode option in the ml movie menu "Movie crop mode". what sucks is that you'll get an additional crop factor of  ~3 (it's a 100% crop on the sensor), therefore you'll get with 18mm a slightly narrower view than with 55mm. so you can't do wide angle shots with that option. but without that option the raw videos do have a imho useless quality. with that option enabled the quality is quite nice.
i'll create the dot removal data for non crop mode, but i don't think that anyone wants to use it.

Thank you very much. I'll try that now.

Is there any possibility that we'll be able to shoot in non cop mode in usable quality?

Since my 60D only has buffer transfer limit @~20MB/s. I really hope my EOS M would do the better job since it has much bigger buffer. Just saying.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 07, 2013, 03:12:00 PM
Quote
Hope %1 and A1ex can figure out how to fix this Intervalometer/Auto Bracketing bug and make it so you don't have to Update Firmware every time you want to use ML on EOS-M 2.02. Keep up the great work!

Its the same problem. Intervalometer works on my camera with a regularly booting version.
Title: Re: Tragic Lantern for EOS M
Post by: Indianac on August 07, 2013, 03:45:30 PM
I had this problem too: you need to copy the modules directory into the ML directory, not on the root level.

-Christian

Thanks Christian. That did the trick! I'm on ML now for 2.02.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 07, 2013, 05:52:34 PM
@Dark-Master: don't think that there will be usable non crop raw video on the eos m. the method canon scales the image down (by just skipping lines and rows, instead of interpolation) combined with the reduced vertical resolution from the sqeeze factor leads to miserable quality. but i don't know, maybe 1% can tell you if there is any hope.
i also had problems with the extreme cropfactor in crop mode first, but you can get used to it. especially with the new 11-22mm lense or a speedbooster (as soon as one for eos m is available) it should be possible to get wide enough angle of view for most situations. since it's cropped from the center and wide angle lenses are mainly distorted at the edges there shouldn't be much barrel distortion or stuff like that with wide angle lenses. have tested it with sigma 10-20mm, but don't use it much, since it doesn't has IS.
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 07, 2013, 07:49:55 PM
I got Intervalometer and HDR Auto Bracketing to work finally. After futzing around with it for awhile, this is what I found...

Basically, you have to turn on Intervalometer. The camera gets stuck and the shutter doesn't release. But then you hit the Power Off button and then again to Power On right away (if you wait more than a few seconds, ML disappears). The camera then turns back on and immediately starts taking pictures using the Intervalometer setting you set. You hit PLAY button to stop the Intervalometer, go back into the ML menu and now Intervalometer and Auto Bracketing works (or at least until you turn the camera off and ML disappears) and you can change your settings and use Intervalometer and Auto Bracketing.

This is obviously not ideal but it is a workaround for all you timelapsers out there like me.

Hope %1 and A1ex can figure out how to fix this Intervalometer/Auto Bracketing bug and make it so you don't have to Update Firmware every time you want to use ML on EOS-M 2.02. Keep up the great work!


Its the same problem. Intervalometer works on my camera with a regularly booting version.

OK, I found that you don't have to invoke the Intervalometer first. All you have to do Update Firmware to load ML, once on, just hit Power On/Off quickly twice (once to turn off, once to turn on) within a second (if you take longer than a second, ML is unloaded again) and Intervalomater and Auto Bracketing (and I am sure other ML features) work. This workaround is probably simulating what the bootflag would have done in the first place but for all those like me that got our EOS-M with 2.02 and not an upgrade from 1.06 with a ML bootflag previously, this is a workaround for now.

Hope %1 can figure out the bootflag for 2.02 firmware users soon
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 07, 2013, 08:12:58 PM
OK, I found that you don't have to invoke the Intervalometer first. All you have to do Update Firmware to load ML, once on, just hit Power On/Off quickly twice (once to turn off, once to turn on) within a second (if you take longer than a second, ML is unloaded again) and Intervalomater and Auto Bracketing (and I am sure other ML features) work. This workaround is probably simulating what the bootflag would have done in the first place but for all those like me that got our EOS-M with 2.02 and not an upgrade from 1.06 with a ML bootflag previously, this is a workaround for now.

Hope %1 can figure out the bootflag for 2.02 firmware users soon

With my 2.02 firmware EOS-M and ML I can't get zebras to work or focus peaking or anything to show up overlaid on the screen - does this also require the on-off trick, or do you have those working? I do get the menus and higher bitrate video and other features working , so my install is fine.
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 07, 2013, 08:26:07 PM
With my 2.02 firmware EOS-M and ML I can't get zebras to work or focus peaking or anything to show up overlaid on the screen - does this also require the on-off trick, or do you have those working? I do get the menus and higher bitrate video and other features working , so my install is fine.

Zebras, focus peaking and Global Draw overlays are all working for me without need to do the on/off trick. I just need to do the on/off trick for shutter release type ML functions.
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 07, 2013, 10:08:30 PM
Zebras, focus peaking and Global Draw overlays are all working for me without need to do the on/off trick. I just need to do the on/off trick for shutter release type ML functions.

Thanks. All I needed to do was press the 'Display' button to get rid of the Canon icons (as the ML instructions say in the camera!) and everything shows up.
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 07, 2013, 10:11:09 PM
OK, I installed ML no problem.

I turned on GlobalView: Live View. Set zebras on and histogram on. But I do not see them on the screen.

I turned on REC/Standby for video: I do not see them on the screen. Again, no ML overlays at all.

What is working (for me):

In video, I can up the bitrate - got it up to 63 Mbps.

I got the log working. But, no report of ISO (just = 0). It does report time, shutter speed, focus distance (I moved that around to check), and aperture. Why no ISO?

There is no audio in video mode. Will this be fixed?

I understand there are limitations, but let's fix the overlay issue (which may be me, but I can follow instructions and they should show as far as I can tell).

I of course appreciate very much the work that went into this and the supposed feature set, so these are not complaints, just questions.

You're an idiot, Markr041:

1. All you needed to do was press the 'Display' button to get rid of the Canon icons (as the ML instructions say in the camera!) and everything shows up - histogram, zebras, STANDBY. and a lot of info on settings, even the name of the file.

2. Audio is disabled only when you add some features (Video hacks).
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 07, 2013, 10:56:13 PM
Zebras, focus peaking and Global Draw overlays are all working for me without need to do the on/off trick. I just need to do the on/off trick for shutter release type ML functions.

What is that trick?
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 07, 2013, 11:36:21 PM
What is that trick?

The on/off trick. Basically you Update Firmware to load ML. Then you hit Power On/Off once to turn off and then immediately again to turn on (must do it within a second or so of turning off or ML will be gone from memory). ML should still be there and shutter release features such as Intervalometer and HDR Auto Bracketing will work where they didn't before.

This trick is only necessary for all those with EOS-M 2.02 from factory. If you upgraded from 1.06 and had loaded ML for 1.06 with bootflag and still have it, you don't need to re-flash every time and you shouldn't need this trick.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 08, 2013, 01:46:03 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 08, 2013, 01:47:14 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Dark-Master on August 08, 2013, 04:09:21 AM
@Dark-Master: don't think that there will be usable non crop raw video on the eos m. the method canon scales the image down (by just skipping lines and rows, instead of interpolation) combined with the reduced vertical resolution from the sqeeze factor leads to miserable quality. but i don't know, maybe 1% can tell you if there is any hope.
i also had problems with the extreme cropfactor in crop mode first, but you can get used to it. especially with the new 11-22mm lense or a speedbooster (as soon as one for eos m is available) it should be possible to get wide enough angle of view for most situations. since it's cropped from the center and wide angle lenses are mainly distorted at the edges there shouldn't be much barrel distortion or stuff like that with wide angle lenses. have tested it with sigma 10-20mm, but don't use it much, since it doesn't has IS.

I see. Thank you very much.

ML is still freakin' awesome for EOS M, thanks to you guys.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 08, 2013, 06:49:51 AM
Has anyone ever gotten a purple screen?

I randomly get those but can't seem to figure out what causes it (and it means that I can't tell you the steps on how to reproduce it). It usually happens when I half-press the shutter button, but also on other occasion.
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 08, 2013, 07:04:53 AM

This is one sequence shot in RAW mode with the EOS M. Then, the single RAW file (one take) was split into its 800 frames as 800 sequentially numbered .DNG files. The .DNG files were read into Adobe Lightroom, where white balance was set (I chose the daylight setting). I also lowered ev by one third and then all 800 files were outputted as .Tif files. The set of 800 Tiff files (really frames) were read into Sony Vegas Pro and then rendered out as an MP4 file with a bitrate of 40Mbps at 29.970. The original frame rate was 29.970, shot at 720p in 2:35 aspect ratio (1280x544) - and that is what you see. The sequence bitrate in the camera was about 35 megabytes per second and continuous shooting (I could have shot until the file size limit). The original RAW file was almost 1 Gigabyte for this 25-second sequence shot in extremely bright sun.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 08, 2013, 07:07:54 AM
Has anyone ever gotten a purple screen?

I randomly get those but can't seem to figure out what causes it (and it means that I can't tell you the steps on how to reproduce it). It usually happens when I half-press the shutter button, but also on other occasion.

A tip, a bug and a comment:

Tip: shut global draw when recording RW video - pushes the CPU use age by half leaving more room for the buffer to take in extra shots;

Bug: if the magic zoom is turned on while HDR video recording, the video just keeps recording and cannot be shut off till the battery is removed and nothing is saved; and

Comment: I don't have the issues with Auto Bracket and Intervalometer that has been pointed by some (i.e., don't have to shut off and on to secure their functioning).
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 08, 2013, 09:15:44 AM

This is one sequence shot in RAW mode with the EOS M. Then, the single RAW file (one take) was split into its 800 frames as 800 sequentially numbered .DNG files. The .DNG files were read into Adobe Lightroom, where white balance was set (I chose the daylight setting). I also lowered ev by one third and then all 800 files were outputted as .Tif files. The set of 800 Tiff files (really frames) were read into Sony Vegas Pro and then rendered out as an MP4 file with a bitrate of 40Mbps at 29.970. The original frame rate was 29.970, shot at 720p in 2:35 aspect ratio (1280x544) - and that is what you see. The sequence bitrate in the camera was about 35 megabytes per second and continuous shooting (I could have shot until the file size limit). The original RAW file was almost 1 Gigabyte for this 25-second sequence shot in extremely bright sun.

That is awesome. What make/model card are you using? :3
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 08, 2013, 04:57:43 PM
That is awesome. What make/model card are you using? :3

Sandisk Extreme 32GB (class 10, UH-1). Claims 50 MB per second write speed.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 09, 2013, 02:13:26 AM
if anyone wants to try a current pink dot remover test version:
http://dl.dropbox.com/s/m0bxzd23p4zow8o/PinkDotRemover_2013_08_08.zip

new features:
* add files via drag and drop
* remove files from list via "del" key
* eosm dot removal data for non crop mode again (it isn't really tested, just the 1472x500 resolution for Dark-Master is tested. if you find any resolution that doesn't work please report it!)
* renamed dot data files. use CropMode for eos-m or 650d in crop mode. use EOSM for eos-m raw video without crop mode and for silent dngs.
* last dropdown selection gets saved that you don't have to select it each time you start the program

since it's based on current version all the latest changes from foorgol are also in that version. you can remove dots directly from the raw files not just the dngs and other improvements. check the 650d pdr thread for details http://www.magiclantern.fm/forum/index.php?topic=6658.125
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on August 09, 2013, 02:25:57 AM
I'm exporting my first real test of the EOS M raw video, recorded using the full sensor at max resolution at 24fps and 2.39 aspect ratio. I resized it in AE to fix the stretch, but so far it's looking pretty good. At this resolution I'm getting continuous recording and it looks about as good as the full res looked on my 60D, except that only got me ~11 seconds.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 09, 2013, 04:42:52 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 09, 2013, 07:29:50 AM
The 20MB/s SD cameras uprezzed OK, no reason why digic V won't.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 09, 2013, 07:48:02 AM
Has anyone been able to use the intervalometer functionality on the EOS-M yet?

If so, are there any tricks?  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 09, 2013, 09:05:34 AM
@gary2013:
non crop with max resolution and 2.39 aspect ratio is 1728x436.
the maximum continuous record speed you can get with eos m is ~35-36mb/s. and you'll get that speed with all fast sd cards, since the sd controller is much slower than the max write speeds of high speed sd cards.
if you want to be sure that the video doesn't stop even for longer recordings you imho shouldn't record above 34mb/s, even if it tells you that continuous recording works.
my prefered settings are: 1408x600 (2.35:1) in crop mode at 23.98fps (no fps override since it isn't needed in crop mode) 33,7mb/s and i use 32gb sandisk extreme 45mb/s card.

@handbanana:
don't know how 60D videos exactly look, but on my eos m videos without crop just aren't usable. why haven't you used a more vertical aspect ratio like 2.20:1 (32,7mb/s) or even 2:1 (36,1mb/s) should be possible with 1728 24fps.
do you want to show us the video?

@cameron12x:
intervalometer works for me just like expected.
Title: Re: Tragic Lantern for EOS M
Post by: xpstudio on August 09, 2013, 09:40:40 AM
@mixer2  I just tested your PinkDotRemover and works fine at 1408x600 (2.35:1) in crop mode  8)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 09, 2013, 09:51:42 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on August 09, 2013, 10:08:31 AM
I recorded at the max res the EOS M lets you on a PNY Class 10 card. And I would upload but my internet is shite at the moment. How would a more vertical aspect ratio help at all? I thought the squeeze factor was the same, and I just prefer the look of 2.39.

Why do you say it is unusable? From my far from perfect test I think I'm getting more detail than from H264, and of course the latitude with raw is another bonus. I think I saw a couple jaggies on a string, but for what it's worth it's a small price to pay for other benefits. Maybe I'll notice it more in other subjects, but so far it's not a bad compromise for a $300 camera shooting raw. I'll have to try the crop mode, but I would much rather be able to use the whole sensor.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on August 09, 2013, 10:19:14 AM
here is a screen grab from the video

http://i.imgur.com/m52FyVe.jpg

Edit: Well, imgur really messed with the quality so this is a terrible example lol
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 09, 2013, 11:02:57 AM
ah ok if you really wanted the exact 2.39 ratio, it's correct to record it. i just prefer to record maximum possible and if i decide in post, that i want a more horizontal aspect ratio it's easy to add a letterbox. the unused pixels can be helpful for finetuning vertical position in that case.
it won't btw use the "whole sensor" anyways. the pixels are just picked from the whole sensor area, instead of the center. but it does just use 753408 of the 17915904 pixels. ~4,2% of the sensor.
crop mode has all the benefits from non crop mode raw, but additionally looks really great. no jagging edges, much less aliasing. the downside is of course the additional crop factor that makes it hard to get wide angle shots or narrow depth of field.
try some shots with fine details, far away objects or hard edges and compare h.264, crop mode raw and non crop mode raw. then you'll see how much better crop mode works.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 09, 2013, 01:18:39 PM
@mixer2:  Where are the instructions for the intervalometer?  It likes 10s is the only option?  I would think it would be more flexible than that.

Also, I get error loading symbol files, despite having the EOS_202.sym file in the MODULES folder.  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 09, 2013, 01:47:01 PM
try tapping on the screen while the intervalometer option is highlighted in the ml menu. you should get into the submenu to configure the interval duration, an timer offset to start the recording, a time limit to stop recording and the settings for expo- and focusramp.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 09, 2013, 02:07:13 PM
I can get to the sub-menu, no problem.  I don't see how to change the setting from 10s, once there, however.
Title: Re: Tragic Lantern for EOS M
Post by: sometimes on August 09, 2013, 03:00:38 PM
5. Open the EOSCard link from the installation section of the 5DMarkIII home page.
6. With the SD card in the card reader open the EOSCard utility.
7. Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
========================================================

Can anyone help me about step5~7 ? Because I don't understand what means........ :'(
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 09, 2013, 03:03:12 PM
@cameron12x:
press set in the submenu and then turn the maindial or press left or right on the main dial to adjust the setting.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 09, 2013, 03:13:06 PM
@mixer2:  Thanks for the baby steps.  I see how to do that now.

But how do I get the sequence to actually start?  I tried setting a test run of 4 images, and it looked like the intervalometer counted down and went through the process, but when I try to review images it says no images found?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 09, 2013, 03:34:34 PM
Its working normally on the actual autoexec.bin version. I can't attest to the signed version since people seem to be having issues.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 09, 2013, 03:50:15 PM
What is the "signed version" and how does that affect the intervalometer?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 09, 2013, 04:30:33 PM
Signed version = fir
Normal version = autoexec.bin


If you're having to run the fir every time and got EOSM with 2.02 pre-installed then you're stuck with the signed version for now.
Title: Re: Tragic Lantern for EOS M
Post by: Henrik on August 09, 2013, 04:57:00 PM
So, here are the steps that I took, a slight modification along with correct links on Canon eos m instructions.

1. First soft format your SD card on your computer.
2. Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
3. Next download files from the bitbucket.org link (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip) provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
4. Next copy the updaterM202.fir (link on page 33 of this thread) UpDaterM.fir (http://www.qfpost.com/file/d?g=NzBmhwaBK) on your SD card.
5. Open the EOSCard link from the installation section of the 5DMarkIII home page.
6. With the SD card in the card reader open the EOSCard utility.
7. Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
8. Then copy the ML directory from the Alpha 1 (http://bit.ly/UP7Avg) version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.
9. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. (step 3)



Ive been using ML with 1.0.6 for a while. Im now trying to install the 2.0.2 version. Stupid question: Do I need to update the camera with canons 2.0.2 firmware prior to this, or is the formware upgrade "included" in any of the above files?

Ive followed the above guide, but I haven't upgraded the camera with canons 2.0.2. firmware, and all I get is a black screen and a blinking green diod after the update-screen.

Henrik
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 09, 2013, 04:58:21 PM
Signed version = fir
Normal version = autoexec.bin


If you're having to run the fir every time and got EOSM with 2.02 pre-installed then you're stuck with the signed version for now.

My camera came with 2.0.2 pre-installed.

I have both of those files in my root folder.   Is that correct?

What does the signed version do differently from the autoexec.bin version?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 09, 2013, 05:11:56 PM
The signed version doesn't boot flag your camera. I think you can remove autoexec.bin in this case and just use the .fir every time, you're doing it anyway.

I have no way to test because my camera has the flag and boots off autoexec.bin at start. AFAIK this is how the 5D3/EOSM alpha worked. Someone has to try it.
Title: Re: Tragic Lantern for EOS M
Post by: Henrik on August 09, 2013, 05:47:37 PM
So, here are the steps that I took, a slight modification along with correct links on Canon eos m instructions.

1. First soft format your SD card on your computer.
2. Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
3. Next download files from the bitbucket.org link (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip) provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
4. Next copy the updaterM202.fir (link on page 33 of this thread) UpDaterM.fir (http://www.qfpost.com/file/d?g=NzBmhwaBK) on your SD card.
5. Open the EOSCard link from the installation section of the 5DMarkIII home page.
6. With the SD card in the card reader open the EOSCard utility.
7. Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
8. Then copy the ML directory from the Alpha 1 (http://bit.ly/UP7Avg) version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.
9. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. (step 3)



Ive been using ML with 1.0.6 for a while. Im now trying to install the 2.0.2 version. Stupid question: Do I need to update the camera with canons 2.0.2 firmware prior to this, or is the formware upgrade "included" in any of the above files?

Ive followed the above guide, but I haven't upgraded the camera with canons 2.0.2. firmware, and all I get is a black screen and a blinking green diod after the update-screen.

Henrik

Installed the 2.0.2 update. ML works, but I have to re-flash it everytime I restart my camera. Is there any way to get around this?
I don't understand this whole bootflag thing. I thought that if I already had ML on 1.0.6 I wouldnt get this problem!?

 If someone could explain it in an easy way I would be very greatful! :)
Title: Re: Tragic Lantern for EOS M
Post by: freshbreath on August 09, 2013, 07:45:45 PM
[EOSM202] zip file (bitbucket)  (http://bit.ly/19h2otN) (add .zip file extension)
 contains MODULES folder + autoexec.bin
UpDaterM.fir file (http://www.qfpost.com/file/d?g=NzBmhwaBK)
 contains single UpDaterM.fir file
 magiclantern-EOSM.106.Alpha1.zip (http://bit.ly/UP7Avg)
 contains __MACOSX and ML folders, autoexec.bin and EOSM106.fir files.
 I believe only the ML folder is used for this install. Use the autoexec.bin from the [EOSM202] zip file.

Quote
1. First soft format your SD card on your computer.
2. Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
Ok, easy enough.

Quote
3. Next download files from the bitbucket.org link (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip) provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
So the MODULES folder + autoexec.bin gets copied straight to the root of the SD card at this point.

Quote
4. Next copy the updaterM202.fir (link on page 33 of this thread) UpDaterM.fir (http://www.qfpost.com/file/d?g=NzBmhwaBK) on your SD card.
At this point, the root of the SD card would have the following, correct:

DCIM (folder)
MISC (folder)
MODULES (folder)
autoexec.bin
UpDaterM.fir

Quote
5. Open the EOSCard link from the installation section of the 5DMarkIII home page.
6. With the SD card in the card reader open the EOSCard utility.
7. Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
At this step, Clicking the big 'ML' icon first and then clicking save worked for me. The save was practically instant, 'write successful' at the bottom of the window.


Quote
8. Then copy the ML directory from the Alpha 1 (http://bit.ly/UP7Avg) version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.
9. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. (step 3)
So only the 'ML' folder is being copied to the root of the card (not the EOSM106.fir or autoexec.bin files that come with the Alpha1 zip)?  At this point the MODULES folder should be moved inside the 'ML' folder and also copy over the _MACOSX folder to the root of the SD card.

All said and done, if the MODULES folder gets placed inside the ML folder, the root of the SD card will have the following:

_MACOSX (folder)
DCIM (folder)
MISC (folder)
ML (folder)
autoexec.bin
UpDaterM.fir

Clear your settings in the camera, go to the EOS firmware and update. After doing this, firmware update is very brief and if you don't see it right away, hitting the Info button takes you to the ML live screen. Touch the screen with two fingers and the ML menus will appear.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on August 09, 2013, 08:38:07 PM
@mixer2:

I'll compare it all next week, I have a bunch of planning for this shoot I'm directing (not to mention finishing this music video) to take up my time now lol.

I know the crop will probably be better detail, but the crop and lack of shallow depth are a bummer. I'll probably end up using them both as needed for shoots I use the EOS M for raw. As it stands now this camera is my best bet for raw video since my 60D and T2i have slow SD card controllers. If the non-crop raw on the M resolves more detail than the H264, then it will be a nice upgrade for now given that I'll get sharper images and more latitude. I don't necessarily even mind the H264 still as I still use it for a bunch of stuff, so we'll see how useful raw even is for me. Also I have no idea how to use the pixel remover thing lol.
Title: Re: Tragic Lantern for EOS M
Post by: wuxiekeji on August 09, 2013, 09:05:41 PM
What does this EOSCard utility do exactly and what are the equivalent steps for a Linux user? Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: EVVK on August 09, 2013, 10:56:14 PM
@ wuxiekeji I was on the same boat too.

Found solution under "Installing Magic Lantern on other cards" subject here:
http://magiclantern.wikia.com/wiki/Unified/Install
 make_bootable.sh

ExFAT is completly broken and at least Ubuntus fuse based exFAT refuses to even mount the card after trying so FATxx is the way to go.
Title: Re: Tragic Lantern for EOS M
Post by: PhasersOnKill on August 10, 2013, 12:21:33 AM
Hi All,

New to this forum as I recently purchased an EOS M only to find that remote capture does not work.
This is a feature that would be supremely useful to me as I tend to do a lot of self filming for vlogs.

Is there any status update on where we're at with enabling this via ML?

Any info is greatly appreciated.

Cheers!
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on August 10, 2013, 12:29:46 AM
Remote capture as in recording via EOS Utility?
Title: Re: Tragic Lantern for EOS M
Post by: PhasersOnKill on August 10, 2013, 12:48:30 AM
Remote capture as in recording via EOS Utility?

Correct. Or any software for that matter.

Title: Re: Tragic Lantern for EOS M
Post by: handbanana on August 10, 2013, 02:40:43 AM
Why don't you just use an external monitor via the HDMI or the other port (the red/yellow/white cable)?
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 10, 2013, 03:13:01 AM

About those instructions:

At this step, Clicking the big 'ML' icon first and then clicking save worked for me. The save was practically instant, nothing was written to the card. Should there have been?
So only the 'ML' folder is being copied to the root of the card (not the EOSM106.fir or autoexec.bin files that come with the Alpha1 zip)?  At this point, should the MODULES folder be moved inside the 'ML' folder? Remember that according to step 3, the MODULES folder and UpDaterM.fir were already transferred over.

So what am I doing wrong?

Keep the _MACOSX file also on the Card

Getting these combinations to work with the EOSCard utility for the EOS M is a bit tricky.

I think the steps that is not working for you is the save from the EOSCard. See the screen shot from the EOSCard after the SD is in the reader: http://www.flickr.com/photos/89977905@N05/9476620696/

(Sorry to point you to my flickr account. I don't know how to post a picture directly in-thread)  :P

The trick is to first refresh and then press save. Do it as many times as it takes. You will hit the sweet spot eventually. It took me a few tries too. 
Title: Re: Tragic Lantern for EOS M
Post by: PhasersOnKill on August 10, 2013, 04:40:28 AM
Why don't you just use an external monitor via the HDMI or the other port (the red/yellow/white cable)?


While this is a decent short term solution (thanks!) it still requires me to control from the camera which makes it a bit cumbersome.

That's why I was asking about remote view. Another thought I had was if it was possible to use an Eye-Fi card for remote view/control
over wifi?

Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 10, 2013, 05:09:23 AM
No boot flag, fir

if you had 1.06 make sure the card itself is bootable too (ie the EOSCARD step) for linux just run it in wine.

If you had 2.0.2 and no ML you need the fir file + ml folder/modules/sym

For the utility, it just may not work. The camera has to create jpegs in parallel to send over USB. Will have to log it and see.
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 10, 2013, 05:26:41 AM
Help: How do I set WB back to AUTO in ML. I set the Kelvin temperature and can change that but I no longer see AUTO as a choice. When I turn off the camera and do not boot into ML, I cannot change WB. The Wiki says nothing about getting back to AUTO.

I had to reset all settings to default in the Canon menu to get back WB control. Is this normal?
Title: Re: Tragic Lantern for EOS M
Post by: freshbreath on August 10, 2013, 06:03:00 AM
Keep the _MACOSX file also on the Card

Getting these combinations to work with the EOSCard utility for the EOS M is a bit tricky.

I think the steps that is not working for you is the save from the EOSCard. See the screen shot from the EOSCard after the SD is in the reader: http://www.flickr.com/photos/89977905@N05/9476620696/

(Sorry to point you to my flickr account. I don't know how to post a picture directly in-thread)  :P

The trick is to first refresh and then press save. Do it as many times as it takes. You will hit the sweet spot eventually. It took me a few tries too.

Ok, turns out I had it the first time. I see the ML menu when I use two fingers to touch the screen. The MACOSX folder did need to be copied over.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 10, 2013, 06:14:09 AM
No boot flag, fir

if you had 1.06 make sure the card itself is bootable too (ie the EOSCARD step) for linux just run it in wine.

If you had 2.0.2 and no ML you need the fir file + ml folder/modules/sym

For the utility, it just may not work. The camera has to create jpegs in parallel to send over USB. Will have to log it and see.

I think this is functionality that a LOT of people will want:  remote shooting.

Separate topic now.  I have the new EOS-M and it came with the 2.0.2 firmware installed.  I've gone through what I understand to be the ML installation process and I have these folders and files:

DCIM -- for photos
MISC -- currently empty
ML -- subfolders: DATA (contains FONTS.DAT file), MODULES (contains modules), SETTINGS (contains MAGIC.CFG file)
autoexec.bin  (381K)
UpDaterM.fir  (393K)

My MODULES sub-folder contains the following files:

EOSM_202.sym (34K)
ETTR.CFG (1K)
ettr.mo (17K)
file_man.mo (14K)
pic_view.mo (5K)
RAW_REC.CFG (1K)
raw_rec.mo (33K)

Are those the correct files for the MODULES sub-folder?  Do I have all of the needed files?

Also, what about a SYM sub-folder?  Is one needed?  If so, does it go under the MODULES folder?  And if so, what should it contain (and where to get the files)?

Note: when flashing the firmware (I have to do this every time I start the camera), I get the following message:

"ML/CROPMKS dir is missing"  What is this all about and how do I fix it?

*** Many thanks in advance for help with all of this ! ***
Title: Re: Tragic Lantern for EOS M
Post by: freshbreath on August 10, 2013, 06:28:19 AM

Note: when flashing the firmware (I have to do this every time I start the camera), I get the following message:

"ML/CROPMKS dir is missing"  What is this all about and how do I fix it?

*** Many thanks in advance for help with all of this ! ***

In your case it seems to be looking for folders/files found in __MACOSX directory of the Alpha zip. Copy that over to the root directory of your SD card as well.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 10, 2013, 09:19:52 AM
Ok, turns out I had it the first time. I see the ML menu when I use two fingers to touch the screen. The MACOSX folder did need to be copied over.

We're you able to get the ML update working on the EOSM?
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 10, 2013, 01:35:58 PM
In your case it seems to be looking for folders/files found in __MACOSX directory of the Alpha zip. Copy that over to the root directory of your SD card as well.

Hmm...  interesting.  What do those folders/files do?  What do they have to do with "crop marks?"  Why __MACOSX?
Title: Re: Tragic Lantern for EOS M
Post by: freshbreath on August 10, 2013, 06:06:30 PM
We're you able to get the ML update working on the EOSM?

I did, thank you. Turns out I had done it right the first (or second) time. I was expecting the ML green install screen to show up but this method is a different type of install.

Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 11, 2013, 03:38:36 AM
a test i did today:
http://dl.dropbox.com/s/p1qo960nrhmcd7g/crop_vs_non_crop.webm

1. 18mm raw video crop mode (no sharpening, some saturation added)
2. 55mm raw video non crop mode (no sharpening, some saturation added), @handbanana: that's why i said, that non crop mode is just not usable
3. 55mm h.264 auto picture style
4. 18mm h.264 video crop mode auto picture style
5. same as 1. but with a lot sharpening
6. same as 3. with the same sharpening as 5.
7. same as 1. with noise reduction, additional saturation and a lot of sharpening

i should have added 3 more pixels to the letterbox at top and bottom to cut the distorted rows. -.-
what the video imho shows:
- h.264 crop mode is bit softer than h.264 but still usable and of course there is much less aliasing
- crop mode raw video on eos m looks really great... less aliasing than h.264 non crop mode and flat image that has imho a very cinematic look out of the box.
- again, raw non crop mode imho isn't usable!!
- h.264 also doesn't has perfect edges (if that lowers the expectations what you should get out of the raw)
- you can add a lot more sharpening to the raw video than to the h.264 in post, without overdoing it and getting to bad sharpening artifacts. this also leads to a sharper overall result.

EDIT:
something totally went wrong with my export from yesterday. hadn't really checked it after export and expected it to be nearly the same i saw in the editor. but as i watched the exported video today i saw that the quality was much worse, because the editing software exported 24i instead of 24p.
i did a fresh export and updated the link...
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 11, 2013, 05:19:08 AM
Hmm...  interesting.  What do those folders/files do?  What do they have to do with "crop marks?"  Why __MACOSX?

Ok, I've created the CROPMKS folder under ML and placed a couple of cropmark (bmp) files there from the library.

I've selected one from the ML menu and have enabled cropmarks, but they don't show up in either video record mode or standard still image mode.  What might I be doing wrong?  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on August 11, 2013, 08:02:43 PM
I played around with the ML successfully on my EOS-M... but I can't, for the life of me, get video in high-bit-rate or Raw video right on my part.

In order to do RAW, do I shot in Camera or Movie Mode, and do I shoot in the Menu button or LiveView (if so, where is the LiveView mode)?

Also, how do I obtain a slightly higher bit rate other than 45+.

Still a newbie at all of this, but quite fascinated so far.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 11, 2013, 08:37:47 PM
I know there are many people who are focusing on video and want make their camera to be a top tier video shooter. But can we also spend some time to improve the photo functions such as the magic room since this is a camera after all?
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 11, 2013, 08:39:22 PM
And also we are really eager to see eyefi card support since the 5d2 ml has supported it.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 11, 2013, 09:08:08 PM
Well first I want to fix the installer... I have no eye-fi card so its kinda hard to test for something I haven't used. MZ and display filters are the next top fixes for this but they haven't been done for lack of trying.. its just kind of a tough nut to crack.
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 11, 2013, 09:16:59 PM
Well first I want to fix the installer...

Yes - that sounds like a very good idea! I guess it will help trying and testing the functions of ML on the EOS M without being irritated by just geting it to work somehow.  :)
Anyway ... it´s still fantastic to read how much efford you put in your ML work. Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 11, 2013, 10:16:28 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 12, 2013, 12:23:55 AM
+1 on fixing the installer. It's a real PIA always having to to install thru update firmware each time. :-) I have also asked a few easy questions here and no one ever answered. Is there another way to get into ML menus besides a two finger swipe? I only have one finger from a car accident and its difficult for me always needing to use two toes and leave a shoe off all the time. LOL J/K, but I would rather have the Menu button open ML menus. And, how do I exit ML menus? I have been waiting until it exits on its own. I would rather the menu stays open and then we hit some button to close the menus. The menus keep shutting off on me while I try to read and learn things within them. Then I have to swipe the display again with two toes to continue with where I left off. :-)

Gary

+1000!  Amen.
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on August 12, 2013, 09:13:30 AM
Here's something I did using the ML Timelapse method.  The ungraded master I had (png to losless codec) was close to 1GB, were graded afterwards.

Anyways, I like the timelapse as a tester I did.

Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 12, 2013, 02:00:36 PM
Can someone say what is the largest 4:3 size that can be recorded in crop mode at 24p

I dont have EOSM.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 12, 2013, 09:02:27 PM
1024x768 (31,4 mb/s) or maybe 1088x816 (35,5 mb/s)... i would choose 1024x768 to be sure that it doesn't stop or skip frames after some minutes. the few extra pixels at 1088x816 shouldn't make much difference in quality. ml says continous recording ok, but for me it stopped after ~2 mins with 1088x816.
i can upload some 1024x768 sample shots tomorrow if they may help to judge the quality.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 12, 2013, 11:18:52 PM
I couldn't seem to find this, but does defishing supposed to work with EOS-M?

How do you use it? (there's no liveview button on it)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 13, 2013, 12:33:58 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 13, 2013, 12:41:21 AM
Hi mixer2,

a 2 sec raw file of a flower or similar would be most appreciated, at your convenience of course.  Something I could evaluate and also try some PDR on

Thanks

1024x768 (31,4 mb/s) or maybe 1088x816 (35,5 mb/s)... i would choose 1024x768 to be sure that it doesn't stop or skip frames after some minutes. the few extra pixels at 1088x816 shouldn't make much difference in quality. ml says continous recording ok, but for me it stopped after ~2 mins with 1088x816.
i can upload some 1024x768 sample shots tomorrow if they may help to judge the quality.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 13, 2013, 12:46:48 AM
@JohnBarlow:
ok, i'll send you some samples tomorrow...

@gary2013:
could you upload a sample... it's hard to guess what's going wrong, without seeing the result.
do you have removed the af dots? is it really noise or blue and pink dots (small crosses)? af dots go all over the image in crop mode and from left to right, but just in the middle in non crop mode.
raw video is btw always more noisy than h264, since h264 is already noise filtered in camera. you should use a good noise filter.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 13, 2013, 01:18:06 AM
Quote
I couldn't seem to find this, but does defishing supposed to work with EOS-M?

New Peaking
Defish
Anamorphic

All of these things need a good vsync to work in video mode. Right now only in photo review mode.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 13, 2013, 01:19:01 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 13, 2013, 03:02:10 AM
I have everything installed, ML is running, but when I try RAW video, the light starts blinking indicating it's recording? but no files show up on SD.

also, I have to re install the FW each time I reboot cam, is this a current issuing being worked around right now?
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 13, 2013, 07:35:15 AM
New Peaking
Defish
Anamorphic

All of these things need a good vsync to work in video mode. Right now only in photo review mode.

I see! How do I trigger defish and anamorphic preview in photo review mode? Tried everything but nothing seems to work...
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 13, 2013, 10:28:46 AM
@gary2013:
Try to remove the dots with this tool:
http://dl.dropbox.com/s/m0bxzd23p4zow8o/PinkDotRemover_2013_08_08.zip

you need to have java jre installed to run the tool. (you can find it there, if it isn't already installed http://java.com/en/download/index.jsp)
if java is installed unzip the PinkDotRemover and doubleclick onto the PinkDotRemover.jar file.
to remove dots just drag and drop the RAW or the DNGs files onto the white area at the left of the tool. you can also use the "Add files"-Button, instead of drag and drop. then select EOSM or Crop Mode from the dropdown.
you should have two types of video:
1. dots are all over the image + image is not vertically squeezed (=> Crop Mode)
2. dots are just in the center + image is vertically squeezed (=> EOSM)

be sure to select "interpolate" at the radio buttons below the dropdown.
then click "Convert Files". If you've added a RAW-file it gets overwritten (so you should make a copy first), if you added DNGs you should find in the same folder copys of the DNG files with a _ prefix. the dots should be gone in that new files.

cloud storages work very well to post images, video etc. for example dropbox, box.com, google drive (if you've already a google account), skydrive (if you've already microsoft/hotmail account), etc etc...
or upload it to a file bin service like this, as long as the files aren't to large (max 20MB):
http://www.qfpost.com/

as noise filter i prefer neat video. there are after effects and premiere plugins for it and it can be testet with a free demo.
but there are also a lot of other noise filters, also free ones, you can use. just do any noise filtering on raw video, since it has a lot of noise, even at iso 100.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 13, 2013, 11:54:37 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 13, 2013, 02:58:37 PM
I dont have EOSM, so can someone say what is max number of frames @24p 1280x720 in crop mode?

With fastest card

Thanks
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 13, 2013, 03:28:13 PM
I  got 2897 Frames at 1280x720 24p, with 32gb sandisk extreme 45MB/s (=> the sd-controller is the bottleneck).
i'll do the flower testshot in few mins... just have to finish some work first.
Title: Re: Tragic Lantern for EOS M
Post by: Rush on August 13, 2013, 03:32:56 PM
I dont have EOSM, so can someone say what is max number of frames @24p 1280x720 in crop mode?
unlimited
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 13, 2013, 03:34:39 PM
Thanks
I  got 2897 Frames at 1280x720 24p, with 32gb sandisk extreme 45MB/s (=> the sd-controller is the bottleneck).
i'll do the flower testshot in few mins... just have to finish some work first.
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 13, 2013, 03:35:26 PM
Impressive!, what card did you use?

unlimited
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 13, 2013, 03:36:39 PM
One more question

Can you record avchd in 3x crop mode or is is just for RAW record?
Title: Re: Tragic Lantern for EOS M
Post by: Rush on August 13, 2013, 05:00:00 PM
Impressive!, what card did you use?
SanDisk 95 mb/s

Quote
Can you record avchd in 3x crop mode or is is just for RAW record?
Yes, moire/aliasing-free 3x H.264.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 13, 2013, 05:01:11 PM
@rush:
have you tested it or trusted the ml prediction?

@JohnBarlow:
you can record h.264 in crop mode. looks bit softer than h.264 in non crop mode, since it's a 100% crop.
check the video i posted few posts above:
http://dl.dropbox.com/s/p1qo960nrhmcd7g/crop_vs_non_crop.webm
the 3rd part (sec 10-15) is h.264 55mm in non crop mode and 4th (sec 15-20) is h.264 18mm in crop mode.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 13, 2013, 05:11:09 PM
SanDisk 95 mb/s
Yes, moire/aliasing-free 3x H.264.

Is this the same movie crop mode in ML? I still get moire with this on. Have you tried shooting a test chart?
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 13, 2013, 05:15:05 PM
@rush, @mixer2

Thanks, very useful information on the crop modes, better aliasing in crop mode and maybe a sharper lens can improve things. The 22mm is supposed to have very sharp centre performance

To summarise in 3x ML crop mode you can
1 record h264 at 1080p, no PDR required
2 record RAW at 720p with a 95 MB card and use PDR
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 13, 2013, 05:24:26 PM
@JohnBarlow:
i really don't think that the 95mb/s card would give you any benefit.

@feureau:
technically 100% crop doesn't mean no aliasing. i read that multiple times, but it's still a digital measurement, which means, if you're signal (the light that comes from the lense) has more detail than your sensor resolution you'll get aliasing effects.
since sensors have such high resolutions and lenses aren't that sharp, it's hard to get any aliasing with 100% crop. and it's definitely much better than without crop.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 13, 2013, 06:07:30 PM
On 6D I can record 720P continuously so I don't see why it wouldn't work here. Its pretty much the same controller.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 13, 2013, 06:17:41 PM
it stopped for me after 2897 frames...
6d may have more buffer? maybe if the speed slightly varyies the eos m just can't compensate it with the small buffer?

Its like 6D controller.. so sandisk 45MB/s is the fastest..

and it stopped for me with sandisk 45MB/s.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 13, 2013, 06:32:12 PM
Possibly. 255M vs ~100M in photo mode on a good day.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 13, 2013, 07:35:45 PM
I don't see much meaning in crop mode video. The crop result of a 22mm lens is definitely far different from a full 50mm f/1.4 lens effect. Especially in terms of field depth.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 13, 2013, 08:13:52 PM
@JohnBarlow:
i'm uploading some raw files for you at the moment. 3gigs... it may take some time. as soon as it's ready there are 11 raw files. resolutions 1280x720, 1024x768 and 1088x816.
https://www.dropbox.com/sh/ofaqeiwwjg0xdrw/HAYYgd9cXk

there are also some h.264 shots with 18mm crop and 55mm non crop for comparison and a 1280x720 24p webm file with the processed raw video files. no real post processing on the webm... just used the default canon raw curve to get some contrast into the image, no noise reduction or sharpening.
http://dl.dropbox.com/s/k8fe71ga1kiw57o/720.webm

720p raw looks much better than i thought. and so much better than h.264 1080p, even without processing Oo
but of course i could have done h.264 better with reduced saturation, contrast and sharpening... it's auto picture style.

can anyone check if faster card really makes a difference to get continuously 1280x720 24p recording?
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 13, 2013, 08:24:04 PM
@mixer2

Thanks for your time, it has convinced me to get an EOSM with MLRAW,
 
who needs a Black Magic pocket cam? :)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 13, 2013, 10:21:56 PM
anyone has experience with the SanDisk SDSDQX-064G-U46A... it's a microSD, but benchmarks look nice and price is very moderate.
i really want to know if we can get more speed (maybe really 36mb/s continuously) with a faster sd-card than sandisk extreme 45mb/s.

or maybe anyone has the 45mb/s sandisk extreme and the 95mb/s and can compare them directly in the eos m.
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 13, 2013, 10:38:48 PM
Anybody know anything about this clip other than what's mentioned? Like exact ML settings and workflow?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 13, 2013, 11:11:25 PM
it was posted by qsara on page 19 of this thread. but the qsara account seems to be deleted.

as the video says it's 1664x464 30fps non crop mode. you can't get that resolution anymore, but 1664x456, if you don't need continuous recording at 24 fps, or 1664x428 (1600x438, if you prefer that aspect ratio) for continuous recording. as the video is recorded at 30fps i think the 21secs was the maximum that could be recorded on that resolution and framerate.

as qsara said on page 19 it's recorded at 100iso. there are not much more camera parameters... i guess medium focal length and aperature wide open. there is no way see what shutter speed is used without motion in the video, but with 30fps normally 1/50 or 1/64 is used.

in post it got unsqeezed and some color correction (i guess whitebalance, added saturation, added contrast and it looks like a warmify filter or something like that was added). since there was no dot remover at that time and it's hard to spot any dots, i think the dots got removed with a dead pixel filter in the raw editor.

everything just guesses, don't really know what qsara did. but if you tell us what exactly from the video you try to achieve maybe anyone finds a solution.
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 14, 2013, 04:13:05 AM
I made a video from shooting RAW at 1280 x 720, 24 fps, in crop mode. Using a Sandisk Extreme sd card, I was getting about 35 MBps and could shoot, according to the camera, over 2400 frames before stopping.


My workflow:

Dot-removed the RAW clips.
Obtained the .dng frames from the dot-removed RAW files.
Used Lightroom 5 to convert the .dng files to uncompressed .tiff files using default settings.
Used Vegas Pro 11 to edit the string of .tiff files to create the 720p video at 24p, using AVC compression and light sharpening using unsharp mask.
Title: Re: Tragic Lantern for EOS M
Post by: Rush on August 14, 2013, 09:28:33 AM
Is this the same movie crop mode in ML? I still get moire with this on. Have you tried shooting a test chart?
I can get it, but it is very very little, comparing to non-crop mode.

Quote
technically 100% crop doesn't mean no aliasing. i read that multiple times, but it's still a digital measurement, which means, if you're signal (the light that comes from the lense) has more detail than your sensor resolution you'll get aliasing effects.
technically 100% crop don't use lineskipping. aliasing and moire comes from the gaps of lineskipped pixels, and gaps becomes minimal in 100% crop mode.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 14, 2013, 10:45:58 AM
@markr041:
looks nice. it would be interessting if you could get more frames.. as i wrote it stopped for me after 2897 frames...

@Rush:
"aliasing and moire comes from the gaps of lineskipped pixels"

afaik, that's not true... any references?
it's all about frequencies... if you've too high frequencies (not the frequency of the light, but the singal frequency) for your sensor, then you'll get aliasing. check the "Nyquist theorem". http://redwood.berkeley.edu/bruno/npb261/aliasing.pdf
it's a gernal problem of sampling analog singals.
of course line skipping makes it even worse, because it heavily reduces the sampling frequency.
the only reason why you don't see much aliasing at 100% is that the lenses aren't that sharp and act like a low-pass filter.
=> sharper lense = more aliasing
Title: Re: Tragic Lantern for EOS M
Post by: Rush on August 14, 2013, 12:15:18 PM
of course line skipping makes it even worse, because it heavily reduces the sampling frequency.
the only reason why you don't see much aliasing at 100% is that the lenses aren't that sharp and act like a low-pass filter.
=> sharper lense = more aliasing
yes, I agree. But for me - without lineskipping aliasing is acceptable and hardly noticable (even with the sharpest lens I have), comparing to lineskipped image where aliasing become obvious.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 14, 2013, 02:40:36 PM
@1%:
since dual iso does also work on 6d and 5d ii, is there any chance that it may also come to eos m? or does it just has a single amplifier?

@JohnBarlow:
the large upload of the test raw files from yesterday is now finished.
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 14, 2013, 05:33:47 PM
@mixer2

Got them, Thank you very much.

Can you confirm my current understanding?

Crop mode is about 3x, giving a recording sensor width of 22.5/3 = 7.5mm

720p would give about 2/3 of that resulting in a recording sensor width of 5mm

Is my calculation correct? Thanks
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 14, 2013, 05:52:58 PM
EOS m has
5184x3456 pixels on 22,2mmx14,7mm

with 1280x720 crop mode you use 5184/1280 ~ 24,69% of the horizontal and 720/3456 ~ 20,83% of vertical pixels.
14,7mm*0,2083 ~ 3,06mm
22,2mm*0,2469 ~ 5,48mm

sqrt((3,06mm)²+(5,48mm)²) ~ 6,27mm

if my calculations are correct you'll use a diagonal of ~ 6,27mm with 720p

43.2mm/6,27mm ~ 6,89 <- this should be the effective crop factor

compared to bmpcc which has a super 16mm diagonal of 14,54mm and 2.97 crop factor, it's a really tiny sensor. less than 1/4 of effective sensor size.
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 14, 2013, 06:34:47 PM
Thank you for a very precise answer
Title: Re: Tragic Lantern for EOS M
Post by: manly on August 15, 2013, 06:15:41 AM
Here is my understanding of the problem. Feel free to correct me.

The only real limitation we have is how to fit a 16:9 aspect ratio in a 3:2 sensor. In other words, 5184 pixels wide (or rather, a bayer-patterned mosaic of 5184 pixels wide) by 2916 pixels, cropping 540 pixels top+bottom combined.

Our cropped 5184x2916 (16:9) video is clearly above 1080p (and the write speed). We only need to resize those into either 720p (1280x720) or 1080p (1920x1080). If the digic5 processor is having a hard time doing this, then how about, in the case of 720p (where we need to cut to 24.69%), take 8x8 pixels (bayer-pattern) and reduce that to a 2x2 by averaging the bit-depths of the corresponding colors to the smaller matrix? You would get an exact 1280x720 pixel (720p) by cropping to 5120x2880, which would be fairly close to the full 5184x3456. This operation, under x86 cpus, would be both easy to code and quick to execute.

For 1080p it would be a bit trickier, since 1920/5184 = 37.03% doesn't rounds nicely. I'll let the knowledgeable people first see if my idea makes sense then I'll see if 1080p raw is even feasible (might not even be with write speed bottleneck).
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 15, 2013, 10:40:31 AM
@manly:

sorry, no... i think everyone wishes that would be the "only real limitation".
it's not possible to record 5120x2880 because of the speed of the sd-controller. there are 2 raw streams to choose from. one is downscaled via row and lineskipping (which leads to really bad quality) and the other is a 100% sensor crop (1792x1028 cropped from the center).
but, since 1792x1028 are still to much pixels to record (continuously... you can record a few frames till it stops), it's even more cropped to ~5% of the sensor size.
=> you can get thise 5% of the pixels from all over the sensor with a lot of aliasing, or from the center, which leads to a high crop factor.

main limitations are sd-controller speed and the bad quality of internal downscaling.
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on August 15, 2013, 10:54:18 AM
@mixer2:

I'm still puzzled as to why the non-crop mode is squished. That doesn't happen on my 60D or T2i, although I did see there was a squished option when recording at 720p resolution in movie mode on the 60D.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 15, 2013, 11:19:53 AM
i think the eos m handles the downscaling different from other canon cameras... but really don't know.
have you watched the video i posted some days ago: http://dl.dropboxusercontent.com/s/p1qo960nrhmcd7g/crop_vs_non_crop.webm

the first 10 secounds show crop mode vs non crop mode... and what i see is that non crop mode has really bad quality compared to crop mode.
maybe 1% can tell you why the downscaled videos on other cameras don't look that bad.
Title: Re: Tragic Lantern for EOS M
Post by: Eran on August 15, 2013, 02:26:20 PM
It will be interesting to see a comparison with the BMPCC Prores in the near future . I wander if anyone thinking the same as I do.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 15, 2013, 02:56:20 PM
It will be interesting to see a comparison with the BMPCC Prores in the near future . I wander if anyone thinking the same as I do.

Speaking of prores. I wonder how they managed to put that in the BMPCC when the canons don't have enough computing power to convert raw to prores... Dedicated prores chip?
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 15, 2013, 03:02:16 PM
Hi guys, any news about the magic zoom function improvement? I heard a new patch was just released.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 15, 2013, 03:22:30 PM
MZ is at least in sync in most modes, but not much different.

Its ugly at idle because its always 720P sized. Other cameras ugly mode is only 60FPS and all modes are like crop mode minus the crop.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 15, 2013, 05:26:51 PM
MZ is at least in sync in most modes, but not much different.

Its ugly at idle because its always 720P sized. Other cameras ugly mode is only 60FPS and all modes are like crop mode minus the crop.

Err, not quite understand the statement. Just want to know if it's possible to use the magic zoom with higher resolution according to the magnification factor?
Title: Re: Tragic Lantern for EOS M
Post by: handbanana on August 15, 2013, 05:42:26 PM
@Mixer2:

Yeah I saw the video, and even based on further testing I did I've seen what you mean. Plus upscaling that much is still not ideal. But what I mean is on the other cameras the raw video in regular (non crop) mode isn't vertically squished so when you upscale you upscale both x and y.
Title: Re: Tragic Lantern for EOS M
Post by: Drizzt321 on August 15, 2013, 07:29:58 PM
Speaking of prores. I wonder how they managed to put that in the BMPCC when the canons don't have enough computing power to convert raw to prores... Dedicated prores chip?

Either implemented in hardware, or more likely using some GPU Compute resources to do some of the work (the latest Tegra based design comes to mind) or a dedicated DSP plus a multi-core ARM chip probably makes it doable without being too expensive either from a cost or power design. It'd be interesting to know what they've done actually. Although, I don't actually know that ProRes is really a heavily compressed for mat. Probably doesn't take much more computing resources over h.264, just a higher write bandwidth is required. Maybe more CPU if there's no hardware dedicated to it.
Title: Re: Tragic Lantern for EOS M
Post by: manly on August 15, 2013, 09:19:25 PM
@manly:
sorry, no... i think everyone wishes that would be the "only real limitation".
it's not possible to record 5120x2880 because of the speed of the sd-controller. there are 2 raw streams to choose from. one is downscaled via row and lineskipping (which leads to really bad quality) and the other is a 100% sensor crop (1792x1028 cropped from the center).
I was talking specifically about how to code an algorithm that would not crop anything (beyond black bars to fit a 16:9 ratio (720p or 1080p) in a 3:2 ratio). The algorithm I described is not CPU intensive, easy to compute, and recreates your new RAW layer from the uncropped RAW data. I *do* assume the full resolution is available and you seem to suggest it's not. Are you saying the lineskip raw stream is directly provided by the canon code and 100% outside of our control? If that lineskip stream is ML code, I described a way to fix both issues...
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 16, 2013, 12:58:41 AM
Hello everyone.  Was very excited to set up my new EOS-M to shoot RAW today.  Having used the 50D was a blessing because I already had an idea of what to do.  Still, I spent half an hour trying to figure out how to start the recording (MENU button) 

Is there any set of settings that removes the red dots?  I don't believe resolution is as important as the color depth you can get from RAW.  I'm also a little confused about how the camera's movie menu settings interact with the ML settings under photo, if at all.  Anyway, great work!

Please let me know if you'd like me to shoot anything, or do anything that would be helpful to you.  I always try to shoot faces because I believe they show the real limitations of AVCHD (skin color). 

Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 16, 2013, 02:24:37 AM
What was your workflow? What resolution? what frame rate? crop mode?

You can remove the red dots quickly and easily with a little software program:

http://dl.dropbox.com/s/m0bxzd23p4zow8o/PinkDotRemover_2013_08_08.zip

It works directly on the RAW files and you can do all of them at once (in batch).

See my video from RAW:

No dots.
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 16, 2013, 02:45:35 AM
Anybody else see blue dots in some of their footage? mainly shadows it looks like?
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 16, 2013, 03:54:53 AM
Hello everyone.  Was very excited to set up my new EOS-M to shoot RAW today.  Having used the 50D was a blessing because I already had an idea of what to do.  Still, I spent half an hour trying to figure out how to start the recording (MENU button) 

Is there any set of settings that removes the red dots?  I don't believe resolution is as important as the color depth you can get from RAW.  I'm also a little confused about how the camera's movie menu settings interact with the ML settings under photo, if at all.  Anyway, great work!

Please let me know if you'd like me to shoot anything, or do anything that would be helpful to you.  I always try to shoot faces because I believe they show the real limitations of AVCHD (skin color). 


Cute video. Really like the subjects innocence and willingness to be part of the experiment. Please say so to her from me, with my regards.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 16, 2013, 04:12:22 AM
@Canon eos m.  It pays to be nice to your wife!  She said as long as I don't put it on FB.  I talk my kids into being subjects too, but they can run away faster ;)

With Mark's help, I was able to do a version without pink dots

Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on August 16, 2013, 04:32:55 AM
Hey everyone,

First off, thanks to the ML guys for putting time into this lil camera. I''m loving it. I'm glad to see it on 2.0.2.


Now, to the point: I've been into bracketing lately and the adv. bracketing feature has a couple problems with the current version. In order to get the shutter to release, I have to quickly restart the camera and hope the ML firmware is still loaded. Ever since firmware 1 w/ ML alpha, the camera autofocuses between shots. It would be great if the camera would not focus after the initial focus and would instead shoot in continuous mode.

1% owns :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 16, 2013, 02:35:58 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 16, 2013, 04:01:37 PM
@gary2013:
normally you'll find new versions there:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/

@maxotics:
with crop mode there won't be those aliasing effects at the edge of the glasses.

@gravitatemediagroup:
can you upload a pic to show us the dots?

@manly:
sorry, i don't know the exact details. maybe one of the ml developers may answer it more detailed.
as far as i know there is no way to get the full sensor resolution. and even if it would be possible the cpu is to slow to do any processing in camera. and it's not possible to do the processing in post, because the sd-controller is to slow to save all the data.

@handbanana:
i don't know any details here, too. it's just the way it seems to be on eos m. maybe canon saves some resources in the small body. again, maybe one of the ml developers may give a more exact answer. they know better what's going on in the cameras.
i can just tell you what my experiences using it are. and they are that non crop mode has horrible quality.
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on August 16, 2013, 06:25:00 PM
What was your workflow? What resolution? what frame rate? crop mode?

You can remove the red dots quickly and easily with a little software program:

http://dl.dropbox.com/s/m0bxzd23p4zow8o/PinkDotRemover_2013_08_08.zip

It works directly on the RAW files and you can do all of them at once (in batch).

See my video from RAW:

No dots.


How do you use the PinkDotRemover, do you apply it with the camera, or is this for computer use?
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 16, 2013, 08:17:37 PM

How do you use the PinkDotRemover, do you apply it with the camera, or is this for computer use?

My steps with EOS-M so far
1. Follow steps in other posts to get it ML to work with Firmware 2.02 (if that's what you have)
2. Boot camera, load ML, load modules (set to autoload), set to RAW, resolution, etc., in ML.
3. Press MENU, take some RAW video.  I wouldn't shoot a lot your first try. 
4. Copy RAW file over to computer
5. Load PinkDotRemover (THANK YOU AUTHOR OF THAT).  You'll need Java installed.
6. Make a copy of your RAW file if important (PinkDotRemover) modifies original.
7. Drag copy or original to PinkDotRemove, pick camera, and run.  NOTE: You won't see a status message, but it should finish in a minute or two. It will say so.
8. Open RAWanizer, select RAW file
9.  Pick Cineform and have it create video output

That's my easy workflow at moment.   I use that for 50D too (except for PinkDotRemover, which isn't necessary for that camera).
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on August 16, 2013, 09:05:27 PM
My steps with EOS-M so far
1. Follow steps in other posts to get it ML to work with Firmware 2.02 (if that's what you have)
2. Boot camera, load ML, load modules (set to autoload), set to RAW, resolution, etc., in ML.
3. Press MENU, take some RAW video.  I wouldn't shoot a lot your first try. 
4. Copy RAW file over to computer
5. Load PinkDotRemover (THANK YOU AUTHOR OF THAT).  You'll need Java installed.
6. Make a copy of your RAW file if important (PinkDotRemover) modifies original.
7. Drag copy or original to PinkDotRemove, pick camera, and run.  NOTE: You won't see a status message, but it should finish in a minute or two. It will say so.
8. Open RAWanizer, select RAW file
9.  Pick Cineform and have it create video output

That's my easy workflow at moment.   I use that for 50D too (except for PinkDotRemover, which isn't necessary for that camera).

Thanks a lot.  I shall try that out next time.
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 16, 2013, 10:47:39 PM
My steps with EOS-M so far
1. Follow steps in other posts to get it ML to work with Firmware 2.02 (if that's what you have)
2. Boot camera, load ML, load modules (set to autoload), set to RAW, resolution, etc., in ML.
3. Press MENU, take some RAW video.  I wouldn't shoot a lot your first try. 
4. Copy RAW file over to computer
5. Load PinkDotRemover (THANK YOU AUTHOR OF THAT).  You'll need Java installed.
6. Make a copy of your RAW file if important (PinkDotRemover) modifies original.
7. Drag copy or original to PinkDotRemove, pick camera, and run.  NOTE: You won't see a status message, but it should finish in a minute or two. It will say so.
8. Open RAWanizer, select RAW file
9.  Pick Cineform and have it create video output

That's my easy workflow at moment.   I use that for 50D too (except for PinkDotRemover, which isn't necessary for that camera).

PinkDotRemover does have a moving green status bar as it proceeds, with reports of number of RAW files processed as well.

This workflow using an intermediate lossy codec (Cineform) may not provide the best results, compared with taking the .pngs from the RAW and converting them losslessly to tiffs and working with them in an NLE. In any case, I could not find a way to change the characteristics of the Cineform file (bitrate) in RAWanizer. The Cineform bitrate I got was around 60Mbps, a bitrate I can get using ML for the AVC video produced by the camera (EOS M) without RAW, and AVC uses more sophisticated compression.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 16, 2013, 11:35:39 PM
@Markr041  Does the bitrate really matter here?  My understanding is that Cineform is a compressed RAW type CODEC, so keeps a lot of sensor information which can be worked on in an NLE.  It seems that way to me at any rate.  I have Vitaliy hacks on my GF1, and the files are larger, but I don't see RAW type dynamic range coming through.  I think a high bitrate can/does improve sharpness by doing less transforms.  I converted some of my RAW files to NDxHD, which is know is huge, but I  see little difference because I think the amount of usable information from the 50D and EOS-M RAW is not really up to large bit rate needs.  I certainly agree with you that working with the RAW frames (TIFF or DNG) would give the best quality.  I hope to do that soon.   I'm just waiting until I master the Cineform stuff, which I"m still working on.  Maybe someone here can chime in, unless you're sure a higher-bit rate MP4 is better than Cineform. 

My workflow is RAW -> Cineform -> Vegas Studio.   What do you think the best workflow is?  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 17, 2013, 12:50:58 AM
Well, for example, the popular intermediate codec ProRes, and used in the BlackMagic cameras for example, has a bitrate in the 100's (224Mbps). So, 60Mbps seems low, and thus something must be sacrificed. The Cineform avi still has 4:2:2 sampling and presumably keeps the RAW dynamic range, so it has advantages over the AVC from the camera,  but subjecting the video to double compression (Cineform and then the NLE), given the Cineform bitrate, may not be ideal. I certainly don't know. And the RAW to TIFF conversions are a big hassle.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 17, 2013, 02:21:54 AM
Per a discussion higher up in the thread, the Black Magic will use the whole sensor, instead of sampling or a crop used by the EOS-M. How well it will write to SD cards remains to be seen.  I can't see the old Canon cameras as competing with the new BlackMagic pocket camera.  For me, I'd be thrilled to get 720p with high dynamic range, when I want to get the mood of film.  The EOS-M body is about $250 and the BMPCC will be $1,000.  Maybe the ML RAW in EOS-M (and other Canon cameras) will be enough for most. I"m sure the BMPCC won't approach the ML Canons in the amount of stuff they can do, from photography, to time-laps, to histograms, etc., etc. 

What I"ve noticed, markr041, is that many people who shoot video with cameras don't recognize that RAW, even at low resolutions, can have a more pleasing look than the highest bit-rate AVCHD at 1080p.  My opinion, so far.  We'll see.  Right now, my EOS-M isn't loading ML so I'm RAW-less at the moment.  :(  Working on it...
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 17, 2013, 02:31:03 AM
Fixing corrupt, ML screen doesn't stay on, camera freezes, problem.

Re-formatted my card and put all the ML stuff on it and the camera still wouldn't show the ML menu for more than a second and then would freeze.  After CLEARING SETTINGS under the menu, ML works fine again.
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 17, 2013, 04:59:27 AM
@maxotics: Glad to hear your EOS M is back up, and that the fix was simple. I agree, there is more to videos than resolution, and color and dynamic range should be better from RAW, and that is important.
Title: Re: Tragic Lantern for EOS M
Post by: thegunshow101 on August 17, 2013, 08:39:46 AM
My steps with EOS-M so far
1. Follow steps in other posts to get it ML to work with Firmware 2.02 (if that's what you have)
2. Boot camera, load ML, load modules (set to autoload), set to RAW, resolution, etc., in ML.
3. Press MENU, take some RAW video.  I wouldn't shoot a lot your first try. 
4. Copy RAW file over to computer
5. Load PinkDotRemover (THANK YOU AUTHOR OF THAT).  You'll need Java installed.
6. Make a copy of your RAW file if important (PinkDotRemover) modifies original.
7. Drag copy or original to PinkDotRemove, pick camera, and run.  NOTE: You won't see a status message, but it should finish in a minute or two. It will say so.
8. Open RAWanizer, select RAW file
9.  Pick Cineform and have it create video output

That's my easy workflow at moment.   I use that for 50D too (except for PinkDotRemover, which isn't necessary for that camera).

Sorry but converting the RAW file direct to Cineform is missing the most critical point of color correcting directly from the RAW source....  This is not the correct way.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 17, 2013, 02:13:57 PM
Sorry but converting the RAW file direct to Cineform is missing the most critical point of color correcting directly from the RAW source....  This is not the correct way.

Establishing the correct workflow is useful for experienced videographers and beginners like me.

I'm glad everyone is taking a stab at documenting what they do. It's a real help, and I'm sure the workflow will be refined over time.

Thanks, and keep it up, please!
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 17, 2013, 03:26:19 PM
Quote
author=thegunshow101 link=topic=3648.msg67555#msg67555 date=1376721586]
Sorry but converting the RAW file direct to Cineform is missing the most critical point of color correcting directly from the RAW source....  This is not the correct way.

"Correct" must always be used in the context of your goal.  If one's goal is to maximize the quality of their RAW footage, then yes, straight to Cineform is probably not the correct way.  However, I have been very clear in my posts why I am going to Cineform first.  I want to walk, before I run, with video RAW.  I appreciate your comments.  But I it's more helpful if you give evidence, or experience, as to why one has to color correct using TIFFs, let's say, then go to Cineform.  Can you show me two sets of footage, one done your way, and the other straight to Cineform, so others can properly evaluate the difference? I"m certainly interested.  My experience is that even straight to Cineform provides higher dynamic range than the straight AVCHD/MP4 that comes out of the camera.  For me it's been a good and fun place to start.  As for the correct way.  I'm a believer in "the perfect is the enemy of the good."
Title: Re: Tragic Lantern for EOS M
Post by: nicklear9 on August 17, 2013, 05:04:35 PM
Just installed ML on my EOS M with new firmware thanks to mark's post  http://www.dpreview.com/forums/thread/3528189 (http://www.dpreview.com/forums/thread/3528189)

Wanted to say a big thank you to all those working on this. Am so happy just to have focus peaking - that's about the only thing I understand so far!

For reference I have the shutter bug (have to turn off and on quickly to be able to take photos).

Is there any place with instructions in one place for this version? I have picked up things here and there on posts like two finger click to get into the menu. Or am I best just to go through the main ML docs?
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 17, 2013, 06:13:57 PM
the blue dots issue I was talking about, I went ahead and lifted the shadow a bit to see them better.  this was iso 800 or 600 I believe, nothing higher, SD was an extreme pro, all ML settings kept stock.

https://www.wetransfer.com/downloads/09cac33146d10224812ea46e740e9e5a20130817155809/2a15b34d5f8d6536ca05d0ba4abbaeab20130817155809/7c8c80
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 17, 2013, 06:44:12 PM
@gravitatemediagroup:
looks like they should get removed by pinkdotremover. have you used pdr and they're still there?
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 17, 2013, 07:21:38 PM

Is there any place with instructions in one place for this version? I have picked up things here and there on posts like two finger click to get into the menu. Or am I best just to go through the main ML docs?

There is no instruction for these kind of versions - only for the official once. But the main docs will help you to understand many features.
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 17, 2013, 09:10:44 PM
@gravitatemediagroup:
looks like they should get removed by pinkdotremover. have you used pdr and they're still there?

Yes, I used PDR with it's default settings, unless it's possible to do a 2nd pass?   
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 17, 2013, 09:23:09 PM
can you send me a frame as dng? then i'll check why they don't get removed.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 17, 2013, 09:43:22 PM
Once the Magic Lantern hack and install become easier and more stable these EOS-M cameras may get a cult following like the GH2


Great work everyone who created the software I used to make these videos!  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: 350D on August 18, 2013, 03:07:50 AM
Anyone, please, share complete file structure archive for EOS M ML ready to copy to sd card. My version doesn't work on my 2.0.2 camera.
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 18, 2013, 03:35:52 AM
Anyone, please, share complete file structure archive for EOS M ML ready to copy to sd card. My version doesn't work on my 2.0.2 camera.

keep trying, it's not that hard the instruction have been laid out 100 times already, follow them EXACTLY how it says and no issues.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 18, 2013, 03:48:35 AM
Anyone, please, share complete file structure archive for EOS M ML ready to copy to sd card. My version doesn't work on my 2.0.2 camera.

Email me at max at maxotics.com and I'll send you a zip. I placed the files to copy to the card before the EOScard write and the files to write after.  I think it works. 
Title: Re: Tragic Lantern for EOS M
Post by: 350D on August 18, 2013, 06:20:04 AM
Email me at max at maxotics.com and I'll send you a zip.

Thank you!
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 18, 2013, 03:58:59 PM
Need help from moderators.

It seems there isn't one easy place to get files for the EOS-M ML.  I could put them up on my maxotics.com site for easy download.  Don't know if that's okay, helpful?  Who would I talk to?  Don't know if it's okay that I've emailed the folder setup I created for the ML setup.  Please advise.  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 18, 2013, 05:15:45 PM
Anyone, please, share complete file structure archive for EOS M ML ready to copy to sd card. My version doesn't work on my 2.0.2 camera.

Instructions cut and paste from Post #904:

There are 3 files to download from this thread (plus the EOSCard app).

[EOSM202] (need to rename to have .zip extension): https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip
UpDaterM.fir: http://www.qfpost.com/file/d?g=NzBmhwaBK
magiclantern-EOSM.106.Alpha1.zip: http://bit.ly/UP7Avg

So, here are the steps that I took, a slight modification along with correct links on Canon eos m instructions.

1. First soft format your SD card on your computer.
2. Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
3. Next download files from the bitbucket.org link (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip) provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
4. Next copy the updaterM202.fir from (http://www.qfpost.com/file/d?g=NzBmhwaBK) on your SD card.
5. Open the EOSCard link from the installation section of the 5DMarkIII home page.
6. With the SD card in the card reader open the EOSCard utility.
7. Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
8. Then copy the ML directory from the Alpha 1 (http://bit.ly/UP7Avg) version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.
9. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. (step 3)
Title: Re: Tragic Lantern for EOS M
Post by: vprocessing on August 18, 2013, 05:39:34 PM
Hi to all !

One more THANKS for you guys creating such usefull tools !
You just impress me ! 8)
With Vitaly (personalview) and Rominator and other guys from netkas, you really help people to make nice videos, all over the world, as pro or as hobby ! Bunch of digital revoltionnaries ;) you are !!!
You also push us to spend some extra time with computers…but that is for a good reason so… ;)

First are you aware if a speed booster will be made for EOS M ?
http://www.canonwatch.com/is-metabones-working-on-a-speedbooster-for-eos-m/
Or lens turbo from China ?

Then the serious Magic Lantern Part :
I have those resolution available:
1344x406 Non crop
1344x672 Crop
It seems that people are usually talking of other sizes…Am I wrong

The Squeeze ?
I don't understand why the pics are squeezed…as we are working with square pixels…

The Framerate ?
People are talking about 24p RAW vids…I have 30fps…Can I have 24 or more usefull for me 25 ?

Quality seems bad when I shoot RAW do I missed something ?

Duration of display of ML menu can I set it longer somehow ? It desappears very fast…when you are on your first days of ML it is a bit short…

Audio off !!!!! Will you be working on a version with audio on and audio output like with the 5DMkII…Even if it is with Canon flat  video settings…

Intervallometer doesn"t work or can cause failing of the camera…black screen and Led flashing red or green, shutter clicks sometimes…

Sometimes ML menu are little Icons…sometimes it is pages…when I have Icones I don't have the 2 last menus (module loading and the previous one…)

The boot :
I have to make firmware update each time I turn on the cam to have ML…
Can it load directly ?
I'm ok with that because it is a good way to make ML or non-ML EOS-M with the same card…

I've been using 3 different cards :
- 1 SANDISK EXTREME HD video Class 10 30MB/S SDHC I
This one seems the best of the 3. I can have RAW recording working.

- 1 SANDISK EXTREME PRO SDHC I
45MB/S with a little 1 but it's not the same icon than the other's class 10…with the 10 circled…it is more like a U around the 1
With this one RAW recording stops after 2 or 3 sec.…If it is a class 1 I understand the problem…

- TRANSCEND SDHC Class 10
RAW recording stops also like with the 45MB/S

I'm on a 2.0.2 firmware.

THX for help !

.V
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 18, 2013, 09:00:32 PM
Here's a video that takes you through setting up the camera to shoot RAW, after the SD card has been prepared with the EOS-M specific Magic Lantern software.  I also show my workflow from RAW to Sony Vegas Studio. 

SEE BELOW, you can now get EOS-M to boot with ML (use EOSM1202.fir)

Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on August 18, 2013, 09:27:27 PM
There are a lot of post about how to install ML on EOS M but what i want is that Alpha 1 bug like 18-55mm shutter don't work after installing ML remove.

It really annoying coz when i press the shutter with 18-55mm lens attach camera shutter just don't work like before.

1% please release a new version of ML.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 18, 2013, 09:41:00 PM
It still doesn't work with 2.02? I have to make a new bin but first want to fix installer boot process to handle 6D/M
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 18, 2013, 10:07:04 PM
It still doesn't work with 2.02? I have to make a new bin but first want to fix installer boot process to handle 6D/M

Please also consider improve the magic zoom function as early as possible. The focus peaking is quick to use but not as reliable as magic room when comes to accuracy. If we don't have a good magic room function, it could be meaningless to use ML for normal photo taking.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on August 18, 2013, 10:26:37 PM
I'm not asking any ETA of the build. I'm very much greatful for your work 1% i really am. But i'm just want to shoot picture with my 18-55mm lens.

Anyway i'm not complaining but i just don't see anyone mention the problem so, i just thought i give it a go.

I'm gonna get 6D soon if i have enough money only because of amazing DEV like 1% is on the scene.

Thank u so much
Title: Re: Tragic Lantern for EOS M
Post by: JohnBarlow on August 18, 2013, 10:36:16 PM
Can someone up a pic of the card speed test with a 95MBs card?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 18, 2013, 10:53:37 PM
I can't check if the boot flag is set because I already have it:

http://www.qfpost.com/file/d?g=fb5V0T8Wj (http://www.qfpost.com/file/d?g=fb5V0T8Wj)

Try it in photo mode, it does boot at least and shows the text.
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 18, 2013, 11:13:45 PM
I can't check if the boot flag is set because I already have it:

http://www.qfpost.com/file/d?g=fb5V0T8Wj (http://www.qfpost.com/file/d?g=fb5V0T8Wj)

Try it in photo mode, it does boot at least and shows the text.

Hallelujah! 1% you the man!

It boots for me and the bootflag keeps. I can now turn off and on without losing ML and don't have to update the firmware every time like before.

The shutter release bug is also gone. I can now take pictures (and intervalometer and advanced bracketing) without having to turn it off and on again quickly though I had to turn it off and on once at least (the first time) for this to happen.

BTW, I do have a 18-55mm lens with a new EOS-M 2.02 (from factory).
Title: Re: Tragic Lantern for EOS M
Post by: DanyoO on August 18, 2013, 11:52:00 PM
I can't check if the boot flag is set because I already have it:

http://www.qfpost.com/file/d?g=fb5V0T8Wj (http://www.qfpost.com/file/d?g=fb5V0T8Wj)

Try it in photo mode, it does boot at least and shows the text.

Thank You 1%
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 19, 2013, 12:42:13 AM
@1%: sorry that i ask again, but i don't know if my question few days ago got read.
do you already know if dual iso may be possible on eos m? that it's working on 600d makes some hope, but since it doesn't work in lv...
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 19, 2013, 12:48:34 AM
Its possible (and 600D has it in LV) but I get a hang when trying to log cmos, ADTG is fine... I tried today. Nanomad might know how to get it going, I think some address in memory has to be changed.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 19, 2013, 01:10:35 AM
oh... nice.
thx!
Title: Re: Tragic Lantern for EOS M
Post by: htmlman on August 19, 2013, 02:47:31 AM
I seem to have run into a problem.

My EOSM came with 2.0.2 factory installed. I downloaded the package from the link in the first post of this thread and then replaced the .FIR file with the one posted by 1% up above (at http://www.qfpost.com/file/d?g=fb5V0T8Wj) so it would work with 2.0.2, then followed standard installation procedures. All seemed to go well and the welcome screen came off. I restarted the camera and the welcome screen was still there so I restarted it again. It didn't start, and now whenever the power button is pressed, the card read light just rapidly blinks green and the camera does not turn on.

Is there something wrong with ML or did I do something stupid? And what (if anything) can I do to fix it?  ???
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 19, 2013, 03:07:23 AM
Check:

Card is bootable
ML autoexec.bin + support files(ml folder from camera/nighlty) are there

Also boot the camera without a card after removing/installing battery.
Title: Re: Tragic Lantern for EOS M
Post by: epyonxero on August 19, 2013, 03:59:02 AM
Which button activates ML mode?
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 19, 2013, 04:02:53 AM
Which button activates ML mode?

Two finger tap touchscreen to get int ML menu

Direction keys to move thru menu

Singer finger tap to go into sub menu of feature
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 19, 2013, 04:13:01 AM

It boots for me and the bootflag keeps. I can now turn off and on without losing ML and don't have to update the firmware every time like before.
BTW, I do have a 18-55mm lens with a new EOS-M 2.02 (from factory).

+1

works now for me also, it was starting to be a pain.


***UPDATE***
it worked for 1 on and off cycle, 2nd attempt the bootflag was gone, now it won't work for even 1 cycle.
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 19, 2013, 04:15:59 AM
Its possible (and 600D has it in LV) but I get a hang when trying to log cmos, ADTG is fine... I tried today. Nanomad might know how to get it going, I think some address in memory has to be changed.

this is awesome.

when it's all said and done and ML on the M is running flawless, 3 M's for the price of 1 pocket cam may have people thinking.
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on August 19, 2013, 06:46:21 AM
Three cycles in, i'm still good, Bootflag stayed on.
this is awesome.

when it's all said and done and ML on the M is running flawless, 3 M's for the price of 1 pocket cam may have people thinking.
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 19, 2013, 06:51:06 AM
I've must of turned it off and on about 20-30 times now. Left, came back after a few hours later and turned it on again. No problem, Bootflag stays for me. It's like ML on the other Canon cameras I have.

I've even done a few battery pulls and Bootflag is there when I put the battery back in and turn it on again.

I am seeing some freezing and other stability bugs but hey, this is still ALPHA.
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 19, 2013, 08:22:48 AM
I am seeing some freezing and other stability bugs but hey, this is still ALPHA.

alpha typically means stable I thought.

it's why Apple release iOS _ Beta _ to developers to work out bugs.

but yeah, it isn't working right for me, I have the "fix" on the root of the SD.  Not quite sure what I'm doing any different, becuase I get ML to load, I'm applying the same "fix" yet it's no good.  Most odd part is I did manage to get the flag to stay ONE time, the other 10 attempts have been fails.
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 19, 2013, 10:00:33 AM
alpha typically means stable I thought.

it's why Apple release iOS _ Beta _ to developers to work out bugs.

but yeah, it isn't working right for me, I have the "fix" on the root of the SD.  Not quite sure what I'm doing any different, becuase I get ML to load, I'm applying the same "fix" yet it's no good.  Most odd part is I did manage to get the flag to stay ONE time, the other 10 attempts have been fails.

Did you get rid of the UpDaterM.fir and replace it with EOSM1202.FIR on your SD. You can't have both on your SD card. That is the only thing I did and the only thing I can think of.

ALPHA means experimental, prototype and untested with lots of bugs and not ready for public consumption
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 19, 2013, 11:15:14 AM
Good news 1%!
It would be great if someone could combine all the needed and latest files in one zip now for download. It would make things much easier for people like me who get confused by these long installation explanations but are willing to test. Especialy for people who do not speak english perfect.
Is that possible?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 19, 2013, 11:16:25 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 19, 2013, 11:46:01 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 19, 2013, 12:37:06 PM
Check:

Card is bootable
ML autoexec.bin + support files(ml folder from camera/nighlty) are there

Also boot the camera without a card after removing/installing battery.

Want to report a small bug: Intervalometer hangs the camera after the camera has taken the chosen number of pictures. To get it working one has to power off and restart.

Also, haven't seen any new modules for the EOS M out in a while. Which is the latest one. Could you please point me out to the location of the latest version? 
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 19, 2013, 12:45:38 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 19, 2013, 01:18:01 PM
I can't check if the boot flag is set because I already have it:

http://www.qfpost.com/file/d?g=fb5V0T8Wj (http://www.qfpost.com/file/d?g=fb5V0T8Wj)

Try it in photo mode, it does boot at least and shows the text.

My EOS-M is already bootflagged, but if this works, it would be a good idea to put it in the first post along with the rest of the update.
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 19, 2013, 01:28:57 PM
My EOS-M is already bootflagged, but if this works, it would be a good idea to put it in the first post along with the rest of the update.

+ what Canon eos m asked - thats what I mean ... it´s getting confusing what file to use when and how. Espescial for people who do not follow and/or do not understand the whole thread every day.
If someone could compile a set (kind of Alpha 2) with all the latest and still working files in one zip-set it would be a huge help. At least for me.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 19, 2013, 01:42:40 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: htmlman on August 19, 2013, 02:54:25 PM
Check:

Card is bootable
ML autoexec.bin + support files(ml folder from camera/nighlty) are there

Also boot the camera without a card after removing/installing battery.

Yeah, booting without card got it working again. I'm a might confused on how to go about things now though... Do I take the nightly build autoexec.bin and ML folder, pair it with the new 2.0.2 ML FIR file and follow standard install?
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 19, 2013, 02:58:36 PM
I asked above if I can help, shouldn't help, but no answer...

I posted a file EOSM20130818 which you can get on my site, go to

http://maxotics.com/photos (http://maxotics.com/photos)

Enter the key "EOSM20130818"

You will get a link to that zip file.  It contains the folder of stuff I put on the SD card before the EOS Card utility, and the files I copy/replace after.  I believe it has the latest stuff according to what the posts above say.  It seems to work for me.  It contains the .fir file to allow autoloading of ML.  BUT I AM NEW TO THIS STUFF too.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 19, 2013, 03:01:16 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 19, 2013, 03:11:34 PM
1% (and all the other great people at ML), can you have the display at the bottom of the screen where it shows aperture, shutter, ISO, etc indicate which item is active for adjusting with the wheel/arrows? I never know if it is on aperture or shutter when i spin the wheel to make changes and it seems like i always have the wrong one. When i press the right arrow it switches between them, but it would be a lot better if it somehow made an indication of which one is ready for adjustment. Maybe make the active value brighter or bigger so we know? can you also make it toggle between aperture, shutter and ISO for adjustments? 

Gary

I even don't understand why ML uses a independent information display screen instead of just using canon's stock interface. It would be best if we can directly display the focus peaking of magic room box on the canon information display interface.
Title: Re: Tragic Lantern for EOS M
Post by: Rootwang on August 19, 2013, 03:47:24 PM
I've made a zip file with all you need for installing on 2.02 firmware magic lantern, with the last firmware installer that 1 % posted, For me it worked and bootflagged. I don't know if i'm supposed to do this but there is a lot of people asking. If i'm doing wrong you can delete the post!

http://www.sendspace.com/file/37061u

P.s. sorry if my english is not perfect!!  :)
Title: Re: Tragic Lantern for EOS M
Post by: christou on August 19, 2013, 05:42:16 PM
go back one page (page 44) and find 1% message with the link to the new firmware file

Gary

intervalometer confirmed to be work partially on 2.0.2 firmware with ML on page 44
but it does only work for non-bulb shutter value
if bulb is set, only the first shot got the correct bulb time. it will then reset to 30" and the intervalo still keep running

may I rise a ticket in the issue system about this?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 19, 2013, 05:54:07 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 19, 2013, 06:36:32 PM
Want to report a small bug: Intervalometer hangs the camera after the camera has taken the chosen number of pictures. To get it working one has to power off and restart.

Also, haven't seen any new modules for the EOS M out in a while. Which is the latest one. Could you please point me out to the location of the latest version?

Thank you gary2013 - my problem resolved with 1%'s latest *.fir update (at page 44 of this thread).
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 19, 2013, 08:33:58 PM
I've made a zip file with all you need for installing on 2.02 firmware magic lantern, with the last firmware installer that 1 % posted, For me it worked and bootflagged. I don't know if i'm supposed to do this but there is a lot of people asking. If i'm doing wrong you can delete the post!

http://www.sendspace.com/file/37061u

P.s. sorry if my english is not perfect!!  :)

Thanks Rootwang - it helped a lot and it works on my M  :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 19, 2013, 09:04:16 PM
Quote
Can we have the audio meters working all the time? Currently, they only work during recording. It's important to see the meters before we record as well as during recording.

Bulb issue is present on all cams without dedicated bulb mode. I think its a meta bug. For the meters I will when I can, didn't set them to only work while recording on purpose.
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 19, 2013, 09:31:13 PM
Did you get rid of the UpDaterM.fir and replace it with EOSM1202.FIR on your SD. You can't have both on your SD card.

BINGO!
Title: Re: Tragic Lantern for EOS M
Post by: gamerblot on August 19, 2013, 10:03:54 PM
how do we get out of ML menus besides sitting here waiting for it to timeout?

I usually hit the Shutter button to get out of the ML menu.

What I find annoying is that the ML screen will timeout after maybe 5 seconds of inactivity when I am looking at something in the ML menu. Then I have to go back into the ML menu again and re-trace where I was. Is there a fix for that?
Title: Re: Tragic Lantern for EOS M
Post by: vladojko on August 19, 2013, 11:43:37 PM
Hi all

This is my first post and i want to report that i still have shutter bug even with using latest .fir file. I guess we need new autoexec.bin to fix this
Title: Re: Tragic Lantern for EOS M
Post by: jonas18z on August 20, 2013, 12:28:12 AM
What is the shutter bug?


Title: Re: Tragic Lantern for EOS M
Post by: jamessandri on August 20, 2013, 12:37:14 AM
Hats off the team and 1%. No more flashing the firmware everytime I want to shoot raw. Here's something I shot in raw using a 60D and the EOS-M.

Title: Re: Tragic Lantern for EOS M
Post by: thegunshow101 on August 20, 2013, 01:15:05 AM
Hi to all !
First are you aware if a speed booster will be made for EOS M ?
http://www.canonwatch.com/is-metabones-working-on-a-speedbooster-for-eos-m/
Or lens turbo from China ?

I was just thinking about this possibility.. I'm glad I see a link to the video. It's surely a prototype for EOS-M.. I feel like when the next round of EOS-M cameras are released and the system becomes more developed Metabones will officially announce this, for sure.

Given the fact that you need to use an adapter for EF lenses anyway this makes so much sense and turns your EOS-M back into an (almost) full camera..+ one f stop brighter..

With RAW + a speedbooster, the EOS-M could be a little powerhouse for video..
Title: Re: Tragic Lantern for EOS M
Post by: mountain_drew on August 20, 2013, 03:39:49 AM
***deleted
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 20, 2013, 05:23:51 AM
I do a quick test, comparing video produced from Magic Lantern's maximum resolution on the EOS-M at 24 FPS, 1472 x 592 (continuous recording) with the 1728 x 684 resolution possible at 12 FPS.  I think there may also be a bug (or it's on purpose for scaling?) in RAWanizer.  It didn't create the TIFFs at the higher resolution.

I created the TIFFs manually using RAW2DNG, then RAWDrop to TIFF and ffmpeg to high quality MP4, I hope ;)

Anyway, as you can see, you do get better quality, and less moire, at the higher resolution, though lower frame rate.

Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 20, 2013, 05:46:14 AM
wow, the new UI looks WAY better.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 20, 2013, 05:47:05 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 20, 2013, 07:26:16 AM
how can I keep ML from showing the flickering menu on the left side of the screen while shooting?
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 20, 2013, 02:58:16 PM
I do a quick test, comparing video produced from Magic Lantern's maximum resolution on the EOS-M at 24 FPS, 1472 x 592 (continuous recording) with the 1728 x 684 resolution possible at 12 FPS.  I think there may also be a bug (or it's on purpose for scaling?) in RAWanizer.  It didn't create the TIFFs at the higher resolution.

I created the TIFFs manually using RAW2DNG, then RAWDrop to TIFF and ffmpeg to high quality MP4, I hope ;)

Anyway, as you can see, you do get better quality, and less moire, at the higher resolution, though lower frame rate.


Your posts are useful, but I do not understand why you shoot at the resolutions you chose - they are not on the horizontal dimension HD. Why not shoot at 1280 x 720? When you process your clips they are less than HD.

Why are you not shooting in crop mode, which has far less aliasing and moire, at 720P? The camera will shoot for at least a couple of minutes in 720p in that mode (24fps) and it is real HD. You clips are seconds, so "continuous" capability seems irrelevant (as it is for most video shooting).
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 20, 2013, 03:45:25 PM
I think the menu thing is universal, it times out when the canon dialog does.
Title: Re: Tragic Lantern for EOS M
Post by: Dave1711 on August 20, 2013, 04:15:47 PM
wow, the new UI looks WAY better.

Do you mean the EOS M UI as seen on the frontpage? http://www.magiclantern.fm/img/eosm.png (http://www.magiclantern.fm/img/eosm.png)
Is this included in the latest .fir file from 1% or where can we get it?
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 20, 2013, 04:22:42 PM
@maxotics:
changing resolution afaik shouldn't have any impact on moire and other aliasing effects. as markr041 wrote changing to crop mode does dramatically reduce aliasing.

@1%:
again a dualiso question, even if it's not available :)
do you know which exact algorithm is used to calculate the hdr result from the 2 interlaced iso imageparts? is there any documentation, link to a paper or something like that?
i ask, because the af dots on eos m and 650d may cause some problems in that procedure and maybe they need some special treatment. maybe a modified algorithm that is aware of the dots could be included in the pinkdotremover. if there is some info about the algorithm i would check how it may be affected by the dots.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 20, 2013, 04:58:30 PM
Hit menu, that is the ML junkie mode... its a good candidate for touch support.

For dual ISO there is a whole thread on it and a PDF that describes the theory. The source is in the module's folder, it should have some notes there too. Dots might be a problem, but first need to make it work to see what kind of a problem.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 20, 2013, 05:04:49 PM
@markr041

I have a 50D which shoots amazing RAW video, was curious to see just how much resolution I could get from the EOS-M, if I wanted to match on that basis (though at a lower FPS).  I can imagine certain types of shots where this high resolution, at a lower FPS, might be useful.  I am also curious to try 16fps with sound later.  What do you think are the best settings, aspect and resolution, for both 24p and 16p?  Also, I meant "continuous" as in the camera won't lose frames or plain shut-down or worse, corrupt the card.

@Mixer2

Eventually, I'll get to crop mode.  For now I want to keep at 22mm.  As I get older I find long focal lengths more artificial.  Sorry to be annoying ;)  Please help me understand this moire and aliasing issue.  My understanding is that when a line, say, is resolved by a lens on the sensor it can fall between the pixels.  When the EOSM samples the sensor, it will skips lines which essentially creates geometric distortions.  I would think that the more resolution, the less moire because the image has more information to fill in (and not show a geometric distortion).  After all, the benefit of crop mode is that there is no (minimal?) line skipping and therefore less chance for a line not to resolve between pixels.  If it's true that more resolution will have no effect on moire than I may quit that higher resolution stuff because there's enough dynamic range in current resolutions.

@All

My silly tests have had one benefit which should hopefully provide better footage in the future.  Because I couldn't get the right-size TIFFs from RAWanizer, I was forced into a higher quality RAW workflow which I hope to use from now on, instead of straight to cineform.

RAW --> RAW2DNG --> RAWSpot (to TIFFS) then ffmpeg:

16fps:

ffmpeg -r 16 -i 000%3d.tiff -c:v libx264 -crf 10 -pix_fmt yuv420p out.mp4

24fps:

ffmpeg -r 16 -i 000%3d.tiff -c:v libx264 -crf 10 -pix_fmt yuv420p out.mp4

I then take the mp4 and put into Vegas Studio.  If you have better ffmpeg setting PLEASE let me know.


Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 20, 2013, 05:42:36 PM
@maxotics:
if you increase the resolution setting it just crops a larger part of the sensor. if you record 1728 x 684 and throw away 256 pixels from the left and right and 46 pixels from top and bottom, you'll get exactly the same image as you would have recorded 1472 x 592. and this obviously won't affect aliasing effects of the remaining pixels.
of course, if there is less crop, you can increase focal length or put the camera closer to the subject, which may help that the texture isn't fine enough to cause aliasing.

@1%:
i read the pdf and most of the thread. the method described in the pdf sounded really temporary. therefore i thought that it doesn't match the current implementation. i'll check the sourcecode.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 20, 2013, 05:53:52 PM
@mixer  THANKS for the explanation.  I now get what Markr40 was trying to get through my thick head :)

@All I can't get Movie Crop mode to turn on.  It stays disabled no matter what buttons/touches I do.  I have the 22mm pancake lens.  Any ideas?  thanks!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 20, 2013, 06:02:53 PM
sounds like you're not in movie mode. switch to movie mode and it should work.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 20, 2013, 06:13:54 PM
@mixer THANK FOR QUICK REPLY  That did trick!  Now should anyone search

On the EOS-M, To enable or select Movie Crop Mode in Magic Lantern you need to be in "Movie" mode (wheel around shutter button).  It will not select if you're in photo mode, it will appear gray or disabled.
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 20, 2013, 06:34:23 PM
@markr041

I have a 50D which shoots amazing RAW video, was curious to see just how much resolution I could get from the EOS-M, if I wanted to match on that basis (though at a lower FPS).  I can imagine certain types of shots where this high resolution, at a lower FPS, might be useful.  I am also curious to try 16fps with sound later.  What do you think are the best settings, aspect and resolution, for both 24p and 16p?  Also, I meant "continuous" as in the camera won't lose frames or plain shut-down or worse, corrupt the card.


@All

My silly tests have had one benefit which should hopefully provide better footage in the future.  Because I couldn't get the right-size TIFFs from RAWanizer, I was forced into a higher quality RAW workflow which I hope to use from now on, instead of straight to cineform.

RAW --> RAW2DNG --> RAWSpot (to TIFFS) then ffmpeg:

16fps:

ffmpeg -r 16 -i 000%3d.tiff -c:v libx264 -crf 10 -pix_fmt yuv420p out.mp4

24fps:

ffmpeg -r 16 -i 000%3d.tiff -c:v libx264 -crf 10 -pix_fmt yuv420p out.mp4

I then take the mp4 and put into Vegas Studio.  If you have better ffmpeg setting PLEASE let me know.

1. I don't understand how the final product has "higher resolution" when the vertical resolution is less than HD standards. What is the benefit of having higher horizontal resolution and lower vertical resolution to get an odd aspect ratio? What does the final editor do with the strange aspect ratio? You can set the ML not to skip frames. ML tells you how many seconds you can shoot at the given resolution and frame rate, so you do not have to shoot until the thing breaks down. At real 720P resolution at 24fps you can shoot for over 2000 frames before it stops, which is plenty. You then can make a nice 720P video at a reasonable frame rate that people might want to watch.

2. You do NOT have to convert the TIFFS to any video like MP4  or Cineform before using Vegas Pro. Your workflow makes no sense (if I understand it). Vegas Pro will read TIFFS natively as an image sequence. By converting TIFFS to MP4 (or Cineform) before you use Vegas you are defeating the whole purpose of RAW - to avoid multiple compression and retain all the info from the sensor.  Why not RAW -> TIFFS (all digital, all info)->Vegas for grading, sharpening and making the final 24fps 720p video. That is what I do (which merely means I know this works).
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 20, 2013, 07:02:55 PM
@Markr41  Sorry you're frustrated with me.  I do appreciate all your help!  ;D  The reason I may avoid certain procedures which you recommend is I'm trying to figure out one thing, and don't want to get caught up trying to figure something else out and then ending up in a very unhappy place.  For example, I suspected that Sony might be able to import a string of TIFFs, but I knew ffmpeg would work, so I went with what I knew. (BTW, you can probably get ffmpg to output a single file without compression and have one file with near TIFF quality to move around). Now, not wanting to annoy you any further ;)  I just went into Sony and figured it out.  So I will now do what you recommend and which I FULLY AGREE is a better workflow. Thanks again!

I thought a high resolution, even at one dimension, would be squished and provide better over-all resolution.  I don't know the answers here.  It's very hard to find conclusive information about any of this; I think you'll agree.  That spreadsheet which is a great idea is not being updated anymore.  I'm going to add a page to my blog and hopefully put all this information in one place so I can save others the pain I'm going through.

I do want to settle on some optimal shooting settings for various situations.  Non-crop, crop, etc.

Again, thanks for you all your help and keep it coming!
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 20, 2013, 07:05:00 PM
Do you mean the EOS M UI as seen on the frontpage? http://www.magiclantern.fm/img/eosm.png (http://www.magiclantern.fm/img/eosm.png)
Is this included in the latest .fir file from 1% or where can we get it?

I was more or less talking about the ML website, but ML itself is also nice.
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 20, 2013, 10:15:12 PM
Does anyone ever pay a little attention on the photo shooting things instead of the movie? I really don't understand why everybody is talking about movie and movie. But we really need to improve the photo shooting features very eagerly.
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 20, 2013, 11:26:17 PM
Does anyone ever pay a little attention on the photo shooting things instead of the movie? I really don't understand why everybody is talking about movie and movie. But we really need to improve the photo shooting features very eagerly.

not sure how much you keep up with "video new" or "video tech" for that matter, but being able to shoot RAW VIDEO!! as a free bonus on any camera is a must have option for any filmmaker.

what could possibly be missing as far as photo features outside of what's stock on cam and the tons of stuff ML currently adds.

also be patient, things take time and the photo stuff isn't what in demand.  if you checked the website traffic of ML in the past 6 months, my guess is you would see a major spike in traffic due to the high demand of affordable of raw video.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 21, 2013, 12:09:48 AM
@haomuch

RAW video is the same as taking X number of stills in quick succession (albeit at a lower than normal resolution).   So if you were taking photos of someone for their profile page on LinkedIn, say, you could shoot in RAW, extract the DNGs, convert them to TIFFs, and be able to pick exactly the right expression in the split second it happened in.  So it's not as if RAW video is completely non-photo related.  It has photo uses. 

Title: Re: Tragic Lantern for EOS M
Post by: DanyoO on August 21, 2013, 02:20:58 AM
Sorry for my bad english  :(

One clip video raw.
Video Raw Eos M
Canon Eos M + 22MM/ F2
1728x694      20FPS
SanDisk Extreme Pro 32GB SDHC Clase10 UHS-I

Drobox

https://www.dropbox.com/s/ym2myfxlo4buv8t/tes%20eos%20m%20raw%20video%2020fps..avi (https://www.dropbox.com/s/ym2myfxlo4buv8t/tes%20eos%20m%20raw%20video%2020fps..avi)
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on August 21, 2013, 03:18:29 AM
can pink dot fix be done in a batch, or just 1 at a time?

and also,  PDF isn't working on the footage I shot today, instead it creates a duplicate (in Dav. resolve it shows up double anyways, before PDF resolve was only showing 1)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 21, 2013, 02:21:39 PM
you can add as many files as you want to the pink dot remover file list and convert them all.

PDF = pink dot fix?
have you tried to remove dots in the dngs or the raw? can you upload a dng that isn't working?
Title: Re: Tragic Lantern for EOS M
Post by: DanyoO on August 21, 2013, 03:34:17 PM
I use PinkDotRemover  ;)
I believe that it erases all the rough files :( intentare recuperar algun dng, but if I won't record myself some other video of my training :) but to 24fps


using a program to recover erased files and gotten some dng.
https://www.dropbox.com/s/md90w4re47h6x2g/%24R6005D7.dng (https://www.dropbox.com/s/md90w4re47h6x2g/%24R6005D7.dng)
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 21, 2013, 08:57:36 PM
Does ML have a "hyperfocal" focus mode, where you simply compose the photo and the camera calculates what will be in focus (from infinity distance to closest distance in focus) using the selected aperture?

Say I select f/8 and want everything to be in focus from infinity to the closest point that f/8 will allow (hyperfocal distance).  Can ML do that automatically?  It would be great if it could!  Thanks for all of the great work!
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 21, 2013, 10:59:15 PM
They can't even provide a usable magic room focus function currently. So I think you may need to wait for a very long time.
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 21, 2013, 11:13:46 PM
They can't even provide a usable magic room focus function currently. So I think you may need to wait for a very long time.

What is a "magic room focus function?"  And how is that less difficult than an automatic hyperfocal distance focuser?  Just curious.
Title: Re: Tragic Lantern for EOS M
Post by: Rush on August 21, 2013, 11:50:28 PM
Does ML have a "hyperfocal" focus mode
check Focus tab. with most electronic lenses - it automatically calculates DOF and Hyperfocal distance, based on current lens settings and will report if you are in hyperfocal distance
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 22, 2013, 12:38:37 AM
check Focus tab. with most electronic lenses - it automatically calculates DOF and Hyperfocal distance, based on current lens settings and will report if you are in hyperfocal distance
Where is the "focus" tab?  I don't see it with my version of ML.  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 22, 2013, 05:52:56 AM
@Markr041  AGAIN, you can say 'I told you so."  I shot a fair amount of crop mode.  The more I grade in Vegas, using both Cineform and MP4, the more I can get them to look alike.  So I've been thinking, RAW isn't worth it.  I've wasted a ton of time (at least on the EOS-M).  But I thought, maybe Markr41 is right.  So before I give up on it I decided to pull in those samples as TIFFs (had to use RAWdrop to get full resolution) and voila, back in business.  Much better than the native MP4.  I'm going to buy a 10-20mm lens on Friday and try it, in crop mode, on both the EOS-M and 50D.  I'll also only do grading using TIFFs.  Hopefully this will yield conclusive footage, high dynamic range and (from crop mode) limited moire.  That's where I'm at! 
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 10:01:40 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Rush on August 22, 2013, 11:24:22 AM
Where is the "focus" tab?  I don't see it with my version of ML.  Thanks!
OH, It is not available for EOS M yet...
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fwww.magiclantern.fm%2Fimg%2Fscreenshots%2Fmenu_focus.png&hash=05a645e4cfffa513f7873c82a516aab9)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 11:27:10 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 12:07:45 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 22, 2013, 02:12:46 PM
@gary2013

From my test and what I can see of others, using a higher bitrate in CBR won't provide better quality.  Or, if it does, for fast motion, it seems to top out at 1.4 (that's what I use, because no sense making bigger files for nothing).  The bigger benefit is if you want to record for a longer time on a card, or keep file sizes low, then you can use .8 say.  If you go the VBR qscale approach you're telling the camera to save more information for higher quality (or you can do less too).  However, high values can stop recording if you hit bright light (no one seems to know why).  Again, i can't see the change in quality.   My take, is based on what I've read elsewhere, that these compression settings effect what happens after the image is produced, so may make some intra-frame quality better (motion), but have no real effect on the IQ of the individual reference frames.  Others can chime in here. I'm curious too.  THESE SETTINGS have nothing to do with RAW.  RAW ignores them, to my knowledge since you're getting straight/full sensor data.

RAWdrop is working for you, just not the way it was intended.  It expect you'd drop, say 600 DNG files onto it, it will then produce 600 TIFFs (in the same directory) which you can grade from, import into your NLE timeline.  What I do, is copy a set of DNGs to a directory I want the TIFFs in, drop all the DNGs there, delete the DNGS (copies), then pull the TIFFs into my timeline as a sequence and grade/edit. 

The best way to get good quality, without RAW, is to have the right light (not too much dynamic range--difficult outside) and the right lens, f-stop, shutter speed, etc.  One famous cinematographer said, 'expose for the detail of your subject and let the highlights blow out'  Because most cameras can only capture limited dynamic range, exposure is very, very important.  I'm guilty of what you're about to do, spend too much time on compression technologies and not enough on the basics.  A primary benefit of RAW is that you have more latitude to "save"/fix exposure/color problems in post.  However, if your light and exposure are perfect, the video will probably look as good as you'll ever want it.  Of course, that's difficult to do and outside light doesn't always cooperate.  So I'm going RAW, but have to keep reminding myself, it's no cure-all.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 02:30:00 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: cameron12x on August 22, 2013, 02:30:44 PM
OH, It is not available for EOS M yet...
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fwww.magiclantern.fm%2Fimg%2Fscreenshots%2Fmenu_focus.png&hash=05a645e4cfffa513f7873c82a516aab9)

WOW!  It would be nice to have all of those FOCUS functions available for the EOS-M!

Praying for them!  :)
Title: Re: Tragic Lantern for EOS M
Post by: atomas72 on August 22, 2013, 03:37:31 PM
There are 3 files to download from this thread (plus the EOSCard app).

[EOSM202] (need to rename to have .zip extension): https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip)
UpDaterM.fir: http://www.qfpost.com/file/d?g=NzBmhwaBK (http://www.qfpost.com/file/d?g=NzBmhwaBK)
magiclantern-EOSM.106.Alpha1.zip: http://bit.ly/UP7Avg (http://bit.ly/UP7Avg)

So, here are the steps that I took, a slight modification along with correct links on Canon eos m instructions.

1. First soft format your SD card on your computer.
2. Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
3. Next download files from the bitbucket.org link (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip)) provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
4. Next copy the updaterM202.fir (link on page 33 of this thread) UpDaterM.fir (http://www.qfpost.com/file/d?g=NzBmhwaBK (http://www.qfpost.com/file/d?g=NzBmhwaBK)) on your SD card.
5. Open the EOSCard link from the installation section of the 5DMarkIII home page.
6. With the SD card in the card reader open the EOSCard utility.
7. Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
8. Then copy the ML directory from the Alpha 1 (http://bit.ly/UP7Avg (http://bit.ly/UP7Avg)) version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.
9. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. (step 3)
Hi all I'm new to this forum.
I tryed 20 (I have a new Eos-m with 2.0.2 firmware) or more times to do this steps above but after the upgrade process I see a color lines for less a second and Camera turns to normal manual mode.
Can anyone tell me how to sure install ML on my camera?
Thanks for the answer and excuse me if the question has yet posted (I made a search but I didn't find nothing).
Tomas
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 22, 2013, 03:45:12 PM
@maxotics: I agree with you completely that shooting technique trumps RAW versus compressed out of camera. One more issue: RAWdrop produces Tiff files that are half the size of those produced by Lightroom when I tell Lightroom not to compress when going from .dng's to Tiff's. So it looks like the Tiff files produced by RAWdrop are compressed. If this is lossy compression, then it seems to me again the purpose of RAW is compromised. Do you know what RAWdrop is doing in terms of the conversion?
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 22, 2013, 04:49:25 PM
Hi all I'm new to this forum.
I tryed 20 (I have a new Eos-m with 2.0.2 firmware) or more times to do this steps above but after the upgrade process I see a color lines for less a second and Camera turns to normal manual mode.
Can anyone tell me how to sure install ML on my camera?
Thanks for the answer and excuse me if the question has yet posted (I made a search but I didn't find nothing).
Tomas

@ atomas72:  Best is to use the link #1110 on side 45 - Rootwang compiled all you need and it worked for me.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 05:16:17 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 22, 2013, 05:16:58 PM
RAWdrop produces Tiff files that are half the size of those produced by Lightroom when I tell Lightroom not to compress when going from .dng's to Tiff's. So it looks like the Tiff files produced by RAWdrop are compressed. If this is lossy compression, then it seems to me again the purpose of RAW is compromised. Do you know what RAWdrop is doing in terms of the conversion?

I'm using the GUI version, which looks like this.  I started using it because I had that problem in RAWanizer (half-size TIFFs).  My guess is there is a way to tell RAWanizer to make a full-size TIFF through DCraw "Use Cusotm DNG to TIFF".  One of us needs to go figure those settings out ;)

Okay, these custom settings worked in RAWanizer to give full-size TIFFS: -6 -W -g 1 1

REFERENCE: http://www.cybercom.net/~dcoffin/dcraw/dcraw.1.html (http://www.cybercom.net/~dcoffin/dcraw/dcraw.1.html)

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fmaxotics.com%2Fphotos%2FRAWDropGUIScreenshot.png&hash=923cc8f2b62eaee4fb07aadaa78278ca)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 05:30:57 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 22, 2013, 05:37:22 PM
I'm using the GUI version, which looks like this.  I started using it because I had that problem in RAWanizer (half-size TIFFs).  My guess is there is a way to tell RAWanizer to make a full-size TIFF through DCraw "Use Cusotm DNG to TIFF".  One of us needs to go figure those settings out ;)

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fmaxotics.com%2Fphotos%2FRAWDropGUIScreenshot.png&hash=923cc8f2b62eaee4fb07aadaa78278ca)

That's what mine looks like too (not surprisingly), and the 'HQ Interpolation' hints at the lossy compression. I do not see the DCraw on my computer, or any configuration other than the basic one. It is a big pain using Lightroom to simply make the conversion from .dng's to Tiff's, so it would be nice if this RAWDrop program would not assume what we want and allow us to choose.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 06:15:45 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 22, 2013, 06:20:10 PM
I have been creating a new folder for each Raw file. Then PDR on each camera Raw file. Then raw2dng. Then Photoshop CC, open the first file of the sequence and all of them load. Select All files and do a quick grade. Then Save All files to Tiff. Then import the Tiff sequence into Premiere Pro CC to edit. Add Neat Video to clear up all the noise from the Raw sensor. Change the scale to 166% on height. Sheesh. Can someone make one utility that does that all in one step to the camera Raw files and even batch a group of camera Raw's? And the highest full quality Tiffs.

Gary

My workflow is the same, except instead of Photoshop CC I use Lightroom 5 and instead of Premier Pro CC I use Vegas Pro and I do not need to stretch, since I shoot crop mode 720p. The steps that are most cumbersome are the placing of RAWs in folders (21 clips = 21 folders) and the conversion from dng to tiff in Lightroom for me.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 06:23:35 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 22, 2013, 06:24:06 PM
@Gary2013

I think we're stuck with the Pinkdot remover for a bit.  At least we can run that first and be done with it. 

The other stuff I can write one script for.  I need the optimum settings for

1. RAW2DNG (assume params not necessary?)
2. DCRAW (or some other command line that will spit out TIFFs

I can set flags to copy/delete files best for our workflow.  My only problem with RAWanizer is the TIFFs have been half-size (height) for me.

Here's a script I started working on for Cineform creation, to give you an idea of what kind of scripts I'd write.  Once set up, you put it on the folder with your source and it will create a target directory with everything ready for editing.

I also feel ffmpeg can be used to create a lossless video clip from TIFFs, saving another step in the NLE. 

Code: [Select]

' ****************** CONFIG ME *******************************
ThisFolder = left(WScript.ScriptFullName,(Len(WScript.ScriptFullName))-(len(WScript.ScriptName)))

' AFTER SETTING PARAMs
' 1. Run this script (it generates ConvertRAW.bat)
' 2. Then run ConvertRAW.bat

' *** PARAMETERS REFERENCE ***
'-422- Encode to YUV 4:2:2 (default RAW.)
'-444- Encode to RGB 4:4:4 (default RAW.)
'-c  - use Cineon curve (black 95, white 685)
'-cbX- use Cineon curve with 'X' black point (default 95.)
'-cwX- use Cineon curve with 'X' white point (default 685.)
'-dX - use debayer type 1-softest thru 4-sharpest (default auto)
'-fX - the framerate override for AVI|MOV media.
'-gX - use gamma curve
'-iX - in point, start processing on frame X (default 0, disables audio.)
'-lX - use log curve of power X (GoPro Protune.)
'-oX - out point, e.g. -o10 would precess 0 thru 9 (default infinite.)
'-qX - the encoding quality for AVI|MOV (default 4, range 1-5.)
'-sX - skip every 'x' frames (default 0).
'-(x1,y1,x2,y2)  - window source Top Left (x,y) to Bottom Right (x2,y2)
 
Dim Prefix_RAW2GPFC, Suffix_RAW2GPFC
FolderForOutput = "Cineform422\"

Prefix_RAW2GPFC = "raw2gpcf "

Suffix_RAW2GPFC = " -dX 4 -qX 5 "
' Write folder for output to FFMPEG command
Suffix_RAW2GPFC = Suffix_RAW2GPFC & ThisFolder & FolderForOutput
NumberOfFilesToProcess = 1000 ' make, say 3, for testing.

UseExtension = ".AVI"
'*************************************************************
ReDim xFiles(0)

GetFiles(ThisFolder)
x = WriteBATFile(ThisFolder, ThisFolder & "\" & FolderForOutput)

'*********************************
' WriteBATFiles
'*********************************
Function WriteBATFile(argDir, argOuputDirectory)
Set WshShell = CreateObject("WScript.Shell")
Set objFso = CreateObject("Scripting.FileSystemObject")
Set objFile = objFso.CreateTextFile(argDir & "/ConvertRAW.bat")

' Create output directory if doesn't exist
If Not objFSO.FolderExists(argOuputDirectory) Then
   objFSO.CreateFolder(argOuputDirectory)
  End If


for i = 1 to ubound(xFiles)
objFile.WriteLine xFiles(i)
Next

objFile.Close

End Function

'*********************************
' GetFiles
'*********************************
Function GetFiles(argDir)
Dim fso, folder, files, NewsFile,sFolder
Set fso = CreateObject("Scripting.FileSystemObject")
Set folder = fso.GetFolder(argDir) 
Set files = folder.Files   
vCounter = 1
For each folderIdx In files
if right(ucase(folderIdx.Name),4) = ".RAW" Then
Redim Preserve xFiles(Ubound(xFiles)+1)
xFiles(Ubound(xFiles)) = Prefix_RAW2GPFC & argDir & "" & folderIdx.Name & Suffix_RAW2GPFC & replace(folderIdx.Name,".RAW",UseExtension)
vCounter = vCounter + 1

' For resting, only run a few
if vCounter > NumberOfFilesToProcess then
exit function
end if

' *** Write file name, testing
'NewFile.WriteLine(folderIdx.Name)
End if
Next
End Function



Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 06:34:58 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 22, 2013, 06:37:47 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 22, 2013, 07:29:03 PM
@maxotics and Gary2013:

the pdr has a cli you can use to automatically remove dots in your script.
Title: Re: Tragic Lantern for EOS M
Post by: atomas72 on August 22, 2013, 10:16:47 PM
@ atomas72:  Best is to use the link #1110 on side 45 - Rootwang compiled all you need and it worked for me.
Thanks for the answer!!
I now have the black screen with green text, how to enable ML? If I restart camera I have normal program... And if I restart procedure I have the green text again...
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 22, 2013, 10:39:13 PM
sure that ml isn't active? try tapping with two fingers on the screen.
Title: Re: Tragic Lantern for EOS M
Post by: atomas72 on August 23, 2013, 07:19:30 AM
sure that ml isn't active? try tapping with two fingers on the screen.
I tryed, nothing happens. Each time I see only success screen.
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 23, 2013, 09:50:09 AM
I tryed, nothing happens. Each time I see only success screen.

That´s strange. No idea what went wrong with your installation. For me it worked totaly normal and still does.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 23, 2013, 11:09:36 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on August 23, 2013, 05:08:52 PM
Hi, maybe this is not the right place to ask so I´m sorry about it but I wanted to ask, since the EOS M is a mirrorless camera with an electronic shutter and previous project like CHDK enabled compact canon cameras to shoot at 1/20000 speeds, its possible to overcome the 1/4000 limitation of the EOS M with magic lantern?

Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 23, 2013, 05:14:31 PM
Not for photo... it has a normal shutter. Shutter syncing didn't work for some reason either but does on 6D.. so probably something to do with the funny timings. I think extra high shutters did work but that implementation went away and changed to sync for lights, screens, etc.
Title: Re: Tragic Lantern for EOS M
Post by: melihozbek on August 23, 2013, 05:21:27 PM
Hi,

I don't know if it is by design, but when I use "FPS Override" for very low fps like 0.5 fps , the shutter speed isn't affected and couldn go below 1/30 (like 1/10, 1/5 etc).. On the other hand, on 5D Mk II, it is the opposite, shutter speed is linked to the fps, and when I choose 0.5 fps, I can't choose shutter speed..

The question is, how can I go below 1/30 when i choose (really) low FPS from "FPS Override" on EOS M?

Thank you

Melih
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 23, 2013, 05:44:49 PM
Under low light you can. This area probably needs some help though. High jello can do the lower fps too.
Title: Re: Tragic Lantern for EOS M
Post by: melihozbek on August 23, 2013, 07:07:10 PM
No luck, it doesn't go below 1/30 (by the way I am not talking about the RAW movie, it is h264.. )

thanks

Melih
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 23, 2013, 10:08:08 PM
No luck, it doesn't go below 1/30 (by the way I am not talking about the RAW movie, it is h264.. )

thanks

Melih

It goes down to, IIRC 0.05 FPS. You have to switch it to low light mode. Look carefully within the fps override menu before you post again.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 24, 2013, 12:39:22 AM
BTW, shutter is what was causing all of those lines and dead pixels at fps like 1, .5, etc... so going back to that may cause the ugly defects to return and certainly don't want that... the low light with these problems was worthless.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 24, 2013, 03:20:45 AM
Hello Everyone,

Couldn't keep the camera still, shooing in crop mode with the 22m.  Also, want wide angle.  So I bought a Sigma 10-22mm.  I shot 1280x720 in crop mode at 24 fps.  I'm still having trouble keeping the camera steady.   And focusing!  You can see a clip in these test videos where I'm shopping for reading glasses.  I bought a pair at 3.25 magnification and they work well.  Hope to get to some tripod, people shots this weekend.  Haven't seen a touch of moire yet!

Have been spending oodles of time trying to find an ffmpeg output that has the same quality of TIFFs.  So far, can't do it.  The lossless setting for h264, gp 0, creates videos that don't play in Windows (or open in Vegas Studio).  So I've been using gp 1.  @Makr041 is right, of course, that creating a clip in Vegas Studio is very easy. 

My take, so far, is that the really good CODECs are proprietary (like Cineform 444).  The public ones, HUFFYUV and Lagarith, are no longer in development.  If anyone has any ideas, please let me know.

I noticed that the TIFFs that were generated from RAWanizer seemed to have a lot of red dots.  Long story short, when I found dcraw version 9.17 (link and photos in the RAWanizer thread) it seemed to render better TIFFs.

Here are the setting I'm using, currently, in RAWanizer

dcraw: -w -6 -T

video (ffmpeg):

-threads 8 -i "{InputVideoName}" -vcodec libx264 -pix_fmt  yuv420p -qp 1 -r {InputVideoFps} {Parameters}  "{OutputVideoName}.mp4"

Here some video footage from today.  I still try to shoot some in-camera H.264 comparisons.  But they're never close to what I'm now getting, even going straight from RAW to gp 1 H.264.  I'm going to stop doing those soon.



Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on August 24, 2013, 05:20:50 AM
@maxotic so, in your opinion what's better - the RAW or the H.264?  I realize that RAW is the real deal then the Video side.  I tried like you and many others, it's a great experience, but I don't see any difference in the RAW.  You're right, even if I tried the PDR and the Rawanizer, I still get other dots on sides of the clips.  So, DCRaw is the better choice in doing RAW/Tiffs -- I'm quite new to all things RAW...  Just like to hear other people's opinions.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 24, 2013, 10:07:06 AM
@CinB13:
can you show me an example of the remaining dots?

@maxotics:
why have you bought the simga 10-20mm instead of the canon ef-m 11-22mm? imho it would be much better choice for eos m, especially for shooting video.
1. much smaller
2. less distortion
3. IS (!!!)
Title: Re: Tragic Lantern for EOS M
Post by: atomas72 on August 24, 2013, 10:27:04 AM
funky,
when you have the black screen with green text saying successful, pull your battery out and then put it back in the camera.Now press the On button and it will start as normal. now tap the screen with two fingertips and the ML menus should show up.

gary
Thanks!! It's ok. tapping the screen with two fingers was the solution. :D
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 24, 2013, 01:39:44 PM
@Mixer2 Yes, I want the 10-22mm for all those reasons.   If I was rich I would have bought one.  Maybe even flown to Japan to get it ;) I found the 10-22mm Sigma on CL for $300 and I can easily use it with my 50D.  I also have a friend who wants a wide-angle at some point, so I can use it and pass it on to them with no loss of money.  Eventually  hope to get the one you mentioned.

@CinB13.  For almost all casual video RAW is not worth the effort.  The video that comes out of these cameras is pretty amazing.  I shot a small audition the other day, used the EOS-M's native video.  Very easy, good quality.  If I had tried RAW I would have needed extra cards, batteries, external audio, and hours of post production.  So, as you ask, why RAW?

Photography is my hobby.  I shoot mostly family and friends.  I like a clean look.  I especially like a natural, 3-dimensional look.  You can see my photos at flicr.com/maxotics, if you wanted an idea.  Mostly, I used Sigma DP cameras.  I've always loved film too, but video cameras that shoot video that looks like film, to me, or has the same quality as my still cameras, costs in the tens of thousands of dollars.  So I shoot camera video like everyone else.  What I would like is a video option, where I can shoot 10-30 seconds of video, that I could put with my stills, maybe in photo/video collages.  I started seeing RAW on Vimeo and knew it was possible.  I then bought Andrew Reid's "50D RAW Shooter's Guide" and tried it on a 50D I picked up.  I LOVED the results.  Now I'm trying with an EOS-M so I can have a camera that is very portable and can shoot RAW.  I should probably wait for the Black Magic Pocket, but, again, it's a hobby, and one doesn't do a hobby to wait and act rationally ;)

The reason you're not seeing the potential beauty of RAW is you're not shooting things you care about.  If you took some footage of someone you love with normal video, and then shot RAW (or had someone shoot it) you would notice that RAW, makes the skin look natural (not yellow and red).  The light would look as you saw it, not artificially bright.  There would be a three-dimensional quality to the image.  There would be no motion artifacts, little colored blocks dispersed thrugh the video, that everyone has gotten used to, like ugly telephone poles, but which, when removed, open up a more pleasurable viewing experience.

RAW is only better if you want certain niche things it can do.  I love all kinds of cameras.  I plan to shoot both RAW and in-camera video for a long, long time.  Knowing I can get near perfect video, with little money (though lots of time) is just something I want.

Finally, most of the videos I post, do not show RAW in all its glory.  They show certain technical differences.  In fact, some have complained about how unappealing these videos look.  They only mean something to others who have similar technical curiosity about what happens when one does this or that.   Right now, it's about ironing out technical issues for me.  My goal is beautiful video, though.
Title: Re: Tragic Lantern for EOS M
Post by: atomas72 on August 24, 2013, 02:44:24 PM
I read a lot of fantastic feature of ML, the most interesting, for me, seems to be video raw, I'm looking for the pinkdotremover.jar version for canon eos m raw video. Where can I find it?
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 24, 2013, 04:21:47 PM
Finally, most of the videos I post, do not show RAW in all its glory.

Speaking of which, has anyone tried a normal-dynamic range comparison (none of these, visible cloud vs visible indoor, but regular level of DR) between H.264 downscaled to 720p and the EOS-M 720p raw?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 24, 2013, 04:51:31 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on August 24, 2013, 06:28:09 PM
Speaking of which, has anyone tried a normal-dynamic range comparison (none of these, visible cloud vs visible indoor, but regular level of DR) between H.264 downscaled to 720p and the EOS-M 720p raw?

@feureau, If you move past my talking head you can see clips where I test exactly that.  A problem is that dynamic range is effected by initial exposure and your post processing.  So I feel people look at my clips and think, 'he just doesn't know how to expose/grade H.264 from the camera'  I've asked many times for workflow to bring in-camera H.264 to the DR I see in RAW.  No one has responded.  I can only say in my experience, working with the both RAW and H.264 from the same camera that RAW has more DR than H.264.  I think it is obvious to anyone if you ask them which video is more contrasty.  Or put another way, try as I might, I can't get detail to show in H.264 that I can in RAW.  In these clips I went straight to Cineform.  If I had graded from the TIFFs the detail enhancement would have been even better (again, in my experience).  Resolution does NOT equal DR.  I thought it would, but it does not (at least for me).  You might get more sharpness down-scaling, not DR, at least again, I can't.  Also, RAW to me gives that three-dimensional light feel to images.  H.264 doesn't, though again, others don't believe it or don't care or who knows what ;)

Title: Re: Tragic Lantern for EOS M
Post by: nech on August 24, 2013, 09:17:18 PM
Hello,

where can I found the last ML for the actual EOS-M Firmware?

thx
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on August 25, 2013, 01:23:33 AM
@CinB13:
can you show me an example of the remaining dots?

I, unfortunately have been testing around the RAW on EOS-M and may have deleted it.  But I tried the RAWanizer to remove the pink dots on the middle of the clips, let it run, go to my editing program [Vegas], and I do see blue dots on the right side of the clips.

So, I won't rule out the implementation of RAW in EOS-M as it got a lot of ways to go in my opinion, but I won't abandon my trying out H.264 either.

P.S.: While following Mark's version of using 720p RAW, I don't see the dots.
Title: Re: Tragic Lantern for EOS M
Post by: dcmgmt on August 25, 2013, 03:46:24 AM
@maxotics... You are correct about the DR. I believe there are several stops difference between RAW & H.264. Here are a couple ACR corrected frame grabs from my video shoot today which were a very good test of DR. Notice the properly exposed model while image detail is still well preserved in the highlights. Thanks to you and all the other wiz kids on here who got me off and running with the eosM!

https://www.dropbox.com/s/awv8jvdxz4ts0uv/Image7_ACR.jpg (https://www.dropbox.com/s/awv8jvdxz4ts0uv/Image7_ACR.jpg)

https://www.dropbox.com/s/sa4dmbgkltfkha3/Image11_ACR.jpg (https://www.dropbox.com/s/sa4dmbgkltfkha3/Image11_ACR.jpg)
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on August 25, 2013, 12:51:32 PM
apart from the RAW video, is there a solution to remove dead pixels from silent shots? I've tried pinkdotremover 2013.08.08 version but no luck. photos neither  squeezed nor have dots all over the place.

another thing is, when you use "take pics.. like crazy" on timelapse, it continues with real shutter action, I'd like to capture 1frame at a time, but fps override gives me headaches because of the half-pink frames and greenish view (I haven't seen anyone mentioned it, but my camera acts like brick sometimes. all the frames are greenish and not recording anything)

any help will be appreciated.

carl.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 25, 2013, 02:31:17 PM
silent dng should work with pdr... if any dots don't get removed upload an example dng please.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on August 26, 2013, 12:18:25 PM
silent dng should work with pdr... if any dots don't get removed upload an example dng please.

here they are, please zoom in to see the dots

original silent dng, http://www.qfpost.com/file/d?g=NmeQn7uLm
supposed to be corrected dng, http://www.qfpost.com/file/d?g=TUeCK3EmA
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 26, 2013, 03:08:27 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 26, 2013, 04:13:22 PM
Quote
Can we get PLEASE get some more audio control by allowing stereo audio out thru the USB AV port AND keep the video showing all the time on the camera's LCD?

2nd part is easy, first part is hard. It doesn't just turn on monitor like on 550D, need to configure the IC to enable monitor mode and I don't even see it in the 650D IC (probably identical) datasheet. Plus it won't even record or beep without freezing.

Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 26, 2013, 04:21:46 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 26, 2013, 04:28:18 PM
I don't know what you mean by the second part and first part.

gary

The second part is the latter bits, and the first part is the former bits, the former of the latter effects the latter of the former.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 26, 2013, 04:37:44 PM
LOL, I Know what that means. :-) I am saying I only asked for one thing. Make the LCD stay on with audio out thru the AV port. Can you be more specific on first and second?

gary
edit-ok, re read it. are you meaning the second part is keeping the lcd on all the time? and the first part as having ther audio out thru the AV?

Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 26, 2013, 04:50:55 PM
Yea, I just did the screen stays on portion... I found something else tho:

TestSetAudioHPMon 1 (24)
I2C > [22] aa
I2C done 1

So... I2C is writing to reg 22 and it wrote AA or the other way around. Maybe this is new way to do audio_IC write since 1/2 the regs on the new IC are only accessed with i2C. I think the parameter I'm throwing into hp mon isn't right. But at least something is happening.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 26, 2013, 04:59:00 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 26, 2013, 05:04:11 PM
It turns off audio when idle so its actually a bit of a problem, it comes back for a second when the meters are on the screen. But the gist of the above is that I caught it sending a command so if I figure out that & compare with the 650D datasheet something might be possible.
Title: Re: Tragic Lantern for EOS M
Post by: hansidar on August 26, 2013, 05:30:39 PM
It seems that there are several versions of a release that works with intervalometer, but none is gathered in one place.
There is a link at page 45, post 1110 wich contains a link.. but this zip file is pasword protected.
I am in spesific after intervalometer funtion... as i am about to put my camera in a multicopter.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 26, 2013, 05:48:13 PM
I have to go to work but I'm planning on EOSM full pack with autoexpo (need *other AE_VALUE maybe) and I wanted to do dual ISO but I'm stuck on logging the regs still. I thought someone posted a full release earlier in the thread.
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 26, 2013, 05:59:26 PM
It seems that there are several versions of a release that works with intervalometer, but none is gathered in one place.
There is a link at page 45, post 1110 wich contains a link.. but this zip file is pasword protected.
I am in spesific after intervalometer funtion... as i am about to put my camera in a multicopter.

Just tested the download link again and for me the zip file is not pasword protected - all works fine ...
Title: Re: Tragic Lantern for EOS M
Post by: FunFox on August 26, 2013, 06:15:25 PM
Is ML on the EOS M working with the Android App ML? Is the live view working?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 26, 2013, 06:44:18 PM
I don't know if M supports this, I don't have the OTG cable to check.
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on August 26, 2013, 07:42:27 PM
@zuzukasuma:

please download this file and replace the one in the dotData dir of your PinkDotRemover.
https://www.dropbox.com/s/j727o0iaho4i3vd/EOSM.txt

that silent dng resolution should work then too. if you find another silent dng resolution that doesn't work, please tell me that i can fix them too. in contrast to the raw movie dngs the silent dng do need special configuration for each resolution.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on August 26, 2013, 09:40:34 PM
@zuzukasuma:

please download this file and replace the one in the dotData dir of your PinkDotRemover.
https://www.dropbox.com/s/j727o0iaho4i3vd/EOSM.txt

that silent dng resolution should work then too. if you find another silent dng resolution that doesn't work, please tell me that i can fix them too. in contrast to the raw movie dngs the silent dng do need special configuration for each resolution.

thank you mixer2, it worked.

processed vs original
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fimg542.imageshack.us%2Fimg542%2F6668%2Fm7p.png&hash=9073b0076653f7c79aa544fcf6520475) (http://imageshack.us/photo/my-images/542/m7p.png/)

to my knowledge silent shots are 3:2 and full-screen, correct me if I'm wrong but all of them at the same resolution; 1734x695..

they are good for short silent timelapse shots, especially after resizing them to 2K on ACR8.

Title: Re: Tragic Lantern for EOS M
Post by: FunFox on August 26, 2013, 09:55:59 PM
I don't know if M supports this, I don't have the OTG cable to check.

The cam have a digital usb/av out. I thought this will be to send the live view to the tablet :o

Dose anyone tested to use the M + ML on Android?
Title: Re: Tragic Lantern for EOS M
Post by: rsaccon on August 26, 2013, 10:45:30 PM
The cam have a digital usb/av out. I thought this will be to send the live view to the tablet :o

Dose anyone tested to use the M + ML on Android?

Not tested myself (yet), from what I have heard all popular USB  remote control / tethered shooting solutions (including the ones from Canon) do not work on the EOS M. And ML on Android is not in active development, last time I checked, the modifications which allow PTP communication to android device were done on a custom version of ML, no idea if those commits have found their way into the main branch. If EOS M does communicate over USB (I really hope so) then it might be interesting idea to base the android app on dslr dashboard, which is open source and in active development.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on August 27, 2013, 07:53:24 AM
anyone working on solving issue of intervalometer? I don't want to use RAW video since there is a 4GB limit, but it seems the only option so far.
Title: Re: Tragic Lantern for EOS M
Post by: FunFox on August 27, 2013, 09:02:05 AM
Not tested myself (yet), from what I have heard all popular USB  remote control / tethered shooting solutions (including the ones from Canon) do not work on the EOS M. And ML on Android is not in active development, last time I checked, the modifications which allow PTP communication to android device were done on a custom version of ML, no idea if those commits have found their way into the main branch. If EOS M does communicate over USB (I really hope so) then it might be interesting idea to base the android app on dslr dashboard, which is open source and in active development.
Thank´s for your answer. DSLRdashboard I have tried. It looks like I can control some parts of the cam (ISO, shutter...) but no live view and no rec function.
For me the EOS M incl. the ML will be teh perfect cam to use in my electronic gimbal. ROW, remote controlled and light weight!
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 27, 2013, 09:10:37 AM
I don't know if it's related to the ML but yesterday I found my eos m can't show the real time exposure results when I adjust the exposure compensation. I can only see the results after taking the photo. Anyone has any idea?
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 27, 2013, 01:11:55 PM
I don't know if it's related to the ML but yesterday I found my eos m can't show the real time exposure results when I adjust the exposure compensation. I can only see the results after taking the photo. Anyone has any idea?

Apparently you've managed to find and disable the exposure sim menu. Enable it and it will adjust for expo comp again.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 27, 2013, 03:24:02 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: daduke on August 27, 2013, 06:24:01 PM
could anyone please tip me off on how to compile ML for EOS M 2.0.2? I have the toolchain and everything and can compile it just fine for my 700D, but the EOSM target in the unified branch seems to be for the 1.0.6 firmware. How do I get an autoexec.bin for 2.0.2?

thanks a lot,
-d
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 27, 2013, 06:34:02 PM
Apparently you've managed to find and disable the exposure sim menu. Enable it and it will adjust for expo comp again.

Thanks very much for the tips. I found the exposure sim option in the ML menu and enabled it to get the real time exposure again. But I can't find the setting in the canon stock setting. Anyone know how to find it?
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 27, 2013, 07:09:47 PM
could anyone please tip me off on how to compile ML for EOS M 2.0.2? I have the toolchain and everything and can compile it just fine for my 700D, but the EOSM target in the unified branch seems to be for the 1.0.6 firmware. How do I get an autoexec.bin for 2.0.2?

thanks a lot,
-d

Did you get your code from Hudson or tragic lantern? The latest is in tragic lantern, and I'm not sure why but it's been failing to compile on my ML compiler. (I'm using that VM thingy they put up)
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 27, 2013, 07:22:23 PM
could anyone please tip me off on how to compile ML for EOS M 2.0.2? I have the toolchain and everything and can compile it just fine for my 700D, but the EOSM target in the unified branch seems to be for the 1.0.6 firmware. How do I get an autoexec.bin for 2.0.2?

thanks a lot,
-d

Look here: page 45, post 1110
Title: Re: Tragic Lantern for EOS M
Post by: daduke on August 27, 2013, 07:46:22 PM
@funkysound: thanks, but I'm not looking for binaries (I have ML running on my M), but for a way to compile it myself

@feureau: oh, I wasn't aware of the tragic lantern fork. I just cloned it, but it also seems to be for 1.0.6 and no, I can't compile it either. Thanks for the hint!
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on August 28, 2013, 02:14:42 AM
I have a question:

Every time I use the ML to do do regular video recording, when I hit the red movie record button.  The screen tells me that Audio is disabled.  Is there a way to un-disable it - I'm not shooting Raw?  I'm just trying out different types like using the Anamorphic option since I have anamorphic projection lens and wanted to do some widescreen stuff.  Also when I try the Anamorphic, and then hit record with the audio disabled (I don't understand), my filming gets out of whack, e.g.: it shoots a frame a sec.

Is there a way to remedy this?

P.S.: when doing regular movie recording, it would say "Sound disabled"
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 28, 2013, 02:25:37 AM
For focusing I need to find a replacement for the property.
Title: Re: Tragic Lantern for EOS M
Post by: MrEdmondDantes on August 28, 2013, 02:35:17 AM
I have a question:

Every time I use the ML to do do regular video recording, when I hit the red movie record button.  The screen tells me that Audio is disabled.  Is there a way to un-disable it - I'm not shooting Raw?  I'm just trying out different types like using the Anamorphic option since I have anamorphic projection lens and wanted to do some widescreen stuff.  Also when I try the Anamorphic, and then hit record with the audio disabled (I don't understand), my filming gets out of whack, e.g.: it shoots a frame a sec.

Is there a way to remedy this?

P.S.: when doing regular movie recording, it would say "Sound disabled"

I would guess that you have "FPS Override" turned on, which will automatically disable sound in any mode.  Make sure that is off if you want sound, even when recording Canon h264.

Does that fix it for you?
Title: Re: Tragic Lantern for EOS M
Post by: epyonxero on August 28, 2013, 03:06:58 AM
anyone working on solving issue of intervalometer? I don't want to use RAW video since there is a 4GB limit, but it seems the only option so far.

Ive been using the intervalometer for the last couple of weeks with 2.0.2 firmware and it seems to be working fine.
Title: Re: Tragic Lantern for EOS M
Post by: CinB13 on August 28, 2013, 03:29:12 AM
I would guess that you have "FPS Override" turned on, which will automatically disable sound in any mode.  Make sure that is off if you want sound, even when recording Canon h264.

Does that fix it for you?

Well, I have worked with FPS Override turned off and still the Sound Disabled would come on after I record something.  Something I noticed, after I reverted back to 2.0.2 firmware, I had to bring my Sound Recording back to audio, so maybe it was something in my part.

I may try to go back to ML and figure out what's going on.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 28, 2013, 04:10:15 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: funkysound on August 28, 2013, 12:55:45 PM
I have to go to work but I'm planning on EOSM full pack with autoexpo (need *other AE_VALUE maybe) and I wanted to do dual ISO but I'm stuck on logging the regs still. I thought someone posted a full release earlier in the thread.

Is there any chance that dual ISO works also in the normal video mode or does it only work for RAW Video? (if it works on the M one day)
Even if the RAW video thing is really great ... I guess 90% or more of filming will still be H264
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 28, 2013, 03:49:03 PM
Yea, but dual ISO photos! I think it will work in LV/Photo as its digic V, differentiating what register is what may be hard but right now getting the log working would be nice.

I found focus info around 0x8926C. The numbers look like the prop on 6D, have to see what is what. and compare. Trap focus may yet work.

I plugged EOSM into USB... canon turns off LV and ML, I couldn't even log it. So if you're wondering why its not shooting LV over USB, now you know.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 28, 2013, 06:16:44 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 28, 2013, 06:25:20 PM
It keeps the video on, not outputting anything yet tho. Its not easy... I have to reverse engineer the whole thing... just audio here and 7D looks promising from looking at it. On other new cameras it just loads a whole mess of commands and sends it as 1 thing to the audio IC.. so like 2x harder to decipher.

There is a nasty way to have meters all the time:

      cache_fake(0xFF10ECF8, 0xE1A00000, TYPE_ICACHE);
Title: Re: Tragic Lantern for EOS M
Post by: BernardDigital on August 28, 2013, 08:39:59 PM
I installed ML and everything seemed to work... But no menu's... If I hit the info button a few times the ML overlays will come up but hitting the trash button at the bottom of the jog wheel dose nothing...

I am using a 128 gig card... But I followed the instructions to use MacBoot to make the card bootable and then copied the ML components to the root of the card... The only difference is I added the UpDater.fir with the modules and the correct Autoexec.bin file because my camera is on 2.0.2 and would not recognize the original .fir file...

Any insights on what I might have done wrong or tips and tricks would be amazing... Thank you!!!
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 28, 2013, 08:42:46 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 28, 2013, 08:48:51 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 28, 2013, 09:20:54 PM
Hi today I just found that the eos m can only use manual lens with M, Av, Tv, and P modes. The shutter can't be released under other mode even it is already set to release without lenses. I just wondering if we can break this limit and allow the shutter to release under all modes?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 28, 2013, 09:22:26 PM
So I can't turn on the meters myself :(... if I do it freezes like with wav. But I can stop them from turning off at least with so far no side effects.

What do you mean it can't? I took the lens off and it let me shoot in movie/photo mode.

Ok found a side effect, video w/audio locks up the camera, I'm having problems turning it off in the same manner as wav/asif/beep.

But found something new... state signatures?

http://pastebin.com/Y8TQYeTv

Title: Re: Tragic Lantern for EOS M
Post by: mountain_drew on August 29, 2013, 12:13:37 AM
I found focus info around 0x8926C. The numbers look like the prop on 6D, have to see what is what. and compare. Trap focus may yet work.
Trap focus would be amazing!
Keep up the good work!
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 29, 2013, 01:50:25 AM
The shutter can't be released without AF lens on under HDR and handle night shooting modes for example. Just like I said, it can only shoot under the first four M, Av, Tv, and P modes.
Title: Re: Tragic Lantern for EOS M
Post by: BernardDigital on August 29, 2013, 01:56:44 AM
tap the LCD display once with two fingers on one hand and the ML menus turn on. Tapping the Info button cycles through the four different displays with ML being one of them. The two finer tap on the LCD works with any display showing.

Gary

Thank you so much Gary and the Dev's for this amazing functionality...

Is the intervelometer working for everyone else? When I go to enable it, the camera pops back to video display and brings up a screen that says the intervelometer is about to start... but when it gets to zero nothing happens and the camera sort of locks up... none of the physical buttons work but if you tap with two fingers (thanks Gary  ;) the ML menu comes back up but you can only cycle to the right through the different categories but you can not select anything... The only way to get control back is to eject the battery and restart the camera...

Epyonxero, did you do anything special?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 29, 2013, 02:04:29 AM
Ok, those modes. I see override isn't overriding stuff for stills either.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 29, 2013, 03:33:34 AM
I'm still getting random purple. I'm still not sure how to reproduce it. But on one occasion, I got this recording:

>
The camera was actually panning down in that shot.

On a different occasion, last night, I was playing with the fps override and it consistently purple at 12 fps low light mode. I can turn it off with the on/off button and it will restart, but once I did a battery pull, it won't reproduce.

@1% have you ever had this problem? On the one hand it's annoying, on the other hand... is there a way to make this consistently reproducible so we can record glitch art videos? :D

EDIT: I managed to get a purple screen by using FPS override: These are 5 shots edited together.
Title: Re: Tragic Lantern for EOS M
Post by: vprocessing on August 29, 2013, 09:04:06 AM
I've posted a few days ago on page 44 reply 1075 of this thread…
I think I was so excited to have my M MagicLanternized ! that I forgot to set my brain to on !!! :P
So as I'm not used to touchscreen for serious gear… I didn't think ML was now a touch app !
So I've found most of my request with the touch menus !

If I understand well the squeeze is due to line skipping ?

I've found discounted Sandisk SDHC UHSI 95mb/s so I've bought one and RAW video seems to be stable.
I'm going to seaside to visit family, I'm gonna try longer recordings but from now 1 to 2 min shot are writing well.

PinkDotremoval seems to work like a charm ! How guys did that ? Are the dots in the metadata…can't understand how you achieve this process but it seems to work and to be without artefacts or approximation…

For me intervallometer still don't work : black screen, or Liveview working but with no response . When I set to Off, black screen with blinking LED, when then put on On it usually make a shutter sound but stuck on LiveView…So pull battery to unlock M…

Menu button change the apparence of the ML menu.

MY bigger QUESTION ??? :o  or REQUEST ?  8)
Will live audio monitoring will be available like on the mark II ?
The AV cable AVC-DC400ST (that is sold separatly…from 5 to 20$) would be required but for me, this function would be SOOOOOO NICE !
Is it possible ? Will you work on it ?

The crop mode is 3x on the M ?
Same crop factor on the 50D ?

I'm still booting each time for ML but didn't try to change for now

AGAIN MANY THANKS !
.V
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 29, 2013, 05:14:29 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 29, 2013, 06:13:09 PM
Quote
Will live audio monitoring will be available like on the mark II ?

It looks possible. I posted a whole thread about audio in reverse engineering. Need to figure out the I2c functions to send the commands or ghetto it somehow with the TestSetAudioHeadphone

I know about the purple FPS thing, just hit play if that happens and then go back to LV. I have to set better limits for timer B which I started and never finished.

BTW, found some dual ISO stuff. It should work in LV and photo, just have to figure out which is which.
Title: Re: Tragic Lantern for EOS M
Post by: markr041 on August 29, 2013, 08:19:06 PM
Just another vote for live audio monitoring (and audio meter fix). Meanwhile I am enjoying playing with RAW shooting.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on August 29, 2013, 11:36:02 PM
BTW, found some dual ISO stuff. It should work in LV and photo, just have to figure out which is which.

this is great! I'm looking forward to test dual ISO on EOS M. do you think you can crank the sensitivity to 14Ev (ISO 100-12800) ?

on 550D I can get max 11 + 2,4Ev (theoretically).
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 30, 2013, 05:47:07 AM
We'll see tomorrow. The 128K might not be real.
Title: Re: Tragic Lantern for EOS M
Post by: feureau on August 30, 2013, 06:48:55 AM
I know about the purple FPS thing, just hit play if that happens and then go back to LV. I have to set better limits for timer B which I started and never finished.

Cool. Thanks!

This is more of a feature request, but is it possible to add something to trigger this purple thing so we can make glitch-art videos not unlike this one: please? :3
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 30, 2013, 12:55:11 PM
Hello 1% I know you are busy with many other features development and may not be able to improve the magic zoom function so quickly. Therefore I have a little suggestion as a work around for the manual focus. Currently I am using the automatic zoom when half shutter in the liveview tweak function in order to precisely focus. It could be a very good substitution of the magic room function. However as I posted before this function currently works in a kind of unstable way. In many situation the liveview get automatic zoom right after the shutter half pressed. And that process just obviously delays the shutter time, which makes it difficult to capture some quick moments. So I am wondering if we can have the option to trigger that function after a certain period when half pressed the shutter and allow immediate shutter if directly pressed down it. I believe it could make this function even more useful and handy.

Of course we finally want to see an improved magic room feature since it doesn't change the view range.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 30, 2013, 04:15:30 PM
I know, I badly want sync on this camera... not just for MZ but display filter too. So far I've come up short.

Anyways, dual iso works. Wonder how it will play with the dots in LV, photo is ok it seems.

The digic registers make for much more fun glitch art than fps override :)

Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 30, 2013, 08:31:26 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 30, 2013, 08:35:35 PM
Its worth a check, I have a few things to check out actually before I put up another d/l
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on August 30, 2013, 08:42:14 PM
Anyways, dual iso works. Wonder how it will play with the dots in LV, photo is ok it seems.

I think we can use the same pink dot remover to remove dual iso AF dots.

its algorithm works the same way.
Title: Re: Tragic Lantern for EOS M
Post by: BernardDigital on August 30, 2013, 09:51:19 PM
Is the intervalolmeter working for everyone else? For me it hangs and freezes up the camera after the countdown gets to zero to start the time-lapse... 
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 31, 2013, 01:15:47 AM
Ok, here is the chance to find out I guess... I think sync is causing trouble with the LV dual ISO, it looks flashy on screen, not sure bout video so test first. Hopefully intevalometer works for you as it does for me.

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5DFullbackADTGui.zip
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on August 31, 2013, 02:04:33 AM
well, its not a bug but, in continuous mode, when you shoot Dual ISO ( with 1 normal - 1dual iso option ) 1st frame normal, 2nd frame dual-iso, 3-4-5-6 dual iso continues. timelapse and dual iso works so far but I think we need a new cr2hdr converter.

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fimg9.imageshack.us%2Fimg9%2F5998%2Flgh8.png&hash=d67ef94f554cd545493feb6ef6f845a7) (http://imageshack.us/photo/my-images/9/lgh8.png/)

*update: pink dot remover 2013.08.08 works to remove dots from RAW - Dual ISO video frames but, as I said before, we need new cr2hdr converter "pack" this time with raw2dng.exe :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 31, 2013, 03:36:39 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 31, 2013, 03:59:41 AM
Not ready yet unfortunately...

I can confirm the dual ISO thing. Post an image to the dual ISO thread or I will when the battery charges.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 31, 2013, 04:19:26 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: haomuch on August 31, 2013, 12:06:38 PM
@1%
Maybe we can trigger the auto zoom function only by the * key so that we can take immediate shutter without half press delay. Currently both key will trigger the function.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on August 31, 2013, 01:32:16 PM
Great work on this guys. ML is amazing. However, is there a fix for the 18-55 ef-m lens shutter bug, its a pita having to keep turning the camera on and off just to get a shot, i even missed a few because of it. Im running the latest firmware with the bootloading ML if that helps.

Thanks.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 31, 2013, 01:59:06 PM
Ok, here is the chance to find out I guess... I think sync is causing trouble with the LV dual ISO, it looks flashy on screen, not sure bout video so test first. Hopefully intevalometer works for you as it does for me.

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5DFullbackADTGui.zip

Hi formatted and loaded the new binary to the SD card as always. Things working fine except the the modules will not load - I get the message that the modules were not loaded but when I press the show console it indicates that the modules are loaded. Anything else to do?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 31, 2013, 06:02:46 PM
Quote
However, is there a fix for the 18-55 ef-m lens shutter bu

Post a DM log of it not working, try to take a pic several times while logging it.


Modules are opt-in now.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 31, 2013, 07:40:22 PM
Hi formatted and loaded the new binary to the SD card as always. Things working fine except the the modules will not load - I get the message that the modules were not loaded but when I press the show console it indicates that the modules are loaded. Anything else to do?

The DM Log file is way to big. Explorer hangs if I try to paste the contents on the thread!

Everything working fine except the modules will not load but when I press load modules the message is modules already loaded.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on August 31, 2013, 07:45:47 PM
Post a DM log of it not working, try to take a pic several times while logging it.


Modules are opt-in now.

@1% hope this helps sort the shutter bug

http://malakai.sytes.net/extras/DM.log (http://malakai.sytes.net/extras/DM.log)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 31, 2013, 07:53:14 PM
You have to set them on and then it will autoload at start... unless you turn that off.

Looking to see if there is anything in the log.

It starts to take the picture and then it cancels it for unknown reasons... canon bug of some sort?

Code: [Select]
fssSW1On
evfPrepareChangeVdInterrupt[FrameNo:365](366)[0x7c714c]
CancelDeliverStage
CancelJpegStage
[CFIL] CancelCFilterStage 0xff0d51d4 0x0
deliverCancelJob:0
Epp_CancelCompleteCBR (0x00000008)
jpegCancelJob:0
Alloc[0]Shrink[0]Free[0]JpegCnt[0]
evfCompleteTransferYuvCBR 0
Epp_CancelCompleteCBR (0x00000020)
[CFIL] roughMonoCancel 0xff0d51d4
Epp_CancelCompleteCBR (0x00000010)
evfJobCancelCompleteCBR
evfPrepareChangeVdInterrupt::1_5_INTERLACE
evfPrepareChangeVdInterrupt::RecMovie[0]
evfPrepareChangeVdInterrupt::Frame[0]
[VRAM] FrameParam[0xab6cd0][0x0][0x279b4][0x0]
[VRAM]vram_SetSenserDriveParameter(73, 946, 3 2)
[VRAM]vram_SetSenserDriveParameter(0, 0, 0 0)
SetVDFrameLiveViewDevice
Cartridge Cancel[0]
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on August 31, 2013, 08:10:04 PM
Can this be fixed do you think? Would a complete removal, format and reinstall cure this?

Thanks 1%
Title: Re: Tragic Lantern for EOS M
Post by: pironio on August 31, 2013, 08:21:14 PM
Hi, is there a specific place for feature requests? I really just want to know id its possible...

Can it be made so that the screen remains off, maybe through hitting the info button. I there are times when I dont even need the screen I know what I want and how to shoot is and the screen just slow me down.

Also, is there a way to turn off the auto focus on the shutter and port it to the record button on the back AF/AF Lock.

Sorry if this is the wrong place for this, I'm still getting my bearrings on the site.

Thanks.
Title: Re: Tragic Lantern for EOS M
Post by: Gevorg on August 31, 2013, 08:25:23 PM
1% thanks for Dual ISO!!! Great work!

As I understood cr2hdr doesn't work for EOS M. Are there other ways to handle them?

Thanks
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 31, 2013, 08:26:43 PM
Not yet, 700D is in the same boat.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 31, 2013, 08:30:34 PM
It is on 'autoload at start mode'. It just says 'module disable' against each module which are currently set to 'off'.

I may be missing a major step in the process.

This is what I did:

Format the SD card on the computer.
Format the SD card on the EOS M.
Copy the ML directory, autoexe.bin and *.fir files on the root directory of the SD card.
Firmware upgrade with the SD card in the camera.

Everything works fine except the modules just wouldn't load.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 31, 2013, 08:47:57 PM
Set the modules you want on and reboot. Its opt in... or turn autoload off and set the modules you want on then load them manually.
Title: Re: Tragic Lantern for EOS M
Post by: BernardDigital on August 31, 2013, 09:14:54 PM
Ok, here is the chance to find out I guess... I think sync is causing trouble with the LV dual ISO, it looks flashy on screen, not sure bout video so test first. Hopefully intevalometer works for you as it does for me.

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5DFullbackADTGui.zip

1% You are the man!!! Intervalometer is totally working flawlessly :) I guess I had a bad .fir compile... Thank you so much!!!
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 31, 2013, 09:21:08 PM
Set the modules you want on and reboot. Its opt in... or turn autoload off and set the modules you want on then load them manually.

That is the challenge - modules are not going on / these remain off even if I try to turn these on manually.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on August 31, 2013, 09:22:55 PM
Sorry stupid of me. Reboot makes these come on. Thanks as always.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 31, 2013, 09:57:41 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on August 31, 2013, 10:56:26 PM
@canon eos m, are you seeing this tab on menu?

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fimg18.imageshack.us%2Fimg18%2F4961%2Ffu8y.jpg&hash=aecdec25d08a57db7b84b902b3b482bb) (http://imageshack.us/photo/my-images/18/fu8y.jpg/)
Title: Re: Tragic Lantern for EOS M
Post by: AnotherDave on August 31, 2013, 11:01:49 PM
Does this work with the latest firmware?  I just bought a used EOS-M, and I'm looking forward to loading it up with ML!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 31, 2013, 11:26:39 PM
How does it not take pictures? Only problem is for that one lens that some people have issues on. Yes, this is 2.02 and no need for downgrades.
Title: Re: Tragic Lantern for EOS M
Post by: BernardDigital on August 31, 2013, 11:27:34 PM
Does this work with the latest firmware?  I just bought a used EOS-M, and I'm looking forward to loading it up with ML!

Yea I am using it with 2.0.2 and its working flawlessly for me... have not played with any of modules or raw record tho... 
Title: Re: Tragic Lantern for EOS M
Post by: BernardDigital on August 31, 2013, 11:36:40 PM
can someone help em with why my camera now does not take pictures? only video movies. I reverted back to just Canon firmware and the shutter then works to take pictures. Reinstalled ML and it goes back to not taking any pictures.

Gary

Yea I noticed with the m22 lens everything works... But if I put my m18-55 lens on I can't take pictures anymore... Do you think its something with how the camera registers that specific lens?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on August 31, 2013, 11:44:02 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on August 31, 2013, 11:51:22 PM
I'll have to compare the above log to one I take with the normal 22mm. Try using intervalometer with the "bad" lens... does it take pics?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 12:11:45 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: BernardDigital on September 01, 2013, 12:15:18 AM
No it dose not take pictures using the intervalometer with the m18-55 lens... It seems to be acting the way it was with the other build I was using... When the countdown gets to zero the camera locks and you have to remove the battery to get control back...

I have been running through the menu's on the m22 and everything seems to work :)

Again many thanks 1% (really cool name btw)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 12:30:06 AM
Do any other IS lenses have similar issues? I have nothing with IS to check.


Here is a bin that doesn't use the malloc memory area, still the same?

http://www.filedropper.com/eosmnomalloc
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 01, 2013, 12:44:06 AM
Do any other IS lenses have similar issues? I have nothing with IS to check.

I have EF-S 18-55 IS II from 550D kit and it seems to work fine, in fact I'm shooting my all timelapses with it, but I'm using lens twist method after setting up all settings. maybe I'm not experiencing any problems due to that.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 12:46:55 AM
It will let you take a photo normally though?
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 01, 2013, 12:48:07 AM
It will let you take a photo normally though?

yeah, no problem at all. maybe they're trying to take photos on video mode. I'm not able to take photos on video mode
Title: Re: Tragic Lantern for EOS M
Post by: BernardDigital on September 01, 2013, 12:52:15 AM
No I am not in video mode
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 12:57:27 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 01:32:11 AM
So IS works, just this one lens... The only other thing that blocks shutter is having crop mode on.

Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 01:39:32 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 01:56:24 AM
I guess we'll have to keep looking.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 01, 2013, 01:59:15 AM
Do any other IS lenses have similar issues? I have nothing with IS to check.


Here is a bin that doesn't use the malloc memory area, still the same?

http://www.filedropper.com/eosmnomalloc

Yeah still no shutter activation using 18-55
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 03:04:21 AM
With intervalometer too? AF off/on? Dummy mode/photo mode/movie?
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on September 01, 2013, 03:44:42 AM
I too had the no shutter issue with the 18-55, but may have a fix. I uninstalled ML with the lens on and fired the shutter with no ML installed but still on the card. Then installed ML with that lens on the camera. The shutter worked. I switched lenses, shutter worked. Put the 18-55 M back on, still worked.

Try that and see if it helps.
Title: Re: Tragic Lantern for EOS M
Post by: kaos42ze on September 01, 2013, 03:49:16 AM
Does anyone have the camera freeze with ML when going to a picture and trying to get to apply the Creative Filters ?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 04:08:44 AM
Its working here. Any more specifics?
Title: Re: Tragic Lantern for EOS M
Post by: dube on September 01, 2013, 04:41:41 AM
Could someone upload UpDaterM.fir to a site other than qfpost.com? That site is down.  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 01, 2013, 09:04:54 AM
I too had the no shutter issue with the 18-55, but may have a fix. I uninstalled ML with the lens on and fired the shutter with no ML installed but still on the card. Then installed ML with that lens on the camera. The shutter worked. I switched lenses, shutter worked. Put the 18-55 M back on, still worked.

Try that and see if it helps.

This didnt work for me. :(
Title: Re: Tragic Lantern for EOS M
Post by: gmueller41 on September 01, 2013, 10:31:20 AM
switch camera on without lens. Then mount 18-55 and you can make pictures.

sorry for my verry bad english
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 04:32:45 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 04:34:38 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 01, 2013, 04:40:05 PM
How can we turn the camera on without ML installing, yet keeping the files intact on the memory card? I have tried holding the set button down when turning the camera on, but ML still installs.

Gary

use firmware update to remove ML from camera, files will be stay on the card until you format. check faq for removal instructions

Carl.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 05:22:56 PM
Quote
I heard it was bad to switch lenses with the camera turned on.

Maybe not good repeatedly but as a test (and accident) I've done it and nothing happened.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 06:39:16 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on September 01, 2013, 07:49:30 PM
I had it again. After i shot some RAW video in crop mode the shutter on the 18-55 ef-m would not fire again. With the camera on I removed the lens not even all the way and put it back on and it fires again.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 01, 2013, 07:51:50 PM
I just tried it and it works now. But how can we avoid this? what is happening when we do this lens off and on with the camera powered on?
BTW, I am back one version of ML. The one "without" the headphone tab top left.

gary

So with your camera off you powered it up, then connected the lens and then you could shoot. What happens when you power off then back on again? Does the shutter activate still or do you have take the lens off and put it back on to get it to work? If so then id rather just power off and back on within a second to be able to use this lens for now until a fix is found.

Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 08:01:18 PM
Dual iso from this should be convertable... dunno how the video will do.

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/dual_iso.mo
Title: Re: Tragic Lantern for EOS M
Post by: daduke on September 01, 2013, 08:33:38 PM
Dual iso from this should be convertable... dunno how the video will do.

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/dual_iso.mo

yup, works like a charm! congrats. Could you commit this to the 700D module too?


thanks,
-Christian
Title: Re: Tragic Lantern for EOS M
Post by: mdwhaley on September 01, 2013, 08:37:41 PM
So with your camera off you powered it up, then connected the lens and then you could shoot. What happens when you power off then back on again? Does the shutter activate still or do you have take the lens off and put it back on to get it to work? If so then id rather just power off and back on within a second to be able to use this lens for now until a fix is found.

No. with the camera on I released the lens and turned to disconnect the terminals and then turned it back to remount it. I never turned it off
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 08:59:48 PM
700D is supported too, someone just has to commit.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 09:05:50 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 09:16:37 PM
asjdlfjsdlfj... this is a weird one... can anyone log with lens not working and then doing the twistaroo and the lens working?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 09:23:09 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 09:28:40 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 01, 2013, 09:40:36 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 01, 2013, 10:03:20 PM
I don't think its related to new dualiso.mo but I'm experiencing something,

here is the setup;
2 sec delay for taking photos
touch shutter active
iso 100, f/3.5, 1/60
canon ef-s 18-55 IS II with fake-chinese EF/EF-S to EF-M adapter
dual iso active ISO 100/400

here is the problem;
when ever I touch the screen to take photo, it countdowns, takes the photo, but then freezes, no light, no screen info, all buttons freezing. have to hard-reset the camera to get working again.


another problem started to emerge on camera,

silent-burst dual iso shots are limited to 2, when it comes to 3 it says "saving cancelled" and continues with the normal shutter action
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 01, 2013, 11:44:38 PM
How big are the shots vs memory. There is only less than 50Mb shoot malloc with raw photo quality and video mode.

I have to try touch shutter, I have it set off.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 02, 2013, 12:07:22 AM
How big are the shots vs memory. There is only less than 50Mb shoot malloc with raw photo quality and video mode.

I have to try touch shutter, I have it set off.

normal silent shots, 1734x695. I've checked it after disabling the dual iso, ettr, and other modules, now seems to work fine on highiso-multishot-noisereduce mode with 42 bursts.
Title: Re: Tragic Lantern for EOS M
Post by: yno0o_15 on September 02, 2013, 07:29:33 AM
Just new here.

I just purchased an EOS-M with version1 put ML on it and happy with it.,

now i want to update it to version 2 can ML work on version 2 of eos-M? does it still have bugs in it? or its fully functional?

what are the steps? and download sites thanks in advance godbless you all guys for developing this wonderful tool ^_^
Title: Re: Tragic Lantern for EOS M
Post by: nick.p on September 02, 2013, 09:51:30 AM
Just new here.

I just purchased an EOS-M with version1 put ML on it and happy with it.,

now i want to update it to version 2 can ML work on version 2 of eos-M?

what are the steps? and download sites thanks in advance godbless you all guys for developing this wonderful tool ^_^
Can somebody post the file that was located at qfpost.com/file/d?g=NzBmhwaBK I can't download it because the site is down.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 02, 2013, 11:18:42 AM
@1%

Ive made a new DM.LOG for you to have a look at to see if you can see anything that may help with the shutter bug with the 18-55mm efm lens.

I started the log, powered off the camera for 10 seconds, powered up, activated the shutter three times, powered off and back on again within 2 seconds, activate the shutter three more times this time with it actually taking shots and powered down. Hopefully it might indicate where the problem is.

DM.LOG (http://malakai.sytes.net/extras/DM.LOG)

Hope it helps
Title: Re: Tragic Lantern for EOS M
Post by: dube on September 02, 2013, 12:28:49 PM
Can somebody post the file that was located at qfpost.com/file/d?g=NzBmhwaBK I can't download it because the site is down.

Bump again for this... there is no way for us to install ML without it. That site seems to have bit the dust.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 02, 2013, 12:39:18 PM
Bump again for this... there is no way for us to install ML without it. That site seems to have bit the dust.

which file is it? ill put a link up to it for a few days from my server until its updated
Title: Re: Tragic Lantern for EOS M
Post by: nick.p on September 02, 2013, 12:42:15 PM
which file is it? ill put a link up to it for a few days from my server until its updated
It's the UpDaterM.fir file. I can also host it for as long as it is needed.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 02, 2013, 12:52:08 PM
edit:

upped to mega

UpDaterM.fir (392 KB) (https://mega.co.nz/#!SMg1WA5L!VHegzkKhCKhN6xJeMezFE0zigmIlYT8GWexN5QDYQNA)

Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 02, 2013, 01:31:42 PM
Good morning folks! Sorry if this is the wrong place to ask! I have a new EOS M that came with firmware 1.06 so I want to know where to find the proper build of ML to use or if its better to update to 2.02. The build I´ve found its for 2.02. Also I´m not sure which tutorial to use, just format the sd card or if I have to use EOSUtility.

Thanks and keep the good work!
Title: Re: Tragic Lantern for EOS M
Post by: nick.p on September 02, 2013, 01:46:25 PM
Good morning folks! Sorry if this is the wrong place to ask! I have a new EOS M that came with firmware 1.06 so I want to know where to find the proper build of ML to use or if its better to update to 2.02. The build I´ve found its for 2.02. Also I´m not sure which tutorial to use, just format the sd card or if I have to use EOSUtility.

Thanks and keep the good work!
I was in the same position a few hours ago. I was trying to avoid updating to 2.02 because I didn't think the boot flag was working. I struggled for about an hour before updating and now everything works perfectly. I was even able to compile the latest version and slap that on.
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 02, 2013, 01:53:27 PM
I was in the same position a few hours ago. I was trying to avoid updating to 2.02 because I didn't think the boot flag was working. I struggled for about an hour before updating and now everything works perfectly. I was even able to compile the latest version and slap that on.

Can you post a guide? I´m just worried about the lens focus issue with the 18-55 lens and firmware 2.02
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 02, 2013, 02:01:08 PM
Can you post a guide? I´m just worried about the lens focus issue with the 18-55 lens and firmware 2.02

What focus issue?
If you are referring to the shutter bug, i think it only effects the 18-55 ef-m but if you turn the camera on then power off and back on within 2 seconds its fine. Basically, when you first power on the shutter wont activate but doing the quick power cycle it fixes it.
Ive posted a new log for 1% to see if anything can be cross referenced from the before and after powercycle. Cross your fingers.

IMHO bootloaded ML on 2.02 is fantastic, focus peaking is an absolute godsend and i dont know why canon didnt include this as part of the stock FW. Also having the ability to up the bitrate on video capture as well as being able to use one picture style for photos and it auto change to another for video is brilliant!
Title: Re: Tragic Lantern for EOS M
Post by: nick.p on September 02, 2013, 02:02:08 PM
Here's how I did it:
Step 0: Update to version 2.02

Step one: Format the card using the computer
Step two: Format in camera
Step three: Put these files on the card - http://www.nickpotts.com.au/downloads/ML_nick_g3gg0_30_Aug_2013 (http://www.nickpotts.com.au/downloads/ML_nick_g3gg0_30_Aug_2013)
Step four: Enable the boot flag and eos develop in eoscard - found here: http://pel.hu/eoscard/ (http://pel.hu/eoscard/)
Step five: Run software update on camera
Step six: Celebrate?
I'm not 100% this will work but this is approximately what I did.
Title: Re: Tragic Lantern for EOS M
Post by: yno0o_15 on September 02, 2013, 03:04:35 PM
how can i update to version 2? sorry guys newbie here ^_^ tnx

is ML in ver2.0.2 1005 bug free now? and 100% working?
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 02, 2013, 03:34:21 PM
how can i update to version 2? sorry guys newbie here ^_^ tnx

is ML in ver2.0.2 1005 bug free now? and 100% working?

Grab the 2.02 fw from canon, pop it in the root of a SD card and go to FW in menu and update.

ML is still in Alpha. Its still buggy. Its not ready for main stream release as its still being worked on and so is installed at your own risk.

Hope this helps.
Title: Re: Tragic Lantern for EOS M
Post by: yno0o_15 on September 02, 2013, 03:42:23 PM
thank you
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 02, 2013, 04:23:32 PM
Here's how I did it:
Step 0: Update to version 2.02

Step one: Format the card using the computer
Step two: Format in camera
Step three: Put these files on the card - http://www.nickpotts.com.au/downloads/ML_nick_g3gg0_30_Aug_2013 (http://www.nickpotts.com.au/downloads/ML_nick_g3gg0_30_Aug_2013)
Step four: Enable the boot flag and eos develop in eoscard - found here: http://pel.hu/eoscard/ (http://pel.hu/eoscard/)
Step five: Run software update on camera
Step six: Celebrate?
I'm not 100% this will work but this is approximately what I did.


Thank you Nick! That worked great except from one link, the Magic Lantern zip does not work, it needs the EOSM1202.FIR file, your link does not have it.

I used this one instead. All worked great!

http://cdn.bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5DFullbackADTGui.zip

Another question, whats que Q button on the M? I cant seem to find it to set the settings on the intervalometer module.

Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 02, 2013, 04:26:34 PM

Thank you Nick! That worked great except from one link, the Magic Lantern zip does not work, it needs the EOSM1202.FIR file, your link does not have it.

I used this one instead. All worked great!

http://cdn.bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM%5DFullbackADTGui.zip

Another question, whats que Q button on the M? I cant seem to find it to set the settings on the intervalometer module.

Thanks!

highlight it and touch the screen to bring up the second menu
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 02, 2013, 04:57:41 PM
I couldn't find any pics being taken in the log. You can't power down while logging or it will stop going I think.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 02, 2013, 05:16:59 PM
I tried taking three shots from powering it on with the shutter not activating because of the bug but then powered off and back on before the light flashes. (If the light flashes after powering off, when powering it up the bug persists) I then took three more shots, this time it worked and took pictures. I then went into the ML menu and hit DL to stop the log....

Wait, i just realised, yeah, it may have stopped the log on the powerdown. Ill do two logs. One powered up with the camera not taking shots. then ill do the restart trick, start another log and take shots with it working and paste both logs here. Perhaps cross refrencing them will help that way. Give me two minutes.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 02, 2013, 05:32:35 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 02, 2013, 05:40:56 PM
I couldn't find any pics being taken in the log. You can't power down while logging or it will stop going I think.

@1%

try these two logs

No shutter activation (http://malakai.sytes.net/extras/eosm/DM_NOACT.LOG)
With shutter activation after quick restart (http://malakai.sytes.net/extras/eosm/DM_ACT.LOG)

Hope these help
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 02, 2013, 05:57:38 PM
Ok, checking it out. BTW the dual ISO for silent pics/video may still have issues so don't shoot anything important with it.
Title: Re: Tragic Lantern for EOS M
Post by: Escaperoute on September 02, 2013, 06:04:45 PM
I am thankful for what 1% has done. But when i install the newest update the modules didn't load. So i can't record raw and auto ETTR couldn't load and dual iso of course don't load.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 02, 2013, 06:36:21 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 02, 2013, 06:37:44 PM
hopefully 1% can figure it out :D
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 02, 2013, 06:40:27 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 02, 2013, 07:24:52 PM
So maybe false alarm about the video:

9-2-CR2hdr-Raw2dng-EOSM.zip (72 KB)
https://mega.co.nz/#!5sRilQJb!bs1pIFbAFwxt7unCkIl3wm2VQbIyhn9fbXB_rsC-auQ


These are correctly built cr2hdr.exe and raw2dng.exe.. you need your own dcraw (9.19 is the latest) and exiftool.

Still says black subtraction failed but the files are coming out... I had lots of trouble using "other" versions. Dunno if you'll have all the libraries, built on mingw + mysys system win7x64.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on September 02, 2013, 07:26:29 PM
Raw video files don't have any black correction info yet.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 02, 2013, 07:30:32 PM
That explains it. I can build "linux" cr2hdr into an EXE (make cr2hdr) or make cr2hdr.exe... former doesn't produce proper files, they have weird horizontal banding, etc.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 02, 2013, 07:56:11 PM
9-2-CR2hdr-Raw2dng-EOSM.zip (72 KB)
https://mega.co.nz/#!5sRilQJb!bs1pIFbAFwxt7unCkIl3wm2VQbIyhn9fbXB_rsC-auQ

is it possible to upload file to another server? I'm not able to access mega.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 02, 2013, 08:10:31 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 02, 2013, 09:04:23 PM
thanks Gary, I've checked the results from new cr2hdr.exe and cr2hdr_exp.exe, not much of a difference, or I think I have to test them in daylight to see the difference.
Title: Re: Tragic Lantern for EOS M
Post by: kaos42ze on September 02, 2013, 09:59:01 PM
Its working here. Any more specifics?

every time i go to press PLAY than press MENU and to to CREATIVE FILTERS ... and try to apply filters the camera will get stuck and no button works until i remove the battery
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 02, 2013, 10:40:30 PM
First off, thanks tons @1% for putting together [EOSM]FullbackADTGui.zip, I've been waiting for a proper Alpha update like this to move up to the v2 firmware. I did so yesterday, and everything is working great for me (or as expected). At this point, I'm not too terribly concerned about RAW workflow, at least not until 2048/24fps is field-dependable. I am wondering however about ML's research history into different captured resolutions in h264. Likely something that's been discussed, but I've failed to locate any discussion of consequence in the forum. Understanding that Movie Crop Mode reduces the bayer pattern to a 1:1 pixel capture ratio, has there been any luck in writing the full sensor to h264? I'm able to write 1920/24fps at 5x CBR without my camera even breaking a sweat with a 45/mbps card, and Movie Crop Mode would be much more useful with the whole sensor as canvas, especially in LiveView. Just some thoughts, I'm really pushing to make this device my full-time production camera. To me, the smaller the rig, the better.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 02, 2013, 11:54:37 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 03, 2013, 12:20:53 AM
@gary2013 - My go-to lens has been Canon's EF 24mm f/2.8, but in Movie Crop Mode, it makes me terribly claustrophobic. I'd love nothing more than to live in Crop Mode because of the tighter pitch and lack of interference, but APS-C sensors already have a 1.6 crop factor, then zoom by 2.7 and I'm suddenly on a 104mm lens. I either need to switch to a 8mm lens to compensate, or figure out how to capture more of the 5,184 total pixels; 4096x2160/24fps in h264 at a respectable bitrate would be super rad.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 12:55:36 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 03, 2013, 01:06:36 AM
Anthony, I've been shooting with the Sigma 10-22mm, in crop mode, with good results. (using Canon EF adapter).  Although the lens and adapter add considerable size to the camera, the weight actually helps me hold it steady.  I've heard the 8mm has some distortions.  I'm going to get a Century Optics .5x wide angle adapter for my 22mm and see how that works.  It's $165 and I'm hesitant, but I know the cheap ones are probably a waste.  The lens is very small.  If it works, that would be the way to go.  So you may want to wait until I get and can post some video.  As for shooting H.264 over RAW, to each is own!  I like the subtle water-color look of RAW.
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 03, 2013, 01:07:20 AM
@gary2013 - I wish I could jump in and help out with the project, but alas, I don't know C. @maxotics - Don't get me wrong about RAW; I am looking forward to using it in production when I can, but for now I'm pretty happy with h264 results using ML.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 01:20:28 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 03, 2013, 01:20:34 AM
@Anthony, I went out and shot some RAW on my 50D.  Come home, it's now in the .MLV format.  Brilliant work by the Magic Lantern team, I'm sure.  But now what am I supposed to do with it?  The processing software is not really ready yet.  All this to say I wouldn't try to push anyone into RAW.  You want to be well-rested ;)  Also, if I could get a flatter picture using H.264 I would maybe you or someone else can tell me how.  That would be great.  So far, everything in the shadows goes to black for me.  In what software?   I'm on a PC and use Vegas Studio (the cheap version)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 03, 2013, 01:34:42 AM
try different profiles like Cinestyle or Flaat

^this

@maxotics - I love love love Technicolor's CineStyle PP; shadows and highlights stay very useable in most situations. Compared to Neutral, it's actually quite difficult to bake all the detail out of your shadows.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 01:52:14 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 02:21:02 AM
Creative filters still working, even with modules loaded.... I dunno what else can be done with H264 in terms of size, if something is figured out sure. Its NOT simple to change the LV size... each one is its own mode.
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on September 03, 2013, 02:31:59 AM
I hate to bother the devs with my trivial problems but I'm so excited to try dualiso that i had to post :P. I have the module working but im on a mac and the build of cr2hdr that i compiled from the ML source isn't working. I know 1% posted a windows binary, so I pulled it up in my wine, however, the dcraw 9.19 isn't running under wine. Is there a trick to compiling it correctly? Am I using the wrong source?

You guys rock

Edit: tried building form TL-6D tree, too. same error...

Edit: so i got it a dcraw.exe 9.19 (http://www.centrostudiprogressofotografico.it/en/dcraw/) working in wine, but i still get the same error as i would running the native built one: Interlacing method not supported
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 03, 2013, 02:45:14 AM
I dunno what else can be done with H264 in terms of size, if something is figured out sure. Its NOT simple to change the LV size... each one is its own mode.

That's sort of what I figured after finding this thread: http://www.magiclantern.fm/forum/index.php?topic=2758.0

Movie Crop Mode's LV when capturing in h264 appears to represent the full 1920x1080 area of the resulting video, however. Canon's choice, or was that a ML effort?
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 02:50:23 AM
I think crop mode is less skips, it was canon's choice.. hence no 6D/5DIII (doesn't have the crop stuff).

Maybe something can be done with ADTG/CMOS but the jury is still out.
Title: Re: Tragic Lantern for EOS M
Post by: eosm1986 on September 03, 2013, 04:28:27 AM
I've tried to find some answers here, but am having trouble.  Hopefully I'm not out of place asking this question.  I am not really all that into the shooting of the RAW video, but am mainly looking to put ML on my EOS-M for the live histogram and focus peaking features. 

Questions:
1.  There seems to be some conflicts about whether or not you can automatically load ML on bootup, or if you have to flash every time you use it.  I know an older version was flash on every use, but any new ones where that isn't the case?
2.  If there is a "new" version, is it really risky to install?  It almost seems like we're flashing firmware designed for a Sony onto the EOS-M.  Maybe I'm just not understanding?

Thanks for everyone's amazing efforts here, and again, pardon my ignorance.
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on September 03, 2013, 04:45:36 AM
Questions:
1.  There seems to be some conflicts about whether or not you can automatically load ML on bootup, or if you have to flash every time you use it.  I know an older version was flash on every use, but any new ones where that isn't the case?
2.  If there is a "new" version, is it really risky to install?  It almost seems like we're flashing firmware designed for a Sony onto the EOS-M.  Maybe I'm just not understanding?

Thanks for everyone's amazing efforts here, and again, pardon my ignorance.
1. 1% just posted a new version that does not require flashing i.e. the bootflag works: FullbackADTGui.zip"]https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM]FullbackADTGui.zip (http://"https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM)
You have to set up your card to with with ML. Use EOSCard or MacBoot: http://magiclantern.wikia.com/wiki/Unified/Install (http://magiclantern.wikia.com/wiki/Unified/Install)

2. It's risky because its Alpha, but i have not had any problems. I do have to pull battery out whenever it stalls just in case it may overheat. Otherwise it seem relatively stable considering its Alpha.

From what I understand there is nothing Sony about this. Correct me if i'm wrong. If anything the new dual_iso module is something Nikon does.
Title: Re: Tragic Lantern for EOS M
Post by: eosm1986 on September 03, 2013, 04:50:30 AM
1. 1% just posted a new version that does not require flashing i.e. the bootflag works: FullbackADTGui.zip]https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM]FullbackADTGui.zip (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM)
You have to set up your card to with with ML. Use EOSCard or MacBoot: http://magiclantern.wikia.com/wiki/Unified/Install (http://magiclantern.wikia.com/wiki/Unified/Install)

2. It's risky because its Alpha, but i have not had any problems. I do have to pull battery out whenever it stalls just in case it may overheat. Otherwise it seem relatively stable considering its Alpha.

From what I understand there is nothing Sony about this. Correct me if i'm wrong. If anything the new dual_iso module is something Nikon does.

Wow!  That was quick.  Thank-you!  I have a 8GB SD card, but when I pull up EOSCard with the files on it, it throws the errors FAT32 VBR failed.  Anyone see this before?  Looks like a few people have seen it before, but no definitive answers.  I've tried multiple times, without effect. 
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on September 03, 2013, 05:01:52 AM
I haven't had this problem since i'm on a mac so the other threads might be more helpful. My hunch is that you haven't done a low level format through your EOS M.
Title: Re: Tragic Lantern for EOS M
Post by: eosm1986 on September 03, 2013, 05:18:38 AM
I haven't had this problem since i'm on a mac so the other threads might be more helpful. My hunch is that you haven't done a low level format through your EOS M.

Hmm - very strange.  No, I just tried a "non-quick" format on my PC followed by a low-level one of the EOS M.  No change.  Boy, after reading about this ML, I'm really excited to use it - if I can get this SD card working. 
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 05:45:29 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 05:52:56 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 05:57:54 AM
It shuts down LV when it connects to the computer. I think its missing the functions to pass lv over USB. I can try PTP to just send it commands.
Title: Re: Tragic Lantern for EOS M
Post by: eosm1986 on September 03, 2013, 07:27:15 AM
Make sure your battery has a good/full charge, and make sure your camera is set to the M (manual) mode for pictures. Then go to the Canon menu option for firmware version which is the last yellow tab on the right. BUT, before all of that, make sure you prep your card in the ways listed, each step in order. It's talked about on here many times. I don't remember the exact reply number. Doesn't hurt to read through the messages on here. You can learn a lot. Maybe even start around page 30 or so and you will find the list of steps.

Gary
Edit= here is a start, page 34, Reply #840

Thanks for everyone's help.  Got it working, but just by copying the files to the card and updating the firmware.  I never was able to make the card truly bootable with EOSCard - just wouldn't recognize the VBR on the SD card.  Hopefully that helps someone.
Title: Re: Tragic Lantern for EOS M
Post by: pizmon on September 03, 2013, 07:28:17 AM
I am new to this forum, very impressed and thankful for your hard work  I loaded successfully the ML however I have two issues, one, no matter what i do I end up with 29.97 f/s even-though I selected 24 f/s frame rate override and second issue,  in crop mode I get 23.97 f/s however image has pinks fine dots all over the place (dot remover doesn't remove them) Am I doing something wrong I am especially disappointed by the frame rate why i can get 24p in raw.  When I do playback (export from after effects) footage seems slightly fast motion
Title: Re: Tragic Lantern for EOS M
Post by: pinghua on September 03, 2013, 08:35:01 AM
Do you have trouble with intervalometer with exposure ramping?  I am having trouble getting it to work.  I can set values, but it will say 0 picture taken when it counts down to take photos. 
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 03, 2013, 09:04:48 AM
@1%

Were those logs any use for the 18-55 shutter bug?


Thanks
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 04:07:19 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 04:20:28 PM
Quote
Were those logs any use for the 18-55 shutter bug?

I looked and still can't find anything that's actually an error. I dunno whats up with just this particular lens.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 04:45:23 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 05:04:34 PM
Yea, I looked over both, maybe some canon task gets stuck and restarts? Really strange problem.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 05:09:23 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 03, 2013, 05:10:16 PM
bummer, its a pita to use that lens having to powercycle just to get shots. But you gotta do what you gotta do.

Thanks for all your help 1%

Edit:

I was hoping that the log would show the difference between the shutter not activating and activating when using the cycle/remove lens trick too.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on September 03, 2013, 05:11:58 PM
Does the lens problem happen without ML?

If not, it's easy to troubleshoot: just disable ML components one by one (or all of them, then enable one by one).
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 03, 2013, 05:16:05 PM
lens is fine without ML, ive not tried disabling components one at a time though. Ill try it now.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 05:17:58 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 03, 2013, 05:21:14 PM
ive just tried it with everything off including modules and with just the modules loaded and its still not activating the shutter.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 05:22:10 PM
I think you'd have to take features out 1 by one and recompile.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 03, 2013, 05:23:49 PM
that sounds like a lot of work. shame the logs we posted cant narrow it down a little.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 03, 2013, 05:26:14 PM
where can i get the updated modules, im getting v2.0 expected v3.0
ETTR.MO
FILE_MAN.MO
PIC_VIEW.MO
RAW_REC.MO
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 05:30:15 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 05:37:47 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 05:43:19 PM
Maybe its related to the USB problem where the camera goes freezy when you pull usb.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 03, 2013, 05:56:45 PM
1% Is it just you working on this version of ML?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 06:00:39 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 06:04:40 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 06:25:08 PM
See for me connecting to my linux pc it doesn't do the cleaning message... and I got LV on with cache hacks while USB is connected. Dunno what the EOS utility will do now, have to try it. Won't let you access the currently used folder.
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 03, 2013, 08:57:20 PM
I looked and still can't find anything that's actually an error. I dunno whats up with just this particular lens.

I´ve been having this problem also, the strange thing is when I installed ML everything worked fine, after a day of use the problem started (unable to shoot a picture using the 18-55 kit lens), the only way to overcome the bug is to turn the camera off then turn it on in less than 2 seconds, sometimes this does not work and you have to repeat the process several times in order to shoot some pictures, its extremely annoying. I´m getting an adapter and I will try to reproduce this error with EF lenses.

But all of this is normal given this is alpha software! Thanks for the great work 1%!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 09:06:53 PM
I used the adapter and wasn't able to reproduce it with lenses other than this one. Above even IS lenses were used and working so its just something this lens does special.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 09:14:47 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 03, 2013, 09:34:21 PM
I used the adapter and wasn't able to reproduce it with lenses other than this one. Above even IS lenses were used and working so its just something this lens does special.

perhaps its something related to the fact that this lens have focus and IS that are enabled or disabled electronically, unlike other EF or EF-S lenses.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 03, 2013, 10:04:42 PM
hey folks, I'm sure you all have ef/ef-s to ef-m adapter, if you don't have it'll be 50$ on ebay (chinese copy) and many of you have other crop sensor canon cameras, 550D, 600D, 60D, use a normal EF-S 18-55 IS II (which costs $50 to $100, new STM is $150 I think).

there is obviously something wrong with EF-M 18-55 IS STM.
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 03, 2013, 10:08:41 PM
there is obviously something wrong with EF-M 18-55 IS STM.

It's a super dark lens, to boot; f/3.5 maximum? No thanks.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 03, 2013, 10:09:39 PM
It's a super dark lens, to boot; f/3.5 maximum? No thanks.

do you know what I'm talking about? check older posts about that 18-55 STM EF-M lens.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 10:25:40 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 03, 2013, 10:26:29 PM
do you know what I'm talking about? check older posts about that 18-55 STM EF-M lens.

I've never owned that lens, myself. Wasn't interested, just bought the body and an ef adapter.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 10:27:54 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 10:32:39 PM
Quote
There is "logically" something wrong with how ML handles the info from this lens.

Probably ML is using some memory area that canon wants to use and some task/process hangs.

I'd say sure, use ANYTHING better and chuck it in the bin but this lens comes with a lot of EOS-Ms and/or costs like $150+.
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 03, 2013, 10:40:09 PM
the forum is here for "all of us" to help fix and test things for ML. NOT to debate about who's lens is better. There are plenty of other forums to have those pissing contests.

Sorry, just got off topic; my apologies.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 10:47:47 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 10:49:35 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 03, 2013, 10:54:05 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 03, 2013, 10:58:00 PM
Not sure, I can try to figure out the USB bug, maybe its related to the same thing. I had this on 6D where something wasn't patched right and wifi/usb would lock up on 112.
Title: Re: Tragic Lantern for EOS M
Post by: gravitatemediagroup on September 04, 2013, 04:39:43 AM
sorry if I missed this in a previous post,  am I supposed to delete another file when adding the DuelISO mod. 
I'm assuming it went in the mod folder, or does it go on the root? 
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 04, 2013, 11:41:56 AM
Just had a thought. I never noticed the 18-55 efm shutter bug when i was loading the firmware via FW menu. Before the bootloading version. Perhaps there is something during bootloading that is causing the problem.
Title: Re: Tragic Lantern for EOS M
Post by: nanomad on September 04, 2013, 12:13:55 PM
@1%: What boot method are you using on the M?
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 04, 2013, 12:57:23 PM
@1%
I just noticed in post #248 you managed to up a new autoexec file that fixed the bug for jupiter55. I tried that autoexec on the latest bootloading version but i just get flashing sd light and have to pull the battery to reset.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on September 04, 2013, 02:10:28 PM
I hate to bother the devs with my trivial problems but I'm so excited to try dualiso that i had to post :P. I have the module working but im on a mac and the build of cr2hdr that i compiled from the ML source isn't working. I know 1% posted a windows binary, so I pulled it up in my wine, however, the dcraw 9.19 isn't running under wine. Is there a trick to compiling it correctly? Am I using the wrong source?

You guys rock

Edit: tried building form TL-6D tree, too. same error...

Edit: so i got it a dcraw.exe 9.19 (http://www.centrostudiprogressofotografico.it/en/dcraw/) working in wine, but i still get the same error as i would running the native built one: Interlacing method not supported

Hi, I downloaded dcraw 9.19 but did but no relief. The dual-ISO photo will not convert with cr2hdr.exe.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 04, 2013, 02:42:40 PM
Can ML do HDR h.264 video? Ive been using the Film Picture style but if i could get HDR too that would be fantastic!


Edit: found it ;)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 04, 2013, 03:11:36 PM
Quote
@1%: What boot method are you using on the M?

6D method. I have to double check restart address and the 2 locations but it looks right. It uses malloc for bvram but without it the kit lens still locks.

Quote
Before the bootloading version.

It was still booting the same just exploiting the FW menu first to restart.
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 04, 2013, 03:40:42 PM
A totally unrelated question. I´ve been using the EOS M for timelapses and the intervalometer is one of the best ML features for me.

Is there a way to disable the liveview while taking photos on the EOS M using the the intervalometer of ML? I cant find a way to turn the liveview off, and the screen drains the battery so fast specially when doing timelapses.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on September 04, 2013, 03:45:37 PM
So maybe false alarm about the video:

9-2-CR2hdr-Raw2dng-EOSM.zip (72 KB)
https://mega.co.nz/#!5sRilQJb!bs1pIFbAFwxt7unCkIl3wm2VQbIyhn9fbXB_rsC-auQ


These are correctly built cr2hdr.exe and raw2dng.exe.. you need your own dcraw (9.19 is the latest) and exiftool.

Still says black subtraction failed but the files are coming out... I had lots of trouble using "other" versions. Dunno if you'll have all the libraries, built on mingw + mysys system win7x64.

Hi 1% please teach me to extract dual iso CR2's from the EOS M to dng.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 04, 2013, 03:46:37 PM
I don't think you can disable the screen completely. Power save with the shortcut might black it out, just set a dim/off value too and then hit info.

Post a Cr2, the utility worked for me on both LV and photo.

Another attempt to fix the lens issue, change boot to copy and restart. It doesn't fix the USB but try with the kit lens:

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/EOSM-COPY.zip
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 04, 2013, 08:13:20 PM
I don't think you can disable the screen completely. Power save with the shortcut might black it out, just set a dim/off value too and then hit info.

Post a Cr2, the utility worked for me on both LV and photo.

Another attempt to fix the lens issue, change boot to copy and restart. It doesn't fix the USB but try with the kit lens:

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/EOSM-COPY.zip

I´ve tried, it worked the fist time then after restarting the camera locks up i have to remove the battery to boot it again. Do i have to flash the firmware again? There´s a EOSM_202.sym on your zip file, I dont know if i have to change the extension to fir.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 04, 2013, 08:15:54 PM
I´ve tried, it worked the fist time then after restarting the camera locks up i have to remove the battery to boot it again. Do i have to flash the firmware again? There´s a EOSM_202.sym on your zip file, I dont know if i have to change the extension to fir.

EOSM_202.sym' is for putting in to ML\modules folder

carl.
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 04, 2013, 08:38:39 PM
EOSM_202.sym' is for putting in to ML\modules folder

carl.

thanks, now i can´t shoot pictures even after turning it off then on quickly, reverting to previous version.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 04, 2013, 08:42:58 PM
thanks, now i can´t shoot pictures even after turning it off then on quickly, reverting to previous version.

new version doesn't require such action like flash reboot.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 04, 2013, 08:59:49 PM
It didn't have any problems like that unless stuff is copied to wrong locations... but if the lens still doesn't work its not the boot method.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 04, 2013, 09:30:28 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 04, 2013, 09:39:37 PM
So the boot method isn't the problem.. with copy and restart it lets you come back from that sensor cleaning but still not shut down... I'd log it but at that point logging doesn't work... you can't touch shoot mem or stack space and they are 0.

Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 04, 2013, 09:41:52 PM
new version doesn't require such action like flash reboot.

i mean that the problem is still present, and even with this version i cant seem to shoot anything.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 04, 2013, 09:51:32 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 04, 2013, 09:59:07 PM
Well I can reproduce it now:

Copy&restart - Unplug usb, off, sensor cleaning -> power back on, won't shut down
Cache hack - unplug, off, sensor cleaning -> black screen

So it comes back w c&R but you still have to pull the battery.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 04, 2013, 10:04:41 PM
I am sorry to report that the Century Optics .5 Wide Angle Adapter does NOT work with the Canon 22mm pancake that is often bundled with the EOS-M.  It is impossible to get focus at any distance.

My guess is that it is designed for camcorders with lenses farther back from the mount and smaller sensors. 

Looks like I will have to get a 10-20mm Canon EOS-M lens from Canada at some point.  My Sigma 10-20mm, with the EF mount, works well on the EOS-M.  So I would expect the same, if not better (IS), from the Canon lens.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 04, 2013, 10:06:47 PM
i mean that the problem is still present, and even with this version i cant seem to shoot anything.

its getting boring to read posts about 18-55 STM here. we know it has a problem, and only one developer tries to fix it. I wish I'm capable of fixing it but I'm not. if you're not able to shot sth ML & 18-55 then try to shoot without 18-55 STM. I don't have the lens I've bought the camera with 22mm f/2 kit and works fine for me. even if I want to use 18 mm I connect my old 18-55 IS II with ef/ef-s to ef-m adapter and works just fine.

@maxotics, if you'd like to spend a few more dollars, I recommend you to use 12-24 sigma for canon, it also supports full-frame usage.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 04, 2013, 10:42:21 PM
@zuzukasuma  Thanks for the suggestions. I have a Sigma 10-20mm that I use with the EF Adapter.  It works very well.  However, I have it on a 50D and would like a setup for each camera.  I would think the Canon 10-20 lens made for the EOS-M would be the best route, but that's $400 and now I'm wondering if I should just wait for the BMPCC if I'm going to start throwing that kind of money around :)  I'm in a real pickle.  On CL I can see a 17mm/3.4 for $150, or a 15mm/2.8 for $450.  Is it worth it? Those lenses good for all Canons.  Maybe just get some sort of way to steady the 22mm in crop mode.  Or maybe a Sigma 17-70/2.8?  Whoa is me  :(  What other suggestions do you have?  What I want is EOS-M, small enough to fit in a fanny pack, where I can go into crop-mode and take what I think is exceptional RAW video at 720p--as wide as possible.  EDIT. I now see there is a 12-24 Tokina f/4 for $350 on CL
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 04, 2013, 10:43:06 PM
its getting boring to read posts about 18-55 STM here. we know it has a problem, and only one developer tries to fix it. I wish I'm capable of fixing it but I'm not. if you're not able to shot sth ML & 18-55 then try to shoot without 18-55 STM. I don't have the lens I've bought the camera with 22mm f/2 kit and works fine for me. even if I want to use 18 mm I connect my old 18-55 IS II with ef/ef-s to ef-m adapter and works just fine.

@maxotics, if you'd like to spend a few more dollars, I recommend you to use 12-24 sigma for canon, it also supports full-frame usage.

I´m just trying to help 1% to find the bug, i know this is alpha software and there will be bugs, im willing to deal with the workaround in order to use the other features, my adaptor is coming. Thanks for your patience.
Title: Re: Tragic Lantern for EOS M
Post by: tetsu on September 04, 2013, 10:48:05 PM
@zuzukasuma  Thanks for the suggestions. I have a Sigma 10-20mm that I use with the EF Adapter.  It works very well.  However, I have it on a 50D and would like a setup for each camera.  I would think the Canon 10-20 lens made for the EOS-M would be the best route, but that's $400 and now I'm wondering if I should just wait for the BMPCC if I'm going to start throwing that kind of money around :)  I'm in a real pickle.  On CL I can see a 17mm/3.4 for $150, or a 15mm/2.8 for $450.  Is it worth it? Those lenses good for all Canons.  Maybe just get some sort of way to steady the 22mm in crop mode.  Or maybe a Sigma 17-70/2.8?  Whoa is me  :(  What other suggestions do you have?  What I want is EOS-M, small enough to fit in a fanny pack, where I can go into crop-mode and take what I think is exceptional RAW video at 720p--as wide as possible.

If you are in to video you must look at Bower/Rokinon/Samyang (they all are the same brand) manual lenses, they are great and cheap. If you want to use them on the EOS M you have to enable the custom operation > others menu > option 7 > Release shutter with out lens in order to use manual lenses.

The 24mm f1.4 is around 500$ but not that wide on crop sensors.
Then you have the 14mm f2.8 for 300 or 330$ on some places, quite a nice wide on a crop sensor.
If you want to go the ultra wide route then go for the 8mm f3.5! Its around 215 - 250$.

Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 04, 2013, 10:50:41 PM
@tetsu

I've read the 8mm distorts in crop mode.  As for the others, I agree with you, the optics are fine.  I am a Rokinon 85mm.  However, the price difference between those and Canons are sometimes not worth losing auto focus (nice to have).  If I went that route, and I'm tempted, I'd see how low the 15mm/2.8 canon guy would go.  He's asking $450.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 04, 2013, 10:51:25 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 04, 2013, 10:54:23 PM
@gary2013  A guy on DPreview said he got one from Henry's in Canada.  Henry's Online it say $400, so that is probably the way to go.  If that's Canadian dollars even a bit cheaper.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 04, 2013, 10:59:26 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 04, 2013, 11:05:08 PM
@maxotics,

its logical to buy this lens as soon as it's on the market
http://petapixel.com/2013/08/14/review-can-the-canon-ef-m-11-22mm-revive-the-eos-m-system/

seems to have distortion problems too but definitely worth to try.

@Canon eos m

do you have new cr2hdr.exe from DUAL ISO page? it seems to work fine, if you don't, this works fine https://www.transferbigfiles.com/9114e79a-8d7a-4910-83c7-3c2ceea08c23/B4THtf_L9lqWULe0XrnLWQ2



and !!! @gary2013, if you have rights to post your problems here, I have my rights too, and your message insulting & offending my post (!)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 04, 2013, 11:31:47 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 04, 2013, 11:33:27 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 04, 2013, 11:44:30 PM
The forum is to help dev's , like 1%, test and fix problems for "ML". You say you are bored reading about a legitimate problem with an M lens. As I said, then don't read those posts. You are wrong with all your talk about other lenses and posting anything you want, which has nothing to do with ML, testing and fixing problems.Use email or PM outside this forum for other discussions off topic. This is the second day now this has happened. How many posts have you made so far in total to help ML?? 

I am sorry you feel insulted. That is you problem you brought on to yourself. I was not trying to insult you. Start showing some respect to 1% and the rest of us on here working hard at making ML good for the M camera and everyone around the world that like using ML on the M.

if I post 3 questions like you in separate posts, I'd have 150 posts now, I'm trying to get the best out of M but its a cheap-o camera with limited hardware. its not a rock-n-roll star like 5D.III, has capabilities but still sucks in some aspects. if there is a real problem with the EF-M 18-55 STM lens why only 2-3 people complaining about it? maybe your lenses are defective (yeah, have you ever thought about it!?).

I'm trying to be as clear as possible to ask my questions and post my problems here. unlike you not posting over and over and over again. learn to use modify button.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 12:13:42 AM
Hi Guys, this stuff if very frustrating and the ML forum, in all it's chaos, certainly doesn't put me in a more patient mood ;)  Let's give each other some room to vent once in a while.  I've said stuff I didn't want to say either.

Looks like I may be having problems similar to the lens issues you are discussing.  I put on the EF adapter, then the 10-20mm Sigma, went out, and it wouldn't shoot RAW, maybe one second.  Also, the aperture was locked to the shutter speed.  I couldn't get it working.  Maybe it has something to do with changing lenses? 

So I came back, put 1%'s new "EOSMFullbackADTGui" build on a new 32GB card (which I wanted to do anyway) but that didn't fix it, indeed, the camera became crazier.  All these messages "modules already loaded".  The ML screen comes up, but the modules don't show they're loaded, though I could make changes to video ML.  I disabled autoboot.  Tried again old card.  Anyway, camera is not working in ML mode anymore.   

Can someone give me a fool-proof method to get camera back?  Or any ideas?  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 05, 2013, 12:40:32 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 12:42:03 AM
Extra files in modules folder like dis/en... Module system probably changed in between.

BTW the C&R bin does have problems.. its just for testing whether that was the prob with the lens.

The camera also dislikes one of my EF to nikon adapters, it says upgrade lens firmware.
Title: Re: Tragic Lantern for EOS M
Post by: RenatoPhoto on September 05, 2013, 12:48:47 AM
Please stop the arguing.  Help the devs in anyway you can and keep the posting to the subject of this post i.e. EOS M.  Other subjects can be discussed in General Chat.
If you want to argue about something then do it off the board!
Title: Re: Tragic Lantern for EOS M
Post by: nick.p on September 05, 2013, 01:01:35 AM
I've been trying to use the mlv_rec module. I always get a file creation error and then it fills the buffer but doesn't write to the card. Does the mlv module work?
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 01:08:15 AM
Although I mucked up my 50D a few days ago, I haven't changed the ML on my EOS-M for some time.  So I think, either the lens change, or some key combination, corrupted it.  I then did as Garry suggested.  1. format on PC, 2 format on camera, then 1st ML stuff onto card, eos util, then 2nd part.  I tried 1%s stuff but had same problem.

1% Again, is there a place that spells this out a bit more.  A lot of what you say is in short-hand and I don't understand.  What was the purpose of your latest build?  Why is it called "[EOSM]FullbackADTGui"  Should I try again with it, only copy some modules? 
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 05, 2013, 01:48:54 AM
I've been trying to use the mlv_rec module.

What is mlv_rec? It wasn't included in 1%'s recent [EOSM]FullbackADTGui package. While I'm on the subject, what is adtg_gui?
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 05, 2013, 01:58:40 AM
I've been trying to use the mlv_rec module. I always get a file creation error and then it fills the buffer but doesn't write to the card. Does the mlv module work?

not everything for EOS M, its only running on 50D and 5D Mark II now, its RAW 2.0 video format.

@AnthonyEngelken, its been out for EOS M ML development for some time, detailed info here -> http://magiclantern.wikia.com/wiki/ADTG

in addition, I'm having sensor breakdown, or something else on my EOS M with fps override even at 14fps.

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fimg19.imageshack.us%2Fimg19%2F2802%2Fwubu.jpg&hash=46df81a0fa9340ea872c67acc1df146c) (http://imageshack.us/photo/my-images/19/wubu.jpg/)
Title: Re: Tragic Lantern for EOS M
Post by: eosm1986 on September 05, 2013, 02:02:55 AM
First of all, thank-you for this firmware.  It really is pretty amazing.  Just a question - I've looked around, but been unable to find an answer.  It seems now that I've loaded the ML firmware, my camera has a REALLY strong affinity towards larger apertures.  It's virtually impossible to get it to stop down below F3.2.  It will, but almost never.  The used to be able to guess pretty much exactly what aperture the camera would choose in P mode - but now, it's almost impossible to get it away from the large apertures.  Anyone else having similar issues?

Thanks again to all.
Title: Re: Tragic Lantern for EOS M
Post by: nick.p on September 05, 2013, 02:04:29 AM

not everything for EOS M, its only running on 50D and 5D Mark II now, its RAW 2.0 video format.
That makes more sense now. I was compiling the source and it was included by default.
Title: Re: Tragic Lantern for EOS M
Post by: nick.p on September 05, 2013, 02:05:05 AM
double post  :(
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 05, 2013, 02:12:25 AM
...Anyone else having similar issues?..

I had those issues then I've used lens twist method with fixed depth-of-field or just Av mode

@nick.p, I think %1 is trying to find registers for SD card controllers on MLV_REC.mo, you can help with it. thread is here -> http://www.magiclantern.fm/forum/index.php?topic=7122.new#new
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 02:18:12 AM
I recorded with it, seems to work. For that error just press play, fps override sometimes misses mode changes.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 05, 2013, 02:20:17 AM
I recorded with it, seems to work. For that error just press play, fps override sometimes misses mode changes.

uh, I thought its a hardware issue, I'm always getting rid of it by play-half shutter, thanks.
Title: Re: Tragic Lantern for EOS M
Post by: eosm1986 on September 05, 2013, 03:39:14 AM
I had those issues then I've used lens twist method with fixed depth-of-field or just Av mode


Lens twist seems to fix the aperture, which is exactly opposite of what I want to do.  Do you mean "When" you used lens twist?  Is there a way to avoid the "sticky" aperture - where it prefers the wide open?  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 03:43:24 AM
Since some commit the mode changes are sometimes missed and this happens, I noticed it on 6D too but there you get 1/2 a screen, go back to zoom mode and the FPS is right, lol.. but I finally looked at timer B again and got 48FPS in crop mode, then my battery died so I'm waiting to see if its nice or even possible to record.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 05, 2013, 03:55:36 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 05, 2013, 05:42:44 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 05, 2013, 10:34:49 AM
1%
When the camera doesn't take pics with the 18-55, I can go to modules menu, press load all modules, shut the camera off, turn the camera back on and then it takes pics. If I then shut the camera off and then back on, the camera goes back to not taking pics. I can keep repeating this cycle. I don't know if you can find anything helpful about that cycle to fix the problem.

Gary

When you load all modules then power off are you waiting for the SD light to flash once then powering up or powering up before that light has flashed?
If you power back up after that light has flashed it still wont shoot. I think that final write closes something or resets something that brings back the lens bug. If you power off before that light flashes and back on then it will shoot.
Crazy bug!! Its the only one that for me is holding ML back a little as I only have the 18-55mm ef-m. I still use it but its a real PITA doing the power cycle every time I want to use it.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 05, 2013, 11:46:49 AM
@1% am I right in thinking you dont have the EOS M to work with? Not criticizing. Just curious. If you dont then hats off to you!
Title: Re: Tragic Lantern for EOS M
Post by: mixer2 on September 05, 2013, 12:00:09 PM
@gary2013:
had not much time for photo and video the last days... last time i tried everything worked fine. but there were also some people having problems with current ml versions on the 650d, because the dot positions changed. maybe they changed the way how the crop offset is calculated. try this dot data file:
https://dl.dropboxusercontent.com/s/j727o0iaho4i3vd/EOSM.txt
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 05, 2013, 12:26:12 PM
Just pondering stuff, is it possible to boost fps on the liveview to 60fps instead of it being 30fps? I only ask cuz i just noticed it jump to 60fps for a second or two after i did something, possibly changed menu or something.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on September 05, 2013, 03:02:55 PM
@Canon eos m

do you have new cr2hdr.exe from DUAL ISO page? it seems to work fine, if you don't, this works fine https://www.transferbigfiles.com/9114e79a-8d7a-4910-83c7-3c2ceea08c23/B4THtf_L9lqWULe0XrnLWQ2

Hi, I did download the cr2hdr.exe from the link but maybe it is some problem with my workflow. Don't know what I am doing wrong? Copied the cr2hdr.exe from the link; copied the dcraw 9.19 version; copied the exiftool - all in the same folder. But do not see the conversion. The cr2hdr.exe starts out but then the screen is gone without any conversion.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 03:08:48 PM
Make sure all programs are unblocked on windows.


I have the EOSM but I don't have the kit lens. Reverse engineering a camera isn't so simple though. If you don't believe me, try it.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 05, 2013, 03:15:35 PM
I can only imagine. Its folk like you that are a godsend to everyone else. As far as im concerned you are an amazing human being.

Thanks for everything you have done so far.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 03:50:18 PM
The more I think about, the more I believe my EOS-M ML getting corrupted happened when I changed the 22mm for the EF Adapter with Sigma 10-20.  I can see the red light blink, even when camera is off, when I do that.  So the circuitry is doing something.  Also remember trying to put M43rd adapter on it.  Maybe I brushed a contact in the wrong way.  I'll see if I can replicate.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 05, 2013, 04:18:25 PM
Hi, I did download the cr2hdr.exe from the link but maybe it is some problem with my workflow. Don't know what I am doing wrong? Copied the cr2hdr.exe from the link; copied the dcraw 9.19 version; copied the exiftool - all in the same folder. But do not see the conversion. The cr2hdr.exe starts out but then the screen is gone without any conversion.

uh, make sure you have administrator rights to use all the programs, sometimes my windows asks for file security (or unknown program source) but works fine. I recommend you to use the DUAL prefix for dual iso shots, it makes life easier with cr2hdr.exe.

@%1, are you considering of running cr2hdr.exe multi threaded? because I'm using 2 virtual machines with my base system. saves lot of time when processing them.

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fimg801.imageshack.us%2Fimg801%2F9384%2F4ymt.jpg&hash=ffc4a5ea5bd7ac4a96d2ba9ef458b5dd) (http://imageshack.us/photo/my-images/801/4ymt.jpg/)
(1st and 2nd horizontal windows are virtual machines, provided by vmware workstation, windows 7 pro virtual, I'm using "unity" expansion, makes easier to use other machines side by side)
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 05, 2013, 04:23:49 PM
The more I think about, the more I believe my EOS-M ML getting corrupted happened when I changed the 22mm for the EF Adapter with Sigma 10-20.  I can see the red light blink, even when camera is off, when I do that.  So the circuitry is doing something.  Also remember trying to put M43rd adapter on it.  Maybe I brushed a contact in the wrong way.  I'll see if I can replicate.

same thing happening on my camera since the 1st day. when I connect the lens (even camera is off) it checks the lens then turn off. yours the same?
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on September 05, 2013, 04:25:35 PM
uh, make sure you have administrator rights to use all the programs, sometimes my windows asks for file security (or unknown program source) but works fine. I recommend you to use the DUAL prefix for dual iso shots, it makes life easier with cr2hdr.exe.


The cr2hdr.exe version works fine to convert dual iso files from teh 5D Mark III but does not work with the Canon EOS M. I copied the files to the root directory but no success.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 04:27:10 PM
Quote
I can see the red light blink, even when camera is off, when I do that.

All lenses do this.

I'm thinking any corruption would be from wrong modules/sym. They load at startup now by default so if your modules folder is messed up it will freeze on bootup and then next time you get the camera wasn't shut down properly... next time freeze again, etc.

If you have a dual file you can't convert, post it.
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on September 05, 2013, 04:32:51 PM
The cr2hdr.exe version works fine to convert dual iso files from teh 5D Mark III but does not work with the Canon EOS M. I copied the files to the root directory but no success.

The command prompt screen comes and goes quickly therefore I cannot see the error. But was something to do with blending, etc.

Edit: Finally managed to capture the error with the burst mode on my 5D Mark III.

"Interlacing method not supported"
"ISO blending didn't work"
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 04:49:34 PM
So I guess you see the stripes in the photo? Maybe using the older version that has 4 lines? try running it in a cmd window and look at the pattern. its going to be like dBBd or something like that.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 05:48:57 PM
same thing happening on my camera since the 1st day. when I connect the lens (even camera is off) it checks the lens then turn off. yours the same?

I'm running a new card on the EOS-M, went through Gary's steps, but the camera is still very flaky.  I can't change the ISO, the screen goes weird in only showing that setting over the LiveView.  I can't get to shutter or fstop, can only change via EV.  The * button is the same as the left click on the wheel.  Anyway @1%, I can't see how I have weird things in the folder since I'm using the same load from a few weeks ago.  Files I put on the card first, I then do the CardUtility, the add the second set of files.  Nothing new.  I've done "clear all settings" a few times in the EOS-M.

Can you give me a fool-proof way of bringing the camera back to where it was a couple of weeks ago?  Once that's working, I can experiment with some lens changing procedures to see where the corruption stems from.  Perhaps you could create another binary download like your ADTKGui thing that you believe the most stable?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 05, 2013, 05:53:42 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 05, 2013, 05:58:34 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 05, 2013, 06:21:31 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on September 05, 2013, 07:19:38 PM
(1st and 2nd horizontal windows are virtual machines, provided by vmware workstation, windows 7 pro virtual, I'm using "unity" expansion, makes easier to use other machines side by side)
Zuzu, are you converting EOS M dual ISO raw files or from another camera? I haven't had success with mine running in wine (windows emulator for *nix, mac in my case). I'm asking because my ISO pattern readout is as follows:

ISO pattern    : dBdB RGGB

My resolutions are also slightly off...

here is the whole output:
Input file     : DUAL9990.CR2
Full size      : 5280 x 3528
Active area    : 5208 x 3476
White level    : 14798
Black borders  : 72 left, 52 top
Black level    : 1973
ISO pattern    : dBdB RGGB
Interlacing method not supported
ISO blending didn't work

i've tried compiling from TL-6D sources and I get the same result.
gcc version 4.7.4 20130613 (release) [ARM/embedded-4_7-branch revision 200083] (GNU Tools for ARM Embedded Processors)
Raw photo decoder "dcraw" v9.19

edit: apologies, the new .exe on the bitbucket makes progress but doesn't quite work. this is probably a wine problem. is there any way to get this working cross platform?
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 05, 2013, 08:17:27 PM
Malakai, you are right, I was doing the quick off and on and not realizing it. It happens when you work a lot and late at night. Sorry.

Gary

No worries lol
Title: Re: Tragic Lantern for EOS M
Post by: eosm1986 on September 05, 2013, 09:44:33 PM
Lens twist seems to fix the aperture, which is exactly opposite of what I want to do.  Do you mean "When" you used lens twist?  Is there a way to avoid the "sticky" aperture - where it prefers the wide open?  Thanks!

Is there a hard reset of the settings?  Or should I reflash the firmware do you think?  Or perhaps ML is more sensitive to dust on the lens and is focusing on that?

Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 10:20:53 PM
Moved install instructions to post 1500
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 10:41:29 PM
Quote
dBdB

This is the problem I think. Its doing every other line instead of 2 dark, 2 bright. So these photos are probably fubar unless I can figure something out with the converter. I took a bit to find the flag that gives the correct pattern. I do need to make another build I think since everyone is confused (+ changes).. I would hope you would test dual iso before using it for something serious at least once.

Install is easy.

1. Drop the EOSM fir from the "fullback" (typo, fullpack). Run that from the firmware update menu, when you have success shut down the camera.

2. Pop the card into your computer and make it bootable with EOScard.

3. Place ML files on the card, ie ML folder, autoexec.bin

4. Boot.

You can reset all settings from the canon menu, for ML delete magic.cfg Reflashing the firmware over and over will not help you any.


Quote
i've tried compiling from TL-6D sources and I get the same result.

Try to compile the new module too. and use that with the new exe. EOSM just got added to the converter as of 45 minutes ago.




Quote
I can't see how I have weird things in the folder since I'm using the same load from a few weeks ago.

Last couple of days the module system changed again from opt out to opt in. So you would have had to delete the whole module folder and re create it to keep out any .dis .en types of files. Also as above, try resetting all canon settings from the menu and see if that helps any because I can't reproduce any inability to change stuff, getting stuck on auto, etc. The copy & restart bin did lose control of the shutter for some reason tho.

Title: Re: Tragic Lantern for EOS M
Post by: a1ex on September 05, 2013, 10:50:15 PM
Its doing every other line instead of 2 dark, 2 bright.

Gimme, gimme.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 10:54:58 PM
Here is one that was sent to me... the 4 on 4 off I deleted.

https://www.dropbox.com/s/xxoxnqnjbonmul1/IMG_0895.CR2?m

Quote
@%1, are you considering of running cr2hdr.exe multi threaded?

I wish, it takes forever on my machine running native too.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 10:56:59 PM

Install is easy.

1. Drop the EOSM fir from the "fullback" (typo, fullpack). Run that from the firmware update menu, when you have success shut down the camera.

Try to compile the new module too. and use that with the new exe. EOSM just got added to the converter as of 45 minutes ago.

Last couple of days the module system changed again from opt out to opt in. So you would have had to delete the whole module folder and re create it to keep out any .dis .en types of files. Also as above, try resetting all canon settings from the menu and see if that helps any because I can't reproduce any inability to change stuff, getting stuck on auto, etc. The copy & restart bin did lose control of the shutter for some reason tho.

Sorry 1%, you're dealing with a 52-year old here :)

When you say fullback you mean this?
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM]FullbackADTGui.zip

I see EOSM-copy has a .fir file and autoexec.bin, are the files from the fullback supposed to be replaced with these?

Sorry, everything from "Try to compile..." I don't understand.  I can forget for now, think it best I/we just have steps to bring camera to where you expect it to be from install/re-install. 

I know you're handling two different problems now, sorry!  I'm modifying my post above.  Can you review, tell me what I should change?  THANKS!!!!

Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 11:02:52 PM
INSTALL AND RE-INSTALL OF EOS-M CAMERAS

Thank you 1%, Gary, and others for your help.

STEPS TO REMOVE ML FROM EOS-M

MAKE SURE MANUAL MODE ON...
1. Turn camera on in Photo mode (middle button top dial)
2. Press "Mode" box on touch screen, top, left
3. Press wheel left until you get to 'M' box (manual)
4. MENU, then First Wrench, then Format Card
   Don't tap screen to format card (keeping ML). Select and press OK
5. Goto last wrench, Update Firmware, pick latest version, SET (now that card's been formatted, it has no ML so camera will see nothing, and look to revert to factory boot)
6. GREEN ML screen should come up about BOOKDISK flag
7. Rotate dial to Movie mode
8. WHITE ML screen will now say "BOOTDISK flag is DISABLED"
9. Turn Camera Off
10. Format card in computer.
11. Format card in camera.

EOS-M SHOULD BE AS IT CAME FROM FACTORY

RE-INSTALL ML (1% Build)

1. Get latest EOS-M install.  Currently: http://ml.bot-fly.com/  (Thanks Jerrykil)
2. Drop the EOSM fir from the zip file
3. Copy autoexec.bin from zip file to card.
4. Copy ML folder to card
5. Camera in 'M' mode, last wrench, update firmware
6. When you have success shut down the camera.
7. Pop the card into your computer and make it bootable with EOScard.
8. Put card back in camera, and start

Other issues

o. Shutter-bug Issue with 18-55mm M STM lens
Using the 18-55 kit lens for video can stop working for photos.  There are two workarounds: 1.) Power up, rotate lens to break connection with camera and rotate back. 2.) Power on the camera then power it back off and then back on before the SD light flashes. You get about a second, maybe two to do this.
o. ISO sometimes gets stuck.  Battery pull fixes.


Keep In Mind
o. When taking out the memory card, watch that your other hand, holding the camera, isn't hitting the power on/off switch.  Possible corruption issues if you remove/insert card during power on/off cycle.
o. The camera won't go into "Crop Mode" unless the top dial in on Movie mode.




This page URL: http://www.magiclantern.fm/forum/index.php?topic=3648.msg73630#msg73630
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on September 05, 2013, 11:05:08 PM
It's 4 dark, 4 bright...

(or "every other line" means that in English?)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 11:07:19 PM
The pattern says dBdB when opened... thats where I got that from.
Title: Re: Tragic Lantern for EOS M
Post by: a1ex on September 05, 2013, 11:09:02 PM
Well, that groups pixels by 4, so it can't detect stuff that repeat every 8 lines. I thought you zoomed in.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 11:14:59 PM
It looked like every other line when I zoomed in but I didn't count. :(
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 05, 2013, 11:18:06 PM

KNOWN ISSUES THAT MY REQUIRE RE-INSTALL

o. Shutter-bug Issue with 18-55mm M STM lens
o. Potential ML corruption from changing lenses.

This page URL: http://www.magiclantern.fm/forum/index.php?topic=3648.msg73630#msg73630

You mean this can fix the 18-55 efm bug!!?
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 11:23:00 PM
You mean this can fix the 18-55 efm bug!!?

Thanks, went up and made clearer I hope.  I only know what I read about that bug.  I only have the potential lens-change issue.  Even there, not sure what's up.
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on September 05, 2013, 11:35:02 PM
thanks for the replies 1% and a1ex. Really impressive work. I skimmed the white paper on the dual_iso capture and I'm very excited to try for myself! Thanks again

the tragic-lantern sources are broken for me as of this afternoon:
Code: [Select]
make -C  ../modules/raw_rec
[ README   ]   module_strings.h
[ CC       ]   raw_rec.o
In file included from ../../src/module.h:276:0,
                 from raw_rec.c:58:
./module_strings.h:8:34: warning: missing terminating " character [enabled by default]
./module_strings.h:9:81: warning: missing terminating " character [enabled by default]
./module_strings.h:12:0: error: unterminated argument list invoking macro "MODULE_STRING"
./module_strings.h:8:5: error: 'MODULE_STRING' undeclared here (not in a function)
In file included from ../../src/compiler.h:59:0,
                 from ../../src/dryos.h:34,
                 from raw_rec.c:59:
../../src/arm-mcr.h:29:1: error: expected '}' before 'asm'
make[1]: *** [raw_rec.o] Error 1
make: *** [raw_rec] Error 2

incase you guys need another sample file, here is my shameless promotion of my photography: http://www.bot-fly.com/DUAL_headphones.CR2

this is from dual_iso module compiled yesterday sometime

EDIT: it works! WOOOHOOO:

██ [ cr2hdr-1 ] [ 17:35:43 ]
██ wine cr2hdr.exe DUAL0005.CR2

Input file     : DUAL0005.CR2
Full size      : 5280 x 3528
Active area    : 5208 x 3476
White level    : 12400
Black borders  : 72 left, 52 top
Black level    : 1991
ISO pattern    : dBBd RGGB
Noise levels   : 8.96 12.51 12.20 9.09 (14-bit)
Estimating ISO difference...
ISO difference : 2.07 EV (419)
Black delta    : -1.37
Interpolation  : mean23-chroma5x5-alias
Dynamic range  : 10.18 (+) 9.70 => 11.77 EV (in theory)
Matching brightness...
Looking for hot/cold pixels...
Full-res reconstruction...
ISO overlap    : 5.1 EV (approx)
Half-res blending...
Chroma filtering...
Building alias map...
Filtering alias map...
Smoothing alias map...
Noise level    : 8.76 (16-bit)
Dynamic range  : 12.21 EV (cooked)
Black adjust   : -10
Output file    : DUAL0005.DNG
File not found.

Not sure about the last line, but it looks like the new module did it!
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 05, 2013, 11:39:06 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 11:42:01 PM
Maz,
I don't know why you press the Play button and then the Menu button in a couple of your steps. I never heard of having to press the Play button first.

Gary

I'm just writing down what I figure out!  Menu would often start RAW recording for me.  I see with the new build Menu goes into Menu!  If I'm missing any documentation please point me to where!  I'm not TRYING to sound like I don't know what I'm doing ;)  You've been a great help!  Please tell me how I can improve that page below so all the knuckleheads like me have a reference point.  THANKS!
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 05, 2013, 11:51:34 PM
INSTALL AND RE-INSTALL OF EOS-M CAMERAS

Thank you 1%, Gary, and others for your help.

STEPS TO REMOVE ML FROM EOS-M

MAKE SURE MANUAL MODE ON...
1. Turn camera on in Photo mode (middle button top dial)
2. Press "Mode" box on touch screen, top, left
3. Press wheel left until you get to 'M' box (manual)
CLEAR SETTINGS...
4. Press MENU key (if old version of ML, press Play first)
5. Move to last wrench on top menu
6. Go to last wrench on right.
7. Scroll down to "Clear all settings" SET
REMOVE ML AUTOBOOT ...
8. Repease Step 2,3; that is, Go back to 'M' Manual mode because it might have changed to default 'CA'
9. MENU, then First Wrench, then Format Card (steps in shorthand now)
10. Then Last wrench, Update Firmware, pick latest viersion, SET (now that card's been formatted, it has no ML so camera will see nothing, and look to revert to factory boot)
11. GREEN ML screen should come up about BOOKDISK flag
12. Rotate dial to Movie mode
13. WHITE ML screen will now say "BOOTDISK flag is DISABLED"
14. Turn Camera Off
15. Format card in computer, ML files will still be on card
16. Turn Camera ON
EOS-M SHOULD BE AS IT CAME FROM FACTORY

RE-INSTALL ML (1% Build)

1. Get latest EOS-M install.  Currently: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/[EOSM]FullbackADTGui.zip
2. Drop the EOSM fir from the zip file
3. Copy autoexec.bin from zip file to card.
4. Copy ML folder to card
5. Camera in 'M' mode, last wrench, update firmware
6. When you have success shut down the camera.
7. Pop the card into your computer and make it bootable with EOScard.
8. Put card back in camera, and start

SOME POTENTIAL ISSUES THAT MAY CORRUPT ML, THEREBY NEEDING A RE-INSTALL.  These may be fixed by the time you read this!

o. Shutter-bug Issue with 18-55mm M STM lens
o. Potential ML corruption from changing lenses.

Stuff To Remember
o. The camera won't go into "Crop Mode" unless the top dial in on Movie mode.



This page URL: http://www.magiclantern.fm/forum/index.php?topic=3648.msg73630#msg73630


Can confirm 18-55mm efm shutter bug remains after trying this.
Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on September 05, 2013, 11:54:43 PM
Using the cr2hdr.exe posted a couple days ago:

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fwww.bot-fly.com%2Ftree_comparison.jpg&hash=9009a6fff3bd6c10a7555541f4eddf09)

not the greatest example, but its working!
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 05, 2013, 11:55:03 PM
Thanks Malakai.  I don't have that lens or problem.  Can you point me to the best reference page, or tell me what the work-around is for now and I'll put it in that page as a work-around?  Or is there none?  Sorry, haven't read those posts deeply as I have problems of my own :)  That said, the new stuff 1% has coded is great!  The red record button now records and menu goes to menu and it just looks cleaner, better.  I was SO CLOSE to quitting today you have no idea! 
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 05, 2013, 11:59:27 PM
Quote
I see with the new build Menu goes into Menu!  If I'm missing any documentation please point me to where!

Menu records raw in photo mode (rec doesn't work there), its a setting in the raw module, you can pick.
Title: Re: Tragic Lantern for EOS M
Post by: Malakai on September 06, 2013, 12:04:53 AM
There are two work arounds, power up, rotate lens to break connection with camera and rotate back. Personally I wouldnt dream of doing this. Risks of shorting etc. Alternatively, power on the camera then power it back off and then back on before the SD light flashes. You get about a second, maybe two to do this.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 12:11:25 AM
Menu records raw in photo mode (rec doesn't work there), its a setting in the raw module, you can pick.

I like what you picked :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 12:22:22 AM
@Gary @Malakai.  I've put in something about the 18-55mm lens above.  Gary, from some of your posts I see you may have had other lens change issues.  If so, can you explain their status, and workaround, if you need one, and I'll put above? 

I don't know why my ML got corrupted.  It may have to do with the lens issue.  I want to be on the lookout for things that corrupt my ML in the future, if it is indeed related to the lens issue, so i/we can give better feedback to 1%.  It doesn't sound like he has the lens so we have to be very specific about what we're experiencing.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 06, 2013, 12:32:29 AM
  Gary, from some of your posts I see you may have had other lens change issues.  If so, can you explain their status, and workaround, if you need one, and I'll put above? 
Max, can you be more specific. I do not recall any. Just the usual 18-55 issue of no pics and the two workarounds of quick off/on and untwist twist. I have had some aperture display settings hang at times, but not recently. And the ISO setting getting stuck to only Auto. Battery pull fixed it.

gary
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 12:40:39 AM
Max, can you be more specific. I do not recall any. Just the usual 18-55 issue of no pics and the two workarounds of quick off/on and untwist twist. I have had some aperture display settings hang at times, but not recently. And the ISO setting getting stuck to only Auto. Battery pull fixed it.

gary

Thanks Gary.  Nothing specific.  Again, don't understand the lens issue and some of posts above so wanted to make sure I know all the current problems.  Please review my page, if you have time, and give other edits.  Thanks!

It looks like the pink dot issue is back for me.  My PDR isn't working.  Tried other files Mixer2 put up for you.  Is PDR working for your crop-mode RAW files?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 06, 2013, 12:50:52 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 06, 2013, 01:39:20 AM
The reason to record in photo mode:

quality jpg, multi shot NR on... ~100MB shoot_malloc... so more frames.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 01:47:27 AM
The reason to record in photo mode:

quality jpg, multi shot NR on... ~100MB shoot_malloc... so more frames.

I'm sorry 1%, totally lost.  record video?  Or you just mean we should take photos too? 
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 06, 2013, 03:23:41 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 06, 2013, 03:33:42 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 06, 2013, 06:12:58 AM
I'm sorry 1%, totally lost.  record video?  Or you just mean we should take photos too?

to record RAW video with more frames (on slow SD cards or even on fast SD cards) dial in to M mode on photo, switch to JPG, press MENU, on the 4th photo options from the left, there is "High ISO speed NR" click it,  choose "multishot noise reduce" click set 2 times and try to record RAW video with greater RAM available.

detailed explanation;

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fimg855.imageshack.us%2Fimg855%2F7630%2Ftyoi.png&hash=39117122f2deac4702968c1e5a2a5e77) (http://imageshack.us/photo/my-images/855/tyoi.png/)

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fimg405.imageshack.us%2Fimg405%2F8191%2Fpof5.png&hash=5902b83770198383f9da918fea2186eb) (http://imageshack.us/photo/my-images/405/pof5.png/)

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fimg23.imageshack.us%2Fimg23%2F5782%2Faatr.png&hash=1c01f641f29f2d3591bea6905c0ac2f0) (http://imageshack.us/photo/my-images/23/aatr.png/)

then you're able to...
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fimg27.imageshack.us%2Fimg27%2F3266%2F4e46.png&hash=f9d01099210780d9834944a8d1424fd3) (http://imageshack.us/photo/my-images/27/4e46.png/)

Title: Re: Tragic Lantern for EOS M
Post by: jerrykil on September 06, 2013, 06:17:29 AM
a1ex,

ur latest experimental commit to TL-6D  modules/readme2modulestrings.py broke my build. my module_strings.h's come out all weird like this:
Code: [Select]
MODULE_STRINGS_START()
    MODULE_STRING("Name", "raw_rec")
    MODULE_STRING("Authors", "g3gg0, a1ex")
    MODULE_STRING("License", "GPL")
    MODULE_STRING("Summary", "Records 14-bit RAW video")
    MODULE_STRING("Description",
    )
    MODULE_STRING("Last update", "usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
            [-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format] (16d145d6507e)")
    MODULE_STRING("Build date", "2013-09-06 03:58:14 UTC")
    MODULE_STRING("Build user", "grey@greybook-9.local")
MODULE_STRINGS_END()

Probably parsing date wrong...i'm on mac


since these were just problems with Darwin's 'date' and the lack of rst2html for mac, i was able to iron out some of the issues by modifying these two lines in modules/readme2modulestrings.py
after installing docutils (http://docutils.sourceforge.net) line 54:

txt=run('cat README.rst | grep -v -E "^:([^:])+:([^:])+$" | /usr/local/share/python/rst2html.py --no-xml-declaration | python ../html2text.py -b 59')

and then the last_change_date variable on line 75:
last_change_date = run("date -ujf '%Y-%m-%d %H:%M:%S %z' \"`hg log . -l 1 --template '{date|isodate}'`\" '+%Y-%m-%d %H:%M:%S %z'")

this ran mac friendly until bolt_rec threw some misc stuff about module_string.h at me that i didn't quite get.

hope this helps
thanks for all the hard work
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 01:34:57 PM
@zuzukasuma  THANKS SO MUCH for your detailed explanation with screen shots.

I tried what you said but can't see any difference between RAW videos shot the normal way and that way.  I also noticed that when I go into video mode, and come back to photo mode "High Speed ISO" is re-set back to standard.

Am I supposed to do anything different in post.  Again, thanks for your instructions.
Title: Re: Tragic Lantern for EOS M
Post by: 1% on September 06, 2013, 03:49:23 PM
Yea, it resets every time you leave photo mode and I'd toggle raw video on/off when changing modes so the indicators are correct... ie histogram,etc.

The readme things I found cool... but then modules went up by a few KB :(
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 04:58:13 PM
Yea, it resets every time you leave photo mode and I'd toggle raw video on/off when changing modes so the indicators are correct... ie histogram,etc.

I see...Changed RAW shooting record to 'MENU' key (so I can shoot RAW in photo mode).  Left RAW shooting on in movie mode.  Went into Photo mode, changed ISO, then pressed MENU and recorded RAW.  Went back to check ISO setting and was still in multi-shot.  Ideas?   Thanks!

BTW Gary, I'm using hit 'play' first to go into Canon Menu again (is there another way) ;)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 06, 2013, 08:16:08 PM
To record RAW video with more frames (on slow SD cards or even on fast SD cards) dial in to M mode on photo, switch to JPG, press MENU, on the 4th photo options from the left, there is "High ISO speed NR" click it,  choose "multishot noise reduce" click set 2 times and try to record RAW video with greater RAM available.

Whoa... More of these memory hacks, please. I just tried this process out and was able to capture 28 frames at 2.5k (2.39) in crop mode. I really feel like it's not going to be long before a revelation permits shooting 2k scope continuous in 24fps. I'm excited!
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 08:25:31 PM
Whoa... More of these memory hacks, please. I just tried this process out and was able to capture 28 frames at 2.5k (2.39) in crop mode. I really feel like it's not going to be long before a revelation permits shooting 2k scope continuous in 24p. I'm excited!

Maybe I don't have the latest module or something?  Anyway, Anthony, can you get close to continuous by lowering your frame rate?
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 06, 2013, 08:33:29 PM
Maybe I don't have the latest module or something?  Anyway, Anthony, can you get close to continuous by lowering your frame rate?

I'm on 1%'s Fullback ADT GUI build. Just tested, and at 2k scope 24fps I can capture 31 frames. If I reduce that to 12fps, capture is indefinitely continuous.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 08:35:18 PM
Just tested, and at 2k scope 24fps I can capture 31 frames. If I reduce that to 12fps, capture is indefinitely continuous.

WOW!  So now I'm a little bit more anxious to get it working on my camera.  Did you install any special module to get that working.  (sorry, see you already said.  Yes, that's what I have).  I followed the procedures above but my RAW files look the same.  What resolution did you pick?  Aspect ratio?
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 06, 2013, 08:37:30 PM
WOW!  So now I'm a little bit more anxious to get it working on my camera.  Did you install any special module to get that working.  I followed the procedures above but my RAW files look the same.  What resolution did you pick?  Aspect ratio?

No special modules, just what's included in 1%'s Fulback ADT GUI package. 2048x856 2.39 aspect, crop mode via 5x magnifying glass. I wish the 2.7x crop mode from the menu worked in photo mode, but as 1% explained earlier, that's just a built-in function they enabled.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 08:45:24 PM
Thanks Anthony!  I didn't see that explanation above.  Didn't realize I had to be in crop mode.  Anyway, did that, and the magnifying glass, can barely wait for it to copy to PC : ) :) :)  WOWZA WOWZA WOZA  2048x856 12fps!

Now if only PDR would start working again.  Here is a still (sorry nothing fancy) from a RAW video shot at 2048x856 2.39 ratio at 12 fps continuous.  THANKS AGAIN FOR YOUR HELP ANTHONY!  (and of course we owe everything to 1%)

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fmaxotics.com%2Fphotos%2FML_2048x856.jpg&hash=c84b9794cf5efa1f9fe55760353e6514)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 06, 2013, 09:00:20 PM
Didn't realize I had to be in crop mode.

The reason crop mode is required for the higher resolutions is because the line-skipped capture takes up most of the sensor. More elbow room in 1:1 mode. Rad image, a question though without digging through the forum if you know right off the cuff: What causes the pink dots?
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 09:08:33 PM
I didn't read it very closely.  Since they don't appear on my 50d, assume they're the pixels that Canon sets aside to do that dual focus thing (STM?), since mirror-less cameras are slow to focus.  I believe the t4i/t5i have a similar problem.  I believe PDR goes to each pixel and takes one next to it, or makes it transparent, don't know.  Did you do your video on an EOS-M.  Just wondering why you haven't wondered about the pink dots.
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 06, 2013, 09:25:02 PM
Just wondering why you haven't wondered about the pink dots.

I've only just experimented, haven't taken any RAW footage through post, so I haven't had to deal with the pink dots yet. Anything I've done for real with this camera has been in h264.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 06, 2013, 09:28:38 PM
@zuzukasuma  THANKS SO MUCH for your detailed explanation with screen shots.

I tried what you said but can't see any difference between RAW videos shot the normal way and that way.  I also noticed that when I go into video mode, and come back to photo mode "High Speed ISO" is re-set back to standard.

Am I supposed to do anything different in post.  Again, thanks for your instructions.

whats your SD card? I'm using Sandisk Extreme 45MB/s editions and works fine with them, best price/performance cards for RAW video

yeah, it happens, and camera sticks at JPG, you can not change to RAW, if you don't change multishot NR mode to normal.
Title: Re: Tragic Lantern for EOS M
Post by: zuzukasuma on September 06, 2013, 09:31:40 PM
Whoa... More of these memory hacks, please. I just tried this process out and was able to capture 28 frames at 2.5k (2.39) in crop mode. I really feel like it's not going to be long before a revelation permits shooting 2k scope continuous in 24fps. I'm excited!

well, you can always resize footage if you're processing it with After Effects, it can easily resize to 2,5K without serious quality loss on normal shooting mode, I've tried to resize 2,5k to 4k, results, just amazing. but I think I have to get 50D for that stuff.

this is one of the hacks, another hack is HDR mode hack, which can give the same buffer but unfortunately you loose all the controls over exposure
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 06, 2013, 10:05:40 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 10:13:56 PM
These are the steps

o. Naturally, you're in 'M'anual mode
1. Set to RAW 2048x, 2.39 and 12 fps (settings Anthony suggested, assume you can try others too)
2. Make sure record is set to 'MENU'  As if I have to tell you ;)
3. Go into PHOTO mode (top dial).  Go into Canon Menu, photo file format switch to 'L'; that is Jpeg, not RAW for photos
4. On the 4th photo options from the left, there is "High ISO speed NR" click it,  choose "multishot noise reduce" (farthest option to right)  You will get a message saying it will go back to 'basic' if you change to movie mode, or others, etc.  Just click OK
5. Back to screen, hit the touch-screen Zoom box on lower right until it says 5x Zoom.  You should now see image in crop mode.
6. Hit MENU and it will start recording RAW at above settings.
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 06, 2013, 10:17:16 PM
I understand the process for removing the pink dots, I'm just wondering why they occur in the first place. A correction to something I said earlier: If I have Multi Shot Noise Reduction enabled, and am in photo mode using the 5x magnifying glass crop mode, I can capture 58-60 frames of 2048/2.39 footage at 24fps. When I said 31 frames earlier, I think MSNR turned itself off after a reboot. 2 1/2 seconds of 2k raw is definitely getting somewhere.

@1% - What's the possibility of replicating whatever happens to memory allocation when MSNR is enabled and creating a dedicated function in video mode that just does that... only more so?
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 06, 2013, 10:32:23 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 06, 2013, 10:46:46 PM
Max, I understand everything after step 2.
Step 0- where? Manual mode in photo mode or video mode top dial?
Step 1- set Raw 2048, 2.39 how and where? If i do that in movie (top dial) in the movie menu raw sub menu, it always goes back to 1728 rez. ?? 12 fps how and where? Using FPS Overide?

Sorry for not understanding. I am a video guy and I never really do any of the photo mode stuff.
Gary

I'm thrilled I'm not the only one needing help around here;)  The issue is that the "High ISO" setting reverts if you go into movie mode.  So you need to set up how you want RAW recorded in movie mode (that is the MENU button for record), then go into Photo mode, change to High ISO, then record RAW video by pressing MENU in Photo mode.  When you go back into movie mode the High ISO setting will revert back to basic on its own.    I take it the devs haven't figure out how to keep the High ISO setting to say where it is, in movie mode, or to stop it from reverting when you twist the dial to movie mode.  Hope that explains it.  Another way of saying it is, once you set High ISO in photo mode it will forget it once you go into Movie mode to change anything.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 06, 2013, 10:54:31 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 06, 2013, 11:10:07 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 06, 2013, 11:23:13 PM
Forget about video mode for a second, start your camera in photo mode and do the following:

1. Hit MENU, then in the first tab, change image quality to the highest JPG value (L).
2. Go to the the fourth tab and change High ISO speed NR to Multi Shot Noise Reduction (NR).
3. Hit MENU again to return to LiveVew, then hit INFO until there's a magnifying glass in the lower right. Hit that, until it says 5x.
4. Double touch the screen to enter the ML menu. Make whatever adjustments you need to in the Expo tab.
5. Go to the movie tab and single-touch the screen while FPS override is selected to set your frame rate; I like 24/Exact FPS.
6. Single-touch RAW video to enter the menu. I currently have Resolution set to 2048x856 and Aspect ratio set to 2.39:1.
7. In photo mode, the video record button doesn't seem to do anything, so you have to change Rec Key to MENU.
8. Single-touch then double-touch to return to LiveView. Press MENU to begin recording.

You never have to enter video mode for this process, all takes place in photo mode. That may change in the future, but this is how to take advantage of the extended memory allocation MSNR provides.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 06, 2013, 11:38:42 PM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 06, 2013, 11:54:20 PM
Anthony, thank you. I got it all working as you described. In the 5x crop, I only get about 50 frames and then it stops. I am using your exact settings. When it comes back on without the 5x crop, it records continuous in the normal view.

Besides just for testing purpose, how is this useful being zoomed in so far using 5x crop? Maybe for macro shots but normal stuff like shooting a green screen interview would require the camera to be very far back from the subject to get a useful head to toe shot of a person.

When you leave 5x crop mode, you're shooting resolution automatically drops back down to 1728x434 (maximum), which is why you're able to record continuous that way. The benefit to shooting in crop mode is that pixels on the sensor aren't skipped, and we technically have the whole surface to make use of. The capture pitch is tighter which I assume would make the image sharper, and also reduces/eliminates moire. When you're not in crop mode, the camera skips pixels so more area of the sensor is covered, but as a result it misses information in between.

The zoom is a little annoying in some applications, but won't be an issue when 4 - 5k continuous capture is cracked. I hope the ML team is able to work out some sort of crop mode override that keeps LiveView on the whole sensor with the zoom only happening in the background. Then the capture area could be displayed by the rectangle marker.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 07, 2013, 12:01:27 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 07, 2013, 12:05:23 AM
thank you for getting me up to speed on this area.

NP, I just hope I'm not lying to you. This is all just the way I understand it.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 07, 2013, 12:17:53 AM

The benefit to shooting in crop mode is that pixels on the sensor aren't skipped, and we technically have the whole surface to make use of. The capture pitch is tighter which I assume would make the image sharper, and also reduces/eliminates moire. When you're not in crop mode, the camera skips pixels so more area of the sensor is covered, but as a result it misses information in between.

Yes, once you film something that produces moire (usually something with hard vertical/horizontal lines.  Shelves, stripes on shirts, siding on a house, etc., you'll see why crop mode is the only real fix.  Moire is very difficult, almost impossible to fix in post.  I've concluded that wiith the EOS-M, and even my 50D, unless I shoot in crop-mode I risk getting a lot of moire. 

About getting this to 24fps, I'm a little skeptical.  There's only so much the EOS-M can write to the SD card, about 40MBS. 
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 07, 2013, 12:25:47 AM
Yes, once you film something that produces moire (usually something with hard vertical/horizontal lines.  Shelves, stripes on shirts, siding on a house, etc., you'll see why crop mode is the only real fix.  Moire is very difficult, almost impossible to fix in post.  I've concluded that wiith the EOS-M, and even my 50D, unless I shoot in crop-mode I risk getting a lot of moire. 

About getting this to 24fps, I'm a little skeptical.  There's only so much the EOS-M can write to the SD card, about 40MBS.

I have my fingers crossed that there's some sort of 100MHz/208MHz clock switch hidden somewhere in the SD controller that's yet to be discovered.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 07, 2013, 12:33:29 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 07, 2013, 12:35:50 AM
Lower to 12fps. 
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 07, 2013, 12:36:50 AM
Lower to 12fps.

^this, or wait and pray for new discoveries.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 07, 2013, 12:37:32 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 07, 2013, 12:41:49 AM
You guys are cracking me up! :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 07, 2013, 12:43:12 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 07, 2013, 12:47:29 AM
what else can we do while 1% gets that audio headphone output working?  8)

Live a healty and meaningful life?
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 07, 2013, 12:48:13 AM
While you're waiting HBO to call, what do you know about the PDR?  I put a message on that board.  I've been able to open a DNG from a file that works and a file that doesn't.  They do look different. 

BTW, I like to use PDR on the RAW files straight (instead of on extracted DNGS).  Anyway, don't know how to read/analyze the current DNG and tell PDR where to look for the dot matrix.  It seems the config file has 4 lines of matrix points, any insight?  Thanks!
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 07, 2013, 01:00:53 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 07, 2013, 02:51:02 AM
I know the topic's pretty well covered, but I just wanted to share; I popped a 95/mbps card into my camera, and there's no noticeable sign of improved performance.
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 07, 2013, 03:17:20 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 07, 2013, 03:36:49 AM
What I've read from some people who seem to really understand this stuff, it isn't possible without more powerful IO circuitry on the camera.  Apparently some CF cards have built in IO processors which can relieve the CPU on the camera of some work--why they are much faster.  Even at the current speeds, the camera gets hot and the batteries probably experience shorter lives.  My guess is that if Canon sent these cameras out with ML a certain amount would fail due to the stress ML puts on the system.  I don't think it hurts it if you're careful.  And there are few ML users and not the kind who will be surprised when the battery dies in 20 minutes.  Keep in mind it didn't take many oil spots on Nikon's D600 sensor for buyers to complain to high heaven.  Finally, 1% made a quip about a help module taking up space in the build.  Memory and IO is always in short, short supply :)
Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 07, 2013, 04:15:05 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: eosm1986 on September 07, 2013, 04:42:34 AM
Hi All:

OK - I am thinking I may know why my camera is having such an affinity towards larger apertures.  I thought it might be trying to focus on dust on the lens, etc., - so I bought a cleaning kit to clean that, reseated the lens, no change.  I then flashed back to old firmware.  Still no change.  However, I see a field in the update firmware section that says my lens firmware is 1.8.0.  I'm wondering if when I flashed ML, it changed the lens firmware.  I guess I'm open to the idea that it *should* be using those larger apertures, but it's just such a big change from before when I flashed ML. 

So, I downloaded the current canon firmware - right from website - and flashed it.  No change.  Behavior still the same. 

So what is the most up to date version of lens firmware? 

Help!

Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 07, 2013, 04:57:18 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Canon eos m on September 07, 2013, 06:12:57 AM
Max, I understand everything after step 2.
Step 0- where? Manual mode in photo mode or video mode top dial?
Step 1- set Raw 2048, 2.39 how and where? If i do that in movie (top dial) in the movie menu raw sub menu, it always goes back to 1728 rez. ?? 12 fps how and where? Using FPS Overide?

Sorry for not understanding. I am a video guy and I never really do any of the photo mode stuff.
Gary

Quick questions:

I don't get more than 1728X on 5x mode. I do go higher with 10x mag though.

Any way of focus racking on EOS M.

I am on 1%'s latest hack version.
Title: Re: Tragic Lantern for EOS M
Post by: maxotics on September 07, 2013, 06:19:54 AM
Towards A More Generalized PDR for the EOS-M?

I've been studying this Pink Dot issue.  1% will have to give his take, or someone else who knows more than I, but I believe the RAW files captured by the EOS-M, in video, are not the same RAW files that the camera takes for a photos.  There are just too many dots used for focus, edge detection, whatever Canon needs to read from the sensor to focus the lens.   I now suspect there is no real fix to the pink dot issue. 

I'm going to talk about a 16:9 aspect ratio.  The EOS-M sensor has 5,184 x 2,456 pixels.  Or, in an aspect ratio of 16:9, 5,184 x 2,903 pixels.  Because Canon knows they will down-sample the images to 1920 x 1080p, they have 3,264 pixels wide they can either discard or average down.  They can do the same for 1,823 pixels high. 

In order to illustrate this I did some graphics.  Here's a graphic showing the relative size of the sensor, to the size of the frame it will save as video in 16:9

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fmaxotics.com%2Fimages%2Fsensorcompare.jpg&hash=a5c00f18db80aebef92d03006294817a)

Do you see any focus dots in that box?  No.  But they were there in the graphic before I shrunk it down.  Here is that file at the same relative size of the sensor.  This optical trick demonstrates how Canon can use all these pixels for focus without them ending up as pink dots in their videos.

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fmaxotics.com%2Fimages%2F1280x720FocxPixelsBlownUpToSensorSize.jpg&hash=5b6bdcf20df29a350a80a65b6254cce7)

And here again, are the pixels, used for focusing, at 100% size on my monitor

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fmaxotics.com%2Fimages%2FFocusDotsAtMonitorResolution.jpg&hash=b9f9395e091ec79fcc89bb5a5484f9e2)

And here they are, blown up to 800%

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fmaxotics.com%2Fimages%2FFocusDots800Percent.jpg&hash=0c26aacb216cfd5260adbad4b2aba9af)

As you can see, on a pixel level, there isn't just one pixel used for focusing.  There are clusters of pixels, a few pixels wide.

Again, after the camera down-samples all these pixels in video mode you don't notice them.

My guess is that in photo mode they shoot one of these pixels-used-to-focus frames, focus, then chuck it out and do another frame where each pixel acquires only image data.  1% your thoughts?

If I look at any frame that went through PDR effectively, I can still see many of these focus pixels, especially at any hard edges where colors make abrupt changes.  They blend out in any set of 50 pixels, say, that are generally the same color.  In short, these RAW movies are made using a large number of focus-debug sensor data from the camera.

Now, I'd rather have a high dynamic range image at 1280x720, with lots of noise/blurred color information, but I believe these essentially heavily masked video frames on the EOS-M, and other similar Canon cameras, will prevent them from reaching the same IQ as the Black Magic cameras.

From what I understand the black magic cameras, because they are reading from the WHOLE sensor, have more room to down-sample their image efficiently.  With the EOS-M, to get moire-less footage, you need to use a very SMALL PART of the sensor, 1280x720 pixels to be exact.  There are no extra pixels to throw out.  Each pixel that is used to focus, and there are many of them in that block,  are there, degrading the image.

If all this is true, the Pink Dot remover will never be able to completely remove the residue of focus pixels.  And if that's true, a simpler dots/spots average algorithm might be better.  (This whole post is the result of my PDR no longer working on my videos.  I have a feeling something changed in RAW output from the developer's new work.)

Another benefit of a different PDR is it could potentially post-process the moire issues away from the camera. Moire makes it imperative one use crop mode on the EOS-M, which means you can never get a very good wide angle shot.  I think 10mm ( or 16mm x 3) or 48mm effective is the lowest you can go.  If someone could "hide" pink dots and fix moire patterns in non-crop mode than the camera's 22mm pancake would make it quit nice.

Anyway, I look forward to the dev's take on this.  Maybe the way to go is higher dynamic range h.264 through HDR or the multi-shot ISO feature, which I've been trying out.   Has RAW reached it's limit on the EOS-M?


Title: Re: Tragic Lantern for EOS M
Post by: gary2013 on September 07, 2013, 07:05:40 AM
 :)
Title: Re: Tragic Lantern for EOS M
Post by: Rewind on September 07, 2013, 07:38:01 AM
Quote
As you can see, on a pixel level, there isn't just one pixel used for focusing.  There are clusters of pixels, a few pixels wide.

What you see in your example is interpolated bayer pattern, that's why you think it's 'clusters'.
In order to see actual af dots locations, you have to use some soft which gives you apportunity to see actual bayer pattern, Photivo for example.
Then, you average a dozen of these shots to avoid noise, and finally you can get the actual af dots locations. A picture like this: (https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fipic.su%2Fimg%2Fimg7%2Ffs%2Fkiss_13kb.1378531962.jpg&hash=05eb4e3b881e51ccd72ffc52c25dbd38)
What PDR is doing, it applies a smart adaptive interpolation for the af dot pixels.
It does not working for crop modes anymore because of something changed in crop mode centering in latest builds, so we have to change dot data files.
Just for your information.
Title: Re: Tragic Lantern for EOS M
Post by: AnthonyEngelken on September 07, 2013, 10:52:28 AM
What PDR is doing, it applies