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 ... 52 53 [54] 55 56 ... 58
Thanks for help. 60D is a too expensive for me and I don't know if that is 300 Euro more worth. 600D now has a really good price.

In that case and since you come from the 400d: Just get the 600d, it has (nearly) the same sensor as the 650d. And it runs ml now, there's no telling how long it'll take for ml to be ported on the 650d. Alex is busy with the 5d3, and maybe after that it'll be the new 6d that interests people more. And as I wrote, in 2013 Canon is likely to replace the whole aps-c line with new models due to a sensor upgrade, so waiting to buy the 650d does not seem to make sense for me.

Or should I wait for the 650D-Firmware and then buy the 650D? What whould you do?

Nobody can tell you how long it'll take for ml to be ported to the 650d, and in 3 month you can nearly wait another 3 month for the 700d with a really updated sensor. The real difference of the 650d is the much better af system (the cross sensors of the 60d I have, I wouldn't want to have any less), so you have to decide for yourself how much that's worth to you. Or you could also just get a (used) 60d that has ml and ok af :-)

General Development / Re: Gettings started as developer
« on: September 27, 2012, 09:48:37 PM »
Just kidding, I somehow overlooked a really simple solution  ::)

Thanks, and you're indeed correct, I was too lazy to look how the vars are relayed to the ruby script :-p

General Development / Re: Gettings started as developer
« on: September 27, 2012, 09:07:28 PM »
Well it seems to work, but now I get following errors

You have to edit plugins/symtblgen.rb too for the correct path to the toolchain. And please come up with a smart way for symtblgen.rb to pull the path from Makefile.user in the root directory and submit the solution as a pull request asap :->

General Development / Re: fOP
« on: September 27, 2012, 03:53:05 AM »
Right, I have no idea why the forum decided to out this as a new topic

But great topic name that surely will draw attention, maybe it should be a sticky :-) ... and did you check for little gnomes inside you computer lately? :->

Use is_movie_mode() - this one is portable.0

Thanks, will do. While I am not the most experienced low level hacker, maybe I can contribute to the usability because I've been using ml for ~2 years on my 60d now.

What's harder is to switch from photo mode to movie mode.

Yes, I remember you removing movie remap - waaaaaaahhhhhh :-o ... but better safe than sorry I guess.

I think the "rack focus" and "stack focus" triggers in the focus menu should/could to be merged since they are mutually exclusive - rack is for video, stack/bracket is for still shots.

Before I do something that only works on my 60d (the only one I have or know) I wan to better make sure: Is there a dedicated video mode (60d: last setting on dial) on all supported eos, so ml can detect if a video or lv photo mode is selected? And if so, is there an existing variable I can check?

Forum and Website / Re: What do the user classes mean?
« on: September 26, 2012, 10:00:50 PM »
Developer refers to someone who's written (developed) any code related to ML (such as specific features).rials.

Ah, thx for explaining :-) ... though I've just been told it takes more than one patch to be a developer, it's not a over-night decision.

Are you sure it's legal to do this in the first place?

I put up a poll (but plz discuss here) to get a survey:

And my 2 cents in this thread, too: For me it doesn't matter if possible, impossible or hard to do, neither if it's legal, illegal or half-legal. Directly torpedoing Canon's high-end business model is something different from beefing up low- to midrange cameras with features Canon is too lazy to implement.

I am convinced Magic Lantern is helping Canon, even if they are too conservative to acknowledge it. Directly obsoleting the 1dc is something else and might change their opinion from neutral to hostile and will hurt the manufacturer. Imho if someone or a company can afford the $6500 1dx, there's no need to help them save money. Ths ml business model should not be "give us half the $$$ difference 1dx/1dc and we'll unlock it".

General Development / POLL: Should ml attempt to hack the 1dx into a 1dc?
« on: September 26, 2012, 08:39:49 PM »
EDIT: Please vote here, but discuss in the existing thread :->

Since it was discovered that the 1dc is "just" a more expensive 1dc with a firmware upgrade, people all over the place (like the CR forum) state that the Magic Lantern will hack the 1dx to save people spending money on the 1dc.

Apart from my personal opinion (see discussion thread) I'd like to get an impression of the general feeling, so here's the possibility to make your voice count (well, at least numerically).

