Re: *ist D Anomalies
As any software designer/programmer knows, the user can always find a way to
beat the system!
John Coyle
Brisbane, Australia
- Original Message -
From: "Tom C" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 12, 2004 1:43 AM
Subject: Re: *ist D Anomalies
It's interesting (I have close to 25 years in software
design/development).
I wonder if I was triggering a bug. I was impatient to get the next shot
and so occassionally would go spastic on the shutter release, hoping to
fire it as soon as the camera would allow. Maybe this rejected input
caused the software to branch unexpectedly and caused the mode to
internally change to .jpg.
Tom C.
From: "Larry Levy" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: Re: *ist D Anomalies
Date: Thu, 11 Nov 2004 08:57:43 -0600
Sounds like the typical computer engineer solution - reboot the system.
This could easily be a software problem. Try to keep track of what was
happening when the camera ('s computer) got stuck. This information
enables you to:
1 - Possibly avoid those situations in the future
2 - Provide the data to Pentax so that they can take corrective action for
release in later versions of the software
For some strange reason, we all (including me) expect software to always
work the way the designers and programmers intended it to. Always is a
long time.
Larry in Dallas (with over 3 decades of system design)
Re: *ist D Anomalies
Ahh yes. The dangers of actually meeting another PDML member in the flesh. ;) Tom C. Heh, heh...You're way sharper than I thought you were! Phaff. William Robb
Re: *ist D Anomalies
- Original Message - From: "Keith Whaley" Subject: Re: *ist D Anomalies Heh, heh...You're way sharper than I thought you were! Phaff. William Robb
Re: *ist D Anomalies
Tom C wrote: Yeah it was me. I saw you ignoring the "DONT WALK" and decided you were a deviant. :) Heh, heh...You're way sharper than I thought you were! Good onya! keith Tom C. Hey! You know, I think I saw you at an intersection the other day, feverishly pressing the "WALK" button at least 100 times a minute. I suppose I should have stopped and said hello... keith whaley Tom C.
Re: *ist D Anomalies
Yeah it was me. I saw you ignoring the "DONT WALK" and decided you were a deviant. :) Tom C. Hey! You know, I think I saw you at an intersection the other day, feverishly pressing the "WALK" button at least 100 times a minute. I suppose I should have stopped and said hello... keith whaley Tom C.
Re: *ist D Anomalies
Tom C wrote: It's interesting (I have close to 25 years in software design/development). I wonder if I was triggering a bug. I was impatient to get the next shot and so occassionally would go spastic on the shutter release, hoping to fire it as soon as the camera would allow. Maybe this rejected input caused the software to branch unexpectedly and caused the mode to internally change to .jpg. Hey! You know, I think I saw you at an intersection the other day, feverishly pressing the "WALK" button at least 100 times a minute. I suppose I should have stopped and said hello... keith whaley Tom C. From: "Larry Levy" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: <[EMAIL PROTECTED]> Subject: Re: *ist D Anomalies Date: Thu, 11 Nov 2004 08:57:43 -0600 Sounds like the typical computer engineer solution - reboot the system. [...]
Re: *ist D Anomalies
It's interesting (I have close to 25 years in software design/development).
I wonder if I was triggering a bug. I was impatient to get the next shot
and so occassionally would go spastic on the shutter release, hoping to fire
it as soon as the camera would allow. Maybe this rejected input caused the
software to branch unexpectedly and caused the mode to internally change to
.jpg.
Tom C.
From: "Larry Levy" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: Re: *ist D Anomalies
Date: Thu, 11 Nov 2004 08:57:43 -0600
Sounds like the typical computer engineer solution - reboot the system.
This could easily be a software problem. Try to keep track of what was
happening when the camera ('s computer) got stuck. This information enables
you to:
1 - Possibly avoid those situations in the future
2 - Provide the data to Pentax so that they can take corrective action for
release in later versions of the software
For some strange reason, we all (including me) expect software to always
work the way the designers and programmers intended it to. Always is a long
time.
Larry in Dallas (with over 3 decades of system design)
Re: *ist D Anomalies
On Thu, 11 Nov 2004, Peter Loveday wrote:
As another note, every time I've had my *istD do something odd, (...)
Half the time, re-inserting the same batteries will fix it
On Thu, 11 Nov 2004, Anders Hultman replied:
Yesterday my *istD did a quite odd thing. It got stuck. The display
continued to show what it previuosly was showing, even if I turned it off
or rotated the mode dial. Quite fresh batteries. Taking them out and
re-inserting them solved it.
Sounds like the typical computer engineer solution - reboot the system.
This could easily be a software problem. Try to keep track of what was
happening when the camera ('s computer) got stuck. This information enables
you to:
1 - Possibly avoid those situations in the future
2 - Provide the data to Pentax so that they can take corrective action for
release in later versions of the software
For some strange reason, we all (including me) expect software to always
work the way the designers and programmers intended it to. Always is a long
time.
Larry in Dallas (with over 3 decades of system design)
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.788 / Virus Database: 533 - Release Date: 11/2/2004
Re: *ist D Anomalies
On Thu, 11 Nov 2004, Peter Loveday wrote: > As another note, every time I've had my *istD do something odd, (...) > Half the time, re-inserting the same batteries will fix it Yesterday my *istD did a quite odd thing. It got stuck. The display continued to show what it previuosly was showing, even if I turned it off or rotated the mode dial. Quite fresh batteries. Taking them out and re-inserting tehm solved it. anders - http://anders.hultman.nu/ med dagens bild och allt!
Re: *ist D Anomalies
The noise reduction starts to kick in at 1/2s, so you won't notice it in normal shots since it ain't there. Sam - Original Message - From: "Tom C" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 10, 2004 11:41 PM Subject: Re: *ist D Anomalies Thanks. I can't remember if noise reduction was on or off. Probably on... are you indicating that possibly because of the type of shot (night shots) that there is more work to do with noise reduction than a typical daylight shot?... because I haven't changed any modes, noise reduction or file format. Tom C. If you have noise reduction turned on, it is making a second dark exposure after the first one, then subtracting the noise from the first one. This is very buffer and time intensive. As far as making a jpeg instead of a tiff, not a clue. William Robb
Re: *ist D Anomalies
- Original Message - From: "Tom C" Thanks. I can't remember if noise reduction was on or off. Probably on... are you indicating that possibly because of the type of shot (night shots) that there is more work to do with noise reduction than a typical daylight shot?... because I haven't changed any modes, noise reduction or file format. I think NR is on by default, though I could be wrong. It's in one of the set up menus. It kicks in automatically at about 1/4 second exposure if activated. William Robb
Re: *ist D Anomalies
Thanks. I can't remember if noise reduction was on or off. Probably on... are you indicating that possibly because of the type of shot (night shots) that there is more work to do with noise reduction than a typical daylight shot?... because I haven't changed any modes, noise reduction or file format. Noise reduction only kicks in on "long" exposures (I'm not sure offhand what this is, the manual may say, but I doubt it :) As another note, every time I've had my *istD do something odd, like not fire the shutter or something really weird like only fire once I release the button and then not properly, its been due to flat batteries. Sometimes the batteries have been fine until I swap lenses too, either the drain is significantly different, or its something physical... it doesn't happen a lot, but fresh batteries always fix it. Half the time, re-inserting the same batteries will fix it Its battery indicator is not one of its strong points... Love, Light and Peace, - Peter Loveday Director of Development, eyeon Software
RE: *ist D Anomalies
Noise reduction is only active at slower speeds. Not sure what speed it kicks in at but I've seen much longer write times below 1/4 second. Don > -Original Message- > From: Tom C [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 10, 2004 4:42 PM > To: [EMAIL PROTECTED] > Subject: Re: *ist D Anomalies > > > Thanks. I can't remember if noise reduction was on or off. > Probably on... > are you indicating that possibly because of the type of shot > (night shots) > that there is more work to do with noise reduction than a typical > daylight > shot?... because I haven't changed any modes, noise reduction or file > format. > > > > Tom C. > > > > >If you have noise reduction turned on, it is making a second > dark exposure > >after the first one, then subtracting the noise from the first > one. This is > >very buffer and time intensive. > >As far as making a jpeg instead of a tiff, not a clue. > > > >William Robb > > > > > >
Re: *ist D Anomalies
Thanks. I can't remember if noise reduction was on or off. Probably on... are you indicating that possibly because of the type of shot (night shots) that there is more work to do with noise reduction than a typical daylight shot?... because I haven't changed any modes, noise reduction or file format. Tom C. If you have noise reduction turned on, it is making a second dark exposure after the first one, then subtracting the noise from the first one. This is very buffer and time intensive. As far as making a jpeg instead of a tiff, not a clue. William Robb
Re: *ist D Anomalies
- Original Message - From: "Tom C" Subject: *ist D Anomalies When I was out shooting several nights ago in (B)ulb mode, the *ist D began acting oddly. Not sure if there's something I'm missing or if this is indeed something to be concerned about. 1. I could not trigger the shutter a 2nd time until the buffer had been *almost* completely emptied from the previous single exposure. In other words, I couldn't load the buffer with 5/6 shots and then wait, I had to wait after every shot. I was shooting TIF's. 2. While the orange busy light was on, I could not fire the shutter... except it seemed sometimes I could, as long as I had waited a significantly long time. When I downloaded my images, I found that a handful had been recorded as .jpgs instead of .tifs. The capture mode was never changed via the control dials to .jpg. It's almost as if the camera, thought it did not have the room for a .tif, so it shot a .jpg instead (hard to believe). If you have noise reduction turned on, it is making a second dark exposure after the first one, then subtracting the noise from the first one. This is very buffer and time intensive. As far as making a jpeg instead of a tiff, not a clue. William Robb
