Why the A99 is slower than the A77 :-)

For me as an engineer it's quite clear:

Compared to the A77 the A99 has
  • about 50% more shutter travel with 50% more mass
  • about 20% more bits, and
  • needs additional settling time for more precise measurement.
So it is no wonder that the frame rate hase reduced to the half.
 
Yes, several years ago I did some research with 250kV.
 
For me as an engineer it's quite clear:

Compared to the A77 the A99 has
  • about 50% more shutter travel with 50% more mass
  • about 20% more bits, and
  • needs additional settling time for more precise measurement.
So it is no wonder that the frame rate hase reduced to the half.
Thank you!

That is pretty much what I am trying to say about the shutter.

Now with the settling down time, are we referring to the shutter or the sensor reset time between shots?
--
Paul
 
I responded to the previous post (above).
I am working on a response to your message, so expect one coming. Today I have been very busy with other stuff.

But just so we can be sure we are on the same plane:

Where exactly in the pipeline are you thinking the bandwidth that is effecting the fps is being limited (around 300MB/s per your theory)?

Between the sensor and the processing chip?

Between the processing chip and the buffer?

Between the buffer and the memory card?
--
Paul
 
Better light sensitivity is just as critical for action photography as is the ability to deal with more frames in a short time frame. Smaller files are faster to clear/store.
I don't think that was their reason. They could have increased the buffer size.
Numbers are approximate:
D800, 75MB 14-bit RAW, at 4 FPS: 300 MB/s.
5DMkIII, 50 MB, 14-bit RAW, at 6 FPS: 300 MB/s
A99, 50MB, 14-bit RAW, at 6 FPS: 300 MB/s
A77, 24MB, 12-bit cRAW, at 12 FPS: 300 MB/s
Why are you mixing compressed RAW file sizes with uncompressed? The processing from the sensor of the A99 (42MB uncompressed, 24MB compressed) to the buffer is no different than the A77.

I do believe the new RAW files out there vary in size more than the older files. Cameras are now doing lens corrections within the body, this can cause the files size to grow dramatically. For example, the 5D MkIII will have file sizes ranging from 25MB to 50MB if DLO is enabled. But this is not occurring on the sensor nor between the sensor and the processing chip.
Can you show me a camera that does better than about 300 MB/s.
I did, the A77. The data being captured directly from the sensor is uncompressed, it isn't compressed until later. Uncompressed, the throughput is exceeding 430MB/s. We haven't even touched on RAW+JPEG which would result in more bandwidth being consumed as well as processing power.

Another camera would probably be the Canon 1D X, up to 12fps in RAW and RAW+JPEG and 14fps in JPEG only. It's RAW files uncompressed will clock in at 31.4MB and compressed at 23.2MB. Uncompressed it is hitting 376.8MB/s at 12fps.
There appears to be a lot of discrepancies between these numbers being tossed around, which is more than enough to result in dramatic differences.
What discrepancies? We have uncompressed and compressed RAW. Uncompressed RAW file sizes are pretty straight forward. That is the exact data being extracted from the sensor for every pixel. RAW will grow in size from data added by the camera (like lens corrections). By going with uncompressed RAW file size prior to this, we are showing results in a best case scenario. The bandwidth consumption can only go higher from what I stated.
PS. I wasn't aware that D800's burst mode can be increased to 6 FPS with battery grip. However, are you sure it is doing that with 14-bit uncompressed RAW?
I was wrong on this. When I was reading the information from Nikon's website, I missed that the 6fps to DX format pictures only. Still interesting how some extra juice will allow the camera to shoot faster.
Which puts us in that 300MB/s ballpark. No?
For that particular camera it is close in the best case scenario. But not for the A77 and 1D X.
300 MB/s is an approximation. However, what are the chances that A99's RAW file is not going to be larger than 42MB? The calculator is a tool good for approximation, but there can be variances. Ultimately, you're looking at a limiting transfer rate. Chances are, Sony doesn't want A99 to get bogged down with transfer either, and I'm sure it is true of others as well.
So now you are saying 300MB/s is an approximation? Then how come that approximation can't be higher? Why does it have to be lower? RAW files with the data itself coming directly from the sensor does not change much. The RAW file sizes change when the camera is adding extra data. Most, if not all, of this extra data is done past the point of the sensor to processing chip transfer.
It will be a bad idea if Sony pushed for 7 FPS on the spec sheet, only to do better than 6 FPS, but the camera's performance (turn-around) suffers as a result.
It wouldn't be the first time. Do you recall how many cameras claimed to do 'X' fps only to really be 'X - .2' fps because the manufacturer rounded up? Not saying this is a good reason, just saying it has been known to happen.
It isn't. It is why you don't see A77 with uncompressed RAW. It has cRAW helping towards that 12 FPS. And that is a 24 MB file. And we're down to 288 MB/s with that... what I call the norm in these higher end cameras.
You cannot get cRAW directly from the sensor. cRAW is a compression technique done by the processing sensor, so it is done post transfer from the sensor to the processing chip. Sony's claim, per Paul Genge of Sony UK, for no regular RAW option and masking the cRAW as RAW was due to their market studies showing that people didn't want to use cRAW when given as an option (despite the claimed no difference in quality). What they did was not give us a choice and called it RAW. Sony isn't the only company to start doing this.

