This article is highly recommended for programmers and people interested in shooting video.
As of iOS 7 beta 2, the built-in Camera application can't make use of the extra pixels of the sensor when zooming. Only custom-written, third-party apps currently can do that. Hopefully Apple fixes Camera in the final version of iOS 7; before that, should you want to use zooming while shooting video, avoid using the Camera app and make sure you write or install an iOS 7-specific video recorder application for best results.
Many of my readers have asked for a complete elaboration on the brand new zooming features of iOS 7, both in the stock Camera application and the programmatic API support (AVCaptureDevice.videoZoomFactor and the related, highly useful properties AVCaptureDevice.activeFormat.videoZoomFactorUpscaleThreshold and AVCaptureDevice.activeFormat.videoMaxZoomFactor).
This article is intended for readers suffering from the narrow field-of-view of iPhones starting with the iPhone 4 and for programmers offering any kind of video recording in their apps.
As you may know already, recent iDevices use image stabilization during video recording. Unfortunately, not even the latest-and-greatest iPhone 5 has optical stabilization, only electronic, unlike the Nokia Lumia 92x. This, unfortunately, means part of the sensor is used for the stabilization itself, further narrowing the already limited field-of-view (FOV). I recommend you watch engadget's iPhone 5 vs. Nokia Lumia 920 videos so you can see how immensely better optical stabilization is.
This article is meant for advanced users and programmers. However, non-techies can easily understand the generic tips and trick sections.
Answering a question from the Macrumors forum, I've made some serious tests to find out how you can best record the contents of the iPhone 5's screen if:
- you don't want to purchase an HDMI recorder so you can use the HDMI adapter
- you need true pixel-by-pixel mirroring
This article is solely targeted at people who want to mirror the image of their iDevice onto an external TV, projector, or streaming service and have jailbroken their iDevice. You'll learn a lot of practical tips and tricks never before published by anyone else.
With the advent of real-time game video streaming services like Twitch.tv in addition to traditional ones like YouTube live streaming, outputting or streaming the contents of the iDevice's screen became even more important. In addition to the standard mirroring available on all A5 CPU-based iDevices (and, with some tweaking, on A4-based ones too), Cydia-based ($3.99) DisplayOut (DO for short) has always been the most preferred solution. In this tutorial, I directly compare it to the stock mirroring readily available in all new devices announced in 2011 or later.
First, let me quickly list the pros and cons of DO.
This article is meant for advanced users and programmers.
Today, I've started investigating the CPU usage of the software decoders of the iOS multimedia players I'm reviewing for my forthcoming iOS Multimedia bible. (Of which the work-in-progress feature & benchmark measurements chart, in OpenOffice format, is already public. It's quite a bit messed up (again, it's a chart I'm actively working on) but you may already find answers to even your most unique questions.) For this, I've reviewed all the CPU measurement techniques available on iOS – a very important parameter of the players if you want to have as good battery life and low device temperature as possible. (There may be huge differences in the efficiency between even custom audio – for example, OGG or WMA – decoders, let alone video ones.)
This article will be useful for anyone planning to display the output of Keynote on an external screen. I've clearly marked sections meant for advanced users or ones with jailbroken devices; they can be safely skipped by other users. This article contains a lot of information on video/TV output in general and the multitasking/backgrounding JB tweaks, which may also be of interest to readers who aren't Keynote users.
Apple's Keynote app ($9.99) is by far the most widely used iOS application to play back presentations. In this writeup, I present you with a complete discussion of everything related to displaying its contents on an external screen or projector (from now on, for brevity, I'll call TV).
This article contains highly technical information tailored to hardcore geeks/engineers. However, section “2. Which one to go for?” is digestable for beginners.
I haven't been able to find any reliable information on the internet about the image quality, speed, and scaling differences of the two 30-pin HDMI adapters: the first-generation MC953ZM/A (model number A1388) and the second-generation MD098ZM/A (A1422) one. The only information I could gather on the differences were the news items reporting the release of the new adapter.
As I know quite a bit about both video theory, processing, and iOS programming, plus have the necessary hardware to properly assess HDMI image quality and speed, I found it necessary to come up with an in-depth article on the differences.
The following article is for people using any kind of external display with their iDevices, and for programmers who would like to provide as good of external display output in their apps as possible.
People have a lot of misconceptions regarding Tv output from iDevices; most importantly regarding the black borders on the left and right sides of the external image and also on the top and bottom. As an engineer well versed in video technology, engineering, and iOS programming, I found it necessary to get the facts right in a manner digestable for advanced iOS users (and all programmers).
While I don't really consider it one of the best players out there, the generic multimedia player CineXPlayer is still pretty popular with folks. This is why I'm constantly asked by my readers to review the updated versions whenever they come out. While I do not recommend this player over nPlayer or AVPlayerHD, only check it out if you can/want to make use of its Dolby Digital features, built-in Web browser, or TV station directory. As a standalone video player, it's considerably weaker than nPlayer or AVPlayerHD.
Note that there are two versions of the app, both called HD. There is only a one-character difference between their names: the iPad-only version (AppStore link; $3.99) is called “CineXPlayer HD – The best way to enjoy your movies” (with a hyphen), while the iPhone/iPod touch version (AppStore link; $1.99) is named “CineXPlayer HD = The best way to enjoy your movies” (with an equation mark instead of the hyphen).
This article targets advanced users who would like to play back MKV video files off SMB networking shares; that is, without copying them on their iDevices first.
Over at MacRumors (original question & answer), I've been asked to elaborate on the current state of SMB + MKV support on iOS.