teepo said:omg i almost have enough money to buy a eos 40d. omgmomgogmogg.
Great King Bowser said:Aaaaand yet more Phuket photos. Sorry, I have nothing else to contribute at this point in time. :lol
.
mrkgoo said:Well, I'd imagine you must have thousands of Thailand shots! Nevermind, I could look at them all day. Cute dog. Is it a stray, or just a frequent visitor?
Your shots are so clean and professional looking.
hey_monkey said:Man, I feel like I never get quite the vibrant colors that you guys do -- this especially makes me sad when I realize mrkgoo does so little processing. My photos feel washed out in comparison. Sad.![]()
hey_monkey said:I'm guessing low iso for bright light and higher for darker lights, but I'm not really sure
hey_monkey said:Man, I feel like I never get quite the vibrant colors that you guys do -- this especially makes me sad when I realize mrkgoo does so little processing. My photos feel washed out in comparison. Sad.
I have a question -- how do I know what iso to use? That's one thing my photography professor has just neglected to tell us. He told us what he wants us to use for class, but not how to decide what's best for any given situation. I'm guessing low iso for bright light and higher for darker lights, but I'm not really sure.
I have some to post later, but I just wanted to comment on all the color I've seen in here so far! Especially in the sky. I said wow.
hey_monkey said:Nah, I have a Nikon D80. I'm about to ask what's probably a stupid question -- what's a polarizer? From the last two posts, I'm guessing it helps with that color.
I don't ever do anything in iPhoto anymore, even though I like some of the features, because I switched to RAW and that seems to move it to .jpg automatically. So I do everything in Photoshop now. In most pictures, it isn't much... of the batch that's uploading to flickr right now, I think the most I did to one was select some areas and adjust them specifically in addition to adjusting the whole picture a little. I almost always at least open levels and curves, even if my adjustments are barely noticeable. I've noticed that even the slightest touches with curves can really bring a picture to life. But RAW seems kind of washed out to me anyway.
I don't use any of the settings on my camera -- everything I do is in manual, from focus to adjustments -- but I do have the "more vivid" setting selected. Just kinda seemed like the thing to do, though I probably shouldn't leave it like that.
BlueTsunami, thank you -- that helps me figure out this iso business. I swear, I feel like my professor just doesn't really teach us the basics.Showing slides does help, but only if we understand how to get those results.
Oh, I didn't see your stuff on it, mrkgoo. Yeah, I've been somewhat distressed by noise lately. I didn't notice any in the first pics I took -- at 100 iso -- and then he wanted us on 400 or 800, and I definitely notice more.
Great King Bowser said:I was going to buy a new laptop and give my old one to my sister. But now she bought a new laptop and I don't actually need to replace this one.
40D get as well?
samusx said:Here is a few of mine from the last week or so.
All shot with Canon EOS Kiss Digital X and Tamron 17-50 or 18-250 lenses.
![]()
mrklaw said:if you have a 350d and are considering a 40D - go for it!
high ISO is more usable (I found 1600 on the 350d too noisy for even small prints)
AF is faster
AF is more accurate on all AF points
more fps (although I usually only use one shot)
Live view is fanastic if you take macro shots.
Its just overall a much nicer camera to use and if you're good at taking photos I think you'll really enjoy it.
mrkgoo said:Ah, I see. My understanding of RAW is that it's the raw data from the sensor - not really a picture. I don't think camera settings has any bearing on your RAW data (well, ideally, its not supposed to) - they are mostly for the inbuilt conversion to JPEG.
The advantage of RAW is that you can adjust things without damaging your final image. The RAW data is typically 12-bit information - 4096 luminance levels per pixel. A JPEG is only 8-bit, so only 256 levels per pixel (of which can be red, green or blue). By using RAW, you can tweak and tweak, and when you get process your JPEG, it will convert to that 256 level. Or something. IT's actually more complex than that, because on the sensor, each pixel is either red, green, or blue, but this information gets converted to a single pixel which has Red/Green/Blue channels, of 8-bit each. I'm not exactly sure how it all works out. But regardless, editing a JPEG is reasonably destructive. Each time you edit and save, the JPEG engine recompresses (depending on quality setting), thus losing some information.
fart said:RAW formats are dumps of the image sensor data for a capture + some metadata. some RAW formats are compressed (somewhat lossily) as well (eg, nikon Dx0(0) series).
with only a few exceptions, digicam sensors are grids of photo-intensity devices overlaid by a bayer filter (and some other junk), so RAW sensor data requires a color interpolation step to yield a color image. this is basically RAW conversion, and where a lot of mojo happens. (exceptions are fuji's S series sensor, which is weird, and the one sigma uses, which is RGB)
one generally manipulates raw rather than interpolated data because of the potential for losing information during the interpolation stage. however, this is a little counterintuitive as the typical interpolation algorithm generates a color image of the same pixel-size as the bayer image (the nikon D1 generated an image 1/4 the size of the sensor: i believe this was done at the interpolation step, and the fuji sensor is again, weird), and no digicam sensor that i know of carries nearly 24 bits of information from the sensor. the trick is that no practical interpolation algorithm guarantees an invertible transformation (information can be thought of as akin to energy in this sense).
on top of that, the JPEG compressor is quite lossy, and some editors will sit there recompressing your image until the cows come home, but the point is that even if you were to store your color images in lossless TIFF or something there's a high chance you couldn't ever recover the sensor data again from a color product of your image sensor.
as an aside on jpeg, don't work with an editor that's silly enough to recompress your jpeg every time you save and then hand you back the decompressed pixels. that's just silly. there are competent non-destructive editors for free on every major desktop platform now, so take advantage of them.
another aside on camera data affecting your RAW data. yes! it can happen, and there's nothing wrong with it. the only things guaranteed not to affect your raw data are post-process settings like color balance/color anything else, sharpening, etc. in particular, the 40d has this setting for highlight preservation which changes the gain mode of the sensor amps to attempt to keep you from blowing out your shots. in the camera is actually where you want stuff like this to happen, because the camera is the only thing that has mutable access to sensor and shutter specifics at the time of capture.
fart said:non-destructive is kind of a buzzword right now for the latter, and everyone's doing it (and by everyone i mean apple, adobe, and picasa), which is great, but in most cases it's kind of overkill. at a bare minimum i think a non-persistent multi-level undo and lossless intermediate format is fine for most purposes, and much less resource intensive in most cases (i think these checkpoint editors try to save the transformation instead of the image whenever it's invertible, and limit the possible transformations to mostly nice linear ones, which is kind of a lame tradeoff).
that is exactly the degenerate non-destructive editor behavior, and it's insanely disk intensive when you have to do that for every single change you make to an image.mrkgoo said:I was pretty happy with it just saving a copy when you made changes so you could always revert (if that counts as non-destructive).
fart said:that is exactly the degenerate non-destructive editor behavior, and it's insanely disk intensive when you have to do that for every single change you make to an image.
mrklaw said:
if true, that's just mind bogglingly stupid.mrkgoo said:Hmm.
My understanding of iPhoto06 and before was that edits actually recompressed a new jpeg (with all changes you made), but saved it as a modified picture, leaving your original untouched (so you could always revert). If you edited it a second time, it would load your modified image, and thus would recompress it again.
well, it can get away with this largely because the user isn't expected to make many changes (and there aren't many one can make in iphoto), and they're relatively inexpensive changes to make. that said, much much smarter than the previous scheme if you're right about these. i'd be willing to be that picasa is similar to this scheme (although the spectrum of operations you're allowed in picasa would have trouble filling a thimble)As for iPhoto08, I believe it loads teh original image... then creates a list of changes (probably a very small file)...then applies that list on exit and saves a modified jpeg. If you export the image, it always uses the modified. If you choose to edit it again, it loads the original, and reapplies the list of changes (you can see the changes and sliders changed). So it only ever has two jpegs, and a small list with changes. Not hugely intensive (except when reapplying lots of changes).
at one point the photoshop history basically did this, and it's one of the major things that started chewing up photoshop disk cache. that of course is not persistent, and may have a slightly smarter implementation now, but it's still a monster. capture NX tries to do something similar but with limited persistence (and a limited spectrum of operations), and the amount of disk it can eat up doing this is mind boggling -- gigs and gigs for a single 10mb raw.It makes me think of another piece of software I use, regarding 3-dimensional models, which had files which were coordinates in space. EVERY change you made was out put as a new set of coordinates (100,000's of points). This was so you could 'undo' any edit - it simply loaded the previous set of entire coordinates. THAT was disk intensive!
mrklaw said:yeah, its definitely nicer handling.
Although I hope it does improve my images. I took some photos of my son's birthday party indoors in low light and was forced to use 1600 ISO and the images were very noisy, even at 6x4" prints.
I'd already been looking at the 40D but that sealed the deal for me.
mrklaw said:yep, 1600. Didn't have a choice, it was a large sports center so flash wasn't possible, and I only have f4 lenses.
as for editing, I love iphoto 08 for organising, but found the editing too limited. So I bought photoshop elements. The two work well together. I import/organise in iphoto, but then I can launch elements from iphoto, and when I come back to iphoto, the image is properly updated.
mrkgoo said:If I had to offer criticism, for shots 2,3,4, and 7, there doesn't seem to be much in the way of composition - kind of a bit 'snapshoty', if you know what I mean. I do see that you were trying to capture a butterfly, and number 7 is positioned so that the statue is holding the beam, but those shots appear a bit flat (and not on purpose flat).