So in summary, it isn't a bandwidth limitation between the sensor and the processing chip. Furthermore, if you think it is a bandwidth issue from the processing chip to the buffer then you need to think again about that. The memory used for buffer is most likely a fast DRAM memory like DDR2 or DDR3. Only a few years ago even the mid range Nikon D5100 was equipped with DDR2 800 memory to use for its buffer. DDR2 800 memory has a theoretical peak bandwidth of 6,400MB/s. You can see here in the tear down the memory it is using if you don't believe me:
http://www.ifixit.com/Teardown/Nikon-D5100-Teardown/5271/1

And that was just a middle of the road camera. You'd think they would equip higher end equipment like the D800, D4, 1D X, and A99 with RAM at least as fast (if not faster) as well as more dedicated memory.

Out of the whole pipeline that it takes to capture an image, your biggest limiting factors in frame rate will be (in order):
1) Mechanical parts such as the shutter and aperture control
2) The processing power of the processing chip
3) The controller interface from the buffer to the memory card
4) The speed of the memory card

Numbers 3 and 4 only come into effect when the buffer gets filled faster than it can dump it. But this does not effect the initial frame rate capabilities of the camera, just its consistency to maintain such a frame rate.

--
Paul
 
Here's a quote of what I wrote in a previous thread that gives an explanation to my reason/theory:
The distance a shutter needs to cover to make a complete cycle on a full frame sensor is longer than for a crop sensor or in crop mode. About 53% longer. This part is obvious.
So the time it takes for a a full frame sensor to meet 6 fps at said distance is faster than the time it would take for a shutter in crop mode to meet 6 fps for its distance.
Thus, if a shutter on a full frame sensor is clicking at 6 frames per second, for a crop sensor that same speed would account for a higher frame rate with no need to speed up the shutter. This is because the shutter has to cover less distance.
Here is some loose math in a very basic environment for ease of understanding and formulas (I know it is more complex than this). My math is assuming our "shutter" is just a single line/string, not a full frame covering multi-leaf shutter that it actually uses. Because of this assumption, the real life shutter speed would actually be much faster. But conversion in speed difference from a full frame to a crop frame should be about the same. Here it goes:
For a full frame sensor (35.8 x 23.8mm) shutter to meet 6 frames per second, it needs to travel at about 142.8 mm/s.
For a crop frame sensor (23.5 x 15.6mm) shutter to meet 6 frames per second, it needs to travel at about 93.6 mm/s. To meet 10 frames per second, it needs to travel at about 156 mm/s.
So assuming that only the cropped portion of the full frame needs to be covered by the shutter for a proper exposure, the speed of the full frame shutter does not need to change that much (if at all). So the camera could be "amping up" the shutter speed by less than .5 fps in full frame equivalent speeds to meet a 10fps crop speed. Or...since most manufacturers only document their frame rates in whole numbers, the actual full frame shutter speed could be slightly faster (maybe up to .5 fps) or the the crop mode frame rate could be slightly slower (maybe by .5 fps), or a combination of both.
With this theory in mind, I believe it is more of a shutter limitation and not a bandwidth limitation as to why crop mode can shoot at 10fps while full frame is limited to 6fps.
Sorry, but posting false information twice does not make it right, nor more right the second time around. I could not follow your logic a week ago, and it still escapes me today.

Your premise in the bold-italic quoted text is that even though the FF shutter travels over the entire FF distance at the same speed you get a faster frame rate with crop mode vs FF mode because the crop area is smaller. That is just plain wrong.

