August 28, 2014, 03:09:41 AM

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 ... 3 4 [5] 6 7 ... 294
Canon General / Re: New Speedlite Coming? [CR2]
« on: July 17, 2014, 10:07:18 AM »
Yep, battery charge indicator would be useful. I suspect if Canon were truthful, they'd tell you that recycle time is the de facto battery indicator.

I have absolutely no clue why there is no battery meter - probably a technical problem because the power flux is so dynamic it's hard to get a good reading on the charge (and because all batteries have different discharge curves)?

Btw Canon *does* say the recycle time is the battery meter, as far as I remember it's there in the manual in the cfn description to show the slave "charge ready" status either by the red blinky or just the small light on the back.

An overheat warning might also be helpful to avoid damaging the flash.

Um, the flash get disabled if it's running too hot, doesn't it?

EOS Bodies - For Stills / Re: 60d results - the bird feeder
« on: July 17, 2014, 05:34:16 AM »
The great think about chickadees is that you don't need hunting blinds to get close.... all you need are some sunflower seeds and a lens that focuses within half of an arm's length....

Ooooooh, these are really sweet :-) !!!

My previous camera, T1i, I didn't have any issues with any of my lenses. I'm betting it's me.

Probably, Canon lenses are usually adjusted just fine and f2.8 isn't as critical as 1.2. But if you can there's  peace of mind after making sure. Note that every camera body needs different afma adjustment values, so if your ti1 worked fine your 60d might not.

Last not least, afma is not a magic bullet. Newer cameras have different settings for the long and wide end of zooms, but it's still not sufficient since afma also changes with the subject *distance*. Afaik the newest Sigma lenses take this into account while Canon (still) doesn't.

EOS Bodies / Re: Canon 6D N
« on: July 17, 2014, 03:51:17 AM »
Then again, I've worked both at Apple and at an embedded Linux startup, so it's possible that I'm just a bit biased against RTOSes.  :)

Interesting observations, though I (I never did rtos programing) like to add this theory: It's easier to debug and build a reliably system because if it works once then it'll work every time sine timing is fixed and this no problem. Do Nikon and/or Sony and other companies use multitasking non-rtos designs in their cameras?

Btw I don't find the Canon wifi implementation *that* horrible, video/wifi is bothersome but I don't do this, my main issue is that you cannot connect to a laptop in client mode but have to setup a virtual ap on the computer.

Canon General / Re: New Speedlite Coming? [CR2]
« on: July 17, 2014, 03:42:01 AM »
I hope they give the new flash head the same range of rotation as the 600EX-RT.  The head of the 430EX has a limited range of rotation.

There are only so many things how you can cripple a flash so people who don't need the "pro" features like ext. power supply and fast recycle time still can be upsold to the most expensive model. Imho Canon won't change a running system, and the extended flexibility of the head is one of the things that appeals to everyone.

The other thing the "small" flash probably won't have is the great 600rt usabilty simply because the flash is smaller, so if using one on-hotshoe or on-bracket flash the 600rt will still be better unless you perfer the in-camera menu (if you manage to find it).

Canon General / Re: New Speedlite Coming? [CR2]
« on: July 16, 2014, 10:14:49 PM »
I think Canon will NOT price the 4X0RT low enough that too many will be inclined to settle for that instead of another 600 (especially if refurbished).

On the other hand, their latest releases (70d, 16-35L-IS) were rather reasonably priced - so you never know, even with Canon :-p

Software & Accessories / Re: Post processing workflow
« on: July 16, 2014, 10:13:40 PM »
Some photogs simply don't want to know anything about post and some of snapshooters just want the magic solution (click and poof).

Thank the maker for that, or otherwise it would be even more difficult to separate oneself from the crowd now that every joe sixpack can buy a ff dslr in the next radio shack (including me) :-)

Canon General / Re: New Speedlite Coming? [CR2]
« on: July 16, 2014, 07:57:23 PM »
Let me rephrase that- how much cheaper will Canon be willing to price the 4X0RT anyway? (considering Canon's general inclination towards R&D roi and profit)

You don't want to hear my answer, I'm Mr. "Canon is too greedy" around here. Though I have to admit the 600rt is a very good piece of equipment, they have to get back their r&d investment and Yongnuo just showed us how not to do it with the terrible st-e3 transmitter clone.

Canon General / Re: New Speedlite Coming? [CR2]
« on: July 16, 2014, 06:34:14 PM »
And how much cheaper can they make the 4X0RT anyway?

Much cheaper, look at third party flashes, even if you allow for a higher Canon quality. Flash technology isn't space age anymore - it's just about how much r&d roi and profit Canon wants to have.

If the 4??-EX-RT came out tomorrow I might buy four in a year or so, but then again I'd probably just get more 600's.

One advantage of having the same flash models is that if you use m flash, you get more of a feeling how much power is required - this alone is a reason I'd stay with the 600rt if I can afford it. Mixing my 600rt with my old 430ex always ends up in a struggle concerning different power output and recycling times. You big boys with studio strobes probably have more experience mixing light sources though.

Software & Accessories / Re: Post processing workflow
« on: July 16, 2014, 06:09:16 PM »
And all the workflows i found differed from each other, irregardless of the gear used, the type of photographs, or the subjects. Every workflow looks like a "magic recipe".

That's because every photographer is different, and the workflow reflects this. This isn't some empty wisdom, but it's really worth it to figure out what *you* want to do in which steps and then adapt your workflow accordingly. LR is a great tool for this with smart collections and keywords. Beware, this takes time.

What are the advantages and disadvantages in doing any of this operations during raw conversion?

A complete raw workflow is non_destructive, a biiiiiiig advantage since you can always go back any step in your history and don't waste disk space on storing rendered images. So if possible keep the raw workflow as long as possible, and only do the final steps on the rendered image.

Why are there so many different functions and algorithms for sharpening? And why should i use one over the others in any given situation?

You can spend the rest of your life researching this issue - it's a tradeoff hassle vs. quality. If you process a shot that will be printed on a large wall and get paid $10k for it, it's worth it to really fine-tune sharpening and noise reduction. If you downsize - which you will do most of the time - it's a wash and you won't see much of a difference in the final exported image.

Is there a book (or several) that can help me quench this thirst for knowledge?

Probably :-) ... but it pays to experiment for yourself to develop *your* style. Also look at video tutorials, either free (yt) or commercial like Lynda.

