Author | Thread |
|
06/03/2009 11:56:33 PM · #51 |
OK -- perhaps I should have said "falsifying" EXIF data ... though I'd consider it "altered" in the sense that the data recorded does not reflect the actual conditions under which the photograph was obtained. I'm pretty sure we'd not be standing on technicalities in such a situation, since the site can essentially cancel anyone's account for about any reason (or maybe no reason) anyway, not that we have any desire to do so.
Message edited by author 2009-06-03 23:56:47. |
|
|
06/04/2009 12:16:25 AM · #52 |
Originally posted by daryn: He runs a highly successful photographic agency, with no paid photographers.
Whatever the customer requests is the next challenge.
The customer then has loads of images to select from.....
Conspiracy freak? Me? |
Assuming this is true which I think it is not; would it be legal? |
|
|
06/04/2009 12:56:49 AM · #53 |
Originally posted by glad2badad: Originally posted by yanko: I'm confused. Are you talking about the image numbers used in the file names (ex. IMG_5395.CR2)? If you entered one challenge with IMG_5395.CR2 and then next week with IMG_3192.CR2 it could just mean the photographer shot a lot between challenges. |
Example scenario:
On May 26th, 2009 you set your camera's date ahead to June 2nd, 2009 and take a photo with file # IMG_2450.CR2.
On May 27th, 2009 you set your camera's date back to May 27th, and take a photo with file # IMG_2500.CR2. You enter this photo in a challenge (call it Challenge One) with a submission date period of May 24th thru May 30th. All is fine with this photo.
On June 3rd you enter a challenge (call it Challenge Two) with the photo taken on May 26th (although it's EXIF says June 2nd) - file # IMG_2450.CR2. On the surface it looks fine as the challenge submission date period for this challenge is June 1st thru June 7th.
You're on a roll and end up in 5th place for Challenge One. Your photo is validated per request (places 1 - 5 are automatically requested). Everything is good.
Challenge Two is rolling along smoothly, then something you did in post-processing triggers a validation request. You submit the original for review. Looks fine date-wise, however, how could you take a photo on June 2nd for Challenge Two with a file # that is earlier (#_2450) than the file (#_2500) for Challenge One?
Yes, SC would have to be looking for it for any red flag to be thrown, and you could have an alibi that you reset the numbering on your memory card, etc...
Certainly would be a lot of effort I suppose and like muckpond said "...all of this effort to win...I'd vote you get to keep it". :-) |
The algorithm you describe is valid but the reference number cannot be the file number as the camera can be set up so that a new set (starting from _0001) is created for each freshly formatted card, in fact, that is the way I prefer to number my images. Instead the shutter actuation number can be used as the reference. Such number cannot be changed, it does not show up (that I know of) in the metadata read by Photoshop but it is easily extractable with opanda.
I doubt there is any other way, besides the way you describe (but using the shutter actuation number and not the file number as a reference), to detect an inaccurately set date, but it would be interesting to hear from muckpond on this.
|
|
|
06/04/2009 02:36:34 AM · #54 |
Originally posted by senor_kasper: Originally posted by glad2badad: Originally posted by yanko: I'm confused. Are you talking about the image numbers used in the file names (ex. IMG_5395.CR2)? If you entered one challenge with IMG_5395.CR2 and then next week with IMG_3192.CR2 it could just mean the photographer shot a lot between challenges. |
Example scenario:
On May 26th, 2009 you set your camera's date ahead to June 2nd, 2009 and take a photo with file # IMG_2450.CR2.
On May 27th, 2009 you set your camera's date back to May 27th, and take a photo with file # IMG_2500.CR2. You enter this photo in a challenge (call it Challenge One) with a submission date period of May 24th thru May 30th. All is fine with this photo.
On June 3rd you enter a challenge (call it Challenge Two) with the photo taken on May 26th (although it's EXIF says June 2nd) - file # IMG_2450.CR2. On the surface it looks fine as the challenge submission date period for this challenge is June 1st thru June 7th.
You're on a roll and end up in 5th place for Challenge One. Your photo is validated per request (places 1 - 5 are automatically requested). Everything is good.
Challenge Two is rolling along smoothly, then something you did in post-processing triggers a validation request. You submit the original for review. Looks fine date-wise, however, how could you take a photo on June 2nd for Challenge Two with a file # that is earlier (#_2450) than the file (#_2500) for Challenge One?
Yes, SC would have to be looking for it for any red flag to be thrown, and you could have an alibi that you reset the numbering on your memory card, etc...
Certainly would be a lot of effort I suppose and like muckpond said "...all of this effort to win...I'd vote you get to keep it". :-) |
The algorithm you describe is valid but the reference number cannot be the file number as the camera can be set up so that a new set (starting from _0001) is created for each freshly formatted card, in fact, that is the way I prefer to number my images. Instead the shutter actuation number can be used as the reference. Such number cannot be changed, it does not show up (that I know of) in the metadata read by Photoshop but it is easily extractable with opanda.
I doubt there is any other way, besides the way you describe (but using the shutter actuation number and not the file number as a reference), to detect an inaccurately set date, but it would be interesting to hear from muckpond on this. |
SMART |
|
|
06/04/2009 05:03:10 AM · #55 |
That's all well and good on 1Dx bodies but the 5D can only have it's shutter count read by sending in to Canon :) |
|
|
06/04/2009 05:31:19 AM · #56 |
There are several methods of editing the EXIF data, but if you are that determined to win then you have bigger problems than cheating. |
|
|
06/04/2009 05:41:50 AM · #57 |
Originally posted by senor_kasper: Originally posted by glad2badad: Originally posted by yanko: I'm confused. Are you talking about the image numbers used in the file names (ex. IMG_5395.CR2)? If you entered one challenge with IMG_5395.CR2 and then next week with IMG_3192.CR2 it could just mean the photographer shot a lot between challenges. |
Example scenario:
On May 26th, 2009 you set your camera's date ahead to June 2nd, 2009 and take a photo with file # IMG_2450.CR2.
On May 27th, 2009 you set your camera's date back to May 27th, and take a photo with file # IMG_2500.CR2. You enter this photo in a challenge (call it Challenge One) with a submission date period of May 24th thru May 30th. All is fine with this photo.
On June 3rd you enter a challenge (call it Challenge Two) with the photo taken on May 26th (although it's EXIF says June 2nd) - file # IMG_2450.CR2. On the surface it looks fine as the challenge submission date period for this challenge is June 1st thru June 7th.
You're on a roll and end up in 5th place for Challenge One. Your photo is validated per request (places 1 - 5 are automatically requested). Everything is good.
Challenge Two is rolling along smoothly, then something you did in post-processing triggers a validation request. You submit the original for review. Looks fine date-wise, however, how could you take a photo on June 2nd for Challenge Two with a file # that is earlier (#_2450) than the file (#_2500) for Challenge One?
Yes, SC would have to be looking for it for any red flag to be thrown, and you could have an alibi that you reset the numbering on your memory card, etc...
Certainly would be a lot of effort I suppose and like muckpond said "...all of this effort to win...I'd vote you get to keep it". :-) |
The algorithm you describe is valid but the reference number cannot be the file number as the camera can be set up so that a new set (starting from _0001) is created for each freshly formatted card, in fact, that is the way I prefer to number my images. Instead the shutter actuation number can be used as the reference. Such number cannot be changed, it does not show up (that I know of) in the metadata read by Photoshop but it is easily extractable with opanda.
I doubt there is any other way, besides the way you describe (but using the shutter actuation number and not the file number as a reference), to detect an inaccurately set date, but it would be interesting to hear from muckpond on this. |
And if you keep the filenaming at continuous with a Canon, the highest it can go is IMG_9999 before it resets back to IMG_0001, which is what I was referring to earlier.
Message edited by author 2009-06-04 05:44:04.
|
|
|
06/04/2009 05:55:46 AM · #58 |
By the way this is the photo in question
 |