Frame rate is a measure of how many times per second the shutter mechanism executes a complete operating cycle. That includes traversing over the entire operating distance to expose the frame, and then back in preparation for the next frame. For the A99 in full frame this is 4000 rows of pixels that need to be exposed/covered but the shutter. If the shutter does 6 cycles per second, you get 6 fps, and that's all there is to it. Any single pixel only gets exposed 6 times per second.

Now by your logic, if we use a smaller portion of the sensor and keep the same traverse speed we get a higher frame rate? I mean, think about it, what sort of frame rate would you get if the crop area were only 10 rows of pixels instead of 4000? Would you get 4000 / 10 x 6 = 2400 frames per second? With the shutter traveling at the same linear speed??? I would agree that with a cropped sensor the image is "painted" in less time because it takes the shutter less time to cover the shorter distance, but the shutter still has to complete its full traverse over the FF and return.

You dismissed the suggestion a week ago that the frame rate could be increased if, using the same shutter traverse speed, the traverse distance were shorter; i.e., limited to the number of pixel rows of the crop area. But that is, in fact, the only way to make the mechanism cycle faster -- decrease the distance the shutter has to travel at its fixed speed, thereby allowing the camera to begin the shutter reset action sooner. (I may be wrong here, but I suspect shutters are spring loaded in the forward direction, and motor or solenoid driven in the reset phase of the cycle.) As was suggested, this would likely complicate the shutter design, and I suspect this is not implemented in practice.

If it were in fact implemented, or if you compare a FF camera with an APS-C camera where traverse speeds of the shutter blades are the same, then you will get higher frame rates with the smaller size sensor. Of course, the ratio of frame rates would not be linearly related to the ratio of the frame sizes because the traverse time during the exposure phase is only a portion of the total shutter cycle duration.

For a FF camera where a faster frame rate can be selected with a crop of the FF, the maximum frame rate is determined largely by the lesser of a) the maximum cycle speed of the shutter mechanism; and b) the maximum rate at which the data from the sensor can be read out to memory. I suspect the mechanicals of the A99 shutter can give you 10 fps max, and that is available in crop mode where less sensor data is being read to memory. When reading the FF sensor, frame rate is limited by the data readout speed, and the shutter is delayed slightly before each cycle to match the readout speed of 6 fps. But the shutter still travels over the sensor at the same rate.

So, shutter traverse speed is likely fixed by the spring tension; shutter release frequency is adjusted to match data readout rate (lower frequency of shutter tripping with FF); and of course "shutter speed" (frame exposure time) is set by the time delay between front and rear curtain, even if using electronic front curtain.

JF
 
Unless A77 has cRAW instead of RAW (uncompressed) in which case you're looking at about 24MB out of A77 but 42MB out of A99. For that matter, the 16 MP sensor in my A55 should get 24 MB RAW (12-bit) per the calculator but we're talking cRAW in that case as well (RAW is 16 MB).
I apologize in advance if I am a bit short with you on this message. I had a nice long, well thought out message written up and my laptop decided to reboot on me with no chance to save. Now I have to start all over.

First I would like to say that I was wrong on the D4 and D800 file sizes. They are actually larger than I specified. The D800 is 74.4MB, not 68.3MB. Compressed it is 35.9MB. The D4 is 34.3MB, not 28.3MB. Compressed it is 17MB. Nikon must be putting some extra data into those files to have them blow up so much larger than I calculated.

Now back to my response to you:

Yes the A77's final output is cRAW, which is 24MB. But almost all of Sony's camera's today are cRAW in some share or form. But the actual RAW data from the sensor is around 36MB worth of data.

But I feel that the uncompressed image size is the best to base our calculations on bandwidth since this is the data that is being captured directly from the sensor and has to be converted to a compressed format before reaching the buffer. I thought we were concerned about the bandwidth from the sensor/chip to the buffer since that is ultimately what effects your frame rate. The buffer and its bandwidth to the memory card only effects how many pictures you can take at a given frame rate before slowing to a crawl. So I find that part irrelevant since that is not what we are talking about. We are talking about the reason why the A99 is capped at 6fps.

But just for giggles, let's crunch the numbers with compressed file sizes.

The A77 at 12fps with 24MB files would be eating around 288MB/s.
The D800 at 6fps with 35.9MB files would consume around 215.4MB/s.
The D4 at 11fps with 17MB files totals around 187MB/s.

