Messages

You may want to look into the rules about this.
If the goal is missed the backers will get their money back. Period.
What the people at Apertus will do if the goal is going to be missed is their part. They may want to fill the gap or not.

Sorry, of course you're right. Forgot 5D3 1.2.3 has a very different schedule compared to the rest of the bunch. Sticks out here:
https://builds.magiclantern.fm/jenkins/

The card slot of your computer (if any) is a cardreader, too. An internal one.

Do the math, canon eos m! We're not any nearer because time is running, too. Still far away from comfort zone. At 4 percent/d it will be an "interesting" finish because of slower weekend. And 350+ 4/3 perk is just ignored. Most attraktive perk now is 350+ Super35 but only 39 left = 13650. Will take a lot of people to throw in smaller amounts to fill the gap. Or lesser with a liberal hand not going for perks.

No, not comfortable at all!

Thanks for the effort! And marketing isn't my strong side, either!

Let's hope the americas are waking up and their monthly salary transfer will find it's way. We'll see how it works later this evening, I suppose.

Spnsir came up with numbers.
Would it be of any use to do some tests with a newer 1.2.3 build? If he wants and has time, of course.

Have no 5D3 at hand, sorry.

Thanks!
What about your (and the other devs) contacts to "the outer world" as in photo/video related site owners/contributors? Just drop them a line about what's going on and why. They might be happy for some content in those halcyon days after Photokina.
Spread the word! ;-)

He said he found no bugs in this 1.1.3 build (10.Aug.2014). Speed is his main concern, I think. And I would not expect anyone claiming to use an rather old build to say something about bugs in a version he/she is not using.
Come on, a1ex ...

Have you been able to reproduce anything about existing/nonexisting speed differences between 1.1.3 and 1.2.3?

Warranty isn't an issue wether or not ML is installed (= Cam's bootflag set). There were several cams in Canon's service where owners haven't done anything to hide the fact ML was/is on the cam. Never heard about any complaints or warranties going void. If you will search you will find some reading. ML doesn't void warranty. Fact.
There is one exception: If - and only if - the specific fault/error/damage can be proven (or within reason linked) to be caused by ML you'll be on your own.

As I wrote above: Those settings which might remain in NVRAM won't do anything to the cam when ML is inactive. Why bother?

That's not correct.
After uninstallation by firmware update -> timeout
the cam's bootflag will be removed and the card will no longer be bootable.
If you choose the format option now the card's content (Autoexec.bin + FIR + ML directory + Canon's default stuff + rest of pic/movies/settings) will be wiped, too and all is cleared up. Apart from a few ML settings remaining in card's NVRAM which will have not effect to the cam.

That's what he/she has done.

Why should he do that?

Stupid question: You enabled "MLV Sound" in Audio tab, too?

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.

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.

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

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.

10 days to go and still 37 percent away from goal.
I don't feel very confident with these numbers and don't want to see this project missing it's goal.

What about more marketing by ML team?
- No link/info on download page or on ML's homepage (Twitter aside). Easy to implement and should make those people happy wanting to donate to ML team.
- Quite a small article on Slashcam with not that much emphasis about money. What about other sites (Cinema5D, DPreview, Lens Rentals + myriad others) that covered ML in some way or another?

My 2 cents for now. Have to check bank account and make some calculations ... yes, haven't donated yet.

Some searching on the web indicates that cmos sensors might require around 40 ms of warm up time to reduce noise in images

Do you have a link where I can find such statements?
It sounds like utter nonsense to me. Noise goes up in semiconductors (and other stuff) with rising temperature, not down.

Remove cards, remove battery, remove lens.
Mount lens, insert battery. Don't insert card.
Try AF again. Results?

Read quoted text.

Top of page -> Downloads
and read disclaimer there.

LR basics:
File -> New catalog
and
File -> Open catalog ...
And consult help files, please.

To remove ML from card and camera you have to follow instructions.
You have not followed instructions. Camera's bootflag is still set. And I have doubts about the card, too. Format it using a cardreader, insert it into cam again and format it again there.

You could try but it won't work. Dedicated versions are for the cam they are build for. Exclusive. Double exclusive because each build requires the firmware version it was build for.
Unified version has this name because it works for different cams. Those are listed on the download page.
If your cam is not listed there (it isn't) you have either to use a nightly version or you have to wait. Long wait, maybe.

Sounds like a card going down the drain. Is this the only one you own?
Replace it.