| Author | Thread |
|
|
10/08/2005 01:17:40 AM · #1 |
Some may dismiss this as an immediate stupid question but I come from the computer industry where everything can be hacked and over-clocked.
My D100 can do about 1.5-2 fps with about 4-6 shots in a row. The buffer seems so limited considering the general quality of the rest of the camera, is there a way to add to the buffer memory or speed up the processor. These are not (as far as I know) dealt with in firmware updates but I wonder if there are other methods. It'd be really nice to be able to take more than 6 images without having to stop and wait for the buffer to clear.
Thanks. |
|
|
|
10/08/2005 01:35:26 AM · #2 |
unfortunately not.. the best way is to upgrade the camera, not a pleasent option i know, I just got the D2H(6 months ago) that can shoot 8 pics/sec and hold 40jpg or 25RAW in its buffer and the clear time is so fast you can start shooting the next lot after about 1 second. its AMAZINGLY fast, but im gonna sell it and buy a D2X because I no longer require the speed.
|
|
|
|
10/08/2005 01:37:07 AM · #3 |
I'm sure you "could" do it, but to do so would probably be a more expensive proposition that buying a new camera, not to mention a HUGE hassle. And thats if you have the technical know-how and at least some crude directions to follow for such a hack.
But, honestly, I don't know where you could even find a crude set of directions. Others have surely explored the possibilities available along that path, but I have never heard of such a thing. |
|
|
|
10/08/2005 07:38:02 AM · #4 |
i don't think it is possible -
mainly because (i believe) it is hard coded in the firmware or is a pipeline issue withthe processor (hey the camera is 2002 model ;)
(too low bandwidth between the sensor -> compression engine -> memory card)
I.E. you are still limited to 4-6 frames in 'basic' (low compression) jpg mode WITH the cap on (black frames which should be small size in comressed bytes)
|
|
|
|
10/08/2005 08:17:15 AM · #5 |
The main reason that this sort of camera hacking isnt done more often is simply the lack of availability of replacement components, and no real publication of the inner workings of these machines. If you manage to get hold of a service manual you might learn a lot, but i doubt you'd be able to find a replacement processor even if you could easily replace it with a bit of soldering. Besides, you're talking about some of the most major components of the camera - aside from the sensor, they would constitute the majority of the body's cost anyway.
|
|
|
|
10/08/2005 08:18:30 AM · #6 |
Originally posted by ralphnev:
I.E. you are still limited to 4-6 frames in 'basic' (low compression) jpg mode WITH the cap on (black frames which should be small size in comressed bytes) |
Actually i reckon that would take the most compression, as you'd get a lot of low noise. If you want to take small images, massively overexpose a white surface in manual mode instead.
|
|
|
|
10/08/2005 09:06:24 AM · #7 |
Originally posted by riot:
Originally posted by ralphnev:
I.E. you are still limited to 4-6 frames in 'basic' (low compression) jpg mode WITH the cap on (black frames which should be small size in comressed bytes) |
Actually i reckon that would take the most compression, as you'd get a lot of low noise. If you want to take small images, massively overexpose a white surface in manual mode instead. |
about equiv.
- you are loading the system with 0(black) as opposed to 255(white) -
compression doesn't care - as long as the bits are all the same (if you could find a 'perfect' 18%gray would work as well )
you get noise at both ends of the spectrum - white/black
the biggest hidrence would be stuck pixels & hot pixels which mess up the file
i picked black because it was a easy experiment -
if you wish - set the camera on Manual for 1sec at f2.8 or f4 and point it outside in day light but that won't help in a speed test ...
ok - quickie experiment -- iso 200 3008x2000 frame with 'basic' jpg compression
white 1sec f3 124k bytes
black 1/2000 sec f3 134kbytes (fair amount of noise)
buffer still hangs at 6 images(very short since the files are so small) then drops down to ~1 frame/sec but since there is no content in he images (black) the delay is short
|
|
|
|
10/08/2005 09:11:42 AM · #8 |
Originally posted by ralphnev:
Originally posted by riot:
Originally posted by ralphnev:
I.E. you are still limited to 4-6 frames in 'basic' (low compression) jpg mode WITH the cap on (black frames which should be small size in comressed bytes) |
Actually i reckon that would take the most compression, as you'd get a lot of low noise. If you want to take small images, massively overexpose a white surface in manual mode instead. |
about equiv.
- you are loading the system with 0(black) as opposed to 255(white) -
compression doesn't care - as long as the bits are all the same (if you could find a 'perfect' 18%gray would work as well )
you get noise at both ends of the spectrum - white/black
the biggest hidrence would be stuck pixels & hot pixels which mess up the file
|
I still disagree. At black there will be the same noise as at grey, but it will be more significant (as they will be the brightest parts of the image) and the jpeg encoder WILL encode the noise with as much detail as possible. On a ccd, noise is mainly thermal and electrostatic - i.e., it can only be positive. Noise will only manifest by random brightening of pixels, not darkening. So at white, when the sensor maxes out, there is absolutely zero noise (unless the sensor is that bad that it introduces significant noise by signal loss along the bucket brigade between capture and processing).
Also, if you're exposing for long enough to make hot pixels, you're hardly helping the speed test either :P
|
|
|
|
10/08/2005 10:17:56 AM · #9 |
I could be wrong, but I think fps may have something to do with the ability to write the information...I know that on the rebel, when it buffers a photo, it buffers the whole RAW file, to clear it from the buffer, it takes the RAW, converts it, THEN writes it to the memory card...which is why it cannot capture that many fps. The d70 is different, it processes quickly, then tosses it in the buffer. (The rebel 350xt may do the same thing now also I don't know).
|
|
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: 09/11/2025 11:57:58 PM EDT.
