Antony Newman
Well-known member
When the 100MB UDMA7 Sandisk CF came out / the 5D2's ability to write was hampered by to Canon low level routines - which you could max out further by frigging the write thread priority. Canon released a 'driver' update with slightly larger buffers which helped a bit.
The live view has a genlock : Background YUV, foreground 8 bit palette - so you can read and display 'raw' data (and the Dryos read routine worked marginally better than write)
Real time YUV -> RGB -> dithered palette onto foreground was possible on the 5D2 .... but a bit heavy on memory.
There is an ASIC temperature sensor to allow shutdown - or stopping of CPU heavy code.
Canon had a lot of 'already working' code in the Dryos (over 19,000 subroutines) - what Alex can do from scratch in two weeks would probably take Canon's team 18 months to code and test ... and then they would have to throw away what they know 'works for the simple workflow / Use Case'.
Now ... the 5D3's DIGIC 5+ is 15-17 times faster than the 5D2 .... what couldn't you do with that sort of horsepower?
AJ
The live view has a genlock : Background YUV, foreground 8 bit palette - so you can read and display 'raw' data (and the Dryos read routine worked marginally better than write)
Real time YUV -> RGB -> dithered palette onto foreground was possible on the 5D2 .... but a bit heavy on memory.
There is an ASIC temperature sensor to allow shutdown - or stopping of CPU heavy code.
Canon had a lot of 'already working' code in the Dryos (over 19,000 subroutines) - what Alex can do from scratch in two weeks would probably take Canon's team 18 months to code and test ... and then they would have to throw away what they know 'works for the simple workflow / Use Case'.
Now ... the 5D3's DIGIC 5+ is 15-17 times faster than the 5D2 .... what couldn't you do with that sort of horsepower?
AJ