canonfuture said:...
- 64-bit processing picture (much higher performance that anything Canon has today)
...
Could you please elaborate on this....
Upvote
0
canonfuture said:...
- 64-bit processing picture (much higher performance that anything Canon has today)
...
canonfuture said:One way that could be called modular is for Canon to do the following:
Make a DSLR that could dock an iPhone 6 in the back.
The best way would be to use a bracket that could be exchanged if you wanted to upgrade to a phone with a different form factor. Maybe reminding of the different data backs Canon used a while ago. As long as the main interface is the same (i e Thunderbolt) it would be quite easy to upgrade the phone.Lee Jay said:canonfuture said:One way that could be called modular is for Canon to do the following:
Make a DSLR that could dock an iPhone 6 in the back.
I assume this is so the camera is obsolete and useless within 2 years?
The raw computing power of the hardware is higher (A8 processor vs Dual Digic 6)(I am comparing iPhone 6 to 7D Mk II). Apple are doing some things with images they don´t say but some things are official:Diko said:canonfuture said:...
- 64-bit processing picture (much higher performance that anything Canon has today)
...
Could you please elaborate on this....
Several of the advantages would be applicable with an Android phone too...Khnnielsen said:canonfuture said:One way that could be called modular is for Canon to do the following:
Make a DSLR that could dock an iPhone 6 in the back.
I might be biased because I am an andriod user, but no offense - this might be the worst idea, I have heard in a long time.
"Market leader" is irrelevant. The question is: Who has and makes the most money to put into processor/hardware and software development? Who has the best economy-of-scale regarding this? - I know it´s not Canon or Nikon or Sony...Kevin B said:canonfuture said:One way that could be called modular is for Canon to do the following:
Make a DSLR that could dock an iPhone 6 in the back.
This would guarantee me switching to Nikon or Sony.
I'm always amazed how Apple users think everyone should use an iPhone when Apple isn't even the market leader in smart phones.
Khnnielsen said:It reminds me a bit of the A7s, where you can attach an audio module via the hotshoe, which is a really cool idea that I would like Canon to do as well.
canonfuture said:The best way would be to use a bracket that could be exchanged if you wanted to upgrade to a phone with a different form factor. Maybe reminding of the different data backs Canon used a while ago. As long as the main interface is the same (i e Thunderbolt) it would be quite easy to upgrade the phone.
dgatwood said:That functionality would be better as part of an optional oversized battery grip. Having a stack of XLR cables hanging off the top of your camera would be unwieldy.Khnnielsen said:It reminds me a bit of the A7s, where you can attach an audio module via the hotshoe, which is a really cool idea that I would like Canon to do as well.
canonfuture said:The raw computing power of the hardware is higher (A8 processor vs Dual Digic 6)(I am comparing iPhone 6 to 7D Mk II). Apple are doing some things with images they don´t say but some things are official:Diko said:canonfuture said:...
- 64-bit processing picture (much higher performance that anything Canon has today)
...
Could you please elaborate on this....
- Tone matching flash
- HDR photo
- HDR video
- Slo-mo video (120 fps or 240 fps)
- Time-lapse video
- Cinematic video stabilization
- Continuous autofocus video
- Take still photos while recording video
Some things are more speculative:
- Picture stabilization using motion coprocessor together with gyros and accelerometers
- Near realtime composites of 4 separate photos to decrease noise and increase sharpness
I would argue that the A8 is a better platform for further improvements in picture processing and it is easier for Apple to propagate these improvements with the normal system upgrades.
Added to that is the immense number of post editing software that runs on the phone...not much of that on Canon...
Apple only states that the Lightning-CABLE supports USB2. Regarding the hardware limitations on the phone we can only speculate... my own belief is that Apple could quite easily implement USB3 (or another higher-speed interface) in their Lightning-connector - if they wanted to... (I base this belief on the level of performance the other hardware has in iPhone 6...)dgatwood said:Khnnielsen said:It reminds me a bit of the A7s, where you can attach an audio module via the hotshoe, which is a really cool idea that I would like Canon to do as well.
That functionality would be better as part of an optional oversized battery grip. Having a stack of XLR cables hanging off the top of your camera would be unwieldy.
canonfuture said:The best way would be to use a bracket that could be exchanged if you wanted to upgrade to a phone with a different form factor. Maybe reminding of the different data backs Canon used a while ago. As long as the main interface is the same (i e Thunderbolt) it would be quite easy to upgrade the phone.
In the best case scenario, on iOS, you would be limited to USB 2.0 speeds (the maximum speed supported by the hardware). At CR2 sizes, that's less than 2 fps maximum shooting speed. And I'm not certain whether you could even achieve those rates. I'd expect the same limitation on Android.
Of course, if you use in-camera storage and only transmit a low-quality image during previewing, it could still be viable, but it would be less than ideal, and the software side would be relatively complex.
No, it would make a lot more sense to just build Android (or iOS, ostensibly) into the device itself. As tempting as it would be to be able to have a dockable camera, the performance limitations imposed by USB 2.0 make it very unlikely that you'd see any practical benefits when compared with just adding Wi-Fi to the camera itself (which is how Sony designed their dockable, incidentally). By contrast, if Canon built Android (or iOS) into the device itself, they could easily provide an SDK for camera control so third-party vendors can extend the device's camera features, and the media would be accessible in the same way that any other media is accessible, which would be a much more practical approach than providing a complicated library with a giant pile of custom views that load different data from the camera based on zoom setting and a complicated back-end piece in the camera to generate that data.