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 - shayok

#1
Quote from: ItsMeLenny on June 08, 2014, 11:07:10 AM
You'd have to turn ML overlays off.
Basically you're describing how the camera is without ML.
But I can't work without ML! At the minimum I need focusing zebras.

Actually I found that whatever I'm asking for (including info bars, with histogram/vectorscope switched off) already exists, possibly because of a bug (I'm using version 20Apr2013 - yes I know it's old). If I turn off Global Draw, then start recording, then switch on Global Draw, I get exactly what I'm requesting. Unfortunately, this is clumsy and short-lived - the moment I switch off Live View, I have to go through these steps again.
#2
It would be useful to see the area above and below the 16:9 frame that is actually recorded. For example, for unrehearsed (documentary) shoots, one would be able to see the boom about to enter the frame before it actually does. The 16:9 frame would be marked by a red border.
#4
General Help Q&A / Spot-metering spot way too small?
April 04, 2014, 01:37:41 AM
I was thrilled to find the spot-metering feature in video mode till I realized that the spot is so small that slight movements in the target (say a person's face) causes significant changes in the reading. The nose is 20%, the cheek is 10%! Am I missing something?

It's funny people always want the spot to be as small as possible to get accurate readings, but when you're shooting video on the run, it would actually be helpful to have a bigger spot, say one that would average over the entire face. Of course, then the spot size would need to be configurable.
#6
General Help Q&A / What is Auto Audio?
March 06, 2014, 05:09:43 PM
I guess this is as much an ML as a general Canon question.

AGC in Magic Lantern is documented as "applied in digital domain". Is it correct to say that if the output of the pre-amp is clipped, AGC won't do anything for you?

The "Sound Recording->Auto" in Canon's Menu: is that adjusting the gain of the pre-amp automatically, i.e. working in the analog domain? If so, is there an equivalent "auto" in the ML menu?

This is where I'm coming from with these questions: I'm only interested in my camera's audio for dual-system sync, and as a fallback in case something goes wrong with the separately recorded audio. I won't be in a position to actively monitor or adjust  the camera's audio gain.
#7
Thanks for the suggestion, but I'll live with the Spring bugs, don't need the Fall (or Autumn, depending on where you live) ones.
#8
It seems that unless I'm shooting with the lens cap on (or MAYBE some other completely static subject) I cannot get the LCD to switch off for unattended shooting. I have the following settings:

Prefs::Powersave in LiveView::Enable power saving = STBY+REC
Prefs::Powersave in LiveView::Turn off LCD = after 5 sec
Shoot::Motion Detect = OFF

If Recording is not on, the sensor and display do switch off; however if recording in on, it says "DISPLAY OFF..." every few seconds but then doesn't switch off. If I set "Turn off LCD" to 10 sec, then even the "DISPLAY OFF..." message doesn't come on.

If I set
  Prefs::Powersave in LiveView::Use Shortcut Key = INFO
I get similar behavior in the sense that it works when recording is not on, but during recording hitting INFO causes the LCD to momentarily switch off but then come back on again.

I'm using ML v2.3.NEXT.2013Apr20.5D2212

#9
Ah thanks!
#10
As I said the blinking warning does not show up on the screenshot. Other than doing a video of the LCD, is there any other way of showing you?
#11
Hi,

It seems to me that files that are clearly not overexposed appear to be so with the RAW blinkies/zebras. The RAW histogram seems right though. In Lightroom, the raw file http://shayok.com/tmp/raw-hist/_MG_1799.CR2 requires only .25 stop underexposure in Process 2010 and none at all in Process 2012 to get all the highlights in the middle of the image. I got screenshots in ML, but unfortunately it doesn't capture the blinkies (VRAM0). VRAM1 and VRAM2 show my RAW zebra/hist settings.

http://shayok.com/tmp/raw-hist/VRAM0.BMP
http://shayok.com/tmp/raw-hist/VRAM0.422
http://shayok.com/tmp/raw-hist/VRAM1.BMP
http://shayok.com/tmp/raw-hist/VRAM1.422
http://shayok.com/tmp/raw-hist/VRAM2.BMP
http://shayok.com/tmp/raw-hist/VRAM0.422

I'm using magiclantern-v2.3.NEXT.2013Apr20.60D.550D.600D.50D.500D.5D2.1100D on 5D2.
#12
Ah well...

zebra.c
#ifndef CONFIG_CAN_REDIRECT_DISPLAY_BUFFER_EASILY // old cameras - simple zoom box
                .max = 2,
                .help = "Size of zoom box (small / medium / large).",
#else // new cameras can do fullscreen too :)
                .max = 3,
                .help = "Size of zoom box (small / medium / large / full screen).",

platform/5D.212/internals.c
/** We can redirect the display buffer to some arbitrary address, but only with an ugly hack **/
//~ #define CONFIG_CAN_REDIRECT_DISPLAY_BUFFER_EASILY
#define CONFIG_CAN_REDIRECT_DISPLAY_BUFFER
#13
General Chat / Funding ML Development
May 05, 2013, 04:10:47 AM
Has there been any thought given to actually paying someone to do ML development (coding/testing)? I did a quick search on "hiring programmer" - didn't yield anything. On the one hand I see "our funding needs have been met for now, donate to EFF", on the other there are only volunteers working on the code. But I feel the veteran developers must have given enough thought to the issue, so I'll stop before making a fool of myself.
#14
Feature Requests / Fullscreen magic zoom for 5D2
May 04, 2013, 05:10:09 PM
I see on magiclantern-v2.3.NEXT.2013Apr20.zip that fullscreen magic zoom is available for the 600D but not on 5D2. This, at 1:1 magnification, is incredibly useful and practically does away with the need for focus peaking.

See also http://www.magiclantern.fm/forum/index.php?topic=5185.msg32985#msg32985
#15
I  tried http://nanomad.magiclantern.fm/nightly/archive/2013-04-20-ae7cc6b5f69e magiclantern-v2.3.NEXT.2013Apr20.zip

I tried it both on the 600D and 5D2. I feel the behavior is different enough that there can't really be an apples-to-apples comparison with 2.2 or 2.3. Maybe in time I'll get used to it, who knows?

I was really happy to see that on the 600D there is now a Magic Zoom fullscreen feature which with 1:1 magnification might actually do away with the need for Focus Peak for me. Then I was really bummed out to see that fullscreen is not available on the same version on the 5D2. Is that a bug? Also Magic Zoom (maybe with Large zoom window especially) is often too flickery to be usable on the 5D2.
#16
Thanks a lot, you've been a great help. Just to be clear, you mean this right?
http://nanomad.magiclantern.fm/nightly/archive/2013-04-20-ae7cc6b5f69e magiclantern-v2.3.NEXT.2013Apr20.zip
There are a couple that were built on 4-20.
#17
General Help Q&A / Recommend recent nightly build
May 02, 2013, 09:17:46 PM
Hello,

I want to try a relatively recent nightly build (to see if the focus peaking is better than on v2.3 http://www.magiclantern.fm/forum/index.php?topic=5185.0), but am keen not to have two broken halves of a brand new 5D2 in my hands. Is there a recent one that someone has been using for a week or so without problems that s/he can recommend? If you've been using it on a 600D or 5D2 that would be best. Please specify.

Thanks,
Shayok
#18
I was wondering if the developers had any thoughts on this, or if I should just invest in a clumsy monitor. It would be such a pity - I was so happy focusing with my lowly 600D, now with the 5D2 I have gone backwards!
#19
2.2 vs 2.3 on 600D.



On the 2.3, I would almost claim (between the 52s and 54s mark) that we get two different peaks on the bookcase.
#20
I'm a little scared of the nightly.
#21
If I understand you correctly there was never a 2.2 for 5D2. So we can't do a meaningful comparison on the 5D2. So the only comparison that can be done is on the T3i, which doesn't serve my immediate selfish interest of getting good focus peak on the 5D2. (It might help developers understand the difference in behavior and fix if necessary the 2.3 behavior, which could eventually help me.)
#22
Let me first make a correction: the 5D2 is using v2.3.5D2.212 not 2.2. I don't know that 2.2 is in the picture at all (unless that's the same as 2011Dec22.600D101.alex). Where can I find the firmware corresponding to 2011Dec22.600D101.alex that I can run on 5D2?

#23
How do I choose different algorithms in the same camera? Do you mean d1 vs d2?
#24
Quotelike the display filter peaking and haven't used blinking dots

Sorry I don't quite follow; in focus peaking there are only a few options: d1 vs d2; threshold; color. Where do I choose "display filter" vs "blinking dots"?

#25
I'm having the most difficulty focusing with the 5D2 on fine details not very close to the camera (at least a couple of meters away), but not at infinity either. The books in the bookcase in this example.

5DMk2 with ML version v2.2.5D2.212:

At 22secs  I say "even at infinity we have a little bit of blinking on those books". Actually that is not so much the problem as that the amt of blinking is not that different from when they're in focus.

T3i/600D with ML version 2011Dec22.600D101.alex