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)
Thanks a1ex //Audionut.
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.
(I have not tried the nightly yet, but my own local compile from a few nights ago works for me)
Finally got a chance to test the nightly. It works for me, with a couple of bugs the I plan to work on. The canon menus seem to briefly overlay the ML menus during things like half shutter presses and autofocus face recognition, but this does not seem to affect taking pictures or video. Also, if you switch the camera off when in 3x crop movie mode and change to a card without ML, there is no way to go back to regular movie mode without rebooting from a ML card and changing it back to uncropped movie mode.
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.
Quote from: jordancolburn on December 30, 2013, 10:21:20 PM
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)
Hi, I'm new here. I've been using ML on my T2i for over two years now. So when I got my EOS-M last month I was elated to know that there was ML for it. I do mostly video with my cameras and audio controls are the most important features to me. Is there a build that has the controls featured on the homepage EOS-M pic?
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.
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.
Hope to see more coming on in the coming days, weeks and months. Thank you for the great work.
A fan of all ML ;)
Quote from: Canon eos m on December 31, 2013, 12:45:52 PM
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? :)
Quote from: Oswald on December 31, 2013, 01:54:20 PM
How you make it? Video? :)
Not difficult. H.264 will record as your camera normally should record.
Go to the ML video interface. Keep RAW recording off. Put the camera in video mode by choosing this option on the dial on top left of the camera. Push the red record button and you will have recorded both video and audio.
Play around with the settings a bit. Choosing VBR and higher bit rates will improve the video quality substantially.
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.
Quote from: Oswald on December 31, 2013, 01:54:20 PM
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.
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.
Quote from: jordancolburn on December 31, 2013, 03:59:55 PM
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.
Quote from: gary2013 on December 31, 2013, 03:56:39 PM
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.
Quote from: gary2013 on December 31, 2013, 03:59:59 PM
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.
Quote from: Canon eos m on December 31, 2013, 12:45:52 PM
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.
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.
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.
Quote from: gary2013 on December 31, 2013, 05:23:14 AM
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'll look into the shutter display. I never tried it, but I don't think headphone was ever working, even on TL.
Quote from: jordancolburn on December 31, 2013, 04:37:13 PM
I'll look into the shutter display. I never tried it, but I don't think headphone was ever working, even on TL.
I forgot to say the shutter "menu settings", not the main display screen.
Hi all,
I tryed some versions of PDR but no one seems to work, where I can find a correct PDR for this eos-ml version?
Thanks,
Tom
Quote from: jordancolburn on December 30, 2013, 10:21:20 PM
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)
Did you figure out the shutter bug?
Quote from: tob on January 01, 2014, 10:12:10 PM
Did you figure out the shutter bug?
No, I'm not sure I've seen any steps to reproduce it, and I haven't experienced it myself.
Quote from: gary2013 on December 31, 2013, 08:15:42 PM
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.
Keep up the good work.
You have rekindled my joy in using the EOSM.
Like I said before, the 3x mode on H.264 is fantastic. The quality is almost cinema grade - better than the RAW output on my 5d Mark3 - or am I dreaming?
After using the EOSM these past few days, I have to really force myself to pick up my 5DM3 for anything at all.
One wish is to see the pinkdot issue vanish magically (w/o having to use the PDR).
Second, when recording on VBR mode at -16 bit rate, the first few videos are reasonably long (about 1 minute or more), but all video recordings that follow are not more than 3-5 seconds even if I bring down the bit rate. There seems to be a bug somewhere.
Quote from: jordancolburn on January 02, 2014, 01:21:29 AM
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.
All of the new EOS M nightly builds so far seem to be missing the .FIR-file for installation. I checked one of the logs an there indeed seemed to be an error when building it.
Can I upgrade from Tragic Lantern to these new builds without reinstalling the fimware update on my camera?
Yes, after you have the boot flag set you can add any bin/ml files that will run.
I have a 60/80 MBps SDHC UHS-I card, I can get up to 140mbps compressed video with this card - CBR 2.9x.
BUT, I can NOT get any more than the buffer's worth of RAW video.
I have tried both TL (Nov 30 & Dec 26 zips) and ML (Jan 02 zip) builds.
What exact settings, loaded modules are needed, and ANY other advice to help solve this - PLEASE !!
OR does RAW not work at all yet ?
TIA!
140mb/s is 140/8 = 17.5mB/s. Raw video requires a lot of speed.
Can anyone share there EOS-M ROM1.bin with me, I would like to study it to compare with 700D port in hopes to help port it further as the EOS-M gets ported more?
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.
Quote from: nick.p on January 04, 2014, 07:29:13 AM
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 !! ;)
Quote from: RavingRover on January 05, 2014, 04:51:55 AM
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 !! ;)
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.
Quote from: belmore on January 04, 2014, 10:24:39 PM
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.
So you think maybe not all the 'fixes' in the last TL has been migrated into ML builds?
What card did you use for 720p in TL?
TIA!
QuoteWhat card did you use for 720p in TL?
SanDisk Extreme 32 GB SDHC Class 10 UHS-1 Flash Memory Card 45MB/s
To be more specific, I could get 720p in the TL build only in crop mode with FPS Override set to 24FPS. If I enabled Magic Focus, even in TL, I had issues (not that it matters, since Magic Focus doesn't work right in crop mode anyway). Focus Peaking enabled didn't seem to pose any problems.
Thanks for the great work!
I can shoot Raw ONLY? when using the 12/31 TL !!
I was able to get Raw in both crop and non crop modes ! 1280x434 non, 1280x720 crop modes !!
(must put Canon video in 2kHD 24fps mode for crop to work BTW!)
So I believe NO TL or ML builds beyond the 2013/12/31 TL build works, I have tried a couple newer ML as well as older TL builds !!
Note: non crop is writing at about 27 MB/s, whereas crop is writing at about 35 MB/s ! (this means likely the fastest/highest resolution possible for M SD writer !!) Sad! :-[
This is with a Sandisk Extreme Plus UHS-I 32gb card - 60/80 MB/s.
So I A$$ume this means not ALL fixes/etc are in the ML stream yet or those for video at least !
Thanks for the help!
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?
Quote from: nick.p on January 05, 2014, 04:55:39 AM
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.
Yep, thats why I put the 'mb' in lower case! Me knows the diff!! Me use to be an Electrical Engineer. Me are used to bits/nibbles/bytes/words/double words/etc. Me be cognizant of the diff. Me prefers 'MB or mb' rather than 'mB or mb', for the emphasis, as well that is what is shown on ML screens - 'MB/s'.
The statement of compressed video is that it will NEVER likely be able to be written at the speed of raw or M SD writer, as the H.264 encoding does take time and the encoder chip is likely processing limited, or I would see a higher bps, wouldn't I?
Also, I can set CBR to higher than 2.9x (4x is where I quit) with my card, just the output NEVER gets higher than about 140mb/s (saw peaks of 150+mb/s), so VERY likely processor/encoder/bus speed limited.
Also, the ultimate speed of compressed seems to a degree dependent on ISO, maybe - limited use/testing of this.
Thanks anyhow.
PS: It is going to be interesting when UHS-II (240MB/s writes) SD writers are in cams, and also when H.265 encoders are in cams, then the Digic engines (dual/triple Digics?) will have some REAL work to do & will be so capable !!
BTW, FYI: Canon works (has work done by?) with Texas Instruments (TI) on their Digic processors - Nikon has FujiFilm do their h/w work & firmware work!
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).
Quote from: gary2013 on January 06, 2014, 03:44:15 AM
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).
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.
I do get the shutterbug occasionally, but I seem to get out of it via changing modes (this may be a general freeze problem not the shutterbug), but another one (shutterbug I believe - less often), I have to take out battery. Very annoying as there is NO prediction when this can occur.
Good Luck.
Quote from: RavingRover on January 05, 2014, 11:24:04 PM
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.
Hi there, I m new in this forum and heard about magic lantern on the chaos communication congress.. seems like a fantastic project for indie filmmakers like me ;)
#i have one question: for a visual project i need a camera with a clean hdmi output, must not be full HD resolution, but clean in the sense of no overlays, shutterspeed , battery infos etc.. is this possible with the Canon eos m and the magic lantern (nightly builds.)?? Thanks :)
In theory yes (it's in the user guide and enabled here (http://nanomad.magiclantern.fm/jenkins/features.html)). In practice, try it and let us know if/how it works.
alright, thanks! this will take a while, i still need to buy one.. once i know I ll share...
Quote from: RavingRover on January 06, 2014, 07:26:52 AM
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.
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
Quote from: jordancolburn on January 13, 2014, 03:02:35 AM
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.
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
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.
Gary
Quote from: kalimerox on January 12, 2014, 06:47:55 PM
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.
Quote from: gary2013 on January 13, 2014, 03:20:51 AM
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.
Gary
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?
I saw it once on my 18-55 but not on the 22 or the 11-22. Of course, that doesn't prove that it doesn't happen.
My primary hope is that there is a way to implement magic zoom with touch screen on this camera. Is that a possibility?
Some things to cleanup: http://nanomad.magiclantern.fm/jenkins/features.html at the end of the page.
Thanks, that chart is really helpful.
Where is build version for Eos? It's disappeared!!
Quote from: atomas72 on January 21, 2014, 07:56:45 PM
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.
Send me a PM if you are willing to cooperate. No development skills needed, just some free time to do boring tests
Quote from: nanomad on January 22, 2014, 09:06:09 AM
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
FTR, I have been doing this on a daily basis since July 2013 with ML/TL on my M.
And that's a very good thing :-)
I'm trying to put things into order though, that's why I've posted this.
Expect a PM from me soon
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 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
Quote from: glmccready on January 22, 2014, 07:13:25 PM
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 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
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-
http://tl.bot-fly.com/
and reply to nano here-
http://www.magiclantern.fm/forum/index.php?topic=3648.msg97471;topicseen#msg97471
you and I are close in MD
great i wait your pm for my eos-M thanks for all
Quote from: nanomad on January 22, 2014, 09:06:09 AM
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
Sent a PM to help test EOS-M.
Thanks!
Quote from: gary2013 on January 13, 2014, 03:20:51 AM
The shutterbug appears when you use the EFM 18-55 lens oin the M with ML.
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?
I'm new to ML but suppose I could help out with testing. Not ready to jump into the syntax just yet though.
Quote from: nanomad on January 22, 2014, 09:06:09 AMNo development skills needed, just some free time to do boring tests
What kinds of tests? I've been trying out a few ML and TL builds this week, and there are some stability problems. Shutter bug, freezes (keeps blinking orange), loss of liveview in photo mode (requiring clearing all camera settings), etc.
Anything particular I can help with? I use manual lenses mainly, but have the 11-22mm and the 22mm STMs.
Quote from: Janke on January 24, 2014, 02:24:56 PM
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.
I have been playing with ML few weeks. Sometimes shutterbug appears, sometimes don't. I dont know why. Also I found another bug. When using Manual lens (c mount lens) with 3x crop mode, The record button don't work. I have to change to half sutter button then the shutter button works.? Any idea why it do that?
Definitely let me know if I can help. ~Andy
www.andyfgray.com
Quote from: jordancolburn on January 13, 2014, 03:02:35 AM
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
Are there any news ... and if - where could I get a newer version?
This port is currently outdated, but Nanomad is trying to bring it back to speed.
It will be back on the nightly builds page when there will be some progress.
Hi guys,
now got a eos m for testing , I m new to all this, but couldnt find the download option for eos m-.. ;(
shall i use the tragiclantern latest download from here http://tl.bot-fly.com/ ? or is there some kind of difference to the old download?
I d like to test the clean hdmi out from the eos m I need for installation purposes..
thanks!
I just saw that EOS M is back on the nightly bulids :)
Does any body know what did change? On the first go I didn´t find out any difference - just realized that shutter speed is still not working.
Nanomad took care of it.
Also take a look http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and be aware that not all of us have an EOS-M, but even so, we may still able to help if you give proper bug reports. If you say "shutter speed is still not working", I have no clue how exactly is "not working".
Sorry a1ex - I thought you all know about this Bug.
In the video mode the shutter-speed-display just doesn´t show the right numbers like: It is 160" but shows 0" or even stranger this moment 0.-8".
In photo mode it seems to be at least better. Means ML shows nearly the right numbers like Canon info says 80" - ML shows a higher 81" or the other way round ... canon 100" / ML 96" or canon 135" / ML 125"
If you try to change shutter speed in both modes ... very often the display jumpes for not even 1/2 a second to the org. canon info view and back to ML view.
Oh, just this moment the camera didn´t start again and showed the orange light - had to take out the batterie. But this was the first time after starting around 10 - 15 times.
That´s my experience so far.
.
Well... one has to double-check FRAME_SHUTTER_TIMER and get_current_shutter_reciprocal_x1000.
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?
Not 100 seconds just 1/100 - but the canon liveview display shows only the 100.
Here, at long exposures it shows the " symbol, that's why I got confused. ML shows 1/100 at short exposures (which is in SI units - you are setting the exposure time, which is measured in seconds, not in Hz).
Frame shutter timer should be right since you can do all the fancy HDR stuff with the shutter... also has the ADTG shutters.
1. I installed a freshversion of 16 feb nightly to EOS M.
2. Cleared the ML settings.
3. I'm in photo mode and M.
Every time i activate the Dual ISO module I got the the message:
ISOless PH err(15)
(http://thumbnails110.imagebam.com/30838/74b74d308376002.jpg) (http://www.imagebam.com/image/74b74d308376002)
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!!
Quote from: glmccready on February 18, 2014, 04:14:51 PM
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.
funkysound: Thanks. A simple solution that didn't cross my mind. I'll give it a try.
Quote from: funkysound on February 19, 2014, 05:23:59 PM
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
Can ML add to EOS M shut with only electronic shutter?
Fps override + raw. Also can do silent pics.
Quote from: feureau on February 24, 2014, 08:05:23 AM
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 M
Quote from: Morghus on March 10, 2014, 01:02:29 AM
Should be in one of the next nightly, and the button to hold is INFO on the M
which nightly build? ML, TL or both?
This applies to EOS-M too:
Quote from: Audionut on March 06, 2014, 01:49:24 PM
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.
@gary: if you don't care about the ML project as a whole, keep using and promoting Tragic Lantern.
Quote from: gary2013 on March 10, 2014, 04:26:44 AM
which nightly build? ML, TL or both?
ML only for now, but I'm sure it'll find its way into TL someday
there are now two listings for the ML nightly build EOS-M. The new one says Cleanup. Which one are we suppose to use? What does Cleanup mean? That it still needs too be cleaned or it is cleaned up and preferable?
http://builds.magiclantern.fm/#/
Cleanup is a branch where I'm doing some code refactoring; it stays there until it gets code review and some basic feedback from the other developers (or anybody who compiles ML from source). Once the changes have been reviewed and cleaned up, they get merged to nightly builds for everyone else to test out.
So, what appears in the bitbucket log may not be available right away in the nightly builds (basically this ensures you are not running truly bleeding edge code, but the new stuff did get a little testing and reviewing from some more eyeballs). Think of it as one small step to improve the overall stability of these nightly builds.
About the cleanup version in the nightly area, my best guess is that nanomad simply tried to compile this branch on the nightly server. For testing I recommend the regular builds; for everyday usage... for myself I simply compile the most recent unified (which is the same source code used to build the nightlies).
I just tried the latest version, Mar 11 ML, for the M and I do not have the mlv/raw listings showing up in the menus even thought the modules are shown to be loaded correctly.
Have some screenshots?
Quote from: a1ex on March 12, 2014, 10:52:02 AM
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. :(
Right, I keep forgetting to update that help message...
ML EOS-M Nightly builds are always now having different dates shown. For example, tonight's listing shows Mar 14th and after the download it shows the file as being named Mar 15th. This can be confusing at times where I think I don't need a download when I actually do need to get it.
Not sure where to look (have a screenshot?)
Here it shows Built on: 2014-03-15 and the file is named Mar15.
Quote from: a1ex on March 15, 2014, 08:27:03 AM
Not sure where to look (have a screenshot?)
Here it shows Built on: 2014-03-15 and the file is named Mar15.
Here is a current screen grab from
http://builds.magiclantern.fm/#/
and the actual file has a name of Mar 15th.
https://www.transferbigfiles.com/364b3205-ef9b-4de4-abf8-9a167d0f0ddf/jNytWQMfjia-gF1DwCHbBA2
EDIT-how do I directly put an image file to this post? I see the icon for add image, but then how do I get my actual PNG file in here between the [ ] ?
Looks like a time zone issue. If I delay the nightly builds by 3 hours, should be OK for you, but still won't be solved for San Francisco users. If I delay them by 6 hours, they might be a bit too late for European users.
To embed an image, you need to paste the link to the image only (without the surrounding html stuff). Try imgur.com or dropbox.
ML ver Mar 16th and Mar 15th will not work at all on the M. I only get a steady red led showing. Nothing else happens.
I just tried magiclantern-Nightly.2014Mar16.EOSM202 on my EOSM and it works just fine. What firmware version do you have?
Can you try renaming the ML folder and then re-extracting the one from the zip?
Quote from: nanomad on March 16, 2014, 03:21:04 PM
I just tried magiclantern-Nightly.2014Mar16.EOSM202 on my EOSM and it works just fine. What firmware version do you have?
Can you try renaming the ML folder and then re-extracting the one from the zip?
I have the latest firmware as far as I know. I am using the fir that always comes with the TL builds.
I just tried a new download of ML Mar 16, deleted the ML and autoexec on the card like I always do, then extracted the zip and copied the two files onto the card. This time, the red led does shutoff like normal when I inserted the card, but when I try to power on, it looks as if it is going to do it with the led flashing then after a couple of seconds it goes to steady red led and nothing happens except it hangs the camera and then a battery pull.
EDIT- I tired booting again and this time it worked. I have never had the steady red led hang up before except for these last two days using the ML nightly. Strange.
BUT, now the intro splash screen is stuck. How do I get past this? In the past, I just swiped the screen again to get to the ML menus.
EDIT 2, now the ML menus showed up after a minute of just sitting there with the splash screen showing. Something is acting strange doing this. Never had this behavior before.
EDIT 3, did my usual settings in ML menus. Turn off audio headphones, turn on all the modules, Debug listing 2 set to Reload modules after a crash. I shut off the camera and then rebooted and now it's back to the steady red led and it hangs there. :-(
LAST EDIT- after trying to boot again for a few more times, it finally does start to work. Something is very wrong with the builds I have tried (many times) the last few days.
What modules do you have loaded?
Can you try booting without them?
nanomad, i just thought that maybe cus I do not have eoscard used on my card, that might be doing all of this? I don't know, just guessing. But I never had any problems like this on ML builds before a couple of days ago.
Quote from: a1ex on March 16, 2014, 04:27:47 PM
What modules do you have loaded?
Can you try booting without them?
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.
Quote from: gary2013 on March 16, 2014, 04:31:58 PM
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?
(it's important for narrowing down)
Quote from: a1ex on March 16, 2014, 04:33:18 PM
This was without any module enabled?
(it's important for narrowing down)
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.
EDIT, after I typed the last message here, I tried again and it's back to not working with the steady red led again. Waited a bit, tried again, it worked. Powered off, waited a bit and the red led hang came back.
I have been having the same problem with the EOS-M ML builds. I've used multiple builds and they all have the same problem. Try to turn it on and I get a blinking LED or solid LED and the screen never turns on and the power button will not turn it off. If I pull the battery and try to cycle it a few more times, at some point it will finally power up completely. I am using a 64GB card with nothing else on it. I do not load more than the very basic modules.
I just tried going back to ML Mar 11th and everything worked a few times in a row of off and rebooting. I was able to shoot an MLV raw file, but it has no MLV playback.
The splash screen is annoying. It appears we have to wait ten seconds or more for it to shut off. I tried swiping and nothing got it to shut off. isn't there some sort of swipe or button push to shut the splash screen off?
Normally, the first key press / scrollwheel / whatever should disable the screen right away (at least this is how it works on all other cameras).
For anyone who can reproduce the issue and has basic command-line skills: can you run hg bisect to find the buggy changeset?
Quote from: a1ex on March 16, 2014, 05:10:45 PM
Normally, the first key press / scrollwheel / whatever should disable the screen right away (at least this is how it works on all other cameras).
For anyone who can reproduce the issue and has basic command-line skills: can you run hg bisect to find the buggy changeset?
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.
I've already explained what needs to be done for fixing shutter speeds: http://www.magiclantern.fm/forum/index.php?topic=9741.msg101808#msg101808
also on 700D: http://www.magiclantern.fm/forum/index.php?topic=5951.msg103451#msg103451
but can't do much more without an EOS-M (porting advice is OK).
Quote from: a1ex on February 15, 2014, 02:01:49 PM
Well... one has to double-check FRAME_SHUTTER_TIMER and get_current_shutter_reciprocal_x1000.
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?
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.
Here we are programming the cameras, not just using them. Try coding ML without math.
Quote
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.
Quote
I also do not understand why it is 1/64 when we need it to be 1/60 for 30 FPS video
You already quoted the answer. We are talking about ML *displayed* values (that is, just printing what Canon gives us).
Why do we need exact values?
1) There is a obscure feature called shutter fine-tuning, which adjusts shutter in 1/50000s increments (or close), which is very useful when filming computer displays (to get rid of flicker).
2) To make sure the shutter speed matches the mains freqency (Canon may print 1/30, but, to avoid flicker, in PAL land you need it to be a multiple of 1/100, that is, 1/50 or 1/33.333). 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).
3) When using FPS override, the image gets brighter; you may want to know how much (well, maybe you don't, but I do).
4) ETTR in LiveView. How's this one supposed to work if it doesn't know where it's starting from?
Also... are you suggesting adding a user preference (added complexity) instead of fixing the bug?!
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.
Quote from: a1ex on March 17, 2014, 09:05:01 AM
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.
Quote from: Audionut on March 17, 2014, 09:08:28 AM
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.
Quote from: Oswald on March 09, 2014, 04:12:09 PM
Fps override + raw. Also can do silent pics.
I want use full camera resolution
And what is silent mode?
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.
Quote from: DJBellis on March 22, 2014, 08:06:14 PM
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/.
Quote from: jordancolburn on December 31, 2013, 04:35:47 PM
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?
Hi EOS M people,
I reported a bug to ML. I had an issue where the shutter would not work, even the touch shutter. My camera locks up and I had to remove my battery to restart. The shutter bug appears when Canon EF-M 18-55mm lens is attached to my EOS M. Magically, the shutter bug disappears when Canon EF-M 22mm lens is attached to it.
It took me a long time to figure it out since sometime ML worked great, and other times ML would just lock up my Canon EOS M. For some reason, I decided to switch my lens. I detached EF-M 18-55mm and put on EF-M 22mm and ML worked as I remembered. Then I realized that there is something going on with EF-M 18-55mm which ML doesn't like. With EF-M 22mm attached, I was even able to take continuous shots using ML's intervalometer and the shutter button and touch shutter worked too.
I'm glad that ML isn't completely broken for Canon EOS M.
I hope that this could help resolve someone's pain with their ML issues with EOS M.
Hi
Tried to install ML (20140402), but first observation was missing fir file. So I got one from TL package. When trying to run firmware update, it says ML/DATA/FONTS.DAT missing and won't continue. Am I missing something?
edit: borrowed also fonts.dat from tl, and then got it installed.
I see audio meters are showing while recording video. This is new, right?
I noticed that the software would not run if I copied it over with the card in my Laptop. I had to use a card reader. I don't understand why that happens but I think other people are having the same problem with the cam not booting up. Please use a separate card reader.
I'm using the TL firmware because I couldn't find it on this site. Others may be having this issue too.
Hope this helps someone.
Quote from: huangyanlai on March 28, 2014, 06:22:38 AM
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?
+1
The current dual iso implementation assumes a constant address in memory for the iso registers, which isn't true for all digic v cameras.
I'll post a build later today with a different address location that may help.
Quote from: huangyanlai on March 28, 2014, 06:22:38 AM
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 have noticed that the touch screen is less responsive now with the newer versions of the builds. For example the scroll wheel does not respond as it used to. Plus, where do I get the mlv modules from- especially the player.
There have been no changes to the touch screen code
I was shooting intervelometer today and when it was set on pic every 0s (pics like crazy) it would not stop or come out of the cycle no matter what was pressed. Had to pull battery.
Mirrorless + http://goo.gl/xpHHt5 + Magic Lantern = winner!
great update guys....
Hello all, I'm not new to ML but haven't installed it on anything since the 650d release. Now i'd like to throw it on my EosM but I had a question on the install differences, the 2014Mar13 of TL has the EOSM_202.fir while the recent ML versions do not.
I guess my question is that am I supposed to prep my card using Macboot and just throw it in or is there a logical way to update the firmware on the camera like previous versions? I read through the thread and most of the info was related to RAW video so I'm sorry if this has been covered and I somehow overlooked.
Other than that I'm happy to help out with any testing of nightly features or whatnot, just let me know how I can be of assistance!
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.
is the Shutter bug with 18-55 already gone in latest nightly?
about to jump to ML but still hesitate due to shutter bug...
No because we can't reproduce it reliably
Quote from: nanomad on April 08, 2014, 08:46:25 AM
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!
Hello everyone,
1st post here in ml forum ;D
I just installed the ml for Eos-m (Nightly.2014Apr07.EOSM202).
1st all it works good and almost stable for such a fresh ml-port.
THANKS A LOT to the DEVELOPERS!!!
Some small problems i encountered :
After entering the menu with two-finger tab for ml setup menu, it often exits the menu without any user action.
I dont know why, is it a timer which closes the menu after a given period with no action?
This strange automatism really disturbs the workflow while setting up ml, how can i change this?
Other proposals: I think the navigation inside the ml functions is lil hustle atm. Always switching between touch and buttons is no good for fast setup.
I would love to see all navigation could be done via buttons, so you could keep your LCD-Hood on and use buttons only.
Maybe some hold down button actions could improve access to ml without the need of using the touch.
Cheers dave
Quote from: nanomad on April 04, 2014, 08:07:36 AM
The current dual iso implementation assumes a constant address in memory for the iso registers, which isn't true for all digic v cameras.
I'll post a build later today with a different address location that may help.
This nightly build Apr09 still shows the same error for dual iso.
Grabbed the nightly (2014Apr09.EOSM202) formatted card, dropped files onto card, run upgrade and got a flicker of the installing screen then a rapid blinking orange light, waited around 15 seconds, removed battery. Did this process and formatting and such 4x - have I missed something?
I didn't make the card bootable is that required still?
I'll check. You did everything right
I had the exactly same experience than Indiejack. Formattet card, evan made it bootable to make sure... copied all the files and then startetd the update process. A short flash shows up, then the screen gets dark and the light keeps flashing forever. Exact the same thing as described two posts before. Tried also several times. Since today appeared a new version of the nightly builds for EOS M a hoped that the problem ist fixed, butwith Version 2014Apr13.EOSM202 it is exactly the same as Version 2014Apr09.EOSM202.
Since I guess that your Versions are at least once testet before published, i was thinking my SD Card might have a problem (I use a 2 GB card) but installing a fresh 202 Version from Canon works well. If anybody would have an idea, I would be very thankful. To be totally honest. I bought my Canon EOS M purely for the reason I read that it is possible to do RAW recording with magic lantern with it. Of course I want to get it going. I like to make living photography, so I only need a few seconds of video in Web Size (Full HD not needed really) always from a tripod, no camera movement, no sound (so all the weaknesses of the camera do not really count), but every single image as crisp as possible. The Canon EOS M is perfekt for this purpose and a small budget.
The EOSM installer is broken and should not be used until further notice
It looks like the installer should be fixed in the next nightly: https://bitbucket.org/hudson/magic-lantern/pull-request/470/eosm-use-traditional-boot-method-this/diff
Well, not until it gets merged
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?
Update. I have focussing like I was expecting. I just set the focus box to the smallest option and enabled full time autofocus. Simple enough.
Quote from: KSphoto on April 14, 2014, 04:52:38 AM
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?
i'm not installing ML yet (camera still virgin), but when i disabled continuous focus, touch to "focus" is also not available.
i belive this is not related with ML.
touch to focus only available when continuous focus is enabled.
I checked twice and can't find any "touch to focus " options even when in continuous focus mode. I'm using the 22mm lens.
I just installed a new ML Version (04.21.) and realized that there is no audio department any more (audio out). Does it come back with more features or is it gone forever because some things do not work with EOS M?
All the other stuff like shutter speed in Video modus seem to work good now - at least during a short test. I also had no shutter-bug with the 18-55.
With older nightlys the shutter bug appeared also after warm boots, which seems to be fixed now, it seems to be a lot better.
However, it still appears with cold boots (re-seat battery and press power). After that I needed to re-seat the lens to get the shutter working again. (11-22 and 18-55 behaves the same). But like I mentioned it now persists warm-boots, so it's a lot better, and seems like we are headed in the right direction.
Needs more testing...
Quote from: EVVK on April 22, 2014, 10:02:03 PM
Amazing :P the shutter bug doesn't seem to appear with 11-22mm either and the last nightly.
We didn't do anything to fix it, but the latest builds contain the classic boot method (from the good old days when ML ran only on 5D2 and 550D). However, my theory says the bug is still there, but the probability of it appearing has been changed (and some people who had the bug before may not have it with new builds, but other people who didn't have the bug before might have it now).
To confirm or invalidate my theories, please report how it works for you.
The nightly builds from 2014-04-18 and newer use the classic boot method, and the previous ones use the cache hacked method. So, try checking a few builds before this date, and a few builds after this date, and write down whether they have the bug or not. To draw a meaningful conclusion, I need results from at least 10 testers.
Does the Advanced Bracketing ( DOF ) work in EOS-M ?
2014Apr20.EOSM202 still has the bug for me.
I have been using the nightly builds over the past month since getting the 11-22mm lens - all have the shutterbug,
including 2014Apr23.EOSM202
I used to get fairly regular red light hang-ups requiring a battery pull on start-up. No problems with that using
the latest build.
Crap, seems like so, just had a good luck the first 5 runs, it's been a while when I last tried the nightlys. Anyway, I now get the shutter bug more frequently again, if not every time.
Has anyone been doing any analysis of the lenses? Similar to this:
http://pickandplace.wordpress.com/2011/10/05/canon-ef-s-protocol-and-electronic-follow-focus/
Maybe it could reveal what differs the zoom lenses. :-\
Hi there @all,
This is great work!
But one little thing:
I installed magiclantern-Nightly.2014Apr25.EOSM202.zip. When i go into the ML menu, it leaves in 5 seconds. This is a very short time. Is there any config option to increase the menu off timeout?
Hi Holicow,
this is sometihing which makes everybody crazy and was mentioned a few times - in older posts someone said that ii is not possible to increase the time here because it´s got to do with some canon internal time settings - if I remember it right
Hi funkysound,
Does this happen with other camera model ports of ML (600D or 50D eg) also? If it does not, it would be just a port specific setting in the sourcecode. Any developers for the M port here?
Also if i press eg in the Help section some entries, it will be shown forever as long i do not press anything (shutter eg), so it must be possible i think.
I'm investigating it. It's a timeout of the hijacked canon dialog but so far I had no luck in killing the actual timer that fires it
Cool, because those 5 seconds are so frustrating. I forked the source and had a little look inside.
(Could be a little better documented, hehe) Maybe a solution is to send cyclic a fake button event?
#ifndef CONFIG_6D
TASK_OVERRIDE( gui_main_task, ml_gui_main_task);
#endif
void ml_gui_main_task()
This is the code for hijacking or?
That is an idea (provide a synthetic event to be processed by the underlying canon dialog and not us. A simple left/right combo may be enough).
Yeah the code could be better documented, I agree
Cool!
So you give it a try?
BTW: Where can i report errors in a correct manner, i found testing the ML 2.02 nightlies?
E.g i use now magiclantern-Nightly.2014May03.EOSM202.zip and found an error.
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])
Quote from: holicow on May 03, 2014, 10:36:37 AM
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
So in theory if i would use crop video recording on canon M then i could actually use 16mm camera lenses without visible vignetting if i will create 16mm lens mount myself ? So its gonna be like true fullhd 16mm camera with no moire and aliasing ?
Anyone measured how much sensor milimeters are used to capture on crop modes ? I think it would be easyt to measuyre by filming video with crop and without crop and then resizing non crop footage to be 223 pixels wide (like 22.3 mm of sensor) then comparing cropped versions should give us size in milimeters.I think it would be more like super8 sensor size (7mm wide x 3)not 16mm unless there is smaller zoom than 3x but that would have moire.
based on my math EOS M, in crop mode and with 1472x626 resolution (2.35:1 and max resolution for continuous RAW recording), use a sensor area slightly larger than 1/2" format: every lens with the same (or larger) projection area is usable, but I can't verify.
Any news on Dual Iso for this little beast? Does it work now?
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
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, i mean only for canon fps, so when you uyse fps override then sound will be disabled, its useful to have at least default canon recording mode with sound on, untill magci lantern sound code will be working .
Quote from: 2blackbar on May 07, 2014, 04:00:08 PM
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
You have some incorrect information. In general ML does not just willy-nilly disable default things that are built-in from Canon. Perhaps you see that some particular
additional ML feature having to do with sound recording is not working/disabled (such as recording sound with raw video), but that does not mean that ML has disabled the built-in sound recording capability from Canon (that would be silly!). ML only adds features to the camera, and pretty much all of ML's features can be disabled leaving you with a camera that is indistinguishable from stock (other than the fact that you can get into the ML menu), even with ML installed.
My mistake I had sound disabled in canon menu when i installed ML, i dont know why it happened but its all ok now, i enabled it :)
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.
Quote from: Yzgyz on May 08, 2014, 11:30:49 AM
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.
That´s an old known problem ... the shutter bug. Till now nobody found a way to fix it as far as I know.
If you read through this forum you will find diffent ways to solve it. If it is happening to me I just remove the lens while the M is turned on and put it on again - then it should work.
Class 6 card is too slow now for magic lantern? My recording stops itself after a couple seconds depends how complicated scene is.
Quote from: 2blackbar on May 07, 2014, 04:00:08 PM
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? :-)
Cheers,
Andrew
Quote from: Fioritura on May 09, 2014, 08:13:46 AM
Hi 2blackbar, which speed booster did you modify, and how? :-)
+1000!
... and please post some shots!
Quote from: tupp on May 09, 2014, 08:31:05 AM
+1000!
... and please post some shots!
Almost full frame camera with sb. :D Please post shots and pics!! :D
It works nice, i modified it a bit yesterday and sits in camera + clicks into place like if it was made for canon M but i had to tile camera mount a bit, its not possible to unscrew camera mount cause 4 screws are glued with epoxy in factory, i had to cover sensor with solid circle i cut myself and used tape to prevent dirt getting into sensors lowpass filter, i lost warranty i think by doing that but i dont care that much cause i have second canon M on planet with speed booster , this is main reason i bought this camera, i even considered taking glass out from focal reducer and gluing them into macro tube for canon M , then gluing EF mount on top of macro tube. I had to file speed booster mount and then camera mount, i bought canon M macro rings first before i bought canon M cause i wanted to see if it will work.It works but unless you have nice set of tools to file down the mount teeth in camera a bit then dont get hopes up, it wont work if you tile only speed booster mount because lens mount on canon body have teeth a bit too long towards each other and wont let the speed booster through even if you will tile down all teeth from speed booster nex mount, i think photographers gave this camera bad opinion because autofocus is slow on electronic lenses, but its fantastic canon camera for video, you can mount any lens and sensor is so close its really different camera than everything canon released so far thanks to it, you can experiment with lenses a lot and convert them yourself.
Interesting fact is NEX body cap fits onto canon M.Mounts are very similar.
Its weird cause ive seen news about speed booster for canon M year ago in may 2013 and still nothing, how hard it can be to use different mount on it.
You can also mount canon EF kit lens on focal reducer and its wider than normal but you cant zoom out completly because vigneting starts from 24mm, but even then its wider than bare 18mm zoomed out and i like that.
Speed booster doesnt work that well with telephoto lenses, or maybe because i have old ones, there is shift in focal plane on sides and middle is sharp.
I think differently shaped glass is needed in speedbooster to work well with telephoto like 100mm or 200mm so its not soft on sides, its super sharp in the middle.
Works well with 50mm and it works best with wide lenses from 50mm down, my 24mm lens doesnt vignette with speed booster but canon's EF kit lens does on 24 and you can hide it by moving to 26mm , then its wider than my non kit 24mm which is weird cause it shouldnt be, yeah canon kit lens on speed booster is wider on 26mm than my other 24mm lens on speed booster.
Average performance on telephoto like 100mm might also be like that because i didnt used speed booster for 600$, i used focal reducer for about 100$.
Anyway im very happy that i did it because difference especially with shallow depth of field is really big between aps-c and full frame, wide lenses have quite a lot of bokeh when you frame someone from hip to top of the head, i wanted that on aps-c but fast lenses are expensive, here with focal reducer you can have that on f2.8 lens.
I dont know if this thread is good place to post pics, maybe its better to start new thread because people wont find the info im posting.
It would be nice if magic lantern for canon M could change shutter , iso or WB values if you press on the bottom on them with finger like with original canon overlay with shutter and iso, is there a way to put white balance icon there using original canon options from menu or something ?
I also wanted to try whats the maximum fps canon M can record at 720p using frame override but you cant do 60fps with it, in override menu it says 60 fps (from 30) like if it was in fullHD but its not and its not in 30fps, i picked 60fps 720p , dont know why it shows "from 30", should be "from 60" if in 720p mode i guess ?
FYI:
I also suffer from the shutter bug with the 18-55mm.
A Quick Poweroff / Poweron Sequence heals it until the next Poweron.
Used ML: magiclantern-Nightly.2014May03.EOSM202.zip Date: 2014-05-03 12:16:11 +0200 .
Used SD Card: Transcend 90MB/s 600x Class 10 SDXC 64Gb card.
I noticed there is black bar on right side of the frame when you record video using fps override with crop zoom enabled, is this normal ? This black area doesnt show up when fps override is disabled.
(http://i.imgur.com/r0s5LTp.jpg)
Quote from: 2blackbar on May 08, 2014, 10:19:13 PM
Class 6 card is too slow now for magic lantern? My recording stops itself after a couple seconds depends how complicated scene is.
You need to specify more info - are you using a CBR of 1.0, for example or RAW video or .....
Anyone know if any effort to enable 'Remote Shooting' via USB & EOS Util. via ML/TL ??
Its incredible that Canon gave us no way to remote control shooting w/ the M !?
If I have missed this capability via ML/TL &/or EOS Utility, plz let me know.
Thx!!
Well I compensate with Dslr.bot over bluetooth, works fine.
:)happy so far. Got the ML for M finally installed and a lot seems to work ok after a few hours fiddling around in the menues testing. Opens a new world also on the M, got it on 60D earlier. Have some old Konica lenses from the 70's I intend to use for video, THANKs for the great work!
I'm using ML with my 8-48mm f1.0 lebs with crop mode. I just love to use this lens, covers perfectly sensor in crop mode and it is great video lens. :)
But there is one bug. Camera don't start recirding in crop mode. It have to set to shutter button, then it starts recording properly. :D
Hi, I've just installed ML nightly build on my Canon EOSM but have no idea how to access the ML menu....2 finger tap brings up developer screenshot. Apologies for my ineptness, I am new to this game.
2 finger tap to open or close ML menu, first time shows info so you have to press set to make it disappear
I also have it on my EOS-M. Installed build from about 2 weeks ago.
I'm running primarily the 35MM f/2 IS EF lens for video, the 22 finds some time too.
So far I have run into zero issues. I did adjust raw settings enough to get crop frame raw working, but I don't have a flow for that or a way to deal with audio, so I just shoot mov with a boosted bit rate. So far so good! No issues yet, other than the odd transient UI glitches.
I have a bug in the latest nightly builds..
Installed the ML - everything else seems to work fine, but with the 18-55 attached, i cannot take a picture. Press shutter fully and nothing happens.
detach the lens, and it fires fine.
Load up stock FW and shutter works with with lens attached...
Thoughts? Ideas?
This is called shutter bug. Or one option is to turn camera on and off quickly. This is known bug.
yes, as I've discovered. And no ones figured out how to fix it yet? Tis a shame :(
I installed the Nightly Build (5/23/14), and am trying to uninstall ML from my EOS-M, but following the instructions, when I try to format the card with ML installed on it, I see the msg 'Format card, leep ML [Tap Screen]'. Tapping the screen does nothing, so I'm unable to uninstall ML. Any ideas?
Instead of tapping the screen rotate the mode dial from 'manual' to 'A+' that should remove the bootflag and then you can delete the files on the card. You can see the procedure at the end of this video (from 3min 30 seconds). The flash-screen information has changed somewhat with the latest builds - keep a close eye on the bottom of the LCD display after rotating the dial, it will keep you informed of proceedings there.
http://www.youtube.com/watch?v=jc8Zo-VMUkU
I have to say, the difference of performance in crop mode is very noticeable, when using compressed output. It's really impressive. Running this 35 f/2 IS in crop is a stellar combo, and the quality has almost the air of BMPC. Combining the 35 in regular and crop makes for a nice pair... about 50mm and about 135ish (crop math? its 3x crop of ape-c or 3x of full frame?). Now I'm sorely tempted by the new 16-35mm IS to get some range.
I installed the nightly build from 5/24/14 this morning. Just saw that HDR had been rolled into Advanced Bracketing. So that answers one of my questions.
The big question for me is that ML menus only display for about 5 seconds. Being pretty new to ML this is a real pain. I looked everywhere but in the right place on where to configure menu display time. How can I not make the menus time out?
Thanks, Hal
The 5 sec Timeout is an error and is still investigated.
Hi all,
after working on ML for over 2 months on my 5D mkII, and more than happy with it, I made my move to to a EOS-M.
I Installed the latest nightly builds (for the last 2 weeks, May 2014), configured and wow!, big difference here in development stage.
I've been trying to set up and configure it based on my 5D experience and what info I've found in the forums, but realize that not only I am dealing with a complete different beast, but I have not managed to get any decent results at all.
My question:
Is there any true and tried documentation about the steps to follow once ML is installed and RAW_REC is running at all?
My biggest issues:
1- aspect ratio; I may be able to choose, say, 16:9 but the result is a stretched file that when squashed to the correct ratio creates artifacts.
2- there's no reliable aspect ratio selection, all I can do is select horizontal; is this the case?
3- though my SD card writes 50mb/s i drop frames anywhere above 1000 pixels across.
4- documentation is spread through the web differently and sometimes people contradicting one another, most info is from last year, and there's very little EOS-M-specific. Or so I have found -apologies if this is wrong.
5- banding in the middle of the video
I'd appreciate if anyone could suggest an up to date guide, i'm ok at installing, etc, except what used to work for me on the 5D is not really doing much for me on the EOS-M.
Moreover, I'm willing to make a step-by-step graphic guide for those facing the same issues, so if anyone is willing to suggest/provide info, experiences, I'd more than appreciate that.
Thanks a lot,
Rush
The limitation is not the card but the card interface of the camera, sadly so.
And yes, documentation (finding it, even more) is one of the sore points of this project.
So, whatever you can do will surely be very welcome.
I'd love to see stickies with platform specific manuals maintained by
small teams of maybe two or three people.
Since this needs volunteers to help and suggesting is not doing,
my help would be available for EOS M - if anybody cares.
Not that I have a plan yet how to start. Maybe a list of all menu
entries and their limitations that the platform sets explained?
Best practices on top?
Installation and uninstallation step by step?
Available as PDF for Download, maybe plus translations into
other languages? (German: Here.)
Anybody else on board? Suggestions, comments?
Hi, sure thing, count me on.
My suggestion: PDF is kinda limiting since it most people are on mobiles nowadays, in my opinion html is the most practical and simple and not OS-specific.
Personally I find the list of menus akin to learning a language by studying the dictionary; my approach would be more or less like: "...and after you installed ML, reboot. Navigate to modules and activate RAW_REC because blah blah, and this or that because of this or that reason", without too much text, mostly screen-shots and some examples so that the whole thing is easy to grasp real quick.
Rush
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?
From IRC:
Quote
06:50 < kur1j> am I crazy or does the EOSM version of magic lantern not support focus confirmation in the "Magic Zoom"?
Can you (any of you) describe the exact behavior? If you have a second camera with ML, it may help comparing the Magic Zoom behavior between the two.
Quote from: canoneer on May 28, 2014, 11:07:26 PM
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?
No. Unfortunately screen goes black.
Good afternoon all,
I have just installed ML on my EOS M. Question, is there a quick way to adjust my iso without having to two finger tap the screen and select iso then left / right buttons? I really use ML for the on screen VU audio metering, Intervalometer and having access to ISO 160,320, etc... I would love it if there is a way i can use the rotary button next to the display to change iso to those magic numbers quickly.
thanks!
digiman
Nor sure where to ask this, but the EOSM for 2.02 firmware would seem to be the relevant place, since that is what I installed on my camera:
I've just succeeded in getting ML loaded and working with my Canon EOS M with 2.02 firmware and the EF-M 22mm f/2.0 lens for nightscape photography. Works great, thanks very much all you guys working on this. However, my other lens is the 18-55mm f3.5 ISM lens which I understand has the "shutter bug" and which, in any case, I don't need ML (at least at this point). MY QUESTION IS: Can I just swap SD cards; one with ML installed, the other without, or do I need to uninstall ML on the SD card that has it installed before swapping???? I don't want to turn my EOS M into a brick, so I would love to get an answer to this question before actually trying it.
Thanks in advance,
Jeff
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.
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?
Quote from: digiman on June 03, 2014, 01:50:46 PM
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?
I didn't figure out a fast way in ML itself, but what I do is just tap info button to switch to Q view, use finger to set ISO, then info back. That is faster than going into ML menu, at least for me. Still disruptive though.
Thank you for the reply,
I have used Q mode via the info button to change it but it only has the standard ISO 100/200/400/800 etc... sigh
The way I intended to use the camera as super compact ENG filming with the power of magic lantern, but if I cannot even control something as simple as ML ISO with the rotary button pad I might just sell my investment in this EOS M and move on..
If you set ML ISO to say -0.3 EV, and change ISO in full-stops from Canon menu, it should keep the digital gain unchanged. Just tried on 5D3 and it works as expected.
Note that ML ISO at -0.3 EV is not the same as Canon ISO 160. The second one will not keep the digital gain.
Hi,
New member here. I have been using ML on the EOSM for about the last month now. I love the output of the crop mode and the ability that gives to use different lenses. I haven't had many problems and so far ML has been quite stable, only a few times I've had the recording stay stuck on and no buttons working, I've had to take the battery out to fix the problem, but it's not a big issue.
I have one question (which I searched to find an answer for); is the Audio Monitoring feature working on EOSM? and if not (which I assume) is there any plans to get that up and running? It's something I would find very useful as I assume other people would also.
Thanks for all the hard work that's been put into ML by all the people on here for the EOSM so far! I'm more than stoked to play around with this camera because of it, I'm no good at coding but I'm more than happy to help test this stuff.
Cheers,
Alex.
Quote from: Oswald on June 02, 2014, 05:56:25 AM
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.
Thank you. If I've understood, it is safe to switch in cards without ML on them and go back to ML when needed. Right?
-Jeff
Anyway, I tried it and survived. So I guess the answer is yes and no brick.
I noticed on the build features page that none of the focus features are supported (checked). Does this mean that the focus infinity module (http://www.magiclantern.fm/forum/index.php?topic=7189.25) won't work? I am trying to get the EOS M to reliably take pictures from an aerial platform, but it loses AF lock and freezes pretty reliably, and I am having trouble focusing to infinity before mounting it on the platform. With the 22mm lens in MF it loses MF when powered off, and I have to power it off to mount it. I have a 40mm lens, but am having trouble keeping MF focused to infinity there too...
If anyone has any idea on how I can achieve MF to infinity and keep it there, I would be most grateful. In CHDK I can tell the camera to focus to infinity and stay there. That would be sooo very nice if I could do it in ML too.
Thanks for any time.
Andy
Buy manual glas from the 70's with an adapter, with only manual focus, or use an EF lense with MF button.
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.
Tried to figure out some new stubs for EOSM.202 . However I would advice someone checks/verifys them as I haven't had any prior experience on this.
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)
- the first two are only needed for 5D2 and cameras from the same generation (FEATURE_LV_BUTTON_PROTECT)
- the display ones are for variangle displays; you can try enabling FEATURE_IMAGE_ORIENTATION though and try them
- EngDrvOut: already defined, but with a different address (?!)
- gui_change_*: for old-style cameras only
- GUI_SetLvMode: 50D only
- SetAudioVolumeIn: take a look at the new-sound-system branch, maybe used there
- mvrSet*: unused, should be cleaned up (the only one used is mvrSetDefQScale)
Ok , Sorry :-[
No idea on the actual code calling those, but those few that were marked with questionmarks in the were empty in EOSM.202/stubs.S . Just tried to help out.
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.
I cannot get the camera to stop taking shots in the Intervalometer mode:
The settings I used were - 3 seconds for duration between shots and to turn off after taking 12 shots.
It counts up to 12 shots and then it starts all over again.
Am I doing something wrong? ::)
Can you record a video showing the problem?
not sure if this is the right window but how possible is 4k h.264 video on the eos m :D
Quote from: khail on June 09, 2014, 04:59:14 AM
not sure if this is the right window but how possible is 4k h.264 video on the eos m :D
Impossible. :D Never gonna happen.
curious as to how come, ml can over ride the FPS and compression of H.264
Quote from: khail on June 09, 2014, 04:14:36 PM
curious as to how come, ml can over ride the FPS and compression of H.264
For 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).
Short answer: by calling functions and/or setting registers that were found in the Canon firmware that cause the FPS to change and the h.264 compression to change.
Ok still a bit foggy but I think I get it. What resolution and card works for you guys while recording raw ?
Quote from: Harry3 on June 08, 2014, 11:48:53 AM
I cannot get the camera to stop taking shots in the Intervalometer mode:
Am I doing something wrong? ::)
You can stop the intervalometer by rotating the mode dial, by pressing MENU or PLAY, or by turning off the camera
Quote from: magnosantos on June 06, 2014, 04:16:41 PM
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.
Quote from: Pharinen on June 05, 2014, 12:04:50 AM
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.
Nobody knows? ???
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.
Quote from: Oswald on June 12, 2014, 09:11:12 PM
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?
Wanted to share this here for those who don't visit the hardware thread: DIY LCD Hood Template for EOS M (http://magiclantern.fm/forum/index.php?topic=12304.0)
Quote from: Pharinen on June 12, 2014, 11:43:07 PM
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.com
It is the same. But I dont know is there any new features in later builds.
Can some explain advantages of TL vs ML?
In my playing around with ML (and I'm excited!!) I found that my EOS M suddenly did not want to display the ML menus any more. When booted in M (manual) photo mode it used to display the ML menus when the screen is touched with two fingers. This has stopped for no reason at all - it just displays the "Welcome" screen ending with "Enjoy" So I could not change settings etc. I removed ML, restored the OEM EOS M 2.02, then camera formatted the SD card and re-installed ML.
Same response - only got the "Welcome" screen but no ML menu!!! Today after trying again, my hand slipped and I touched the SET dail's outer ring on the right side.... and MAGIC! There my EOS M came alive with the ML menus! I'm back in business!
I do not know if I posted in the right place or if this is even helpful to the forum members - it worked for me!
Regards.
Quote from: Oswald on June 13, 2014, 10:54:27 AM
http://tl.bot-fly.com
It is the same. But I dont know is there any new features in later builds.
Thank you for the help! :)
Thought I didn't get the headphone monitoring to work.. I was using the a/v cable which came with 550D. When I plug the cable in the screen just blacks out(it doesnt matter if the setting is on or off), camera is still working though. Maybe it thinks that I'm using external screen?
Have anyone got it to work?
E: The exact cable what I'm using is
Canon AVC-DC400ST, it should be 100% compatible with EOS M.
Quote from: Braga on June 10, 2014, 10:04:51 AM
You can stop the intervalometer by rotating the mode dial, by pressing MENU or PLAY, or by turning off the camera
Hi,
I just realised that there was a reply to my post.
On my camera the intervalometer will not stop if I use the dial or menu button. Only pressing "PLAY", switch from camera to video button or turning it off.
I am starting to believe that there is a software issue with the intervalometer not turning off on it's own. What a pity as I do not want to use infrared to control the camera. :'(
Regards
Harry
hello !
i have a question, i just installed ML on my eos M, it works great for videos but i cannot shoot pictures! i tried M, AV.....nothing works. It does focus but not shoot.
if i put a new sd without ML it does work but with the ML installed SD not working.
Do you have the same issue ?!
It is called shutter bug. Just turn off and turn it back on quickly and vuala now it is possible to take pics. :)
hello
i just turn off and back on but not working ;-(
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
When I shoot in H.264 (X2.5) the file is copied from the EOS M as a *.MOV file. If I now need to render it I use Adobe Premiere (or Vegas 12 Pro). Here is my problem: The original *.MOV file is for example 450Mb in size. If I use Adobe Premiere and render it as "loss less" I get a very large *.AVI file of about 8Gb! If I render, using H.246 the original file is shrunk from the mentioned 450Mb to 220Mb - indicating more compression... Is this right? Am I doing something wrong? How do I get the best "true" copy of the original file I used after rendering? Am I using the wrong rendering software?
Please help!
You have to learn about video formats.
H.264 is a standard covering lots of options. Canon is using just one subset of those options.
Trying to understand what's under the hood may try to blow your mind.
There are different frame types (I-frames, B-frames), different chroma subsampling options and more.
"You have to learn about video formats.
H.264 is a standard covering lots of options. Canon is using just one subset of those options.
Trying to understand what's under the hood may try to blow your mind.
There are different frame types (I-frames, B-frames), different chroma subsampling options and more."
Thanks Walter..... see below after another test video (please be patient - I'm still learning!)
"You have to learn about video formats."
Walter:
So let me put this in another way then. I have two EOS Ms. On the one I have ML (latest Nightly Build) and have taken the video option (H.264) to X2.0. I have shot the same video (simultaneously) with both of the cameras. The video on the ML camera has a *.MOV file much larger then the standard EOS (which is understandable). When I compare the two videos in my mind the ML video should be better? In fact I see very little difference.
I used Vegas Pro 12 to render both to a *.m2ts file, viewed both and they looked very much alike. I also made a second render and put the two videos side by side. I use a 120Hz latest generation 55" Samsung 1080p monitor for viewing.
Am I doing something wrong?
Quote from: Wynand on June 16, 2014, 02:43:13 PM
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.
ML has no influence on noise reduction, chroma subsampling, sharpening done there.
You *may* see differences in motion blur/artifacts if ML is able to manipulate I-/B-frame ratio.
Quote from: Wynand on June 16, 2014, 02:43:13 PM
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.
Ciao
Walter (not using H.264 that much)
Hi all,
I installed Magic Lantern on EOS M and there seems to be a few issues.
1. The overlapping focus box on Magic Lantern menu.
2. I cannot seem to use the rack focus. Any idea how to use it on Magic Lantern?
And thanks for porting Magic Lantern to EOS M. :)
Cheers,
Sandeep
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?
Quote from: canoneer on June 22, 2014, 11:31:44 AM
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?
I just realised that a 11-22 would give me approx. 52-104 zoom in crop, with close to no artifacts.
is there another way to go in ML menu without activating my touch shutter?
it is so annoying i can't use my touch shutter with ML. when i try to tap with my 2 fingers %95 it thinks that i used the touch shutter.
Press the delete button for one second (with the latest nightly).
You are fast! Thanks!
and i can't believe nobody has talked about this until now.
That's because it was added last night.
https://bitbucket.org/hudson/magic-lantern/commits/e876a7b1117e
http://www.magiclantern.fm/forum/index.php?topic=12380.0
Just checking again... I took a video yesterday with two EOS M cameras. One camera runs ML (Nightly latest version) and the other EOS M is standard. Both cameras were on tripods, running in Manual mode and were started with a single remote. After 30 seconds I ended the recording. The EOS M running ML was bumped up to X 2.5 in the movie menu and had a *.mov file much larger than the EOS M running standard. I could not see a difference between the two movies when I viewed them. Should ML not provide a better movie when bit rates are set higher than normal? Comments?
Wynand: I have never tried bumping up the bitrate on the EOS-M, but my understanding based on other people's tests is that increasing the bitrate does very little for image quality on Canon DSLR's. It might help with certain grades and fast movement, but I have rarely heard of people seeing a difference.
When I tried changing from 1x to 3x filming the same thing I noticed the 3x video to be sharper... that's just my un-scientific observation. Also I think when what your filming has moving objects it makes more of a difference. This was shot in 3x crop mode.
Quote from: florian.gerard51 on June 15, 2014, 10:36:51 AM
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
For me formatting the card and preparing it in MacBoot did away with it. Not sure for other cards though, mine is a Transcend 16GB Class 10.
What is the, video out put on the eos m,
Quote from: tweak on June 24, 2014, 07:13:29 AM
Also I think when what your filming has moving objects it makes more of a difference.
My observation as well, and it does make color grading a hell of a lot easier. Far fewer artifacts in the shadows to fight with, better definition on edges of moving objects. Video just has better definition in general.
Quote from: khail on June 24, 2014, 11:29:40 PM
What is the, video out put on the eos m,
HDMI and composite. It's in either PAL or NTSC, depending on the region. I don't think that in this case ML has anything to offer in terms of video output.
Is it 8 bit ??
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.
Quote from: kolen on June 26, 2014, 09:15:28 AM
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.
In my testing, the camera does record RAW video in full mode, but I couldn't really get anything out of it(sd card too slow, O'm a cheapskate). No idea aout the PDAF problem.
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.
Quote from: kolen on June 27, 2014, 08:40:53 AM
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.
Oh, I get it. Yes, it does have it, though again, I can't really shoot RAW because of my card.
So is the 5 second ML menu timeout eliminated in new builds? I guess not ?
Sadly, the menu still pops off after about 5 seconds.
What is the last build without the 5 second menu timeout?
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?
Quote from: kareemery on June 29, 2014, 06:35:11 PM
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 think there's no audio menu possibility(at least yet).
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?
Quote from: canoneer on June 30, 2014, 06:26:41 PM
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?
Press Menu.
Thanks!
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!!
Quote from: Wynand on July 01, 2014, 02:59:43 PM
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!!
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.
Quote from: velihukka on July 02, 2014, 10:36:02 AM
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.
Hi every ones,
Many thanks for the job !
I am new... could you please confirm that with EOS M and new FW 2.0.2 and with nighlty last ML, HDR and RAW are available for video recording ?
I am close to buy EOS M and I need to know...
Thx for your help !
Quote from: velihukka on July 02, 2014, 10:36:02 AM
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.
I bumped up the FPS but even going to as little as 35 FPS makes the camera "hang" - only way to rectify then is to take out the battery. The "crop" mode is blanked out.... Any ideas?
It means the FPS timer limits are wrong. Find out the safe values by changing the timers manually, and I'll update them.
Quote from: Oswald on July 02, 2014, 01:27:45 PM
It increases noise. It is true, I have tested it. Crop mode reduces aliasing and moire. because there is no lineskipping.
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.
I do hope the 'next' M (M3? or Pro model) will address the fairly poor H.264 encoder used by Canon (or Texas Instruments - their DSP (DIGIC) suppliers - I assume f/w encoders as well?)
The M3 could be a BMPCC fighter but it has to have much more attention to the video, if not 4k at least state of the art H.264 encoding with higher bit rates and true raw &/or HDMI output & 4:4:2 as well ?
Quote from: a1ex on July 03, 2014, 02:27:13 PM
It means the FPS timer limits are wrong. Find out the safe values by changing the timers manually, and I'll update them.
Thanks - will do and let you know. (By saying "timers" you mean manually upping the FPS till it creates issues?)
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.
Quote from: oenopion on July 05, 2014, 01:05:20 AM
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.
Have you simply tried to change the file type to .MOV, .mov or .mp4 ? A diff file extension/type means NOTHING to the content (many times) just the 'packaging' of the contents! Do not erase until you check a few things!
ex. - .3gp is just .mp4/H.264, aac audio, etc contents in a file wrapper.
Good Luck!
Yes, I tried a few different tricks. I'm thinking something may not have been fully compiled?
I may try starting a dedicated thread, for this may have also happened on another model?
Mods, can I break my question off into a separate thread?
The creation of a DAT file instead of a .mov file happened to me on a 6D using tragic lantern last year. I figured it might have something to do with the automatic restart function of ML and continuous file creation in the newer Canon cameras. I changed a couple of settings and no longer had a problem with the 6D. I've never had problems with the EOS-M. In any case, I've never really trusted the 4GB threshold automatic file creation on the Canon cameras with ML installed since then.
Hi cpreston,
I think your incident was the one I had read through. I rarely exceed the limit, but have never had any problems with the restart on my 600D, and a couple times on my 50D. It might have just been a fluke. Were you able to salvage the file? Or have any ideas to try? And what settings did you change, just curious?
Thanks, Sean
First time poster here, but LONG TIME camera user.
I installed the ML build from July 2nd, 2014 and found it had tons of amazing features, but it pretty much rendered my camera useless. I cannot reliably take still photos when running ML, and it's a struggle to get the intervalvometer to function. It seems that I have to power cycle the camera 3-4 times before the camera will take photos and then once I power the EOS M down again, all bets are off.
I'm surprised to not see more people complaining about this - is there something wrong with my camera / build?
Quote from: supertsai on July 06, 2014, 09:17:19 PM
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
Regarding my problems with the DAT file, I couldn't retrieve the files. I didn't have the patience to track down the problem. I just loaded a new version of ML and did a couple of tests to make sure I was no longer getting the problem. I've actually sold the 6D, now. I continue to us ML on the EOS M even though it sometimes feels like I'm playing around with an OS that is overrun with computer viruses. It's nothing like the good old days of ML 2.3 on my 60D.
Thanks, that's what I assumed. Luckily this was just some b reel type stuff, so i have no patience to try to track it down either.
And I hear you about the m. I love it for the size factor for hiking, but it is not the easiest to work with right now.
Quote from: Stedda on July 06, 2014, 09:26:59 PM
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.
I'll try a different card later today and maybe try the lens twisting workaround.
Is the out put on the eosm 1080, the Atomos ninja star is being released today that will be a nice addition to my eosm, if the output is 1080 and if not how possible is that?
Quote from: supertsai on July 08, 2014, 12:07:56 AM
Stedda, thanks for helping out the n00b! Glad to know that I'm not going crazy.
...maybe try the lens twisting workaround.
I do the twisting myself...
Quote from: 2blackbar on May 07, 2014, 04:00:08 PM
use speed booster wich i already modified for M :D
Anyone know a good tutorial to modify a speed booster to work with eos m?
Currently the only way is to grind your camera mount a bit and focal reducer mount, i bought cheap focal reducer from ebay for NEX, both mounts are very similar.Now my Camera mount looks like this, all lenses work normally :
(http://i.imgur.com/7tMQGYf.jpg)
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?
As there is not only one video on youtube we have not the slightest clue what you have done, which ML version you used and why something went wrong.
That's wrong!
Looks like the EOSM has a firmware installer. First post has been updated.
QuoteThe 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)
Yes, I've done everything as you just told:
1) Low level format in the camera
2) checked the firmware version (2.0.2)
3) downloaded 'magiclantern-Nightly.2014Jul08.EOSM202' from http://builds.magiclantern.fm/#/
4) copied unzipped files on SD card using card reader
5) run firmware update
6) after successfull update restarted the camera
The video I used as a guide: http://www.youtube.com/watch?v=lSS41UOUNIg
I can try to upload the video with my process of installation, if needed.
Here's what I did: http://www.youtube.com/watch?v=NkkOfEAmENA
Quote from: zenerv on July 10, 2014, 11:11:03 AM
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?
On that intro screen, just scroll left or right and you will go into the regular menus.
It is like the screen is the 1st screen of the menus?
Once you've done that it will come up on your last used menu screen as usual.
However, it does seem to return to that screen after every power down?
Quote from: RavingRover on July 04, 2014, 10:35:28 AM
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.
I agree with that and also usually film with 2.5x CBR and audio enabled. I have had people comment on videos I've taken noticing better details in the shadows and also even a lack of rolling shutter.
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!
I would pay good money if somebody could code a way to reposition the magic zoom window while shooting on the M either through the touch screen or the keys.
Quote from: keisconon on July 13, 2014, 09:35:35 PM
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.
Hi guys,
I'm thinking on buying an EOS M for video (short budget, I'll end up using it for vacations and the like).
I want ML because of 3 things: HDR video, focus peaking and audio metering.
I have two questions regarding ML on it:
1 - Is it stable enough for shooting a gardening vlog? I don't mind the occasional freeze (patient family crew) as long as it's workable.
2 - What kind/brand of card should I get?
Thanks
Quote from: velihukka on July 14, 2014, 10:55:47 AM
You can get to submenus by tapping the screen.
THANK YOU!!!
hey,
got a problem with the video-mode.
i've tested some nightlybilds, but none helped.
when i start a video, some seconds later (4-8 seconds) i automaticaly stops.
wrong settings oder realy a bug?
Most likely is that you have too slow an SD card to use all the things you have enabled with ML. What SD card do you have and what are your settings?
#define AF_BTN_STAR 2
in consts.h doesn't work for advanced bracketing, setting it to 1 fixed some of the woes associated with focusing between shots w/ advanced bracketing on
it would be great if continuous shooting fps (like native bracketing) was possible with ML bracketing. It is much slower between captures through ML. any advice?
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.
Latest nightly has an important fix from jpaana: https://bitbucket.org/hudson/magic-lantern/pull-request/571/correct-stubs-for-acquirerecursivelock-and/diff
Did you notice any difference?
Hi!
I installed ML just fine. 2.02 FW, magiclantern-Nightly.2014Jul30.EOSM202.
All video and interface tweaks work fine, except I can't shoot regular photos.
In photo or intelligent photo mode the the camera just focuses but won't fire with a full press.
If I turn on the 'touch to shoot' it will try to shoot and lock up the interface, no button or screen presses work, only taking out the battery.
Any ideas?
Using a sdcard without ML it works fine.
I can post dumps/logs later when I get home.
Quote from: kosmarnik on August 01, 2014, 05:56:14 PM
...just focuses but won't fire with a full press.
Any ideas?
Using a sdcard without ML it works fine.
I can post dumps/logs later when I get home.
Hey, welcome!
It's called shutter-bug, just browse in previous posts. It appears with EF-M zoom lenses, not fixed (22mm) primes or with EF-adapter. There are atleast two known? work-arounds when it appears, either quickly reboot your camera by pressing powerbutton twice, or just twist the lens and reseat it again while the camera is on.
I'm not sure if we still have any clues what triggers this bug, as it appears mostly to be random. Sometimes it wierdly seems to work fine for a while in a row.
When I use FPS Override to shoot a video at night with very low FPS (about 1),
the first few frames (of both video file and LCD when shooting) will go very dark, then very bright, and then normal.
Is this a bug? Or can you make an adjustment for it? Thanks.
Meanwhile I need to use EV -3 for a correct brightness video at daylight with a ND8. That's quite weird too.
Anyone using ETTR+DUALISO?
I tried ETTR but it just seems to generate random exposure times, most of the time much too long (several seconds in sunny daylight). The same happens when combined with dualiso
Hello,
Few questions on the EOS-M when going into ML if you don't touch anything for 6-7 seconds it comes out of the ML Menu, can this be changed?
With ML installed power saving options do not appear to work, I'm set to 1 min but is there something in ML overriding this?
How do I remove ML, I'm go to format, only option I have is format card, Keep ML. I tap the screen to toggle but nothing happens.
TIA
Format you card in your computer et voilà !
Or report the bug...
https://bitbucket.org/hudson/magic-lantern/issues?q=eos-m
Quote from: a1ex on August 05, 2014, 12:00:58 PM
Or report the bug...
https://bitbucket.org/hudson/magic-lantern/issues?q=eos-m
It's effectively impossible to tap to switch.
Bug report done.
Almost fixed, please review: https://bitbucket.org/hudson/magic-lantern/pull-request/575/restore-after-format-refactoring-fix-for/diff
Can't seem the option to shoot in video in Raw, is this an option on the EOS M ?
You have to load RAW_REC.MO or MLV_REC.MO first. See Module tab.
Quote from: Walter Schulz on August 06, 2014, 11:46:55 AM
You have to load RAW_REC.MO or MLV_REC.MO first. See Module tab.
RAW_REC.MO enable and camera restarted, still can't see an option to enable raw
If I don't touch anything with 7 secs the camera comes out of ML, not giving me enough time to have a proper read through options
Movie tab
Quote from: Walter Schulz on August 06, 2014, 12:38:54 PM
Movie tab
Nope not showing, just glanced through the whole thread and noticed a linky to TL, stuck that on and now have the raw option after enabling the modules.
I'm was using the latest ML nightly builds
Also the same also with duel iso, enable the ML IOS module but it does not show under the expo tab but shows using TL
Just noticed the EOS-M build was missing some modules and recompiled it.
Make sure you didn't disable all the modules by mistake from the Debug menu.
Sometimes when enabling a module and restarting, I don't give the camera enough time to fully power off. The camera flashes orange a few seconds after hitting the power button, wait until then to start up again.
Quote from: a1ex on August 06, 2014, 02:00:04 PM
Just noticed the EOS-M build was missing some modules
I was thinking that is "normal" and didn't report it... My bad.
Thank you a1ex !
Tried with my EOS-M, no problems, all modules loading perfectly.
The "ML menu dissapearing after 5-7 sec." bug is still present.
Quote from: vertigopix on August 06, 2014, 03:07:30 PM
Tried with my EOS-M, no problems, all modules loading perfectly.
The "ML menu dissapearing after 5-7 sec." bug is still present.
I've just tried the latest build, can see more modules now and enabled Dual ISO and the raw videos ones but still not joy
My guess is they are not loading, with TL if I pull the battery out then startup there is an error saying camera was not shutdown properly... modules not loading, using the on / off switch then its ok. With ML if I pull the battery I do not see this error hence I'm guessing they are not loading and that's why I can't play with raw video / dual ISO
Paste a screenshot of the "modified settings" menu (the one with a Delta icon).
Stop using TL, it is not longer maintened.
With the latest ML there is no problem !
low level format, latest build and all ok now
I own a Canon EOS-m with the Tamron lens E-M 18-200mm VS. After installing ML I can't take a photo. Changing to Canon 18-55mm all is ok. Anyone can help?
Shutter bug again, I suppose. Do a search about
Shutter bug twist lens
and test the procedure. Please post results.
Quote from: a1ex on July 28, 2014, 08:56:10 AM
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:
(http://tl.bot-fly.com/misc/_images/cfn.jpg)
consts.h for af_disable is 2 right now, which does not disable it.
Is there any way to shoot in continuous mode to get handheld bracketing to be a possibility?
Sorry for the noob post, but the forum search isn't helping due to minimum search term length constraints and Googling my questions only yields install videos. I have ML running, and I am stumbling through the menus with some luck setting up the intervalometer, which was my primary case. But I could use a bit of help getting to standard aperture and shutter speed settings because I can't seem to do this well from the ML Live View screen.
What is the Q button equivalent for our camera?
Is there an EOS M specific user guide out there?
Any guidance on standard photo shooting so I can quickly make aperture and shutter adjustments from the ML Live View screens?
Is there a better place to post noob questions? (This 14 page thread has so much info, much of it out of date, it really isn't terribly helpful for "getting started" noobs to start on page 1 and read through).
Thanks!
Doug
I tried all, but no success. With all Canon lenses ML works perfect, but not with the Tamron E-M 18-200mm. After turning on the camera I had the shutter bug. Then I twisted the lens off, wihout turning the camera off and twisted the lens on and it works. After turning the camera off and on again I had the shutter bug again.
Yes, that's why it's called a bug. Use the workaround you described.
On the EOS-M, when using HDMI output on an external while shooting, I notice two things.
A) Focus peaks are shifted half a screen upwards
B) Touch screen is disabled ---- so basic camera controls are gone . how to change focus point, access to "Q" etc
Are my observations correct or am missing something here?
--------------------------------------------------
Also how do we access the touch camera functions while in ML mode (direct camera screen and when using the HDMI output)???
another question for the developers.
I noticed PROP_AEB sets the range of EV's taken with built-in HDR. The max value was 10, has anyone tried to set PROP_AEB to get a greater EV spread (> +/- 2 EV)?
Thanks dudes
edit: tried to set PROP_AEB past 16 and it gave me an error sayin it wasnts 2 bytes, oh well...
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
Access to ML menu whilst using an external screen can be done by holding down the Trash Can button for 3 seconds. I usually set my camera up well before plugging it into a screen, but if I need to do anything it's usually only changing shutter speed and iso and this is quite easy to do by simply holding down the trash can button then going into the shortened ML menu (the one you get to if you press the Menu button after holding down the trash can). I'm not sure what other controls you would really need to use quickly on a shoot that aren't easy to get to.
Quote from: johangx on August 12, 2014, 07:40:14 PM
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
These are the "Pink Dots" aka AF pixels that are on the sensors, similar to what 650D and 700D have. There are ways to remove them, search for PinkDotRemover or use chroma smoothing options to mlv_dump (-cs2x2 or 3x3) or similar option in the converter you use.
Really stoked with the progress so far of ML on the EOSm. I've been using the latest nightlys as they release and I'm never really having a problem with anything I do, really stoked with it!
One question I do have however as I start to muck around a bit more with RAW is this:
What is the easiest way to remove the Pink Dots from MLV footage on Mac OS??? The fact that MLV now records audio on the M is amazing, but I can't for the life of me find information on a simple process (or any) to remove these pink dots from MLV on Mac OS.
Please help me internet gurus!
To add further to what I'm asking, I am aware of PDR for RAW files but what I want to know if there's something that can do this directly for MLV? It would be awesome if it was integrated into MLRawViewer somehow... surely there's someone who can do that :D .
Hi everyone.
I don't know if this is good place for my problem but I will try...
I tried latest nightly build for eos m and I noticed that shutter locks. I can only check focus on half pressed button and nothing happens when full pressed.
On card without ML all works good.
I tried full reset camera and ML configuration and nothing helps.
Has anyone the same problem? Maybe any solution?
Thanks in advance.
Do a search for
Shutter bug twist lens
and try the workaround
Working. Thanks!
But I made some test with different SD cards and I must say is important which one is used...
I have 3 card to test. All of them low level format from canon menu.
1st. Old SanDisk 2GB class 2. ML installed and I'm not noticed any problem with shutter even after longer fun.
2nd. New SanDisk SDHC 8GB class 10. On this card shutter is locked from first use. Helps twist lens but only to power off. Next start camera and shutter is locked again.
3rd. GoodRam microSD with adapter 8GB class 4. This card the same as first works without any problem with shutter even after longer play.
All of them tested in the same way. Always low level format. 2nd card even performed full format from windows, next low level from canon camera and always shutter is locked from firs usage.
Maybe this helps to improve next release.
Sounds strange to me. You're sure you didn't change lenses during this test? Which lens was used?
No, lens not touched during test. I have only 18-55mm.
Thanks for your input!
Curious about what the devs have to say about this odd thing.
Ciao
Walter
Hello,
I tried a lot of cards and I think, it works only with file-system FAT, not with FAT32 or exFAT. I formated a 4GB class4 micro SDHC card on the PC with file-system FAT, copy the file and then installed ML and all works fine including the lens Tamron E-M 18-200 VC.
PS.:
by using the tamron E-M 18-200mm, after opening the battery door, you need to twist the lens, but only one time. you can turn the camara on or off and all works till you open the battery door. With Canon lenses are no limits.
I think it is not valid all time. I have two 8GB cards and both FAT32. 1st works but second not...
I've been wondering and have been meaning to test it out, but it I haven't had the bug show up in awhile. Has anybody tried changing the camera menu to allow shutter release without a lens attached to see if it fixes the issue?
I tried changing the camera menu to allow shutter release without a lens attached an there was no difference. I only have the problems with the the Tamron lens E-M 18-200mm and ML, All Canon EF-M lenses works finewith ML.
I played another few days with 8GB SD class 4 and no any shutter lock... I'm really interested what developer says for this problem...
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...
Quote from: jerrykil on August 09, 2014, 07:18:09 PM
Is there any way to shoot in continuous mode to get handheld bracketing to be a possibility?
Greg did some research here: http://www.magiclantern.fm/forum/index.php?topic=8535.0
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.
Quote
edit: tried to set PROP_AEB past 16 and it gave me an error sayin it wasnts 2 bytes, oh well...
ML will refuse to change a property if its length does not match the length reported by Canon firmware. If a property is known to have different lengths on different cameras, but if the code is generic enough to cover all cases (usually the data buffer being large enough), you can pass 0 to use the autodetected length.
Quote
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...
Just tried it on 5D2 and 5D3 and it works fine; probably a camera-specific quirk. Report it to the issue tracker, with a video showing the problem.
Hi Im new here, but I read whole 14pages. So also I hawe shutter bug with EOS-M +18-55 STM. But fast on/off solve this. I bought the camera at shop and I already have firmware 2.0.2 in it. I tried 2 different cards, but bug still here. maybe it will help.
But my question: did Nightly support ghost images? or is there some other module which help to create panoramas? sorry for maybe dumb question.
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.
Quote from: tweak on August 19, 2014, 01:51:37 PM
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.
Wouldn't matter, more than half of all posts are people asking the same covered topics over and over again...
Quote from: a1ex on August 19, 2014, 08:56:21 AM
Greg did some research here: http://www.magiclantern.fm/forum/index.php?topic=8535.0
but I could only get it working on 500D. I should probably revisit it, since others also confirmed it on 550D and 600D.
Great thread. Apologize I couldn't find it on my own. I will play with this code and see if it works on EOSM.
Quote from: a1ex on August 19, 2014, 08:56:21 AM
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.
Quote from: Stedda on August 19, 2014, 03:28:26 PM
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...
As always, thanks for the hard work a1ex!!!
If you don't want to wait use google. Just line up your search terms and restrict your search as in
anything you want to look for site:magiclantern.fm/forum
Test Footage from EOSm shooting MLV RAW. Read the description for more info. By the way this is my first attempt at it so any info/help is greatly appreciated.
ShutterBug
I foung solution for me (EOS-M with 18-55 IS STM). Pulling battery out!
I think it is like rooting Samsung S1, if you dont pull battery out, you jump into boot loop and you will never get rooted phone.
1) format SD card (low-level)
2) copy ML files
3) install ML
4) turn off (wait until led stop blinking)
5) pull out battery and card!!!
6) wait aprox. 5sec and put all back
7) turn on
(dont need twist lens, dont need fast turn on/turn off, dont need special SD card, dont need new firmware)
Quote from: arcadio on August 20, 2014, 09:26:56 PM
ShutterBug
I foung solution for me (EOS-M with 18-55 IS STM). Pulling battery out!
Please read this thread about the shutter-bug: http://www.magiclantern.fm/forum/index.php?topic=8347.275
Quote from: Walter Schulz on August 19, 2014, 09:12:04 PM
If you don't want to wait use google. Just line up your search terms and restrict your search as in
anything you want to look for site:magiclantern.fm/forum
thanks 8)
I have the August 08 build on my eosm and last night I was playing with external audio. The first time I plugged in the output from my mixer I was able to change levels manually using the Canon menu. Then after recording a test file I noticed that ML wasn't showing me the audio levels. At this point even the Canon audio menu isn't showing me any levels any more. Camera reboot didn't help. Audio is being recorded into the videos though. Very strange...
I think I read some glitch with Audio in the 600/650D thread to a similar nature, maybe someone has more info?
Hello all,
I'm new here, sorry if repeating already discussed question, but didn't found in search.
Installed the 08-19 nightly build:
magiclantern-Nightly.2014Aug08.EOSM202.zip
In Manual mode the ML menu doesn't show up at all, in A mode works the Delete button.
When in menu, the submenu doesn't show up none of the submenus - is there some trick with the Q button?
Thanks,
Algkalv
Hi everybody,
I'm very newbie, sorry if disturbing with shallow issues, maybe you'll help me decide to buy a EOSM camera.
Is any chance to set EOSM with ML loaded to shoot with display turned off?
It seems you cannot do this with its original firmware.
I wish I use EOSM as a discrete package with 22mm (35mm equiv) lens plus a hot shoe old style 35 mm optical viewfinder.
When playing with the camera in a showroom, couldn't find a way to shoot in PASM modes with display turned off.
Turning off the display from a custom set button and continuing to shoot with the camera would be a very nice "pro" option,
saving battery and nerves while using fixed lens and the appropriate optical viewfinder.
Many thanks for your attention! All the best with your great ML projects!
Right now, ML allows you to turn off the display after 5 seconds of not being used. If a picture is taken or a setting changed, though, the display pops back up for five seconds. It might be possible to add a method to turn off the display entirely, but I didn't see it.
@cpreston
Many thanks for the information, would be so nice to find a way to keep the display turned off while shooting. In my dreams I imagine taking pictures with a fixed lens like the 22mm and an optical viewfinder without any annoying display response, in an almost Leica like photographic approach, just shooting...from my perspective, even you loose some controls, this feature might transform the EOSM in a more versatile tool.
Well what you could do is plug in the cord for an external screen, this would switch the screen to black... although I guess that's not the best option around. I haven't seen an option for turning the screen off completely besides that.
To the guy above what do you mean by "Manual mode"? The ML menu should show up any-time by either holding down the trash button for three seconds or two finger tapping the screen. If you want to switch between the 2 ML menus you have to press the "menu" button after either two finger taping or holding down the trash button.
Hope that helps.
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.
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.
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
I haven't read absolutely every post in here, so I'm sorry if I'm being repetitive.
When I adjust WB, I can't set it back to AWB. Removing ML doesn't help, it's stuck at the previous Kelvin value.
I need to clear all the camera's settings to get AWB back. :'(
In regards to my last post, I had said that "magic zoom" worked in crop mode, what I meant to say was that the "focus box" zoom works in crop mode, the "magic zoom" (fullscreen) on the other hand does not. This is still quite handy however and I didn't realise it was useable until now.
^To the poster above I always have the same problem. Once you move from AWB there is no way to get back to that setting unless you reset the cameras settings. I usually just shoot in 5400, but if you want auto it's almost best not to touch that dial! haha.
Quote from: cpreston on August 22, 2014, 05:45:33 PM
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.
You are on the money when using EF-M glass and regular shooting mode.
Quote from: andyroo on August 22, 2014, 07:40:59 PM
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
What they are talking about is using a manual focus lens like FD, PK or OM glass. You can get all these adapters to EF-M mount on ebay for about 10 dollars a pop. Then all you need to do is get the right size lens for your needs and set the lens to infinity focus, in this way your camera will not auto-focus and will take shots much quicker. (you will need to go into the camera settings and enable "release shutter without lens").
As for length of lens the conversion will be 1.6x, so you will probably need either a 20mm (32mm equiv) or 24mm (38.4mm equiv) lens. Old 20mm lenses are quite expensive and also quite heavy and big, I think your best best would be trying to find an 24mm in P/PK mount (Pentax), these lenses also seem to be smaller than most.
Hope that helps.
Quote from: sstbrg on August 23, 2014, 10:52:25 AMWhen 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.
@arcadio: Your above shutter bug doesn't seem to work 100%.
For me it indeed works first time straight after install. But this is nothing new, I've had luck to get it working 25times in the row, where I thought I had something. But then suddenly the bug was back again. It's random.
Anyway, add to your procedure that you take take two photos and then Press the power-button. Wait few seconds then press on again. The bug is back. Almost always for me. (11-22 lens and sensor cleaning off). However If I wait 2 minutes my luck is better and it usually works.
Maybe there is a soft shutdown pattern.
Quote from: andyroo on August 22, 2014, 07:40:59 PM
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
I bought an adaptor for EF lenses on eBay for $35. There a lot of them, but get one with a tripod mount, like this: http://www.ebay.com/itm/Electronic-Auto-Focus-AF-Lens-Adapter-Canon-EF-EF-S-mount-to-EOS-M-EF-M-camera-/331273182148?pt=US_Lens_Adapters_Mounts_Tubes&hash=item4d216b9bc4
There are also adaptors to m4/3 etc on eBay, or you can add a Nikon adaptor to the EF to EF-M adaptor, like this: http://www.bhphotovideo.com/c/product/742913-REG/Vello_LA_CEF_NAF_Canon_EOS_To_Nikon.html/prm/alsVwDtl There are lots of these as well.
Pick a lens that has a hard-stop focus ring. You could use the Tokina 12-28 f/4 on the EF to EF-M adaptor (gives you lots of focal length choice from 19-45mm FF equiv), set aperture at f/8, focus at infinity (beware some lens markings are not accurate, so check this before flight, or take a focus at about 1000 feet away), and use electric tape to make sure the zoom and focus rings do not move during flight. http://www.bhphotovideo.com/c/product/969884-REG/tokina_12_28mm_f_4_0_at_x_pro.html
High end lens option: http://www.bhphotovideo.com/c/product/655184-REG/Zeiss_1762_848_Distagon_T_21mm_f_2_8.html
Nikon (add nikon F adaptor): http://www.bhphotovideo.com/c/product/36905-GREY/Nikon_1415_Super_Wide_Angle_20mm.html
Cheaper nikon option: http://www.bhphotovideo.com/c/product/66980-GREY/Nikon_1919_Wide_Angle_AF_Nikkor.html
Hi there.
I loaded the latest nightly build but did not find anywhere to setup time lapse? A google search did not come up with anything helpful. Could someone here point me to some useful resources (web site, documents, tutorial etc.)? Thanks.
http://magiclantern.fm/forum/index.php?topic=5705.0
First hit when using
http://lmgtfy.com/?q=timelapse+site%3Awww.magiclantern.fm%2Fforum
I am using magiclantern-Nightly.2014Aug20.EOSM202
I find that if I use "Continuous Shooting" mode, I will get a burst of about 7-8 frames before the buffer fills and then if I try to shoot again as the buffer clears, the camera will lock up to the point that I need to remove the battery to reset it.
It does not seem to be dependent on manual or autofocus.
thanks for the time and please forgive if this has been covered.
Ron
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.
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 (Nightly.2014Aug20.EOSM202). 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.
- 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?
I understand the fact we are using nightly builds but I hope there are better solutions that I just missed. Thank you!
Quote from: $167 on September 01, 2014, 10:04:13 AM
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.
- 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?
I understand the fact we are using nightly builds but I hope there are better solutions that I just missed. Thank you!
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!
Hey guys
Sorry if this is a dumb question but is there a guide for using ML quickly with my Eos M. I've had ML on my T2i for years and have gotten very quick at using it. I'm shooting a wedding this Saturday and the eos M is my 2nd camera and I'm struggling to really feel comfortable with it so far.
In particular, i can't seem to find the Auto WB Adjust (I usually use this w/ a grey card when changing lighting situations with my t2i).
Also, I can't seem ot find Quick Settings. On the T2i I just hit the AV button and then I can use L / R for ISO, U / D for Kel, and the cneter button for Push WB.
thanks!!!
Quote from: mxma1 on September 02, 2014, 04:11:59 PM
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!
Hi mxma1, thank you for responding!
RE: #2 - I noticed the two tricks to switch A/S/ISO but wish there's a better way - As you said in Canon LV, there are two green triangles indicate whether I'm assigning setting to Aperture or Shutter when rolling the dial. But in ML LV, I have to guess and there is a slight delay when dialing - it really slow down the entire process. I could have done this in Canon LV but I would miss the Focus Peak badly. As far as ISO via the trash can - I have done it but it apply a full stop of ISO (eg. from 400-800) vs in ML, it goes 1/3 of a stop like 400>500>640>800.
One new issue I noticed is the White Balance in ML, say I was on AWB, when I go into ML manual and switch it to custom, I'm stuck with custom kal number. There isn't any way for me to switch back to AWB or Custom Presets. So I have to go into Canon LV again to do the adjustment, kind of a pain.
Anyway, I'm still very happy with ML for EOS-M. I look forward to having these fixed in future release. Thank you!
Quote from: dchen99 on August 30, 2014, 02:50:03 PM
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.
Are the other tools working in QuickReview mode (after taking a picture)? For example, the RAW overlays (they should work not just in LiveView, but also on the review screen).
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?
What is the max resolution that you can shoot RAW continuously on EOSM?
I am shooting most raw projects at 2.35:1 aspect ratio, what is the max resolution at this aspect?
What is the workflow like for shooting raw with sound? Do you just use the audio from the h264 file?
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.
Quote from: dpjpandone on September 06, 2014, 06:39:56 AM
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
Perhaps someone here can help me? I installed magiclantern-Nightly.2014Sep01.EOSM202 on my EOS M (2.0.2) mainly for Intervalometer shooting. But it don't works. If I am able to start the Intervalometer, I have no chance to stop it. I tried all buttons (I think the review button should do the trick?) The only chance was to put battery out. Also when I turned off and on again it started again. Sometimes it stopped, but then all freezed. The greatest problem: Also in normal mode I am sometimes not able to make a photo. Fokus is working, but when I press the button down no photo is taken. I formated, turned several times on and off and suddenly it works and then again the same problem.
And now the biggest problem: Because of this I tried to remove ML. But when I go to "format card" there is written "format card, keep ML [Tap Screen]". But when I Tap Screen noting happens. So, my most important question: How to remove ML? :-/
Thanks!
You may want to read the first post of this thread ...
Thank you for your answer, but this also didn't work. In the starting post I read:
QuoteUninstallation:
1) Run Firmware Update from your ML card.
2) Follow the instructions.
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.
Did I something wrong?
Thanks
Yes, you have to follow instructions found on page 1. From start!
Ok, I put ML back onto the SD card and then it worked. Thank you!
To the other point: Had someone else the bug that he was not able to take a photo? A little strange was that it still was the case when I removed ML. Now I formatted the SD card and in the moment it is working. Could it be that ML damaged something on my camera?
"Had someone else the bug that he was not able to take a photo?"
Yes - we call it shutter bug here.
Sorry that nobody answered till now but I think everybody got tired to explaine everybody new here in this forum what is going on with it.
Just put the lens of while the m is on and it will work again after putting the lens on again.
Just search for shutter bug and you will find more answers ...
^Just read any of the 16 pages of this thread and it would tell you that...
Quote from: tweak on September 11, 2014, 10:39:36 PM
^Just read any of the 16 pages of this thread and it would tell you that...
I don't blame the new users, The first time I came here I read the entire discussion, going thru lots of issues that had nothing to do with what I'm trying to do. All that just to find out one specific feature isn't available. Now we have 16 pages of threads (40 pages in tapatalk). I think it would be helpful to create a FAQ page for EOS-M. It would save everyone's time not having to read from scratch...
Ideally, someone who owns the camera, and is aware of its specifics (bugs/features), could compile a post with that information. I can sticky it and link it in other stickies, or add it to the first post.
can someone please explain the eos m raw aspect ratio to me? If I am reading correctly, shooting full frame requires stretching in post, but shooting in 3x crop mode does not? I am used to the 50D, 7D where you have to stretch if shooting 1280 60p (canon Q) but shooting 1920 (1728) doesn't require stretching....
What is different? Is it not possible to shoot in 1920 24p and select a smaller resolution like I am used to?
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.
@dpjapandone - you should be able to select any resolution and frame rate you like in the ML menu. I only ever shoot in 3x crop mode so I'm not sure that the full sensor mode even works properly on the M (anyone know???). You can only shoot up to a certain resolution depending upon what aspect ratio you have selected, the ML menu will give you the information as to what resolution is possible with what aspect ratio to be able to keep continuously recording.
I've just loaded magiclantern-Nightly.2014Sep12.EOSM202 and cannot figure out how to enable VBR. I noticed very early in the thread someone mention shooting RAW using VBR, but have not heard anyone mention it since, nor have I been able to get VBR to work with either of the last two nightly builds. Also can't find any info or documentation on VBR for the EOSM anywhere on the wiki, nightly build site or FAQ. Any help is much appreciated.
UPDATE:
As in subsequent comments, figured out that touching the screen acts as pressing Q, allowing me to open submenus, thus allowing me to enable VBR.
I figured it out, it seems full frame live view is always 720p so it behaves the same as other cams do when canon Q menu is set to 720p, therefore very crappy quality with heavy aliasing... it's a damn shame.
So what lenses are you guys using with this camera in crop mode? anyone experimenting with c-mount or other small format lenses? Any reccomendations?
Also, is there a list somewhere of the changes that need to be backported from One Percent's branch? I was thinking I could help with that. Or is the eosm pretty much up to date?
Quote from: tweak on September 12, 2014, 02:30:11 PM
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.
Good idea, tweak - Admin, pls put this up.
OK, it seems you can enter ML menu with long press trash, (thank god, otherwise impossible to navigate ML menu with ext. monitor attached)
but how to fake Q? any alternate method? Any hints on how to implement?
I had the same problem until I remembered the M is a touch screen. I think this is the question of how to get into the "Q" to change the settings within a ML feature???
yeah, I'm working on getting the play button to act as Q when ml menu is open, does anyone disagree?
Quoteyeah, I'm working on getting the play button to act as Q when ml menu is open, does anyone disagree?
Agreed. I also just realized that I could touch the screen in place of pressing Q. Found out how to enable VBR and a bunch of other functions that I couldn't find before. Feel a little silly now...
The touch function is great, but the menus in ML are, by neccessity, pretty cramped and I often touch the wrong item. This is not a critical problem, but it is an annoyance. If the ML menu could become more touch friendly overall, perhaps icon-based a la iOS, that would be great. That is a big job, so rather than reinventing the wheel (since the ML menu is already very well designed for use with physical buttons) I think that having the play button act as Q in the ML menu would be a good idea.
Just got the EOS-M and as soon as I got home... ML was installed. All went well and so far I'm loving all the features regardless of its minimal flaws!
Love the two-finger tap to get into the ML menu...
I'll be on the lookout for updates.
*cheers*
I'm brand new to the group, I have installed ML on my EOS M and am really keen to use the rack focus tool for macro photography stacked images. I can see that the nightly build has the Brack script included, which works so well with my Canon SX50HS CHDK build.
Does anyone know if this is a working feature on EOS M 202 ML build? If so, how do you get to it?
Hey guys,
Just got my EOS M and installed ML on it. I was hoping to use the audio features, but I see from this thread that they aren't available on the EOS M.
Two questions:
1) Are they impossible for this model and not to be expected eventually?
2) I've seen some comments about audio levels during recording which is one of the main things I want. Should that be there? The other nice to have would be the headphone monitors, so really curious if that one is possible and maybe coming later or if it's just off the table.
thanks!
b.
as far as I know... I noticed the audio meters are working actively. You just have to remember to turn off MLV audio after you are done recording in either RAW or MLV otherwise once you record it in h.264 without disabling the MLV Audio first...You won't get any audio as it has been mentioned in this forums as well!
It's a bit tricky but there are ways to work around it...
as long as you enjoy troubleshooting like 90% of us users are?
SJ
Just dropped and damaged my EoS M. Can you propose a replacement model that works well with ML. Already have a Canon 5d3. But looking for a smaller ML capable camera. Sorry if this is off topic.
if you don't need high raw resolutions, I would recommend the t3i (600D) it's one of the only cameras that let's you over crank to 36fps in 1080p and it has support for pretty much every feature in ML. if you require a fast cardbus go with t4i or t5i
I get exposure flashes (short duration brightening), every time I zoom with the 11-22 STM lens, and whenever I focus with the Canon 28 f/2.8 IS. This makes ML unusable with these lenses.
Anyone else have this problem?
Also the magic focus box flickers so much during record that it's unusable.
Canon eos m .... get a T3i ... cheap and works with the stable release
re: exposure shift:
check custom settings in canon menu -> change ae/af lock till u get the desired result
Need help.
How to access ML menu and Q without double tap and tap screen?
Because I use my M with external monitor, when monitor connect the tap screen will disabled.
How to use Delete button to access ML menu like other camera?
Thanks for support.
Hold the trash can button
currently no way to acces q from button, - working on it
Quote
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.
this is not my experience, no matter what I do, magic zoom is unusable in crop mode. I done exactly what you described and it's still all chopped up, are you sure you weren't in full frame and just thought you were in crop mode? I have noticed that framerate has an effect on this as well, in FF mode eosm idles at 30p, then changes to 24p during record and magic zoom glitches out again....
Probably a stupid question from a new forum member - and new EOS-M owner. I went to the Magic Lantern Downloads page - and saw that the current stable release of ML (V 2.3) supports a number of different cameras - BUT NOT THE EOS-M.
So which release or releases of ML do or will support the EOS-M? Do I have to access a "nightly-build" download? Or what?
Like I said, it's probably a stupid question. But I searched the forum and couldn't find an answer - so I'm posting it here. Hope someone can clear this up for me - THANKS!
First post of this thread ...
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.
Something happens in the first part of the code that is conflicting with commands.
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.
This means that some sort of command, once the battery is in the camera, reads the card, or at least a part of the code.
you will have to switch it off and on again to be operative. It will take only a few seconds to enable the M to work again, and I believe that the ram, by doing this, and the bug itself, are renewed, and the mistake put aside.
There must be a bug in the first lines f the program, conflicting with some instruction that follows.
If your M's led lights on when you insert a battery with magic lantern card inserted in it, who is ordering M to read the starting script?
I am just trying to understand what is happening. Could you find out please?
Thank you.
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? Concerning canon's hdr idea, i guess they did not want to make a good one, and just offered a minimal one.
I hope tha ML will solve the problem. STACKING, BRAKETING AND MERGIN ALL TOGETHER THE SHOTS. And offering a control of the levels aswell, so that we could see immediately the resulting picture. I'm just starting to appreciate ML on this camera, but it still lacks some functions that I would like it to perform. I used to load scripts, to enable these functions, and so, if anyone knows where to find them, I would be glad to test them and to work on them. I hope I have been able to express the concept in a proper way. Bracketing, 3 pictures, stacking them, and merging the job. Real hdr, with values that can be programmed in advance. Like styles. HDR1 HDR2 HDR3 Thakn you very much.
Guys need some help , after installing the latest batch. My EOS-m no longer works. The power button just blinks green real fast.
Any ideas
Quote from: Visir on September 26, 2014, 11:40:52 PM
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.
shutterbug, known issue. read thread for workarounds
Quote from: Visir on September 26, 2014, 11:40:52 PM
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.
Is this a problem? is this different from default behavior?
Quote from: Visir on September 26, 2014, 11:56:49 PM
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?
turn off "tap shutter" so that you can only take a picture with the shutter button (you prob have it set to take a pic when you touch the screen) Also check the sensitivity setting in canon menu
Thanks.
Shutterbug. Ok.
Switch it on and off twice. Second time it works.
False instruction handled in the starting script.
Default movie mode.
It will not take pictures but only video with this version of ML if you do not switch the camera off and on again.
The bug is there. Change default video mode command to picture. Thanks.
What does the letter M stand for?
Let me guess....
- "M" stands for the last letter of the word ".....mmmmm, ??? " ( thinking about taking a picture ). ( Thought ). Cliiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii ck. Oh gosh!!! :-X
I love innovation. I did not expect them to add Panda Mode. :o
The best ever camera for stills. Dead or alive.
Now you know. Just take your time for the time being .... till the next update".
It's a software problem.
I guess the third model they will call it "Zzzzzzzzzzz" 8)
I just bought a second one. I feel so Zen now. I can take a picture with my second one whilst my first one is thinking about it!
Wise choice!
I think that they are testing us to see if we are able to solve the "M's" problem.
............... 3
............... 2
............... 1
Which one?
Slow motion i guess.
;D
The right camera for nervous photographers!
:P
:o 8) :-[ ::) :-* :'( >:( ;D ;) :) ;)
We are all waiting for a brand new firmware!!!!!
8) :P :P ::) :-X :-\ :'( :-* ??? ::)
So when do you think they will discontinue "M"?
- "Mmmmmmmmmmmmm.... "
- Don't tell me you really believe they are still thinking about it!!!!!!
They sold us the whole lot!!! :-[ :P
- Just in time. :D
- I believe so.
What a bargain!!!!
- Ok stop it. It looked like a camera.
Didn't you read the specs?
- Too tiny.....
- Mmmmmmmmmm
:P
Cheers!!!! :D
Who should use nightly builds?
- Anyone who likes to live on the bleeding edge, wants to help ML development, and doesn't care about some features being broken.
...and anyone who have read, read and read the Canon manual...
Has anyone tried this on an imported EOS M2? I picked one up. Happy with it so far (*such* an upgrade from my 2008 450d), but with no jack for my intervalometer, long exposures and time lapse are a pain.
Thanks!
--- Carl
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?
Quote from: tweak on October 01, 2014, 05:49:11 PM
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.
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
Quote from: tweak on October 01, 2014, 05:49:11 PM
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
Just like the posts you are criticizing, the above adds absolutely nothing to the conversation either....
Quote from: tweak on October 01, 2014, 05:49:11 PM
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?
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.
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.
would headphone monitoring work with a cable like this http://www.bhphotovideo.com/c/product/765530-REG/Sescom_DSLR_550D_HOCF_DSLR_550D_HOCF_AV_Out_Headphone.html? if not will headphone monitoring ever exist for the eos m?
It does not work now and I don't know if it ever will.
Quote from: dpjpandone on October 03, 2014, 02:26:18 AM
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.
Pink dots are easy to remove once you have the workflow. Sound works almost every take for me, I don't have a problem with that. Headphone output isn't an issue if you have a monitor or shoot without sound (as a lot buying do). Do a lot of people need a tablet connected? Kind of defeats having a small package camera no? Ergonomics aren't that great I guess, but on the other hand it's great to have a small camera to easily take places. The resolution for M in RAW is still better than the others (regardless of the cons) in it's price range, so I don't think you can really compare them. Also ability to use C-mount lenses and the like in crop mode for RAW is a feature that the others can't even touch...
If it at least drives one person to read the manual before asking irrelevant questions I think it has.
Sucks there's no Greyscale option, maybe one day... I've been messing around about and starting to understand better where it's framed.
Hey guys!
Does anybody know if it is possible to sense 5V input on the USB port with ML? I am asking because with CHDK, it is possible to trigger the shutter by putting 5V to the USB connector (plugging in a USB cable) and with a remote shutter port missing on the eosM, this could be a perfect remote shutter mechanism, while still retaining a free mic-input port for those who need it (avoiding solution described here: http://www.magiclantern.fm/forum/index.php?topic=11930.0).
The CHDK mechanism is described here: http://chdk.wikia.com/wiki/USB_Remote
Hi,
Coming back to the EOSM after a long time since the camera right dial push doesn't work anymore after the camera fell from my hands.
Must say that the overall ML experience has greatly improved with lot lesser bugs. The pink dots on RAW / MLV recording are still a pain workflow-wise. But otherwise awesome.
Build: 8 October 2014.
Thank you all developers for keeping the development going.
Another thing. I want to shoot S3D using 2 EOSM's. Anyone know if the best way to sync the cameras - ML way or non-ML way?
hi all, new to the forum. been using ML for a week now and I can't imagine how lame the eos m (or any other eos for that matter) would be without it. once you use it you can't go back. for the past week i've been browsing through the forum and slowly understanding all the features and workarounds in ML for this camera. I got to say the raw video is is simply a joy, filming in mlv and removing the pink dots with mlvMystic gives marvelous results, even if only at 720p 24fps (I wouldn't do 1080p anyways due to its insanely high data consumption).
anyways, one thing I couldn't find is how users of this camera can transfer mlv files to computer; when I plug the camera to pc via usb, all the files I can see are JPGs and MOVs. to access files of different extensions I must remove the sd card use a card reader, only then I can find all the existing files in that card. Since I'm is test mode, the process of removing the card repeats numerous times during a day, so wear becomes an issue.
well, thanks Magic Lantern and all its developers and enthusiasts. hope I can contribute with something nice soon.
SD-cards and slots are specified for 10,000 "mating" cycles.
Do the math ...
Quote from: Walter Schulz on October 27, 2014, 05:28:17 PM
SD-cards and slots are specified for 10,000 "mating" cycles.
Do the math ...
was that referring to my post?
well, seems canon won't let any file other than jpg and mov to be sent to pc via camera usb. why? one can only guess. I'll stick to using the card reader...
Quote
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.
Tried this, but it didn't make any difference on my camera.
Tried the nightly build that you are using, and also the latest nightly (8th October).
Hi everyone,
First my apologies for posting this here again, but I guess this a better place in the forum for my question as it is specific for the EOS M:
I'm running magiclantern-Nightly.2014Oct08.EOSM202 on my EOS M.
The ML screen displays a framerate of 29.973 although the framerate is set to another value (eg. 24 fps or 60fps). Tried it with both PAL and NTSC settings. FPS ovverride is not activated.
When I'm recording, the files are recorderd with the fps set in the main menu.
However those false fps rate detected by ML seems to affect the availabe settings for recording raw video as it always relates to those 29.973 fps.
Anyone else experiencing this issue?
Thanks!
I think that this indication is related to the LV framerate, not the recording framerate.
When you start recording you can see the "real" framerate upper right.
No, the displayed framerate does not change. When selecting the resolution all available options relate to those 29 fps.
fps override? like it was said before, the display is always 29.97
Upper right, under the red "rec" dot, not the "big" fps numbers.
did anybody try the intervalometer in conjunction with silent picture mode?
it would be a treasure for time lapse since there's no shutter activation and pics come in raw but for some reason my eos-m stopped after a random number (sometimes 40, other times 10 or 11)of photos were taken. will try some other settings and let y'all know in case I can solve it.
About the eos M shutter bug: is there any problems with manual lenses? What i understood its only with eos m kit lenses.
Just a preliminary note - I managed to solve the shutter bug with a new card and a new install. I still need to investigate the root cause but I have a good idea about a process to fix this.
Here is what I did:
- I had a 64GB card (Transcend) in my camera that was affected by this bug
- I got a new 64 GB card (Kingston) and DID NOT prepare it at all in anyway
- I downloaded the Original Canon 2.02 Firmware update and put it on the new card - NOTE: I tried to power cycle camera and the shutter was working, as expected, when the card with ML was removed
- I inserted the new card in the Camera and reflashed the original 2.02 Firmware (Shutter still worked after power cycling camera)
- I downloaded the latest nightly (8.11.2014 at the time of writing) and dropped it into the new card
- I inserted the card again in the camera (I used a memory card reader for all the operations; shutter was still working) and repeated the firmware update process to install ML
- ML installed successfully and told me to power cycle the camera (I did not mess with the boot settings - just told it to reboot camera)
- Camera rebooted and.... SHUTTER WAS WORKING!!!
I could not believe it, so I cycled it a few times more and it was still working. Inserting the old card back would immediately reproduce the bug but with the new card, working fine.
I followed to the letter the official instructions to update firmware from the Canon site (P mode, etc.)
Next up I am going to format the old car, actually, even wipe all the partitions, format it similar to the new card and going to try and reproduce the "fix" on it
Hi Jaco2k this sounds interesting to me.
But ... Question: Is someone out there still working on ML or are all gone to Apertus?
Hi!...my first post here. I have the Oct 8th Build for EOS m...
the zebras stop functioning in video mode when I use Magic Lantern to set my ISO to any non-standard number, like 160, etc. If I set my ISO to 100, 200, etc, the zebras return.
Also, I see no way of zooming in whilst in movie mode (not recording) other than the magic zoom box feature. any ideas on this? I love having that full screen zoom before I record. (or snap a shot!)
also, the magic lantern menu dissapears after 5 seconds of idle. not cool!
QuoteI see no way of zooming in whilst in movie mode
Prefs>LiveView zoom tweaks>Zoom on HalfShutter>
hey thanks man! so cool!
Just a quick question I have just brought a EOS M and wanted to know if the ML firmware is installed into the camera or does it run of the sd card.
Look at the picture in the first post of this thread.
There are 3 requirements:
- Camera bootflag set. This one is indeed located in the cam. Has to be done once.
- Bootable card. Each and every card you want to run ML from has to be enabled.
- ML files on card: Autoexec.bin (= ML "firmware") + ML directory (modules, settings and other stuff).
For installation you need a ML FIR file, too.
Cam with bootflag set will look for a bootable card. If found it will load Autoexec.bin and run ML as a task. Very much like a program loaded at startup in your computer.
Thanks for the info, so if there is no ML software on the sd card it will use the Canon firmware ?
It will always use Canon's firmware because ML is not firmware but a task running on Canon's firmware (= OS). And of course ML won't run if no bootable card is there.
Top of page -> User Guide -> FAQ
Once again thanks for the info :)
UPDATE on "Zebras not working at non-native ISO numbers"
This, for some reason, is no longer and issue on my camera. I posted earlier that zebras were not working, but they are now. So, ignore that earlier post (which you probably already have :)
UPDATE 1 - 19 - 2015
Well, again, the Zebras, when using non native ISO numbers, no longer show up. I don't know why it worked for a time. But now the Zebras disappear when I use 320, 640, 1250, etc. When I use 100, 200, etc, the Zebras show back up. The Zebras always disappear when I am actively in the ML menu, but this has been expected.
So, anyway, I got an EOS-M that's still factory default, with no bootflag and doesn't use ML. One day it just crashed while I was shooting, and when I turned it on again, if I use the green A auto mode, the frame would be in 1:1 cropped mode. There's no way to return this to regular 3:2 mode even after resetting to factory default, so now one of my EOS-M is stuck in 1:1 when in Auto mode. Not that I complain. *shrugs*
I just want to put this out there in case someone experience the same thing. Changing crop mode would be a nice thing to have in ML though.
feureau, if factory reset doesn't work. Try re-flashing the official firmware update (again) even if you already are on that version.
http://www.canon-europe.com/Support/Consumer_Products/products/cameras/Digital_SLR/EOS_M.aspx?type=firmware
So i just received 2 Sandisk Extreme 32gb SDHC cards from BB- First thing I did was load ML onto them, and 2 EOS M's (one visible, one IR) have been working without the shutter bug on the 11-22 and 18-55.
interesting...
However, I think I did something similar to the Samsung 64gb card I got a when they were on sale, and it worked for a while, and then I did something to it and now it doesnt...
wonder if its a matter of location on the SD Card or something.
Just installed the latest EOS-M nightly build but the menu doesn't appear when I tap two fingers on the screen, just the ML info screen. Anyone else had this problem?
we all had it, just press SET button ;)
does focus trap work with EOS M?
Is there an overview which functions works on every modell?
http://www.magiclantern.fm/forum/index.php?topic=11108.msg107864#msg107864
I have the Eos M2 and firmware version is 1.0.2. I don't surpose Magic Lantern will work with it.
@Marcandsebe -- do a simple upgrade from a Canon's site to get the latest firmware (2.0.2) from here... http://www.usa.canon.com/cusa/support/consumer/eos_slr_camera_systems/eos_digital_slr_cameras/eos_m_ef_m_22mm_stm_kit?WT.mc_id=C126149#DriversAndSoftware
and then install nightly for EOS-M from here... http://builds.magiclantern.fm/#/
EOS M2 is an entirely different camera. You will not be able to run ML on it until someone ports it.
Didn't see you wrote down Eos-m2 til just now... My apologies on that typo!
Hello, could you help me with problem with Advanced bracketing on EOS M?
In Av mode: Bracketing type: exposure, frames: 2 , increment: 1EV, sequence: for example 0 - --, ISO shifting: OFF, Post scripts: OFF
First couple of bracketed pictures is ussually good, from second picture starts unforeseen behavior: burst of pictures - sometimes incrementaly bracketed (for example: first -1EV, second -2EV, third -3EV and so on, and so on...), sometimes with standard exposure. Number of pictures seems to be random (five or more). After burst of bracketed pictures, exposure compensation stays with last values (for example -5EV). I can'n find any way to use advanced bracketing in Av mode.
Other settings: RAW, WB: K, No AutoISO, no intervalometer, no motion detection, no Auto Lighting Optimizer, ML: nightly 2015Jan03 EOSM202 (older builds with the same problems)
In M mode, everything is O.K.
I tried the same settings with 5D III and there is no problem, everything is O.K. in M and Av mode as well (I was testing ML on theese cameras for first time in last several days).
Many thanks to developers an ML community for amazing work!
Hey Everyone, I'm planning on using my Canon M for remote purposes during certain sporting events. I want to use the M because it's smaller than my 7D and can fit in tighter spaces. The issue, of course, is remote firing. I use Pocket Wizards Plus X. I downloaded the latest ML build and it doesn't seem to have the "sound trigger" feature. Any idea which update had it last??
Not available for EOS M:
https://builds.magiclantern.fm/#/features
Shoot -> Audio_remote_shot
Hi all
Firstly many thanks to all the developers for the eos-m software which is installed and working in my camera. I am an experienced film cameraman since the 70's but relatively new to the digital technology, hence need the help of you "young-guns" with some questions.
I have carried out quite a few experiments regarding the bit-rate settings. I have shot static shots as well as repeatable pan & tilt sequences on both static and moving subjects. I have repeated each test on 1x (default) 2x and 3x bit rates to examine the difference. Problem I have is that visually I can see no difference at all between 1x, 2x, 3x bit rates even though I can see the overall bit rate chance from 43.9 to 61.3 (which in fact does not go above 61.3Mbps regardless of setting). On 1x the average bit rate is 43.9, this increases to 61.3 at 2x setting but will not go above that at any setting above 2x (in fact it's about 1.8x).
Visual checks were done on various platforms including Premier Pro, VLC etc (including magnified modes) as well as HD Panasonic 50" monitor and MediaInfo for digital information. I have checked to make sure settings work and if bit rate is reduced (say 0.6x) the picture obviously degrades. All tests were done in same lighting/asa/speed conditions (100asa 1/50th 25fps 6400degK) with 50mm prime Nikkor AI lens and 95MB/s ExtremePro SD card.
I would appreciate it if anyone can tell me if they can see definite change in quality in any setting above 1x (default) and if so, which area(s) they see the improvements? I might be missing something? No age jokes please as yes I have new glasses, can see and got few younger friends to double check the visual tests lol!.
Many thanks in advance and best regards to all...
I came to the same conclusion , there is no difference between 1x and 2x but there is huge difference between 0.9x and 1x.
Maybe there is some more detail with a lot of movement but its really not that visible to justify bigger files so its just better to leave it at default.
Many thanks "2blackbar" good to know we weren't imagining it :-) Likewise, will keep to default and save space on storage.
magiclantern-Nightly.2015Jan15.EOSM202
Saw the posts about CBR and this must be a build issue. I certainly was seeing up to 235mbps bit rates for 2kHD using a TragicLantern load a while back. I recently did some video w/ latest ML, set to 2.5CBR, and the resulting vids were peaking at 114mbps rates, some at same setting only show around 99mbps.
Just performed a 2.9CBR vid out the window and it shows - peaks to 155mbps, mostly 135mbps peaks. I then upped it to 3.0CBR and got - crash/stop - 4-5 secs only - peak around 160mps!
I loaded in the 'last' TL build - tragiclantern-v31337.TRAGIC.2014Dec19.EOSM202 - at 3.5CBR it crashed - <10secs only (saw a peak of 168mbps), went down to 3.2CBR and got peaks of 133mpbs.
Put in my old TL load (used for audio remote trigger) which I believe was where I saw 235mbps peaks and - only saw 150mbps peaks - and 3.5CBR crashed after 10 secs, whereas 3.2 worked fine - about 133mbps.
So either I am GREATLY MISremembering getting peaks of 235mbps (saw when SD card was new) OR since my card has been useds LOTS, a reformat and so forth may show those higher results - which I think some ppl have seen when attempting RAW video.
So, 133mbps = 133/8 is ~16mBps, FAR from the 30mBps M SD writer speed capability (30mBps * 8 = 240mbps) of M (once again I think we think that is the speed limit of the writer ?).
So something has changed in the year or so I saw 235mbps peak, and the only change was/is the fairly heavy use of my SD card and NO reformat or conditioning !! (Sandisk UHS-II 80mBps read, 60mBps write or some such)
So maybe reformat/condition your fast SD card before doing critical video - test and see !!
On the other hand, I do not think using the Canon encoder algorithm, that a 200mbps recording is any usefully better than is a 133mbps or maybe lower.
Most of the above testing was done in 'crop' mode, both TL & ML so a higher bit rate and crop mode will give you the 'BESTEST' Canon video, maybe as good as RAW via ML/TL or better !!
PS: But honestly Canon 1080p 2kHD video is so soft that it barely looks better than other makes 720p !! This really is a shortcoming of Canon at the moment - IMO ! And 4kHD blows it away even via an iPhone 4kHD !!
Good Luck ALL !!
Hi there!
I am wondering how to format/remove ML from my Eos-M? The problem is that when I go to the format-tab like Ive normaly done on my 60D, I can´t select the "remove Magic Lantern" option. It says "Tap the screen" but when I do, nothing happens... Since I want to be able to use this fast SD-card in my 60D tomorrow for a shoot, I want to be able to get rid of the Eos-M-ML without screwing up that camera.
Does anyone know how to fix this?
Many thanks for any reply!
/Bobby
If you used the format option on your 60D to wipe ML from the cam you wiped the card instead. Cam's bootflag is still set. You have to run install again to reset it.
Read first post of this thread.
Okay, I did not know that. But the problem is still that I need to uninstall it from my Eos-m first, if I try to do the update-way of uninstalling it says "Memory card containing firmware is required...".
Thanks alot for the reply!
Read first post. And follow instructions.
I have had ML installed for some time and now want to remove ML. I have followed the instructions given in the first post...
Uninstallation:
1) Run Firmware Update from your ML card.
2) Follow the instructions.
There seems to be no 'instructions' to remove ML after running the firmware update.....
Thanks in advance!
Mike
Edit - Found how to do it!! At the bottom of the screen you need to wait for 30 seconds to remove the boot flag. Obvious really but the initial post could say this to clarify the uninstall process. If you simply reboot without waiting the 30 seconds, ML is not removed. (And yes I was being slow but finally caught up!!)
Just read the screen messages ...
All it says is.....
'Please restart your camera'
which I do (switch Off and then back On) - and then the camera still has ML firmware! Sorry, but I must be really slow tonight, as I cannot see a way to remove the ML firmware.
Mike
Wait for 31 seconds after this message appears.
Guys!
Possible break through on the shutter bug.
Try renaming your SD Card volume to EOS_Develop.
For whatever reason, I can make both of my Ms exhibit and then cure the shutter bug with this trick. It must be related to how the camera starts up and looks for the card.
I name it that, it works, name it something else, it stops working. format and rename, it works again!
You sure about that @slvrscoobie?
Quote from: slvrscoobie on January 22, 2015, 11:23:43 PM
Try renaming your SD Card volume to EOS_Develop.
This makes sense (I also believe it's something from the bootloader). If you experience the shutter bug, please try and report.
@slvrscoobie: does it matter if you write the label as upper-case?
No cigar.
I renamed my ML card to EOS_Develop - shutter is still buggedly locked, will operate only after lens twist trick.
This happened with the 18-55, and also the new 55-200 mm lens.
It ALSO happens with the 11-22 if it is in the shooting position when you power on the camera, but NOT if you power on with the lens collapsed.
However, then the message "Set lens to shooting position" does NOT appear! This always appears with a collapsed 11-22 lens with a non-ML card.
The 22 pancake lens does not cause the shutter bug, only the 3 other lenses.
Yes, I've got all four lenses, being an EOS-M fan (or freak?)
Hope the above helps diagnosing...
Changing the card name makes no difference on mine - at the moment mine works correctly with all lenses.
I'm trying to make the problem happen rather than fix it, so I can try and diagnose the cause.
The problem stopped on my camera after a low level format of the SD card in the camera, and has not returned since.
Phil.
I tried that and - wow! Indeed, no shutter bug anymore.
Very strange, though: Letting the camera do a low-level format did NOT remove the autoexec or the ML files, but did indeed zero the DCIM and MISC folder, and removed a folder named "old FIR". The card was also renamed to EOS_DIGITAL by the camera.
So, this looks promising. Anyone else care to try? Will your autoexec and ML folder be left intact after the low-level format?
With format setting "keep ML" ML will just do that.
Ha! Yes - it's *supposed* to leave the ML on the card... my bad! ;D
BUT: Loading the latest nightly build, the bug is back! New low-level format, shutter bug gone !
So, everytime you load a new nightly, do a low level format (and lose the photos on the card...) ?
You lose the photos if you format the card in both modes ...
What about copying them to your computer first?
"Loading" means: Fresh install or "extract nightly contents and copy contents to card"?
"What about copying them to your computer first?"
That goes without saying... :P
Seriously, does the fact that the "Set lens to shooting position" is missing on power-on give any clue to the problem?
"Loading" means: Fresh install or "extract nightly contents and copy contents to card"?
In my case, it was the latter. I did remove and trash the old before copying the new.
But, if this means the problem is solved, i.e. do a low-level after a nightly, then all is rosy for the future... :P
Sorry if this has been asked before, a quick search of the forum didn't help:
Can you use the ML intervalometer for taking pictures with an open shutter, i.e. not mechanically straining the camera taking hundreds, even thousands of photos?
http://wiki.magiclantern.fm/userguide#intervalometer
Thank you!
Looks like it is not possible to take full-res stills without shutter clicks :
"To make a timelapse without increasing shutter count, do not use the intervalometer; instead, set FPS override to a very low value (for example, 3fps) and start recording.
When using the intervalometer in LiveView with noisy mode, your shutter will wear twice as fast than outside LiveView."
I have now bookmarked the manual, which I could not find by searching for "EOS-M manual"
Why should ML team create an EOS M manual? ML team codes ML and a User Guide (the upmost line may contain a hint about that one).
If you go to
Top of page -> Downloads -> Browse Nightly Builds -> Features
you get a list with links to forum threads and User Guide sections.
And FRSP is still in development.
I used those search terms here, because I thought they were relevant to the EOS-M model and ML... ;)
But, I found what I needed, i.e. the ML User Guide, and am happy with having found it.
Testing the low fps rates, I can get down to about one frame in every 5 seconds, but no longer interval. So, shutter clicks will increase...
But, all in all, any EOS (be it either my 550D or the two EOS-M) gets a fantastic boost by ML - so thanks to all involved!
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 second that regarding FRSP is still being in development.
Be patience guys!
[emoji106]
Quote from: Janke on January 26, 2015, 02:23:15 PM
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! ;)
Sounds marvelous... Any chance you could show us a footage to see what that particular 3x crop looks like? [emoji2]
I'm a new user of ML and have played with it for a few days (usually my best way of learning) and searched the forum and User Guide, but still have a question I hope you can help with.
When trying to use the Magic Zoom (which works) I can't find any way of changing the focus point that it zooms in to. If I use the Canon menu's I can change it by touching the screen and then hitting the zoom icon, but whatever I have selected in the Canon menu gets stuck as the focus point when I go into the ML menus and use Magic Zoom. I am using old Manual Focus lenses via a non electronic adapter so the camera doesn't think I have a lens attached (if that makes a difference) but again the Canon menus allow me to change the focus point by touching the screen, while the ML menus don't. I hope I have explained myself clearly.
Am I doing something wrong, or is this not supported?
Thanks, Neil.
DeafEyeJedi asked: Any chance you could show us a footage to see what that particular 3x crop looks like?
Try this:
http://youtu.be/uKWW0rr5GR8
Note that this is a very early and quick test, focus isn't the best possible, and the shadow at lower left disappeared with a rotation of the lens mount. This lens is old, intended for standard definition ENG cameras, resolution 720x576, so no wonder it's not perfectly sharp.
I have a much better lens, a Canon f 1.8, 12.5 - 75 mm TV zoom, but it's only 5x. No YT demo at the moment, sorry...
Btw, does anyone know the method to start the camera without ML loading? I understand on other camera, it's holding down the set button while powering up, but it doesn't seem to work with EOS-M ML?
Wondering if not loading the ML would help with the shutter bug. It's still happening with my 18-55mm. No shutter bug on the 22mm.
Just change to a card without ML - that's what I do...
Try the low-level format option, the bug disappeared for me using that trick.
Anybody tried out the Tamron 18-200mm EF-M lens with Magic Lantern yet? I was wondering if you get the shutter bug with that lens.
So far it only seems to affect the Canon EF-M IS lenses--meaning all but the 22mm prime. Apparently EF lenses mounted via the adapter won't trigger the shutter bug.
I checked with some owners of the new Tamron 18-200mm EF-M lens. It IS affected by the shutter-bug.
Dang!
Have they removed the RAW video from the Nightly build for EOS-M? It's not showing up. I heard it was working... but where, how?
It's a module. You have to enable it in Module tab, restart the cam and configure RAW record options in Movie tab.
I got it, but it stops after a couple of seconds. Is there a limit on how long it goes?
Yes, there are limits.
Start reading here
http://www.magiclantern.fm/forum/index.php?board=49.0
with special attention to
http://www.magiclantern.fm/forum/index.php?topic=6215.0
Thanks, Walter.
Clips all stop at 2.5 seconds, 114,465kb. Is there a way to overcome this? Otherwise it's useless to me.
Which modules are loaded?
Global draw on or off?
Which resolution and frame rate?
How fast is your card? Debug tab -> Benchmarks -> Card R/W benchmark (5 min). Use photo mode, global draw off.
Hi Walter,
The pink dots in RAW were a deal killer.
My other major problem, with EOS-m, is that I can't get any overlay info while shooting. Nothing appears at all when recording, so I can't judge exposure. Is there some trick or module to enable?
Maybe you're a bit jumpy?
Are you recording MLV or RAW? If MLV: You may want to set this option in Movie tab -> RAW video (MLV) -> Global Draw
"Maybe you're a bit jumpy?"
No. I'm a filmmaker, not a beta tester.
I turned off raw. It's in movie mode, bit rate 2.5x. The 3.0x wasn't stable at recording. The slower speed seems okay, but no overlays work. Global draw is on for all modes, but as I said, it doesn't appear.
Quote from: joeg on February 04, 2015, 10:02:17 PM
I'm a filmmaker, not a beta tester.
Yes, Director McCoy.
You pressed INFO several times to toggle until ML's overlays show up?
Actually I cleared all settings in Canon's menu to try and default it and try again, but now I have a brand new issue.
The screen that allows firmware upgrades has disappeared. I'm trying to just reinstall Canon's 2.02 firmware, but the menu choice is in the ether. Any idea why it disappeared?
Update:
Odd happenings, very flaky results. The firmware finally reappeared, but my shutter no longer works in picture mode. The camera won't take pictures, even with a different card without ML. I reinstalled 2.02 firmware, cleared settings (again), but the shutter no worky. Is this a known bug?
Update 2:
Changing to the Canon 18-55 lens got the shutter to work again. The other button in the top right still doesn't though. I'll try changing lenses again.
Known as "Shutter Bug".
https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug
My "shutter bug" is a bit odd. Shutter works on Canon 18-55, but I can't take stills now with Nikon lenses. Nothing happens.
There is also this:
"Firmware default completely disables bitrate control."
I find myself stuck with "FW default," and have lost the one reason I had for installing ML in the first place. There doesn't seem to be any entry about getting the bitrate control BACK again.
I bemoan the apparent dying of the magic lantern project, but I completely understand it. I check these forums to see if anything new has happened, but all I ever see are the same questions and ignorant requests. I don't personally have the talent or knowledge to code and I certainly don't have the patience to deal with questions from people who can't first take the time to understand their tools. I feel bad that I've never contributed more than money to the project, but I am very grateful for what has been given me and it's ability to help me be a "filmmaker".
Now that I've said that, if you want to use manual lenses you need to set the camera in the menu to release the shutter without a lens attached. This is not an ML issue.
I'm using Nightly.2015Jan29 but ML menu disappears after a few seconds.
I've found similar situation reported here.
https://bitbucket.org/hudson/magic-lantern/issue/1974/6d-in-live-view-mode-ml-menu-times-out
Is there any way to extend the time menu appears?
Quote from: farb on February 09, 2015, 05:52:04 PM
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.
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.
Quote from: DeafEyeJedi on February 08, 2015, 09:49:34 PM
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).
Then, import the DNG files into Photoshop Lightroom and export them as TIF files with no pink dots.
Quote
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.
Quote from: lapser on February 09, 2015, 07:00:27 PM
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.
Pressing the shutter halfway should also do the trick.
But I'm on a mac @ lapser -- RawTheraPee is somewhat an OK app. Just don't understand or where to start batch process within this app.
Unless there's a Mac version of RawFlow? If not then perhaps I'll have to run it within VM ware?
Quote from: DeafEyeJedi on February 08, 2015, 09:49:34 PM
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 :)
Hmmm... Regular Silent Photos did work and still do but haven't been able to locate a Full_Res Silent Photo module for EOS-M as of yet.
I have been able to get FRSP to work well for both 5D3 & 7D.
Just not the M...
Quote from: jpaana on February 11, 2015, 09:50:31 AM
FRSP should work fine for M in the branch since August last year, at least it did back then :)
Download link? :)
GUys-
Was hoping I didnt need to bring this to your attention but I accidentally tried a unified version with FRSP compiled last night and now my M just blinks green light RAPIDLY whenever I try turning it on. Tried all 3 of my SD cards. (1 with ML & 2 without ML)
I read it somewhere that you can "Put card into cardreader, format with NTFS, insert card into cam, format it there." but didn't do the trick for some reason.
Tried using MacBoot but didn't help. Ive also used Disk Utility to erase the card and put it back in previous ML that worked before to try and format again in camera but to no avail... because it still blinks green light rapidly. Even without a card in it still blinks. Strange?
I think I may have read it somewhere that you can press the Info button to get out of it which didn't work this time but it has in the past if I can recall correctly?
Remove battery. Format card inside cardreader. Don't make the card bootable. Insert card, insert battery. Startup.
Report results.
@Walter Schulz:
Indeed, that did the trick. I think previously I may have messed up the order with taking out the battery and putting it back in first before the card after NTFS'ing it -- That's a big NO-NO!
https://vimeo.com/119370912 (https://vimeo.com/119370912)
Now off I go and try again with the newly compiled FRSP for the M.
Thanks again to you for your clarifications & @jpanna for the FRSP build!
*EDIT*
(https://farm8.staticflickr.com/7397/15881154414_6764c53de6_n.jpg) (https://flic.kr/p/qcn4V9) (https://farm9.staticflickr.com/8675/15883556423_23f3fea327_n.jpg) (https://flic.kr/p/qcznX6)
:D [emoji119] [emoji482]
Phew, glad it worked out :)
Hi
I have been using ML for years in my x4 and 7D and now want to use it on my M. It is my understanding that the shutterbug does not occur on any EF/s lenses (even with IS eg 15-85) nor any manual focus lenses. Am I correct?
Thanks
I've only encountered the shutter-bug with EF/M IS zoom lenses. Don't let fear of the shutter-bug keep you from using ML on the EOS-M. It turns the M into an awesome little camera. If the bug does bite, simple switch to a card w/o ML or turn off the camera boot flag by running the firmware update and waiting about 30 sec. before power cycling the camera. A few of us that have had the bug are bug free after reformatting the card and reinstalling ML.
Can I ask about rack focus capabilities? I hear they aren't present on the EOS M build of ML. Why not? It would be cool to be able to use the thumb wheel as a focus knob.
25 FPS ON EOS M&ML PLEASE HELP! The firmware seems great but I can't get it to run on 25fps. Anyone knows?
Quote from: Audionut on February 25, 2015, 10:25:46 AM
Page 187 of your camera manual (http://gdlp01.c-wss.com/gds/8/0300008788/01/eosm-im-en.pdf).
Thx dmilligan! Got it & Works! Would you OR ANYONE KNOW if EOS M2 would work with ML?
not until somebody ports ML to it
I haven't got any SD cards at the moment, and thus cannot test this out on my new-to-me M, but does the latest build have follow focus ability at all? To control autofocus lenses via the camera interface?
I would so love that. Sorry to repeat myself.
Hi guys. Is it possible use magiclantern on eos m3? Has anyone done the test?
@dfort - thanks for your reply. My research says the same that it only occurs with ef-m IS lenses.
Off to download ML :)
Please REFRAIN from asking non-sense (or half-@$$) questions regarding M2 or M3.
If you would've taken the time to read the actual forum as a whole, then you wouldn't be wasting our time.
This thread is specifically for the M and only the M!
Keep it original...
Thank You!
I've been a Magic Lantern user for the last few years now, for the M I have refrained from installing the software as it's basically my travel camera and if the shutterbug were to occur that would be my documenting of my travels affected, does anyone have a sure way to disable the bug eg, swapping out our memory card that doesn't have ML, or do you have to wait until you're out a computer to format?
What would greatly help is if someone had a sure 'simple' way to fix the issue, for Windows users and then if anything does occur then there is a safe fix.
I'm using the 22mm, the 18-55mm and the walimex 12mm without any problems. The shutterbug occurs on the tamron 18-200mm, but since it can be removed by loosening the lens once after turning on the camera I just do that and keep the camera turned on as long as I need it.
I would like to refrain from reattaching lenses, my workflow is fast and I would need there to be very little margin of errors as possible, I think we would all appreciate the development of the bug in this case as ML is king, went from the Sony A7 to M and with the video quality there is a lot more from the M, and the capabilities that ML unlocks the camera is basically a beast!!!
Also at the moment I'm running into some buffer issues inside of the camera with my memory card, what would be the recommended speed of card I can go to?? Is there a right speed limit in the M?
Thanks
Afaik the SD card controller is the bottleneck. You should be able to find more information somewhere in this forum
Prime lenses are fantastic and a few years ago I would never of dream of using a zoom especially the 18-200, but The contrast and sharpness of these modern lenses really do performe fantastically even the M's 18-55 I would consider that possibly the best 18-55 on the market, so I have really got a love for these modern lenses sold my Canon LTM 0.95 and I was a glass snob...
I think if you know what you're doing theoretically with a camera it doesn't matter what camera you have or lens your artistic vision and execution is everything, but with the M it is quite hard to Pin the focus sharp so ML would ROCK, on this bad boy and the processor and colour rendering of the M even the way it handles noise... Totally underestimated little package, but the bug!
Can someone add a link to the speed of the SD buffer?
Suppose you're asking for SD-card interface limit in MByte/s:
Give or take (http://en.wikipedia.org/wiki/40_%28number%29)
Hi,
using magiclantern-Nightly.2015Mar03.EOSM202 I still get only old silent pictures, no FRSP.
What version has the FRSP?
The one compiled by you.
Quote from: Walter Schulz on March 10, 2015, 03:42:11 PM
The one compiled by you.
I was under the impression that if was merged in the main branch from which the nightlies are compiled?
Quote from: kosmarnik on March 10, 2015, 03:59:41 PMI 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
Do keep in mind there are some issues: http://www.magiclantern.fm/forum/index.php?topic=12523.msg142216#msg142216
Hi there, I've ordered my EOS M this afternoon, and I'm planing to install ML as soon as I receive it. But I've few interrogations :/
I saw that the last build has a shutter issue, is it still the case? Is there any kind of stable version?
I'm buy the M because I wanna shoot videos with it, does anyone has found good settings to do so?
Thanks for your help, really excited to soon be part of this community! :)
Hi all,
I´m trying to use magic lantern on my EOS M to shoot bracketed spherical panoramas. I want to use my IR remote to trigger the camera but I'm having some trouble making this work in combination with magic lantern. A lot of the time it will not shoot all the brackets and most of the time it is doing the 10 sec delay/timer before each exposure. This is not happening with every try though, and the results seems, to me, quite random. Anyone have any experience with this and know a good workaround?
Quote from: arthurpattee on March 13, 2015, 09:57:44 PM
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
I don't have it myself but I might be a lone case.
Quote from: arthurpattee on March 13, 2015, 09:57:44 PM
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.
Ok, so just got my 2.0.2 and flashed it immediately with ML.
What are the best settings for video? I would like to retain the 1080, 16:9 size, and it will be used on a gimbal on a drone...what are my options?
I have the 22mm lens.
Does anyone know if ML will allow me to tether my EOS M? I hope to be able to use it with a microscope but I really need to be able to control the camera from a computer adjacent to the scope.
No and i think that this will never happen...
Thanks for your answer, I'll try out soon anyway!
And I have the same question that Silverburn, does anyone shoot in video mode with the M? :)
I shoot video mode with the M. In fact I shot some tests with the idea that I'd do my "real" shooting with a higher end camera but the EOS M performed so well that I'm using it for a documentary I'm doing.
I'm not shooting raw, increasing the H.264 bit rate or anything like that. My settings are the standard 1080p 23.976fps. The ML features that I use the most are the audio metering, focus peaking and 3x crop mode. The crop mode is particularly interesting because I mostly use prime lenses and it is like having two lenses without having to change lenses. It doesn't seem to reduce the resolution and people report that moire and aliasing artifacts are greatly reduced or eliminated though I haven't had problems with this because of my subject matter and I always shoot with a flat profile.
By the way, the most important setting seems to be the profile. I use Technicolor Cinestyle because that's what I started my project with but there are several others. The best advice I can give is to test, test, test and then shoot a lot.
The EOS M is a fun camera for video. You can set it up to look like a point and shoot camera to go stealth or attach cine lenses on it and it looks like you're using a director's viewfinder. Of course you can also put it on a shoulder rig or strap it on a drone.
Got the M1 build compiled again:
What's changed:
*updated to the latest FRSP commit e6e9753 (https://bitbucket.org/hudson/magic-lantern/commits/branch/fullres-silent-pics)
*bypassed the dual_iso module build error introduced in commit 9e99764 (https://bitbucket.org/hudson/magic-lantern/commits/9e99764f432025872286f87d5b7e10014061277f?at=fullres-silent-pics) ( info here (http://www.magiclantern.fm/forum/index.php?topic=12523.msg142493#msg142493) )
*bumped wait_lv_frames from 4 to 20 so one can use *-hold for AF ( just set C.FnIV to 1 or 3 ) when taking FRSP ( info in these posts (http://www.magiclantern.fm/forum/index.php?topic=12523.msg142489#msg142489) )
*added the Depth of field display (http://www.magiclantern.fm/forum/index.php?topic=14734.0) patch
Link: <removed>
/LE: links fixed
/LE: use the nightly, it's merged in main already ;)
Thanks @Licaon_Kter -- will definitely check it out and test it on the M1!
Quote from: arthurpattee on March 19, 2015, 09:10:23 AMAnd 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.
Thank you every one! I should receive my M before the end of the week. I'll go on tests and publish the results if some of you are interested :)
Is there a trick to read the help files?
I only get the message: Help files not found.
Top of page -> Downloads -> Browse Nightly Builds.
What are the disadvantages of nightly builds? Second item.
I read all the 23 pages and nothing found about help files. Now I know why.
But as always....... Read the manual before operating........ And start reading at page 1.........
Thank you.
Updated again, this (http://www.magiclantern.fm/forum/index.php?topic=9741.msg142766#msg142766) plus these (https://bitbucket.org/hudson/magic-lantern/commits/848d3944d5b91f84d4b195b02ee8db5231f773f4) three (https://bitbucket.org/hudson/magic-lantern/commits/d190470d38c889cabcc75e0cc9e4b08ec7af6aa0) tweaks (https://bitbucket.org/hudson/magic-lantern/commits/35295ffb47063166ddf5bbd2761db7aee0dec682)
Link:
/LE: use the nightly, it's merged in main already ;)
Is anyone else having an issue with ML displaying the frame rate as 29.97 regardless of the actual selected frame rate? also, I can't find 1/48 shutter speed because of this.
Is it possible to rollback to original EOS M 2.0.2 firmware?
How?
First page, first post.
hi guys,
i got my EOS-M (mk1) and have problems with my raws
(http://www.snabshod.com/M14-1127_frame_000024.jpg)
has anybody an idea how to solve this pattern problem?
thx a lot
Pink dot remover
And visit Postprocessing forum
Are the pink dots/patterns the Phase Detect &/or the Contrast Detect sensor locations - anyone really know ? They certainly do not cover as much of sensor (total coverage area) as I would have thought.
From the Canon site ( Hybrid AF ) compared to M2 ( Hybrid AF II ):
(http://www.canon.com/camera-museum/tech/report/2014/01/img/zu_06.jpg)
I keep seeing the camera temperature on other cameras ML menu, does this need more data for M to be usable or what?
How i can change default ML shortcuts when i liveview? I want to use arrowup/down to change my ISO, currently they do single shooting and other options if i press up and i can change ISO with down arrow but i only have canon values to choose (100/200/400/800 etc)and i want all of them from ML menu.
Would be best to change ISO with UP/DOWN arrow, change white balance with LEFT/RIGHT arrow and change shutter speed by rotating wheel.
There is something i don't understand about RAW with EOS M... (and have searched the forum ;))
This document https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=5 (https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=5) says that EOS M "can record FullHD only when also recording H.264"
So do i need to set it to 720p in the Canon menu to work correctly ? I've not seen any difference in the results when tryed both 1080p and 720p mode.
Is the Canon menu setting make any difference in RAW recording ?
And about FPS : It's mandatory to use FPS override to get something another than LV approx 30 fps, right ?
Another question (maybe bug ?) :
In photo mode, when i set M mode and use AETTR (configured in HalfS DblClick) the "ETTR..." symbol in LV never disappear. But, if i set Av mode, it's ok, it disappear (as usual) after the mesurement is done.
You could check that with regular silent pictures. If I remember well, Canon video settings only get applied when you start recording H.264 (and until you do that, it stays at 720p 30fps or something like that - you tell me).
Currently you can't record RAW at the same time with H.264, but it should be doable.
The redraw issue is probably a bug. You could check if redraw() gets called at the end of NotifyBox_task(). If yes, check if dialog_redraw() gets called in _redraw_do. If that gets called, but does not do the right thing, we are probably asking it to redraw some tiny dialog (not the entire screen). I'm not sure how to fix it in this case (need to experiment, probably need to redraw some dialog below the topmost one).
Thank you a1ex,
I think there's no need for "simulREC"... Or maybe just to trick the M with a fake (unusable) H.264 rec and get 3x3 sampling in 1080p mode.
For the redraw issue i can try and report here, thank you.
Can you get the VRAM image dumps for EOS M? http://www.magiclantern.fm/forum/index.php?topic=12375
These will tell exactly what subsampling factors are in each video mode.
My M is always with me... ;D
Here is : http://www.filedropper.com/eosm_1
- 1080p25 stby
- 1080p25 rec
- 720p50 stby
- 720p50 rec
If you need something else, tell me.
Yes, photo mode LV and 5x zoom please. Also, can you repeat the 1080p25 rec image? (it came out corrupted).
Are there other video modes like 640x480 or crop?
Here is : http://www.filedropper.com/eosm_2
1080p25 rec (still corrupted ?)
photo LV
photo 5x zoom
640x480p25 stby
640x480p25 rec
1080p25 crop stby
1080p25 crop rec
So, these dumps confirm what the spreadsheet says: FullHD buffers are only available while recording H.264 (and in crop mode, but that one is listed on another column). In standby or in photo mode, the sensor is read out at 720p.
To get a clean picture in 1080p rec, you might have better luck with a low FPS.
Ok, fine. Happy to help.
QuoteTo get a clean picture in 1080p rec, you might have better luck with a low FPS.
Do you need it ?
Would be nice to have it for QEMU experiments, but I can find an workaround (like duplicating some good data).
Tried at different fps (1,10,20) but can't get it clean...
Then, you might have better luck with silent pictures.
If not, nevermind.
What do you mean ?
Take a SP while recording 1080p25 ?
If yes, here is : http://www.filedropper.com/09500000
Hi there,
I only recently installed ML. I read before that the audio monitoring function for the AV cable out port didn't work before, is that still the case? or is there an alternative solution?
Hello
I'm new to Magic Lantern and discovering it right now.
I'm having some issues on my EOS M with the latest nightly buil (2015 /4/19)
1/ The menu seems to appear only in movie mode, not in photo mode.
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?
3/ Help files seem to be missing from the zip file.
Thanks in advance.
Quote from: JX on April 25, 2015, 01:32:56 PM
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?
Answering my own question: to select an option value, touching the screen seems to be the thing to do.
Quote from: JX on April 25, 2015, 01:32:56 PM
1/ The menu seems to appear only in movie mode, not in photo mode.
press INFO one more time until you get it
Quote from: JX on April 25, 2015, 01:32:56 PM
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?
Quoteyou know that already since you've read this: http://magiclantern.fm/downloads.html right?
I think I don't get it. Is there something else than the nightly builds to download for EOS-M, some full version that would include help files?
At time of writing there is only one version and there are no helpfiles included.
Quote
At time of writing there is only one version and there are no helpfiles included.
OK, thanks.
Quotepress INFO one more time until you get it
I couldn't get it to work. When I'm in photo mode I can get to the ML view pressing Display, but if I press the Trash can button it just shows the DOF preview, although it opens the ML configuration menu if I am in video mode.
Switch Trash to ISO, does it help?
I'm not able to repro this, it just works... pressing INFO:
1. Canon interface without Live View
2. Canon mode interface simple
3. Canon mode interface more info
4. ML interface
5. press again to go to point 1.
A heads up. EOS-M build is currently failing, I hope this means new goodies are in the works. :)
Quote from: Marc Griffith on April 29, 2015, 05:02:04 PMA 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)
Quote from: Licaon_Kter on April 30, 2015, 01:40:08 PM
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)
Done. I have the shutter bug.
Hi,
is there a reason why all the focus specific stuff in the eos-m build is disabled ? (like stack focus, rack focus ...)
I tried to use the Focus Infinity Module (foc_inf.mo) but it wont change the focus so i think the problem is that even the basic api focus controls like lens_focus() in focus.h are not working for eos-m ?
*feedbacks*
Guys... I just decided today to randomly test out the M with AF Nikkor 24mm f/2.8D (with Fotodiox lens mount adapter) and it wouldn't allow me to record MLV/RAW or even take photos on the M.
Once I then took the Nikkor lens off and swap it with Canon lenses... it was back in working condition. Not a big deal to me but just thought it may be worth noting unless I'm missing something?
Is this normal?
@DeafEyeJedi Check and update your "Custom function 7 " in Canon settings menu
That's probably it. Will check on that and report back!
Thanks, @350D!
I have been shooting time lapse with a 20D and a TC-80N3 remote. I find my Sony RX100 out shoots it by lot, in particular at night, but it doesn't have a good way to do time lapse, plus I miss all my canon lens, I tend to use a lot of wide lenses; Canon 10-22EFS and Sigma 18mm fisheye being my favorite. I don't shoot professionally anymore so I don't want the cost or bulk of the 70d, and I'm leaning toward the original Eos M. Traveling with kids it is nice to have a smaller camera. I can keep 22 on for quick shooting, but will use adapter for my other lens a lot.
My question is about battery life when shooting time lapse. Didn't know if anyone had experience with it that they can share. I know there are a number of settings I can configure that will impact this. I will be traveling for 8 days without my computer and the idea of the FPS sounds convenient to save space on memory card (although they are so big now, maybe not a big issue) but of course I give up resolution, mainly important if I wanted to do some zooming on the time lapse. FYI - going to Grand Canyon, Antelope Canyon, X=Zion , Bryce, and Capital Reef on road trip. That is what is spurring me to make a decision.
Any thoughts,
Latest Build
This Build Failed! :o
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?
You may want to press button "Show older builds" and try one of those 223 builds before build 224.
Test please (latest build needed):
Switch Magic Zoom to Fullscreen mode. Does screen look fine or is there some kind of vertical splitt with "tiles"?
Quote from: walaw on May 12, 2015, 08:22:52 PM
This Build Failed! :o
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?
It's broken because of this: http://www.magiclantern.fm/forum/index.php?topic=14959 (http://www.magiclantern.fm/forum/index.php?topic=14959)
And you are not missing much anyway, use the
magiclantern-Nightly.2015Apr19.EOSM202.zip from the
Older buildsQuote from: Walter Schulz on May 13, 2015, 01:47:33 PM
Test please (latest build needed):
Switch Magic Zoom to Fullscreen mode. Does screen look fine or is there some kind of vertical splitt with "tiles"?
Not a M feature: https://builds.magiclantern.fm/#/features (https://builds.magiclantern.fm/#/features) ;)
There is developer of nightly for EOS M? Why progress is stopped?
Many things implemented in ML ports for 6D and 70D not work on M. What about recording in MLV? Why i can not record without squeezing by vertical?
Silent picture produces black images. Magic Zoom not work as it should. My EOS M was broken for long time, and i use ML mostly on 6D. And now when i'm repair M and install ML fo it I lost a lot of the usual functionality. Very sad... ::)
> There is developer of nightly for EOS M? Why progress is stopped?
This is a blocker: http://www.magiclantern.fm/forum/index.php?topic=14959 (http://www.magiclantern.fm/forum/index.php?topic=14959)
Contribute, maybe you can help, although you are not missing anything compared to the latest good build of April 19.
BTW, progress has not stopped in any form or fashion, you can undo the error line and it will compile just fine, but the issue in the thread still stands.
> Many things implemented in ML ports for 6D and 70D not work on M.
Correct, try this: http://www.magiclantern.fm/forum/index.php?topic=12657.0 (http://www.magiclantern.fm/forum/index.php?topic=12657.0)
Different cameras... you can't just compare 6D and a M, c'mon.
> What about recording in MLV? Why i can not record without squeezing by vertical?
The camera can't handle a bigger resolution/data rate, try a 5DIII if you want more. ;)
Some info about what it can do: https://rbrune.github.io/mlraw/ (https://rbrune.github.io/mlraw/)
> Silent picture produces black images.
Report this in the right thread: http://www.magiclantern.fm/forum/index.php?topic=12523.725 (http://www.magiclantern.fm/forum/index.php?topic=12523.725)
FYI, it's working fine for me and others on M, except that pesky lens not closing to correct aperture bug.
> Magic Zoom not work as it should
Details?
> And now when i'm repair M and install ML fo it I lost a lot of the usual functionality.
What did you lose exactly?
What build had everything you wanted?
Also, what was the problem with your M and how did you fix it?
Hello, I was wondering if anyone can help.
I installed magic lantern on my canon eos M however due to the shutter bug I decided to delete it, however i completely messed this process up! I took the card out and blanked it on my computer. When putting it into the camera it just flashes green constantly. I tried putting the firmware 2.0.2 onto another memory card and i can get into the camera this way however when i go to the 4th wrench menu to reroute it all of the options have gone (http://s2.postimg.org/kw7dfn4it/Full_Size_Render.jpg) (http://postimg.org/image/kw7dfn4it/)
Does anyone know how i can get my camera back to how it was when i bought it with the original sd card??
Thank you,
James
put ML on the card again and uninstall from the camera first
see this: http://wiki.magiclantern.fm/install
To Licaon_Kter
May be you misunderstand me in some things. English is not my native language ,so I can't describe all widely. Google translate is not the answer. And I practice English only on forums like this. :(
About Magic Zoom: image flickers in zoomed part.
About MLV record. I use my 6D and 70D to record mlv video. And bandwidh of SD card ~40 MB/S is quite usable for me. As I know EOS M has the same SD card bandwidh. Why i can't record MLV with same settings as on 6D or 70D? Image is squeezeed vertically. May be i do some thing wrong?
I try FRSP again, and report about results.
About repair. Multicontroller(wheel+5 buttons) worked not good, i disassembled it to clean and accidentally broke ribbon cable. Needed detail shipped not so quick. On last week I install new parts and now camera work like a new.
Quote from: grey on May 21, 2015, 02:21:34 AMWhy 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?
Quote from: glassescreditsroll on May 21, 2015, 03:25:26 AM
i dont seem to find anything on why eosm dosent have focus controls like rack focus and focus pulling?
Probably because the M uses a different lens system (EF-M mount). And probably this implies different code in firmware to control the focus. And also probably no developer has found yet the way to get the ML focus related stuff working, due to these differences.
Quote from: Licaon_Kter on May 21, 2015, 02:28:54 AM
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/700D. And these cameras can record MLV with almost same settings as 6D or 70D. Why EOS M can't?
Quote from: grey on May 22, 2015, 01:19:58 AM
EOS M is almoust identical to EOS 650D/700D
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).
Quote from: dmilligan on May 22, 2015, 02:10:53 AM
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).
I am not a coder, but M has same CPU, Digic, CMOS chip, card interface as 650D. ML work mostly in LV mode on DSLR's, so mirror is most unnecessary thing in camera for ML. IMHO.
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.
Quote from: Walter Schulz on May 23, 2015, 02:22:05 PM
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.
I don't think that firmware of these two cameras identical. I talk about hardware installed in cameras, and their similarity.
Hardware partly similiar. Firmware not similiar. Conclusion?
Quote from: Walter Schulz on May 23, 2015, 02:39:27 PM
Hardware partly similiar. Firmware not similiar. Conclusion?
If HW similar, EOS M can record MLV with same resolution as 650D. But for some reason in LV mode CRAW buffer is smaller that in videorecord mode, and FPS set to 30. ???
Quote from: grey on May 23, 2015, 01:44:27 PMI am not a coder, but ...
Great, now that you admit that, stop this conversation that leads nowhere.
The EOS-M can actually record 1280x720 raw video at 30fps ... in crop mode (both with raw_rec or mlv_rec)
In normal mode (full, sensor, no crop) I can get only 1280x692 with raw_rec and 1280x432 with mlv_rec. And the aspect ratio gets changed, a little with raw_rec, and a lot with mlv_rec. So I suspect the problem is not lack of speed, but something not fully understood or properly fine-tuned in video modes settings or timers.
The main problem is (as g3gg0 says here: http://www.magiclantern.fm/forum/index.php?topic=13746.msg143184#msg143184) that there are way more camera models currently supported by Magic Lantern than skilled developers that are able to maintain them.
And many people is constantly demanding in the forums that even more camera models should be supported: every new camera launched by Canon, and also the oldest cameras (VxWorks based, etc.)
So I do not see an easy solution, witthout more developers contributing, and more users involved in testing and feedback.
I think nobody is really interested in fine-tuning EOS M ML project. And this is very sad.
Stop trolling around, please. Take a look into ML team's Bitbucket section.
Quote from: grey on May 23, 2015, 09:59:16 PM
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)
Or better yet test my fix for REC mode here (or in the issue above): http://www.magiclantern.fm/forum/index.php?topic=15210.0 (http://www.magiclantern.fm/forum/index.php?topic=15210.0)
Either use cloud: http://www.magiclantern.fm/forum/index.php?topic=14725.0
Or VM: http://www.magiclantern.fm/forum/index.php?topic=7579.0
Or real Linux.
Report your patches here for testing.
Thank You 8)
The autoexpo module seem wonderful. Does anyone know if a build has been made that solves the issue of the absence of a wheel button on the eos-m? ie: use other buttons to change the second values.
was it clear the way I said?
Unfortunately the shutter bug is a big problem, as my main lens is 11-22. I tried formatting my card in the PC and after that in camera and for a few days it was bugg-less, but then it came back.
Some SD card brands (Sandisk) seem to be less afected by the shutter bug than others (Transcend). See this dicussion (https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug) and share your own results there, also.
And you can minimize the shutter bug with your EF-M 11-22mm lens if you keep the lens in collapsed position when starting the camera.
Quote from: Ernani on May 24, 2015, 03:52:48 PM
was it clear the way I said?
Not really, detail your workflow.
Quote from: Licaon_Kter on May 24, 2015, 10:01:00 PM
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.
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.
I prefer a dark picture to a noisy one, thus I'd like to let ISO alternate between 100 and 1600 but never cross over it. "auto exposure" module would do the trick but with the M I can't chose the highest value which is set to 6400.
Am I the only one who finds Canon's auto-expo dreadful?
Quote from: Ernani on May 25, 2015, 07:39:01 PM
Am I the only one who finds Canon's auto-expo dreadful?
No, you are not the only one ;) But there is Magic Lantern's Auto ETTR module ... and that's all I need, I use it all the time.
I know A-ETTR is a very different method. Amazingly precise for raw pictures, but it takes a while to do the measurements, it's not intended for fast action.
I have tried autoexpo now in the M... and you are right, I can't change the upper value for ISO, etc.
In my 500D it works, the left/right keys change the lower value and the main dial next to shutter button changes the upper value.
But with the EOS-M the wheel and left/right, up/down and "play" keys all do the same function, they change always the lower value.
And with ML's menu disappearing after few seconds it's really tricky to properly adjust the autoexpo module in the EOS-M.
Quote from: Ernani on May 25, 2015, 07:39:01 PM
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.
Hey M users, can I have a request?
Can anyone/everyone please see my reported bugs ( https://bitbucket.org/hudson/magic-lantern/issues?reported_by=~licaon_kter (https://bitbucket.org/hudson/magic-lantern/issues?reported_by=~licaon_kter) ) and maybe at least confirm/deny them, either here/on their threads/on bitbucket so that we can get more data points or something?
Cheers and thank you.
Wow Licaon_Kter, looks like you've been working hard on ML for EOS-M.
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.
Quote from: dfort on May 30, 2015, 08:49:57 PMWow 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.Quote from: dfort on May 30, 2015, 08:49:57 PM
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
BTW, there is nothing extra, except the DoF info verbose patch that one would be missing when using the April 19 build compared with a un-broke newer build.
Thanks for helping
Nice progress on your bug reports. You're doing things I never knew could be done with this camera, ML keeps amazing me. Hope you get your fixes into the nightly build. Speaking of, it would be nice if nightly EOS-M builds get fixed.
Some day I might dive into the code and try getting Audio RemoteShot working again but since I don't have a coding background that will be a long shot. :-\
No, no, no, I don't have any fixes, unfortunately, I only stumble on issues. :-[
I hope that somehow a1ex can read my detailed reports and repro steps and get the same results on a different camera model or in QEMU and track it down, given his knowledge of the code that is.
Replying to David Goldwasser to his reply #608 back on May 07, 2015
I noticed a while back you posted some questions about extending the battery life on the EOS-M for timelapse. Sorry I was busy on other projects when you posted this but I thought I'd share a solution that has worked for me.
When I did my first timelapse using ML on the EOS-M I knew that the internal battery wasn't going to cut it because I was shooting a couple of artists doing a painting at a 4-hour event. I used a cheap third party AC adapter that I bought through Amazon:
http://www.amazon.com/gp/product/B00CDK0BOA
It worked great but it got me thinking about what to do when there isn't an electrical outlet nearby. The EOS-M batteries are 7.4V and I found that these batteries made for radio controlled cars were also 7.4V:
http://www.amazon.com/gp/product/B001BKPAR6
So I cut the cable on the AC adapter, spliced in a Tamiya connector to plug in the battery and it worked. It got a real workout a few weeks ago when I took a timelapse workshop in the desert and my little EOS-M kept clicking away all night while the big boys with their DSLR's had to pack it in because their batteries ran out.
If you combine this with some battery saving settings like turning off live view, silent shutter, etc. this could give you even longer shooting times though honestly I've never run one of these batteries out in the field.
I'm sending you a PM in addition to posting it on the forum because if you're like me you might have a hard time searching through the forums for an answer to your question.
After I got my M I was testing the settings, looking around ML, messing basically, and I was struck/disappointed by the fact that after half an hour or so the battery would go to yellow/red, as in empty. So reading around, got that the LV is using so much power hence using it in the menus and/or LV will drain it fast, but I was still not convinced, I though that the battery and/or camera was broken.
So I did a simple test, with the help of ML, 32gb empty card, RAW file only, intevalometer, 5 seconds, GO.
Result: >50gb in 2207 pictures in a little more than 3 hours.
Now, that doesn't mean much since the LV mostly stayed on for less that 1 second after every picture, but for me I understood that the camera/battery are not broken at least.
Also I understood that using it on a simple workflow of: open, quick setting, picture, no preview (mostly), close, will serve me good enough.
For pros or far away from a wall plug, yeah, a second/third battery might be needed, and it's on my list also.
Quote from: dfort on June 07, 2015, 09:06:13 PM
*snip*
I'm also looking for external battery solution for my EOS M.
I don't know if could help me since you have build one. :D
My original plan was to buy this: http://www.amazon.com/EasyAcc%C2%AE-20000mAh-Precise-External-Smartphones/dp/B00LHB51GO (http://www.amazon.com/EasyAcc%C2%AE-20000mAh-Precise-External-Smartphones/dp/B00LHB51GO)
and plug it into Canon's original DC coupler for EOS M(Canon DR-E12). The problem is that I don't find anywhere what is the size of that DC plug on that DC coupler so that I could buy adapter for it! Do you know the dimensions of that DC plug which goes to the "dummy battery"?
Other thing is that now I'm second guessing if that power bank can deliver enough power. It is rated at 8.4V 1A. Voltage should be fine(fully charged canon battery outputs over 8V) but I don't know if 1A is enough. ???
QuoteI'm also looking for external battery solution for my EOS M.
It's a little bulky, but I got these three things:
power inverter (http://www.amazon.com/gp/product/B007Y4BL1C?psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00)
battery (http://www.amazon.com/gp/product/B004WENYYE?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00)
battery charger (http://www.amazon.com/gp/product/B000GZL29M?psc=1&redirect=true&ref_=oh_aui_detailpage_o01_s00)
...and now I have AC power wherever I go.
You could combine that with an AC adapter for your camera.
Just wondering if this is a bug or a feature.
In the Canon menu, 4th wrench, Custom Functions(C.Fn), C.FnIV:Operations Others Trash button, set it to 0:Normal(set center AF point)
Now the Trash button brings up the ML menu. That's fine unless you really wanted a button to center the AF point.
Is this documented somewhere?
Trash is traditionally ( aka on other cameras ) used to bring up ML menu, now given that M has a limited number of buttons things get crammed in, hence you have 2 fingers touch for ML menu on M.
I think you've seen my bug report regarding Trash as ISO selector, so I think ML and Canon might fight for it a bit sometimes.
Anyway, I did get Trash to open ML menu but it was really rare, right now having it set up to centre like you said it looks like it's working as it should ( I mean it centres the focus point ).
On that note, is not easier for you too to touch the centre of the screen instead and use trash for ISO or whatever? I find the whole touch to focus much better than the traditional navigate the points with the controller way.
I like the touch screen but I also like having options. Some of the ML submenus can only be accessed by touch. At least I haven't figured out any other way. Not complaining, but the EOS-M doesn't have many buttons to work with--then again neither do iOS and Android devices.
Well yes, 1 finger touch is the missing Q button.
For the life & sake of EOS-M -- @dmilligan saved myself from selling this tiny beast. Couldn't stand the PDR nightmares!
MLVFS sure enough got rid of the PINK DOTS and what a beauty - Thanks @dmilligan!
Not too bad for a $200 toy...
MLV shot on EOS-M w Nikkor 50 1.4 AI (http://www.magiclantern.fm/forum/index.php?topic=15331.msg149353#msg149353MLV%20shot%20on%20EOS-M%20w%20Nikkor%2050%201.4%20AI)
Happy to see a lot of activity around the M ! :)
Il like this "small big one" !
Quote from: DeafEyeJedi on June 10, 2015, 09:49:50 AM
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
I had a recent RAW clip that was showing some colour artefacts on some frames, besides PDR that is, red/blue/white pixel groups on some black parts of the image,
cs5x5 and
bad-pix saved the day! ;)
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
I have been aware of PDR being effective for years -- it was either the stupidity or laziness of me who couldn't get around it until I just decided to give it a shot with MLVFS because previously I had failed with other methods on Mac's (RawTheraPee, ACR Defringe, etc).
it's just a PITA for me, especially when I have my other cameras that can be ready to color grade right off the bat... Ya know?
But like you said, CS and Bad-Pix saved the day and always will be able to! 8)
Good stuff to know on your end, Thanks for sharing @Licaon_Kter and the M is only in the beginning of a great long somewhat of a career ahead! lol
*I can also confirm that MLV audio only works with first clip and not the next one unless I power off the camera as well as the star-baff crashes*
BTW during NLE work I keep it at cs2x2 for speed but before export I restart MLVFS with cs5x5/badpix/stripes/whatever is necessary.
and it doesn't affect the quality negatively? resolution loss or some sort of?
I'll do another export and see for myself.
;)
Quote from: Licaon_Kter on June 10, 2015, 10:31:19 AMNow, 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
And once this gets resolved so we can get our nightly builds back:
https://bitbucket.org/hudson/magic-lantern/commits/6cf6b881dc18c84d1da70df8d2063e7b9423f92f
There are other bugs specific to the EOS-M including the infamous shutter-bug. Pitch in and help if you can.
https://bitbucket.org/hudson/magic-lantern/issues?version=EOS-M
BTW--Going through the steps to reproduce the bugs is a good way to help developers and learn the capabilities and limitations of ML on this little camera.
How know if my camera used was used with ML, my eos m have shooter bug only with Toshiba card class 10. Thanks
With sandisk class 10 is normal, and if i push the lens works with Toshiba!!!
Install ML and you will have a screen telling you if cam's bootflag has already been set. Then wait 30 seconds and cam's bootflag will be removed.
:D :D 8)
thanks walter!!! my two cards toshiba works perfect now after remove the flag.
this shooter bug is in some memory cards, now all works!really thanks!
I got rid of a debts.
now, i want install ML for video raw, and i see nightly verision magiclantern-Nightly.2015Apr19.EOSM202.zip
i want video raw, this version have this ¿?
I wonder if install this need use Eoscard.exe and mark "EOS_DEVELOP" and "BOOTDISK".
or only this
"Installation
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."
verry thanks for your time! and sorry my english, i from brasil.
Quote from: peste777 on June 18, 2015, 07:29:04 PM
"Installation
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."
This!
so the last 5 failed nightly's are very fixable, but a1ex wants the eos m community to fix fps.engio because it is slightly broken and causes exposure problems for some people ( me included ). that's great that he wants us to fix it but if after 2 months we haven't had any progress and removing fps.engio caused the build failures we should just put it back broken and fix it later. Buggy ML is better than no ML. Also if anyone knows how to fix fps override please do so, or if hudson is reading this please add the fps override back on to the fps override builds.
The last successful build, from april 19th, works Ok, and it's not so different from current code. So it's not true that we do not have ML for the EOS-M.
And you can learn to build ML code yourself. It's not so hard (either in the cloud (http://www.magiclantern.fm/forum/index.php?topic=14725.0), with virtualbox (http://www.magiclantern.fm/forum/index.php?topic=7579.0), or using a Linux or OSX machine (http://www.magiclantern.fm/forum/index.php?topic=991.0), everything is explained in the forum) and this way you can use the latest code, from "Unified" or from experimental branches, and you will be able to contribute better with the project, helping to test new features and to fix bugs.
Is there any new update of the ML for EOS-M ?
No, read the post immediately above yours: no new builds for EOS-M since april 19th, and until the FPS limits get fixed.
I've done the work, that I could do anyway: http://www.magiclantern.fm/forum/index.php?topic=14959.msg149308#msg149308
Now it's up to a1ex
I do not know what to do, already tried in every way to set this camera ,not found any way to configure.
i received this " frame skipped stopping " and video dont have 1080p resolution, I"m LOST
i need help! thanks.
i use nightly verision magiclantern-Nightly.2015Apr19.EOSM202.zip
SD-card interface write speed limit for EOS M: About 41 MByte/s.
Are you trying to shoot raw video? You cannot shoot raw at 1080p, because SD card interface cannot write at speeds higher than 40 MB/s. RAW recording is only possible at resolutions of 720p or lower.
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 guild
Quote from: peste777 on June 22, 2015, 02:11:43 AM
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 guild
Shooting 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).
The best results I've seen are with these settings:
Use Magic Lantern Video with audio (mlv_rec.mo and mlv_snd.mo modules loaded)
You have to go to the ML audio options to turn MLV Sound ON.
Note that raw_rec.mo also works but you can't record sound.
Canon movie setting 1920x1080 24fps
Movie crop mode ON
ML RAW video (MLV) ON and set to 1280x720
It is a bit confusing that the Canon movie size needs to be set up for 1920x1080 but that's the only way to record in 24fps (actually 23.98) The ML menu sets the raw video frame size.
Note that you will have to deal with the focus pixels (a.k.a. pink dot removal or PDR) in post production and if your sound is important you'll have to reboot the camera after each take because of this:
https://bitbucket.org/hudson/magic-lantern/issue/2255/mlv_sound-working-only-on-the-first-video
Having to shoot in Movie Crop Mode might seem strange at first. After all you bought a camera with a large sensor for the shallow depth of field but the line skipping that the EOS-M uses to record 1 megapixel (1280x720) video on an 18 megapixel sensor causes all sorts of aliasing and morié issues.
Of course there are lots of other setting that can be used. Writing up a full EOS-M raw video shooter's guide is rather futile because few people use it and users keep coming up with different configurations that work best for them.
Can I check is the current build not working properly? Read there is some issue with the shutter bug? trying to download but the download page states This Build Failed! Any hope where I can download ML and install it on my EOS M? Much appreciated guys!
Button to the right: Show older builds.
I just recently got an EOS M and want to use focus peaking for manual focusing. I was told Magic Lantern does add that feature. If so, can I just grab the April 19th built and work with that or is that one also suffering from the shutter bug?
Quote from: inxlee on June 22, 2015, 10:27:39 AM
Can I check is the current build not working properly?
The most current build is April 19 and it works properly.
There are no later builds until an issue gets fixed, read posts on the previous pages.
Quote from: elmoandzoey on June 23, 2015, 05:11:12 PM
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.
Read here: https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug
Thanks guys! Got it installed running without any shutter issues. Only sometimes the screen goes haywire and somethings don't show if i keep changing my settings. Btw how do I enable Raw Video? Just noticed the option isn't available in the menu.:/
Enable RAW/MLV in "Modules" tab
Quote from: Licaon_Kter on June 23, 2015, 06:03:24 PM
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
Thank you for that info. I did read that topic before but somehow got lost in it due to the sheer length. It seems that it only affects EF-M lenses? If so, I probably won't have an issue anyways because I am using EF lenses with the adapter.
It only affects EF-M zoom lenses, not the EF-M 22mm F2 prime lens. And the EF-M 11-22mm usually does not show the bug if you take care to keep the lens in collapsed position during camera startup. EF or EF-S lenses used with the adapter are not affected.
Does anybody know the power requirements of EOS M(or Canon cameras in general)?
Canon's AC adapter for EOS M(CA-PS700) outputs 7.4V/2A but is meant for many other camera models as well. And I think there are quite a bit of headroom "just in case".
I found one guy's website(http://www.berndmargotte.com/technical/external_power_en.html (http://www.berndmargotte.com/technical/external_power_en.html)) who have measured power draw of Canon 20D and he came a
conclusion that around 600mA should be enough. But that is a old camera with no liveview/video functions so that doens't help that much.
I'm just thinking that could I get away with only 1A but slighty higher voltage ~8.4V.
What do you guys think? :D
See this too: http://www.eos-m.net/review-power-to-the-m-mains-power-adaptors-for-eos-m/
How add the Audio RemoteShoot function on the EOS M (magiclantern-Nightly.2015Apr19.EOSM202)? Is it's possible?
I want that too, looked at the source code but couldn't make heads or tails of where to start.
http://www.magiclantern.fm/forum/index.php?topic=14913
Quote from: guits1 on June 29, 2015, 10:26:39 AM
How add the Audio RemoteShoot function on the EOS M (magiclantern-Nightly.2015Apr19.EOSM202)? Is it's possible?
Alright, I gave it another try and got it to work for me. I put in a pull request:
https://bitbucket.org/hudson/magic-lantern/pull-request/645/enable-feature_audio_remote_shot-on-eosm/diff
You can get this now if you are able to compile ML on your system. Otherwise you'll have to wait until the EOS-M nightly builds are unblocked. Provided of course that my pull request is accepted.
[EDIT: The pull request was merged by a1ex so the Audio RemoteShoot function on the EOS-M is now in the unified branch. It should show up in the nightly builds once it is unblocked.]
Is it possible to manually choose 1/3 stop of ISO when taking a photo, such as 125, 160, 250, 320?
Thanks.
I looks like the Canon menu allows: 100, 200, 400, 800, 1600, 3200, 6400, 12800
The ML menu lets you choose from: 100, 160, 200, 320, 400, 640, 800, 1250, 1600, 2500, 3200, 5000, 6400, 12800
1/3 stop ISO increments would be: 100, 125, 160, 200, 250, 320, 400, 500, 640, 800, 1000, 1250, 1600, 2500, 3200, 4000, 5000, 6400, 8000, 10000, 12800
So short answer, no but close enough. Longer answer:
You can go into the Canon menu, 4th wrench, Custom Functions(C.Fn) I:Exposure and choose between 1/3-stop and 1/2-stop increments. This will allow you to set the shutter speed and F-stop to 1/3 or 1/2 stop increments. So you can still expose to 1/3-stop accuracy if that's what you really want.
By the way, my understanding is that some of the ISO settings are interpolated, gain up or gain down, from the actual ISO and can introduce noise. In addition, when shooting raw it is best to expose as far to the right of the histogram as possible without clipping in order to record with the highest signal to noise ratio and when doing this quite often a higher ISO will exhibit less noise than a lower ISO. To make matters even more confusing the very high end cameras like the RED and Arri Alexa perform best at their "native" ISO and cinematographers go to great lengths to make sure they shoot at the optimum ISO as well as the best f-stop for lens performance and depth of field and they are pretty much limited to the shutter speed they can use so they have to make the best of it with their lighting and use of ND filters to nail their exposure--then they spend countless hours in the color grading suite getting exactly what they want.
Hi everybody!
I'm from Italy and I've just joined the forum. I'm a ML user since 2 years on a 5D II.
Recently I discovered (lately) the potential of EOS M (further improved by ML).
So I decided to buy a refurbished one with original Canon EF adapter because I've various L lenses to be used on this camera.
I'll use the M on a glidecam or on a monopod for those situations where extreme lightness and versatility is required.
Now i'm going to buy some SD cards (because I've almost CF cards) and I'm going to buy Transcend TS32GSDHC10U1 Secure Digital SDHC, 32GB Class 10 UHS-I, stated for 90mb/sec (I assume it's the reading value) because of its very good price.
I know the hardware interface on EOS M is limited on transfer rate to about 40mb/s, so I don't want to buy cards with speed that gives me no advantage in using them (and wasting money).
I'll sure record with bitrate multiplier to obtain better results.
What do you think about those cards?
Thanks!
Transcend 32 GB SDHC UHS-I cards are very prone to be affected by the shutter bug. See discussion here:
https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug (https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug)
Not an issue if you use only EF lenses, but an annoying hassle when using EF-M zoom lenses.
Sandisk Extreme Pro 32 GB UHS-I 95 MB/s are a safer option, the ones we have tested do not show the shutter bug.
Hi josepvm, thanks for your prompt reply.
I'm not going to use the M with any M lens, because I don't own one and I think I'm not planning buying one of them.
I'll use it with EF L lenses exclusively.
Will the EOS-M benefit the extra speed of the sandisk for recording at higher bitrate or will be capped by SD interface speed?
Thanks again in advance.
Well, I have both cards, and I have run Magic Lantern's SD benchmark with the EOS-M this evening, and there is really a significant difference in write speed: 38 MB/s max. for Sandisk Extreme Pro 32GB SDHC Class 10 UHS-I U3 95 MB/s, and only 29.9 MB/s max. for Transcend 32 GB SDHC Class 10 UHS-I U1 600x 90MB/s. Both cards are FAT32 formatted. Max. write speed is attained with a 15625 Kb buffer.
Read speeds are similar for both cards: 38.1 MB/s max. for the Sandisk card, and 37.1 MB/s max. for the Transcend card.
I have not compared both cards during real raw video recording, (I do not shoot video at all). During some tests one month ago I saw that with the Sandisk I can continuously record 1280x720 30fps RAW video in crop mode (with raw_rec or mlv_rec). I will try to test it also with the Transcend later.
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/
Quote from: josepvm on July 01, 2015, 09:10:07 PM
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.
Quote from: Licaon_Kter on July 01, 2015, 11:29:02 PM
Answers here: https://rbrune.github.io/mlraw/
Thanks for your taking time doing tests, I apreciated it.
The difference between cards are in flash memories and controllers for sure. Sandisk has better flashes chip and faster controller.
I chosen the Sandisk Extreme 60mb-40mb (RW)/sec, I would use them only on the M and occasionally shoot RAW (for personal projects), so I think the 95MB/sec would be a waste of performance.
Anyway, for more robust performance in RAW I've the 5D Mark II (the best would be the Mark III but I'm waiting for a possible new body from Canon, Mark IV?).
As soon as I'll receive the M from courier I'll post my feedback here.
Something is not right. I Downloaded and installed nightly build april19. I can no longer access or view my firmware vers. Two finger tap does nothing. I am really freaked out that magic lantern is bugged and my camera is hacked. I wish I hadn't done this. Can anybody help?
Are you starting your camera with mode dial in A+ position?. Firmware update or info is not available on A+ mode, you should use "still camera" mode.
I was not using (A+). This is very tragic. I have found that I cannot access ISO, SS, or F/stop controls anymore either, (l only shoot manual). I am freaked out this is not good.
Remove battery, and test again. If this does not work, format the SD card on your computer, using a card reader, and put it again on camera, you should be able to start your camera normally, without ML.
Btw, EOS-M nightlies have failed for the past couple-a months. Can someone have a look at it please?
It was broken for a reason and we are waiting for a1ex to find time to review work done on this very item and convert it into code.
http://www.magiclantern.fm/forum/index.php?topic=14959.msg150024#msg150024
Ah, I see. Thanks
Anyway, some assert logs:
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
Quote from: feureau on July 04, 2015, 05:50:30 PM
Anyway, some assert logs:
at ../../src/raw.c:1690 (raw_lv_request), task shoot_task
Yeah the M get's plenty of those, being a LV only camera.
Hi guys,
I'm successfully recording in H264, with 3.0x bitrate settings. I get values of about 90-120mbps.
I've read that above 1.4x video and sound doesn't mix very well.
I've made a try and on a one minute clip everything looks fine.
What are supposed to be side effects on audio when recording with bitrates higher than 1.4x?
Strangely, I'm able to record very long clips at x3.0 bitrate and high iso (3200) on EOS M (SDHC Sandisk Extreme 32gb 60mb/s) and I had problems on my 5D Mark II at same settings instead (but with CF Sandisk Extreme 8gb 60mb/s), the recording stops when I film dark areas (I suppose the data rate increase further).
On both cameras I'm using Cinestyle PP.
I was trying to shoot this timelapse and tried the intervalometer. The camera fires, and then it locks up. I thought this was the shutter bug thing but I was using the EF-M 22mm. And afterwards I can't take a picture with my EOS-M again. If I hit the shutter it will just lock up. I tried shooting without ML, and every time I hit the shutter it just locks up and I had to pull out the battery. I'll play around with it to see if I can get it fixed. I tried removing the lens with the power on but no dice.
core dump: https://mega.nz/#!uw1DgY6R!uCloB-3TsHboryD8O_8fTUvwGYiLPvlGPLrW8bDRpC8
Error log:
[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
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.
Hello friends,
Is it possible to disable the touch screen of the EOS M ? (eg with an hot key...)
It can be interesting because sometime my clothes changes settings without telling me... ;)
Is there any such setting in Canon menu? If so, one should be able to find the associated property and attempt to change it.
Another option would be to block touch events (gui.h) in the button handlers (return 0 to block an event). This one shouldn't be very hard to implement (even the Lua scripting engine could handle it).
Pleased to read you a1ex, i hope you're okay !
QuoteIs there any such setting in Canon menu?
No... You can adjust the sensitivity (standard/sensitive) or enable/disable touch shutter.
Canon as been asked for this function by users in another forums but nothing new for now.
Quote from: josepvm on July 09, 2015, 12:30:04 AM
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.
It was not activated.
great thread here, soon will be uploading ML to both of my EOS M bodies. In the mean time was doing some your tube research and came across this:
http://www.magiclantern.fm/forum/index.php?action=activate;u=57668;code=6af992ae69
4K with ML and an EOS M - Is that possible?
Any advice on this would be great
Cheers Guys
@olliedtog
Wrong link?
Quote from: olliedtog on July 15, 2015, 10:49:35 PM
http://www.magiclantern.fm/forum/index.php?action=activate;u=57668;code=6af992ae69
I've done 4K movie files with ML and EOS-M but that was shooting timelapse on full-res raw frames so technically I started out much higher than 4K.
People that mention 4K are trolling for views (with the exception of time lapse stuff). It's a buzzword and it attracts clicks. All they did was upscale the footage to 4K. It is silly to call such footage 4K and it's very misleading. Effectively all they have achieved is to force youtube to compress their footage at a higher bitrate.
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.
That was olliedtog's first post and the link was wrong so nobody can follow up on it.
Glad I mentioned time lapse, hope I'm not banned--yet. Well, I did mention 4K in a General Chat topic I started about image stacking to increase resolution:
http://www.magiclantern.fm/forum/index.php?topic=15306.msg149257#msg149257
I guess I'm still on topic here because the camera used was an EOS-M.
Straying into dangerous territory I might mention that I worked at a job where I was involved with preparing demonstration footage of an animated feature for a new wide screen UHDTV. The source material was 1968x816 and instead of re-rendering, which they could have done, they just upscaled the footage. All of this reminds me of several years ago when audio equipment manufactures were pushing 24-bit 96k audio yet some of the best sounding mixes at the time were coming out of Skywalker Sound and they were still using 16-bit 44.1k.
I like Magic Lantern because anyone can jump in and participate--of course that could be a disadvantage too.
Crash log:
[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
Core dump: https://mega.nz/#!PokzgYjL!bU4r80-0jGIoiJ83sB5LDK6x-U1XtuF6-ThoLKZGZC4
Pretty geeky -- hopefully a developer can help you out.
Speaking of geeky, a few of us have been trying to work on the shutter-bug issue. I'm not sure if we're getting close to a solution but we're learning a lot. Check it out:
https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug
@dfort:
Unfortunately, I agree with your statements "what is going on?" and I still don't know to this day how I got rid of the shutter bug. Or even if I Did or Not?
Does it matter on the card sizes or with/without EF adapter?
I don't mind getting myself back on track with the M boat to get this rolling again w you guys!
@DeafEyeJedi - Earlier today I compiled a version from the dm-spy-experiments branch and it is creating some interesting logs of the boot process. I posted a download link on the bitbucket shutter-bug issue page.
Here's more info about Intercepting DebugMsg with cache hacks:
http://www.magiclantern.fm/forum/index.php?topic=2388.msg113154#msg113154
Sorry guys from the wrong link posted in a hurry so will try and dig it out again, was just surprised at saying 4k! Will be adding ML to my EOS M soon, now I have two bodies and my now full kit ready to run & gun shoot.
Am off to a car show at Santa Pod UK next weekend so will be filming as much as I can. Will post a ;ink to any clip as well.
One question is it a good idea to get a larger memory card when using ML?
Cheers Peeps and happy shooting!
At about 40 MByte/s data rate one hour footage will sum up to about 141 GByte ...
Run & gun in 4K video with an EOS-M? Don't get your hopes up. This is what dmilligan was referring to when said:
Quote from: dmilligan on July 16, 2015, 03:17:10 AM
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.
Please understand that those 4K videos you saw were all time lapse. If you found one that wasn't a time lapse it was probably just scaled up. The image stacking that I'm experimenting with is just another method of scaling up. The Magic Lanterns developers have stated that shooting 4K with the current Canon models that can run ML is physically impossible. We users should accept this.
Quote from: olliedtog on July 21, 2015, 12:25:29 PM
One question is it a good idea to get a larger memory card when using ML?
Short answer: The best card to date as far as capacity, speed and is free of the EOS-M shutter-bug is the SanDisk 32GB Extreme Pro UHS-I SDHC U3 Memory Card (Class 10).
Longer answer: Are you planning on shooting raw? H.264? Time lapse using full resolution raw? Are you using EF-M zoom lenses? Do you also plan on shooting run & gun stills? All of these questions are relevant when choosing the best card for your needs. Get too big of a card when shooting H.264 and you run the chance of losing many hours of footage if the card gets corrupted. Too small of a card when shooting raw video and you quickly run out of space--see Walter Schultz's comment for a ballpark figure at the highest possible data rate for the EOS-M.
Oh and if you think raw (MLV) is the holy grail of video, the EOS-M is pretty much limited to around 1280x720 and less--not exactly 4K.
Just a reality check :-X
Perfectly well said @dfort, I agree with the fact that SanDisk 32GB Extreme Pro Class 10's are mainly free from the SB and don't forget the battery life isn't so up to par especially for run n' gun type of shooting unless you want to carry around 5-6 (or more) pieces with you all day.
Don't get me wrong though I do admit that it is still a FUN little toy to own and ML is just icing on the cake for the M!
Hey EOS-M users. Thought I just might report some EOS-M posts you may have missed.
https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug
QuoteFinally, 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
http://magiclantern.fm/forum/index.php?topic=15550.msg151516#msg151516
Quote@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?
Quote from: Disease on July 28, 2015, 12:27:02 PM
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?
Nope, page 188: http://gdlp01.c-wss.com/gds/8/0300008788/01/eosm-im-en.pdf
Hi yes I know what it says in the manual but as this hack unlocks more features and has the fps over/underdrive and as you can record 60fps raw on the canon 5dMKIII I thought it might have been possible on the EOSM...
:-[
http://wiki.magiclantern.fm/userguide#fps_override
There is a problem with the timing values to overcrank/undercrank fps on the EOS-M. Once it is fixed I don't know if the camera will be able to go all the way to 60fps at 1920x1080.
http://www.magiclantern.fm/forum/index.php?topic=14959.0
This is an open source project so if you want to dive into the code, you're more than welcome to work on whatever is on your wish list.
https://bitbucket.org/hudson/magic-lantern
By the way, Canon set up the EOS-M so it can do 1280x720 at 60fps but there's a lot of aliasing in that format. I've been doing some image stacking experiments to uprez to 1920x1080 while eliminating most of those problems, though there are other issues with this technique.
http://www.magiclantern.fm/forum/index.php?topic=15306.0
Hello ML gurus
I'm posting here because I heard you can get 4K RAW video now? At 60 fps??
Just kidding, HAHAHA
I'm new to this and have had a read of the bit bucket and the last few pages of this thread.
Is this a fair assessment of the current situation:
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).
I'm a total beginner to photography but I'd like to try ML for timelapse (intervalometer or bulb ramping) and star trails (bulb mode). Reason I'm so cautious is I'd be borrowing a friend's EOS M.
Do I need to update to latest firmware?
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?
Thanks in advance if you can answer these questions! I really appreciate the work you have done to create ML!
Cheers,
Lloyd
Quote from: lloyd on July 29, 2015, 12:16:17 PM
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.
Besides the latest nightly Apr 19, there's my July 01 build somewhere (https://bitbucket.org/hudson/magic-lantern/issues/2255/mlv_sound-working-only-on-the-first-video#comment-19410615).
Quote from: lloyd on July 29, 2015, 12:16:17 PMDo I need to update to latest firmware?
2.0.2? Yes, it fixes (most of) the focus speed, not ML related but needed.
Quote from: lloyd on July 29, 2015, 12:16:17 PMIf 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.
Quote from: lloyd on July 29, 2015, 12:16:17 PM
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?
Make sure you uninstall ML before returning the camera to your friend. To do this run the ML installer (firmware update) and wait 30sec to 1min (depending on which version of ML you're using) then restart the camera. You will get on screen prompts so it is pretty easy, though I need to put on reading glasses to see the tiny letters. Also, the screen might go to sleep before the timer is up so just keep counting. This will disable the camera boot flag and it will not start ML again until you re-install it.
If you read the bitbucket thread you know which Sandisk card has been the most reliable.
Finally, there are workarounds so don't be afraid of the shutter-bug!
- Unmount then re-mount the lens
- Play-power on button combination
- With the 11-22mm lens simply collapse then extend the lens
Once the shutter-bug is gone it won't come back until the next time you power cycle the camera.
Hello all... rather than double posting but felt this was worth noting for M users.
http://www.magiclantern.fm/forum/index.php?topic=13512.msg151902#msg151902
It is basically about my recent experience while shooting crop-mode on the M in MLV.
Thanks very much Licaon_Kter and dfort!
Hopefully I can borrow it soon and have a go :)
Cheers
Hi
New canon m owner and would like to try magic lantern but build says failed and does not show a download.
How can I download a working build ?
Many thanks
Button to the right "Show Older Builds"
If I click on this button nothing happens. Right click says inspect element?
Scroll down ...
Thanks Walter found them now. Will see if ML works on my EOS M.
Why wouldn't it?
Was messing around with the M last night during a Moon sighting ... came across a moment when it created a crash log afterwards.
Here's for what's worth:
Sun Aug 2 22:08:13 2015
p.s. hope someone wouldn't mind explaining to me why the crash report log file info that I copied and pasted into the code link above won't work? I must be doing something incorrectly.
Did you happen be shooting the moon in MLV with audio? There's a bug that was fixed but it won't appear in the nightly builds until the fps issue is resolved and the build unblocked.
If the crash log is too big you might try putting it on a cloud drive and linking to it.
BTW--were you trying to do this (http://magiclantern.fm/forum/index.php?topic=15621.msg152060#msg152060)?
Well I was actually using the test build (July 24) that I received via PM from you recently so maybe I should have mentioned that in previous post, my apologies.
Anyway, Yes I remember reading that post regarding a moon-sighting with a 400L recorded in MLV which came out pretty damn nice!
To answer to your question, Yes, that's precisely what I was trying to do but this Nikkor 200 f4 AI is all I got atm for the extra reach.
Tried shooting in crop mode as well. Doesn't cut it as much as I would like.
*EDIT*
Here's the log file per your request @dfort: Crash Report (https://mega.co.nz/#!LkkngKaS!1J1n2dKtjh3Z2Kg5PFLvAWbUfJ4ysnz8Z0fxRK8ZDS8Crash%20Report)
I just suggested a way to put up the crash log. I have no idea how to make any sense out of it. Though if you're using one of my test builds this might not even be a regular crash log.
Maybe a developer should take a look at it.
BTW--I got a Nikon 2x tele extender on ebay pretty cheap. That might do the trick for you. Love how you can adapt so many lenses so easily to the EOS-M. Nikon manual lenses on Canon bodies are a staple with stop motion animation because they don't flicker.
There is now a firmware update (for European models anyway) for the M3. Is this helpful?
http://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos_m3.aspx?type=firmware&firmwaredetailid=tcm:13-1286211
we know: http://www.magiclantern.fm/forum/index.php?topic=14990.25
I understand that raw video in full frame mode is sucky line-skipped 720p because this is the mode that eosm live view uses, but what happens when you plug an hdmi monitor and record raw? doesn't this change live view to 1080p? anyone tried this?
Crop mode is not line-skipped.
IIRC, it does not output clean HDMI, not even EOS M3 does.
I was not asking about crop mode or clean hdmi out. I found the answer to my question, which is that even though hdmi output is 1080p, raw still records from a 720p buffer (in full frame mode) even when a monitor is plugged in. this is pretty lame. There has to be a way around this.
Are there any active developers for EOSM? my guess is not. one percent hasn't updated his fork since last December. I guess I'll start working on porting some of his changes over to the main branch like I did for 7D. The main things are that he got MLV to record audio for multiple takes without a restart needed, and he got magic zoom working without flicker in crop mode. I'll work on those first. If there is someone else who's interested in maintaining EOSM, let's talk. I guess we need to find some stubs or something to bring it current. I'll look at the last build before it broke (sometime in april, right?)
The unified build supports EOS M as a main platform.
April brake is intentional, it can be fixed by hand ( edit fps-engio.c ) or by @a1ex once he gets a chance to tune the timers, see my values report in this thread: http://www.magiclantern.fm/forum/index.php?topic=14959.msg149308#msg149308 (http://www.magiclantern.fm/forum/index.php?topic=14959.msg149308#msg149308)
MLV Audio works fine, did you mean this bug: https://bitbucket.org/hudson/magic-lantern/issues/2255/mlv_sound-working-only-on-the-first-video (https://bitbucket.org/hudson/magic-lantern/issues/2255/mlv_sound-working-only-on-the-first-video) ? Was fixed already: https://bitbucket.org/hudson/magic-lantern/pull-requests/646/added-sounddevshutdownin/diff (https://bitbucket.org/hudson/magic-lantern/pull-requests/646/added-sounddevshutdownin/diff)
Want the latest unified build for EOS M to test? It's here: https://bitbucket.org/hudson/magic-lantern/issues/2255/mlv_sound-working-only-on-the-first-video#comment-19410615 (https://bitbucket.org/hudson/magic-lantern/issues/2255/mlv_sound-working-only-on-the-first-video#comment-19410615)
I'm not sure what current means for you, current like the other unified cameras ( where there already afaik ) or current compared to what 1% was working on ?
Long standing issues for M now are the main shutter bug: https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug and I guess those reported by me :) ( more or less): https://bitbucket.org/hudson/magic-lantern/issues?reported_by=~licaon_kter&status=open&status=new
Also this one is nasty too: https://bitbucket.org/hudson/magic-lantern/issues/1974/6d-m-700d-70d-in-live-view-mode-ml-menu
Hey thanks for bringing me up to speed, It's been months since I used unified from the main repo, I've just been running my own build because of the 1 take sound issue. I'm going to check it out right now.
As far as the menu timing out after 5 seconds, I never really thought of this as a bug... but we can fix it easily with a fake button press every four seconds if it bothers people. I think the larger issue is not being able to access ML menus when an external screen is attached. High on my list of priorities is better support for external display navigation, and also disabling touch altogether (so you can use a viewfinder/loupe on the camera screen without accidental button presses)
currently, you can long-press trash to enter ml menu, but there is no button that works as q button,
I see two solutions:
1.when ml menu is open, "info" button acts as "q" button. (currently it does nothing)
or:
2.when ml menu is open, "play" button acts as "q" button. (currently it does the same as pressing "set)
What do you think?
Now "1 finger touch" is used in place of Q in the ML menus or you mean something else?
Regarding buttons, there is one exception where M feels cramped, the Autoexpo module: http://www.magiclantern.fm/forum/index.php?topic=7208.msg136296#msg136296 (http://www.magiclantern.fm/forum/index.php?topic=7208.msg136296#msg136296) you can't change some values since we don't have that extra wheel.
when you plug in an external monitor, the touch screen stops working, therefore, there is no way to navigate ml menu when external monitor is attached. Same problem if you're using a screen loupe viewfinder on the eosm screen, u have to remove the loupe to navigate, pain in the butt...
Oh, right, then I'm glad somebody is able and willing to advance EOS M development.
I'll gladly test. ;)
Hi @dpjpandone
Glad you're going to dig into the code. A few of us users have been making some minor contributions and the EOS-M has gotten a few updates recently.
You probably figured it out by now but here's the only change you need to make to get an EOSM build from the current unified branch:
http://www.magiclantern.fm/forum/index.php?topic=14959.msg148768#msg148768
Also, keep an eye on the EOSM issues and pull requests in bitbucket:
https://bitbucket.org/hudson/magic-lantern/issues?version=EOS-M
I'm currently on a vacation for a week but had to chime in when I heard about the good news.
Hey, who removed all the resolutions from mlv module!!??? why does it jump from 1280 to 1600? when was this decision made?
And who said shutter fine tuning doesn't work? It absolutely works, point your camera at a monitor and adjust the value.....
was there stability issues with it?
Anyways, here is a thread regarding fix for alternate Q navigation: http://www.magiclantern.fm/forum/index.php?topic=15681.new#new
Here is a test build: https://www.dropbox.com/s/ycrof8qoxprna9k/magiclantern-Nightly.2015Aug12.EOSM202.zip?dl=0 (https://www.dropbox.com/s/ycrof8qoxprna9k/magiclantern-Nightly.2015Aug12.EOSM202.zip?dl=0)
with the following differences:
1. Play button acts as "Q" button when ml menus are open, now you can navigate without using the touchscreen (useful for external monitors)
2. Shutter Fine-tuning re-enabled (why was this disabled in the first place?)
3. MLV_Rec has 1472 and 1504 resolutions (optimal for shooting 2.39 aspect ratio on SD Card)
Next on my list:
1. fps override - let's fix this first so nightly builds will work again. Dunno if anyone has played with overcranking on other builds, but the EOSM shoots up to 45fps 1080p (crop mode, h264, low-light method) it's pretty awesome. So let's get that back working again.
2. magic zoom is useless in crop mode, we need to slow it down to stop the flicker, - this is lower on my list of priorities since I can navigate with my external monitor attached now...
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.
Quote from: dpjpandone on August 12, 2015, 05:04:09 AMHey, 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
Thanks @dpjpandone for the kind update on the M and will definitely test them out tonight after work.
Will report back results asap.
*cheers*
Quote
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 don't know why, but that's true, some cards do not show the shutter bug. Read the possible explanations by A1ex on the related issue thread on Bitbucket.
https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug
Make sure you check out the EOSM issues on bitbucket and make pull requests for these changes.
I'm still on vacation for another couple of days but I had yet another idea for the shutter-bug issue. If you note in the firmware disassembly there is a call to reboot all the properties after a firmware update. Maybe utilizing this in the same place as a1ex used for the 7D fix?
Thanks for taking this on dpjpandone.
@dpjpandone:
Seems that your build has failed link to the modules. Is there a workaround for this?
(https://farm6.staticflickr.com/5693/20505395986_0082bd6707_n.jpg) (https://flic.kr/p/xeZvQ7)
However, the playback button works great as a 'Q' -- good job on that!
*update*
If I choose 2 or 3 modules -- it works fine after restart. Seems the Deflicker and AutoExpo don't get along with others?
You probably need to delete all the ml stuff from your card and then unzip the contents of the zip i posted. I'm gonna post a new build with the correct fps values for you to test later tonight.
You think I didn't know that?
C'mon...
I even set my cards to exFat every time I put a new nightly on it...
However, after following your directions precisely and still can't get 45 FPS to work with FPS override with crop mode hack enabled during h264 1080p recording, thoughts? It just stays at 31.xxx FPS.
Also FYI I notice the shutter nbrs were slightly off. If I set 1/30 according to canon UI then I go to ML UI which shows 1/48 which is off.
Anyway thanks and I look forward to your next update.
that build doesn't have the fps changes, it's coming later, but the encoder won't record more than 34fps unless you set gop to 1, and gop controls were removed, best we can do in near future in unified is 34fps. I'll PM you some info later so you can play with higher fps. BTW, sorry the modules won't link, i didn't try autoexp to be honest...
Gotcha no problem and no worries. Also another note worth sharing is the fact that I had to type in my admin password to allow your build to be copied over to my SD card. Could that be related to the modules not linking properly?
Doubt it...
Here is today's build with fps fixed. All available settings should be stable, and remember, you can still get 34fps 1080p crop, by overcranking from 30p
https://www.dropbox.com/s/2y9lrmjv5gerjr2/magiclantern-Nightly.2015Aug13.EOSM202.zip?dl=0
please confirm, so we can get nightlies working again. test procedure described here: http://magiclantern.fm/forum/index.php?topic=14959.25
Thanks to nikfreak, this commit reduces flicker on magic zoom in crop mode:
https://bitbucket.org/dpjpandone/magic-lantern-4/commits/5a9c265d088646d055272156a43258251bb0f0ab
Good going dpjpandone. So how do we get your work into the unified branch? It would be nice to get nightly builds working again and it looks like you worked on that too. Any progress on the shutter-bug? I'm not a developer but let me know if there's anything I can do to help push EOS-M development along.
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
I'm Daniel Fort (https://bitbucket.org/daniel_fort/) on bitbucket. My old Unix login, dfort, was taken.
Your changes aren't in the unified pull requests queue which is one of the reasons I asked how to get your work into the main branch--and eventually into the nightly builds.
Quote from: dpjpandone on August 19, 2015, 06:04:10 AM
I just ordered the 18-55 so maybe if i start to experience the shutterbug I'll be able to help.
With that lens and just about any card that isn't a SanDisk 32GB Extreme Pro UHS-I SDHC U3 Memory Card (Class 10) you'll become very familiar with the shutter-bug. I've got a few cards that will guarantee it and one old and very slow 1GB Kodak card that somehow isn't affected so we know it isn't the speed of the card that's the problem. You've probably seen the issue tracker for the shutter-bug (https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug) on bitbucket. Ay ya yay.
Quote from: dpjpandone on August 19, 2015, 06:04:10 AM
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
Check my comment over there. No need to call lv_vsync_signal twice!
ok, think i fixed it, added u as reviewer, can't test till I get home
You created a pull request against your own repository. You need to create a pull request against the unified branch of the main ML repository. If you've done it correctly, you should see your PR in this list: https://bitbucket.org/hudson/magic-lantern/pull-requests/
got it now, thanks for that!
FYI - shutter fine tuning DOES in fact work, and always has. Someone must have disabled it because they overlooked the fact that timer changes are not applied until you press record (Full Frame mode) when in crop mode changes are applied immediately. I have submitted a pull request so that we can get this feature back in nightlies. Thanks to DeafEyeJedi for bringing this to my attention!
EOSM is a funny little thing. It's the only camera that idles in 720p, (hence the squeezed raw video) and the only reason i can think of for doing this is that it somehow conserves battery life. After all, it's battery is about half the capacity of an lp-e8 or similar. I wonder if we can eventually find a way to trick it into staying in 1080p all the time so that we can record full frame raw video without the squeeze factor...
I second that, Mate!
Glad we caught that and yet more to come for this little fun Toy!
*Fun Stuff*
Not really since it was rather difficult to see the LCD screen under the bright sun @ the Beach... Lots of OOF's 8)
workflow as follows:
cr2hdr-r > FCPX
https://vimeo.com/137108865
https://vimeo.com/137108864
*edit*
MLVFS > FCPX (For Dual-ISO comparisons)
https://vimeo.com/137110121
Are you getting 45fps in raw unsqueezed footage?
Seems to be if set AR to 16x9...
https://vimeo.com/137155361
Nice one. Makes me hope for 48fps unsqueezed on 5D mark 3 :P.
Think I found the log issue in HDR raw folder. It affects RAW files. Thanks for reporting.
I'm a bit silly, but how does one record video with a manual lens (using a mechanical lens adapter)?
Silly indeed. Under Custom Functions (C.Fn), select no. 7 (C.Fn IV): Operation/Others Release Shutter w/o lens, enable.
Hi,
This is my first post and its probably a noob question.
how is it possible to display the ML menu like it is displayed on the EOS M on the homepage
http://www.magiclantern.fm/index.html
In ML menu press Info to toggle menu design.
Quote from: Walter Schulz on September 01, 2015, 01:32:00 PM
In ML menu press Info to toggle menu design.
Thanks Walter,
I tried that but it doesn't change the layout to the grid format.
I'm using the last nightly build that compiled successfully, 2015April19
I meant the other Info button labeled Menu ...
Quote from: Walter Schulz on September 01, 2015, 02:00:53 PM
I meant the other Info button labeled Menu ...
Walter, you are a *
Thanks v much
Hi guys.
Been using ml in eosm for about a year now. I use only the 22mm lens.
Today i was testing some ml functions and i think i broke it :'(.
I was testing intervalometer with autofocus and manual focus ramp, when i wanted it to stop it didnt so i tried turning it off and at power on it hanged while focusing, and i had to remove the battery to turn it off again.
Now i dont have autofocus in manual modes, it works in auto mode and in the creatives modes but if i use M, Av, Tv or P it dont work. I have reseted the camera and ml settings, tested with another card and battery. No matter the camera settings AF or AF+manual.
Is there a way to try to reinstall v2.02 firmware in the camera? Dont know what else to try really.
Thanks
Edited-Reinstalled v2.02 in the machine and now life is good again. Thanks
Pressing * ( star ) in M/Tv/Av mode does focus, right?
If it does, then go to Canon menu, custom functions CFn IV 5 and I guess is in mode 1 or 3, so you need to put it in 0 or 2 ;)
( page 282 Canon big M manual )
I tried all that settings too, i reseted the canon settings and ml settings and nothing.
Now with v2.02 reinstalled and card formated and ml reisntalled all works as it should.
Thank you for your quick reply.
Did you have to reinstall the Canon firmware? Usually all that's needed to clear out your settings is on the Canon menu, 4th wrench all the way to the right, Clear settings, Clear all camera settings and/or Clear all Custom Func. (C.Fn) then on your SD card look in the ML folder > settings > and delete MAGIC.CFG.
Hi all... I have two issues and I'd be glad if somebody who are familiar with these could inform me:
I was using my EOS-M in PAL setting.
Than noticed that, in 24fps setting in Canon menu, ML indicates that it is decreased from 30fps
and it shows the shutter angles I adjusted as per 30fps but not as per 24fps.
Now I use it in NTSC setting in general. When I set it 24fps in Canon menu ML shows 29.958-29.953 on the screen.
When I turn on recording or when I set 1.6 crop mode in ML menu, than ML shows 23.970-23.980 on the screen.
When 1.6 crop mode is turned on in ML menu, automatically Canon fps setting changes to 30 fps, whatever the video mode is, PAL or NTSC.
Are these normal?
During record mode or ML menu?
I ask because when NOT recording it's on 30fps no matter what setting.
Once you begin recording it will do it at the desired fps.
Maybe you can detail exactly the steps you set up and the result?
I would like to thank everyone who has worked on ML for the EOS M as well as all the contributers to the discussion thus far. It's so cool to have access to all these rad features canon didn't see fit to provide for us. I think I how the answer already but being that the last successful nightly was in April, I assume that until whatever has broken the nightly is resolved that is the most recent build we can use. Is that a correct assumption? Also- has anyone been able to compile a more recent build for the EOS m and if so, is it much better than the April build?
Thanks!
There are a couple of fixes/improvements in the pipline but nothing earth shattering. I guess that once a1ex comes back they'll be officially integrated too.
Any major bug encountered?
Hi @Justkeepexploring
Welcome to the forum. To see exactly what has been going on with development check out the Magic Lantern section of bitbucket (https://bitbucket.org/hudson/magic-lantern), specifically the most recent commits to the unified branch (https://bitbucket.org/hudson/magic-lantern/commits/branch/unified) which is what gets pushed to the nightly builds.
Regarding the EOS-M, check out the current pull requests (https://bitbucket.org/hudson/magic-lantern/pull-requests/) to see if there's anything interesting in the pipeline and the open issue (https://bitbucket.org/hudson/magic-lantern/issues?version=EOS-M&status=new&status=open)s for any gotchas.
@Licaon_Kter, thanks! Nope everything is working pretty nice, no major bugs here!
@dfort, thanks! I will check out these links, very helpful!
Hello,
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. When using the MagicZoom feature in video mode once recording starts it will begin to flicker.
2. When in video mode and selecting shutter speed or aperture after a few seconds the selection will reset to shutter speed.. Is there a way to default to having the aperture selected? Is it possible to change the color of the text for which ever is selected?
3. Is there a way to show what the white balance is currently at in kelvin when in auto mode like below?
(http://wiki.magiclantern.fm/_media/beertje6.jpg)
Quote from: Mcpackin on September 17, 2015, 01:32:47 AMI 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.
2. Canon UI does this too, not sure ML can force it otherwise. Although it would be useful to highlight it, like: https://bitbucket.org/hudson/magic-lantern/issues/2257/selected-wheel-setting-marked (https://bitbucket.org/hudson/magic-lantern/issues/2257/selected-wheel-setting-marked)
3. Not that I know.
Quote from: Licaon_Kter on September 17, 2015, 10:58:18 AM
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.
Is this fix not present in the Aug 13th build? Also I am experiencing the flicker when not in movie crop mode, just regular movie mode.
You should ask the user that compiled it I guess.
hello or can we find a newer version than the 2015-04-19 8)
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.
Hello, i wonder if there is any way to get ML for EOS M 2? Or is it maybe someone trying to do it?
Quote from: dfort on September 20, 2015, 02:22:50 AM
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.
I followed the tutorial and built ML but all of the modules failed and aren't present in the menu. How do I enable modules for RAW?
That'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.
cd ~/magic-lantern
hg pull
hg update
I posted a couple of other tutorials showing how to set up different build environments. If one of these won't work for you try another. It doesn't really take much time to set up, I've done it many times while preparing the tutorials.
Cygwin (your best choice and you don't need the Windows specific changes for this one to work)
http://magiclantern.fm/forum/index.php?topic=15894.msg154435;topicseen#msg154435
Original MinGW (some people might prefer this but you need the Windows changes to the source code for this to work)
http://magiclantern.fm/forum/index.php?topic=15845.msg154394#msg154394
By the way, let's stay on topic (EOS-M) and continue compiling discussions in their appropriate topic.
Hey there!
Been 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.
I do have one consistent problem with the interface. I have difficulty changing the default values of some options. Let's take the FPS Override function. Turning on the mod edefaults to 2.5 fps. I'm unabl eto change that value. What buton combo do need in order to change values lke that? (In this particular case, I also don't get the submenu that lets me adjust the Jello effect... you can guess I wanna try the slit-scan effect)
I've got ML installed on my t4i as well, and there are enough butons on there that it was easy to find how to tweak those settings, but on the EOS M, nothing I try seems to work. is there a magic button combo?
I have searched the forum for this info - sorry if its someplace super easy to locate (though the search tool doesn't like to search for the term "eos m").. I just couldn't find it.
Thanks SO MUCH for any help. I've become a huge ML fan, and am psyched to get even more out of it once I know how to make these tweaks.
Thans again!
Quote from: bohus on September 23, 2015, 07:39:10 AM
Been 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.
Wow, your first post--welcome!
I also bought an EOS-M to try out Magic Lantern and it has worked out great.
To search for answers I use Google. For example, this gave me several hits:
site:magiclantern.fm eos-m q buttonThe M uses a touch screen. You probably already know that a two finger touch brings up the ML menu, as does the Trash if you hold it for about a second. To get to a submenu touch the "Q" with one finger.
You have to be quick, the menu disappears after a few seconds. That's a known issue that also affects the 6D, 700D and 70D.
https://bitbucket.org/hudson/magic-lantern/issues/1974/6d-m-700d-70d-in-live-view-mode-ml-menu
Quote from: dfort on September 22, 2015, 07:08:08 PM
That'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.
cd ~/magic-lantern
hg pull
hg update
By the way, let's stay on topic (EOS-M) and continue compiling discussions in their appropriate topic.
EDIT: I was able to build ML with all of the modules using the Cygwin guide.
BTW I am building on Windows 10 Pro 64bit using Cygwin/MinGW-w64. Thank you for all of your help!
Your PM says:
Quote from: Mcpackin on September 23, 2015, 04:32:13 PM
I was able to build ML with the Modules with your commit for the cleaned up windows code.
Yay! Now EOS-M users don't have to wait until a1ex gets back to get the latest (unofficial) updates.
Don't worry about all the warning messages the build process spews out, unless it stops with an "Error 1" you're probably ok.
@ Dfort
Thanks for the nice welcome, and the reply! of course I should have used Google to do the search for me. Duh. ;)
Id been using the touchscren to bring up ML, but it idn't occur to me to try it for getting submenus. It totally works, and I feel a little foolish for not working it out. Even using these features at their default values, I've been blown away. Now tha I can actually adjust stuff, I can already see that I'm going to be very vey busy. ;)
What kinda stinks is that ML is realy spoiling me for other cameras. I have an URSA, and yearn for the inds of thing that are in ML. There's so much processor power to spare in that camera, I've got to think that ML could really make that camera into a powerhouse. As I've been using ML, I've wondered "where is the single camera that all these features are inspired by?" Simply amazing stuff... (I defintiely have to look into that open source 4K cinema camera where ML is going to be native. That alone is enough to inspire real interest in that 4k camera project for me).
Two questions...
I see you referencing a compile that's fairly recent. How can I check it against the version of ML that I've got installed now? Just to see where I am in the scheme of things...
Neither my t4i no the EOS M benefit from ML's advanced audio features. Just the VU meters are a lifesaver, so I'm not for a second complaining. I'm just curious whether it's a hardware limitation, or whether it's just an area that requires more development than it's worth right now.
Here are the latest commits to the unified branch--that is what gets pushed out in the nightlies. Note that EOS-M nightlies are still frozen but as you can see we can work around that:
https://bitbucket.org/hudson/magic-lantern/commits/branch/unified
To see what is in the works check out the current pull requests:
https://bitbucket.org/hudson/magic-lantern/pull-requests/
And to watch out for any bumps on the road, the bug reports--these are the new and open ones for the EOS-M:
https://bitbucket.org/hudson/magic-lantern/issues?status=new&status=open&version=EOS-M
As for the advanced audio features--yes, it is a hardware limitation. The 5D mark III probably has the most features available but it is still amazing how many features made it into the EOS-M.
Hello ... is there a chance to see the new version of firmware for this camera? :)
Yes
:P He's on a run, again 8)
And for EOS M 2? :D
Quote from: neoplanta on October 14, 2015, 05:11:53 PM
And for EOS M 2? :D
Different hardware.
Now... the M10 on the other hand :P
M2 was JUST dumped today http://www.magiclantern.fm/forum/index.php?topic=15895.0
I'd assume the M10 would be similar enough to the M3, and stuck with CHDK.
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.
Quote from: Pharinen on October 24, 2015, 10:06:05 AM
Is there anyway to use your smartphone as a monitor with your EOS M?
It is done all the time on movie sets. Most devices draw from the HDMI output and transmit through a wireless network. There's a delay and it isn't cheap though. Here's just one company that makes systems:
http://teradek.com/pages/shop
Quote
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?
Interesting product (http://dslrcontroller.com/), never heard of it. Of course you already found out that the EOSM can't be controlled remotely.
Quote
If not suggest a reasonable priced "field monitor" for me, mainly to check focus. It should be rather small, under <6" preferably.
The Frugal Filmmaker usually has some good suggestions. You can even send him email and he'll answer.
http://filmflap.blogspot.com/search?q=monitor
One gotcha is that your live view will probably be useless when you plug into the HDMI output.
Quote from: Pharinen on October 24, 2015, 10:06:05 AM
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.
have you tried canon's app?
https://play.google.com/store/apps/details?id=jp.co.canon.ic.cameraconnect
i don't see the m listed, but the m2, m3 and m110 are, so it's worth a shot.
M2/M3/M10 have Wi-Fi
M1 does not.
Quote from: Licaon_Kter on October 28, 2015, 10:17:35 PM
M2/M3/M10 have Wi-Fi
M1 does not.
totally forgot that. never mind what I said. disregard. foot in mouth moment while trying to help.
First post here. I just acquired an EOS M and thought I would compile Magic Lantern to start playing around with it. I followed the instructions on this page
http://magiclantern.fm/forum/index.php?topic=15894.msg154435;topicseen#msg154435
to setup my Cygwin environment and after running make clean && make zip I get the following error.
../../src/fps-engio.c:237:6: error: #error fixme: FPS_TIMER_B_MIN and FPS_TIMER_B_MIN are plain wrong
#error fixme: FPS_TIMER_B_MIN and FPS_TIMER_B_MIN are plain wrong
^
../../src/fps-engio.c:295:12: warning: 'fps_timer_b_method' defined but not used [-Wunused-variable]
static int fps_timer_b_method = 0;
^
../../Makefile.filerules:23: recipe for target 'fps-engio.o' failed
make: *** [fps-engio.o] Error 1
I primarily a Java developer, so I'm not completely familiar with C development, but from looking at the code, this seems to be a directive that will always fail.
Is there not a working branch/revision for the EOSM that can compile right now?
Travis
http://www.magiclantern.fm/forum/index.php?topic=16012.msg156314#msg156314
Scroll down to bottom from that post & there you will see the link...
Yes, the EOSM platform is still blocked until this pull request is (https://bitbucket.org/hudson/magic-lantern/pull-requests/649/fps_timer_a_min-and-fps_timer_b_min-fixed/diff) QC'd by a1ex. In the meantime you're more than welcome to use my branch:
hg clone -r EOSM__working https://bitbucket.org/daniel_fort/magic-lantern
Thanks, Daniel. I followed the link that DeafEyeJedi (thanks to him, too) originally gave me which pointed to your repo. I pulled it down and built that and I've been very happy with it so far. I originally had the build from April on it and found it glitchy. Your build seems much more stable.
As expected and indeed it does work well on my M as well.
Well done, Daniel and Thanks for your hard work as always!
Do we have GOP controls yet on the EOSM?
Thanks!
Not really.
Theres that IPP/ALL-I but that's it.
Thanks! ALL-I is great!
Is this feature enabled, or does one have to compile?
Looks like it has to be compiled. The notes on what needs to be done is in this topic:
http://www.magiclantern.fm/forum/index.php?topic=15685.0
I followed dpjpandone's instructions but couldn't get it working. Maybe you can give it a try and report back?
Thanks, dfort.
It appears perhaps that Licaon_Kter knows something that we don't. The dpjpandone thread that you link indicate that there were extensive GOP and flush rate settings back in August, but dpjpandone recommended having only the choice between IPP and ALL-I. However, Licaon_Kter seemed to imply that now there is only the choice of either IPP or ALL-I (with a locked, default flush rate), in coincidence with dpjpandone's recommendation.
Were dpjpandone's suggestions incorporated since last August, and, if so, could that be the reason why your compile attempt failed?
This is the dpjpandone build: https://www.dropbox.com/s/3d6zpxnndvhxpoa/magiclantern-Nightly.2015Aug21.EOSM202.zip (https://www.dropbox.com/s/3d6zpxnndvhxpoa/magiclantern-Nightly.2015Aug21.EOSM202.zip) that has it.
Although there is a catch, but I can't find the info now, something will happen (crash?) if you switch to photo mode when enabled or something.
Thanks, Licaon_Kter.
Is the "catch" the problem that is described in this passage (from the dpjpandone post in the thread linked above):
Quote from: dpjpandoneIf 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
If so, I might keep using the "unmentionable fork" and its GOP controls, as, even though it is outdated, it doesn't seem to have this problem.
Oh, you mean you want to go there (https://bitbucket.org/OtherOnePercent/). No problem looking into a developer's code, after all this is an open source project. If you want to use old builds from no longer supported forks, nobody is stopping you.
I tried adding dpjpandone's changes as he described them on his post (http://www.magiclantern.fm/forum/index.php?topic=15685.0) but it didn't add the video hacks options to the menu.
This is something that dpjpandone as been asking for (http://www.magiclantern.fm/forum/index.php?topic=13439.0) -- for over a year. It looks it just needs someone with the programming skills, motivation and most of all time to get it working in a way that won't leave the camera stuck in some sort of altered state.
dfort, I pulled down the changes your made in your repo to try to get the video hacks to work. You are on the right track. What I ended having to do in order to get it to build properly was add the following
ML_SRC_EXTRA_OBJS = \
video_hacks.o
to the eosm's Makefile.setup.default
That brought the video_hacks.o file into the build directory and the build then successfully completed. I haven't ran the firmware from the build on my camera yet, but I'm think it should work. I haven't been messing with ML long enough yet to be confident enough to be the first one to try it.
Got it, I took dpjpandone's notes literally including what is apparently a typo.
Ok--so I updated EOSM__working. If you don't feel like being a crash test dummy don't mess with video hacks. Otherwise, welcome to the bleeding edge. Note that I haven't loaded it on my camera yet but will as soon and I can get to it.
By the way if you read the very first post in this topic:
QuoteI 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.
So don't be shy to dig into his code and bring back some features. I did an EOSM code cleanup (https://bitbucket.org/hudson/magic-lantern/pull-requests/657/eosm-code-cleanup/diff) that hasn't been merged yet but it is in my EOSM__working branch. In there you will find all the Tragic Lantern stubs that were either not used or removed from the ML main repository. That may give you either enough rope to hang yourself or the key to your favorite TL features.
[EDIT: News flash--a1ex just merged some pull requests including EOSM code cleanup.]
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.
Quote
- 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'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).
Hello!
I have been installing the last available built (april 2015), and i start having fun. Shutter bug is here but a power cycle solves the problem every time, so that's alright. I didn't pay attention before installing, but it looks like there is no way of doing some focus stacking on the eos M. Did I miss something in the thread? Is there any hope to see that happening?
I also got confused a little bit about what's going on in the last improvement. Mostly some video stuff right?
Anyway, thanks to the people working on the code!
Quote from: dfort on November 06, 2015, 03:35:17 AM
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).
First time here, just got a second hand M in ebay. Compiled from your branch a couple weeks ago, and now downloaded and installed that zip. I noticed smthin, now I can go in CBR further than 3.0x, I think before I could just go up to 3.0x, no more values. ¿Am I right? Anyway no matter the value, when I enable bitrate info it seems to be stuck in q+-1.
Tomorrow will try to make some tests.
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.
Quote from: dfort on November 09, 2015, 01:08:48 AM
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]
Thanks for the work.
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.
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).
Quote from: dfort on November 11, 2015, 03:00:04 AM
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.
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).
Thanks! I will build it later and give it a look!!
Is it impossible to develop a magic lantern firmware for EOS M2? :-[
I really want to have the peak focus function on EOS M2 as it helps a lot in focusing when using manual focusing lens
Quote from: alvinlok on November 29, 2015, 11:48:43 PM
Is it impossible to develop a magic lantern firmware for EOS M2? :-[
Not impossible. It is being discussed in the EOS-M2 topic:
http://www.magiclantern.fm/forum/index.php?topic=15895.0
I doubt that a developer picked it up yet but there is still a glimmer of hope--thought the "official" response is something like, "Don't hold your breath."
I recently was introduced to the "Auto adjust Kelvin + G/M" tool by Danne while doing some testing on his new MLV workflow. This is such a valuable tool and we should be using it more often. Basically the way Canon tells you to do a custom white balance is by shooting a still of a white or grey card then using that captured image to set the white balance. Those steps might make sense if you have a mirror flipping in front of your camera's sensor but since the EOS-M is mirrorless there shouldn't be a need to capture a still that you're going to throw away, especially if you shooting in crop movie mode.
Ok--so what I did was to make an extra copy of the "Auto adjust Kelvin + G/M" tool in the main shooting menu to make it more accessible. I put it in my EOSM__working branch that you can build from source via bitbucket (https://bitbucket.org/daniel_fort/magic-lantern/branch/EOSM__working) or download (https://bitbucket.org/daniel_fort/magic-lantern/downloads). I also made a pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/673/auto-adjust-kelvin-g-m-tool-in-the-main/diff) so you can comment on it.
Here's how it works. The tool actually a submenu under White Balance in the Shooting Menu.
(https://farm1.staticflickr.com/578/23327690841_51cc33bb3d.jpg)
This makes it a bit difficult to get to with the EOS-M so I put an extra copy in the main shooting menu.
(https://farm1.staticflickr.com/603/22875195543_843444194e.jpg)
Aim at a white or grey card and it will sample the center 200 pixels to adjust the white balance in both the amber, blue and magenta green.
(https://farm6.staticflickr.com/5703/23042264749_08fc427442.jpg)
That's an Xrite Color Checker Passport though there are other options (http://www.magiclantern.fm/forum/index.php?topic=15915.0). Don't worry about focus, just make sure it is in the center.
By the way, all professional camcorders have a button dedicated to doing this--the EOS-M has a lack of buttons but this makes it much easier. No more excuses for not taking the time to set white balance before shooting!
Seriously now this feels like a Canon Porn site and digging 'em BIG time ... LOVE IT and thanks for sharing @dfort!
Still a work in progress. Fun experimenting on this little camera.
http://www.magiclantern.fm/forum/index.php?topic=16283
Did some changes - I updated the White Balance button assignment so it triggers "Auto adjust Kelvin + G/M" instead of incrementing the color temperature.
[EDIT: That broke something so I'm going back to the cluttering up the Expo menu. Note that you can also set up a custom menu but this is the way I've got my camera setup for now. Keep an eye on the pull request for the latest on what is going on with this.
https://bitbucket.org/hudson/magic-lantern/pull-requests/673/auto-adjust-kelvin-g-m-tool-in-the-main/diff ]
how i can downloaded this????
Reading first post of this thread might help. Use "Show older builds" to get last successful build.
Quote from: alias on December 12, 2015, 10:39:01 PM
how i can downloaded this????
If you are referring to my experimental build with the white balance hack, you can find it here:
https://bitbucket.org/daniel_fort/magic-lantern/downloads
This is where I share my working version and it contains stuff that hasn't been merged yet so caveat emptor!
8) :o
Latest Build
magiclantern-Nightly.2015Dec21.EOSM202.zip
Built on: 2015-12-21 01:07:56 +0200
Changeset: c897f3f (https://bitbucket.org/hudson/magic-lantern/commits/branch/unified)
GOGOGO: http://builds.magiclantern.fm/ (http://builds.magiclantern.fm/)
Thx @a1ex, @dfort, @dpjpandone and everyone else.
Yay!
Thanks @Licaon_Kter for running through all those batteries in order to create the data needed to make this happen.
Keep up the great work!!!
Thanks!
Merry Christmas to @Licaon_Kter for your excellent work as always as well as to everyone else on board for bringing magic back to the M.
Feels good to finally take out the little M from my kit bag and will definitely do a test run with the latest ML on it once again!
[emoji319]
I'm looking for feedback about FPS override changes.
In particular, set FPS override to max (65 fps) and try all available modes. You should get the following figures:
Quote
* 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)
And, of course, you should not get garbled images in any video mode.
Many thanks to A1ex, Licaon_Kter, dfort, and dpjpandone for your efforts to improve ML for the EOS M, and making possible this new nightly build !
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.
ETTR worked in previous versions, but the "ETTR ..." on-screen message during exposure adjust locked and did not dissapear until I pressed the shutter button. So I needed to look at ETTR hint in RAW histobar to know if A-ETTR had already fiinished calculation or not. With the new build, this issue is gone, A-ETTR works fine.
Thanks again !
Quote from: josepvm on December 22, 2015, 11:27:01 AM
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. :)
Is anyone here using a Wi-Fi SD card with their EOS M? Please could someone recommend me one, I'd really like to be able to transfer RAW to my phone and edit in Snapseed (supports RAW). Thanks!!
AFAIk their (mostly) not supported by ML anyway: https://www.google.com/search?q=magic+lantern+wi-fi+card+site:www.magiclantern.fm
Eye-Fi X2 won't work but according to a1ex Transcend card may have not that problem.
http://www.magiclantern.fm/forum/index.php?topic=16249.msg157683#msg157683
Yeah, but the speed is meh.
OMFG a1ex, Licaon_Kter, dfort, and dpjandone for making this update possible, it took 9 months but it was the best christmas present i could have gotten from a bunch of people i have never met. you are all angels to me now and i hope you have the happiest holiday season ever!!!!!!!!!!
magiclantern-Nightly.2015Dec21.EOSM202
Ran the following FPS tests. Max user selectable FPS topped at 70. Tests run at both 65 and 70, no change between them.
Resulting displayed fps results:
1920x1080@30 (no crop mode)
Actual fps: 31.237
Lowest shutter I can select is 1/34.85. The next step after that results in flashing video with horizontal pink bands, and a shutter speed of 0" -6 degrees.
Highest selectable shutter speed: 1/8791, 1 degree.
1920x1080@24 (no crop mode)
Actual fps: 31.237
Lowest clean shutter: 1/34.85. Next step also results in flashing video with horizontal pink bands, and a shutter speed of 0" -6 degrees.
Highest selectable shutter speed: 1/8791, 1 degree.
1280x720@60 (no crop mode)
Actual fps: 31.237
At this setting, I was unable to reduce my shutter below 1/68.91 @ 163 degrees. Shutter speed idled between 1/68.83 and 1/68.91.
1920x1080@30 fps (Movie Crop Mode)
Actual fps: 45.022
Lowest clean shutter: 1/52.81. idles to 1/52.86. Next step, shutter 0" -162 degrees. Flashing video with horizontal pink lines.
1920x1080@24 fps (Movie Crop Mode)
Actual fps: 45.022
Lowest clean shutter:1/92.54 idles to 1/92.68. Next step, 0" -293 degrees. Flashing video with horizontal pink lines.
Ouch - that doesn't sound good.
Do the artifacts go away if you increase Timer B?
If yes, can you find the safe limit for this timer in each video mode? (that is, the lowest value for Timer B where all shutter speeds work)
Yes, artifacts begin to disappear as the Timer B is increased. Below are the lowest safe limits I could find that keep the maximum shutter speed below 1/4000. At the high shutter speeds, there is still an alternating variance that occurs, causing the video to rapidly flutter between exposure levels. It is not noticable at low shutter speeds, as the variance is 0.02. At shutter speeds in excess of 1/3000, the variance is over 1/200.
1920x1080 @ 30 fps (Canon Menu)
Desired FPS: 65 (from 30)
Actual fps: 30.389
FPS Timer A 520 -8 (no user change was made)
Fps Timer B 2025 (FT+55)
Shutter min 1/33.79
Shutter max 1/3619.80 and 3846.20 (idle variance)
1920x1080 @ 24 fps (Canon Menu)
Desired FPS: 65 (from 30)
Actual fps: 30.389
Fps Timer A 520 -8 (no user change was made)
Fps TImer B 2025 (FT+55)
Shutter min: 1/33.79
Shutter max: 1/3619.80 and 3846.20 (idle variance)
1280x720 @ 60 fps (Canon Menu)
Desired FPS: 65 (from 30)
Actual fps: 30.389
Fps Timer A 520 -8 (no user change was made)
Fps Timer B 2025 (FT+55)
shutter min: 1/64.84
Shutter max: 1/3619.80 and 3846.20 (idle variance)
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.
Quote from: Steve_FR on December 30, 2015, 08:48:10 PM
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.
Follow up for ML Movie Crop Mode timer values:
1920x1080 @ 30 fps (ML Movie Crop Mode)
Desired FPS: 65
Actual fps: 30.720
FPS Timer A: 532 (FT-8)
FPS Timer B: 1958 (FT+622)
Shutter min: 1/34.18
Shutter max: 1/3538.20 and 1/3759.40 (idle variance)
1920x1080 @ 24 FPS (ML Movie Crop Mode)
Desired FPS: 65
Actual fps: 24.581
FPS Timer A: 532 FT-8
FPS Timer B: 2447 (FT+1111)
Shutter min: 1/34.16
Shutter max: 1/3538.20 and 1/3759.40 (idle variance)
Side note: While testing FPS Timer B values above FT+1120, ML interface froze and I was unable to shut the camera off. I ejected the battery, and the problem occurred again. After quickly accessing ML menu and lowering Timer B, the problem did not happen again. I attempted to reproduce, but was unable to get it to happen a third time.
@Licaon_Kter You were right about the FPS, thank you!
hi,
but the max resolution for record in raw 25p whit the m1 ??
Thanks
Alessio
At 24 fps I get 1280x720 infinite runtime.
thanks
Hi guys!
I'm having problems when I'm recording H264 video. The video turns to black after few minutes although the time indicator is still counting. This happens randomly (sometimes 3mins sometimes 15min) . I've tried with both ML and Canon interface, with different sd cards,another lens, different batteries but the problem still exists. I 've noticed weird colors (pink mostly) on lcd. I was using magiclantern-Nightly.2015Dec21.EOSM202 with 2.0.2 firmware. I've also re-updated 2.0.2 firmware with EOS Utility. It didn't worked. I have recorded a short session with another camera, you can download two small video files (around 5mb) from here : http://we.tl/pIBOem6yDS
Any ideas?
Quote from: yt2 on January 07, 2016, 01:59:18 PM
I'm having problems when I'm recording H264 video.
Maybe report it here: https://bitbucket.org/hudson/magic-lantern/issues
Thanks, I reported it but I could not find %1 on the assignee list so I choose a1ex.
Issue #2445
https://bitbucket.org/hudson/magic-lantern/issues/2445/black-video-after-a-few-minutes-of
Have you actually tried to reset ML settings yet, @yt2?
Yes, same issue.
The Canon firmware is missing these items in the menu: (even without a card in the camera)
-certification logo display
-copyright information
-firmware version
I know it sounds weird but is it possible that ML messed with canon firmware?
I have been told "If this happens without a ML card then it's a hardware issue" in bitbucket.
It is getting strange.
Quote from: yt2 on January 07, 2016, 09:59:59 PM
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 ;)
Responding to the FPS override changes:
(http://i.imgur.com/g4cWrvV.jpg?1)
At 45.02 fps in 3x crop, horizontal pink lines are visible. I think this is because of changing shutter speed. it showed 0" when I was testing different shutters.
Also at 720p in no crop mode, maximum fps is 31.23.
Did you try turning off camera and back on?
In my case, the HPL went away after reboot.
Is this normal?
Wow, 182 downloads of my EOSM 1280x720 crop-mode video focus pixel file?
I just did some cleanup work on it and posted a new version. Nothing major but if some stray dots are showing up this new version should take care of it.
More info about focus pixels at this topic:
http://magiclantern.fm/forum/index.php?topic=16054.0
Download the new focus pixel file here:
https://bitbucket.org/daniel_fort/magic-lantern/downloads
Eye-Fi revisited:
Eye-Fi Mobi 8GB working with Magic Lantern and EOS 650D, installation and all. But as mentioned above: Slow, very slow. About 15.5 MByte/s write and 18.3 MByte/s read. Haven't tested transfer speed via WiFi yet.
Seriously that's better than what it used be and could you confirm which version is this ... either the Mobi Pro or Mobi Pro X2?
Curious of the transfer speed for snapping photos!
None of those. It's the orange "Mobi" (no suffix) to the right. http://www.eyefi.com/buy-now
So the $30 versions won't be any "faster" than these two mentioned which costs usually between $70-90?
I have done a single test with single card and don't know what you are talking about.
(http://images.tapatalk-cdn.com/16/01/09/2903425562ae42f0c74d502c460180c2.jpg)
This is the new model version that I'm assuming you just got.
(http://images.tapatalk-cdn.com/16/01/09/2ef76cae4d7a50771be2f4b7b7c95248.jpg)
This is the older version although it's 16GB.
(http://images.tapatalk-cdn.com/16/01/09/84ef6b71b20a44a5e23587c8cd0dc34a.jpg)
The newer version of the 16GB is literally half the price?
(http://images.tapatalk-cdn.com/16/01/09/5c53b59f68ff6e589877f4a968a8a5ce.jpg)
Now here comes my question ... Is this by any chance any quicker for about $20 more than the one above?
*Sorry guys for the off-topic*
Again: I tested one single card (the first one on your list). How on earth should I know the performance/compatibility of the other ones?
And the "Pro X2" is not the older version, I think. There is a "Connect X2".
And prices for out-of-stock/out-of-production items are sometimes weird und not to be taken seriously.
Gotcha Walter and I'll figure it out on my own.
Again thanks for sharing!
http://img.plici.ro/images/2016/01/09/Untitled7926b.png
hi guys in mlv_rec i got this issue but in raw video work perfect.
MLRAWViewer (https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_4_3_win32.zip) has the same issue?
yap + MLVViewSharp
crop mode http://img.plici.ro/images/2016/01/09/Untitled244518.png
i try diferit shuter speed + diferit frame rate 24/30. :|
i use magiclantern-Nightly.2015Dec21.EOSM202.zip
What kind of memory card do you use @Bobe?
Lexar 32Gb 633x 95/MB/s u3 I
Have you tried setting it into exFAT from card reader on your computer first?
and if so be sure to enable 'exFAT' within MLV advance menu in ML settings.
http://img.plici.ro/image/vTs
is fine here :|
i go format and reinstall ML BRB
rec not stop, just when shooting stripes on eos m display. in raw viwer i see the issue. When filming everything seems ok
sry for bad eng
the problem has not disappeared, I tried another resolution and sound off :(
(http://img.plici.ro/images/2016/01/10/Untitled3c4423.md.png) (http://img.plici.ro/image/vuW)
same magiclantern-Nightly.2015Dec04.EOSM202 :( I think it's something bad on camera hardware :/
Upload a original MLV of that file if possible?
https://mega.nz/#!YlAHGTjI!5htKdhxVOGZdV088WwQcWZ5vkstCo1l1NFt5OZ5crB8
same bad lines whit other ML vers magiclantern-Nightly.2015Apr19.EOSM202.zip
@bobe: Bad frames, I guess the card can't keep up or other hardware issue.
Lexar 32Gb 633x 95/MB/s u3 - advertised speeds don't matter in general, true speeds matter, now the EOS-M can't do more than 40Mb/s anyway, no matter the card.
Try to benchmark the card: Start H.264 ( normal) video recording an then go to ML menu -> Debug -> Benchmark -> Card R/W, wait for it to finish and take a pic of the results.
Although that resolution should be low enough to not pose transfer issue, hmmmm.
hi,
i'm new in eos m ( i am a user of magic lantern in mark 3 )
i have a problem whit the RAW File
there ara many many pink noise.
can you help me ??
https://www.dropbox.com/s/v1y69wzz2cxv1o2/M10-1135_C0000_00008.jpg?dl=0
FIX i change the frame rate in canon menu 1920x1080 30fps to24fps and fps overwrite 24fps the issue gone :) i rec mlv 411.4 sec. clean.
who want try this issue put camera in 1920x1080 30fps and record in mlv 1280x432 @ 30fps.
the issue not fix in 20-31 fps range overwrite in ml menu, she gone afther i change the video setings in canon menu 30fps top 24fps.
Sry for Bad ENG.
Quote from: musicmanx on January 10, 2016, 12:04:59 PM
i have a problem whit the RAW File
there ara many many pink noise.
Look around here: http://www.magiclantern.fm/forum/index.php?board=54.0 for the word pink.
Also, your RAW program (which one do you use?) should have something that handles that.
Quote from: musicmanx on January 10, 2016, 12:04:59 PM
i'm new in eos m ( i am a user of magic lantern in mark 3 )
...
there ara many many pink noise.
I'm a new 5D3 user but have been using the EOS-M for a while.
What you are seeing are the dreaded "Pink Dots" though they show up in other colors too but mainly green and magenta. They are most likely caused by the focusing system used by certain cameras like the 100D, 650D, 700D and EOSM.
You can either try chroma smoothing or if the program you are using has it, Focus Dots suppression--MLV Producer for Windows (http://www.magiclantern.fm/forum/index.php?topic=15271.0) has it.
Here's more than you will ever want to know about that "pink noise": http://www.magiclantern.fm/forum/index.php?topic=16054.0
QuoteAlso, your RAW program (which one do you use?) should have something that handles that
thanks for your answer
i' susing RAW MAGIC but there isn't a fixed problem.
a program for mac thet fix the problem ??
Quote from: musicmanx on January 10, 2016, 03:04:54 PM
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)
See here for other apps that you can use: http://www.magiclantern.fm/forum/index.php?board=54.0 (http://www.magiclantern.fm/forum/index.php?board=54.0)
MLVFS for Mac/Linux
MLP for Mac
Also MlRawViewer is kinda old, if it works ok if not the developer did not update it in a while.
Thank you ;)
Strange, I just checked the Nightly Builds (https://builds.magiclantern.fm/#/) and it looks like the only platform that hasn't been updated is the EOSM. Ironically, the latest changeset (https://bitbucket.org/hudson/magic-lantern/commits/ca5315a3b586931c1b58b9e72fbed6b96d558d6f) fixes an exposure compensation limits issue on the EOSM.
For overview ask Jenkins: https://builds.magiclantern.fm/jenkins/
And you are right. Don't know why.
Thanks for verifying Walter. Looks like there are some other platforms that either didn't get built or are broken but we're only interested in the EOSM here. 8)
EOSM is not broken, it builds fine, Jenkins did not even try to build it yet.
Looks like something didn't quite get pushed to the repo in time last night (some cameras got it, some didn't, I guess the EOSM ran first):
EOSM Build:
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
60D Build:
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
Should get updated tonight though, so just be patient ;)
1100D and 600D are disabled because: http://www.magiclantern.fm/forum/index.php?topic=15360.msg160341#msg160341
5D3.123 has to be merged (it's in a separate branch).
New EOSM nightly is ready.
https://builds.magiclantern.fm/#/
The update includes an exposure compensation limits fix (https://bitbucket.org/hudson/magic-lantern/issues/2447/exposure-compensation-stuck-cant-be) for the EOSM and it also fixes a bug in mlv_rec.mo that is key to automating focus pixel removal. There's still lots to do with focus pixels (http://www.magiclantern.fm/forum/index.php?topic=16054) but the research is being carried out on the EOSM.
By the way, I took down the custom EOSM build from my bitbucket download area because all my pull requests have been merged except for the EZ White Balance which I can't get working yet. I also took out Video Hacks which I never figured out. I'm currently using the standard unified branch which is available from the nightly downloads page.
(http://i.imgur.com/rcuDqov.jpg?2)
I tried to shoot time lapse in 3x crop mode. But the files are posterized. I don't know if the dng files are corrupted or another issue.
Settings: Basic silent picture in Video crop mode. FPS override. Shooting interval : 30 Seconds. Magiclantern-Nightly.2016Jan15.EOSM202
Sample DNG file :https://drive.google.com/file/d/0B5vPhFcWMEVic1l4SmJ1ZW9VWEk/view?pref=2&pli=1 (https://drive.google.com/file/d/0B5vPhFcWMEVic1l4SmJ1ZW9VWEk/view?pref=2&pli=1)
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 again
Quote from: mshirani on January 18, 2016, 11:03:11 PM
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 again
Use "leave menu" as trigger.
You need a "Picture review" time (not off) in Canon menu set up.
The camera is/might not be stopped, it just waits for your input (buttons?) since, I believe, you did not set up a review time.
What are your power saving settings? Be aware of this bug: https://bitbucket.org/hudson/magic-lantern/issues/2265/turn-off-lcd-enabled-stops-intervalometer
Do upload the (a shorter) MLV with your issue.
Does it happen when saving as DNG (instead of MLV) in camera?
Tried any other program for MLV ? ( MLVFS? MLP for Mac? MLVProducer? )
Thanks for the reply.
The problem was the bug since I used the settings that you mentioned.
About the video, it was MLV. I tried recording again it was working without a problem. I think the file somehow corrupted.
Why is there no audio tab in the newer builds?
Quote from: Justinliv5 on January 25, 2016, 09:59:41 PM
Why is there no audio tab in the newer builds?
There was never one in the first place. See: http://builds.magiclantern.fm/#/features ?
Be careful not to confuse it with the MLV_SND module option.
Hi
Tried magic lantern and getting along well. Thanks so much for all the hard work.
Just a query if I may?
Like the use Prefs>Powersave in LiveView>Use shortcut key>INFO = Blank LCD screen.
However this stops the menu to change to AV/ TV/M etc unless it is changed back. Am I correct or is there another way?
Would be great INFO key could be like TRASH key short click one action hold ML menu. Don't know if the INFO key could be like that ie click blank screen/hold choice of camera setting?
Many thanks Michael
Not so many buttons on the M unfortunately.
Use a lower timer in Turn LCD off maybe?
Hi Licaon_Kter
Thanks for reply which I take it is NO to all possible amendments.
Hello! Im new here and i have problem. Got EOS M and i did try to install ML but ... install goes fine, it says restart camera and back up ... i do that and then when i turn on camera there is nothing ... everythign is normal. I did try to flash Canon FW 2.0.2 again just in case and then ML and still nothing ... And help would be good. Thanks
EDIT
I figured it out :D
I've got a similar problem to what donmarkon describes.
I've been thru the process about 4 times now and the result is the same - everything goes fine, but when I touch the screen with 2 fingers, I can a message screen, which has something like "Magic Lantern - Development version for test purposes". It remains on screen for a few seconds, flickers a little, then nothing - ie back to normal screen.
Any help appreciated.
Thanks.
just press any button when the message is on screen ;)
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.
Quote from: StopGap on February 12, 2016, 01:53:57 PM
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)
Done, all builds after Feb 13 have a little helpful text ;)
Quote from: keel on February 21, 2016, 04:14:03 PM
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.
It seems like you probably have FPS override turned on and set at a low setting. Some more information might help. Are you using MLV or RAW? What other modules do you have turned on?
Quote from: keel on February 21, 2016, 04:14:03 PM
sidenote- can i make the ML menu appear for longer, i barely have a moment to read before it disappears.
That's been an issue (https://bitbucket.org/hudson/magic-lantern/issues/1974/6d-m-700d-70d-in-live-view-mode-ml-menu) on the EOSM and a few other cameras for a while. The developers have tried several times to fix it.
Quote from: keel on February 21, 2016, 04:14:03 PM
My liveview is lagging severely.
I thought maybe when I imported the video it might be okay, but the video is lagging as well.
Do detail your settings, fps, size, etc.
What SD card?
the issue was the fps defaulting to a low number, once i adjusted it the issue went away. Feeling a little stupid, but very happy that first hurdle has been cleared. Thanks !
Hi guys
Im new & have some problem
for the first time i tried to install latest Ml on my eos M
After format in low level & uzip files to root and update firmware for ML
it shows all command and restart camera command , when i restart camera nothing happened
default canon firmware running then i uninstall ML & install canon firmware then again install Ml but it running on canon firmware not Ml
Camera Boot with canon default not ML
what is problem
thanks
Read replies #923-925
Tap w two fingers on touchscreen OR press and hold the trash button for abt 2 seconds...
Many Thanks Walter Schulz & DeafEyeJedi
Quote from: Walter Schulz on February 27, 2016, 10:19:03 AM
Read replies #923-925
The latest builds contain the "press button" tip already ;)
hello all, i am new here , using ML for quite few days and i love it.
i have seen new canon G16 or S120 camera which came recently , and i liked one perticular mode of shooting called "star mode" , can we have something like that in ML build ?? , its seems the setting are almost there in ML but for effortless shooting if we have similar menu and features it will be great
Describe what it does.
Hi guys,
I've been searching a lot and not finding what I'm looking for. Would anyone be willing to upload some high quality footage to Vimeo for download or high quality footage to you tube? A lot of the footage I'm finding is rather old and looks low res. What I'm wanting to see is the sharpness and detail of the M with the raw hack. Lots of stuff I'm seeing has had sharpening added of is very shallow depth of field... Making it hard to judge sharpness and detail. Wide angle sharp footage is what I'm looking to see about f5.6 or f 8 aperture. Thank you.
Quote from: Teamsleepkid on March 02, 2016, 01:53:22 AM
Would anyone be willing to upload some high quality footage to Vimeo for download or high quality footage to you tube?
Whatever gets uploaded there will be subject to lossy compression. What is it exactly that you want--to see the quality that is possible shooting raw video on the EOSM? It can pretty much stand up to any of the other Canon APS-C cameras in crop mode but it is terrible in full frame mode because it can only do what is called mv720 which does lots of line skipping and the aliasing is quite bad.
Here's a frame from the EOSM in crop mode using dual iso raw video: https://flic.kr/p/DoKXCV
Yeah I'm mainly interested in crop mode. Like I said I can't really find any video that isn't shallow depth of field. I realize it's compressed that's why I was asking for Vimeo download. Also new videos seem to look better even on YouTube. Most of the vids of the M are from 2012 2013. I also realize it's hard to have a wide angle on a 3x crop. I'm just looking. I'm interested in the M but I just can't tell about sharpness and detail. I haven't seen anything very definitive. That still does look pretty good though btw. Thanks dfort.
Hi, I am new here and have trouble in finding RAW video function.
I installed the latest version(magiclantern-Nightly.2016Feb29.EOSM202) of ML and didn't find the RAW video function.
I tried several older versions and couldn't find RAW video function.
Can someone tell me what's the problem? Many thanks!
@modachu
Step #1
Go to Modules and select
mlv_rec.mo Press the Set button.
(https://farm2.staticflickr.com/1641/25663894616_e665382a5c_z.jpg)
Step #2
Restart the camera and check to see that the module loaded.
(https://farm2.staticflickr.com/1575/25389211280_88c7274752_z.jpg)
Step #3
Go to the Movie menu, select Raw Video (MLV) and press the Set button to enable it.
(https://farm2.staticflickr.com/1546/25663894566_f5467ceb3b_z.jpg)
Ok--there's more to recording raw video. You can enable mlv_snd.mo and record audio with your raw recording and mlv_play.mo that allows non-real-time in-camera playback. You also need to play around with the horizontal resolution, aspect ratio, crop vs. non-cropped mode, fps override--in other words there's lots of settings to try out until you find something that fits your needs.
There's also another module named raw_rec.mo which is an earlier implementation of raw recording that some users still prefer when they are pushing the limits of image size and/or fps.
I find that the best results when recording raw on the EOSM is with the Canon menu set to 1920x1080, ML menu set to 1280x720, Aspect Ratio 16x9, Movie crop mode turned on. This uses just a small section of the center of the sensor so you'll need to use much shorter focal length lenses. Fortunately it is easy to adapt C-mount lenses made for 16mm film or 1/2 or 2/3 inch video cameras to the EOSM to make a compact setup.
Note that the EOSM cannot do what is called mv1080 mode (http://magiclantern.fm/forum/index.php?topic=16608) so don't expect it to match results you're seeing from the other cameras. Still, you can get some impressive results with the EOSM.
Oh yeah--then there's the focus pixels issue (http://magiclantern.fm/forum/index.php?topic=16054.0). Many of the shot posted on that topic were done with the EOSM.
EOSM MLV raw video frame shot in Movie crop mode, 1280x720, Dual_ISO
(https://farm2.staticflickr.com/1540/24460418311_088b48f7e9_z.jpg)
After focus pixel removal using MLVFS (http://magiclantern.fm/forum/index.php?topic=13152.0) along with MLP (http://www.magiclantern.fm/forum/index.php?topic=13512.0)
(https://farm2.staticflickr.com/1466/24542740305_d4a1d9c47c_z.jpg)
@dfort
Thank you very much for your kind reply and detailed instructions. It does solve my problem. It's sweet to have this forum and it helps all beginners a lot. Thank you again!
I just wanted to share that with sandisk 32gb sdhc uhs-I card I don't expirience the "shutter bug" (while using the 18-55mm IS EF-M lens)
I read on several places that the cause for the bug is not known (please correct me if I am wrong) and that using some cards "prevents" it from happen.
Well are you experiencing the shutter bug issue with other cards?
There are a few cards that can get you around the shutter-bug, the SanDisk 32GB Extreme Pro UHS-I SDHC U3 (Class 10) 95 MB/s SD Memory Card seems to be the most popular.
Note that the shutter-bug only affects EF-M zoom lenses. Primes and lenses mounted via a lens adapter don't seem to be bring up the shutter bug. There are several workarounds including turning the camera on/off/on within a second or so and twisting the lens off then on while the camera is powered on.
Here's more than you'll ever want to know about the shutter-bug: https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug
Hello ALL. Love Magic Lantern on EOS M. I have searched and found info about All-I in Tragic Lantern and that it was merged into the current iteration of ML. I can't seem to find it in the menus. How do I Record in H264 All-I? Thanks
It's not in, you need a special build.
An older one from @dpjpanone (http://www.magiclantern.fm/forum/index.php?action=profile;u=40679):
Quotehttps://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)
anybody got any sharp wide angle footage? Like trees... I wanna see some detail. :)
How wide does it have to be and how many trees?
I've got a 12.5 c mount and I was thinking about getting something wider like an 8mm or 6mm. I'm coming from a gh2 which has pretty good detail so I'm wondering how 720p crop mode will stack up. As many trees as possible lol. Actually 1 tree would work. Or buildings, whatever. Looking for detail.
Alright lemme call 1-800-GO-DFORT.
Well first of all there is no 720 crop mode that I know of. There's mv1080crop and zoom mode.
A while back I posted a few still frames using a few C-mount lenses.
http://magiclantern.fm/forum/index.php?topic=15660
Then there's this shot that I posted too many times, shot with an 8mm Rokinon fisheye lens in Movie crop mode, though it doesn't show much in the way of fine detail. This is a Dual ISO shot.
(https://farm2.staticflickr.com/1466/24542740305_d4a1d9c47c_z.jpg)
I think what @Teamsleepkid might like to see are some DNG frames made from EOSM raw video. Crop mode is where the EOSM can hold up to the other Magic Lantern enabled cameras that use APS-C sized sensors and SD cards. Full frame--not so much because it cannot do mv1080 video.
Very interesting post on the c mounts and crops thank you. So let me see if I can get this straight. There's a 1080p mode which the M can't do. There's a 3x crop mode that is h.264 only and there's some thing like a 5x crop when recording raw on the M? I was thinking raw was at 3x... Bummer. I mean over apsc. I always do my math over apsc or super 35. Not full frame. Films are never shot this way except for Hitchcock or vistavision.
Sorry for the confusion--I meant the full APS-C sensor, not full frame as a 35mm still camera frame. I come from a film background so 35mm to me is a four perforation high Academy Full Aperture dimension of about 24mm x 18mm (1.33 : 1).
H.264 frame dimensions are defined by the Canon firmware though ML adds crop and zoom modes to 1920x1080 H.264.
Here are the raw video modes as they apply to the EOSM:
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.
The buffer size is the area of the sensor the camera is using in each mode. The actual image size is a crop from the full buffer. You'll notice that mv1080 has a buffer size that's smaller than 1920 wide. That's also true when shooting H.264, the on board compressor is doing some upscaling when shooting 1920x1080 H.264.
Note that the EOSM will record in mv720 mode even when everything is set to mv1080 mode.
To add to the confusion you are limited to the write speed of the SD card controller so there's no way to record more than a second or so at maximum possible resolution. The sweet spot seems to be about 1280x720. Now on most ML enabled APS-C cameras that save to SD cards you can shoot in mv1080 mode but you need to scale back the image to about 1280x720. Only the 5D3 can record 1920x1080 (and slightly larger in zoom mode) raw video.
The difference between getting into mv1080crop and zoom modes is that you enter mv1080crop via the Movie menu and zoom mode via the magnifier button.
There's a lot more to it than this. I'd recommend searching through the forum for more information on raw video.
Can someone explain me how to update magic lantern to latest version ?
http://builds.magiclantern.fm/#/
Choose EOSM and follow the simple instructions :)
So i can just delete files and do a new install ?
Yes
I've been looking at the nitrate calculator. Does the 3x5 subsampling option have lots of moire and aliasing?
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? I don't need any of the extreme hacks like RAW and stuff. Just a stable way to get audio levels on my screen and focus peaking and stuff. Thanks all, sorry for being that guy. I just can't find anything anywhere.
Cams supported in "stable":
550D
60D
600D
50D
500D
5D2
Quote from: kentb on March 28, 2016, 09:57:24 AM
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 :)
Quote from: Licaon_Kter on March 28, 2016, 10:33:04 AM
You have this forum... and its search function... go bleeding edge :)
Hah, I've tried! I have kinda limited access to interweb and time, otherwise I wouldn't be the guy to ask dumb questions. Just wanna see if I'm missing something. Like a nice big link that says "stable nightly with help files" I wouldn't be upset to find that.
also the search is either janky or I'm dumb (very possible) or it's my internet or something. But it's not working.
http://magiclantern.fm/forum/index.php?topic=13652.0
Ok. Each word must be at least two characters long. Yup. Read the red text. My bad. :P
And your problem with nightly builds is? Q is rhetorical because - excluded experimental builds - it's your only option. There is no "stable" version for M and never was. If you don't need a specific feature: Feel free not to use it.
You can use Google advanced search options:
"EOS M" and all the stuff you need to look for site:www.magiclantern.fm/forum
Ok, rookie user error. I'm just gonna be that guy today. How do I get my WB back on auto for when I want it there. Kelvin is nice, but sometimes auto is useful. Last question of the day.
Edit: Never mind figured it out. Thanks for the patients folks.
Quote from: Teamsleepkid on March 26, 2016, 06:00:59 AM
I've been looking at the nitrate calculator. Does the 3x5 subsampling option have lots of moire and aliasing?
You mean
bitrate calculator? Which one? There are many online.
Please explain what you mean by 3x5 subsampling option. Is this a menu option?
Perhaps you're talking about mv720 mode in raw video or the 1280x720 H.264 setting which skips every 3 pixels horizontally and 5 pixels vertically. Yes, this does have lots of moiré and aliasing on the EOSM as it does on other cameras except for the 5D3 which uses pixel binning instead of skipping.
The EOSM doesn't have mv1080 mode raw video, 3x3 sampling, which is far superior. However it does have crop mode which shows virtually no moiré and aliasing on most shots. If your subject has lots of fine patterns and details you may still have some problems but that is an issue with pretty much all digital cameras.
Got two changes for you in the latest nightly:
- workaround for menu timeout (https://bitbucket.org/hudson/magic-lantern/pull-requests/688/eosm-restart-the-canon-dialog-for-ml-menu/diff) (dmilligan)
- fix for cropmarks in movie mode for playback (http://www.magiclantern.fm/forum/index.php?topic=16991) (not tested)
Do they work?
Quote from: a1ex on March 30, 2016, 09:14:28 AM
Do they work?
Nice work @a1ex as usual once again!
•Confirmed the Workaround for Menu Timeout (Thanks @dmilligan!)
•Confirmed the Cropmarks in movie mode to be working.
https://vimeo.com/160855613
Looks like the framing is different between standby and recording. How can that be called "nice work" instead of bug? :P
Do you mind printing the value of get_current_dialog_handler() during movie playback? ML couldn't figure out that in the playback screen you actually have a video.
Actually assumed it was due to the external monitor recorder I had used (confirmation below) to show the EOSM liveview display but sure if you can refresh my instincts ... In order for me to print the value of get_current_dialog_handler() during movie mode would require for me to use LUA scripting, correct?
*edit*
It was in fact due to the limitations from EOSM HDMI output being recorded onto an external monitor which was why the crop marks were chopped off during playback but this isn't the case on the LiveView LCD itself.
So yes indeed nice work once again @a1ex and please let me know how can I help with providing you the print values per your request?
https://vimeo.com/160861255
You can't do it from Lua (or at least not yet), but you can put that in a printf or bmp_printf or NotifyBox somewhere (for example, in don't click me).
The bug is only present with external monitors.
@a1ex -- Not even sure if I did this correctly per your request.
https://vimeo.com/160930659
Hehe, just delete that verbose code ;)
got some probs with my m...
ran all the time stable, but today the first error.
tryed three different ml-builds (1.april 16, 12. jan 16, 19.april 15), every time the same error, can someone help me?
camera works without ml fine!
(http://fs5.directupload.net/images/160401/temp/3qv3zmvj.jpg) (http://www.directupload.net/file/d/4311/3qv3zmvj_jpg.htm)
The best solution is to find the nearest trash. Sorry
@GutterPump, for your post?
Relax, it's a joke, we are April 1.. Just change the date of your camera and it will work fine.
very clever April fools joke. it got me! i was all over the internet looking for a solution LOL
guys... dont scare the shit out of me! :D
Quote from: jeredmckenna on April 01, 2016, 10:58:36 PM
it got me! i was all over the internet looking for a solution LOL
Really? 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")
Why not use a search engine ( "magic lantern error 0x000000aa" ) ? It's in the first five as last year was covered pretty good.
At least he was reading the screen and followed advice. Those opening bitbucket issues didn't.
03.30 & 04.01 Both versions start
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
02.29 then previous versions is no problem
(Use google translate, if not fluent, please forgive me)
You see this: https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug
Quote from: leonarka on April 07, 2016, 12:40:52 PM
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
Yes, this is a known issue, the shutter bug (https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug) but currently the causes are not well understood and there is still no way to completely solve it. It affects all EF-M zoom lenses, but not the EF-M 22mm f2, and also does not affect EF and EF-S lenses mounted on the EOS-M using the lens adapter.
The bug can appear frequently or not, and this depends a lot on the brand and type of SD card you are using. Currently we know that using a SanDisk 32GB Extreme Pro UHS-I SDHC U3 (Class 10) 95 MB/s SD Memory Card in most cases can greatly help to reduce to the minimum the probabilty of experiencing the bug.
Hello dear friend
2015.04.19 in the previous version, the shutter occasional problem, I know
But the version 2015.10.01 later, I've never had this problem
Until 2016.02.29 previous version, are no problem
Until this version 2016.03.30, before there was a problem
And not accidental, is fixed, it must happen
Just unlock the lens first, and then boot
They will be unable to press the shutter
This can be compared to 02.29 03.30 differences between two versions,
Then catch the bug
-------------------------------------------------
After repeated testing
Formatting can be solved shutter BUG
Kind of hard to follow what you're saying. If you are referring to what is available on the Nightly Builds Download page there are no 2016-02-29 or 2016-04-19 builds. These are the builds that are available:
Date: 2016-03-30 00:11:06 -0700
Date: 2016-03-28 15:08:54 -0700
Date: 2016-02-28 15:09:11 -0800
Date: 2016-02-26 15:08:47 -0800
Date: 2016-02-23 15:08:36 -0800
Date: 2016-02-12 15:08:55 -0800
Date: 2016-01-14 15:09:12 -0800
Date: 2016-01-11 16:20:06 -0800
Date: 2016-01-11 15:08:04 -0800 (failed)
Date: 2015-12-20 15:07:56 -0800
Date: 2015-09-30 15:09:02 -0700 (failed)
Date: 2015-04-18 15:08:06 -0700
Date: 2015-04-14 15:08:11 -0700
I have a card and lens combination that reliably brings up the shutter-bug (I think any card 64GB and greater along with an EF-M zoom lens will do this) and have tried the 2016-02-28 and 2016-02-26 builds. Both exhibit the shutter-bug. As far as I know there has been nothing done over the past couple of years that has had any effect on the shutter-bug.
https://builds.magiclantern.fm/#/
EOSM.202
Date: 2016-04-01 06:08:48 +0800
Date: 2016-03-30 15:11:06 +0800
Date: 2016-03-29 06:08:54 +0800
Date: 2016-02-29 07:09:11 +0800
Date: 2016-02-27 07:08:47 +0800
Date: 2016-02-24 07:08:36 +0800
Date: 2016-02-13 07:08:55 +0800
Date: 2016-01-15 07:09:12 +0800
Date: 2016-01-12 08:20:06 +0800
Date: 2016-01-12 07:08:04 +0800 (failed)
Date: 2015-12-21 07:07:56 +0800
Date: 2015-10-01 06:09:02 +0800 (failed)
Date: 2015-04-19 06:08:06 +0800
Date: 2015-04-15 06:08:11 +0800
This is what I see on the page
On the current generated by 2016-03.30 & 04-01 Shutter BUG
Determine certain occurs
Repeated tests, put on 2016-02-29 previous versions, there is no problem
Put a version of 2016-0330, the problem immediately
Ok--I see, different time zones. So what you are saying is that this build doesn't exhibit the shutter-bug:
Quotemagiclantern-Nightly.2016Feb29.EOSM202.zip
Changeset: dd16e5d
Well it
does exhibit the shutter-bug on my system. I also tested this version:
Quotemagiclantern-Nightly.2016Feb27.EOSM202.zip
Changeset: c8c0c20
and came up with the same results.
I'm not saying that your tests aren't valid, just that I cannot repeat your findings. On some cards the shutter-bug is intermittent so the test should be repeated multiple times. You need to cycle the power each time you test for the shutter-bug. On my system the shutter-bug appears 100% of the time with all of the builds that I have tested.
Quote from: leonarka on April 07, 2016, 12:40:52 PM
Necessary to unlock the lock and then press the shutter
Depends 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)
Guys i need help, when im using vintage lens i loose square box in ML so im unable to move it around, so when i use half press zoom it always zoom in midle. And sometimes i want to change location of center. Can you tell me how to change location easy? This is also the case for magic zoom
Thanks magic lantern Team
The latest version 04-11
Fixed EF-M 11-22MM, this type of lens to be unlocked
Just before turning on the power to unlock, you can not press the shutter BUG
But there is a new small problem,
Is (P) mode, turn the dial, the aperture can be adjusted even !! ??
Thanks for all the help guys. Especially dfort. I'm understanding much more about the m now. I've been reading about mlvfs and workflows. What are you guys doing for workflows. What I'm after is something that will remove the Focus Pixels and make me prores files quickly and easily...
@Teamsleepkid are you using OS-X, Windows or Linux?
There are several ways to make ProRes files from MLV's.
MLVFS removes the focus pixels and works with all platforms. To make ProRes files from the virtual DNG's you can use MLP (http://magiclantern.fm/forum/index.php?topic=13512) (OS-X), convmlv (http://magiclantern.fm/forum/index.php?topic=16799) (Linux, OS-X) or MLV Producer (http://magiclantern.fm/forum/index.php?topic=15271) (Windows). I have also had success feeding the virtual DNG image sequence into Adobe Media Encoder and Apple Compressor. Finally, many people are using DaVinci Resolve not only for creating quick ProRes files for editing but also for final color grading.
Hi, I'm considering putting ML on my Canon M, the main two features I currently want are Analog Gain, and Headphone monitoring through the AV port. I would like to check first if those features are available for the M, because on one page somewhere on the site I read that the ML Audio features are not available for cameras after the 600D, and I think the M is after the 600D.
Can you confirm if those two features (and the Audio features in general) are available on the Canon M?
Thanks.
Quote from: holmes200 on April 25, 2016, 02:19:15 AM
Hi, I'm considering putting ML on my Canon M, the main two features I currently want are Analog Gain, and Headphone monitoring through the AV port. I would like to check first if those features are available for the M, because on one page somewhere on the site I read that the ML Audio features are not available for cameras after the 600D, and I think the M is after the 600D.
Can you confirm if those two features (and the Audio features in general) are available on the Canon M?
Thanks.
Not available, see here: http://builds.magiclantern.fm/#/features
Just thought this one might be interesting for EOS M users:
Quote from: a1ex on April 29, 2016, 08:29:56 AM
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
Really loving raw on the M. Looks like 16! I'm on a Mac and I'm using pink dot remover and morse keeper to output prores. Looks nice and I'm using the Alexa log-c profile. 2 things... It's kinda noisey and it's a bit hard to focus even with the magic focus box.. Ideas?
Not morse keeper... Autocorrect. Mlraw viewer.
Quote from: Teamsleepkid on May 01, 2016, 02:05:54 AM
I'm using the Alexa log-c profile.
Where did you get the Alexa profile?
Log c is built right into mlrawviewer. You can get log c to rec 709 lut from arri website. Haven't really got it looking right yet though still testing.
So just thought I'd ask for some help: I posted some issues I was having with a previous nightly build (unfortunately don't know which one) here http://www.magiclantern.fm/forum/index.php?topic=17187.msg166553#msg166553 (http://www.magiclantern.fm/forum/index.php?topic=17187.msg166553#msg166553), however, I received little feedback. I just updated to the most recent nightly build, and my camera won't turn on now. The green light blinks, and that's it, with or without the memory card. What does this mean and is there anything I can do about this?
If I remove both the memory card and the battery and keep the memory card out after putting the battery back in, the camera will at least turn on, and otherwise seemingly behave normally.
I noticed something strange right before I formatted the card in the camera: I couldn't select the "light formatting" option by pressing the "info" button, which parallels another problem I reported having in my other thread (that I could no longer disable the ML overlays by pressing the "info" button).
Hey Guys,
Im using an OLD version because, well, it doesnt seem to exhibit the shutter bug. (oct 8,2014)
However, I dont use much of the ML features, mainly its just to turn off that damn'ed touch shutter function. I do this by turning off global draw, and basically left with the std canon SS and A numbers, and exposure dial. I like this since it draws a box around which one your adjusting in Aperture. The ML version doesnt so its a crap shoot, and quite slow to update.
However, the one problem with this is that the numbers only appear while the shutter button is held. :/
Is there another way to accomplish this? I turned off most of the ML features, and auto hid is disabled but I cant find a good way to get the SS/A/Comp to show all the time like it normally does.
Hi all, I'm new here and very interested. Can I use the ML for Eos M also on the M2? Is there any solution for the shutter problem? Thanks!
No, it does not work on EOS-M2.
And no, there is not a known way to solve the shuttter bug. But there are ways to minimize it, mainly using some SD card brands and models that usually do not experience the bug.
Both questions have been already asked and answered many times in this thread. So please, read the thread from the beginning before posting.
hey guys
im using ML whit eos M.... i have a problem, my camera gets very hot, even when I turn it off,
What should I do???
plz help
Is anyone else getting the camera starting all by it self when hanging from your neck?
I use the boxed strap either straight down on my belly or on my side, and it happens all the time eating the small battery away. ;(
Tried to repro this and handle it, pressing the buttons, to no avail.
Also, while you could get it in PictureView mode (my first suspect) by long pressing the PLAY button, I DON'T find it in THAT mode but rather in Normal picture shooting mode or ML menu.
Quote from: Licaon_Kter on May 22, 2016, 06:07:14 PM
Is anyone else getting the camera starting all by it self when hanging from your neck?
I had that happen a few times using the stock Canon neck strap. Once it even turned on the touch shutter release option (which I never use) so I ended up with a bunch of oddly frames stills. Not sure how it turns on but I haven't been able to reproduce the problem. I've gotten used to powering down the camera in order to save the battery so it isn't an issue for me.
Quote from: dfort on May 22, 2016, 08:41:17 PMI'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 -- Does this happen with latest nightly or any build?
I'll try to reproduce on my end but not sure where to start?
Haven't seen anything like this on my end on top of my head.
Had this like forever, not sure if it's ML related though.
Hi, I'm having issues with Advanced bracketing.
I set it up for 3 x 2ev, +++ , Exposure, no delay, no iso shift.
The results are chaotic.
Test:
Drive mode set to single:
2 photos, 0, +2ev, exposure left untouched
4 photos, 0, 0, +2ev, +4ev, exposure changed to 0+2ev
4 photos, 0, 0, +2ev, +4ev, exposure changed to 0+2ev
2 photos, 0, +2ev, exposure left untouched
4 photos, 0, 0, +2ev, +4ev, exposure changed to 0+2ev
At this moment I remembered I should use the latest nightly :-
Switched to Nightly.2016May16
Getting this results:
2 photos, 0, +2ev
3 photos, 0, 0, +2ev
2 photos, 0, +4ev
3 photos, 0, 0, +6ev
Everything is set to default settings.
4 photos, 0, +2ev, 0, +4ev
Such behavior makes the ML bracketing useless for me.
Shoot preferences: pics at once set to 3
Using the Audio remoteShot, only 2 pics are taken.
Weird. I set it up to 4 pics at once, it takes 3.
Testing some more, and it does 2-3 pics.
Inconsistent.
Seems to be related to shutter speeds.
Set it at 5 pics per shot, so far it does 3, but remains to be seen if it will actually be reliable.
So I just uninstalled ml from my eosm, and now it's continuing to produce a similar issue as when I had ml installed:
when I try to take a photo, it simply won't. The overlays flash off for a second, and the camera doesn't take a picture.
It did the same thing after I had enabled, and then disabled silent picture mode, so I'm somewhat confused.
Can somebody help me out with some information? What happened? Is there anything that can be done?
The camera still works with ML running and with silent picture enabled, but has it permanently affected the camera?
Sounds like you haven't uninstalled ML from the cam (= removed cam's bootflag). Run installation once again and wait for timeout. Reboot cam.
Retry and report.
That is exactly what I did. I didn't know how else to uninstall it, so I let the automatic timed uninstall run, after which I noticed these issues. I have since reinstalled ML and confirmed twice that I can't take photos without full res silent pictures enabled. Without silent picture enabled, it won't do anything except something that seems to resemble the EOSM shutter bug (so I'm told) however, I have not yet experienced an actually locked shutter. Without silent picture enabled, all that happens when I try to take a photo is that the screen overlays (M mode, shutter, expo., etc.) disappear, then reappear. Thus far (three times including before uninstall and reinstall) it has consistently proved the case that I can work around the issue by enabling silent picture, but it has to be set to full resolution, otherwise a text box appears that says "preparing..." in place of taking a photo.
hey guys
im using ML whit eos M.... i have a problem, my camera gets very hot, even when I turn it off,
What should I do???
some body help me, if i using ml my cameraو it can break??????
What ML build?
What do you do? Pics? H.264 video? RAW video?
using the last version,
16.5.2016
It is hot, even when turned off :-[
It does get hot while used, but it should not be hot while off though.
Whomever solved the ML meny exiting thingie, much appreciated. The last build is so friggin nice. :D
sorry guys, If this a repeat question from other.
Is EOS M10 capable of shooting with ML?
According to CHDK project camera's code base is Canon's P&S line.
As a1ex pointed out it might not be impossible to implement ML but it's about as difficult to port ML to Nikon DSLRs.
-> No dev is working on it and you better put your hopes in CHDK.
https://chdk.setepontos.com/index.php?topic=12757.0
how do i install the bin file on the sd card for the m10?
You don't. See message above yours.
Hi
Problem first image perfect (B&W)but if I do a another screen from info button I get coloured background (light blue) not B&W.
Tried reformating , reinstalling ML, different card but no change!
Can you please tell me what Im doing wrong?
Opening in Adobe cs6
Thanks
(http://i64.tinypic.com/2a6uhax.jpg)
(http://i67.tinypic.com/2hywhg4.jpg)
any guidance?
Hello guys, I just installed ML to my Eos M and there is no audio metering and no audio menu in ML. Audio without ML works fine, but not with ML.
Could you help me? Thanks.
What ML build date?
Hi
magiclantern-Nightly.2016Jun13.EOSM202.zip
Built on: 2016-06-12 23:08:10 +0100
Changeset: 90fe6de
Many thanks
Reset ML settings to default.
Reset Canon settings to default.
Retry.
@Licaon_Kter: are you able to get correct behavior on your EOS M?
On-topic: the palette registers are write-only, so if you are able to get the palette values, be my guest ;)
Quote from: a1ex on July 08, 2016, 07:10:09 PM
@Licaon_Kter: are you able to get correct behavior on your EOS M?
Not sure what the problem is though.
S/he make a screenshot of ML or what?
Hi from he (Michael)
Reset camera to defaults
Formatted card and reinstalled ML
Same results PPM file 1 good other blue
(http://i64.tinypic.com/9unk0g.jpg)
(http://i65.tinypic.com/oaoqzc.jpg)
Camera and ML working fine except screen print. Loaded PPM files to Adobe CS6 to convert to jpeg
Thanks for your time
I tried reproducing this and it turns out that the colors are wrong when doing a screen capture of the Canon INFO screen. All of the other screen captures I tried turned out fine.
(https://c8.staticflickr.com/9/8736/28202912015_ef659f9433_z.jpg)
Yes, I can confirm too. Strange.
Thanks for replies, at least I know its not just my camera!
Quote from: Licaon_Kter on July 10, 2016, 04:09:07 AM
Yes, I can confirm too. Strange.
Quote from: mapline on July 10, 2016, 01:50:02 PM
Thanks for replies, at least I know its not just my camera!
a1ex already gave you the answer to what is going on, it's seems maybe the answer passed over your heads:
Quote from: a1ex on July 08, 2016, 07:10:09 PM
the palette registers are write-only, so if you are able to get the palette values, be my guest ;)
Translation: we don't know what the color values (https://en.wikipedia.org/wiki/Indexed_color) in the bitmap vram (overlay screen buffer) are supposed to mean.
Canon firmware sets up the color palette (https://en.wikipedia.org/wiki/Palette_(computing)) for it's graphics, and we can't read the values directly from the display registers that control the palette, they are write-only (figuring out the current color palette would require reverse engineering the Canon code that setups the color palette and patching it in a way that allows us to keep track of the palette; a1ex says that if you are able to do that then "be my guest", implying that it would be a non-trivial and time consuming task; I suppose all the recent qemu (http://www.magiclantern.fm/forum/index.php?topic=2864.msg168603#msg168603) advancements booting the Canon GUI would be a great help to this end).
Quote from: dfort on July 10, 2016, 01:13:12 AM
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.
Screenshots of Canon graphics on other cameras look incorrect too, but not quite as crazy.
Thanks for the further explanation which I can understand and makes sense.
The latest version
If using the left button to lock focus
Then shutter metering, patterned after the move
Click the lock will have metering and click, no metering lock
Whether used to weigh the formula, or spot metering, the situation is the same
Is there any place can be set?
In Canon menu -> Key with four squares -> Custom functions (Fn.p) -> Fn.pIV AE lock -> did you use option 1 or 3? Test them both.
Option 2
To use the left button to lock focus
Options 1 & 3
Not lock the focus
Then shutter metering
Umm, it's not working like this here, but:
* 1 -> lock only focus on * (star) press (or left button how you've said), it will meter and take the picture on button press.
* 3 -> lock both focus and metering on star press, it will just take the picture (unchanged) on button press.
Both 0 and 2 don't do anything on * (star) press, at least on my EOS M.
Hi
Use
* 1 -> locks only focus by * button.
Pressing half shutter button ( and hold) will meter and toggles AE lock with * showing on left next to lens info when locked.
Release half press again releases lock * then meters, press again will meter and lock again with * on half press.
Take the picture on continue to full button press.
At least this is on my camers
Hi - I am not able to turn off the LCD of my EOS M when using the intervalometer on ML. This could easily be user error, can someone walk me through the steps to turn off LCD.
My current settings:
Powersave in LiveView
Enable power saving -> on STBY + REC
Use Shortcut key -> INFO
Turn off LCD -> after 20 seconds
This does nothing in my case, just downloaded most recent nightly build available.
Am I missing something? Any settings I need to change?
Thanks.
What interval?
Works fine here for both normal and silent pics, with 10s and Canon picture review of 2sec.
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?
Use the magnifying glass button to get into 5x zoom mode then adjust the image size with the ML settings. Going way up in size will limit recording time to about a second or so. A crash could also wipe out the card so good luck!
Sent from my iPad using Tapatalk
Quote from: Teamsleepkid on August 10, 2016, 11:02:38 PM
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?
Here's a better explanation.
Turn on the raw video (MLV preferred) module. Now change your display using the INFO button in order to access the magnifying button. On the EOSM it is only on the touch screen and is located on the lower right side.
(https://c3.staticflickr.com/9/8791/28648227770_d5b4efa8f2_z.jpg)
Tap the magnifying glass icon until you get into 5x zoom mode. Now when you go back to the raw settings you can set the resolution to a maximum of 2496x1074.
(https://c7.staticflickr.com/9/8674/28901837006_36f2f8b687_z.jpg)
Note that at this resolution the write speed needed is 134.0 MB/s and the EOSM tops out at about 21 MB/s but I just tried it and the camera can record 1 second, give or take a couple frames. That's all that fits in the buffer at that resolution. Not very practical but it is doable.
Besides the short recording times you'll also have to deal with figuring out how to accurately frame the shot because there are no crop marks to show where the image cuts off.
I am trying unsuccesfully to use PowerSave on my EOS M using the intervalometer in 5 second intervals, I have image review turned off in the Canon menu. I would like to turn the LCD off during record but am unable to. I have the option turned on in the Magic Lantern menu but my LCD stays active the whole time the camera is shooting.
Anything else I can try?
Do I need to actually turn image review on??
Thanks!
I asked this somewhere else and no, you can't.
Post #701 and #702 here: http://www.magiclantern.fm/forum/index.php?topic=12523.msg145189#msg145189
@davebreal: the 5-second interval is a bit too small: ML powersave kicks in after the picture is fully taken and nearly processed (ML is a bit conservative here, sometimes waiting more than necessary, in order to prevent camera-specific quirks). With a 10-second interval, it works just fine on a 700D, for example.
For your case, I recommend enabling image review, in order to prevent the camera from going back to LiveView. The biggest power hog is not the display - it's the sensor in LiveView. For the display, just set the brightness to minimum.
To turn the display off, you can write a short Lua script, but I doubt it will make any real difference.
@Licaon_Kter: you asked about something else.
thank you dfort. i guess i thought since it was windowing the sensor it would be lower bitrate. 100MB per second aint gonna work lol.
I found bug. I was on crete and it was very warm in there. I found out that if cam temperature rises over 45 celsius or something like that, camera temperature meter shows -60 Celsius. When I am home, I can show screen shots. I am using i think latest build.
Hi there, just installed the latest version of ML successfully on my EOS M. Use it with a non-AF Nikkor f 2,8/28mm lens. Works just fine. The only thing puzzling me is the temperature. Camera gets warm in a hurry. Shows 41 C just after a few shots. Then "-60 Celsius". Is there a danger to the camera's electronics?
Interesting, I checked it out and saw the temperature go from 41 to -60.
Opened a bug report on this:
https://bitbucket.org/hudson/magic-lantern/issues/2596/temp-goes-from-41-c-to-60-c
Hi all!
Thanks for all the work on ML, I love it so far! I've been reading on HDMI out. I don't have a way to record HDMI and am considering buying ablackmagic decklink mini recorder to do so. So, how does the quality of HDMI out stack up to regular avchd at 1080p30? I know it has black bars on sides, but that could be livable for me if quality otherwise is good. Also, my TV says the HDMI is 1080i, but I don't know if that means 1080i60 or 1080i30 or something else? Thanks so much, and sorry if I somehow missed that info!
Magic Lantern can turn off the overlays on the EOSM so it outputs a clean signal from the HDMI output.
http://wiki.magiclantern.fm/userguide#clear_overlays
The black bars on the side are because it doesn't output a 1920x1080 signal, most cameras don't. The exception being the 5D3. However, there are users who are using external recorders and are reporting good results. Just a little blowup in post is all that's needed to fill the frame. The EOSM signal should be about the same as the DSLR's so it should be fine. Note that the camera screen will go blank when going out HDMI. Again, the 5D3 is the only Magic Lantern enabled camera that I know of that can mirror the image in the Live View when connected to an external monitor.
Note that the picture style affects the output so if you are serious about this consider using a log picture style like CineStyle (http://www.technicolor.com/en/solutions-services/cinestyle), EOSHD C-LOG (http://www.eoshd.com/2016/09/now-available-eoshd-picture-profiles-brings-c-log-canon-dslrs-including-1d-x-mark-ii-5d-mark-iv/) or one of the reverse engineered CineStyle (http://magiclantern.fm/forum/index.php?topic=16299) picture styles.
Thanks so much for the reply! I saw how to turn off displays, which got me excited! Thanks for the tips!!
This is a bit random, but would it be difficult to put all the black bars on the left or right? Maybe an option for image a) center, b) left, c) right? Normally I could just do it in post, but I'm trying to do some things live with the stream and don't think I can easily move the image.
Thanks!
Quote from: jgrauman on September 05, 2016, 05:39:37 PM
...would it be difficult to put all the black bars on the left or right?
That sounds hard, certainly way beyond my abilities. You might post it in the feature requests topic.
Hi everyone!
I was testing a noncrop RAW video recording and got a problem.
(https://dl.dropboxusercontent.com/u/25628174/moire_artefact.png)
This is a screenshot 200% crop from MLVP (same situation in ML RAW Viewer and RAW2cDNG). I understand, that it's canon's downscale with skipping lines, plus ML squeezes image vertically, which leads to heavy moire and ladders. But where did these false blue and red pixels came from, looks like color moire? Is there a way to fix it while exporting RAW (without post in LR or PS)?
Shot RAW 1728x434 ISO 320 50mm f/2.8 (same thing at all ISO settings)
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.
P.P.S. Sorry for bad english
Hello all
Not sure if this is the right place to ask for eos-M help but If I'm wrong please move my post to appropriate subforum.
First off thanks to all of you who are taking the time to develop this fantastic software. Been using it on all my canon cameras and still learning.
Recently I bought a canon eos-M and have installed latest nightly on it but 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.
So my question is does eos-m support magic zoom or if some one has noticed issue with magic zoom in latest nightlies ?
Any input is appreciated.
Quote from: madz on September 05, 2016, 10:23:14 PM
I was testing a noncrop RAW video recording and got a problem.
That is a great test. It clearly illustrates the issues with mv720 mode. The EOSM is the only camera that doesn't do mv1080 mode. I've got a feature request (http://magiclantern.fm/forum/index.php?topic=16608) for it but it isn't an easy fix. Basically mv720 does a 3x5 line skip which creates lots of aliasing, mv1080 does a 3x3 pattern which also suffers from aliasing but not nearly as much. Note that there is also some aliasing in crop mode, there's no way to get around it because of the way the sensor was designed.
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.
Quote from: madz on September 05, 2016, 10:23:14 PM
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 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.
(https://c4.staticflickr.com/9/8083/29503000355_42450fdbe5_z.jpg)
Quote from: mlentuzijast on September 06, 2016, 11:04:34 AM
...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.
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?
Quote from: dfort on September 06, 2016, 07:49:12 PM
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?
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.
Quote from: dfort on September 06, 2016, 07:49:12 PMThe 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.
Yeah I read that few days ago, because that was the very first problem that popped up in testing RAW. Great job done, thank you!
BTW need to compare to 720 h264 for color moire... Because 1080 h264 didn't have that.
Quote from: dfort on September 06, 2016, 07:49:12 PMWhat 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.
I did some quick search for C-mount lens on ebay and Aliexpress, but most of them are noname 25mm+ (160mm equivalent in crop mode). And I need something in 35-80mm eq. range. Also looked for vintage USSR fisheyes, but they are very rare or not fast enough.
Looks like I'll have continue to shoot in flat h264 :(
P.S. did compare test
(https://dl.dropboxusercontent.com/u/25628174/moire_test.png)
in fact I can see red and blue cast on 720 h264 at the same place like in RAW, but codec's blur hides it (plus flat cinestyle profile) and it becomes not so noticeable.
P.P.S. yeah... mv1080 would solve lot of issues...
Just one more thought:
I read somewhere that mv1080 mode turns on with beginning h264 recording. <stupid idea>CPU probably won't handle it, but still, what if we set lowest h264 bitrate possible (CBR 0.1x or VBR Qscale 16, may be something even lower is possible) and write both h264 + RAW? (we can also grab audio track from h264)</stupid idea>
@madz
Wow, great tests.
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.
You should be able to find C-mount lenses much wider than 25mm. In my lens stash I've got a Rainbow H6x8 II 8 48mm F1.0 TV Zoom Lens, Ricoh 8.5mm f/1.5 (https://www.bhphotovideo.com/c/product/979785-REG/ricoh_c30811kp_c_mount_8_5mm_m_series.html) and a Ricoh 4.8mm f/1.8 (https://www.bhphotovideo.com/c/product/979784-REG/ricoh_c30405kp_c_mount_4_8mm_m_series.html). The 8-48 F1.0 zoom you'll have to search for but the others are still in production. These aren't great lenses but ok if you're going for a vintage Super8 movie look.
Keep up the good work. You're helping elevate the EOSM to the next level.
@Licaon_Kter, any thoughts on the Magic Zoom issue @mlentuzijast is reporting?
BTW--I'll be offline for about a month so excuse my slow response time.
Magic Zoom is not something that I use, not sure if because it does not work as well or anything else, although I do like do play with my OM Zuiko glass, I just use the zebras.
I'll take a look asap.
@dfort
Quote from: dfort on September 07, 2016, 03:56:21 PM
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.
h264 1080p @ 0.1x bitrate takes about half megabyte per second + PCM stereo 48/16 audio up to 0.2MB. So it's less than 2% from EOS-M SD module write speed (I have card with bit overkill). I'm fine with that, just hope that CPU can handle that.
Do you know if fixing mv1080 on EOS-M is in the plans for some near future or should I save the money for other camera like 650D for example?
Yes mv1080!! please please. Great ideas!
Hello everybody.
Please excuse me in advance if this is not the correct place for this question.
I am looking to modify the EOS M3 functionality, specifically the AEB (auto exposure bracking), with different variables. Currently it does e +/- 2 ev range. I've seen that other (higher class) Canon cameras can go up to +/- 8 ev, which is a much larger scope. Can this sort of upgrade/modification be done ?
Thank you in advance!
I could be wrong but I don't think there's anything going on with the M3. Aparently it runs on the powershot firmware. There's CHDK they work on powershot stuff. Look that up.
Quote from: Teamsleepkid on September 20, 2016, 06:36:35 AM
I could be wrong but I don't think there's anything going on with the M3...
Well maybe if an EOS-M3 user is willing to help out?
http://magiclantern.fm/forum/index.php?topic=14990.msg169808#msg169808
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.
Quote from: Shutterbutton on October 02, 2016, 05:38:43 PM
If you record in h.264 with FPS override your audio will be disabled only if you have a microphone plugged in.
Weird--hadn't had a chance to check this out yet. I thought audio recording was disabled with FPS override turned on. Does the audio recorded with the camera's internal mic stay in sync?
Yes, the audio is synced without a mic (I was shocked about that).
Hi, I want to set a minimum shutter speed on my Canon M when in A mode. Since you can't do it in the default menus, I was hoping ML would let me set it, it's a very useful feature. After reading around, it seems that it's not possible in the stable v2.3 build, but it used to be in a module called Auto ISO, which is no longer developed and has been pulled from the official build. Am I understanding it right? Is there any way to get this feature? Is it in the nightly build? Do I have to enable that module somehow? The modules feature doesn't seem to be very well documented, so I don't really understand them. Thanks for your help. I'd like to have this feature available on my M.
@biggles: Do not use that 2.3 version, it's years behind. Get the Nightly.
Ok, does it have that feature in the nightly that I want?
Control shutter speed while in full auto mode? I don't think so.
Sent from my iPhone using Tapatalk
No, set a minimum shutter speed that the camera won't go slower than, to be used in Av mode.
Not in Av mode. But you can do that in Auto ETTR module, using M mode.
ETTR exposure calculation is slower than Canon autoexposure, but much more precise.
Quote from: Shutterbutton on October 02, 2016, 05:38:43 PM
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.
I finally got around to checking this out and I'm not getting any audio on the H.264 file when FPS override is enabled either with the internal camera mic or an external mic. It doesn't seem to matter what fps setting is used, even when adjusted to the same fps speed as the Canon menu (no override).
Is there a way to set different picture styles for movie and picture mode? On 600D that worked. If i remember right even a different global drawings setup was possible. That would be so great, cause i don't want to shoot flat pictures;)
You are not shooting RAW where styles don't apply?
Quote from: Licaon_Kter on October 12, 2016, 02:42:56 AM
You are not shooting RAW where styles don't apply?
When using Canon Digital Professional Pro app picture styles do get applied to CR2 files. You can also switch picture styles with that program--with raw files only of course.
I suppose it can also be an issue if you want to shoot H.264 video in a flat picture style then switch to JPEG stills with a creative look picture style for color grading reference.
Though I don't know if it is possible to automatically switch picture styles when changing between movie and photo mode. However, when switching to full automatic mode it changes into an (auto) picture style no matter what picture style you have selected.
Quote from: madz
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 change my mind about RAW in crop mode, I don't like it at all. The first impression was good, but after some more tests... yeah it's 1:1 and no lines skipping, but it becomes soooo soft, even with very sharp lenses and noise grain also now 1:1 :)
So, is there any chance to get mv1080 in some near future? Or is there somewhere an information about that, just to know if it's in the plans or not? Anyone?
Hi I am trying to work out if I can use an EOS M in a wildlife camera trap. I have the latest ML firmware installed. I have the audio release on and a PIR sensor connected to the mic port using a stereo cable. I have been using a remote control car battery pack so that I can leave the camera switched on as it lasts much longer than the normal battery. I have Canon firmware 2.02 installed on the camera. What I have found is this:
If under power saving mode in the camera main menu I have "camera auto off" disabled and the LCD auto set to greater the 2 mins (2 mins is the interval setting on the PIR) the camera and PIR work perfectly. i.e. the camera is on and the pulse from the PIR fires the camera.
However once the LCD powers down the PIR does not trigger the camera even though it has sent a pulse to the camera and the camera green light is still on. Looking at the Power saving menu the longest I can have the LCD on for is 30 mins. Therefore as it stands if the camera is not triggered every 30 mins it will power down the LCD and for some reason the PIR will not trigger the camera. Any advise would be greatly appreciated.
Ok so I have done some tests with a remote cable release on the EOS M and the audio remote shoot enabled to rule out it being the signal from the PIR sensor I want to use with the camera. In a nutshell if the EOS M is on and the LCD is on the remote cable trigger works fine firing the camera. If the LCD switches off, even with the camera still on the cable release does not fire the camera. Any ideas or help would be appreciated. The camera limited the LCD to being on for a maximum of 30 mins according to the camera menu. I am at the point of giving up and sticking with a DSLR for camera traps / trail cameras which is a real shame.
So you need a way to keep the LCD active? What if you switch to the ML menu? There's code that keeps refreshing the display. Can't test it right now but it is worth a try.
Sent from my iPhone using Tapatalk
Another idea is to write a lua script. Check on the scripting section. Someone could probably help you with that.
Sent from my iPhone using Tapatalk
Quote from: dfort on October 17, 2016, 07:36:55 PM
What if you switch to the ML menu?
Ok--just tried it and that idea doesn't work. Audio RemoteShot cannot fire the camera while in the ML menu.
I would think that what you really want is for the LCD to be off and have the camera triggered by audio, or some other means. I'm assuming you're using Audio RemoteShot because the M doesn't have any way to use a cable release? You can use an infrared remote but it probably isn't suitable for your purposes because it has a 10sec. delay. I haven't checked if it will fire with the LCD off.
So the next step would be to write a lua script. This seems like an interesting problem that's perfectly suited for lua. Check out the lua scripting (http://www.magiclantern.fm/forum/index.php?topic=14828.0) topic.
I posted a question there to see if someone familiar with lua scripting can tell us if there's a solution for you.
http://www.magiclantern.fm/forum/index.php?topic=14828.msg173487#msg173487
Dfort your assumptions are correct basically I need the EOS M to stay on and allow the camera to be triggered using a cable release connected to the audio socket whilst the LCD is switched off.
@Flash_Gordon keep checking the lua scripting topic (http://www.magiclantern.fm/forum/index.php?topic=14828.msg173498#msg173498). It looks like there might be a way to get this working.
I've been thinking about your project and at first it seemed that the EOSM would be ideal for this application being so small and inexpensive compared to DSLR's. However, there may be a problem switching off the LCD because the EOSM must have LV on or it won't fire. Of course this means that it will be drawing a greater amount of current from the battery than a DSLR that can basically go into a sleep state while waiting for an event to wake the camera and fire the shutter. I just tried Audio RemoteShot on a 700D and it seems to work fine with the LCD off. Of course with a DSLR you've got the option of using a cable release to trigger the shutter.
Don't give up hope yet, there might be a way to get something working on the EOSM.
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/17017931@N06/30394580436
(https://www.flickr.com/photos/17017931@N06/30394580436)
@Flash_Gordon are you keeping up with that LUA topic? I'm getting really close to a solution for you:
http://www.magiclantern.fm/forum/index.php?topic=14828.msg173600#msg173600
PM me and I can wrap up a test build for you. In the meantime let's see what suggestions come up.
Hello Guys :)
I'm new here and have a question.
Is it possible to make a headphone jack for 700D with ML?
If it is, please explain for me how.
I'd be glad for your help.
Quote from: me.n.khof4sh on October 22, 2016, 09:29:38 PM
Is it possible to make a headphone jack for 700D with ML?
You posted this in the wrong topic. This is for the EOSM. The 700D topic is: http://www.magiclantern.fm/forum/index.php?topic=5951.0
Here's a list of features for each camera: https://builds.magiclantern.fm/features.html
Sorry, headphone monitoring for the 700D isn't on the list. That means that the developers haven't been able to get it working--yet.
Quote from: andresvina on October 19, 2016, 06:37:08 PM
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/17017931@N06/30394580436
(https://www.flickr.com/photos/17017931@N06/30394580436)
Could you provide more information? Things like what is the date of the build you're using, at what shutter speed does this occur, what are your settings? CR2 or DNG or ?? Have you tried uninstalling ML and seeing if this is still occurring? That might point to a hardware issue.
By the way you can display images from flickr by "sharing" using "BBCode" and posting only the
img tag. For example:
[img]https://c5.staticflickr.com/6/5827/30394580436_64f811d2e1_z.jpg[/img]Make sure you keep the image resolution less than 900x900 pixels as stated in the Magic Lantern Forum Rules (http://www.magiclantern.fm/forum/index.php?topic=934.msg1141#msg1141).
(https://c5.staticflickr.com/6/5827/30394580436_64f811d2e1_z.jpg)
@Flash_Gordon came up with an interesting idea turning the EOSM into a wildlife trap camera. I came up with a simple solution using a lua script that keeps the LCD active indefinitely but it requires a custom build from the lua_fix branch. It isn't ideal, a better solution would be to allow the LCD to power down and still be able to trigger the camera with Audio RemoteShot but that requires digging deep into the ML code and it might not even be possible.
I posted a package with the custom build and instructions on how to set it up if anyone wants to try it out.
https://bitbucket.org/daniel_fort/magic-lantern/downloads/EOSM_wildlife_trap_2016-10-23.zip
Hello all, about EOS M do you notice a poor battery life? It seems to me really poor (not even an hour of usage). Better with a compatibile battery, worse with the original Canon one.
Thanks to ML I noticed that CPU usage never decrease below 40%... is it normal? What's the idle cpu load for other cameras? Maybe the reason for poor battery life and what's using the CPU so much? (LV?)
60D: 57% in photo mode (30fps, global draw off).
Drops to 26% with FPS override at 10 FPS.
Quote from: a1ex on October 23, 2016, 06:23:17 PM
60D: 57% in photo mode (30fps, global draw off).
Drops to 26% with FPS override at 10 FPS.
Thank you a1ex! So it seems that CPU usage is related to LV...
EOS M with FPS override at 10 FPS has 20% cpu usage... good for battery... but the camera become unusable.
AF slows down proportionally to FPS. It's already slow without override... at 10 fps it takes 4-5 seconds to focus :o
In the 60D AF slows down?
Yes, it does.
Powersave idea: drop to 10 FPS after X seconds of idle time, switch back on half-shutter press (or on any key press).
Quote from: a1ex on October 23, 2016, 06:59:04 PM
Powersave idea: drop to 10 FPS after X seconds of idle time, switch back on half-shutter press (or on any key press).
Great idea. I just wrote some modifications to powersave.c, it works... but there is an annoying issue: with touch or keypress the camera returns instantaneously responsive, while with half shutter there is a little delay... little but noticeable... :-\
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
Can I install ML on the new M5 ? Looks a great combination for product photography (custom cropmark/ghost image + focus stack)
M5 and EOS M are playing different games. EOS M shares codebase with Canon DSLRs. M5 shares with Canon's Point-and-Shoot. It would be quite a big task to port. Look for CHDK port instead.
I meant the EOS M5, there is a difference ? ..
I meant EOS M5, too ...
I just realized that "movie crop mode" does not show up under Modified if I use it. Is it supposed to be this way or does it just happen with my M?
To appear in the Modified menu, an item must also have a CONFIG_INT entry (to be saved in ML config file). Otherwise it doesn't know which is the default state, so it can't tell whether it was modified or not.
You'll need to use a new variable (other than video_mode_crop, which is global and updated from Canon settings aka properties).
Fairly easy coding task, although it requires a little attention to details.
Wasn't this (crop mode) something that had an issue on EOS M? It got reset on restart or something.
Then, adding a config entry will solve that as well.
I believe that the problem was that if you turn on crop mode then switching to a non ML card, you get stuck in crop mode for video. Yep--just tried it. Put camera in crop mode, remove the card, restart the camera and it stays in crop mode.
Would it be possible to turn off crop mode on shutdown then turn it back to the desired state from the configuration file on start up? Of course this wouldn't help if the camera crashes.
Should work if you call movie_crop_hack_disable() from ml_shutdown.
Quote from: a1ex on November 27, 2016, 11:39:08 PM
Should work if you call movie_crop_hack_disable() from ml_shutdown.
Yes it does.
https://bitbucket.org/hudson/magic-lantern/pull-requests/776/disables-crop-mode-hack-when-turning/diff
Next we can take a look at the Modified menu thing.
So close. Just need to figure out how to read the config file and switch to the saved mode when restarting the camera. The movie_crop_hack_disable() from ml_shutdown trick works great when switching to non-ML cards but we should be able to restore Movie crop mode if that's what was saved in the config file.
(https://c1.staticflickr.com/6/5810/31186861352_0641b23c5b.jpg)
https://bitbucket.org/daniel_fort/magic-lantern/commits/bca4abfb0e8d9c63bfcf8fc244bb2db32fbb9c15
Just discovered that Canon released a firmware update for the EOSM on November 29.
QuoteFirmware 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.
Looks like the same update that the 100D, 650D, 700D, 70D and perhaps others got recently.
No big deal but porting a minor firmware update might be an interesting advanced beginner project. (Is that an oxymoron?)
hey so I went to uninstall ml and I did something wrong now I'm stuck when I try to turn it on the light just flashes green with a black screen but if I take out the sd card and battery and only put the battery back in it will start up any ideas ?
@cluna
The bootflags on your card and camera are still active. If you put in a card that doesn't have the bootflag set it should work fine. If you want to uninstall ML properly, put ML back on your card and run the install process (firmware update) again but wait 1 minute before restarting the camera. There is a countdown timer on the bottom of the install screen. That will remove the bootflags from both the camera and card.
Hi. Long used ML on different cameras. Very interested in the question. Is there a possibility of follow focus like other cameras. It's just the perfect camera for gimbal. And it would be nice to control the lens without an additional servo. Sorry for the quality of English.
Quote from: branex on December 20, 2016, 06:27:30 PM
Is there a possibility of follow focus like other cameras.
Yes, you need to turn on Movie Servo AF from the Canon movie menu. When it is disabled a shutter half-press will trigger the auto focus.
(https://c3.staticflickr.com/1/778/30926637674_b51b5dbcf6.jpg)
Thank you dfort. No. I need to continuously focus as SLR cameras canon. Full manual control of the servo. There's tracking focus(follow focus) is implemented with buttons up/down and left/right - tab in the ML menu "focus". And mirrorless the tab "focus" - only DOF.
(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
Quote from: Pharinen on December 21, 2016, 10:22:46 AM
(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
Because in movie mode, the lens aberration only correct the peripheral illumination, chromatic does not.
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.
Quote from: branex on December 21, 2016, 06:38:55 AM
Full manual control of the servo.
In that case, no.
https://builds.magiclantern.fm/features.html
However, there is a work in progress that might change that if someone can follow a1ex's instructions better than I:
https://bitbucket.org/hudson/magic-lantern/pull-requests/748/focus-backend-updates-precise-focus/diff
Just out of curiosity, how do you plan to follow focus manually on a gimbal without some sort of a remote control? 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.
Eosm not expensive. I would have just soldered the contacts in it. And would be brought to the place of management. (Did it with a 550d and 5d2). There would be the possibility to smoothly adjust the area of focus. Besides camera size and weight allow you for brachial rig to make a great stabilizer. Most importantly the ability to shoot in Raw on interlaced enlargement up to 1700*600(35 MB/sec). And the comb can be removed by using an anamorphic lens(it would increase the amount of information in the horizon, and it is not necessary to approximate ~of 1.66 x in the vertical(let me use the 1.33x Slr magic or equivalents). The output is a high dynamic range, color and high resolution(with good quantization and detail, with smart stretch to 4k).
Quote from: dfort on December 21, 2016, 07:03:49 PM
... 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.
Agreed -- In fact that's exactly what I'm aiming for (or at least trying) to make the EOSM this little toy that can bode well with the Ronin-MX espcially while in AF for certain situations!
Quote from: pokepe on December 21, 2016, 05:30:49 PM
Because in movie mode, the lens aberration only correct the peripheral illumination, chromatic does not.
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.
Oh I see... I knew I didn't think of something. I bet they even mention about that in Canon's manual. :-[
Anyone know who Eosm Developer is on Bitbucket? I'd like to buy him a beer!
https://bitbucket.org/hudson/magic-lantern/pull-requests/792/update-to-eosm-firmware-revision-203/diff
Any reason to upgrade to 2.0.3? Saw that only 1 lens compatibility was added.
I hope someone can help.
I haven't used my EOSM for a while, but thought I would try my Auto bracketing script.
I am using a Sigma 10-20mm AF lens on the Canon lens mount.
I'm using the latest EOSM nightly.
My script loads OK but when it should be driving the lens, the on/off light rapidly flashes, but with no lens move.
The script works ok on my 5D3.
I thought someone one told me that the EOSM should drive a normal, ie non-EOSM, lens, ie via the Canon mount.
Any feedback welcome.
Cheers
Garry
@garry23 - You might need one of the lua fix versions that hasn't made it into the nightly builds yet. The EOSM wildlife trap (https://bitbucket.org/daniel_fort/magic-lantern/downloads/EOSM_wildlife_trap_2016-10-23.zip) build that is in my download page might work for you. If not I can try to see if there are newer lua fixes. Oh and yes, I got the lua test script on the EOSM to drive EF lenses via the Canon adapter but it doesn't seem to work with EF-M lenses.
Quote from: Licaon_Kter on January 02, 2017, 06:31:31 PM
Any reason to upgrade to 2.0.3? Saw that only 1 lens compatibility was added.
Is there any reason to climb a mountain other that because it is there? I think it was cool that someone jumped in and made a firmware update port as a first project. Maybe solving the shutter-bug and getting mv1080 raw video mode working on the EOSM will be next? Maybe I'm just dreaming?
@dfort
Many thanks for the wildlife version. This version drives the lens OK :), but my script that works OK on the 5D3 does erratic movements now. I need to look at the script and understand why.
I'll report progress.
Cheers
Garry
@dfort
I tried your EOSM build on this simple test script, which only move the lens one way until a condition is meet.
All it does is flash the on/off light, ie no lens move.
Any ideas ;)
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
@dfort
Even tried this 'improved' test script, as I thought placing the move in the keypress event handler might cause an issue. But still no luc.
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
Quote from: dfort on January 03, 2017, 04:31:13 AM
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.
So please put me out of my misery ;)
Quote from: garry23 on January 03, 2017, 01:04:44 PM
OK I admit I'm stupid, have a lot going on in my life, and am still learning.
My feelings exactly. If your script works on the 5D3 it
should work on the EOSM. Do you want to try it on a test build of the non-cpu manual lens lua (http://www.magiclantern.fm/forum/index.php?topic=18083.0) branch?
Quote from: Licaon_Kter on January 03, 2017, 12:42:13 PM
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.
Quote from: dfort on January 03, 2017, 06:30:29 PM
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? :)
@dfort
I may do, however, I'm tempted to 'just' keep the EOSM for shutter and shutterless timelapse, and do the heavy lifting, i.e. all my scripts, on the 5D3 and IR-50D.
I must say I find the EOSM very fiddly to use.
Cheers
Garry
Quote from: Licaon_Kter on January 03, 2017, 06:35:43 PM
...was the joke actually the answer...
Pretty much. That firmware update was done for several cameras but it doesn't give most users a good reason to install it.
QuoteCorrects 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.
Though this is an opportunity for users who want to get some porting practice by taking on a relatively simple firmware update to begin with.
BTW--one of the first things I tested was the shutter-bug and it is still there. Rats!
@garry23 -- I encountered issues building the manual_lens_info branch. Several modules are not compiling. Need to look into it further before I can get you a test build.
[EDIT] Oh yeah--the problem is documented so it looks like that branch is currently broken.
http://www.magiclantern.fm/forum/index.php?topic=18083.msg176957#msg176957
Quote from: dfort on January 03, 2017, 08:14:16 PM
Pretty much. That firmware update was done for several cameras but it doesn't give most users a good reason to install it.
BTW--one of the first things I tested was the shutter-bug and it is still there. Rats!
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.
Too bad about the shutter-bug :(
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" ) ?
Quote from: Licaon_Kter on January 03, 2017, 09:38:58 PM
...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" ) ?
That
should do the trick as it currently does with others afaik inlcluding 5D3, 7D, etc...
5D3 with firmware 1.3.3/1.3.4 does *not* allow in-cam downgrade to 1.1.3 or 1.2.3 ....
Either Walter is going off topic again or maybe he found a way to change an EOSM to a 5D3 with just a firmware upgrade.
I went through the 2.0.2 -> 2.0.3 -> 2.0.2 drill and there were no problems. Just make sure your battery has enough juice before you start.
[EDIT] That tip is for users who haven't done Canon firmware updates. Of course @Licaon_Kter knows about charging batteries--he's gone through many charge cycles getting the EOSM to this stage in ML development.
Quote from: dfort on January 04, 2017, 01:25:29 AM
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!!!
Test some things? Charge to 100%!
Come back after shooting outside? Charge to 100%!
The thing is, this camera has 3 stages: full-white (100% I hope?! when did I charge the battery exactly?), half-yellow (at 50%, right? 50% or 30%? please tell me!?!?) and empty-red (yeah, hey it turned on, let me try anot- oh fffs)
hi
how i can update ml on may cam
Backup and delete *.FIR, autoexec.bin, ML directory. Copy nightly build content to card.
Put new version on card, use!
thank u
Hi. Recently I "inherited" my dad's EOS M camera and I want to use it to some amature film projects. The reason why I wanted to keep it is because this hack and the RAW video, but i noticed that in the latest build ther's no option to shoot in RAW, only in 3xH.264. Is there any way for me to shoot in RAW, or just use the H.264? Also what lens and basic settings you guys recommend? (Have the kit lens and an ef adapter)
Hi. What's the highest available video resolution when shooting Raw and h264 on Eos M?
Quote from: j_szczygiel on January 12, 2017, 12:12:44 AM
Hi. What's the highest available video resolution when shooting Raw and h264 on Eos M?
H.264 is 1080p@30fps max, as Canon does
RAW it depends, do test
Quote from: matyineni on January 11, 2017, 12:36:37 PM
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?
Quote from: Licaon_Kter on January 12, 2017, 10:14:15 AM
H.264 is 1080p@30fps max, as Canon does
RAW it depends, do test
I'll be pleased if you can check that as the camera seems to be a perfect entry-level gear to me :) There are no strict informations like "resolution + codec + fps" and eventually recording time, crop (if applies) for EOS M in the "[ML] Canon EOS Features Comparison" chart. I guess it would be helpful to others too. That would be awesome if you can share some DNG and H.264 files in best quality.
Also, is there a significant DR improvement when shooting in H.264 with ML?
@j_szczygiel since you are a newcomer I'd advise you to read through this discussion and search the forum for other EOSM related posts. I too got this camera as an introduction to Magic Lantern and while the cost/size/performance ratio is impressive, it has some severe limitations though it has gotten significantly better since the camera was first ported.
Video shooters wanting raw will be disappointed that it will not shoot mv1080 like the other cameras--at least not yet (http://www.magiclantern.fm/forum/index.php?topic=16608.0).
Still photographers who want to use compact EF-M zoom lenses will swear at the still unresolved shutter-bug (https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug).
However, it is a fun little camera that is inexpensive enough to risk bricking for the experience of learning how to use Magic Lantern. In fact it already looks like a small brick.
Anyone feeling adventurous? @garry23 -- You asked for it! I put all the latest experimental stuff you could possibly want to play with into one build.
- Update to 2.0.3 firmware (https://bitbucket.org/hudson/magic-lantern/pull-requests/792/update-to-eosm-firmware-revision-203/diff)
- crop_rec module (http://www.magiclantern.fm/forum/index.php?topic=17021.0)
- 10bit 12bit raw video (http://www.magiclantern.fm/forum/index.php?topic=5601.0)
- MLV Lite (http://www.magiclantern.fm/forum/index.php?topic=16650.0)
- The latest lua updates (http://www.magiclantern.fm/forum/index.php?topic=14828.msg178317#msg178317)
- Manual Lens lua script (http://www.magiclantern.fm/forum/index.php?topic=18083.0)
- bulb_nd module (http://www.magiclantern.fm/forum/index.php?topic=12960.0)
- Simultaneous H.264 and raw recording to get into mv1080 video mode (http://www.magiclantern.fm/forum/index.php?topic=16608.msg177561#msg177561)
This started out with someone who just signed up on bitbucket and the first pull request was a complete firmware update from 2.0.2 to 2.0.3. I don't know who this person is but he/she did an excellent job. It works so well that as far as I can tell everything works as well as the current 2.0.2. In order to encourage EOSM users to give it a test drive I pimped it with all sorts of goodies and posted it on my bitbucket download area:
https://bitbucket.org/daniel_fort/magic-lantern/downloads
If you prefer rolling your own, the branch is in my repository:
https://bitbucket.org/daniel_fort/magic-lantern/branch/update-to-EOSM.203_experimental_branch
Some things are working great like crop_rec and 10bit/12bit. Other things are highly experimental like simultaneously recording H.264 and MLV. I got it working once with raw_rec (MLV Lite) but not with mlv_rec. I also defined RAW_DEBUG_TYPE which lets you select the raw type (for PREFERRED_RAW_TYPE) from the Debug menu if you want to experiment with that while testing out mv1080 video. In order to run the manual lens lua script the latest lua fix is included. Oh yeah and that bulb_nd module is something that keeps coming up in the forum. It is in the code base but not activated so let's activate it and try it out.
The download package has the ML folders inside of the zip package, sort of like a TurDunkin. That's because I also included the Canon firmware 202 and 203 files so you can go back and forth easily. You can actually copy both firmware updates to the same card--but don't mix it up with the ML-SETUP.FIR file because that won't work.
(https://c1.staticflickr.com/1/400/32124987402_ee399f6dae.jpg)
If you just want to take a peak of coming attractions, that's fine too. Going back to the previous firmware is easy. Just make sure you always do a firmware upgrade/downgrade with a freshly charged battery.
(https://c1.staticflickr.com/1/652/31463973423_fde938d038.jpg)
This is all experimental stuff so the chances of having something going terribly wrong is greater than with a nightly build. Though I've got 4 EOSM's and have done some crazy things to these cameras without incident.
If something starts going weird and you feel you discovered a bug do everyone a favor, reset your Canon settings and delete the ML configuration file and try to reproduce the issue before making a bug report. Learned that lesson the hard way with these experimental features!
A special note about the way crop_rec works on the EOSM. You'll need to use software that can handle the focus pixels for this format. The one that is currently working properly is Danne's cr2hdr.app (http://www.magiclantern.fm/forum/index.php?topic=15108.0) which already has a special focus pixel map file for this format. If you want to use MLVFS (http://www.magiclantern.fm/forum/index.php?topic=13152.0) you'll need to install the EOSM_crop_rec_mv720_combo_map_file (https://bitbucket.org/daniel_fort/ml-focus-pixels/src/22bc5a79967ce51668fa7e733a4bf67d1d8eb3a3/focus_pixel_map_files/fpm_archived/EOSM_crop_rec_mv720_combo_map_file/?at=default) in the MLVFS application. I'm not sure if MLVProducer (http://www.magiclantern.fm/forum/index.php?topic=15271.0) has the new map file but the developer, AWPStar, is usually quick to respond to user's requests.
Hell fuckin' YEAH and I'm definitely jumping onto this EOSM.203 wagon and THANKS so much for just being you, Dan!
Here's one for you -- "Don't just risk anything, take risk with everything!" and I usually go by that motto!
Quote from: dfort on January 13, 2017, 08:06:11 AM
...reset your Canon settings and delete the ML configuration file...
As in 'Clear all camera settings' or 'Clear all Custom Functions. (C.Fn)' or both?
Lovely stuff, Dan. Felt wonderful to upgrade to 203 and now after resetting Canon settings (did both 'Clear all camera settings' & 'Clear all Custom Functions. (C.Fn)' just to be safe) and yes I took note (photo from iPhone) of each settings so I can have them back the way I had them. I noticed some differentials in Canon's settings between 202 and 203. No big deal I guess.
Off I go installing ML with ease and restarted camera after loading required modules and ran few tests files (couldn't get MLV to work keep getting 'Threads failed to start')...
*edit* I remember @Danne mentioned that it may have something to do with while having MLV Sound enabled on so I turned that off and voila MLV works like normal.
*edit2* I also learned that if I disable raw_twk.mo then enable MLV Sound which allows for recording with audio even in 10-bit but then I would have to re-enable raw_twk.mo to get preview to work -- is there a workaround for this to get audio included or at least to work with raw_twk.mo or not yet?).
...with RAW and noticed a bug already when activating mlv_play.mo and is reproducible.
Here it is in order:
•Record RAW and then press play which would give you the black screen (not frozen tho) and shutter button gets you out of it.
•Then here comes the orange light next to the on/off switch constantly blinking indication something (tried turning off to no avail) so battery pull does the trick here.
•Turn camera back on and go ahead press 'Play' which then would finally preview files (even in 10-bit 8)) and haven't seen any corrupted footage as of yet.
Getting late out here and need some sleep but felt this was worth to note even tho it's minimal but will test more thoroughly tomorrow and the rest of this weekend.
Thanks again, Dan!
Here is another framegrab shot in mv1080(1728x972)10bit
Shot with "Simultaneous H.264 and raw recording to get into mv1080 video mode"
Shortened original MLV(two dng files)
https://bitbucket.org/Dannephoto/magic-lantern/downloads/mv1080eosm.MLV
Original dng(altered in acr)
https://bitbucket.org/Dannephoto/magic-lantern/downloads/mv1080eosm_000001.dng
Run it with latest mlv_dump like follows:
mlv_dump --black-fix=2047 --white-fix=15000 --cs2x2 --dng input.MLV
Downscaling isn,t justifying the output. Download original PNG here
https://bitbucket.org/Dannephoto/magic-lantern/downloads/mv1080eosm.png
mv1080(1728x972)10bit
(https://s24.postimg.org/mvvjqkkbp/mv1080eosm_000000.png)
mv1080(1728x972)10bit would be super awesome! How long recordings(in theory) could you expect in 24/25p? :)
The EOSM has very similar specifications to the 700D as far as image size and SD card write speed is concerned. On that camera I'm getting from 12 sec. (mlv_rec with mlv_snd on 48kHz) to 15 sec. (raw_rec) with 10bit at 23.98 fps.
Danne, what settings are you using? I got mv1080 working a couple of times but not consistently and certainly nothing as impressive as the results you are getting. Of course that cat of yours is also awesome but that's besides the point.
That experimental EOS.203 build I posted also has some code that isn't working on the EOSM yet, like the lossless compression for the silent module (http://www.magiclantern.fm/forum/index.php?topic=18443.0), just to see if that is causing issues with unsupported cameras. Some of this might be creating issues that have nothing to do with the 2.0.2 -> 2.0.3 firmware update so I added a plain vanilla build of the Update to EOSM firmware revision 2.0.3 (https://bitbucket.org/hudson/magic-lantern/pull-requests/792/update-to-eosm-firmware-revision-203/diff) pull request to my download page (https://bitbucket.org/daniel_fort/magic-lantern/downloads).
[MOD edit] Bitbucket link no longer working. Use Web Archive instead: https://web.archive.org/web/20200622002229/https://bitbucket.org/daniel_fort/magic-lantern/downloads/
[MOD edit end]
@DeafEyeJedi -- I was able to reproduce the 'Threads failed to start' issue you reported. Probably the main reason you would choose mlv_rec over raw_rec (MLV Lite) is in order to record sync sound and having to off mlv_snd is a rather big problem. However, I tracked it down to raw_twk. Try turning off that module. Yeah, I know you need it for in camera playback but it is still experimental.
By the way, this issue doesn't have anything to do with the 2.0.3 update, I was able to reproduce it on 2.0.2.
My cat is deeply involved in compiling right now ;).
Anyway. Settings used.
- raw_rec, highest resolution 10bit
- H.264 bitrate set to 0.1(I just leave it on and start stop raw_rec while it,s running)
Caveats:
- Frames comes out with bad white and black levels. Easily fixed with latest mlv_dump
- A lot of frames comes out corrupted and in choppy order
- chroma smooth is prone to crap out in blown highlights delivering green dots
- mlvfs could be a solution but it,s not possible to alter black and white levels to the dng files. Turns black.
Thanks for the tips, got it working--sort of. Lots of crazy frames but the good ones are very good.
Quote from: Danne on January 13, 2017, 09:26:16 PM
- Frames comes out with bad white and black levels. Easily fixed with latest mlv_dump
Is there a magic number for the EOSM? I used 2048 and that looked pretty much ok.
Cool, yes, the good ones looks great.
I run this command
mlv_dump --black-fix=2047 --white-fix=15000 --cs2x2 --dng input.MLV
Also added black/white level handling from mlv_dump menu inside cr2hdr.app.
Now how lift this from proof of concept to something fully working?
So for the EOSM shot in 10-bit -- the magic number for the black-fix should be set to 2047 (not 2048?) or was that a typo?
So far there has been 32 downloads of the EOSM.203 build and 52 downloads of the EOSM.203 experimental version and still no reports either here or on the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/792/update-to-eosm-firmware-revision-203/diff)?
Even if you find nothing unusual to report that's worth reporting. On bitbucket you can give it your stamp of approval to help move this forward.
Hey y'all.
First time poster, long time lurker.
Basically jumping to the point now, I recently made the jump into buying an EOS M with the intent of installing ML. To my surprise, the seller of the camera already updated the thing to 2.03. Now I have been reading about 2.03 builds and such but I guess I'm a bit slow to these things. Is there a way to install ML on 2.03 or are the experimental builds just ML pre-baked into the 2.03 update?
just pop Canon official 2.0.2 on the card and downgrade.
Or use the experimental 2.0.3 from @dfort https://bitbucket.org/daniel_fort/magic-lantern/downloads
Dear *,
I've got an EOS M with 2.02 Firmware and I wonder if the MagicLantern gives me Clean HDMI out (and do I have to record with / on the camera?) and 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?
Kindest regards
sws
@a1ex -- saw your request to run the stubs API test from the selftest module, from the latest lua_fix build for the 100D and was thinking that maybe this could also benefit the EOSM so I tried but it got stuck here and needed a battery pull to shut down:
(https://c1.staticflickr.com/1/508/32377828982_a59200fea3.jpg)
It got quite far and it looked like it was saving a 2GB file but the card had no log file.
Quote from: swschilke on January 24, 2017, 11:34:52 PM
MagicLantern gives me Clean HDMI out
Yes it does, just turn global draw off. However it isn't a 1920x1080 signal, it is slightly smaller so you'll need to resize it in post. Also these cameras put out 8bit 4:2:2 so take that into consideration too. Another issue is that the camera LCD goes blank when an HDMI cable is plugged in and there's a slight time lag on the output. Finally, no audio through the HDMI. Oh, and if you want to record in the camera at the same time my understanding is that the signal shrinks to SD.
Quote from: swschilke on January 24, 2017, 11:34:52 PM
(and do I have to record with / on the camera?)
What is your question?
Quote from: swschilke on January 24, 2017, 11:34:52 PM
no time barrier while recording (or capturing the hdmi out signal), i.e. the 30 minute max recording time.
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.
Quote from: swschilke on January 24, 2017, 11:34:52 PM
Does the latest build work nicely or any things I should better be aware of?
The shutter-bug (https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug)is a pain for still photographers and lack of mv1080 (http://www.magiclantern.fm/forum/index.php?topic=16608.0) sucks if you want to record raw video. Then there are these bug reports (https://bitbucket.org/hudson/magic-lantern/issues?status=new&status=open&q=eos%20m). Still, for the current price that these cameras go for we shouldn't complain too much.
Quote from: dfort on January 26, 2017, 07:42:27 AM
@a1ex -- saw your request to run the stubs API test from the selftest module, from the latest lua_fix
Not a bad idea, since you said it had problems on 2.0.3 as well. If it still locks up after the latest fix, you could try commenting out the troublesome test (stub_test_exmem or parts of it, maybe other tests if it still locks up somewhere else) until you narrow down the issue.
Commenting out stub_test_exmem on the latest lua_fix commit did it, though I should narrow it down to find out that's causing it to hang. Everything looked good until the end of the log:
[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
Latest commit might help with the last error; if not, the advice from the 100D thread applies here as well.
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.
That commit got through more tests, lots of UNCACHEABLE Fails but those might be the timer errors that can be ignored? It still gets stuck on stub_test_exmem and I'm still trying to narrow down where the problem is.
When talking about computers, cache (https://en.wikipedia.org/wiki/Cache_memory) usually refers to memory, not timers.
What's the status of the Debug -> Free Memory dialog box?
Free Memory -> 191K + 3406K
I put the latest couple of logs in the dropbox folder (https://www.dropbox.com/sh/m17imm8wqavd1q3/AADOhSg95KRemu6WGc9zRqgaa?dl=0).
[EDIT] Ran another test and checked the memory after the test finished. Don't know if this is significant:
Free Memory -> 185K + 3364K
Click it.
Oops, I was trying to figure out what was tripping up stub_test_exmem but couldn't figure it out.
Impossible to do a screenshot of this is it?
(https://c1.staticflickr.com/1/663/31698776284_6516ea4c75_z.jpg)
Another iPhone screenshot. This is after running the stubs test without stub_test_exmem:
(https://c1.staticflickr.com/1/409/31698936804_386e9d2f5c_z.jpg)
Indeed, looks like a bug. It works fine on the dm-spy branch on 500D, though...
That red scrollwheel also looks like a bug, and the duplicate menu warning is yet another bug.
If you wait for a few seconds, does it come up with valid numbers for all entries, instead of 0?
The red scrollwheel comes on after the screen refresh hack kicks in the first time. That was because the ML menus kept timing out.
After a while some information scrolls by in the console, too fast to read and it doesn't save any log file. Here's what it looks like after it finishes:
(https://c1.staticflickr.com/1/758/32163793010_eaf40d4b4f_z.jpg)
- Same for the red wheel on my cams after the ML menu timeout PR was merged
- Same Duplicate menu: Free Memory (2) with latest lua fix experimental build on 100D
- same "stuck" memory overview with all zeros as seen on above screenshot with buld stated above
Quote from: cavcavictor on January 26, 2017, 09:14:10 PM
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.
Quote from: dfort on January 27, 2017, 05:00:54 PM
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.
That's nice. I just ordered it. Can't wait to get it!
Thank you! :)
@dfort Thank you for your answers
QuoteThe 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.
Would it be possible to enable MagicLantern to stop the camera from getting into power saving?
Which Canon Camera (preferable cheap / old :P) would be best suited as a camera device for recording with an HDMI capture device (Atomos, HDMI Capture cards with USB, ...)? or do you have other recommendations (I have a GH2 as well).
Thank you and kind regards
.
@swschilke
There have been lots of answers for your questions. Please search the forum.
This topic is for discussing the original mirrorless, Canon EOS-M.
That said, for H.264 recording there is a restart feature and it is possible to use a simple lua script to keep the camera from going to sleep. Neither of these solutions are perfect because they either stop recording or create a glitch that needs to be edited out.
Even if you settle on a way to record over 30 minutes, the EOSM battery has a rather limited run time so you should consider either the AC adapter or some sort of external battery pack. Then there's also the possibility of the sensor overheating and the camera automatically shutting down. Remember, these are still cameras not dedicated video cameras.
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?
Thanx in advance!
Quote from: zabenoid on February 05, 2017, 11:20:52 AM
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?
What you are probably seeing is the refresh that ML is doing to keep the camera from jumping out of the ML menu. Otherwise you have about 5 seconds to find and select a setting. At least that's my guess. A video showing what you are seeing on your screen would help. Just load it up on YouTube or Vimeo and post the link here.
Quote from: zabenoid on February 05, 2017, 11:20:52 AM
And is it normal to have several self tests crash the system?
Unfortunately yes. The EOSM is very different from the DSLR's so many of the tests don't work on this camera.
Quote from: zabenoid on February 05, 2017, 11:20:52 AM
And is it ok to have temperatures over 50c constantly?
The sensor temperature reading wasn't working properly on the EOSM (https://bitbucket.org/hudson/magic-lantern/issues/2596/temp-goes-from-41-c-to-60-c) a while back but it was fixed (https://bitbucket.org/hudson/magic-lantern/commits/db40ff86890bb68d6a9016a0bcc3108ad2160d5f). If you have an older build you might be experiencing this. I don't have a camera in front of me right now but I believe that after it has been running for a while the temperature will probably go up to about 50c. That shouldn't be a problem. If it gets too hot it should automatically shut down.
Hello friends. I'm a wedding photographer who is training cinematography. I have a 5dm3 and I'm thinking to buy a second hand eos m for raw video, I think I could record save the date sessions with this camera. I picked this camera because of the small size and also can be installed magic lantern on it. Another reason is my wife. She is learning photography and 5dm3 is too much for her. That camera will help her to learn photography also.
Whatever. :)
My concern is about raw videos' size.
a) For example, 1 minute raw video; how much space will it take?
b) I have this card: http://www.ebay.co.uk/itm/Lexar-32GB-SDHC-633X-Professional-UHS-I-U1-Card-LSD32GCB1EU633-/311708743530
How many minutes can I write to this card in total and continuously?
c) What is the exact writing speed of eos m? :)
regards
a) https://github.com/rbrune/mlraw + basic math
b) Not well suited. Max. write speed is about 30 MByte/s. See a)
c) There is no such thing as exact writing speed. Interface is SDR50 and continuous recording will get you somewhere below 40 MByte/s.
Cam should be good for 720p@24fps with 14 bit RAW.
Concerning the ML menu screen, is there a way to extend the time before it goes away? I believe the current delay is 5 seconds.
Use a recent ML build for EOS M. A workaround for this problem was implemented in nightly builds months ago.
Hi I have been using Magic lantern on my x4 and 7D for years but have been too scared to load it onto my M due to the shutterbug.
Could someone please clarify:
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?
Every time, even after all this time, when I use Magic Lantern I get a thrill!
Thanks
Déjà vu (http://www.magiclantern.fm/forum/index.php?topic=9741.msg140865#msg140865)
Quote from: Arte Automobilistica on March 05, 2017, 07:04:22 PM
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?
1. Yes
2. Yes
The shutter-bug hasn't been squashed yet but it only shows up with EF-M zoom lenses. They all have IS so we're not really sure if that is causing the problem.
The newer EF-M zoom lenses are collapsible so if you collapse and extend the lens the bug is gone. If you untwist the lens to break the lens to body connection and remount the lens, the shutter-bug is gone. If you start, shutdown and restart in just the right timing the shutter-bug is gone. And if you use Sandisk Extreme PRO UHS-I cards 32GB or smaller, you'll never encounter the shutter-bug.
@dfort
Thanks for the bug correcting tips.
Does the using the 'correct' SD card really work?
Cheers
Garry
Quote from: dfort on March 06, 2017, 05:25:25 PM
...And if you use Sandisk Extreme PRO UHS-I cards 32GB or smaller, you'll never encounter the shutter-bug.
Quote from: garry23 on March 06, 2017, 06:53:15 PM
Does the using the 'correct' SD card really work?
Yep. I can confirm this from my own experience and funny thing is I never knew how to produce this shutter-bug until I tried a different brand SD card at a later date since the Sandisk Extreme Pro UHS-I 32GB cards were my first set of SD's to begin with. :P
@DeafEyeJedi
Great yo know. As a stills photographer I'm not that interested in large and fast SD cards.
Cheers
Garry
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.
Quote from: garry23 on March 06, 2017, 07:32:12 PM
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.
Dfort Thank you 8)
Quote from: Danne on March 06, 2017, 07:34:49 PM
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.
Sure and here are the files (took two 10 second clips) on each Sandisk Extreme Pro UHS-I 32GB cards w same settings per within ML:
Card #1 (104.8 MB) - https://mega.nz/#!GkdxnQwQ!9q8plzyG56gptQ6xjQ57FS4U6G8mYPK_BnV5SBGaIWE
Card #2 (95 MB) - https://mega.nz/#!WxEQUJaa!nC4LwdMV4dp69C4kYrjBAy6XznDColy6PuqbXqWH8JY
Hello. I have an issue with my EOS M after installing ML.
If I shoot in "Photo still mode" (non auto) the images previews on the screen show a blue, green or purple tint.
It's not recorded in the card, the images recorded are perfect, but the camera shows a tinted image for a few seconds. Here's a video of it https://youtu.be/dypKBdqWgb4 (https://youtu.be/dypKBdqWgb4).
Anyone can help? I tried turning off all features of ML but nothing changed.
Thanks.
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.
Quote from: dfort on March 12, 2017, 10:56:14 PM
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!
No worries -- I've found myself in a few situations where clearing the Canon settings was the fix. Of course the problem is that we don't know which setting was the one that caused the issue in the first place.
There is this menu in autoexposure module when you adjust auto ISO values, but its been like 3 years since i tried last time and i could not edit maximum value, only minimum can be changed, it says "use left right for minimum and main dial for maximum" , well, what is main dial ? I cant do anything to change maximum value and i tried all buttons on camera to do it, is it some kind of bug that nobody mentions because no one is using this feature ? Can i somehow edit behaviour of on camera buttons so they will work fully in ML submenus like this and ill be able to edit maximum value ?
Known problem, not so many buttons on the camera, maybe this thread will yield something helpful in the future: http://www.magiclantern.fm/forum/index.php?topic=18544.0
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.
Quote from: veryverynew on April 04, 2017, 02:13:13 PM
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.
1. make sure you on manual photo mode
2. click info until you see the stock canon menu
3. select the shutter speed
4. set it to bulb
5. click info until you see ML screen
6. enter the ML menu
7. Scroll right until you get the camera icon that says "shoot"
8.Scroll downward until you get to bulb timer
9. click on it an set your desired time
10. exit out of menu
11. press shutter half way until you see it counting the seconds
This makes it so you don't have to Keep your finger on the camera button
Any new news on on the MLV1080 raw recording?
Without binning
Also I've been trying to find out how to install cinestyle onto the eos m so far no luck because most of it requires the eos utility
Does anybody know how?
Hi,
joining (a bit late I know) ML EOS M party :). I want to use it as a travelling camera (with 15-45/3.5-6.3 IS it's mere 430 g and it can do raw), and I'd like to use two modes: mv1080 for wide shots, and 3xcrop for details/tele. I did some tests (https://youtu.be/FyfRVbYHYh8) with crop mode (2496x1044 2.39:1, as in lower resolutions bigger parts of frames are corrupted) and I love quality (although I can get only 68 frames before buffer runs out, but I can live with that, also at frame override to 23.976 i get black stripe on the right, which is not present at native 30 fps).
Concerning mv1080, several months ago there appeared several test builds with mv1080 support when recording along with h264. Some of them were for 2.03 firmware others for 2.02, and to be honest, i got lost at it. So my question is: Can someone direct me to newest(/most stable) build, that allows mv1080 mode? I am getting all shots in pink when using 02/04/2017 "10/12-bit RAW video build" from experiments.
Thank you. :)
Hey everybody!
I've been messing with anamorphics on a number of my cameras, and it seems that the EOS M might b e perfect for this kind of shooting. I've tried to enter the pixel dimensions that Tito Farrandans shares in this video: https://www.youtube.com/watch?v=h5vRS5YhZdc
The problem is that I can't dial up the RAW pixel dimensions that he mentions in his video. I get a list of various choices, but the numbers he uses aren't on that list.
Also, I shoot c-mount lenses with my EOS M using 3x movie crop. Will I be able to use a cmount lens with movie crop mode and with anamorphic settings? Or do the anamorphic settings take the place of what 3x movie crop is doing.
Hope that my description here isn't too confusing. Any ideas?
Thanks!
If you have a 2x anamorphic just use the highest resolution 4:3 image you can. You don't have to match his numbers. You can set 4:3 for 2x or you can set it to 16:9 for a 1.5 or 1.33x lens. Or whatever you want.
Hey - that makes sense! I've got a 1.33x lens, so I appreciate the additional advice. My experiments last night seem to have worked with some ad libbed settings, but I'll try again given your thoughts. Thanks for such a zippy answer!
One more weird thing - and I don't know if this is just me - I installed the latest build, and it doesn't appear that 3x crop is sticky. i.e. I have to re-activate it every time I turn the camera back on. Anyone else?
Hello-I'm new to ML. I do a lot of time-lapse work and that was my main motivation for installing ML on my EOS M. The camera booted fine and the intervalometer was working great for the first test. I did not set a frame limit and after about 20 minutes of shooting a frame every 3 seconds, it was time to end the test. However I could not figure out how to exit the intervalometer. I could not access the menu with the routine running. If I turned off the power and turned it back on the intervalometer routine would run again. Finally I turned off the power and removed the battery. After reinstalling the battery the intervalometer routine did not boot and I was able to access the menu again and turn it off. BTW the routine was set to trigger with the first shutter release.
Now however I have lost autofocus with half-shutter or touch-screen press in M, AV, TV and P modes. Half-press autofocus does work in all of the auto-exposure modes. I uninstalled ML and rebooted 2.0.2 but that did not fix the problem. I reinstalled 2.0.2 and that did not solve the problem. I updated to the latest 2.0.3 and still no luck. Any suggestions on how to fix the issue I'm having-Thanks
Did you reset Canon settings too?
Hello i would like to know if it would be possible to make live view possible through usb
Just like this video
https://youtu.be/JnzkHegu3aA
I know the camera doesn't have this capability due too the stupidity of canon
Quote from: Licaon_Kter on April 29, 2017, 09:54:17 PM
Did you reset Canon settings too?
After clearing all camera settings and custom functions in the menu, I have autofocus in all modes again. Thanks for the advice.
Hi all, I recently bought an used EOS M and updated to firmware 2.0.3 before reading about ML. Now I am desperate to downgrade to 2.0.2 so I can try ML. I could find the firmware version 2.0.2 in the first page of this thread. Is that the right one? Should I downgrade or wait for ML stable build with 2.0.3?
When taking a picture in raw format im getting the "raw error falling back to YUV overlays" error message
I have the newest nightly build
Is there anyway to fix this?
also what does it mean
https://www.magiclantern.fm/forum/index.php?topic=19226.0
Just sharing,
another card which is shutterbug-proof
(https://www.jakartanotebook.com/upload/images/toshiba%20exceria%20class%2010(1).JPG)
it's microsd, have not tested the full sd version..
Probably because it's toshiba they make great shit only 30MBps though need 40 for video..
Compressed raw video.. anything going on for the M?
I updated my EOS M with Nightly Build, acquired a SD card to use the M-zoom-lense without shutterbug and it works.
My humble question now, probably because I have not used ML for several years - the Focus racking and stacking tools seems to have disappeared- or might they not be available on the M - had it on my 60d last I tried?
https://builds.magiclantern.fm/features.html -> Focus
Indeed focus features are not available for EOS M. Maybe dfort or a1ex will jump in and telling why.
Thanks. Forgot to check the matrix.
The EOSM should have focus capabilities similar to the 650D and 700D but there is a problem controlling EF-M lenses.
https://bitbucket.org/hudson/magic-lantern/pull-requests/748/focus-backend-updates-precise-focus/diff
It does better with EF, EF-S lenses on an adapter.
I haven't looked into turning on those features. According to the source code:
features.h
/* Some Hope Yet */
#undef FEATURE_TRAP_FOCUS
#undef FEATURE_FOLLOW_FOCUS
#undef FEATURE_RACK_FOCUS
#undef FEATURE_FOCUS_STACKING
Having made two videos in EOS-M 720p raw crop mode...
https://vimeo.com/222128427
https://vimeo.com/221350421
...I'm left with the following practical questions:
1) The video crop mode setting isn't remembered by the camera even after ML parameters have been saved. It needs to be manually reactivated in the ML video menu each time the camera has been turned on. Is there any way around this?
2) Sound recording with the mlv_snd module isn't 100% synchronous, because the audio track usually runs a bit longer than the video clip. (I tested this with two different copies of the EOS-M, and the behavior is consistent and reproducible.) While this shouldn't be an issue, it seems to throw off MLV-to-CinemaDNG converters. Raw2CDNG doesn't correctly decode the sound so that audio tracks end up being fragmentary and out-of-sync. This can be fixed by extracting .wav files from the MLV files via ffmpeg and manually aligning them to their corresponding video clips in the editing timeline. But is there a way to convert MLV created by the EOS-M to CinemaDNG without these issues? [I'm primarily a Windows user and couldn't get MLVFS to work.]
3) We keep reading great things about MagicLantern's new 10bit and 12bit raw recording options. Are they available (or in the pipeline) for the EOS-M at all?
you can get 10 bit and 12 bit magic lantern under downloads downloads again then experiments
> 1) The video crop mode setting isn't remembered by the camera
That's there for a reason: https://bitbucket.org/hudson/magic-lantern/pull-requests/776/disables-crop-mode-hack-when-turning/diff
There's an open pull request to save the "Movie crop mode" setting in a preference file and restore the last used state.
https://bitbucket.org/hudson/magic-lantern/pull-requests/787/crop-hack-config/diff
I haven't tried it in a while but it looks like maybe it doesn't work on the other cameras that can do that trick (650D 700D 100D).
So I'm searching for EOSM2 stubs using similar cameras as reference (700D 100D EOSM) and the msg_queue_create stub on the EOSM doesn't seem to be matching what the other cameras are using:
/** 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
Shouldn't it be?
NSTUB(0xFFA880D8 - RAM_OFFSET, msg_queue_create)
Not sure how to check this.
0xFFA73C84 is a wrapper for 0xFFA880D8 (the only difference being at error handling, which never happened within our usage - yet).
For consistency, it's best to use the same stub on all models. Probably a good candidate for automation (the algorithm is in ARM-console, but that one does have some weird dependencies...)
Also noticed that EOSM still has the old post_isr_hook/pre_isr_hook in unified. This was changed in the dm-spy-experiments branch with commit b1bd219 (https://bitbucket.org/hudson/magic-lantern/commits/b1bd219209b382669c84080e90758c1a20a918b4).
EOSM.202/stubs.S
/** 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)
Pretty sure I caught another issue, this time with an EOSM constant.
magiclantern/platform/EOSM.202/const.h
#define YUV422_LV_BUFFER_DISPLAY_ADDR (*(uint32_t*)(0x3E650+0x11c))
Should be:
#define YUV422_LV_BUFFER_DISPLAY_ADDR (*(uint32_t*)(0x3E650+0x118))
Anyone care to double check? It is after *"call ChangeVramCallBack pFlipCBR=%x"
Compared it with the code for 100D, 700D and 550D.
On 5D3 1.2.3's consts.h there's a better hint - near ImageEffect. That one would give 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).
Not a ML issue but..
How does one treat "Change battery pack" error? (I guess this is the message, I get the localized text)
Had it at 100%, shoot a bit yesterday (still fullbar), forgot to charge it last night, but I put it in the charger in the morning for 15 min, charger led still orange.
I had to go, put it in the camera and went outside.
After more than an hour of walking outside in sunny weather, trying to take a picture I get the surprise messag e with a red empty battery icon AND the ML message of "bad shutdown modules not loaded" (as expected).
This happens without SD card too.
I don't have a collapsible 15-45, just plain 18-55 and 22.
Original Canon battery that came in the box.
/LE: False alarm, got it charged up to green and now it starts fine. Got me scared there for a bit. :)
Quote from: a1ex on June 26, 2017, 09:32:34 AM
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).
Tried it, Display > Anamorphic and Display > Defishing are working. Is there anything else that should be checked?
Updated stubs pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/839/eosm-stubs-tweaks/diff).
Yay! This one was broken for a very long time.
Raw video previews also depend on this backend, and also HDR video should no longer flicker while recording.
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.
(We really need some tests for all these constants, to catch such mistakes early)
QuoteRaw video previews also depend on this backend, and also HDR video should no longer flicker while recording.
:o
Nice work @dfort!
Thanks @dmilligan. You taught me many lessons.
Quote from: a1ex on June 26, 2017, 04:04:06 PM
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.
Just tried it--still doesn't work. Also
didn't get rid of the shutter-bug, solved the mv1080 problem or suddenly started recording in 4K on the EOSM.
nice dfort! always wondered what the black and white preview everyone was talking about was because id never seen it. nice to be able to frame in 5x crop mode. any chance this could be put into the old experimental builds? currently can only be used on 14bit. could it be put into the compressed raw and crop mode builds on experimental page for 10 bit and 12 bit?
@Teamsleepkid - If you really want to live on the cutting edge set up a development environment and learn how to merge branches. I just updated my Macintosh (http://www.magiclantern.fm/forum/index.php?topic=16012.0) and Cygwin (http://www.magiclantern.fm/forum/index.php?topic=15894.0) tutorials. Note that there is currently a gotcha on the Cygwin version (http://www.magiclantern.fm/forum/index.php?topic=15894.msg186461#msg186461) that should get fixed upstream but it is easy enough to work around for now.
yeah i figured something like that was coming. honestly I'm more into cameras then into coding. appreciate what you do a lot though. you're always killing it. same with the others. appreciate all your hard work on the eos m. its a great little camera now.
looks like it made it into one of the new experimental builds. very cool. so being able to frame in 5x zoom mode is super useful. anyone ever notice? or am i way off base here? i have no scientific proof but...5x crop mode seems to have tighter grain? makes no sense. and also seems less noisy for sure. maybe a little brighter? it definitely looks better than regular "crop mode". try it. 5x crop mode is cleaner in low light i swear to god. I've done lots of tests. i do them for myself though and i always delete them. just looking for someone else to corroborate this claim..
Cool if so. I use my eosm with crop_rec all the time recording 12bit with audio. Those files comes out golden. Chroma smooth set to --cs2x2 and ran through dfort focus pixel lists through bouncyball pixel map in mlv_dump and we get clean dng's.
Don't forget about darkframe averaging and files comes out even better. All baked in cr2hdr.app :)
please can someone give a direct link to ML 2.03 for canon EOSM? I know its not finished testing yet, just want to try it.. been following links and hunting the forum but cant seem to find an active download.. many thanks :)
You can find it in here.
https://bitbucket.org/daniel_fort/magic-lantern/downloads/
Hi,
if I understood correctly, when shooting raw video, most of you are using (one way or another) crop mode in either telephoto mode (with EF-M lenses) or you are using some short focal length C-mount TV lenses. Is there a list of usable (and affordable preferably) lenses (i'm looking for sub 15mm)? 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.
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.
Quote from: loknar on July 16, 2017, 09:46:54 AM
...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.
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.
Quote from: Teamsleepkid on July 16, 2017, 11:18:14 AM
c mount lenses don't seem to focus to infinity though... at least mine don't .
They should -- mine do.
The EOSM isn't the best camera to shoot raw video though it is fun trying. There are development branches that allow you to shoot H.264 proxies along with mv1080 raw video. Best set up a compiling environment if you want to have some real fun with the EOSM.
Quote from: Teamsleepkid on July 16, 2017, 11:18:14 AM
... im still waiting for compressed raw. then we are talking better than a7sii in sharpness territory...
Cool. We're all waiting for you to get this started.
dfort i always thought you were a great guy. sorry if i made you mad. you have always helped me a lot. nothing but respect. i have no idea how to code anything. i just see tremendous potential in the little eos m so im wishing out loud.
@Teamsleepkid
What makes you think I'm angry? Insane, maybe. All I'm doing is trying to get some of the more advanced users, like you, to compile ML instead of waiting for someone else to do it. Once you can roll your own you'll be able to try out some of the more experimental branches. In addition, if you want to regress to an earlier version you can pick which commit to go back to. You don't need to change a single line of code to do any of this. Download the SourceTree app (https://www.sourcetreeapp.com/) and watch ML development nearly real time. Just clone the ML repository using this URL: https://bitbucket.org/hudson/magic-lantern
If you are on Windows my Cygwin tutorial (http://www.magiclantern.fm/forum/index.php?topic=15894.0) makes it super easy. On Mac (http://www.magiclantern.fm/forum/index.php?topic=15894.0) I just updated the install script so it is pretty much automatic once you make /usr/local writeable. The scripts even clones the repository and sets you up on the unified branch. You can switch branches, merge and even poke around in the code if you want. If you muck things up simply delete your local repository and re-clone it.
Quote from: Danne on July 16, 2017, 10:31:30 AM
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.
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.
Quote from: Teamsleepkid on July 16, 2017, 11:18:14 AM
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.
Could you elaborate on manufacturers of these lenses? I managed to find some from Tamron and Fujinon.
Quote from: dfort on July 16, 2017, 10:22:04 PM
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.
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
Quote from: loknar on July 25, 2017, 08:50:57 AM
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.
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
Keep us posted on your results.
Sent from my E6653 using Tapatalk
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?
I've been away for almost 2 yrs. I'm excited to see whats new and I need advice on recording video with the screen off. How to? I need to record for as long as possible. I got the LCD to turn off while recording but my first file was only 4.7 minutes long with the camera going to sleep. What do I need to do to get the longest recording?
Quote from: Shutterbutton on August 12, 2017, 02:20:47 AM
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
So essentially just 10/12 bit recording?
Hi, Firstly I hold my hands up, have not read through 50 plus pages of this EOS M part of the site but if someone would like to comment?
I don't even have the camera as yet, bought second hand to dip my feet in the water of mirrorless. I do use M/L on my DSLR's 6D/70D, have done so for many years now and I only shoot stills not video so for those who shoot stills what are the top three advantages of M/L with the EOS M to date?
Thankyou in advance for any input.
Russ.
Top 3 for still photographers on the EOSM? Hard to trim it down but how about.
- Audio Remote - The EOSM doesn't have a cable release but you can hack one together with this feature.
- Full Resolution Silent Pictures - If you're on a tripod making long exposures this will keep your shutter count way down.
- Lua Scripting - There are lots of scripts for still photographers, like the one for manual lenses and of course the scripts garry23 wrote for landscape photograhy.
My top 3 for stills
* focus peaking, especially for manual lenses
* dual ISO w/ ETTR (especially when you are used to dynamic range from FF like your 6D)
* advanced bracketing
Sent from my SM-T719 using Tapatalk
" dual ISO w/ ETTR (especially when you are used to dynamic range from FF like your 6D)"
I never managed to get anything decent out of dual ISO. :(
@Shutterbutton
'Even' the humble EOSM is able to exploit dual-ISO.
I'm afraid without seeing your source dual-ISOs, I can't help devine what trouble you are having. It's all in the ML settings and post processing ;-)
You may get some pointers by reading some of my post on dual-ISO at photography.grayheron.net.
In addition to dfort's favorites, I would add raw spotmeter, and, as dfort says, scripting is the killer feature, as you can access all the other good stuff through scripts.
On my EOSM I have two scripts always running. My Toggler and my Focus Bar.
Cheers
Garry
Do you find Dual ISO doing anything that you couldn't accomplish with standard bracketing? Also, does your focus bar script work with manual lenses? I'm interesting to know which you've been using with your EOS M.
@Shutterbutton
The key difference between dual and multi-image bracketing is the fact dual allows about a 3Ev boost, all in a single image. Thus there is no risk of movement artifacts.
Of course, if the scene requires greater than 3 Ev help, I will exposure bracket.
Tne RAW spotmeter will help you gauge the DR of the scene, from which you can decide if dual will do it or not.
My focus bar works with all lenses that report focal length, focus distance and aperture. For me it works with all my EOSM lenses, both EOSM lenses and EOS lenses via an electronic adapter.
Hi, still await arrival of the camera so when in live view and you bring up the ML menu does the screen flicker as it does on the 6D and 70D and does this ML version on this camera have rack focus, focus stacking options please? Many thanks, sorry for the simple questions but as I don't have the camera I have to ask. Russ
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
I am having an issue with ML and my 18-55mm KIT lens. For whatever reason my 18-55mm Kit Lens refuses to take photos with pretty much any version of ML. So far the only version that seemed to work with the lens was the August 1st version. However that only worked until I switched off the kit lens for my vintage 55m 1.4 lens. Once I put the kit lens back on it no longer works. It will focus, and record video but the aperture won't change and will not take a photo. I have tried changing the different modes and everything. Nothing seems to work. The main reason I want to use ML is for the forced Exposure Simulation so I can see exactly how the shot is going to look like through the live-view. It bothers me to no end when I take a photo and the screen is darker or lighter than the actual picture taken. I don't think the default Canon EOS M settings have that feature.
Any advice?
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.
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.
Quote from: dfort on August 29, 2017, 01:52:20 PM
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.
Quote from: Walter Schulz on August 29, 2017, 08:06:13 AM
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.
Wow thank you. I have always been turning the camera off before I switched lens and that is why I kept getting the shutter-bug. If I do it with the camera still on it switches fine. And yes taking the battery in and out fixed it as well.
I just have a Lexar Platinum ll 32GB 300x 40MB/s. Is there any benefit to having a faster SD card with this camera?
Quote from: igrease on August 29, 2017, 07:32:15 PM
I just have a Lexar Platinum ll 32GB 300x 40MB/s. Is there any benefit to having a faster SD card with this camera?
I believe it does. Test for yourself. Go to Modules tab and enable Bench.mo. Disable all others. After restart in photo mode go to Debug tab -> Benchmarks -> Card Benchmarks -> Quick R/W benchmark (1 min). Would be surprised to see write speeds above 20 MByte/s with this card. Cam can do about 40 MByte/s.
Installed experimental crop_rec ML from 14sep2017 on my EOS-M.202
mv720 3x3 is working great, but now I have a question: is there any working solution for focus pixels in mv720 3x3 footage?
Quote from: madz on September 21, 2017, 01:34:58 AM
is 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.
Anyone else having issues with Advanced bracketing?
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!
Interesting discovery while trying to track down another issue--Audio Remote Shot works fine with the EOSM removed from this list:
#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)
Though I have a feeling the proper fix would be to remove that hack from shoot.c and ask for audio meters (tell the audio backend that we are going to record sound, with a ml-cbr snd_rec_enabled handler). That request would enable any camera-specific tricks required to enable the sound card.
Another possible bug on the sound side: does mlv_sound record sound with... global draw off?
Quote from: a1ex on October 01, 2017, 09:48:08 AM
Even when starting the camera in photo mode? (with the sound device likely disabled by Canon firmware)
Interesting--it doesn't work when starting the camera in photo mode. Glad I didn't take that any further.
Quote from: a1ex on October 01, 2017, 09:48:08 AM
Another possible bug on the sound side: does mlv_sound record sound with... global draw off?
That does work. Even started the camera with global draw off just in case.
Quote from: kosmarnik on September 24, 2017, 03:12:40 PM
Anyone else having issues with Advanced bracketing?
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.
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: russellsnr on October 02, 2017, 08:56:40 AM
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.
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
Yeah, saw that one, but as it may be an EOS-M specific issue, it might be useful to have it here too.
Quote from: dfort on September 21, 2017, 01:56:28 AM
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.
Thanks! But I had to tell that I'm on Windows, sorry :)
I tested MLVProducer build 3151, it removes focus pixels in the center (profile 80000331_1808x727 (https://www.dropbox.com/s/m85brnbumwdj3nt/focus_pixels_sides.png?dl=0)), but leaves some at sides. And vice versa with profile 80000346_1808x1190 (https://www.dropbox.com/s/lc7vhahm6ewmjkz/focus_pixels_center.png?dl=0). I thought it might be using an old version of your EOS-M profile and downloaded it from bitbucket (https://bitbucket.org/daniel_fort/ml-focus-pixels/get/6f164bf8fe45.zip), but unfortunately it uses some different format (not plain text as yours).
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.
----
Experimental crop_rec_4k.2017Oct02.EOSM202
Quote from: madz on October 04, 2017, 12:16:59 AM
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 :)
Don't forget @Danne also made a window batch processing app as well: https://www.magiclantern.fm/forum/index.php?topic=10526.msg188558#msg188558
Quote from: madz on October 04, 2017, 12:16:59 AM
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.
Interesting question. You aren't doing anything wrong. The EOSM always records MLV (RAW) at 23.976 frames per second (even when set to PAL) except when in Movie crop mode or when using FPS override. The only way around this is to record H.264 at the same time which of course is a real challenge on this camera. You can find more information in the mv1080 on EOSM (http://www.magiclantern.fm/forum/index.php?topic=16608.0) topic.
If you set the Canon menu to 1280x720 you'll be able to record 60/50fps in H.264 but the quality suffers because it does some extra vertical line skipping causing all sorts of aliasing and moiré. However, if you turn on crop_rec you can get better quality video. Note that on the LiveView and the movie file it will look like it was shot with an anamorphic lens so it needs to be stretched out in post. Give it a try, it might be the effect you're looking for. One caveat--I've seen focus pixels on H.264 when using the crop_rec module and I haven't found an easy way to deal with that.
I never thought about it before but the same trick for getting the EOSM to record mv1080 should also work for recording 60/50fps with the crop_rec module--though the sd card controller will never be able to keep up.
As for the focus pixels, mlv_dump on steroids (http://www.magiclantern.fm/forum/index.php?topic=18975.0) should work on any computer platform. I haven't tried MLVFS (http://www.magiclantern.fm/forum/index.php?topic=13152.0) on Windows but that should work too.
Batch_mlv for windows uses mlv_dump_on_steroids. It can work with most methods around focus pixels built around your fpm.sh. Batch_mlv uses the mlvfs method(lists are stashed in a folder). As we know crop_rec footage should use a replacement list. A list that is only used in Switch atm for all I know.
Now how about that crop_rec focus pixel list for the 100D? Could it be added to fpm.sh?
Quote from: Danne on October 04, 2017, 07:01:35 AM
Now how about that crop_rec focus pixel list for the 100D? Could it be added to fpm.sh?
+1
Quote from: Danne on October 04, 2017, 07:01:35 AM
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)?
Sorry, language barrier :(
About 48/50/60fps on EOS-M for this moment I fail.
setting in Canon menu 1280x720p50
enabling mlv_lite raw resolution 640x268 14bit/14bit lossless/10bit (for some reason 10/12bit lossless is not available)
enabling h.264 proxy with CBR 0.1x
and most of the time I get a lot of error messages and only battery pull helps out.
if it records something it's actually 50fps, but corrupted frames (black with vertical lines).
without proxy it's always 29.973, and with fps override it tops at 31.2xx
Offtopic: Does 700d/100d manage to shoot 48/50fps RAW? I was planning to get a 50d (no focus pixels and CF card), but if 700d/100d can do slowmo with 10/12bit lossless - that would be a huge plus for me.
Quote from: madz on October 05, 2017, 03:12:27 AM
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)?
That's the only app that I tested and works for me. MLVFS works too but you need to manually change out the focus pixel map file. There
might be others that can do the job.
Quote from: madz on October 05, 2017, 03:12:27 AM
Offtopic: Does 700d/100d manage to shoot 48/50fps RAW? I was planning to get a 50d...
Only the 5D3 can shoot 48/50fps RAW. At least for now.
Quote from: Danne on October 04, 2017, 07:01:35 AM
Now how about that crop_rec focus pixel list for the 100D? Could it be added to fpm.sh?
Speaking of offtopic--let's pick that up on the Dealing with Focus Pixels in raw video topic (http://www.magiclantern.fm/forum/index.php?topic=16054.new#new).
Would some of the devs please take a look at the Advanced bracketing issue?
I't doesn't work with audio remote shot (as described in my earlier post). It also has issues when used with the intervalometer.
I grabbed the source to take a look at shoot.c, but it's a bit too much for me to grasp at a glance.
Hi all!
Just installed ML on my EOS M, mainly because of the Dual ISO mode in stills, but I can't find it. Tried two builds. Please help.
Thanks!
Have you followed this: http://www.magiclantern.fm/forum/index.php?topic=12713.0
This may be a hardware issue, but my scroll wheel stopped working, as well as my AF. I swapped lenses, batteries, cards, tried with no card, no ML, etc. with no luck. Has this happened to anyone's eos-m? Did I hit something by mistake? The touch screen and other buttons are working fine. Any ideas what I can try to fix this? Thanks.
See replies #1276 and #1277.
Quote from: Walter Schulz on October 23, 2017, 03:22:33 AM
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.
Quote from: dfort on October 23, 2017, 11:30:58 PM
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?
Quote from: oenopion on October 25, 2017, 12:52:55 AM
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.
Say that resetting CANON settings did not help?
Sounds more like a hardware issue.
Quote from: Licaon_Kter on October 25, 2017, 10:59:58 AM
There is an experimental 2.0.3 version, but it's better to stay on 2.0.2.
Say that resetting CANON settings did not help?
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?
Quote from: dfort on October 25, 2017, 04:49:41 PM
Sounds more like a hardware issue.
I was just typing that thought as you posted.
Is there any way to check (diagnostic)? Or is that repair shop territory?
I suggest to wait for a1ex's opinion on that before going to upgrade/downgrade firmware.
Do you have backups of ROM0.BIN and ROM1.BIN?
It's possible to build some diagnostic code (based on some old Linux experiments), but it takes a while, and I won't get a contiguous chunk of time to experiment with it until weekend (and possibly not even then).
Upgrading the firmware is unlikely to help, but shouldn't hurt.
If you can compile ML, start from the dm-spy-experiments (http://www.magiclantern.fm/forum/index.php?topic=2388.msg113154#msg113154) branch, comment out LOG_INTERRUPTS (https://bitbucket.org/hudson/magic-lantern/issues/1974#comment-40761896), and you may also have to leave just mpu_send / mpu_recv (as LiveView is very verbose). If you know how to start the camera without LiveView (maybe by starting directly in Canon menu, or in play mode), try that, as these modes are way less verbose. Then try the affected buttons in these modes, to see what events you get. Button codes are mpu_recv(06 05 06 ...) (http://www.magiclantern.fm/forum/index.php?topic=17596).
Also related: anyone else who can compile is welcome to get some logs for troubleshooting the menu timeout issue (https://bitbucket.org/hudson/magic-lantern/issues/1974#comment-40758822).
Thanks, a1ex. I haven't tried to compile, but will take a look later when I have time.
Since the problem still exists without an sd card in camera, is this pointing toward a hardware failure?
And if I do the firmware upgrade, can I revert to the firmware that is more stable with ML?
That's the point of these diagnostic tools - to find out what's going on. In particular, the bootloader test will show the raw GUI events, not altered by a possibly misconfigured main firmware.
The dm-spy logs should also be pretty good in this case. There is a precompiled build here (https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log/) (the latest one has LOG_INTERRUPTS disabled, but it might still be too verbose - try to start the camera without entering LiveView; even a few LiveView frames will fill the buffer very quickly). That's why it's best if you can compile - you'll have to fiddle with the logging code to get useful info (here, you may want to silence LiveView messages, for example).
Quote from: a1ex on October 25, 2017, 06:20:08 PM
Upgrading the firmware is unlikely to help, but shouldn't hurt.
So how about doing a little upgrade on the EOSM? Posted a pull request to test out the latest Canon firmware on the bleeding edge crop_rec_4k branch.
https://bitbucket.org/hudson/magic-lantern/pull-requests/879/crop-rec-4k-eosm203/diff
Test build available in my Bitbucket downloads page:
https://bitbucket.org/daniel_fort/magic-lantern/downloads/
Hello, i am new so maybe mine is a stupid question. I've installed latest ML firmware on my EOS M. Everything's gone fine, no shutter bug. The only thing is that while i am in the option view i see a red symbol flashing in the right low corner of the screen. Can't understand what is it.
Hope you can help me.
Thank you
(http://thumb.ibb.co/dMxEYG/23600083_10215084815420924_1263297975_o.jpg) (http://ibb.co/dMxEYG)
It's a fix for: https://bitbucket.org/hudson/magic-lantern/issues/1974/6d-m-100d-70d-in-live-view-mode-ml-menu
Hi 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. Is FB compatible with a regular prime 50mm F/1.8 STM ?
Cheers.
Quote from: garry23 on August 19, 2017, 02:47:56 PM
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
Quote from: EOSM-user_1 on November 21, 2017, 04:57:18 AM
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.
Canon EF 70-300mm f/4-5.6 IS USM is among the few lenses featuring "micro-USM". Most micro-USM lenses lack of FTM and focus distance encoder. This lens is not suited for FB script.
Good day, Guys,
I have an M6, and it amazes me that Canon crippled Live Shooting and being able to use as a webcam.
My question is can Magic Lantern enable live shooting and Webcam for the Canon M6.
In the past, I had a Rebel, Which I hong from the ceiling and would connect to my computer via USB and EOS utility.
I would manage my shots with Live view and was able to stream it as well using Wirecast.
My goal and hopes is that Magic Lantern can get me back to is on the M6
Thank you.
Top of page -> Downloads -> Download Nightly Build -> Scroll down to "Your camera is not listed?"
If M6 follows Canon's M lineup (M2 successors) it is hosting PowerShot code and you will not get ML ported. Jump to CHDK instead.
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)
650D has this feature and EOS M should do, too:
Display tab -> Advanced Settings
- UpsideDown mode ON
- Orientation Mirror
EDIT: Sorry, just checked https://builds.magiclantern.fm/features.html and EOS M does not support Image Orientation.
I just hope it does one day ;)
I suggested this a while ago.
It really is needed.
Looking at the ML User Guide, it seems the feature required for this to work is "Display: Normal/Reverse/Mirror", under Display-->Advanced Settings.
Does this mean that the 'Display: Normal/Reverse/Mirror' could possibly be added to the eosM, or that this is not possible because the eosM is not a flip-out LCD camera?
These 3 functions are only present in Canon firmware on models with flip-out LCD. The feature is likely implemented in hardware, so the low-level interface might be present in other models as well.
If you run these functions in QEMU (-d debugmsg to log Canon's debug messages; change this option from ML menu and write down what their code does), you'll get this (700D):
[ 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
so it's likely to be on the TFT controller, in SIO [1]. On D4 models, this looks similar, but with 4 SIO numbers and different values. 70D uses yet another set of values.
Can the same SIO communication be replayed on other models? I've tested this on 5D3 1.1.3, unsuccessfully (the display turns off; you can check the debug messages in QEMU or with dm-spy-experiments):
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");
}
My advice would be:
1) try the above code (update the stubs first!) on 700D or 650D (not other models) and make sure it mirrors the display (there may be more things to patch, no idea)
2) after 1) is working, try on EOS M (extremely unlikely to work on other models)
edit: after comparing the TFT SIO initialization sequences, 650D and 700D are identical, while 5D3 and EOSM are quite different, so the chances of this working are next to none. Still, I'm curious whether the above code works on 650D/700D (even if this knowledge has no practical value right now, it might have later).
BTW - it is possible to implement the image orientation in software, using the display filter interface. Disadvantages: low frame rate; will not work with other display filters (raw video preview, anamorphic/fisheye correction etc).
Would like to test on 650D but I have no idea which stubs have to be updated.
All of them.
650D 104: FF127E88, FF127D88, FF13B868, 23C48.
700D 115: FF128A28, FF128928, FF13C420, 23C58.
update: the TFT controller on 5D3 can definitely do mirroring and flipping. Just opened a reverse engineering thread (https://www.magiclantern.fm/forum/index.php?topic=21108) for this.
Works on 700D, found stubs for EOSM with the exception of p_lcd_sio_obj: [EDIT] missing stub found
EOSM 202: FF12909C, FF128F9C, FF13B454, 3E690.
More on the FT SIO communication (https://www.magiclantern.fm/forum/index.php?topic=21108.msg193715#msg193715) topic.
wow.. you guys are guns! Unfortunately most of this it flying way above my head. If the only way to do this is in software I agree it wouldn't be worth the overall slowdown and incompatibilities. Many thanks for your great work.
Quote from: MrFurious70 on November 25, 2017, 08:50:39 AM
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)
Looks like the TFT SIO communication topic (http://www.magiclantern.fm/forum/index.php?topic=21108.0) and the new tft_regs module could make this possible.
Register 0x6 seems to hold the key:
06:00
(https://farm5.staticflickr.com/4569/37953501014_a6824d4f58.jpg) (https://flic.kr/p/ZPPBz9)
06:02
(https://farm5.staticflickr.com/4538/38639166242_b594b1ce0a.jpg) (https://flic.kr/p/21SpPXq)
06:04
(https://farm5.staticflickr.com/4579/24798824698_e39dd20ac3.jpg) (https://flic.kr/p/DMosB5)
06:06
(https://farm5.staticflickr.com/4563/37953501454_a5113e2764.jpg) (https://flic.kr/p/ZPPBGJ)
The pattern repeats every 0x8. The odd numbered values produce garbled results -- maybe half-resolution?
@dfort
:)
I already know how I'm going to implement this on the EOSM, once it gets into a Nightly: I'll add it to my Toggler script so I can switch between modes on the fly, i.e. With out opening up the ML menu.
As usual, thanks for all your experimentation and perseverance.
Cheers
Garry
Flipped mirror, how cool is that.
Quote from: dfort on November 27, 2017, 06:40:37 AM
Register 0x6 seems to hold the key
This matches 70D. Didn't expect that.
Downloaded TFT_SIO_communication.2017Nov26.650D104.zip from dfort's repository.
After "Don't click me!" screen is flipped according to pic dated "6:02".
Not 6.04? :(
No tft_regs.mo -> nothing to play around without compiling ...
Hi,
I stupidly updated my M to 2.03, but ML requires 2.02..... not available from Canon site - could somebody plz post up a link for me to download..... thanks much.
Now you do (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). The module should work for various cameras including the 650D and EOSM. I'll elaborate on the TFT SIO communication (tft_regs.mo) (http://www.magiclantern.fm/forum/index.php?topic=21108.0) topic.
Thanks. Unfortunately fiddling around with registers does the following:
Every even register -> Switch value from 0x0 to 0x1 -> Screen goes blank.
Switching to 0x2 -> Nothing happens at all -> Screen stays blank, pressing Menu button brings screen back but orientation is normal.
And strange but true: After pressing "Don't click me!" screen does 6:04 flip+mirror, regardless if module is loaded or not. Tried to reset even registers 0x0 to 0xc with value 0 but "Don't click me!" still works this way.
Quote from: Walter Schulz on November 28, 2017, 08:27:45 AM
And strange but true: After pressing "Don't click me!" screen does 6:04 flip+mirror, regardless if module is loaded or not.
Are you still using the previous build? That one had flip+mirror test hardcoded in the Debug menu. Try the module with a nightly or experimental build. The module also works on the 7D so I updated the module on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). a1ex explained why things might be a bit wonky with the 650D/700D on the TFT SIO communications topic (http://www.magiclantern.fm/forum/index.php?topic=21108.msg193774#msg193774).
Back on this topic, so far the best experience I'm having with the tft_regs module is on the EOSM.
:)
QuoteBack on this topic, so far the best experience I'm having with the tft_regs module is on the EOSM.
TFT flip and bound to a hotkey... simply amazing, I cannot wait for this.
@MrFurious
Using Lua, choose any key you wish ;)
Quote from: MrFurious70 on November 25, 2017, 08:50:39 AM
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)
Damn, now I get why its so cool that you flip the screen. I remember I tried with a mirror at the bottom once, but yeah I quickly realized it was not such a good idea ;) Who needs tilt screen now, just get your wives makeup mirror ;)
Hello, guys. Thanks for the incredible Magic Lantern, which I've been interested in for a long time and finally got a canon eos m to start playing with it. I got problem with raw video aspect ratio.
In short, I always get a narrowed footage, like this:
(http://thumb.ibb.co/dnA9pb/DSC_1280.jpg) (http://ibb.co/dnA9pb)
It looks the same after converting to dng.
I tried different settings and always get message like "1280x432 Stretch by 1.67x to get eg. 1280x720 (desired aspect ratio) in post" in ML raw video resolution / ratio menu
(http://thumb.ibb.co/k5cuNw/DSC_1281.jpg) (http://ibb.co/k5cuNw)
I checked all combinations and the image is always narrowed (during recording seems to be ok)
(http://thumb.ibb.co/b8X5Ub/DSC_1279.jpg) (http://ibb.co/b8X5Ub)
Canon Video option is set to 1920x1080@24
ML Bitrate 1x
ML FPS override 24
Card: Sandisk Extreme 16gb 45mb/s
I use latest nightly build (2017-10-30)
Googled and checked this forum for it, but cannot find any solution.
Am I missing sth? Pls help.
Quote from: mariw on December 02, 2017, 02:24:35 PM
Googled and checked this forum for it, but cannot find any solution.
Am I missing sth? Pls help.
Did you read every post from every topic before posting?
Just kidding of course, this is your first post. You aren't missing anything, the EOSM is. This topic should clear things up for you:
http://www.magiclantern.fm/forum/index.php?topic=16608.0
So to get mv1080 working on the EOSM you need to use the crop_rec_4k branch which is available on the experiments download page (https://builds.magiclantern.fm/experiments.html) and use the H.264 proxy workflow. Another option is to use the crop_rec module that is available on that same branch. A word of warning, H.264 proxy recording isn't working yet though some people have had limited success with it.
@dfort
Thank you for your answer. Apparently I was not looking deep enough. After watching some amazing clips on YouTube, I thought it was enough to buy a camera and upload ML :)
Actually it is amazing what can be done with an EOSM. It looks like you are into raw video so try this. Put the camera into Movie crop mode:
(https://farm5.staticflickr.com/4580/23948038527_6c23587c36.jpg) (https://flic.kr/p/CucXvZ)
In this mode the EOSM sheds most of its quirks like only running at 29.97 fps and not going into mv1080 mode unless you're recording H.264 at the same time. The downside is that you're using a small area of the sensor so you'll need some wide lenses for this to be practical. Still, if you're shooting raw video the EOSM can hold its own when compared to much more expensive cameras if you use the Movie crop mode.
If you want to use a larger area of the sensor to get that cinematic depth of field and don't mind shooting in a wide aspect ratio, try the crop_rec module.
Tried both and got some very promising results with crop_rec and some of my ef-s L and manual m42 lenses. I am pretty amazed with eos m overall performance in terms of color depth and dynamic range :)
(http://thumb.ibb.co/hd6t0G/M03_1602_frame_79.png) (http://ibb.co/hd6t0G)
Hey boys, been away for a while and currently at work with no time to spend an hour searching, any word on follow focus working on the eosm ? Haven't tested a nightly in several months. Debating on buying an old t3i or such just to have this feature back.
Thanks for any feedback.
Checked the latest build for eosM and can't seem to find the display flip/mirror function.. did this not make the final cut?
You mean like this?
(https://farm5.staticflickr.com/4738/38223663714_780696eae7.jpg) (https://flic.kr/p/21eGgwJ)
If you are referring to the new TFT SIO communication (http://www.magiclantern.fm/forum/index.php?topic=21108.0) module to flip and mirror the LiveView, I put a build of that module on my downloads page -- thought that is still very much experimental.
@nlantz - what are you talking about? This is what I use for follow focus:
(https://farm2.staticflickr.com/1594/24485578289_afa133e3ea.jpg) (https://flic.kr/p/DiGZmV)
But seriously folks:
platform/EOSM.202/features.h
/* Some Hope Yet */
...
#undef FEATURE_FOLLOW_FOCUS
So you could either try to get it working, get that old T3i or hire someone to pull focus for you.
@dfort
Looking forward to the flip/mirror feature.
I purchased this http://flipbac.com/viewfinder-specifications.htm but it only has a 3in aperature.
Does anyone know if there is a larger one from another company?
One that will fit an EOSM.
I have my Varavon 90 degree unit for my 5D3, but sadly they don't make it any more.
Cheers
Garry
So you're doing this?
(https://farm5.staticflickr.com/4585/38940374441_7f2c6b3b90_m.jpg) (https://flic.kr/p/22k2AEe)
Ha ha -- got to love the music on their demo videos:
Ok, had a good laugh but I can see how this could be very handy for cameras without articulating screens. Just a thought, how about adding an inexpensive HDMI monitor? There are even adapters so you can use your phone as the monitor. That would provide even more flexibility though it does add bulk.
@dfort
Covering all bases and having fun.
I also have a viltrox DC-50 HDMI monitor: good value.
Cheers
Garry
I installed the TFT SIO communication module with the values shown earlier in this thread. Haven't properly field tested this yet but so far seems to work great. Only issue is that it resets to default zero values every time the camera is turned off. Garry I wonder if you could walk me through installing the Toggler script and possibly having this feature bound to a hard button? (new to all this)
I did try installing the script (after loading the LUA module) but couldn't find your script anywhere in the menu, although on booting the camera if appears to load ok.
Cheers,
Dino.
@MrFurious70
I wrote the Toggler script to run in the background, i.e. There are no menus.
To use just pres the PLAY button followed by the INFO button, this puts you in interactive mode. The toggler should show at the top middle.
You toggle through your preset states using PLAY and MENU.
Once you reach a state you want to toggle, press INFO to exit toggler and set that state.
Toggler is designed for you to rewrite to your needs.
Cheers
Garry
Thanks Garry I can't get this to work on the latest build.? ???
It's tricky getting the right timing for the 'play-info' button combination when in live view, and once I get it, it reads 'Exit & Do Nothing' top and center.
p.s. I'm using 1TOG2.lua
You should be using the latest nightly Lua fix experimental build.
I don't understand what you mean by getting the timing right
All you need to do is press PLAY then, with no timing sensitivity, INFO
If you are seeing 'Exit & Do Nothing' you are in interactive mode.
Now press MENU and PLAY to move through your presets.
Once you find a preset that you wish to change, then press INFO, this will toggle that state according to your scripting and exit interactive mode. Pressing PLAY twice will give you normal PLAY.
1TOG2 is the right script.
Have you read and changed the script to your needs.
The default toggler script runs with my Focus Bar script, although toggler should run if FB is not loaded, i.e. the FB menu toggles are ignored.
Cheers
Garry
Many thanks Garry. Yes I did open the script in a text editor and saw the usage info. I think the reason it's not working is I'm not using the experimental build... I simply dropped the script into the latest nightly build. Will give this another try with the experimental.
cheers,
Dino.
Hi,
on my EOS is firmware 1.2.
I would like to update my firmware and install ML.
But i cant update from my sd card, files are on card, but eos m cant find them.
dont know whats wrong.
please help.
thank you
"Files"?
Format card using your cam, copy file EOSM1202.FIR to card and retry.
If it doesn't work try card with capacity < 32 GB.
Report back.
Hi everyone. First time post and glad to be here.
I seem to be getting a grid of colored dot/cubes on my raw footage. Does anyone know what this is and how I can get rid of them??
(http://thumb.ibb.co/mBEWaR/Screen_Shot_2017_12_21_at_10_10_47_AM.png) (http://ibb.co/mBEWaR)
blogger image hosting (http://imgbb.com/)
Known issue: Do a search for PDR or "focus pattern" or "focus pixels". User dfort cornered this one well.
http://www.magiclantern.fm/forum/index.php?topic=16054.0
All tools recently discussed in http://www.magiclantern.fm/forum/index.php?board=54.0 are able to deal with it.
Hello, just posting in case it may interest somebody here.
After buying a second hand M, I quickly realized that the lack of shutter remote really annoyed me. Unfortunately ML+ mic trigger didn't cut it for me.
I then made this : https://www.thingiverse.com/thing:2524414
(http://stuff.knackes.com/dld/201712/IMG_2017-09-09_00-02-57-500_680EA1F5.jpg)
(http://stuff.knackes.com/dld/201712/IMG_2017-09-09_00-01-36-500_E33C1E3E.jpg)
The 3D printed part fits on the EOS M and permits to send IR trigger signal directly to the IR sensor of the M.
To emit the IR I use a Wemos D1 Mini ESP8266 board and a 940nm IR led.
Hi,
i tried a card smaller than 32GB.
My Camera says there is no firmware on card to update. Why?
I formated sd card in camera and copied the firmware 202 on card.
please help if you can.
Best regards Markus
I've just tested build magiclantern-crop_rec_4k.2017Dec19.EOSM202.zip and it's amazing, 2.5K RAW video (altough with some limitations given SD card write speed).
Did some shots, in case anyone is interested you can check video here https://youtu.be/YcKTqGJUTls (https://youtu.be/YcKTqGJUTls)
Great stuff going on with the EOSM.
Tip - to post a YouTube video change the URL from https to http and enclose it in youtube tags like this:
[youtube]http://youtu.be/YcKTqGJUTls[/youtube]
Quote from: dfort on December 30, 2017, 01:08:47 AM
Tip - to post a YouTube video change the URL from https to http and enclose it in youtube tags like this:
[youtube]http://youtu.be/YcKTqGJUTls[/youtube]
Thanks, didn't know that.
Good day,
I have an M6 and wanted to know if Magiclantern can help me get a Clean HDMI out for video.
Thanks
Hello all,
I read all posts on EOSM and what I understood is that current capabilities are :
MV1080p possible with H264 proxy enabled
Lossless is possible.
My question is : Can we record in MV1080 with 1720*972 (no crop mode) in 10 bits lossless and with H264 proxy with a low bitrate (say 0.6x) ?
If this works, let me say this little camera would become a killer camera like the 100D !
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.
Quote from: dfort on January 02, 2018, 09:01:42 PM
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
Quote from: dfort on January 02, 2018, 09:49:31 PM
Try it and you'll see what I mean.
Sent from my iPhone using Tapatalk
Sorry, I'm asking it because I don't have an EOSM but I'm very interesting in it. This is the reason I can't test it to understand the problem. I'm planning to buy one, but I'm waiting for an EOS-M VAF-filter first (I asked mosaic engineering for that).
Got it, thought you picked one up.
I see you've got a 5D3 and 7D. Don't expect that the EOSM can compete with those camera but it is a pretty cool little camera that can do about 80% of the ML tricks. A VAF-filter will help with mv720 and crop_rec which use 5x3 and 3x3 sampling respectively but a practical way to record mv1080 on the EOSM isn't possible yet. 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.
(https://farm9.staticflickr.com/8083/29503000355_42450fdbe5.jpg) (https://flic.kr/p/LX5A8V)
If nothing else, it is a great little timelapse machine. Shooting timelapse in photo mode technically give you better than 4K resolution.
Quote from: dfort on January 03, 2018, 01:54:49 AM
... 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 :)
I'm currently using crop_rec_4k branch, that allows using full buffer 2512? pixels horizontal resolution in 1:1 crop mode, but as pretty much in all modes on EOS M at 30 fps and as you wrote i indeed need to use FPS override to get to 24 fps (and that has it's own set of problems regarding rolling shutter and exposure time).
Can you elaborate how to record in this mv1080crop mode?
I found only this table, but i don't know how to activate it http://www.magiclantern.fm/forum/index.php?topic=5601.msg194406#msg194406 (http://www.magiclantern.fm/forum/index.php?topic=5601.msg194406#msg194406)
(Also I presume, that maximum resolution stays at 1872x1060?)
Quote from: dfort on January 03, 2018, 01:54:49 AM
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.
Wow, very cool Dfort ! I didn't understand these possibilities !! With a wide lens, that can be fabulous ! For the mv1080crop mode, I suppose it's a 3x factor ? Do we record in 10 bits or lossless 10/12/14 bits for continuous ?
@12georgiadis:
"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!
Quote from: IDA_ML on January 03, 2018, 02:00:08 PM
@12georgiadis:
"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!
Thanks IDA_ML! It convinced me for a 100D!
Envoyé de mon iPhone en utilisant Tapatalk
Hello,
I am new to ML so sorry if this question is already answered.
If I remove ML from a SD card by formatting it is the shutterbug also gone or is it persistent?
Thanks
Short answer, the shutter-bug isn't persistent.
The shutter-bug only happens on certain cards when ML is loaded and you are using an EF-M zoom lens (don't know if it is the zoom or the IS that is causing this). There are a few workarounds but the easiest is to use a SanDisk Extreme 32GB or smaller SD card. Others might or might not work. It is important that the card not be over 32GB.
(https://farm5.staticflickr.com/4766/25926305528_9f5c3df788_m.jpg)
Hey EOSM users. How about testing a new build that gets you up to 2520x1080 raw video or 1920x1080 continuous? Check out this post on the crop_rec on steroids topic:
https://www.magiclantern.fm/forum/index.php?topic=19300.msg196350#msg196350
New test build posted on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) that resolves the black bar on the right issue with using FPS override with the Exact of Low Jello option like in this video by @loknar
how do you do it?
Quote from: Teamsleepkid on January 26, 2018, 08:22:44 AM
how do you do it?
You mean get into zoom mode on the EOSM? Press the INFO button until you see the magnifying glass on the bottom right of the screen and press it to get into 5x zoom mode. Then when you go to the raw settings you'll have these huge resolution options.
If you mean how do I code--when I was a kid I used to stick various objects into electrical outlets to see what would happen. That's pretty much it.
Quote from: dfort on January 26, 2018, 03:38:13 PM
when I was a kid I used to stick various objects into electrical outlets to see what would happen. That's pretty much it.
Ha, ha, Dfort, my 3-years old grandson does this all the time and despite the fact that his father replaced the fuses with fast automatic ones, I am scared to death when I see that. Maybe, one day he will become a good code writer, who knows ... ? :-)))
By the way, how do you get continuous recording at 1920x1080 on the EOS-M? Does it have write speeds of about 45 MB/s. Do you use the 8 ... 11bit LL mode and do you underexpose? If yes, how many stops? I only get about 29 s. on the 100D at these settings and about 40 s. if I underexpose by one stop. Mine writes at 41,6 MB/s on a fast card.
I'm at work today and don't have any camera with me so I can't confirm it but I believe that setting zoom mode at 1920x1080 in 8..11bit lossless compression should give you continuous recording. The EOSM and 100D have pretty much the same card write speed but a fast card is still needed. I use 32GB Sandisk Extreme Pro (95 MB/s) cards on the EOSM because of the shutter-bug issue and they also seem to perform better for video than the larger and/or slower cards.
I don't underexpose. If anything, when shooting raw I expose as far to the right as possible--before clipping/pink highlights. Yes, there are situations where overexposing will stop the recording or maybe even crashes ML but too much underexposure creates other problems.
On my 700D x5 crop mode at 1920x1080 in 8..11bit lossless, 23.976 fps the continuous recording depending on the how much detailed scenes you shoot and maybe ISO also.
Sometimes I get continuous recording sometimes didn't but I still have long recording times about 30 second to 3 minutes or more (It's depend). So It's not 100% continuous.
BTW I use 32GB Sandisk Extreme Pro 95mb/s.
EDIT: With audio of course, mlv_snd turned on.
very cool and not trying to downplay it at all but the problem with this mode is its impossible to use it for filmmaking because you can't really frame. theres no live view just the choppy 6fps preview looking thing. if we could see real time the frame then it would be useful. I used to shoot 1920x800 with it on the previous builds which would be best best res before but never used it because shooting 1800x768 in crop mode was wiser to frame and use. if somebody could get it so we could see the framing in real time this would be the best cheapest small camera on earth for filmmaking at this time. 2 cents
Quote from: a1ex on April 29, 2016, 10:16:32 AM
Just thought this one might be interesting for EOS M users:
Quote from: a1ex on April 29, 2016, 08:29:56 AM
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
Finally got it working in QEMU!
If you can compile from source, please give it a try and report back.
Quote from: a1ex on February 02, 2018, 03:34:04 PM
If you can compile from source, please give it a try and report back.
Yes! Great feature. Like the little animated progress indicator on the bottom right of the screen when you do the long press.
I wanted to see if QEMU shows that progress indicator but I've never been able to get the EOSM to show the Canon menus, much less the ML menus.
[EDIT] Tried the latest QEMU changes that includes a fix for the EOSM/EOSM2 (https://bitbucket.org/hudson/magic-lantern/commits/90f702cde5dc45dc112164556fb300ab3045fce7) menus but I still can't get it working. Compiling like this from the qemu-eos directory (noticed that changed recently):
make -C ../magic-lantern EOSM_install_qemu
Also add CONFIG_QEMU=y to enable the menu browsing hack (only needed for M and M2), then open ML menu directly from the date/time dialog.
Hum, thought I read somewhere that CONFIG_QEMU=y is applied when compiling with EOSM_install_qemu option.
In any case, just tried it again and it never gets to the GUI. Just a blank grey QEMU screen.
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.
Quote from: garry23 on February 02, 2018, 06:56:55 PM
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.
Right, you need to use the touch screen to get into the submenus. The Set and Q button are combined on the EOSM and the "longpress" branch decodes a short press as Set and long press as Q. Don't know if that accessable from lua.
@dfort
Yes I knew that, but thought I was reading that Q was now accessible on the EOSM.
BTW I have faked it via keypress event, i.e. hyjacking a key, but, I don't have many keys on the EOSM and I'm already hyjacking most of them in my Toggler script.
The Q trick was done shortly after the latest lua_fix build; I was just necroposting that old experiment, since I now had the tools to look into it. Will include it in the next one.
@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" ? Here it starts at the date/time dialog and can navigate Canon menu from there; if loading ML compiled with CONFIG_QEMU=y from the qemu branch, I can also navigate ML menu from the same screen (opened with the delete key).
To test longpress in qemu:
# platform/EOSM.202
hg up longpress -C
hg merge qemu
make clean
make install_qemu CONFIG_QEMU=y
The CONFIG_QEMU option is explained here: https://bitbucket.org/hudson/magic-lantern/src/qemu/contrib/qemu/README.rst?fileviewer=file-view-default#rst-header-config-qemu
and plain "make install_qemu" means "regular build, but copy it on the virtual card used for QEMU, not on the SD card".
@a1ex
Thanks.
BTW I also noticed that the DOF reporting looks and is 'wrong' in the latest fix, but I thought you had added in the new maths?
Diffraction is wrong on the EOSM I looked at.
Cheers
Garry
Quick check: "hg diff -r ec86da538297 -r lua_fix src/focus.c" shows no differences since I've included your fix, and "hg diff -r ec86da538297 -r crop_rec_4k src/focus.c" only shows a change relevant to 100D.
So, I don't expect any changes since including your fix, but I didn't double-check the math either. If you have some numeric example, I can check that in QEMU too (can fake lens data - aperture, focal length, etc, by editing the MPU messages).
@a1ex
Just checked the source and you still appear to have the uncorrected math in there.
Which changeset did you check?
https://bitbucket.org/hudson/magic-lantern/src/ec86da538297/src/focus.c#focus.c-121 - with your fix (https://bitbucket.org/hudson/magic-lantern/commits/ec86da538297)
https://bitbucket.org/hudson/magic-lantern/src/lua_fix/src/focus.c#focus.c-121
https://bitbucket.org/hudson/magic-lantern/src/crop_rec_4k/src/focus.c#focus.c-121
They are identical.
@a1ex
I looked at the source in the latest Lua fix.
In there the diffraction, for example, is presented in the old way.
Here are the changes I put in:
- // 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 micron
As I say, looks like the latest Lua fix source doesn't use the tenth of a micron approach, to get round the integer math.
I may have spotted an error in a dropped zero.
Assuming aperture is in tenths, the new diffraction approach, which drops the mag term, should have one less zero than the old one, ie to get it in tenths.
const uint64_t diff = (244*freq*lens_info.aperture/1000000; // Diffraction blur at infinity in tenths of a micron
This should be:
const uint64_t diff = (244*freq*lens_info.aperture/100000; // Diffraction blur at infinity in tenths of a micron
I spotted the error as ML is reporting diffraction or 0 to 1ish, ie a magnitude out.
Sorry for the typo.
But note the Lua fix source shouldn't be using the mag term: hence I think something is wrong.
Comparing to https://gist.github.com/pigeonhill/ee60d0c23b27273c0445bf1846c258a5 and the PR (https://bitbucket.org/hudson/magic-lantern/pull-requests/831) (found the two versions to be identical)
I did add a closing bracket, compared to your version, since it did not compile without it, but that's the only change I did.
@a1ex
It may be me as I'm going to the Lua Fix branch and looking in the source here: https://bitbucket.org/hudson/magic-lantern/src/97b73e7a781e78f3364555c5c30afbd3c0e5cae8/src/focus.c?at=unified&fileviewer=file-view-default
Anyway, there is an error in the diffraction equation. It needs to read this:
const uint64_t diff = (244*freq*lens_info.aperture/100000; // Diffraction blur at infinity in tenths of a micron
Quote from: a1ex on February 02, 2018, 07:55:25 PM
@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" ?
No, I always get a blank grey screen. Here is the log (https://pastebin.com/9mx6Ytxu). Looks like something around here might be a problem:
[ 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] ####################################
Tried with patches.gdb, as mentioned in the guide (https://bitbucket.org/hudson/magic-lantern/src/qemu/contrib/qemu/README.rst#rst-header-running-canon-firmware)?
@a1ex
Just confirmed that this commit https://bitbucket.org/hudson/magic-lantern/commits/ec86da538297c4299d3154a2e7ed7bbd56056254 has a typo error as I indicated above.
Thus with the error the diffraction is not converted to tenths of a micron, but stays in microns. Thus at the end instead of being converted back to microns, from tenths, it is incorrectly converted.
You can check this yourself by looking at the ML reported diffraction in the ML menu.
A simple fix, which I hope you can incorporate when next you update things.
This shows me the weakness of me not being able to compile myself, so I can check things. I 'just' recoded and submitted, with the error.
So this is the correct code:
const uint64_t diff = (244*freq*lens_info.aperture/100000; // Diffraction blur at infinity in tenths of a micron
I had installed ML 202 Feb 4 2018 build a day ago and have been shooting stills with EF-S 55-250mm STM. I have an EF-M 18-55mm STM as well so I wanted to test it for shutterbug. I am using SanDisk Ultra Plus SDXC 64GB and shot about 30+ stills with EF-M but no sign of shutterbug yet.
Can someone guide me on how to recreate shutterbug? Just trying to see if the above SD card can be cleared from the shutterbug list.
(https://thumb.ibb.co/i48yYS/IMG_20180305_223711.jpg) (https://ibb.co/i48yYS)
Quote from: a1ex on February 02, 2018, 07:55:25 PM
@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" ?
Looks like I zoned out on this. Tried to get the EOSM QEMU combination again to see if the "SET" while powering on camera (https://www.magiclantern.fm/forum/index.php?topic=21765.msg198829#msg198829) issue could be reproduced in QEMU. I still can't get to the GUI much less the ML menus on the EOSM in QEMU. The lua_fix branch has the EOSM menu hack (https://bitbucket.org/hudson/magic-lantern/commits/90f702cde5dc45dc112164556fb300ab3045fce7) so it should work, right? Compiled with CONFIG_QEMU = y
./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
Quote from: kiru on March 06, 2018, 05:02:57 AM
Can someone guide me on how to recreate shutterbug?
Your EF-M 18-55mm and that card that you're using should show the shutter-bug. It doesn't always show up right away. Shoot some stills, restart the camera, delete your CR2 files, restart the camera, change your ML configuration, change it back, restart the camera, eventually the filesystem will become fragmented and the shutter-bug will most likely show up. Format the card in camera and the shutter-bug might go away but it will most likely return with that lens/card combination.
More about the shutter-bug:
https://bitbucket.org/hudson/magic-lantern/issues?q=shutter-bug
https://www.magiclantern.fm/forum/index.php?topic=21728.0
Quote from: a1ex on February 02, 2018, 07:55:25 PM
I still can't get to the GUI much less the ML menus on the EOSM in QEMU.
You no longer need the menu hack for emulating the EOS M's (I should probably remove it), but you do need to run with patches.gdb. Also disable raw features before getting into LiveView, as these are not emulated well. Then, press the L key 3 times, then keep the down arrow key pressed for ~ 1 second to open ML menu. That should do the trick.
Sample magic.cfg with raw histogram and fast zebras disabled:
hist.type = 1
zebra.colorspace = 0
To emulate the unified branch, which doesn't (yet) use a physical key for opening submenus, add this to patches.gdb:
# remap the PLAY button (P) to submenu key in ML
break *0xFF0CC6EC
commands
silent
set $r4 = -0xFFFE
set $pc = 0xFF0CC6F0
c
end
https://builds.magiclantern.fm/EOSM-202.html -> test results (with the above patches)
BTW - is that Focus menu really empty? nothing works from there?
This is what the EOSM focus menu looks like on the camera.
(https://farm1.staticflickr.com/807/39168036360_a8d0f93f5a.jpg) (https://flic.kr/p/22F9qBJ)
(https://farm1.staticflickr.com/808/39168036130_959ecb29bc.jpg) (https://flic.kr/p/22F9qxL)
I still can't get into anything on QEMU with the EOSM but I'm seeing things I've never seen before on the EOSM2 (https://www.magiclantern.fm/forum/index.php?topic=15895.msg198855#msg198855).
[EDIT] The important thing is if others can reproduce this issue (https://www.magiclantern.fm/forum/index.php?topic=21765.msg198829#msg198829) in either QEMU or in camera.
My log looks like this:
./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 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)
15: 40.960 [STARTUP] InitializeIntercom
16: 41.216 [STARTUP] InitializeIntercom End(0x0)
17: 41.984 [PROPAD] SerialFlash Packages!! 0x7
30: 48.640 [DL] dlMain : Start
33: 48.896 [DL] PROP_ACTIVE_SWEEP_MODE (1)
[MPU] Received: 0a 08 03 57 10 33 00 01 00 00 (PROP 8003005E - spell #4)
[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 01 1d 21 84 00 00 (unknown - PROP_PICTURE_STYLE)
[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 : 0a 08 03 58 00 00 00 00 00 00 (PROP 8003005F)
[MPU] Sending : 06 05 03 5a 02 00 (PROP 80030060)
[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] Received: 0a 08 03 06 00 00 00 00 00 00 (PROP_AVAIL_SHOT - spell #5)
[MPU] Sending : 0a 08 03 2f 00 00 00 00 00 00 (PROP_SPECIAL_OPTION)
[MPU] Received: 06 04 03 10 00 00 (PROP 80030008 - spell #6)
[MPU] Sending : 06 05 03 20 01 00 (PROP_STARTUP_CONDITION)
[MPU] Received: 06 05 03 07 ff 00 (PROP_BURST_COUNT - spell #7)
[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] Received: 06 05 01 2e 01 00 (PROP_SAVE_MODE - spell #8)
[MPU] Received: 0a 08 03 0b 00 00 00 00 00 00 (PROP 80030007 - spell #9)
[DMA5] Copy [0xFF892D90] -> [0x01E00000], length [0x00065BD4], flags [0x00000001]
[DMA5] OK
[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] Sending : 06 05 01 2e 01 00 (PROP_SAVE_MODE)
[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)
[MPU] Received: 22 20 03 3b 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 (unnamed - spell #10)
[MPU] Received: 06 05 04 0e 01 00 (PROP 8002000D - spell #11)
101: 43.520 [RSC] hMemoryQueue (0xA20012) hStorageQueue (0xA40014)
102: 44.544 [RSC] ### LIST 5 0 5 ###
167: 56.832 [SND] Seq LPC fin
193: 58.368 [ENG] [ENGIO](Addr:0x41400000, Data:0x 44000)
209: 72.704 [FM] FM_RegisterSpaceNotifyCallback
213: 72.704 [AUDIO] [GPS] GPS_RegisterSpaceNotifyCallback
217: 72.960 [FM] FM_RegisterSpaceNotifyCallback
219: 72.960 [TERMINATE] SHUTDOWN init comp
221: 72.960 [TERMINATE] Abort init comp
253: 75.008 [MC] [MC] PROP_HEADPHONE_VOLUME_VALUE : 0
254: 75.008 [MC] [MC] PROP_MOVIE_PLAY_VOLUME : 10
259: 75.264 [MC] regist master CardCover
[MPU] Received: 08 07 01 2a 1b e6 00 00 (PROP_CARD2_FILE_NUMBER - spell #12)
[MPU] Received: 06 05 03 07 05 00 (PROP_BURST_COUNT - spell #13)
[MPU] Received: 0a 08 03 06 00 00 04 56 00 00 (unknown - PROP_AVAIL_SHOT)
[MPU] Received: 06 05 03 11 01 00 (PROP_ICU_AUTO_POWEROFF - spell #15)
[MPU] Received: 06 05 02 0a 00 00 (PROP_PERMIT_ICU_EVENT - spell #16)
[MPU] Sending : 06 05 01 2c 02 00 (PROP_CURRENT_MEDIA)
[MPU] Received: 06 05 03 0d 00 00 (PROP_CARD2_RECORD - spell #17)
[MPU] Sending : 12 10 03 00 b8 00 00 3a 07 00 00 00 00 00 00 00 00 00 (PROP 80030000)
[MPU] Received: 06 05 03 0c 00 00 (PROP_CARD1_RECORD - spell #18)
[MPU] Sending : 06 05 03 23 19 00 (unnamed)
[MPU] Sending : 06 05 03 04 00 00 (PROP_POWER_KIND)
[MPU] Sending : 1e 1d 03 24 45 46 2d 53 31 37 2d 35 35 6d 6d 20 66 2f 32 2e 38 20 49 53 20 55 53 4d 00 00 (PROP_LENS_NAME)
303: 89.856 [PRP] M:B8 F:0 L:0 P:3A T:7
304: 90.112 [STARTUP] update coded version.
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #19)
[MPU] Sending : 06 04 03 25 00 00 (unnamed)
[MPU] Sending : 24 23 03 15 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 21 00 00 (PROP_LENS)
[MPU] Sending : 24 22 03 3c 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 00 (PROP 8003003C)
[MPU] Sending : 06 05 03 5d 8e 00 (PROP 80030062)
[MPU] Sending : 24 23 03 15 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 21 00 00 (PROP_LENS)
[MPU] Sending : 06 05 01 3d 00 00 (PROP_TEMP_STATUS)
[MPU] Sending : 06 05 03 37 00 00 (PROP_MIRROR_DOWN_IN_MOVIE_MODE)
[MPU] Sending : 06 05 04 06 05 00 (PROP_DEFAULT_LV_MANIP)
[MPU] Sending : 06 05 03 0d 00 00 (PROP_CARD2_RECORD)
[MPU] Sending : 06 05 03 0c 00 00 (PROP_CARD1_RECORD)
[MPU] Received: 06 05 09 11 01 00 (PROP_LV_DISPSIZE - spell #20)
[MPU] Received: 12 11 09 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (PROP 80050020 - spell #21)
[MPU] Received: 14 13 09 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (unnamed - spell #22)
[MPU] Received: 06 05 01 5a 00 00 (PROP_CONTINUOUS_AF_VALID - spell #23)
[MPU] Received: 06 05 09 2f 01 00 (unnamed - spell #24)
[MPU] Sending : 06 05 01 59 01 00 (PROP_MOVIE_SERVO_AF)
[MPU] Received: 14 13 09 25 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (unnamed - spell #25)
[MPU] Received: 06 05 01 5a 01 00 (PROP_CONTINUOUS_AF_VALID - spell #26)
[MPU] Sending : 06 05 01 59 01 00 (PROP_MOVIE_SERVO_AF)
[MPU] Received: 0a 08 09 1a 00 00 00 00 00 00 (PROP 8005002A - spell #27)
[MPU] Received: 0a 08 09 24 00 00 00 00 00 00 (unnamed - spell #28)
[MPU] Received: 08 06 03 18 00 00 00 00 (PROP 8003000F - spell #29)
[MPU] Received: 08 06 03 1f 00 00 00 00 (PROP 80030019 - spell #30)
[MPU] Sending : 06 05 01 58 00 00 (PROP_VIDEOSNAP_MODE)
[MPU] Received: 06 05 03 13 00 00 (PROP_LOGICAL_CONNECT - spell #31)
[MPU] Received: 06 05 03 1e 00 00 (PROP 8003001A - spell #32)
[MPU] Received: 06 05 01 8a 00 00 (PROP_SW2_MOVIE_START - spell #33)
[MPU] Received: 08 06 03 1f 00 00 00 00 (PROP 80030019 - spell #34)
[MPU] Sending : 06 05 01 8a 00 00 (PROP_SW2_MOVIE_START)
[MPU] Received: 0a 08 01 3b ff ff 00 00 00 00 (PROP_USBDEVICE_CONNECT - spell #35)
[MPU] Received: 0a 08 01 3b ff 00 00 00 00 00 (PROP_USBDEVICE_CONNECT - spell #36)
[MPU] Sending : 06 05 03 38 8f 00 (PROP 80030035)
348: 131.328 [MR] mvrChangeAckCBR : Video - Mode=0, Type=0, Rate=24, GOP=12
391: 139.264 [LVDTS] WARN First Get DTS_GetAllRandomData
392: 139.520 [LVDTS] WARN First Get DTS_GetAllRandomData
400: 140.800 SPECIAL_OPTION AF MOVIE GERO OFF
406: 141.312 [LVDTS] WARN First Get DTS_GetAllRandomData
407: 141.312 [LVDTS] WARN First Get DTS_GetAllRandomData
408: 141.312 [LVDTS] WARN First Get DTS_GetAllRandomData
411: 141.312 [LVDTS] WARN First Get DTS_GetAllRandomData
412: 141.312 [LVDTS] WARN First Get DTS_GetAllRandomData
414: 141.312 [LVDTS] WARN First Get DTS_GetAllRandomData
415: 141.312 [LVDTS] WARN First Get DTS_GetAllRandomData
420: 141.568 [LVDTS] WARN First Get DTS_GetAllRandomData
421: 141.568 [LVDTS] WARN First Get DTS_GetAllRandomData
422: 141.568 [LVDTS] WARN First Get DTS_GetAllRandomData
423: 141.824 [LVGMT] PROP_LV_PROHIBIT_OUTPUT 0 0
424: 141.824 [LVDTS] WARN First Get DTS_GetAllRandomData
426: 141.824 [LVGMT] PROP_LV_CFILTER[0][0]
427: 141.824 [LVGMT] PROP_LV_CENTER_OF_DIORAM_CFILTER[2684][1793]
431: 142.336 [LVDTS] WARN First Get DTS_GetAllRandomData
432: 142.592 [LVDTS] WARN First Get DTS_GetAllRandomData
441: 144.384 [LVCOM] InitializeLiveViewDefectDetection
442: 144.896 [LVCOM] ExecuteDefectMarge Start
443: 144.896 [LVCOM] ExecuteDefectMarge End
448: 80.128 [LVDTS] WARN First Get DTS_GetAllRandomData
449: 80.128 [LVDTS] WARN First Get DTS_GetAllRandomData
462: 150.272 [AF] Ratio:30 Reboot:2 !!!
464: 150.528 [LV] PROP_LV_BLOCK PROP_LV_UNBLOCKING 0
475: 153.344 [AUDIO] RegisterCBRSDIOCableConnect
503: 156.928 [WFT] PROP_ADAPTER_DEVICE_ACTIVE: Can Not Change(0) Connect(0)
541: 161.280 [PTP] PSI UnlockTransImg : Trans List is NULL
542: 161.280 [PTP] PSI TarminateTransImgList : SessionTarget [1]
543: 161.280 [PTP] PSI TarminateTransImgList : Trans List is NULL
546: 161.536 [PTP] PSI UnlockTransImg : Trans List is NULL
547: 161.536 [PTP] PSI TarminateTransImgList : SessionTarget [10]
548: 161.536 [PTP] PSI TarminateTransImgList : Trans List is NULL
550: 161.536 [PTP] PSI DisconnectViewFinder
557: 162.048 [PTP] PROP_SCREEN_SAVER 0
560: 162.304 [PTPCOM] SetPtpTransportResources:0,323d
562: 162.560 [PTP] PSI UnlockTransImg : Trans List is NULL
563: 162.816 [PTP] PSI TarminateTransImgList : SessionTarget [10]
564: 162.816 [PTP] PSI TarminateTransImgList : Trans List is NULL
594: 100.352 [WFT] Regist PropCBR PROP_WFT_BLUETOOTH
SD: Unknown CMD1
[SDIO] Error
SD: Unknown CMD1
[SDIO] Error
SD: Unknown CMD1
[SDIO] Error
627: 131.072 [SD] ERROR SDINTREP=0x00000000
628: 131.328 [SD] ERROR UNEXPECTED ERROR
[MPU] Received: 0a 08 03 06 00 00 00 0b 00 00 (unknown - PROP_AVAIL_SHOT)
655: 240.640 [FM] FileNo (DriveNo = 2, 0 <-> 7142)
656: 240.640 [FM] FreeCluster (DriveNo = 2, 11628 <-> 932093)
[MPU] Received: 08 07 01 2a 1b e6 00 00 (PROP_CARD2_FILE_NUMBER - spell #37)
[MPU] Received: 08 07 01 2a 1b e6 00 00 (PROP_CARD2_FILE_NUMBER - spell #37)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #39)
[MPU] Received: 1e 1c 01 4e 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 (PROP_VIDEO_MODE - spell #40)
[MPU] Sending : 1e 1c 01 4e 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 (PROP_VIDEO_MODE)
[MPU] Received: 1e 1c 01 4e 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 (PROP_VIDEO_MODE - spell #40)
[MPU] Sending : 06 05 01 53 01 00 (PROP_AF_DURING_RECORD)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #42)
[MPU] Sending : 06 05 01 58 00 00 (PROP_VIDEOSNAP_MODE)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #42)
[MPU] Sending : 06 05 01 59 01 00 (PROP_MOVIE_SERVO_AF)
[MPU] Received: 06 05 02 0a 01 00 (PROP_PERMIT_ICU_EVENT - spell #44)
[MPU] Sending : 06 05 01 49 01 00 (PROP_LIVE_VIEW_AF_SYSTEM)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #45)
[MPU] Sending : 1e 1c 01 4e 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 (PROP_VIDEO_MODE)
[MPU] Received: 06 05 04 00 00 00 (NotifyGUIEvent - spell #46)
696: 250.112 [FM] [GPS] GPS_Initialize (36, 25)
772: 190.976 [DP] LOGICAL_CONNECT [0x00000000]
774: 190.976 [PROPAD] ERROR GetPropertyData ID (0) = 0x02050038
775: 190.976 [PRP] ERROR NOT FOUND PROPERTY ID = 0x02050038 L:2411
776: 190.976 [DP] PROP_WIFI_SETTING [0]
796: 259.840 WARN localI2C_Read : 377
797: 260.352 WARN localI2C_Read : 377
798: 260.608 WARN localI2C_Read : 377
799: 260.864 WARN localI2C_Read : 377
800: 261.120 WARN localI2C_Read : 377
801: 261.120 WARN localI2C_Read : 377
802: 261.376 [HDMI] cec_initialize_reg_set : END
803: 261.376 WARN localI2C_Read : 377
804: 261.632 WARN localI2C_Read : 377
805: 261.888 WARN localI2C_Read : 377
806: 261.888 [HDMI] Logical Address Set : End
807: 261.888 [HDMI] CEC DEVICE SETUP
808: 261.888 [HDMI] InitializeHDMI
815: 268.032 [IMPP] H264E InitializeH264EncodeFor1080pDZoom
816: 268.032 [IMPP] H264E InitializeH264EncodeFor1080p25fpsDZoom
1051: 288.768 [MR_MOV] (Empty Func) MVW_RegisterXmpDataCallback
1065: 289.280 [HDMI] CEC OFF
1083: 290.560 [STARTUP] startupInitializeComplete
1086: 290.560 [MC] guimode comp. 0
1101: 291.072 [MC] guimode comp. 0
1148: 295.168 [MR] mvrChangeAckCBR : Video - Mode=0, Type=0, Rate=24, GOP=12
1157: 231.936 [LVDTS] WARN First Get DTS_GetAllRandomData
1158: 231.936 [LVDTS] WARN First Get DTS_GetAllRandomData
[MPU] Received: 08 06 04 0c 03 00 00 00 (PROP_SHOOTING_TYPE - spell #53)
[MPU] Received: 06 05 03 1d 1f 00 (unknown - PROP_BATTERY_REPORT)
1176:[MPU] Sending : 06 05 01 53 01 00 (PROP_AF_DURING_RECORD)
[MPU] Received: 06 05 08 06 ff 00 (unknown - COM_FA_CHECK_FROM)
244.480 [MR] mvrChangeAckCBR : Video - Mode=0, Type=0, Rate=24, GOP=12
[MPU] Sending : 06 05 01 58 00 00 (PROP_VIDEOSNAP_MODE)
[MPU] Sending : 06 05 01 59 01 00 (PROP_MOVIE_SERVO_AF)
1183: 247.2[MPU] Sending : 06 05 01 49 01 00 (PROP_LIVE_VIEW_AF_SYSTEM)
96 [LVDTS] WARN First Get DTS_GetAllRandomData
1184: 247.296 [LVDTS] WARN First Get DTS_GetAllRandomData
[MPU] Sending : 06 05 06 11 01 00 (GUI_SWITCH)
[MPU] Sending : 06 05 06 12 00 00 (GUI_SWITCH)
[MPU] Sending : 46 45 0a 08 ff 1f 01 00 00 00 00 00 00 00 01 03 50 20 28 01 01 00 60 04 01 04 87 00 00 00 00 00 00 01 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 00 00 (PD_NotifyOlcInfoChanged)
[MPU] Sending : 08 06 01 04 00 00 00 00 (PROP_AF_MODE)
[MPU] Sending : 06 05 03 37 00 00 (PROP_MIRROR_DOWN_IN_MOVIE_MODE)
[MPU] Sending : 06 05 04 00 00 01 (NotifyGUIEvent)
[MPU] Sending : 08 06 04 0c 03 00 01 00 (PROP_SHOOTING_TYPE)
1230: 261.888 [MC] guimode comp. 0
[MPU] Received: 08 06 00 00 04 00 00 00 (Complete WaitID = 0x80020000 - spell #47)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 04 04 13 00 00 (unknown - PROP 80020012)
[DMA5] Copy [0xFFA14DDC] -> [0xD0288000], length [0x00006E74], flags [0x00000001]
[DMA5] OK
[DMA5] Copy [0xFFA1BC50] -> [0xD0280000], length [0x000001C0], flags [0x00000001]
[DMA5] OK
[DMA5] Copy [0xFFA1BE10] -> [0x01E80000], length [0x00001A28], flags [0x00000001]
[DMA5] OK
[MPU] Received: 08 06 00 00 04 0c 00 00 (unknown - Complete WaitID)
[MPU] Received: 14 13 09 25 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (unnamed - spell #25)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #39)
[MPU] Received: 06 04 09 00 00 00 (unknown - PROP_LV_LENS)
[MPU] Received: 06 05 09 0b 02 00 (unknown - PROP_LV_AF_RESULT)
[MPU] Received: 0a 08 09 24 ff ff 00 00 00 00 (unknown - unnamed)
[MPU] Received: 06 05 0e 00 01 00 (unknown - unnamed)
1271: 265.984 [RSC] ###!! Lv or MovieRec (X 48000064)18:0
1272: 265.984 [RSC] ###!! Lv or MovieRec (46000064)
1279: 267.264 [LVDTS] WARN First Get DTS_GetAllRandomData
1280: 267.264 [LVDTS] WARN First Get DTS_GetAllRandomData
1281: 267.520 [LVDTS] WARN First Get DTS_GetAllRandomData
1286: 267.776 [LVDTS] WARN First Get DTS_GetAllRandomData
1287: 267.776 [LVDTS] WARN First Get DTS_GetAllRandomData
1288: 267.776 [LVDTS] WARN First Get DTS_GetAllRandomData
1292: 267.776 [LVDTS] WARN First Get DTS_GetAllRandomData
1293: 267.776 [LVDTS] WARN First Get DTS_GetAllRandomData
1294: 267.776 [LVDTS] WARN First Get DTS_GetAllRandomData
1306: 269.312 [LVDTS] WARN First Get DTS_GetAllRandomData
1307: 269.312 [LVDTS] WARN First Get DTS_GetAllRandomData
1308: 269.312 [LVDTS] WARN First Get DTS_GetAllRandomData
1312: 269.824 [LVDTS] WARN First Get DTS_GetAllRandomData
1325: 270.592 [LVDTS] WARN First Get DTS_GetAllRandomData
1326: 270.848 [LVDTS] WARN First Get DTS_GetAllRandomData
1328: 271.104 [LVDTS] WARN First Get DTS_GetAllRandomData
1329: 271.360 [LVDTS] WARN First Get DTS_GetAllRandomData
1331: 271.616 [LVDTS] WARN First Get DTS_GetAllRandomData
1333: 271.872 [LVICV] LVICV_SetResource Rsc:0 Img:0
1428: 350.720 [TCH]ERROR TouchPanelIC Ack Error
Key event: 32 -> 0001
[MPU] Sending : 06 05 06 00 01 00 (GUI_SWITCH)
[MPU] Received: 06 05 04 00 01 00 (NotifyGUIEvent - spell #46)
[MPU] Sending : 06 05 04 00 01 01 (NotifyGUIEvent)
[MPU] Received: 08 06 00 00 04 00 00 00 (Complete WaitID = 0x80020000 - spell #47)
1468: 1335.552 [MC] guimode comp. 1
1477: 1336.832 [LVDTS] WARN First Get DTS_GetAllRandomData
1482: 1337.856 [LVDTS] WARN First Get DTS_GetAllRandomData
1483: 1338.112 [LVEVF] ERROR [VRAM]VRAM_SDV_SetSenserDriveParameter FrameData==NULL)
1489: 1340.928 [LVICV] LVICV_ReleaseResource
1490: 1340.928 [LVCOM] ERROR [ADST] ADST_ReleaseMemAddrArray(16):Failed
1495: 1341.440 [LVDTS] WARN First Get DTS_GetAllRandomData
1575: 1368.320 [DISP] MuteONImage (1470)
1580: 1368.576 [PTP] PSI DisconnectViewFinder
1583: 1471.744 [LVDTS] WARN First Get DTS_GetAllRandomData
[MPU] Received: 06 05 03 19 00 00 (unknown - PROP_TFT_STATUS)
or, with lua_fix and CONFIG_QEMU=y (keys pressed: L L L, followed by down arrow pressed for 1 second):
./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)
- 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 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 : 0x6BE60
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 0x11d240 (1167936)
[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: FBE3A (task id 20002)
[BOOT] autoexec.bin loaded at 9E1E0 - 11D240.
[BOOT] reserved 520288 bytes for ML (used 520288)
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 FBE3A.
[****] Starting task ff0f34a4(47e82c) Startup
[****] Starting task ff0c357c(0) Startup2
[DMA1] Copy [0xF8099000] -> [0x40540200], length [0x00000F84], flags [0x00030001]
[DMA1] OK
[DMA1] Copy [0xF8F00000] -> [0x40541400], length [0x0001132C], flags [0x00030001]
[DMA1] OK
[****] Starting task ff0c28c8(0) TaskMain
[****] Starting task 22138(47e530) DbgMgr
[EEPROM-DMA]! [0x340000] -> [0x40480000] (0xBD820 bytes)
0: 41.728 [STARTUP]
K331 ICU Firmware Version 2.0.2 ( 9.9.8 )
8: 45.312 [PROPAD] SerialFlash Packages!! 0x340000
[****] Starting task ff341390(0) PowerMgr
[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
13: 53.760 [PROPAD] SerialFlash Packages!! 0x7
15: 53.760 [PROPAD] PROPAD_CreateFROMPropertyHandle DRAMAddr 0x4fe00000
16: 54.528 [PROPAD] SerialFlash Packages!! 0x10000
[EEPROM-DMA]! [0x10000] -> [0x4FE00000] (0x191570 bytes)
[EEPROM-DMA]! [0x10000] -> [0x4FE00000] (0x0 bytes)
18: 60.928 [PROPAD] SerialFlash Packages!! 0x7
[****] Starting task 22138(5a4750) PropMgr
[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(5aed88) EventMgr
[****] Starting task ff0cb890(0) HotPlug
22: 62.720 [STARTUP] InitializeIntercom
23: 62.976 [STARTUP] InitializeIntercom End(0x0)
33: 69.632 [DL] dlMain : Start
36: 70.144 [DL] PROP_ACTIVE_SWEEP_MODE (1)
[MPU] Received: 0a 08 03 57 10 33 00 01 00 00 (PROP 8003005E - spell #4)
[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 01 1d 21 84 00 00 (unknown - PROP_PICTURE_STYLE)
[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 : 0a 08 03 58 00 00 00 00 00 00 (PROP 8003005F)
[MPU] Sending : 06 05 03 5a 02 00 (PROP 80030060)
[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)
[****] Starting task 22138(5af3b0) FileMgr
[****] Starting task 22138(6cfcc0) FileCache
[****] Starting task 22138(6d00c0) RscMgr
[MPU] Sending : 0a 08 03 2f 00 00 00 00 00 00 (PROP_SPECIAL_OPTION)
[MPU] Received: 0a 08 03 06 00 00 00 00 00 00 (PROP_AVAIL_SHOT - spell #5)
[MPU] Sending : 0a 08 03 2f 00 00 00 00 00 00 (PROP_SPECIAL_OPTION)
[MPU] Received: 06 04 03 10 00 00 (PROP 80030008 - spell #6)
[MPU] Sending : 06 05 03 20 01 00 (PROP_STARTUP_CONDITION)
[MPU] Received: 06 05 03 07 ff 00 (PROP_BURST_COUNT - spell #7)
[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] Received: 06 05 01 2e 01 00 (PROP_SAVE_MODE - spell #8)
[****] Starting task 21a30(6d4554) ShootCapture
[MPU] Received: 0a 08 03 0b 00 00 00 00 00 00 (PROP 80030007 - spell #9)
[DMA5] Copy [0xFF892D90] -> [0x01E00000], length [0x00065BD4], flags [0x00000001]
[DMA5] OK
[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] Sending : 06 05 01 2e 01 00 (PROP_SAVE_MODE)
[MPU] Sending : 06 05 04 06 05 00 (PROP_DEFAULT_LV_MANIP)
[****] Starting task ff4166fc(0) systemtask
[****] Starting task 21a30(6e9ab0) ShootBlack
[****] Starting task 21a30(6ee410) ShootPreDevelop
[****] Starting task 22138(6ee664) SAF
[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)
[****] Starting task 22138(6ee6b4) SAF_CROSSTALK
[****] Starting task ff0cee8c(0) MainCtrl
[MPU] Received: 22 20 03 3b 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 (unnamed - spell #10)
[MPU] Received: 06 05 04 0e 01 00 (PROP 8002000D - spell #11)
[****] Starting task 21a30(6ef0e4) TOMgr
[****] Starting task 21a30(6f0298) Fstorage
[****] Starting task 22138(6f1510) HDRMgr
[****] Starting task 21a30(6f1698) HDRStage
[****] Starting task 22138(6f3b14) GISMgr
[****] Starting task 21a30(6f3ca8) GISStage
[****] Starting task ff144e74(0) AEmodeJudge
[****] Starting task ff4f550c(0) CSMgrTask
104: 64.512 [RSC] hMemoryQueue (0xA20012) hStorageQueue (0xA40014)
105: 65.792 [RSC] ### LIST 5 0 5 ###
170: 79.616 [SND] Seq LPC fin
196: 81.152 [ENG] [ENGIO](Addr:0x41400000, Data:0x 44000)
212: 93.696 [FM] FM_RegisterSpaceNotifyCallback
216: 93.952 [AUDIO] [GPS] GPS_RegisterSpaceNotifyCallback
220: 93.952 [FM] FM_RegisterSpaceNotifyCallback
222: 94.208 [TERMINATE] SHUTDOWN init comp
224: 94.208 [TERMINATE] Abort init comp
256: 97.536 [MC] [MC] PROP_HEADPHONE_VOLUME_VALUE : 0
257: 97.536 [MC] [MC] PROP_MOVIE_PLAY_VOLUME : 10
262: 98.048 [MC] regist master CardCover
[MPU] Received: 08 07 01 2a 1b e6 00 00 (PROP_CARD2_FILE_NUMBER - spell #12)
[****] Starting task 21a30(6f653c) FrontShtDevelop
[****] Starting task 21a30(6f68b0) DianaFrontShtDevelop
[MPU] Received: 06 05 03 07 05 00 (PROP_BURST_COUNT - spell #13)
[****] Starting task 21a30(6f6d08) RearShtDevelop
[****] Starting task 21a30(6f6eec) DianaRearShtDevelop
[****] Starting task 21a30(6f7138) ShootSsDevelop
[****] Starting task 21a30(6f74b0) ShootVfx
[MPU] Received: 0a 08 03 06 00 00 04 56 00 00 (unknown - PROP_AVAIL_SHOT)
[MPU] Received: 06 05 03 11 01 00 (PROP_ICU_AUTO_POWEROFF - spell #15)
[MPU] Received: 06 05 02 0a 00 00 (PROP_PERMIT_ICU_EVENT - spell #16)
[MPU] Sending : 06 05 01 2c 02 00 (PROP_CURRENT_MEDIA)
[MPU] Received: 06 05 03 0d 00 00 (PROP_CARD2_RECORD - spell #17)
[MPU] Sending : 12 10 03 00 b8 00 00 3a 07 00 00 00 00 00 00 00 00 00 (PROP 80030000)
[MPU] Received: 06 05 03 0c 00 00 (PROP_CARD1_RECORD - spell #18)
[MPU] Sending : 06 05 03 23 19 00 (unnamed)
[MPU] Sending : 06 05 03 04 00 00 (PROP_POWER_KIND)
[MPU] Sending : 1e 1d 03 24 45 46 2d 53 31 37 2d 35 35 6d 6d 20 66 2f 32 2e 38 20 49 53 20 55 53 4d 00 00 (PROP_LENS_NAME)
[****] Starting task ff0d8260(0) GuiLockTask
306: 112.640 [PRP] M:B8 F:0 L:0 P:3A T:7
307: 112.896 [STARTUP] update coded version.
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #19)
[MPU] Sending : 06 04 03 25 00 00 (unnamed)
[MPU] Sending : 24 23 03 15 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 21 00 00 (PROP_LENS)
[MPU] Sending : 24 22 03 3c 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 00 (PROP 8003003C)
[MPU] Sending : 06 05 03 5d 8e 00 (PROP 80030062)
[MPU] Sending : 24 23 03 15 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 21 00 00 (PROP_LENS)
[MPU] Sending : 06 05 01 3d 00 00 (PROP_TEMP_STATUS)
[MPU] Sending : 06 05 03 37 00 00 (PROP_MIRROR_DOWN_IN_MOVIE_MODE)
[MPU] Sending : 06 05 04 06 05 00 (PROP_DEFAULT_LV_MANIP)
[MPU] Sending : 06 05 03 0d 00 00 (PROP_CARD2_RECORD)
[MPU] Sending : 06 05 03 0c 00 00 (PROP_CARD1_RECORD)
[****] Starting task 22138(726c5c) ASIF
[****] Starting task 22138(726dac) AudioCtrl
[****] Starting task 22138(72b5f0) SoundEffect
[****] Starting task 22138(72c400) MovWriter
[****] Starting task 22138(72caf8) MovieRecorder
[****] Starting task 22138(744124) MoviePlay
[****] Starting task ff1e6754(0) AviRead
[****] Starting task 22138(74441c) MovReader
[****] Starting task 22138(7446b4) LVC_DEV
[****] Starting task ff0f99a8(0) LVC_FACE
[****] Starting task 22138(7456dc) Gmt
[MPU] Received: 06 05 09 11 01 00 (PROP_LV_DISPSIZE - spell #20)
[MPU] Received: 12 11 09 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (PROP 80050020 - spell #21)
[MPU] Received: 14 13 09 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (unnamed - spell #22)
[MPU] Received: 06 05 01 5a 00 00 (PROP_CONTINUOUS_AF_VALID - spell #23)
[MPU] Received: 06 05 09 2f 01 00 (unnamed - spell #24)
[MPU] Sending : 06 05 01 59 01 00 (PROP_MOVIE_SERVO_AF)
[****] Starting task 22138(75c320) Evf
[MPU] Received: 14 13 09 25 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (unnamed - spell #25)
[MPU] Received: 06 05 01 5a 01 00 (PROP_CONTINUOUS_AF_VALID - spell #26)
[MPU] Sending : 06 05 01 59 01 00 (PROP_MOVIE_SERVO_AF)
[****] Starting task 22138(767838) Epp
[****] Starting task 22138(76add8) LVFACE
[****] Starting task 22138(76b04c) LVICV
[****] Starting task 22138(76b2e8) CLR_CALC
[****] Starting task 22138(76cbd4) AeWb
[MPU] Received: 0a 08 09 1a 00 00 00 00 00 00 (PROP 8005002A - spell #27)
[MPU] Received: 0a 08 09 24 00 00 00 00 00 00 (unnamed - spell #28)
[MPU] Received: 08 06 03 18 00 00 00 00 (PROP 8003000F - spell #29)
[MPU] Received: 08 06 03 1f 00 00 00 00 (PROP 80030019 - spell #30)
[MPU] Sending : 06 05 01 58 00 00 (PROP_VIDEOSNAP_MODE)
[MPU] Received: 06 05 03 13 00 00 (PROP_LOGICAL_CONNECT - spell #31)
[MPU] Received: 06 05 03 1e 00 00 (PROP 8003001A - spell #32)
[MPU] Received: 06 05 01 8a 00 00 (PROP_SW2_MOVIE_START - spell #33)
[MPU] Received: 08 06 03 1f 00 00 00 00 (PROP 80030019 - spell #34)
[MPU] Sending : 06 05 01 8a 00 00 (PROP_SW2_MOVIE_START)
[MPU] Received: 0a 08 01 3b ff ff 00 00 00 00 (PROP_USBDEVICE_CONNECT - spell #35)
[MPU] Received: 0a 08 01 3b ff 00 00 00 00 00 (PROP_USBDEVICE_CONNECT - spell #36)
[MPU] Sending : 06 05 03 38 8f 00 (PROP 80030035)
[****] Starting task ff10cd40(0) SoundDevice
[****] Starting task 22138(72b4f4) AudioLevel
[****] Starting task ff203358(0) TestGero
[****] Starting task 21a30(787d8c) GaUSB20Drv
[****] Starting task ff285ae8(0) USBTrns
[****] Starting task ff28757c(0) SDIOTrns
[****] Starting task ff283c10(78a908) PTPSessionTASK
[****] Starting task 21a30(7ab800) PtpDps
[****] Starting task 22138(806bf8) Ceres
[****] Starting task 21a30(80b554) Remote
[****] Starting task 21a30(82a498) Fcreate
351: 88.576 [MR] mvrChangeAckCBR : Video - Mode=0, Type=0, Rate=24, GOP=12
394: 96.768 [LVDTS] WARN First Get DTS_GetAllRandomData
395: 96.768 [LVDTS] WARN First Get DTS_GetAllRandomData
403: 98.304 SPECIAL_OPTION AF MOVIE GERO OFF
409: 98.816 [LVDTS] WARN First Get DTS_GetAllRandomData
410: 98.816 [LVDTS] WARN First Get DTS_GetAllRandomData
411: 98.816 [LVDTS] WARN First Get DTS_GetAllRandomData
414: 98.816 [LVDTS] WARN First Get DTS_GetAllRandomData
415: 98.816 [LVDTS] WARN First Get DTS_GetAllRandomData
417: 98.816 [LVDTS] WARN First Get DTS_GetAllRandomData
418: 98.816 [LVDTS] WARN First Get DTS_GetAllRandomData
423: 99.072 [LVDTS] WARN First Get DTS_GetAllRandomData
424: 99.072 [LVDTS] WARN First Get DTS_GetAllRandomData
425: 99.328 [LVDTS] WARN First Get DTS_GetAllRandomData
426: 99.328 [LVGMT] PROP_LV_PROHIBIT_OUTPUT 0 0
427: 99.328 [LVDTS] WARN First Get DTS_GetAllRandomData
429: 99.328 [LVGMT] PROP_LV_CFILTER[0][0]
430: 99.328 [LVGMT] PROP_LV_CENTER_OF_DIORAM_CFILTER[2684][1793]
434: 100.096 [LVDTS] WARN First Get DTS_GetAllRandomData
435: 100.096 [LVDTS] WARN First Get DTS_GetAllRandomData
444: 102.144 [LVCOM] InitializeLiveViewDefectDetection
445: 102.656 [LVCOM] ExecuteDefectMarge Start
446: 102.912 [LVCOM] ExecuteDefectMarge End
450: 103.168 [LVDTS] WARN First Get DTS_GetAllRandomData
451: 103.168 [LVDTS] WARN First Get DTS_GetAllRandomData
465: 108.544 [AF] Ratio:30 Reboot:2 !!!
467: 108.544 [LV] PROP_LV_BLOCK PROP_LV_UNBLOCKING 0
478: 112.384 [AUDIO] RegisterCBRSDIOCableConnect
506: 116.480 [WFT] PROP_ADAPTER_DEVICE_ACTIVE: Can Not Change(0) Connect(0)
544: 121.600 [PTP] PSI UnlockTransImg : Trans List is NULL
545: 121.856 [PTP] PSI TarminateTransImgList : SessionTarget [1]
546: 121.856 [PTP] PSI TarminateTransImgList : Trans List is NULL
549: 121.856 [PTP] PSI UnlockTransImg : Trans List is NULL
550: 121.856 [PTP] PSI TarminateTransImgList : SessionTarget [10]
551: 121.856 [PTP] PSI TarminateTransImgList : Trans List is NULL
553: 122.112 [PTP] PSI DisconnectViewFinder
560: 122.624 [PTP] PROP_SCREEN_SAVER 0
563: 122.624 [PTPCOM] SetPtpTransportResources:0,323d
565: 122.880 [PTP] PSI UnlockTransImg : Trans List is NULL
566: 122.880 [PTP] PSI TarminateTransImgList : SessionTarget [10]
567: 122.880 [PTP] PSI TarminateTransImgList : Trans List is NULL
597: 125.440 [WFT] Regist PropCBR PROP_WFT_BLUETOOTH
SD: Unknown CMD1
[SDIO] Error
SD: Unknown CMD1
[SDIO] Error
SD: Unknown CMD1
[SDIO] Error
630: 155.648 [SD] ERROR SDINTREP=0x00000000
631: 155.648 [SD] ERROR UNEXPECTED ERROR
658: 187.392 [FM] FileNo (DriveNo = 2, 0 <-> 7142)
659: 187.392 [FM] FreeCluster (DriveNo = 2, 11628 <-> 932093)
[MPU] Received: 0a 08 03 06 00 00 00 0b 00 00 (unknown - PROP_AVAIL_SHOT)
[****] Starting task 21a30(8b4da4) Fwrite
[****] Starting task 22138(8b550c) Sound
[MPU] Received: 08 07 01 2a 1b e6 00 00 (PROP_CARD2_FILE_NUMBER - spell #37)
[MPU] Received: 08 07 01 2a 1b e6 00 00 (PROP_CARD2_FILE_NUMBER - spell #37)
[****] Starting task 21a30(8b4b58) Fread
[****] Starting task 22138(8b52c8) Voice
[****] Starting task 22138(8b5624) WavReader
[****] Starting task 22138(8b5b08) Gps
[****] Starting task 21a30(8cfb9c) ShootArtFilter
[****] Starting task 22138(944a6c) TouchMgr
[****] Starting task 22138(944c48) DisplayMgr
[****] Starting task ff0d72a0(0) GuiMainTask
[****] Replacing task ff0d72a0 with ac6b0
[****] Starting task ff239654(0) ImgPlayDrv
[****] Starting task ff327478(0) CtrlSrv
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #39)
[****] Starting task 22138(8cc94c) ReDevelop
[****] Starting task 22138(8cc9f0) DpMgr
[****] Starting task ff24ede0(0) DpsReceiveTask
[****] Starting task 22138(8cecc8) DpImgEditMgr
[****] Starting task 22138(8ceeec) InnerDevelopMgr
[****] Starting task 22138(945cd4) CEC
[****] Starting task ff31ba90(0) EyeFi
[MPU] Received: 1e 1c 01 4e 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 (PROP_VIDEO_MODE - spell #40)
[MPU] Sending : 1e 1c 01 4e 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 (PROP_VIDEO_MODE)
[MPU] Received: 1e 1c 01 4e 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 (PROP_VIDEO_MODE - spell #40)
[MPU] Sending : 06 05 01 53 01 00 (PROP_AF_DURING_RECORD)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #42)
[MPU] Sending : 06 05 01 58 00 00 (PROP_VIDEOSNAP_MODE)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #42)
[MPU] Sending : 06 05 01 59 01 00 (PROP_MOVIE_SERVO_AF)
[MPU] Received: 06 05 02 0a 01 00 (PROP_PERMIT_ICU_EVENT - spell #44)
[MPU] Sending : 06 05 01 49 01 00 (PROP_LIVE_VIEW_AF_SYSTEM)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #45)
[MPU] Sending : 1e 1c 01 4e 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 (PROP_VIDEO_MODE)
[****] Starting task ff492674(0) PTPtoFAPI_EventProcTask
[****] Starting task 22138(8cc42c) Mrk
[MPU] Received: 06 05 04 00 00 00 (NotifyGUIEvent - spell #46)
[****] Starting task 22138(847454) MetaCtg
[****] Starting task ff1df3b8(0) LpfMode
699: 194.816 [FM] [GPS] GPS_Initialize (36, 25)
775: 201.472 [DP] LOGICAL_CONNECT [0x00000000]
777: 201.728 [PROPAD] ERROR GetPropertyData ID (0) = 0x02050038
778: 201.728 [PRP] ERROR NOT FOUND PROPERTY ID = 0x02050038 L:2411
779: 201.728 [DP] PROP_WIFI_SETTING [0]
799: 207.104 WARN localI2C_Read : 377
800: 207.360 WARN localI2C_Read : 377
801: 207.616 WARN localI2C_Read : 377
802: 208.128 WARN localI2C_Read : 377
803: 208.384 WARN localI2C_Read : 377
804: 208.896 WARN localI2C_Read : 377
805: 208.896 [HDMI] cec_initialize_reg_set : END
806: 209.408 WARN localI2C_Read : 377
807: 209.664 WARN localI2C_Read : 377
808: 210.176 WARN localI2C_Read : 377
809: 210.176 [HDMI] Logical Address Set : End
810: 210.176 [HDMI] CEC DEVICE SETUP
811: 210.688 [HDMI] InitializeHDMI
818: 221.440 [IMPP] H264E InitializeH264EncodeFor1080pDZoom
819: 221.696 [IMPP] H264E InitializeH264EncodeFor1080p25fpsDZoom
1054: 242.688 [MR_MOV] (Empty Func) MVW_RegisterXmpDataCallback
1068: 243.200 [HDMI] CEC OFF
1086: 244.224 [STARTUP] startupInitializeComplete
1089: 244.480 [MC] guimode comp. 0
1104: 244.992 [MC] guimode comp. 0
1152: 249.344 [MR] mvrChangeAckCBR : Video - Mode=0, Type=0, Rate=24, GOP=12
1160: 251.648 [LVDTS] WARN First Get DTS_GetAllRandomData
1161: 251.648 [LVDTS] WARN First Get DTS_GetAllRandomData
[MPU] Received: 08 06 04 0c 03 00 00 00 (PROP_SHOOTING_TYPE - spell #53)
[MPU] Received: 06 05 03 1d 1f 00 (unknown - PROP_BATTERY_REPORT)
[MPU] Sending : 06 05 01 53 01 00 (PROP_AF_DURING_RECORD)
[MPU] Received: 06 05 08 06 ff 00 (unknown - COM_FA_CHECK_FROM)
1179: 264.192 [MR] mvrChangeAckCBR : Video - Mode=0, Type=0, Rate=24, GOP=12
[MPU] Sending : 06 05 01 58 00 00 (PROP_VIDEOSNAP_MODE)
[MPU] Sending : 06 05 01 59 01 00 (PROP_MOVIE_SERVO_AF)
1186:[MPU] Sending : 06 05 01 49 01 00 (PROP_LIVE_VIEW_AF_SYSTEM)
267.264 [LVDTS] WARN First Get DTS_GetAllRandomData
1187: 267.264 [LVDTS] WARN First Get DTS_GetAllRandomData
[MPU] Sending : 06 05 06 11 01 00 (GUI_SWITCH)
[MPU] Sending : 06 05 06 12 00 00 (GUI_SWITCH)
[MPU] Sending : 46 45 0a 08 ff 1f 01 00 00 00 00 00 00 00 01 03 50 20 28 01 01 00 60 04 01 04 87 00 00 00 00 00 00 01 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 00 00 (PD_NotifyOlcInfoChanged)
[MPU] Sending : 08 06 01 04 00 00 00 00 (PROP_AF_MODE)
[MPU] Sending : 06 05 03 37 00 00 (PROP_MIRROR_DOWN_IN_MOVIE_MODE)
[MPU] Sending : 06 05 04 00 00 01 (NotifyGUIEvent)
[MPU] Sending : 08 06 04 0c 03 00 01 00 (PROP_SHOOTING_TYPE)
1233: 282.368 [MC] guimode comp. 0
[MPU] Received: 08 06 00 00 04 00 00 00 (Complete WaitID = 0x80020000 - spell #47)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 04 04 13 00 00 (unknown - PROP 80020012)
[DMA5] Copy [0xFFA14DDC] -> [0xD0288000], length [0x00006E74], flags [0x00000001]
[DMA5] OK
[DMA5] Copy [0xFFA1BC50] -> [0xD0280000], length [0x000001C0], flags [0x00000001]
[DMA5] OK
[DMA5] Copy [0xFFA1BE10] -> [0x01E80000], length [0x00001A28], flags [0x00000001]
[DMA5] OK
[MPU] Received: 08 06 00 00 04 0c 00 00 (unknown - Complete WaitID)
[MPU] Received: 14 13 09 25 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (unnamed - spell #25)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #39)
[MPU] Received: 06 04 09 00 00 00 (unknown - PROP_LV_LENS)
[MPU] Received: 06 05 09 0b 02 00 (unknown - PROP_LV_AF_RESULT)
[MPU] Received: 0a 08 09 24 ff ff 00 00 00 00 (unknown - unnamed)
[MPU] Received: 06 05 0e 00 01 00 (unknown - unnamed)
1274: 285.696 [RSC] ###!! Lv or MovieRec (X 48000064)18:0
1275: 285.952 [RSC] ###!! Lv or MovieRec (46000064)
1282: 286.720 [LVDTS] WARN First Get DTS_GetAllRandomData
1283: 286.720 [LVDTS] WARN First Get DTS_GetAllRandomData
1284: 286.720 [LVDTS] WARN First Get DTS_GetAllRandomData
1289: 286.976 [LVDTS] WARN First Get DTS_GetAllRandomData
1290: 286.976 [LVDTS] WARN First Get DTS_GetAllRandomData
1291: 286.976 [LVDTS] WARN First Get DTS_GetAllRandomData
1295: 287.232 [LVDTS] WARN First Get DTS_GetAllRandomData
1296: 287.232 [LVDTS] WARN First Get DTS_GetAllRandomData
1297: 287.232 [LVDTS] WARN First Get DTS_GetAllRandomData
1307: 288.512 [LVDTS] WARN First Get DTS_GetAllRandomData
1308: 288.512 [LVDTS] WARN First Get DTS_GetAllRandomData
1309: 288.512 [LVDTS] WARN First Get DTS_GetAllRandomData
1313: 289.024 [LVDTS] WARN First Get DTS_GetAllRandomData
1326: 289.792 [LVDTS] WARN First Get DTS_GetAllRandomData
1327: 290.048 [LVDTS] WARN First Get DTS_GetAllRandomData
1329: 290.304 [LVDTS] WARN First Get DTS_GetAllRandomData
1330: 290.560 [LVDTS] WARN First Get DTS_GetAllRandomData
1332: 291.072 [LVDTS] WARN First Get DTS_GetAllRandomData
1334: 291.328 [LVICV] LVICV_SetResource Rsc:0 Img:0
[****] Starting task 9ecb4(0) ml_init
1430: 369.920 [TCH]ERROR TouchPanelIC Ack Error
Lens moving (0, 0)
[****] Starting task 9ea30(0) ml_backup
[****] Starting task a6578(0) menu_task
[****] Starting task a911c(0) menu_redraw_task
[****] Starting task b2110(0) bitrate_task
[****] Starting task bd604(0) focus_task
[****] Starting task bdfe0(0) notifybox_task
[****] Starting task c10e4(0) fps_task
[****] Starting task c82f8(0) shoot_task
[****] Starting task c4c38(0) clock_task
[****] Starting task cedbc(0) audio_common_task
[****] Starting task d59d4(0) livev_hiprio_task
[****] Starting task d4744(0) cls_task
[****] Starting task e0588(0) console_task
[****] Starting task ab7b4(0) debug_task
[****] Starting task b337c(0) tweak_task
[****] Starting task bde24(0) focus_misc_task
[****] Starting task ca43c(0) vignetting_init
[****] Starting task e5d14(0) module_task
[****] Starting task d5570(0) livev_loprio_task
Scanning modules...
Load modules...
Linking..
Register modules...
Load configs...
Init modules...
Updating symbols...
[i] 404: edmac_format_size 9fb90
[i] 404: edmac_format_size a1ea0
[i] 404: edmac_format_size aab70
[i] 404: edmac_format_size ac630
[i] 404: dual_iso_get_recovery_iso b4e80
[i] 404: dual_iso_is_active b4e80
[i] 404: auto_ettr_intervalometer_wait c1bf0
[i] 404: auto_ettr_intervalometer_warning c1bf0
[i] 404: auto_ettr_export_correction cc820
[i] 404: dual_iso_get_dr_improvement db2e0
[i] 404: dual_iso_get_recovery_iso db2e0
[i] 404: edmac_format_size df9c0
Modules loaded
updating Movie Tweaks -> Movie Logging
updating Movie Tweaks -> Time Indicator
Key event: 26 -> 2701
[MPU] Sending : 06 05 06 27 01 00 (GUI_SWITCH)
Key event: 26 -> 2701
[MPU] Sending : 06 05 06 27 01 00 (GUI_SWITCH)
[MPU] Received: 08 06 04 0c 00 00 00 00 (PROP_SHOOTING_TYPE - spell #53)
[MPU] Sending : 08 06 04 0c 00 00 01 00 (PROP_SHOOTING_TYPE)
[MPU] Received: 06 05 04 00 00 00 (NotifyGUIEvent - spell #46)
[MPU] Sending : 06 05 04 00 00 01 (NotifyGUIEvent)
[MPU] Received: 08 06 00 00 04 0c 00 00 (unknown - Complete WaitID)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 04 00 00 00 (NotifyGUIEvent - spell #46)
[MPU] Sending : 06 05 04 00 00 01 (NotifyGUIEvent)
[MPU] Received: 08 06 04 0c 03 00 00 00 (PROP_SHOOTING_TYPE - spell #53)
[MPU] Sending : 08 06 04 0c 03 00 01 00 (PROP_SHOOTING_TYPE)
[MPU] Received: 06 04 04 13 00 00 (unknown - PROP 80020012)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 03 19 00 00 (unknown - PROP_TFT_STATUS)
Key event: 26 -> 2701
[MPU] Sending : 06 05 06 27 01 00 (GUI_SWITCH)
[MPU] Received: 08 06 04 0c 00 00 00 00 (PROP_SHOOTING_TYPE - spell #53)
[MPU] Sending : 08 06 04 0c 00 00 01 00 (PROP_SHOOTING_TYPE)
[MPU] Received: 06 05 04 00 00 00 (NotifyGUIEvent - spell #46)
[MPU] Sending : 06 05 04 00 00 01 (NotifyGUIEvent)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 04 00 00 00 (NotifyGUIEvent - spell #46)
[MPU] Sending : 06 05 04 00 00 01 (NotifyGUIEvent)
[MPU] Received: 08 06 04 0c 03 00 00 00 (PROP_SHOOTING_TYPE - spell #53)
[MPU] Sending : 08 06 04 0c 03 00 01 00 (PROP_SHOOTING_TYPE)
[MPU] Received: 06 04 04 13 00 00 (unknown - PROP 80020012)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 03 19 01 00 (PROP_TFT_STATUS - spell #56)
[MPU] Received: 06 05 03 19 00 00 (unknown - PROP_TFT_STATUS)
Default raw buffer OK for 0x727 (0).
raw update from livev_hiprio_task
LV RAW size too small
Key event: 50 -> 1901
[MPU] Sending : 06 05 06 19 01 00 (GUI_SWITCH)
[MPU] Received: 06 05 04 00 06 00 (NotifyGUIEvent - spell #46)
[MPU] Sending : 06 05 04 00 06 01 (NotifyGUIEvent)
Key event: d0 -> 1900
[MPU] Sending : 06 05 06 19 00 00 (GUI_SWITCH)
Log diff (https://a1ex.magiclantern.fm/bleeding-edge/EOS-M/diff-eosm-lua_fix-me-vs-dfort.html).
The ROM is from you:
700154260069474f478dc4904862e4de EOSM/ROM1.BIN
a3eefdfb3f9ed2ab4516423866e56b64 EOSM/SFDATA.BIN
Some messages are in different order; this may indicate a race condition. One way to diagnose these is to run in deterministic emulation mode, with -icount (try -icount 1, -icount 2 ... -icount 10). That way, if we both run with -icount 5, we should get the same execution trace (repeatable). By default, the execution is not deterministic; it just tries to mimic the real-time clock to some extent, and depends a lot on the host CPU speed.
Here, all -icount settings from 1 to 15 are working well; the last ones are too slow to be practical. Try one of them. Unfortunately, we can't set intermediate values, so the issue is hard to debug.
A similar issue happens on 6D: different CPU speeds between my local machine and the build server cause the menu navigation test to pass nearly all the time on mine, and fail (with only one screenshot slightly different, but repeatable) on the server.
Got another suggestion: spell #4 is not recognized in your log. What if you change it in mpu_spells/EOSM.h?
- { { 0x0a, 0x08, 0x03, 0x57, 0x10, 0x33, 0x00, 0x01, 0x00 }, .description = "PROP 8003005E", .out_spells = { /* spell #4 */
+ { { 0x0a, 0x08, 0x03, 0x57, ARG0, ARG1, 0x00, 0x01, 0x00 }, .description = "PROP 8003005E", .out_spells = { /* spell #4 */
That change would match any argument for that property. Our emulated MPU waits for this property in order to send properties 8003005F and 80030060 (whatever these do, I have no idea); yours property 8003005E is set to 0x31. That must be a setting from Canon menu.
edit: maybe not?
FF0F5280:
DebugMsg(129, 3, "PROP_RequestChange PROP_LEO_LENSID 0x%lx Tender 0x%x Ver 0x%x", v6);
prop_request_change(0x8003005E, &v6, 4);
known_spells.py:
"03 57" : (0x8003005E, "PROP_LEO_LENSID", (4, "ARG0"), (5, "ARG1")),
"03 58" : (0x8003005F, "PROP_LEO_LENS_START"),
"03 5a" : (0x80030060, "PROP_LEO_LENS_END"),
Fix committed, let's hope it works :D
Rebuilt qemu with the latest changes, tried the various ROM's and SFDATA files I've got (can't find that exact match), found an -icount setting in run_tests.sh but the tests don't work work on the Mac--basically going down in flames here.
No matter what I do, EOSM emulation comes to a screeching halt on:
[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: 41.728 [PROPAD] SerialFlash Packages!! 0x7
Going back to the reason I tried running the latest lua_fix on QEMU -- if you set the Config option to "SET at startup - Required to load ML" do you see the LED lit on startup?
Yes, I see it. ML turns on the LED at startup, and expects Canon firmware to do some sort of file I/O to turn it off.
./run_canon_fw.sh 700D,firmware="boot=0" -d io |& grep -a LED
[GPIO] at CSMgrTask:FF4E3038:FF74CA58 [0xC022C188] <- 0x138800 : Card LED
[GPIO] at CSMgrTask:FF4E3068:FF74CB10 [0xC022C188] <- 0x838C00 : Card LED
...
[GPIO] at FileMgr:FF4E3038:FF74CA58 [0xC022C188] <- 0x138800 : Card LED
[GPIO] at FileMgr:FF4E3068:FF74CB10 [0xC022C188] <- 0x838C00 : Card LED
...
[GPIO] at MetaCtg:FF4E3038:FF74CA58 [0xC022C188] <- 0x138800 : Card LED
[GPIO] at MetaCtg:FF4E3068:FF74CB10 [0xC022C188] <- 0x838C00 : Card LED
(./run_canon_fw.sh EOSM,firmware="boot=0" -d io -s -S & arm-none-eabi-gdb -x EOSM/patches.gdb) |& grep -a LED
[GPIO] at 0x00102E98:06626400 [0xC022C188] <- 0x83DC00 : Card LED
(./run_canon_fw.sh EOSM,firmware="boot=1" -d io -s -S & arm-none-eabi-gdb -x EOSM/patches.gdb) |& grep -a LED
[GPIO] at 0x00102E98:06626400 [0xC022C188] <- 0x83DC00 : Card LED
[GPIO] at 0x00102824:001028B8 [0xC022C188] <- 0x93D800 : Card LED
[GPIO] at 0x00102830:0010950C [0xC022C188] <- 0x83DC00 : Card LED
[GPIO] at 0x00869E0C:0010E470 [0xC022C188] <- 0x138800 : Card LED <--- here's ML turning on the LED in reboot.c
Yet another EOS M quirk - Canon firmware accessing the SD card without turning on the LED (or maybe the SD LED has a different color and ML has it wrong?)
Some pattern matching will reveal what's going on.
... "boot=0" -d io,debugmsg |& grep CSMgr -a
700D:
[ CSMgrTask:ff74c98c ] (23:01) sdReadBlk: st=0, num=1, buf=0x4082fee0
[GPIO] at CSMgrTask:FF4E3038:FF74CA58 [0xC022C188] <- 0x138800 : Card LED
[ CSMgrTask:ff74b3e8 ] (23:01) sdDMAReadBlk: st=0, num=1
M:
[ CSMgrTask:ff642944 ] (23:01) sdReadBlk: st=0, num=1, buf=0x40845f80
[ CSMgrTask:ff6413a0 ] (23:01) sdDMAReadBlk: st=0, num=1
Looks like the M really accesses the card without turning on the LED, as far as I could tell from the I/O activity. Nevermind, added a LED fade-out feedback if ML is disabled (that will also turn off the LED when it ends).
Quote
No matter what I do, EOSM emulation comes to a screeching halt [...]
May I have a copy of the bad ROM/SFLASH to take a closer look?
Ok--looks like the QEMU issues were due to some bad SFDATA.BIN dumps I've been using. All good now and I can also recreate the issue in QEMU:
(https://farm1.staticflickr.com/808/40989303411_453651f8c8.jpg) (https://flic.kr/p/25s5TRM)
LED indicator in the lower right corner is on in QEMU and on the camera it is solid red.
On the Mac I'm having to press "M" to get out of a grey screen to the menu screen then "L" to get to LiveView then fn + delete to get to the ML menus.
Pulled in the commit that should fix this (https://bitbucket.org/hudson/magic-lantern/commits/8b6b858dd5a7317e3027e3ec10174c7556777ebe) but it is still exhibiting the same behavior on the EOSM.
Really? Mind recording a video? The LED should now fade out after booting...
In QEMU, with that commit it blinks a few times and then stays off.
If that really includes changeset 8b6b858, the result is very surprising. Are you able to see the fade out effect on 700D, for example?
If yes: are you able to see the LED blinks on the M with CONFIG_HELLO_WORLD?
FF4EFD08 led_enable
FF34849C j_led_enable
DebugMsg(36, 3, "LED Permit"); // if PROP_TFT_STATUS is 0 aka display on?
j_led_enable(1);
DebugMsg(36, 3, "LED Prohibit"); // from PROP_SCREEN_SAVER?
j_led_enable(0);
So yeah, Canon code really makes an effort to suppress the LED activity during card access. If I understand well, only when the main display is off?! Why?!
Quote from: a1ex on March 24, 2018, 09:15:35 PM
If that really includes changeset 8b6b858
Oops. Note to self: Make sure to do an "hg update" after an "hg pull" command.
It is working fine on the EOSM, no lingering LED. Starting without loading ML still shows the shutter-bug, darn it. CONFIG_HELLO_WORLD blinks the LED.
Also tested and working fine on the 700D.
Quote from: dfort on March 23, 2018, 06:44:03 PM
Your EF-M 18-55mm and that card that you're using should show the shutter-bug. It doesn't always show up right away. Shoot some stills, restart the camera, delete your CR2 files, restart the camera, change your ML configuration, change it back, restart the camera, eventually the filesystem will become fragmented and the shutter-bug will most likely show up. Format the card in camera and the shutter-bug might go away but it will most likely return with that lens/card combination.
Thanks. I did few photo shoots and videos, however all with default configuration and the memory card is still fresh(not formatted after ML installation). I guess I will need to wait for few more days of usage before the shutterbug kicks in. Will keep this thread posted.
@dfort @kiru
Aren't Sandisk cards known to be immune to this? maybe this model is too
SanDisk Extreme Pro cards
32GB and under are mostly immune though I have had an instance where the shutter-bug showed up on one of these cards too.
I can provide a build that should be able to show the shutter-bug on pretty much any card:
https://www.magiclantern.fm/forum/index.php?topic=21728.msg198456#msg198456
Quote from: kiru on March 26, 2018, 03:46:42 AM
I guess I will need to wait for few more days of usage before the shutterbug kicks in.
Just try this combination:
- Your EF-M 18-55mm STM
- The 64GB card you showed on Reply #1407 (https://www.magiclantern.fm/forum/index.php?topic=9741.msg198141#msg198141)
- Start the camera normally with ML - no need to load any module or change settings. Lens must be mounted on startup.
- Try shooting a still photo, CR2 or JPEG. The shutter-bug doesn't affect movie recording.
I've got a couple of third party EF-M to EF adapters. The top one is a Fotasy and the bottom one a Fotodiox. Note that the Fotasy adapter has a push button. This is an important difference. One of my lenses almost got stuck on the Fotasy adapter. No problems with the Fotodiox adapter.
(https://farm1.staticflickr.com/795/41041220761_1542b7c464.jpg) (https://flic.kr/p/25wEZ5v)
Turns out that the Fotodiox adapter is pretty much identical to the Canon adapter. FYI--buyer beware.
Hi!
Great work being done with the EOSM (and other models) in regards to raw with SD card overclock!
However, I am one of those strange outcasts who is still interested in shooting h264 with ALL-I frames. Has any progress been made in getting GOP controls into the main build?
One big advantage of h264 ALL-I is that it utilizes the entire area of the sensor, so that the character of lenses designed for APS-C/S35 doesn't get obliterated by using a crop mode.
If it is not in the main build, instructions on where to get the code and how to compile it would be greatly appreciated. I have installed the gcc-arm-none-eabi package on my Debian-derived distro, but I am a little rusty on compiling procedures.
As I understand, there is a 3x3 binned raw mode that allows the use of the full width of the sensor. Is that correct? If so, that might work, as long as there is no excessive aliasing/moire nor a pink dot problem. From my scans of the threads, I gather that @dfort has made EOSM pink dot masks, but I am not sure how to apply them.
Thanks!
Hi @tupp
Setting up a development environment on Debian should be very similar to Ubuntu which can be used in the Windows 10 Linux subsystem and there's an entire topic devoted to that (https://www.magiclantern.fm/forum/index.php?topic=20214.0).
A few of us played around with the H.264 settings though I'm not sure if it will give you the ALL-I feature you're looking for.
Seems like there's more interest in raw which is a challenge on the EOSM because it defaults to mv720 mode which samples 3x5. The 3x3 raw mode you're referring to is by using the crop_rec module. Yes, you can use up to the full width of the sensor with that module but the vertical resolution is currently limited.
As far as the "pink dot" a.k.a. "focus pixels" most of the newer MLV apps can process them out automatically so that's no longer a big problem.
@dfort:
Thank you for the prompt reply!
I found where I previously inquired about the All-I/GOP controls in this thread here:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg156491#msg156491
You directed me to another thread in which some of the steps were outlined on compiling the GOP control:
https://www.magiclantern.fm/forum/index.php?topic=15685.msg152612#msg152612
I am unsure on a few things. Is the code mentioned in the thread above included in the source, so all I have to do is uncomment the lines before compiling? If not, where do I paste the lines into the source?
Also, I have read that it is suggested to reset the camera before installing ML. Is this always necessary? Doing so is problematic for me as I run Linux and have picture styles installed -- I would have to get access to a Windows/Mac machine to reinstall those picture styles.
Thanks!
dpjpandone worked on that code and he has moved on to other interests but his build with the All-I/GOP controls is still in his Dropbox (https://www.dropbox.com/s/3d6zpxnndvhxpoa/magiclantern-Nightly.2015Aug21.EOSM202.zip) and his Bitbucket account is still online (https://bitbucket.org/dpjpandone/) though I couldn't find anything related to what you're looking for in there.
The topic you referred to seems pretty clear. Just uncomment this line:
platform/EOSM.202/features.h
//~ #define FEATURE_VIDEO_HACKS // unclean patching
and add these lines:
platform/EOSM.202/Makefile.setup.default
ML_SRC_EXTRA_OBJS = \
video_hacksU.o \I haven't tried it recently but I do remember playing around with it a while back and some of those video hacks did work on the EOSM.
Quote from: tupp on April 24, 2018, 05:07:51 AM
Also, I have read that it is suggested to reset the camera before installing ML. Is this always necessary? Doing so is problematic for me as I run Linux and have picture styles installed -- I would have to get access to a Windows/Mac machine to reinstall those picture styles.
Does clearing the settings remove the picture styles? I'm not sure, I'd have to try it out and see.
Resetting the Canon settings usually isn't necessary. For me I found it sometimes helps after doing a Canon firmware update but otherwise I rarely clear the settings.
Quote from: dfort on April 24, 2018, 07:12:54 AM
dpjpandone worked on that code and he has moved on to other interests but his build with the All-I/GOP controls is still in his Dropbox (https://www.dropbox.com/s/3d6zpxnndvhxpoa/magiclantern-Nightly.2015Aug21.EOSM202.zip) and his Bitbucket account is still online (https://bitbucket.org/dpjpandone/) though I couldn't find anything related to what you're looking for in there.
Thanks for the links!
I have already installed dpjpandone's build and enabled ALL-I and boosted the bitrate to 1.5x. Will test soon, and, if there are no glitches, I will gradually increase the bitrate until the video breaks.
QuoteThe topic you referred to seems pretty clear. Just uncomment this line:
platform/EOSM.202/features.h
//~ #define FEATURE_VIDEO_HACKS // unclean patching
and add these lines:
platform/EOSM.202/Makefile.setup.default
ML_SRC_EXTRA_OBJS = \
video_hacksU.o \
Thank you! So I can uncomment and add said lines to any recent version of ML source code?
QuoteDoes clearing the settings remove the picture styles? I'm not sure, I'd have to try it out and see.
I think it does... it's mentioned in the ML install instructions.
QuoteResetting the Canon settings usually isn't necessary. For me I found it sometimes helps after doing a Canon firmware update but otherwise I rarely clear the settings.
Thanks!!! That was very helpful to know! Saved me a lot of hassle!
I've been trying to push through some firmware updates and running the lua_fix branch Script API Tests on various cameras. The EOSM has always had problems going through these tests so I thought I'd take a closer look at it. Here are the tests that are failing and the specific assert failures within each test.
-- test_camera_gui()
assert(camera.gui.idle == true
-- test_menu()
assert(menu.select("Play mode actions", "Trigger key(s)")); sleep(1)
-- test_camera_take_pics()
assert(camera.gui.play_photo == true)
-- test_lv()
assert(lv.vidmode == "PH-NOLV")
The EOSM will complete the tests if those assert commands are commented out. Now the puzzle to solve is how to get them working properly on the EOSM?
Finally got a perfect score on the selftest module, Stubs API test:
[Pass] is_play_mode() => 0x1
[INFO] Camera model: Canon EOS M 2.0.2 (0x80000331 EOSM)
[Pass] is_camera("DIGIC", "*") => 0x1
[Pass] is_camera(__camera_model_short, firmware_version) => 0x1
[Pass] src = fio_malloc(size) => 0x4de1a084
[Pass] dst = fio_malloc(size) => 0x4e61e090
[Pass] memcmp(dst, src, 4097) => 0x98
[Pass] edmac_memcpy(dst, src, 4097) => 0x4e61e090
[Pass] memcmp(dst, src, 4097) => 0x0
[Pass] edmac_memcpy(dst, src, 4097) => 0x4e61e090
[Pass] memcmp(dst, src, size) => 0x81
[Pass] edmac_memcpy(dst, src, size) => 0x4e61e090
[Pass] memcmp(dst, src, size) => 0x0
[Pass] memcmp(dst, src, size) => 0xb
[Pass] edmac_memcpy_start(dst, src, size) => 0x4e61e090
dt => 0x2971
[Pass] copied => 0x4003f0
[Pass] copied => 0x4003f0
[Pass] copied => 0x4003f0
[Pass] memcmp(dst, src, copied) => 0x0
[Pass] memcmp(dst, src, copied + 16) => 0xffffffaf
edmac_memcpy_finish()
free(src)
free(dst)
Cache test A (EDMAC on BMP buffer)...
[Pass] bmp = bmp_load("ML/CROPMKS/CINESCO2.BMP", 1) => 0x80e894
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x15df
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x0
Cache test B (FIO on 8K buffer)...
[Pass] tries[0] => 0xf9
[Pass] tries[1] => 0x105
[Pass] tries[2] => 0xe6
[Pass] tries[3] => 0x104
[Pass] failr[0] => 0x7c
[Pass] failw[0] => 0xdd
[Pass] failr[1] => 0x75
[Pass] failw[1] => 0x0
[Pass] failr[2] => 0x0
[Pass] failw[2] => 0xc5
[Pass] failr[3] => 0x0
[Pass] failw[3] => 0x0
times[0] / tries[0] => 0x1d
times[1] / tries[1] => 0x1d
times[2] / tries[2] => 0x1d
times[3] / tries[3] => 0x1d
Cache tests finished.
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] f = FIO_CreateFile("test.dat") => 0x3
[Pass] FIO_WriteFile(f, (void*)0xFF000000, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)0xFF000000, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize("test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = (void*)_alloc_dma_memory(0x20000) => 0x408630ec
[Pass] f = FIO_OpenFile("test.dat", O_RDONLY | O_SYNC) => 0x3
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
_free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] buf = fio_malloc(0x1000000) => 0x4de1a084
[Pass] FIO_GetFileSize_direct("test.dat") => 0x82000000
[Pass] f = FIO_OpenFile("test.dat", O_RDWR | O_SYNC) => 0x3
[Pass] FIO_SeekSkipFile(f, 0, SEEK_END) => 0x82000000
[Pass] FIO_WriteFile(f, buf, 0x10) => 0x10
[Pass] FIO_SeekSkipFile(f, -0x20, SEEK_END) => 0x81fffff0
[Pass] FIO_WriteFile(f, buf, 0x30) => 0x30
[Pass] FIO_SeekSkipFile(f, 0x20, SEEK_SET) => 0x20
[Pass] FIO_SeekSkipFile(f, 0x30, SEEK_CUR) => 0x50
[Pass] FIO_SeekSkipFile(f, -0x20, SEEK_CUR) => 0x30
[Pass] FIO_GetFileSize_direct("test.dat") => 0x82000020
[Pass] is_file("test.dat") => 0x1
[Pass] FIO_RemoveFile("test.dat") => 0x0
[Pass] is_file("test.dat") => 0x0
[Pass] SetTimerAfter(0, timer_cbr, overrun_cbr, 0) => 0x15
[Pass] timer_func => 0x2
[Pass] SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0xb746
msleep(900)
[Pass] timer_func => 0x0
msleep(200)
[Pass] timer_func => 0x1
[Pass] ABS((timer_time/1000 - t0) - 1000) => 0x3
[Pass] ABS((timer_arg - ta0) - 1000) => 0xa
[Pass] timer = SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0xb7b0
msleep(400)
CancelTimer(timer)
[Pass] timer_func => 0x0
msleep(1500)
[Pass] timer_func => 0x0
[Pass] SetHPTimerAfterNow(0, timer_cbr, overrun_cbr, 0) => 0x15
[Pass] timer_func => 0x2
[Pass] SetHPTimerAfterNow(100000, timer_cbr, overrun_cbr, 0) => 0x318b0
msleep(90)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x1
[Pass] ABS(DeltaT(timer_time, t0) - 100000) => 0x14e
[Pass] ABS(DeltaT(timer_arg, ta0) - 100000) => 0xfd
[Pass] ABS((get_us_clock() - t0) - 110000) => 0x13f
[Pass] SetHPTimerAfterNow(90000, next_tick_cbr, overrun_cbr, 0) => 0x318b2
msleep(80)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x3
msleep(80)
[Pass] timer_func => 0x3
msleep(20)
[Pass] timer_func => 0x1
[Pass] ABS(DeltaT(timer_time, t0) - 300000) => 0x1d1
[Pass] ABS(DeltaT(timer_arg, ta0) - 300000) => 0x1b3
[Pass] ABS((get_us_clock() - t0) - 310000) => 0x119
t0 = GET_DIGIC_TIMER() => 0xa9407
msleep(250)
t1 = GET_DIGIC_TIMER() => 0xe5c63
[Pass] ABS(MOD(t1-t0, 1048576)/1000 - 250) => 0x3
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x28
Date/time: 2018/05/08 15:53:40
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x29
[Pass] MOD(s1-s0, 60) => 0x1
[Pass] MOD(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x3e460
[Pass] p = (void*)_malloc(50*1024) => 0x1313f0
[Pass] CACHEABLE(p) => 0x1313f0
m1 = MALLOC_FREE_MEMORY => 0x31c50
_free(p)
m2 = MALLOC_FREE_MEMORY => 0x3e460
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x337218
[Pass] p = (void*)_AllocateMemory(128*1024) => 0x8630ac
[Pass] CACHEABLE(p) => 0x8630ac
m1 = GetFreeMemForAllocateMemory() => 0x31720c
_FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x337218
[Pass] ABS((m0-m1) - 128*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x3e460
m02 = GetFreeMemForAllocateMemory() => 0x337218
[Pass] p = (void*)_alloc_dma_memory(128*1024) => 0x408630ec
[Pass] UNCACHEABLE(p) => 0x408630ec
[Pass] CACHEABLE(p) => 0x8630ec
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x408630ec
_free_dma_memory(p)
[Pass] p = (void*)_shoot_malloc(16*1024*1024) => 0x4de1a074
[Pass] UNCACHEABLE(p) => 0x4de1a074
_shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x3e460
m12 = GetFreeMemForAllocateMemory() => 0x337218
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
[Pass] suite = shoot_malloc_suite_contig(16*1024*1024) => 0x131358
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1000000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x131380
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1000000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4de1a070
[Pass] UNCACHEABLE(p) => 0x4de1a070
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite_contig(0) => 0x131358
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1f24000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x131380
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1f24000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x44000064
[Pass] UNCACHEABLE(p) => 0x44000064
largest_shoot_block = suite->size => 0x1f24000
[INFO] largest_shoot_block: 31MB
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(largest_shoot_block + 1024*1024) => 0x131358
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x5
[Pass] suite->size => 0x2024000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x131380
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x13b4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4de1a070
[Pass] UNCACHEABLE(p) => 0x4de1a070
chunk = GetNextMemoryChunk(suite, chunk) => 0x131418
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x17b4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x419ff0a4
[Pass] UNCACHEABLE(p) => 0x419ff0a4
chunk = GetNextMemoryChunk(suite, chunk) => 0x131450
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x189c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4ae00064
[Pass] UNCACHEABLE(p) => 0x4ae00064
chunk = GetNextMemoryChunk(suite, chunk) => 0x131488
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1974000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x45f240e4
[Pass] UNCACHEABLE(p) => 0x45f240e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x1314c0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2024000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x44000064
[Pass] UNCACHEABLE(p) => 0x44000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x2024000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(0) => 0x131358
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x5
[Pass] suite->size => 0x3700000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x131380
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x13b4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4de1a070
[Pass] UNCACHEABLE(p) => 0x4de1a070
chunk = GetNextMemoryChunk(suite, chunk) => 0x131418
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x149c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4ae00064
[Pass] UNCACHEABLE(p) => 0x4ae00064
chunk = GetNextMemoryChunk(suite, chunk) => 0x131450
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x189c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x419ff0a4
[Pass] UNCACHEABLE(p) => 0x419ff0a4
chunk = GetNextMemoryChunk(suite, chunk) => 0x131488
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1974000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x45f240e4
[Pass] UNCACHEABLE(p) => 0x45f240e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x1314c0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x3700000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x44000064
[Pass] UNCACHEABLE(p) => 0x44000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x3700000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x213924
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x213900
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x2138e0
[Pass] bar => '*****hjkl;'
bzero32(bar + 5, 5)
[Pass] bar => '****'
EngDrvOut(LCD_Palette[0], 0x1234)
[Pass] shamem_read(LCD_Palette[0]) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
task_create("test", 0x1c, 0x1000, test_task, 0) => 0xdb9200ca
[Pass] test_task_created => 0x1
[Pass] get_current_task_name() => 'run_test'
[Pass] get_task_name_from_id(current_task->taskId) => 'run_test'
[Pass] task_max => 0x68
[Pass] task_max => 0x68
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0xdb9400b6
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0xdb96021a
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0xdb980036
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_GUI_MODE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_GUI_MODE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_GUI_MODE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(1000);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(1000);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[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
[Pass] is_pure_play_photo_mode() => 0x1
[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
[Pass] is_pure_play_movie_mode() => 0x0
=========================================================
Test complete, 11872 passed, 0 failed.
.
What I did was to check the EOSM stubs against the 700D. The check-stubs.py was useful in finding a few that were different but then I remembered something that happened when I was stub hunting the EOSM2 and found the 700D PlayMain_handler stub looked out of place (https://www.magiclantern.fm/forum/index.php?topic=15895.msg187867#msg187867). Well, that wasn't a mistake. So just now I thought about going the other way and find the 700D stub on the EOSM and it got past this last stubborn failure:
[FAIL] is_pure_play_photo_mode() => 0x0
Looking for confirmation that this makes sense:
platform/EOSM.202/stubs.S
-NSTUB(0xFF3BC078, PlayMain_handler)
+NSTUB(0xFF715BA4, PlayMain_handler)
[EDIT] BTW--This was run on the lua_fix branch. Just found out that the selftest API test from the unified branch will not complete on the EOSM. With or without the PlayMain_handler stub change.
Looks like the EOSM is getting some favorable press thanks to Magic Lantern.
(https://farm1.staticflickr.com/956/28338649898_c4ab134c95.jpg)
https://petapixel.com/2018/05/18/the-original-canon-eos-m-can-shoot-2-5k-raw-video-with-magic-lantern/
Damn it!
That just means the secondhand market adds on a few extra pound.
;) :)
Quote from: dfort on May 19, 2018, 04:42:11 PM
Looks like the EOSM is getting some favorable press thanks to Magic Lantern.
Yeah, I've got like 50 times more traffic on my YT videos with SD UHS hack :o).
I've been curious, what maximum framerate did you achieve with EOS M?
I didn't managed to get past 45 fps, and I'd like to shoot some DualISO 2x24fps video, any tips?
Also can anyone recommend anamorfic lens that are suitable (and not too expensive) for EOS M?
Quote from: dfort on May 19, 2018, 04:42:11 PM
Looks like the EOSM is getting some favorable press thanks to Magic Lantern.
(https://farm1.staticflickr.com/956/28338649898_c4ab134c95.jpg)
https://petapixel.com/2018/05/18/the-original-canon-eos-m-can-shoot-2-5k-raw-video-with-magic-lantern/
I saw that article, can't seem to make sense of the sd uhs install on the EOSM.
I have managed to find it, install, and it completes a few memory patches. From here, I am lost.
Any help ? Is there a step by step for running the hack?
Copy SD_UHS.mo into modules folder of 4k_crop experimental build.
Load sd_uhs.mo in photo mode.
Go to Debug tab and run SD overclock.
Switch to movie mode and record.
Be aware this is risky and is able to do permanent damage to card and camera!
Ceterum censeo experimental build page esse delendam.
Thank you Walter, I have been running the module incorrectly by the sounds of it.
-
After this process, my card appears to remain limited at 40mb write speed.
In other words, no reaction is happening with different cards (in a form of improvement).
I have seen things listed such as blacks 1/5, malloc errors, but I am not sure if I am hitting problems.
If it records, it crashes at 5 seconds or less, but the bottleneck doesn't pass 40mb.
Are you running magiclantern-crop_rec_4k.2018Mar10.EOSM202 as advised?
I am yes, although my initial tests were from a different month. I think the issue was this movie crop vs crop mode.
You'll have to humor me, I have not touched my eos m in years.
What is your status now?
If problem persists post screens of
- sd_uhs after running
- modules tab
- Help tab, highlight on Press Info
Where does one get this module?
Quote from: Walter Schulz on May 21, 2018, 10:44:05 PM
Copy SD_UHS.mo into modules folder of 4k_crop experimental build.
Load sd_uhs.mo in photo mode.
Go to Debug tab and run SD overclock.
Switch to movie mode and record.
Be aware this is risky and is able to do permanent damage to card and camera!
Ceterum censeo experimental build page esse delendam.
@keel - for the SD hack I used files from @Danne's bitbucket page: https://bitbucket.org/Dannephoto/magic-lantern/downloads/ (I hope it's ok to share this, if not I'll delete the link)
I downloaded the "magiclantern-Nightly.2018Apr17.EOSM202_sd_uhs.zip" file from 17th April 2018 and put that in my card (not the 27th April file which wouldn't do anything when I tried to run the overclock test). Then I downloaded his sd_uhs module file from 19th April and put that into the modules folder in ML (replacing the sd_uhs module that was already there).
After that I followed @IDA_ML 's instructions on how to run the SD overclock test and the card benchmark test, ensuring it's all done in photo mode. His instructions are here: https://www.magiclantern.fm/forum/index.php?topic=16040.msg200229#msg200229
And it worked. I used a Sandisk extreme pro 95mb/s 64gb card. I'm only shooting 24fps.
Do let me know if there's a better way to do this!
Quote from: alpicat on May 23, 2018, 12:09:21 AM
(not the 27th April file which wouldn't do anything when I tried to run the overclock test).
You are aware that this build skips the tests and goes right into patching(160mhz) when selected? Card needs to be about 95mb. Works on 100D at least.
Quote from: Danne on May 23, 2018, 08:07:30 AM
You are aware that this build skips the tests and goes right into patching(160mhz) when selected? Card needs to be about 95mb. Works on 100D at least.
Good to know - I wasn't aware! I was using a 95mb/s card so should have been ok. Might give it another try when I get a chance.
@Danne I've now tested your 27th April build and it works fine on my eos m with a fast card, same good results as the previous build. Thanks for this!
Cool. Also check this:
https://www.magiclantern.fm/forum/index.php?topic=12862.msg201743#msg201743
Is it possible to get Image Stabilization working when shooting RAW videos? I bought a EF-M 18-55MM IS for shooting videos, hoping it would fix all the shaky problems but when reviewing all the footages I still get very shaky results. When shooting H.264 the IS is apparently working well. Also when previewing from camera there is a line stating that there is no IS in the videos. I did some searching in the forum but can't find anything helpful to this issue.
This works out of the box on most other models, where IS is active by default during standby. The only exception I'm aware of is 50D, where one needs to keep the shutter pressed halfway while recording in order to activate IS.
If the EOS M is different, you may want to document its behavior (when IS gets activated by Canon firmware, when it's stopped, whether the same happens in movie vs photo mode and so on). On most other models, in LiveView, IS is enabled by half-shutter in photo mode and stays active for a few seconds after releasing half-shutter, but it's always enabled in movie mode, including standby.
To understand how it works, you need to know the IS is handled by a secondary CPU -- the MPU, which also controls the buttons. If the IS is triggered by half-shutter, then it's very likely the MPU deciding to activate the IS. If it's triggered by actions performed on the main CPU (such as starting H.264), you can find what the main CPU tells to the MPU when that happens, using the startup-log-mpu (https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log-mpu/) build.
I was curious about this so I plugged my 15-45mm IS that came with my EOS M10 onto my EOSM and the IS is definately stabilizing when raw recording. I don't use any liveview functions. This may or may not be useful.
That was a nice find as I use manual lenses most of the time and considered the 15-45 just a pfffft kit lens but its working well as is the Tamron 18-200 Di III VC which I also got for the EOS M10.
Quote from: Walter Schulz on May 22, 2018, 06:14:29 PM
What is your status now?
If problem persists post screens of
- sd_uhs after running
- modules tab
- Help tab, highlight on Press Info
Hey Walter, sorry for delayed response. Lot of hospital days draining my energy levels.
Is there a way for a screenshot with magic lantern? I apologize I am unfamiliar.
I am specifically using Lexer 150mb/s 1000x 32gb cards.
I turn on cam, set to photo mode, went to SD OVERCLOCK and it began "before the hack" running.
Got 45mb tops on a benchmark, every couple of tries. Usually 40mb.
Whenever I activate movie crop mode or crop mode, i get frame skipping/stopping immediately.
Quote from: alpicat on May 23, 2018, 12:09:21 AM
@keel - for the SD hack I used files from @Danne's bitbucket page: https://bitbucket.org/Dannephoto/magic-lantern/downloads/ (I hope it's ok to share this, if not I'll delete the link)
I downloaded the "magiclantern-Nightly.2018Apr17.EOSM202_sd_uhs.zip" file from 17th April 2018 and put that in my card (not the 27th April file which wouldn't do anything when I tried to run the overclock test). Then I downloaded his sd_uhs module file from 19th April and put that into the modules folder in ML (replacing the sd_uhs module that was already there).
After that I followed @IDA_ML 's instructions on how to run the SD overclock test and the card benchmark test, ensuring it's all done in photo mode. His instructions are here: https://www.magiclantern.fm/forum/index.php?topic=16040.msg200229#msg200229
And it worked. I used a Sandisk extreme pro 95mb/s 64gb card. I'm only shooting 24fps.
Do let me know if there's a better way to do this!
This was exactly what I did originally, and now all I changed was the build date to Walter's recommendation (and I moved the sd uhs module, unless there is different iterations of the module and i used an incorrect one but the module runs, and my recording crashes. Sounds like user error and I am loading something incorrectly related to raw video)
**************
UPDATE: i have made a bit of progress,
i was confused about the various modes (movie crop/crop mode/zoom)
especially coming from 50d, that zoom feature on the touchscreen of the eosm went over my head.
After closing the other modules for crop/raw to experiment i found it started to work a bit with MLV lite instead of 2.0
(im sure this is said somewhere in the threads, i may have missed it)
Highest I got on two cards was around 41mbs 2240 X 954 (3.74X) 2.35 12BIT
Highest bench was 45mbs write. This really boggles my mind because I was expecting some great performance from these Lexer Pro 150mb/s 1000x cards. Even a bump to 56mb/s seemed feasible, but I am stumped.
Again, I assume more often than not, user error.
There's also these versions. It all depends on what cards are used I guess.
https://www.magiclantern.fm/forum/index.php?topic=12862.msg201915#msg201915
is there a way to start up straight into sd card overclock and 3x zoom? or start up into sd card overclock and 5x zoom?
This build for eosm here kind of work this way(use at own risk and will):
https://bitbucket.org/Dannephoto/magic-lantern/downloads/
Enable your modules(also lua.mo) then set enable SD overclocking script to Autorun ON. There are a few additional preset scripts in there. Choose one of the presets , for example 10bit_5x_iso100_2.5k and set it to Autorun ON as well. Now first sd_uhs will be enabled then the 5xzoom preset.
Note that if you hold halfshutter while filming you also get correct framing in 5xzoom mode(although a bit sluggish) then releas the button and it goes back to real-time preview. Pretty neat.
hahaha says set 24 fps or you're in deep shit. thats funny
Quote from: Teamsleepkid on June 03, 2018, 09:30:36 AM
hahaha says set 24 fps or you're in deep shit. thats funny
Yes—I learned that the hard way. FPS goes to 29,97 when in zoom mode.
Sent from my iPhone using Tapatalk
Hehe, yup, thanks to dfort feedback I put this in the lua script. Anyway. The better step would be to automate FPS override on via the script so hopefully I find a way to that in time...
After updating to the April build from a _much_ older build, I have found that my M doesn't retain movie crop mode on restart. This is kind of important, as one of my use cases is placing the camera where I cannot see the back of it and powering it up (on battery).
I have tried adding crop.enable = 1 to my config file but can't get it to work (everything else seems to work)
This is kind of a big problem for me. Any help?
Quote from: dfort on November 27, 2016, 11:06:32 PM
I believe that the problem was that if you turn on crop mode then switching to a non ML card, you get stuck in crop mode for video. Yep--just tried it. Put camera in crop mode, remove the card, restart the camera and it stays in crop mode.
Would it be possible to turn off crop mode on shutdown then turn it back to the desired state from the configuration file on start up? Of course this wouldn't help if the camera crashes.
from https://www.magiclantern.fm/forum/index.php?topic=9741.msg175596#msg175596 in Dec 2016
You will need this to reenable movie crop mode:
https://bitbucket.org/Dannephoto/magic-lantern/commits/aa10d0776b1d2aec907ee0e1bd80528daff1f413
Here is a build from the branch:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jun08.EOSM202sd_uhs.zip
excellent build danne exactly what i wanted. goes right into 3x crop and works well with my c mount lenses. basically got a pocket cinema camera now.
It's a nice little cam. By the way. Reenabling settings is possible with lua scripts to. Most things are possible through lua thanks to dmilligan and A1ex.
I'd like to look into the adtg module for the EOS M to increase the max resolution in crop mode. There's some nice progress being made on this with the 100D.
To get started do I just put the adtg_gui file into the modules folder and enable it, or is it necessary to create a custom-made build specifically for the EOS M to make it work?
@alpicat
I wrote this guide for 700D ,, it will be similer for EOS M but the values isn't the same but it's same way.
You should define ENGIO_WRITE_FUNC and ENG_DRV_OUT_FUNC in adtg_gui.c for EOS M --> I will do it for you ASAP.
Then put adtg_gui.mo in modules folder under build from crop_rec_4k branch and start working.
After enabling adtg_gui go to adtg_gui submenu -->Advanced --> Enable DIGIC Registers --> Go to PLAY mode and go back to live view --> Press x5 to get into crop mode and start adjusting the registers.
Change the registers menu to Known registers only to help you finding the registers.
https://www.magiclantern.fm/forum/index.php?topic=19300.msg197870#msg197870
@theBilalFakhouri thanks, if you're able to prepare the adtg module file for the eos m I'd really appreciate it (there's no rush though). Then I can start working on it!
Cool. I just started digging into adtg_gui stuff so if I can assist in any way I will. Got an eosm here too :).
Cheers @Danne - I'm following the work you're doing with the 100D which is very interesting. Once I have the adtg_gui file I'll get on with it and post my findings here.
This should work with EOS M from Stubs.s
else if (is_camera("EOSM", "2.0.2")) // from 1%
{
ADTG_WRITE_FUNC = 0x2986C;
CMOS_WRITE_FUNC = 0x2998C;
ENGIO_WRITE_FUNC = 0xFF2C19AC; // from stubs
ENG_DRV_OUT_FUNC = 0xFF2C1694;
}
Download adtg_gui (https://drive.google.com/open?id=1Gq7udjM4cdlmJiSGVVZTxFL1wv4o0GSk)
Seems I got 2520x1256 24fps 14bit-lossless on the eosm. Registers very close to 100D.
2.5khttps://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jun09.EOSM202adtg_gui_ver_06_2.5K.zip
3.5khttps://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jun09.EOSM202adtg_gui_ver_06_3K.zip
Above two versions for early testing. Automation if wanted via lua script. This applies for both 100D and eosm:
Set global draw to off prior to running lua script(bug on 100D, maybe works for eosm, didn´t check this)
ADTG_GUI form this branch:
https://bitbucket.org/Dannephoto/magic-lantern/branch/iso-research_nikfreak
commit:
https://bitbucket.org/Dannephoto/magic-lantern/commits/fa52c2810c6a8ab4b8fe865329926c7398d9c85e
All thanks to Nikfreak and bilal* etc...
Thanks so much for your help @Danne and theBilalFakhouri (and Nikfreak)! I've tested both of your builds Danne using your automated lua script, and they work without crashes but there's an issue with the bottom part of the recorded frame which seems to correspond to the increased height resolution area (see images below). Is this also happening with the 100D?
2.5k
(https://thumb.ibb.co/hqLw0J/2520x1256.jpg) (https://ibb.co/hqLw0J)
3k
(https://thumb.ibb.co/iPT5ud/3k.jpg) (https://ibb.co/iPT5ud)
The liveview preview works fine with the 2.5k build, with the 3k one it's garbled - but that doesn't affect the recorded video.
I'll take a closer look this weekend once I get the chance. Personally I really like the idea of being able to do 2520x1256 which is close to 16:9.
Didn't test too much on eosm. Are you getting these results with 14bit-lossles?
@alpicat
Could you test again? I messed up the code before. Should be fixed now:
2.5k
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jun09.EOSM202adtg_gui_ver_06_2.5K.zip
3k
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jun09.EOSM202adtg_gui_ver_06_3K.zip
Hi, I tried newest build and lower part of image is still missing, although in my case there are two color lines and the rest is black. Also in 3K LiveView is garbled (not complaining, just FYI). And thanks for howto video :).
2.5K
(https://thumb.ibb.co/nn4upd/M14_1160_000010.jpg) (https://ibb.co/nn4upd)
3K
(https://thumb.ibb.co/iP8yFJ/M14_1151_000031.jpg) (https://ibb.co/iP8yFJ)
Eh, yes, found out myself today that height is black. Placebo on my part.
Yes, 3k garbled.
What's next? We need to find out how to increase actual image into height. How? I tried some with cmos7 register but it only got me halfway giving me black transparency with some image.
Any hints are most welcome here Nikfreak, A1ex, Bilial* maybe?
Sorry for my delayed replies. I've tested both new builds and getting the same results as @loknar with the black lower part of the image and the thin colour line.
I mostly tested in 14 bit lossless which is fine, but also briefly tried 10 and 12 bit lossless with the original 2.5k build. Some of those clips worked but sometimes they were glitchy - I can recheck that if you like?
However with today's build when I tried 10 and 12 bit lossless on the 2.5k build, all the resulting footage was glitchy and unusable (it looks ok on liveview when you're recording it), and 14 bit lossless is fine as expected.
Just for more comparing and understanding the values differences between the models and trying to figure out the black vertical problem:
Log "Known registers" in x5 mode without overriding (the normal values) for EOS M & 100D
1-Enable adtg_gui
2-Change registers menu to Known registers only
3-Go to adtg_gui submenu --> Advanced --> Enable DIGIC registers
4-Go to PLAY mode then go back to live view and press magnification to get into x5 mode
5-Go to adtg_gui submenu --> Advanced --> Log displayed registers
Search for it ML folder .LOG --> it will look like this:
Canon EOS 700D 1.1.5
c0400008:236b1087 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=LVFACE pc=ff2c5da8 addr=182f98 Clock control
c0400048: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=LVFACE pc=ff2c600c addr=182fa8 LClk (from 5D classic)
c0f07148: 4 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=PowerMgr pc=ff56fdc4 addr=42890 HEAD4 timer (start?)
c0f07134: 4 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56fd0c addr=42848 HEAD3 timer (start?)
c0f37ae4: 200 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f25f8 addr=17e2f8 ISO digital gain (5D3 photo mode)
c0f37af0: 200 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2604 addr=17e2f8 ISO digital gain (5D3 photo mode)
c0f37afc: 200 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2610 addr=17e2f8 ISO digital gain (5D3 photo mode)
c0f37b08: 200 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f261c addr=17e2f8 ISO digital gain (5D3 photo mode)
c0f08038: 800 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2658 addr=17e2f8 SHAD_POSTSETUP_14_12
c0f08030: 1000 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2664 addr=17e2f8 Digital gain for ISO (SHAD_GAIN)
c0f08024: 1000 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2670 addr=17e2f8 ISO related? (SHAD_MODE) (5D2: used for ISO 25600)
c0f0814c: 5 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f269c addr=17e2f8 DEFM_GRADE
c0f0819c: 12f0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f273c addr=17e2f8 Saturate Offset (photo mode) (HIV_POST_SETUP)
c0f37ae0: 6d10 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2908 addr=17e2f8 ISO black/white offset (5D3 photo mode)
c0f37aec: 6d10 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2928 addr=17e2f8 ISO black/white offset (5D3 photo mode)
c0f37af8: 6d10 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2948 addr=17e2f8 ISO black/white offset (5D3 photo mode)
c0f37b04: 6d10 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2968 addr=17e2f8 ISO black/white offset (5D3 photo mode)
00028830: 1 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56d92c addr=40453348 Only slightly changes the color of the image (g3gg0)
00f00000: 803 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56da64 addr=4045368e Analog ISO (most cameras)
00f00001: 4ce ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56da64 addr=40453690 Vertical offset
00f00002: 2 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56da64 addr=40453692 Horizontal offset / column skipping
00f00003: f00 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56da64 addr=40453694 Analog ISO on 6D
00f00004: 2 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56da64 addr=40453696 ISO-related?
00f00005: 300 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56da64 addr=40453698 Fine vertical offset, black area maybe
00f00006: 789 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56da64 addr=4045369a ISO 50 or timing related: FFF => darker image
00f00007: a49 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56da64 addr=4045369c Looks like the cmos is dieing (g3gg0)
00028882: 446 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56dab4 addr=4045336c ISO ADTG gain (per column, mod 4 or mod 8)
00028884: 447 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56dab4 addr=40453370 ISO ADTG gain (per column, mod 4 or mod 8)
00028886: 446 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56dab4 addr=40453374 ISO ADTG gain (per column, mod 4 or mod 8)
00028888: 445 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56dab4 addr=40453378 ISO ADTG gain (per column, mod 4 or mod 8)
c0f06000: 1 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56f590 addr=429e8 FPS register for confirming changes
c0f07048: 4 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=PowerMgr pc=ff56fb30 addr=427b8 HEAD1 timer (start?)
c0f37014: e ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960e18 LV raw type (see lv_af_raw, lv_set_raw) - DIGIC V
c0f07010: 3fff ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff381124 addr=42a60 HEAD timers
c0f0700c: 1 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56fad8 addr=42530 HEAD timers, 0x01 to stop/standby
c0f0714c: c ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff38086c addr=42868 HEAD4 timer
c0f07138: c ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff380858 addr=42820 HEAD3 timer
00028000: 5 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56dbc8 addr=40452894 Causes interlacing (g3gg0)
c0f07000: 1 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff380d1c addr=42730 HEAD timers (SSG counter, 0x01 to restart)
c0f0705c: 4 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff380d1c addr=42718 HEAD2 timer (start?)
c0f0704c: c ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff380d2c addr=42790 HEAD1 timer
c0f03074: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f3af8 addr=ff961340 Playback: horizontal banding (500D only?)
00020009: ff0e ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56e710 addr=404533d8 ADTG preamp (per column, mod 4 or mod 8)
0002000a: 3121 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56e710 addr=404533dc ADTG preamp (per column, mod 4 or mod 8)
0002000b: c40 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56e710 addr=404533e0 ADTG preamp (per column, mod 4 or mod 8)
0002805e: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56e71c addr=4045263c Shutter blanking for x5/x10 zoom
00028060: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56ec58 addr=40452c24 Shutter blanking for LiveView 1x
000282f3: c ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56efa8 addr=40452dd8 Line count that gets darker (top optical black related)
00028806: 408 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56e738 addr=40452f18 Causes interlacing artifacts
00028880: 800 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56e738 addr=40452f9c Black level (reference value for the feedback loop?)
c0f0601c: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56faa0 addr=42368 FPS related
c0f06084: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56faa0 addr=42430 RAW first line|column. Column is / 2. 600D: 0x0001007E.
c0f06088: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56faa0 addr=42438 RAW last line|column. 600D: FHD 1182|1070, 3x 1048|1102, HD 720|1070
c0f06018: 20 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56faa0 addr=424d0 FPS related
c0f06020: 2 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56faa0 addr=424d8 FPS related
c0f06008: 2cb02cb ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff570228 addr=42a90 FPS register A
c0f0600c: 2cb02cb ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff570228 addr=42a98 FPS related
c0f06010: 2cb ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff570228 addr=42aa0 FPS related
c0f06800: 10010 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff570228 addr=42aa8 RAW first line|column. Column is / 8 on 5D3 (parallel readout?)
c0f06804: 4540298 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff570228 addr=42ab0 RAW last line|column. 5D3: f6e|2fe, first 1|18 => 5936x3950
c0f07004: 1 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56fad8 addr=42500 HEAD timers
c0f07014: 3 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56fad8 addr=42510 HEAD timers
c0f07018: 7c ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56fad8 addr=42518 HEAD timers
c0f0707c: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56fad8 addr=42520 HEAD timers
c0f071ac: 1000010 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56fad8 addr=42528 HEAD timers
c0f07038: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56fad8 addr=42538 HEAD timers, 0x01 <- stops processing?
c0f06014: 5d3 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56f19c addr=428a0 FPS register B
c0f07050: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff380d2c addr=42780 HEAD1 timer (ticks?)
c0f0713c: 455 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff380858 addr=42810 HEAD3 timer (ticks?)
0002800c: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56dc9c addr=40452e50 Line skipping factor (2 = 1080p, 4 = 720p, 0 = zoom)
00028172: 67c ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56efa8 addr=40452dbc Line count to sample. same as video resolution (g3gg0)
00028178: 67c ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56efa8 addr=40452dc8 dwSrFstAdtg1[4], Line count + 1
00028179: 775 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56efa8 addr=40452dcc dwSrFstAdtg1[5]
00028196: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56f2f8 addr=40452e98 dwSrFstAdtg1[2], Line count + 1
00028197: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff56f2f8 addr=40452e9c dwSrFstAdtg1[3]
c0f08138: 10 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960a30 DEFM_MODE
c0f08158: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960a40 DEFM_INTR_EN
c0f08154: 8 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960a48 DEFM_INTR_CLR
c0f08140: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960a50 DEFM_INTR_NUM
c0f08150: fff ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960a58 DEFM_DAT_TH
c0f0815c: 2 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960a60 DEFM_14_12_SEL
c0f08160: 3fff ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960a68 DEFM_DAT_TH_14_12
c0f08420: 5bf ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960b68 HIV_BASE_OFST
c0f08428: 111 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960b70 HIV_GAIN_DIV
c0f0842c: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960b78 HIV_PATH
c0f08184: 453 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960b90 LV resolution (RAW.height) aka HIV_V_SIZE
c0f08188: a1f ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960b98 LV resolution (RAW.width) aka HIV_H_SIZE
c0f0818c: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960ba8 HIV_POS_V_OFST
c0f08190: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960bb0 HIV_POS_H_OFST
c0f08194: a1f ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960bb8 LV resolution (RAW.width)
c0f08198: a1f ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960bc0 LV resolution (RAW.width)
c0f082c4: 1 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960c70 HIV_DEFMARK_CANCEL
c0f08028: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960d58 SHADE_PRESETUP
c0f0802c: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960d60 SHAD_POSTSETUP
c0f08034: 1800 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960d70 Black level in LiveView / BW offset in photo mode (SHAD_PRESETUP)
c0f08280: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960d80 SHAD_CBIT
c0f08284: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960d88 SHAD_C8MODE
c0f08288: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960d90 SHAD_C12MODE
c0f0828c: 1 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960d98 SHAD_RMODE
c0f08290: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960da0 SHAD_COF_SEL
c0f082a8: 1 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f24d8 addr=ff960da8 SHAD_KZMK_SAV
c0f08214: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff382738 addr=17e288 HIV_PPR_EZ
c0f08548: 4530a1f ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff3826d4 addr=17e288 LV resolution * downsize factor? (RAW.height * D | RAW.width * D)
c0f08578: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff382750 addr=17e288 Vignetting correction data (DIGIC IV)
c0f383d4: 15300af ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff70c524 addr=17e010 Preview area (y1 | x1/4)
c0f383dc: 40c01b7 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff70c6b8 addr=17e020 Preview area (y2 | x2/4)
c0f1a00c: 2af0407 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4f2f0c addr=ff96254c LV resolution (raw.j.width | raw.j.height)
c0f11394: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff4fbe9c addr=ff977e14 LV resolution (raw.j.height | raw.j.width)
c0f07150: 428 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=Evf pc=ff38086c addr=42858 HEAD4 timer (ticks?)
c0f140c4: 8080 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=DisplayMgr pc=ff128e6c addr=ff8e6310 Display saturation
c0f14140: 0 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=DisplayMgr pc=ff128e6c addr=ff8e6540 Display filter (EnableFilter, DIGIC peaking)
c0f14164: c0046 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=DisplayMgr pc=ff128e6c addr=ff8e6588 Display position (vertical shift)
c0f141b8: 80 ISO=100 Tv=50 Av=41 lv=1 zoom=5 mv=1 res=0 crop=0 task=DisplayMgr pc=ff128e6c addr=ff8e65f0 Display brightness and contrast
==================================================================
These registers isn't in the Known registers menu:
C0F06824 (You will find it in Image size only)
C0F06828
C0F0682c
C0F06830
ADTG2[82b6] (Fix vertical artifact in 700D) -->This isn't in above menus you can see it by using Modified from now --> First go into normal mode then change the menu to Modified from now and press x5 button to get into crop mode and write it manually. (We should make pull request for this).
On EOS M, an even more interesting comparison would be between 1080p standby vs recording (https://www.magiclantern.fm/forum/index.php?topic=16608.msg176846#msg176846). The former is actually 720p at some low FPS, so the only differences between these two modes are:
- vertical resolution (horizontal resolution is the same in all "1x" video modes)
- frame rate (30 during standby? no other cameras configure a 720p readout at low FPS, to my knowledge)
- H.264 activity (can be ignored)
Some results of the above comparison were linked above, but it's probably a good idea to double-check them. In particular, the comparison should be done at whatever FPS is used during standby, to minimize the number of variables that are going to change. Also, register 800C is not in the linked logs; it should be, according to previous discussion.
Most definitely will try and document and figure out changes/anomalys with eosm. Tried locking registers in standby going to recordings in raw with the thinking it might have kept the mv1080p mode in place 8). It did not work :P
@Danne @loknar
Can you do this (https://www.magiclantern.fm/forum/index.php?topic=9741.msg202758#msg202758) please for EOS M & 100D?
I'd like to test the resolution 2904x1248 for 700D and try to guess the full resolution live view for 100D & EOS M.
Thanks!
Great, appreciated:
Log for eosm in x5 zoom:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/ADTG.LOG
100D will not save to a log when selecting that option. It only goes out from the menu leaving the LOG folder empty...
By the way. These registers are set to get to 3096x1256 or 2520x1248(unsuccessful height):
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6800: /* C0F06804 - raw resolution */
return 0x10010;
case 0x6804: /* C0F06804 - raw resolution */
return 0x5040298; /* Valid liveview 2520x1248 24fps 14-bit lossless */
/* return 0x5040328; /* crushed liveview 3096x1256 24fps 14-bit lossless */
case 0x6824:
return 0x4ca;
case 0x6828:
return 0x4ca;
case 0x682c:
return 0x4ca;
case 0x6830:
return 0x4ca;
case 0x6008:
return 0x35b035b;
case 0x600c:
return 0x35b035b;
case 0x6010:
return 0x35b;
case 0x6014:
return 0x60b;
case 0x7150:
return 0x428;
case 0x713c:
return 0x505;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x8172:
return 0x437;
case 0x8178:
return 0x437;
case 0x8179:
return 0x5a5;
}
}
}
@Danne thanks!
EOS M registers is identical 100% to 700D in x5 (I guess the other modes will be the same) ,, except I couldn't find "Timer B" in the log. I assuming the problem:
Quote from: theBilalFakhouri on February 27, 2018, 08:54:32 AM
Somethings I have noticed:
Disappearing Timer B in 1080p 23.976 (@a1ex this is a issue?).
So the best thing when overriding the registers is to make sure you are in mv1080 @ 25 fps (that's was better for 700D and I don't know if EOS M can do this without recording --> Make sure the Timer B isn't disappearing and maybe this is the problem for black vertical.)
Edit before releasing the post :P : I am pretty sure the problem is here:
case 0x8172:
return 0x437;
case 0x8178:
return 0x437;
You may change it to:
case 0x8172:
return 0x77c;
case 0x8178:
return 0x77c;
Now can you please try these presets for EOS M (I made it for 700D (https://www.magiclantern.fm/forum/index.php?topic=19300.msg202049#msg202049) but it should work without problems in EOS M )
1-
2520x1384 ~16:9 @ 23.976 Using this adtg_gui (https://drive.google.com/open?id=1Sir5CtgJ9d7zRwFllbEo_izwiu93_r-b) for EOS M & 700D
2-
3K 3072x1304 @ 20fpsUsing this adtg_gui (https://drive.google.com/open?id=1qp_K6L2DiQm6Y8cZXgH3OHLWiKhhARjO) for EOS M & 700D
3-
nearly Full-res 5208x3240 @ 6.5fpsUsing this adtg_gui (https://drive.google.com/open?id=1mS3Ik0Xsc-xkeZ4f6sF2OihnN7RMhcLG) for EOS M & 700D
Follow the steps in the link (https://www.magiclantern.fm/forum/index.php?topic=19300.msg202049#msg202049)!!
After applying Full-res preset or the other it's better to go to PLAY mode then get back to live-view and getting into x5 --> I noticed issues when using magnification button to update overriding registers .
Quote from: Danne on June 16, 2018, 12:00:38 AM
100D will not save to a log when selecting that option. It only goes out from the menu leaving the LOG folder empty...
This is bad --> @a1ex we need your help please why this happening ?
Quote from: theBilalFakhouri on June 16, 2018, 01:51:35 AM
1-2520x1384 ~16:9 @ 23.976
Using this adtg_gui (https://drive.google.com/open?id=1Sir5CtgJ9d7zRwFllbEo_izwiu93_r-b) for EOS M & 700D
2- 3K 3072x1304 @ 20fps
Using this adtg_gui (https://drive.google.com/open?id=1qp_K6L2DiQm6Y8cZXgH3OHLWiKhhARjO) for EOS M & 700D
3- nearly Full-res 5208x3240 @ 6.5fps
Using this adtg_gui (https://drive.google.com/open?id=1mS3Ik0Xsc-xkeZ4f6sF2OihnN7RMhcLG) for EOS M & 700D
Do these resolutions and frame rates really work without corrupt frames and at what bit depth (14-bit lossless ???). Have they been tested on the EOS M and 700D? If yes, that is a remarkable progress, theBilalFakhouri !!!
Quote from: Danne on June 16, 2018, 12:00:38 AM
100D will not save to a log when selecting that option. It only goes out from the menu leaving the LOG folder empty...
If there's nothing screaming in the Debug menu, one has to debug it and see where it fails.
Best guess: out of memory => turn off raw video.
@a1ex. Best guess == good guess. Turned off raw video and log is produced. Will see if I can do something about getting it out with raw video on somehow. Maybe force low fps will help. Just ran out of battery. Meanwhile, here´s the log with raw video to off:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/100D_rawvideo_off_ADTG.LOG
Awesome work @theBilalFakhouri. I can do recordings on the eosm in 2520x1384 ~16:9 @ 23.976 now, the black border is gone! I put your provided build into modules and then just ran my lua helper script which puts me right into action.
MLV proof:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/2520x1384.MLV
Tested the other two as well, only briefly. 3K 3072x1304 @ 20fps was giving me a full view image when viewed with global draw to on and framing enabled. Recording was corrupted. Needs more tests.
nearly Full-res 5208x3240 @ 6.5fps needs more testing. Viewing lcd global draw on and framing shwed a 1/3 of the image black on the right side, but I need to test more on this.
Would be cool if you could print out the changes in your adtg_gui or are you using the ones in your 700D spreadsheet without modifications? I can check later with overriden register. Could you maybe publish code into a bitbucket branch?
Appreciate all the help here. Now let´s see if we can kickstart the 100D here :)
@theBilalFakhouri
Just for comparison my ATDG.LOG (As expected it's nearly same as @Danne's)
http://txt.do/dpiz0
I tried your new atdg_gui module:
1-2520x1384 ~16:9 @ 23.976
So cool! :) It's almost there, black bar is gone, there is 1 red line and 7 white lines at the bottom. (Don't mind right side, that's window frame that's really there)
(https://thumb.ibb.co/iB3PaJ/M16_0914_000026.jpg) (https://ibb.co/iB3PaJ)
If that's caused by my processing, here is also pristine raw file.
http://s000.tinyupload.com/index.php?file_id=49985433615303677505
Quote from: IDA_ML on June 16, 2018, 06:57:58 AM
Do these resolutions and frame rates really work without corrupt frames and at what bit depth (14-bit lossless ???). Have they been tested on the EOS M and 700D? If yes, that is a remarkable progress, theBilalFakhouri !!!
This was stable for 700D but write speed limit is confusing :D Thanks!
@a1ex
Thanks!@Danne
Quote from: Danne on June 16, 2018, 08:53:50 AM
nearly Full-res 5208x3240 @ 6.5fps needs more testing. Viewing lcd global draw on and framing shwed a 1/3 of the image black on the right side, but I need to test more on this.
Yes are right and this is because CMOS 5 wasn't overridden in adtg_gui I don't know why it didn't respond to the code (Full-res):
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 5: return 0x0;
case 7: return 0x800; /* CMOS[7]: ISO related? */
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6: return 0x97f; /* it's 5 in zoom mode and 6 in 1080p; this also overrides ADTG4 */
case 0x8172: return 0x8fd; /* without this, you get some weird artifacts; this should only go to ADTG2, not 4 */
case 0x8178: return 0x8fd;
case 0x8000: return 0x5;
case 0x800c: return 0x0;
}
}
return 0;
}
static int res3k_reg(int reg)
{
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804: /* C0F06804 - raw resolution */
return 0xccc0538; /* from 0x528011B -> 3072px in raw_rec */
case 0x6824: return 0x56a;
case 0x6828: return 0x56a;
case 0x682c: return 0x56a;
case 0x6830: return 0x56a;
case 0x6008: return 0x56b056b;
case 0x600c: return 0x56b056b;
case 0x6010: return 0x56b;
case 0x6014: return 0xdcb;
case 0x713c: return 0xca7;
case 0x6800: return 0x30010;
}
}
return 0;
Just change
CMOS 5 to
0x0 manually.
Quote from: Danne on June 16, 2018, 08:53:50 AM
Would be cool if you could print out the changes in your adtg_gui or are you using the ones in your 700D spreadsheet without modifications? I can check later with overriden register. Could you maybe publish code into a bitbucket branch?
Yes the same in spreadsheet --> This the last one for 3K:
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 5: return 0x280; /* CMOS[5]: ISO related? */
case 7: return 0xa89; /* CMOS[7]: ISO related? */
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6: return 0x7f4; /* it's 5 in zoom mode and 6 in 1080p; this also overrides ADTG4 */
case 0x8172: return 0x77c; /* without this, you get some weird artifacts; this should only go to ADTG2, not 4 */
case 0x8178: return 0x77c;
}
}
return 0;
}
static int res3k_reg(int reg)
{
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804: /* C0F06804 - raw resolution */
return 0x5340322; /* from 0x528011B -> 3072px in raw_rec */
case 0x6824: return 0x3ca;
case 0x6828: return 0x3ca;
case 0x682c: return 0x3ca;
case 0x6830: return 0x3ca;
case 0x6008: return 0x37b037b;
case 0x600c: return 0x37b037b;
case 0x6010: return 0x37b;
case 0x6014: return 0x6d7;
case 0x713c: return 0x555;
}
}
return 0;
I will try to do it in bitbucket .
Quote from: Danne on June 16, 2018, 08:53:50 AM
Appreciate all the help here. Now let´s see if we can kickstart the 100D here :)
In progress :D
Quote from: loknar on June 16, 2018, 09:15:22 AM
If that's caused by my processing, here is also pristine raw file.
http://s000.tinyupload.com/index.php?file_id=49985433615303677505
This dng looking corrupted --> on 700D only the last few frames before the recording stops it's sometimes shows corrupted frames it's depending in scene, iso and whatever --> But we are here to fix all that problems :D
The most shots was very stable on 700D --> I am thinking this because adtg_gui it's heavy on the camera and when loading other modules the more corrupted frames shows --> I tried to implement it in crop_rec no much luck yet let's ask a1ex some questions :D
QuoteThis dng looking corrupted --> on 700D only the last few frames before the recording stops it's sometimes shows corrupted frames it's depending in scene, iso and whatever --> But we are here to fix all that problems :D
You are right, frames at the end are garbled (test image was just random pick from the middle).
Also camera reacts kind of sloppy, so maybe there really is more load than CPU can handle.
3072x1304 working.
else if (is_camera("EOSM", "2.0.2"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 5:
return 0x280; /* CMOS[5]: ISO related? */
case 7:
return 0xa89; /* CMOS[7]: ISO related? */
}
}
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804: /* C0F06804 - raw resolution */
return 0x5340322; /* from 0x528011B -> 3072px in raw_rec */
case 0x6824:
return 0x3ca;
case 0x6828:
return 0x3ca;
case 0x682c:
return 0x3ca;
case 0x6830:
return 0x3ca;
case 0x6008:
return 0x37b037b;
case 0x600c:
return 0x37b037b;
case 0x6010:
return 0x37b;
case 0x6014:
return 0x6d7;
case 0x713c:
return 0x555;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6:
return 0x7f4; /* it's 5 in zoom mode and 6 in 1080p; this also overrides ADTG4 */
case 0x8172:
return 0x77c; /* without this, you get some weird artifacts; this should only go to ADTG2, not 4 */
case 0x8178:
return 0x77c;
}
}
}
MLV proof:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/3072x1304.MLV
Trying this for fullres but doesn´t work good. Also have to add cmos 5 manually. Do you see anything Bilal?:
else if (is_camera("EOSM", "2.0.2"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 5:
return 0x0; /* CMOS[5]: ISO related? */
case 7:
return 0x800; /* CMOS[7]: ISO related? */
}
}
if (regs[reg].dst == 0xC0F0 && DST_CMOS)
{
switch (regs[reg].reg)
{
case 0x6804: /* C0F06804 - raw resolution */
return 0xccc0538; /* from 0x528011B -> 5208px in raw_rec */
case 0x6800:
return 0x30010;
case 0x6824:
return 0x56a;
case 0x6828:
return 0x56a;
case 0x682c:
return 0x56a;
case 0x6830:
return 0x56a;
case 0x6008:
return 0x56b056b;
case 0x600c:
return 0x56b056b;
case 0x6010:
return 0x56b;
case 0x6014:
return 0xdcb;
case 0x713c:
return 0xca7;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6:
return 0x97f; /* it's 5 in zoom mode and 6 in 1080p; this also overrides ADTG4 */
case 0x8172:
return 0x8fd; /* without this, you get some weird artifacts; this should only go to ADTG2, not 4 */
case 0x8178:
return 0x8fd;
case 0x8000:
return 0x5;
case 0x800c:
return 0x0;
}
}
}
EDIT: adding cmos 5 and then turning on and off raw video finally breaks height from 696 to 2928 giving me 5208x2928. Recording anything is another story though. Getting a good liveview from framing and global draw on but once I hit record I get raw detect error or in best cases a 2kb file :P
New version(thanks to bilal)
2.5k (
2520x1336 24fps) EDIT: changed resolution to 2520x1320 24fps due to corruption.
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jun16.EOSM202_2.5k.zip
Automation if wanted via lua script. Reworked/renamed to
adtg_gui helper
Thanks Danne and Bilal, that's some incredible progress and really appreciated! With your latest 2.5k build (newest 16th June version), it works well with no glitches or corrupted lines. I've made a quick video recorded at 2520x1320 and also 2336x1314 for a slightly longer record time. This is 14 bit lossless (I briefly tried 10 bit lossless but immediately got error messages).
I had tried your 16th June build yesterday @Danne before you posted the edited version and was getting glitchy footage that was jumping everywhere. Same with Bilal's adtg_gui file. But this version is perfect.
Thanks for posting this. 14bit lossless works but not the lower bits. Too bad and probably very hard to get those bits going from what I heard...
Posted a new build with exfat compatibilty with the included lua scripts:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jun16.EOSM202_2.5k.zip
Will be no problems if running fat32 before but now it works for both.
Edit: Could 14-lossless record in a lossy format to gain longer recording times?
I got lower bit rates to work without error messages in earlier builds but the resulting footage had glitches. I might investigate that again when I have time. I can imagine it will be hard to find a way around that though - let's just hope there will be a way to achieve higher write speeds with the SD overclock hack in future, or that an SD card company manages to release a faster UHS-I card!
Thanks for changing the lua scripts file names, that will save some time!
@alpicat
14-bit lossless is only working ,, the lower lossless bit-depths isn't working (sometimes you can select it but this doesn't mean it's working ) = you will have glitch in the footage as you mentioned and corrupted frames --> But 14-bit lossless is working fine is there a problem with it ?
And the solution was for using lower bit-depths to override registers we don't know it yet:
Quote from: a1ex on May 28, 2018, 06:57:22 PM
Other image processing modules have to be reconfigured for the higher resolution. The solution is probably somewhere in these huge logs (https://www.magiclantern.fm/forum/index.php?topic=2388.msg197313#msg197313), but I didn't try to decipher them yet.
And if we found it we will need at least
70mb/s write speed --> with
sd_uhs only we can get
55mb/s effective speed so if we could push the write speed to the max
@ 208MHz I think we will get
80mb/s effective speed or more and this will be better.
You are using
EOS M right ? why you didn't use this adtg_gui ?
Quote from: theBilalFakhouri on June 16, 2018, 01:51:35 AM
1-2520x1384 ~16:9 @ 23.976
Using this adtg_gui (https://drive.google.com/open?id=1Sir5CtgJ9d7zRwFllbEo_izwiu93_r-b) for EOS M & 700D
@theBilalFakhouri 14-bit lossless works yes, and I'm using the EOS M. With one or two of Danne's earlier builds it was possible to get liveview to work and record fine with lower bit depths, but it's true that the recorded footage had glitches.
I did try your 2520x1384 adtg_gui file yesterday and all looked fine in liveview, but unfortunately when I looked at the footage on my computer it was jumping around and was glitchy. Danne posted an example (see here below) which is exactly what I was getting with my footage:
Quote from: Danne on June 16, 2018, 08:53:50 AM
MLV proof:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/2520x1384.MLV
I'll try again to double check in case I did something wrong, but in any case Danne's newest build (2520x1320) works 100% as you can see in my video.
A higher write speed is definitely needed though. I wonder what it will take to push to 208MHz?
very cool. is it possible to get more than 1800 wide in crop mode 3x? crop mode also has real time preview, everyone im sure already knows this but just wondering. i heard someone mention it on sl1 thread. exciting times. i thought we reached an end to hardware tweaks and that software fo magic lantern would be the next big thing, im sure we will have higher res and 10 bit raw very soon.
Quote from: alpicat on June 17, 2018, 11:53:46 PM
I wonder what it will take to push to 208MHz?
Understanding how these registers (https://www.magiclantern.fm/forum/index.php?topic=12862.msg202116#msg202116)works because these registers controls write & read speeds .
Or someone helping me with this (https://www.magiclantern.fm/forum/index.php?topic=12862.msg202179#msg202179). :P
@Teamsleepkid
Do you mean increasing resolution in movie crop mode?
I think it's possible to do it but when you start
increasing horizontal resolution the real time preview will be
garbled and it's will show only the old frame size same of live-view as x5 crop mode .
levas probably knows
4k version:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jun16.EOSM202_4k.zip
Thanks to Levas, Bilal, Nikfreak
Automation if wanted via lua script. Reworked/renamed to
adtg_gui helper
For reference(x5 zoom settings working)
2520x1320: 24fps
else if (is_camera("EOSM", "2.0.2"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 7: return 0xaa9; /* CMOS[7]: ISO related? */
}
}
if (regs[reg].dst == 0xC0F0 && DST_CMOS)
{
switch (regs[reg].reg)
{
case 7: return 0xaa9; /* CMOS[7]: ISO related? */
case 0x6804: /* C0F06804 - raw resolution */
return 0x5490298; /* 2520x1320 x5 Mode; */
/* return 0x5040328; /* crushed liveview 3096x1256 24fps 14-bit lossless */
case 0x6014:
return 0x747;
case 0x7150:
return 0x428;
case 0x713c:
return 0x535;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x8172:
return 0xfa8;
case 0x8178:
return 0xfa8;
case 0x82b6:
return 0x8f4;
}
}
}
3072x1304: 20fps
else if (is_camera("EOSM", "2.0.2"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 5:
return 0x280; /* CMOS[5]: ISO related? */
case 7:
return 0xa89; /* CMOS[7]: ISO related? */
}
}
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804:
return 0x5340322;
case 0x6824:
return 0x3ca;
case 0x6828:
return 0x3ca;
case 0x682c:
return 0x3ca;
case 0x6830:
return 0x3ca;
case 0x6008:
return 0x37b037b;
case 0x600c:
return 0x37b037b;
case 0x6010:
return 0x37b;
case 0x6014:
return 0x6d7;
case 0x713c:
return 0x555;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6:
return 0x7f4;
case 0x8172:
return 0x77c;
case 0x8178:
return 0x77c;
}
}
}
4038x2558: 9fps
else if (is_camera("EOSM", "2.0.2"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 5:
return 0x200; /* CMOS[5]: ISO related? */
case 7:
return 0xf20; /* CMOS[7]: ISO related? */
}
}
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804:
return 0xa1b0412; /* 4032x2558 x5 Mode; */
case 0x6824:
return 0x4ca;
case 0x6828:
return 0x4ca;
case 0x682c:
return 0x4ca;
case 0x6830:
return 0x4ca;
case 0x6008:
return 0x45b045b;
case 0x600c:
return 0x45b045b;
case 0x6010:
return 0x45b;
case 0x6014:
return 0xbd4;
case 0x713c:
return 0xa55;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6:
return 0xbf4; /* it's 5 in zoom mode and 6 in 1080p; this also overrides ADTG4 */
case 0x8172:
return 0x8fd;
case 0x8178:
return 0x8fd;
}
}
}
3072x1304: 24fps? thats getting up there
Corrected to 20fps
@Danne Have tested your 4k build and it works, see video. Able to record 4 or 5 frames at a time at 4096x2552 resolution at 9fps. That's the first time I've ever recorded anything in 4k! Liveview is scrambled, but with global draw on it works - you get the usual pixelated low fps preview.
In one of the exterior shots close to the horizon area the focus pixels make an appearance (small area only). I've looked at the various options to remove these in MLV App but they don't seem to go away.
Also, I tried to see if it was possible to select a lower resolution with this build (2.5k or 3k), but it didn't seem to work so I did no further testing. I'm assuming this 4k build is only designed to work with 4k resolution?
Quote from: theBilalFakhouri on June 18, 2018, 01:12:18 AM
Understanding how these registers (https://www.magiclantern.fm/forum/index.php?topic=12862.msg202116#msg202116)works because these registers controls write & read speeds .
Or someone helping me with this (https://www.magiclantern.fm/forum/index.php?topic=12862.msg202179#msg202179). :P
Thanks for bringing this up @Bilal. I guess that's probably the most important next step to take in order to make higher resolution recording feasible. What sort of coding or steps would be needed to help you with this? I don't know how to help but maybe could ask around, although I imagine anyone who looks at this would need to have specific knowledge about coding for Magic Lantern?
I see you use ML preview for 4K.
To squeeze out a tiny bit more performance, you can go inside ML raw menu and set preview to 'real-time' instead of auto or framing.
Now you'll only see the scrambled liveview, BUT with half shutter press(while holding half shutter), you should be able to see the ML preview.
So set preview option to real-time, do the framing with half shutter press...let half shutter press go and push record button...maybe you'll get 8 frames instead of 4 :P
Cool alpicat. Presets probably coming to crop_rec code soon. For now only proof of concept.
Pixel maps not working since this is considered bleeding edge. Try to set chroma smooth to 2x2, will probably eliminate most of them.
Thanks @Danne and @Levas. It's definitely bleeding edge! That's great to hear it's coming to the crop_rec code soon though. With chroma smoothing at 3x3 the focus pixels are gone - at 2x2 they're still slightly visible.
Yes it should definitely be possible to get a few more frames with real time view mode, or global draw turned off :)
Hello, can someone help me with a little bit of information on using the eos-m? I have the original first version of the eos-m with the latest magic lantern build and using Canon version 2.02 firmware. I have not used this camera for a few years and forgot a few of the specs.
1- Does my eos-m camera stop recording video at 29 minutes? If so, does the magic lantern install eliminate this limit? Or, is there a hack somewhere that eliminates this limitation?
2- I am using a SanDisk 64gb Ultra Plus 80mb/s memory card. I will be shooting 1080 30p video. How many minutes of video can I record to this card?
3- How many minutes will the batteries usually last? I will be shooting a band next week at an outdoor concert for two hours straight. The camera will be recording non-stop until a quick battery change is needed.
4- What steps do I take to make my memory card formatted as exfat? Currently, I am only getting 4gb files when I test the camera and IIRC, that means it is formatted as fat 32 and if I make it exfat format, I can record files larger than 4gb.
I found it hard to find any of this info online probably because there are a few newer models. I appreciate any help.
the battery only lasts about a half hour. i don't think it will record more than 29 minutes either. sorry.
1: Using H.264 (without ML or not): Recording time limit is 29:59. ML can do automated restart but you will loose some frames.
Using ML raw/mlv: No time restriction. Only card space, battery life, cam temperature limit exists.
2: H.264: See manual page 188.
MLV/RAW: Using latest experimental builds + UHS-hack you will be able to use transfer rate between 38 and 55 MByte/s. Do the math.
UHS-hack gives best results (as things are today) with Sandisk Extreme Pro 95MB/s.
BTW: Never heard of Sandisk Ultra Plus 80MB/s. I know Sandisk Ultra (different versions exist with write rates starting at about 20 MByte/s), Extreme, Extreme Plus, Extreme Pro. Label numbers are for read only, you need to know write rates. Get a decent cardreader and use some benchmark program to find out. See www.cameramemoryspeed.com for details.
3: Answered. Consider using external power source.
4: You have to use a cardreader and your PC. Google helps.
You don't need ExFat for recordings exceeding 4 GB.
H.264 recording will be splitt into file chunks up to 4 GB, though. Doesn't matter if ExFat is used or not. And ML will not change this.
ML will be able to use file sizes above 4 GB for MLV/RAW when proper option is set and Exfat is used.
Thank you Walter and TeamSleepKid.
no problem dude. if you do find a power solution let me know. I've been looking for one.
Hello Teamsleepkid and gary2019,
Regarding a power solution, you can try contacting Lanparte. I currently use these: https://www.bhphotovideo.com/c/product/1100255-REG/lanparte_pb_600_e6_e6_portable_battery_with.html
If you can find a dummy battery online, email Lanparte and ask if it would be compatible with their batteries. It is also possible to order without their dummy adapters to keep the price down a bit. BH has some used for sale though.
If Lanparte can verify a dummy battery that will work with their batteries, this would be great. Can help with shooting long events. I can verify this with my Canon 7D and Canon T3i.
- Paul
Thanks, Paul
Hey gary2019,
You're welcome!
- Paul
Added croprec goodies to the eosm:
https://www.magiclantern.fm/forum/index.php?topic=19300.msg203377#msg203377
Quote from: Danne on July 01, 2018, 12:43:43 AM
Added croprec goodies to the eosm:
https://www.magiclantern.fm/forum/index.php?topic=19300.msg203377#msg203377
Thanks for the build, unfortunately it mostly doesn't work for me. I am able to get some shots in 2.5K 16:9, although several frames are corrupted. But i can't get consistent results in 3K, either it won't even start with on screen message "Raw detect error" or it ends almost immediately and when try to play the file it says something about file ending prematurely, or it seems to records garbled live view, or in some cases i can get around 30 frames uncorrupted, but cannot use fps override to get longer shots as it fails immediately. Are you getting better results? I understand highly experimental nature of this, i'm just curious if i'm doing something wrong. (Global draw off, SD overclocked and raw setting are only options i'm using)
Garbled 3K frame
(https://thumb.ibb.co/fKxHbd/M01_0106_000015.jpg) (https://ibb.co/fKxHbd)
@loknar
Are you in x5 zoom mode while recording?
I put up a new version which lower resolution a little to keep corruption away:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jul01.EOSM202_2K-3K-4K.zip
Reference:
For getting a log from eosm. If not working in movie mode, turn off adtg_gui once wanted registers are obtained, then enter photo mode and print the log from there.
Step description from theBilalFakhouri
Quote
1-Use the latest adtg_gui which working in 720p 50/60fps without locking up(Download Here).
2-Enable DIGIC registers in Advanced menu then enable adtg_gui module
3-Select 1080p 25fps from Canon menu --> Enter x5 mode --> Get back to adtg_gui and change in Show menu to "Modified from now on"
4-Get back to mv1080 by pressing zoom button twice --> Log from Advanced settings --> If it didn't log it --> Turn off adtg_gui for not missing the values and go to photo mode then Log again.
A few useful logs:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/ADTG-x5zoom-mv1080p-eosm.LOG
https://bitbucket.org/Dannephoto/magic-lantern/downloads/ADTG_mv720p60fps.LOG
https://bitbucket.org/Dannephoto/magic-lantern/downloads/ADTG_mv720p50fps.LOG
Quote from: Danne on July 01, 2018, 08:59:49 AM
@loknar
Are you in x5 zoom mode while recording?
I put up a new version which lower resolution a little to keep corruption away:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jul01.EOSM202_2K-3K-4K.zip
Yes, in 5x zoom, didn't even try it elsewhere.
You can work magic! :)
Now, 2.5K works (also changing raw resolution in menu is smooth, before it reacted sloppy and with delay, and also each and every resolution step works, no corruption).
3K works (liveview garbled, but as i understood that's a feature for now)
4K works (liveview garbled, but as i understood that's a feature for now)
Also I didn't have any errors whatsoever, so this build works like a charm with my EOS M.
Would it be possible to tailor some high res mode to exactly 15 or 16 fps? It would allow continuous recording at ~65 MB/s and also it could be interpolated by whole number to get "normal" fps (15->30, 16->48). FPS override produces corrupted shots, but i think this is not supposed to work right now(or perhaps at all)?
@loknar
Can you also check this crop_rec (https://www.magiclantern.fm/forum/index.php?topic=19300.msg203316#msg203316) for 700D & EOS M. Just replace it in Danne build for not missing lua and SDoverclock script.
What is working and what isn't working for EOS M ?
Quote from: loknar on July 01, 2018, 09:57:28 AM
Would it be possible to tailor some high res mode to exactly 15 or 16 fps?
You can use FPS override :P
But if you mean 4096x2560 @ 16fps I don't think this is possible (It's the limits). However There are UHD 3840x2160 preset @ 12fps (Maybe we can push this to 14 or 16FPS) in above crop_rec.
@theBilalFakhouri
I tried your build before, 2.5K went fine, but i had problems with 3K, so i've waited "when the dust settles" because i didn't know, whether problem was with build or me using it incorrectly, or on top of incompatible build.
In Danne's build frame override unfortunately produces corrupted videos, so i can adjust (=lower) resolution to get continuous 20.5 fps or 12 fps, or 9.5 fps as defaults in 2.5K, 3K and 4K.
So as far as i'm concerned, live view in 3K and 4K would be nice and functional FPS override would push this micro beast into (yet another) higher class :).
(these are the only things that don't work right now)
Since i'm most into landscapes 3K+ (because of crop factor) in 2.35:1 and 15/16fps continuous would be ultimate feat :).
It's unbelievable how much you guys can get from these cameras :).
@loknar
Hmm,,
The presets is working flawlessly in 700D without any problem --> Some times one corrupted frame in the whole clip not a big deal and the most times there are no corrupted frames. The registers in EOS M is identical to 700D %100 I am wondering why this happening.
The scrambled LiveView is actually a Heavy slicing and tilting for the image of LiveView .
And these registers for Fixing LiveView (https://www.magiclantern.fm/forum/index.php?topic=19300.msg202054#msg202054) but the relationships between these registers is complicated .
Also I am trying to figure out how to expand the cropped area of LiveView in x5 and maybe it's in the registers below not sure @a1ex Do have any information about how to do this?. A real time correct framing in 2520x1080 like normal 1080p ;D .
mv1080 to x5
Canon EOS 700D 1.1.5
0002805f: 37c (was 21c) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56d980 addr=40452d18
00028061: 37c (was 21c) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56d980 addr=40452d1c
00f00005: 300 (was 20) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56da64 addr=404536dc Fine vertical offset, black area maybe
00f00006: 789 (was 78b) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56da64 addr=404536de ISO 50 or timing related: FFF => darker image
00f00007: a49 (was 800) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56da64 addr=404536e0 Looks like the cmos is dieing (g3gg0)
00f00008: 0 (was 400) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56da64 addr=404536e2
c0f09008: 4530a1f (was 4a5070f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff4fe97c addr=189db8
c0f09090: a1f (was 70f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff4feba0 addr=189db8
c0f0b024: 0 (was 14) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff4ff404 addr=189db0
c0f0b028: 0 (was 14) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff4ff414 addr=189db0
c0f08548: 4530a1f (was def152d) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff3826d4 addr=17e288 LV resolution * downsize factor? (RAW.height * D | RAW.width * D)
c0f0854c: 0 (was 7200b04) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff38287c addr=189da0
c0f08550:7fff7fff (was 0) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff38288c addr=189da0
c0f08554:7fff7fff (was df0152e) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff382898 addr=189da0
c0f08558: 1010101 (was 3030303) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff3826c0 addr=ff90b0b4
c0f0855c: 0 (was 10b) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff382834 addr=189da0
c0f08568: 0 (was 20) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff382858 addr=189da0
c0f0856c: 0 (was 4) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff382864 addr=189da0
c0f085a0: 1 (was 0) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3828c8 addr=189da0
c0f08d14: 102 (was 302) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3828d4 addr=189da0
c0f08544: 110 (was 100) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff382828 addr=189da0
c0f08560: 0 (was 800) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff382840 addr=189da0
c0f08570: 0 (was 800) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff382870 addr=189da0
c0f0820c: 50f0000 (was 3870000) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2580 addr=3e244
c0f081bc: 54 (was 3c) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f25c4 addr=3e27c
c0f04808: 210dce4 (was 20f61ec) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=11474 addr=17e298
c0f35084: a1f (was 70f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff280434 addr=29050
c0f35088: 454 (was 4a6) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff280434 addr=29058
c0f3511c: 31 (was 21) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff280434 addr=290a0
c0f26908: 47b711e (was 47af3c6) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=compress_task pc=11474 addr=1b0c70
00028000: 5 (was 6) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56dbc8 addr=40452894 Causes interlacing (g3gg0)
000282b6: 67f (was 6f4) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56efa8 addr=40452de0
00028300: 1 (was 2) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56dbc8 addr=40452898
00028826: d05 (was e05) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=404531cc
00028827: 53 (was 42) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=404531d0
00028828: 3111 (was 3010) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=404531d4
c0f06008: 2cb02cb (was 27f027f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff570228 addr=42a90 FPS register A
c0f0600c: 2cb02cb (was 27f027f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff570228 addr=42a98 FPS related
c0f06010: 2cb (was 27f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff570228 addr=42aa0 FPS related
c0f06804: 4540298 (was 4a601d4) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff570228 addr=42ab0 RAW last line|column. 5D3: f6e|2fe, first 1|18 => 5936x3950
c0f06824: 2ca (was 206) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff570228 addr=42ae0
c0f06828: 2ca (was 206) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff570228 addr=42ae8
c0f0682c: 2ca (was 206) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff570228 addr=42af0
c0f06830: 2ca (was 206) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff570228 addr=42af8
c0f06014: 5d3 (was 7cf) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f19c addr=428a0 FPS register B
c0f0713c: 455 (was 4a7) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff380858 addr=42810 HEAD3 timer (ticks?)
0002800c: 0 (was 2) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56dc9c addr=40452e50 Line skipping factor (2 = 1080p, 4 = 720p, 0 = zoom)
00028183: 0 (was 21) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56dc9c addr=40452e60
00028184: 0 (was 7b) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56dc9c addr=40452e64
00028172: 67c (was 6fd) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56efa8 addr=40452dbc Line count to sample. same as video resolution (g3gg0)
00028173: 775 (was 453) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56efa8 addr=40452dc0
00028178: 67c (was 6fd) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56efa8 addr=40452dc8 dwSrFstAdtg1[4], Line count + 1
00028179: 775 (was 453) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56efa8 addr=40452dcc dwSrFstAdtg1[5]
000288c6: 455 (was 4a4) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=404531fc
000288ca: 6 (was 416) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453204
000288ce: 455 (was 4a4) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=4045320c
000288d2: 6 (was 416) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453214
000288d5: 1d0b (was 903) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453218
000288d6: ef (was 1cb) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=4045321c
000288d7: 454 (was 2f6) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453220
000288d8: 115 (was 1c5) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453224
000288d9: 4e0 (was 308) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453228
000288da: 603 (was 201) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=4045322c
000288db: 1412 (was 706) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453230
000288de: b (was 3) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453238
000288e0: 6 (was 2) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453240
000288e1: 903 (was 1) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453244
000288e6: 3f (was f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453250
000288e7: 80e (was 6) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453254
000288e8: 2031 (was 9) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f178 addr=40453258
00028196: 0 (was 12e) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f2f8 addr=40452e98 dwSrFstAdtg1[2], Line count + 1
00028197: 0 (was 38c) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff56f2f8 addr=40452e9c dwSrFstAdtg1[3]
c0f37a70: 4530a1f (was 4a5070f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f24d8 addr=ff960ab0
c0f37b8c: 4530a1f (was 4a5070f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f24d8 addr=ff960af0
c0f08184: 453 (was 4a5) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f24d8 addr=ff960b90 LV resolution (RAW.height) aka HIV_V_SIZE
c0f08188: a1f (was 70f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f24d8 addr=ff960b98 LV resolution (RAW.width) aka HIV_H_SIZE
c0f08194: a1f (was 70f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f24d8 addr=ff960bb8 LV resolution (RAW.width)
c0f08198: a1f (was 70f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f24d8 addr=ff960bc0 LV resolution (RAW.width)
c0f08434: a1f (was 70f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f24d8 addr=ff960bc8
c0f081dc: a20 (was 0) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f24d8 addr=ff960c08
c0f37ad0: 4530a1f (was 4a5070f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f24d8 addr=ff960cc8
c0f4200c: 1000012 (was 12) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff57cdf0 addr=17e220
c0f42208: 8800800 (was 8900810) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=7646a4
c0f42244: 8800800 (was 8900810) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=7646bc
c0f42348: b40096 (was b40020) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=7646d4
c0f42350: 30003 (was 50005) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=7646e4
c0f42354: ce004b (was ce0026) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=7646ec
c0f4235c: 30003 (was 50005) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=7646fc
c0f42360: b40040 (was b40020) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=764704
c0f42368: 30003 (was 50005) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=764714
c0f42430: 30003 (was 50005) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=764774
c0f4243c: 30003 (was 50005) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=76478c
c0f42440: 32800c8 (was 2800c8) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=764794
c0f42444: 23f010a (was 3f010a) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=76479c
c0f42448: 32800c8 (was 2800c8) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=7647a4
c0f42478: 12c012c (was 2000200) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=AeWb pc=ff3844b4 addr=7647ac
c0f38070: 2b80107 (was 48801b5) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c5bc addr=17e020
c0f38078: 1080001 (was 1b60001) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c5e4 addr=17e020
c0f3807c: 1070000 (was 1b50000) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c5f8 addr=17e020
c0f38080: 2b60002 (was 4860002) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c60c addr=17e020
c0f38084: 1090000 (was 1b70000) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c620 addr=17e020
c0f38094: 2b90000 (was 4890000) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c684 addr=17e020
c0f380a0: 1090000 (was 1b70000) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c698 addr=17e020
c0f380a4: 1090000 (was 1b70000) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c6ac addr=17e020
c0f38024: 4530287 (was 4a501c3) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c4dc addr=17e010
c0f383d4: 15300af (was 1d000e) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c524 addr=17e010 Preview area (y1 | x1/4)
c0f383dc: 40c01b7 (was 4a601c4) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70c6b8 addr=17e020 Preview area (y2 | x2/4)
c0f38934: 2b50107 (was 48501b5) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70e02c addr=17dc60
c0f38960: 2b50000 (was 4850000) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70e0d4 addr=17dc60
c0f389a4: 2b50107 (was 48501b5) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70e224 addr=17dc60
c0f389b4: 2b60108 (was 48601b6) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70e274 addr=17dc60
c0f389d4: 2b50107 (was 48501b5) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70e2c8 addr=17dc60
c0f389e4: 2b60109 (was 48601b7) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70e318 addr=17dc60
c0f389ec: 1080001 (was 1b60001) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff70e34c addr=17dc60
c0f42014: 2b80107 (was 48801b5) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff57ce24 addr=17e220
c0f4204c: 2b80107 (was 48801b5) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff57ce88 addr=17e220
c0f42194: 107 (was 1b5) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff57ceec addr=17e220
c0f3b054: 2b5040f (was 48506c7) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff7069dc addr=17e1e0
c0f3b070: 2b5045f (was 4850717) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff706a04 addr=17e1e0
c0f3b074: 2af045f (was 47f0717) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff706a18 addr=17e1e0
c0f3b0dc: 2af0457 (was 47f070f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff58363c addr=17e218
c0f1a00c: 2af0407 (was 47f06bf) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff96254c LV resolution (raw.j.width | raw.j.height)
c0f11b8c: 0 (was 50009) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff96258c
c0f11b90: 0 (was 20333) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff962594
c0f11b98: 407 (was 3bf) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9625a4
c0f11b9c: 2af0407 (was 47f06bf) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9625ac
c0f11bc8:80000000 (was 0) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9625cc
c0f11bcc: 0 (was 50009) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9625d4
c0f11bd0: 0 (was 20333) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9625dc
c0f11bd8: 2af (was 27f) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9625ec
c0f11bdc: 2af0407 (was 47f03bf) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9625f4
c0f2c01c: 2b00407 (was 28003bf) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9626e4
c0f2c054: 2b10418 (was 28103d0) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff962714
c0f2c0b8: 2b00000 (was 2800000) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff96272c
c0f2c0c0: 40a0000 (was 3c20000) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff96273c
c0f110e0: 14 (was 1) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9627ac
c0f11a8c: 1e002b (was 30004) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9627bc
c0f11a90: 40222 (was 102ab) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9627c4
c0f11a9c: 2af0407 (was 27f03bf) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff9627dc
c0f11acc: 1e002b (was 30004) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff96281c
c0f11ad0: 40222 (was 102ab) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff962824
c0f11adc: 2af02cf (was 27f02cf) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f2f0c addr=ff96283c
c0f04110: 2af0810 (was 27f0780) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff4f3294 addr=ff962b2c
c0f07150: 428 (was 475) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=ff38086c addr=42858 HEAD4 timer (ticks?)
c0f26d34: 0 (was 3) ISO=400 Tv=50 Av=35 lv=0 zoom=10 mv=0 res=-1 crop=-1 task=Evf pc=111e0 addr=24bf88
==================================================================
This is the next big thing will happen to ML .
Quote from: theBilalFakhouri on July 01, 2018, 04:34:54 PM
Also I am trying to figure out how to expand the cropped area of LiveView in x5 and maybe it's in the registers below not sure @a1ex Do have any information about how to do this?. A real time correct framing in 2520x1080 like normal 1080p ;D .
You mean, the preview?
We should figure that out by comparing x5 vs x10 in Canon code. Unfortunately, adtg_gui doesn't seem to capture that info (locking registers in x5 does not keep the image when you select x10). Even reworked the adtg_gui backend locally to use io_trace rather than EngDrvOut/engio_write hooks, just to catch everything, including registers changed by direct MMIO writes. It didn't help.
I have a feeling the secondary processor Eeko may have something to do with this. The main CPU appears to delegate some image processing tasks (after the raw image is captured) to that processor, so understanding what that does
might be the key to figuring this out.
This is probably easier to understand on DIGIC 4 (here, the entire image processing is managed from the main CPU, as far as I could tell). However, that knowledge probably won't help much on D5/6/7; it's very much like all these image effects (https://www.magiclantern.fm/forum/index.php?topic=2120.0) that only work on DIGIC 4 cameras.
Reversing various image processing paths (EekoAddRawPath, FA_MaxSelectTestImage, MJPEG etc)
might be low-hanging fruit that could eventually lead to understanding how the live preview works.
Here is what´s going on when logging H264(mv1080p 24 fps) recording on eosm:
Canon EOS M 2.0.2
000288b0: 0 (was 1) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33ac8 addr=404821d4
00028172: 6fd (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33be8 addr=40481b28 PowerSaveTiming 'on', set to Line count + 1
00028173: d71 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33be8 addr=40481b2c PowerSaveTiming 'off', should be slightly below FPS timer B
00f00008: 400 (was 800) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33e38 addr=404825d0 Unknown, used on 6D
c0f08030: c56 (was 1000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5040f8 addr=1ae700 Digital gain for ISO (SHAD_GAIN)
c0f08d74:80010e00 (was 80010f00) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff504150 addr=1ae700
c0f04808: fef6df0 (was ff00a38) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=1c5f0 addr=1ae6a0
00028882: 473 (was 8e6) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33e98 addr=404821f4 ISO ADTG gain (per column, mod 4 or mod 8)
00028884: 474 (was 8e8) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33e98 addr=404821f8 ISO ADTG gain (per column, mod 4 or mod 8)
00028886: 472 (was 8e4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33e98 addr=404821fc ISO ADTG gain (per column, mod 4 or mod 8)
00028888: 470 (was 8e0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33e98 addr=40482200 ISO ADTG gain (per column, mod 4 or mod 8)
c0f35088: 4a6 (was 2d7) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff27c848 addr=439c4
c0f09008: 4a5070f (was 2d6070f) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=31fdc addr=1ba1b8
c0f0903c: 200064 (was 280064) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=32088 addr=1ba1b8
c0f09040: 4a006f4 (was 2c806f4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=320a4 addr=1ba1b8
c0f0905c: 200064 (was 280064) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=32124 addr=1ba1b8
c0f09060: 4a006f4 (was 2c806f4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=32140 addr=1ba1b8
c0f0b0a0: 57000f (was 5d000f) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=32cb8 addr=1ba1b0
c0f0b100: 78 (was 84) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=32de0 addr=1ba1b0
c0f0b104: f720000 (was f6a0000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=32dfc addr=1ba1b0
c0f42034: 20002 (was 20001) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28ee0 addr=772ec0
c0f42730: 0 (was 1) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28ee0 addr=772ec8
c0f4274c: 29d6 (was 38f4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28ee0 addr=772f00
c0f08548: def152d (was e2e152d) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=280bc addr=4076c2b0 LV resolution * downsize factor? (RAW.height * D | RAW.width * D)
c0f0854c: 7200b04 (was 7580b04) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=280bc addr=4076c2b8
c0f08554: df0152e (was e2f152e) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=280bc addr=4076c2c8
c0f08558: 3030303 (was 5050303) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=280bc addr=4076c2d0
c0f14408:1f000000 (was 3f000000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=menu_redraw_task pc=b4b00 addr=1e9cd0
c0f14808:1f000000 (was 3f000000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=menu_redraw_task pc=a9ba8 addr=1e9ce0
c0f03004:80070002 (was 80160000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a698 addr=1a76b8
c0f03008:80070004 (was 80150000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a698 addr=1a76b8
c0f03010: 0 (was 80130000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff9846e8
c0f03014:80080000 (was 80160002) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a698 addr=1a76b8
c0f03018:80120000 (was 80150002) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a698 addr=1a76b8
c0f03020: 0 (was 80130002) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984700
c0f03030:80130000 (was 80130004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978804
c0f03038:80150000 (was 80050000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978814
c0f0303c: 0 (was 80060000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984718
c0f03064:80130004 (was 80150004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff97881c
c0f03068:800b0000 (was 80160004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978824
c0f03070:80080004 (was 800b0000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a698 addr=1a76b8
c0f038f0: 0 (was 801c0004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984860
c0f038f4: 0 (was 801d0004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984868
c0f038f8: 0 (was 801e0004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984870
c0f038fc: 0 (was 801f0004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984878
c0f03900: 0 (was 80200004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984880
c0f03904:80210008 (was 80210004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff9789c4
c0f03908:80220008 (was 80220004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff9789cc
c0f03934: 0 (was 80280000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984898
c0f0393c: 0 (was 80250004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff9848a0
c0f03950:80230004 (was 80260000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978a0c
c0f03954:80240004 (was 80270000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978a14
c0f03958:80250004 (was 80280002) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978a1c
c0f03964:80280000 (was 80230004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978a34
c0f03968:80280002 (was 80240004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978a3c
c0f030d4: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff9848f0
c0f030e4: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984900
c0f03a24: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff9849d0
c0f03a28: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff9849d8
c0f03a2c: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff9849e0
c0f03a30: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff9849e8
c0f03a34: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff9849f0
c0f03a38: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff9849f8
c0f03a3c: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984a00
c0f03a40: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50ab14 addr=ff984a08
c0f01034: f9fe1 (was f9fe0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff2c4cd0 addr=1a7660
c0f01030: f9fe1 (was f9fe0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff2c4cc4 addr=1a7660
c0f13048: 3 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff2c4e9c addr=1a7658
c0f0301c:80080002 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a698 addr=1a76b8
c0f03060:80120002 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a698 addr=1a76b8
c0f0306c:80050000 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff97882c
c0f030a4:80050003 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff97883c
c0f030ac:80050005 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff97884c
c0f030b0:80040002 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978854
c0f03000:80070000 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a698 addr=1a76b8
c0f0300c:80040000 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff9787f4
c0f030a0:80160004 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978834
c0f030a8:80160006 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054d4 addr=ff978844
000282b6: 6f4 (was 3b4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=359a8 addr=40481be8 PowerSaveTiming 'on'? set to Line count - 1
c0f0713c: 4a7 (was 6f4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=270e0 addr=5df48 HEAD3 timer (ticks?)
0002800c: 2 (was 4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=341e0 addr=40481c14 Line skipping factor (2 = 1080p, 4 = 720p, 0 = zoom)
00028178: 6fd (was 3b7) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=359a8 addr=40481bd0 PowerSaveTiming 'on', set to Line count + 1
00028179: d71 (was 47c) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=359a8 addr=40481bd4 PowerSaveTiming 'off', should be slightly below FPS timer B
000288c6: 4a4 (was 2d4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f24
000288ce: 4a4 (was 2d4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f34
000288d5: 903 (was b03) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f40
000288d6: 1cb (was 11f) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f44
000288d7: 2f6 (was 1d2) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f48
000288da: 201 (was 504) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f54
000288db: 706 (was b0a) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f58
000288df: 0 (was 2) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f60
000288e0: 2 (was 1) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f64
000288e1: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f68
000288e7: 6 (was 5) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f70
000288e8: 9 (was a) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481f74
00028196: 12e (was 190) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35e74 addr=40481ca0 PowerSaveTiming 'on', set to Line count + 1
00028197: 38c (was 13a) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35e74 addr=40481ca4 PowerSaveTiming 'off', should be slightly below FPS timer B
c0f37a70: 4a5070f (was 2d6070f) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff503f44 addr=ff977ff4
c0f37b8c: 4a5070f (was 2d6070f) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff503f44 addr=ff978034
c0f08184: 4a5 (was 2d6) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff503f44 addr=ff9780d4 LV resolution (RAW.height) aka HIV_V_SIZE
c0f37ad0: 4a5070f (was 2d6070f) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff503f44 addr=ff97820c
c0f37014: e (was 22) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff503f44 addr=ff97835c LV raw type (see lv_af_raw, lv_set_raw) - DIGIC V
c0f4200c: 12 (was 2) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e3c addr=772cf8
c0f42348: 570020 (was 140014) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772d38
c0f42354: 610022 (was 140014) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772d50
c0f42360: 570020 (was 140014) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772d68
c0f42368: 50005 (was 30003) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772d78
c0f4236c: 42800c8 (was 52800c8) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772d80
c0f42370: 43f010a (was 33f010a) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772d88
c0f42374: 42800c8 (was 32800c8) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772d90
c0f423b8: 15e015e (was 320032) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772da8
c0f423bc: 1130113 (was c800c8) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772db0
c0f423c0: 600060 (was 320032) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772db8
c0f423c4: 2190219 (was 1f401f4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772dc0
c0f42428: 7d0028 (was 140014) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772dc8
c0f42434: 7d0028 (was 140014) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772de0
c0f42478: ee00ee (was 700070) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772e10
c0f4247c: eb00eb (was 1000100) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772e18
c0f42480: 3a003a (was 120012) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772e20
c0f42484: 1e201e2 (was 2500250) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e90 addr=772e28
c0f38070: 48801b5 (was 2ba01b5) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fc48 addr=1ae3e0
c0f38080: 4860002 (was 2b80002) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fc98 addr=1ae3e0
c0f38094: 4890000 (was 2bb0000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fd10 addr=1ae3e0
c0f38024: 4a501c3 (was 2d601c3) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fb68 addr=1ae3d0
c0f383d4: 1d000e (was 1c000e) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fbb0 addr=1ae3d0 Preview area (y1 | x1/4)
c0f383dc: 4a601c4 (was 2d701c4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fd44 addr=1ae3e0 Preview area (y2 | x2/4)
c0f38934: 48501b5 (was 2b701b5) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff7216b8 addr=1ae020
c0f38960: 4850000 (was 2b70000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721760 addr=1ae020
c0f38998:6c6c6c6c (was e4e4e4e4) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721868 addr=1ae020
c0f3899c: 120001 (was 100000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721888 addr=1ae020
c0f389a4: 48501b5 (was 2b701b5) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff7218b0 addr=1ae020
c0f389b4: 48601b6 (was 2b801b6) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721900 addr=1ae020
c0f389d4: 48501b5 (was 2b701b5) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721954 addr=1ae020
c0f389e4: 48601b7 (was 2b801b7) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff7219a4 addr=1ae020
c0f42014: 48801b5 (was 2ba01b5) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5886e4 addr=1ae5e0
c0f4204c: 48801b5 (was 2ba01b5) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff588748 addr=1ae5e0
c0f3a044: 2ac (was 22c) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff726de0 addr=1ae5d8
c0f3b054: 48506c7 (was 2b706c7) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff719b5c addr=1ae5a0
c0f3b070: 4850717 (was 2b70717) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff719b84 addr=1ae5a0
c0f3b074: 47f0717 (was 2b10717) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff719b98 addr=1ae5a0
c0f3b0dc: 47f070f (was 2b1070f) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff58eefc addr=1ae5d8
c0f1a00c: 47f06bf (was 2b106bf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979b98 LV resolution (raw.j.width | raw.j.height)
c0f11b88:80000000 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979bd0
c0f11b8c: 0 (was 50009) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979bd8
c0f11b90: 0 (was 20333) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979be0
c0f11b98: 6bf (was 3bf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979bf0
c0f11b9c: 47f06bf (was 2b106bf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979bf8
c0f11bc8:80000000 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979c18
c0f11bcc: 0 (was 400045) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979c20
c0f11bd0: 0 (was 50200) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979c28
c0f11bd8: 47f (was 27f) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979c38
c0f11bdc: 47f06bf (was 2b103bf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979c40
c0f2c01c: 48006bf (was 28003bf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979d30
c0f2c054: 48106d0 (was 28103d0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979d60
c0f2c0b8: 4800000 (was 2800000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979d78
c0f2c0c0: 6c20000 (was 3c20000) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979d88
c0f11a8c: 50006 (was 30004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979db0
c0f11a90: 20333 (was 102ab) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979db8
c0f11a98: 59f (was 2cf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979dc8
c0f11a9c: 47f06bf (was 27f03bf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979dd0
c0f111c4: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979df0
c0f11acc: 50006 (was 30004) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979e10
c0f11ad0: 20333 (was 102ab) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979e18
c0f11ad8: 3bf (was 1df) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979e28
c0f11adc: 47f02cf (was 27f02cf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979e30
c0f11588: 1 (was 0) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50489c addr=ff979e58
c0f04110: 47f0d80 (was 27f0780) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff504c60 addr=ff97b70c
c0f1197c: 47f06bf (was 2b106bf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff504fe0 addr=ff978488
c0f11984: 47f06bf (was 2b106bf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff504fe0 addr=ff978498
c0f11388: 0 (was 6073) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff504fe0 addr=ff978510
c0f11394: 0 (was 2b106bf) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff504fe0 addr=ff978520 LV resolution (raw.j.height | raw.j.width)
c0f113bc: 3 (was 1) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff504fe0 addr=ff978530
c0f11a58: 3 (was 1) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff504fe0 addr=ff978558
c0f07150: 46a (was 320) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=270f4 addr=5df90 HEAD4 timer (ticks?)
c0f030c0: 0 (was 2) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a890 addr=1a76b8
c0f26234: 0 (was 3) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=1c264 addr=27bf88
c0f26d34: 0 (was 3) ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=1c35c addr=27bf88
==================================================================
Interesting. Managed to force my eosm into mv1080p by recording h264 while in modified from now on and while recording I locked the registers. Then turned off recording, selected RAW video and started recording in mv1080p.
Ideas build upon theBilalFakhouri wanting some registers sent and from ideas from A1ex prior instructions, dfort etc.
The file is far from perfect. Plays ok in MlRawViewer while Mlv App gets the picture all distorted. Metadata is probably off:
Mv1080p file:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/M01-1640short.MLV
Here´s a log where I hit record (H264 mov) and while recording I go to modified from now on and turn that setting on. When I stop recording the camera goes back into mv720p mode and a bunch of stuff is revealed. adtg_gui is really something...
Canon EOS M 2.0.2
c0f04808: ff00a38 (was fef6df0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=1c5f0 addr=1ae6a0
c0f35088: 2d7 (was 4a6) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff27c848 addr=43a9c
c0f09008: 2d6070f (was 4a5070f) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=31fdc addr=1ba1b8
c0f0903c: 280064 (was 200064) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=32088 addr=1ba1b8
c0f09040: 2c806f4 (was 4a006f4) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=320a4 addr=1ba1b8
c0f0905c: 280064 (was 200064) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=32124 addr=1ba1b8
c0f09060: 2c806f4 (was 4a006f4) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=32140 addr=1ba1b8
c0f08548: e2e152d (was def152d) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=280bc addr=4076c2cc LV resolution * downsize factor? (RAW.height * D | RAW.width * D)
c0f0854c: 7580b04 (was 7200b04) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=280bc addr=4076c2d4
c0f08554: e2f152e (was df0152e) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=280bc addr=4076c2e4
c0f08558: 5050303 (was 3030303) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=280bc addr=4076c2ec
00028172: 3b7 (was 6fd) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33be8 addr=40481b28 PowerSaveTiming 'on', set to Line count + 1
00028173: 47c (was d71) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33be8 addr=40481b2c PowerSaveTiming 'off', should be slightly below FPS timer B
00f00008: 800 (was 400) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=33e38 addr=4048258c Unknown, used on 6D
c0f14408:3f000000 (was 1f000000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=menu_redraw_task pc=afbb4 addr=1e9cd0
c0f14808:3f000000 (was 1f000000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=menu_redraw_task pc=afbc0 addr=1e9cd0
c0f03004:80160000 (was 80070002) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984398
c0f03008:80150000 (was 80070004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843a0
c0f03010:80130000 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843a8
c0f03014:80160002 (was 80080000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843b0
c0f03018:80150002 (was 80120000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843b8
c0f03020:80130002 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843c0
c0f03030:80130004 (was 80130000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843c8
c0f03038:80050000 (was 80150000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843d0
c0f0303c:80060000 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843d8
c0f03064:80150004 (was 80130004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843e0
c0f03068:80160004 (was 800b0000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843e8
c0f03070:800b0000 (was 80080004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9843f0
c0f038f0:801c0004 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984520
c0f038f4:801d0004 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984528
c0f038f8:801e0004 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984530
c0f038fc:801f0004 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984538
c0f03900:80200004 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984540
c0f03904:80210004 (was 80210008) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984548
c0f03908:80220004 (was 80220008) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984550
c0f03934:80280000 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984558
c0f0393c:80250004 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984560
c0f03950:80260000 (was 80230004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984568
c0f03954:80270000 (was 80240004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984570
c0f03958:80280002 (was 80250004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984578
c0f03964:80230004 (was 80280000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984590
c0f03968:80240004 (was 80280002) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984598
c0f030d4: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9845b0
c0f030e4: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9845c0
c0f03a24: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984690
c0f03a28: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff984698
c0f03a2c: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9846a0
c0f03a30: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9846a8
c0f03a34: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9846b0
c0f03a38: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9846b8
c0f03a3c: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9846c0
c0f03a40: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50aaf0 addr=ff9846c8
c0f01034: f9fe0 (was f9fe1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff2c4cd0 addr=1ae628
c0f01030: f9fe0 (was f9fe1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff2c4cc4 addr=1ae628
000282b6: 3b4 (was 6f4) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=359a8 addr=40481be8 PowerSaveTiming 'on'? set to Line count - 1
c0f0713c: 6f4 (was 4a7) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=270e0 addr=5df48 HEAD3 timer (ticks?)
0002800c: 4 (was 2) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=341e0 addr=40481c14 Line skipping factor (2 = 1080p, 4 = 720p, 0 = zoom)
00028178: 3b7 (was 6fd) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=359a8 addr=40481bd0 PowerSaveTiming 'on', set to Line count + 1
00028179: 47c (was d71) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=359a8 addr=40481bd4 PowerSaveTiming 'off', should be slightly below FPS timer B
000288c6: 2d4 (was 4a4) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481fd4
000288ce: 2d4 (was 4a4) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481fe4
000288d5: b03 (was 903) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481ff0
000288d6: 11f (was 1cb) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481ff4
000288d7: 1d2 (was 2f6) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40481ff8
000288da: 504 (was 201) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40482004
000288db: b0a (was 706) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40482008
000288df: 2 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40482010
000288e0: 1 (was 2) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40482014
000288e1: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40482018
000288e7: 5 (was 6) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40482020
000288e8: a (was 9) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35c44 addr=40482024
00028196: 190 (was 12e) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35e74 addr=40481ca0 PowerSaveTiming 'on', set to Line count + 1
00028197: 13a (was 38c) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=35e74 addr=40481ca4 PowerSaveTiming 'off', should be slightly below FPS timer B
c0f37a70: 2d6070f (was 4a5070f) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509198 addr=ff983e28
c0f37b8c: 2d6070f (was 4a5070f) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509198 addr=ff983e68
c0f08184: 2d6 (was 4a5) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509198 addr=ff983f08 LV resolution (RAW.height) aka HIV_V_SIZE
c0f37ad0: 2d6070f (was 4a5070f) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509198 addr=ff984040
c0f37014: 22 (was e) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509198 addr=ff984190 LV raw type (see lv_af_raw, lv_set_raw) - DIGIC V
c0f4200c: 2 (was 12) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=AeWb pc=28e3c addr=772d14
c0f38070: 2ba01b5 (was 48801b5) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fc48 addr=1ae3e0
c0f38080: 2b80002 (was 4860002) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fc98 addr=1ae3e0
c0f38094: 2bb0000 (was 4890000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fd10 addr=1ae3e0
c0f38024: 2d601c3 (was 4a501c3) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fb68 addr=1ae3d0
c0f383d4: 1c000e (was 1d000e) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fbb0 addr=1ae3d0 Preview area (y1 | x1/4)
c0f383dc: 2d701c4 (was 4a601c4) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff71fd44 addr=1ae3e0 Preview area (y2 | x2/4)
c0f38934: 2b701b5 (was 48501b5) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff7216b8 addr=1ae020
c0f38960: 2b70000 (was 4850000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721760 addr=1ae020
c0f38998:e4e4e4e4 (was 6c6c6c6c) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721868 addr=1ae020
c0f3899c: 100000 (was 120001) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721888 addr=1ae020
c0f389a4: 2b701b5 (was 48501b5) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff7218b0 addr=1ae020
c0f389b4: 2b801b6 (was 48601b6) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721900 addr=1ae020
c0f389d4: 2b701b5 (was 48501b5) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff721954 addr=1ae020
c0f389e4: 2b801b7 (was 48601b7) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff7219a4 addr=1ae020
c0f42014: 2ba01b5 (was 48801b5) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5886e4 addr=1ae5e0
c0f4204c: 2ba01b5 (was 48801b5) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff588748 addr=1ae5e0
c0f3a044: 22c (was 2ac) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff726de0 addr=1ae5d8
c0f3b054: 2b706c7 (was 48506c7) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff719b5c addr=1ae5a0
c0f3b070: 2b70717 (was 4850717) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff719b84 addr=1ae5a0
c0f3b074: 2b10717 (was 47f0717) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff719b98 addr=1ae5a0
c0f3b0dc: 2b1070f (was 47f070f) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff58eefc addr=1ae5d8
c0f1a00c: 2b106bf (was 47f06bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff98570c LV resolution (raw.j.width | raw.j.height)
c0f11b88: 0 (was 80000000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff985744
c0f11b8c: 50009 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff98574c
c0f11b90: 20333 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff985754
c0f11b98: 3bf (was 6bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff985764
c0f11b9c: 2b106bf (was 47f06bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff98576c
c0f11bc8: 0 (was 80000000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff98578c
c0f11bcc: 400045 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff985794
c0f11bd0: 50200 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff98579c
c0f11bd8: 27f (was 47f) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff9857ac
c0f11bdc: 2b103bf (was 47f06bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff9857b4
c0f2c01c: 28003bf (was 48006bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff9858a4
c0f2c054: 28103d0 (was 48106d0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff9858d4
c0f2c0b8: 2800000 (was 4800000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff9858ec
c0f2c0c0: 3c20000 (was 6c20000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff9858fc
c0f11a8c: 30004 (was 50006) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff985924
c0f11a90: 102ab (was 20333) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff98592c
c0f11a98: 2cf (was 59f) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff98593c
c0f11a9c: 27f03bf (was 47f06bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff985944
c0f111c4: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff985964
c0f11acc: 30004 (was 50006) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff985984
c0f11ad0: 102ab (was 20333) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff98598c
c0f11ad8: 1df (was 3bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff98599c
c0f11adc: 27f02cf (was 47f02cf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff9859a4
c0f11588: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff509eb8 addr=ff9859cc
c0f04110: 27f0780 (was 47f0d80) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50a324 addr=ff985c8c
c0f1197c: 2b106bf (was 47f06bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50a6b0 addr=ff988548
c0f11984: 2b106bf (was 47f06bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50a6b0 addr=ff988558
c0f11388: 6073 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50a6b0 addr=ff9885d0
c0f11394: 2b106bf (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50a6b0 addr=ff9885e0 LV resolution (raw.j.height | raw.j.width)
c0f113bc: 1 (was 3) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50a6b0 addr=ff9885f0
c0f11a58: 1 (was 3) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff50a6b0 addr=ff988618
c0f07150: 320 (was 46a) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=270f4 addr=5df90 HEAD4 timer (ticks?)
c0f0300c: 0 (was 80040000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978b3c
c0f0302c: 0 (was 80020000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978b44
c0f03034: 0 (was 80160000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978b54
c0f0306c: 0 (was 80050000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978b74
c0f030a0: 0 (was 80160004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978b7c
c0f030a4: 0 (was 80050003) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978b84
c0f030a8: 0 (was 80160006) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978b8c
c0f030ac: 0 (was 80050005) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978b94
c0f030b0: 0 (was 80040002) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978b9c
c0f030f0: 0 (was 80040004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978ba4
c0f038c8: 0 (was 801c0004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978cdc
c0f038cc: 0 (was 801d0004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978ce4
c0f038d0: 0 (was 801e0004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978cec
c0f038d4: 0 (was 801f0004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978cf4
c0f038d8: 0 (was 80200004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978cfc
c0f038dc: 0 (was 80210004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978d04
c0f038e0: 0 (was 80220004) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978d0c
c0f0390c: 0 (was 801c0008) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978d3c
c0f03910: 0 (was 801d0008) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978d44
c0f03914: 0 (was 801e0008) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978d4c
c0f03918: 0 (was 801f0008) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978d54
c0f0391c: 0 (was 80200008) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978d5c
c0f03940: 0 (was 80260000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978d64
c0f03944: 0 (was 80270000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978d6c
c0f03048: 1 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978dac
c0f03050: 1 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=Evf pc=ff5054f8 addr=ff978db4 Playback: vertical banding / darken?
c0f13048: 0 (was 3) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff2c511c addr=1a7480
c0f13058: 0 (was 1133) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff730394 addr=1a7478
c0f03000: 0 (was 80070000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a7750
c0f03024: 0 (was 80070006) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74f0
c0f0301c: 0 (was 80080002) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a7750
c0f03060: 0 (was 80120002) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74f0
c0f03200: 0 (was 80270000) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03204: 0 (was 80270003) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03208: 0 (was 80270006) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f0320c: 0 (was 80270009) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03210: 0 (was 8027000c) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03214: 0 (was 8027000f) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03218: 0 (was 80270012) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f0321c: 0 (was 80270015) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03220: 0 (was 80270018) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03224: 0 (was 8027001b) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03228: 0 (was 8027001e) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f0322c: 0 (was 80270021) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03230: 0 (was 80270024) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03234: 0 (was 80270027) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03238: 0 (was 8027002a) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f0323c: 0 (was 8027002d) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03240: 0 (was 80270030) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03244: 0 (was 80270033) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03248: 0 (was 80270036) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f0324c: 0 (was 80270039) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03250: 0 (was 8027003c) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03254: 0 (was 8027003f) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03258: 0 (was 80270042) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f0325c: 0 (was 80270045) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03260: 0 (was 80270048) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03264: 0 (was 8027004b) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03268: 0 (was 8027004e) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f0326c: 0 (was 80270051) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03270: 0 (was 80270054) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03274: 0 (was 80270057) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48a6cc addr=1a74e8
c0f03074: 1 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48aa9c addr=1a74f8 Playback: horizontal banding (500D only?)
c0f03078: 1 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48aab4 addr=1a7758
c0f030c0: 1 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48ab5c addr=1a74f8
c0f03040: 1 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48ae3c addr=1a74f0
c0f03340: 1 (was 0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff48ae48 addr=1a74f0
c0f04d08: ddf6088 (was 72dfb0) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff73044c addr=1a7478
c0f13008: 101 (was 112) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71b47c addr=1a7450
c0f1300c: 280 (was c00) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71b4a4 addr=1a7450
c0f13010: 3c0 (was f00) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71b4d0 addr=1a7450
c0f13014: 0 (was 9) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71b4dc addr=1a7450
c0f13018: 77009f (was 44f00bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71b4f0 addr=1a7450
c0f1301c: 0 (was bf) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71b4fc addr=1a7450
c0f11094: 13 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff7304a4 addr=1a7478
c0f11114: 3 (was b) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71dc14 addr=1a73e8
c0f11184: 0 (was 7) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71c0f4 addr=1a7430
c0f11188: 0 (was 10000334) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71c100 addr=1a7430
c0f04408: ddf7348 (was dd4a07c) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff7300e0 addr=1a7440
c0f04400: 4 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=RscMgr pc=ff413ff8 addr=27bfa0
c0f13128: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff723ae4 addr=1a74b0
c0f13140: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff72fcb8 addr=1a74b8
c0f1304c: 0 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=MovieRecorder pc=ff71b418 addr=1a74e0
c0f04d00: 4 (was 1) ISO=800 Tv=60 Av=45 lv=1 zoom=1 mv=1 res=0 crop=0 task=RscMgr pc=ff41402c addr=27bfa0
==================================================================
EDIT:
A few more mv1080p files:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/M01-1731_14bitlossless.MLV
https://bitbucket.org/Dannephoto/magic-lantern/downloads/M01-172912bitlossless.MLV
https://bitbucket.org/Dannephoto/magic-lantern/downloads/M01-173012bitlossless.MLV
Got an idea for mv1080. After enabling the 3x3 preset in crop_rec, run this from don't click me, while in LiveView 1080p:
EngDrvOut(0xC0F06804, 0x4a601d4);
That should change the raw resolution on the fly. This particular register is changed only when switching video modes, so the above should work. I've tested it on 5D3 with magic value 0x528011B starting from 720p 3x3 overridden to 30 fps. It almost worked (with corrupted frames).
Also make sure you have the generic PowerSave stuff enabled in crop_rec on the 3x3 preset. According to your latest log, it might be important. oops, that won't work; PowerSave registers are also set once when switching video modes; still, if you can get valid image with black bars at the bottom, that's a good sign.
Solved the corrupted frames by changing the HEAD timers. That should be done from a crop_rec preset, but first step is to get an image with the right dimensions; expecting only the top half to look fine at this stage.
Oki, I have never put in a line in 'don´t click me'. Is it in debug.c? Could you hand me this one by putting it in a code example :P?
Quote from: loknar on July 01, 2018, 02:52:20 PM
@theBilalFakhouri
In Danne's build frame override unfortunately produces corrupted videos, so i can adjust (=lower) resolution to get continuous 20.5 fps or 12 fps, or 9.5 fps as defaults in 2.5K, 3K and 4K.
Since i'm most into landscapes 3K+ (because of crop factor) in 2.35:1 and 15/16fps continuous would be ultimate feat :).
It's unbelievable how much you guys can get from these cameras :).
Loknar,
For your information, with Danne's build from June 30-th, on the 100D, I get
CONTINUOUS recording with sound at:
- 3096x1320, 15 fps
- 3840x2160, 4056x2552, 4 fps By underexposing by one stop, I can squeeze 1 fps more in both modes but that's it.
In my opinion, it will be very difficult to push 4k to 15/16 fps unless the SD-card interface is overclocked to 80 MB/s write speed and stable recording at 8 ... 11 bit lossless is achieved.
As far as corrupt frames are concerned, please check whether you are not in 12 or 8 ... 11 bit lossless. This build works
only with 14-bit lossless compression. At this bit rate recording stops when buffer is full but there is no frame corruption at all.
Quote from: Danne on July 01, 2018, 06:44:47 PM
Oki, I have never put in a line in 'don´t click me'. Is it in debug.c? Could you hand me this one by putting it in a code example :P?
Look for this:
src/debug.c
static void run_test()
{
}
Now add the code a1ex told you to run in there:
static void run_test()
{
EngDrvOut(0xC0F06804, 0x4a601d4);
}
I haven't tried this and am not sure if it needs something else before it will work but when you select "Don't click me!" from the debug menu it will run whatever is in that run_test() function.
#ifdef FEATURE_DONT_CLICK_ME
{
.name = "Don't click me!",
.priv = run_test,
.select = run_in_separate_task,
.help = "The camera may turn into a 1DX or it may explode."
},
Tried above dfort when here:
QuoteGot an idea for mv1080. After enabling the 3x3 preset in crop_rec, run this from don't click me, while in LiveView 1080p:
So canon menu set to mv1080p 24 fps counts as LiveView 1080p even since we are are actually in mv720p always. Could get the image to change so croprec 3x3 footage and preview comes out the same. Missing something?
Raw video preview (the slow one) still the same?
Max resolution displayed in the raw video menu still the same?
I don't expect Canon preview to change at all, but recorded raw video should change. The modification is temporary - it only stays there until you exit LiveView; if you do that, you will have to run that snippet again.
Tried the don´t click me snippet in my version of crop_rec and the version from crop_rec_4k_mlv_snd. Nothing seems to bite on eosm. Checked also against "slow preview". As a matter of fact only time I am able to change resolution is while filming H264 mov and during this period entering RAW video(check pic). Old news by now. Of course, by the time I exit back to my ongoing recording mov file liveview freezes.
Are you actually being able to change resolution while also in mv720p mode with this snippet? Over here liveview is probably treated as mv720p also when selecting mv1080p(you know this already)
theBilalFakhouri seems to have some registers working for running mv1080p in mv720p mode. Seems to work on 700D but not on eosm. Maybe he posts his code soon.
(https://s8.postimg.cc/jcwb0fscl/Screen_Shot_2018-07-01_at_21.19.18.png_scaled.jpg)
Yes, on 5D3 I'm able to change the resolution from 720p (with the 3x3 preset in crop_rec and FPS override to 24 or 30) to 1080p with this method. Can you try on 100D?
Also, if you are able to keep the mv1080 by locking the registers in adtg_gui, can you find a minimal subset of registers that have to be locked? (trial and error: after locking all the registers, deselect some of them with the Q key until it breaks)
Tested on 100D and the don´t click me snippet is affecting it. I could even get it up to around 1100 vertical but retrying couldn´t get it back. Trying to record gave raw detect error. Then tried some more with eosm against various builds but still no luck here. Will not bite.
Will try the register in mv1080 some more when I get some rest.
THanks
Alright, here's the io_trace backend for adtg_gui (https://bitbucket.org/hudson/magic-lantern/commits/0a2e1167f5b7f68dafebd6363b17b5a704432407); I'd expect it to help with this mystery.
Write down the values of 0xC0F06804 in standby vs recording (this time I expect different values), and also the fine print.
BTW...
Quote from: a1ex on July 01, 2018, 05:02:39 PM
This is probably easier to understand on DIGIC 4 (here, the entire image processing is managed from the main CPU, as far as I could tell). However, that knowledge probably won't help much on D5/6/7; it's very much like all these image effects (https://www.magiclantern.fm/forum/index.php?topic=2120.0) that only work on DIGIC 4 cameras.
Confirmed on 60D - latest adtg_gui is able to lock the zoom factor between x5 and x10 (so the image no longer doubles). Procedure: simply locking the registers modified between x5 and x10. As expected, this doesn't work on 5D3.
(https://a1ex.magiclantern.fm/bleeding-edge/lv-preview/60D_x5_vs_x10.png)
Screenshot: 60D registers specific to x5 (the "was" values are from x10).
Caveat: the iso-research branch does not work out of the box on 60D (fix is not straightforward; for quick tests I just comment out the stuff that locks up).
Cool. What branch can I drop this version of adtg_gui into? Linking error in crop_rec_4k and iso_research gives this compiling for eosm:
[ AR ] newlib-libc.a
[ CP ] newlib-libm.a
[ CP ] gcc-libgcc.a
[ LD ] magiclantern
installer.o: In function `copy_and_restart':
/Users/dan/magic-lantern_Daniel/installer/EOSM.202/../../src/installer.c:246: undefined reference to `sync_caches'
fio-ml.o: In function `FIO_WriteFile':
/Users/dan/magic-lantern_Daniel/installer/EOSM.202/../../src/fio-ml.c:554: undefined reference to `sync_caches'
make[1]: *** [magiclantern] Error 1
make: *** [installer_check] Error 2
logout
Wait a minute. Getting the above error also when trying to compile a ML build for eosm in crop_rec_4k branch. Something with the latest update?
@Danne
Compile a new build from crop_rec_4k branch .
There is also a new commit (https://bitbucket.org/hudson/magic-lantern/commits/378698f9560110fd98f3587e5c4dbc43d9a60ee7).
EDIT: Tried to compile from crop_rec_4k I also got an error.
C:\cygwin\home\Bilal4Fakhouri\magic-lantern\installer\700D.115/../../src/installer.c:246: undefined reference to `sync_caches'
fio-ml.o: In function `FIO_WriteFile':
C:\cygwin\home\Bilal4Fakhouri\magic-lantern\installer\700D.115/../../src/fio-ml.c:554: undefined reference to `sync_caches'
make[1]: *** [../../src/Makefile.src:198: magiclantern] Error 1
make[1]: Leaving directory '/home/Bilal4Fakhouri/magic-lantern/installer/700D.115'
make: *** [../../platform/Makefile.platform.extras:53: installer_check] Error 2
Yes, that´s the branch I compiled from. Not working here.
I lack time right now. If you get it to compile maybe pm me a version?
Even after "make clean; make" ? Can you show the full log? I've tried with gcc-arm-none-eabi-5_4-2016q3, gcc-arm-none-eabi-6-2017-q2-update, gcc-arm-none-eabi-7-2017-q4-major and gcc-linaro-7.2.1-2017.11-x86_64_arm-eabi, from platform/EOSM.202, commit 378698f. Couldn't get this error...
edit: ok, found; it appears only when building with "make zip"; use _sync_caches (add an underscore) in installer.c until I'll figure out how to fix it.
The value of 0xC0F06804 while recording H.264 in EOS M is 0x4a601d4 the same in 700D at 1080p and the others registers values too (PowerSaveTiming & ReadOutTiming) .
I made a preset in crop_rec "mv1080 in EOS M" in this commit (https://bitbucket.org/bilal_fakhouri/magic-lantern-crop_rec/commits/df4cab0f2cdf25e99b14f9e663ebd2f58c204392) which is working fine to bring mv1080 @ 25fps in mv720 with stretched LiveView and without corrupted frames unlike EOS M the resolution hasn't changed .
A new register here ?
This how it's look like in 700D:
https://www.youtube.com/watch?v=ZQnFu3X5rKs
Yeah; the mystery is why that value doesn't change in standby vs recording in adtg_gui. EOS M has some unique behavior: when not recording, LiveView is always in 720p30, regardless of Canon menu setting. However, register 0xC0F06804, which sets the captured raw image size, doesn't show up as "modified" in adtg_gui when you start recording H.264 1080p (it's not in this log (https://www.magiclantern.fm/forum/index.php?topic=9741.msg203417#msg203417), for example); furthermore, there is a hardcoded exception in raw.c near line 558 that suggests this register might be modified in some way other than EngDrvOut or engio_write. It is this hypothesis that I'd like to check with the latest adtg_gui.
Soon have a few hours here to fiddle on this. Yesterday was hectic 8)
Quote from: a1ex on July 02, 2018, 09:42:58 PM
edit: ok, found; it appears only when building with "make zip"; use _sync_caches (add an underscore) in installer.c until I'll figure out how to fix it.
This:
// Make sure that our self-modifying code clears the cache
sync_caches();To this?:
// Make sure that our self-modifying code clears the cache
_sync_caches();Stiil won´t let me copmile from iso_research branch. I can compile the the adtg_gui alone but not the full eosm version.
Compiled a eosm build in crop_rec_k and then added the adtg_gui.mo from iso-research branch. Getting undefined sybol 'sync_caches' issue.
By the way, how are you compiling without make zip?
If I could get a working adtg_gui.mo linked I could get going asap.
If you compile from some branch derived from crop_rec_4k (anything other than 5684ac8 or ba4ffcc at the time of writing), make sure you sync with the latest one (hg pull && hg merge crop_rec_4k). Or just with patchmgr.
Ok, a1ex, back on it.
Got a version from theBilalFakhouri to test.
By the way. Erasing the exception below in raw.c is opening up to vertical 1160. However footage is corrupted but this coul be the restriction issue?
#ifdef CONFIG_EOSM
/* EOS M exception */
/* http://www.magiclantern.fm/forum/index.php?topic=16608.msg176023#msg176023 */
if (lv_dispsize == 1 && !video_mode_crop && !RECORDING_H264)
{
*height = 727;
}
#endif
136x1160:
corruption every other frame comrrupted, lines at bottom. All bits shows corruption:
(https://s15.postimg.cc/icuslkegb/Screen_Shot_2018-07-03_at_12.15.19.png_800px.jpg)
Tested against code registers found by theBilalFakhouri:
https://bitbucket.org/Dannephoto/magic-lantern/commits/1f80cf380404622d39d3ca6a750281c7a18f9e37?at=crop_rec_4k_mlv_lite_snd_sd_uhs_HDR_croprec
Does the corruption look like this, or different? https://www.magiclantern.fm/forum/index.php?topic=16608.msg176083#msg176083
"By the way. Erasing the exception below in raw.c is opening up to vertical 1160." -> does this happen even right after startup, or only after recording a H.264 clip?
Also try to change these:
case 0xC0F0713c: return 0x6f4; /* unsure; also try deleting */
case 0xC0F07150: return 0x46a;
Maybe also try not to change the FPS (delete entries for 0xC0F06008 ... 0xC0F06014) or override it to some low value (10 fps or so).
Ok, will try registers provided:
Footage looks osmething like lnked to:
In regular mv720p(or canon mv1080p for that matter)
https://bitbucket.org/Dannephoto/magic-lantern/downloads/default_liveview_mv720p.MLV
Original 3x3_crop_rec code:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/mv3x3_720p.MLV
bilal tryout:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/mv1080p_in720p_mode.MLV
Quote
"By the way. Erasing the exception below in raw.c is opening up to vertical 1160." -> does this happen even right after startup, or only after recording a H.264 clip?
Raw video is set to 0x0 when starting up camera. When fiddling with crop_rec settings I´m still kept with 1736x1160 after turning crop_rec off but not before.
QuoteRaw video is set to 0x0 when starting up camera.
Okay, that starts ringing a bell. So, with the exception erased, without enabling H.264 or crop_rec, are you able to get some valid resolution in the raw video menu?
Sometimes it´s gets enabled when turning it on and off. All resolutions are showing when checking into the menu section.
Well, some good news. I shaved it to this in raw.c and footage seems corruption free. Only recorded one clip(uploading as we speak):
#ifdef CONFIG_EOSM
/* EOS M exception */
/* http://www.magiclantern.fm/forum/index.php?topic=16608.msg176023#msg176023 */
if (lv_dispsize == 1 && !video_mode_crop && !RECORDING_H264)
{
*height = 1080;
}
#endifLet´s me set vertical resolution to 1048, will try to find edge for vertical resolution until it starts getting corrupted. This works with bilals registers published above.
EDIT 1:
Seems to only work with 14bit-lossles but hey, better than poop before.
https://bitbucket.org/Dannephoto/magic-lantern/downloads/M03-1229.MLV
EDIT 2: Tried suggested added and erased registers before A1ex but didn´t change anything for the better.
EDIT 3: 1736x1088 working...
EDIT 4: 1736x1120 working...
EDIT 4: In raw.c
*height = 1160;Getting us earthquake material
EDIT 4: In raw.c
*height = 1150;Working getting us
1736x11201736x1120 MLV file(14bit-lossless):
https://bitbucket.org/Dannephoto/magic-lantern/downloads/eosm_mv1080p_mr_cat.MLV
Finally:1736x1120 seems to be max here. Totally epic that this actually is working now. No way this would work without the helping hand of a lot of people. A1ex, g3gg0, dfort, rbune and more. Finally this guy nails the registers.
theBilalFakhouri! Epic work.
First one :):
Here is test version:
mv1080p for eosmhttps://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jul03.EOSM202_mv1080p.zip
Select 3x3_mv1080p_EOSM from Crop mode menu.
You will be able to get good footage in 14bit lossless. You can select 24fps and also global draw on for full frame preview. Preview is a bit wonky atm but there´s some serious skill out there(in here) so maybe that will be better with time. Probably continous with sd_uhs hack on(seems continuous without at 24fps).
Other modes might be broken since I modified exception code in raw.c.
Great work for all guys helped for getting this and Congratulations for EOS M users :D
Next thing to fix LiveView ;)
Quote from: Danne on July 03, 2018, 12:59:31 PM
Finally:
1736x1120 seems to be max here. Totally epic that this actually is working now. No way this would work without the helping hand of a lot of people. A1ex, g3gg0, dfort, rbune and more. Finally this guy nail the registers. theBilalFakhouri! Epic work.
Well done @Danne and everyone involved, this is legendary work and that footage looks awesome! Being able to shoot raw with the full aps-c sensor is going to be amazing - especially because Viltrox are close to releasing their ef-m to ef 0.71x speed booster, which will allow people to turn this into a full frame camera if they want!
With this resolution I'm assuming it pretty much uses the full sensor height (i.e. close to 3:2 aspect ratio)? If so that makes anamorphic shooting a nice option here too.
I've tested @Bilal's croprec module with 2.5k mode, but shooting at a lower resolution of 2224x1200 to get longer record times (10-20 seconds). Shot 14 minutes of footage and not a single problem - thanks so much for this!:
Here is test version:
mv1080p for eosm
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jul03.EOSM202_mv1080p.zip
Select 3x3_mv1080p_EOSM from Crop mode menu.
You will be able to get good footage in 14bit lossless. You can select 24fps and also global draw on for full frame preview. Preview is a bit wonky atm but there´s some serious skill out there(in here) so maybe that will be better with time. Probably continous with sd_uhs hack on(seems continuous without at 24fps).
Other modes might be broken since I modified exception code in raw.c.
Great, this works perfectly for me. Thanks so much - I think I'll be using this camera a lot more often now! Have tried without the sd uhs hack so far. Liveview preview is slightly stretched but totally usable. When global draw is on it says Mv 3x5 along the bottom on the liveview screen, is that normal or should that be 3x3?
Hehe, I think *bilal* can answer about stretch modes :)
Nice illustration of the new modes with increased resolution, Alpicat! You may want to try also 3096x1320 at somewhat reduced frame rate (say 15 or 16 fps). You will be amazed at the quality!
Quote from: alpicat on July 03, 2018, 03:33:42 PM
When global draw is on it says Mv 3x5 along the bottom on the liveview screen, is that normal or should that be 3x3?
It should be fixed somewhere in the code because this unusual for EOS M,, it's actually 3x3 when enabling the preset and You can't get up to 1120 height in 3x5 ;).
It's very fishy. Earlier code(when mv1080p wasn't working) gave correct liveview with global draw. Now this. Maybe some register in my code?
https://s8.postimg.cc/7ozhy1eud/Screenshot_20180703-183716.png
Trying to add support for different frame rates; currently it's hardcoded to 25p; was the sample clip recorded with FPS override at 24?
One puzzle I'd like you to solve: what is the minimal value of timer A that still gives valid image? (without borders on the right side)
Code from fps-engio.c suggests 520 = 0x208. That means, in this block, use 0x207 instead of 0x27f (the hardware expects timerA - 1):
case 0xC0F0600c: return 0x27f027f;
case 0xC0F06008: return 0x27f027f;
case 0xC0F06010: return 0x27f;
If 520 doesn't work, try something higher, until 640. If 520 works, try 510 or so - it should break.
Binning factors and vertical resolution override can be updated from raw_info_update_cbr, so raw.c can stay untouched. Will post a patch soon.
Yes, fps override 24fps.
Gonna do some fast tests here from suggestions above. Unfortunately I don´t have the time I want for this atm. But hey, who´s in a hurry right :P
Need to go out for a while...
I've been using 23.98fps override. Works well but I think the video is coming out darker than what I recorded, so I have to increase the exposure in post to compensate. I don't know if I'm doing something wrong, will test further including shooting at 25p. I can confirm that the sd uhs hack functions properly though - recording is fully continuous. Also it's definitely 3x3, if it were 3x5 I'd be getting a lot more moire!
EDIT: my bad, exposure is fine - my monitor brightness was turned right down so everything was looking dark.
@IDA_ML definitely need to try doing timelapses with the higher resolutions, I'll need a tripod for that though!
Quote from: a1ex on July 03, 2018, 06:43:51 PM
Trying to add support for different frame rates; currently it's hardcoded to 25p; was the sample clip recorded with FPS override at 24?
One puzzle I'd like you to solve: what is the minimal value of timer A that still gives valid image? (without borders on the right side)
Code from fps-engio.c suggests 520 = 0x208. That means, in this block, use 0x207 instead of 0x27f (the hardware expects timerA - 1):
case 0xC0F0600c: return 0x27f027f;
case 0xC0F06008: return 0x27f027f;
case 0xC0F06010: return 0x27f;
If 520 doesn't work, try something higher, until 640. If 520 works, try 510 or so - it should break.
Binning factors and vertical resolution override can be updated from raw_info_update_cbr, so raw.c can stay untouched. Will post a patch soon.
Not sure what to test here but following and adding following doesn´t change anything with performance:
case 0xC0F06014: return 0x7cf;
case 0xC0F0600c: return 0x207027f;
case 0xC0F06008: return 0x207027f;
case 0xC0F06010: return 0x207;
case 0xC0F37014: return 0xe;In fps-engio.c changing:
#elif defined(CONFIG_EOSM)
#define TG_FREQ_BASE 32000000
#define FPS_TIMER_A_MIN (ZOOM ? 716 : MV1080CROP ? 532 : 520)to this doesn+t change anything:
#elif defined(CONFIG_EOSM)
#define TG_FREQ_BASE 32000000
#define FPS_TIMER_A_MIN (ZOOM ? 716 : MV1080CROP ? 532 : 520)Not even this:
#elif defined(CONFIG_EOSM)
#define TG_FREQ_BASE 32000000
#define FPS_TIMER_A_MIN (ZOOM ? 716 : MV1080CROP ? 532 : 500)Am I following correctly, couldn´t get it to break anyway.
Different frame rates from Canon 700D in mv1080:
30FPS:
C0F06014 = 0x7e6
C0F06008 = 0x20f020f
C0F0600c = 0x20f020f
C0F06010 = 0x20f
C0F0713C = 4a7
C0F07150 = 46a
25FPS:
C0F06014 = 0x7cf
C0F06008 = 0x27f027f
C0F0600c = 0x27f027f
C0F06010 = 0x27f
C0F0713C = 4a7
C0F07150 = 475
23.976FPS:
C0F06014 = 0x9de
C0F06008 = 0x20f020f
C0F0600c = 0x20f020f
C0F06010 = 0x20f
C0F0713C = 4a7
C0F07150 = 46a
Edit: added the head timers also.
Quote from: Danne on July 04, 2018, 12:00:05 AM
Not sure what to test here but following and adding following doesn´t change anything with performance:
case 0xC0F06014: return 0x7cf;
case 0xC0F0600c: return 0x207027f;
case 0xC0F06008: return 0x207027f;
case 0xC0F06010: return 0x207;
case 0xC0F37014: return 0xe;
It's late, try using find/replace. It won't affect performance in any way; it will affect rolling shutter and available frame rates. I'm only asking about the lowest value that still gives valid image (not asking about performance).
You don't have to change anything in fps-engio.c. Just in that block. To change the values, use a hex calculator or write the constants in decimal, e.g. (x << 16) | x.
Ok, thanks for clarifying. Will find time asap.
Another thing. Just played around with 100D values which gives me 42 fps in mv1080p and simply added them to eosm. At least in 3x3_mv1080p mode I can crank fps override to 38 fps. Not bad for this tiny cam.
Added this to eosm:
#define FPS_TIMER_A_MIN (ZOOM ? 676 : MV1080CROP ? 540 : 520)
#define FPS_TIMER_B_MIN (ZOOM || MV1080 || MV1080CROP ? 1288 : MV720 || (lv && lv_dispsize==1 && !is_movie_mode()) ? 990 : 1970)
38 fps file
https://bitbucket.org/Dannephoto/magic-lantern/downloads/38fps_10frames.MLV
That's so cool it can do 38fps!
Here's my first test with mv1080, really happy with the results :)
Having trouble finding some magic numbers:
- default timer B and exact frame rate in x5 zoom (timer A is 716); can be found in the FPS override submenu, with FPS override turned off
- default timer B in 1080p crop modes (timer A is either 546 or 640); guess: 2444/2445 in 24p, 2000 in 25p, 1955/1956 in 30p; please confirm
- default value of C0F06084 in adtg_gui right after startup (without starting to record H.264 and without enabling FPS override or crop_rec)
Caveat: timer B might not be fixed, but might alternate between two values (e.g. in 24p it's either 2527 or 2528). If that happens, please write both values.
Will edit as I'll need more values.
Quote- default timer B and exact frame rate in x5 zoom (timer A is 716); can be found in the FPS override submenu, with FPS override turned off
FPS timer B 1491
Actual FPS 29.975Edit 1: retest shows the same numbers
Quote- default timer B in 1080p crop modes (timer A is either 546 or 640); guess: 2444/2445 in 24p, 2000 in 25p, 1955/1956 in 30p; please confirm
I only got 3x3_mv1080_EOSM crop mode (regarding 1080p crop modes)FPS timer A 640
FPS timer B 2000Edit 1:retest:
Movie crop mode set and:
2444/2445 in 24p confirmed
2000 in 25p confirmed
1955/1956 in 30p confirmed
Quotedefault value of C0F06084 in adtg_gui right after startup (without starting to record H.264 and without enabling FPS override or crop_rec)
without enabling RAW video or anything else enabling latest adtg_gui:
0xa601d4Edit 1:
C0F06084 when starting cam with nothing enabled:
0x0(https://s8.postimg.cc/kom6120zp/VRAM0.PPM_500px.jpg)
QuoteC0F06084: did that show up with previous adtg_gui, before commit 0a2e116? Please write context info for this one as well (the fine print at the bottom of screen). Also, 0xa6 is way too small, please double-check.
Tested june 21 build in adtg_gui and could not get the
C0F06084 to show up.
Quote
Caveat: timer B might not be fixed, but might alternate between two values (e.g. in 24p it's either 2527 or 2528). If that happens, please write both values.
Not sure about this one but when checking directly when starting cam:
FPS timer B 2022Edit 1:
Timer B alterations while recording H.264:
24 fps either 2527 or 2528 confirmed
30 fps either 2022 or 2023
25 fps either 2000
1080p crop modes: from Canon firmware, not crop_rec (movie crop hack). In crop_rec we fill in our own values, I can read them from the source.
C0F06084: did that show up with previous adtg_gui, before commit 0a2e116? Please write context info for this one as well (the fine print at the bottom of screen). Also, 0xa6 is way too small, please double-check.
FPS timer B: when starting the camera it's always 2022? it never goes to 2023?
You need to record H.264 to get most of the FPS modes; remember that EOS M stays in 720p30 during standby.
To be clear, I want you to fill in the missing values from this post (ignore SHUTTER; it's no longer used):
Quote from: coutts on November 27, 2012, 10:58:24 PM
FPS register values (for enabling FPS control in ML). posting it here so it's documented somewhere.
NTSC:
LV (and all non-recording modes):
TIMER_A: 0x20f020f
TIMER_B: 0x7e5 / 0x7e6 [changes between the 2 twice a second]
SHUTTER (1/60): 0x3B2 (same in all recording modes too)
Recording:
1080p 30fps:
- same as LV conditions
1080p 24fps:
TIMER_A: 0x20f020f
TIMER_B: 0x9de / 0x9df
720p 60fps:
TIMER_A: 0x20f020f
TIMER_B: 0x3f2 / 0x3f3
480p 30fps:
- same as LV conditions
PAL:
LV (and all non-recording modes):
TIMER_A: 0x20f020f
TIMER_B:0x7e5/0x7e6
SHUTTER (1/100): 0x25e
Recording:
1080p 25fps:
TIMER_A: 0x27f027f
TIMER_B: 0x7cf (doesn't change)
SHUTTER: 0x1f4
1080p 24fps:
TIMER_A: 0x20f020f
TIMER_B: 0x9de / 0x9df
SHUTTER: same as lv
720p 50fps:
TIMER_A: 0x27f027f
TIMER_B: 0x3e7 (doesn't change)
SHUTTER: 0x1f4
480p 25fps:
TIMER_A: 0x27f027f
TIMER_B: 0x7cf
SHUTTER: 0x1f4
I get on it tonight. Hooked up here atm 8)
Thanks.
Quote from: a1ex on July 02, 2018, 05:55:48 PM
BTW...
Confirmed on 60D - latest adtg_gui is able to lock the zoom factor between x5 and x10 (so the image no longer doubles). Procedure: simply locking the registers modified between x5 and x10. As expected, this doesn't work on 5D3.
(https://a1ex.magiclantern.fm/bleeding-edge/lv-preview/60D_x5_vs_x10.png)
Screenshot: 60D registers specific to x5 (the "was" values are from x10).
And here the registers for 700D (overridden x10 in x5) and of course the image no longer doubles it stays x10 in x5 so it's working on DIGIC 5 and maybe 5D3 has different case ?
(https://image.ibb.co/cwYLpy/1.jpg)
(https://image.ibb.co/iMpt9y/2.jpg)
The last two registers are related to each other you can break the image in the first one and fix it in the second (I can change the preview position with these registers in x10 but not in x5):
C0F118E0
C0F118E4
Is there better way (QEMU?) to understand these registers instead of overriding and guessing what it does ? because sometimes it's really hard to find the relationships between these.
I am pretty sure this register for fixing stretched LiveLivew in EOS M when enabling mv1080 and in other cameras when enabling 3x3 in 720p 50/60fps:
C0F11BCC = 0x50009 in mv1080 | 0x400045 in mv720
The proof: I changed [ADTG]800c to 0x4 in mv1080 so I have now stretched LiveView (white bar in the bottom the stretched LiveView to the top other wise the stretched LiveView to the bottom when enabling 3x3) then I copied the register value from mv720 in mv1080,, and the LiveView back to the normal.
Edit before releasing: the LiveView back to the stretched when recording H.264 (not our case now because we will record RAW and this will not affect the LiveView maybe but this means there are more registers to find) .
The Proof 2: I tried all other registers to solve stretched LiveView one by one with no success (from mv1080 registers values to mv720).
The problem: LiveView will stuck when copying the register value from mv1080 into mv720 and I don't know why :-\ .
Maybe not the most exciting discovery but a while back I was looking at some stubs and found a few that might be off. Anyone care to look into these before I make the pull request?
/** Events **/
NSTUB(0xFFA8B8BC - RAM_OFFSET, TryPostEvent)
-NSTUB(0xFFA8B940 - RAM_OFFSET, TryPostEvent_end)
+NSTUB(0xFFA8B91C - RAM_OFFSET, TryPostEvent_end)
NSTUB(0xFFA8B1DC - RAM_OFFSET, TryPostStageEvent)
-NSTUB(0xFFA8B260 - RAM_OFFSET, TryPostStageEvent_end)
+NSTUB(0xFFA8B238 - RAM_OFFSET, TryPostStageEvent_end)
/** Recursive locks **/
NSTUB(0xFFA88520 - RAM_OFFSET, AcquireRecursiveLock) // AJ_KernelDry_KerRLock.c
-NSTUB(0xFFA73E6C - RAM_OFFSET, CreateRecursiveLock)
+NSTUB(0xFFA88488 - RAM_OFFSET, CreateRecursiveLock)
NSTUB(0xFFA88634 - RAM_OFFSET, ReleaseRecursiveLock) // AJ_KernelDry_KerRLock.c_p2
TryPostEvent_end / TryPostStageEvent_end are no longer used; functionality replaced by the dm-spy-experiments branch; I should clean it up a bit, make sure it doesn't break anything (currently it does), make sure it works on all models, and merge it.
CreateRecursiveLock: one of these functions is a wrapper to another. Any of them is fine. TODO: figure out what's up with the SubReset / MainReset thingie; it's used on all DIGIC <= 5 models, but this string is not present in newer ROMs.
I have a 90EX speedlite that powers off automatically when the camera turns off. Is it possible to disable this feature via ML?
I am using it to trigger external strobes through an underwater housing. The problem is, the flash power button is not accessible via the dive housing, so if the camera powers off (powersave, or I accidentally hit the power button) then the flash is off for the rest of the dive and I can't trigger the strobes.
There does not appear to be a canon native way to disable it. It is a documented feature:
https://support.usa.canon.com/kb/index?page=content&id=ART136735
and there is a way to disable the 5-minute idle power, off, but it doesn't stop the flash from turning off with the camera.
Hi, just doing first steps ever with video recording using EOS M and magiclantern-crop_rec_4k.2018Jul04.EOSM202.zip from official experimental builds.
I load:
- sd_uhs (my custom build, fixed to 160MHz, D1 D1, found to work best with my SD card)
- mlv_lite
- mlv_snd
- dual_iso
- ettr
Recording videos using Manual Exposure mode, 5x zoom, RAW 1920x1080, FPS override to 25fps, preview: framing
In Canon menu selected: 1920/25, Servo AF in videos: off, AF on half-shutter during recording: on/off (tried both)
Have noticed a problem with AF:
After starting recording in 5x zoom with ML overlays the focusing on half-shutter stops working. I doesn't work even after stopping the recording. Preview changes to 5x, full color for the time when I hold half-shutter but if does not focus. To use AF I need to: click INFO to exit ML overlays and have magnifier icon visible, unzoom completely. Then it works until I press INFO again to enable ML overlays and start recording.
There is also an unexpected behaviour with the exposure time. To change exposure parameters I close ML overlays and enable the Canon overlays using INFO (otherwise I don't see which parameter is actually selected). Exposure time box shows 1/50s and is not modifiable. If I change the value it reverts to 1/50s immediately afterwards. But it seems, that the recording was not made with 1/50s but rather 1/38s, which was also the time shown in ML overlays. But as I now see, this can be adjusted in ML menu. Actually not to exactly 1/50s but 1/53s which is close enough. Also ISO setting is there and I believe the ML histogram shows the exposure which will be really applied during recording. Is this, how you work at the moment or is there a simpler way to set everything up?
Quote from: ArcziPL on July 08, 2018, 12:01:31 AM
After starting recording in 5x zoom with ML overlays the focusing on half-shutter stops working. I doesn't work even after stopping the recording. Preview changes to 5x, full color for the time when I hold half-shutter but if does not focus. To use AF I need to: click INFO to exit ML overlays and have magnifier icon visible, unzoom completely. Then it works until I press INFO again to enable ML overlays and start recording.
This is unexpected. Questions:
- do you need to start recording in order to break the AF, or it's enough to enable the overlays?
- if yes (you need to start recording): can you get a screenshot with all EDMAC channels (edmac.mo) in x5, before and after AF?
- if no (enabling overlays is enough to break AF): can you narrow down to some particular overlay?
Possibly related: issue #2254 (https://bitbucket.org/hudson/magic-lantern/issues/2254/star-bbaf-during-raw-recording-crashes-ml)
Quote from: ArcziPL on July 08, 2018, 12:01:31 AMExposure time box shows 1/50s and is not modifiable. If I change the value it reverts to 1/50s immediately afterwards. But it seems, that the recording was not made with 1/50s but rather 1/38s, which was also the time shown in ML overlays. But as I now see, this can be adjusted in ML menu. Actually not to exactly 1/50s but 1/53s which is close enough.
I might have a fix for that (https://www.magiclantern.fm/forum/index.php?topic=19300.msg203623#msg203623), but I'm not sure what to do with the UI. On other models you just dial the desired shutter speed from scrollwheel.
Quote from: EstaDive on July 06, 2018, 06:52:33 PM
I have a 90EX speedlite that powers off automatically when the camera turns off. Is it possible to disable this feature via ML?
Does the flash have its own power source (batteries)? Assuming yes; otherwise you wouldn't ask this question.
The communication between camera and flash is likely done by the MPU (https://www.magiclantern.fm/forum/index.php?topic=17596.msg199973#msg199973); however, we are not exactly familiar with its CPU architecture. To figure this out, one may also need to log the communication through the hot shoe. I use neither a flash, nor an EOS M, so can't help much other than some advice.
Quote from: a1ex on July 08, 2018, 09:29:17 AM
I might have a fix for that (https://www.magiclantern.fm/forum/index.php?topic=19300.msg203623#msg203623), but I'm not sure what to do with the UI. On other models you just dial the desired shutter speed from scrollwheel.
Does the flash have its own power source (batteries)? Assuming yes; otherwise you wouldn't ask this question.
The communication between camera and flash is likely done by the MPU (https://www.magiclantern.fm/forum/index.php?topic=17596.msg199973#msg199973); however, we are not exactly familiar with its CPU architecture. To figure this out, one may also need to log the communication through the hot shoe. I use neither a flash, nor an EOS M, so can't help much other than some advice.
The flash has its own batteries. Is there a way to log the MPU messages sent during shutdown? From the link you sent, there are instructions to log the startup, but not shutdown. I haven't figured out how to reproduce this behavior without turning the camera off.
--edit--
I've noticed that the flash only powers off if the camera has communicated with the flash, either through the flash settings, taking a picture, focusing, or pressing the AE lock button. If I just turn the camera on and off the flash stays on. So I think if I can log the shutdown sequence, it should be possible to find what signal is being sent by comparing shutdowns with the flash attached and flash unattached.
-------
Moderators - feel free to move this to reverse engineering or feature request if that is a more appropriate location.
With this build (https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log-mpu/), simply turn off the camera before the 20-second timeout expires. That would log the MPU messages during shutdown. However, these only cover the communication between MPU and main CPU; they won't include whatever the MPU decides to do on its own. From previous experiments, it seems like the MPU handles the flash side and only reports some status messages to the main CPU.
Here's an experiment you could try:
- turn on the camera with the battery door open (close the microswitch with something)
- take a picture
- remove the camera battery
That way, the camera won't be able to tell the flash that it turned off. Hopefully the flash will stay on.
Then, try an emergency shutdown: turn off the camera by opening the battery door. That way, I'd expect the MPU to perform its shutdown procedure, and tell the main CPU to perform a rushed shutdown. I'd expect the flash to turn off in this case, but who knows.
Some notes on different shutdown methods. (https://bitbucket.org/hudson/magic-lantern/src/qemu/contrib/qemu/README.rst#rst-header-shutdown-and-reboot)
Quote from: a1ex on July 08, 2018, 09:29:17 AM
This is unexpected. Questions:
- do you need to start recording in order to break the AF, or it's enough to enable the overlays?
- if yes (you need to start recording): can you get a screenshot with all EDMAC channels (edmac.mo) in x5, before and after AF?
- if no (enabling overlays is enough to break AF): can you narrow down to some particular overlay?
Yes, recording is needed to crash AF.
When trying to do screenshots, I wanted to use the feature from DEBUG menu first but... doing a screenshot causes an out of memory error.
(https://s25.postimg.cc/ns3ribq8v/memerr.jpg) (https://postimages.org/)
Then I have noticed, that after recording a movie the status also shows memory error. Can it kill the AF?
Anyway, what method of documenting EDMAC channels status do you consider as best in this case? Just making photos of the screen with another camera? BTW: several values on several pages are alternating between different values (addresses, flags).
If I remove the battery without powering down, the flash stays on. However, if I turn it off by opening the battery compartment the flash turns off.
I think the AE lock was a bit of a red herring. If I press any button on the camera, the flash will power off when the camera turns off. This is true even if the flash is not attached when the button is pressed.
Here are a collection of logs:
Odd numbered logs, I do not do AE and the flash stays on. Even number logs, I do AE/Lock (4,6,8) or enter the flash menu (10,12) and the flash turns off.
https://anonfile.com/Q809l0fbb8/magiclantern_flash_logs.tar.gz
There is no single log line that is present in all of the "off" cases that is not present in any of the "non-off" cases. So it must be more complicated than a single mpu message. Perhaps part of a large MPU message? Or handled entirely within the MPU, in which case it sounds like disabling the auto-off would not be possible.
@ArcziPL:
You can turn off raw video, as it's preallocating the entire memory (so there may not be enough RAM for a screenshot once you enable it). Memory errors reported in the Debug tabs are all from ML; when Canon code cannot allocate its stuff, it usually throws ERR70. Still, a memory error during video recording is unexpected; I just doubt it has anything to do with AF.
Got another idea: disable Small Hacks from the raw video menu. Maybe it's one of those.
For the EDMAC screen, just the two summary pages showing all channels should be enough. Only wanted to check if AF uses the channel reserved for our DMA memcpy operations. However, there's another way you can test that - load bench.mo and run the memory benchmark. That includes a similar memcpy. If the memory benchmark also breaks AF, it's likely that; otherwise, it's likely something else.
@EstaDive: what if you just disable Auto Power Off in Canon menu? Does the EOS M has some standby mode where it turns off just the display? (other models do this if you press INFO a few times, outside LiveView)
Quote from: a1ex on July 08, 2018, 11:55:40 PM
@EstaDive: what if you just disable Auto Power Off in Canon menu? Does the EOS M has some standby mode where it turns off just the display? (other models do this if you press INFO a few times, outside LiveView)
Yeah, the EOS-M has a standby mode where it can power down the display, but leave the power on. The flash stays on in this case. I was worried that I will accidentally turn off the camera power during the dive, since I use pretty thick gloves and don't always hit the button that I intend to.
Quote from: Danne on July 03, 2018, 02:32:11 PM
Here is test version:
mv1080p for eosm
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jul03.EOSM202_mv1080p.zip
Select 3x3_mv1080p_EOSM from Crop mode menu.
You will be able to get good footage in 14bit lossless. You can select 24fps and also global draw on for full frame preview. Preview is a bit wonky atm but there´s some serious skill out there(in here) so maybe that will be better with time. Probably continous with sd_uhs hack on(seems continuous without at 24fps).
Other modes might be broken since I modified exception code in raw.c.
Hi all,
thanks for the great effort you're putting in. I wanted to try out Dannes build. But the 3x3 raw recording 1080p does not work. I use Sandisk Extreme Pro 64Gb with 95mb/s write speed. The sd uhs overclocking module works and i could record 2.5k with another build before, in 5x zoom mode. In the 1080p 3x3 mode my max resolution i could choose was something around 1700x600. I tried with lossless 14 bit and lossless 12 bit but my footage was corrupt. Can you maybe tell me which modules/files i need to activate? Are all needed files in this build?
And what values i need to modify after a fresh install?
Thanks in advance
This build only works when crop_rec.mo is enabled. Then selecting the mv1080p setting should get you into 1736x586 or something like that. Enter raw video and change setting for max vertical resolution.
Quote from: a1ex on July 08, 2018, 11:55:40 PM
For the EDMAC screen, just the two summary pages showing all channels should be enough. Only wanted to check if AF uses the channel reserved for our DMA memcpy operations.
That's the 5x mode with ML overlays, so my starting point:
(https://s25.postimg.cc/81wxd9hrv/IMG_20180709_200637.jpg) (https://postimg.cc/image/81wxd9hrv/)
EDMAC registers before recording (AF still works)
Red marks show channels, where Address field alternates between several values
(https://s25.postimg.cc/v3dij1zfv/IMG_20180709_200652_b_mod.jpg) (https://postimg.cc/image/v3dij1zfv/) (https://s25.postimg.cc/57trzv5bv/IMG_20180709_200657_b_mod.jpg) (https://postimg.cc/image/57trzv5bv/)
And below are EDMAC registers after recording, when AF not works anymore. Actually, after recording it works ONCE and then not anymore, i.e. pressing the half-shutter second time after recording changes only the preview to Canon's normal 5x zoom preview but without triggering AF anymore. The status below is from a moment when AF does not work already.
(https://s25.postimg.cc/gwxrnubq3/IMG_20180709_200747_a.jpg) (https://postimg.cc/image/gwxrnubq3/) (https://s25.postimg.cc/pf77s6pyj/IMG_20180709_200738_a.jpg) (https://postimg.cc/image/pf77s6pyj/)
Quote from: a1ex on July 08, 2018, 11:55:40 PMHowever, there's another way you can test that - load bench.mo and run the memory benchmark. That includes a similar memcpy. If the memory benchmark also breaks AF, it's likely that; otherwise, it's likely something else.
Loaded, went to Video Mode, 5x, ML overlays, then started Memory Benchmark. It stops at this stage:
(https://s25.postimg.cc/3ss7b7ou3/IMG_20180709_195753.jpg) (https://postimg.cc/image/3ss7b7ou3/)
even some minutes later no progress. Camera still responds to user's input but very slow.
Tried it also in photo mode. It stopped at this stage, looks like finished (?)
(https://s25.postimg.cc/h9p5u3maz/IMG_20180709_195447.jpg) (https://postimg.cc/image/h9p5u3maz/)
but I didn't find a way to quit it. Only battery pull let me break it. I waited about 2 minutes, tried several buttons, starting with the half-shutter. How long is it supposed to run? I selected the "1 min" version.
Quote from: a1ex on July 08, 2018, 11:55:40 PM
Got another idea: disable Small Hacks from the raw video menu. Maybe it's one of those.
Unfortunately it doesn't help.
Quote from: a1ex on July 08, 2018, 11:55:40 PMYou can turn off raw video, as it's preallocating the entire memory (so there may not be enough RAM for a screenshot once you enable it).
This I don't get. If I disable mlv_lite, I can indeed make screenshots. But it doesn't make sense in this case, a I won't be able to enter the 5x with ML overlays and record RAW to break the AF, so there will be no point of making any screenshot.
EDIT:
And just be sure that I don't have some strange conflicting settings of ML:
1) removed ML from the card
2) unpacked plain vanilla magiclantern-crop_rec_4k.2018Jul04.EOSM202.zip
3) booted up, enabled mlv_lite and mlv_snd only
4) reboot
5) entered movie mode, entered 5x zoom, enabled "RAW video" option in ML menu (it defaults to 1920x1080, 14 bit), half-shutter to exit ML menu, enabled ML overlays by pressing INFO
6) started recording, stopped recording, AF doesn't work.
Some weeks ago I had magiclantern-crop_rec_4k.2018Mar10.EOSM202.zip on my SD card and it behaved the same.
Unable to tell what's going on, but you should be able to narrow down by commenting stuff from mlv_lite.c, raw_video_rec_task. For example, start by commenting out the main recording loop and replace it with a delay, so it will buffer a few frames. You could also try to disable the vsync hook (a function called once every LiveView frame), e.g. by commenting out the MODULE_CBR line for raw_rec_vsync_cbr. Without knowing the outcome of this tweak, it's hard to give advice on what to do next; maybe try asking me on IRC if you get stuck.
Reproduced the memory benchmark issue in QEMU. It works fine in main builds, but it's broken in crop_rec_4k. Looking into it.
Edit: seems fixed if you build from source (changeset 5684ac8 and later).
Quote from: Danne on July 09, 2018, 04:54:42 PM
This build only works when crop_rec.mo is enabled. Then selecting the mv1080p setting should get you into 1736x586 or something like that. Enter raw video and change setting for max vertical resolution.
hey its very strange, did what you said. enabled crop_rec and also mlv_lite and sound and tried. but with no luck. the raw recording settings give me just the same resolution. even when i try higher resolution like around 2500x1000, it stays on 1736x586 .
any idea?
You have to change vertical resolution, doesn't matter if you set 2500 or more, it's the wrong place.
So you mean I have to change the aspect ratio? Which one do you use, somehow it's puzzling me...
16:9 5:3 etc. Don't have my cam here. Below resolution settings. Roll dial to the right...
To get full sensor recording of 1736x1120 on EOSM, you need to have the aspect ratio set to 1:2 in Danne's current 2018Jul03.EOSM202_mv1080p build. Ensure that crop mode is set to 3x3_mv1080_EOSM
All other crop modes and other features are not working (in this build) as he has already advised.
@ArcziPL as far as i can remember (and I could be wrong) I've never been able to enter 5xCrop or 10xCrop mode having AF turned on in the Canon Menu. As soon as I turn it off, the option for zoom comes up.
Some interesting action going on with this pull request:
EOS M: enabled FRAME_SHUTTER_BLANKING_WRITE. Does it work? (https://bitbucket.org/hudson/magic-lantern/commits/046e3888a3bc884a6791586d542f0569832dd509#general-comments)
Never knew how the Low Light mode in FPS override is supposed to work because it was broken on the EOSM. It is working now, though with some issues. It would be great if some other EOSM users who can compile the latest crop_rec_4k (not the sound branch) try it out.
Have tried the July 3 nightly build, but when I try mv1080, LiveView goes nuts and the video always stops recording immediately (showing a list of corrupt frames). Danne: Could you please list the exact settings you used to pull off mv1080? I turn AF off, crop mode on (set to mv1080), and then I set CBR to 0.1x, bit rate to 14, ratio to 1:2, and h.264 proxy on as you mention in a previous post. Still...nada. Also turned "small tweaks" off. Q: Does the SD card hack need to be on? Do I also need to turn off RAW sound?
Just wondering if someone can share screenshots of their relevant movie settings. Mine are attached.
Thanks much. Be blessed today.
(https://thumb.ibb.co/hnxZWo/IMG_9940.jpg) (https://ibb.co/hnxZWo)
(https://thumb.ibb.co/nhimcT/IMG_9941.jpg) (https://ibb.co/nhimcT)
(https://thumb.ibb.co/mdW6cT/IMG_9943.jpg) (https://ibb.co/mdW6cT)
(https://thumb.ibb.co/hROKxT/IMG_9942.jpg) (https://ibb.co/hROKxT)
Also, wondering if the brand of SD card matters. I'm using this card.
(https://thumb.ibb.co/kqiuxT/image.png) (https://ibb.co/kqiuxT)<br /
Helo
maybe this may help You.
First, let's ensure You have something similar like the following -
eosM
Firmware v202
Camera in Videomode
64GB W50 R55 , Exfat
nonAF lens
a full battery
canon settings
PAL & 1920x1080@24
ML Version
magicklantern-Nightly.2018Jul03.EOSM202_mv1080p.zip
Put Your card in a card reader and Save Your data.
Start the cam and go to ML Menu -> Prefs -> Config files -> Restore ML defaults, then leave the ML menu.
Turn Your cam off and back on again.
Go to ML menu -> Overlay and turn GD off
Go to ML menu -> Modules and activate
crop_rec
lua
mlv_lite
mlv_snd
sd_uhs , then leave the ML menu.
Turn Your cam off and back on again.
Go to ML menu -> Movie -> Crop mode and select 3x3_mv1080_EOSM
Wait few seconds then leave ML menu and enter it back again.
Go to ML menu -> Debug and check Memory patches entry - it should be active (red) and show "1 ROM, 2 RAM" entry.
Go to ML menu -> Scripts and select one of the mv1080p_12bit scripts.
Press SET to load/run this script. Wait until it completes, then leave the ML menu. Turn Your cam off and back on again.
Message visible after startup should be "FPS override : 24.002" *)
Go to ML menu -> Movie -> Raw video and tap the screen . Inside it change the Aspect ratio value to 1:2 and the resolution should change to 1736x1120. Change the value of Data format to 14-bit lossless. Change the "Preview" to "Real-time".
Leave the ML menu. Turn Your cam off and back on again.
Now Your cam is set up. The following step is necessary to allow higher speeds of the SD card. This step has to be repeated after each start of the cam.
Go to ML menu -> Scripts and select the "enable SD overclocking" script and hit "Run Script". Wait until it's done. Don't use the "Autorun" feature to start this script automatically at startup.
Activate GD if You like.
You should see an upper portion of an image. Press&hold Half-shutter for framing.
My recording speed is around 50,8 MB/sec
So this works for me and I can record non cropped 3x3 mv1080 type video. The cam is responsive and the green recording sign jumps in right from start on. Disable GD, then record to check the actual speed, reenable GD after again.
The first picture is 50mm lens, the second a 28mm and the third a c-mount 12.5mm lens.
Many Thanks to user "the associate" who motivated me and of course to Danne for this build and all other Devs and ML folks
Af-off
(https://thumb.ibb.co/bszPXT/m39_28mm_f2_8.png) (https://ibb.co/bszPXT)
(https://thumb.ibb.co/eguf6o/m39_50mm_f1_5.png) (https://ibb.co/eguf6o)
(https://thumb.ibb.co/dJpPXT/mount_c_12_5mm_f1_9.png) (https://ibb.co/dJpPXT)
*) Even thou this message is shown at startup, the frame rate shown under ML menu -> Movie -> FPS override is shown as 23,980
@AF-OFF
Thank you for the instructions on getting "full sensor" 1736x1120 raw working on the EOSM! Very helpful!
Unsure on this bit:
QuoteGo to ML menu -> Scripts and select one of the mv1080p_12bit scripts.
There is a selection? Which one is best?
Now I just have to figure out the easiest post "workflow" in Linux.
Thanks!
Is there a reason to use mv1080 over say the 2.5k RAW with the sd_uhs module?
@ tupp - I think the only difference between the two is the ISO - 100 - 800. So choose which one fits Your needs. You don't have to use the script every time you power the cam on. if you wish to change the iso, please do it in the ML menu, not in the canon one.
the script "enable SD overclocking" has to be used every time the cam is powered on.
( Sometimes I forget about it. )
af-off
Set it to auto and it starts on start up.
it always seems like im too dumb to figure this stuff out but i followed all the instructions and i can't seem to get the full height mv1080 working. stuck at 864 pixels won't go any higher. tried the preset. maybe i should just install it again.
QuoteAspect ratio value to 1:2
Tried that after selecting the preset in crop_rec?
@Danne
Autostart the script breaks somehow the whole setup. BtW do You use the PAL or the NTSC preset in Canon menu?
@Teamsleepkid
if You can't get over the 864px therefore there is the script used for. even if this seems ridiculous, restart the cam afterwards. hope You will catch it.
Af-off
It does. Hm, will have to check that. Unfortunately tied up in vacation stuff. Have to get back on track after this.
ooooh i was in 1:2:1 i got fooled
@Danne (aspect ratio set to 1:2)
Yes.
After the initial loading of all modules - set 3x3crop and execute one of those 3x3 lua script. restart again and the set the aspect ratio to 1:2 and the res should change to 1736x1120px.
@All
please follow the instruction carefully and this should work for You too....#1595
sidenote - with MLVFS and Resolve everything seems fine. in MLV App the resolution is shown as in cam, when halfpressing the shutter for framing (1:2) has to be corrected under the Edit -> Transformation - Height Stretch shows 1.67x have to be 1.0x
(https://thumb.ibb.co/gx2Awy/mlv_app_distorted.png) (https://ibb.co/gx2Awy)
(https://thumb.ibb.co/ezuC9J/mlv_app_ok.png) (https://ibb.co/ezuC9J)
@AF-OFF
your findings are the same as what I get. Seems to default to 1.67 stretch in MLVAPP too.
Mlv metadata has to be changed for this mode. Apps still works/thinks the cam is recording stretched material. Luckily Mlv App let's you select ratios manually as well so it can be corrected.
Quote from: AF-OFF on July 17, 2018, 11:48:59 PM
@Danne
Autostart the script breaks somehow the whole setup. BtW do You use the PAL or the NTSC preset in Canon menu?
Just tested enable sd overclocking set to autorun works over here. Exactly what issues are you having?
@Danne
Just tested again. works perfectly. sorry for that confusion.
Quote from: tupp on July 16, 2018, 07:20:42 PM
@AF-OFF
Now I just have to figure out the easiest post "workflow" in Linux.
Thanks!
I use MLVFS and Resolve and also the MLV APP by Ilia3101 , which is very nice! I wish You success with finding a solution which works for You.
https://www.magiclantern.fm/forum/index.php?topic=20025.0
https://ilia3101.github.io/MLV-App/
I'm wondering if anyone else has this issue, or if someone can test it for me on the EOSM (2.0.2). Or point me to a thread - i've searched, but unable to come up with anything.
Taking FRSP in both dng and mlv format - I am unable to choose a custom dcp in ACR when post-processing. All the standard ones are available to select (ie. all adobe profiles, camera matching, artistic, Legacy, B&W etc.) however the one's I have added myself like BMDFilm, ML-Log and VisionLOG do not come up. Have tried with latest nightly and latest croprec experimental builds and both give the same result.
I know the profiles are loaded and normally working in ACR because they work with dng's from my 5D3.
Here are the files I am having trouble with.
https://www.dropbox.com/s/6qf41mp47lzr124/EOSM%20DNG%20files.zip?dl=0
You´re profiles are connected with 5D3 but not with other cams like eosm. Either that or the Unique Camera Model tag is incorrect or missing in your files. Checking the dng files that is not the case so you´re acr profiles need to be profiled also for the eosm. Solution. Ask the creators of the dcp profiles for further profiling.
Quote from: Danne on July 19, 2018, 07:14:14 AM
Either that or the Unique Camera Model tag is incorrect or missing in your files. Checking the dng files that is not the case so you´re acr profiles need to be profiled also for the eosm. Solution. Ask the creators of the dcp profiles for further profiling.
Thanks Danne, this makes more sense now. Appreciate your help!
@alex
Retested this(magic numbers) and did edits to all tests(Edit 1). Think numbers are valid now. WIll try to squeeze in more tests if you have some more ideas to try. Thanks:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg203569#msg203569
@Danne: thanks, will cross-check them with this commit (https://bitbucket.org/hudson/magic-lantern/commits/d556a102239697c650257b3010981356bbdae64c).
"30 fps either 2222 or 2223" -> this doesn't match, likely typo; I've got 2022/2023; if it's not a typo, please check timer A as well.
I've pushed a commit that should reveal missing registers in certain modes. By default, adtg_gui hides stuff that changes "too often", as it's probably noise, but that includes registers that flip back and forth between two successive values, effectively averaging them to get something in-between.
Yes, typo, corrected.
Nice addon to the adtg_gui. Will check when time is here.
Did a quick dirty test on fps override with crop_rec(generic code) here:
https://bitbucket.org/hudson/magic-lantern/commits/d556a102239697c650257b3010981356bbdae64c
Only with 720p mode. Firstly I need to hit menu button to get into crop_rec live view window(white bottom border before this even in 720p mode).
So initial tests first works fine but after a while image gets distorted and neon coloured. Happens randomly after changing fps override to lower or higher values.
Sidenote question. Trying to create an exception for eosm when filming mv1080p in raw.c.
For now all settings will apply this:
#ifdef CONFIG_EOSM
/* EOS M exception */
/* http://www.magiclantern.fm/forum/index.php?topic=16608.msg176023#msg176023 */
if (lv_dispsize == 1 && !video_mode_crop && !RECORDING_H264)
{
/* breaks mv720p mode but works for mv1080p */
*height = 1150;
}
#endif
This of course breaks other settings but mv1080p so we need:
*height = 727;
for the rest of the modes but then I notice there is no crop_rec bindings with raw.c. Should I look in the config file or is there a way already to find out the exception somewhere else?
Quote from: a1ex on July 03, 2018, 06:43:51 PM
Binning factors and vertical resolution override can be updated from raw_info_update_cbr, so raw.c can stay untouched. Will post a patch soon.
Working this hint I managed to get a better mv1080p preview with eosm and in crop_rec setting:
"3x3_mv1080_EOSM"
Commit:
https://bitbucket.org/Dannephoto/magic-lantern/commits/687dbf6df923f23dead32c9d0e24842bb70d5c9b
Still don´t really know how to handle this exception in raw.c:
#ifdef CONFIG_EOSM
/* EOS M exception */
/* http://www.magiclantern.fm/forum/index.php?topic=16608.msg176023#msg176023 */
if (lv_dispsize == 1 && !video_mode_crop && !RECORDING_H264)
{
*height = 1150;
}
#endif *height = 1150;will break compatibilty with other modes since it needs to be *height = 727;
I asked before but is there a way to communicate between raw.c and crop_rec.c? Check for a register already set or so? Can the height exception be patched in raw_info_update_cbr as well so still leaving raw.c alone maybe?
Maybe do something similar to the is_5D3 code block at the end of the raw_info_update_cbr function?
Haven't tried it yet:
if (is_EOSM)
{
/* use this instead of the EOS M exception to set the height */
if (CROP_PRESET_3x3_mv1080_EOSM)
{
*height = 1150;
}
else
{
*height = 727;
}
}
Probably needs some tweaking--almost nothing I do works the first time.
[EDIT] Since you need the exception in raw.c for when the crop_rec module isn't being used the "else" probably isn't necessary since the height is already set to 727.
Tried this before but:
Using ~/gcc-arm-none-eabi-5_4-2016q3/bin/arm-none-eabi-gcc (preferred).
Updated HGVERSION
[ README ] module_strings.h
[ CC ] crop_rec.o
crop_rec.c: In function 'raw_info_update_cbr':
crop_rec.c:2765:18: error: 'height' undeclared (first use in this function)
*height = 1150;
^
crop_rec.c:2765:18: note: each undeclared identifier is reported only once for each function it appears in
make: *** [crop_rec.o] Error 1
undeclared identifier. With the level of my c coding this is considered advanced :P
Here are examples with fixed framing preview in mv1080p for eosm.
real time preview(not all is shown)
(https://s8.postimg.cc/spcjnoww5/20180803_184228.jpg_800px.jpg)
framing preview before fix
(https://s8.postimg.cc/97hw7r7o5/20180803_184637.jpg_800px.jpg)
framing preview with fix
(https://s8.postimg.cc/nqp1968it/20180803_184239.jpg_800px.jpg)
Nice!
Tried it here and my screen display and mlv_dump is showing 3x3, yay! Also, the fps is showing 25fps no matter how the camera is set, right? Screenshot feature not working is it?
Super quick and dirty test--stretched the image a bit too much:
(https://farm2.staticflickr.com/1831/42024927370_b1e3fd815e.jpg) (https://flic.kr/p/272AJMh)
Yeah--my suggestions didn't work. Spent too much time trying different things and failing. Need some help from a1ex on this so it will work with the other resolutions.
Cool. Yes, fps is hard coded. If you check in crop_rec.c there are alternatives but maybe best if we could get fps modes to work with canon settings and fps override as with other cams.
Feedback welcome for exception making both for height but also for playing with reducing bits with analog gain registers...
@danne any chance of a build with the updated preview for testing purposes.
I've been using the various EOS M builds in 4K crop rec on steroids, but I'm really interested in making mv1080 with the full sensor usable.
Happy to help with reports/logs if I can.
I am also eager to test a new build with an updated preview on the 100D, Danne. Any chance for that?
Here is a version with filled preview screen in mv1080p. Didn´t test so please report back.
Will mainly work with mv1080p mode selected or x5 modes. If crop_rec disabled expect corrupted files...
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Aug07.EOSM202_mv1080p.zip
@IDA_ML nothing new for 100D coming from here yet...
Hi Danne, thanks for the build...one quick question...do we need to follow the following steps to use mv1080p:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg204144#msg204144
i activated crop_rec and mlv lite and it works...do i need to activate the sd uhs hack?
You don't need the hack but if used you should be able to record continuous 24 fps with a fast sd card.
just noticed that, only able to record 6 seconds, i only got into this whole "raw/magic lantern/eos-m boat" recently... i apologize for perhaps asking the same questions.
1- to get 1736x1120 i need to setup the aspect ratio to 1:1 or 1:2, thats the only way i can select that resolution that i'm aware.
2- Is there a difference between mv720p and mv1080p in a "x" resolution? For example 1728x736 is the highest i can select using an aspect ratio of 2:35 on both mv720 and mv1080.
Thanks
1: yes
2: check files, not able to compare output. If you manage to get 1120 working just stick to that if it's working.
Also this helps for general mv1080 setup this guide helps:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg204144#msg204144
I find that with 1736x1120 I need a write speed of 44.6 MB/s which requires the SD UHS hack to get 40+ MB/s speeds
The Framing preview is now un-stretched which is great, but obviously still not in realtime (which would be grand).
I've had a couple of issues where pressing half shutter to go realtime means that the camera doesn't go back to more accurate preview.
There also appears to be a difference in the brightness of the accurate preview vs realtime preview.
The realtime preview appears to have accurate top/left/right framing, just the bottom say 15%. I'll try and shoot some charts to see if I can get an accurate read on it.
In terms of the actual shooting, the files are coming out without corruption. I've shot for approx 1min continuous, but will see what the max limit it.
MLV app takes the footage just find and reads the metadata correctly so isn't applying any transformation.
More tests to come, but it's looking pretty solid. The icing on the cake would be getting a more realtime, accurate preview for monitoring etc.
But overall, thumbs firmly up :)
More to come.
I am wondering, if it would be possible to get 2.5k recording with proper framing on the screen, so without the 5x zoom. Do you think this could be possible ?
Set preview to framing in raw video settings. Should get you slowish full screen preview.
so it has proper framing? good to know. thank you :). Do you think one day it can be faster?
First of all, thank you all devs. for the hard work you guys put in the ML development.
===
I'm a new user of ML on an EOS M and very much impressed by the features offered by ML on this camera... I also have a feature I miss, that is focus stacking, which according to the feature matrix is not supported on EOS M. I was wondering, what is the missing info that is required to get this feature working ? I was studying the ML code and I already have some prime suspect, but I'd like to ask advice from devs.
Also, what are the main tools for figuring out possible stubs/property cases, etc. ? (Btw., I know a bit about how CHDK works, but I'm new to ML.)
Thanks !
EDIT: Well, in the meantime I went ahead and recompiled ML sources with enabled FEATURE_FOLLOW_FOCUS, FEATURE_RACK_FOCUS and FEATURE_FOCUS_STACKING, and (at least) focus stacking seems to work :). Am I missing something ?
Welcome, other folks from CHDK are probably still around.
For me, the main reverse engineering tools are currently QEMU (https://bitbucket.org/hudson/magic-lantern/src/qemu/contrib/qemu/README.rst) and io_trace (https://www.magiclantern.fm/forum/index.php?topic=2388.msg196941#msg196941). Unfortunately, the former can't handle LiveView yet. The latter can get some very detailed low-level logs, but it's not exactly focused on properties.
For properties, here is a global property handler in debug.c that prints the raw data with tiny fonts and highlights the changes. I haven't touched this code in years, so it may not compile out of the box. Edit: this seems to fix the compilation:
diff -r d05eaebda31d src/debug.c
--- a/src/debug.c
+++ b/src/debug.c
@@ -26,2 +26,4 @@
+#define CONFIG_DEBUGMSG 1
+
#ifdef CONFIG_DEBUG_INTERCEPT
@@ -1127,3 +1129,4 @@
-ack:
+ack:;
+ extern void* _prop_cleanup(void* token, int property);
return (void*)_prop_cleanup( debug_token, property );
You could also add prop_request_change_log to a gdb script and run the firmware in QEMU; this will cover most UI properties, but not autofocus, since that's controlled by the main CPU only in LiveView, which is not emulated well.
For focus functionality, please try the lua_fix experimental branch, as it has some significant backend changes in this area. It looks like some newer models still have some problems with it though, as api_test.lua doesn't complete. For EOSM, dfort looked into this here (https://bitbucket.org/hudson/magic-lantern/pull-requests/748/focus-backend-updates-precise-focus/diff) and here (https://www.magiclantern.fm/forum/index.php?topic=14828.msg173589#msg173589); also had some detailed feedback from garry23. Still need to refresh my memory about the outcome of their experiments...
@a1ex: Thanks for the info. I'll start reading the posts in the links you gave me.
But, maybe you haven't noticed my Edit in the initial message, but focus stacking definitely works here :). One issue is that sometimes after running the stack the focus gets stuck, i.e., it doesn't respond to half-shutter presses. Any idea how this can be cured ?
Thanks !
Other than finding a way to reproduce and inserting printf's in the source code to see where it fails, no idea. Is the entire UI locked up? or just half-shutter? or only some of the actions triggered by half-shutter, such as autofocus?
Some unrelated issue I've noticed last night. Looks like the EOS M might be affected by this bug (https://www.magiclantern.fm/forum/index.php?topic=7473.msg198464#msg198464), but I'm unable to see any weird things in QEMU (likely because LiveView is not emulated well). I did notice 90 is not a valid value for GUIMODE_ML_MENU and ran some tests on a 700D (borrowed one for a few days). Based on these tests, I'm expecting the following:
- if you enable Canon histogram with the INFO key, then open ML menu in LiveView, some parts of our menu might be erased by Canon firmware;
- if you enable face detection AF, then yoou open ML menu and then you point the camera at some face, the face detection box might pop up over ML menu;
- if the menu gets erased by Canon firmware in the above scenarios, or other similar ones (maybe audio meters or other animated overlays), I'd expect this change to fix it:
diff -r 6764356de075 platform/EOSM.202/consts.h
--- a/platform/EOSM.202/consts.h
+++ b/platform/EOSM.202/consts.h
@@ -106,3 +106,3 @@
-#define GUIMODE_ML_MENU ( RECORDING_H264 ? 99 : 90 ) // any from 90...102 ?!
+#define GUIMODE_ML_MENU ( RECORDING_H264 ? 99 : 91 ) // any from 90...102 ?!
Maybe either 99 or 91 could work for both standby and recording; IIRC the values were tweaked in order to allow scrollwheel operation in ML menu.
Can you or anyone else confirm the issue?
Can confirm the issue below and the provided fix takes care of the issue. ML menu stays clean, not erased when fix provided.
Quote- if you enable face detection AF, then yoou open ML menu and then you point the camera at some face, the face detection box might pop up over ML menu;
Only way I know how to enable histogram is by opening up an image or MOV file and then hit info button. Exiting this previewing mode is getting me into liveview, no problems. Was this to test for? Couldn´t find any issues before or after.
Quote
- if you enable Canon histogram with the INFO key, then open ML menu in LiveView, some parts of our menu might be erased by Canon firmware;
Quote from: a1ex on August 23, 2018, 03:20:37 PM
Other than finding a way to reproduce and inserting printf's in the source code to see where it fails, no idea. Is the entire UI locked up? or just half-shutter? or only some of the actions triggered by half-shutter, such as autofocus?
It's only the autofocus system not reacting to the half shutter. The GUI behaves normally, well sort of... When the issue happens, if I press the half-shutter the Canon bottom bar appears (as usual), but (re)focusing doesn't work (not even the focus window appears). Then, if I depress the shutter and try a second time, the bottom Canon bar appears but shows that exposure is locked. IF I also press the exposure lock button, and keep shutter pressed half-way, then focus seems to kick in. If I depress the buttons focus becomes inactive and it all repeats... Btw. I can shoot a picture at any time, but it will be out of focus. So, to me this sounds more of a messed-up state, right ?
Right, sounds like something's messed up on the MPU side (the secondary CPU that actually turns the focus motor). On older models, I had to throttle the AF commands (https://bitbucket.org/hudson/magic-lantern/commits/0188f1297598ca98de0475ff5fb9a9039e3543e6?at=focus) to avoid a camera crash. Maybe the EOS M has similar quirks.
There are some low-level focus commands (http://www.magiclantern.fm/forum/index.php?topic=4997) that can give a very smooth movement, but they also leave the MPU in a messed up state on other models. Tried a couple of times to get some half-decent operation with these, unfortunately without success.
The MPU architecture on DIGIC 5 and newer is not exactly something I'm familiar with (https://www.magiclantern.fm/forum/index.php?topic=17596.msg199973#msg199973). In contrast, the architecture of the MPU used on DIGIC 4 (TX19A) is well documented and emulation is probably doable, given enough time to sit down (very unlikely during the next year, from my side). Understanding what the MPU code does might be helpful.
One low-hanging fruit is recording Canon's debug messages during AF in LiveView, hoping the focus commands are initiated on the main CPU. The startup-log-mpu (https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log-mpu/) builds might be a good starting point. Then, one may try to replay the MPU messages, hoping some of them may be low-level focus commands.
@Danne: on other models, pressing INFO while in LiveView activates Canon overlays, and one of them has a histogram. I'd be surprised if the EOS M doesn't have one.
Got it. Histogram correctly eats through ML menu and the fix is the same as for face detection. Confirmed working.
Cool. While you are at it, can you check whether 99 is required for browsing ML menu while recording H.264?
This value was introduced back in 2013, commit 5043182 (https://bitbucket.org/hudson/magic-lantern/commits/5043182); possibly unwanted change, as that commit included some unrelated stuff, besides what was described in the commit message. Just wanted to know what's up with it.
From QEMU experiments, I'd expect both 91 and 99 to work fine for both standby and recording. Maybe one of them blocks scrollwheel events or has some other quirks, no idea.
@a1ex: I'll have to look into the throttling commands. Thanks for pointing me to your commit.
One more little annoyance is the bottom Canon bar overwriting the ML one, when half-shutter pressed. I've came across a commit dealing with this -- forgot exactly which one -- but that would merely freeze the ML bar so that the Canon one takes cleanly over. Not exactly the right way, I'd say....
What I have in mind is a follows: By default, show the ML bottom bar, as is. If half-shutter pressed, restore background (part of image in LV), hide the ML bar from the bottom-most position and have it rendered on top of the (bottom) Canon bar. All additional stuff like DOF (near/far points) can be translated on top of the ML bar AND be updated in 'realtime'. At this instance (half-shutter still pressed), some items from the ML bar can also be hidden, since they are redundant (they appear anyhow in the Canon bar). This in my opinion would be nice...
For now, I simply moved the ML bar upwards just enough such that the Canon bar never overwrites it. It's quite fine, though what I've tried to describe above would be nicer, I think. Is this doable ? May main question is now -- can we quickly 'erase' the ML bar ? I.e., restore image pixels underneath ?
I'd probably try to block Canon bar completely; unfortunately, that's not straightforward (read: Canon code is too convoluted for me to understand what to patch). So, the next best thing was to block our bar and allow theirs. On 700D it works reasonably well, but there are some parts of Canon overlays conflicting with ML top bar this time. These parts are not present on older models.
Maybe you have looked at this PR (https://bitbucket.org/hudson/magic-lantern/pull-requests/665/650d-700d-eos-m-cleaner-method-for-hiding/diff) ?
Caveat: this tiny issue may turn into a big rabbit hole: we have already tried many workarounds (though none of them attempted to save and restore the bitmap overlay contents). And I don't currently have a way to test this workaround on cameras I don't own (need to update the emulator to handle LiveView, and that's not exactly an easy task).
Tried:
#define GUIMODE_ML_MENU ( RECORDING_H264 ? 91 : 91 ) // any from 90...102 ?!
While recording h264 and entering ML menu will work but almost immediately goes out of ML menu and some buggy black screen will appear when stopping recording. Pressing menu button and again let´s me start using the camera again.
Retesting again with:
#define GUIMODE_ML_MENU ( RECORDING_H264 ? 99 : 91 ) // any from 90...102 ?!
and everything works as expected. No bugs and going into ML menu works while recording and so on.
Alright, what about defining both as 99?
#define GUIMODE_ML_MENU ( RECORDING_H264 ? 99 : 99 ) // any from 90...102 ?!
Also works fine.
Quote from: a1ex on August 23, 2018, 09:01:33 PM
Maybe you have looked at this PR (https://bitbucket.org/hudson/magic-lantern/pull-requests/665/650d-700d-eos-m-cleaner-method-for-hiding/diff) ?
Indeed. Problems with this are: i) freezes the ML bar (no distance update near/far, etc. info), and ii) Canon's bar only partially covers the ML one, so it looks ugly.
Quote from: a1ex on August 23, 2018, 09:01:33 PM
Caveat: this tiny issue may turn into a big rabbit hole: we have already tried many workarounds (though none of them attempted to save and restore the bitmap overlay contents). And I don't currently have a way to test this workaround on cameras I don't own (need to update the emulator to handle LiveView, and that's not exactly an easy task).
What would it take to restore image info underneath ? On the other hand, it's not a big issue, as you've already pointed out. Also, I'm fine with my current solution (moved the ML bar slightly upwards so that it's never under the Canon bar, and re-enable real-time updates).
One more thing ;). I've played with magic zoom. I have it kick in on half-shutter + zoom ring (Default, I think). However, it only works every other time I use the half shutter. So on first half-press, magic zoom pops up as expected. If I depress half-shutter, it's still on screen... Only if I push half-shutter a second time it goes away, then it all repeats. Is this the normal behaviour ? I suppose not. I'd expect, once I release the half-shutter, it goes away and then the whole sequence repeats.
What could I do to attempt fixing this ? Where should I start ?
Canon code uses double-buffering; the back buffer ("idle" buffer in ML source) might be good enough for a backup copy.
At first, Magic Zoom used the Zoom In button for toggling; that would require one click to enable the zoomed window and another click to disable it. However, on some models, the Zoom In button did not work while recording (the MPU just does not send these events); in this case, half-shutter was used instead, but the overall logic wasn't changed. I assume you want it to be displayed only while holding half-shutter, right?
The toggling logic is in zebra.c, handle_zoom_overlay.
Similar tweaks were requested for the DIGIC peaking feature and for Canon's x10 zoom shortcut via half-shutter. The former should be easy, the latter conflicts with Canon's AF, so it's only enabled in MF.
Quote from: a1ex on August 23, 2018, 10:30:13 PM
At first, Magic Zoom used the Zoom In button for toggling; that would require one click to enable the zoomed window and another click to disable it. However, on some models, the Zoom In button did not work while recording (the MPU just does not send these events); in this case, half-shutter was used instead, but the overall logic wasn't changed. I assume you want it to be displayed only while holding half-shutter, right?
Yes, this is what I'm after.
Quote from: a1ex on August 23, 2018, 10:30:13 PM
The toggling logic is in zebra.c, handle_zoom_overlay.
Ok, I'll have a look and see if I can manage. I'll post here my findings.
Anyways, thanks for your help !
@a1ex: I've been trying to modify handle_zoom_overlay() to show the zoom overlay only while half pressed; unfortunately without success... It works if I press and then release half shutter (so it shows up and the disappears), but if I take a shot it remains on screen. This is what I've tried in handle_zoom_overlay(...) in zebra.c.
if(get_zoom_overlay_trigger_by_halfshutter()) {
//make sure zoom overlay is not shown and show it
if (!is_zoom_overlay_triggered_by_zoom_btn() && event->param == BGMT_PRESS_HALFSHUTTER)
zoom_overlay_toggle();
//make sure it is shown and hide it
else if(is_zoom_overlay_triggered_by_zoom_btn() && !get_halfshutter_pressed())
//else if (is_zoom_overlay_triggered_by_zoom_btn() && event->param == BGMT_UNPRESS_HALFSHUTTER)
zoom_overlay_toggle();
}
What am I doing wrong ?
Btw. EOSM (apparently) falls under the #ifdef CONFIG_ZOOM_BTN_NOT_WORKING_WHILE_RECORDING ... #endif branch so I'm basically trying there to replace
if (event->param == BGMT_PRESS_HALFSHUTTER && get_zoom_overlay_trigger_by_halfshutter())
zoom_overlay_toggle();
by the above.
HI there I am pretty new to all this I just got the EOS M and installed Magic Lantern and I am hooked already.
I wondered how can I help?
I wanted to play around with pushing the frame rates higher, I couldn't work out how to get it into 3x crop mode to get rid of moire and aliasing.
Still getting used to things. So the ML menu just over rides everything in the standard canon menu? I am on 25p but in the ML menu it says 30p.
I am just reading into everything now and it is all quite complex and overwhelming but if I can do some testing or reports to help I will as I would like to use this cam to shoot a documentary and have some more reliability and functionality, not that it will be overnight but every little counts right?
Is there a way to shoot in log profile in standard 1080 25p reliably?
Anyway a lot of questions so leave it at that. And greeting to you all. Dom.
Quote from: Danne on August 07, 2018, 03:17:46 PM
Here is a version with filled preview screen in mv1080p. Didn´t test so please report back.
Finally got around to play with this build, i didnt follow the "guide", i just selected crop_rec, mlv lite, lua and sd-uhs, selected mv1080p, 1:1 aspect ratio, 1736x1120 resolution, 14 bit and enabled the sd card hack under scripts...so far so good, sometimes i manage to get 2 seconds sometimes 12 seconds, i'm using the Kingston Canvas Go 64GB class10 UHS-I U3 v30 sdcard, got some purple flashe's artifacts on some clips.
Cool. Set it to 24fps for continuous action.
What's up with the black border on the left?
Quote from: Danne on August 26, 2018, 10:17:10 PM
Cool. Set it to 24fps for continuous action.
Will test it further this week
Quote from: Danne on August 26, 2018, 10:17:10 PMWhat's up with the black border on the left?
you mean both left and right? I forgot to adjust the width to 1920... 1920-1736=184.... 92px black bars were added to each side...i was in a hurry and only noticed it after render.
one of the things that i miss compared to the older build i was using is the ability to use magic zoom, i only use manual focus and magic zoom was very usefull to focus things...i tried pressing the zoom button but it doesnt do anything.
Sorry if I'm being daft, but I can't find the TFT_SIO mo for flipping/mirroring the EOSM's screen anywhere. I see a bunch of old posts by people like @DFort, and mentions it being on his bitbucket page, but I don't see it there. Has this module just died off?
The TFT_SIO module is a development tool. You should be able to compile ML before playing around with it:
https://bitbucket.org/hudson/magic-lantern/src/tft_lcd/modules/tft_regs/
hg update -C tft_lcd
Quote from: dfort on August 28, 2018, 04:51:44 PM
The TFT_SIO module is a development tool. You should be able to compile ML before playing around with it:
https://bitbucket.org/hudson/magic-lantern/src/tft_lcd/modules/tft_regs/
hg update -C tft_lcd
ok :( I've got some research to do tonight.
Now with this non-crop mode thanks to the 1080mlv is that possible to shot non-crop without aliasing ?
Thanks
I use the latest Danne build a lot and have some feedback.
The white level error is easy to correct in post but it seems like it affects autofocus. Autofocus does't work well now.
I use 2520 * 1146 resolution and it gets a good image quality. I use 24 fps and get almost continous recording. It's essential to get highest resolution as possible because the higher the resolution the less noise and sharper image quality even looking at a monitor with lower resolution. I would love to have a resolution at 2560*xxxx because then it will be in 1440p in Youtube. If you upload in 2520 you get only 1080p. So now I upscale before I upload.
It would be nice to have 10 bit (and 8 bit) lossless and working liveview in 3K.
The camera locks up if you try to take pictures when croprec is activated now. It would be nice if this could be fixed.
The most fantastic thing would be if the writing speed could be even higher with a revision 2 of SD hack.
Quote from: EOS M dude 1 on September 04, 2018, 09:30:52 PM
I use 2520 * 1146 resolution and it gets a good image quality. I use 24 fps and get almost continous recording. It's essential to get highest resolution as possible because the higher the resolution the less noise and sharper image quality even looking at a monitor with lower resolution. I would love to have a resolution at 2560*xxxx because then it will be in 1440p in Youtube. If you upload in 2520 you get only 1080p. So now I upscale before I upload.
If you use this build:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jul25.EOSM202_2K-3K-4K_10bit_patch_g3gg0.zip
And enable the 3k hack in crop_rec you can set it effectively to something like 2560x1164 and fps override to 24 fps.
@Danne
If i remember correctly there is only 10 bit lossless with 2,5K.
And no liveview while filming in 3K.
Hi!
Where can i download latest Canon EOS-M build for 2.0.3 firmware that i am currently rocking? :)
Cheers! 8)
EOSM.203 isn't mainline yet but I'm posting test builds on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
Quote from: dfort on September 13, 2018, 03:56:29 PM
EOSM.203 isn't mainline yet but I'm posting test builds on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
I tried to install this: crop_rec_4k_mlv_snd.2018Aug06.EOSM2103.zip
When i try to update firmware it says: Update file cannot be found.
Please cheack the memory card and reload the battery and try again.
Do i do something wrong?
I try to install it same way as i would do other builds (nightly)
Format card in cam...then copy from zip and make card bootable with eoscard...
Then try...
Quotecrop_rec_4k_mlv_snd.2018Aug06.EOSM2103.zip
is for EOSM2, not EOSM
Quote from: critix on September 13, 2018, 06:00:25 PM
Format card in cam...then copy from zip and make card bootable with eoscard...
Then try... is for EOSM2, not EOSM
Oh mate now i feel stupid, EOSM2... daaamn!
It is a bit confusing but there is a working ML-SETUP.FIR for the EOSM.203 that will set the camera and card bootflag.
Yes, but @Muwex tried to use the EOSM2 version, instead of the EOSM version ...
That's the confusing part. The way the build scripts name the files it is hard to tell the EOSM from the EOSM2 because the EOSM firmware starts with a number 2 and there is no delimiter between the camera name and the firmware version.
For example:
magiclantern-Nightly.2018Sep13.EOSM203.zip (EOSM.203)
vs.
magiclantern-Nightly.2018Sep13.EOSM2103.zip (EOSM2.103)
But i got it working now when i found right version! :)
THIS INSTALLED: crop_rec_4k_mlv_lite_snd.2018Mar10.EOSM203.zip
Will post if i have something! :)
Thanks!
Hi All,
Is it possible to get 24 fps, 1080p raw 8...11 bit lossless & h264 proxy on EOS-M by using SD hack ? When we use 8...11, is it darker than usual on liveview or normal ?
Thanks
Only problem is the H.264 proxy. I haven't had much luck with it on the EOSM. I believe that the LiveView brightness when switching to various bit depths and lossless compression has been fixed--at least I don't see the problem on the latest versions.
Quote from: dfort on September 16, 2018, 08:02:58 PM
Only problem is the H.264 proxy. I haven't had much luck with it on the EOSM. I believe that the LiveView brightness when switching to various bit depths and lossless compression has been fixed--at least I don't see the problem on the latest versions.
Thank you for the update Dfort. Do we have continuous rec in 1080p 24fps 14bit lossless +12 bits lossless with eosm or only with 8...11bits ?
Envoyé de mon iPhone en utilisant Tapatalk
Quote from: 12georgiadis on September 16, 2018, 09:56:03 PM
Do we have continuous rec in 1080p 24fps 14bit lossless +12 bits lossless with eosm or only with 8...11bits ?
Tricky question to answer. The mv1080 mode is missing on the EOSM but Danne has a crop_rec module that will put it in mv1080 mode. He also has builds with the experimental sd_uhs module which allows longer recording times at higher resolutions. I've recorded continuous 2520x1080 at 24fps with audio using his builds. Note that all APS-C cameras in mv1080 mode will only record a maximum of about 1736x976. You probably already know this but it is worth repeating for newer users that might be reading this.
Quote from: dfort on September 17, 2018, 05:15:28 PM
Tricky question to answer. The mv1080 mode is missing on the EOSM but Danne has a crop_rec module that will put it in mv1080 mode. He also has builds with the experimental sd_uhs module which allows longer recording times at higher resolutions. I've recorded continuous 2520x1080 at 24fps with audio using his builds. Note that all APS-C cameras in mv1080 mode will only record a maximum of about 1736x976. You probably already know this but it is worth repeating for newer users that might be reading this.
Thank you Dfort, it's always good to refresh our mind and the progress of the thread. I just bought an EOS-M and want to experiment. That's why I'm asking about the current possibilites. So, if I understand correctly, there is a build with Sd_uhs hack + MV1080 (1736*976) and 2520*1080 or this are all separate builds ? 1736*976 is lineskip 3X3 ?
Here is a build which will work with crop_rec high res builds and sd_uhs hack:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Aug07.EOSM202_mv1080p.zip
Not gonna work so good with non crop modes.
Thank you Danne. WHen you say Non crop mode you mean 1736*976 ?
Yes, if you set that with the mv1080p crop setting you get nice 16:9 output.
Thanks !
Quote from: dfort on March 27, 2018, 05:24:35 AM
I've got a couple of third party EF-M to EF adapters. The top one is a Fotasy and the bottom one a Fotodiox. Note that the Fotasy adapter has a push button. This is an important difference. One of my lenses almost got stuck on the Fotasy adapter. No problems with the Fotodiox adapter.
Turns out that the Fotodiox adapter is pretty much identical to the Canon adapter. FYI--buyer beware.
Hi! Sorry the OT
I bought a Viltrox EF adapter and it works like a charm with EF lenses. A few a days ago a tried to add a mechanical Nikon adapter to Viltrox to put an AIS lens on my EOSM but when I tried to shoot a photo, shutter didn't work. Do you know if Fotasy, Fotodiox and Canon adapters have the same issue?
Thanks!
The mechanical adapter doesn't communicate with the camera so it "thinks" there's no lens attached.
(https://farm2.staticflickr.com/1895/44713325512_bd4dba85a5.jpg) (https://flic.kr/p/2b8atTo)
It works, thank you very much!
You are doing a great work with this camera. ;)
(https://farm2.staticflickr.com/1861/30923713738_26d6641118_n.jpg) (https://flic.kr/p/P7C7Jf)
You mean you dumped your other cameras and kept the EOSM?
Hi, so i'm just setting up a EOS M and had already updated the firmware, when I noticed here that magic lantern seems to be still in a rough beta mode for 203? Is this build proving to be stable and debuted yet?
https://bitbucket.org/daniel_fort/magic-lantern/downloads/crop_rec_4k_mlv_lite_snd.2018Mar10.EOSM203.zip
I'm wondering, compared head to head, would anyone venture to say if ML running a stable build on 202 vs ML on 203 at this time, which is over all better to use for film and ect? What are the trade offs?
thanks!
That build should be fine but it is still experimental meaning that there hasn't been enough user feedback to make the switch from 2.0.2 to 2.0.3 in the main repository. You can do a firmware update to regress to 2.0.2. To get the Canon firmware for 2.0.2 you can click on the "Useful Links (https://builds.magiclantern.fm/EOSM-202.html#links)" button on the nightly downloads page. I've also got a EOSM Canon Firmware for Testers.zip package with both 2.0.2. and 2.0.3 Canon updaters on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
any one have the 1x3 binning working on eosm yet? 5d3 quality and no aliasing? can it possibly be true? 8)
So how many people are using 203 magic lantern for the m?
I'm thinking about going for , I'm really hyped on it and I'm very new to magic lantern
Quote from: Teamsleepkid on September 22, 2018, 07:31:25 AM
any one have the 1x3 binning working on eosm yet? 5d3 quality and no aliasing? can it possibly be true? 8)
Looking forward to this too. :)
Anyone tried the newest croprec.mo (for 700D) on the EOSM? Does it work?
I am having some problems with getting MV1080 to work on my EOS-M I made a video showing the issue that I am having. It only happens after I record something and requires a full reboot to fix it.
https://youtu.be/ryF2BldZ2x4 (https://youtu.be/ryF2BldZ2x4)
I played the raw recording method, you know - it bothers to use postproduction, even in some minor situations.
I would like to get good quality in H264. Does the magical flashlight improve the quality in 264? I am very upset by the quality of comparing with the former Sony A6000 camera.
Or move to a more new , compact m100?
Hey guys! Fantastic work on this camera! I'm loving every second of it!
I'm sure this was answered ad nauseam, but has there been any updates in getting this camera to work on Android or at least there's a workaround for it? I've been wanting to use my tablet as a monitor but I can't seem to get the EOS M to communicate with qDslrDashboard. It would connect very briefly via USB and then disconnect again. I can't seem to narrow down the search for more information. Any thoughts?
As far as I know, the EOSM is still not supported in DSLR controller or Dashboard. I don't think the code has been cracked yet. It's been showing in development on DSLR Controller for as long as I can remember.
Quote from: Danne on September 17, 2018, 08:39:23 PM
Here is a build which will work with crop_rec high res builds and sd_uhs hack:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Aug07.EOSM202_mv1080p.zip
Not gonna work so good with non crop modes.
Just tried this build, recording on the 2.5k preset ends around 8 seconds. I think there is some sort of issue with the sd card hack autorun.
8 sec sounds about right with 2.5k setting on.
Hello all - I'm a longtime lurker, seldom a poster. I've been messing with using my EOSM as a Digital Super 8 camera and I'm pretty happy with the results.
For the video below I used the following setup.
6mm f/1.2 Pentax TV lens (paper shim between lens and C mount-EOSM adapter, for infinity focus)
Tiffen Digital Diffusion 5 filter (reduces moire artefacts)
EOSM with latest ML build
18fps override (exact)
5x zoom
12bit lossless RAW
4:3 aspect
1440 x 1080
This video has effects applied - FilmConvert's Super 8 grain; FCPX native "aged film" effect applied very sparingly for jitter and a little dust; a telecine'd Super 8 black frame (keyed over footage). If there is interest, I can post the ungraded footage.
https://vimeo.com/294197368/fb4876b181 (https://vimeo.com/294197368/fb4876b181)
Hi !
I just made some tests with magiclantern-Nightly.2018Aug07.EOSM202_mv1080p.
I used San disk Extreme 95MB/s
1008/1018, lossless 12, 24fps, cropmode X5. I only had corrupted clips. I'll test tomorrow with another sd card.
I noticed that my sound was disabled everytime I use eosm with magiclantern. I even tried with H264 normal and crop mode with no luck. It's not the case without magiclantern.
Is it normal ?
I tried to use h264 proxy with cropmode but it didn't work. Do you think it will be possible to enable it in the future ?
Do you have other recommandations ??
Thank you !
Quote from: 12georgiadis on October 10, 2018, 11:44:08 PM
I just made some tests with magiclantern-Nightly.2018Aug07.EOSM202_mv1080p.
That build from Danne is about as bleeding edge as you can get. Did you remember to wear gloves and safety goggles before starting your camera?
Seriously, I just downloaded and tried out that build and it took me a few tries but it does work--pretty amazing really.
(https://farm2.staticflickr.com/1952/43441197830_45e4fb6569.jpg) (https://flic.kr/p/29bKuDu)
Settings I used:
Make sure the Canon Movie setting is on 1280x720/60 (very important)
Loaded these modules:
crop_rec
lua
mlv_lite
mlv_snd
sd_uhs
In the LUA menu select these scripts to Autorun:
mv1080p_12bit_iso100_24fps
enable SD overclocking
I also used a SanDisk Extreme Pro 95MB/s card and got continuous recording 1736x936 with audio.
You are really pushing it with the H.264 proxy. That used to be the only way to get the EOSM to record mv1080 video but we were lucky to get a few uncorrupt frames.
Quote from: dfort on October 12, 2018, 12:12:24 AM
That build from Danne is about as bleeding edge as you can get. Did you remember to wear gloves and safety goggles before starting your camera?
Seriously, I just downloaded and tried out that build and it took me a few tries but it does work--pretty amazing really.
(https://farm2.staticflickr.com/1952/43441197830_45e4fb6569.jpg) (https://flic.kr/p/29bKuDu)
Settings I used:
Make sure the Canon Movie setting is on 1280x720/60 (very important)
Loaded these modules:
crop_rec
lua
mlv_lite
mlv_snd
sd_uhs
In the LUA menu select these scripts to Autorun:
mv1080p_12bit_iso100_24fps
enable SD overclocking
I also used a SanDisk Extreme Pro 95MB/s card and got continuous recording 1736x936 with audio.
You are really pushing it with the H.264 proxy. That used to be the only way to get the EOSM to record mv1080 video but we were lucky to get a few uncorrupt frames.
Thank you Dfort for all these useful informations ! Very cool if we can get 1736x936 with audio!
Do you get it in cropmode or normal with line skip ?
I'm just starting with EOSM and it was a bit frustrating when you come from 5D3 but this is because I didn't know these hidden tips =)
I need H264 proxy for my workflow and it doesn't matter if I can get only 8...11 losless with EOS-M... I prefer to have a cool preview and offline/online workflow !
Do you put your H264 settings in 0.1x ?
What are the risks to enable sd overcloacking ? I didn't use this option in my last test.
Next month, I go to HK and I'd like to find a viltrox speedbooster EF-M to make some test in cropmode with the 11-22mm!
Hi
Does anyone know if this build works for the M5? Thanks. I'd like to use it for bracketing, but haven't used it for several years now, since I had the 600D.
Quote from: mcgillro on October 12, 2018, 07:46:24 AM
Does anyone know if this build works for the M5?
Nope--it definitely doesn't work.
@12georgiadis - I also have a 5D3 and an EOSM and can tell you they are different cameras--very different.
I don't think any camera, not just the EOSM, can successfully do the H.264 proxy workflow the way you can do it with the 5D3. One reason may be that on the 5D3 you can record H.264 on the SD card while recording raw on the CF card.
Quote from: 12georgiadis on October 12, 2018, 01:29:34 AM
Do you put your H264 settings in 0.1x ?
Not even that will do it though you're welcome to keep trying. If you can get it working please share your settings.
Quote from: 12georgiadis on October 12, 2018, 01:29:34 AM
What are the risks to enable sd overcloacking ?
Global warming and the possibility of ruining your card.
Quote from: 12georgiadis on October 12, 2018, 01:29:34 AM
Next month, I go to HK and I'd like to find a viltrox speedbooster EF-M to make some test in cropmode with the 11-22mm!
Let us know how it works out. I only tried one cheap ebay speedbooster for the EOSM and of course it was rather disappointing.
Thanks for the reply.
Quote from: dfort on October 12, 2018, 08:02:49 AM
I don't think any camera, not just the EOSM, can successfully do the H.264 proxy workflow the way you can do it with the 5D3. One reason may be that on the 5D3 you can record H.264 on the SD card while recording raw on the CF card.
Not even that will do it though you're welcome to keep trying. If you can get it working please share your settings.
Let us know how it works out. I only tried one cheap ebay speedbooster for the EOSM and of course it was rather disappointing.
Thanks Dfort. Tested with your settings and it works very well !! It's impressive and there isn't a lot of aliasing on most shots.
H264 proxy is not working. It is freezing. MOV is recording with sound but corrupted&frozen frame and MLV is 10ko. Maybe it can work with a 8...11bit script?
Can we record MV1080 in 8...11 ?
Cropmode possible in MV1080 ?
Sorry for the noob questions but it is very different from my 7D & 5D3 settings !
Hi !
What is the best resolution to have the maximum image quality with the less aliasing possible : 1736x1120 (1:2) or 1736x976 (16/9) ?
Also i hesitate between Danne's builds : Nightly.2018Aug07.EOSM202_mv1080p
And
Nightly.2018Jul03.EOSM202_mv1080p
It seems the Jully version does not allow the 1736x976 ?
Any help would be very welcome !
Thanks a lot.
You can record mv1080p continuous with 14bit lossless(16:9, 24 fps) with sd_uhs module set. You find the setting in crop rec section. Regular RAW video(mv720p will not work with this build):
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Aug07.EOSM202_mv1080p.zip
OK thank you Danne. For now, I'll stick to MV1080, that's the best result for regular shooting !
Only way to get mv1080 is with the build above but I assume that is what you are using right now? Otherwise you are shooting mv720p even when mv1080p is selected in canon menu.
Danne,
yes I'm using this build with 1080MV.
What I'm looking for is something that doesn't seem to work :
1) 1080MV with cropmode & normal to shoot without aliasing and to extend focal lenght possibilities.
2) 1080MV with cropmode + Lossless 8...11bits + H264 Proxy+sound for a similar 5D3 workflow
3) or maybe 1X3 is a possible solution to shoot smaller than HD rez but without aliasing ? I suppose it's not for now because of the development
Just exit crop rec and enable movie crop mode for 1920x1080p 3x zoom mode. Working with all bits.
@12georgiadis
1-Like what Danne said.
2-H.264 doesn't work for all cameras except for 5D3, If you enable it you will have corrupted frames in both MLV and H.264 Especially with lossless compression.
3-It's working but with very wide aspect ratio 1736x386. We are trying to increase the resolution.. nothing interesting yet to make it under preset.
Thank you Danne & theBilalFakhouri for the update infos !!
Hi!
I try Danne build (Nightly.2018Aug07.EOSM202_mv1080p), but always freez the lcd when I focusing in the canon live view and ML view too. Globaldraw always on, preview set Real-time. The jul03 build is work fine with same settings.
what do i do wrong? :)
thanks.
you must be in MF , AF doesn't work with mv1080p i think . At least with the 2 builds i tried .
Anyway i'll stick with danne's Nightly.2018Aug07.EOSM202_mv1080p . It allows some great quality footage in 1736x976 16/9 , and for the tricky shots with aliasing i found i can get rid of it with Mlv app .
So far so good !
Quote from: Lanza on October 13, 2018, 02:59:20 AM
you must be in MF , AF doesn't work with mv1080p i think . At least with the 2 builds i tried .
Anyway i'll stick with danne's Nightly.2018Aug07.EOSM202_mv1080p . It allows some great quality footage in 1736x976 16/9 , and for the tricky shots with aliasing i found i can get rid of it with Mlv app .
So far so good !
thanxs your's reply
Trying to get 1x3 Binning with increased resolution with Danne:
"I got 1736x2184 using adtg_gui without problems (resized to 1736x728). When enabling preset in mv720 it offer 1736x2084 resized to 1736x694 . Of course this for EOS M maybe you should tweak something in raw.c like you did before to get max resolution. But hey it's 1x3 Binning :D .
Here is a compiled version: Download (https://drive.google.com/open?id=1k-g48HyqOdhfZjWGcRwKv_3ZlnD_40pY).
Here is the settings:
case CROP_PRESET_3x3_mv1080_EOSM:
cmos_new[7] = 0x260;
cmos_new[8] = 0x400;
break;
case CROP_PRESET_3x3_mv1080_EOSM:
adtg_new[0] = (struct adtg_new) {6, 0x800C, 0};
adtg_new[1] = (struct adtg_new) {2, 0x8172, 0x9fd};
adtg_new[2] = (struct adtg_new) {2, 0x8173, 0x453};
adtg_new[3] = (struct adtg_new) {2, 0x8178, 0x9fd};
adtg_new[4] = (struct adtg_new) {2, 0x8179, 0x453};
adtg_new[5] = (struct adtg_new) {2, 0x8196, 0x12e};
adtg_new[6] = (struct adtg_new) {2, 0x8197, 0x38c};
adtg_new[7] = (struct adtg_new) {2, 0x82b6, 0x9f4};
break;
static inline uint32_t reg_override_mv1080_eosm(uint32_t reg, uint32_t old_val)
{
switch (reg)
{
/* raw resolution (end line/column) */
/* X: (3072+140)/8 + 0x17, adjusted for 3072 in raw_rec */
case 0xC0F06804: return 0x8a601d4; // 2520x1386 x5 Mode;
case 0xC0F06014: return 0x9df;
case 0xC0F0600c: return 0x20f020f;
case 0xC0F06008: return 0x20f020f;
case 0xC0F06010: return 0x20f;
case 0xC0F37014: return 0xe;
case 0xC0F0713c: return 0x8a7;
case 0xC0F07150: return 0x46a;
The settings is a mix between mv1080 for EOS M and 1x3 Binning."
Unfortunately the resolution hasn't increased it stays 1736x1120, in 700D as I said I can get up to 1736x2084 in mv720. So what is the limit for the resolution here? Before it was from raw.c (https://www.magiclantern.fm/forum/index.php?topic=9741.msg203530#msg203530) when we tried to get mv1080, But now? 1x3 Binning is working but when hit recording at above settings in EOS M we have a jumping frames it seems like corrupted in 700D it's working without probelms.
When Danne tried different values in raw.c:
"Good catch with the exception. Unfortunately I am getting corruption as soon as going over 1150 the same as when filming mv1080p."
What the problem can be here?
thanks bila. been messing around with it. does seem like 1x3 is working if you set canon menu to 720p you get live view. but its about a 5x crop it feels like. doesn't appear to have any aliasing though. i have no idea what I'm doing though just playing around. i almost bricked my camera yesterday. hit a button while formatting and it was unresponsive. somehow got it back working. close call.
@Teamsleepkid
Unfortunately it doesn't work yet in EOS M. corrupted frames in above settings.
Quote from: dfort on September 20, 2018, 04:55:23 AM
(https://farm2.staticflickr.com/1861/30923713738_26d6641118_n.jpg) (https://flic.kr/p/P7C7Jf)
You mean you dumped your other cameras and kept the EOSM?
Ahah, yes but not because of ML on EOSM! [emoji6]
Just interested in the different crop factors for current recording capabilities?
So I played arround with the liveview in MV1080 and stumbled uppon this little trick:
When in MV1080 and using Realtime Liveview you get a more accurate, fluid representation by using "Anamorphic 9:5" and "DigitalPanning".
However the framing, although better, is still not properly centered and is missing info on the top and bottom.
Not sure if this helps, but maybe there is a way to fix the liveview this way?
Although Im optimistic there is a way to make it work properly... at least in 16:9... but I wouldnt know where to start.
Here some comparisons:
(https://thumb.ibb.co/huxWOA/Streched.jpg) (https://ibb.co/huxWOA)
Streched Realtime liveview
(https://thumb.ibb.co/mh8o3A/Slow-correct-framing.jpg) (https://ibb.co/mh8o3A)
Correct framing but slow liveview
(https://thumb.ibb.co/b1iXVq/Anamorph9-5and-Panning.jpg) (https://ibb.co/b1iXVq)
Anamorphic9:5 and DigitalPanning Method
(https://thumb.ibb.co/h5rEbV/recording-worksfine.jpg) (https://ibb.co/h5rEbV)
Recording is not affected
(https://thumb.ibb.co/mPe0GV/MV1080.jpg) (https://ibb.co/mPe0GV)
Settings
...
Hope this is helpfull in any way.
Cheers!
is there a read me or instruction on which model this ML is for?
is this only for M1?
i was not sure if M is general for m1, m2, m3, m5, m6, m10, and m100.
This thread is for Canon EOS M (without suffix).
Top of page -> Downloads -> Download Nightly Builds -> Your cam is not listed? -> Last item. M100 runs PowerShot firmware, too.
Quote from: whothe on October 26, 2018, 04:05:15 PM
When in MV1080 and using Realtime Liveview you get a more accurate, fluid representation by using "Anamorphic 9:5" and "DigitalPanning".
However the framing, although better, is still not properly centered and is missing info on the top and bottom.
Not quite following you. The Anamorphic 9:5 setting is under the Display menu but where's DigitalPanning? I'm not seeing a big improvement in preview performance just by turning on Anamorphic 9:5.
Quote from: dfort on October 31, 2018, 06:49:43 PM
Not quite following you. The Anamorphic 9:5 setting is under the Display menu but where's DigitalPanning? I'm not seeing a big improvement in preview performance just by turning on Anamorphic 9:5.
Right!
The quality of the improvement is debatable.
I meant: In my opinion this method offered the best trade-off between the correctly framed but laggy "Framing" live view (selectable in the raw menu) and the fluid but very stretched "Realtime" live view (selectable in the raw menu).
The effect of the describe settings are:
Anamorphic 9:5=Elimination of the stretching of the real-time liveview
Digital Panning (in the advanced Raw settings)= pushing the liveview upwards a tiny bit towards (although far from) center framing
Sorry for my inaccurate post before.
I hope this is not confusing things even more.
Although center framing in real-time liveview would help even more in getting a sens of what I am recording, I preferred the non-stretched liveview over the stretched... even with the cutoff framing...
How much does that lens cover? would it cover 2.5k wide shot you think?
Quote from: lintel on October 10, 2018, 01:01:42 PM
Hello all - I'm a longtime lurker, seldom a poster. I've been messing with using my EOSM as a Digital Super 8 camera and I'm pretty happy with the results.
For the video below I used the following setup.
6mm f/1.2 Pentax TV lens (paper shim between lens and C mount-EOSM adapter, for infinity focus)
Tiffen Digital Diffusion 5 filter (reduces moire artefacts)
EOSM with latest ML build
18fps override (exact)
5x zoom
12bit lossless RAW
4:3 aspect
1440 x 1080
This video has effects applied - FilmConvert's Super 8 grain; FCPX native "aged film" effect applied very sparingly for jitter and a little dust; a telecine'd Super 8 black frame (keyed over footage). If there is interest, I can post the ungraded footage.
https://vimeo.com/294197368/fb4876b181 (https://vimeo.com/294197368/fb4876b181)
Quote from: Tullen on November 05, 2018, 10:41:00 AM
How much does that lens cover? would it cover 2.5k wide shot you think?
The Pentax 6mm f1.2 is for 1/2 inch sensors I think so will vignette anything beyond max resolution in movie crop mode (which is 1800x1030). I used that lens in a couple shots in the video linked here below at this res. See the shot starting at the 3:39 minute mark and at 4:10, and you'll see some vignetting in the top left hand corner: https://youtu.be/5YeUUZS9t3c?t=219 (the other non vignetting shots were done with a stock ef-m lens).
If you want to avoid vignetting in 5x zoom mode (with 2.5k res) I think you'll need lenses that are at least for 2/3 inch sensors and above.
Hi
I test 3x3_mv1080-EOSM in 1736x1040 with a vaf AA filter and this is how great !!!
What we need, is a good liveview setting to frame correctly.
Because, with this mod, it's 1:1 box to frame...
Please, how to make it real good ?
Thanks
Hi,
I am new to MagicLantern. I would like to use it with EOS M. At the nigthly build section (https://builds.magiclantern.fm/EOSM-202.html) I see the latest build: "magiclantern-Nightly.2018Jul03.EOSM202" has a failed test case. Can I use this firmware without any problem or should I use other version?
any way to change the "Canon digital ISO" default value of 1 EV to 0 or other values?
i can change equivalent ISO, Canon analog iso, and ML digital ISO. but not the canon digital iso. :(
Quote from: zsolex on November 15, 2018, 02:50:43 PM
...At the nigthly build section (https://builds.magiclantern.fm/EOSM-202.html) I see the latest build: "magiclantern-Nightly.2018Jul03.EOSM202" has a failed test case. Can I use this firmware without any problem or should I use other version?
The EOSM failed the "Null pointer test" -- something that hasn't been a problem with this camera. In addition:
QuoteThis build was tested, to a limited extent, in QEMU (a virtual machine modified to run Canon firmware).
Please take the results with a grain of salt - this is not the same as running on a physical camera.
As far as using any version of ML, "without any problem," nobody can guarantee that.
However, if you want to expand the capability of this little camera--by all means give ML a try. If you do find problems, please let us know. This is an open source project so if you want to have even more fun, dive into the code.
Quote from: regularfellow on November 14, 2018, 06:46:22 PM
I test 3x3_mv1080-EOSM in 1736x1040 with a vaf AA filter and this is how great !!!
Which VAF filter are you using? I haven't found anything for the EOSM.
For the first install (EOS M) can I use SDXC card or only SDHC? I have read this on some webpage..
Outdated, restriction doesn't apply anymore.
I just put a Cheap ebay vaf filter for a 50d inside a eos m to eos adapter.
It works well.
But it's hard to frame with the 1080 3x3 option
Link?
http://www.mosaicengineering.com/products/vaf/50d.html
Some time, on ebay, second hand one are cheap.
Don't quite understand how you shoehorned that VAF into the EOSM but hey, all the more power if it works for you.
Yeah, framing is an issue. That's one of the quirks we're still struggling with. The EOSM is always in LiveView mode and for some reason defaults to 1280p at 29.97 fps so getting it to shoot mv1080 at 24 fps was a real challenge.
sounds like if we get the 1x3 working properly on the eos m we won't need a vaf though. true?
just want to know how much of a difference with and without the movie crop mode.
Can anyone help?
P.S. when shooting RAW
Quote from: Teamsleepkid on November 19, 2018, 10:03:11 AM
sounds like if we get the 1x3 working properly on the eos m we won't need a vaf though. true?
That's right, in theory. It would also mean Dual ISO without aliasing. Again, in theory. The limit is the SD card write speed so you'll either have to settle for a smaller image size or very short recording times.
Quote from: youshouldtry11 on November 19, 2018, 05:04:00 PM
just want to know how much of a difference with and without the movie crop mode.
What exactly is your question? Movie crop mode records a smaller area of the sensor using 1x1 sampling while the nightly build (a.k.a. unified branch) in non-crop mode does 5x3 sampling. Confusing? Read more about it on this topic:
https://www.magiclantern.fm/forum/index.php?topic=16608.0
The crop_rec_4k branch allows you to shoot 3x3 sampling with a wide aspect ratio. Also, Danne has some highly experimental builds that can do 3x3 sampling but with a larger image size and using the full dimensions of the sensor. We haven't figured out 1x3 sampling on this camera yet.
Hello everyone!
I'm not sure how all this is going to fair up at the end but I thought I'd come here for a specific advise regarding my upcoming trip and other user's proven workflow, I'd looked and watched YouTube videos but I'm not sure if what I'm thinking is even possible...
Here is my current situation, I've accepted a self inflicted challenge (via our local filmmaking hub) to go into a unfamiliar place destination and record a 7 day blog using whatever equipment available.
2 weeks from now I will be in Sapporo Japan to visit a friend!
I only have these available for me to use.
1. Old IPhone 8
2. iPad Pro lots of memory (lumafusion and other video editing app installed)
3. Bought a Second hand Canon EOS M with lens etc... (all I can afford at the moment) with ML soon to be installed into a card.
4. Rode field shotgun mic.
5. Still to purchase memory card and reader.
I know that I will be shooting a few night scenes the reason why I bought the Canon EOS M better sensor so according to my research...my iPhone 8 light sensor is just not up to the task of low light scenes.
My question to the community is this.
I am not really set up for raw recording workflow, from my research (YouTube) most of the people are all using LM to shoot RAW and would either have to go into a specific Mac desktop / laptop workflow to get a useable friendly format for editing, for this coming trip I don't have the time nor the set up, in addition to time constraints I would have to deliver some rough cuts in a day.
1. So with this in mind, I read somewhere here that I could disable the RAW recording in ML video and activate 3 x zoom, would this enable H264 codec? Just like recording in the native camera.
2. Would this then show up as an MP4 file format upon import on my iPad Pro via a card reader?
3. Is there another way that I can utilised all the controls ML provides without recording in RAW.
Lastly, so with ML running on the card, will it be advisable to install on a few memory cards? If take the memory card out of the camera and insert a new initialised card without ML installed, will my Canon EOS M defaults to the original firmware I gather? Sorry it's now late at night and my brain is turning into mush.
I apologised in advance if this is way basic questions for the community, I'm new to all this and due to the lack of time I have left, I'm trying to soak this all in.
Basically what I'm trying to achieve while I'm away is to be able to produce a 1-2 minutes Vblog using the equipment and App I have on my disposal. Maybe using my iPhone for day outside shots and use my Canon EOS M for less lighting situations.
If you get to read this far, I thank you in advance and in good groovy karma points! Hopefully I'd learn enough to do the same for someone in the future.
Cheers!
I never try without the vaf filter but it depends the lens you use for the aliasing.
I put it inside a cheap eos to eos m adapter, it's very easy to do it.
Today, the camera record greatly in full size sensor mode. But it's limited to the ability to frame
frame with the 1 : 1 ratio
But i say, developers, you are such amazing to change what change on this little camera !
@regularfellow - You are mounting the VAF filter inside the EF to EF-M adapter? Could you post a picture of that?
Yes but it's on a cheap one. So you have more space to do it.
It's a bad work with scotch, I am not as proud of it to share pictures of it. Sorry.
You just have to put any kind of filter between the lens and the sensor and it's effactive...
New version to found here:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208810#msg208810
These settings in Crop mode
(https://i.postimg.cc/Hk1dvgBn/VRAM0-PPM-500px.png)
Practically a port of some older stuff I had going before. New is 1x3_1736x1120 mode. Couldn´t get any higher without corrupted frames. Talking corruption all setting have to go through Crop mode or Movie crop mode in this build since I changed the height 727 exception in raw.c to 1150.
Commits:
https://bitbucket.org/Dannephoto/magic-lantern/commits/c89935365f0d434fa17b79956a9e6cff8c441642
https://bitbucket.org/Dannephoto/magic-lantern/commits/9b2e892094395eae60d3764574dd1d3f1f3d105f
Both 100D and eosm have their own quirks when it comes to giving up when increasing height in 1x3. Any help and hints here would be great. Got some good help already from both Bilal and levas and of course A1ex whose crop_rec.c code we are all using here.
Edit:
Also possible to add 10 or 12 bit from the Crop mode submenu on top of a selected Crop mode setting:
(https://i.postimg.cc/hvhF6tDL/VRAM0-PPM-scaled.png)
Excellent. Now I suppose you need a new focus pixel map?
Hell yeah @dfort.
No footage yet but hopefully some of the downloaders could provide. There's a focus pixel map for the mv1080p setting already? Only one needed for 1x3 right?
GODLIKE. awesome danne
New version:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_presets_2018Dec03.EOSM202.zip
commit:
https://bitbucket.org/Dannephoto/magic-lantern/branch/crop_rec_4k_mlv_snd_isogain_1x3_presets
(https://i.postimg.cc/L8d9vdzb/VRAM0-PPM-500px.png)
Can now read what registers being set in raw.c so exception for 10bit and eosm quirks is no t a problem anymore. Means that this build will work just as any eosm build(mv720p mode and so on) but with the extra features in Crop mode menu.
Awesome, Danne! Thank you so much for this!
Edit: I din't manage to get the CROP MODEs to work, but I only played around with it for 15 minutes. Will try more as soon as possible.
Does this build break any of the other platforms?
It would be great if we can get all the great work being done being done recently on the EOSM, 100D and 700D into merged into the experimental branches of the main repository. Then maybe see if some new resolutions can be found for the 6D and 650D as well.
is there any way to get the "framing" liveview work on an external display? whatever i choose for preview, it's showing "realtime" for hdmi external. by the way, i searched but i couldn't really get 1x3 crop mode, it shows at liveview and records very wide. i can provide footage does it need to be dng or are compressed formats okay? (i'm using mlv app on windows and i'm really grateful to both firmware and software developers.)
Quote from: Danne on November 27, 2018, 05:50:39 PM
Hell yeah @dfort.
No footage yet but hopefully some of the downloaders could provide. There's a focus pixel map for the mv1080p setting already? Only one needed for 1x3 right?
Danne,
First, thank you again your hard work!!!
And can you explain what you need to the focus pixel map for new fw?
One file recorded with 1x3 setting showing focus pixels. Might be hard to find them. You can load the file in Mlv App and uncheck all focus pixel fixing function and look.
Quote from: Danne on November 30, 2018, 08:29:43 AM
One file recorded with 1x3 setting showing focus pixels. Might be hard to find them. You can load the file in Mlv App and uncheck all focus pixel fixing function and look.
Danne,
here is the file:
https://we.tl/t-t1OpChmFaN (https://we.tl/t-t1OpChmFaN)
something I do not understand, the file is what i upload is 696px height and the focus pixels showing. on/off the eos m changed the height to 1120px and the focus pixels not showing... hmmm which setting is wrong?
Interesting, MLV App is changing the height with the focus pixel fixing on/off?
I tried it with the current version of MLV App and didn't experience that. Here is your file with the focus pixels removed:
(https://farm5.staticflickr.com/4810/45393551804_4c12bdde6d.jpg) (https://flic.kr/p/2cagPsU)
And without fixing the focus pixels:
(https://farm5.staticflickr.com/4817/44301077200_054d151e30.jpg) (https://flic.kr/p/2auJAPS)
I obviously stretched the colors to make the focus pixels more obvious.
I've seen height changes because of the "Default Scale" tag in the exported DNG file. The Default Scale tag is useful when shooting mv720 (5x3 sampling) though not all graphics applications honor that tag. Your sample file exported as DNG in MLV App and mlv_dump show different Default Scale values:
Software : MLV_DUMP CDNG
Default Scale : 1 1.666666667
Reel Name : M30-0960_.MLV
Image Size : 1736x696
Software : MLV App
Default Scale : 1 1
Reel Name : M30-0960_
Image Size : 1736x696
This means that the DNG files with the 1 1.666666667 Default Scale tag will be stretched vertically, depending on the app used.
Interesting that mlv_dump keeps the filename extension in the "Reel Name" tag while MLV App drops it. (Used exiftool to look at the tags.)
Your file appears to be shot with the crop_rec module using 3x3 sampling so the correct Default Scale should be "1 1":
mlv_dump -v
raw_capture_info:
sensor res 5184x3456
sensor crop 1.62 (APS-C)
sampling 3x3 (read 1 line, skip 2, bin 3 columns)
I'm not sure if mlv_dump needs a "fix" for this or if the problem is in the MLV file because the crop_rec module is using the mv720 raw buffer but modifying it with 3x3 sampling in place of the default 5x3 sampling. It should probably be fixed though it is easy enough to rescale the height in post for now.
The the new crop_rec module resolutions are a relatively new development and mlv_dump (crop_rec_4k version, a.k.a. mlv_dump on steroids) doesn't handle these focus pixels yet:
(https://farm5.staticflickr.com/4875/31178477277_29fd92c8c1.jpg) (https://flic.kr/p/Pv8R44)
Just for fun, here's the same frame using MLV App with the correct aspect ratio and focus pixel fix turned off:
(https://farm5.staticflickr.com/4805/45393788624_346e9b2a70.jpg) (https://flic.kr/p/2cai2S1)
In this case the DNG files were converted with Adobe Camera Raw and manipulated to get the focus pixels to show up clearly.
No, the MLV App is working ok, not change the height. I thing upload wrong file yesterday (non-crop).
https://we.tl/t-lzgOVocvSr (https://we.tl/t-lzgOVocvSr) crop mode is: 1x3_1736x1120, but I don't see the focus pixels...
my mlv app is showing the video correct and then outputting it squashed too tall not wide. i had to stretch it out in final cut. like it was anamorphic footage. looks great lots of detail. very good quality this 1x3 footage. I'm doing 1120x1120 which looks like 2:66:1 aspect ratio very nice. i use chroma smoothing 2x2 to get rid of focus pixels
1x3 mode is supposed to be used in regular mv1080p mode, not in x3 zoom which already can do 1:1.
For version 203 of firmware:
https://bitbucket.org/ccritix/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_presets_2018Dec01.EOSM203.zip
No focus pixels -- Yay! Got a similar sample from the 100D and it does show focus pixels so maybe you just got "lucky" and shot a lighting situation that doesn't show the focus pixels. This is actually happens quite a bit and makes hunting down all of the possible focus pixels a challenge.
Found some interesting stuff with these 1x3 sample. I'm a little lost as far as figuring out which app is doing the "correct" thing because there is nothing to guide us in this image. I guess you can say that there's no image in this image.
mlv_dump -v
Res: 1736x1120
...
raw_capture_info:
sensor res 5184x3456
sensor crop 1.62 (APS-C)
sampling 1x3 (read every line, bin 3 columns)
Note that the sensor resolution is 5184 pixels wide but the sampling bins every 3 columns so the maximum width should logically be 5184/3 = 1728. Well, there's an area that normally gets cropped so the sensor resolution is actually a bit more -- 5208.
Another thing to watch out for is that while resolution is written as width by height, the sampling is written as height by width. We had a conversation about this on another topic:
Quote from: dfort on September 15, 2018, 07:15:52 PM
Quote from: a1ex on September 15, 2018, 05:41:10 PM
I was used to Octave notation (line/column) when writing the binning notation (5x3 etc), but relating these to resolution seems more logical; too late to swap them?
Probably not necessary. Besides, it makes the "desqueezing factor" super easy to figure out -- 5/3 = 1.67x
So, for 1x3 sampling the "desqueezing factor" should be 1/3 = 0.3333...
Let's see what some of the MLV apps are doing with 1x3 footage when exporting to DNG.
mlv_dumpSoftware : MLV_DUMP CDNG
Default Scale : 1 1
Reel Name : M01-0745.MLV
Image Size : 1736x1120
dcraw -T (1736 × 1120)
(https://farm5.staticflickr.com/4896/31191269397_54ccaeffd7.jpg) (https://flic.kr/p/PwgpGR)
Adobe Camera Raw (1736 × 1120)
(https://farm5.staticflickr.com/4917/45406521084_ab1361f226.jpg) (https://flic.kr/p/2cbqhMb)
Not that exciting yet. There's a difference between the way ACR and dcraw rendered the DNG file but that's expected.
MLVFSI recently updated my Mac to Mojave and it wasn't working when I was checking out that previous file. After updating osxfuse to 3.8.2 it is working again.
Software : MLVFS
Default Scale : 1 1
Reel Name : /M01-0745.MLV
Image Size : 1736x1120
dcraw -T (1736 × 1120)
(https://farm5.staticflickr.com/4878/31191266627_a2bbd5657a.jpg) (https://flic.kr/p/PwgoT6)
Adobe Camera Raw (1736 × 1120)
(https://farm5.staticflickr.com/4840/45406519014_a4eb2fee56.jpg) (https://flic.kr/p/2cbqhau)
No surprises there.
MLV AppSoftware : MLV App
Default Scale : 1 0.3333333333
Reel Name : M01-0745
Image Size : 1736x1120
It makes sense that MLV App shows the correct Default Scale because some of the developers working on this app are also experimenting with the new crop_rec resolutions. This app also allows you to save to various types of image files so you don't have to create DNG files to work with. Let's export a tiff file from MLV App
MLV App (1736 × 373)
(https://farm5.staticflickr.com/4823/46080964612_db02aed693.jpg) (https://flic.kr/p/2dd1ZkS)
Let's take a DNG file exported from MLV App and run it through dcraw and ACR.
dcraw -T (5208 × 1120)
(https://farm5.staticflickr.com/4863/31191276607_b15a1454d9.jpg) (https://flic.kr/p/PwgrRa)
What's up with that file size? Instead of reducing the height dcraw increased the width to get the correct aspect ratio.
Adobe Camera Raw (1736 × 373)
(https://farm5.staticflickr.com/4808/45406525734_1f4946fa7c.jpg) (https://flic.kr/p/2cbqjam)
Cool findings dfort
What are everyone's thoughts on updating the EOSM to 2.0.3? The original pull request has been up for nearly two years. Recently @critix and I have been running tests on it and it is as stable as 2.0.2. I can do it on some of the experimental builds to get started--provided @a1ex approves.
Quote from: Danne on December 01, 2018, 05:55:07 PM
Cool findings dfort
Indeed cool findings! :)
Quote from: dfort on December 02, 2018, 09:07:12 PM
What are everyone's thoughts on updating the EOSM to 2.0.3? The original pull request has been up for nearly two years. Recently @critix and I have been running tests on it and it is as stable as 2.0.2. I can do it on some of the experimental builds to get started--provided @a1ex approves.
Sounds good. I'm all for this plan. In fact, I've wanting to get my hands dirty again w you guys sooner rather than later.
How can I release shutter buttom when I. Use a sigma 56 lens?
Quote from: liuk718 on February 03, 2021, 06:30:24 AM
How can I release shutter buttom when I. Use a sigma 56 lens?
In the Canon menu, go to the "4th wrench" and enter the " Custom Functions" menu, setting #7 -- "Release shutter w/o lens," and select "1:Enable." (https://youtu.be/CSoyTf4A45U&t=24)
Quote from: tupp on February 03, 2021, 07:26:18 AM
In the Canon menu, go to the "4th wrench" and enter the " Custom Functions" menu, setting #7 -- "Release shutter w/o lens," and select "1:Enable." (https://youtu.be/CSoyTf4A45U&t=24)
Thanks dude,i knew this settings for manual lens. sigma 56 ef-m lens is a fully auto lens,i can take a photo when i was using sigma 17-70 ef old lens. but this time if i press and relase shutter bottum ,it seems try to pre foucus onece and do nothing.
If i uninstall ML,it will take a photo and no false.
Quote from: liuk718 on February 03, 2021, 04:17:45 PM
Thanks dude,i knew this settings for manual lens. sigma 56 ef-m lens is a fully auto lens,i can take a photo when i was using sigma 17-70 ef old lens. but this time if i press and relase shutter bottum ,it seems try to pre foucus onece and do nothing.
If i uninstall ML,it will take a photo and no false.
Well, if your lens is automatic, you could be experiencing the ML EOSM "shutter bug."
You might try partially unmounting the lens. Also, I seem to recall that certain SD cards prevent the shutter bug.
This works :-) :D
Hi every one, can somebody tell is it possible in future to make a proper real time framing in crop modes? and also is it possible to make reviewing the mlv files more smothly in file manager in camera?
Smoothness: Unlikely. There isn't enough processor power inside.
Quote from: ctfire on February 27, 2021, 04:28:49 PM
Hi every one, can somebody tell is it possible in future to make a proper real time framing in crop modes? and also is it possible to make reviewing the mlv files more smothly in file manager in camera?
Smoothly, as said above, nope... but you can change to exact and fast, then you'll get a B&W preview almost in real time playback (20~24fps) in-camera
has this thread moved?
No, this thread has not been moved. If you are looking for discussion about Danne's builds: This has been splitted and moved to https://www.magiclantern.fm/forum/index.php?board=66.0
Quote from: dfort on December 02, 2018, 09:07:12 PM
What are everyone's thoughts on updating the EOSM to 2.0.3? The original pull request has been up for nearly two years. Recently @critix and I have been running tests on it and it is as stable as 2.0.2. I can do it on some of the experimental builds to get started--provided @a1ex approves.
I have firmware 2.0.3 on my camera. Does ML work ?
EDIT: Couldn't find the experimental version for 2.0.3 so I've downgraded th camera to 2.0.2 and loaded ML.
Hola tengo la EOS M6 Mark II ¿Sabéis si hay algo para cambiar el formato de grabación , quiero grabar a 3840X1645
Offtopic. This thread is about "EOS M" only. There is no ML for M6 Mark II.
:)
I have an annoying problem with my trusted EOSM
I am setting up a budget friendly streaming studio using available canon cameras (5D mk2, 5D mk3 and EOS-M) and a Black magic Atem mini Pro as video-mixer and capture card.
I scale up the HDMI output of the cameras by 120% to get around the lack of clean 16:9 HDMI output from the 5Dmk2 and the EOS-M.
Everything works fine with the 5Dmk2/5Dmk3 but the EOS gets "stuck" when I use the ML "sticky-shutter" function to get around the 30min limit. I can activave the sticky shutter but I seem unable to deactivate it without turning off the camera (no battery pull needed)
I am running FW202 and I have tried several different builds to no avail.
Any thoughs on this particular issue?
Thanks
https://wiki.magiclantern.fm/faq#how_do_i_record_stream_for_more_than_30_minutes
Quote from: Walter Schulz on August 25, 2021, 05:43:22 AM
https://wiki.magiclantern.fm/faq#how_do_i_record_stream_for_more_than_30_minutes
Thank you my friend. As usual, you provide quick and on the point answer :)
I will try the "lua-fix" solution.
Do you have a simple explanation for why the sticky shutter is behaving differently on the EOS compared to the 5D mk2?
On the MK2, I can use the shutter to go in and out of sticky shutter-mode without any hickups.
This is really nice as it gives me a super easy and reliable way of switching between "settings-mode" and "live-mode" :)
IMO "Sticky Half-Shutter" was a dirty workaround and notorious for side-effects like yours.
Hey guys, here are some footage I shotted with ML on a FPV drone
https://www.youtube.com/watch?v=90RjjqLTpAY
https://www.youtube.com/watch?v=GDtRnf7LYuA
I have scoured the web and searched this forum a lot but I still haven't arrived at a clear answer yet about EOS M HDMI output quality.
The raw modes seem excellent for internal recording but how bad/good is the EOS M HDMI output at 576p (recent build with registers for more hdmi output options) or 1080i? Is it useable for live streaming? I read that moire and alaising is worse in live view?
Have seen some YouTube videos showing other Digic 5 cameras and I guess I am expecting it to be similar? A Sony A6000 definitely seems to blow it out of the water as far as HDMI output but only 8-bit 4:2:0 internal recording I think.
My last ML camera was a T3i probably a decade ago.
ATM (almost) all ML supported cams do pretty much the same: 1620x1080 in photo mode and 1620x912 in video mode embedded in 1080i60 with 8 bit.
Hey guys I am a canon 700D shooter. I was curious as what are you guys able to shoot in regards to non crop since we both share the same sensor? Is the absolute best non cropped option is 1736x736 14 bit losseless 1x3 binning?
https://docs.google.com/spreadsheets/d/16cgnRivbUv7nA9PUlCLmLdir3gXdIN3pqzCNAAybepc/edit#gid=5 -> Column H
Quote from: Walter Schulz on November 06, 2021, 11:06:48 PM
https://docs.google.com/spreadsheets/d/16cgnRivbUv7nA9PUlCLmLdir3gXdIN3pqzCNAAybepc/edit#gid=5 -> Column H
They are basically the same
Except for the fact that you can put speedboosters on eos m but not 700d
I would like to ask if any devs are around about possible future developments on certain areas. Mainly if getting wysiwyg or 1:1 framed real time preview for Eos M 2.5/2.8K modes (more than 1920x1080) is something that might ever be worked on (or even possible). I noticed that after fixing of monitoring M has become such a good option for narrative filmmaking and the only thing that Im struggling with is the occasional softness and lack of resolution. 2K mode with frtp is nice, but those couple of hundred extra pixels that could be gotten from 2.5/2.8, would at least for me, give a needed "level up" (atm. I can get 2288x1288 stable recordings which is good enough for almost everything). I need to focus pull people, so monitoring and rtp is a must. I can work with current 2.5k regular mode (turn monitor off, check the framing from cameras live view, put the monitor back on), but having it as a standard feature obviously would make life much easier (not having to guess/remember the framing that is).
Also on 5K Anamorphic the lack of 25fps is making it no-go for me. Since new debayering in MLVapp are making 1080p great option again this is less of an issue.
Now I'm eternally grateful for what i already have, the thing is already awesome. So please, don't take any of this as me expecting to be served nor me being dissapointed if I never see these options. I am mainly thinking if I could skip the whole Black magic / GH5 midrange all together and stick with M a bit longer, so in an odd chance that these are in the works or in plans, it would be nice to hear about it.
Folks I've just dug out my EOS M after letting it gather dust for a for a year or two. In the past I've mainly experimented with Super 8 simulation e.g.:
https://vimeo.com/345342123
Now I'd like to try using the whole sensor (i.e. 1.6x crop or as close as possible) - what is currently the most stable build that gets decent results? Sorry if it's cheeky not to trawl the thread for answers but I'd like to know if there's a consensus. 1080p is fine - I'm more concerned about aliasing but I've generally found the diffusion filter helps deal with that anyway. Most of all I'd like to avoid dropped frames and be able to get a decent idea of what I'm filming with live preview. Thanks for any advice ...
for 8mm or 16mm emulation use 1440*1080 in crop mode and cctv lenses for this.
i use lenses for 1/2' sensors , super 8 will get you vignette so you would have to crop to maybe 800*600, notnsure.
1/2' covers about the same as 16mm film lenses.
this will get you moire free footage
overall best quality is 2800*1080 or something similar ( ita almost 3k!!) i use it and 2500*something(2.5k).
some cctv lenses dont covee 2800 or 2500 so i use 2400*1400 (16:9).
also upscale when rendering, it will retain more details.
Quote from: 2blackbar on November 19, 2021, 12:55:17 AM
for 8mm or 16mm emulation use 1440*1080 in crop mode and cctv lenses for this.
i use lenses for 1/2' sensors , super 8 will get you vignette so you would have to crop to maybe 800*600, notnsure.
1/2' covers about the same as 16mm film lenses.
this will get you moire free footage
overall best quality is 2800*1080 or something similar ( ita almost 3k!!) i use it and 2500*something(2.5k).
some cctv lenses dont covee 2800 or 2500 so i use 2400*1400 (16:9).
also upscale when rendering, it will retain more details.
Thanks but I'm really only looking for the best full-width build. I will use a 35mm lens that covers the whole APS-C sensor.
https://www.magiclantern.fm/forum/index.php?topic=25781.0
Anamorphic mode.
Quote from: Danne on November 19, 2021, 01:41:55 PM
https://www.magiclantern.fm/forum/index.php?topic=25781.0
Anamorphic mode.
Nice, thanks very much I shall give it a spin. Assume this is just anamorphic in terms of the aspect ratio - not requiring desqueeze or an actual anamorphic lens?
Exactly. Record per usual and then scaling back correctly will happen automated if opening mlv files in Mlv app or dng files through adobe camera raw.
why there are no working features with focus like focus stacking or focus trap ?
So I got ahold of an EOS M for a great deal, and I've been playing around with the various raw modes the past day or so. I've got a couple questions that I can't seem to nail down definitive answers on.
- Is there a post that lists all the crop factors of the various raw modes in the latest Danne builds? I can find mentions of the crop factors in various videos and blog posts but nothing that just plainly says "x mode has y crop factor, etc..."
- I've noticed that the 2.5k FRTP doesn't show the entire frame being captured. When shooting at 2.35:1 The right ~1/5 of the frame is black unless I enter "crop preview" with the INFO button. Is that correct behavior?
- Along with the previous question - is there a way to hide the garbage data on the LCD when shooting in 2.5K FRTP? I'm referring to the noise/bad data/previous frames that show up below the live view on the screen. 5K anamorphic FRTP seems to auto-overlay a crop mask of some kind to fix this issue, so I'd think something similar for 2.5K would be easy.
Hoping to replace my 650D with this camera (technically it's smaller cousin I suppose) so I'd love to learn as much as I can about all the new modes that have been added since my last adventure with ML nearly 5 years ago.
1. Crop factors should be calculated individally for the setting you use. A list would not really help here. EOSM has 5208 pixels in width.
crop = sensor width / (footage width * readout factor)
The readout factor can be 3 or 1 in dependency to the preset you use: 3 for 3x3 and 1x3 readout modes, 1 for 1x1 crop modes.
2. This mode is not ready yet, but the devs wanted to give the offer to use a realtime preview for this crop mode. So far this is correct as is, until someone finds better code. https://www.magiclantern.fm/forum/index.php?topic=25784.msg231212#msg231212
3. Same here, but you could use cropmarks to hide this area. Or you use the screen layout "Bottom, under 3:2" in Display->Advanced settings.
Quote from: Pekka on November 10, 2021, 05:31:18 PM
I would like to ask if any devs are around about possible future developments on certain areas.
You should ask questions related to Danne's builds for EOS M in this thread: https://www.magiclantern.fm/forum/index.php?topic=25781.3050
Is there a "quick delete" option for the last recorded file ?
need to frequently & quickly delete the last recording (to save on card space).
This is for capturing live action.
I think I did something very stupid...
I had a spare EOS M that I wanted to sell, so I wanted to remove ML. In order to do so: I downloaded the 2.0.3 firmware and installed it on the camera. Then I got a message on the screen (from ML) saying: model detection error. Your camera doesn't look like a EOSM 2.0.2. (no shit).
What you can do:
- Make sure you've got the right ML zip for you camera model.
- If in doubt, upgrade (or downgrade) your Canon firmware to 2.0.2 (again).
- To use your camera without ML, format this card from your computer.
You may remove your battery.
So I formatted my card on my computer (cause I wanted to use it without ML), inserted it again, then: nothing. Just a continuing blinking green light.
I tried putting the 2.0.2 firmware on my card, but there's no way to install it now... Just a black screen with a blinking light...
Does anyone have any ideas on how I can fix this?
Remove battery.
Use EOScard (Windows) or Make_bootable.sh (macOS/Linux) to create a bootable card.
Copy extracted ML build for firmware 2.0.3 to card.
https://web.archive.org/web/20200622002229/https://bitbucket.org/daniel_fort/magic-lantern/downloads/magiclantern-Nightly.2017Jan13.EOSM203.zip
Insert card, insert battery, close compartment doors and follow instructions found in wiki.magiclantern.fm/faq to deinstall ML from camera: "To remove the bootflag, run Firmware Update from a ML card and follow the instructions."
Quote from: Walter Schulz on February 17, 2022, 04:50:02 PM
Remove battery.
Use EOScard (Windows) or Make_bootable.sh (macOS/Linux) to create a bootable card.
Copy extracted ML build for firmware 2.0.3 to card.
https://web.archive.org/web/20200622002229/https://bitbucket.org/daniel_fort/magic-lantern/downloads/magiclantern-Nightly.2017Jan13.EOSM203.zip
Insert card, insert battery, close compartment doors and follow instructions found in wiki.magiclantern.fm/faq to deinstall ML from camera: "To remove the bootflag, run Firmware Update from a ML card and follow the instructions."
Thank you Walter, I was able to fix it!
Here is the latest ML version M1 2.0.2 backup from my pc, if anyone needs this:
[Walter Schulz: Link removed. Requires account, unknown content, description unclear. Intention unclear.]
For rolling shutter.
would it be possible to have the sensor read sideways? this way there would be rolling shutter up and down but not side to side.
Nope.
It's more likely that you could capture a "portrait" aspect ratio, and rotate the camera 90 degrees, for the same effect.
Could you then change the aspect ratio? So it would be 1080 x 1920
Hi. I currently have eosm1 and no to little scripting experience. What can I do to contribute? Maybe run some tests? I'm using ML for a bit now, primarly for taking photos. Using WB (auto and manual), exp sim, thats great futures, thank you guys for doing this.
Hey guys!
Feel free to check out my first eos m footage from Malta. I struggled a lot with finding focus in bright sunlight as you can tell. I'm not really satisfied with the final results, I made several mistakes. I couldn't manage to turn IS on the whole time, so I had to stabilize it in Davinvci, thats why it is falling apart in some shots. I also noticed that in 5k frtp mode the AF focuses at the center of the screen and not the center of liveview.
I'd like to ask some advice from you guys with the following;
- any idea why I can't turn IS on?
- can I use AF+MF somehow when recording video?
- why does the black crop jumping up and down after stabilization?
https://www.youtube.com/watch?v=UfkWp_SfY30
Hello friends, I have the Eos M6 Mark II, do you know if there is any magic flashlight for it?
AFAIK nobody is working on it.
Ask again in spring 2023 or begin to learn how to develop ML.
Public warning: One more crosspost/spam -> Banned!
I can no longer use 3x crop mode with a external HDMI monitor, or with a HDMI capture card. This has been an issue for the past 2-3 builds. I had another SD card with the older Jun26_2021 build and I can get 3x crop to work with that, but I can't get the other improved modes like the 2.4k continuous frtp, or 48fps mode which I love in the latest build! I have been using 3x crop for a while with specific C-Mount lenses that i have, it comes in handy and looks great! Please fix!
Has anyone notice that MLV files ignores the gain settings in canon audio menu? I recorded some clips at a concert saturday night and adjusted the gain in the canon menu, my .h264 files have the correct volume, but the raw videos I shot are all distorted.
Hi guys.
Can anyone give me some tutorial how to make custom cropmark?
Quote from: kolodiazniy on September 28, 2022, 09:50:46 PM
Can anyone give me some tutorial how to make custom cropmark?
https://magiclantern.fandom.com/wiki/Cropmarks
Needs a serious makeover but it is the best we have now.
Photoshop worked for me. No luck in GIMP yet.
Quote from: mothy on August 23, 2022, 06:47:03 PM
I can no longer use 3x crop mode with a external HDMI monitor, or with a HDMI capture card. This has been an issue for the past 2-3 builds. I had another SD card with the older Jun26_2021 build...
Are using custom build from Danne?
If your issue is still present, report in the following section:
Danne's crop_rec_4k experiments for EOS M (https://www.magiclantern.fm/forum/index.php?topic=25781.msg208959#msg208959)
Quote from: Walter Schulz on September 28, 2022, 10:06:29 PM
... it is the best we have now.
Your tutorial containce wrong link. The conversion file can not be downloaded.
Please post dead link(s).
I found two:
https://bitbucket.org/hudson/magic-lantern/raw/03b264ac8e16/convertrle.rb
http://www.sawomedia.de/magiclantern/cropmarks/
https://web.archive.org/web/20151231031309/https://bitbucket.org/hudson/magic-lantern/raw/03b264ac8e16/convertrle.rb
https://web.archive.org/web/20140706110334/http://www.sawomedia.de/magiclantern/cropmarks/
Can someone explain me
the difference in setting up aspect ratio
in "Movie" main menu and in "raw video" submenu?
"Aspect ratio" in "Movie" menu? Snapshot please!
You mean a screenshot?
I don't know how to make it. Is the ML has such function?
You can use another camera or a smartphone and you can use ML's screenshot feature: https://wiki.magiclantern.fm/camera_help#screenshot_-_10_s
Thanks for your support!
Native screenshot function is much more usable.
(https://i.imgur.com/Q0b960L.png)
Customized to work optimal for each preset in this specific ml build.
You mean another builds hasn't this item?
Depends on build.
See lua_fix for EOS M:
(https://abload.de/img/vram0jeiaj.png)
(https://i.imgur.com/6lS4psA.png)
Please use https://www.magiclantern.fm/forum/index.php?topic=25781.msg240684;topicseen#msg240684 for issues with Danne's crop_rec_4k build.
Can someone explain me what is "lua"?
Top of page -> Downloads -> Downloads (drop down list) -> Experiments.
In short:
lua_fix build is recommended build for general purpose shooters not aiming at highest resolutions/data rates for raw/MLV recording.
And Lua iitself is a programming language implemented in ML and used to run scripts. See https://www.magiclantern.fm/forum/index.php?topic=14828.0
What kind of "scripts"?
https://www.magiclantern.fm/forum/index.php?board=53.0
Is there some way to remove unusable presets?
iso 10
is it possible to get a lower iso?
this way we don't need a nd filter.
Hello,
I'm a little bit worried: what is the last working built for M-Firmware 2.0.3 and where to find it?
Reason:
I use "M" with firmware 2.0.3 - suddenly focus peaking does not work anymore, no dots appear. Reset on all settings proceeded. Restarted camera. No positive effects. Use standard settings. What is to do? Perhaps new ML-version?
Kind regards
Joerg
More likely a misconfiguration. Access Prefs tab -> Config options/files -> Restore ML defaults
Restart and retry.
ok,
resetted, activated focus peaking (no other mod's), nothing. Did the same with my 50D - works perfectly.
Version is Nightly.2017.Jan13.EOSM203.
Joerg
Retry with lua_fix build from experimental build page.
:-[ there are no further builts for M 2.0.3 ... I do not unterstand why it worked in the past and now does not. With no changes.
Some spooky behaviour came up: In the ML - menu suddenly the exposure-correction bar appears for some seconds (+/- setting), disappears and comes back, covering the ML menu. Think I remove and make a new SD - then try again. If it will not work again - downgrade to 2.0.2 and use Version for 2.0.2 which is newer, 2.0.3 seems to be a dead end.
For users with similar problem: FIX
1. deinstall ML from camera -> process via Canon firmware-update, waiting, ML removes itself, resets bootflag;
2. change nothing - start the camera, have a look if everything works as it should. Then:
3. start firmware update again, ML installs again.
fine. As it seems this was a camera-internal problem or a problem with the sd-card. I changed the card after steps 1-3 to a new one. Perhaps it has been damaged by age or some other influence (reading out outside the camera or other)
So everything is fine. 8)
Quote from: lightspeed on March 20, 2022, 01:42:44 AM
For rolling shutter.
would it be possible to have the sensor read sideways? this way there would be rolling shutter up and down but not side to side.
If you want to eliminate Rolling shutter artefacts you could take your footage into "Gyroflow" (free stabilisation software) and put in the exact rolling shutter values (can be found in FPS override tab) and it can fix rolling shutter effect. You will also need some kind of gyrologger to make this work, but if it's what you really need it does work (I've done it myself).
Long time, no chat, friends!
Today I experimented a little with a "Kingston Canvas Select Plus" 32 GB HC1 card in the EOS M, and was very surprised - it worked well at 2 x normal data rate, i.e. around 86 Mbps. It looked like the camera buffer never exceeded 30% during short takes (didn't shoot any long ones), so would this be safe to use, or would it overheat camera and/or card?
At 2.4 x rate, slightly over 100 Mbps, the buffer filled up quite fast, and recording stopped after less than 10 seconds. But I wonder - is the EOS M even supposed to work at such speeds? :o
I also tried lower bit rates, and found that even 0.4 or 0.5 gives enough quality for recordings that will be uploaded to YouTube - which will degrade the image regardless of original quality...
BTW: Did I ever post a link to a 30-minute documentary I shot with two EOS M cameras for Finnish TV? The subject is hot air ballooning - can I put the YT link here if there is any interest? ;)
The build you are using is?
Are you talking about H.264/MOV recording?
Mbps may be misleading. Please use MByte/s or MBit/s.
Native write speed for EOS M is around 41 MByte/s in benchmark and around 38 MByte/s for recording.
Overclocked modes can do around 80 MByte/s recording with compatible cards. Until now we only have reports about Kingston Canvas being incompatible.
Subforum for linking videos: https://www.magiclantern.fm/forum/index.php?board=19.0
I'm using the "latest build 2018-07-02" for the EOS M - are there any newer? If so, I haven't found them, despite searching...
Yes, I'm recording H.264/MOV, and I meant Mbit/s - that's what QuickTime reports when I look at the files.
QT reports a bitrate for "default" MOV video around 45 Mbit/s - that's what has confused me, since "native speed", as you say, is 41 MByte/s - those numbers are too close for comfort, even though one is 8x the other.... :-\
But 2x normal bitrate means only about 11 MBytes/s - well within both camera and card specs.
"Kingston Canvas being incompatible" - just with overclocking, I assume?
I've never gone into RAW (would hamper my workflow too much), but I use ML for the 3x zoom feature, enabling me to use a plethora of C-mount lenses I have, including a Canon 7.5 - 97.5 mm, 13 x zoom... :D
Hi,
two years ago, i thought that limit of my EOS M have been reached. Today I see how wrong i was :o
Unfortunately, my Sandisk Extreme Pro 32GB 95MB/s doesn't work at 240 MHz, so I've been scanning forum for the list of compatible cards, but it seemed like mixed bag even with newer Extreme Pro cards (i've seen theBilalFakhouri's thread)and now i see this
Quote from: Walter Schulz on February 05, 2023, 10:52:08 AM
Native write speed for EOS M is around 41 MByte/s in benchmark and around 38 MByte/s for recording.
Overclocked modes can do around 80 MByte/s recording with compatible cards. Until now we only have reports about Kingston Canvas being incompatible.
did i missed some post/thread with compatible/tested cards? Or every card with UHS-1 90MB/s write speed should work?
It can work. Enter the submenu of where you select Mhz and choose the alternate patch routine.
Sorry, i din't made myself very clear.
My old card still works, 38 MB/s default, 58 MB/s at 160 MHz, anything higher drops to 20 MB/s.
So my question would be, what card should i buy to join the party and make it work at 240 MHz?
Yes but could work with 240 if patched with the other routine.
It took me while to figure out what "the other routine" means ???
You were right, with SDR50 it works at 240 MHz @ 73MB/s :D
Thank you.
Nice. Good you figured it out. Can't keep track of all terminology all the time 8).
Canon 13x zoom, 7.5 - 97.5 mm, f 1.4
I mentioned this lens in a post long, long ago, but I have significantly improved its performance since then, Using the ML 3x crop feature.
Here's a still photo of the lens mounted on the EOS M:
(https://i.ibb.co/VmryB34/Canon-13x-zoom.jpg)
Note the dark grey tube behind lens & camera, it contains the secret of the improvement!
Detailed explanation in the "Share Your Videos" thread: https://www.magiclantern.fm/forum/index.php?topic=26787.msg242174#msg242174
Quote from: Janke on February 09, 2023, 11:43:59 AM
Canon 13x zoom, 7.5 - 97.5 mm, f 1.4
I mentioned this lens in a post long, long ago, but I have significantly improved its performance since then, Using the ML 3x crop feature.
Here's a still photo of the lens mounted on the EOS M (in a YouTube container, AFAIK you can't attach photos in this forum?):
https://i9.ytimg.com/vi_webp/qJvnPw7obzo/mq2.webp?sqp=CNifk58G-oaymwEmCMACELQB8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGFQgYShlMA8=&rs=AOn4CLBPE4loQx6-eQEjlBxo23QiZeN9Dw
Note the dark grey tube behind lens & camera, it contains the secret of the improvement!
Detailed explanation in the "Share Your Videos" thread: https://www.magiclantern.fm/forum/index.php?topic=26787.msg242174#msg242174
you can try using this https://imgbb.com/ (https://imgbb.com/) then paste code generated to post, usually I use bbcode full to attach photo
Thanks, ML700D and Walter! I didn't know the correct tag, apparently IMG need to be in captions and/or the /description is necessary? (Me being a geezer noob... ;) )
I have another optical project ongoing, too, a relay-lens system for a "periscope lens" using a 1.7 mm fisheye lens for GoPro-type cameras. Here, too, ML's 3x function enables full-frame video from that tiny lens.
However, it necessitates quite an optical construction, here assembled on a piece of angle iron, working as an "optical bench":
(https://i.ibb.co/hDGXJwq/Relay1.jpg) (https://ibb.co/FgQsLCP)
(https://i.ibb.co/VVQVr7k/Relay2.jpg) (https://ibb.co/6Y1YV3q)
Explanation: Furthest from the camera, at left, is the 1.7 mm fisheye lens, diameter only 22 mm (7/8"), then a 20 mm Bolex 8mm projector lens that focuses the image from the fisheye toward the relay lens, which is from a laser copier. Then follows an objective lens from a small binocular, which collimates the light toward the actual camera lens, which is the rear part of a C-mount video "pinhole" lens. The pink rings are just holders for the components, all turned to 22 mm diameter. The angle iron is attached to the camera lens with masking tape - simple, but workable for this test!
Since all the optical components are achromats, the chromatic aberrations should be minimal. There is quite a bit of spherical aberration, though. I already know that the edge sharpness won't be perfect, but the intended use is for closeups of flowers and insects, still showing a relatively in-focus background. A 1.7 mm lens has an incredible depth-of-field (2" to infinity) even fully open - which in this case is around 5.6 to 8 due to all the optical components.
I'll post a video when I get the project finished - I will yet have to make a system of threaded tubes (total length about 250 mm, 10") in order to do a final assembly - thanks to my hobby lathe, that should not be too difficult a project...
Demo video here: https://www.magiclantern.fm/forum/index.php?topic=26804.msg242418#msg242418
So cool. I want one!
You can buy one - it's "only" US$ 2,299.00 :
https://www.venuslens.net/product/laowa-24mm-t14-2x-periprobe/
Mine will not be as good, but a few f-stops faster, and much wider... 8) ... and cost me zilch!
Here's the very first movie test on the "optical bench" - mid-take, I'm actually almost touching the lens with my finger:
https://youtu.be/1Vud91Klwys
Hi, I'm new with Canon Eos M and ML. I've installed the latest build.
If I enter the movie mode I cannot see presets, custom modes, ratio, bitdepth...
My menu start with Bit Rate, Rec Key, Gradual exposure etc
I'm sorry if it's a stupid question but
Can you help me, please?
Tnx
It would really help to put a name and date to "latest" build.
Most likely you haven't installed Danne's custom build for EOS M. Start here: https://www.magiclantern.fm/forum/index.php?topic=25781.0
First test of the above mentioned "periscope lens" installed in aluminum tubes is now on "Share your videos", i.e. here:
https://www.magiclantern.fm/forum/index.php?topic=26804