Magic Lantern for the Canon EOS 600D/Rebel T3i
Magic Lantern User Interface animation (https://www.magiclantern.fm/)
- An overview of the user interface with Magic Lantern installed
- User controllable
Install Guide (https://wiki.magiclantern.fm/install)
- Step by step instructions to get Magic Lantern installed on your camera
- Includes troubleshooting and useful notes
600D/T3i build page (https://builds.magiclantern.fm/600D-102.html)
- Correct Canon firmware version to run Magic Lantern can be found here
- Lots of useful links and information
Feature matrix (https://builds.magiclantern.fm/features.html)
- List of Magic Lantern features that work on the 600D/T3i
- Link heaven
Frequently Asked Questions (https://wiki.magiclantern.fm/faq)
- Common questions regarding the Magic Lantern project
- If you have a question, check here first
User Manual (https://wiki.magiclantern.fm/camera_help)
- Needs work (https://www.magiclantern.fm/forum/index.php?topic=22275.msg202207#msg202207)
- In camera, in the Magic Lantern menus, all options have a short one or two line help text at the bottom of the display
General help
- Tutorials (https://www.magiclantern.fm/forum/index.php?board=15.0)
- Pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/915/update-to-600d103/diff) to port ML to 1.0.3 firmware. Discussion (https://www.magiclantern.fm/forum/index.php?topic=15360.msg199663#msg199663)
Original post
[size=14pt][u]Magic Lantern Installation & Updating Guide[/u][/size]
[u][size=12pt]for Canon EOS 600D/Rebel T3i[/size][/u]
This guide will help you install and update your Canon EOS 600D/Rebel T3i to the lastest Magic Lantern Nightly builds.
[size=8pt][color=red]Warning! Magic Lantern is not approved nor endorsed by Canon in any way, and using it will probably void your warranty. We are not responsible for any damages to your camera.[/color][/size]
[u][size=10pt]Before you start:[/size][/u]
- Make sure your battery is fully charged.
- Remove unnecessary accessories (battery grip/flash/etc).
- Have a sd card reader or laptop with integrated sd card reader.
- Use a sd card of 32GB or smaller for first install.
- Understand that you may lose your warranty and brick your camera.
[u][size=10pt]Updating Canon firmware:[/size][/u]
- Make sure you are running Canon firmware v1.0.2 before you install ML, if you are you may skip this step.
- If not, download it [url=http://pel.hu/down/eos600d-v102.zip]here[/url].
- Follow included instructions and update your camera.
[u][size=10pt]Magic Lantern Install:[/size][/u]
- Download the last nightly version [url=https://builds.magiclantern.fm/#/]here[/url]
- Format your SD card in camera first, then put it in your SD card reader connected to your PC.
- Unzip 'ML' directory, 'autoexec.bin' and 'ml-setup.fir' from the downloaded ZIP file onto your sd card.
- Put your sd card in your camera, switch camera to M-mode and power it up.
- Launch firmware update and install ML.
- After the green confirmation screen, turn off your camera.
- Power your camera back up and enjoy Magic Lantern!
[u][size=10pt]Updating Magic Lantern with new build in the future (on camera and sd card with ML installed):[/size][/u]
- When new nightly is available (see [url=https://builds.magiclantern.fm/#/]here[/url] for last build), download it onto your PC.
- Put your sd card (running the old build) into your PC and delete (NO format!) the 'ML' directory and 'autoexec.bin' file.
- Extract the content of the zip from the new build onto your sd card.
- Repeat this process for all sd card with old ML builds you want to update.
[u][size=10pt]Uninstalling Magic Lantern from SD card:[/size][/u]
- You cannot simply delete the files from the sd card to uninstall ML from it (as the boot flag will remain set).
- Format the SD card in the camera (select this option: Format card, remove Magic Lantern).
[u][size=10pt]Uninstalling Magic Lantern from camera:[/size][/u]
- You cannot simply reinstall the canon firmware to remove ML.
- With a ML sd card, launch the Firmware Update process and follow the instructions on-screen to uninstall ML.
[u][size=10pt]Boot without loading Magic Lantern:[/size][/u]
- If you want to boot your camera without ML, all you have to do is hold down the "SET" button while switching your camera "ON".
[u][size=10pt]Updated user Guide for ML nightly builds:[/size][/u]
- [url=http://magiclantern.fm/forum/index.php?topic=11269]User Guide[/url]
[img width=300]http://a1ex.magiclantern.fm/bleeding-edge/new-installer.png[/img]
Edit: Modified install procedure for new nightly and installer.
I'd also like to maintain this thread. I've been around the forum for almost 3 years now and my 600D is still ticking and still running Magic Lantern. So let's DO THIS THANG!
Quote from: rainless on June 16, 2015, 02:30:52 PM
I'd also like to maintain this thread. I've been around the forum for almost 3 years now and my 600D is still ticking and still running Magic Lantern. So let's DO THIS THANG!
Thanks :) Same here, using ML almost 3 years now, but only recently moved to the nightly builds. And glad I did, because the new builds are just so more stable and feature-rich.
Let's kick this camera support back to life and get the new nightly builds we all love 8)
Going to do some work with my build from last year and the new one I just downloaded from a month or two ago.
Looks like 600D has the updated installer. I've added some details to the OP and will leave for Avenger to make look pretty.
Quote from: Audionut on June 21, 2015, 12:59:46 AMLooks like 600D has the updated installer.
I don't think so. Latest nightly was built April, 19th and project is disabled. No FIR in zip.
Well it got a new installer. Not sure what's needed to get the builds kicking again.
edit: Perhaps this thread and some interest is enough. I don't recall the builds being disabled because of broken features.
Users may ask: Where is this new installer? If they are following your updated information installation will fail.
Users don't read OP's! ;)
I´m interested in the question, too: Why doesn´t exist an actual nightly build for the 600D?
In the download-section of ML-homeepage I can read:
"What are nightly builds?
- Nightly builds are binaries compiled from the latest source code, automatically, whenever there are any changes to the main branch (unified)."
At least since the new ML-Setup.fir-files, there are such changes, but no new nightly.
Walter, you wrote, the project ist disabled. Where did you read that? In my eyes, the 600D should be supported (with or without maintainer-thread).
I don´t need these nightlies, because I compile ML myself. I did so today with success, all went fine. But I would be interested in an answer.
Edgar
Compiling with default settings does not boot on 600D, that's why it's disabled.
https://bitbucket.org/hudson/magic-lantern/issue/2268/nightly-2804
Thanks Alex for the quick answer.
ML boots on my 600D with the sourcecode from today. I´m not sure, what you mean with "default settings". OK, I only compile few modules, I need (mlv_rec, mlv_play at the moment). And my makefile.user looks like that:
ARM_PATH=/home/edgar/Software/MagicLantern/gcc-arm-none-eabi-4_9-2015q1
GCC_VERSION=-4.9.3
HOST_CFLAGS = -g -O3 -m32 -W -Wall -fms-extensions -std=c99
HOST_LFLAGS = -m32
CONFIG_SITE = n
CONFIG_PICOC = n
CONFIG_TCC = y
CONFIG_MEMCHECK = y
CONFIG_MODULES = y
This is all, I do. And this works for me.
Edgar
Maybe it's time to upgrade the compiler on the build server (since your version produces a slightly smaller binary, small enough to boot).
So, there is no hope for new builds for 600d?
How do you came to this conclusion? Posts above indicate a solution.
600D user here running ML with April 19 nightly. Solid - zero crashes. Not interested in installing another version unless there's a critical upgrade to ML functionality.
Installing to additional SD cards for me worked well this way:
1. Remove working ML card from camera, mount on laptop, copy all contents from it to a folder on my laptop (named "ML April 19 Nightly").
2. New card - format in Camera, then mount card on laptop (no format)
3. Copy contents from "ML April 19 Nightly" folder to SD card.
4. Remove card from laptop, load it on camera. Run "update firmware" on Camera.
I've installed ML on 3 other 32gb cards and they all run smoooooth.
?
600D nightly builds doesn't contain FIR.
Invalid/incomplete/irreproducible installation description!
"600D nightly builds doesn't contain FIR." True, but a working ML card running the nightly does.
So you are describing something not reproducable by others and therefore misleading which is worse than useless.
I don't know who has hurt you, Walter, but you could use a bit of a lesson in civility. You're constantly abrasive like a disgruntled employee at a video store. Last I checked, ML employs NO ONE, so you can keep your shitty tone. You may think that because you answer to just about every post here that you're entitled to write the things you do, but no - you're not. Being helpful doesn't entitle you to be a condescending a-hole, no matter what you may think.
I'll create a video showing how I've done it and will post it (it's going to take some time because I've got a ton of things on my plate). I don't know who else has tried this and failed, but to everyone else BUT Walter, my apologies if I've mislead you, I promise you this works for new cards and I'll eventually prove it.
LU72, the fact that Walter is not "employed" or paid here makes it all the more remarkable that he is so helpful. Without him (or someone like him) there would be a lot more people wandering around this site searching fruitlessly for information.
Frank7D, Walter isn't the only helpful person here. I've learned quite a bit from reading other users' posts and they're helpful and cordial. Walter tends to be short and inarticulate; personally I can't say that Walter's posts have been the most helpful for my needs.
I'm not sure if your response here is to defend him and give him a "pass" for his tone on these forums, but I guess you're entitled to your opinion as I am to mine. In the meantime, I'll just shut up and try to find time to create a video showing how I'm able to copy the contents of a working card to another as I described above. I was only looking to contribute to the T3i/600D thread and not have to be told I'm "worse than useless" because Walter doesn't think my method works (did he say that he tried it and it didn't work? I can't tell due to his inarticulateness).
Quote...not have to be told I'm "worse than useless"...
If you look again, he was talking about the installation steps you recommended, not you as a person. Instead of feeling insulted, you could just prove him wrong (or could you?).
LU72 I see no reason why this would not work. I assume you always kept the first fir you downloaded when you first installed ML. Walter I think jumped the gun and thought you only put on the nightly download. The one without the fir.
When I do it I make my card bootable with EOScard then copy the new nightly. No need for the fir as long as you have used it once in the camera. Which way is best is the one that works for you.
Hello,
Full on newby here, I have a T3i, and will be using it to shoot video for company purposes. Until we purchase our primary video camera, this will be what I am shooting all video with. I came across a youtube video that recommeded ML for the audio metering, and other features. I have a couple of questions before I do this. I realize there is risk in everything, but what would be the best process to install this? What are the real world chances of me Bricking the camera during this process? Are there any known issues with the T3i and this software?
Top of page -> Downloads -> Browse Nightly Builds -> 600D.102 and read instruction. v2.3 contains a very detailed guide for the first step.
I made the mistake of deleting the files from the card by accidentaly formating it on my pc. I tried doing a new install but it does not recognize the files on the sd card. Yes, the files are on the root of the card.
Use EOScard/Macboot to make card bootable. Wipe all contents from card (but don't format again) and copy extracted nightly build contents to card.
Not an option, unless I use it through Wine. I'm on Linux.
Solved. Reinstalled the old stable version, then upgraded to the nightly build by deleting the files and copying the new ones over to the sd, thanks for the help!
For Linux users there is make_bootable.sh:
https://bitbucket.org/hudson/magic-lantern/src/tip/contrib/make-bootable
Hello, I have one 600D and I'm a C# programmer. What can I do to improve the 600D support?
Stuff needs to be refactored out of the core and into modules so that the autoexec.bin size is less than 512K (that's currently the most pressing issue).
You're probably going to need to learn some C/embedded programming and dig into the code base. The first thing to do is setup the ARM toolchain and try to compile a build.
See:
http://www.magiclantern.fm/forum/index.php?topic=991.0
http://www.magiclantern.fm/forum/index.php?topic=9625.0
http://www.magiclantern.fm/forum/index.php?topic=9517.0
Sorry for asking but can anyone help me with this? Every time when I am recording raw I got like blue, pink and yellow pixels around for example leaves and I don't understand why!? I have tried both Rawmagic and MLRawViewer, I have tried both Mac and PC but nothing will help me! Can anyone help me to get rid of those colored pixels?
Down here I put a picture so you guys understand what I mean!:
I am also sorry for my bad english!
(http://www.freeride.se/img/photo/l/29d96b7d32a95ec5e93c2db05c6d0358.jpg)
Looks like aliasing to me. Try reshoot scene in crop mode and compare results. For avoiding aliasing in non-cropped mode there is VAF. Expensive.
I just purchased the T3i a week ago after having a T2i since 2010. I've used ML on my T2i for a few years now and was always able to adjust the digital and analog ISO levels by pressing the ISO button and using the wheel to select the different increments. After installing ML on my T3i, I have found the camera unable to achieve the same control. The only way I am able to select the digital ISO levels like 320 and 640 on my t3i is by opening up the ML menu and changing them there. If I press the ISO button and use the wheel, I am only given the analog levels like 100, 200, 400, ect. I am wondering if there is a setting I have to turn on to be able to select the digital ISO levels on the fly or if the T3i is just not able to do this? Any help on this issue would be great. Thanks.
Hi all,
I have a quick question, after doing some research I was a bit confused about the installation of the nightly builds on the 600D/T3i. Watching an installation of ML on youtube for a 5D didn't help to much obviously!
I understand that the stable version of v2.3 needs to be installed first, and I did this a couple of years ago. At the time, I copied all the files over to the sd card (so all the .fir files and also pdf files.)
Having read the installation instructions for v2.3 here, for the 600D it says "- Unzip 'ML' directory, 'autoexec.bin' and '600D-102.fir' from the downloaded ZIP file onto your sd card."
As I didn't install ML this way in the first place and I originally placed all the files on my sd card, could I delete all the files except the '600D-102.fir' file, and then continue with the update process by placing the nightly build files onto my sd card? Or should I uninstall ML and start again?
Hope my post makes sense, thanks.
Here is a good tutorial! https://www.youtube.com/watch?v=rxwXi1X0xGc (https://www.youtube.com/watch?v=rxwXi1X0xGc) exact the same steps for the t3i!
Hey _OLLE_,
Thanks for the reply! I'm not sure if the video is the same as the installation on the t3i.
I understand the instructions on the t3i sticky fine, but comparing them to the t5i sticky and the video you linked tom, there are some differences. But, thank you for your help!! :)
From my understanding the t3i needs the original stable version (v2.3) to be installed first. In the sticky, it says to copy over the 'ML' directory, autoexec.bin and 600D-102.fir from the original stable version. And, then once 2.3 is installed you can delete the 'ML' directory and autoexec.bin and replace those files with the new files from the t3i nightly build - but you have to keep the 600D-102.fir file from the v2.3 install.
But the sticky is relatively new, and when I originally installed ML on my t3i, I just copied every file over to the sd card. So, I had .fir files for the 5D and other cameras on the card, and they are still there today along with the help pdf files.
I don't know whether it would be ok to delete the files I don't need e.g the pdf files, the (old) autoexec.bin, the (old) 'ML' directory and all of the .fir files except for the 600D-102.fir file and then place the new nightly build autoexec.bin and 'ML' directory onto my sd card. I'm not sure if something will break?
After installing v2.3 *wipe* disk. Don't format it but delete just everything. Copy extracted nightly build contents to card.
Thanks for the reply Walter,
I'm sorry, if I'm missing something. But I think it's better to know what I'm doing, instead of coming back and saying I bricked my camera.
I'm still a little confused, because I already have ML v 2.3 installed (from 2 years ago) I just want to upgrade to the nightly build. I'm sure I installed ML v 2.3 correctly per the instructions from 2 years ago. As I copied every file from the v2.3 zip to my t3i sd card which is stated in the INSTALL.pdf file. Here is a video, (not me!) but it shows what I did https://www.youtube.com/watch?v=Sp-5wSmUsHc (https://www.youtube.com/watch?v=Sp-5wSmUsHc).
So, presumably I could skip to "Updating Magic Lantern with new build in the future (on camera and sd card with ML installed):" step in the sticky. But where the sticky describes the updated why of installing v 2.3, which only copyies the the ML directory, autoexec.bin and 600D .fir files from the v2.3 zip.
In my case as I have excess .fir files and pdf files from my original install, I'm not sure if it is ok to copy and replace the new nightly build files with the existing files on my sd card and then delete the excess .fir files and pdf files?
Sorry, Walter. I included the original text in italic just for information purposes (I can edit it out later if you think it would confuse users.) I re-read the sticky. I thought for some reason I had to keep the 600D.fir file. So, just to confirm I can safely delete all the files from my SD Card, except for I'm guessing the DCIM and MISC folders and then just place the new nightly build files (ML directory and autoexec.bin) to the sd card.
You only need the fir file if you have a new or formatted card. This is how you make it boot able in camera. I tend to do this in the computer using eoscard then copy the .exe over .
Thanks for the replies. I have re-read all the documented info and all the posts I think I know what I am doing now!
Thank you everyone for the help :)
Just don't drop the camera when you are swapping cards. This about the only way you will break it with magic lantern.
Thanks Datadogie for the heads up! ;D
Been meaning to get a few words in here... but I'm a longtime PC user/absolute Apple-hater... and it's taken me some time to adjust to this MacBook Pro since my Asus died...
If I don't sell my 600D in favor of an a6000 I'll have some things to report.
Been there, Done that.
Stick with Apple. You'll be happier in the long run.
Especially on the creativity level (post workflow) so yes you should also keep the Canon and upgrade when you can down the line.
Hey Can someone tell me did i remove ml properly. First i formated the card from the dslr but ml was there again. Then i formated from my PC and now its look like its fine. Can someone tell me is there something wrong to my camera that i dont know
Wrong all over. You just deleted ML from your card but you have cam's bootflag set.
You may want to read first post of this thread.
How can I do this. I don't understand. Can you show me with pics?
Read first post. And inside v2.3 "stable" ML zip is the most detailed installation instruction covering uninstallation, too.
I just formated the card from my pc and there is nothing in the card and that is the reason why I don't know what to do. My dslr looks like its new.
You have to run installation to uninstall. Please take special attention to pic's bottom line and last few lines of first post.
You need ML v2.3 stable. No need to mess up with nightly builds.
If you insert a bootable card without ML files or an Eye-Fi card cam will get stuck at startup ...
Want to bet? Just run EOScard/MacBoot to make card bootable, wipe all contents and try your luck. You will have to remove battery and card to proceed.
I think is the same if the card is formatted from pc
ok bro I understand I will install again and then I will unistall
I install it again and then I did this https://www.youtube.com/watch?v=dkVNn7AQ42Q
I didn't run EOScard I just installed it like the first time and then I did like in the video
To verify deinstallation format your card in cardreader, use EOScard to make card bootable, wipe contents from disk and startup cam with card inserted.
- If cam get stuck: Cam's bootflag is there
- If cam starts up with Canon menu: All done. Format card in cardreader and you're clean.
Have anyone working on update for 600d?
Will ML shoot video using STM on the 24mm pancake?
I think you're asking about the "smooth" AF introduced with STM technology. Nope, ML won't bring this feature to 600D/T3i.
Two problems to solve:
- I just bought a new 64gig SD card.
Magic lantern don't load on it.
I have ML installed in a 16g card and it works fine. I copy the ML files to the new card , put it on the camera and nothing happen when I put camera ON.
Did somebody already try a 64g successfully here? (It will be useful for long video shoot)
-Other thing, when I update my 16g with the new nightbuild ML, it works but the screen flicker a bit and I can see "firmware" write very palely .
He's anyone can help me with that?
Thxs
Format card in cam, insert card into cardreader, copy nightly build contents to card. Run Canon firmware update.
I already try all of these. Is there limitation for the card size?
No.
Which error do you have trying to run firmware update?
Or try this:
Run EOScard/MacBoot to make card bootable. Delete all content but do not format card. Copy extracted nightly build content to card. Startup.
Well what I dont understand is wy is it working perfectly with my 16g card and not at all with my 64g.
When I try to install the firmware from the 64g card, I have a grey screen whith : " Update file cannot be found,Please check the memory card ..."
It's really wird. I did the exact same procedure with my other card and everything is fine.
Thank's guys for your answers anyway!
My wrong: Totally missed you're running 600D.
You cannot use card bigger than 32 GByte with Canon's update procedure. And you cannot make a card bootable using nightly build for 600D.
You have to use EOScard/MacBoot to make cards >32GB bootable. Wipe card's content after and copy extracted nightly build content to card.
ok so card uper than 32 gig won't work on 600d. Is it working on 60D? (A friend of myne have one, I could trade )
Wrong. You cannot use Canon's firmware update procedure in 600D to enable cards > 32 GB . You have to use EOScard/MacBoot.
Hello,
The follow focus seems to be a wonderful tool ! But I can't use it with my 600D and the last night build : only a short part of the distance between the current focus point and the stored focus point is triggered when I press "play" , maybee is it a solvable problem ?
Lens used?
Focus -> Focus Settings -> Step Delay. Increase number. Results?
Tamron SP 17-50 F/2.8
Same thing with step delay 50ms and 100ms
Tamron SP AF 17-50mm f/2.8 XR Di II VC LD Aspherical [IF]?
Yes, this one
Works fine with 650D and Sigma 18-125 here. Unable to reproduce.
Since the official nightly build is still not being updated, I created a small cronjob that pulls the unified branch from the magic-lantern repository and builds a new version if there have been any changes.
It is available here: https://hege.cc/magic-lantern/ (https://hege.cc/magic-lantern/)
I use the gcc-arm-embedded toolchain from this repository (https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded) and the build seems to work fine. I have not had any obvious problems with it on my 600D, but I have not done any thorough testing. So, as always:
USE AT YOUR OWN RISK
I will probably stop providing these builds once the official nightly builds are available again.
Thanks, will give it a try.
Thanks a lot, Datensuppe. Seems to work as expected here.
Edit: as of January, 2016 these builds no longer work and may be risky to use. Suggest using the official build instead.
Quote from: Datensuppe on September 07, 2015, 02:51:46 PM
Since the official nightly build is still not being updated, I created a small cronjob that pulls the unified branch from the magic-lantern repository and builds a new version if there have been any changes.
It is available here: https://hege.cc/magic-lantern/ (https://hege.cc/magic-lantern/)
I use the gcc-arm-embedded toolchain from this repository (https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded) and the build seems to work fine. I have not had any obvious problems with it on my 600D, but I have not done any thorough testing. So, as always:
USE AT YOUR OWN RISK
I will probably stop providing these builds once the official nightly builds are available again.
Datensuppe, this weekend I'll give it a try.
Quote from: PG on August 27, 2015, 05:30:47 PM
ok so card uper than 32 gig won't work on 600d. Is it working on 60D? (A friend of myne have one, I could trade )
Hey, I bought one and had the same problem. I solved using the EOScard app http://pel.hu/eoscard , like Walter Schulz said
I everyone!
Newbie approaching so please don't kill me.
I am wondering if anyone was able to take photos under a lower than ISO. I've read you can make videos, but I can't find a reference on photos.
Thanks anyway,
D.
About my autofocus problem
Quote from: xmanoux on August 31, 2015, 09:53:09 PM
Only a short part of the distance between the current focus point and the stored focus point is triggered when I press "play"
I just have bought a new lense (Tokina 11-16 dx II ) and I notice exactly the same problem with this lens
Thanks Datensuppe! Will try out on mine. On whatever version I currently have, I've noticed a few small inconsistencies vs original firmware, particularly around the multi-stop shooting; in stock firmware it would automatically take all the specified stops, whereas with ML, I had to manually press the shutter 3 times; making it more likely to misalign the shot.
Why firmware for EOS 600D is not updated from April 19?
Because you haven't contributed any improvements.
Quote from: Yuriy_Mosiychuk on October 24, 2015, 06:15:55 PM
Why firmware for EOS 600D is not updated from April 19?
Apparently for a number of reasons, including that the current code doesn't always compile for the 600D, the programmer who was coordinating 600D builds has disappeared (?), and the main dev for the project is very busy.
Cannot understand why people keep stating "Why firmware for EOS 600D is not updated" or any other camera come to that. Here we have a free firmware, yes that is FREE!!! that does on most Canon cameras what before you could only dream about or wait years for Canon to play catch up, be happy and grateful for what we have been given and go out and take pictures!!!
Russ
personally i think part of the problem is that the download page says "nightly" builds. some might take that literally.
This is dark but you made my day!
Nightly builds are for us budding teenage kids who play in the dark, totally aware of our own inadequaties and flaws - it's like holding your first love in the hand and dreaming of an adulthood so far away... we hold our breath while exploring what is actually possible to do... with the beautiful girl and the equally beautiful pictures and footage our cam is capable of, and we dream far beyond what is physically possible... HDR, Raw... her smile, her hair, backlit, do I open the flash... Ahh no, open the diaphragm a bit...
ML is what dreams are made of, not some consumer level kind of spaghetti bolognese...
ML expands what you can do with your camera. You really start exploiting ML when you have fully exploited the in-camera options. When you know your cam by heart.
People who buy a camera and install ML right away are in for a very tough lesson. For every available option the cam has, you can multiply with a factor 2 or 3 as soon as you open the ML menu. You are kids, and you're living your childhood with the best toy ever invented: the camera. Walk through the basics. Try a new lens or two. Experiment with portraying the sweetest girl in the world - the one from paragraf 1. A consumer cam has an option for HDR, but if you teach yourself AEB or even manual AE, the result is so much more rewarding. Her eyes, so dark and mysterious in a cascade of off-focus hair... That's what photo is about.
Learn the basics with the camera that has most appeal to you. If it's a Canon, count yourself lucky that in this world we have people like... Ahh no names, but you'all know who I mean. If you are a beginner in photo, learn your camera. If you know your camera inside-out, come and enjoy the tremendous work other outstandingly good photographers - and programmers - have done: ML.
And if you're a beginner, photo is like meeting the worlds most beautiful girl, catching her eye and exchange phone numbers... you hold your breath, for the world is spinning around you, and the NOW is bigger than life... With ML you're practically holding her hands and looking in her eyes and seeing a universe of a future..
Let us never forget why we became photographers in the first place.
What I wanted to say to irvcobb: If the ML/600d hasn't changed from April 9, maybe it's because it works. That's a testimony to the quality those dev deliver: No complaints in 5 months.
Perfectly well said, @axelcine and I've actually been keeping a close eye on you since you seem to not only have a great understanding and IQ for when it comes to ML stuff especially in terms of cinematography, photography as well an excellent sense of humor in yourself, Sir!
"Come to the Dark Side, Son!"
Thanks for a great morning read and you definitely got yourself a new Follower in me.
@DeafEyeJedi - "It's like fine wine... The longer it takes the better it taste..." I think you wrote something like this in a discussion of workflows. And we met in a discussion of audio recording...
Come to the dark side. When witchcraft works and magic lanterns glow, something wonderful is going to happen...
If I were irvcobb I'd be out of my mind for that fine cam he has. One of the singular Canons with built-in movie crop...! Am I envious or not? With ML he's going to skyrocket. Oh, sorry irvcobb, I know you're there, just didn't see you; high five and good luck, and let's see what you come up with. And - oh, my ML/700d also has movie crop, thanks to our fine devs. The 600d gave them the idea.
Walter - sorry for being a little out of topic
Quote from: axelcine on October 28, 2015, 04:49:18 PM
What I wanted to say to irvcobb: If the ML/600d hasn't changed from April 9, maybe it's because it works. That's a testimony to the quality those dev deliver: No complaints in 5 months.
No complaints here. But newbies tend to see "nightly builds" as meaning either (a) "latest and greatest" at which point they feel they are missing something with an apparently older build or (b) "too scary to touch" which isn't the case with ML.
ML is amazing, and I get the thrill of creating something this cool. But not everyone is or wants to be a coder, and not everyone understands the way such things work.
I used to code, and in assembly. I understand the technical challenge, the thrill of problem solving, and even the beauty of a good hack. My interests are elsewhere now, and the occasional note here trying to clarify for a newbie is about all I have the time of skills for.
Yuriy may never contribute back to the code base. But he may use ML to take some very satisfying images, and he may contribute back to the community in other ways, seen or unseen. And maybe that's enough, at least I think it is.
@irvcobb - Exactly why do you think that I see you as one of the guys taking the 600 to its very limits? You'll show us what it can do once you get your grips on ML.
@DeafEyeJedi - you're far too kind. You're all over the place, posting in several threads and providing people like me with tons of information. You're one of those paving the way, and following your tracks in the various threads makes us address and understand many important issues.
Trying to follow your lead has taught me a lot about my camera's basic functions, so that I have been better able to understand ML.
Hi all,
I was wondering if anyone could help me. I have had the nightly (April 19) build installed on my camera for a few months now. I have mainly been using the ML to adjust white balance. The other day, I tried to use canon's custom white balance feature (the one where you take a picture and it uses that as a reference point) and nothing seemed to change.
I'm just wondering if ML is overriding canon's white balance, or if I've done something wrong.
Cheers, Rob
Reset cam to factory defaults, retry and report.
Thanks Walter, that did the trick!
Thanks again, Rob
Re: Canon 600D / T3i Bricking UP, never had an issue using ML (2011) on a T3i for several years, except it can run hot after shooting for hours in the sun at sporting events/outdoors. I use a custom golf umbrella to keep the suns heat off my camera body when feasible, or opt for the best location with some shade. Sometimes the red light may stay on and won't go off. Remove the battery, and reinsert it. This setup is better than most why? because you can get away with getting this equipment into places that a traditional video camera would raise a big red flag... Wanting money for permits, scarring security, etc. Just use a better external video source if that part of your video matters. I purposely bought the T3i to run ML on it. I used every sort of video format old skool since U-Matic. I will continue using ML, it just works. If you need a newer port then get another Canon. T3i's are a bargain and can be picked up for $250. Way cheaper than most high end Panasonic's, etc. OK 4k video is coming, make sure you s-can (chit_ ) all of your existing Computers because the horsepower and HD requirements are enormous. I'll keep the change as technology advances. Who knows maybe next year ML will be obsolete, because Canon or Nikon has come to the table and seen the light, or some crowd-funded startup has blown all of them to the wall! Just my Opinion. I'm constantly being admired by my peers when they see what I do with my T3I. The photographer makes the image the tools are really all the same.
I have been using movie restart from time to time when i have multiple cams recording and can't be at them at all times...and in general it works, HOWEVER it doesn't consistently record all the way to the 4gb limit, which is ~12 minutes, before restarting. In other words, it will record 4/5/6 minutes or so then stops, and starts again.
The newer nightly build seem to be better at getting longer record times, but it still isn't perfect by any means. It appears to be a stability issue of some kind, so i'm wondering if there might be some other setting that i need to turn off or adjust that might make it more stable... ie --> bitrate or something like that.
Thanks,
Tompdog
Please clarify: You are recording native Canon H.264 without ML tweaks (CBR tuned up or else) and cam stops before 4 GB limit is reached?
Yeah, thats right Walter...no ML tweaks at all aside from base ML & "movie restart" selected. In fact, I reformatted one card and left magic lantern on the card, and another card i reformatted and wiped it all the way down, then reinstalled from scratch by updating the firmware in the camera....in both situations its more or less the same... they will not consistently record to the 4gb limit before restarting. (it does however restart without fail each time it stops recording...most times bf it reaches 4gb limit, occasionally when it does...)
And like i said... i also tried the most recent nightly build, and its a little better on avg, but not close to perfect.
One of the memory cards is a really nice one...way faster than the sd card bottleneck restriction, so its not that....
anyway....anyone else have this experience in any capacity???
Don't have a 600D to test it but I never heard of such an issue before. Blunt H.264 without ALL-I will result in a data rate below 6 MByte/s which is just far away from cam interface bottleneck (about 21 MByte/s). And I don't use cards not meeting Class 10 requirements.
@a1ex: Are there any 600D specific issues with recordings stopping before 4GB?
There were similar issues reported for 550D and 60D, but I could not reproduce any of them, even on my slowest card (class 2).
Some things worth trying: http://www.magiclantern.fm/forum/index.php?topic=2651.0
Thanks for answering, a1ex!
But link is not working for me.
The topic or board you are looking for appears to be either missing or off limits to you.
@ Walter - search [CAN'T REPRODUCE] Video stops first time (550D) - and a good weekend to you.
Thanks a1ex & Walter for the input!!!
OK...i'm posting a 5 minute video to youtube right now, i'll have it up in 15 minutes or so... i video'd my T3i starting and restarting so ya'll can see it if you care to. I happened to catch a particularly bad stretch where the longest recording was like 1.5 minutes...most 30 seconds or less. Throughout the video i stopped and you can see me turning off options listed in the thread a1ex linked to...still no benefit. I also pull out the memory card at the end to show its a class 10 card.
My wife came home during the video...so please ignore the banter....and my Yorkie making an appearance at the beginning...lol
https://youtu.be/hp2I_Y4SaoE
i'm noticing now that right before it restarts every time some type of meter flashes up on the right of the screen...odd, not sure what that meter is measuring???
thanks
Hello I'm stuck on installing the new Magic Lantern on my T3i. I had Magic Lantern before and the instruction are quite confusing and intimidating I don't want to brick my camera so I came here to ask questions before I mess up. Please help
Run EOScard/Macboot and make card bootable
Wipe card's files and directories (if any) but don't format.
Copy extracted nightly build content to card.
Done.
hi
are there any updates planned for the 600D?
I saw that for other models the nightly builds are all recent and for the the T3i they are quite old.
any idea if new updates are planned?
There are never any plans.
Actually, several of the nightly builds are quite old. There probably weren't any commits that affected the 600D/T3i. However, if you want to try some newer stuff you can download the source and compile it yourself. It isn't that hard.
Topic: Getting a development machine up and running and developing. (http://www.magiclantern.fm/forum/index.php?topic=9517.0)
Thank you all.
If there are no new stuff then i shall stick with the current version.
Do you believe that is there will be new stuff it will be available for the T3i as well?
My T3i is stuck on firmware 1.0.1 and can't get the camera to update. Camera is stock and has never had firmware updated.
I've downloaded the CCF11102.FIR file and instructions from Canon web site, formatted (low level) the SDHC card cleanly, and copied firmware file to root directory. Always get "Update file cannot be found" error on camera. Have tried with both 32GB and 8GB cards with no luck. I've tried copying the file, and extracting the zip to the card with no change.
File size is shown in explorer as 11.6 MB (12,232,284 bytes)
Any suggestions?
Edit: I also tried to update by downloading the latest EOS Utility program, but the Windows 7 x64 machine I'm using (on vacation) doesn't recognize the camera (nor does the Utility). I don't have the original USB cable with me, but used two different ones. Frustrating...
Retry: Format card in cam, insert into cardreader, copy FIR file to card, insert into cam. Use photo M mode (no Liveview!). If it fails: Reset cam settings to factory defaults (includiing C.Fn settings) and retry.
Do *not* use EOS Utility 3.x! You may use EOS Utility 2.x included in "EOS Digital Solution Disk" v29.0A/29.1A.
Hello! Dear forum, help, I need the technical service manual. I want to make the outlets to handle contacts booster, but I do not have a technical dokumentytsii and power circuits. If you have, help your fellow man.
There is no such thing, Canon would never consider making such a document public. We figure out everything we know about the camera from reverse engineering.
In the extremely off chance that anyone is in possession of such a document, please DO NOT SHARE IT HERE. Doing so would put this project in legal jeopardy. The laws that make it legal for us to do what we do, depend on this being a "clean room" reverse engineering effort (in other words we don't steal or share Canon's IP, we simply figure out how it works from reversing). See: http://wiki.magiclantern.fm/faq#is_it_legal
Thanks for the reset suggestion Walter. Unfortunately no change - camera still can't find the update file.
I've copied it to the root of the CF card, alongside DCIM and MISC folders. I downloaded the file from both Australia and USA Canon sites to be sure I had the right file - identical size.
Any ideas?
Quote from: irvcobb on December 15, 2015, 04:09:10 AM
There are newer builds here:
https://hege.cc/magic-lantern/
No new features, but possibly some bug fixes.
New important change:
Quote
e5cc80d | Gr3g01
Fullres silent pics: max exposure for 500D/550D/600D is 15 seconds :)
Quote from: sfmike99 on December 24, 2015, 11:34:30 PM
Any ideas?
Try changing filename to all uppercase/lowercase.
If it doesn't work check MD5 for this file.
MD5: 195DEFC3EEF7CFF7FA2317F7D8EE19AA
600D has a memory management problem for some time. Seems to be solvabable by using another (more recent) compiler. But: As long there is no maintainer to take over long time support cam will be stuck in limbo. Use old build with all limitiations instead.
I doubt a different compiler could save ~8KB, and as soon as anything else is added, you go over again, but it's easy to just disable features.
Has the 600D less memory then the 550D? Or just less free memory because of heavier canon firmware?
600D has limited memory to load the autoexec.bin binary into memory during boot. This is just a result of how the Canon bootloader works, and how ML starts up, not a result of total memory available (Why? It's very common for bootloaders in general to have very little resources available, in fact this is the very reason it is called bootstrapping; this article is about x86 not ARM, but the same principles apply: http://wiki.osdev.org/Boot_Sequence).
For us, there are only 512KB (0x80000) of memory available for autoexec.bin during bootstrapping for whatever reason (this is true for 600D and 1100D, other cameras have more, so they work fine if autoexec is bigger than 512KB). Later on we have vastly more memory available (several hundred MB usually, depending on what Canon firmware is doing and how much it needs), this is why we can still load lots of modules, they aren't loaded until later on when a lot more memory is available*.
Going over 512KB is very bad. This is my understanding of why: it basically means that an arbitrary chunk of ML's code is basically going to be missing, and there may be, for example, functions that point into uninitialized/invalid memory locations. Due to the lack of memory protection on the ARM CPU, this means that arbitrary code can execute, which is VERY BAD! What's worse is that if it's only a small chunk missing, then most things may appear to be working until all of a sudden, randomly later on, you try to execute something in the missing chunk and you get a hard crash.
Always check the MemSiz header in the build output:
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
EXIDX 0x073918 0x00cf3918 0x00cf3918 0x00008 0x00008 R 0x4
LOAD 0x000100 0x00c80100 0x00c80100 0x73820 0x7ff0c RWE 0x100
It must be less than 0x80000 for 600D and 1100D. Above is the last valid 600D build, notice it's right on the edge. The current ML source results in something about 8KB over the limit.
So, whoever is doing this: hege.cc/magic-lantern/ should probably disable it until this issue is resolved, or they should disable ML features to get the size below 512KB. Because arbitrary code can execute, there is a possibility of bricking. This is no joke.
*This should give you some clue as to a possible solution: move stuff to modules. There are two main issues moving things to modules. 1) A lot of the ML core is tightly coupled (things depend on each other), so it's hard to move things out without refactoring out the tight coupling (it is possible to remove a lot of dependencies, just time consuming). 2) There are a ton of macros that specify unique camera specific code all over the place in the core. This is not allowed in modules, modules are supposed to be camera agnostic or at least they contain all the code for all cameras if there's a difference, (e.g. dual_iso), so the same module can be used on all cameras. Again, there is refactoring that can be done to alleviate some of this, but it is considerable work. I've been trying to work on this some b/c one of my cameras, 1100D, is also plagued by this issue.
Another possible solution (and a much better one actually) is an 'ML bootloader'. Basically the part of ML that goes in autoexec.bin is just a minimal core that knows how load some camera specific binary from a specific location. This too is a lot of work. It has the advantage of allowing one single download for all supported cameras, and the ability to use the same ML SD/CF card on different cameras.
Thanks, dmilligan, for what I find to be a great explanation of the situation.
hege.cc/magic-lantern/ was set up by user Datensuppe. He hasn't been active here since last September,. The code that appears on the site is from a cron job he set up. (see this post: http://www.magiclantern.fm/forum/index.php?topic=15360.msg153980#msg153980)
I have pointed people a few times to these builds. Will go back and edit my posts if possible with a warning not to use them.
Thanks, very good explanation.
Hi,
I have followed exact instructions provided to install Magic Latern by I do not see all the changes Magic Latern brings.
I see some changes in live view. But Menu brought by Menu button is old one; Attaching screenshot showing ML install success .http://imgur.com/G6ja3cJ
Please help me guide what is missing for me.
Top of page -> User Guide -> User Guide/Install Guide
yes I have followed exact same instructions, but I see old MENU only when I click 'MENU' button on camera body!
Delete ML directory and Autoexec.bin and *.FIR from card. Extract latest vaild nightly build to card.
adaware- Magic Lantern Menu is accessed by pressing the Trashcan button not the Canon Menu System these are basics you would have found by reading up on what you are using... its no more than a page deep in the user manual.
Any good field monitors to use with the T3i? I was looking for one that allowed me to see ML overlays.
I've filmed several scenes but get greenish cast, which I haven't been able to correct in post.
Does this cast result of the increased CBR from 1.0x to 1.4x or due to something else?
I filmed in RAW 960x540 on 600d.
Hello ibrahim,
I had a similar problem in the past with the T3i. There is a solution. I will provide some links to forum posts, but watch this video first: https://www.youtube.com/watch?v=hn-djQijUZE
Here is my post from the summer about having the same problem, and the resolutions people came up with: http://www.magiclantern.fm/forum/index.php?topic=15653.msg154979#msg154979
A few more posts to check out:
http://magiclantern.fm/forum/index.php?topic=11664.0
http://www.magiclantern.fm/forum/index.php?topic=13465.0
http://www.magiclantern.fm/forum/index.php?topic=11942.0
Please let me know if I can help in any way, and please let us know how this goes. I hope you are able to resolve your issue.
- Paul Harwood
When you are shooting LV either stills or video, with ML display, is there a way to move the AF box about?
I seem to have to use the * or back-button focus button with arrows, this is impossible to move
without moving the camera about. It does not work in every focus mode either.
It seems that the in the ML config, one would want to have focus box move by arrows as one
of the options (just like ISO/TEMP, step focus, etc.) for the DISPLAY button.
If one were to use the DISPLAy button instead of the * button, then the arrows being pressed
does not move the camera about.
Reset ML settings to default.
Canon menu (4th from left) -> AF method -> FlexiZone (do not use "Quick")
Retry and report-
Managed to move it about, by using the * button, and set buttons, until the box appears. Then the arrows could be used without simultaneous pressing.
It was better.
Now my beef is more about tracking, it seems that follow-focus with focus peaks is the best for video.
Although I am getting really good at MF with riding the focus ring.
Too bad it does not track continuos with an aiservo, as the subject moves about. Its really only geared for the shutter press.
Now that would be an enhancement, trick it into constantly AF as the subject tracks in aiservo for video.
Thanks dmilligan for the clarification about the memory-size limit. I currently don't have the time to look into disabling features in my 600D nightly ML-builds so I disabled the cron-job and removed all builds, that are broken due to the bootloader being too big.
The build from 2015-12-21, which is the last one that should be ok in this respect, is still available.
Sorry, I didn't remove the broken binaries earlier...
The latest build available on the web is #355 19.Apr.2015. Do not use newer builds, please! They have been removed for a reason.
https://builds.magiclantern.fm/jenkins/job/600D.102/
I enjoyed reading all 6 pages of this forum. I looked in my "My Documents" folder and realized that it was 2012 when I last used ML and still have all the files, etc from that time. I stopped using it shortly after trying it as I am mostly a still shooter and sometimes it got in the way. I might get into shooting video with it so that is another reason I'll keep an eye on this forum. Anyway keep up the Nightly Builds!
I wonder if there is a way to marry the the step focus function with the Auto_ETTR.???
The idea is if it can adjust focus by steps, and set auto_ettr, should one be
able to create a rather awesome focus tracking, that keeps in focus while adjusting auto_ettr,
and ofcourse I am refering to video. The though of dynamic exposure adjust while a subject
moves in a frame in focus would be rather exciting.
JM2C
PS: We would need an ISO max limit too. Currently ML ISO = AUTO, is not max. limitted, leading to undesirable ISO=A6400 or A3200.
Trying to put ML on my T3i... the version is 1.0.4 though....
Is there a way to downgrade the firmware? I have tried downloading the 1.0.2 and 1.0.1 official firmwares and running the update, but the camera comes back saying that there is no update file found.
600d with firmware 1.0.4? Please check your camera version. I quite sure you are actually using a 650D/T4i.
Huge mistake, camera is a T3 not t3i.... :-[
My bad.... sorry for the confusion
I have a question, since i didn't see this being mentioned anywhere. I recently bought a new 32GB SanDisk Ultra 80MB/s card and it seems to be very inconsistent with the write speeds, I checked and the bottleneck for the 600d is 21MB/s but my speeds are all over the place. When i start recording raw it shoots up to 20MB/s and and 3 seconds later it goes down to 10 and then 18 and it just keeps jumping up and down which averages out at EXACTLY 15MB/s in the card benchmark. what is going on... My old 30mb/s card is A LOT more consistent with it's 14.8MB/s. How so? How can i fix it? Is it the card? :(
PS: before you tell me how buying a 80MB/s card on a t3i is a bad decision, i only did it because it was on a 50% discount.
EDIT: Heres a video on exactly whats happening https://www.youtube.com/watch?v=Nqu-8MkYkds (https://www.youtube.com/watch?v=Nqu-8MkYkds)
EDIT: IT WAS the card. I regret not doing any research about this. If you ever plan on buying a card look at the benchmarks beforehand.
Hello everyone, i am newer to the magic lantern firmware. I have been using it now for a few months and I love all of the features. Recently I was looking around to see about being able to listen to the audio from the camera with headphones and i found that the nightly build allows you to do just that through the usb. So i downloaded the last updated nightly build and it runs great and does exactly what i wanted it to do. My only question is and it may be me being picky but on the v2.3 firmware when you had the live display on for recording all your settings were lit up all different colors which made it really easy to see them and pick out what setting you were looking for. With the newest nightly build i can only find changing the whole screen to a certain color. Am I missing something or was that feature replaced with the newest nightly build?
ML has come a long, long way since the legendary 2.03. stevefal and others proposed a new interface way back in 2013; you may read some of the story here:
http://www.magiclantern.fm/forum/index.php?topic=4386.0
http://www.magiclantern.fm/forum/index.php?topic=3072.msg124971#msg124971
http://www.magiclantern.fm/forum/index.php?topic=8539.msg80905#msg80905
ok thanks. My last question im trying to do the audio monitoring with the nightly build. I have the usb to 3.5mm female and i have all the settings i think need to be on and im not getting any sound out of my head phones. Am I doing something wrong?
Reminder: this PR is all that's needed to re-enable the 600D builds [1] (http://www.magiclantern.fm/forum/index.php?topic=15360.msg150013#msg150013) [2] (https://bitbucket.org/hudson/magic-lantern/issues/2268/nightly-2804#comment-17737213).
https://bitbucket.org/hudson/magic-lantern/pull-requests/610/benchmarks-and-self-tests-refactored-as/diff
Anyone interested in helping me testing it?
I'm willing to consider it. What would the testing involve, and how much risk to the camera? (I know: I get to keep the pieces.)
Compiling that branch, trying the "new" (well, moved to modules) menu options (it may take 1-2 hours, or maybe more if you want to run the infinite tests) and uploading the files created in the process. Or, if it doesn't work, reporting at which step it stopped / crashed / failed or whatever it did.
To minimize the risk, you can save a copy of your ROM files (in ML/LOGS on your card) in a safe place, just in case. The risk should be pretty small; for example, I have no hesitation running these tests on my 5D3.
I've uploaded a build with the benchmarks and selftests modules for testing and reporting.
http://www.magiclantern.fm/forum/index.php?topic=12608.msg165286#msg165286
I've been working with it for a few days and it seems solid so far.
I need help please , Ive been trying all morning to update the ml on my camera. First time I tried with my new sd card it worked, i could perfectly see the new menu and everything, minutes later i wanted to also intall it on m y other sd on which i had the previously ML version, so i followed all steps, and my camera freezed, it didnt turn on with any of those cards in! (it would turn on without only without them) so I found a video that explained how to format sd cards in your pc, followe steps. and worked ! then again I tried to installed everything from the begining , and all went fine, until i put the unzipped nightly build folder on the card and insert it in the camera, then is frozen again!!
Pleaseee what to do !!Ive been all morning trying to solve it , when i was supossed to do some nice timelapses!!
This is more of a development thread. I'd look at the camera emergency department thread for direct assistance.
While I use a 600D and ML I've never had issues like you describe so I don't know what to say. You did make both cards bootable with EOScard and included the .fir file ?
"I've been working with it for a few days and it seems solid so far."
IrvCobb, Were you able to upload the benchmarks or whatever else the devs need? If not, let me know and I can try to do it when I have some time.
p.s. what's with having to wait 900 seconds between posts? Very annoying.
So far, there is a problem running the 15-minute self test, in both the test build and the latest nightly build.
I wasn't able to understand where the test fails (at which step), so if you can run the same test and tell me where it fails, it would help. If it's hard to describe, a video of the camera screen will do.
A1ex, check my PMs to you. The issue was that the camera was set to power down after two minutes, which was interrupting the tests. Since I've switched that setting to always on, all the tests I've run have been successful. I've been using the build for about a week with no issues.
Pretty sure I sent you links to the output of my test results.
Ah, got it now. At first I thought you were only able to run the other (shorter) tests, sorry.
Added a few more tests, which were previously under Don't click me; now they are in menu. One of these tests revealed a bug in SRM memory routines as well (hopefully fixed now). Do you mind running these new tests as well? (they are 3, and it should take 10 minutes). You need to recompile the core ML as well for the SRM fix.
A1ex,
Had a couple of issues. See PM.
With the new benchmark-modul, will the resulting autoexec.bin be small enough to reenable this stuff in features.h for 600D?
// disabled, because autoexec.bin gets to big and 600D does not boot
#undef FEATURE_DONT_CLICK_ME
#undef FEATURE_SHOW_TASKS
#undef FEATURE_SHOW_CPU_USAGE
#undef FEATURE_SHOW_GUI_EVENTS
#undef FEATURE_SHOW_IMAGE_BUFFERS_INFO
#undef FEATURE_SHOW_EDMAC_INFO
#undef CONFIG_TSKMON
Edgar
See reply #147, escho!
Thanks for the link, Walter. Will play a bit with this next week.
As I can see, the burn-in-tests and the benchmarks are now inplemented as modules in unified. What´s missing in addition, to bring back 600D into nightles?
Edgar
There are some things that broke after merging the branch - just let me fix those first.
Ah, I see.
Alex, if you need someone to test (600D and/or 6D), let me know, please. Next week, I have some time.
Edgar
escho (and anyone else with a 600D), could use please check if your camera bypasses Magic Lantern if you press the SET button while turning it on? This is the documented behavior, but does not work on my cam with builds clear back to 2014. Trying to understand if the issue is my cam or ML.
Thanks.
Never mind.
Found the issue. If the SET button is programmed to a special function other than "normal" (I had mine set to Flash Exposure Comp), ML does not recognize it as pressed during boot.
I enabled the features (you can see in post 159) and looked at the MemSiz
disabled: 0x7802c.
enabled: 0x7af2c
That would be fine, but with patchmgr on top, we come quite close to the boundary for not booting, I guess (didn´t compile with patchmgr, because I don´t know, how to enable it).
So, what shall we do? Reenabling these features or not?
Edgar
To merge a branch (in this example, patchmgr) for a quick test, you can do:
hg merge patchmgr
This will also ask you to commit this change; you probably don't want to, so after playing with it, run this to undo the change:
hg update -C
To merge multiple branches, the best way IMO is a "working" branch, as explained in this guide: http://www.magiclantern.fm/forum/index.php?topic=9524
I tried this, but fail:
edgar@linux-pzco:~/ML/escho-magiclantern> hg branch
reenable-600D
edgar@linux-pzco:~/ML/escho-magiclantern> hg merge patchmgr
abort: merging with a working directory ancestor has no effect
edgar@linux-pzco:~/ML/escho-magiclantern> hg update -C
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
edgar@linux-pzco:~/ML/escho-magiclantern>
Are you sure you branched off the unified branch? And that you haven't merged patchmgr in to unified?
Quoteabort: merging with a working directory ancestor has no effect
Not shure, wht I´m doing and not shure, I´m doing it right. This mercurial-stuff isn´t my world.
Tried it another way:
cloned ML
updated to patchmgr
merged unified into patchmgr
But now, ML didn´t compile anymore for my 600D. So I let it be for the moment, I want to do other things first.
Edgar
In case you missed it: 600D is back in business! With new installer, of course: All those installation workarounds with v2.3, EOScard/MacBoot are no longer necessary.
Last successful build before: April, 19th. 2015!
You may want to take the weekend off: Change list contains 960 items ... most not exclusive to 600D, of course
Thanks a1ex!
http://magiclantern.fm/forum/index.php?topic=15360.msg166036;topicseen#msg166036
@Audionut/a1ex: Are you able to update Avenger 2.0's first post in this thread?
Thanks, A1ex!
Thanks A1ex!
Modified first post to reflect new install procedure.
This is great news. Thank you to all those who contributed time and expertise.
Great news!
Just a question... If the old nightly is properly installed, the tipical update (deleting and copying new files in sd) is still enogh. True?
Enviado desde mi LG-D855 mediante Tapatalk
Yes, that's what I did and it worked. The first post of this thread was updated with more detailed instructions if you need them.
I did install ML now but the user interface is still Canon and is somewhat ML,
Please help me with this.
Please don't use all capitals. //Audionut Click me (http://netiquette.wikia.com/wiki/Rule_number_2_-_Do_not_use_all_caps)
I appreciate that my Rebel T3i / 600d is back to being actively supported. Thanks!
And it seems the installation has gotten smoother .... don't need to use the old Stable 2.3. Grrrrreat Job!
Quote from: jayesh on May 24, 2016, 10:14:13 PM
I did install ML now but the user interface is still Canon and is somewhat ML,
Please help me with this.
The interface is completely Canon unless you hit the trash can button and override Canon settings with ML ones. ML just exists to solve problems. Try features as you need them. Personally I find it most useful for video mode (magic zoom, auto restart) and I like the built in intervalometer for time lapses.
hi all
I've been a long time ML user, but lately stumbled upon ML mention on the web and decided that I'll try new build with my T3i (aka D600) and ended up with unexpected problem.
Here are my steps:
1) dl-ed latest nightly
magiclantern-Nightly.2016Jun13.600D102.zip
Built on: 2016-06-12 20:59:14 -0400
Changeset: 90fe6de
2) formatted 4Gb card in the camera, made sure that the battery is fully charged
3) copied contents of the archive onto SD card on my laptop
4) put SD card back into camera, run firmware upgrade
5) ML installation screen appeared with green message about successful installation
6) I turned camera off, copied LOGS dir with ROMs onto my laptop, then put card back and turned camera on, it booted up into ML ok, I briefly checked settings once again - didn't change any settings except owner info string and shooting a picture for test
7) turned camera off, replaced SD card with another one (16Gb Transcend) - it is my main one, the card was previously formatted in the camera and had some pics on it, I removed it and reviewed photos on my laptop just a moment before. Tried to boot the camera...here the problem starts, 'cause
8) NOTHING HAPPENS :( even red LED didn't blink... I pulled out battery and card, waited for a min, put back 1st SD with ML - it booted ok.
9) put back 2nd card - not a single sign of camera booting... battery trick again, 1st card, uninstalled ML via fw upgrade menu, turned camera off.
10) put back 2nd 16 gb card - red led lit up and after a few seconds (it looked like something was happening, took more time than usual) camera turned on, but card was not recognized. "Card cannot be accessed. Reinsert/change the card or format card with camera" message popped up.
I turned camera off, put card into laptop - but it can't recognize the card now too. Even on USB level no new devices appear when I plug it in :(
Now the 16Gb card is totally dead and to me it looks like that ML just killed my card somehow :(
Questions: any chance of reviving the card? Silly me didn't back up photos, never ever before I had an SD card died such out of a sudden ((( so any advice appreciated.
Any clues on what happened? Did the canon/modified bootloader when ML is installed look up parts of firmware on SD card and could it happen that it killed SD flash controller somehow?
ML enabled cams will access card *after* opening card slot. It doesn't matter if there is an ML enabled card inserted or a "dumb" one. And it doesn't matter if "Power switch" is in OFF position.
Your incident may be related to this access mimic or not. Always wait some time after opening card door before removing cards from ML cams.
Quote from: Walter Schulz on June 17, 2016, 07:28:24 AM
ML enabled cams will access card *after* opening card slot. It doesn't matter if there is an ML enabled card inserted or a "dumb" one. And it doesn't matter if "Power switch" is in OFF position.
Your incident may be related to this access mimic or not. Always wait some time after opening card door before removing cards from ML cams.
:o
yes, that's most likely what happened. But I'm pretty sure the camera LED in the lower right was off. So if you're familiar with ML source code - is there any way to modify ML to provide a clear indication via LED flashing when there are I/O operations happening?
Details about the shutdown problem: http://www.magiclantern.fm/forum/index.php?topic=1455.0
I'm not sure what happened. Most likely, the camera didn't shutdown correctly, and you probably inserted the other card while the camera was still powered on (but locked up). Probably this is what killed the card.
What happens if you plug the card under Linux? (try a Live CD and paste the last few lines from dmesg after inserting a good card and then a bad card).
If there's no sign of life from the card on the PC, I can get the raw card contents from the camera (it's not easy, you will have to boot from one card, then, after ML is loaded, insert the bad card without turning the camera off; then, find a way to transfer the data, maybe via USB). I need to do some experiments about that on my camera first.
Thanks, a1ex! Yes, this shutdown problem thread you're referring to pretty much describes my particular problem. Seems to be unlucky coincidence where card has been accessed and write happened without any visual indication at the very moment it was ejected.. I wish I've read it earlier...well, lesson learned the hard way :(
If there's any slight chance to recover contents of the SD card with camera - I'm in game, let me know here or via PM if other experiments needed.
Here are dmesg outputs for both cards
With normal 4Gb Kingston branded card I'm getting
[ 401.948949] mmc0: new SDHC card at address 1234
[ 401.968919] Driver 'mmcblk' needs updating - please use bus_type methods
[ 401.969048] mmcblk0: mmc0:1234 SA04G 3.70 GiB
[ 401.971195] mmcblk0: p1
[ 402.336852] FAT-fs (mmcblk0p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
With corrupted 16Gb Transcend card (mixmax - AFAIU first 2 lines stll refer to previous card )
[ 546.713246] mmc0: card 1234 removed
[ 546.749369] FAT-fs (mmcblk0p1): unable to read boot sector to mark fs as dirty
[ 554.570100] mmc0: card never left busy state
[ 554.570110] mmc0: error -110 whilst initialising SD card
[ 556.216025] mmc0: card never left busy state
[ 556.216034] mmc0: error -110 whilst initialising SD card
[ 557.861903] mmc0: card never left busy state
[ 557.861914] mmc0: error -110 whilst initialising SD card
[ 559.507737] mmc0: card never left busy state
[ 559.507746] mmc0: error -110 whilst initialising SD card
+ with another healthy 8Gb Samsung card again
[ 964.423396] mmc0: new SDHC card at address 0002
[ 964.423777] mmcblk0: mmc0:0002 00000 7.41 GiB
[ 964.425486] mmcblk0: p1
[ 964.777148] FAT-fs (mmcblk0p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
+ with empty microSD-SD adapter, again first 2 lines can be ignored AFAIU
[ 1060.984609] mmc0: card 0002 removed
[ 1061.016661] FAT-fs (mmcblk0p1): unable to read boot sector to mark fs as dirty
[ 1153.950719] mmc0: card never left busy state
[ 1153.950729] mmc0: error -110 whilst initialising SD card
[ 1155.596602] mmc0: card never left busy state
[ 1155.596612] mmc0: error -110 whilst initialising SD card
[ 1157.242471] mmc0: card never left busy state
[ 1157.242483] mmc0: error -110 whilst initialising SD card
[ 1158.888373] mmc0: card never left busy state
[ 1158.888384] mmc0: error -110 whilst initialising SD card
- looks like the card is dead and some trick with low-level access via camera is the only chance...keeping fingers crossed
thanks!
Other thoughts:
The reason I was somewhat nervously pulling cards in and out was that the camera apparently did not boot up after I changed cards and this (see p.7 in my steps) resonates with msg on ML fb page (https://www.facebook.com/magiclantern.firmware) -
QuoteEric J. Russell
Yesterday at 1:55pm
Two Identical SDXC cards. One boots ML fine, the other puts my 700D in a brickatose state that can only be broken by ejecting the SD card and pulling the battery in and out, and even then the brickatosing SD card can't be in the slot or else the camera stays dead.
This probably sounds silly for everyone who has been using this software, but at the end of the installation instructions it would be great if you say that to get the menu you push the garbage can button after install.
The reason being that after watching a couple youtube videos I only saw the ML menu and just assumed it replaced the existing menu. I even went and looked at the user guide but while I saw a lot of information about features (and I admit I jumped around) nothing said to click the garbage can. The ML home page just seems to say "yes this sounds great, let me install"... nothing about pushing the garbage can button. This led me trying a few different builds and being a bit confused until I came across another video that explained it.
Recently had the same "Card cannot be accessed. Reinsert/change the card or format card with camera" message on my 650D (with Meike battery grip) twice.
Both times the camera was switched on and several photos had been taken already.
The SD card was a SanDisk 64 GB Extreme (90 MB/s) class 3.
On site there was nothing I could do. So I removed and locked the card, and replaced it with a 32 GB card without ML.
First time I could recover all photos with Recuva from Pirisoft (https://www.piriform.com/recuva). This is freeware.
After this I formatted the SD card with SD Card Formatter (https://www.sdcard.org/downloads/formatter_4/index.html). This little freeware program will restore the hidden partition on the SD card also in case it's lost.
Than I added ML to the SD card again.
Two weeks later it happened again. Same SD card.
This time I wasn't able to recover my photos, but a quick format first did the trick.
After this I could recover all photos with Recuva again.
Since the second 'crash' I haven't use ML anymore and use the 32 GB card only.
I'm still not sure what caused the error, but both times the card was in the camera, camera switched on and in use.
I've just compared focus step size while shooting tethered and using follow focus. Shooting from PC gives 3 times smaller steps, compared to ML follow focus. If I'm not mistaken, the step size was defined as the minimal step size from canon API. Maybe it's an important update or just another command for smaller steps. Is there any way to sniffer that command from PC or from ML? It may have a great value for macro photography.
600D + Tamron 60mm f/2.0
Software: CaptureOne 9.2 (with latest canon API, I believe)
ML Menu > Focus > Focus Settings > Step Size
> ML Menu > Focus > Focus Settings > Step Size
It's already set to 1.
P.S. I'll do some deeper testing later.
Defining Focus End Point works OK - it reports the same great number of steps as computer. But using left-right arrows (FF+/FF- to be sure) I can pass the same distance in a few clicks (3 times less steps). I guess something is wrong while reading stepsize/step_size variable. Or it just works how it was intended?
Upd
Finally I've solved the problem after resetting all CFn from canon menu. Strange, but setting AF to anything but halfshutter gives such unpredictable focus steps.
I'm looking for a 600D user to run a short test; I need it in order to be able to emulate the 600D firmware in QEMU.
Preferably somebody who can compile ML.
A1ex, I can help.
Thanks, here are the tests I need:
1. http://www.magiclantern.fm/forum/index.php?topic=5071.msg166799#msg166799 (0xFF0DA2E4 smemShowFix)
2. https://bitbucket.org/hudson/magic-lantern/pull-requests/741/minimal-target-fixes-hello-world/diff (just check if it boots)
3. compile the dm-spy-experiments branch with CONFIG_DEBUG_INTERCEPT_STARTUP=y, start the camera, go to Canon menu, navigate the menu a bit (doesn't matter where) and wait for dm.log to be saved. If needed, you can increase the delay before saving the log file (boot-hack.c, near line 580).
600D Tests
1: http://www.magiclantern.fm/forum/index.php?topic=5071.msg169195#msg169195
2: Booted
3: https://bitbucket.org/mk11174/1200d/downloads/DM.LOG
Thanks, I had some partial success (http://magiclantern.fm/forum/index.php?topic=2864.msg169223#msg169223) with the emulation.
QuoteRecently had the same "Card cannot be accessed. Reinsert/change the card or format card with camera" message on my 650D (with Meike battery grip) twice.
Both times the camera was switched on and several photos had been taken already.
The SD card was a SanDisk 64 GB Extreme (90 MB/s) class 3.
On site there was nothing I could do. So I removed and locked the card, and replaced it with a 32 GB card without ML.
First time I could recover all photos with Recuva from Pirisoft (https://www.piriform.com/recuva). This is freeware.
After this I formatted the SD card with SD Card Formatter (https://www.sdcard.org/downloads/formatter_4/index.html). This little freeware program will restore the hidden partition on the SD card also in case it's lost.
Than I added ML to the SD card again.
Two weeks later it happened again. Same SD card.
This time I wasn't able to recover my photos, but a quick format first did the trick.
After this I could recover all photos with Recuva again.
Since the second 'crash' I haven't use ML anymore and use the 32 GB card only.
I'm still not sure what caused the error, but both times the card was in the camera, camera switched on and in use.
Hey McDonald,
I had a similar problem a couple months ago. The key is to not use an SD card above 32 GB.
I had spent hours recovering the video files, that ended up being corrupted. I was able to use a software to repair the video clips, but this was a pain to figure out, however I was really thankful.
I've had a couple times where a 64 GB SD card has been corrupted with the T3i, and through another post found out 64 GB cards do not work well with the T3i and Auto Restart.
I realize you're using a T4i, but it might be related. Also, I used a battery grip. I'm wondering if a battery grip is the issue. Mine is Canon, yours is Meike, so it isn't a third party issue. I wonder if using external power like a V Mount instead of a battery grip would solve this. As rsmith02 stated in the other post, it might not even be Magic Lantern related. Anyways I just use 32 GB cards now. I hope this helps.
Here is a link to the other post about the same issue: http://www.magiclantern.fm/forum/index.php?topic=17271.msg167353#msg167353
If I can be of any other help please let me know. Thanks.
- Paul Harwood
600D is not compiling, as noted on the downloads page. I can compile, but don't have the skills to debug. This seem to be the issue:
../../src/raw.c: At top level:
../../src/raw.c:1510:26: error: 'PREFERRED_RAW_TYPE' undeclared here (not in a function)
static int lv_raw_type = PREFERRED_RAW_TYPE;
^
../../src/raw.c:1510:12: warning: 'lv_raw_type' defined but not used [-Wunused-variable]
static int lv_raw_type = PREFERRED_RAW_TYPE;
^
../../Makefile.filerules:23: recipe for target 'raw.o' failed
make: *** [raw.o] Error 1
Solved, next build will be fine.
Thanks, A1ex.
Did I install magic lantern correctly? A big thing I've read in all my research is that the camera will *not* turn on without an sd with ml files installed.
When I flashed this summer, the latest build was 2015 April.
I recently upgraded to a new sd card without magic lantern, and was surprised to see the camera would go on, and I know I have had access to the magic lantern menus, the firmware would show magic lantern, etc.
I have upgraded my firmware on both, and it is working, but I'm still wondering why it works without magic lantern files.
Quote from: lokael on September 13, 2016, 11:46:43 PM
A big thing I've read in all my research is that the camera will *not* turn on without an sd with ml files installed.
Wrong.
You need three things to make ML run
- Cam with "bootflag" set (will be done first time ML is installed)
- Bootable card
- ML files and directories.
If you have a non-bootable card ML will not start but Canon standard menu will work.
If you have a bootable card but no ML files on it -> Cam will get stuck and you will have to remove battery.
That's weird though, because it turned on fine, and my SD card did not have ML files on it.
Hi everyone.
This is my first forum post, though I've been using ML v2.3 on my 600d for a few years - mainly to shoot documentary b-roll and interviews.
It's been great - particularly the Magic Focus, peaking, audio levels, expanded ISO and white balance options - a million thanks ML team!
Hope someone can offer some advice:
Have there been any big video-making developments with the Nightly Builds which may be of use to me?
If so, which Nightly Build would you recommend?
I've tried reading the Build Log, Bug Tracker and Older Builds section, but unfortunately it doesn't make any sense to me.
Happy to learn how to translate lines like: "Merged in cleanup (pull request #751)" - if someone wants to help.
Otherwise be great just to know any specific video-function advantages of the newer builds for the 600d, compared to v2.3.
(Best would be if headphone monitoring has finally been cracked).
Thanks again!
Elliot
The last nightly build will be way more stable than v2.3.
A lot has changed since then (headphone monitoring, audio controls, etc...)
Best to try it out on a spare sd card, but I promise, you will not want to get back to v2.3 ;)
Does anyone know how to get ML to work on Canon Eos Rebel 3Ti with the latest firmware v1.0.3 ?
You will have to downgrade to v1.0.2.
Really need some help here, ML community. I just upgraded to Latest Build (2016-12-03 01:59) for Canon T3i, and I've seen other people voicing concern that they're getting an option for a shutter speed of 1/46 or 1/47 as an option by overriding the option of 1/50, but they want shutter speed 48 when shooting at 24fps. I'm set up for 24fps, but shutter speed (with or without override) is ONLY allowing me to choose 45 (or lower), or 50 (or higher no matter what I try to do. I was hoping to get as close to a shutter speed of the 180 degree 1/48 shutter speed. My older version of ML from a couple of years ago DOES have 1/48 shutter speed as an option. What is wrong with this newest Build Latest Build (2016-12-03 01:59) for Canon 600D/T3i? Or... what I am doing wrong? Please help. I should never have upgraded less than a week before a short film shoot, but I thought "why not?" Now I truly regret it. I cannot find a version now that provides 24fps and 1/48 shutter speed. I really need your feedback. Thank you all so much in advance. :-[
http://www.magiclantern.fm/forum/index.php?topic=1669
http://www.magiclantern.fm/forum/index.php?topic=5951.msg175579#msg175579
Quote from: BunkyJack on December 16, 2016, 05:44:21 PM
...My older version of ML from a couple of years ago DOES have 1/48 shutter speed as an option...
Maybe it never did? You can certainly roll back to an earlier build if you want:
https://builds.magiclantern.fm/600D-102-all-builds-changes.html
However, you'll be missing out on some of the latest features and bug fixes. The difference between 1/46, 1/48, 1/50 is insignificant. Also, the camera doesn't normally record at 24fps and digital cameras don't have 180 degree shutters but for the sake of argument:
24/1.001 = 23.976023976023976 - theoretical frame rate
23.976023976023976 * 2 = 47.952047952047952 - theoretical 180 degree shutter speed at theoretical frame rate
Let's say that the closest we can possibly split hairs is within 1/10 of a stop (which is actually quite ridiculous because shutter speeds are usually marked in 1-stop increments):
47.952047952047952 + (47.952047952047952/10) = 52.747252747252747
47.952047952047952 - (47.952047952047952/10) = 43.156843156843157
Basically, anything between 1/43 and 1/53 would be within tolerance of your theoretical 180 degree shutter.
Those very old ML versions (<= 2012) displayed the shutter speed using the APEX formula, and simply rounded to integer. When Canon shutter speed was set at 1/50, the value displayed by ML happened to be 1/48.
Since then, we have noticed the exact value of shutter speed is tweaked in movie mode, probably to avoid flicker. Some low-level details:
http://www.magiclantern.fm/forum/index.php?topic=16814.msg164058#msg164058
My second link points you to a feature (2013) that lets you adjust the shutter speed in very small increments (about 20 microseconds). This may be useful to avoid flicker in some cases (e.g. when filming certain monitors).
TLDR: the old version displayed 1/48, but the real speed was 1/50. The new one displays the real shutter speed AND it actually lets you fine-tune it to 1/48 (from menu).
www.youtube.com/watch?v=nn6fPHCEMuw
Testing the new 10 bit RAW Recording on Canon EOS 600D
Resolution: 1728x648 @23,97fps, 10bit RAW, ISO 100, (postprocess: RawTherapee, VirtualDub, Deshaker, Kdenlive)
Location: Karviná, CZ
Date: 17.12.2016
Original File:
https://ulozto.cz/!jqr4LccvsKqn/2016-12-17-karvina-10bit-raw-600d-mp4
Looks Awesome!
Enviado desde mi SM-G930F mediante Tapatalk
Who would have thunk that a 600D could actually be used to shoot 10 bit raw video, 1280 cinemascope (2:35), 24fps continuous.
Talk about blowing the stink off it. That crappy card writer can actually handle 10bit raw continuous.
This is next best thing to clean outs, in fact who cares about an 8 bit out stream if you can record 10 bit raw for 30mins. This camera has a niche again.
Load it up with focus peaks & zebras for great MF and wow. Not to mention you can program step focus points for marked focus pulls.
And yes it has a 3X lossless digital zoom without line skipping which becomes even more interesting with raw video, as it can be processed harder than H264.
At 12 bit raw, it can shoot 1280 cinemascope for about 30s. So probably for most shots this would be ok. Most folks cant tell 12bit raw from 14 bit raw anyway.
This is huge. The 600D is fighting obscurity rather nobly.
As this camera use to be a DSLR student/learner camera but was becoming less compelling every day.
However with its renewal into a 1280 cinemascope raw video camera, that gets you into raw, and at 1280 with a low-cost processing system.
One can recommend this camera again for newbies, who want to gain raw video experience.
Who would have thunk?
This should be hitting the unified build in the nightlies soon. Again wow.
When will ML support the latest version of the Canon firmware?
Perhaps foolishly I have just updated to camera firmware version 1.0.3, to discover that ML can no longer be installed on the camera!
I wonder how easy it is to downgrade the firmware to version 1.0.2, if I even dare to try it!
TIA for any advice/information.
Jeff
@honza123 - any info on your config?
I'm getting pretty bad frame skipping at 1728x648 23.976 10 bit with sound.
Are there any other specific config settings to get it stable?
The aspect Honza was using is 1:67, rather wide. He could only shoot 9s clips, which is limiting for most projects.
I would suggest a more versatile setting of 10 bit raw, 1280 @ 2:35 / 24fps, which shoots continuous.
This works nice with h264 720p /60 fps, 1.4x bitrate set, (shot flat) for slow motion shots.
The card writer cant support 1920 at any aspect. 1280 @ 2:35 / 24 fps is the sweet spot.
Add external lighting so you're within one stop of exposure, as 10bit raw after one stop of correction gets noisy in the shadows.
I see I'm not the only one who foolishly upgraded the firmware. I have used ML for some time and loved it, but after updating the Canon firmware to 1.0.3 I have no luck installing ML. Does anyone have some useful suggestion? We (apparently) cannot go back to Firmware 1.0.2 - the camera only accepts new firmware, and ML (upon attempting install) informs it was expecting 1.0.2 and that's it.
Are we not able to use ML with firmware 1.0.3?
Use EOS Utility 2.x to downgrade firmware. If not installed download and install EOS Digital Solution Software 29.1A.
1.0.2 is available via http://pel.hu/eoscard
PS: Can someone confirm Canon's firmware 1.0.3 blocking in-cam downgrade?
PPS: 650D in-cam downgrading from 1.0.5 to 1.0.4 without problems.
Thank you!
I was able to downgrade the EOS firmware (as per your link) to 1.0.2. The camera did not block this.
Then I extracted the latest nightly build - 2016Decv19.600D102.zip - to the root folder of a 64G card.
Reformatted the card.
Now my old 16 Gig card with ML worked again. I am mostly using the focus-dots feature, so this was good.
And after some ML Menu tweaking I got the 64 G card to display the focus dots.
GREAT !
Thanks again.
I've followed the installation instructions and I get no response from my T3i that the card even has ML copied to it. Any ideas?
I've verified that ML is on the card itself and yes I did format the card in camera beforehand. I've also verified that the T3i is on v1.0.2 firmware from Canon first.
Thoughts?
------------------------
DUH. Run firmware update. It's been a while. I had a T3i running ML as my fifth camera body for my photo business (extra video angle) and sold it last year. Immediately regretted it. So I bought another one this holiday season (used from a FB group - barely used!) and I'm back running ML.
Thanks to Walter Schulz and Visionears!
Firmware now downgraded to 1.0.2 and updated ML now installed and working again after following the instructions in Walter's post.
:) :) :)
Hi! :)
First, sorry for my grammar mistakes, im not good at this language. :(
I was tried a few version of ML, but, i don't have audio meters :( Why? Can I install it? I can't find this in ML menu, nowhere.
I need this, please, help :(
1. Audio has to be enabled in Canon menu
2. In movie mode press INFO button until ML screen appears. If using MLV_REC.MO you have to load MLV_SND.MO, too.
Thanks! :)
600D is still what it was sold to me as.
"A great camera to learn video & photography on"
1. twisty-flex lcd screen for great angles & has sensor similar size to a red-one
2. Shoots 1280 10 bit raw, anamorphic virtually continuous, or higher res with fps variable rate set low for static shots.
3. Shoots H264 60 fps 1280 FHD, for slo-mo.,
4. Shoots H264 at 1.4X bit rate over sample (great for fine detail edging & blacks)
5. Shoots H264 with custom pics, like flat, to increase DR. Did I mention 10/12bit raw video that also increase DR.
*** And if you think 600D H264 sucks, go to vimeo and watch some Kendy Ty videos (shot on the 550D no less). Then recant ***
6. With ML can shoot 4k timelapse video.
7. With ML - Focus peaks & Zebras even Magic Zoom PIP for best focus info., crucial for manual focus helpful for AF.
8. With ML - AW to sample (small sample in pic) or dial in Temp. manually these blow away Canon s/w, and did I mention with global write on, you can record with an anamorphic black bars on viewer for proper framing.
9. With ML - Can program follow focus points. A poor mans focus pulls.
10. Lossless 3X zoom, that has no line skipping, made even more potent in post with 10/12 bit raw video. Not bad for shooting brick walls, tiles, wires, and zebras.
These are a crap load of useful stuff any photography & video student would want to play around with.
And with 1280 anamorphic raw video, guess what its actually a relevant inet cam!!!
So what is 1280p HD good for? V-Blogging, and creating portfolio video clips.
With 14 bit raw, it did not even support HD, so its raw video use was near nil.
Now with 1280 anamorphic video support it shakes the dust off, and as a great learning camera
its fully delivering on its potential.
Can anyone verify that lua loads successfully on the 600D? I get memory errors. Have tried a variety of nightlies back to 2016Apr22, and get the same behavior on all of them. More details later, if there is interest.
You can try the Latest Lua Updates build from here: https://builds.magiclantern.fm/experiments.html
I can verify that the experimental build boots successfully. Don't have time to test further tonight. Should the Features page be changed to indicate Lua as unavailable for the 600D until these get pushed?
Lua is in the regular nightly builds but the experimental builds have the latest changes. Please report any issues.
Sent from my iPhone using Tapatalk
Done.
Hey guys, I haven't been messing around with ML for a great while now, I just decided to blow th dust off my 600D and get the latest ML release. So far so good, but there is one thing about the new releases that really bug me: every time I hit the trashbin button and enter the ML menu, Canon's own menu pops up for a really short time. It's not a great deal breaker for me, never the less it's annoying to see every time I enter the menu.
How long has this been around? Would it be realy difficult to get rid of it?
Also, congrats with the 10/12 bit raw guys!
Quote from: Satis on February 05, 2017, 09:08:42 AM
How long has this been around? Would it be realy difficult to get rid of it?
Since May 2011. There was no ML for 600D back then.
Feel free to reverse engineer this issue. You'll have to find a way to prevent Canon menu from getting displayed - that's all. The current approach is to trigger a series of very quick redraws of ML menu (codenamed "redraw flood"), hoping it will mask Canon menu quickly.
To see why Canon menu is used, set GUIMODE_ML_MENU to 0 in consts.h to disable it, and see what happens.
QuoteWho would have thunk that a 600D could actually be used to shoot 10 bit raw video, 1280 cinemascope (2:35), 24fps continuous.
So let me get this straight ! The 600D / T3i can now shoot continuously 1280x??? 10 bit raw ?
Can someone please show me how to get this on 600D ? I have looked on various parts of the forum but nothing clear to me at this point.
Top of page -> Downloads
Downloads (drop down menu) -> Experiments -> 10/12-bit RAW video
Select download for 600D.
Hello, i have a 64 GB memory and my Firmware is 1.0.3 can i still download and install it?
You'll have to downgrade to 1.0.2 first before you install ML.
Hi everyone,
Recording MLV RAW, I want to get a shutter speed of 1/50 with 24fps. Right now I'm using FPS override, but the 'shutter 'option in the Expo menu is locked. How can I do this?
Thank you.
Firmware 1.0.3
Did Canon Post what was changed or updated in the new firmware? All I saw on the UK site was a download link. No explanation while upgrading their desktop software & Utilities.
I'm not upgrading mine... Always look in the forums first before doing anything!
Just a FYI, Canon Just leave a good thing alone.
-Steve
I've been using 600d as a B camera for a few years now but for the past several months have experienced a huge problem with it. After insert my SD card to my card reader I get the popup windows "you need to format the disk before you can use it". I've lost a lot of footage due to this issue. I don't have this issue with my used SD or CF cars on my 5d3.
Any help?
You have to wait for proper shutdown and wait a few seconds *after* opening card door before removing card. The cam will access the card right after opening the lid. If you are too hasty you will likely damage the card.
And you can always try to use data recovery tools for troubled cards.
If you have only one SD-card I recommend to replace it now (if proper handling doesn't solve your issue).
If you believe the same card behaves well on 5D3, but not on 600D, you'll have to do a controlled experiment.
Step 1: Find a way to reproduce. Even if it's something like this (just an example): record video clips until the card is full, download the clips on PC, format or delete, repeat 10 times, and at least one of those attempts is unsuccessful. The key is to find a sequence of actions that gives the error every time you try (even if that sequence requires recording many test videos or whatever).
Step 2: Run the test sequence on 5D3 (with SD only).
Step 3: If your test sequence does not include any ML-specific features (such as raw video), run it without ML as well.
Step 4: Trying on a different 600D, a different card reader, or a different USB cable or port may be helpful (to exclude hardware issues such as weak contacts in the SD slot).
The above steps should be helpful for any other issue hard to narrow down.
Hi, I had the january version of magic lantern and updated it with the new (just discovered) 10 bit raw version, but my screen is flashing. Without sd card camera is ok so it should be a ml bug, even when I restored my settings to default (both canon and ml) I got no changes. Am I the only with this problem? Can I fix it and start using raw to have a bit more quality over shitty h264?
hi everyone,
Been using ML for years now. I recently got a few new SD cards. Installed ML fine. I cannot for the life of me, though, find the suggested settings (I believe bit rate cbr was adjusted) for avoiding the "your video recording has been stopped automatically." I have the autostart enabled, but I remember adjusting some settings to get avoid the error. I have a sandisk class 10 card, etc. Anyway, I have searched and cannot find anything about specific settings.
Thank you.
Recording will stop if buffer is full. There is no way to bypass hardware limits.
6D is able to use about 40 MByte/s recording rate with fast cards. 600D interface has only half the bandwidth ... go figure.
Class 10 just says the card is good for 10 MByte/s continuous recording.
Modules tab -> bench.mo ON -> restart cam in photo mode-> Debug tab -> Benchmarks -> Card benchmarks -> Quick R/W benchmark (1 min)
thanks, I could have sworn that there was a way to adjust settings so the buffer did not fill as frequently. I might be wrong or the changes I did really didn't do anything.
If you adjust settings to minimize data traffic you have it (if using RAW). Bit rate manipulation (CBR) is for H.264 recording only. And for your cam highest write rate for H.264 should be below 6 MByte/s (with default bit rate CBR = 1).
So guys one question, how much resolution can handle now 600d with 10bit raw, crop 3x3 and loseless compression at 24fps?
http://rbrune.github.io/mlraw
Don't expect to run 21 MByte/s write speed recording RAW/MLV. If you don't want to run on the edge stay below.
but the loseless option arent
Disclaimer: You can't predict the efficiency of this compression algorithm for a random scene.
Use 2/3 compression rate (3 MByte uncompressed -> 2 MByte compressed) with more than a grain of salt.
The rate I recommend is 720p @2:35, 24fps, 10 bit raw. Its 19.6 MB/s, so its continuous.
That is rather excellent for this camera, and is very fine setting for Inet delivery (assume you deliver at 2:39).
If you want better raw, you need a higher card write speed than 21 MB/s max. really 5DMkII or 5DMkIII would do it.
Hi all, new to Magic Lantern..
Have a Canon 600D and would like to know how I can only make this software under a certain setting. i.e. Only have ML with bracketing options only in the "M" mode of the camera which will allow me to use the "A+" setting for non bracketing option.
Thanks
Hi guys,
Sorry if this is a real basic question, but I've been trying find out the exact steps to work with a new SD card on a cam with ML already.
The previous owner was using ML, so it's already on the camera working fine. I've got a new 64GB SD card, and I'm wondering what steps I need to take to start using ML myself...
Am I correct in assuming this is what I need to do?
1: format card on camera
2: install ML on SD card from PC
3: put card in camera and enjoy
Am I missing some crucial step here...?
Thanks for helping me not brick my camera...!
Top of page -> User Guide -> Install Guide
Grids do not show up on T3i on latest build.
I have been using ML for a while now, I also use a lot of older manual lenses on the camera. I have noticed that when I have the AF mode set to "AI Servo" when using an auto focus lens and then change the lens to a older manual focus one (with a focus confirm chip) ML seems to turn on "Trap Focus". Is this normal or should I report it as a "Bug"?
Dave
No silent module in latest build?
Hey guys I am having problems with the audio meters in the Canon 600D. I have an external preamp/xlr adapter on top of my camera. I really just want accurate audio meters on screen so I can bypass the internal volume control. But it does not show any signal at all. I have checked in the Canon menu and I am definitely getting a signal from my Saramonic SR-PAX1 into the canon. It is just not registering in ML's audio metering system. I do not want to control the volume digitally from ML but from the analogue knobs on the preamp. Anything I can do? Or just a bug in the nightly build?
I find the levels often show up low I can't rely on them. If you jack it up to +24 or higher they may be clearer but the audio will be very noisy so I wouldn't record like that.
The meters also aren't active upon power on. You either need to record or open the ML menu (trashcan) and exit for them to wake up and start working.
Hi I find that I have to go into the normal canon menu and tweak the sound level there then when I come out to live view the level metering is working but it is so un reliable I am un installing ML. Also I went over 60 degrees heat today I was worried as it showed up red on screen. Is that dangerous?
If the leveling worked well adn I didnt have heating issue would leave on my camera but seems too risky as I am using it for professional jobs and do not want any risk.
I don't see any reason to uninstall ML. If you don't want to see the ML menus, you can just hit the info button. Doesn't the Canon default to no audio meters while recording? That's worse. I really value the histogram and the focus box for shooting video.
The heating isn't related to ML- your camera heats up in liveview mode. I wouldn't worry about it at all. I've shot for fairly long days with no problems. If the camera overheats it will shut off, ML or not.
Quote from: Disease on October 13, 2017, 02:34:00 PM
Hi I find that I have to go into the normal canon menu and tweak the sound level there then when I come out to live view the level metering is working but it is so un reliable [...]
Did a quick test, comparing ML audio meters to Canon's (5D3):
(http://a1ex.magiclantern.fm/bleeding-edge/audio/audio-meters-canon.png) (http://a1ex.magiclantern.fm/bleeding-edge/audio/audio-meters-ml.png)
Unable to see what's wrong with them.
Additionally, a long time ago, a 60D user compared ML audio meters with a calibrated reference and found nothing wrong:
QuoteA -12dB tone recorded with my 60D (only the tip of the meters was yellow) resulted in a perfect -12dB tone. I checked all signals on our calibrated system.
Therefore, if you are looking for help, it's your duty to document the issue properly (https://www.chiark.greenend.org.uk/~sgtatham/bugs.html).
Hi a1ex, I have no idea how to determine whether the meters are accurately recording volume so I don't think I can be of help there (I have no known reference). It may be fine.
I can easily demonstrate that the audio meters do not engage until you hit record or enter the ML menus and leave, playback a video, etc. I can repeat it each time I turn my camera off to on. After you do that you can see levels while non-recording which is what I want to do (want to nail settings before starting to record an interview for example).
The Canon audio menus are set to manual, levels 6 notches or so above 0, and ML menus have audio override on and levels +24. To keep things simple I'm just using the built-in mic. Latest 600D build of ML installed 2017-10-04.
Is that how the camera is supposed to work or a bug, and what sort of documentation is useful (a video of ML's behavior?)
The link to bug reporting is too general for me to do much with. Of course specificity is good and repeatability moves the burden from the programmer to the user.
Yes, a video would be nice.
Unfortunately, the audio side of 600D is different from all other modes, so it requires a 600D owner with programming skills to look into it. Also check the new-sound-system branch, maybe the issue is fixed there. I'm afraid diagnosing this issue without a camera is going to be more difficult than asking a tester whether it works.
Maybe if QEMU will ever be able to emulate the audio chip and Canon's LiveView. Docs are available, manpower is always welcome.
Hi I am not able to test in such a way but there is definitely a bug and it even states on the ML page that audio features for the 600D (not 60D) are unavailable. I wonder how you got to show audio levels natively in the canon display?? Thats all I wanted from ML anyway so if that is already there I am moaning about nothing.
Quote from: Disease on October 16, 2017, 11:57:38 PM
it even states on the ML page that audio features for the 600D (not 60D) are unavailable.
What? Where? Because:
(https://img3.picload.org/image/dgpocacl/audio600.png)
i cant find it :(
Can you show audio metering on live view overlay without having ML installed?
Wait a moment! You are actually asking how to use an ML feature without having ML installed?
If so: Please stop trolling here and contact Canon services.
If not: Stop trolling anyway.
:o I think he/she is confused.
So I just put in a non ML card and unsurprisingly, no, there are no audio meters in live view mode on the 600D/T3i. You need to enable Magic Lantern for that. ML works very well on the T3i so I recommend keeping it.
Dear a1ex, sorry it took a few days but I finally had a chance to do a quick test video to show the issue with audio meters "falling asleep" on the T3i.
Here's a link to a video I made to demonsrate: https://www.dropbox.com/s/fxmjruhdixcaerp/C0006.MP4?dl=0
My version is 1.0.3 and it says to go to 1.0.2.for the initial download. I do notice the article is dated 2015. is this correct and I have to go back to an earlier versuion?
Install instructions in download page are up to date.
Quote from: Walter Schulz on October 28, 2017, 09:38:52 AM
Install instructions in download page are up to date.
There's any changelog for ML pages? This (http://builds.magiclantern.fm/600D-102.html#install) is the page? Also, can't the admin self-host the original canon firmware link, instead of pointing to "pel.hu"? I don't find it very safe to point to a unknow website. The owner could just replace the zip with a exploit and *uck everyone. If for legal reasons it can't be made, at least mirror it in another server and post the SHA256 hash...
edit to add: it's running a old Apache with bad SSL, btw.
@bpv5P - Yes, it is strange that we're directed to Pelican's website for old firmware versions but he's got the most complete collection. Canon takes down their old updates from the official support pages. I was on a mission to get all the ML supported cameras ported to the most recent Canon firmware updates but that seems to be a very low priority project. It isn't all that difficult and a good project when you get past compiling, which is very easy to do these days.
If you want to try to port a firmware update:
http://www.magiclantern.fm/forum/index.php?topic=19417.0
Easiest way to setup a Mac development environment:
http://www.magiclantern.fm/forum/index.php?topic=16012.0
Cygwin on Windows is also easy:
http://www.magiclantern.fm/forum/index.php?topic=15894.0
Though a more complete solution is to do it in the new Windows 10 Ubuntu environment:
http://www.magiclantern.fm/forum/index.php?topic=20214.0
Most of the time I simply ignore meta discussions and ad hominem. Let's make an exception here:
@bpv5P: I have to say that I'm not happy with your view on user pelican who is around us for more than 5 years. He not only offers a quite complete archive for firmware taken from Canon's web. He developed EOScard utility which for a very long time was the most convienient way to get ML running on cards >32 GB for Windows users. And it was standard program for getting ML v2.3 installed for Windows users. For free, without nagging ads.
Instead of going into sinister plots a regular may came up with (You're aware this kind of argument does apply to the devs, contributors, anyone offering a link, too?) your post would might get a warmer welcome (at least by me) sticking to the very risks involved in non-redundant structures and unsecure web hosting. I'm fine with pointing at pelican's householding duties. I'm fine with all ideas trying to get rid of single points of failure.
BTW: There are some prominent examples where big web based services failed, their user databases got public or - like recent - got unusable by changing terms of use.
Quote from: dfort on October 28, 2017, 10:07:21 PM
@bpv5P - Yes, it is strange that we're directed to Pelican's website for old firmware versions but he's got the most complete collection.
That's the point, why not mirror the files?
Quote from: Walter Schulz on October 28, 2017, 10:49:41 PM
@bpv5P: I have to say that I'm not happy with your view on user pelican who is around us for more than 5 years.
I don't have a bad view of "pelican" specifically, that's just my default mode.
Quote
You're aware this kind of argument does apply to the devs, contributors, anyone offering a link, too?
Yes, but the code is open source, the website don't runs too many nasty things as the pelican website and it's not distributing a compressed file with unknow binary. All ML builds has the code, changelog and (now) tests (on QEMU). We can compile and check for ourselves. There's a big difference between the two cases.
Quote
I'm fine with all ideas trying to get rid of single points of failure.
Decentralization without security/safety is for dummies.
You're trying to apply a good concept with the very wrong implementation.
Quote
BTW: There are some prominent examples where big web based services failed, their user databases got public or - like recent - got unusable by changing terms of use.
This is a admin issue. Database should always be encrypted. (edit: and a backup of this database)
Quote from: bpv5P on October 29, 2017, 01:59:45 AM
why not mirror the files?
It is one thing if an individual does this and another thing when an open source project hosts these files which are closed source and contain Canon's copyrighted intellectual property. It is probably best not to go there.
Quote from: rsmith02 on October 14, 2017, 02:21:15 PM
I can easily demonstrate that the audio meters do not engage until you hit record or enter the ML menus and leave, playback a video, etc. I can repeat it each time I turn my camera off to on. After you do that you can see levels while non-recording which is what I want to do (want to nail settings before starting to record an interview for example).
...
The video you posted does indeed show the bug.
I recently spent some time straighten out a hack that used the address for StopASIFDMAADC in SoundDevShutDownIn on several cameras (http://www.magiclantern.fm/forum/index.php?topic=20597.0). It turned out a bit more complicated that I anticipated.
Maybe the bug you're exeriencing is related to this. The 600D doesn't have StopASIFDMAADC in stubs.S but I just looked at a disassembly and the camera does in fact have it. This is needed on for the audio meters to work properly on some cameras and maybe the 600D is one of them. On my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) you'll find a test build named StopASIFDMAADC.2017Oct28.600D102.zip. Please give it a try and report back. Of course other 600D users are also welcome to join in the test. Make sure you understand how to reproduce the bug that is clearly illustrated in the video.
https://www.dropbox.com/s/fxmjruhdixcaerp/C0006.MP4?dl=0
Seems I overlooked an important detail on rsmith02's video, the camera is recording H.264 and not mlv_rec/mlv_snd.
Ok--so there's something else that might fix this issue.
src/audio-common.c
/* some models require the audio to be enabled using audio_configure() */
#if defined(CONFIG_650D) || defined(CONFIG_700D) || defined(CONFIG_EOSM)
int reconfig_audio = 0; // Needed to turn on Audio IC at boot, maybe neeed for 100D
#else
int reconfig_audio = 1;
#endif
Let's see if the 600D needs this. Test build "turn_on_Audio_IC_at_boot.2017Oct29.600D102.zip" on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
I'd still like to get feedback on the test build mentioned on my previous post. Start with the current nightly build, turn on only mlv_rec and mlv_snd. Check to see if the audio meters are working. Record a short clip, check the meters. Do this at least 4 times and see if the audio meters continue to function. On the 650D and 700D there was a problem where the audio meters stopped working after recording a clip. (Sort of like the opposite of the H.264 bug on the 600D.) If there is a problem with the current nightly build try the "StopASIFDMAADC.2017Oct28.600D102.zip" test build that I posted.
By the way, I found several of the missing ASIF stubs for the 600D. I created a dummy pull request if anyone wants to follow along:
https://bitbucket.org/daniel_fort/magic-lantern/pull-requests/10/600d-audio-meters-issue/diff
Hi dfort, sorry to not clarify but yes I was just using the standard H.264 camera features. The last time I tried ML raw was before there was sound support ; )
So I downloaded an installed the fix file and am happy to report audio meters now work when you go into video mode. I switched into the mode from photo modes and from power off and it works fine. I recorded 5 clips in a row (few seconds each) and the meters stayed live. If I notice anything odd during my course of normal use I will report back but I think this fixes it. Is there anything else in H.264 mode I can test? (not sure what the other stubs are for- happy to do tests with a mic, etc. if it is useful).
I attempted to help troubleshoot ML RAW but do not know enough about how it it supposed to work to be of much help.
So I used the last standard nightly build (not a dfort fixed file), loaded the raw and sound modules, enabled raw video in the menu, enabled sound. I set resolution to 960x540 16x9. I turned global draw on.
In live view there is a preview window in the center surrounded by a black box (because this is a crop mode?) While there are meters at the top they are not active while not recording.
I hit record, it says "busy ... please wait". A counter runs of seconds elapsed. The video cam icon is yellow. I'm recording at about 20mb/s. The audio meters are gone as are the histogram and everything else. If I try to change aperture, etc. it just says busy. After 2 minutes I give up, hit the record button to turn it off and now audio meters are registering. I realized 16x9 may not be continuous so I changed the aspect ratio, tried again and also only have meters after I exit recording. Aperture can't be changed using physical controls while recording though ISO can (after a delay). It says busy and is barely responsive.
Second test and again no meters after power on.
I swapped cards to the one with the "turn on" H.264 fix I reported on earlier. I did the same procedure to enable raw and MLV sound. Now there are meters before recording! Now when I record I have audio meters up top but also the full magic lantern display (histogram, settings at bottom). I can also change aperture while recording and the black mask stays active during recording. It no longer says "busy" and is responsive to starting and stopping movie recording now.
I have not tested the stop build as the turn on build seems to be what the camera needs?
Movie tab -> RAW video (MLV) -> [Q] -> Global Draw ON
Off by default ...
And there is a third option to surpress GD in Display tab -> Clear overlays. Off by default, so this one should be fine.
Thanks Walter. I think I must have accidentally had GD off the first time I tested the 10.4 build. With it on I have meters/full functionality in this build, too.
Re: sound, there are no meters in liveview on initial power on with MLV raw/MLV sound modules enabled. When you record a clip they wake up. When you stop recording the meters work in standby again (same behavior as H.264). I recorded 5 raw clips and upon return to standby mode each time the meters stayed live. They worked while recording.
I think the "turn on" fix fixes audio meters for both raw and H.264 with the 600D.
Thanks for the testing @rsmith02 - made a pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/877/600d-audio-meters-fix/diff) and posted a new test build on my Bitbucket downloads page (http://bitbucket%20downloads%20page). Please make sure it still works and feel free to approve and/or comment on the pull request.
Hello, tested the latest version and it worked fine with H.264 and RAW. I got meters before, during and after recordings with both.
Forgive my ignorance but as I didn't see how to comment on a pull request so I wasn't able to. A1ex is listed as the reviewer.
To date I've just been a ML user/forum commenter.
My Canon 600 is firmware version 1.0.3 but magic Lantern instructions for installation says I need 1.0.2. Is this true and do I need to go back to this earlier version? Also will I destroy the installation if at a later date I go to 1.0.3 or 1.0.4 if a later version is brought out? I need to know this for re-assurance before I proceed. Thanks.
No worries, the changes were merged and will soon be available on the nightly build. I'll take my test build down when I see a new one is available on the download page (https://builds.magiclantern.fm/600D-102.html).
Excellent, that's good to hear.
I'll be away from my camera for a few weeks but would be happy to test other features for the 600D when I return.
Overall ML for the 600D is stable and mature so maybe there's no need, but it is a standing offer as ML has helped me so much.
Can someone please give me a little advice on audio settings...
When using the internal mic, whats the wisdom on getting the best balance between Analogue Gain and Mic Boost for a given sound level?
UPDATE:
After a little trial and error here's the gain structure I've settled on.
Obviously avoid any 'Digital Gain'....
Analog Gain - around +6db
Mic Boost - around +20db
A decent enough noise floor without being undersensitive with the built in mic, works ok for a mid-level wireless pack system too (Boya WM6) cranked up to level 29 (of 32) on both the body pack transmitter and the receiver also.
Lav mic placed at mid chest position.
Wind Filter - DC = On High Pass = On HPF2 Cutoff Hz = 130 takes care of breathy bursts ok for me.
Headphone monitoring works fine, best to use a headphone amp such as something portable in the Fiio range.
Hi guys,
I can not get my 600d with san disk ultra 64GB 80MB/s exfat and latest experimental build to run continuously in 10 bit raw, 1280 @ 2:35 / 24fps mode with sound. Recording stops after 10-12 seconds.
Is there something special I should be aware of?
Thanks.
Quote from: xaled on November 04, 2017, 10:06:24 PM
Hi guys,
I can not get my 600d with san disk ultra 64GB 80MB/s exfat and latest experimental build to run continuously in 10 bit raw, 1280 @ 2:35 / 24fps mode with sound. Recording stops after 10-12 seconds.
Is there something special I should be aware of?
Thanks.
The maximum speed of 600D is about 25MB/s. That's the bus interface limitation. You can test your card using the benchmark tool inside ML.
You can probably stretch some more seconds disabling Global Draw (using HacKeD preview on MLV menu) and disabling sound rec (use external recorder).
Quote from: bpv5P on November 04, 2017, 11:36:04 PM
The maximum speed of 600D is about 25MB/s. That's the bus interface limitation. You can test your card using the benchmark tool inside ML.
You can probably stretch some more seconds disabling Global Draw (using HacKeD preview on MLV menu) and disabling sound rec (use external recorder).
thanks for the benchmark tool tip!
I was under impression from this posts:
https://www.magiclantern.fm/forum/index.php?topic=15360.msg178287#msg178287
https://www.magiclantern.fm/forum/index.php?topic=15360.msg176951#msg176951
that 600D can do more then I'm getting now.
So what is the highest continuous resolution you get from 600D with 10bits?
What resolution are you using exactly? Doesn't ML estimate the number of frames you'll get at different resolutions?
For me, I wasn't getting write speeds much over 20mb/s so do the math to see what resolution and bit depth will keep you under that.
Quote from: xaled on November 05, 2017, 08:21:14 PM
So what is the highest continuous resolution you get from 600D with 10bits?
Sorry for the late reply...
On a SDXC Toshiba Exceria card, the speed is about 19.5 MB/s (according to the quick benchmark - global draw off).
So, the maximum resolution for continuos recording, in 16:9, is 960x540 10bpp.
On 2.50:1 aspect ratio, it's possible to record 1280x512 10bpp continuous.
I don't advice you to record above 640 ISO. Try to stay bellow 400.
I did a comercial project using MLV on 600D, it went not so well, although the I could finish the work and the cliend liked it.
If you want to know how MLV perform, compared to x264, on 600D I would say: try it yourself. Sometimes you'll get better results from a upscaled MLV, other times (especially at night) you will get very bad results.
If you want seriously experiment with MLV, try some camera with CompactFlash support (50D, for example).
Quote from: bpv5P on November 07, 2017, 07:51:44 AM
If you want seriously experiment with MLV, try some camera with CompactFlash support (50D, for example).
I strongly recommend the EOS 7D for serious MLV work. This is a solidly built machine, very reliable and can be obtained at a very reasonable price used. At 14-bit and 1728x972 resolution, MLV quality with sound is fantastic (continuous recording), also at 10-bit with sound in the 5x crop mode where resolutions of 2496x1200 are possible! Due to the fast CF card write speed, (mine writes at 90 MB/s) and the excellent battery life this body is second best after the 5DMkIII for ML work.
@ xaled
IDA_ML is right in saying that the 7D is perhaps the best option in terms of price/versatility, the fast cf write speed is really what sets this cam apart.
However, (at least without sound, not sure about sound recording) 1280 x 544 @ 2.35:1 is possible on a 600D, continous recording in 10bit. I shot this music video https://www.youtube.com/watch?v=pHs1wI6hG3c completely on a 600D, at the resolution and ratio mentioned above.
Your problem is the card. The Sandisk Ultra does 80Mbit/s READ speed, but not WRITE. Both of my golden Sandisk Extreme can do 1280x544 continous. This, however, is the absolut max on a 600D at the moment.
Hope that helps,
Dave
Hey guys,
Have a slightly older build of ML on my 600D and was wondering if the continuous video shooting (ie start new recording when reaching gb limit/over heating) still has one second gap in between files?
I shot a gig with my 600D and 700D for over 30 mins and noticed the 700D has no gap between recordings, which I was amazed by! So just wondering if that has been looked at for 600D?
I say it every time but the work you guys do is phenomenal. Thanks again!
Hi, i have firmware 1.0.3.
Is there a way to downgrade, so I can use Magic Lantern?
Use https://bitbucket.org/daniel_fort/magic-lantern/downloads/ until this problem is solved.
thanks!
Hi guys I'm doing some youtube videos and I would like to do more than 12 minutes clips, what settings should I use? Is ML usefull for that?
Thanks!
P.S I got a kiss5 it's ok? what firmware should I install before mL?
http://wiki.magiclantern.fm/userguide#bit_rate
Hello,
I played the last ML-firmware from 07th December 2017 up.
My EOS 600D gets too hot (over 50 ° C) after only 2 minutes.
The camera is about 10°C warmer than the ML-firmware
from the 24th of November 2017.
I came across it on the 24th of November because it was downloaded by many users.
I'm back on the ML-FW on November 24th
Are you able to reproduce this effect?
Setting ML to default doesn't fix it?
I could give it a try by telling me what to do.
Lately, I've taken many pictures with long exposure with ISO160.
I did not do anything else except using the latest ML.
Which information would be helpful?
I would play the new ML for it again ....
We are also happy to talk by PM and in German and publish the solution in English here
regards
GerdmitPferd
Ich kann Dir nicht erzählen, was Du zu tun hast. Die Info, dass mit dem neuen Build die Kamera schneller warm wird, kam von Dir, nicht von mir. Also kannst nur Du erklären, unter welchen Bedingungen die Kamera diesen Effekt zeigt und ob das mit älteren Builds ebenfalls eintritt.
Falls der Effekt nicht reproduzierbar ist, haben die Entwickler nichts in der Hand, dem Fehler auf die Spur zu kommen.
Du kannst ML auf der Karte einfach überschreiben. Nimm die Zip, entpacke sie und überschreibe alles im ML-Verzeichnis und ebenso die Autoexec.bin.
I used ML several years ago when I first got my T3i. I went to use it several weeks ago after a LONG hiatus and the card wouldn't load. So I'm looking for a new build. The most current nightly build shows 2 tests failed. Now, I'm not sure those test are important--or are they? Is there a previous build that passes all the tests that maybe I should use?
And lastly, am I posting this in the correct forum? :-\
Thanks for the help
Bill W
I believe the lua_fix build should pass all these tests, but didn't run them yet. These tests are just scratching the surface though - only 5-6 features out of a few hundreds.
This build has some major changes in the backend, and I hope they are in the good direction, but I've barely tested a tiny percentage of them (mostly on 5D3 and 60D). From the feedback received so far, I'm currently unable to judge the status of this build, sorry.
BTW - to see what these tests do, go to QEMU-nightly-tests (http://builds.magiclantern.fm/jenkins/view/QEMU/job/QEMU-nightly-tests/382/artifact/qemu/magiclantern-Nightly.2017Dec07.600D102/) and watch the gif files (todo: I should link them in the main page). For the failed tests, look at some other model to see how they should look like. Feel free to repeat these tests on actual hardware and report any differences.
Quote from: gerdmitpferd on December 10, 2017, 02:33:20 PM
I could give it a try by telling me what to do.
Lately, I've taken many pictures with long exposure with ISO160.
I did not do anything else except using the latest ML.
Which information would be helpful?
I would play the new ML for it again ....
We are also happy to talk by PM and in German and publish the solution in English here
regards
GerdmitPferd
My problem with the Temparatur, which incidentally right after switching on, has been done.
I installed the latest LUA for the 600D.
It works ok for me.
https://builds.magiclantern.fm/jenkins/job/lua_fix/427/artifact/platform/600D.102/magiclantern-lua_fix.2017Dec16.600D102.zip/
@ Walter Schulz
I thought that maybe you can debug something. To limit errors
Proceeded after exclusion, ... what did I do when it happened was not feasible.
I meant it friendly
regards
GerdmitPferd
i am version 1.0.3 on my 600d. Can I still download ML although it says 1.0.2?
Hi everyone,
I am new to the forum - couldn't find the right thread to ask this question - My 600D has been acting weird for the past few days - it wouldn't turn on ! I tried to remove the battery and SD card , insert them back and try again - sometimes it worked and sometimes it didn't.
Now, my camera just won't turn on and whenever I try to remove the battery, a red light blinks - that's all. I checked my camera with another good battery (my friend's), but the camera won't turn on.
Any guidance will be really helpful ! :)
Remove battery, remove card.
Insert battery. Do *not* insert card.
Turn on cam. Results?
I tried the operations that you had asked me to do! Not working :(
( I didn't have the camera battery with me , so I couldn't test it earlier. When I got it back, i inserted the battery back into the camera, and it started working. It was fine for 2 days.
Now its not working :(
Backup autoexec.bin located on ML card. Copy Portable Display Test autoexec.bin (https://www.magiclantern.fm/forum/index.php?topic=2296.msg8815#msg8815) to card.
- Remove battery
- Insert card
- Insert battery
Results?
ML - I don't have Magic Lantern installed on the camera. :(
How do I proceed ?
Quote from: Walter Schulz on December 01, 2017, 02:41:43 PM
Use https://bitbucket.org/daniel_fort/magic-lantern/downloads/ until this problem is solved.
I can't find any version for 600D listed on your page ...where is it? (the only available file for 600D is "firmware for tester") Should I choose a build for a different model,which one in case?
I hope to find a solution to my issue with that, because....
...In the last days I have installed (and reinstalled) several times, the following packages, but no luck: each one of them it caused some serious issue ( camera hangs, modules won't load, module errors, memory errors, script errors,unusable video preview...), so that I had to give up using those latest ML 600D N.B.
magiclantern-raw_video_10bit_12bit.2017Dec18.600D102
magiclantern-Nightly.2017Dec07.600D102
magiclantern-lua_fix.2017Dec23.600D102
enGlPb+uLUA_FIX)
d62nh6VR*
tniyhfWA*
(* Those last two are just the names of the zips when downloaded, following a thread in some ML forum board).
I used ML from 2013 especially for photo (and then left it for more than 1 year, and now I'm back to experiment with video) and I never had so many issues have it running, I'm now quite confused: is it there a more stable Build somewhere that I've missed, or a more reliable build is coming out soon so would be better to wait?
solution or not I'am amazed anyway for the genius technicians and coders behind the ML project, I'am learning so much.
Without documenting the issues properly, there is no "more reliable build coming out soon" (in particular, not regarding the above issues).
Why? Because nobody else reported anything like this on the recent builds.
In particular, I'm waiting for feedback on the lua_fix builds (http://www.magiclantern.fm/forum/index.php?topic=14828.msg194706#msg194706), to decide whether to merge them into mainline, or wait. Before your report, I would have assumed things are fine on 600D, fix the remaining nitpicks for other models (not related to any of your issues), and merge lua_fix into mainline (without being able to address your issues). Now I'm confused.
Without seeing the error, and without knowing what modules you were trying to load, what settings you have changed from default, and what additional files you have used (such as extra modules or custom scripts - you mentioned scripts), I'm unable to answer (and I doubt anyone else is). It might be user error or it might be a real issue - I have no idea.
To create a more reliable build, first I need to know the issues with the current build and how to reproduce these errors. From fuzzy reports (or worse, from lack of reports), I'm unable to draw any meaningful conclusions, so if you just wait, the next build will either be mostly the same as the current one (with just minor fixes on other models) or it may have untested stuff that breaks even more functionality (as I may assume things are working fine, and go ahead and merge some experimental branches into mainline without knowing how they actually work on 600D).
I can run some limited tests in QEMU (http://www.magiclantern.fm/forum/index.php?topic=20560), but as emulation doesn't currently cover LiveView or photo capture, the tests I'm able to run are quite basic (whether you can navigate ML menu, whether you can load modules/scripts, whether we are correctly reserving memory from Canon firmware and similar stuff). Most of the "interesting" features are much harder to test in the emulator.
The above applies to any other camera model, not just 600D.
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Quote from: ToniX on January 16, 2018, 07:49:06 AM
I can't find any version for 600D listed on your page ...where is it?
This was meant to be a temporary solution for users asking about temporarily dead links to Canon firmware on ML's download page. This condition doesn't apply anymore.
Quote from: xysunny on January 15, 2018, 06:54:27 PM
ML - I don't have Magic Lantern installed on the camera. :(
How do I proceed ?
@a1ex: Any ideas?
The current state is not clear to me.
Was ML ever installed on this camera?
If yes, I understand the camera was used temporarily without ML for 2 days, then it stopped working. If this is the case, how was ML uninstalled? By formatting the card, or by running the firmware update to disable the boot flag in the camera?
If the card was formatted, place portable display test autoexec on the card, make it bootable with EOSCard / MacBoot and check for any signs of life.
If ML was never installed on the camera, and it does not show any signs of life, we are unable to run any code on it. If OP has electronics skills, this might help, but I don't know how these signals should look on a good camera: http://www.magiclantern.fm/forum/index.php?topic=7531 (it's still an open puzzle, where anyone with an Arduino or RPi or similar board can help)
General checks: make sure the card and battery doors are closed and their micro-switches are working. If any of them is open, on some models you will not get any signs of life. Without ML installed or without a bootable card inside, this is probably true on all models (at least if talking about signs of life visible with the naked eye, without a multimeter).
@a1ex Thanks a1ex for taking my post into consideration.
Your observations are correct and I totally agree with you on all the line..
I own a 600D which is notoriously limited in terms of filming in 14Bit RAW.
Then the 10/12 bit RAW as well as the LUA implementation appeared and this reignited my interest in ML :D.
The NB .2017Dec07.600D102 does not offer 10-12 RAW bits and the LUA module completely blocks the machine if activated and therefore is useless.
The other builds (LUA fix and laters) are updates of the latter (RAW video only at 14Bit) and running LUA I still had errors, if I remember correctly.
Is there a way to test both 10/12 Bit RAw and LUA in a single build?
If yes, how should I do?
(I tried to copy the 10/12 modules over the builds with LUA fix and vice versa but, without success).
P:S I've read your call for tester, I hope I can participate-
All the best :)
You could merge both branches and compile from source. Copying modules over won't work, as lua_fix contains many backend changes that break binary compatibility.
Once I'll integrate one of these two branches into mainline (whichever I'll consider ready first, based on user feedback), the functionality will also arrive in the remaining experimental builds.
@a1ex
Quote from: a1ex on January 17, 2018, 08:46:54 AM
You could merge both branches and compile from source. Copying modules over won't work, as lua_fix contains many backend changes that break binary compatibility.
Unfortunately this is out of my Hw/SW/time/skills, reach. :-[
For a while I will play with magiclantern-raw_video_10bit_12bit.2017Dec18.600D102 wich should be the most updated build available.. can you please confirm?
Thanks
I just made an update to the current nightly build (2017-12-07), to hopefully get a bug fixed, but the "missing feature" is still there:
I want to have clear display of the live view. Therefor I turned on the option "clear overlays" and set it to "always".
This works on the camera display, but when using the HDMI out of the camera I get the black/grey borders on the right and left side, nearly every time I switch on the camera again - but not always
When pressing [Trash] button, the displays is cleared fine every time. But next time I shut the camera off and on, the black borders are there again and I have to press [Trash] again.
Anyone else having this problem?
I found the user fdwet, who also had/has this problem with a 100D:
https://www.magiclantern.fm/forum/index.php?topic=16040.msg183340#msg183340
My problem is that my 600D is placed in a case, so I can not press the Trash button every time the camera is powered on.
Trying to diagnose a possible bug in the emulator and I need some input from a 600D owner:
1) when trying to format the card from the camera, can you toggle between Keep ML and Remove ML? (according to escho, yes (https://bitbucket.org/hudson/magic-lantern/pull-requests/575/restore-after-format-refactoring-fix-for/diff#comment-2780246))
2) if yes, can you create startup log (http://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log/) that also covers the above action? (just toggling between the two options a few times; no need to actually format the card)
@Stryker1: no 600D/100D here; have some screenshots to show the issue?
1 - Yes.
2 - I cannot boot to the startup-log ML. Three long and three short flashes. Have to remove battery and card to reset cam. Double-checked that the card is good, that I have the right build, and that I got a good download.
Hopefully fixed - the startup-log build seems to work now in QEMU...
Log:
https://www.dropbox.com/s/8sl2qh333fa4yk8/DM-0002.LOG?dl=0
@a1ex:
Here is a sample image:
(https://thumb.ibb.co/j1LM4G/15166929239910.jpg) (https://ibb.co/j1LM4G)
- The only options I have activated in ML is "Clear Overlays: always" and "Global Draw: off"
- I am in film mode on the 600D
- The bars appear -sometimes- when turning the camera on, but only in the HDMI output.
- The bars appear -always- when I take a photo (while in film mode, but not recording), so that the output gets black and when the liveview comes back, the bars are there.
When I press the Trash-Button twice, the overlays are cleared again, as they should be.
If I plug out the HDMI cable, so that the liveview is shown on the camera display, the bars are always gone, as they should be.
What I also noticed is that the Option "Advanced settings -> Orientation: mirror" is not enabled for the HDMI output.
It would really be great if these two issues can be fixed.
Expected result? (how does a good screen look like?)
The bars are not symmetrical (both in position and colors), something which I'm unable to reproduce. There's no focus box either; how did you hide it? (assuming Global Draw is off in ML)
Can you also use the startup-log build linked above to create a log file with the external monitor connected?
Is the clear overlays feature working properly on the built-in LCD?
Reproduced the display orientation issue on 60D, but apparently this one is handled by the built-in LCD controller (http://www.magiclantern.fm/forum/index.php?topic=21108), so it's very hard to fix. Flipping upside-down may be doable with the EDMAC routines (http://www.magiclantern.fm/forum/index.php?topic=18315.0) (not straightforward, not sure if it's worth the trouble); flipping horizontally is very hard to do with our current knowledge on DMA hardware (and impossible in software if you want it in real-time).
>Expected result? (how does a good screen look like?)
No Canon standard firmware bars with the vertical grey lines on the left and right, so a clean and a little bit larger screen of the camera's live view, see this image:
(https://thumb.ibb.co/gQZptb/15167776117770.jpg) (https://ibb.co/gQZptb)
>There's no focus box either; how did you hide it?
The only two settings I made in ML is "Clear Overlays: always" and "Global Draw: off".
"Focus Box Setttings" is set to "Display: Auto-Hide", but I guess this is the default.
>The bars are not symmetrical (both in position
>and colors)
Colors are correct in "real life" - it is justed caused by my bad smartphone camera quality :)
But you are right that the live view is not centered on the external monitor. But this is only a matter of the external monitor: I had to set the "mirror option" in the external monitor, as a workaround, because the mirror setting in ML does not work for the HDMI out, as you know. If I do not mirror the video signal in the external monitor, it is perfectly centered. So not an issue of the video signal of ML.
>Is the clear overlays feature working properly on the built-in LCD?
Yes, on the build-in LCD it is always perfectly cleared, on the external only sometimes when I switch on the camera and never, when I take a photo (when the live view gets black and switches on again). It is important to know, that I am in the Movie mode of the camera. If I switch to M or another photo mode, the display is cleared well after taking a photo and going back to live view.
>Reproduced the display orientation issue on 60D, but apparently
>this one is handled by the built-in LCD controller, so it's very hard to fix.
That would be bad, because I would have to live with my workaround to set the mirror option in my external monitor which leads to a black stripe on the right, because of it's issues no centering the image when in mirror mode. See also the current picture.
PS: Maybe interesting to know: normally I set the movie resolution to 640 Pixel in the Canon, which can lead to the described bug of the stripes right and left until pressing the delete button twice.
If I set movie resolution to 1280 or 1920, stripes appear on the top an bottom, if the bug occurs. But when pressing the Delete-Button twice, the video signal is also scaled, without the stripes (as in the 640 mode).
(https://thumb.ibb.co/cDhW6w/15167776118131.jpg) (https://ibb.co/cDhW6w)
Any hints about this or is there anything I can help with fixing this?
Hi 600D users. I'm trying to get the SRM_BUFFER_SIZE cataloged for all cameras and am missing an in camera confirmation for the 600D. I was able to find it in QEMU and I'm 99.99% sure this is correct but it would be nice to be 100%.
(https://farm5.staticflickr.com/4603/40285571001_b149a09202.jpg) (https://flic.kr/p/24nU5Jn)
I uploaded a build named find-SRM_BUFFER_SIZE.2018Feb15.600D102 to my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Simply go to the Debug menu and select Free Memory.
Thanks!
Mine reads just as yours, except:
Allocated RAM 589KB, peak 1.1MB
SRM job total 4x31MB
Not surprised that Allocated RAM and SRM job total will change. As long as the SRM_BUFFER_SIZE matches we're golden. Thanks!
@dfort
Quote from: dfort on February 15, 2018, 07:11:40 PM
Hi 600D users.
I uploaded a build named find-SRM_BUFFER_SIZE.2018Feb15.600D102 to my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Simply go to the Debug menu and select Free Memory.
Thanks!
hyi, I just wish to inform you that such file is not present at the provided url.
@ToniX - The test was run on the camera so I deleted the build. In addition, the QEMU results were verified as valid by a1ex and merged into the crop_rec_4k branch. Now this doesn't mean that the 600D can do 4k but we've got SRM_BUFFER_SIZE saved for future reference.
Just a wake up call for 600D users, this test hasn't been run yet:
https://www.magiclantern.fm/forum/index.php?topic=5601.msg196632#msg196632
Let me know if you need any help getting a special build working to run the test.
Quote from: wildbill001 on December 13, 2017, 03:45:40 PM
I used ML several years ago when I first got my T3i. I went to use it several weeks ago after a LONG hiatus and the card wouldn't load. So I'm looking for a new build. The most current nightly build shows 2 tests failed. Now, I'm not sure those test are important--or are they? Is there a previous build that passes all the tests that maybe I should use?
And lastly, am I posting this in the correct forum? :-\
Thanks for the help
Bill W
Hi Bill I'm in a similar situation, I'm a first time user (NOOB to ML) and collecting the files and information to do the update, however I'm concerned about using the current build because of the test errors reported. Did you get an answer on your question? If the current version is not appropriate which version should I be looking for?
Thanks
Quote from: shadowrider on March 09, 2018, 05:00:59 PM
Hi Bill I'm in a similar situation, I'm a first time user (NOOB to ML) and collecting the files and information to do the update, however I'm concerned about using the current build because of the test errors reported. Did you get an answer on your question? If the current version is not appropriate which version should I be looking for?
Thanks
Hello Bill,
i use to photograph the nightly build from 2018-02-04
I'm doing quite well. However, I can not comment on audio and video.
Hey!
Can someone help me enable 10bit raw - I've searched all the menus, I've searched the forum, I've installed the latest experimental build....
I'm a fairly experienced MLV user having shot many projects on my old 5D3. Recently acquired a 600d for view finding. I feel like there is something blindingly obvious I am missing
CHeers,
Modules tab -> mlv_lite.mo ON -> restart cam -> Movie tab -> RAW video -> Data format
Quote from: Walter Schulz on March 30, 2018, 03:16:27 PM
Modules tab -> mlv_lite.mo ON -> restart cam -> Movie tab -> RAW video -> Data format
Thanks but that "Data Format" menu item doesn't exist in my version
I am running: magiclantern-lua_fix.2018Mar21.600D102.zip
Which build are you running?
You may want to try "10/12-bit RAW video" experimental build.
Quote from: Walter Schulz on March 30, 2018, 08:15:11 PM
You may want to try "10/12-bit RAW video" experimental build.
Thanks man!
One more question: any thoughts on what makes sense as the optimal SD card for this camera's bottle necks?
600D theoretical card interface limit is 25 MByte/s. There is a chance that's not the last word. But there is no schedule to make it happen for 600D. Therefore: www.cameramemoryspeed.com and pick anything decent. 30 MByte/s (or higher) in UHS-I write mode.
How about a firmware update for the 600D?
(https://farm1.staticflickr.com/807/39534742330_a2d8021f00.jpg) (https://flic.kr/p/23exTws)
Thanks @mk11174 for running the portable dumper on the 600D.103. Got it updated and running on QEMU but it looks like the 600D won't show a firmware signature in QEMU. If anyone wants to lend a hand I put a fw-signature build on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). To run it first make sure you've got 102 running, use the Canon firmware updater (also on my downloads page) to update your camera to 103. Note that there is no ML-SETUP.FIR for this yet so your camera and card bootflags needs to remain set to run this. The firmware signature should display on the LCD. Please report it here on the forum or PM me.
BTW -- the stubs in QEMU need to be changed but since this camera can run ML in QEMU even without the debugmsg.gdb file I'm not 100% sure I got this right:
# ./run_canon_fw.sh 600D -d debugmsg
# ./run_canon_fw.sh 600D -d debugmsg -s -S & arm-none-eabi-gdb -x 600D/debugmsg.gdb
source -v debug-logging.gdb
# To get debugging symbols from Magic Lantern, uncomment one of these:
#symbol-file ../magic-lantern/platform/600D.103/magiclantern
#symbol-file ../magic-lantern/platform/600D.103/autoexec
#symbol-file ../magic-lantern/platform/600D.103/stubs.o
macro define CURRENT_TASK 0x1a2c
macro define CURRENT_ISR (MEM(0x670) ? MEM(0x674) >> 2 : 0)
# GDB hook is very slow; -d debugmsg is much faster
# ./run_canon_fw.sh will use this address, don't delete it
# b *0xff06e3a0
# DebugMsg_log
b *0xff071580
task_create_log
b *0xff1f5830
register_interrupt_log
# MPU communication
if 0
b *0xff1db52c
mpu_send_log
b *0xff05ed8c
mpu_recv_log
end
# message queues
if 0
b *0xff1f594c
create_msg_queue_log
b *0xff1f5c48
post_msg_queue_log
b *0xff1f5ba4
post_msg_queue_log
b *0xff1f5a5c
try_receive_msg_queue_log
b *0xff1f5b14
receive_msg_queue_log
end
cont
Hum--this is strange. So "Hello World" works fine in camera and gives a firmware signature of 0x5113b56e:
(https://farm1.staticflickr.com/882/39548561080_4f9cef5f3d_o.jpg) (https://flic.kr/p/23fLHmL)
Plugging this into fw-signature.h makes this happen:
(https://farm1.staticflickr.com/871/26479660127_8139e7dbdd.jpg) (https://flic.kr/p/GkVbqg)
The basic autoexec.bin that is packaged with QEMU shows that this is in fact 600D.103:
(https://farm1.staticflickr.com/820/40637111704_07e2185670.jpg) (https://flic.kr/p/24UXPwY)
Weird part is commenting out the firmware signature it runs fine in QEMU:
(https://farm1.staticflickr.com/819/27487439738_f2c0ca4a5a.jpg) (https://flic.kr/p/HSYjbN)
Maybe this is just a QEMU thing? Anyone want to try it on camera? It should work thought there's a chance that it might break your camera. Test build on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). This doesn't have a ML-SETUP.FIR file yet so make sure your camera bootflag is set before doing the firmware update.
Just tried, Def not just a QEMU thing, same Model Detection popped up right away.
Try on new-dryos-task-hooks branch (long answer later). Relevant changesets: 8260b141b233 and e601292baa57.
Tried the new-dryos-task-hooks branch and got the same results. Turned on CONFIG_QEMU and got this:
[boot] firmware signature: 0x4f4d4712 (1330464530)
expected: 0x5113b56e (1360246126)
So I changed the firmware signature to 0x4f4d4712 and everything seems to be working fine.
Lesson learned -- it is better to do a firmware update using the qemu branch.
Unsolved mystery -- why did "Hello World" report a different firmware signature on camera?
New 600D.103 test build on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
Working!
(https://s9.postimg.cc/6wy8x1vzz/VRAM1.jpg)
Hi,
New user here, would like to check some things please.
am looking to get the "best" RAW that is going to work without crashing out.
I must admit I am confused by some of these things.
I am running the experimental 4k build, with crop_rec and MLV_lite modules installed
I have CBR at 1.
I have resolution at 1736x1160 and ratio 1:1
And I am using Switch to convert the file into a folder of .dngs
What I am confused about is how to get the "right" resolution so I can use Resolve to edit in 1920x1080
Also, how does one set it to 24fps?
Sure, I have a shed load more questions, how can one not with all these options to play with. however, I wanna start recoding asap and figure the rest out as I go.
thanks for any help,
Simon.
[Pass] is_play_mode() => 0x1
[Pass] src = fio_malloc(size) => 0x422040a4
[Pass] dst = fio_malloc(size) => 0x42a080b4
[Pass] memcmp(dst, src, 4097) => 0x82
[Pass] edmac_memcpy(dst, src, 4097) => 0x42a080b4
[Pass] memcmp(dst, src, 4097) => 0x0
[Pass] edmac_memcpy(dst, src, 4097) => 0x42a080b4
[Pass] memcmp(dst, src, size) => 0xee
[Pass] edmac_memcpy(dst, src, size) => 0x42a080b4
[Pass] memcmp(dst, src, size) => 0x0
[Pass] memcmp(dst, src, size) => 0xffffffd2
[Pass] edmac_memcpy_start(dst, src, size) => 0x42a080b4
dt => 0x3200
[Pass] copied => 0x4016ec
[Pass] copied => 0x4016ec
[Pass] copied => 0x4016ec
[Pass] memcmp(dst, src, copied) => 0x0
[Pass] memcmp(dst, src, copied + 16) => 0xffffffdf
edmac_memcpy_finish()
free(src)
free(dst)
Cache test A (EDMAC on BMP buffer)...
[Pass] bmp = bmp_load("ML/CROPMKS/CINESCO2.BMP", 1) => 0xc7dc8
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x570
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x0
Cache test B (FIO on 8K buffer)...
[Pass] tries[0] => 0xff
[Pass] tries[1] => 0x104
[Pass] tries[2] => 0xdd
[Pass] tries[3] => 0x108
[Pass] failr[0] => 0xa6
[Pass] failw[0] => 0xd3
[Pass] failr[1] => 0x82
[Pass] failw[1] => 0x0
[Pass] failr[2] => 0x0
[Pass] failw[2] => 0xba
[Pass] failr[3] => 0x0
[Pass] failw[3] => 0x0
times[0] / tries[0] => 0x2f
times[1] / tries[1] => 0x39
times[2] / tries[2] => 0x37
times[3] / tries[3] => 0x38
Cache tests finished.
[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) => 0x409d2894
[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) => 0x422040a4
[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) => 0x80ba
msleep(900)
[Pass] timer_func => 0x0
msleep(200)
[Pass] timer_func => 0x1
[Pass] ABS((timer_time/1000 - t0) - 1000) => 0x7
[Pass] ABS((timer_arg - ta0) - 1000) => 0xa
[Pass] timer = SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0x80bc
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) => 0x1c8
msleep(90)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x1
[Pass] ABS(DeltaT(timer_time, t0) - 100000) => 0x138
[Pass] ABS(DeltaT(timer_arg, ta0) - 100000) => 0xfc
[Pass] ABS((get_us_clock_value() - t0) - 110000) => 0xe6
[Pass] SetHPTimerAfterNow(90000, next_tick_cbr, overrun_cbr, 0) => 0x1ca
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) => 0x17f
[Pass] ABS(DeltaT(timer_arg, ta0) - 300000) => 0x150
[Pass] ABS((get_us_clock_value() - t0) - 310000) => 0x103
t0 = *(uint32_t*)0xC0242014 => 0x5522c
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0x91e99
[Pass] ABS(MOD(t1-t0, 1048576)/1000 - 250) => 0x2
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x21
Date/time: 2018/04/10 12:26:33
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x22
[Pass] MOD(s1-s0, 60) => 0x1
[Pass] MOD(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x3b5f8
[Pass] p = (void*)_malloc(50*1024) => 0xc9b18
[Pass] CACHEABLE(p) => 0xc9b18
m1 = MALLOC_FREE_MEMORY => 0x2ede8
_free(p)
m2 = MALLOC_FREE_MEMORY => 0x3b5f8
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0xfc120
[Pass] p = (void*)_AllocateMemory(256*1024) => 0xbe20b0
[Pass] CACHEABLE(p) => 0xbe20b0
m1 = GetFreeMemForAllocateMemory() => 0xbc110
_FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0xfc120
[Pass] ABS((m0-m1) - 256*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x3b5f8
m02 = GetFreeMemForAllocateMemory() => 0xfc120
[Pass] p = (void*)_alloc_dma_memory(256*1024) => 0x40be20f0
[Pass] UNCACHEABLE(p) => 0x40be20f0
[Pass] CACHEABLE(p) => 0xbe20f0
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40be20f0
_free_dma_memory(p)
[Pass] p = (void*)_shoot_malloc(24*1024*1024) => 0x42204084
[Pass] UNCACHEABLE(p) => 0x42204084
_shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x3b5f8
m12 = GetFreeMemForAllocateMemory() => 0xfc120
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
[Pass] suite = shoot_malloc_suite_contig(24*1024*1024) => 0xa8b28
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1800000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xa8b50
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1800000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42204080
[Pass] UNCACHEABLE(p) => 0x42204080
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite_contig(0) => 0xa8b28
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1df8000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xa8b50
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1df8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42204080
[Pass] UNCACHEABLE(p) => 0x42204080
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(64*1024*1024) => 0xa8b28
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x4
[Pass] suite->size => 0x4000000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xa8b50
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1df8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42204080
[Pass] UNCACHEABLE(p) => 0x42204080
chunk = GetNextMemoryChunk(suite, chunk) => 0xaff98
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x29fc000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x413f8070
[Pass] UNCACHEABLE(p) => 0x413f8070
chunk = GetNextMemoryChunk(suite, chunk) => 0xaffd0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2a90000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4bf68100
[Pass] UNCACHEABLE(p) => 0x4bf68100
chunk = GetNextMemoryChunk(suite, chunk) => 0xc4740
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x4000000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000070
[Pass] UNCACHEABLE(p) => 0x4a000070
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x4000000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(0) => 0xa8b28
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x4
[Pass] suite->size => 0x4700000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xa8b50
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1df8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42204080
[Pass] UNCACHEABLE(p) => 0x42204080
chunk = GetNextMemoryChunk(suite, chunk) => 0xaff98
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x29fc000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x413f8070
[Pass] UNCACHEABLE(p) => 0x413f8070
chunk = GetNextMemoryChunk(suite, chunk) => 0xaffd0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2a90000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4bf68100
[Pass] UNCACHEABLE(p) => 0x4bf68100
chunk = GetNextMemoryChunk(suite, chunk) => 0xc4740
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x4700000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000070
[Pass] UNCACHEABLE(p) => 0x4a000070
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x4700000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1990c4
[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) => 0x1990a0
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x199080
[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) => 0xc9200be
[Pass] test_task_created => 0x1
[Pass] get_current_task_name() => 'run_test'
[Pass] task_max => 0x68
[Pass] task_max => 0x68
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0xc940094
[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) => 0xc9601f2
[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) => 0xc980042
[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
Quote from: dfort on April 10, 2018, 05:14:56 PM
Tried the new-dryos-task-hooks branch and got the same results.
This was unexpected. I know the emulation is broken after uninstalling cache hacks (started to fix it), but I'd expect CONFIG_HELLO_WORLD on new-dryos-task-hooks to show the correct signature on the Hello World screen on real hardware (tested on 1300D (https://www.magiclantern.fm/forum/index.php?topic=17969.msg195984#msg195984), which boots in the same way as 600D).
I'm not sure why the firmware signature shows up wrong in the camera and "Hello World" didn't work in QEMU but CONFIG_QEMU with the new-dryos-task-hooks branch showed the problem.
Now that I'm going over my notes I don't think we ran "Hello World" on the new-dryos-task-hooks branch in camera.
@mk11174 - Mind checking this out? I've got a new-dryos-task-hooks_600D.103 branch in my repository. All that should be necessary is to uncomment this line:
config-defines.h
/** Load fonts and print Hello World (disable CONFIG_EARLY_PORT); will not start any other ML tasks, handlers etc. */
#define CONFIG_HELLO_WORLD
Come to think of it, I think you taught me that trick.
Well, it is def different than the last check!
(https://thumb.ibb.co/eGWBHS/30177048_1945464932130776_464556773_o.jpg) (https://ibb.co/eGWBHS)
Thanks -- looks like the new-dryos-task-hooks branch is showing the correct firmware signature in camera.
What I meant with getting the same results in QEMU was that the signature didn't print on the screen but it did show up in the log when it was run with CONFIG_QEMU.
Hi Daniel,
I just bought my Canon 600D, and I'm very beginner at the firmware update thing, but I really need magic lantern and it's features.
I've got version 1.0.2 firmware now on my camera, but I can upgrade it to 1.0.3. if it's needed.
Could you please give me some instructions step by step, using your source (or not) to install a magic lantern to my cam?
I really don't want to broke it with an install :)
Many thanks in advance,
Zsolt
Quote from: a1ex on January 23, 2018, 12:35:44 AM
1) when trying to format the card from the camera, can you toggle between Keep ML and Remove ML? (according to escho, yes (https://bitbucket.org/hudson/magic-lantern/pull-requests/575/restore-after-format-refactoring-fix-for/diff#comment-2780246))
Does that work in the current lua_fix experimental build?
Additionally, can you open ML submenus (e.g. options for Zebras or Magic Zoom) with the same build?
This is the feedback I got from @mk11174 who helped with the 600D.103 firmware update:
Quote from: mk11174 on April 10, 2018, 06:48:59 PM
Ok, the 600D seems pretty solid so far, Raw recording working as it always did, never perfect really cause its slower and has the pink frame issues every so often, but seems same as usual, silent fullres fine too, Raw histogram and audio controls are fine, no errors yet on anything, nothing sticking out that is an issue.
@a1ex - I pointed out your question to him.
@kanyos - ML currently works with the 1.0.2 firmware for this camera. You can download builds using the "Downloads" tab at the top of the forum page. The 1.0.3 firmware update is new and not yet a part of the official builds. I'd suggest using the current version before doing a firmware update. Installation instructions are in the "User Guide" also linked at the top of the forum page.
hello,
i just discovered about ml, i have a 600D and successfully downgraded from 103 to 102 then installed ml and everything is working right. maybe just some small things with the lcd reflesh
i would like to say a big thank you to all of you!
Byeeeee
edit: i just saw that the ml-setup.fir it is still in the sd card, i guess i can remove it, isn't it?
Quote from: a1ex on May 02, 2018, 12:18:55 PM
Does that work in the current lua_fix experimental build?
Additionally, can you open ML submenus (e.g. options for Zebras or Magic Zoom) with the same build?
I tried this on both 1.02 and 1.03 and I get the exact same results, no problem with Format changing option with Q button in Live View or Without Live view.
As for ML submenus, these can be used only while in Photo Mode without Live View, once you turn on Live View or Moviemode, it seems like Q button no longer works with ML menus to get in the Submenus, BUT, the Play button seems to work as the Q button. So I can get in and out of Submenus with Play button and Q button in Photo Mode no Live View and In Live View or Movie mode only Play button allows use of Submenus.
600D 103 API TEST
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-5-6 00:26:13
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 101
apex = 5.625
ms = 20
value = 0.020263
aperture = table:
raw = 47
apex = 4.875
value = 5.4
min = table:
raw = 47
apex = 4.875
value = 5.4
max = table:
raw = 90
apex = 10.250001
value = 34.799999
iso = table:
raw = 104
apex = 9.
value = 1600
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 4700
mode = 3
metering_mode = 3
drive_mode = 0
model = "Canon EOS REBEL T3i"
model_short = "600D"
firmware = "1.0.3"
temperature = 167
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
reboot = function: p
burst = function: p
shoot = function: p
bulb = function: p
wait = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
show = function: p
clear = function: p
write = function: p
hide = function: p
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
resume = function: p
info = function: p
wait = function: p
pause = function: p
start = function: p
stop = function: p
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS"
focal_length = 49
focus_distance = 655350
hyperfocal = 23499
dof_near = 22692
dof_far = 1000000
af = false
af_mode = 3
autofocus = function: p
focus = function: p
display = table:
idle = nil
height = 480
width = 720
rect = function: p
on = function: p
circle = function: p
draw = function: p
pixel = function: p
notify_box = function: p
screenshot = function: p
print = function: p
clear = function: p
load = function: p
line = function: p
off = function: p
key = table:
last = 10
wait = function: p
press = function: p
menu = table:
visible = false
select = function: p
close = function: p
set = function: p
block = function: p
open = function: p
get = function: p
new = function: p
movie = table:
recording = false
stop = function: p
start = function: p
dryos = table:
clock = 8
ms_clock = 8875
image_prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 8192
drive_letter = "B"
file_number = 9976
folder_number = 100
free_space = 15567104
type = "SD"
path = "B:/"
_card_ptr = userdata
shooting_card = table:
cluster_size = 8192
drive_letter = "B"
file_number = 9976
folder_number = 100
free_space = 15567104
type = "SD"
path = "B:/"
_card_ptr = userdata
date = table:
min = 26
isdst = false
sec = 14
year = 2018
day = 6
month = 5
hour = 0
yday = 1
wday = 7
remove = function: p
call = function: p
rename = function: p
directory = function: p
interval = table:
time = 10
count = 0
running = false
stop = function: p
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:36: in function <ML/SCRIPTS/API_TEST.LUA:35>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:35: in function 'print_table'
ML/SCRIPTS/API_TEST.LUA:81: in function 'generic_tests'
ML/SCRIPTS/API_TEST.LUA:1338: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1364: in main chunktask = table:
yield = function: p
create = function: p
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
File I/O tests completed.
Testing Canon GUI functions...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Stop LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Stop LiveView...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Start LiveView...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Stop LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Start LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Start LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Canon GUI tests completed.
Testing ML menu API...
Menu tests completed.
Testing picture taking functions...
Snap simulation test...
Single picture...
B:/DCIM/100CANON/IMG_9977.CR2 not found.
B:/DCIM/100CANON/IMG_9977.JPG not found.
600D 102 API Test
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-5-6 00:18:23
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 101
apex = 5.625
ms = 20
value = 0.020263
aperture = table:
raw = 47
apex = 4.875
value = 5.4
min = table:
raw = 47
apex = 4.875
value = 5.4
max = table:
raw = 90
apex = 10.250001
value = 34.799999
iso = table:
raw = 104
apex = 9.
value = 1600
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 4700
mode = 3
metering_mode = 3
drive_mode = 0
model = "Canon EOS REBEL T3i"
model_short = "600D"
firmware = "1.0.2"
temperature = 165
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
bulb = function: p
burst = function: p
reboot = function: p
shoot = function: p
wait = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
clear = function: p
show = function: p
hide = function: p
write = function: p
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
resume = function: p
stop = function: p
wait = function: p
info = function: p
pause = function: p
start = function: p
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS"
focal_length = 49
focus_distance = 655350
hyperfocal = 23499
dof_near = 22692
dof_far = 1000000
af = false
af_mode = 3
autofocus = function: p
focus = function: p
display = table:
idle = nil
height = 480
width = 720
print = function: p
on = function: p
screenshot = function: p
draw = function: p
line = function: p
load = function: p
pixel = function: p
notify_box = function: p
off = function: p
clear = function: p
circle = function: p
rect = function: p
key = table:
last = 10
press = function: p
wait = function: p
menu = table:
visible = false
new = function: p
open = function: p
close = function: p
block = function: p
select = function: p
set = function: p
get = function: p
movie = table:
recording = false
stop = function: p
start = function: p
dryos = table:
clock = 29
ms_clock = 29294
image_prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 8192
drive_letter = "B"
file_number = 9974
folder_number = 100
free_space = 15527360
type = "SD"
path = "B:/"
_card_ptr = userdata
shooting_card = table:
cluster_size = 8192
drive_letter = "B"
file_number = 9974
folder_number = 100
free_space = 15527360
type = "SD"
path = "B:/"
_card_ptr = userdata
date = table:
month = 5
sec = 24
day = 6
isdst = false
yday = 1
hour = 0
year = 2018
min = 18
wday = 7
call = function: p
directory = function: p
remove = function: p
rename = function: p
interval = table:
time = 10
count = 0
running = false
stop = function: p
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:36: in function <ML/SCRIPTS/API_TEST.LUA:35>
[C]: in function 'globals.xpcall'
ML/SCRIPTS/API_TEST.LUA:35: in function 'globals.print_table'
ML/SCRIPTS/API_TEST.LUA:81: in function 'globals.generic_tests'
ML/SCRIPTS/API_TEST.LUA:1338: in function 'globals.api_tests'
ML/SCRIPTS/API_TEST.LUA:1364: in main chunktask = table:
create = function: p
yield = function: p
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
File I/O tests completed.
Testing Canon GUI functions...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Start LiveView...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Stop LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Start LiveView...
Enter MENU mode...
Exit MENU mode...
Stop LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Resume LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Canon GUI tests completed.
Testing ML menu API...
Menu tests completed.
Testing picture taking functions...
Snap simulation test...
Single picture...
B:/DCIM/100CANON/IMG_9975.CR2 not found.
B:/DCIM/100CANON/IMG_9975.JPG not found.
600D 103 lua/fix Stubs Test
[Pass] is_play_mode() => 0x1
[INFO] Camera model: Canon EOS REBEL T3i 1.0.3 (0x80000286 600D)
[Pass] is_camera("DIGIC", "*") => 0x1
[Pass] is_camera(__camera_model_short, firmware_version) => 0x1
[Pass] src = fio_malloc(size) => 0x422c00c4
[Pass] dst = fio_malloc(size) => 0x42ac40d4
[Pass] memcmp(dst, src, 4097) => 0xec
[Pass] edmac_memcpy(dst, src, 4097) => 0x42ac40d4
[Pass] memcmp(dst, src, 4097) => 0x0
[Pass] edmac_memcpy(dst, src, 4097) => 0x42ac40d4
[Pass] memcmp(dst, src, size) => 0x1a
[Pass] edmac_memcpy(dst, src, size) => 0x42ac40d4
[Pass] memcmp(dst, src, size) => 0x0
[Pass] memcmp(dst, src, size) => 0xffffff97
[Pass] edmac_memcpy_start(dst, src, size) => 0x42ac40d4
dt => 0x3151
[Pass] copied => 0x400d6c
[Pass] copied => 0x400d6c
[Pass] copied => 0x400d6c
[Pass] memcmp(dst, src, copied) => 0x0
[Pass] memcmp(dst, src, copied + 16) => 0x37
edmac_memcpy_finish()
free(src)
free(dst)
Cache test A (EDMAC on BMP buffer)...
[Pass] bmp = bmp_load("ML/CROPMKS/CINESCO2.BMP", 1) => 0xbcfb0
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x1030
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x0
Cache test B (FIO on 8K buffer)...
[Pass] tries[0] => 0xfe
[Pass] tries[1] => 0x106
[Pass] tries[2] => 0xee
[Pass] tries[3] => 0xf6
[Pass] failr[0] => 0xc4
[Pass] failw[0] => 0xf6
[Pass] failr[1] => 0x97
[Pass] failw[1] => 0x0
[Pass] failr[2] => 0x0
[Pass] failw[2] => 0xe6
[Pass] failr[3] => 0x0
[Pass] failw[3] => 0x0
times[0] / tries[0] => 0x2f
times[1] / tries[1] => 0x29
times[2] / tries[2] => 0x33
times[3] / tries[3] => 0x31
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
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 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) => 0x40bc215c
[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) => 0x422c00c4
[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) => 0x95c0
msleep(900)
[Pass] timer_func => 0x0
msleep(200)
[Pass] timer_func => 0x1
[Pass] ABS((timer_time/1000 - t0) - 1000) => 0x1
[Pass] ABS((timer_arg - ta0) - 1000) => 0xa
[Pass] timer = SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0x95e6
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) => 0x1e0
msleep(90)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x1
[Pass] ABS(DeltaT(timer_time, t0) - 100000) => 0x12d
[Pass] ABS(DeltaT(timer_arg, ta0) - 100000) => 0x103
[Pass] ABS((get_us_clock() - t0) - 110000) => 0x219
[Pass] SetHPTimerAfterNow(90000, next_tick_cbr, overrun_cbr, 0) => 0x1e2
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) => 0x2b8
[Pass] ABS(DeltaT(timer_arg, ta0) - 300000) => 0x28e
[Pass] ABS((get_us_clock() - t0) - 310000) => 0x227
t0 = GET_DIGIC_TIMER() => 0x3037c
msleep(250)
t1 = GET_DIGIC_TIMER() => 0x6b218
[Pass] ABS(MOD(t1-t0, 1048576)/1000 - 250) => 0x9
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x11
Date/time: 2018/05/06 00:42:17
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x12
[Pass] MOD(s1-s0, 60) => 0x1
[Pass] MOD(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x43f78
[Pass] p = (void*)_malloc(50*1024) => 0xc0a40
[Pass] CACHEABLE(p) => 0xc0a40
m1 = MALLOC_FREE_MEMORY => 0x37768
_free(p)
m2 = MALLOC_FREE_MEMORY => 0x43f78
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0xe1f8c
[Pass] p = (void*)_AllocateMemory(128*1024) => 0xbc211c
[Pass] CACHEABLE(p) => 0xbc211c
m1 = GetFreeMemForAllocateMemory() => 0xc1f7c
_FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0xe1f8c
[Pass] ABS((m0-m1) - 128*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x43f78
m02 = GetFreeMemForAllocateMemory() => 0xe1f8c
[Pass] p = (void*)_alloc_dma_memory(128*1024) => 0x40bc215c
[Pass] UNCACHEABLE(p) => 0x40bc215c
[Pass] CACHEABLE(p) => 0xbc215c
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40bc215c
_free_dma_memory(p)
[Pass] p = (void*)_shoot_malloc(16*1024*1024) => 0x422c00b4
[Pass] UNCACHEABLE(p) => 0x422c00b4
_shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x43f78
m12 = GetFreeMemForAllocateMemory() => 0xe1f8c
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
[Pass] suite = shoot_malloc_suite_contig(16*1024*1024) => 0xbbd10
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1000000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbbd38
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1000000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x422c00b0
[Pass] UNCACHEABLE(p) => 0x422c00b0
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite_contig(0) => 0xbbd10
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1f68000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbbd38
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1f68000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000070
[Pass] UNCACHEABLE(p) => 0x4a000070
largest_shoot_block = suite->size => 0x1f68000
[INFO] largest_shoot_block: 31MB
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(largest_shoot_block + 1024*1024) => 0xbbd10
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x2
[Pass] suite->size => 0x2068000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbbd38
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1d3c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x422c00b0
[Pass] UNCACHEABLE(p) => 0x422c00b0
chunk = GetNextMemoryChunk(suite, chunk) => 0xbbd98
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2068000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x413f8070
[Pass] UNCACHEABLE(p) => 0x413f8070
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x2068000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(0) => 0xbbd10
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x3
[Pass] suite->size => 0x4700000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbbd38
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1d3c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x422c00b0
[Pass] UNCACHEABLE(p) => 0x422c00b0
chunk = GetNextMemoryChunk(suite, chunk) => 0xbbd98
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2940000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x413f8070
[Pass] UNCACHEABLE(p) => 0x413f8070
chunk = GetNextMemoryChunk(suite, chunk) => 0xbbdd0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x4700000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000070
[Pass] UNCACHEABLE(p) => 0x4a000070
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x4700000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x16a01c
[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) => 0x16a000
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x169fe0
[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) => 0x1aaa00be
[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) => 0x1aac0094
[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) => 0x1aae030c
[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) => 0x1ab000a4
[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, 11457 passed, 5 failed.
.
600D 102 lua/fix Stubs Test
[Pass] is_play_mode() => 0x1
[INFO] Camera model: Canon EOS REBEL T3i 1.0.2 (0x80000286 600D)
[Pass] is_camera("DIGIC", "*") => 0x1
[Pass] is_camera(__camera_model_short, firmware_version) => 0x1
[Pass] src = fio_malloc(size) => 0x42204094
[Pass] dst = fio_malloc(size) => 0x42a080a4
[Pass] memcmp(dst, src, 4097) => 0x7f
[Pass] edmac_memcpy(dst, src, 4097) => 0x42a080a4
[Pass] memcmp(dst, src, 4097) => 0x0
[Pass] edmac_memcpy(dst, src, 4097) => 0x42a080a4
[Pass] memcmp(dst, src, size) => 0x78
[Pass] edmac_memcpy(dst, src, size) => 0x42a080a4
[Pass] memcmp(dst, src, size) => 0x0
[Pass] memcmp(dst, src, size) => 0x7
[Pass] edmac_memcpy_start(dst, src, size) => 0x42a080a4
dt => 0x31fd
[Pass] copied => 0x400a9c
[Pass] copied => 0x400a9c
[Pass] copied => 0x400a9c
[Pass] memcmp(dst, src, copied) => 0x0
[Pass] memcmp(dst, src, copied + 16) => 0xfffffffc
edmac_memcpy_finish()
free(src)
free(dst)
Cache test A (EDMAC on BMP buffer)...
[Pass] bmp = bmp_load("ML/CROPMKS/CINESCO2.BMP", 1) => 0xbd1f0
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x10df
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x0
Cache test B (FIO on 8K buffer)...
[Pass] tries[0] => 0xe6
[Pass] tries[1] => 0x102
[Pass] tries[2] => 0xf8
[Pass] tries[3] => 0x108
[Pass] failr[0] => 0xbe
[Pass] failw[0] => 0xe3
[Pass] failr[1] => 0x98
[Pass] failw[1] => 0x0
[Pass] failr[2] => 0x0
[Pass] failw[2] => 0xf4
[Pass] failr[3] => 0x0
[Pass] failw[3] => 0x0
times[0] / tries[0] => 0x2c
times[1] / tries[1] => 0x32
times[2] / tries[2] => 0x2e
times[3] / tries[3] => 0x2c
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
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 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) => 0x40bc20f0
[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) => 0x42204094
[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) => 0x956e
msleep(900)
[Pass] timer_func => 0x0
msleep(200)
[Pass] timer_func => 0x1
[Pass] ABS((timer_time/1000 - t0) - 1000) => 0xa
[Pass] ABS((timer_arg - ta0) - 1000) => 0xa
[Pass] timer = SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0x9594
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) => 0x1e0
msleep(90)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x1
[Pass] ABS(DeltaT(timer_time, t0) - 100000) => 0x128
[Pass] ABS(DeltaT(timer_arg, ta0) - 100000) => 0xfc
[Pass] ABS((get_us_clock() - t0) - 110000) => 0x220
[Pass] SetHPTimerAfterNow(90000, next_tick_cbr, overrun_cbr, 0) => 0x1e2
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) => 0x2c2
[Pass] ABS(DeltaT(timer_arg, ta0) - 300000) => 0x294
[Pass] ABS((get_us_clock() - t0) - 310000) => 0x23f
t0 = GET_DIGIC_TIMER() => 0xcafa5
msleep(250)
t1 = GET_DIGIC_TIMER() => 0x5fbf
[Pass] ABS(MOD(t1-t0, 1048576)/1000 - 250) => 0x9
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x23
Date/time: 2018/05/06 00:52:35
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x25
[Pass] MOD(s1-s0, 60) => 0x2
[Pass] MOD(s1-s0, 60) => 0x2
m0 = MALLOC_FREE_MEMORY => 0x44158
[Pass] p = (void*)_malloc(50*1024) => 0xc0c80
[Pass] CACHEABLE(p) => 0xc0c80
m1 = MALLOC_FREE_MEMORY => 0x37948
_free(p)
m2 = MALLOC_FREE_MEMORY => 0x44158
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0xe1f9c
[Pass] p = (void*)_AllocateMemory(128*1024) => 0xbc20b0
[Pass] CACHEABLE(p) => 0xbc20b0
m1 = GetFreeMemForAllocateMemory() => 0xc1f8c
_FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0xe1f9c
[Pass] ABS((m0-m1) - 128*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x44158
m02 = GetFreeMemForAllocateMemory() => 0xe1f9c
[Pass] p = (void*)_alloc_dma_memory(128*1024) => 0x40bc20f0
[Pass] UNCACHEABLE(p) => 0x40bc20f0
[Pass] CACHEABLE(p) => 0xbc20f0
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40bc20f0
_free_dma_memory(p)
[Pass] p = (void*)_shoot_malloc(16*1024*1024) => 0x42204084
[Pass] UNCACHEABLE(p) => 0x42204084
_shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x44158
m12 = GetFreeMemForAllocateMemory() => 0xe1f9c
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
[Pass] suite = shoot_malloc_suite_contig(16*1024*1024) => 0xbbb30
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1000000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbbb58
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1000000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42204080
[Pass] UNCACHEABLE(p) => 0x42204080
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite_contig(0) => 0xbbb30
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1f68000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbbb58
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1f68000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000070
[Pass] UNCACHEABLE(p) => 0x4a000070
largest_shoot_block = suite->size => 0x1f68000
[INFO] largest_shoot_block: 31MB
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(largest_shoot_block + 1024*1024) => 0xbbb30
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x2
[Pass] suite->size => 0x2068000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbbb58
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1df8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42204080
[Pass] UNCACHEABLE(p) => 0x42204080
chunk = GetNextMemoryChunk(suite, chunk) => 0xbbbb8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2068000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x413f8070
[Pass] UNCACHEABLE(p) => 0x413f8070
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x2068000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(0) => 0xbbb30
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x3
[Pass] suite->size => 0x4700000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xbbb58
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1df8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42204080
[Pass] UNCACHEABLE(p) => 0x42204080
chunk = GetNextMemoryChunk(suite, chunk) => 0xbbbb8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x29fc000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x413f8070
[Pass] UNCACHEABLE(p) => 0x413f8070
chunk = GetNextMemoryChunk(suite, chunk) => 0xbbbf0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x4700000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000070
[Pass] UNCACHEABLE(p) => 0x4a000070
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x4700000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x16a01c
[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) => 0x16a000
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x169fe0
[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) => 0x169400be
[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) => 0x16960094
[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) => 0x16980318
[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) => 0x169a00a4
[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, 11457 passed, 5 failed.
.
Look pretty much the same to me. Did you by any chance have the colorspace set to adobe? Reason I ask is because we had a similar situation happen with the 1200D (https://www.magiclantern.fm/forum/index.php?topic=12627.msg200725#msg200725). Note that the Stubs API test from the selftest module didn't complete.
Could you next try the lua_fix builds. 1.0.3 is on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) and 1.0.2 is on the experiments download page (https://builds.magiclantern.fm/experiments.html).
The lua API Stubs test on the lua_fix branch is tougher to get through. Something I have been experiencing is that if the tests fail, try clearing the Canon settings and run the tests again. If there's a particularly stubborn test. Comment it out or try running one or just a few tests at a time. The lens focus test is a bit tricky because some lenses won't focus through lua on some cameras (https://www.magiclantern.fm/forum/index.php?topic=22053.0). If the focus test fails, try another lens.
600D 102 Memory Benchmark
(https://thumb.ibb.co/cfW3M7/BENCH102.jpg) (https://ibb.co/cfW3M7)
600D 103 Memory Benchmark
(https://thumb.ibb.co/eG0kZS/BENCH103.jpg) (https://ibb.co/eG0kZS)
Quote from: dfort on May 06, 2018, 06:51:16 AM
Look pretty much the same to me. Did you by any chance have the colorspace set to adobe? Reason I ask is because we had a similar situation happen with the 1200D (https://www.magiclantern.fm/forum/index.php?topic=12627.msg200725#msg200725). Note that the Stubs API test from the selftest module didn't complete.
Yes, Adobe RGB colorspace was set for this camera at time of testing.
QuoteCould you next try the lua_fix builds. 1.0.3 is on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) and 1.0.2 is on the experiments download page (https://builds.magiclantern.fm/experiments.html).
This 103 version is the build from your downloads page. And the 102 is from experiments page
In order to get through these tests we should be checking apples to apples so please clear your Canon settings. Then (optionally) change the photo settings to shoot RAW+JPEG, change from Single shooting to Continuous shooting and finally, (this one isn't optional) Disable Continuous AF.
You've got a bunch of left over files from the tests so I'd recommend reformatting your card while you're at it.
What is happening when Color space is set to Adobe RGB is that the filenames start with an underscore. Here are the files after running just test_camera_take_pics():
sRGB
(https://farm1.staticflickr.com/865/41029875635_59b5488b54_n.jpg) (https://flic.kr/p/25vEQyT)
Adobe RGB
(https://farm1.staticflickr.com/969/28058169098_659a8ba35c_n.jpg) (https://flic.kr/p/JKps9b)
Now I don't know why this is happening but when "assert(size_cr2 or size_jpg)" is called it will crash the test.
So, long story short, put your camera in sRGB Color space or better yet clear all Canon settings, format your card and try the lua API test again.
But wait -- there's more!
The selftest module fails are "get_focus_confirmation()" -- try doing a half-shutter press, does the lens focus and camera sound a confirmation beep? If not, then clear out Canon settings and try it again. Once you get focus confirmation with a half-shutter press, run the selftest module, Stubs API test again and it should pass all the tests.
I can do that, I only noticed the focus conf fail, did not seem very important since I had lens cap on, seems to be ok to fail it, both tests came back same for both versions so I thought the main goal was to show 103 was good for merge, if both versions give same results, that should show it is good to go?
Quote from: mk11174 on May 06, 2018, 05:36:02 PM
...I had lens cap on, seems to be ok to fail it...
LOL! :P
Quote from: mk11174 on May 06, 2018, 05:36:02 PM
...I thought the main goal was to show 103 was good for merge, if both versions give same results, that should show it is good to go?
Chances are that the firmware update didn't introduce any new issues but it is still good to run these tests to see if there are any issues we might be able to fix while we're at it. Note that the EOSM firmware update pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/792/update-to-eosm-firmware-revision-203/diff) has been available for over a year and it works as well as the currently supported firmware but wow--that camera has issues getting through these tests!
Trying the API_Test on 103 seems to be going on FOREVER doing the same thing on this Lens Moving test, light flashing away, but going so long battery almost dead, console showing same repeating text? Gonna give up I guess. Reset all camera settings and Formatted and set to continuous shooting also.
Battery died, here is log it saved
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-5-6 13:45:28
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 109
apex = 6.625
ms = 10
value = 0.010132
aperture = table:
raw = 48
apex = 5.
value = 5.6
min = table:
raw = 48
apex = 5.
value = 5.6
max = table:
raw = 91
apex = 10.375001
value = 36.400001
iso = table:
raw = 0
apex = 0
value = 0
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 5200
mode = 3
metering_mode = 3
drive_mode = 1
model = "Canon EOS REBEL T3i"
model_short = "600D"
firmware = "1.0.3"
temperature = 188
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
shoot = function: p
burst = function: p
reboot = function: p
bulb = function: p
wait = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
clear = function: p
show = function: p
write = function: p
hide = function: p
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
resume = function: p
start = function: p
stop = function: p
info = function: p
pause = function: p
wait = function: p
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS"
focal_length = 55
focus_distance = 1820
hyperfocal = 28540
dof_near = 1722
dof_far = 1929
af = true
af_mode = 0
autofocus = function: p
focus = function: p
display = table:
idle = nil
height = 480
width = 720
line = function: p
notify_box = function: p
draw = function: p
load = function: p
clear = function: p
off = function: p
print = function: p
screenshot = function: p
on = function: p
rect = function: p
pixel = function: p
circle = function: p
key = table:
last = 10
press = function: p
wait = function: p
menu = table:
visible = false
new = function: p
block = function: p
set = function: p
close = function: p
select = function: p
open = function: p
get = function: p
movie = table:
recording = false
stop = function: p
start = function: p
dryos = table:
clock = 101
ms_clock = 101541
image_prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 9988
folder_number = 100
free_space = 15633664
type = "SD"
path = "B:/"
_card_ptr = userdata
shooting_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 9988
folder_number = 100
free_space = 15633664
type = "SD"
path = "B:/"
_card_ptr = userdata
date = table:
year = 2018
yday = 1
hour = 13
wday = 7
sec = 29
month = 5
isdst = false
min = 45
day = 6
call = function: p
directory = function: p
remove = function: p
rename = function: p
interval = table:
time = 10
count = 0
running = false
stop = function: p
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:36: in function <ML/SCRIPTS/API_TEST.LUA:35>
[C]: in function 'globals.xpcall'
ML/SCRIPTS/API_TEST.LUA:35: in function 'globals.print_table'
ML/SCRIPTS/API_TEST.LUA:81: in function 'globals.generic_tests'
ML/SCRIPTS/API_TEST.LUA:1338: in function 'globals.api_tests'
ML/SCRIPTS/API_TEST.LUA:1364: in main chunktask = table:
yield = function: p
create = function: p
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
File I/O tests completed.
Testing Canon GUI functions...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Pause LiveView...
Resume LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Resume LiveView...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Canon GUI tests completed.
Testing ML menu API...
Menu tests completed.
Testing picture taking functions...
Snap simulation test...
Single picture...
B:/DCIM/100CANON/IMG_9989.CR2: 19657379
B:/DCIM/100CANON/IMG_9989.JPG: 1746728
Two burst pictures...
Ideally, the camera should be in some continuous shooting mode (not checked).
B:/DCIM/100CANON/ABC_9990.CR2: 19633952
B:/DCIM/100CANON/ABC_9990.JPG: 1728852
B:/DCIM/100CANON/ABC_9991.CR2: 19601666
B:/DCIM/100CANON/ABC_9991.JPG: 1725152
Bracketed pictures...
B:/DCIM/100CANON/IMG_9992.CR2: 26354896
B:/DCIM/100CANON/IMG_9992.JPG: 4597540
B:/DCIM/100CANON/IMG_9993.CR2: 19554523
B:/DCIM/100CANON/IMG_9993.JPG: 1635620
B:/DCIM/100CANON/IMG_9994.CR2: 15526094
B:/DCIM/100CANON/IMG_9994.JPG: 437395
Bulb picture...
Elapsed time: 12755
B:/DCIM/100CANON/IMG_9995.CR2: 14504886
B:/DCIM/100CANON/IMG_9995.JPG: 363713
Picture taking tests completed.
Testing multitasking...
Only one task allowed to interrupt...
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Multitasking tests completed.
Testing half-shutter...
Half-shutter test OK.
Testing module 'lv'...
Starting LiveView...
Overlays: ML
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: disabled
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: disabled
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Setting zoom to x1...
Setting zoom to x5...
Setting zoom to x10...
Setting zoom to x5...
Setting zoom to x1...
Setting zoom to x10...
Setting zoom to x1...
Pausing LiveView...
Resuming LiveView...
Stopping LiveView...
LiveView tests completed.
Testing lens focus functionality...
Autofocus outside LiveView...
Focus distance: 1820
Autofocus in LiveView...
Please trigger autofocus (half-shutter / AF-ON / * ).
19...18...17...16...15...14...13...Autofocus triggered.
Autofocus completed.
Focus distance: 655350
Focusing backward...
Focus distance: 655350
Focus motor position: 469
Focusing forward with step size 3, wait=true...
...........
Focus distance: 250
Focus motor position: -1414
Focusing backward with step size 3, wait=true...
..........
Focus distance: 655350
Focus motor position: 500
Focus range: 11 steps forward, 10 steps backward.
Motor steps: 1883 forward, 1914 backward, 31 lost.
Focusing forward with step size 3, wait=false...
...
Focus distance: 250
Focus motor position: -1401
Focusing backward with step size 3, wait=false...
............................................................................
Focus distance: 655350
Focus motor position: 501
Focus range: 101 steps forward, 76 steps backward.
Motor steps: 1901 forward, 1902 backward, 1 lost.
Focusing forward with step size 2, wait=true...
................................................................
Focus distance: 250
Focus motor position: -1457
Focusing backward with step size 2, wait=true...
..............................................................
Focus distance: 655350
Focus motor position: 467
Focus range: 64 steps forward, 62 steps backward.
Motor steps: 1958 forward, 1924 backward, 34 lost.
Focusing forward with step size 2, wait=false...
...
Focus distance: 250
Focus motor position: -1472
Focusing backward with step size 2, wait=false...
...
Focus distance: 655350
Focus motor position: 458
Focus range: 248 steps forward, 222 steps backward.
Motor steps: 1939 forward, 1930 backward, 9 lost.
Focusing forward with step size 1, wait=true...
...
Focus distance: 5270
Focus motor position: 29990
Focusing backward with step size 1, wait=true...
...
Focus distance: 5270
Focus motor position: 29990
Focus range: 17990 steps forward, 753 steps backward.
Motor steps: 29532 forward, 0 backward, 29532 lost.
Focusing forward with step size 1, wait=false...
...
Stubs Test Fine
[Pass] is_play_mode() => 0x1
[INFO] Camera model: Canon EOS REBEL T3i 1.0.3 (0x80000286 600D)
[Pass] is_camera("DIGIC", "*") => 0x1
[Pass] is_camera(__camera_model_short, firmware_version) => 0x1
[Pass] src = fio_malloc(size) => 0x423ec154
[Pass] dst = fio_malloc(size) => 0x42bf0164
[Pass] memcmp(dst, src, 4097) => 0xda
[Pass] edmac_memcpy(dst, src, 4097) => 0x42bf0164
[Pass] memcmp(dst, src, 4097) => 0x0
[Pass] edmac_memcpy(dst, src, 4097) => 0x42bf0164
[Pass] memcmp(dst, src, size) => 0x78
[Pass] edmac_memcpy(dst, src, size) => 0x42bf0164
[Pass] memcmp(dst, src, size) => 0x0
[Pass] memcmp(dst, src, size) => 0xffffffa5
[Pass] edmac_memcpy_start(dst, src, size) => 0x42bf0164
dt => 0x3208
[Pass] copied => 0x400f5c
[Pass] copied => 0x400f5c
[Pass] copied => 0x400f5c
[Pass] memcmp(dst, src, copied) => 0x0
[Pass] memcmp(dst, src, copied + 16) => 0xffffffb2
edmac_memcpy_finish()
free(src)
free(dst)
Cache test A (EDMAC on BMP buffer)...
[Pass] bmp = bmp_load("ML/CROPMKS/CINESCO2.BMP", 1) => 0xbed50
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x740
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x0
Cache test B (FIO on 8K buffer)...
[Pass] tries[0] => 0x119
[Pass] tries[1] => 0xe4
[Pass] tries[2] => 0xf4
[Pass] tries[3] => 0xf7
[Pass] failr[0] => 0xe4
[Pass] failw[0] => 0x114
[Pass] failr[1] => 0x86
[Pass] failw[1] => 0x0
[Pass] failr[2] => 0x0
[Pass] failw[2] => 0xeb
[Pass] failr[3] => 0x0
[Pass] failw[3] => 0x0
times[0] / tries[0] => 0x34
times[1] / tries[1] => 0x2f
times[2] / tries[2] => 0x38
times[3] / tries[3] => 0x34
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] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 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) => 0x40c0cef4
[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) => 0x423ec154
[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) => 0x99de
msleep(900)
[Pass] timer_func => 0x0
msleep(200)
[Pass] timer_func => 0x1
[Pass] ABS((timer_time/1000 - t0) - 1000) => 0x6
[Pass] ABS((timer_arg - ta0) - 1000) => 0xa
[Pass] timer = SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0x9a04
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) => 0x1fa
msleep(90)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x1
[Pass] ABS(DeltaT(timer_time, t0) - 100000) => 0x13f
[Pass] ABS(DeltaT(timer_arg, ta0) - 100000) => 0x10e
[Pass] ABS((get_us_clock() - t0) - 110000) => 0x1b8
[Pass] SetHPTimerAfterNow(90000, next_tick_cbr, overrun_cbr, 0) => 0x1fc
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) => 0x24f
[Pass] ABS(DeltaT(timer_arg, ta0) - 300000) => 0x226
[Pass] ABS((get_us_clock() - t0) - 310000) => 0x1e6
t0 = GET_DIGIC_TIMER() => 0x3e5c9
msleep(250)
t1 = GET_DIGIC_TIMER() => 0x79643
[Pass] ABS(MOD(t1-t0, 1048576)/1000 - 250) => 0x9
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x38
Date/time: 2018/05/06 14:21:56
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x3a
[Pass] MOD(s1-s0, 60) => 0x2
[Pass] MOD(s1-s0, 60) => 0x2
m0 = MALLOC_FREE_MEMORY => 0x42dd8
[Pass] p = (void*)_malloc(50*1024) => 0xc0a90
[Pass] CACHEABLE(p) => 0xc0a90
m1 = MALLOC_FREE_MEMORY => 0x365c8
_free(p)
m2 = MALLOC_FREE_MEMORY => 0x42dd8
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0xbc198
[Pass] p = (void*)_AllocateMemory(128*1024) => 0xc0ceb4
[Pass] CACHEABLE(p) => 0xc0ceb4
m1 = GetFreeMemForAllocateMemory() => 0x9c188
_FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0xbc198
[Pass] ABS((m0-m1) - 128*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x42dd8
m02 = GetFreeMemForAllocateMemory() => 0xbc198
[Pass] p = (void*)_alloc_dma_memory(128*1024) => 0x40c0cef4
[Pass] UNCACHEABLE(p) => 0x40c0cef4
[Pass] CACHEABLE(p) => 0xc0cef4
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40c0cef4
_free_dma_memory(p)
[Pass] p = (void*)_shoot_malloc(16*1024*1024) => 0x423ec144
[Pass] UNCACHEABLE(p) => 0x423ec144
_shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x42dd8
m12 = GetFreeMemForAllocateMemory() => 0xbc198
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
[Pass] suite = shoot_malloc_suite_contig(16*1024*1024) => 0xc0a90
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1000000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xc0ab8
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1000000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x423ec140
[Pass] UNCACHEABLE(p) => 0x423ec140
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite_contig(0) => 0xc0a90
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1f68000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xc0ab8
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1f68000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000070
[Pass] UNCACHEABLE(p) => 0x4a000070
largest_shoot_block = suite->size => 0x1f68000
[INFO] largest_shoot_block: 31MB
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(largest_shoot_block + 1024*1024) => 0xc0a90
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x3
[Pass] suite->size => 0x2068000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xc0ab8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1c10000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x423ec140
[Pass] UNCACHEABLE(p) => 0x423ec140
chunk = GetNextMemoryChunk(suite, chunk) => 0xc0b18
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1d34000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42100070
[Pass] UNCACHEABLE(p) => 0x42100070
chunk = GetNextMemoryChunk(suite, chunk) => 0xc0b50
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2068000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x413f8070
[Pass] UNCACHEABLE(p) => 0x413f8070
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x2068000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(0) => 0xc0a90
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x4
[Pass] suite->size => 0x4700000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0xc0ab8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1c10000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x423ec140
[Pass] UNCACHEABLE(p) => 0x423ec140
chunk = GetNextMemoryChunk(suite, chunk) => 0xc0b18
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x1d34000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42100070
[Pass] UNCACHEABLE(p) => 0x42100070
chunk = GetNextMemoryChunk(suite, chunk) => 0xc0b50
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2938000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x413f8070
[Pass] UNCACHEABLE(p) => 0x413f8070
chunk = GetNextMemoryChunk(suite, chunk) => 0xc0b88
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x4700000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4a000070
[Pass] UNCACHEABLE(p) => 0x4a000070
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x4700000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x16a01c
[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) => 0x16a000
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x169fe0
[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) => 0x328e00c0
[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) => 0x32900094
[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) => 0x32920202
[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) => 0x32940098
[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, 11622 passed, 0 failed.
.
API Test Redid new battery
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-5-6 14:25:23
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 133
apex = 9.625
ms = 1
value = 0.001266
aperture = table:
raw = 48
apex = 5.
value = 5.6
min = table:
raw = 37
apex = 3.625
value = 3.5
max = table:
raw = 80
apex = 9.
value = 22.6
iso = table:
raw = 0
apex = 0
value = 0
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 5200
mode = 3
metering_mode = 3
drive_mode = 1
model = "Canon EOS REBEL T3i"
model_short = "600D"
firmware = "1.0.3"
temperature = 172
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
bulb = function: p
shoot = function: p
burst = function: p
wait = function: p
reboot = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
clear = function: p
write = function: p
hide = function: p
show = function: p
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
info = function: p
pause = function: p
stop = function: p
resume = function: p
wait = function: p
start = function: p
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS"
focal_length = 18
focus_distance = 655350
hyperfocal = 3081
dof_near = 3066
dof_far = 1000000
af = true
af_mode = 0
autofocus = function: p
focus = function: p
display = table:
idle = nil
height = 480
width = 720
print = function: p
clear = function: p
on = function: p
off = function: p
notify_box = function: p
draw = function: p
load = function: p
line = function: p
circle = function: p
rect = function: p
screenshot = function: p
pixel = function: p
key = table:
last = 10
wait = function: p
press = function: p
menu = table:
visible = false
get = function: p
set = function: p
close = function: p
block = function: p
open = function: p
select = function: p
new = function: p
movie = table:
recording = false
stop = function: p
start = function: p
dryos = table:
clock = 24
ms_clock = 24404
image_prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 9997
folder_number = 100
free_space = 15633696
type = "SD"
path = "B:/"
_card_ptr = userdata
shooting_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 9997
folder_number = 100
free_space = 15633696
type = "SD"
path = "B:/"
_card_ptr = userdata
date = table:
min = 25
wday = 7
yday = 1
year = 2018
month = 5
hour = 14
day = 6
isdst = false
sec = 24
directory = function: p
rename = function: p
call = function: p
remove = function: p
interval = table:
time = 10
count = 0
running = false
stop = function: p
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:36: in function <ML/SCRIPTS/API_TEST.LUA:35>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:35: in function 'print_table'
ML/SCRIPTS/API_TEST.LUA:81: in function 'generic_tests'
ML/SCRIPTS/API_TEST.LUA:1338: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1364: in main chunktask = table:
create = function: p
yield = function: p
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
File I/O tests completed.
Testing Canon GUI functions...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Start LiveView...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Canon GUI tests completed.
Testing ML menu API...
Menu tests completed.
Testing picture taking functions...
Snap simulation test...
Single picture...
B:/DCIM/100CANON/IMG_9998.CR2: 22508842
B:/DCIM/100CANON/IMG_9998.JPG: 3915831
Two burst pictures...
Ideally, the camera should be in some continuous shooting mode (not checked).
This looks like you had Continuous AF Enabled. Not exactly sure how it works on the 600D but if the camera is trying to focus continuously while in LiveView it will be playing tug-of-war with the lua script.
Good to see you're using a lens that has completed these tests on other cameras, EF-S18-55mm f/3.5-5.6 IS. Some lenses are not working with lua on some cameras (https://www.magiclantern.fm/forum/index.php?topic=22053.msg201056#msg201056).
600D does not have the option for continuous focus like the 700D has
Weird, on this 2nd test, it never did the lens focus part.
Update: Got lens focus test to finish by changing zoom to wide open and it finished all focus movements, but the next test shut camera off and lost log results.
To save some time you can comment out all the tests that have already completed.
api_test.lua
-- note: each test routine must print a blank line at the end
-- strict_tests()
-- generic_tests()
printf("Module tests...\n")
-- test_io()
-- test_camera_gui()
-- test_menu()
-- test_camera_take_pics()
-- sleep(1)
-- test_multitasking()
-- test_keys()
-- test_lv()
-- test_lens_focus()
test_camera_exposure()
test_movie()
printf("Done!\n")
It would be interesting to try the focus test on a few different lenses, just comment out all the other tests. I found that sometimes the test needs to be restarted multiple times to get one successful run depending on the lens you're using and the mode the camera is in when you run the test. For example, the 500D can't run the focus test outside of LiveView.
Well, it wasnt the focus test that shut camera off, ran it again and as long as its wide open it always passes focus test now, just whatever test is after focus test, that one is shutting cam off and need to take battery out.
https://youtu.be/0sW4BsP8sO0
UPDATE: Good news for your 103 port, it does the exact same thing on 102, crash in same spot.
Looks like it is hanging on the ISO test. No assert error message on the console? We could try commenting out that line. Also, try running the movie test so we can narrow it down to just the test_camera_exposure() that is failing.
Good to know that I didn't break anything with the firmware update. (Like I did with the 550D.)
Got to run around this afternoon so I'll be offline for a while.
No, no console just like on video I uploaded, just turns cam off. No crash logs either
Skipped Exposure Test, all passed fine.
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-5-6 16:31:22
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 96
apex = 5.
ms = 31
value = 0.03125
aperture = table:
raw = 59
apex = 6.375
value = 9.100001
min = table:
raw = 37
apex = 3.625
value = 3.5
max = table:
raw = 80
apex = 9.
value = 22.6
iso = table:
raw = 72
apex = 5.
value = 100
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 5200
mode = 3
metering_mode = 3
drive_mode = 1
model = "Canon EOS REBEL T3i"
model_short = "600D"
firmware = "1.0.2"
temperature = 161
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
shoot = function: p
bulb = function: p
wait = function: p
burst = function: p
reboot = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
show = function: p
clear = function: p
write = function: p
hide = function: p
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
wait = function: p
stop = function: p
resume = function: p
info = function: p
pause = function: p
start = function: p
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS"
focal_length = 18
focus_distance = 655350
hyperfocal = 1909
dof_near = 1903
dof_far = 1000000
af = true
af_mode = 0
autofocus = function: p
focus = function: p
display = table:
idle = nil
height = 480
width = 720
off = function: p
on = function: p
screenshot = function: p
circle = function: p
print = function: p
rect = function: p
notify_box = function: p
draw = function: p
load = function: p
clear = function: p
line = function: p
pixel = function: p
key = table:
last = 10
press = function: p
wait = function: p
menu = table:
visible = false
new = function: p
block = function: p
set = function: p
open = function: p
select = function: p
close = function: p
get = function: p
movie = table:
recording = false
stop = function: p
start = function: p
dryos = table:
clock = 9
ms_clock = 9330
image_prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 16
folder_number = 100
free_space = 15633696
type = "SD"
path = "B:/"
_card_ptr = userdata
shooting_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 16
folder_number = 100
free_space = 15633696
type = "SD"
path = "B:/"
_card_ptr = userdata
date = table:
min = 31
isdst = false
wday = 7
yday = 1
month = 5
year = 2018
hour = 16
day = 6
sec = 23
remove = function: p
directory = function: p
call = function: p
rename = function: p
interval = table:
time = 10
count = 0
running = false
stop = function: p
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:36: in function <ML/SCRIPTS/API_TEST.LUA:35>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:35: in function 'print_table'
ML/SCRIPTS/API_TEST.LUA:81: in function 'generic_tests'
ML/SCRIPTS/API_TEST.LUA:1338: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1364: in main chunktask = table:
create = function: p
yield = function: p
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
File I/O tests completed.
Testing Canon GUI functions...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Start LiveView...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Stop LiveView...
Enter PLAY mode...
Exit PLAY mode...
Start LiveView...
Pause LiveView...
Resume LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Stop LiveView...
Start LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Stop LiveView...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Canon GUI tests completed.
Testing ML menu API...
Menu tests completed.
Testing picture taking functions...
Snap simulation test...
Single picture...
B:/DCIM/100CANON/IMG_0017.CR2: 25094833
B:/DCIM/100CANON/IMG_0017.JPG: 4848220
Two burst pictures...
Ideally, the camera should be in some continuous shooting mode (not checked).
B:/DCIM/100CANON/ABC_0018.CR2: 25128798
B:/DCIM/100CANON/ABC_0018.JPG: 4849283
B:/DCIM/100CANON/ABC_0019.CR2: 25097122
B:/DCIM/100CANON/ABC_0019.JPG: 4831500
Bracketed pictures...
B:/DCIM/100CANON/IMG_0020.CR2: 24226800
B:/DCIM/100CANON/IMG_0020.JPG: 4858297
B:/DCIM/100CANON/IMG_0021.CR2: 25116757
B:/DCIM/100CANON/IMG_0021.JPG: 4864994
B:/DCIM/100CANON/IMG_0022.CR2: 23374510
B:/DCIM/100CANON/IMG_0022.JPG: 3675372
Bulb picture...
Elapsed time: 11925
B:/DCIM/100CANON/IMG_0023.CR2: 14243432
B:/DCIM/100CANON/IMG_0023.JPG: 363713
Picture taking tests completed.
Testing multitasking...
Only one task allowed to interrupt...
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Multitasking tests completed.
Testing half-shutter...
Half-shutter test OK.
Testing module 'lv'...
Starting LiveView...
Overlays: Canon
Overlays: ML
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: disabled
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: disabled
Overlays: ML
Overlays: disabled
Overlays: ML
Setting zoom to x1...
Setting zoom to x5...
Setting zoom to x10...
Setting zoom to x5...
Setting zoom to x1...
Setting zoom to x10...
Setting zoom to x1...
Pausing LiveView...
Resuming LiveView...
Stopping LiveView...
LiveView tests completed.
Testing lens focus functionality...
Autofocus outside LiveView...
Focus distance: 5270
Autofocus in LiveView...
Please trigger autofocus (half-shutter / AF-ON / * ).
19...18...17...Autofocus triggered.
Autofocus completed.
Focus distance: 655350
Focusing backward...
Focus distance: 655350
Focus motor position: 92
Focusing forward with step size 3, wait=true...
.......
Focus distance: 250
Focus motor position: -1796
Focusing backward with step size 3, wait=true...
........
Focus distance: 655350
Focus motor position: 111
Focus range: 7 steps forward, 8 steps backward.
Motor steps: 1888 forward, 1907 backward, 19 lost.
Focusing forward with step size 3, wait=false...
.........................
Focus distance: 250
Focus motor position: -1761
Focusing backward with step size 3, wait=false...
.......................
Focus distance: 655350
Focus motor position: 134
Focus range: 25 steps forward, 23 steps backward.
Motor steps: 1872 forward, 1895 backward, 23 lost.
Focusing forward with step size 2, wait=true...
.....................................
Focus distance: 250
Focus motor position: -1753
Focusing backward with step size 2, wait=true...
.....................................
Focus distance: 655350
Focus motor position: 119
Focus range: 37 steps forward, 37 steps backward.
Motor steps: 1887 forward, 1872 backward, 15 lost.
Focusing forward with step size 2, wait=false...
...
Focus distance: 250
Focus motor position: -1768
Focusing backward with step size 2, wait=false...
...
Focus distance: 655350
Focus motor position: 109
Focus range: 156 steps forward, 105 steps backward.
Motor steps: 1887 forward, 1877 backward, 10 lost.
Focusing forward with step size 1, wait=true...
...
Focus distance: 250
Focus motor position: -1850
Focusing backward with step size 1, wait=true...
...
Focus distance: 655350
Focus motor position: 126
Focus range: 149 steps forward, 150 steps backward.
Motor steps: 1959 forward, 1976 backward, 17 lost.
Focusing forward with step size 1, wait=false...
...
Focus distance: 250
Focus motor position: -1850
Focusing backward with step size 1, wait=false...
...
Focus distance: 655350
Focus motor position: 121
Focus range: 307 steps forward, 299 steps backward.
Motor steps: 1976 forward, 1971 backward, 5 lost.
Focus test completed.
Testing movie recording...
Please switch to Movie mode.
Movie recording tests completed.
Done!
UPDATE: If the Exposure test is done by itself, it passes just fine.
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-5-6 16:49:11
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 75
apex = 2.375
ms = 193
value = 0.192776
aperture = table:
raw = 59
apex = 6.375
value = 9.100001
min = table:
raw = 37
apex = 3.625
value = 3.5
max = table:
raw = 80
apex = 9.
value = 22.6
iso = table:
raw = 104
apex = 9.
value = 1600
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 5200
mode = 3
metering_mode = 3
drive_mode = 1
model = "Canon EOS REBEL T3i"
model_short = "600D"
firmware = "1.0.2"
temperature = 168
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
wait = function: p
bulb = function: p
reboot = function: p
shoot = function: p
burst = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
show = function: p
write = function: p
clear = function: p
hide = function: p
lv = table:
enabled = true
paused = false
running = true
zoom = 1
overlays = 2
stop = function: p
wait = function: p
pause = function: p
resume = function: p
start = function: p
info = function: p
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS"
focal_length = 18
focus_distance = 655350
hyperfocal = 1909
dof_near = 1903
dof_far = 1000000
af = true
af_mode = 0
autofocus = function: p
focus = function: p
display = table:
idle = nil
height = 480
width = 720
on = function: p
rect = function: p
pixel = function: p
clear = function: p
load = function: p
draw = function: p
notify_box = function: p
circle = function: p
off = function: p
print = function: p
screenshot = function: p
line = function: p
key = table:
last = 9
wait = function: p
press = function: p
menu = table:
visible = false
set = function: p
close = function: p
open = function: p
get = function: p
new = function: p
select = function: p
block = function: p
movie = table:
recording = false
stop = function: p
start = function: p
dryos = table:
clock = 20
ms_clock = 20466
image_prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 24
folder_number = 100
free_space = 15404160
type = "SD"
path = "B:/"
_card_ptr = userdata
shooting_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 24
folder_number = 100
free_space = 15404160
type = "SD"
path = "B:/"
_card_ptr = userdata
date = table:
month = 5
year = 2018
min = 49
hour = 16
wday = 7
isdst = false
yday = 1
day = 6
sec = 13
directory = function: p
remove = function: p
rename = function: p
call = function: p
interval = table:
time = 10
count = 0
running = false
stop = function: p
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:36: in function <ML/SCRIPTS/API_TEST.LUA:35>
[C]: in function 'globals.xpcall'
ML/SCRIPTS/API_TEST.LUA:35: in function 'globals.print_table'
ML/SCRIPTS/API_TEST.LUA:81: in function 'globals.generic_tests'
ML/SCRIPTS/API_TEST.LUA:1338: in function 'globals.api_tests'
ML/SCRIPTS/API_TEST.LUA:1364: in main chunktask = table:
yield = function: p
create = function: p
property = table:
Generic tests completed.
Module tests...
Testing exposure settings...
Camera : Canon EOS REBEL T3i (600D) 1.0.2
Lens : EF-S18-55mm f/3.5-5.6 IS
Shoot mode: 3
Shutter : ,5 (raw 75, 0.192776s, 193ms, apex 2.375)
Aperture : 9.1 (raw 59, f/9.100001, apex 6.375)
Av range : 3.5..22 (raw 37..80, f/3.5..f/22.6, apex 3.625..9.)
ISO : €1600 (raw 104, 1600, apex 9.)
EC : 0.0 (raw 0, 0 EV)
Flash EC : 0.0 (raw 0, 0 EV)
Setting shutter to random values...
Setting ISO to random values...
Setting aperture to random values...
Please switch to Av mode.
Setting EC to random values...
Setting Flash EC to random values...
Exposure tests completed.
Done!
Great -- I'm still waiting for my wife to get ready to go out so---Don't kill me but yet another test?
Remove this section out of the exposure test and run just the exposure test again. Let's see if shutter and aperture are working and it is only ISO that's the problem.
request_mode(MODE.M, "M")
old_value = camera.iso.raw
printf("Setting ISO to random values...\n")
for k = 1,100 do
local method = math.random(1,3)
local d = nil
if method == 1 then
local iso = math.random(100, 6400)
if math.random(1,2) == 1 then
camera.iso.value = iso
else
camera.iso = iso
end
d = math.abs(math.log(camera.iso.value,2) - math.log(iso,2))
elseif method == 2 then
local apex = math.random(5*100,11*100)/100
camera.iso.apex = apex
d = math.abs(camera.iso.apex - apex)
elseif method == 3 then
local raw = math.random(72, 120)
camera.iso.raw = raw
d = math.abs(camera.iso.raw - raw) / 8
end
-- difference between requested and actual ISO should be max 1/3 EV
if d > 1/3 then
printf("Error: ISO delta %s EV\n", d)
end
-- ISO and Sv (APEX) should be consistent
local expected_apex = math.log(camera.iso.value/3.125, 2)
if math.abs(expected_apex - camera.iso.apex) > 0.2 then
printf("Error: ISO %s != Sv%s, expected %s\n", camera.iso.value, camera.iso.apex, expected_apex)
end
-- setting ISO to the same value, using any method (value,apex,raw)
-- should not change anything
for i,field in pairs{"value","apex","raw"} do
local current = {}
current.apex = camera.iso.apex
current.value = camera.iso.value
current.raw = camera.iso.raw
camera.iso[field] = current[field]
if camera.iso.value ~= current.value then
printf("Error: ISO set to %s=%s, got %s, expected %s\n", field, current[field], camera.iso.value, current.value)
end
if camera.iso.apex ~= current.apex then
printf("Error: ISO set to %s=%s, got Sv%s, expected Sv%s\n", field, current[field], camera.iso.apex, current.apex)
end
if camera.iso.raw ~= current.raw then
printf("Error: ISO set to %s=%s, got %s, expected %s (raw)\n", field, current[field], camera.iso.raw, current.raw)
end
end
end
camera.iso.raw = old_value
Doesn't seem to be either of them cause the whole exposure test finishes just fine if done by itself, just crashes cam if all tests are done with it. So guess there's no point in editing the exposure script.
The camera state must be changed in some way by the time it gets to the exposure test that makes it crash since it can pass just fine from a fresh cam restart.
UPDATE:
Well, I played with placement of Camera Exposure Test, if it is first in the list, all tests complete fine.
If it goes anywhere after IO test, it crashes with this.
(https://thumb.ibb.co/jFCwtn/VRAM0.jpg) (https://ibb.co/jFCwtn)
UPDATE 2: It seems to be copy_test("autoexec.bin", "tmp.bin") inside IO test
Guess its just running out of memory to finish the other tests after it copies?
If I put all the tests back in the normal order and just comment out copy_test inside test_io test then that fixes everything.
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-5-6 20:59:23
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 128
apex = 9.
ms = 2
value = 0.001953
aperture = table:
raw = 59
apex = 6.375
value = 9.100001
min = table:
raw = 37
apex = 3.625
value = 3.5
max = table:
raw = 80
apex = 9.
value = 22.6
iso = table:
raw = 72
apex = 5.
value = 100
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = -12
value = -1.5
kelvin = 5200
mode = 3
metering_mode = 3
drive_mode = 1
model = "Canon EOS REBEL T3i"
model_short = "600D"
firmware = "1.0.2"
temperature = 155
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
burst = function: p
wait = function: p
bulb = function: p
shoot = function: p
reboot = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
write = function: p
show = function: p
hide = function: p
clear = function: p
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
stop = function: p
start = function: p
info = function: p
wait = function: p
pause = function: p
resume = function: p
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS"
focal_length = 18
focus_distance = 760
hyperfocal = 1909
dof_near = 558
dof_far = 1216
af = true
af_mode = 0
focus = function: p
autofocus = function: p
display = table:
idle = nil
height = 480
width = 720
screenshot = function: p
off = function: p
rect = function: p
line = function: p
notify_box = function: p
draw = function: p
load = function: p
pixel = function: p
print = function: p
on = function: p
circle = function: p
clear = function: p
key = table:
last = 10
press = function: p
wait = function: p
menu = table:
visible = false
block = function: p
select = function: p
set = function: p
open = function: p
new = function: p
get = function: p
close = function: p
movie = table:
recording = false
start = function: p
stop = function: p
dryos = table:
clock = 18
ms_clock = 18904
image_prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 53
folder_number = 100
free_space = 15600928
type = "SD"
_card_ptr = userdata
path = "B:/"
shooting_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 53
folder_number = 100
free_space = 15600928
type = "SD"
_card_ptr = userdata
path = "B:/"
date = table:
month = 5
year = 2018
day = 6
yday = 1
min = 59
isdst = false
sec = 24
wday = 7
hour = 20
remove = function: p
rename = function: p
directory = function: p
call = function: p
interval = table:
time = 10
count = 0
running = false
stop = function: p
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:36: in function <ML/SCRIPTS/API_TEST.LUA:35>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:35: in function 'print_table'
ML/SCRIPTS/API_TEST.LUA:81: in function 'generic_tests'
ML/SCRIPTS/API_TEST.LUA:1338: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1364: in main chunktask = table:
yield = function: p
create = function: p
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
File I/O tests completed.
Testing Canon GUI functions...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Resume LiveView...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Canon GUI tests completed.
Testing ML menu API...
Menu tests completed.
Testing picture taking functions...
Snap simulation test...
Single picture...
B:/DCIM/100CANON/IMG_0054.CR2: 22956594
B:/DCIM/100CANON/IMG_0054.JPG: 4822231
Two burst pictures...
Ideally, the camera should be in some continuous shooting mode (not checked).
B:/DCIM/100CANON/ABC_0055.CR2: 23009531
B:/DCIM/100CANON/ABC_0055.JPG: 4848494
B:/DCIM/100CANON/ABC_0056.CR2: 23052820
B:/DCIM/100CANON/ABC_0056.JPG: 4864321
Bracketed pictures...
B:/DCIM/100CANON/IMG_0057.CR2: 20934042
B:/DCIM/100CANON/IMG_0057.JPG: 3050554
B:/DCIM/100CANON/IMG_0058.CR2: 23038542
B:/DCIM/100CANON/IMG_0058.JPG: 4853789
B:/DCIM/100CANON/IMG_0059.CR2: 26637511
B:/DCIM/100CANON/IMG_0059.JPG: 5049995
Bulb picture...
Elapsed time: 11754
B:/DCIM/100CANON/IMG_0060.CR2: 17216150
B:/DCIM/100CANON/IMG_0060.JPG: 1215102
Picture taking tests completed.
Testing multitasking...
Only one task allowed to interrupt...
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Multitasking tests completed.
Testing half-shutter...
Half-shutter test OK.
Testing module 'lv'...
LiveView is running; stopping...
Starting LiveView...
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: ML
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: disabled
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Setting zoom to x1...
Setting zoom to x5...
Setting zoom to x10...
Setting zoom to x5...
Setting zoom to x1...
Setting zoom to x10...
Setting zoom to x1...
Pausing LiveView...
Resuming LiveView...
Stopping LiveView...
LiveView tests completed.
Testing lens focus functionality...
Autofocus outside LiveView...
Focus distance: 1130
Autofocus in LiveView...
Please trigger autofocus (half-shutter / AF-ON / * ).
19...18...17...16...15...14...13...12...11...10...9...8...7...6...5...4...3...Autofocus triggered.
Autofocus completed.
Focus distance: 760
Focusing backward...
Focus distance: 655350
Focus motor position: 582
Focusing forward with step size 3, wait=true...
.......
Focus distance: 250
Focus motor position: -1287
Focusing backward with step size 3, wait=true...
.......
Focus distance: 655350
Focus motor position: 607
Focus range: 7 steps forward, 7 steps backward.
Motor steps: 1869 forward, 1894 backward, 25 lost.
Focusing forward with step size 3, wait=false...
..............................
Focus distance: 250
Focus motor position: -1263
Focusing backward with step size 3, wait=false...
............................
Focus distance: 655350
Focus motor position: 630
Focus range: 30 steps forward, 28 steps backward.
Motor steps: 1870 forward, 1893 backward, 23 lost.
Focusing forward with step size 2, wait=true...
....................................
Focus distance: 250
Focus motor position: -1230
Focusing backward with step size 2, wait=true...
.....................................
Focus distance: 655350
Focus motor position: 652
Focus range: 36 steps forward, 37 steps backward.
Motor steps: 1860 forward, 1882 backward, 22 lost.
Focusing forward with step size 2, wait=false...
...
Focus distance: 250
Focus motor position: -1210
Focusing backward with step size 2, wait=false...
...
Focus distance: 655350
Focus motor position: 667
Focus range: 120 steps forward, 126 steps backward.
Motor steps: 1862 forward, 1877 backward, 15 lost.
Focusing forward with step size 1, wait=true...
...
Focus distance: 250
Focus motor position: -1283
Focusing backward with step size 1, wait=true...
...
Focus distance: 655350
Focus motor position: 685
Focus range: 150 steps forward, 151 steps backward.
Motor steps: 1950 forward, 1968 backward, 18 lost.
Focusing forward with step size 1, wait=false...
...
Focus distance: 250
Focus motor position: -1266
Focusing backward with step size 1, wait=false...
...
Focus distance: 655350
Focus motor position: 743
Focus range: 296 steps forward, 325 steps backward.
Motor steps: 1951 forward, 2009 backward, 58 lost.
Focus test completed.
Testing exposure settings...
Camera : Canon EOS REBEL T3i (600D) 1.0.2
Lens : EF-S18-55mm f/3.5-5.6 IS
Shoot mode: 3
Shutter : ,5 (raw 75, 0.192776s, 193ms, apex 2.375)
Aperture : 9.1 (raw 59, f/9.100001, apex 6.375)
Av range : 3.5..22 (raw 37..80, f/3.5..f/22.6, apex 3.625..9.)
ISO : €1600 (raw 104, 1600, apex 9.)
EC : 0.0 (raw 0, 0 EV)
Flash EC : -1.5 (raw -12, -1.5 EV)
Setting shutter to random values...
Setting ISO to random values...
Setting aperture to random values...
Please switch to Av mode.
Setting EC to random values...
Setting Flash EC to random values...
Exposure tests completed.
Testing movie recording...
Please switch to Movie mode.
Movie recording tests completed.
Done!
Nice find. Not the first time I saw that error message (https://www.magiclantern.fm/forum/index.php?topic=14828.msg201107#msg201107). So it looks like the 600D is passing all the tests and 1.0.3 should be good to go once we get reports on that last item a1ex asked for:
Quote from: a1ex on December 16, 2017, 01:36:42 AM
- overall sanity check (for example, if you decide to take this build out and use it for a couple of hours, please report back)
I have 1.0.3 and the test version of ML up and running. I'll walk around with it for a few days. Anything specific I should be looking for?
Quote from: irvcobb on May 09, 2018, 04:14:13 PM
Anything specific I should be looking for?
Nothing specific. Basically try it out and tell us if it is working for you. If you encounter any issues check to see if the same issues are in 1.0.2. Most important of all, please report back.
I've taken the camera on a couple brief outings, and ML seems to work as expected. Specifically, DualISO, ETTR, and focus blinkies are working fine. I'm not a video guy, so don't know enough to play with that. Will continue to experiment and report.
Thanks for the testing. Looks like the firmware update is working fine. At least we didn't break anything that was working and found some quirks with the ML tests on various cameras.
@a1ex and all others here :)
Are there any news/fixes for the bug with the black bars that appear on the HDMI out display?
See my posts from january, beginning here: https://www.magiclantern.fm/forum/index.php?topic=15360.msg196249#msg196249
I've shot some more with 1.0.3 with no issues. Specifically checked focus stacking and it works fine.
I'm troubleshooting a 600D that no longer boots, and would like some logs to cross-check the results:
https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log/
-> build #25 was reported to work (able to save a log from the bad camera, but screen is black)
https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log-mpu/
-> build #7 was reported not to boot, but it works fine in QEMU (direct link (https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log-mpu/7/))
-> build #10 is from an older codebase (same as #25 from above, just with different logging options)
Would like to make sure these 3 builds are all working fine on a healthy 600D. They all work in QEMU.
This one boots fine on the 600D:
magiclantern-startup-log.2018May20.600D102.zip
LOG(accidentally overwrote this log with one below, tell me if you need it at all and rerun it.)
This one working too:
magiclantern-startup-log-mpu.2018May29.600D102.zip
LOG
https://bitbucket.org/Dannephoto/magic-lantern/downloads/DM-0000.LOG
There was a third build to test. Would appreciate a direct link to it. Gotta run atm...
EDIT:
Last one also working
magiclantern-startup-log-mpu.2018May20.600D102.zip
LOG:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-startup-log-mpu.2018May20.600D102.zip.LOG
All three versions working.
Updated.
Just returned from vacation. Shot about 1000 frames with 1.0.3. No issues noted.
There's a new build for 1.0.2. Any chance for one for 1.0.3, dfort?
I recently returned from vacation too. Updating firmware pull requests to the latest unified commits is on my todo list. Thanks for the wake up call.
Also got something to test on 600D, for the audio side: https://bitbucket.org/hudson/magic-lantern/pull-requests/420/refactor-audio-to-use-new-config-var/diff
Please document any changes in functionality in the config_var_refactor (https://bitbucket.org/hudson/magic-lantern/branch/config_var_refactor) branch, compared to unified. There shouldn't be any, as the PR is supposed to just refactor things, but I did notice surprises on other models.
@irvcobb - made a bunch of new firmware update builds including the 600D.103
All other 600D users, I also made a test build of the config_var_refactor that you can compare to the unified build on the nightly builds page (https://builds.magiclantern.fm/).
As usual, my test builds are posted on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
Got it, and thanks. Will see what it does later tonight.
Took the 600D to the stock car races last night. Battery consumption seemed very high. Might be be ML, might be my batteries, might be my imagination. Thought I'd report. Will check into it some, but will be slow. Life keeps getting in the way of leisure.
hi everyone, newbie to the forum.
I notice that newbies are pretty useless, (and maybe not too welcome) and I may well be the same.
However that said, I have read through this entire thread, and my question is pretty simple.
If I want to be safe, I should only update my firmware to 1.02, (which I was able to get from a link provided in the thread), instead of the 1.03 which is available on the Canon website?
I have just bought a Canon EOS 600D (used, as new) which came from Germany. It's got version 1.01 firmware on it at the moment.
I see the last few posts (apart from the testing posts, which mainly go right over my head) mention that everything seems to be working with 1.03.
In some ways I would rather use the latest Canon official firmware, but I see that the first page still says to use version 1.02, although it links to the Canon website, which only offers 1.03.
Also, I wish to note that I saw (and understand) the general warning given that until one is used to the original Canon software functions, one doesn't need the extra complexity. However, I only bought this camera to do timelapse videos (or at least mainly) and I misunderstood the Canon specifications where it said
QuoteDrive Modes Single, Continuous, Self timer (2s, 10s+remote, 10s + continuous shots 2-10)
I thought this last referred to being able to take shots at intervals from 2 to ten seconds, not that it would take two to ten shots after self timer.
My bad.
Your software seems to be my saviour, as of course, it offers the intervalometer, and also the reduced frame rate shooting videos.
Most of the rest of the functions are probably just extra confusion for me, without a doubt.
I owned a Canon A-1 as a teenager (yes, I am that old!) and it was my pride and joy, bought with my own money earned in my part time jobs, but I sold it to buy a motorbike later. I never had another SLR (too much sadness) and have only had compact cameras since I started having cameras again a couple of decades ago.
I am also investigating as it seems that that the EOS software that comes with the camera, perhaps allows timelapse to be organised from the computer itself. That would allow me to set up my main project, as it is timelapse of my drawing projects, but I would still be interested in the more general use of the camera for timelapse.
Thanks in advance to anyone who takes the time to answer my query.
Saludos, as they say here in Spain.
Quote from: spaingaroo on September 23, 2018, 05:07:05 PM
If I want to be safe, I should only update my firmware to 1.02, (which I was able to get from a link provided in the thread), instead of the 1.03 which is available on the Canon website?
I have just bought a Canon EOS 600D (used, as new) which came from Germany. It's got version 1.01 firmware on it at the moment.
In some ways I would rather use the latest Canon official firmware, but I see that the first page still says to use version 1.02, although it links to the Canon website, which only offers 1.03.
Fixed the link in the first post. Thanks. Valid links are always present in the camera download pages. https://builds.magiclantern.fm/
Publicly available builds of ML for the 600D are only available (working on) firmware 1.0.2. If you want to use ML for the 600D, then you must be running the correct firmware for code.
I see the value in wanting to use the latest update (the 1.0.2 version we link to is
official Canon firmware, just to be precise), but there is also value in the saying, "if it ain't broke, don't fix it".
The 1.0.3 firmware update only fixed a
minor issue.
https://www.canon.com.au/support/support-news/firmware-updates/2016/eos-600d-firmware-version-1,-d-,0,-d-,3
QuoteFirmware Version 1.0.3 incorporates the following fixes:
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.
If you don't use this lens with this camera, then the update is mostly mute (imho).
Quote from: spaingaroo on September 23, 2018, 05:07:05 PM
I see the last few posts (apart from the testing posts, which mainly go right over my head) mention that everything seems to be working with 1.03.
There is a pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/915/update-to-600d103/diff) to port the main builds of ML to firmware 1.0.3. These pull requests are subject to a bunch of development related stuff before they are made available to all users. If you spend some time here, read sticky threads are so forth, it's actually reasonably easy to setup your own compiling environment, so that you may make your own 1.0.3 build of ML and help the developers test the code (beta test). If you're worried about breaking your camera, that's fine too. :)
Based on your own observations of the discussion in this thread, it seems like the 1.0.3 port is stable, and just waiting for that developer stuff (users to test and report back to devs) to be polished.
You can still use the 1.0.3 firmware and help test ML without having to compile code by yourself. @dfort has builds available on his bitbucket page. See a few posts above this one.
Quote from: Audionut on September 25, 2018, 07:48:37 AM
Fixed the link in the first post. Thanks. Valid links are always present in the camera download pages. https://builds.magiclantern.fm/
Publicly available builds of ML for the 600D are only available (working on) firmware 1.0.2. If you want to use ML for the 600D, then you must be running the correct firmware for code.
I see the value in wanting to use the latest update (the 1.0.2 version we link to is official Canon firmware, just to be precise), but there is also value in the saying, "if it ain't broke, don't fix it".
The 1.0.3 firmware update only fixed a minor issue.
https://www.canon.com.au/support/support-news/firmware-updates/2016/eos-600d-firmware-version-1,-d-,0,-d-,3
If you don't use this lens with this camera, then the update is mostly mute (imho).
There is a pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/915/update-to-600d103/diff) to port the main builds of ML to firmware 1.0.3. These pull requests are subject to a bunch of development related stuff before they are made available to all users. If you spend some time here, read sticky threads are so forth, it's actually reasonably easy to setup your own compiling environment, so that you may make your own 1.0.3 build of ML and help the developers test the code (beta test). If you're worried about breaking your camera, that's fine too. :)
Based on your own observations of the discussion in this thread, it seems like the 1.0.3 port is stable, and just waiting for that developer stuff (users to test and report back to devs) to be polished.
You can still use the 1.0.3 firmware and help test ML without having to compile code by yourself. @dfort has builds available on his bitbucket page. See a few posts above this one.
Thanks for that Audionut, I ended finding that out too, about the fact it was only a fix for that one lens, basically as you said.
I am not game to risk the camera, nor I am really willing to learn enough to be of use to others.
Sorry.
I really have enough trouble trying to keep up with my own needs. Sounds selfish, but my own needs include 12 rescues, so it's only sort of.
Instead, I will happily use the firmware 1.02 and try not to make anything break.
haha
Hopefully I can make some timelapses that seem worth it.
Cheers.
Thanks for fixing the link too, I got the link from within the discussion, but good move.
And thanks to all those who are helping with the community and getting this sort of software out there.
Canon needs to learn a trick or two.
I was so disappointed when I realised the camera couldn't do it for itself, and then along came magiclantern and led me out of the darkness, I hope. jaja
I just realised I have another problem now
reading the instrucciones again, carefully. It says to check the size of the firmware file formed after the self-extractor creates it.
QuoteThe name and size of the firmware update file can be checked on the website.
But, of course, only the name and size of 1.03 is on their website.
Does anybody have the info for 1.02?
I'll try a bit of googling
Suggestion: Ignore this!
Fixed the first post. Better?
A successful installation following those first page instructions. Thanks for the instructions. Thanks for the software.
In case anyone else comes along with the same question. Re: size of file of firmware v1.02 after extraction.
file name: CCF11102.FIR, file size: 12,232,284 bytes
Hi,
I see the nightly build for the 600D fail 1-2 tests. Which version could I install which optimally would pass all the tests?
There is none passing all the emulator tests.
QuoteThese tests are automated - if they fail, there might be either a real bug in the tested build, or a bug in the emulation. The only way to tell is by testing on real hardware and comparing the results - your feedback is welcome!
Assuming this is the correct location to post following(?)...
So I was already running a compatible firmware version/ML build on 600D/T3i for years (fmwr 1.0.2), and stupidly installed Canon's 1.0.3 last night. Have not been able to succeed in any downgrade attempts back to 1.0.2. Working directly off SD card for all downgrade attempts (not connected to Mac 10.6/Utility for any of my tries)...
I believe I've tried everything in firmware update (downgrade) attempts! When I have 1.0.2 on SD only, camera hangs between starting firmware upgrade step and screen where I would pick the version... red indicator LED blinks slowly is all that happens. Blank/black screen. If I put both firmware 1.0.3 AND 1.0.2 on SD card, I can get further through the upgrade steps in camera... actually selecting the 1.0.2 version from LCD menu (I see both versions displayed), but shortly after receive message on lines of "sorry buddy, this ain't happenin' remove battery"
Any tips on how I can force camera back to 1.0.2?? (or, what are chances developer is possibly going to tickle ML file to be compatible with this firmware version (1.0.3), esp. considering age of the 600D?)
All help much appreciated! Use ML lots and miss it already...
If you have a spare card with 32 GByte (or less) capacity:
- Format card in cardreader
- Remove and insert battery
- Insert card in cam and format again
- Copy Canon firmware file CCF11102.FIR to card.
- Insert card and battery and startup cam.
- Downgrade to 1.0.2.
Report back. And avoid crossposting.
Hello Walter. Thanks for taking the time to reply. All of those things I'd already done repeatedly to no avail. However...
(and this is where it gets weird)... This morning I downloaded another copy of the 1.0.2 firmware from a different site, and repeated the usual steps. This time it worked!
To review, I had a 1.0.2 firmware copy originally downloaded from Canon stored in three places (on the card in camera itself - the one from which ML normally runs), a dedicated installer card (from which I updated the camera back when I first started using ML) and on my computer.
None of these three worked as described in my original post. Afterwards, I searched and found a copy of 1.0.2 online at a major (reputable?) support site, and tried using that one also without success.
This morning I risked a download of 1.0.2 from a site that I did not recognize as reputable, meaning it wasn't a major or common site relative to photography, however this copy successfully installed (down-graded) as expected!
Some relevant (??) data: All of the firmware files referenced in this exercise are exactly the same file size, and equal the size referenced in the "read me" included in the downloads. The ONLY difference is that all of the ones tried prior to the final successful attempt were downloaded as .dmg files (I'm on a mac)... and this morning's came as a ZIP file!
Regardless, glad to have ML back in service, and thanks again.
Thank you for your feedback.
BTW: Those Canon firmware files linked in this site (=download pages) are not dmgs but exe or zip which will be expanded in macOS/OS X without troubles.
You may want to run MD5 or CRC32 check on those FIR files to see if there are any differences. File size doesn't really say that much about file integrity.
Hi, Movie Restart is missing in my T3i menu after installing . Someone could help me resolve this please?
Here's Build : magiclantern-Nightly.2018Jul03.600D102
It should be there, according to feature matrix (https://builds.magiclantern.fm/features.html)
Movie tab -> Movie Tweaks -> Movie Restart
Hi, everyone
I followed installation guide 15 minutes ago.
It's not finished yet, still showing upgrade screen
What should I do ?
PS : I just remained what I missed : I did not format from camera, but from my computer
PS2 : the camera shutdown itself, and I could start it, problem solved !
Regards
(https://i.ibb.co/QX9BmL6/l-Qkbq-N6u7d-AJus9-UXCj-JAGKrtpcq-BEK-XCMwu-Vf-ZPsbz1-Wd96532-G-2-HNr1-Wwj1-Q7b-Nxp-SRrl-Jpko-Bdyrd-EPis-EWHvm-Pbt-h-014-GMCas1-S-Wgp-Hu7-Lpxoos-UWk1-Qk-Qcf-Ysam-PKw-Y5-AD2j-Kmgu-ITZ6-Bpy4du3j8-DAf-LRHr3-Lggy2-I8-Z-k1n-Te-RIAi3ut-Yf0-Zc97ica-Io-Q-rc6ik56-Ald-JM2-MPELAo-OTk3-Pi-YTic-w-Rs-Bxs-VBKk-OEOve4-V-5vr.jpg) (https://ibb.co/QX9BmL6)
Quote from: mk11174 on May 06, 2018, 05:53:20 AM
I tried this on both 1.02 and 1.03 and I get the exact same results, no problem with Format changing option with Q button in Live View or Without Live view.
As for ML submenus, these can be used only while in Photo Mode without Live View, once you turn on Live View or Moviemode, it seems like Q button no longer works with ML menus to get in the Submenus, BUT, the Play button seems to work as the Q button. So I can get in and out of Submenus with Play button and Q button in Photo Mode no Live View and In Live View or Movie mode only Play button allows use of Submenus.
After chatting with a 600D user, I have finally understood what this report means. TLDR: menu navigation is broken in the lua_fix branch on 600D and 1100D.
Yes, PLAY works like Q in this branch, but it was a change meant for EOS M and other cameras without this button. This change in behavior shouldn't be considered "normal" for 600D (and other related models); that's a serious bug (in my opinion) that I need to fix before merging lua_fix into mainline.
Where does this bug come from? The 600D uses two different (!) button codes for Q: in LiveView vs photo mode.
7C5CB> **INT-36h*:00cb7730:00:00: *** mpu_recv(06 05 06 05 01 00), from ff1db6d8 ; BGMT_Q (used in Canon menu)
693B8> **INT-36h*:00cb7730:00:00: *** mpu_recv(06 05 06 20 01 00), from ff1db6d8 ; BGMT_Q (used in LiveView)
The unified branch uses two button codes (so it works fine). With the recent cleanups for Q button, I was hoping to get rid of some of the complexity, but it looks like that duplicate button code wasn't there without reason. Other cameras don't share this issue - 550D uses the first code in both LiveView and Canon menu, 60D uses the second code in both cases, 1100D appears to behave just like 600D. 1200D appears to be like 60D. Some older notes on this:
Quote from: a1ex on May 02, 2018, 11:42:05 AM
This issue is quite puzzling.
I could easily identify this button code in QEMU. Canon firmware accepts both codes - the new one is used in recent cameras, so that makes a bit of sense. The only models still using the old button code are 1100D, 600D and 550D.
550D/600D/1100D/1200D in QEMU: old code (05 01 on the MPU side) is translated into PRESS_DIRECT_PRINT_BUTTON, new code (20 01) is translated into PRESS_UNAVI_BUTTON. They both do the same action on Canon UI (e.g. activate the settings screen).
550D clearly uses the old MPU code (05 01).
Oh well, such a simple nitpick, so hard to get it right without proper testing feedback...
At least I can now test both button codes in QEMU, i.e. I have everything I need to fix it (no need to capture further logs or other stuff like that).
Edit Dec. 23: test builds posted (https://builds.magiclantern.fm/experiments.html#lua_fix), please report back.
What version of ML are you running on your Canon 600D/T3i's?
I've used ML 2.3 for years and finally decided it might be time to upgrade. Having not been on the website in many years I pulled the latest "nightly build" for the T3i (Latest Build: 2018-07-03) So far so good on a new 64GB SD card. I still have 2.3 on each of my collection of 16GB cards.
Finding the new interface a bit easier to navigate. Haven't ran into any issues yet. I mostly use ML to help with video/audio adjustments. The Zoom Focus box is probably the main reason I use ML.
Thanks to anyone still rocking a T3i and ML who responds.
I'm running a development version of ML 20180704 Nightly on Canon's v103 firmware. Been testing it for a few months with no issues. Wouldn't do without it. :-)
Glad to hear you're having a good experience with the 1.0.3 firmware update. It would be great to get some comments on the pull request.
https://bitbucket.org/hudson/magic-lantern/pull-requests/915/update-to-600d103/diff
Old guy who can't figure out how to add a comment. I've been using the 103 version since maybe June. No issues whatsoever. Shot a few thousand clicks and a little video.
Hi, first post here....
I am currently on a 40D and since ML has not been available I am considering getting a 600D to play around with ML and as a video recorder for family videos. Do you think this is a wise choice? I have considered all options and even though the camera is quite old I can get a reasonable deal and as a second camera for ML/video it seems to me the best bang for buck available.
Opinions/suggestions?
Hi guys I'll buy a 600D in next few days, the latest build is the most stable and safe? I have see on build log that firmware 03jul2018 is marked failed, so why?
NEW HERE, LOVING IT
TWO QUESTIONS ON BIT RATE AND OVERHEATING
Hi folks,
I installed the July 3, 2018 build for the 600D (the latest I think). Most things are work very well. I have just a couple of questions:
1. BIT RATE
Mostly interested in the higher bit rates for compression. When I use the default of 1.0. I am getting a bit rate readout on the LCD screen while filming of upper 30's. When I push that setting up to 2.0 or even 3.0 (audio off), it seems to only go up a bit to mid 40's. Now this is at a lower ISO. When I move to a higher ISO, 800 or so, then the increased bit rate numbers go way up to around 60.
I recall reading somewhere that the higher the ISO, the more headroom there is to increase the bit rate. Am I remembering that right? Does this beg the question, under what conditions is the increased BR best used for? I'm mostly looking to use it for studio work where I expect to keep the ISO to 200. Does a higher ISO's lower quality get offset by adding to its BR? And how does this effect green screen work?
Related, is there a visual of the ML LCD readout that diagrams what each element is? I get that the red boxes in the upper right are A: Average BR, and B: Current BR. But I am not sure that the green box to the left or the box to the right is (maybe Q on that one, as it is often -16?). Boy these are hard to read, so small!!!
2. OVERHEATING
I am having issues with overheating. Even just sitting and not filming, the readout went up to: 56c / 131F / 201 raw. I tried moving the LCD away from the body, but no effect. (And neither the LCD or area behind it was warm anyway.)
When I was filming tests for 12 minutes, the temp display went up to 62C and shown in red (at standard 1.0 Bitrate). Though there were no other warnings and the camera did not shut down. I have no idea if this was always a problem or not, as I never knew the temps before ML gave me the readouts just now. So....how concerned should I be? What temperature (in Celsius since that is the only LCD display) should I be worried about?
I have noticed the SD card was very hot after the filming. Could that be the source?
Thank you for your work, your generosity, and any light you can shed on these questions.
Oh, one last item: Minor bug in that when trying to set the FPS over 30 (I think), every click would briefly display a different interface. It looked like Canon's picture style interface.
Best,
J
Quote from: Jstaff on February 12, 2019, 09:39:22 PM
2. OVERHEATING
I am having issues with overheating. Even just sitting and not filming, the readout went up to: 56c / 131F / 201 raw. I tried moving the LCD away from the body, but no effect. (And neither the LCD or area behind it was warm anyway.)
When I was filming tests for 12 minutes, the temp display went up to 62C and shown in red (at standard 1.0 Bitrate). Though there were no other warnings and the camera did not shut down. I have no idea if this was always a problem or not, as I never knew the temps before ML gave me the readouts just now. So....how concerned should I be? What temperature (in Celsius since that is the only LCD display) should I be worried about?
I have noticed the SD card was very hot after the filming. Could that be the source?
In my experience, the battery contributes a lot to the heat. Get yourself a battery grip [$25(US) on Amazon] and the cam will run cooler and you can film longer, too.
Hi Irv,
Thank you for the reply and good thought. However, I actually have a grip with battery holder. So yeah, no effect. Plus, that part of the camera isn't running hot.
1) Test without ML
Turn cam off.
Press SET and turn cam on.
Release SET after QC screen appears.
Take a pic (= pic 1).
Record for 12 minutes and take a pic (= pic 2) again.
Turn cam off. Let cam cool down. 30-60 minutes.
2) Test with ML active
Don't press set and turn cam on.
Take a pic (=pic 3).
Record for 12 minutes and take a pic (= pic 4) again.
Check exif tag "Camera Temperature" for all 4 pics and compare.
Quote from: Jstaff on February 15, 2019, 09:10:40 PM
Hi Irv,
Thank you for the reply and good thought. However, I actually have a grip with battery holder. So yeah, no effect. Plus, that part of the camera isn't running hot.
I've also found that the screen position impacts camera heat. It'll run cooler if you swivel it out away from the camera body.
With recents updates on bleading edge versions flexinfo works ok without problems.
I've fixed some positions and cleaned up some parts.
If there is someone interested in testing it:
DOWNLOAD (https://bitbucket.org/600dplus/magiclantern_eyefi_trick_cleanup/downloads/magiclantern-Nightly.2019Apr15.600D102_Flexinfo.zip) (don't load rebelgui module included, it's here for mistake and not working)
(based on unified branch)
SOURCE CODE (https://bitbucket.org/600dplus/magiclantern_eyefi_trick_cleanup/branch/flexinfo_600D)
PULL REQUEST (https://bitbucket.org/hudson/magic-lantern/pull-requests/957/flexinfo-600d/diff)
EDIT: added screenshot of trapfocus written with another font
Please, to anyone who download and test the test build, post your feedback here or in the pull request.
Give feedback also if it works ok,please. Just a simple "confirmed working ok on my 600D" is enought and really appreciated.
;)
Will test the build tomorow and give my feedback when I can
confirmed working ok on my 600D!
I ran the self test and everything seem to run fine.
What is the maximum resolution for video in RAW mode can be achieved?
Hey all.
First of all thanks for the info on the thread. It's already been helpful. So, I have a Canon T3i and as of yet have not used Magic Lantern. But I'm going to be taking some shots of some fairly complicated circuit boards here at work for our website, and I like the idea of the focus peaking feature on ML. Here's my conundrum, however. Given the (what seems to be quite rare) possibility of bricking my camera if I install this, do those of you who have used ML think it's going to make that much of a difference? We do not upload large files to the web in order to maintain loading speed to maximum, but I'd like to get as much detail into the product pics as possible. I just don't know if ML is going to make that much of a difference. Here's https://www.axcontrol.com/automation/ge-boards/mark-v-ds200/DS200DCFBG1BLC (https://www.axcontrol.com/automation/ge-boards/mark-v-ds200/DS200DCFBG1BLC) an example of one of our typical pages to get a feel for what I'm talking about.
Thanks.
M
With or without ML: You should work on white balance, light/exposure control (good read: Light - Science and Magic (https://books.google.com.pe/books/about/Light_science_Magic.html?id=QzLuYhpQmocC&redir_esc=y). I think 5th edition is the newest one.).
Maybe focus stacking with ML is an option, too.
Risks: What do you want to hear? Nothing I can say will change the risk you are taking.
Quote from: Walter Schulz on March 04, 2020, 08:07:21 PM
Risks: What do you want to hear? Nothing I can say will change the risk you are taking.
After reading through the forum I think I have some idea of the risk, and I'm not overly concerned about the "might happens." More looking for users to give their opinion of whether it would be valuable for my needs. I may install it anyway for my non-work hobby time since we go hiking a lot and I think ML would give me some great options when taking photos in the Nantahala.
Thanks for your feedback.
M
I've used Magic Lantern as long as I've had the T3i. For taking static product pics I don't think it will do much. Maybe the automatic self-timer with liveview or exposure bracketing control will be useful. You can zoom in to focus in live view, which is more precise than peaking.
For video it's a much bigger deal and really transforms what this camera can do for usability (white balance, audio levels, focus box, smooth exposure jumps with autoISO make the camera much more versatile as a video camera).
Hi everyone,
I have a 600d and ML 03 july 2018 but I can't find the Bulb Ramping feature in the Shoot Section. I have Intervalometer then Bulb Timer but not Bulb ramping.
However the help section on the web site explain how to use BR with a 600D. So, I'm confused :-\
Can you help me.
Thanx a lot
Aeron San
If you access ML help via
Top of page -> User Guide
you will get the info this guide is outdated and that is true.
Hey y'all, I'm sorry if this is the wrong place or if there's a topic just like this somewhere on the forum already - I'm a bit confused about the forum structure and the builds.
To get to my question: I'm absolutely new to ML, even though I've been following news about ML for a couple years now. After upgrading bodies I'd like to test ML on my old EOS 600D/T3i but I'm slightly confused with all the builds on the homepage being basically 2 years old. Is there some "go to" snapshot to use / is there a newer &/ more stable build (since that particular one failed a test)?
A failed test does not mean that much. Years ago we had no automated tests and therefore no errors. ;-)
A test may fail and you cannot tell if there is a failure in the code tested or in the emulation. Those automated tests run in a simulated cam (= emulation) only.
Go to experimental build page for newer and enhanced builds. And you won't see test results for those builds! ;-)
Thank you for your reply Walter! :) Sorry for bringing up the automated test result in the first place. I'm not that concerned about those.
I was mainly looking for the most stable/recent (tested) build specifically for the T3i/600D - sorry if I caused confusion. 2018 for all available main builds was throwing me off.
I'll just try the one from 2018 first :-)
Hi folks.
I recently picked up a T3i and put ML on it (build from 2018 July 03). Overall it works fine but I've noticed when the camera reboots (from overheating?), the grid reappears on the HDMI output. I have to restart the camera a time or two to get the grid to go away again.
Anyone have any tips on how to fix this? Are there any later builds available?
Thanks!
Mark
Newer builds: Top of page -> Downloads -> Downloads (drop down menu) -> Experiments -> lua_fix build for 600D.
I'm getting a black bar on the bottom of my liveview using magiclantern-lua_fix.2020Sep13.60D111.zip
(https://i.imgur.com/d9VyELJm.png)
HI,
Sorry for my english but i got some questions to ask.
1. i installed ML 10-12bit vesion and everything going just well. but this day when i try to zoom (zoom with focus ring mode, magic zoom disable, focus peaking disable) it used to go to x5 zoom first but now it is straight to x10 without me pressing *button, how do i go back to it used to be?
2. i tried to use hdr mode but the problem is when i try to focus, the liveview goes dark about a sec or so and then normal again. i know it is something to do with the hdr ISO setting cause when i turned the hdr off or changed both ISO to 3200, i can zoom normally, is there any setting that can bypass the HDR ISO setting when i just try to focus?
Thank you
Hello everyone. I wanted to try the module from this post.https://www.magiclantern.fm/forum/index.php?topic=18515.msg218319#msg218319. But unfortunately it does not work on my 600d. Maybe someone has a working module for this camera. I would be very grateful!
Top of page -> Downloads -> Download nightly builds -> 600D / T3i
Astro.mo doesn't work with latest Lua_fix and derived builds.
Could please help me answering the following questions:
Does SD Card hack works on the 600D?
10 bit recording?
Compressed raw?
1x3 anamorphic?
As far as i know only 10 bit worked years ago, but if SD hack works now, the 600d could be a viable option to choose for MLRAW recording.
Hello @Deadcode
Currently there is no SD overclocking/Lossless compression for DIGIC 4 cameras, like the 600D, also there are no active developers working on these right now.
10-bit is available here for 600D:
https://builds.magiclantern.fm/experiments.html
Under 10/12-bit RAW video.
1x3 mode isn't implemented for 600D yet, no one worked on it, this should fairly easy task BTW.
Hello, Just recently started using ML and an old 600D lying around.
I have trouble getting an HDMi output from my 600d to a capture card. i cant get any signal, just black screen.
but when i connect it to my TV via an HDMI/MHL port. it reads my camera as 4:3 display.
should i get a specific capture card for my 600d ?
I use a 15 Euro HDMI-to-USB stick and an UHD capture card with different cameras. The stick just works (lots of lag), capture card seems to be tricky (sometimes) in my environment but I can get around it. Blackmagic Intensity Pro 4k.
Guys how can i activate higher than 30 fps? Any compromises tolerable. 320*240 acceptable, cuz i'm doing astrophotography ;D Okey,i got that it's not possible on 5x zoom , i want at least one working mode. I'm sitting at 10/12bit right now.
@Amrch
600D can already do 1736x696 5x3 @ 60 FPS (in 720p), patching this mode to make it sample the sensor in 1:1 is possible (1:1 is like x5 mode), but it's not implemented.
After patching 720p mode to 1:1, you will have 1736x696 in 1:1 (square pixels), from that you will be able to lower res down to 320x240 and get 60 FPS.
Quote from: theBilalFakhouri on April 20, 2023, 08:43:13 PM
@Amrch
600D can already do 1736x696 5x3 @ 60 FPS (in 720p), patching this mode to make it sample the sensor in 1:1 is possible (1:1 is like x5 mode), but it's not implemented.
After patching 720p mode to 1:1, you will have 1736x696 in 1:1 (square pixels), from that you will be able to lower res down to 320x240 and get 60 FPS.
Do you know which of canon dslr's do support 60fps in 1:1 5x crop? Could you share this info, please?
Did i get you correct - 60 fps in 1:1 5x crop is not possible at this moment?