Now for the A99. I looked at some RAW files from this camera and, surprisingly, they are also 24MB (just like the A77). This makes it obvious that Sony is using their cRAW as their RAW again. So figuring this in at 6fps, we would be consuming only 144MB/s.

So after seeing all four cameras, we see that if considering that compressed files are what's eating the bandwidth then we do stay under the 300MB/s theoretical ceiling you keep floating. But then if that is the case, then why are these full frame cameras so slow with their frame rate? Clearly then, it shouldn't be bandwidth. None of them come close to 300MB/s. Only the A77 comes close at 288MB/s.

By going by this idea of a 300MB/s limit, then the A99 should also be capable of around 12fps. The D800 should be around 8fps and the D4 around 17fps. But this isn't the case.

So clearly it shouldn't be the bandwidth that is holding these cameras back if we are going by compressed RAW files. Otherwise, why would the A77 (the cheapest of all listed) have the highest throughput capability? Why would Nikon and Sony cheap out on their most expensive cameras by only designing them with a bandwidth throughput of 1/2 to 2/3 of what a camera that is a fraction of the cost is capable of.

Could it be that a mechanical part, the shutter in this case, can be the main limiting factor for these cameras final frame rate speed?

That's how it is looking to me.
--
Paul
There is one reason for this. This is the a99v... v undoubtably stands for video. Sony will shortly bring out a a99p which will be optimized for still shooting probably clock in at 12fps and have a much deeper buffer. Maybe will be 24 or 36mp.

Why? Perhaps to keep costs down but more likely because they need something fresh to sell.

Personally I hated the a99 at first because it had so many cobbled together components from the a77. But the more I look at its design the more I appreciate it. I just hope it has proper blinkies not squished down into the histogram screen thumbnail and that its sensor has similar performance to the d600
 
There is one reason for this. This is the a99v... v undoubtably stands for video. Sony will shortly bring out a a99p which will be optimized for still shooting probably clock in at 12fps and have a much deeper buffer. Maybe will be 24 or 36mp.

Why? Perhaps to keep costs down but more likely because they need something fresh to sell.

Personally I hated the a99 at first because it had so many cobbled together components from the a77. But the more I look at its design the more I appreciate it. I just hope it has proper blinkies not squished down into the histogram screen thumbnail and that its sensor has similar performance to the d600
You asked this similar question months ago about the A77.

The 'V' is just a designation that Sony uses to declare which body has GPS and which one does not. 'V' = GPS, no 'V' = no GPS. Any other letter will designate which lens kit was bundled with the camera such as 'Q' or 'K'.
--
Paul
 
Switching the sensor cell to the ADC causes some transient voltage swinging. And if you want to measure more exactly (14 bits instead of 12) you have to wait longer until this transient effect is settled.
 
Sorry, but posting false information twice does not make it right, nor more right the second time around. I could not follow your logic a week ago, and it still escapes me today.

Your premise in the bold-italic quoted text is that even though the FF shutter travels over the entire FF distance at the same speed you get a faster frame rate with crop mode vs FF mode because the crop area is smaller. That is just plain wrong.

Frame rate is a measure of how many times per second the shutter mechanism executes a complete operating cycle. That includes traversing over the entire operating distance to expose the frame, and then back in preparation for the next frame. For the A99 in full frame this is 4000 rows of pixels that need to be exposed/covered but the shutter. If the shutter does 6 cycles per second, you get 6 fps, and that's all there is to it. Any single pixel only gets exposed 6 times per second.

Now by your logic, if we use a smaller portion of the sensor and keep the same traverse speed we get a higher frame rate? I mean, think about it, what sort of frame rate would you get if the crop area were only 10 rows of pixels instead of 4000? Would you get 4000 / 10 x 6 = 2400 frames per second? With the shutter traveling at the same linear speed??? I would agree that with a cropped sensor the image is "painted" in less time because it takes the shutter less time to cover the shorter distance, but the shutter still has to complete its full traverse over the FF and return.

You dismissed the suggestion a week ago that the frame rate could be increased if, using the same shutter traverse speed, the traverse distance were shorter; i.e., limited to the number of pixel rows of the crop area. But that is, in fact, the only way to make the mechanism cycle faster -- decrease the distance the shutter has to travel at its fixed speed, thereby allowing the camera to begin the shutter reset action sooner. (I may be wrong here, but I suspect shutters are spring loaded in the forward direction, and motor or solenoid driven in the reset phase of the cycle.) As was suggested, this would likely complicate the shutter design, and I suspect this is not implemented in practice.

