Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - themichael

#1
Thank you a1ex
#2
Forgive the noobness of the question:

Where in the code can I find the white balancing and spotmeter sections? Or some "terms" to search with. Looked but couldn't find.  I'm an idiot. Searching in the right folder helps.

I wanted to look at the Auto adjust Kelvin + G/M maths for another project to get K and G/M from YUV or RGB but it sounds like that is using Canon routines.

My C was learned at uni on a PDP-11 without the + or ++ and definitely without the #  ;) Going is slow.
#3
Ilia3101 - It is a non-scientific reason and a good way to measure color for my purpose.   XYZ/RGB or xyY is getting too deep. I need to stack filters to get close to a tungsten/halogen color under various lighting conditions. 

Danne - Tried that but I may have not done it right, nothing happened and the WB didn't change. Going to try that again.

On a podcast they were talking about positive paper prints like Polaroids without the negative part. It involved R4 color paper used in a reversal process at room temp.  I think they used a contrast 00 and a contrast 1/2 filters (BW printing filters) and got good results under later day daylight.

Thanks for the fast response.  I may even shoot more digital now; great stuff in the newer ML.
#4
It has been quite some time since visiting the forums and trying out new builds. My Canon AE-1P doesn't run Magic Lantern.  ;D

About 5 years ago I had figured out how to use LV and a white balance setting to get a Kelvin and G/M readout near the spot meter square. I know this was an off schedule use of the firmware; but now I have need of it and forgotten how I did it. I even have the old version on a card but couldn't figure it out. My wife would kill me if I drop $5K on a colorimeter!

Help please and thanks.
#5
Scripting Corner / Re: LUA Scripting (lua.mo)
April 11, 2015, 09:36:42 PM
Now the test script is there and works. Trying my own.

Two questions -
A. (off topic) Can I save the scripts over USB so I don't risk damaging the CF pins on the camera?

2. Something is wrong with this script below, it doesn't show up. Is the mistake is in the menu.new part? Or am I completely off the rails?
mykeys = menu.new
{
    parent = "LUA",
    name = "Key Test Script",
    help = "Key code script.",
    submenu =
    {
            name = "Test",
            help = "Run my script.",
            icon_type = 5,
            update = "",
    },
    update = "key?",
}

mykeys.submenu["Test"].select = function()
    console.show()
    print("Waiting 10 sec for key")
    key.wait(,10000)
    if (key.last <> 0) then print("key "..key.last) else print("no key")
    print("donesies!!")
end
#6
Scripting Corner / Re: LUA Scripting (lua.mo)
April 11, 2015, 03:35:11 AM
I still cannot find any Lua scripts.

Removed all the *.lua scripts in the directory.
Used the menu script in LuaAPI.rst saved as menu.lua
Cannot see it under any menu (no lua tab either) but can see it with file manager.

Compiled 15 hours ago, last change on bitbucket was 23 hours ago.
#7
Scripting Corner / Re: LUA Scripting (lua.mo)
April 10, 2015, 05:35:02 AM
I went to try out my cloud compiled version and I don't have a Lua tab like Wolf does (post #6 above).

screen by memoirs-in-digital, on Flickr
#8
Here is one for the 7D.

I used hg clone -b lua https://bitbucket.org/hudson/magic-lantern
instead of -r that surami used. Also added lua to ML_MODULES_DYNAMIC.

Added the dual_iso.mo from the latest nightly, the  "forced_delay.lua" and "stop_thief.lua" from the original post.

Off to learn lua.

// Outdated build removed.  Audionut.
#9
Scripting Corner / Re: LUA Scripting (lua.mo)
April 07, 2015, 03:00:33 AM
Would it be possible to play back a short audio file? 

Something useless like -

script_name = "Shutter Tones";
script_help = "Avoid talking to models";
events =
{
post_shoot = function() play("shutrton.wav") return true end
}


Or to say a wake up message, show a screen looking for a certain keypress sequence before playing "help help I am being camera napped!"

Of course it could play more useful stuff like focus distance (if reported) when focused or exposure settings, counting down long exposures, or the "number of number" when using auto bracketing.
#10
General Chat / ML RAW video in Canon ad
August 09, 2014, 06:47:27 PM
Some Magic Lantern RAW footage pop-up in an advertisement made by Canon dubbed "Bring It" at about 0:15 and 0:18 seconds.



The Magic Lantern RAW clips were excerpted from  Video Skiing Sample by Justin Majeczky (at about 15 seconds in) and A Flood of Emotion by Kim Jong Seong at Pastel Glyph (at about 18 seconds in).
#11
Feature Requests / Re: Film Camera Magazine Sound
March 03, 2014, 12:06:39 AM
There was a joke among photographers 5 years ago or so based on the massive popularity of ring tones for cell phone.
"Download your shutter tone paks from your favorite photographer."
"Model encouragement shutter tone pak"
#12
Archived porting threads / Dead battery
September 26, 2013, 08:58:54 PM
Sorry if this is the wrong thread, pls move if it is.

I am running
V2.3.NEXT.2013Sep02.7D203
Mercurial changeset 63c523d7a208 (unified) tip
Built on 2013-09-02 01:42:29 UTC

