Messages

[not]

Does in build if you comment out what I've pointed?
The FULL ML does not have or need a Linux binary for cr2hdr ( which that line builds and what make zip DOES NOT package anyway ).


Or maybe I don't understand what you mean by FULL? Autoexec + modules + ( others like fonts/cropmarks ) ? Or?

It could trigger when a USB connection is detected, but it will try to infect the SDcard at most, use it to try to skip the air gap.

On another thought, 40D is what 7 years old or so? What were the chances of it malfunctioning all by itself anyway just of "old age". (Yeah yeah everyone has a friend with a really old camera that still works ok but exceptions...)

[dual_iso]

I've pointed it before, regarding dual_iso, @garry23, can't you do this since you don't need cr2hdr built anyway?

I don't think they access that as USB/MTP/PTP hence the virus should be able already to infect Canon which is less likely anyway.

I guess it's some sort of warning as some modules are not compatible with some cameras, compiling all ML for that camera first will let it sort out if it's usable or not (then it will not build the module)

[make]

(not on Codio, but on real Linux system or in VirtualBox)
I just enter the module/<whatever> folder and issue: make but I did that after building whole ML first for my camera, not sure if it matters.


But in the mean time maybe it's a good idea to clone the iso-research repo and build it there and not just pick up what you want.

- EF-M 18-55mm STM   Expo override does not work, exposure in FRSP does not change at all when changing aperture.
- EF-M 11-22mm STM   Same behaviour, expo override does not work

Yep, confirmed the same behaviour with my own EF-M 18-55mm STM

I had recently a strange encounter with a TV, large screen LG 55"/3D or bigger (forgot to take note of the exact series), and although I looked around the menus for some sort of frame-rate setting, I could not find it.


Anyway, it was a strange encounter because I was seeing the same CSI like shows, but they had (how do I put this in to words?), a realistic feeling, like the news crew filmed the whole show and maybe that won't be a problem but everything looked fake and wrong.

Sounds like expo override may not work with STM lenses. Any other STM lens users can confirm?

Confirmed on my EF-M 22mm 1:2 STM too.
Now that I think of it the other thing shows it exactly as described.

Can you manage to take a picture with the DOF preview button pressed?

Umm, having C.FnIV (6) setting Trash for "DoF preview", a single-press will trigger a quick iris closing up to my set up aperture AND after the iris moves back to max-aperture it will trigger a FRSP too, weird !? Also while *-press or half-shutter press exit the preview, pressing Trash again does not.
Hold-press Trash most of the time will close the iris properly but the screen will go from "Hold on..." to black screen with "Raw error" until you depress Trash and after it will stay as a black screen that waits for *-press or half-press, no FRSP will be taken on hold.

Actually as far as I can see it will always make a FRSP at max aperture no matter what I have selected and whether ExpOverride is used or not.

Hello, I have a Canon EOS M and installed ML.
In RAW mode，it can only take three seconds...
The LED shows "Frame skipped"
My SD card is PNY Elite Performance（90MB/s）.
I don't know why....

see this: https://rbrune.github.io/mlraw/


Also keep an eye out for: https://bitbucket.org/hudson/magic-lantern/issue/2255/mlv_sound-working-only-on-the-first-video


I guess you are having this issue too: https://bitbucket.org/hudson/magic-lantern/issue/2254/star-bbaf-during-raw-recording-crashes-ml

Whats your MLV processor? It should load the M00..Mxx by it self anyway.


Try this, load the MLV and check the frame number.
Move all the files EXCEPT the MLV (to some other folder) and THEN open the MLV and see what frame number you've got.


If it's the same then your program does something wrong. Try MLVFS ot MLRAWVIEWER.

Cropmarks help?

[diff]

@garry23: Can you diff and so I can patch and test ? See how to: http://jungels.net/articles/diff-patch-ten-minutes.html

Trying to record a bit with the intervalometer, to answer @JoshuOne, got the timer running, 10s, FRSP, MLV, the screen was always off which is nice, but after 9 frames or so:

Code Select Expand

ML ASSERT:
lv
at ../../src/zebra.c:4202 (idle_display_dim), task cls_task
lv:0 mode:3


Figured it ( by setting up ML multiple times ) how it was trigger ( BUT it's obvious now since it's written RIGHT THERE in the assert daamit ) and reported it: https://bitbucket.org/hudson/magic-lantern/issue/2262/dim-display-triggers-assert-in-zebras-when

Just to thanks the whole dev team to provide a tool like ML. I'm an open source enthusiast (using and working with GNU/Linux & Unix systems for many years) and I just discovered the project, replace my old Nikon D3100 with a 60D. Fabulous.

If you plan to use Darktable and RAW MLV video or Full-res silent pics/MLV see this tip too: http://www.magiclantern.fm/forum/index.php?topic=9560.msg142928#msg142928

that means no: http://www.magiclantern.fm/forum/index.php?board=24.0

I keep seeing the camera temperature on other cameras ML menu, does this need more data for M to be usable or what?

It's the "Reserve card space" feature, it ML -> Movie-> RAW menu

The latest nightly is the latest stable, always.

Just a protection mechanism.

v2.3.600D.102

That's stable.


Get nightly: http://builds.magiclantern.fm/#/ and do as @Walter Schulz said.

Update first and retry.


Those 608bytes files mean that the recording failed, somewhere, I don't think there is anything to recover.

First of all why would one use 8 months old builds anyway?

Second, I got this error too on my M, see this: https://bitbucket.org/hudson/magic-lantern/issue/2255/mlv_sound-working-only-on-the-first-video

https://nikonhacker.com/wiki/Supported_Models

I was testing FRSP so sometimes it ended up in a black screen hence ETTR/zebras could not get its needed data, makes sense.
For now I will set Zebras->RAW Zebras to OFF so that maybe that won't trigger again on intervalometer use, when the camera does not get a chance to display the image at all anyway.

Another thing, are asserts a sign of things being unstable (like the error that I got later) or just plain warnings that can be ignored?