If it were in fact implemented, or if you compare a FF camera with an APS-C camera where traverse speeds of the shutter blades are the same, then you will get higher frame rates with the smaller size sensor. Of course, the ratio of frame rates would not be linearly related to the ratio of the frame sizes because the traverse time during the exposure phase is only a portion of the total shutter cycle duration.

For a FF camera where a faster frame rate can be selected with a crop of the FF, the maximum frame rate is determined largely by the lesser of a) the maximum cycle speed of the shutter mechanism; and b) the maximum rate at which the data from the sensor can be read out to memory. I suspect the mechanicals of the A99 shutter can give you 10 fps max, and that is available in crop mode where less sensor data is being read to memory. When reading the FF sensor, frame rate is limited by the data readout speed, and the shutter is delayed slightly before each cycle to match the readout speed of 6 fps. But the shutter still travels over the sensor at the same rate.

So, shutter traverse speed is likely fixed by the spring tension; shutter release frequency is adjusted to match data readout rate (lower frequency of shutter tripping with FF); and of course "shutter speed" (frame exposure time) is set by the time delay between front and rear curtain, even if using electronic front curtain.

JF
1) It is my theory, I never stated it as fact. It is a theory that I have been digging for more information on until I can get to a fact. I am learning more and more as these discussions evolve, thus my theory has been evolving as people contribute more and more to it.

2) Since it is a theory, it is only wrong if disproven. And so far, nobody has decided to explain to me how the shutter is actually working in crop mode. So, I am still not wrong in the sense that it hasn't been disproven. It is still in the form of an agreeable or disagreeable idea.

Now, did you read the full conversation from the other forum?

If you did you will see that I did not flat out dismiss that the shutter could be working at a shorter distance in crop mode, ie, half-cocked. Initially, there was a misunderstanding between me and the other contributor on exactly what we were referring to as a different design of the shutter mechanism. I think there may have been a bit of a communication issue or my blurry eyed late nights doing too much reading (maybe a combination of both).

The shutter is most likely tied to a spring tension of some sort, but I think the motor can also control the speed on top of that in both opening and closing.

We were in that forum talking about many different ideas, like if it is possible for the camera to capture an image in both the falling action and the rising, reset action. Another idea was that in crop mode the reset action of the shutter is quicker but the falling action remains the same speed as it would on the full frame since the velocity of a shutter on a full frame in a downward action at 6fps is equal to the velocity of a shutter on a cropped sensor in a downward action.

I would love to be able to find some video of a DSLR running in its high speed mode in full frame mode and then again in its cropped mode to be able to see the difference in action of how the shutter is working. But I am having trouble finding this. Plus, there are not many cameras that have a faster crop mode and most of them are mirrored SLRs. Because of this, the videos are few and the ones that are out there the mirror gets in the way in between shots.
--
Paul
 
I responded to the previous post (above).
I am working on a response to your message, so expect one coming. Today I have been very busy with other stuff.

But just so we can be sure we are on the same plane:

Where exactly in the pipeline are you thinking the bandwidth that is effecting the fps is being limited (around 300MB/s per your theory)?

Between the sensor and the processing chip?

Between the processing chip and the buffer?

Between the buffer and the memory card?
--
Paul
Through out. Do you think data rate is a non-issue?
 
Paul,

Disagreements often arise out of misunderstanding, and perhaps we have misunderstood each other on some fine points. I tried pulling this apart point by point and reassembling it so that we might see eye to eye, but the discussion was getting far too long. A better approach might be to clarify some high level concepts; we could get into the weeds later if you like.

Let's start with your statement near the end of your post where you said:
So assuming that only the cropped portion of the full frame needs to be covered by the shutter for a proper exposure, the speed of the full frame shutter does not need to change that much (if at all).
In a follow-up post (in the original thread) you responded to altendky's suggestion (that your theory only works if the FF shutter travels a restricted distance) by saying:
Why would you need to design the shutter to travel two different distances?
A crop mode resides within the center of a full frame and covers less area. The larger shutter distance will cover the crop mode area just as well. Since there is less distance that has to be covered during the shutters travel to black out the crop mode area, the full frame shutter's traveling speed at 6fps would be equivalent to a faster fps for the crop mode with little to no increase done to the shutter motor.
I took from these statements that you believe a FF shutter traveling the full-frame 23.8 mm vertical distance during 6 fps burst operation will magically provide a faster equivalent frame rate on a crop area of 15.6 mm vertical distance with no increase in traverse speed. Read your statements again -- they really imply that a shutter operating at 6 fps can give higher (10?) fps simply by selecting crop mode on the sensor.