and when the camera is physically turned off the battery goes dead after a few days.  It used to last at least a month in sleep mode while I used film cameras. If I let the camera go to sleep (switch on, camera off) the battery also dies in a few days. The card door has not been opened. Does not happen with a plain card or no card in the slot.
#13
http://www.homebrewusb.com/DIY/DIY%20%20Portable%20Wireless%20USB.html

The problem is Cables Unlimited is dead. But the basic idea is still the same.
#14
Tried this on two different computers, XP-32 laptop and Win 7-64 desktop. Both have the same results, connection lost no ML.

Grasping at straws - could it be the date of manufacture? Found this list and mine was made in Sept 2011 -

Date       First 2 digits of serial #
Sep 09   01
Oct 09   02
Nov 09   03
Dec 09   04
Jan 10   05
Feb 10   06
Mar 10   07
Apr 10   08
May 10   09
Jun 10   10
Jul 10   11
Aug 10   12
Sep 10   13
Oct 10   14
Nov 10   15
Dec 10   16
Jan 11   17
Feb 11   18
Mar 11   19
Apr 11   20
May 11   21
Jun 11   22
Jul 11   23
Aug 11   24
Sep 11   25
Oct 11   26
Nov 11   27
Dec 11   28
Jan 12   29
etc   etc
#15
Quote from: pit3k on August 02, 2013, 08:55:53 PM
Make the firmware again using cmd and carefully check what are you typing into console. It should create just one file: firmware.fir. Do the rest of steps as the tutorial says.

Sorry, I wasn't clearer. The three ROM bin files are after the update in the camera.

EOScard 1.36 crashed on two computers (Win7 and XP) even if nothing is clicked.

Will try once more with all new downloads.

**EDIT: Still no joy. The autoexec.bin goes in the root corrct? I am using a 16MB 133x card. Somebody have a checksum for the generated firmware file?
#16
Having problems getting ML to boot on my 7D. Followed britom's instructions to set the bootflag. ended up with the 3 ROM bin files so I assume it worked. Manually put the autoexec and ML folders on the root of my CF card with the DCIM and MISC folders. When I turn on the camera and hit the delete key nothing happens.
#17
I've followed Pelican's post here for Windows (http://www.magiclantern.fm/forum/index.php?topic=2899.msg14021#msg14021)

I get the following no matter which camera I choose, recipe failure. A forum search didn't yield any solutions.

Michael@Desktop2 ~/magic-lantern
$ make 50D V=1
make -C /home/Michael/magic-lantern/platform/50D.109
make[1]: Entering directory `/home/Michael/magic-lantern/platform/50D.109'
../../../arm-toolchain462/bin/arm-none-eabi-gcc-4.6.2.exe -E -Wp,-MMD,./magiclantern.lds  -Wp,-MT,magiclantern.lds  -nostdlib  -fomit-frame-pointer  -fno-strict-aliasing  -DCONFIG_MAGICLANTERN=1  -DCONFIG_50D=1  -DRESTARTSTART=0x0004b000  -DROMBASEADDR=0xFF810000  -DVERSION=\"v2.3.NEXT.2013May08.50D109\"  -DCONFIG_DEBUGMSG=0  -Os  -Wall  -W  -Wno-unused-parameter  -Wno-implicit-function-declaration  -Wno-unused-function  -Wno-missing-field-initializers  -Wno-format  -Wdouble-promotion  -ffast-math  -fno-trapping-math  -fsingle-precision-constant  -fshort-double  -std=gnu99  -D__ARM__  -I.  -I../../src  -I../../picoc  -mthumb-interwork  -DCONFIG_PICOC -DCONFIG_CONSOLE ../../src/magiclantern.lds.S | grep -v ^# > magiclantern.lds
../../../arm-toolchain462/bin/arm-none-eabi-gcc-4.6.2.exe -Wp,-MMD,./entry.d  -Wp,-MT,entry.o  -nostdlib  -fomit-frame-pointer  -fno-strict-aliasing  -DCONFIG_MAGICLANTERN=1  -DCONFIG_50D=1  -DRESTARTSTART=0x0004b000  -DROMBASEADDR=0xFF810000  -DVERSION=\"v2.3.NEXT.2013May08.50D109\"  -DCONFIG_DEBUGMSG=0  -c -o entry.o ../../src/entry.S
../../Makefile.inc:746: recipe for target `entry.o' failed
make[1]: *** [entry.o] Error 1
make[1]: Leaving directory `/home/Michael/magic-lantern/platform/50D.109'
Makefile:44: recipe for target `50D' failed
make: *** [50D] Error 2

#18
Let me first add my thanks for ML on the 7D. Love in HDR and the in camera exposure fusion. Going to do more exploring over the next couple of days.

Now for some requests, Can you add an in camera multiple exposure feature similar to Nikon's? Can you enable second curtain sync without having an EX II series flash attached (not holding my breathe on this one)?

And lastly, a bug. I was playing with the focus stack, following the steps on the docs page. I went a bit to far on adjusting the focus with the joystick (20 steps, 10 pics) and the camera buttons stopped responding. The off switch and CF door didn't turn the camera off. Pulling the battery worked. Tried the same steps and got the same result. Tried one more time the next day and just received a focus error message and the camera stopped responding to button pushes. The display/liveview continues to update like normal. I am using the new 40mm pancake.