General Development / Re: Suggestion: Focus menu improvment
« on: September 26, 2012, 08:28:40 PM »
Looks like not many users share my suggestion, i find it quite useful and quick.

Imho it certainly would be useful and would defeat the need to af to see what the pattern is - but as I wrote you should do a feature request in the correct section, that'd make it more likely for someone to implement it. I currently only do what I really miss badly from ml myself.

Forum and Website / What do the user classes mean?
« on: September 26, 2012, 07:37:27 PM »
I know supporter means you have paid some $$$ for ml ... but what does contributor (yellow bar) or developer (green bar) mean, and what does it take to be acknowledged as such?

General Development / Re: Suggestion: Focus menu improvment
« on: September 26, 2012, 07:34:47 PM »
Yes, i agree with you and i'd love to see one more thing added, if you can do it.
I always try to use the focus patterns but if you don't have a particular setting for both the AF start and the focus point selection the selection of the points itself is pretty hard.
Since we have the diagram of the patterns already can't you integrate them directly in the focus patterns submenu? (like cropmarks, for instance) .
Or, at least, think of a way to call them so you don't have to see them if it's not possible?

I don't quite get it - you want an option to cycle through the patterns and preview of the current pattern in a submenu like cropmarks? If so, that goes beyond a restructure of the focus menu, you should do a feature request for that. It makes sense to me, but I wouldn't implement it myself since I concentrate on focus stacking/bracketing atm.

General Development / Re: How to get number of focus steps for dof range?
« on: September 26, 2012, 07:17:38 PM »
Keep in mind that not all lenses report focus distance

I know (there's even a table in some wiki), but at least for the ones that so (like the Canon macro lenses) it would be a nice addition. Btw: These macro lenses (I've got both the 100L and non-L) report the distance only very roughly at far range, my 70-300L is much more precise.

Your suggestion with the per-lens table might be the only working way to go, maybe it isn't that much work to implement it after all.

General Development / Re: Gettings started as developer
« on: September 26, 2012, 07:15:47 PM »
Hello ML developers,

I'm a hobby open source developer and electronic engineering student. As I'm quite familiar with C development and embedded systems, I wan't to join the ML development team. I have a EOS 7D, so I'm especially interested in porting ML to this DSLR. I already got ML classic to compile, but then I found out that ML Unified is the way to go. So can anybody please introduce my to the development community and help me getting started with development and testing?


Just code away (maybe after getting feedback for your idea) and then do a mercurial pull request, that's what I just did with focus bracketing. But it's easier for me since ml already works on my 60d, little chance to brick it at this stage.

General Development / Suggestion: Focus menu improvment
« on: September 26, 2012, 07:13:37 PM »
Am I the only one who thinks "wtf?" all the time when looking at the focus menu? The rest of the menus is neatly organized, but in the focus menu rather informational lines (like "Focus End Point") mix with settings, and rack/stack/bracketing options are all over the place.

If no one violently opposes, I'd integrate the following change in a patch:
* Move "Focus StepSize & Focus StepDelay & Rack Delay" the menu that is @"Stack focus"
* Move "Focus End Point" down to the other informational lines
* Merge "Rack Focus" and "Step Focus" triggers because they are mutually exclusive anyway: You do Rack focus in video mode and stack/bracket focus in the photo modes, so ml should be smart enough to trigger the correct one itself.
* Maybe add a real "Reset distance" option because it's not intuitive that have to use SET on the distance like now

The change might break some existing stack/rack focus tutorials, but I don't think too severely, and you cannot make an omelet w/o breaking eggs :->

General Development / How to get number of focus steps for dof range?
« on: September 23, 2012, 02:00:04 PM »
When I added focus bracketing (see pull request) I wanted to add an "auto" setting that takes one shot behind and/or in front the current focus pane so that the start/end of the depth of field is where the original focus was. The intention to use the whole dof on the object and not unnecessaryly shoot some sharp air next to the object - it can be done with mf, focus peaking and dof preview but I'd like to automate it.

This would be *extremely* convenient for focus stacking, too - instead of manually guessing a stepsize for a given aperture ml could calculate it so that the dof-panes are exactly (or with a little overlap) behind each other with no missing parts out of focus!

