Author Topic: Nightly Builds - try the very latest stuff here (Read 1182875 times)

Wynand · « **Reply #900 on:** September 29, 2014, 02:03:33 PM »

Is it possible to have the EOS M display ON while using the HDMI cable for an external monitor? I like to use an external monitor but the touch screen display of the EOS M then gets disabled and no "easy" touch screen changes is then possible. Regards and thanks for all the great work done!

avipami · « **Reply #901 on:** September 29, 2014, 10:52:53 PM »

Hello!!!
I Love the ML for the 5d mIII and I have a question !

Is it possible that someone can incorporate a shutter lag setting ?
I want the shutter to lag but not the flash release
In other words I want the flash to go off when pressing the button, before the shutter by some milli seconds.

Would help a lot !

Walter Schulz · « **Reply #902 on:** September 29, 2014, 10:57:53 PM »

By "go off" you mean strobe firing?
Why not use highspeed sync? When using this strobe will begin to fire before shutter opens and strobe will be retriggered until shutter closes.

avipami · « **Reply #903 on:** September 29, 2014, 11:12:20 PM »

Im doing it with studio strobes and the 2nd curtain closes before the strobe gets any light out of it. If I put a delay to the triggers it only gets worse so I figured that the strobes needs to get off earlier than the shutter starts to move. By then the whole frame would get filled with awesome light

I have tried all different settings and cables and this is the only way i guess.

Walter Schulz · « **Reply #904 on:** September 29, 2014, 11:16:20 PM »

Which lighting problem you're trying to solve? Do you need exposure time 1/160 s or below?

avipami · « **Reply #905 on:** September 29, 2014, 11:19:08 PM »

No , like im trying to explain. I would like a shutter lag and the flash firing before. Im shooting at hypersync but the second curtain manages to close before the flash starts burning. Lower part of my image is very dark.

dmilligan · « **Reply #906 on:** September 29, 2014, 11:41:51 PM »

Your concept of what the problem is is all wrong. Flashes fire almost instantaneously, like 1/20000s. The problem is the way your shutter mechanism works. It is a "focal plane shutter" meaning there are two shutter mechanisms, a top one and a bottom one. They are both up and then the top one starts moving down exposing the sensor to light then the top one starts down covering it up. The fastest that these shutters can move from top to bottom is known as the x-sync speed and is around 1/200 of a second. So to get shorter exposure, the top one starts moving down before the bottom gets to the bottom. This is why the bottom of your frame is dark. All you need to do is use a slower shutter speed or the "high speed sync" mode, which fires the flash multiple times while the shutters are moving so that the whole frame is illuminated.

Walter Schulz · « **Reply #907 on:** September 29, 2014, 11:57:13 PM »

You got one thing wrong: Lower part of a picture is located at the upper part of the sensor.

The time needed for the first curtain "falling" down is constant. Strobe is triggered after (!) first curtain hits ground. If exposure time is shorter than x-sync the second curtain is on it's way down. Shadowing is caused by second curtain.

HSS will start triggering before first curtain opens and retriggers until 2nd curtain closes. And most studio strobes won't do HSS.

avipami · « **Reply #908 on:** September 30, 2014, 12:04:33 AM »

Well. I know all what you have said since 2 years ago. If you have seen the latest trends where a studio flash is used with hyper sync triggers you will know. And a flash does not burn at that speed you are talking about. Then you would have a 10000 dollar single flash. Mine burnes at a 1200/second. And it is the second curtain cutting the strobelight. And the question was not about this at all. It was if someone knows how to do or if it is possible to delay the picture taking part and make the flash output to fire before it. And possibly make it set-able in magic lantern

avipami · « **Reply #909 on:** September 30, 2014, 12:06:16 AM »

What walter said

Walter Schulz · « **Reply #910 on:** September 30, 2014, 12:21:34 AM »

Quote from: dmilligan on September 29, 2014, 11:41:51 PM

Flashes fire almost instantaneously, like 1/20000s.