EOS Bodies / Re: Canon 6D N
« on: July 16, 2014, 06:00:15 PM »
A company trying to do it themselves is pretty insane.

Correct me if I'm wrong - but I guess Canon is licensing some ip core with sdk and then either puts it inside one of their custom chips or adds another chip on its own (probably together with gps). If that's so, then Canon dryos doesn't do anything different than Linux would do: interface with the wifi ip core and do some high level requests like "please connect to xyz" or "transfer image abc"?

EOS Bodies - For Stills / Re: 60d results - the bird feeder
« on: July 16, 2014, 02:37:30 PM »
Overall, I was happy with the pictures.  I did have a lot of OOF shots that I will chalk up to my mistake, but I have also noticed that other shots I've taken with other lenses seem soft too.  I'll investigate this more in the coming weeks.  I hope I don't have to have my lenses/camera calibrated, but if I do then I do.

The 60d is a great camera for macro or tele shots, and for that kind of money it's a steal.

The one problem is the missing af micro adjustment (thanks, Canon!) so if slightly oof shots occur you never know if it was the phase af normal variance or a systematic error. I'd advise you to get hold of a camera with afma (for example the 70d) and then test your lens(es). If there is a large afma requirement, you can get it adjusted by Canon service. The 70-200L is such a premium lens so that it's probably worth the hassle.

Technical Support / Re: Stop exposure at overexposed pixel threshold
« on: July 16, 2014, 02:33:49 PM »
Pixels can Overexpose due to factors other than true exposure.  e.g. Image noise and hot pixels could cause your camera to underexpose.

Of course the software can account for that: Magic Lantern does it with the ettr function, you can set a threshold of allowed clipping. Problem is that it only after reading the data from the sensor (i.e. in live view or analyzing a shot just taken) and thus cannot cope with fireworks.

Canon General / Re: New Speedlite Coming? [CR2]
« on: July 16, 2014, 02:13:59 PM »
here is a sample photo that

You should clean your sensor or use LR's healing brush :-p

I can't wait. I hope this is the 4?0EX-RT everyone is expecting.  I'd love to get three flashes and a controller for under $1k.

Don't hold your breach: The 600rt price has dropped some and it's included all Canon deals, while the 440ex (or whatever the name) is new = price premium. It might even have some additional gimmicks like continuous video light that many people won't use but that sill drives up the price. If it's €300, I'd rather get a €400 full 600rt...

Technical Support / Re: Stop exposure at overexposed pixel threshold
« on: July 16, 2014, 09:51:58 AM »
Hence, I was thinking that maybe an exposure time based on how many pixels are reaching their overexposed status during the actual shooting would be a working approach.

For that, you'd need the ability to read information from the sensor before the actual data readout, afaik that's not possible with the current design. But I already wished for this myself, "why not just engage bulb mode and let the camera figure out the rest?".

So for fireworks, you basically have to resort to trial & error and try to be on the safe side to prevent white clipping or the colors are gone. This is tricky for short fireworks w/o previous experience, when in doubt look at shots around the net and check what expo settings they were using. Last new years eve, I was using 60sec @iso200 with f8.

Few days ago I was trying to make a timelapse of a firework show. I went for a fixed exposure in every shot: well, it turns out fireworks can have a great and sudden dynamic range, so half of the pics are exposed just right, but the other half is way overexposed.

In general for timelapses use Magic Lantern, it's got built-in expo ramping and deflickering for this very purpose.

For fireworks,  it depends if you also want part of the dark background visible. In that case, you want as much dynamic range as you can grab, so use Magic Lantern's dual_iso module - if exposing @iso100 it should also result in a nice blur effect for the fireworks.

EOS Bodies / Re: Canon 6D N
« on: July 15, 2014, 05:38:15 PM »
The first thing that I'd do if I were designing the next camera would be to use DRYOS solely for the guts of the camera operation (if at all).

Oh no, I hope they keep using dryos, after all this is what makes Magic Lantern run :-) ... even with a oss os, they most likely would have to scratch a lot of their work.  From a ML programer's perspective, dryos seems to be pretty ok esp. considering Canon developed it on their own to avoid license fees. Of course with the catch that Canon doesn't release an sdk and you have to find and figure out all functions for yourself, but that's not the os' fault.

As for needing a rtos or not, I cannot quite say (though I guess the ML devs could) - but I figure there is a good reason they use it other than some workarounds. Linux has a considerable overhead and for running on embedded you have to customize it all the time (see Android or routers running Linux). And you really don't need Linux on your EOS, you can already play Sokoban and Arkanoid with Magic Lantern :->

Pages: 1 ... 3 4 [5] 6 7 ... 294