pogster wrote:
The problem with this type of communication is what you are describing and what I think you are describing can sometimes be different so my apologiies in that regard.
No worries. I agree - text-only communication can be a rather clunky experience in trying to convey complex issues without any visual or (2-way live) verbal means. I was a bit worried about being too wordy in an already wordy post and feared that it might just be ignored if it was too long. Again - I appreciate your chiming in. You seem very knowledgable in digital photography, which is exactly what I was hoping to find. 🙂
Given that my description of "bad pixels" is a bit sloppy for what is really going on, I think you understand what I mean in my usage of those words.
To answer your question, the offending pixels, or very, very small little dots of imperfections, are present in both video playback and in still photos. After shooting several test videos against neutral and textured backgrounds to see what kind of results I'd get in the appearance of the bad pixels, I also took several stills in "burst mode" using an app called "Camera-" against a wood grain background, as the woodgrain background offered the most visible and consistent view of the blemishes. In motion video, the dots (bad pixels) are pretty easy to see on a large display, or when zoomed in during playback on my iPad 2's screen. In stills, it was kind of tricky to identify them, because without the persistent motion of the background, the bad pixels almost blended in as random image noise. I was however, able to identity with certainty the same bad pixels in most of the stills. Additionally, at the higher resolution of the stills, the offending pixels almost don't even need masking or removal with photo editing software. Like I said - without the constant visible background motion to make them stand out as irregularities, or the ability to do a frame-by-frame analysis (which I can do easier with the video file using an app called VideoPix), the bad pixels are more difficult to identify.
The importance in identifying the bad pixels in stills, even though they are practically not noticeable, is that it can now be determined that the bad pixels are not the result of some kind of video coding glitch, but rather present in the hardware of the device itself - either as a defective image sensor, or defective hardware that translates the data from the image sensor into the pixels utilized by the software for photos and video.
As part of the tests I ran, I captured video with an app called KingCamera, and it, too, produced the same results. KingCamera also has an option for "locking" of the auto white balance and brightness, loosely similar to setting those manually on a higher-end, dedicated camera. Even locking the white balance and brightness, the pad pixels were present, so the potential for the issue being caused by an anomaly in the software's auto-settings management were put to rest.
In regard to being able to correct the bad pixels in stills - yep, easily done. BUT, I shouldn't need to. In terms of correcting them during video playback, that *is* actually something I could probably work out a method of doing. I used to dable in production videos that involved complex imaging filters, multiple composite video layers, and automated ways of identifying specific colors, contrast points, and patterns within images/video streams and altering them (such as cleaning up sloppy image mattes or locking in on visual patterns for the application of various video effects). Again, this is something I *shouldn't* need to do.
The still photo and video capabilities on the iPhone 4S are outstanding, in contrast to what other similar existing devices offer (arguably better than or almost as good as the best competitor offerings, depending), but the quality is not DSLR, and like I said - I'm not expecting it to be. I do expect however, and I don't think it is unreasonable to, image rendering without persistent "bad pixels" showing - even if I am only in the 1% of people who are likely to notice such image defects. They are, in fact, defects, and not "normal operation for a device of this caliber".
I was hoping there might be some trick to correct them, but I kind of figured there would not be. It seemed smart to at least reach out and see what other people may know that I might be missing. Again, I regret terribly my poor decision to return my perfectly-functioning 32 GB iPhone 4s for the 64 GB model. Knowing a little about the very intricate technologies that make these things seem "magical", I understand that there are dozens or even hundreds of very complex little components that are mostly stamped out on an assembly line of robot fabrication means, then assembled, at least in part, by humans in a factory who are required to pump out x number of these things in short periods of time. I worried about the possibility of trading in my perfectly functional device for something that may be just a tad less perfect - just because of the odds. My bad for not following my natural instincts on this one. I just didn't want to have to constantly be managing space on my device. I failed to think through my initial choice of the 32 GB model in regard to my trigger-happy photo/video nature. The cumulative files are much larger on this device than I was initially expecting (because I was just too excited to get my hands on one on October 14 and failed to do enough research and calculations). Days into owning my 32 GB 4S, I was already spending time, almost daily, re-rendering videos at 720 and 580 through iMovie, being somewhat irritated about having to replace the original videos with reduced resolution versions just to keep the videos live on my iPhone (sometimes archiving the originals on my Mac first). Anyway - enough of my rambling.
Thank you again for your input, pogster. If you have any other ideas, please share. I'm pretty sure I know what I have to do to feel happy with my investment, though. I'm just not looking forward to complaining about 3 bad pixels to a Genius Bar employee who's probably going to look at me like I'm one of those "never happy with..." people. Three bad pixels that I won't even be able to show ON the actual iPhone itself, but rather bring my iPad 2 and show zoomed-in playback of the video footage.
Message was edited by: ascii-T - fixed type-o
