Messages

we know: http://www.magiclantern.fm/forum/index.php?topic=14990.25

[/ML/scripts/LIB/config.lua]

My script used to detect shooting mode changes for this bug: https://bitbucket.org/hudson/magic-lantern/issues/2297/shoot-mode-ca-and-hdr-backlight-control

Code Select Expand

--copies the shutter, aperture, and iso of the current mode when switching to M mode
require("config")


--class to keep track of property values using prophandlers
prop_value = {}
prop_value.__index = prop_value


function prop_value.create(...)
    local pv =
    {
        value = 0,
        previous = 0,
        time = dryos.ms_clock,
        props = {...}
    }
    setmetatable(pv,prop_value)
    return pv
end


function prop_value:enable()
    for i,v in ipairs(self.props) do
        function v.handler(prop,value) self:set(value) end
    end
end


function prop_value:disable()
    for i,v in ipairs(self.props) do
        v.handler = nil
    end
end


function prop_value:set(value)
    if camera.mode ~= MODE.M and value ~= 0 then
        self.previous = self.value
        self.value = value
    end
end


function prop_value:get()
    --ignore value if we've been in the current mode for less than 1 sec
    if dryos.ms_clock - self.time < 1000 then
        return self.previous
    else
        return self.value
    end
end


--will be set as the prop handler for property.SHOOTING_MODE, when enabled
function shooting_mode_handler(self,value)
      print("shutter: "..value)
end


modedisplay_menu = menu.new
{
    parent = "Prefs",
    name = "Mode display",
    help = "Switch mode and print",
    choices = {"Off","On"},
    value = "Off"
}


function modedisplay_menu:select(delta)
    if self.value == "Off" then self.value = "On" else self.value = "Off" end
    modedisplay_update(self.value)
end


--start/stop the prop handlers to enable/disable this script's functionality
function modedisplay_update(value)
    if value == "On" then
        property.SHOOTING_MODE.handler = shooting_mode_handler
    else
        property.SHOOTING_MODE.handler = nil
    end
end


config.create_from_menu(modedisplay_menu)
modedisplay_update(modedisplay_menu.value)



It's a modified script from here: https://davidmilligan.github.io/ml-lua/examples/copy2m.lua.html with lots of cruft.
What you should change is SHOOTING_MODE to whatever property you desire: https://davidmilligan.github.io/ml-lua/modules/property.html
Two tips, never use two scripts with the same menu/function names, it will crash LUA & ML, and second you need /ML/scripts/LIB/config.lua present too.

0xdeadbeef is usually just a place holder, it's meaningless (dead beef) and it conforms to the need of hex numbering (0..9a..f). My guess is that this value is not actually known.

[mlv_snd]

Enable mlv_snd module, restart, turn MLV Sound ON.

Wasn't the camera already perfect?


Hopefully this kickstarts ite

Latest nightly works [functions as described in ML wiki] reliably (?) if you use the EF-M STM 22mm lens. Other lenses work too but a shutter bug exists which can lock the camera (least likely to happen if you use a SanDisk 32 GB or smaller card).

Yep, kinda.
Besides the latest nightly Apr 19, there's my July 01 build somewhere.

Do I need to update to latest firmware?

2.0.2? Yes, it fixes (most of) the focus speed, not ML related but needed.

If I get this shutter bug, is there a reliable way to permanently restore the camera? So my friend would never know I had risked the life of his little camera?

Non-ML cards don't have it, hence it won't matter to your friend.

Hi I cannot find this information anywhere.
I just want to know if the EOSM will shoot 1080p at 60fps (or more?) in normal avchd mode?

Nope, page 188: http://gdlp01.c-wss.com/gds/8/0300008788/01/eosm-im-en.pdf

[press W]

   
• W - File dialog to choose the export directory
• C - Export all files in the current directory using the current settings

So you start MLRawViewer in a folder that has many MLVs ( say you open one MLV file directly), press W to select where the converted files will be saved and then you press C and nothing happens?

There are like 4 people that can and do code right now for ML, and you want them to do what? Clean up their code written with passion like it's a corporate thing?