Is that what you were saying, or did I misinterpret?

The only way to get a higher frame rate is to increase the number of full-cycle operations of the shutter each second. Period. (Or is this just my theory that you might some day disprove? -- Sorry, I just could not resist this little dig ;-) )

Now, there are a number of ways to reduce the cycle time of the shutter that include speeding up traverse times (and re-cocking times), and reducing the traverse distance so the next cycle can start sooner, neither of which you say are necessary simply because the vertical crop area is smaller.

Respectfully,
JF
 
I responded to the previous post (above).
I am working on a response to your message, so expect one coming. Today I have been very busy with other stuff.

But just so we can be sure we are on the same plane:

Where exactly in the pipeline are you thinking the bandwidth that is effecting the fps is being limited (around 300MB/s per your theory)?

Between the sensor and the processing chip?

Between the processing chip and the buffer?

Between the buffer and the memory card?
--
Paul
Through out. Do you think data rate is a non-issue?
If it is throughout from beginning to end, then it isn't a limitation than it is more so by design, wouldn't you say? ;)

With how far technology has come today, data rate (to me) is really only an issue between the controller of the memory buffer and the memory card. Since memory cards are flash based memory that needs to keep data stored even when power is not being supplied and the buffer is RAM based memory that requires a power source to retain data, flash based memory today is still very limited in speed in comparison to RAM based memory. But this doesn't effect frame rate potential, only consistency.

Now where we can hit a snag in performance, thus frame rate, is the processing power of the processing chip. That can slow things down if it isn't beefy enough.
--
Paul
 
If it is throughout from beginning to end, then it isn't a limitation than it is more so by design, wouldn't you say? ;)
No, it is an engineering limitation. If you have limited capacity for how fast data can move and clear, you can't really do anything about it, until the technology advances further.
With how far technology has come today, data rate (to me) is really only an issue between the controller of the memory buffer and the memory card.
Technological improvements will continue as data size also increases.
 
If it is throughout from beginning to end, then it isn't a limitation than it is more so by design, wouldn't you say? ;)
No, it is an engineering limitation. If you have limited capacity for how fast data can move and clear, you can't really do anything about it, until the technology advances further.
No, it is a budget limitation then. The technology and engineering know how is already out there. The question is can they afford to implement it within the price range they wish to sell the camera at. Thus, it if is limited by budget and not the limitations of what technology has to offer us today then it is by design.
With how far technology has come today, data rate (to me) is really only an issue between the controller of the memory buffer and the memory card.
Technological improvements will continue as data size also increases.
That is a given, but the data size and the complexity of the file sizes in this camera versus say the A900 hasn't really grown to the point that it should bring the processing chip to its knees or saturate the bus. The processing chip has advanced just as much, if not more, than the sensor has (when looking at resolution and A/D conversion). The resolution of the A99 is slightly lower than the A900 but the bit depth has grown by about 17% to 14-bit from 12-bit. Frame rate has only Increased by 1fps.

Has our advancements in the technology to improve the processing chip really grown so little in the past 4 years that a camera is hampered by a bandwidth consumption increase of 17% per image?

Yet they manage to squeak out a 140% improvement (when compared to the A900) in frame rate on the A77 whose file sizes, bit depth, and resolution have a lot in common with the A900 (with exception to the physical size of the sensor).

I am not saying the A99 should be able to do 12fps, but if it was bandwidth and processing we were talking about, you would think they should be able to get 8-10 fps out of it. 10fps being the amount of bandwidth it would approximately consume to match about what the A77 would consume at 12fps, again considering Raw files only and not Raw+Jpeg.

I do have some ideas as to some potential limitations that can hold back the processing chip if it has to pool it's resources instead of each task having dedicated resources, but I will save them for a later date. It is getting late, I am out of town, and I have a crying baby to attend to.
--
Paul
 
No, it is a budget limitation then. The technology and engineering know how is already out there...
Unlimited data transfer rate? Show me, at any price.
 

Keyboard shortcuts

Back
Top