I moved some of the great work 1% did to get ML functioning on the EOSM for firmware 2.02 back into the main ML code base. I'm sure its missing some features and bugs from it's TL counterpart, but if you are interested in testing ML and helping make it stable and in sync with the code for other ML cameras for all base features, please comment here and I'll do my best to port 1%s bugfixes, or to test, create issues for new bugs and attempt to solve. IMO, the main focus is ensuring all basic ML functions work well before branching out to things like raw video.
The nightly build is now available here:
http://builds.magiclantern.fm/#/
(I have not tried the nightly yet, but my own local compile from a few nights ago works for me)
How you make it? Video? :)
However, I just discovered the H.264 recording at 3X zoom. And wow! This feature alone makes this release worth a million bucks.
How you make it? Video? :)
How you make it? Video? :)There is a setting under the video tab in the ML menu that lets you turn on/off the 3x crop. This uses the center area of the sensor and gets rid of moire and aliasing. With the 22mm lens, this feature gives you a lot of flexibility to get semi-wide and close up shots in a small package.
There is a setting under the video tab in the ML menu that lets you turn on/off the 3x crop. This uses the center area of the sensor and gets rid of moire and aliasing. With the 22mm lens, this feature gives you a lot of flexibility to get semi-wide and close up shots in a small package.I believe it also gets rid of aliasing and moire since it is not using line skipping algorithms.
it would be good to have the audio return to it's ON state after shooting raw and then going back to shooting H264. Raw disables the sound, so enable the audio when we disable the raw settings to go back to H264.Thanks, I think this was an issue on TL as well. I will add it to the list.
Fix the red box temp settings. I have posted before that it is definitely incorrect saying it is Centigrade. It should be down to around 30C and my M is always showing around 100C more or less even when I first turn it on.Yes, I think there might be more than just changing C to F going on. My camera has shown temps of 100C after just turning on in a cool room, and the camera is very cool to the touch. I will add this as well.
I have tested the latest release of the EOS ML firmware. There are quite a few bugs and some features do not seem to be active yet. Dual ISO/ ETTR need some working on.I think ETTR hints on the menu are correct, but the actual feature isn't correct. I have not tried dual ISO on any camera, so I can't speak to that, but again, my focus is weird menu things, audio/video features before working on dual ISO, raw, etc.
The pink dots while RAW recording are still seen. RAW video replay does not work.
However, I just discovered the H.264 recording at 3X zoom. And wow! This feature alone makes this release worth a million bucks.
thanx Jordan. The display for the shutter seems strange with all the numbers and letters. Can we get the normal 1/48 and so on back? Headphone does not work. I did record some raw at 720p24, but I don't think it is MLV. There was no playback of the file in the File Manager section like before.
I forgot to say the shutter "menu settings", not the main display screen.
I'll look into the shutter display. I never tried it, but I don't think headphone was ever working, even on TL.
I moved some of the great work 1% did to get ML functioning on the EOSM for firmware 2.02 back into the main ML code base. I'm sure its missing some features and bugs from it's TL counterpart, but if you are interested in testing ML and helping make it stable and in sync with the code for other ML cameras for all base features, please comment here and I'll do my best to port 1%s bugfixes, or to test, create issues for new bugs and attempt to solve. IMO, the main focus is ensuring all basic ML functions work well before branching out to things like raw video.
The nightly build is now available here:
http://builds.magiclantern.fm/#/
(I have not tried the nightly yet, but my own local compile from a few nights ago works for me)
No, I'm not sure I've seen any steps to reproduce it, and I haven't experienced it myself.
Did you figure out the shutter bug?
I forgot to say the shutter "menu settings", not the main display screen.Yeah, the menu settings are really weird, I will look into fixing it. As a work around you can see what the actual shutter value is by pressing set while on the shutter menu to hide the rest of the menu options and looking at bottom ML bar.
No, I'm not sure I've seen any steps to reproduce it, and I haven't experienced it myself.I still have the shutter bug but I have a workaround that I explained before in detail. Basically, I have to do a second format in the Canon menu keeping the ML files on the card. The downside is I lose my 8gb exfat format because Canon turns it back to the 4gb format. If I try a new exfat format on my computer, as soon as I put the card back in the camera, it makes me do a new fir install and then the shutter bug is back. So, I still hope the shutterbug gets fixed so I can use my camera with an exfat format for 8gb recordings. 8gb helps for doing interviews.
140mb/s is 140/8 = 17.5mB/s. Raw video requires a lot of speed.
Its compressed video, maybe slowed down by ACTUAL processing - who would imagine?
So what card? M only has a 40mBps SD writer, my card is a 60mBps card, so How much is required ? Plz answer the question, not show math skills !! ;)
I played around with the 12/31 build for a while. While continuous raw recording at 720p worked pretty consistently in TL, with this build, I couldn't get a raw recording more than a few seconds.
What card did you use for 720p in TL?
You only need a 45 or 60 mB/s card because as you stated the writer is only capable of 40mB/s.
On the other hand that h264 video was probably in megabits not megabytes and hence it was 17.5 megabytes per second.
I am now trying the new ML, Jan 5, for the M 2.02 and it makes the shutterbug come back on my cam. When I use any of the TL versions, I do not have the shutterbug (after I do my reformat workaround that I explained a few times so far on here).
PS: Now the question is, is it worth the huge trouble processing raw 720p when the world wants 2kHD or even 4kHD !? Especially considering the ability to get high bit rate compressed H.264, would anyone notice the diff for a huge amount of situations? Maybe only for high ISO situs?Not really. 720 will still look good as most people viewing your work (if it is meant for web) won't even bother to put it in fullscreen on their tiny laptop monitors. I've put more than a few hours into trying to develop a raw workflow to even do a simple 1-2 minute project shooting around town, and the results of my simple comparison tests don't show enough difference to warrant all the extra effort. After the basic stability/usability features get sorted, there is no reason not to push the camera to its limit, but for me, the EOSM is a great tiny camera that I can keep on me to get good video with minimal fuss, and stock h264 really is good enough for most simple doc pickup shots (again, for web delivery). If anyone really needs raw on the cheap and it's non-negotioable, they should pick up one of the BMD cameras.
IIRC, the person porting TL to ML was mostly concerned with 'picture taking' changes to TL, NOT video. So this is of importance to him, I think !! I am sure it is not easy getting all the code deltas correct, assuming his tools are not so great, shame there is not a 'versioning' code repository to keep each code 'effort/changes' independent by 1% & others.Acutally, I'm mainly a video guy, so smooth operation of things like zebras, rec picstyle, and basic audio meters are my main concern. I do use the eosm for photos a lot too, but I haven't experienced the shuterbug, if someone can give me steps to recreate it, I can try to find a fix.
Acutally, I'm mainly a video guy, so smooth operation of things like zebras, rec picstyle, and basic audio meters are my main concern. I do use the eosm for photos a lot too, but I haven't experienced the shuterbug, if someone can give me steps to recreate it, I can try to find a fix.The shutterbug appears when you use the EFM 18-55 lens oin the M with ML. After you turn on the camera in Movie mode, try to take a pic pushing the shutter button and nothing happens. Three workarounds- power off and on real quick before the red led flashes, untwist the lens slightly and then twist back on and reformat using the Canon menu choosing to KEEP the ML files intact and then always having a 4gb record cycle instead of 6gb using exfat. all three work for me. But the shutterbug only relates to The M with the EFM lenses. And some people have different experiences with it, but very similar.
After porting, it's been working well enough for me to use for small family photos and videos, but haven't used it on a real project yet. I've been pretty busy this past week, but my short list of bugs to look at next:
-shutter speed display in menu
-canon menus overlaying ML menu bugs
-bug I'm experiencing with it hanging every few startups
alright, thanks! this will take a while, i still need to buy one.. once i know I ll share...I am selling my M system if you want to buy one. I never used it out my my house, so still very brand new condition. I bought it all last mid July.
The shutterbug appears when you use the EFM 18-55 lens oin the M with ML. After you turn on the camera in Movie mode, try to take a pic pushing the shutter button and nothing happens. Three workarounds- power off and on real quick before the red led flashes, untwist the lens slightly and then twist back on and reformat using the Canon menu choosing to KEEP the ML files intact and then always having a 4gb record cycle instead of 6gb using exfat. all three work for me. But the shutterbug only relates to The M with the EFM lenses. And some people have different experiences with it, but very similar.Strange, I have the 22 EFM and haven't seen it. Can anybody confirm this happens with the 22 or 11-whatever wide angle lens too?
Gary
Where is build version for Eos? It's disappeared!!http://www.magiclantern.fm/forum/index.php?topic=3072.msg97344;topicseen#msg97344
We are looking for volunteers to do testing of the ML and TL ports for the EOSM to see what's needed to put it on track.FTR, I have been doing this on a daily basis since July 2013 with ML/TL on my M.
Send me a PM if you are willing to cooperate. No development skills needed, just some free time to do boring tests
Does the EOS M use the "Stable Release: v2.3" or is there another version I would need. It doesn't appear to be n the "drop down" list.I have used all ML and TL builds on a daily basis without any problems. They just reemoved the M from the ML drop list but they are still developing it as well as 1% on TL. nano has asked for people to test the ML build which I just joined. You can get TL here-
I really only need the Intervalometer. I'm am currently using it on me 550, but want a lighter camera.
Thanks,
Gary in Salisbury, MD , USA
We are looking for volunteers to do testing of the ML and TL ports for the EOSM to see what's needed to put it on track.
Send me a PM if you are willing to cooperate. No development skills needed, just some free time to do boring tests
The shutterbug appears when you use the EFM 18-55 lens oin the M with ML.
No development skills needed, just some free time to do boring tests
Also with the 11-22 EFM lens. Got it three times in a row, even after removing battery - maybe should have left battery out for longer?pulling the battery has nothing to do with it.
After porting, it's been working well enough for me to use for small family photos and videos, but haven't used it on a real project yet. I've been pretty busy this past week, but my short list of bugs to look at next:
-shutter speed display in menu
-canon menus overlaying ML menu bugs
-bug I'm experiencing with it hanging every few startups
How do you stop ML from loading on the M. With the t3i i just hold down the set button as it boots, but that didn't seem to work. I did get the intervalometer to work just fine. Thanks!!
As far as I know there is no way to stop ML from loading - you have to uninstal ML or better use 2 cards. One with ML and one without.
But I agree that it is a good idea if this function would be there one day.
On other cameras you can hold the set button and turn on the camera to disable ML to load, but that doesn't seem to be implemented in EOS-M
Should be in one of the next nightly, and the button to hold is INFO on the Mwhich nightly build? ML, TL or both?
I'd rather not have any more politics of the development situation discussed in threads all over the forum.
Suffice to say.
Tragic Lantern is a personal fork. Just like you, me, and everyone else is capable of creating our own personal forks.
This forum is for the support of Magic Lantern. First and foremost.
[...]
Rather then speculating, and worrying about things that do not improvement the development progress.
- Fork the ML repository (https://bitbucket.org/hudson/magic-lantern/overview), fix some bugs and create some pull requests. (http://www.magiclantern.fm/forum/index.php?topic=10774.0)
- Browse the Tragic Lantern (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/all) repository, and back port fixes and features.
- If you do not know how to code, there are ways to help (http://www.magiclantern.fm/forum/index.php?topic=9516.0) the development team that do not involve coding.
Regards.
which nightly build? ML, TL or both?ML only for now, but I'm sure it'll find its way into TL someday
Have some screenshots?MY bad. I think I just found it. I accidentally set the wrong thing in the Debug page. I usually set line 2 on to load all modules after a crash and I had line 1 turned on instead which is Disable all modules. :(
Not sure where to look (have a screenshot?)Here is a current screen grab from
Here it shows Built on: 2014-03-15 and the file is named Mar15.
I just tried magiclantern-Nightly.2014Mar16.EOSM202 on my EOSM and it works just fine. What firmware version do you have?I have the latest firmware as far as I know. I am using the fir that always comes with the TL builds.
Can you try renaming the ML folder and then re-extracting the one from the zip?
What modules do you have loaded?I have all the modules loaded, six of them, except arkanoid. I just tried shutting off all modules and rebooted and it worked. I powered off and tried to boot again and it went back to the steady red led and hang... battery pull.
Can you try booting without them?
I powered off and tried to boot again and it went back to the steady red led and hang... battery pull.
This was without any module enabled?yes, no modules were loaded. The camera has been sitting for a few minutes and now it powers up with no modules loaded. I tried three times in a row and all three times it powers up with no modules.
(it's important for narrowing down)
Normally, the first key press / scrollwheel / whatever should disable the screen right away (at least this is how it works on all other cameras).The new magiclantern-Nightly.2014Mar17.EOSM202 works now on the M. The splash also goes away with a single push on the set button. I don't understand the shutter display in the ML display. It says 0.-1, -1818 ?? What happened to the usual 1/48 and 1/64 and so on like the Canon menus show and the TL versions? How do we get the shutter to go to the usual settings for video? I had to go into the Canon menus to set it to 1/50 and 1/60 as needed.
For anyone who can reproduce the issue and has basic command-line skills: can you run hg bisect to find the buggy changeset?
Well... one has to double-check FRAME_SHUTTER_TIMER and get_current_shutter_reciprocal_x1000.sorry, I just do not understand it. I never had to do math to set the shutter speed for video. I tried making the shutter adjustments and nothing seemed to be changing except the picture display was getting darker. When I checked in the Canon display, it was up over 200 yet the ML display kept showing 0". Is this method something more that still photographers need? Can this be something that could be a user pref setting so we all can choose what method we need? Can anyone tell me why TL is showing the 1/48 and 1/64 and Canon shows settings like 1/50, 1/60 and so on? Is there something wrong with the TL and Canon way of displaying shutter speed that will ruin our video footage? We need to set the shutter in video to be double the frame rate most of the time.
There is a big quirk here from Canon (all other cameras are well-behaved): EOS-M does not configure LiveView with the real shutter speed while not recording (so the readings will be only relevant while recording). Same for FPS.
So, for standby, one might want to rely on APEX units. Also, if one can't figure out how to fix the bug, just undefine FRAME_SHUTTER_TIMER (don't leave the wrong value) and the code will fallback to APEX (which is portable, but not very exact - Canon does some unusual rounding and ML doesn't copy it - and the APEX method doesn't account for FPS override, for example, but it's easy to fix).
In photo mode, you can set exposure time of 100 seconds?! are you sure about that?
Can anyone tell me why TL is showing the 1/48 and 1/64 and Canon shows more settings like 1/50, 1/60 and so on?Sounds like they use the APEX method.
I also do not understand why it is 1/64 when we need it to be 1/60 for 30 FPS videoYou already quoted the answer. We are talking about ML *displayed* values (that is, just printing what Canon gives us).
Canon actually does this rounding for you, and ML is supposed to print it properly (but somebody needs to sit down and fix it somehow on the M).I understand, thank you for explaining it for me. I wish I could help more on the dev end as you say someone still needs to fix it for the M.
I prefer the correct values being printed in ML. If I want to know what the Canon rounded values are, I look at the Canon feedback.That is what I have been doing, using the Canon menu for shutter setting.
Fps override + raw. Also can do silent pics.
Sorry this is a totally noob question, but where do I find the download that actually has the .fir file for the EOS M? I have the nightly build, but the 2.3 release doesn't have it. . . Thanks ahead for help.http://tl.bot-fly.com/.
I think ETTR hints on the menu are correct, but the actual feature isn't correct. I have not tried dual ISO on any camera, so I can't speak to that, but again, my focus is weird menu things, audio/video features before working on dual ISO, raw, etc.
Pink dots are just what this camera does from hardware, the pink dot remover will take care of that. Raw playback was working (slowly) on TL, so when I get to working on that, it shouldn't be too bad to pull over.
I tested on the nightly build (2014mar27) to try the dual ISO feature. I saw an error message: "ISOLess PH Err (15)". Does "dual ISO" work for EOS-M or not yet available?
I tested on the nightly build (2014mar27) to try the dual ISO feature. I saw an error message: "ISOLess PH Err (15)". Does "dual ISO" work for EOS-M or not yet available?
The next nightly build will have the eosm installer (fir). Put in on the card along all the other ML files, run it once and you'll have both the card and the camera bootable. It also doubles as an un installer should you need it.Thanks for the info nanomad!
The current dual iso implementation assumes a constant address in memory for the iso registers, which isn't true for all digic v cameras.This nightly build Apr09 still shows the same error for dual iso.
I'll post a build later today with a different address location that may help.
I have been using ML version from about 4-2-14. I don't have the exact figures, but I noticed that when using the camera with a non ML card my auto focus has changed. It seems that continuous focus works but if it is disabled it will not focus with a touch of the screen only a press of the shutter. I always thought it was fun to just touch an object on the screen and watch it focus. I'm bummed. Anyone else have this problem?
Any feedback on the newest (4-13-14) version?
Amazing :P the shutter bug doesn't seem to appear with 11-22mm either and the last nightly.
A question, i found this nowhere: When i set ExpSim to ON, there is this group of bars on the top line beside the time. What is the exact meaning of those bars? (some are full white, some are half white, one is yellow, i can get one red [overexposed i think])It's the "Histobar": http://www.magiclantern.fm/forum/index.php?topic=8539.msg80619#msg80619
Is there any version in the past that had audio recording enabled ? Currently from what i see you cant record sound at all if you install magic lantern, i think its worth to leave original canon with sound on untill its fixed
Hi,
I've a problem: Since I've installed ML on my Canon EOS M, I cannont shoot photos, in any mode. It's still focusing when pressing half-shutter, but doesn't take a picture when pressing it through.
I just got canon M today and its great with unlocked crop zoom in video, i can also mount any lens i want on it and use speed booster wich i already modified for M :D
Hi 2blackbar, which speed booster did you modify, and how? :-)
+1000!
... and please post some shots!
Class 6 card is too slow now for magic lantern? My recording stops itself after a couple seconds depends how complicated scene is.
06:50 < kur1j> am I crazy or does the EOSM version of magic lantern not support focus confirmation in the "Magic Zoom"?
Re. Atomos Ninja2 and EOS M.
I am soon a lucky Atomos Ninja2 owner, intended for my future 5DM3, but for learning purposes I will use it on the 60D. and... my M. My question is - will I be able to keep the M screen with ML live while feeding the HDMI output?
Anyone have an answer if ML iso 160,320,640..etc.. can be switched quickly from the rotary button when I have a eye loupe covering the touch screen?
Eos M starts without ml card and can be used without ml card. But remember to switch overlays etc on, otherwise you don't see it.
NSTUB(FF555B80, StartPlayProtectGuideApp)
NSTUB(FF5557BC, StopPlayProtectGuideApp)
NSTUB(FF4E5E2C, MirrorDisplay)
NSTUB(FF4E5E8C, NormalDisplay)
NSTUB(FF4E5E5C, ReverseDisplay)
NSTUB(FF2C17B8, EngDrvOut)
NSTUB(FF0D7918, gui_change_shoot_type_post) ; or is it FF0D7904 ?
NSTUB(FF0D7830, gui_change_mode)
NSTUB(FF1B524C, GUI_SetLvMode)
NSTUB(FF134A8C, SetAudioVolumeIn)
NSTUB(FF2C0474, mvrSetFullHDOptSize)
NSTUB(FF2C0658, mvrSetGopOptSizeFULLHD)
not sure if this is the right window but how possible is 4k h.264 video on the eos m :D
curious as to how come, ml can over ride the FPS and compression of H.264For a complete technical description, have a look at fps-engio.c (https://bitbucket.org/dmilligan/magic-lantern/src/10205a6547dc384c9d143fe016b6165de7b63f52/src/fps-engio.c?at=unified) and bitrate.c (https://bitbucket.org/dmilligan/magic-lantern/src/10205a6547dc384c9d143fe016b6165de7b63f52/src/bitrate.c?at=unified).
I cannot get the camera to stop taking shots in the Intervalometer mode:
Am I doing something wrong? ::)
Hello Guys,
I neewbie on this, and today i finally received my canon eos m (still waiting for the 22mm f2 lens), and after a few experiments with a Pentax M 50mm F1.7, i already noticed that i will have a new toy to play with. Already installed ML (5jun14 nightly) andone thing that i would like to ask, is if it is normal that no Audio Functions are available on ML Menu.
Besides this, does someone recommend a getting started path do HDLSR and ML?
Many thanks, and keep the good work going.
Which build includes headphone monitoring? Does it work any good?
At least in this video there is a build including that submenu:
http://youtu.be/1cHtl0nseEc?t=53s
Tried with latest nightly build, there wasnt that submenu. Btw which one is the most stable release with headphone monitoring and cropvideo?
I don't need raw video, too much hassle with pink dot issues and all.
There are no audio functions. Eos M lacks of audio controls. I don't know but i'm using TL build and there is headphone monitoring. I don't know is it working or not. I bought zoom h1 and now I have proper preamps etc.
OK, thank you! :)
Where can I download the latest TL build(can you put a direct link to the download)?
Is the installation process same as with the ML?
http://tl.bot-fly.comThank you for the help! :)
It is the same. But I dont know is there any new features in later builds.
You can stop the intervalometer by rotating the mode dial, by pressing MENU or PLAY, or by turning off the cameraHi,
When I compare the two videos in my mind the ML video much look better? In fact I see very little difference.AFAIK H.264 encoding is done by hardware.
The video on the ML camera has a *.MOV file much larger then the standard EOS (which is understandable).Well, I don't understand that one. Maybe dev team is able to shed some light on this.
Hi all ML'ers.
I am using ML for focus helping in foto/video- and crop in video with old Konica lenses. I was wondering if anyone had the 11-22 yet and how the shutterbug showed itself or not?
ok thank i did find the thread reporting this issue :
http://www.magiclantern.fm/forum/index.php?topic=8347.0
for me the twist lens works....but annoying solution...
thanks
Also I think when what your filming has moving objects it makes more of a difference.
What is the, video out put on the eos m,
Hi, all. Some how I can't confirm it by googling it: does EOS-M record RAW video in 3x crop mode only? And it has PDAF pixel problem?
Thanks all.
Thanks.
For the PDAF pixel problem, I mean those pixel will show up in the RAW video like a hot pixel and requires clean up.
I have my eos-m running the latest nightly. Trying to figure out how to enable audio to run out through usb. Is there an option buried in the menu, or is the audio functions tab a work in progress?
I wonder....
After using the ML lightly for some time on the 60d and M, my M suddenly showed all (almost) the ML menues on one page as selectable box images - this during one of my hectic 5 second sessions fighting against the shortlived menu.
But since I have no clue to why I got the one page menu, I can not get back to the full one. The boxed onepage is not complete.
Could one of you help a lost one, please?
What ML settings should I look at (change) to get the "best" video out of my EOS M using the 22mm lens?? Regards and tx for the fantastic work!!
Movie crop mode makes for less noise and other weird stuff by just using the middle of the sensor.It increases noise. It is true, I have tested it. Crop mode reduces aliasing and moire. because there is no lineskipping.
Bitrate doesn't really change anything on the EOS M. FPS Override may be useful, but it disables sound. Movie crop mode makes for less noise and other weird stuff by just using the middle of the sensor.
Of course, you can experiment with RAW video, but for that you should check out the subforum dedicated to it.
It increases noise. It is true, I have tested it. Crop mode reduces aliasing and moire. because there is no lineskipping.
It means the FPS timer limits are wrong. Find out the safe values by changing the timers manually, and I'll update them.
I had a 4.1 Gb h.264 file come out of my eos-m as a .dat file today?
I've read something about this coming from going over 4 gb, or something I may not have had set right?
Anyway, can that file be retrieved, salvaged, or is it toast?
Thanks.
I'm surprised to not see more people complaining about this - is there something wrong with my camera / build?
Shutter Bug, all 12 pages
http://www.magiclantern.fm/forum/index.php?topic=8347.msg95683#msg95683
Stedda, thanks for helping out the n00b! Glad to know that I'm not going crazy.
...maybe try the lens twisting workaround.
use speed booster wich i already modified for M :D
The nightly build is now available here:
http://builds.magiclantern.fm/#/
Installation:
1) Format the card from the camera.
2) Make sure you are running Canon firmware 2.0.2 (http://pel.hu/down/eosm-v202-win.zip).
3) Copy ML files on the card and run Firmware Update.
Uninstallation:
1) Run Firmware Update from your ML card.
2) Follow the instructions.
(http://a1ex.magiclantern.fm/bleeding-edge/new-installer.png)
Please, can anyone explain why I cannot reach the menu?
I've installed ML like shown on youtube.
Pressing 'info' button shows me ML interface. As I could see in videos, when I tap screen with two fingers, the menu should appear. But I see a text instead:
"Magic Lantern
This is a development snapshot for testing purposes
..."
What's wrong?
I do not see increased noise, actually next to none, but then I use higher bit rates, usually 2.0x CBR. 1 example of this was taking a still of the same shot of same scene of crop vid, the video was much better in shadows (details & low noise) and less geometric distortion.
Hi guys, I just installed a nightly build from a couple days ago (2014Jul10). The few enhancements that I've tried are working great. My main uses are Focus Peaking and Magic Zoom - to aid in manually focusing my legacy lenses.
Question(s): Is there only a single setting for Focus Peak at this time? It seems that I can either have the featured disabled (OFF) or enabled (ON,0.5,local). Is their some way to tweak/customize the settings and be able to cycle through those settings with a button press? Same for Magic Zoom - can the magnified window be re-positioned to other areas on the screen?
thanks in advance!
You can get to submenus by tapping the screen.
THANK YOU!!!
...just focuses but won't fire with a full press.Hey, welcome!
Any ideas?
Using a sdcard without ML it works fine.
I can post dumps/logs later when I get home.
Or report the bug...
https://bitbucket.org/hudson/magic-lantern/issues?q=eos-m
You have to load RAW_REC.MO or MLV_REC.MO first. See Module tab.
Movie tab
Just noticed the EOS-M build was missing some modules
Tried with my EOS-M, no problems, all modules loading perfectly.
The "ML menu dissapearing after 5-7 sec." bug is still present.
Find out Canon values for this custom function, as returned by cfn_get_af_button_assignment(), then I'll tell you which one to use.thx for the reply a1ex. so cfn_get_af_button_assignment() is returning appropriate values from the C.Fn menu. Here is a screenie from the menu:
whenever I try to burn me video ML raw red dots appear on the images someone been the same
http://es.zimagez.com/zimage/capturadepantalla2014-08-12alas125742.php
Is there any way to shoot in continuous mode to get handheld bracketing to be a possibility?
edit: tried to set PROP_AEB past 16 and it gave me an error sayin it wasnts 2 bytes, oh well...
And I found intervalometer bug. If used MAKE PICTURE for start the last picture made by intervalometer activates next intervalometer loop. Camera makes photos infinity...
We should make a sticky at the top of this thread about the "shutter bug"... since half of this thread is people asking the same question.
Greg did some research here: http://www.magiclantern.fm/forum/index.php?topic=8535.0Great thread. Apologize I couldn't find it on my own. I will play with this code and see if it works on EOSM.
but I could only get it working on 500D. I should probably revisit it, since others also confirmed it on 550D and 600D.
Another way would be with the full-res silent pictures, once we figure out how to use the rolling shutter.This is very interesting and exciting, also. Though, I'm not up to date on those new features...yet.
Wouldn't matter, more than half of all posts are people asking the same covered topics over and over again...Personally, I would like to be able to make multiple searches without having to wait 15 seconds. For example, I was searching for prop_aeb and continuous hdr, but was unable to find the fast hdr that greg had posted on. after a few search queries, i grew tired of waiting 15 seconds between each dead end search...
ShutterBugPlease read this thread about the shutter-bug: http://www.magiclantern.fm/forum/index.php?topic=8347.275
I foung solution for me (EOS-M with 18-55 IS STM). Pulling battery out!
If you don't want to wait use google. Just line up your search terms and restrict your search as inthanks 8)
anything you want to look for site:magiclantern.fm/forum
Regarding magic zoom, it took me awhile to figure out how to use it with EF-M lenses while maintaining manual focus. The best way to do it is to go into the M's Config menu and reassign the focus to the * button on the dial so that it no longer focuses when you half press the shutter button. Also, set the focus mode to AF/MF and set magic zoom to appear when focusing or half pressing the shutter. Now you can set the focus box by tapping the screen and then when you turn the focus ring or half press the shutter button, the magic zoom box will appear to aid in focusing.
Someone at some point told me to "use '70s glass" Can anyone be a little more specific and tell me what lens and adapter I would need to get the closest to 35mm as possible on the EOS M?
Andy
When I adjust Kelvin WB, I can't set it back to AWB.I solved this by going to "Q" menu, set WB to some value (sunny) and after set to AWB. Anyway to set Kelvim WB to Auto would be perfect.
I wonder if someone on this forum could give me some pointers. I am trying to use the EOS M + intervalometer to collect aerial imagery from a Cessna, but I have a problem - in AF, when flying over water sometimes the reflection stops the AF from achieving focus and the rest of the flight there are no images. Even when not over water the AF makes it so that the minimum delay between pics is too long ( > 3 sec) to get continuous coverage.
But in MF I can't reliably get the 22mm pancake to stay in focus, even using magic zoom on a faraway object to manually focus before takeoff. I think I've had about 1 out of ~20 flights work ok.
I am also flying with a D10 modified with CHDK, and in that case, I have an intervalometer script that tells CHDK to focus to infinity and lock focus. Is there any way to do something like that programattically with the EOS M? Someone at some point told me to "use '70s glass" Can anyone be a little more specific and tell me what lens and adapter I would need to get the closest to 35mm as possible on the EOS M?
Sorry if I am beating a dead horse, or offending anyone by comparing CHDK with Magic Lantern. I am a scientist, not a photography wizard, and I am currently contemplating an experiment whereby I determine how many pieces the EOS M fragments into when dropped from an airplane at 600 meters.
Andy
Hi everyone! I have been using ML on 60D for a while. I purchased the EOS M last week and been playing with ML for a couple days. I would like to share my user experience and hopefully get some tips & advises from you if you have better way/shortcut of handling these.I understand the fact we are using nightly builds but I hope there are better solutions that I just missed. Thank you!
- one major issue I'm having when I was going thru setting in the ML menu, if I pause for a sec or two, the screen switches from menu to the ML live view. It gets annoying, did I miss something here?
- I found it difficult to change aperture/shutter/ISO setting when I was in the ML live view. I was in M mode, I could roll the dial to change the shutter setting and if I want to mess with the other two, I have to open up ML menu OR switch to Canon live view screen (which defects the purpose of the ML).
- Is Auto-Kelvin WB available in current build? If not, is there any shortcut switching between different WB preset (including AWB) within ML live view? Currently I have to switch to Canon menu to adjust WB. I hope the Arrow/SET shortcuts will be included in future release
- *NOT ML related - I'm shooting with the 22mm and would like to use manual focus exclusively relaying on ML's Focus Peak feature. However I noticed the focus ring takes a good 360+ turns to focus from infinite to MFD. It makes it difficult to operate. Any advise?
Hi and welcome! I've been using ML on the EOS M for the past 2 months and here's my experience in response to your questions:
- This is a known issue. Canon's GUI has some way of canceling out the ML menu while in LiveView on the 6D and EOS M (there is only LiveView on the EOS M, so that means always)
- The EOS M has a native functionality where you press the +/- button on the jogwheel buttons to alternate wheel control of the shutter speed or aperture. In the regular LiveView mode, you will see the green indicator alternate between the two boxes when you press this button. As for ISO, you have the option of setting Custom Function VI to assign the Trash Can button to select ISO Speed. With these two options, you can quickly change all 3 exposure values quickly and easily while using ML LiveView
- Unsure, sorry
- I don't think ML currently supports any kind of modification to EOS M's focus ring awfulness... but being able to increase the rotation sensitivity of the focus ring sounds like an amazing feature!
Has any one used post deflicker module with xmp successfully?
I installed the latest nightly build (magiclantern-Nightly.2014Aug20.EOSM202.zip) and followed the instruction mentioned in this thread: http://magiclantern.fm/forum/index.php?topic=5705.0 (http://magiclantern.fm/forum/index.php?topic=5705.0).
There were no .xmp files generated along the .cr2 files.
I hope I get a pass if these has been asked before because I did search for "EOSM Continuous" and did not get my answer:
The chart says raw can only be shot while recording h264 simultaneously, is this still true?
I don't think so, I don't know that has ever been possible.
What is the max resolution that you can shoot RAW continuously on EOSM?
next question
I am shooting most raw projects at 2.35:1 aspect ratio, what is the max resolution at this aspect?
1504x456 is what I can get at that aspect ration on a Sandisk Extreme 45MB/sec SD card
What is the workflow like for shooting raw with sound? Do you just use the audio from the h264 file?
Use mlv raw format with sound
Thanks for answering these questions, I am considering picking up an EOSM for helicopter shots, and if I do. I will be glad to contribute what I can in helping with development for this body as well.
Cool. IMO the M sucks for Raw. Aside from the card speed limitations there are post production considerations such as pink dots that need removed and the image needs stretched. Magic Lantern on the EOS M really helps the camera from a usability standpoint though :D
Uninstallation:So I went in the menu to "Firmware-Ver.: 2.0.2" (the same option I used for installation), but it claimed that a firmware is needed on the card for update.
1) Run Firmware Update from your ML card.
2) Follow the instructions.
^Just read any of the 16 pages of this thread and it would tell you that...
Well since the shutter bug is mentioned on almost every single page of the 16 page thread most people mustn't have looked too hard to find an answer ;). A sticky at the top would be the smartest thing, something like this that could be added to the top of the page. VVV
Sticky:
Shutter Bug: Most prevalent with 18-55 EFM lens. Fix - half take lens off and put it back on again.
Menu disappearing: Menu only stays open for about 3 seconds. Fix - there isn't one.
Opening Menu: Either two finger tap the screen or hold down the trash can button for 3 seconds.
Cycle between menus: For different menu views press the "menu" button after two finger tapping or holding the trash can button down.
Movie stopped recording: Likely that there's too much info to record. Fix - lower Q-scale or CBR (if enabled) for more complex scenes.
yeah, I'm working on getting the play button to act as Q when ml menu is open, does anyone disagree?
Reply #364 on: August 22, 2014, 05:16:25 PM »
Maybe I'm an idiot and never realised, but I have some interesting info in regards to the focus box while using crop mode as I always assumed it didn't work...
I found that the focus box does actually work in crop mode as long as you make sure the focus box is positioned in the top of the screen (top left) and I usually set pixel size at 2:1 for best results.
It works in small medium or large box size, but the small window looks the least glitchy. The bigger sizes will have some flicker, but on my camera are still totally useable to judge focus.
If this has been discussed already I apologise, but I don't remember reading it here, hopefully it helps others like me.
I tried 2.0.2 version.
Too many bugs. Can't take pictures, everything is blocked, unless you switch off the camera and switch it on again.
If you insert battery, the camera will light up the green orage led, for a few seconds even if you do not switch it on.
Could anyone stop my shirt by taking pictures by itself when I am wearing my M on my tommy?
there must be some kind of tap 3 times system, to activate or deactivate the touch screen.... please could you add this function?
Why would anyone choose a T3i, 600D etc over the M for a cheap ML soloution??? Am I missing something here? The M does everything I need and more with ML and I rarely have a problem with it. Not to mention Raw on the M is better than others in it's class and price range.
Also I'm pretty suprised by the amount of people that ask questions on here that have absolutely nothing to do with ML... for gods sake read the manual or do a bit of research first! :D
REAL question - Does anyone else have a problem with the "Greyscale" live view when shooting RAW??? All the other options work for me (Hacked, No live view etc) but Greyscale doesn't seem to. The framing when shooting RAW on my M is a bit off and I assume if you can shoot with the Greyscale function it will be more correct?
because pink dots are a pain to remove in post, sound only works for one take and then you have to reboot the camera, no headphone output, no tethered (tablet) control, and it's not very ergonomic.... these are some of the reasons to choose a t2i/t3i
Just like the posts you are criticizing, the above adds absolutely nothing to the conversation either....
Greyscale preview has not been implemented on the M, either it hasn't been found, or doesn't exist in the M's firmware. The menu entry is still there to keep the code cleaner since it is ported from other cameras.
SD-cards and slots are specified for 10,000 "mating" cycles.was that referring to my post?
Do the math ...
I may have found a fix for the shutterbug (not sure).
The shutter bug always occurred when using the EF-M 18-55 IS STM lens.
I changed the Custom Function "Release shutter without lens" to "Enable", restarted the camera and the shutter bug was gone.
Since then I have not been able to replicate the shutter bug (not even by changing the setting to "Disable").
It worked for me. I am using the sept 27 nightly build.
I see no way of zooming in whilst in movie modePrefs>LiveView zoom tweaks>Zoom on HalfShutter>
Try renaming your SD Card volume to EOS_Develop.
PS: I have adapted a Canon 7.5 - 97.5 mm f:1,4 TV zoom lens to my EOS-M - works well with the 3x video crop. Wow! ;)
I'm a filmmaker, not a beta tester.
Is there any way to extend the time menu appears?It seems to reset the timeout if you press a key. Sometimes I hold the <DOWN> key down to keep the menu on screen while I'm figuring out which menu option to choose.
The good old EOS-M has been somewhat a deal killer with RAW/MLV (pink dots removal is a PITA)I use Rawflow.exe to save DNG files for each frame, and exit the program when it starts to save TIFF files (delete any that are saved).
But yes I agree with the fact that the M3 would definitely be a game-changer with ML for the current EOS-M owners!The M3 has a Digic 6 processor, which has been really hard to port with CHDK. It may take awhile for a Magic Lantern port too.
I've had the opposite problem of trying to get rid of the menu more rapidly. Tapping the screen with two fingers does that, I discovered.
Any updates regarding FRSP for EOS-M or is that ever not going to be a possiblity?
FRSP should work fine for M in the branch since August last year, at least it did back then :)Download link? :)
Page 187 of your camera manual (http://gdlp01.c-wss.com/gds/8/0300008788/01/eosm-im-en.pdf).
The one compiled by you.I was under the impression that if was merged in the main branch from which the nightlies are compiled?
I was under the impression that if was merged in the main branch from which the nightlies are compiled?I compiled it ( this VM updated: http://www.magiclantern.fm/forum/index.php?topic=7579.0 w/ updated gcc-arm to 4.8.4 as the included one failed: https://launchpad.net/gcc-arm-embedded/4.8/4.8-2014-q3-update ) for myself yesterday ( commit 666c09b ): http://we.tl/p1e78AKUef
I saw that the last build has a shutter issue, is it still the case?Apparently it is: https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug
Is there any kind of stable version?Not really, always get the latest build: http://builds.magiclantern.fm/#/ -> EOSM.202 as it's better to report issues having the latest version anyway.
And I have the same question that Silverburn, does anyone shoot in video mode with the M? :)Apparently someone (https://vimeo.com/ryanmoorman/videos) is shooting on M1.
To get a clean picture in 1080p rec, you might have better luck with a low FPS.
2/ I am not able to select menu options. For instance I can't change the time value for intervallometer; pressing the Q button (which is the same as the Set button on the EOS M) toggles only between “Off” and “On, 10s” values. Any suggestion on what I am doing wrong?
1/ The menu seems to appear only in movie mode, not in photo mode.press INFO one more time until you get it
3/ Help files seem to be missing from the zip file.you know that already since you've read this: http://magiclantern.fm/downloads.html (http://magiclantern.fm/downloads.html) right?
you know that already since you've read this: http://magiclantern.fm/downloads.html right?
At time of writing there is only one version and there are no helpfiles included.
press INFO one more time until you get it
A heads up. EOS-M build is currently failing, I hope this means new goodies are in the works. :)This needs fixing, hence the hold up, contribute to unblock it: http://www.magiclantern.fm/forum/index.php?topic=14959
Anyone else can contribute? https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug#comment-17792140 (https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug#comment-17792140)
This Build Failed! :oIt's broken because of this: http://www.magiclantern.fm/forum/index.php?topic=14959 (http://www.magiclantern.fm/forum/index.php?topic=14959)
I need magic-lantern for my eos m - because I need to record a video which is longer than 29 mins. Where can I get a magiclantern build now?
Test please (latest build needed):Not a M feature: https://builds.magiclantern.fm/#/features (https://builds.magiclantern.fm/#/features) ;)
Switch Magic Zoom to Fullscreen mode. Does screen look fine or is there some kind of vertical splitt with "tiles"?
Why i can't record MLV with same settings as on 6D or 70D?Yes, but it's not only a card speed issue, it's a different camera, one that costs 1/3 or 1/5 or there about by comparison. :P
i dont seem to find anything on why eosm dosent have focus controls like rack focus and focus pulling?
Yes, but it's not only a card speed issue, it's a different camera, one that costs 1/3 or 1/5 or there about by comparison. :P
EOS M is almoust identical to EOS 650D/700DHeh. Have you seen a picture of these cameras? I would hardly call them "almost identical". In fact, the M is about the most different camera from the rest of the cameras supported by ML, it's actually not even in the same category of camera (i.e. it's a "mirrorless" camera not a "dslr" technically), it even has it's own unique lens mount. The difference is not just physical either. The M is probably the most different from the rest of the cameras in terms of internals and Canon and ML code (with the possible exception of the old VxWorks cameras, like 5Dc). There are quite a few special/unique exceptions for the M in ML code (obviously all cameras have their own unique things in the ML code base, but the M's things tend to be the most unique or non-standard compared to other cameras).
Heh. Have you seen a picture of these cameras? I would hardly call them "almost identical". In fact, the M is about the most different camera from the rest of the cameras supported by ML, it's actually not even in the same category of camera (i.e. it's a "mirrorless" camera not a "dslr" technically), it even has it's own unique lens mount. The difference is not just physical either. The M is probably the most different from the rest of the cameras in terms of internals and Canon and ML code (with the possible exception of the old VxWorks cameras, like 5Dc). There are quite a few special/unique exceptions for the M in ML code (obviously all cameras have their own unique things in the ML code base, but the M's things tend to be the most unique or non-standard compared to other cameras).
Your logic is flawed. Because ML works fine in Liveview with 650D and M both it doesn't mean there is no difference between firmware versions for both cams.
Hardware partly similiar. Firmware not similiar. Conclusion?
I am not a coder, but ...Great, now that you admit that, stop this conversation that leads nowhere.
I think nobody is really interested in fine-tuning EOS M ML project. And this is very sad.Why are you still posting here instead of fixing issues, here start with those that I reported: https://bitbucket.org/hudson/magic-lantern/issues?reported_by=~licaon_kter (https://bitbucket.org/hudson/magic-lantern/issues?reported_by=~licaon_kter)
was it clear the way I said?Not really, detail your workflow.
Not really, detail your workflow.In the options of the "auto exposure" module some options require the "main dial" button to change values. problem is the M doesn't have it.
Am I the only one who finds Canon's auto-expo dreadful?
for example the ISO option: lowest value is changed by pressing left or right (works also by pressing up, down and by rotating the wheel), but upper value cannot be changed no matter what.oh, so I see now, yes, unfortunate.
Wow Licaon_Kter, looks like you've been working hard on ML for EOS-M.I'm barely shooting, only on weekends, mostly family stuff, by I did stumble upon those even as a n00b that I am.
I take it that testers should be using magiclantern-Nightly.2015Apr19.EOSM202 since the newer builds have been failing. I'll try to reproduce and comment on your bug reports.Actually the most important ones are before April 19. The breakage after that is intentional, this thread actually: http://www.magiclantern.fm/forum/index.php?topic=14959 (http://www.magiclantern.fm/forum/index.php?topic=14959) where we did try to help out but I'm not sure what we can do better/more, I actually don't understand half of those things anyway. :P
*snip*I'm also looking for external battery solution for my EOS M.
I'm also looking for external battery solution for my EOS M.
For the life & sake of EOS-M -- @dmilligan saved myself from selling this tiny beast.Umm wasn't common knowledge that PDR can be removed ? :P
Now, if a1ex could defeat these 2 beasts: https://bitbucket.org/hudson/magic-lantern/issue/2255/mlv_sound-working-only-on-the-first-video and https://bitbucket.org/hudson/magic-lantern/issue/2254/star-bbaf-during-raw-recording-crashes-ml things would be perfect :D
"InstallationThis!
Format the card from the camera.
Make sure you are running Canon firmware 2.0.2.
Copy ML files on the card and run Firmware Update."
Thanks for this information, 720p is good, the problen is i dont configure this, is verry hard and need one help,like a manual or simple user guildShooting raw on the EOS-M is a bit tricky but it can be done. First of all you must be using a fast enough SD card. The camera has about a 41 MByte/s data transfer limit and uses UHS-1 cards so a really fast UHS-II won't help at all. I use SanDisk Extreme Pro UHS-I SDHC U3 Memory Card (Class 10).
Can I check is the current build not working properly?The most current build is April 19 and it works properly.
If so, can I just grab the April 19th built and work with that or is that one also suffering from the shutter bug?They all suffer from it, or better yet put, on certain cards they do, on some others they don't, Sandisk is the better bet.
They all suffer from it, or better yet put, on certain cards they do, on some others they don't, Sandisk is the better bet.
Read here: https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug
How add the Audio RemoteShoot function on the EOS M (magiclantern-Nightly.2015Apr19.EOSM202)? Is it's possible?
Already tested: raw video recording (either mlv_rec or raw_rec) is not possible at 1280x720 30fps with the Transcend 90MB/s card: red warning in mlv recording, skipped frames, recording stops imediately. And it works with the Sandisk Extreme PRO 95MB/s (yellow warning in mlv, because actual writing speed is ~ 38 MB/s, but it works) ... so there is really a write speed difference.
Answers here: https://rbrune.github.io/mlraw/
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
lv:0 mode:0
Magic Lantern version : Nightly.2015Apr19.EOSM202
Mercurial changeset : e08c6c0be070 (unified) tip
Built on 2015-04-18 22:08:28 UTC by [email protected]
Free Memory : 160K + 3302K
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
lv:0 mode:0
Magic Lantern version : Nightly.2015Apr19.EOSM202
Mercurial changeset : e08c6c0be070 (unified) tip
Built on 2015-04-18 22:08:28 UTC by [email protected]
Free Memory : 160K + 3302K
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
lv:0 mode:0
Magic Lantern version : Nightly.2015Apr19.EOSM202
Mercurial changeset : e08c6c0be070 (unified) tip
Built on 2015-04-18 22:08:28 UTC by [email protected]
Free Memory : 159K + 3302K
Anyway, some assert logs:Yeah the M get's plenty of those, being a LV only camera.Code: [Select]at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
[9] ?: NULL PTR (80c3e100,e1a00000)
pc= 7ef4 lr=19980218 stack=17cf70+0x400
entry=ff0d0d68(0)
e1a00000 e59ff014 e59ff014 e59ff014
e59ff014 e1a00000 e59ff010 e59ff010
Magic Lantern version : Nightly.2015Apr19.EOSM202
Mercurial changeset : e08c6c0be070 (unified) tip
Built on 2015-04-18 22:08:28 UTC by [email protected]
Free Memory : 183K + 3479K
Is there any such setting in Canon menu?No... You can adjust the sensitivity (standard/sensitive) or enable/disable touch shutter.
Are full res silent pictures activated in your cam? If true, to take pictures you need to use a half shutter press. A full press causes an error.
http://www.magiclantern.fm/forum/index.php?action=activate;u=57668;code=6af992ae69
[9] ?: NULL PTR (80c3e100,e1a00000)
pc= 7ef4 lr=19980218 stack=17cf70+0x400
entry=ff0d0d68(0)
e1a00000 e59ff014 e59ff014 e59ff014
e59ff014 e1a00000 e59ff010 e59ff010
Magic Lantern version : Nightly.2015Apr19.EOSM202
Mercurial changeset : e08c6c0be070 (unified) tip
Built on 2015-04-18 22:08:28 UTC by [email protected]
Free Memory : 183K + 3479K
Personally I'd be in favor of removing such posts (or at least scrubbing references to 4K) and banning users who continue to post such nonsense. It certainly does not help drive this project forward, in fact very much the opposite, only serves to confuse users.
One question is it a good idea to get a larger memory card when using ML?
Finally, something significant to report.
Matthias Bretz found the key. After a few practice runs I got the Play-Button-Power-Button combination timing down and got a consistent StartupCondition : 4, 0 on all the cards. This killed the shutter-bug on the cards that exhibited the shutter-bug and the cards that didn't exhibit the shutter-bug continued to function without the shutter-bug.
So now we need help from a developer to figure out how to get this to happen every time the EOS-M is powered on:
PropMgr:ff23cfb4:81:03: StartupCondition : 4, 0
@DeafEyeJedi - Good tip. The Trash button on the EOS-M is equivalent to the Del button on other cameras. I tried it out an not only does it work but the custom function assigned in the Canon menu - custom function 6 (C.Fn IV:Operation/Others Trash) also works. Well all except if the trash button is assigned to bring up the ISO menu.
Hi I cannot find this information anywhere.
I just want to know if the EOSM will shoot 1080p at 60fps (or more?) in normal avchd mode?
Latest nightly works [functions as described in ML wiki] reliably (?) if you use the EF-M STM 22mm lens. Other lenses work too but a shutter bug exists which can lock the camera (least likely to happen if you use a SanDisk 32 GB or smaller card).Yep, kinda.
Do I need to update to latest firmware?2.0.2? Yes, it fixes (most of) the focus speed, not ML related but needed.
If I get this shutter bug, is there a reliable way to permanently restore the camera? So my friend would never know I had risked the life of his little camera?Non-ML cards don't have it, hence it won't matter to your friend.
If I get this shutter bug, is there a reliable way to permanently restore the camera? So my friend would never know I had risked the life of his little camera?
Sun Aug 2 22:08:13 2015
Hey, who removed all the resolutions from mlv module!!??? why does it jump from 1280 to 1600?http://www.magiclantern.fm/forum/index.php?topic=14309.msg152404#msg152404
what else? shutter bug? what's really going on with that, do you really believe the brand of memory card makes a difference? That doesn't make any sense to me.
I just ordered the 18-55 so maybe if i start to experience the shutterbug I'll be able to help.
I made pull requests for the fixes, we just have to wait for them to be merged. I just ordered the 18-55 so maybe if i start to experience the shutterbug I'll be able to help. BTW, what is your name on bitbucket? I'll add you as a reviewer on my PR's
In ML menu press Info to toggle menu design.Thanks Walter,
I meant the other Info button labeled Menu ...Walter, you are a *
I have been using the build from Aug 13th and I have noticed a few things that could be normal or possibly a bug?1. Fixed here ( https://bitbucket.org/hudson/magic-lantern/pull-requests/650/dpjpandone-fixes-magic-zoom-flicker-on/diff (https://bitbucket.org/hudson/magic-lantern/pull-requests/650/dpjpandone-fixes-magic-zoom-flicker-on/diff) ) I guess, once a1ex pulls it anyway.
1. Fixed here ( https://bitbucket.org/hudson/magic-lantern/pull-requests/650/dpjpandone-fixes-magic-zoom-flicker-on/diff (https://bitbucket.org/hudson/magic-lantern/pull-requests/650/dpjpandone-fixes-magic-zoom-flicker-on/diff) ) I guess, once a1ex pulls it anyway.
There are a few test builds floating around but the best way to get the latest and greatest EOSM build is to grab the code and roll your own. It isn't really that difficult. If you are on a Windows system I just put up a tutorial that should be fairly easy to follow.
http://magiclantern.fm/forum/index.php?topic=15845.msg154356;topicseen#msg154356
Notice that the source that I pointed to in that article has all the pending EOSM related pull requests merged in.
If you are on a Mac like me you'll need to install the free Xcode app and if you are on Linux, well that is the easiest of all to setup. There should be plenty of help in the General Development Discussion (http://magiclantern.fm/forum/index.php?board=25.0) section of the forum.
cd ~/magic-lanternhg pullhg updateBeen lurking for a while, and am glad to join in the conversation. I'm relatively new to ML.. only been using it for a few months. It's quickly become indispensible. I bought an EOS M exclusive;y as a guinea pig for ML, and have not regreted it.
site:magiclantern.fm eos-m q buttonThat's odd. Are you on Windows or Mac? Did you clone my EOSM__working branch? What is the error? Most likely it is rst2html not found but that shouldn't happen if you followed my instructions. I did update the branch this morning so you might try it again.Code: [Select]cd ~/magic-lanternCode: [Select]hg pullCode: [Select]hg update
By the way, let's stay on topic (EOS-M) and continue compiling discussions in their appropriate topic.
I was able to build ML with the Modules with your commit for the cleaned up windows code.
And for EOS M 2? :DDifferent hardware.
Is there anyway to use your smartphone as a monitor with your EOS M?
I know of the app called "DSLR Controller" but it won't work on EOS M because of Canon have crippled remote functions of M. I was wondering could it somehow work with MHL adapter and MHL enabled phone?
If not suggest a reasonable priced "field monitor" for me, mainly to check focus. It should be rather small, under <6" preferably.
Is there anyway to use your smartphone as a monitor with your EOS M?have you tried canon's app?
I know of the app called "DSLR Controller" but it won't work on EOS M because of Canon have crippled remote functions of M. I was wondering could it somehow work with MHL adapter and MHL enabled phone?
If not suggest a reasonable priced "field monitor" for me, mainly to check focus. It should be rather small, under <6" preferably.
M2/M3/M10 have Wi-Fi
M1 does not.
hg clone -r EOSM__working https://bitbucket.org/daniel_fort/magic-lantern
If i recall correctly, the reason this is not included in main, is because the settings persist until you restart the camera, not only this, but the camera must be restarted with the same card (with the current implementation) in order to clear the settings, this presents a dangerous situation, as someone who isn't aware of this might remove their magic lantern card, and the GOP/flush settings don't go back to default
I moved some of the great work 1% did to get ML functioning on the EOSM for firmware 2.02 back into the main ML code base. I'm sure its missing some features and bugs from it's TL counterpart, but if you are interested in testing ML and helping make it stable and in sync with the code for other ML cameras for all base features, please comment here and I'll do my best to port 1%s bugfixes, or to test, create issues for new bugs and attempt to solve. IMO, the main focus is ensuring all basic ML functions work well before branching out to things like raw video.
- 45.02 fps in 3x crop standby (available for raw recording; limited to 45 as suggested by LK)
- 34.37 fps in 3x crop H.264 (without video hacks)
- 31.24 in 1080p 1x (can be pushed to 33fps in H.264 if desired)
- 62.16 fps in 720p (can probably be pushed further)
- 31.24 fps in photo mode (no big deal here)
- 35.96 fps in 5x zoom (available for raw recording; can be pushed further if desired)
a1ex made some comments on bitbucket (https://bitbucket.org/hudson/magic-lantern/pull-requests/649/fps_timer_a_min-and-fps_timer_b_min-fixed/diff) that should push the frame rate on the EOSM a bit further.
I'm a bit busy right now to test it but if there are any users who want to see how far they can push their little camera I added it to my EOSM__working branch and also compiled it and uploaded it to my bitbucket download area (https://bitbucket.org/daniel_fort/magic-lantern/downloads).
I keep adding what seems like interesting pull requests to my EOSM branch so at times it might exhibit some odd behavior. Of course ML in general exhibits some odd behavior. As do ML users--but I don't think there's a fix for that.Well, that's why I got a canon m, I'm odd...[emoji16]
A few more improvements that will benefit EOSM users are in the works but the issue that is holding up nightly builds isn't fully resolved yet. Patience.Thanks! I will build it later and give it a look!!
However, for the impatient who prefer a little more excitement I decided to merge lua into my EOSM__working branch. What the heck, it is very useful and it is a module so if you don't load it you won't even know that it is there. For those that still haven't set up a Magic Lantern development system I uploaded a nightly to my bitbucket download area:
https://bitbucket.org/daniel_fort/magic-lantern/downloads
Check out what you can do with it on the lua topic (http://www.magiclantern.fm/forum/index.php?topic=14828.0).
Is it impossible to develop a magic lantern firmware for EOS M2? :-[
how i can downloaded this????
* 45.02 fps in 3x crop standby (available for raw recording; limited to 45 as suggested by LK)
* 34.37 fps in 3x crop H.264 (without video hacks)
* 31.24 in 1080p 1x (can be pushed to 33fps in H.264 if desired)
* 62.16 fps in 720p (can probably be pushed further)
* 31.24 fps in photo mode (no big deal here)
* 35.96 fps in 5x zoom (available for raw recording; can be pushed further if desired)
I do not shoot video, but I'm glad to see that an old issue with A-ETTR present in previous builds for EOS-M seems fixed now.Not sure I saw that before, but I'm glad it's fixed. :)
ML FPS Override menu still displays "From 30" even when resolution is set to 1280x720 @ 60 fps in the canon menu, maximum actual FPS idles at 30.389.IIRC, the fps will change once RECording starts, the menu is at 30 always.
I'm having problems when I'm recording H264 video.Maybe report it here: https://bitbucket.org/hudson/magic-lantern/issues
The Canon firmware is missing these items in the menu: (even without a card in the camera)Remember that Canon Menu has _all_ the items only in M(anual) mode only ;)
i have a problem whit the RAW FileLook around here: http://www.magiclantern.fm/forum/index.php?board=54.0 for the word pink.
there ara many many pink noise.
i'm new in eos m ( i am a user of magic lantern in mark 3 )
...
there ara many many pink noise.
Also, your RAW program (which one do you use?) should have something that handles that
a program for mac thet fix the problem ??RawMagic can not discussed here: http://www.magiclantern.fm/forum/index.php?topic=13335.0 (http://www.magiclantern.fm/forum/index.php?topic=13335.0)
Started on Jan 14, 2016 12:07:49 AM
Polling SCM changes on master
[workspace] $ hg pull --rev unified
pulling from https://bitbucket.org/hudson/magic-lantern/
no changes found
[workspace] $ hg log --rev unified --template {node}
[workspace] $ hg log --rev unified --template {rev}
Done. Took 2.7 sec
No changes
Started on Jan 14, 2016 12:14:49 AM
Polling SCM changes on master
[workspace] $ hg pull --rev unified
pulling from https://bitbucket.org/hudson/magic-lantern/
searching for changes
adding changesets
adding manifests
adding file changes
added 2 changesets with 2 changes to 2 files
(run 'hg update' to get a working copy)
[workspace] $ hg log --rev unified --template {node}
[workspace] $ hg log --rev unified --template {rev}
[workspace] $ hg status --rev f87b7594be9cd50b31226819f646c596f2e05348 --rev ca5315a3b586931c1b58b9e72fbed6b96d558d6f
Dependent changes detected
Done. Took 2.9 sec
Changes found
Also sometimes intervalometer stops after the first picture in Full Silent Picture mode. The only fix that I know is to remove the battery and try againUse "leave menu" as trigger.
Why is there no audio tab in the newer builds?There was never one in the first place. See: http://builds.magiclantern.fm/#/features ?
I feel like a dick - I'm sure I tried that earlier and nothing happened - particularly Delete. In any case, it's working now. Thanks.It will be fixed in the next build: https://bitbucket.org/hudson/magic-lantern/commits/2a1f972cdbd87e77059539622fd4308618fa9ae6 (https://bitbucket.org/hudson/magic-lantern/commits/2a1f972cdbd87e77059539622fd4308618fa9ae6)
Can someone help me to understand the issue? Is the shutter/frame rate not writing fast enough to the card? Or is it set very low and I am not noticing?
I am using cropmode, and i assumed it was the telephoto effect (stabilization) but the video is lagging so badly, it seems like the frame rate is extremely slow.
sidenote- can i make the ML menu appear for longer, i barely have a moment to read before it disappears.
My liveview is lagging severely.Do detail your settings, fps, size, etc.
I thought maybe when I imported the video it might be okay, but the video is lagging as well.
Read replies #923-925
Would anyone be willing to upload some high quality footage to Vimeo for download or high quality footage to you tube?
https://www.dropbox.com/s/3d6zpxnndvhxpoa/magiclantern-Nightly.2015Aug21.EOSM202.zip?dl=0
If you want to try to record 44fps in 1080p crop mode, you have to set the compression method to ALL-I under "video hacks", just don't forget to set it back to IPP before you turn video hacks back off (read the menu comments)
Mode Buffer Size Notes
mv1080 - 1808x1190 - not available on the EOSM.
mv720 - 1808x727 - needs to be stretched by 1.67x
vertically - up to 50/60 fps
except on EOSM.
mv640 - 1808x1190 - basically the same as mv1080 mode.
mv1080crop - 1872x1060 - highest resolution and largest
sustainable frame sizes on all cameras.
mv640crop - - not possible.
zoom - 2592x1108 - same 5x magnification as mv1080crop but
can pan around sensor and can achieve
higher resolution than mv1080crop.
Ok, I know this has to have been asked before. But is there a place to get an old stable release with the help files?
You have this forum... and its search function... go bleeding edge :)
I've been looking at the nitrate calculator. Does the 3x5 subsampling option have lots of moire and aliasing?
Do they work?
it got me! i was all over the internet looking for a solution LOLReally? Where? On Facebook? Admit it, it's a lie, everyone came here to complain or on Bitbucket to make an issue: 1 (http://"https://bitbucket.org/hudson/magic-lantern/issues/2490/stop-error-screen"), 2 (http://"https://bitbucket.org/hudson/magic-lantern/issues/2493/5d-mk-ii-bluescreen-crash-or-april-fool"), 3 (http://"https://bitbucket.org/hudson/magic-lantern/issues/2494/70d-stop-0x000000aa"), 4 (http://"https://bitbucket.org/hudson/magic-lantern/issues/2497/60d-bluescreen-error-0x000000aa"), 5 (http://"https://bitbucket.org/hudson/magic-lantern/issues/2498/blue-screen-cannt-use-magic-lantern"), 6 (http://"https://bitbucket.org/hudson/magic-lantern/issues/2499/blue-screen-cannt-use-magic-lantern"), 7 (http://"https://bitbucket.org/hudson/magic-lantern/issues/2500/blue-screen-stop-error")
ef-m 11-22mm lens in this category need to unlock
If the advance has been unlocked before boot
Press the shutter results do not go
Necessary to unlock the lock and then press the shutter
magiclantern-Nightly.2016Feb29.EOSM202.zip
Changeset: dd16e5d
magiclantern-Nightly.2016Feb27.EOSM202.zip
Changeset: c8c0c20
Necessary to unlock the lock and then press the shutterDepends on the lens, on your 11-22 if you do that first, yes, it works, this issue appears on non-collapse lenses too like the 18-55 and there is no known fix (besides using only some SD cards)
Hi, I'm considering putting ML on my Canon M, the main two features I currently want are Analog Gain, and Headphone monitoring through the AV port. I would like to check first if those features are available for the M, because on one page somewhere on the site I read that the ML Audio features are not available for cameras after the 600D, and I think the M is after the 600D.Not available, see here: http://builds.magiclantern.fm/#/features
Can you confirm if those two features (and the Audio features in general) are available on the Canon M?
Thanks.
For EOS M, a long press on SET/Q can be made to open submenus, in the same way as a long joystick press opens the submenu on 50D/5D2/5D3/7D.
I'm using the Alexa log-c profile.
Is anyone else getting the camera starting all by it self when hanging from your neck?
I've gotten used to powering down the camera in order to save the battery so it isn't an issue for me.Umm, it's powered down and it starts here, in case I wasn't clear enough.. :'(
@Licaon_Kter: are you able to get correct behavior on your EOS M?Not sure what the problem is though.
Yes, I can confirm too. Strange.
Thanks for replies, at least I know its not just my camera!
the palette registers are write-only, so if you are able to get the palette values, be my guest ;)
All of the other screen captures I tried turned out fine.Screenshots of ML stuff looks correct b/c for our graphics, we know what the palette is.
Dfort awhile ago you mentioned a zoom mode that was capable of2592x1108 or something like that.. is that do-able on the eos m? And if so how do you do it?
...would it be difficult to put all the black bars on the left or right?
I was testing a noncrop RAW video recording and got a problem.
P.S. I would love to shoot in crop mode (fantastic quality), but it need's fast wide lens and I can't afford it at this moment.
...I'm having some issues with magic zoom and my manual lens samyang 85mm F/1,4. When I try to focus green bars do not show up and I'm not sure if I am in focus or not.
I also like focus peaking but at times I find it touch off-focus. Until few min ago samyang 85mm F/1.4 was my only manual lens that I used with canon genuine EF to EF-M adapter. Its not chipped so manual all the way. I see no change with magic zoom with my FD 28mm F/2.8 lens as well. Reason that I am asking is that on my 5D mark2 I also use magic zoom but there I get 2 green bars confirmation when shot is in focus (same lens samyang 85mm) while on eos-m I do not. Its a minor issue but still would like to have this option on my eos-m if possible. I do not own any eos-m lenses so I cant compare.
The EOSM supports magic zoom but I'm not very familiar with it, I prefer focus peaking when using manual lenses. You said that the issue is with your manual lens. Is it a chipped lens? Assuming it is an EF mount which lens adapter are you using? Do you have the same issue with an EF-M lens?
The little color dots you're seeing and possibly the vertical color lines may be artifacts from the focus pixels. It was an interesting journey dealing with focus pixels (http://magiclantern.fm/forum/index.php?topic=16054.0). I ended up mapping all of the focus pixels for the affected cameras starting with the EOSM and @dmilligan coded a fix into MLVFS. I assume that @AWPStar is using the same algorithm in MLVProducer (http://magiclantern.fm/forum/index.php?topic=15271.0). Basically to hide the focus pixels the surrounding pixels need to be averaged. Dual ISO was a problem because of the alternating horizontal lines of light and dark so the averaging is only done on the pixels in the horizontal axis. This usually works fine until you get into fine details that are one pixel wide. That might be what's causing those vertically colored lines.
What is unique about the EOSM in crop mode is that you can use C-mount lenses. There's a bunch of cheap fast lenses out there though the quality isn't exactly fantastic. On the plus side crappy lenses do tame moiré. There are some nice quality vintage C-mount lenses made for 16mm but it seems that collectors are bidding up the prices on ebay.
Your ideas aren't stupid. In fact it is along the lines that a1ex, the main developer, suggested to get mv1080 working on the EOSM.
I could be wrong but I don't think there's anything going on with the M3...
If you record in h.264 with FPS override your audio will be disabled only if you have a microphone plugged in.
Quick question to anyone who shoots video. I've recently started using external microphones with this camera and have come across an issue that I've never found in the 1+ year of using this camera with ML. If you record in h.264 with FPS override your audio will be disabled only if you have a microphone plugged in.
I tested this with and without a microphone and only having a mic plugged in with FPS override kills the audio signal. Does anyone know the reason for this? Seems very random, as the camera has the ability to record the audio signal with nothing plugged into the jack.
Issue doesn't exist in RAW due to the MLV option for audio.
You are not shooting RAW where styles don't apply?
P.S. I would love to shoot in crop mode (fantastic quality), but it need's fast wide lens and I can't afford it at this moment.
What if you switch to the ML menu?
Is it possible to make a headphone jack for 700D with ML?
Hi,
I am using ML everythings works fine for months, but since I started to shot long exposure even manual or intervalometer from ML, always raw photos, and different setups, SD cards, etc., I´ve got corrupted photos, below ejemple, so anyone had any similar one? even I´m thinking in a hardware problem....
https://www.flickr.com/photos/[email protected]/30394580436
(https://www.flickr.com/photos/[email protected]/30394580436)
[img]https://c5.staticflickr.com/6/5827/30394580436_64f811d2e1_z.jpg[/img]60D: 57% in photo mode (30fps, global draw off).
Drops to 26% with FPS override at 10 FPS.
Powersave idea: drop to 10 FPS after X seconds of idle time, switch back on half-shutter press (or on any key press).
diff -r 15fce5b49b23 src/powersave.c
--- a/src/powersave.c Sat Oct 08 16:22:41 2016 +0200
+++ b/src/powersave.c Mon Oct 24 02:31:13 2016 +0200
@@ -129,6 +129,7 @@
static CONFIG_INT("idle.display.gdraw_off.after", idle_display_global_draw_off_after, 0);
static CONFIG_INT("idle.rec", idle_rec, 0);
static CONFIG_INT("idle.shortcut.key", idle_shortcut_key, 0);
+static CONFIG_INT("idle.display.fps_on.after", idle_display_fps_on_after, 0);
/* also used in zebra.c */
volatile int idle_globaldraw_disable = 0;
@@ -143,6 +144,8 @@
static int idle_countdown_display_off_prev = 50;
static int idle_countdown_globaldraw_prev = 50;
static int idle_countdown_clrscr_prev = 50;
+static int idle_countdown_fps = 50;
+static int idle_countdown_fps_prev = 50;
/* this will block all Canon drawing routines when the camera is idle */
/* (workaround for 50D) */
@@ -154,7 +157,7 @@
int idle_is_powersave_enabled()
{
- return idle_display_dim_after || idle_display_turn_off_after || idle_display_global_draw_off_after;
+ return idle_display_dim_after || idle_display_turn_off_after || idle_display_global_draw_off_after || idle_display_fps_on_after;
}
int idle_is_powersave_enabled_on_info_disp_key()
@@ -166,7 +169,8 @@
{
return (idle_display_dim_after && !idle_countdown_display_dim_prev) ||
(idle_display_turn_off_after && !idle_countdown_display_off_prev) ||
- (idle_display_global_draw_off_after && !idle_countdown_globaldraw_prev);
+ (idle_display_global_draw_off_after && !idle_countdown_globaldraw_prev) ||
+ (idle_display_fps_on_after && !idle_countdown_fps_prev);
}
void idle_force_powersave_in_1s()
@@ -174,6 +178,7 @@
idle_countdown_display_off = MIN(idle_countdown_display_off, 10);
idle_countdown_display_dim = MIN(idle_countdown_display_dim, 10);
idle_countdown_globaldraw = MIN(idle_countdown_globaldraw, 10);
+ idle_countdown_fps = MIN(idle_countdown_fps, 10);
}
void idle_force_powersave_now()
@@ -181,6 +186,7 @@
idle_countdown_display_off = MIN(idle_countdown_display_off, 1);
idle_countdown_display_dim = MIN(idle_countdown_display_dim, 1);
idle_countdown_globaldraw = MIN(idle_countdown_globaldraw, 1);
+ idle_countdown_fps = MIN(idle_countdown_fps, 1);
}
int handle_powersave_key(struct event * event)
@@ -229,6 +235,7 @@
idle_countdown_display_off = sensor_status ? 25 : idle_display_turn_off_after * 10;
idle_countdown_display_dim = sensor_status ? 25 : idle_display_dim_after * 10;
idle_countdown_globaldraw = sensor_status ? 25 : idle_display_global_draw_off_after * 10;
+ idle_countdown_fps = sensor_status ? 25 : idle_display_fps_on_after * 10;
if (reason == -2345) // disable powersave during recording
return;
@@ -379,6 +386,16 @@
idle_globaldraw_disable--;
}
+void idle_fps_en()
+{
+ set_config_var("fps.override", 1);
+}
+
+void idle_fps_dis()
+{
+ set_config_var("fps.override", 0);
+}
+
#ifdef CONFIG_KILL_FLICKER
static void black_bars_50D()
@@ -463,6 +480,11 @@
if (idle_display_global_draw_off_after)
idle_action_do(&idle_countdown_globaldraw, &idle_countdown_globaldraw_prev, idle_globaldraw_dis, idle_globaldraw_en);
+ #ifdef FEATURE_FPS_OVERRIDE
+ if (idle_display_fps_on_after)
+ idle_action_do(&idle_countdown_fps, &idle_countdown_fps_prev, idle_fps_en, idle_fps_dis);
+ #endif
+
/* zebra.c */
extern int clearscreen;
if (clearscreen == 2) // clear overlay when idle
@@ -611,6 +633,17 @@
.help = "Turn off GlobalDraw when idle, to save some CPU cycles.",
//~ .edit_mode = EM_MANY_VALUES,
},
+ #ifdef FEATURE_FPS_OVERRIDE
+ {
+ .name = "Turn on FPS override",
+ .priv = &idle_display_fps_on_after,
+ .update = idle_display_feature_print,
+ .select = idle_timeout_toggle,
+ .max = 900,
+ .icon_type = IT_PERCENT_LOG_OFF,
+ .help = "Turn on FPS override when idle, to save some CPU cycles.",
+ },
+ #endif
MENU_EOL
},
}
@@ -633,5 +666,7 @@
void idle_globaldraw_en() { }
void idle_force_powersave_now() { }
void idle_force_powersave_in_1s() { }
+void idle_fps_en() { }
+void idle_fps_dis() { }
#endif
Should work if you call movie_crop_hack_disable() from ml_shutdown.
Firmware Version 2.0.3 incorporates the following fix:
Corrects a phenomenon in which when using the camera with the EF-S 18-135mm f/3.5-5.6 IS USM or EF 70-300mm f/4-5.6 IS II USM lens, even if lens aberration correction is set to "Enable", correction will not be applied.
Is there a possibility of follow focus like other cameras.
(I don't know if this is any new info to you guys but I found it quite interesting.)
I found out that JPEG buffer is almost unlimited* when shooting stills in video mode. Raw buffer depth is the same.
I know there is a crop(either 4:3 or 16:9) and file size is slightly smaller(around 5-10%) but it still doesn't explain to me why I can only get 3 JPEG in a row(without slowdown) in photo mode. Even with the lowest quality JPEGs! Maybe there is some logical reason and I'm just being dumb. Don't be harsh on me. xD
I don't know if this is any useful info for the development but I thought I would share this. :)
E: *I tested this a bit more. It is not quite unlimited as I first though but it's still much better than in photo mode. Buffer depth seems best in 4:3 video mode. I can get around 75 shots(shooting large jpegs) in a row without slowdown after formatting and reboot. After that I can get roughly 25 shot bursts. In 16:9 mode it seems to be slightly worse weirdly(bigger crop). I only have 40 MB/s card though, maybe it is better with faster card.
E2: Shooting medium or small size jpegs buffer seems almost unlimited. Got over 150 shots and I stopped myself. Didn't want to ruin my shutter any more. :D
Full manual control of the servo.
... Seems like the EOSM AF controls would work better for that kind of work. A light touch on the LCD is all that's needed to change the focus area, that's even better than on the C100.
Because in movie mode, the lens aberration only correct the peripheral illumination, chromatic does not.Oh I see... I knew I didn't think of something. I bet they even mention about that in Canon's manual. :-[
Correct peripheral illumination seem doesn't affect process speed, so leave it always enable.(EF-M 22mm has strong light fall-off)
In photo mode, disable chromatic aberration in Lens aberration correction will help, set L-size and low quality jpeg give me unlimited buffer.(with fast sd card like sandisk extreme pro)
Set higher ISO and NR also affect process speed.
Any reason to upgrade to 2.0.3? Saw that only 1 lens compatibility was added.
function event.keypress(key)
local lens_ok = false
if key == KEY.INFO then
repeat
lens_ok = lens.focus(-1,1,false)
until lens.dof_far > 100000
return false -- steal key for testing
end
end
move_flag = false
function test4key(key)
if key == KEY.INFO then
move_flag = true
return false -- steal key for testing
else
return true
end
end
function move(arg)
local lens_ok = false
if move_flag == true then
repeat
lens_ok = lens.focus(-1,1,false)
until lens.dof_far > 100000
move_flag = false
end
end
event.keypress = test4key
event.shoot_task = move
Is there any reason to climb a mountain other that because it is there?Oh, c'mon, really? :) :) :) ::) :D
OK I admit I'm stupid, have a lot going on in my life, and am still learning.
Oh, c'mon, really? :) :) :) ::) :D
Just saying that doing the firmware update just because it is a challenge and sharing it with the community is in the spirit of a hobby project like this.I agree, although you did not answer my question, or was the joke actually the answer, like nothing more? :)
...was the joke actually the answer...
Corrects a phenomenon in which when using the camera with the EF-S 18-135mm f/3.5-5.6 IS USM or EF 70-300mm f/4-5.6 IS II USM lens, even if lens aberration correction is set to "Enable", correction will not be applied.
Pretty much. That firmware update was done for several cameras but it doesn't give most users a good reason to install it.I love updates don't get me wrong, but given the age of the camera (launched in 2012) and the poor support Canon gave it, I'm rather uneasy to flash away.
BTW--one of the first things I tested was the shutter-bug and it is still there. Rats!
...That being said, is the downgrade procedure straight away (eg. I update to 2.0.3 and I don't like something, I just put 2.0.2 on the card and "update" ) ?
Of course @Licaon_Kter knows about charging batteries--he's gone through many charge cycles getting the EOSM to this stage in ML development.Battery at 100% no matter what!!!
Hi. What's the highest available video resolution when shooting Raw and h264 on Eos M?H.264 is [email protected] max, as Canon does
i noticed that in the latest build ther's no option to shoot in RAW, only in 3xH.264.Did you enabled the MLV_REC/MLV_SND modules first and restarted the camera, right?
H.264 is [email protected] max, as Canon does
RAW it depends, do test
...reset your Canon settings and delete the ML configuration file...
mlv_dump --black-fix=2047 --white-fix=15000 --cs2x2 --dng input.MLV- Frames comes out with bad white and black levels. Easily fixed with latest mlv_dump
mlv_dump --black-fix=2047 --white-fix=15000 --cs2x2 --dng input.MLVAlso added black/white level handling from mlv_dump menu inside cr2hdr.app.MagicLantern gives me Clean HDMI out
(and do I have to record with / on the camera?)
no time barrier while recording (or capturing the hdmi out signal), i.e. the 30 minute max recording time.
Does the latest build work nicely or any things I should better be aware of?
@a1ex -- saw your request to run the stubs API test from the selftest module, from the latest lua_fix
[Pass] dialog->type => 'DIALOG'
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
SW1(1,100)
[Pass] HALFSHUTTER_PRESSED => 0x1
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] is_play_mode() => 0x1
[FAIL] is_pure_play_photo_mode() => 0x0
[Pass] is_pure_play_movie_mode() => 0x0
[Pass] is_play_mode() => 0x1
[Pass] is_pure_play_photo_mode() => 0x0
[Pass] is_pure_play_movie_mode() => 0x0
[Pass] is_play_mode() => 0x1
[Pass] is_pure_play_photo_mode() => 0x0
[Pass] is_pure_play_movie_mode() => 0x1
[Pass] is_play_mode() => 0x1
[Pass] is_pure_play_photo_mode() => 0x0
[FAIL] is_pure_play_movie_mode() => 0x1
Hello,
I am not sure if there isn't an answer to my question on this thread already, but if I buy a Canon EOS M via Ebay, from Japan (which has only japanese and english languages), can I install ML on it? Is the japanese version compatible with ML?
Sorry if it is a dumb question, I tried to find the answer for about 2 hours using google, but I couldn't.
Thanks.
Sorry, your post was almost lost with all the recent testing.
Yes--One of my EOSM's was purchased from Japan via ebay and there was no problem installing Magic Lantern on it. Make sure it is an original EOS-M and not an EOS-M2, M3, M10 or M5.
On a side note, though it is possible to port ML to the M2 nobody, to my knowledge, has taken on that project. The M2 uses the same sensor as the 100D so the autofocus speed should be improved and it includes built-in Wi-Fi along with some other improvements. Distribution was limited and there are still few of these cameras in North America and Europe where most ML developers are located.
The camera still has a maximum time of 30 minutes before the power savings kicks in and turns off the display so you'll have to do a shutter half-press to keep it alive. The bad news is that the shutter half-press will also momentarily turn on the screen graphics.
Yo! Is it normal to have a lot of bitmap icons (exp. corr scale mostly, or exp iso) popping momentarily on top of ML settings screen?
And is it normal to have several self tests crash the system?
And is it ok to have temperatures over 50c constantly?
1. If I install ML on a SD card and only use vintage manual lenses and Efs lenses will my camera stay bug free?
2. If I use another SD card (without ML) when using my Efm zoom lens will my camera stay bug free?
...And if you use Sandisk Extreme PRO UHS-I cards 32GB or smaller, you'll never encounter the shutter-bug.
Does the using the 'correct' SD card really work?
Great yo know. As a stills photographer I'm not that interested in large and fast SD cards.It's not about fast, you'll still be limited by the camera interface, but in this case that brand of cards (and maybe those models exactly, as you can read in the "shutter bug issue") make the camera usable with ML.
Could you try filming crop_rec HDR H.264 in 60fps with that card. I keep getting a frame glitch here and there and maybe it,s card specific. A 10 second clip should do fine.
Tried to reproduce it but couldn't. Clear all the Canon settings and try it again. That's on the 4th wrench of the Canon menu.That fixed, I'm feeling a huge noob. Thanks!
Hello,
I am reeaally new to magic lantern, I installed it because we are going camping and I want to be able to do long exposures for astro shots. I have ML installed and working, but I cannot for the life of me work out how to dial up the bulb time past 5sec, every button I press in the ML menu when I have Bulb selected takes me to another menu, or the Q button just toggles between off and 5sec.
I am sure I am missing something really obvious, and it is frustrating the crap out of me given I can get 30 second exposures out of the standard options, yet I can't get longer than 5 out of ML.
I am running the latest nightly build.
Thanks for any help or advice.
Did you reset Canon settings too?
/* Some Hope Yet */
#undef FEATURE_TRAP_FOCUS
#undef FEATURE_FOLLOW_FOCUS
#undef FEATURE_RACK_FOCUS
#undef FEATURE_FOCUS_STACKING
/** Message queues **/
NSTUB(0xFFA88414 - RAM_OFFSET, msg_queue_count) // 0x1EE84 Above "!!!!!!! QUE Overflo"
NSTUB(0xFFA73C84 - RAM_OFFSET, msg_queue_create)
NSTUB(0xFFA883D4 - RAM_OFFSET, msg_queue_post) // 1EE44
NSTUB(0xFFA881E8 - RAM_OFFSET, msg_queue_receive) // 1EC58
NSTUB(0xFFA880D8 - RAM_OFFSET, msg_queue_create)
/** Interrupts **/
-NSTUB(0xFFAA775C - RAM_OFFSET, post_isr_hook)
-NSTUB(0xFFAA7758 - RAM_OFFSET, pre_isr_hook)
+NSTUB(0x3DD6C, post_isr_hook)
+NSTUB(0x3DD68, pre_isr_hook)
#define YUV422_LV_BUFFER_DISPLAY_ADDR (*(uint32_t*)(0x3E650+0x11c))
#define YUV422_LV_BUFFER_DISPLAY_ADDR (*(uint32_t*)(0x3E650+0x118))
Could this be what's missing for the so-called display filters? (you could try enabling them in internals.h, should be the same as on all other D5 models).
Raw video previews also depend on this backend, and also HDR video should no longer flicker while recording.:o
There's also FEATURE_MAGIC_ZOOM_FULL_SCREEN, but that one doesn't work on 700D/650D, so I don't have high hopes for the M.
...Problem with C-mount is that there are two versions and most seller cannot (or don't want to) differ between them, talking about C-mount and CS-mount, same thread but different flange distance (CS 12.5 mm, C 17.5 mm) so CS is pretty much unusable since it's impossible to focus it.
c mount lenses don't seem to focus to infinity though... at least mine don't .
... im still waiting for compressed raw. then we are talking better than a7sii in sharpness territory...
I have a used sigma 10-20mm f3.5 which works good for the price paid. Of course you will also need a canon ef converter to mount the lens.
I've got c mount lenses. 25,12.5,8.5 and 6mm. i think pretty much any of them will work in crop mode. 3x or 5x crop mode. i had a 4.5mm lens and that one even worked. i broke it though. c mount lenses don't seem to focus to infinity though... at least mine don't . i haven't made any modifications to them. also they are all over the place. I've got 1",3/4", 1/2" they all close focus no problem. wide angle infinity focus seems soft to me. not terrible though. more resolution and we would be in serious territory. im still waiting for compressed raw. then we are talking better than a7sii in sharpness territory. I've got one of those too. and sometimes i prefer the 100 dollar M to it.
CS isn't C. The CS lenses are designed for small surveillance cameras. You can use C mount lenses on a CS mount camera with an adapter but not vice-versa.
That looks fine, but it's way out of my price range (around $400 here), also with adapter it's not so light combo with EOS M anymore.Keep us posted on your results.
Could you elaborate on manufacturers of these lenses? I managed to find some from Tamron and Fujinon.
I don't say it is, i'm saying that the only difference is in flange distance, and some sellers do not make difference between C and CS mount, hint would be size of an image circle, 1/2" being borderline size (at least i understood that from wiki).
Anyway I ordered this Tamron 8mm for 2/3" sensor http://www.tamron-usa.com/IO/IndOp/prod/23fm08l.php (http://www.tamron-usa.com/IO/IndOp/prod/23fm08l.php) when it arives i'll do some tests and post results in case someone else is solving the same problem.
EDIT: mistype
I've been away from builds since early 2016. Have there been any big developments that are in either the nightly build or experimental builds that I should look into?Plenty: https://builds.magiclantern.fm/experiments.html
Ah yes, the shutter-bug. A few weeks ago I thought that maybe if we can come up with a different way of booting up the camera, like the AllocateMemory pool method, it would solve this issue. Sadly it didn't resolve the shutter-bug (http://www.magiclantern.fm/forum/index.php?topic=15895.msg187644#msg187644). The best work around I have found is to use a SanDisk Extreme PRO card that is 32GB or less.
(https://farm5.staticflickr.com/4382/36082769233_20b07676f2.jpg)
Anything over 32GB (SDXC cards) will most likely exhibit the bug. Other cards 32GB or less may work, some intermittently. Note that it doesn't have to do with the speed of the card because I've got an old and very slow Kodak 1GB card that works fine.
The shutter-bug is only present with EF-M zoom lenses. A quick, though annoying, "fix" is to break the lens/body by twisting the lens off and on while the camera is turned on. This kills the shutter-bug until the next time you restart the camera. There are other work arounds but if you use this card you'll never have to deal with it.
Welcome to the dreaded "EOS M Shutter Bug": https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug
Workaround for you and your August 1st version: Remove battery before mounting kit lens again.
I just have a Lexar Platinum ll 32GB 300x 40MB/s. Is there any benefit to having a faster SD card with this camera?
is there any working solution for focus pixels in mv720 3x3 footage?
#ifdef FEATURE_AUDIO_REMOTE_SHOT
#if defined(CONFIG_7D) || defined(CONFIG_6D) || defined(CONFIG_650D) || defined(CONFIG_700D) || defined(CONFIG_EOSM) || defined(CONFIG_100D) || defined(CONFIG_70D)
/* experimental for 7D now, has to be made generic */
static int last_audio_release_running = 0;
if(audio_release_running != last_audio_release_running)
{
last_audio_release_running = audio_release_running;
if(audio_release_running)
{
//Enable Audio IC In Photo Mode if off
if (!is_movie_mode())
{
SoundDevActiveIn(0);
}
}
}
#endif
Even when starting the camera in photo mode? (with the sound device likely disabled by Canon firmware)
Another possible bug on the sound side: does mlv_sound record sound with... global draw off?
Anyone else having issues with Advanced bracketing?I did reply to this in the other posting on the same subject by the same OP in the GH Q/A section but if it helps here.
My setup:
EOS-M with the latest nightly (magiclantern-Nightly.2017Sep15.EOSM202)
Manual mode, manual lens, 6exp 3ev from 1/4000.
Most of the times I get the expected exposure range:
1/4000
1/500
1/60
1/8
1"
8"
But not always.
Sometimes I'll even get more than 6 shot.
If I use Audio remoteshot (audio gain set to manual), I never get the expected range, just a bunch of random exposure values that changes every time:
1/4000
1/4000
1/500
1/500
1/500
128"
Or
1/4000
1/500
1/60
1/8
1/4000
1/4000
Or
1/30
1/4
1/30
1/30
127"
10"
Seems like a bug in the Advanced bracketing module, and using Audio remoteshot makes it worse.
Would someone please try it out, using at least 5 exposures?
Thanks!
I did reply to this in the other posting on the same subject by the same OP in the GH Q/A section but if it helps here.Yeah, saw that one, but as it may be an EOS-M specific issue, it might be useful to have it here too.
Did a quick test also with the 'M' and got in first 6 images at 3 stops. 320,320,40,40,40 and 40 second try I got 320,2500,40,40,1.6 and 1.6
Russ
Quote from: madzis there any working solution for focus pixels in mv720 3x3 footage?
Yes, I published the map files and they are being used in a few apps. I only tried it extensively in Danne's Switch (http://www.magiclantern.fm/forum/index.php?topic=15108.0) and it is working great.
Is there any other option for Windows user besides MLVP? Can mlv_dump do that?
P.S. Looks like I need to find my old laptop to install Linux+Switch on it :)
Extra question: Is it possible to get 48/50fps in RAW (resolution is not very important)? Mine tops at 31.something, may be I'm just doing it wrong.
Now how about that crop_rec focus pixel list for the 100D? Could it be added to fpm.sh?
As we know crop_rec footage should use a replacement list. A list that is only used in Switch atm for all I know.
Did I understand it correctly, that at this moment only Switch is able to fix focus pixels on crop_rec footage (720 3x3 on EOS-M in our case)?
Offtopic: Does 700d/100d manage to shoot 48/50fps RAW? I was planning to get a 50d...
Now how about that crop_rec focus pixel list for the 100D? Could it be added to fpm.sh?
See replies #1276 and #1277.I'm not sure if this suggestion was for my issue, but this is not the shutter bug problem. Also, I use the 22mm and a Tokina 12mm as my lenses. I can take photos in MF, just the half press AF is not working, nor is the scroll wheel, side buttons inside it, and the enter button in the center. Inside ML, I can't do anything, since I'm stuck in the white balance icon, and can't swipe out of it. I will try uninstalling tonight, but wanted to see if this issue had popped up before. It seems like I am stuck in MF, and with the scroll wheel locked out. Just no idea how I got there, or how to get out either.
Is it working without ML? Just pull out the card and see if it is working properly. Maybe your ML settings are corrupted? Delete the ML/SETTINGS folder from your SD card and try it again. I've had situations where my Canon settings were the problem, you can try resetting those too.Yes, even without a card my scroll wheel and the buttons on it are unresponsive. Clearing settings didn't do anything. Maybe I'll try updating the firmware to 2.03? Can I use ML with that version of firmware?
Yes, even without a card my scroll wheel and the buttons on it are unresponsive. Clearing settings didn't do anything. Maybe I'll try updating the firmware to 2.03? Can I use ML with that version of firmware?There is an experimental 2.0.3 version, but it's better to stay on 2.0.2.
There is an experimental 2.0.3 version, but it's better to stay on 2.0.2.Yes, resetting did not fix the problem. That's why I asked about the 2.0.3 upgrade. Can I upgrade, but revert to 2.0.2 if the upgrade fixes the problem? Of course, it could be a hardware issue?
Say that resetting CANON settings did not help?
Sounds more like a hardware issue.I was just typing that thought as you posted.
Upgrading the firmware is unlikely to help, but shouldn't hurt.
Russ
I haven't used rack focus on the EOSM, you will need to test this.
I do know that ML has difficulty driving native EOSM m lenses, i.e. it will drive EOS lenses via an adapter.
I have two Lua scripts running on my EOSM.
One is called the toggler, and it allows you to toggle between various ML states. That is you don't need to go into the ML menu.
The other is my focus bar, which gives you three killer features.
First, you are visually presented with the focus field between the near and far depth of fields.
Second, you can achieve an optimum focus when doing landscape work, which is a focus point between the HFD and infinity. The focus bar also gives you info on the defocus and diffraction blurs, so you can make focus decisions.
Thirdly, the focus bar allows you to focus bracket.
You can download and read about my scripts at photography.grayheron.net
Cheers
Garry
thanks for offering the lua scripts - can you tell me the compatible lenses for the FB? Tried with Canon EOS 70-300 IS USM - FB does not show up although the script is loaded.
[ GuiMainTask:ff4d5698 ] (04:03) -->Mirror start
...
[ DisplayMgr:ff129644 ] (82:03) TFT Command start
[ DisplayMgr:ff127de0 ] (82:01) SIO [0]:0x36
[ DisplayMgr:ff127de0 ] (82:01) SIO [1]:0x140
[ DisplayMgr:ff129684 ] (82:03) TFT Command end
...
[ GuiMainTask:00088c10 ] (04:03) Mirror finish
[ GuiMainTask:ff4d56f8 ] (04:03) -->Normal start
...
[ DisplayMgr:ff127de0 ] (82:01) SIO [0]:0x36
[ DisplayMgr:ff127de0 ] (82:01) SIO [1]:0x100
[ GuiMainTask:ff4d56c8 ] (04:03) -->Reverse start
[ DisplayMgr:ff127de0 ] (82:01) SIO [0]:0x36
[ DisplayMgr:ff127de0 ] (82:01) SIO [1]:0x1c0
static void run_test()
{
msleep(3000);
#ifdef CONFIG_5D3_113
void (*lcd_sio_init)() = (void *) 0xFF12D284;
void (*lcd_sio_write)(uint32_t * data, int size) = (void *) 0xFF12D1E0;
void (*lcd_sio_finish)(void * sio_obj) = (void *) 0xFF13BDC8;
void ** p_lcd_sio_obj = (void **) 0x246F0;
#endif
printf("LCD sio start\n");
lcd_sio_init();
lcd_sio_write((uint32_t[]) { 0x36, 0x140 }, 2);
lcd_sio_finish(*p_lcd_sio_obj);
printf("LCD sio finish\n");
}
Hi I'm new to Magic Lantern and so far finding it a pretty awesome hack and most of what I need seems to run perfectly. If I might add a suggestion/request...
I noticed there is the UpsideDown mode, which rotates the display 180 degrees. I was wondering if it wouldn't be difficult to also ad the option to flip the display vertically, so users of fixed LCD cameras such as the eosM could rig up a mirror to the bottom of the LCD for 'top down' shooting?
Similar to this...
(http://thumb.ibb.co/bPz5L6/index.jpg) (http://ibb.co/bPz5L6)
Register 0x6 seems to hold the key
And strange but true: After pressing "Don't click me!" screen does 6:04 flip+mirror, regardless if module is loaded or not.
Back on this topic, so far the best experience I'm having with the tft_regs module is on the EOSM.
Hi I'm new to Magic Lantern and so far finding it a pretty awesome hack and most of what I need seems to run perfectly. If I might add a suggestion/request...
I noticed there is the UpsideDown mode, which rotates the display 180 degrees. I was wondering if it wouldn't be difficult to also ad the option to flip the display vertically, so users of fixed LCD cameras such as the eosM could rig up a mirror to the bottom of the LCD for 'top down' shooting?
Similar to this...
(http://thumb.ibb.co/bPz5L6/index.jpg) (http://ibb.co/bPz5L6)
Googled and checked this forum for it, but cannot find any solution.
Am I missing sth? Pls help.
/* Some Hope Yet */
...
#undef FEATURE_FOLLOW_FOCUS
[youtube]http://youtu.be/YcKTqGJUTls[/youtube]
Tip - to post a YouTube video change the URL from https to http and enclose it in youtube tags like this:Code: [Select][youtube]http://youtu.be/YcKTqGJUTls[/youtube]
H.264 proxy has never been reliable on the EOSM or any other camera other than the 5D3. It would be wonderful on the EOSM because so far that is the only way we currently have to get it to record in mv1080 mode (http://www.magiclantern.fm/forum/index.php?topic=16608.0)--though it does a decent job with crop_rec mode.Thank you Dfort. Yes, I read all the MV1080 thread. But when you say not reliable, you mean with a low bitrate + 10 bits lossless test ? Is it not reliable because of the 40MB/s limit ? Don't you think that we can handle h264 proxy with low bitrate and 10 bit lossless in the 40MB/s limit ?
Try it and you’ll see what I mean.
Sent from my iPhone using Tapatalk
... This camera works best in Movie crop mode (a.k.a. mv1080crop or CROP_MODE_HACK). In fact that's the only mode where the camera will record in 23.976 fps without having to use the FPS override option. ...And just when i thought that I understand all different modes, new wild mode appears :)
Got it, thought you picked one up.
This camera works best in Movie crop mode (a.k.a. mv1080crop or CROP_MODE_HACK). In fact that's the only mode where the camera will record in 23.976 fps without having to use the FPS override option. What is also cool about mv1080crop mode is that you can use C-mount lenses and keep it a very small package, the VAF-filter isn't necessary and if you really want to experiment, Dual-ISO works quite well in this mode.
@12georgiadis:Thanks IDA_ML! It convinced me for a 100D!
"Do we record in 10 bits or lossless 10/12/14 bits for continuous ?"
I don't own the EOS M but the 100D which should be very similar and has the same card write speed. I can confirm that the 100D can record in the Movie Crop Mode (3xCrop) at:
1) 8...11 bit LL, 1800x1008 resolution @23,976 fps WITH SOUND !!! - CONTINUOUSLY
2) 12 bit LL, 1800x1008 resolution @23,976 fps WITH SOUND - for about 40 s.
3) 14 bit LL, 1800x1008 resolution @23,976 fps WITH SOUND - for about 14 s.
The recording times in #2 and #3 depend on the fine detail and whether or not there are very bright areas in the scene. With very contrasty scenes, underexposing by 0,5 to 1 stop may increase record times substantially. Dual ISO works very well in such situations. Video quality is fantastic! No VAF filter in Movie Crop Mode necessary!
If you can live with somewhat lower (1728x972) resolution, recording in #2 is continuous! If you do not underexpose, video quality at even ISO 6400 is perfectly usable!
The 100D used is so cheap at the moment that you could buy one to play around with just for fun. It is the perfect replacement of the 7D which is not ready yet for crop_4K and as a bonus it solves also your sound issue, (no h.264 proxy necessary, sound sync is perfect). You also have in-camera playback in color in the above three modes.
Get yourself a used 100D. You will not regret!
how do you do it?
when I was a kid I used to stick various objects into electrical outlets to see what would happen. That's pretty much it.
Just thought this one might be interesting for EOS M users:For EOS M, a long press on SET/Q can be made to open submenus, in the same way as a long joystick press opens the submenu on 50D/5D2/5D3/7D.
https://bitbucket.org/hudson/magic-lantern/pull-requests/722/eos-m-long-press-set-q-to-open-submenus/diff
If you can compile from source, please give it a try and report back.
make -C ../magic-lantern EOSM_install_qemu
Also, I just tried the latest Lua fix experimental, and I think I'm having a senior moment as Q doesn't work, i.e. it never has for me on the EOSM.
# platform/EOSM.202
hg up longpress -C
hg merge qemu
make clean
make install_qemu CONFIG_QEMU=y
- // Set up some dof info
- const uint64_t freq = 550; // mid vis diffraction freq in nm (use 850 if IR)
- const uint64_t imag = (fd-fl)/fl; // inverse of magnification (to keep as integer)
- const uint64_t diff = (244*freq*lens_info.aperture*(1+imag)/imag)/1000000; // Diffraction blur in microns
+ // Estimate diffraction
+ const uint64_t freq = 550; // mid vis diffraction freq in nm (use 850 if IR)
+ const uint64_t diff = (244*freq*lens_info.aperture/1000000; // Diffraction blur at infinity in tenths of a micronconst uint64_t diff = (244*freq*lens_info.aperture/1000000; // Diffraction blur at infinity in tenths of a micronconst uint64_t diff = (244*freq*lens_info.aperture/100000; // Diffraction blur at infinity in tenths of a micronconst uint64_t diff = (244*freq*lens_info.aperture/100000; // Diffraction blur at infinity in tenths of a micron@dfort: are you able to get Canon GUI on EOS M without loading autoexec.bin? If not, can you show me a log with "-d debugmsg" ?
[ DL:ff0d0b04 ] (00:03) [DL] executePreDL 1stDL
[ DL:ff0cfcc0 ] (00:01) [DL] SendSerialDataToDL : 0x2a85
[ DL:ff0cfcc4 ] (00:05) [DL] localCreateSerialIOChannelForDLIC
[ PowerMgr:ff0d050c ] (00:03) [DL] EndChangeFreqCBR 0x46370 750
[ DL:ff0cfda0 ] (00:05) [DL] localCreateSerialIOChannelForDLIC
[ DL:ff0cfda0 ] (00:05) [DL] localCreateSerialIOChannelForDLIC
[ DL:ff0d0b58 ] (00:03) [DL] executePreDL Max:0x0,Min:0x0,Result:0x0
[ DL:ff0d0b74 ] (00:06) [DL] ####################################
[ DL:ff0d0b84 ] (00:06) [DL] ########## DL ERROR!!!!! ###########
[ DL:ff0d0b94 ] (00:06) [DL] ####################################
89: 447.744 ERROR [DL] ####################################
90: 447.744 ERROR [DL] ########## DL ERROR!!!!! ###########
91: 447.744 ERROR [DL] ####################################
[ DL:ff0d0bf0 ] (00:03) [DL] executePreDL 2ndDL
[ DL:ff0cfcc0 ] (00:01) [DL] SendSerialDataToDL : 0x2a85
[ DL:ff0cfcc4 ] (00:05) [DL] localCreateSerialIOChannelForDLIC
[ PowerMgr:ff0d050c ] (00:03) [DL] EndChangeFreqCBR 0x46370 750
[ DL:ff0cfda0 ] (00:05) [DL] localCreateSerialIOChannelForDLIC
[ DL:ff0cfda0 ] (00:05) [DL] localCreateSerialIOChannelForDLIC
[ DL:ff0d0c44 ] (00:03) [DL] executePreDL Max:0x0,Min:0x0,Result:0x0
[ DL:ff0d0c60 ] (00:06) [DL] ####################################
[ DL:ff0d0c70 ] (00:06) [DL] ########## DL ERROR!!!!! ###########
[ DL:ff0d0c80 ] (00:06) [DL] ####################################
98: 963.328 ERROR [DL] ####################################
99: 963.328 ERROR [DL] ########## DL ERROR!!!!! ###########
100: 963.328 ERROR [DL] ####################################
const uint64_t diff = (244*freq*lens_info.aperture/100000; // Diffraction blur at infinity in tenths of a micron
@dfort: are you able to get Canon GUI on EOS M without loading autoexec.bin? If not, can you show me a log with "-d debugmsg" ?
./run_canon_fw.sh EOSM,firmware=boot=1 -s -S &
arm-none-eabi-gdb -x EOSM/patches.gdb -ex quit
DebugMsg=0x40D4 (from GDB script)
Lockdown read 0
Lockdown read 0
Lockdown read 1
Lockdown read 1
Lockdown read 2
Lockdown read 2
Lockdown read 3
Lockdown read 3
Lockdown read 4
Lockdown read 4
00000000 - 00000FFF: eos.tcm_code
40000000 - 40000FFF: eos.tcm_data
00001000 - 1FFFFFFF: eos.ram
40001000 - 5FFFFFFF: eos.ram_uncached
F0000000 - F0FFFFFF: eos.rom0
F1000000 - F1FFFFFF: eos.rom0_mirror
F2000000 - F2FFFFFF: eos.rom0_mirror
F3000000 - F3FFFFFF: eos.rom0_mirror
F4000000 - F4FFFFFF: eos.rom0_mirror
F5000000 - F5FFFFFF: eos.rom0_mirror
F6000000 - F6FFFFFF: eos.rom0_mirror
F7000000 - F7FFFFFF: eos.rom0_mirror
F8000000 - F8FFFFFF: eos.rom1
F9000000 - F9FFFFFF: eos.rom1_mirror
FA000000 - FAFFFFFF: eos.rom1_mirror
FB000000 - FBFFFFFF: eos.rom1_mirror
FC000000 - FCFFFFFF: eos.rom1_mirror
FD000000 - FDFFFFFF: eos.rom1_mirror
FE000000 - FEFFFFFF: eos.rom1_mirror
FF000000 - FFFFFFFF: eos.rom1_mirror
C0000000 - DFFFFFFF: eos.iomem
[EOS] loading './EOSM/ROM0.BIN' to 0xF0000000-0xF0FFFFFF
[EOS] loading './EOSM/ROM1.BIN' to 0xF8000000-0xF8FFFFFF
[EOS] loading './EOSM/SFDATA.BIN' as serial flash, size=0x800000
[MPU] warning: non-empty spell #30 (PROP 80030019) has duplicate(s): #34
[MPU] warning: non-empty spell #40 (PROP_VIDEO_MODE) has duplicate(s): #41
[MPU] Available keys:
- Arrow keys : Navigation
- [ and ] : Main dial (top scrollwheel)
- SPACE : SET
- DELETE : guess (press only)
- M : MENU (press only)
- P : PLAY (press only)
- I : INFO/DISP (press only)
- L : LiveView (press only)
- Shift : Half-shutter
- 0/9 : Mode dial (press only)
- B : Open battery door
- C : Open card door
- F10 : Power down switch
- F1 : show this help
Setting BOOTDISK flag to FFFFFFFF
0xffff0000 in ?? ()
++macro define CURRENT_TASK ((int)0xFFFFFFFF)
++macro define CURRENT_ISR ((int)0xFFFFFFFF)
++macro define RTC_VALID_FLAG ((int)0xFFFFFFFF)
++macro define NUM_CORES 1
++macro define PRINT_CALLSTACK 0
++macro define MEM(x) (*(unsigned int*)(x))
++set pagination off
++set output-radix 16
++define hook-quit
++define KRED
++define KCYN
++define KBLU
++define KGRN
++define KYLW
++define KRESET
++macro define CURRENT_TASK_NAME (((int*)CURRENT_TASK)[0] ? ((char***)CURRENT_TASK)[0][9] : CURRENT_TASK)
++define print_callstack
++define print_current_location
++define print_current_location_with_callstack
++define print_formatted_string
++define DebugMsg_log
++define DebugMsg1_log
++define printf_log
++define task_create_log
++define task_switch_log
++define msleep_log
++define assert_log
++define assert0_log
++define create_semaphore_log
++define delete_semaphore_log
++define print_sem_name
++define take_semaphore_log
++define give_semaphore_log
++define create_msg_queue_log
++define print_mq_name
++define post_msg_queue_log
++define try_receive_msg_queue_log
++define receive_msg_queue_log
++define register_interrupt_log
++define register_func_log
++define mpu_decode
++define mpu_send_log
++define mpu_recv_log
++define mpu_analyze_recv_data_log
++define prop_lookup_maybe_log
++define mpu_prop_lookup_log
++define prop_print_data
++define prop_request_change_log
++define prop_deliver_log
++define try_expand_ram_struct
++define try_post_event_log
++define delayed_call_print_name
++define delayed_call_log
++define SetTimerAfter_log
++define SetHPTimerAfterNow_log
++define SetHPTimerNextTick_log
++define CancelTimer_log
++define engine_resource_description
++define engine_resources_list
++define CreateResLockEntry_log
++define LockEngineResources_log
++define AsyncLockEngineResources_log
++define UnLockEngineResources_log
++define StartEDmac_log
++define SetEDmac_log
++define print_date_time
++define set_date_time
++define load_default_date_time_log
++define rtc_read_log
++define rtc_write_log
++define CreateStateObject_log
++define state_transition_log
++define log_result
++define generic_log
++define generic_log_with_result
FFFF0800: MCR p15,0,Rd,cr9,cr1,0: XSCALE_LOCK_ICACHE_LINE <- 0x40000006 (40000000 - 40000FFF, 0x1000)
FFFF094C: MRC p15,0,Rd,cr1,cr0,0: SCTLR -> 0x2078
FFFF094C: MCR p15,0,Rd,cr1,cr0,0: SCTLR <- 0x12078
FFFF4604: MCR p15,0,Rd,cr6,cr0,0: 946_PRBS0 <- 0x3F (00000000 - FFFFFFFF, 0x100000000)
FFFF460C: MCR p15,0,Rd,cr6,cr1,0: 946_PRBS1 <- 0x3D (00000000 - 7FFFFFFF, 0x80000000)
FFFF4614: MCR p15,0,Rd,cr6,cr2,0: 946_PRBS2 <- 0xE0000039 (E0000000 - FFFFFFFF, 0x20000000)
FFFF461C: MCR p15,0,Rd,cr6,cr3,0: 946_PRBS3 <- 0xC0000039 (C0000000 - DFFFFFFF, 0x20000000)
FFFF4624: MCR p15,0,Rd,cr6,cr4,0: 946_PRBS4 <- 0xFF00002F (FF000000 - FFFFFFFF, 0x1000000)
FFFF462C: MCR p15,0,Rd,cr6,cr5,0: 946_PRBS5 <- 0x37 (00000000 - 0FFFFFFF, 0x10000000)
FFFF4634: MCR p15,0,Rd,cr6,cr6,0: 946_PRBS6 <- 0xF700002F (F7000000 - F7FFFFFF, 0x1000000)
FFFF463C: MCR p15,0,Rd,cr2,cr0,0: DCACHE_CFG <- 0x70
FFFF4644: MCR p15,0,Rd,cr3,cr0,0: DACR <- 0x70
FFFF4648: MCR p15,0,Rd,cr2,cr0,1: ICACHE_CFG <- 0x70
FFFF464C: MCR p15,0,Rd,cr5,cr0,0: DATA_AP <- 0x3FFF
FFFF4654: MCR p15,0,Rd,cr5,cr0,1: INSN_AP <- 0x3FFF
FFFF4658: MRC p15,0,Rd,cr1,cr0,0: SCTLR -> 0x12078
FFFF4658: MCR p15,0,Rd,cr1,cr0,0: SCTLR <- 0xC001307D
FFFF095C: MCR p15,0,Rd,cr9,cr1,1: XSCALE_UNLOCK_ICACHE <- 0x6 (00000000 - 00000FFF, 0x1000)
FFFF095C: MRC p15,0,Rd,cr1,cr0,0: SCTLR -> 0xC001307D
FFFF095C: MCR p15,0,Rd,cr1,cr0,0: SCTLR <- 0xC005307D
FFFF098C: MRC p15,0,Rd,cr1,cr0,0: SCTLR -> 0xC005307D
FFFF098C: MCR p15,0,Rd,cr1,cr0,0: SCTLR <- 0xC005107D
MID=0xEC(fact_area=0xEC)
SD: CMD12 in a wrong state
[SDIO] Error
SD: CMD12 in a wrong state
[SDIO] Error
SD LOAD OK.
Open file for read : AUTOEXEC.BIN
SD: CMD12 in a wrong state
[SDIO] Error
SD: CMD12 in a wrong state
[SDIO] Error
File size : 0x6BFC0
Now jump to AUTOEXEC.BIN!!
0010E408: MRC p15,0,Rd,cr1,cr0,0: SCTLR -> 0xC005107D
0010E408: MCR p15,0,Rd,cr1,cr0,0: SCTLR <- 0xC005107D
[boot] copy_and_restart 0x9e1e0 (647648)
[BOOT] changing user_mem_start from 0x9e1c8 (647624) to 0x11d440 (1168448)
[BOOT] changing init_task from 0xff0c5484 (-15969148) to 0x9e67c (648828)
[BOOT] installing task dispatch hook at 0x3dd60 (253280)
[****] Starting task 9e67c(0) init
[BOOT] expecting armlib to overwrite E5CC8: FBFD2 (task id 20002)
[BOOT] autoexec.bin loaded at 9E1E0 - 11D440.
[BOOT] reserved 520800 bytes for ML (used 520800)
K331 READY
64K Sector FROM From BL 0xec
[SF] InstallSerialFlash 4 0xc022c0d4 0x0 0x800000 1
[SF] Bufcon Base 0xc022c0d4
SerialFlash Initialize
[BOOT] E5CC8 now contains 0, restoring FBFD2.
[****] Starting task ff0f34a4(47e82c) Startup
[****] Starting task ff0c357c(0) Startup2
[DMA1] Copy [0xF80A0000] -> [0x40540200], length [0x00000F84], flags [0x00030001]
[DMA1] OK
[DMA1] Copy [0xF8F20000] -> [0x40541400], length [0x0001132C], flags [0x00030001]
[DMA1] OK
[****] Starting task ff0c28c8(0) TaskMain
[****] Starting task 22138(47e530) DbgMgr
0: 13.056 [STARTUP]
K331 ICU Firmware Version 2.0.2 ( 9.9.8 )
8: 13.824 [PROPAD] SerialFlash Packages!! 0x340000
[****] Starting task ff341390(0) PowerMgr
[EEPROM-DMA]! [0x340000] -> [0x40480000] (0xBD820 bytes)
[DMA1] Copy [0xF8F60000] -> [0x40561600], length [0x0001AEDC], flags [0x00030001]
[DMA1] OK
[EEPROM-DMA]! [0x340000] -> [0x40480000] (0x0 bytes)
[DMA1] Copy [0xF8060000] -> [0x40581700], length [0x00000D2C], flags [0x00030001]
[DMA1] OK
12: 19.200 [PROPAD] SerialFlash Packages!! 0x7
14: 19.200 [PROPAD] PROPAD_CreateFROMPropertyHandle DRAMAddr 0x4fe00000
15: 19.456 [PROPAD] SerialFlash Packages!! 0x10000
[****] Starting task 22138(5a47cc) PropMgr
[EEPROM-DMA]! [0x10000] -> [0x4FE00000] (0x191570 bytes)
[MPU] Received: 06 04 02 00 00 00 (Init - spell #1)
[MPU] Sending : 50 4e 02 0e 02 02 01 01 00 00 00 60 00 00 00 19 64 00 00 00 00 21 00 00 06 04 00 00 06 04 00 00 06 04 00 00 00 00 00 00 65 28 00 00 00 00 00 00 00 00 00 00 00 00 80 48 78 48 00 03 03 01 00 00 00 00 02 01 00 00 00 01 00 00 00 00 03 00 01 00 (Mode group)
[****] Starting task ff0d0d68(0) DL
[****] Starting task 22138(5aee04) EventMgr
[****] Starting task ff0cb890(0) HotPlug
17: 20.992 [STARTUP] InitializeIntercom
18: 20.992 [STARTUP] InitializeIntercom End(0x0)
28: 23.296 [DL] dlMain : Start
31: 23.296 [DL] PROP_ACTIVE_SWEEP_MODE (1)
[MPU] Received: 0a 08 03 57 10 31 00 01 00 00 (unknown - PROP 8003005E)
[MPU] Sending : 24 23 02 0d 00 00 00 00 01 00 00 00 00 01 00 00 00 01 02 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 (Card group)
[MPU] Received: 08 06 00 00 02 0e 00 00 (Complete WaitID = 0x80000001 Mode group - spell #2)
[MPU] Sending : 28 27 02 0f 01 00 00 10 01 01 00 00 00 00 00 00 00 00 00 00 00 18 00 00 00 0c 00 00 00 00 00 00 00 02 00 00 00 01 01 00 (Movie group)
[MPU] Sending : 3c 3a 02 10 00 00 00 00 00 00 01 00 00 00 00 ff 00 00 ff 00 ff ff ff ff ff ff ff ff 00 00 00 00 00 01 ff 00 00 02 01 01 00 03 00 01 00 04 00 00 01 05 00 01 01 00 01 00 00 3f 00 00 (AF group)
[MPU] Sending : 3e 3c 02 11 01 ff 01 00 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 28 00 ff 00 00 ff 00 ff ff ff ff ff ff ff ff 00 00 00 (AF2 group)
[MPU] Sending : 0a 08 01 6e 80 48 00 00 00 00 (PROP_ISO_RANGE)
[MPU] Sending : 08 06 01 0b 00 00 00 00 (PROP_AEB)
[MPU] Sending : 06 05 01 76 00 00 (PROP_SILENT_CONTROL_SETTING)
[MPU] Sending : 06 05 01 71 00 00 (PROP_AF_METHOD_SELECT_FOCUS_AREA)
[MPU] Sending : 06 05 01 7e 00 00 (PROP_GPS_COMPAS_SELECT)
[MPU] Sending : 06 05 01 7c 00 00 (PROP_GPS_AUTO_TIME_SETTING)
[MPU] Sending : 0a 08 01 85 00 00 00 01 00 00 (PROP_GIS_SETTING)
[MPU] Sending : 08 06 01 47 0a 02 00 00 (PROP_SELFTIMER_CONTINUOUS_NUM)
[MPU] Sending : 06 05 01 7b 01 00 (PROP_CONTINUOUS_AF)
[MPU] Sending : 08 06 01 57 00 00 00 00 (PROP_BUILTIN_STROBO_MODE)
[MPU] Sending : 06 05 01 86 00 00 (PROP 8004004A)
[MPU] Sending : 06 05 01 87 00 00 (PROP 8004004B)
[MPU] Sending : 06 05 01 8d 00 00 (PROP 80040050)
[MPU] Sending : 06 05 01 8e 00 00 (PROP_GPSLOG_SETTING)
[MPU] Sending : 10 0e 01 8f 00 00 00 00 00 00 00 00 00 00 00 00 (PROP_LV_CFILTER)
[MPU] Sending : 06 05 01 90 00 00 (PROP_WIFI_SETTING)
[MPU] Sending : 06 05 01 8b 00 00 (PROP 8004004E)
[MPU] Sending : 08 06 01 91 00 00 00 00 (PROP_BUILTINGPS_PINPOINTING_INTERVAL_SETTING)
[MPU] Sending : 06 05 01 98 00 00 (PROP 80040056)
[MPU] Sending : 08 06 01 88 07 08 00 00 (PROP 8000004F)
[MPU] Sending : 06 05 03 37 00 00 (PROP_MIRROR_DOWN_IN_MOVIE_MODE)
[MPU] Sending : 06 05 01 92 07 00 (PROP_IMAGE_ASPECT_RATIO)
[MPU] Sending : 0e 0c 02 04 08 00 00 00 00 00 00 01 00 00 (PROP_CFN)
[MPU] Sending : 16 14 01 61 00 09 d1 3e 00 00 00 00 ff e7 ff ff 00 0a 26 fe 00 00 (PROP 80040027)
[MPU] Sending : 0a 08 03 2f 00 00 00 00 00 00 (PROP_SPECIAL_OPTION)
[MPU] Sending : 0a 08 03 2f 00 00 00 00 00 00 (PROP_SPECIAL_OPTION)
[MPU] Sending : 06 05 03 20 01 00 (PROP_STARTUP_CONDITION)
[MPU] Sending : 0c 0b 03 42 00 00 00 00 00 00 00 00 (PROP_LED_LIGHT)
[MPU] Sending : 62 61 02 12 01 20 50 00 f0 00 11 00 37 91 77 1a 00 00 ff 00 00 00 00 00 00 00 01 f8 96 00 00 00 00 00 00 01 f8 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 23 43 23 00 00 00 00 00 00 00 10 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (Lens group)
[MPU] Sending : 06 05 03 05 02 00 (PROP_POWER_LEVEL)
[MPU] Sending : 06 05 04 06 05 00 (PROP_DEFAULT_LV_MANIP)
[MPU] Sending : 06 05 01 97 00 01 (PROP 8003006F)
[MPU] Sending : 06 05 04 06 05 00 (PROP_DEFAULT_LV_MANIP)
[MPU] Received: 08 06 00 00 01 97 00 00 (Complete WaitID = 0x8003006F PROP 8003006F - spell #3)
[MPU] Sending : 06 05 04 06 05 00 (PROP_DEFAULT_LV_MANIP)
[EEPROM-DMA]! [0x10000] -> [0x4FE00000] (0x0 bytes)
67: 42.240 [PROPAD] SerialFlash Packages!! 0x7
Can someone guide me on how to recreate shutterbug?
I still can't get to the GUI much less the ML menus on the EOSM in QEMU.
hist.type = 1
zebra.colorspace = 0
# remap the PLAY button (P) to submenu key in ML
break *0xFF0CC6EC
commands
silent
set $r4 = -0xFFFE
set $pc = 0xFF0CC6F0
c
end
./run_canon_fw.sh EOSM,firmware=boot=0 -s -S &
arm-none-eabi-gdb -x EOSM/patches.gdb
DebugMsg=0x40D4 (from GDB script)
Lockdown read 0
Lockdown read 0
Lockdown read 1
Lockdown read 1
Lockdown read 2
Lockdown read 2
Lockdown read 3
Lockdown read 3
Lockdown read 4
Lockdown read 4
00000000 - 00000FFF: eos.tcm_code
40000000 - 40000FFF: eos.tcm_data
00001000 - 1FFFFFFF: eos.ram
40001000 - 5FFFFFFF: eos.ram_uncached
F0000000 - F0FFFFFF: eos.rom0
F1000000 - F1FFFFFF: eos.rom0_mirror
F2000000 - F2FFFFFF: eos.rom0_mirror
F3000000 - F3FFFFFF: eos.rom0_mirror
F4000000 - F4FFFFFF: eos.rom0_mirror
F5000000 - F5FFFFFF: eos.rom0_mirror
F6000000 - F6FFFFFF: eos.rom0_mirror
F7000000 - F7FFFFFF: eos.rom0_mirror
F8000000 - F8FFFFFF: eos.rom1
F9000000 - F9FFFFFF: eos.rom1_mirror
FA000000 - FAFFFFFF: eos.rom1_mirror
FB000000 - FBFFFFFF: eos.rom1_mirror
FC000000 - FCFFFFFF: eos.rom1_mirror
FD000000 - FDFFFFFF: eos.rom1_mirror
FE000000 - FEFFFFFF: eos.rom1_mirror
FF000000 - FFFFFFFF: eos.rom1_mirror
C0000000 - DFFFFFFF: eos.iomem
[EOS] loading './EOSM/ROM0.BIN' to 0xF0000000-0xF0FFFFFF
[EOS] loading './EOSM/ROM1.BIN' to 0xF8000000-0xF8FFFFFF
[EOS] loading './EOSM/SFDATA.BIN' as serial flash, size=0x800000
[MPU] warning: non-empty spell #30 (PROP 80030019) has duplicate(s): #34
[MPU] warning: non-empty spell #40 (PROP_VIDEO_MODE) has duplicate(s): #41
[MPU] Available keys:
- Arrow keys : Navigation
- [ and ] : Main dial (top scrollwheel)
- SPACE : SET
- DELETE : guess (press only)
- M : MENU (press only)
- P : PLAY (press only)
- I : INFO/DISP (press only)
- Q : guess
- L : LiveView (press only)
- Shift : Half-shutter
- 0/9 : Mode dial (press only)
- V : Movie mode (press only)
- B : Open battery door
- C : Open card door
- F10 : Power down switch
- F1 : show this help
Setting BOOTDISK flag to 0
0xffff0000 in ?? ()
++macro define CURRENT_TASK ((int)0xFFFFFFFF)
++macro define CURRENT_ISR ((int)0xFFFFFFFF)
++macro define RTC_VALID_FLAG ((int)0xFFFFFFFF)
++macro define NUM_CORES 1
++macro define PRINT_CALLSTACK 0
++macro define MEM(x) (*(unsigned int*)(x))
++set pagination off
++set output-radix 16
++define hook-quit
++define KRED
++define KCYN
++define KBLU
++define KGRN
++define KYLW
++define KRESET
++macro define CURRENT_TASK_NAME (((int*)CURRENT_TASK)[0] ? ((char***)CURRENT_TASK)[0][9] : CURRENT_TASK)
++define print_callstack
++define print_current_location
++define print_current_location_with_callstack
++define print_formatted_string
++define DebugMsg_log
++define DebugMsg1_log
++define printf_log
++define task_create_log
++define task_switch_log
++define msleep_log
++define assert_log
++define assert0_log
++define create_semaphore_log
++define delete_semaphore_log
++define print_sem_name
++define take_semaphore_log
++define give_semaphore_log
++define create_msg_queue_log
++define print_mq_name
++define post_msg_queue_log
++define try_receive_msg_queue_log
++define receive_msg_queue_log
++define register_interrupt_log
++define register_func_log
++define mpu_decode
++define mpu_send_log
++define mpu_recv_log
++define mpu_analyze_recv_data_log
++define prop_lookup_maybe_log
++define mpu_prop_lookup_log
++define prop_print_data
++define prop_request_change_log
++define prop_deliver_log
++define try_expand_ram_struct
++define try_post_event_log
++define delayed_call_print_name
++define delayed_call_log
++define SetTimerAfter_log
++define SetHPTimerAfterNow_log
++define SetHPTimerNextTick_log
++define CancelTimer_log
++define engine_resource_description
++define engine_resources_list
++define CreateResLockEntry_log
++define LockEngineResources_log
++define AsyncLockEngineResources_log
++define UnLockEngineResources_log
++define StartEDmac_log
++define SetEDmac_log
++define print_date_time
++define set_date_time
++define load_default_date_time_log
++define rtc_read_log
++define rtc_write_log
++define CreateStateObject_log
++define state_transition_log
++define log_result
++define generic_log
++define generic_log_with_result
FFFF0800: MCR p15,0,Rd,cr9,cr1,0: XSCALE_LOCK_ICACHE_LINE <- 0x40000006 (40000000 - 40000FFF, 0x1000)
FFFF094C: MRC p15,0,Rd,cr1,cr0,0: SCTLR -> 0x2078
FFFF094C: MCR p15,0,Rd,cr1,cr0,0: SCTLR <- 0x12078
FFFF4604: MCR p15,0,Rd,cr6,cr0,0: 946_PRBS0 <- 0x3F (00000000 - FFFFFFFF, 0x100000000)
FFFF460C: MCR p15,0,Rd,cr6,cr1,0: 946_PRBS1 <- 0x3D (00000000 - 7FFFFFFF, 0x80000000)
FFFF4614: MCR p15,0,Rd,cr6,cr2,0: 946_PRBS2 <- 0xE0000039 (E0000000 - FFFFFFFF, 0x20000000)
FFFF461C: MCR p15,0,Rd,cr6,cr3,0: 946_PRBS3 <- 0xC0000039 (C0000000 - DFFFFFFF, 0x20000000)
FFFF4624: MCR p15,0,Rd,cr6,cr4,0: 946_PRBS4 <- 0xFF00002F (FF000000 - FFFFFFFF, 0x1000000)
FFFF462C: MCR p15,0,Rd,cr6,cr5,0: 946_PRBS5 <- 0x37 (00000000 - 0FFFFFFF, 0x10000000)
FFFF4634: MCR p15,0,Rd,cr6,cr6,0: 946_PRBS6 <- 0xF700002F (F7000000 - F7FFFFFF, 0x1000000)
FFFF463C: MCR p15,0,Rd,cr2,cr0,0: DCACHE_CFG <- 0x70
FFFF4644: MCR p15,0,Rd,cr3,cr0,0: DACR <- 0x70
FFFF4648: MCR p15,0,Rd,cr2,cr0,1: ICACHE_CFG <- 0x70
FFFF464C: MCR p15,0,Rd,cr5,cr0,0: DATA_AP <- 0x3FFF
FFFF4654: MCR p15,0,Rd,cr5,cr0,1: INSN_AP <- 0x3FFF
FFFF4658: MRC p15,0,Rd,cr1,cr0,0: SCTLR -> 0x12078
FFFF4658: MCR p15,0,Rd,cr1,cr0,0: SCTLR <- 0xC001307D
FFFF095C: MCR p15,0,Rd,cr9,cr1,1: XSCALE_UNLOCK_ICACHE <- 0x6 (00000000 - 00000FFF, 0x1000)
FFFF095C: MRC p15,0,Rd,cr1,cr0,0: SCTLR -> 0xC001307D
FFFF095C: MCR p15,0,Rd,cr1,cr0,0: SCTLR <- 0xC005307D
FFFF098C: MRC p15,0,Rd,cr1,cr0,0: SCTLR -> 0xC005307D
FFFF098C: MCR p15,0,Rd,cr1,cr0,0: SCTLR <- 0xC005107D
MID=0xEC(fact_area=0xEC)
K331 READY
64K Sector FROM From BL 0xec
[SF] InstallSerialFlash 4 0xc022c0d4 0x0 0x800000 1
[SF] Bufcon Base 0xc022c0d4
SerialFlash Initialize
[DMA1] Copy [0xF8099000] -> [0x40540200], length [0x00000F84], flags [0x00030001]
[DMA1] OK
[DMA1] Copy [0xF8F00000] -> [0x40541400], length [0x0001132C], flags [0x00030001]
[DMA1] OK
[EEPROM-DMA]! [0x340000] -> [0x40480000] (0xBD820 bytes)
0: 22.528 [STARTUP]
K331 ICU Firmware Version 2.0.2 ( 9.9.8 )
6: 26.112 [PROPAD] SerialFlash Packages!! 0x340000
[DMA1] Copy [0xF8F60000] -> [0x40561600], length [0x0001AEDC], flags [0x00030001]
[DMA1] OK
[EEPROM-DMA]! [0x340000] -> [0x40480000] (0x0 bytes)
[DMA1] Copy [0xF8060000] -> [0x40581700], length [0x00003B24], flags [0x00030001]
[DMA1] OK
10: 34.304 [PROPAD] SerialFlash Packages!! 0x7
12: 34.560 [PROPAD] PROPAD_CreateFROMPropertyHandle DRAMAddr 0x4fe00000
13: 35.072 [PROPAD] SerialFlash Packages!! 0x10000
[EEPROM-DMA]! [0x10000] -> [0x4FE00000] (0x191570 bytes)
[EEPROM-DMA]! [0x10000] -> [0x4FE00000] (0x0 bytes)
[MPU] Received: 06 04 02 00 00 00 (Init - spell #1)
[MPU] Sending : 50 4e 02 0e 02 02 01 01 00 00 00 60 00 00 00 19 64 00 00 00 00 21 00 00 06 04 00 00 0