SztupY
2011.04.21. 17:14 keltez�ssel, arm.indy �rta:
Updated with magiclantern.fir from Sztupy's zip; ML started, but did
not set the boot flag. No dumps or logs found on the card. Going to to
write a minimal installer...
> --
> http://magiclantern.wikia.com/
>
> To post to this group, send email to ml-d...@googlegroups.com
> To unsubscribe from this group, send email to ml-devel+u...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
Just installed ML on 60D/1.0.9 with these steps:
1) Downgrade to 1.0.8,
http://web.canon.jp/imaging/eosd/firm-e/eos60d/download.html
2) Use 2nd magiclantern.fir from Indy:
http://groups.google.com/group/ml-devel/browse_thread/thread/f4b54ae5fdbc385
3) Made card bootable and tested autoexec.bin for 1.0.8 (just saw the
startup message and then turned the camera off).
4) Format card and upgrade back to 1.0.9,
http://www.usa.canon.com/cusa/consumer/products/cameras/slr_cameras/eos_60d#DriversAndSoftware
5) Made card bootable and ran latest autoexec.bin from Sztupy:
http://sztupy.hu/magiclantern/109.html
New installer coming next week; until then, you can use this procedure
at your own risk.
Certain functions can be dangerous to try, as they set properties in a
way specific to 550D. Properties are stored in NVRAM and incorrect
values can make the camera not to boot (I almost did it on 550D...
i.e. got ERR70 at every startup, even with original firmware or
without card).
I've already experienced many crashes and had to take battery out.
Don't forget: If it breaks, you get to keep both pieces!
If I understand well, you only control focus with 1, 2, 3, 0x8001,
0x8002 and 0x8003, right? If this is the case, you can simply change
PROP_LV_LENS_DRIVE_REMOTE with those values. See my changeset here:
https://bitbucket.org/hudson/magic-lantern/changeset/a462975938f5
It seems we were working at the same issue simultaneously. If I understand well, you only control focus with 1, 2, 3, 0x8001, 0x8002 and 0x8003, right? If this is the case, you can simply change PROP_LV_LENS_DRIVE_REMOTE with those values. See my changeset here: https://bitbucket.org/hudson/magic-lantern/changeset/a462975938f5 On Thu, Apr 28, 2011 at 11:10 PM, SztupY <ma...@sztupy.hu> wrote: > Alpha5 build from me: > http://sztupy.hu/magiclantern/109_a5_76e269f6413d/magiclantern-2011Apr28.60d.fw109.alpha5.sztupy.zip > > Changes: > - Rack focus/Movie AF mostly working (but it's functionality might > depend on the lens used, I only tried with the EF50/1.8). I wrote > about how it works here: http://magiclantern.wikia.com/wiki/Focus/60D > - Fixed some of the constants based on the 550D dump > > SztupY > > -- > http://magiclantern.wikia.com/ > > To post to this group, send email to ml-d...@googlegroups.com > To unsubscribe from this group, send email to ml-devel+u...@googlegroups.com > For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en -- http://magiclantern.wikia.com/ To post to this group, send email to ml-d...@googlegroups.com To unsubscribe from this group, send email to ml-devel+u...@googlegroups.com For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
Here's my latest autoexec.bin... let's call it alpha6. It has
everything from alpha5, plus:
- better overall stability (at least I can't crash it any more by
pressing record)
- CFN's work (including MLU and HTP)
- bitrate (QScale, emulated CBR) and indicators near the red dot work
- trap focus works, intervalometer worked for me too
- fast zoom in play mode
And the latest stuff from 550D:
- shortcut key for movie mode (press ISO and then LV); this is because
MovieModeRemap was not handy, as CA is farther from P/Tv/Av/M and
there's no A-DEP.
- auto ExpSim (disable during zoom in, enable otherwise)
- RGB zebras
If you can crash the camera, please tell me how to reproduce.
I have found an issue with the Apr26 build (and I assume current one, but I haven't tested that yet).
In movie mode, if you have the magiczoom enabled "always" and take a still photo with a full shutter press. The magiczoom goes away, and you have to mess with the DISP button a few times to make it come back again.
I was having similar issues with an earlier build using the kit lens, but only displaying the zoom during focusing.
After taking a still the box would no longer show up during focusing.
Regards, Morgan.
> For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en<autoexec.bin>
Also, Alpha7 contains new false color palettes similar to SmallHD (not
yet announced on 550D, but code is committed).
Debug - > "Don't click me!" ? :)
If you click it, the camera will behave like drunk :)
* Audio monitoring works!
- not fully tested, as I don't have the headphones right now; only
the USB cable
- minor issue: if you unplug the cable in LiveView, press MENU
twice to restore the display
- USB works, not sure about HDMI
* Fixed bracketing and bulb timer.
* This zip contains the small cropmarks from Sztupy (they seem to work better).
Manuals are not 100% accurate, so I didn't include them in the zip.
Arm.Indy has prepared a minimal installer for 60D/1.0.9, based on this
source code:
https://bitbucket.org/a1ex/magic-lantern/changeset/93135f58ed93
We need a brave tester with a vanilla 60D to check if it sets the bootflag.
I've ran this magiclantern.fir on my camera, and it worked as
expected. Since my bootflag was already set, it did nothing special
(but I did get the dump and the log file).
4: 13.239 [MAGIC] Magic Lantern 2011Apr30.60d.fw109.install.user ()
5: 13.259 [MAGIC] Built on 2011-04-30 08:01:13 by user@ubuntu1004desktop
...
1449: 2009.518 [MAGIC] Calling init_func bootflags.c (60f28)
This installer only sets the version string and calls initial_install.
No user tasks are started, no property handlers, no task override, no
change of camera settings, so the risk is minimal... in theory.
It may be best to run the fir from BULB mode, because otherwise the EV
indicator will overwrite ML installer display (just a cosmetic issue).
Contains latest stuff and fixes from 550D:
http://groups.google.com/group/ml-devel/browse_thread/thread/850ec268bc883ceb/07af12c3754890d7?show_docid=07af12c3754890d7
Most important change: audio monitoring works without any glitches.
Menu has a glitch outside LiveView: you have to press Q or
half-shutter after you close it. This is an workaround; without it,
display would freeze.
My camera seems dead, not sure what happened. Battery went low, I've
charged it, and now it doesn't boot any more, and no lights are coming
up. Last time I was running prop_spy with alpha9.
is your camera now working? I hope so, btw is any one experiencing any T2i overheating issues while using Canon's EOS utility live view. It has happened twice and once I wasn't even recording yet. The camera was on for about 30 minutes the overheating sensor came on. also if I trigger recording from the EOS utility the recording usually stops after a few seconds, whereas if I trigger recording from the camera it records for longer but still doesn't go longer than a 1 to 3 minutes before it stops. I have to disconnect the usb cable to record for longer. I am using a transcend class 10 16gb SD. I can't recall experiencing this issue with earlier ML builds. I may go back to an earlier build on one of my three SD cards to see which build was stable with EOS utility. Which I unfortunately use as my poor-man's field monitor on my unibody MBP 2.5ghz. Any feedback or advice is greatly appreciated!
Thanks
Adrian
What's new:
- Fixed startup bug in movie mode (it was a redraw issued too early)
- Fixed issues 468/1,4,5,7,9;
- Seems to be stable (at least I couldn't crash it in the past few
hours.. with cropmarks off).
- FIR installer for 1.0.9 works.
- All the new stuff from 550D, see
http://groups.google.com/group/ml-devel/browse_thread/thread/850ec268bc883ceb/869771091cbabb4f?show_docid=869771091cbabb4f
. LiveView loop was rewritten first on 60D to improve stability.
- Press Unlock in Play mode to show zebras & co.
Known problems:
- Cropmarks still give ERR70 (disable them).
- Not ready for average users => no manuals included.
SztupY
> Any brave testers for Alpha 10?
>
> What's new:
>
> - Fixed startup bug in movie mode (it was a redraw issued too early)
>
> - Fixed issues 468/1,4,5,7,9;
>
> - Seems to be stable (at least I couldn't crash it in the past few
> hours.. with cropmarks off).
>
> - FIR installer for 1.0.9 works.
>
> - All the new stuff from 550D, see
> http://groups.google.com/group/ml-devel/browse_thread/thread/850ec268bc883ceb/869771091cbabb4f?show_docid=869771091cbabb4f
> . LiveView loop was rewritten first on 60D to improve stability.
>
> - Press Unlock in Play mode to show zebras& co.
Also, finding other segments of memory which can be used (like ExMem)
could help.
The problem is random; sometimes I can toggle through all (full-sized)
cropmarks without a glitch, other times I get ERR70 when toggling disp
profiles (and the new profile has a cropmark configured).
I'll apply your fix in next build.
- Almost everything from 550D branch, see
http://groups.google.com/group/ml-devel/browse_thread/thread/850ec268bc883ceb/84f39efd77501fd2?show_docid=84f39efd77501fd2
- Follow focus / rack focus are much smoother, but sometims stop
working (it seems to be when focus ring touches its limits)
- Outside LiveView, ML menu rides on the back of Canon menu (which
avoids flickering and lets you use the wheels)
- Hopefully fixed 476/1,2,3,4,5,7,8,9,10,12,13*,14.
- I've shot over 1000 pictures with trap focus (both LV and non-LV)
and magic zoom, without a single crash. PM if you want to see some
pics.
* = removed the feature which caused that bug.
- RLE cropmarks from Sztupy (5k of RAM compared to over 300k with
classic cropmarks!)
- All new features and fixes from 550D branch, see
http://groups.google.com/group/ml-devel/browse_thread/thread/da15b5d1e0a337ac/e63c1ab5b5e3ca06?show_docid=e63c1ab5b5e3ca06
(especially my posts starting from May 12). It would be nice if
someone could compile a changelog :)
Split focusing screen works much smoother than on 550D, because 60D
refreshes focus data at a much higher rate :)
Flash key still doesn't work in movie mode, so there's no false color
shortcut for now. But DISP profiles are easier to switch (with the
Metering button).
False color seems to works from time to time by pressing the metering button the top. This may be the route to go on the 60d
sent from my android phone
On May 25, 2011 8:21 PM, "daniel thissen" <thisse...@gmail.com> wrote:
Hi Alex, thanks for your work !!!!I know you have a lot of request, but can you try to use another button for false color
shortcut?False color is my favorite function in ML.Thanks again.
Daniel from Perú
2011/5/25 Alex <broscu...@gmail.com>
>
> Alpha 12:
>
> - RLE cropmarks from Sztupy (5k of RAM...
One question: how did you create 4 profiles? When clicking the metering button, I can only switch between profiles 0 and 1. Am I doing something wrong?
--
:) right, even on 550D it's much more handy.
Remapping buttons:
Many buttons do not send events in certain modes, so ML can't intercept them.
> - HDR bracketing: Why on earth would ml only use the 2sec timer?
Should work better with audio trigger (I don't have the camera right
now to test).
> high speed serial pictures
Try the "take pics like crazy" mode; that will give the max speed
possible from ML.
> - Menu navigation: It would be nice if a way would be found to reverse
> cycle through the values, it is annoying to have to press SET 99 times
> to get from 3 to 2 in stack focus...
A menu with submenus will solve this (see Fernando's proposal,
http://magiclantern.wikia.com/wiki/GUIdelines )
> it would be great to get custom iso values on the 60D, too...
The 60D refuses them.
> and of course fixing magic.disable_bootdiskf would be good for one's ease of mind.
http://www.cinema5d.com/viewtopic.php?f=39&t=29632&p=189030#p189002 :)
> - Another question: My camera is getting warmer and is using noticable
> more battery charge with ml. Are there any hints which operations are
> most cpu intensive (and thus should only be used when relly needed)?
Almost all items from LiveV menu are CPU-intensive. I believe the most
power hungry is focus peaking. There are some power saving features
for LiveView, and more will be coming soon.