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.

Messages - Marsu42

Pages: 1 ... 54 55 [56] 57 58
Archived porting threads / Re: Canon 5D Mark III
« on: September 06, 2012, 09:07:18 PM »
For now, I can say that LiveView is actually a lot more usable in darkness on 5D3, compared to 5D2, probably a 2-3 stop improvement. Certainly a lot more than the 0.5 stops rumoured on some forums.

Thx for the first impressions- it's valuable to me because I trust you to be more independent than the usual "I bought it for $3500, it must be stellar" vs "I cannot afford it, it has to be bad" forum talk.

Btw, the alleged 0.5 stops improvement concerns the iso noise in raw shots, and I must admit myself after comparing iso samples from 5d2 and 5d3 myself that up to iso3200, it doesn't make much of a difference. The one thing that is more of a problem on the 5d2 seems to be stronger banding, and this limits raising shadows much more than iso noise - the 5d3 has cleaner sensor readouts...

Archived porting threads / Re: Canon 5D Mark III
« on: September 06, 2012, 11:23:41 AM »
I just thought of another thing that drives me bonkers sometimes is the ability to see the AF points at times. I wonder if you can figure out how to make it so that it's always on the bright red for confirmation. There was word that Canon was working to fix this problem.

The problem according to Canon is that highlighted af points hinder metering (unlike the 1d4), it seems to be a design flaw with the many af points and Canon already stated that the upcoming solution "might not make everyone happy". On another forum it was already suggested that's because the solution might be "no solution at all" :-p

@alex: Now that you've handled both 5d2 & 5d3 extensively, maybe you could write something about your personal "is it worth it" opinion about the differences? I'm still unsure about which camera to get, and for the 5d3 I'd have to wait for a price drop anyway. But now that ml is really ported, I'm not so sure about the 5d2 anymore (worse af, more banding).

General Development / Re: Compile ml w/ Linaro gcc?
« on: September 06, 2012, 10:01:40 AM »
Only one thing, wasn't movie restart working on 50D lately?
There was a fix by somebody, i read about it on google groups.

My compile is the ml2.3 release build, if it's not working in alex' official version it won't work on this one (and I have got a 60d, not a 50d). But feel free to install mercurial & gcc yourself and add the patch from google groups, it just takes a day to set it up :->

General Development / Re: Compile ml w/ Linaro gcc?
« on: September 05, 2012, 11:43:22 PM »
I usually only add these lines:

@alex: *Where* do I add these lines in the In the places I tried they are ignored and everything is compiled with -Os in spite of the special lines with -O3 for zebra.o and so on...

edit: just realized that ML uses -march so it should be good.

... still, if the exact cpu is known shouldn't be -mtune=arm946e-s or even -mcpu=... better in addition to -march?

Please do all tests on 2.3 stable (it's tagged on bitbucket as ML2.3-stable, revision afdeefef62fa)

Ok, here it goes - standard -Os compile with current Linaro gcc 4.7, working ok on my 60d, anyone feel free to try it for regressions to the release build with the vanilla fsf compiler:

General Development / Re: Compile ml w/ Linaro gcc?
« on: September 05, 2012, 10:02:13 PM »
Let me try to reproduce it.
I just opened LV with focus peaking active.

Alex did some changes to focus peaking recently (see changelog), it might be buggy. I'll do Linaro compiles for the stable 2.3 tag, optimized and non-optimized, this should be better than testing the unstable trunk. Check this thread again tomorrow at latest for the d/l links.

General Development / Re: Compile ml w/ Linaro gcc?
« on: September 05, 2012, 09:40:55 PM »
Got an error, here's the log file.
Looks huuuge.

:-) ... what did you do to throw the error? I turned on all optimizations the devs recommended for the 60d, but they also said that might decrease stability. Maybe the next step should be to compile it with standard settings and Linaro 4.6 and then 4.7 to isolate the cause of problems - but as I wrote it runs just fine on my 60d as far as I can see, but your 50d is another model alltogether.

General Development / Re: Compile ml w/ Linaro gcc?
« on: September 05, 2012, 09:32:26 PM »
Thanks, will try it out.

... and remember it's the latest trunk, so if anything's broken it might be very well the sourcecode itsself, too.

General Development / Re: Compile ml w/ Linaro gcc?
« on: September 05, 2012, 08:58:19 PM »
... btw, here's the autoexec if anyone wants to run a stability test and is to lazy to compile Linaro gcc: [link deleted: obsolete]

General Development / Re: Compile ml w/ Linaro gcc?
« on: September 05, 2012, 08:17:42 PM »
Maybe it's worth a shot