|
|
06/04/2009 08:12:02 AM · #59 |
Originally posted by senor_kasper: ... Instead the shutter actuation number can be used as the reference. Such number cannot be changed, it does not show up (that I know of) in the metadata read by Photoshop but it is easily extractable with opanda. ... |
Interesting thought / observation...not sure if the shutter actuation count is available with my two DSLR's or not. Something I think I'll follow up on if for no other reason than curiosity. :-) Thanks! |
|
|
06/04/2009 08:33:23 AM · #60 |
Originally posted by HighNooner: By the way this is the photo in question
|
With those fantastic colors it would have been a serious ribbon candidate!
Must have been tempting to submit it and see if GeneralE is bluffing :) |
|
|
06/04/2009 08:57:58 AM · #61 |
Originally posted by yanko:
And if you keep the filenaming at continuous with a Canon, the highest it can go is IMG_9999 before it resets back to IMG_0001, which is what I was referring to earlier. |
You can also change the starting image number by using a memory card for your photo shoot, that already has an old image on it. The numbering will start from that image number on the card. I have used this technique several times to ensure that when I am shooting with the two 5'Ds, the numbers will not clash and overwrite the photos.
|
|
|
06/04/2009 09:02:57 AM · #62 |
Originally posted by Judi: Originally posted by yanko:
And if you keep the filenaming at continuous with a Canon, the highest it can go is IMG_9999 before it resets back to IMG_0001, which is what I was referring to earlier. |
You can also change the starting image number by using a memory card for your photo shoot, that already has an old image on it. The numbering will start from that image number on the card. I have used this technique several times to ensure that when I am shooting with the two 5'Ds, the numbers will not clash and overwrite the photos. |
That's what they (Sony) suggest in their camera firmware update instructions. Put a card in with the last image file # on it, the next shot will increment. I know that's what you just said Judi...just wanted to say it works quite well. :-) |
|
|
06/04/2009 11:19:45 AM · #63 |
Originally posted by rrdjserv: There are several methods of editing the EXIF data, but if you are that determined to win then you have bigger problems than cheating. |
Exactly and it's all much too complicated anyway plus there's no fun in cheating win or loose. The challenge is too see if one can find something to shoot that fits in the challenge theme and in the time frame. Pulling that of is part of the fun. |
|
Home -
Challenges -
Community -
League -
Photos -
Cameras -
Lenses -
Learn -
Help -
Terms of Use -
Privacy -
Top ^
DPChallenge, and website content and design, Copyright © 2001-2025 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 08/29/2025 03:40:32 AM EDT.