Ml already reports the dof in meters - I didn't really look at the code yet, but can anyone tell me if there's a way to get a stepsize for the focus command from these dof values?

Archived porting threads / Re: Canon 5D Mark III
« on: September 23, 2012, 01:11:21 PM »
To solve these things, I don't see other way than posting a few versions with even less features, and see which ones crash and which ones don't. This might provide a hint for what is causing trouble.

I can't help because I don't have a 5d3, and even if I'd be hesitant to use a €3000 camera with alpha ml - with my 2y old 60D that has 100k shutters it's different now.

My opinion: Take your time, most people will understand debugging these things w/o a tethered software debugger or eos simulator is extremely time-consuming and annoying. There has never been an announcement for the ml 5d3 release date, and every time some posts "it's here soon" I reply "not necessarily".

Feature Requests / Re: Powersave for focus peaking
« on: September 23, 2012, 01:07:14 PM »
See - from my measurements, peaking does not drain the battery.

Wupps, it that's still valid for the latest peaking code I fell into the same trap and time runs much faster when using Magic Lantern because it's more fun :-) ... so forget the request until I come up with a different measurement myself.

Archived porting threads / Re: Canon 5D Mark III
« on: September 23, 2012, 11:32:25 AM »
Is stability less important than those?!

At the moment, from what I've reading on "Canon Rumors" I'd definitely opt for stability before features before usability/beauty, many people still seem to be concerned that the ml "hack" voids their warranty (Canon dealer's fud) or bricks their investment. Usability should be the main focus when the new menu system/look is implemented (Magic Lantern 3.0?).

PS: Esp. the 5d3 and 7d are more professional cameras with a userbase that won't be very thrilled to play guinea pigs because they could loose money if it their camera breaks or doesn't do what they'd expect it to do.

Feature Requests / Powersave for focus peaking
« on: September 23, 2012, 11:26:38 AM »
I really like peaking when doing macro work, but it drains the battery even on the rather power-efficient 60d in no time. Setting the "turn off global draw" timer is nice, but not a real alternative because it disables the whole thing. As it is now, when I'm running low on battery I cannot use peaking anymore ... and yes, I could buy a bunch of spares, but I'd prefer a software option :-)

If possible it'd be nice to have a powersave option that either would use a tweaked more power-efficient algorithm or simply lower the update frequency from "as fast as possible" to "as slow as usable" - or wouldn't that make a difference battery-wise?

Feature Requests / Re: Canon 6D with shutter speed 1/4000
« on: September 22, 2012, 08:48:26 PM »
ML wasn't able to change this yet in photo mode. In movie mode, it was easy.

I suspect the 1/4000s limitation (and only 1/180s x-sync) is purely due to marketing, but on the other hand the shutter might not be designed for 1/8000s and wear down faster its only 100k lifecycle - hard to say w/o Canon telling us...

Archived porting threads / Re: Canon 5D Mark III
« on: September 21, 2012, 03:48:52 PM »
Yes 4k may not be possible on the 5D3 but maybe a firmware analysis of the 1DC will show how to make clean hdmi and maybe 1080p60/50 ?

I'd be amazed if Canon didn't take some countermeasures to port 1dc features to the 1dx or even 5d3, they'll loose a lot of money if it would be done... though no harm trying I guess.

Archived porting threads / Re: Canon 6D support?
« on: September 21, 2012, 03:47:13 PM »
Regarding AF, I've shot a few pictures with 5D3 in AF ( 50/1.8 ) and a few of them came out grossly out-of-focus. No moving subjects, just static portraits. So, for me, lack of advanced AF is not a big deal.

The 5d3/1dx af is tuned for the latest Canon 2010+ lenses, esp. the 2.8 zooms and some like the 70-300L - in these cases it's a fast and precise "closed loop" system. I wouldn't expect the oldest possible lens w/o even usm to profit from the 5d3 af.

It is a request from the Canon rumors forum, but I think it makes sense, too and should be easy to implement:

It was so easy I've just done it myself :-), working just fine. I'll test it a little and then upload it as a Mercurial pull request.

Pages: 1 ... 52 53 [54] 55 56 ... 58