Harrrgnnn ... now *that* was annoying, but I managed to compile ml with latest Linaro gcc 4.6 series (d/l from Launchpad) and even valiantly tested it - runs fine so far :-)

However, I couldn't persuade summon-arm to get even fsf gcc to compile on my x64 Ubuntu lts system, so I used the arm toolchain from and replaced their gcc source with Linaro before running their ... and I had to patch newlib, see the patch @

If you manage to write some benchmark we might even see if it was worth it - but since Linaro is working on optimizing gcc for arm for years, I think it certainly cannot be worse than the vanilla version. And we could try to compile ml with Linaro gcc 4.7, but without any benchmarks it would be a waste of time because we cannot tell the difference offhand.

General Development / Re: Compile ml w/ Linaro gcc?
« on: September 05, 2012, 12:01:47 PM »
Compiling with -O3 also has noticeable speed improvements, but it caused trouble on 500D so I've turned it off in 2.3.

... that's the CFLAG in line 161 in which is -Os in the current hg checkout, so I can should/can change that to -O3 if the target is my 60d?

General Development / Re: R: Compile ml w/ Linaro gcc?
« on: September 05, 2012, 11:53:38 AM »
The stability test sub-menu has some benchmarks too if I'm not mistaken

Alex' post implies that you are mistaken - but I'll have a go at compiling it w/ Linaro and let you know my findings. There shouldn't be too many changes necessary (unless I try 4.7), Linaro is proven & stable and is the default compiler on Ubuntu.

General Development / Re: Compile ml w/ Linaro gcc?
« on: September 05, 2012, 11:14:12 AM »
I'm interested too, if you succeed, please let me know (especially if there are any performance improvement). I couldn't compile with Linaro, but that was many months ago.

Hmmmm, I'm still somewhat critical about the guinea pig role, but I've been using Linaro for years to compile OpenWrt for my router (though it is mips and Linaro improvements are mainly for arm). And since I'm no ml insider, it is very unlikely I could recognize any performance improvements, or are there any dev benchmark tools hidden somewhere in ml? But I'll let you know if it compiles, and if I'm to hesitant to try it myself maybe you could have a go with your sponsored guinea pig hardware :-o

General Development / Compile ml w/ Linaro gcc?
« on: September 05, 2012, 11:05:34 AM »
I'm just setting up the arm toolchain and noticed that that the summon-arm script contains the outdated gcc 4.6.2 (current is 4.6.3).

Is there any reason to use this particular gcc release, and why doesn't it use the current linaro 4.6 or 4.7 gcc which is supposed to be the latest and greatest for building arm compiles? Is it just because of "never touch a running system" or does any more current gcc release make your cameras crash and burn? What gcc do you guys use?

Archived porting threads / Re: Canon 5D Mark III
« on: August 31, 2012, 12:01:36 PM »
CARD_DRIVE is used in string concatenation at compile time ;)

Well, then the easiest way would be to do two compiles (at least for ml release versions), one for the sd and one for cf card slot? Imho that would be better than to force end-users to use one specific slot.

General Help Q&A / Re: Magic Lantern Slow Bracketing
« on: August 31, 2012, 11:57:48 AM »
Ignoring the intervalometer for a second, I set ML bracketing to take 3 shots: 0, +2, -2.  My problem is that ML seems to take the shots quite slowly in comparison to Canon's AEB.

Ml's bracketing is slower than Canon's (I guess esp. on the faster 60d), but not by that much. Try m mode, that should be the setting w/o anything else interfering to see max ml speed. Once I had a problem that 5+ bracketing was slow because ml took a pause after each 2 shots, but that's been solved in the meantime.

Feature Requests / Re: Improvement for "Compare Images"
« on: August 30, 2012, 09:22:08 PM »
5D3 has it, exactly as you describe it. It's not easy to implement; if it can be done, there will be a lot of flicker when moving one image.

Then it's time for me to save for a 5d3 :-o ... but this proves that if even Canon think it's useful it might be a good idea to give it to the rest of us, too. Personally I don't expect super-smooth scrolling, but if it works at all it would make compare images much more useful for 1:1.

Well, as always it's up to you to decide how much work it'll consume and what priorities to set. But maybe at some point when you've collected lots of possible feature requests you could do a poll to get some user/supporter feedback on how much demand there is.

Archived porting threads / Re: Canon 5D Mark III
« on: August 30, 2012, 10:05:25 AM »
- HDR bracketing looks pretty nice in Canon's implementation (7 frames), do we still need ML HDR?

... but Canon doesn't do *automatic* bracketing with as many frames as it takes, or weren't you talking about that?