Avipami, I think he is not talking about burn time (t.5/t.1) but about delay between strobe triggered and flash starting to burn.
Got this one wrong after first reading, too.

avipami · « **Reply #911 on:** September 30, 2014, 12:41:55 AM »

probably right there
Sorry ^_^

legreve · « **Reply #912 on:** October 04, 2014, 08:26:12 PM »

Is there a way to get hold of august 2013 5D3 builds?

chross · « **Reply #913 on:** October 09, 2014, 02:14:30 AM »

Hi,
is there a way to get a nightly that includes both, 5DmkII and 50D? I'm asking since am used to swap cards between my Cameras all the time. It seems as if the nightly I installed to get DualISO for the 5DmkII doesn't work on my 50D. Installing the 2.3 stable works fine.

Any hints?

Cheers,
chross

Stedda · « **Reply #914 on:** October 09, 2014, 11:25:16 AM »

Quote

is there a way to get a nightly that includes both

There is no unified build after 2.3 so the short answer is no...

fotogemeinschaft_de · « **Reply #915 on:** October 10, 2014, 08:16:33 AM »

The nightly Build for Canon 5D MK 3 (firmware 123) wasn't updated for 4 Weeks; the older firmware is updated daily? Any reasons for this?

Walter Schulz · « **Reply #916 on:** October 10, 2014, 08:27:28 AM »

http://www.magiclantern.fm/forum/index.php?topic=11017.msg130897#msg130897

dmilligan · « **Reply #917 on:** October 10, 2014, 03:39:43 PM »

Quote from: fotogemeinschaft_de on October 10, 2014, 08:16:33 AM

the older firmware is updated daily?

Nope. Look at the logs, it is far from "daily". There haven't been any substantial changes to the main ML branch for several months now. The handful of minor changes to the main branch that may have triggered a new build on 5D3-1.1.3, didn't get merged over to the 5D3-1.2.3 branch probably because either: they were camera specific to some other camera, or they were very insignificant.

JABA2 · « **Reply #918 on:** October 18, 2014, 10:35:23 PM »

Hey everyone. I've got one question.
Since it seems like we're not gonna see another stable build, I'm using nightlies for my 600D. They are great, but there's one thing bothering me: there's this 'developer screenshot' popping up everytime I start the camera and enter ML menu. Any idea how to remove this?

dmilligan · « **Reply #919 on:** October 18, 2014, 11:03:35 PM »

You can #define CONFIG_RELEASE_BUILD in menu.c. If you don't know what that means, then the answer is no.

JABA2 · « **Reply #920 on:** October 19, 2014, 08:46:27 PM »

I'm guessing you mean I should compile the source code myself. Well, too bad, 'cause I'm not bright enough for figuring that out.
'Thanks' for the advice, though.

rainless · « **Reply #921 on:** October 21, 2014, 09:25:15 AM »

Read some books, take some Omega 3 tablets, eat one pear a day... It all helps!

a1ex · « **Reply #922 on:** October 29, 2014, 10:41:27 AM »

I've removed the old 2.3 downloads and added install instructions on the nightly builds page. Feel free to check the stuff, suggest improvements, and update the wiki.

I've updated these pages:

http://magiclantern.fm/downloads.html
http://builds.magiclantern.fm

My spare time has dropped to almost zero (usually I can barely find time to read the forum), so please don't expect major progress from me in the near future. I expect things to clear up around January or February; until then I'm stuck with personal stuff unrelated to ML (and unrelated to Apertus).

swinxx · « **Reply #923 on:** October 29, 2014, 11:48:56 AM »

dear a1ex,

could you please update the 1.2.3 canon 5d mk3 build before you make a break..
it would be great cause then all builds would be at the same dev level..

thx.

a1ex · « **Reply #924 on:** October 29, 2014, 11:50:32 AM »

I won't take a long break, I will only make minor steps whenever I find some time (that is, things that only take a few minutes during a short break).

I've already answered the question about 1.2.3 a while ago.

News:

Author Topic: Nightly Builds - try the very latest stuff here (Read 1182875 times)