The iPhone 5s Reviewby Anand Lal Shimpi on September 17, 2013 9:01 PM EST
- Posted in
- iPhone 5S
Apple’s new H6 ISP brings with it a modernization of the video recording options for the iPhone 5s. The default video record mode is still 1080p at 30 fps, but there’s also a new 720p 120 fps “slo-mo” mode as well. In the latter, video is captured at 120 fps but optionally played back at 30 fps in order to achieve a high speed camera/slow motion effect. The result is pretty cool:
In the camera UI you can select what portions of the video you want to play back at 30 fps and what portions you want to leave at full speed. The .mov file is stored on NAND as a ~27Mbps 720p120 without any customizations, however when you share it the entire video is transcoded into a 30 fps format which preserves the slow motion effect.
The slo-mo mode is separate from the standard video recording mode, it’s the next stop on the dial in the new iOS 7 camera app. Video preview in slo-mo mode also happens at 60 fps compared to 30 fps for the standard video record and still image capture modes.
Camera preview frame rate, toggling between slo-mo and normal modes
Adding high speed camera modes to smartphones is a great step in my opinion and a wonderful use of increases in ISP and SoC performance. I would like to see Apple expose a 1080p60 mode as well. Technically 1080p60 does require slightly more bandwidth than 720p120, but I’d hope that Apple targeted both in the design of H6 and simply chose to expose 720p120 as it’s an easier feature to market.
Standard 1080p30 recording is also available:
Post Your CommentPlease log in or sign up to comment.
View All Comments
Wilco1 - Thursday, September 19, 2013 - linkThe Geekbench results are indeed skewed by AES encryption. The author claimed AES was the only benchmark where they use hardware acceleration when available. There has been a debate on fixing the weighting or to place hardware accelerated benchmarks in a separate category to avoid skewing the results. So I'm hoping a future version will fix this.
As for cross-platform benchmarking, Geekbench currently uses the default platform compiler (LLVM on iOS, GCC on Android, VC++ on Windows). So there will be compiler differences that skew results slightly. However this is also what you'd get if you built the same application for iOS and Android.
smartypnt4 - Thursday, September 19, 2013 - linkA lot of the other stuff in Geekbench seems to be fairly representative, though. Except a few of the FP ones like the blur and sharpen tests...
It surely can't be hard to have Geekbench omit those results. I think if they did that, you'd see that the A7 is roughly 50-60% faster than the A6 instead of 100% faster, but I'm not sure there. I'd have to go and do work to figure that out. Which is annoying :-)
name99 - Wednesday, September 18, 2013 - linkI'd agree with the tweaks you suggest: (improved memory controller and prefetcher, doubling of L2, larger branch predictor tables).
There is also scope for a wider CPU. Obviously the most simple-minded widening of a CPU substantially increases power, but there are ways to limit the extra power without compromising performance too much, if you are willing to spend the transistors. I think Apple is not just willing to spend the transistors, but will have them available to spend once they ditch 32-bit compatibility. At that point they can add a fourth decoder, use POWER style blocking of instructions to reduce retirement costs, and add whatever extra pipes make sense.
The most useful improvement (in my experience) would be to up the L1 from being able to handle one load+store cycle to two loads+ one store per cycle, but I don't know what the power cost of that is --- may be too high.
On the topic of minor tweaks, do we know what the page size used by iOS is? If they go from 4K to 16K and/or add support for large pages, they could get a 10% of so speed boost just from better TLB coverage.
(And what's Android's story on this front? Do they stick with standard 4K pages, or do they utilize 16 or 64K pages and/or large pages?)
extide - Wednesday, September 18, 2013 - linkThose are some pretty generous numbers you pulled out of your hat there. It's not as easy as just do this and that and bam, you have something to compete with Intel Core series stuff. No. I mean yeah, Apple has done a great job here and I wish someone else was making CPU's like this for the Android phones but oh well.
name99 - Wednesday, September 18, 2013 - link"Now, I will agree that this does prove that if Apple really wanted to, they could build something to compete with Haswell in terms of raw throughput."
I agree with your point, but I think we should consider what an astonishing statement this is.
Two years ago Apple wasn't selling it's own CPU. They burst onto the scene and with their SECOND device they're at an IPC and a performance/watt that equals Intel! Equals THE competitor in this space, the guys who are using the best process on earth.
If you don't consider that astonishing, you don't understand what has happened here.
(And once again I'd make my pitch that THIS shows what Intel's fatal flaw is. The problem with x86 is not that it adds area to a design, or that it slows it down --- though it does both. The problem is that it makes design so damn complex that you're constantly lagging; and you're terrified of making large changes because you might screw up.
Apple, saddled with only the much smaller ARM overhead, has been vastly more nimble than Intel.
And it's only going to get worse if, as I expect, Apple ditches 32-bit ARM as soon as they can, in two years or so, giving them an even easier design target...)
What's next for Apple?
At the circuit level, I expect them to work hard to make their CPU as good at turboing as Intel. (Anand talked about this.)
At the ISA level, I expect their next major target to be some form of hardware transactional memory --- it just makes life so much easier, and, even though they're at two cores today, they know as well as anyone that the future is more cores. You don't have to do TM the way Intel has done it; the solution IBM used for POWER8 is probably a better fit for ARM. And of course if Apple do this (using their own extensions, because as far as I know ARM doesn't yet even have a TM spec) it's just one more way in which they differentiate their world from the commodity ARM world.
smartypnt4 - Wednesday, September 18, 2013 - link@extide: agreed.
@name99: It is very astonishing indeed. Then again, a high profile company like Apple has no problem attracting some of the best talent via compensation and prestige.
They've still got quite a long way to match Haswell, in any case. But the throughput is technically there to rival Intel if they wanted to. I would hope that Haswell contains a much more advanced branch predictor and prefetcher than what Apple has, but you never know. My computer architecture professor always said that everything in computer architecture has already been discovered. The question now is when will it be advantageous to spend the transistors to implement the most complicated designs.
The next year is going to be very interesting, indeed.
Bob Todd - Wednesday, September 18, 2013 - linkHow many crows did you stuff down after claiming BT would be slower than A15 and even A12? Remember posting this about integer performance?
"Silverthorne < A7 < A9 < A9R4 < Silvermont < A12 < Bobcat < A15 < Jaguar"
Apple's A7 looks great, but you've made so many utterly ridiculous Intel performance bashing posts that it's pretty much impossible to take anything you say seriously.
Wilco1 - Wednesday, September 18, 2013 - linkBT has indeed far lower IPC than A15 just like I posted - pretty much all benchmark results confirm that. On Geekbench 3 A15 is 23-25% faster clock for clock on integer and FP.
The jury is still out on A12 vs BT as we've seen no performance results for A12 so far. So claiming I was wrong is not only premature but also incorrect as the fact is that Bay Trail is slower.
Wilco1 - Wednesday, September 18, 2013 - linkAlso new version with A7 and A57 now looks like this:
Silverthorne < A7 < A9 < A9R4 < Silvermont < A12 < Bobcat < A15 < Jaguar < A57 < Apple A7
Bob Todd - Wednesday, September 18, 2013 - linkCherry picking a single benchmark which is notoriously inaccurate at comparisons across platforms/architectures doesn't make you "right", it just makes you look like more of a troll. Bay Trail has better integer performance than Jaguar (at near identical base clocks), so by your own ranking above it *has* to be faster than A12 and A15.
You show up in every ARM article spouting the same drivel over and over again, yet you were mysteriously absent in the Bay Trail performance preview. Here's the link if you want to try to find a way to spin more FUD.
Apple's A7 looks great, and IT is still the powerhouse of mobile graphics. The A7 version in the iPad should be a beast. None of that makes most of your comments any less loony.