- I'm thinking to limit ML to CF cards only, anyone requires SD cards?

... I think it should be the other way around (!): The sd card controller on the 5d3 is crippled and only writes at very slow speeds if you didn't realize yet - so many people will be using the sd slot only for backup purposes (like write jpeg to it while raw/video goes to cf). Thus, cf cards will get changed much more often, and ml might be better placed on the sd that stays in the camera.

General Development / Re: Custom ML themes/menus!
« on: August 29, 2012, 10:18:28 AM »
I would love to be able to choose between different menu styles every now and then, just like in the old Sony Ericsson phones with  custom flash menus supported!

Themes are nice and all, but my 2cents is to ask for a default theme that looks as similar to the Canon menus as possible. From what I'm reading, ml is still widely considered a "hack" by seasoned photogs and a seamless integration might help to change this, allowing the user base to grow.

General Help Q&A / Re: How to make the shortcut keys work (60d ml 2.3)
« on: August 29, 2012, 09:02:44 AM »
On a 60D to access the shortcuts in movie mode you must press the metering button (the button between ISO and the light bulb)

Yuck, how am I supposed to know *that*?! And on my 60d it works in lv, too, though adjusting the audio doesn't really make sense there ... this piece of information should really make it into the help display - but thanks a lot for explaining!

Feature Requests / Re: Multiple Settings/Presets
« on: August 29, 2012, 08:51:44 AM »
That's a different feature IMO, autoexec selection is useful for beta testers, config presets is for end users.

+1 for different config presets like the display presets - I always wondered why ml doesn't feature this, even Canon has a "C" setting on its camera bodies.

The nicest option would be menu tab / ml start screen that appears after pushing the ml button (like the Canon user menu). There the different configs should be quickly selectable, optimally with custom names. I'm only using ml for 4-5 scenarios, and juggling through the menus is possible, but time-consuming.

General Help Q&A / Re: Am I to stupid for focus stacking on a 50D ?
« on: August 28, 2012, 11:26:54 PM »
Descriptions on a 60D doesn´t work on a 50D. If I push "Focus End Point" on the videos liveview appears again (at me too), but I can´t change the focus range and therefore the message is always "will take 0 pictures"

There are many outdated descriptions, you must not push "Focus End Point", this resets the range. Just follow these steps (well, on 60d at least, but it's a unified build after all): 1. enable follow focus, 2. go in to lv, 3. zoom to start point (any way, manually is also ok), 4. zoom to end point with arrow keys, 5. go to ml menu & start rack focus or stack focus.

Forum and Website / Re: Plz remove 90sec delay limit between posts...
« on: August 28, 2012, 08:48:04 PM »
Unfortunately, given the forum software we are working with, it is not possible to give different post-time restrictions to different member types.

Ok, I can understand that. I guess the software is only able to count 90secs from the last *try* to post? Because just now this happens: Wait 89sec -> error -> counter is reset -> Wait another 89sec -> next error (though the last real post is 2*89sec ago) - argh. At least I've learned to ctrl-a+ctrl-c my post before submitting.

Feature Requests / Re: One shot Audio RemoteShot
« on: August 28, 2012, 08:46:19 PM »
Maybe we can expand it with a "number of shots" sub-option like the other features have?

+1 for that, calibrating the trigger level is a pain in the a** and at least this way multiple accidental shots would be prevented. Actually for me personally a calibration would be even more useful, I created another ticket for this:

Feature Requests / Calibrate Audio RemoteShot Level
« on: August 28, 2012, 08:39:46 PM »
Setting the "Trigger level" for Audio RemoteShot is rather annoying because you have to exit the menu, try, change, retry, ... until finding the level that is louder than the background noise and still does the trigger w/o firing a gun next to the camera.

Suggestion: When opening the "Audio RemoteShot" submenu, add an audio meter or some much simpler binary indicator that shows if the threshold is reached. This way the the level could be changed in the submenu and it the result could be seen/tried *immediately*. Imho shouldn't be too difficult to implement because the metering code is of course already there and would simply have to be tied to some indicator in the submenu?

Feature Requests / Re: [WONTFIX] In Camera HDR for 550D
« on: August 28, 2012, 08:06:42 PM »
but this will be just awesome.

No, it wouldn't - the in-camera hdr mode of the 5d3 is just an excuse for the lack of dynamic range improvement in comparison to the 5d3 and Sony sensors. No in-camera processing will even come close to the quality and versatility of something like Photomatrix. Canon should have used the dev time to implement a game like pong in the firmware :-p

Pages: 1 ... 54 55 [56] 57 58