You want official/professional/corporate software, go use the camera manufacturers software, I heard it's great: https://luminous-landscape.com/rantatorial/a-plea-for-dng-again/

You pressed INFO until you got the ML overlay and it shows what?


Make a picture of the display.

@phooser: read this www.magiclantern.fm/forum/index.php?topic=14779.0

@all: DO NOT FEED!

Convert MLVs with MLRawViewer or MLVFS and compare.

You activated in the MODULES tab first, right?

And you set in ON in the SOUND tab after restart too, right?


Can you try with mlvfs too?

Is there a problem with MlRawViewer_1_4_3_win32.zip?

that's here: https://bitbucket.org/baldand/mlrawviewer/downloads

maybe someone should edit the OP and replace the link from 1.3.3 to 1.4.3 ?

Using *nix ( Linux, Mac ) that's: lmgtfy.com/?q=diff


Or GUI tools like meld, Kdiff3, Winmerge, Totalcommander has a compare function, etc

screenshots?

Anyway, some assert logs:

Code Select Expand


at ../../src/raw.c:1690 (raw_lv_request), task shoot_task


Yeah the M get's plenty of those, being a LV only camera.

It WORKED with your settings!!! No bad frames for 6 minutes. Well now i have to find out which setting it is...

Those SETTINGS are text files, just diff them.

Answers here: https://rbrune.github.io/mlraw/

[@dfort]

Fixed by @dfort: https://bitbucket.org/hudson/magic-lantern/issue/2255/mlv_sound-working-only-on-the-first-video#comment-1940140

Genius, you just enabled it and it works! 

I wonder why was this not enabled on the M in the first place? 

And a test build for you M users: https://mega.co.nz/#!4URwyTSQ!rt2PhD_RCTjvVJAB0zGgD61FU28BH5D1PiQr9zwPvuM
I'll just keep it up for a few days to test it properly.

On that note, I find the maximum value of 20 pretty low leading to false triggering, or maybe I miss the point and this is an audio cable intended feature anyway?

[: montage]

Now what??  Should I open a new thread or post in an existing thread?[/size][/font][/size]How do I get help from now on as I am ready to do some very very minor mods to the codes?Also I need to know the procedure to submit my new codes (if any) to the ML team... absolutely no clues...

Start a thread here: http://www.magiclantern.fm/forum/index.php?board=25.0 I guess

@DeafEyeJedi:
montage is missing, says so right there, looking for it like this might help: https://packages.debian.org/search?searchon=contents&keywords=montage
so install imagemagick?

See this too: http://www.eos-m.net/review-power-to-the-m-mains-power-adaptors-for-eos-m/

[/home/<username>/arm-toolchain]

I did not see the youtube clip, but I advise you to use this compiler: https://launchpad.net/gcc-arm-embedded/+milestone/4.8-2014-q3-update -> gcc-arm-none-eabi-4_8-2014q3-20140805-linux.tar.bz2
you unpack it in /home/<username>/arm-toolchain

Makefile.user (to put in the root of magic-lantern)

Code Select Expand

SUPPORTED_MODELS:=EOSM
SUPPORTED_UNIFIED_MODELS:=
ARM_ABI=none-eabi
ARM_PATH=~/arm-toolchain
GCC_VERSION=-4.8.4
ARM_BINPATH=$(ARM_PATH)/bin
CONFIG_TCC          = y
CONFIG_MODULES      = y
CONFIG_PICOC        = y

Replace EOSM with your camera model, see these two lists, leave only your targets:

Code Select Expand

SUPPORTED_MODELS:=50D 60D 550D 600D 500D 5D2 5D3 7D 650D 700D EOSM 1100D 6D
SUPPORTED_UNIFIED_MODELS:=50D 60D 550D 600D 500D 5D2 1100D

in the magic-lantern folder run:

Code Select Expand

make clean && make && make all_modules && cd platform/<yourcamera> && make zip
(yeah yeah it's a bit redundant but works ok and you make sure it's a clean slate before re-compile )

Use your distro packaging tools to find what package provides fuse.h, some thing like libfuse-dev  on Debian.