Originally posted by RonHendriks1966 Same test with the K-5, 16 megapixel one * quality. This brings in one minute 238 Jpeg's, that's just under 4 fps and a datastream of 8,0 MB/s (2,0 MB average).
I've made numerous comments on the issue, starting Sep. 20 for the K-5.
My latest comment was that I only get 44 images whatever I do. The smallest possible JPGs are from lens cap shots (2 MP, 1 star) resulting in only 0.8 MByte/s datastream. All settings manual, incl. exposure and focus. Sandisk Extreme III card. As you say, K-7 streams forever.
Your 4 fps forever result most likely is from having AF.C enabled. Which is a good trick showing that the K-5 can maintain 4fps but not 7fps.
Firmware 1.01. With 1.00 it was even less.
Originally posted by Adam FYI I tried shooting at 2MP and I still got about 34 JPEGs - so I can't help but think that the camera just throws unprocessed data into the buffer.
I confirm the number for regular JPGs (it can go up for 1 star quality).
I don't think it is unprocessed data. But some buffer is still limiting things. The raw buffer size doesn't shrink with RAW+JPG so it's not final SD card data written to the buffer indeed.
Originally posted by WerTicus 1080p video is 2mp, so may as well just film at 25fps
Video is working with completely different data. Argument not applicable here.
I notice different differences between K-7 and K-5 buffer handling too which is more cumbersome for me.
If I use the remote trigger, the K-7 remains responsive after the first shot for about 8 more shots. The K-5 starts to become a bit unresponsive after the first or second shot but doesn't have the break-down after about 9 shots. That's a problem for people using a remote wireless trigger in the studio. Fortunately, the K-5 behaves just as it should (remains responsive) with direct shutter presses. So, part of the buffer processing must stall the remote receiver and I consider it a bug.
Last edited by falconeye; 11-26-2010 at 04:08 AM.