Archive for the ‘Red’ Category

Red vs. Arri: Cars or Workstations

The most controversial thing about Red has always been pricing, and the implications that pricing has for industry politics. So let’s talk about pricing, its long term implications, and Red’s power as a disruptive industry force. In particular, I’d like to focus on what impact Red’s entry into the market might be expected to have on existing digital cinema camera vendors. And I’m mostly going to pick on Arri, which is actually a bit of a complement, because second to what Red is doing (and, at the lower end, what’s happening with the video-enabled dSLRs), Arri’s upcoming A-EV cameras are the most interesting products in the industry right now, as far as I can see.

For the sake of context, these new Arri cameras begin at around $70K.

The Car Analogy

Over in this thread on Red user (which is of general interest to anyone concerned with this topic), another poster (I don’t want to use names without permission) suggested that perhaps we shouldn’t expect Red to have too much influence on Arri’s market. Arri has positioned itself as a high-end brand, and sells to customers with the money to afford its products. Red has much more aggressive pricing, and sells largely to the low-budget market, moving a lot more units. The poster compares the companies to Mercedes and Hyundai, respectively, and makes the case that once you’ve established your brand downmarket, it’s hard to move up; how many people would buy a luxury-model Hyundai, if Hyundai decided to make such a thing?

This initially seems plausible, but… is the car analogy really the right model? Cars are a basically mature technology, with differentiation mostly based on aesthetics, brand marketing, and non-functional frills like fancy interiors. Digital cinema cameras, in contrast, are in extremely active development. There are real technical differences between them and there are real improvements from year to year. In fact, the whole shape of the market is still in flux, as demonstrated by the fact that over the last couple of years, Red appears to have sold some thousands of units to people who were previously not in the digital cinema camera market at all, but in the ENG or prosumer camera markets.

Image not to Scale

Maybe instead of Hyundai vs. Mercedes, we’re looking at Mac and Windows NT desktops vs. SGI workstations in the late ’90s. Yeah, remember Silicon Graphics? They made expensive specialized hardware for a small customer base. They were good at it. I’m sure they told themselves the same things the high-end vendors are telling themselves now. “Our customers have a lot of money, and they want the best, and there will always be a market for that.”

They got completely trashed by the rise of commodity hardware. Completely. Trashed.

Why? Because it turns out there are massive economies of scale with most technology products, both for R&D and actual physical production. If the other guy is selling 50x as many units as you are (or in SGI’s case hundreds or thousands of times as many units), it might well be the case that you can’t make a better product even if you charge 10x as much for every unit.

Is this going to happen with digital cinematography cameras? Well… we won’t really know until someone shoots them side by side, but by the numbers Red’s new $7K camera body looks like it might actually produce a better image than Arri’s new ~$70K camera body. So that’s something to consider.

Coasting… off a cliff?

There are a lot of snobs in this industry, and enough subjectivity that they’ll be able to go on justifying the use more expensive gear even if it doesn’t really work any better. That will let some vendors basically ignore Red for a while. Maybe years.

But I think eventually, if for no other reason than that workforce turnover will fill the industry with people who came up using the cheap/powerful stuff, it will be “change or die” time. Companies like Arri need to decide whether they want to get out ahead of the market on this, or try to hold onto the existing high price/low volume model for as long as possible. The latter approach (which is, unfortunately, the direction companies most often decide to take in situations like this) will mean that when these vendors do eventually try to make the transition, Red will already be firmly entrenched in the market they’re trying to move into.

Bayer Market

(This post is based on a recent post of mine from RedUser.)

There’s a lot of counterproductive elitism in the film world, and one of the silliest examples of it is that right around the time the Red One started shipping (this is pure coincidence, I’m sure), some people suddenly decided that Bayer pattern sensors (see Wikipedia article if you’re not familiar) like the ones used in Red cameras are somehow unacceptable for motion imaging.

This, of course, has essentially no basis in reality.

Bayer is virtually the only technology used in the stills world these days, from the cheapest consumer cameras to the most expensive large format digital backs. Bayer sensors are used by probably tens of thousands of pro photographers every day to shoot images that sometimes get blown up to billboard size, and as stills, tend to be examined with far more scrutiny than individual frames in a moving sequence ever will be. And yet somehow, Bayer has been presented by some people in the motion imaging world as some sort of weakness for the Red One, as if Red is somehow cheating.

The truth is, Bayer is so widely used because for a given photosite count, with proper processing, it delivers a better image than anything else. Three chip designs or striped sensor patterns deliver at best 20-25% more visible resolution using 300% more photosites; in many cases it would make much more sense to just build a higher resolution Bayer sensor.

The real reason why Bayer isn’t already widely deployed for high-end motion imaging is not that it’s somehow unacceptable for that purpose, but that high-quality Bayer processing is very computationally intensive. The Red One gets around this by recording a raw image, so this computation doesn’t have to happen in real time — but as the RED Rocket and the 1080p RGB recording modes on the new cameras demonstrate, it is now possible to build ASICs which can do such processing in real time, which allows Bayer sensors to be used even in workflows that require high-quality live output.

I expect that as a result of this, we’ll see large Bayer sensors increasingly become the dominant technology in high-end motion imaging, just as they have in the stills world. Arri’s new cameras all use them. (Though whether this will clue in the industry snobs is anyone’s guess. A friend of mine was having a chat with someone at an LA rental house a few days ago who explained they’d be buying into Arri’s new system rather than Red’s because “The Red uses a Bayer sensor, and is really only a 2K camera”, apparently completely unaware that the Arri cameras are also Bayer, and Red’s S35 cameras are 5K to Arri’s 3.5K.)

Update: David Newman of CineForm points out that processing Bayer images isn’t necessarily that computationally intensive, and that most of the computational overhead of working with Red footage is associated with the compression, not the debayer process. I wonder what implications this will have for the RGB recording modes on the new cameras. If most of the complexity is in the compression rather than the debayer, playing back Redcode RGB footage might actually be more taxing than playing back raw footage currently is, which I think is contrary to what most people expect.

Red October

So, I’m sure everyone has seen Red’s new announcements about the Epic X rollout and other plans by now.

As existing Red One owners, we’re pretty happy, though it’s going to be hard to decide whether to upgrade in Stage II or Stage III — as I see it, upgrading in Stage II basically means getting to keep your Red One body for an extra $9000. But if the previously announced price on the S35 Scarlet holds up, that will be only $7000 and if you don’t need anamorphic, speed ramping, or frame rates about 72 fps, will otherwise be a better camera that’s part of the new modular system and so can share accessories with the Epic X better. Our decision will probably come down to timing; it’s unclear at this point how much of a time gap there will be between Stage II and Stage III.

Epic vs. Red One size

See here. According to this post from Jarred, that little thing has “EVF/LCD output plus CF recording via the side CF module, HD-SDI out, HDMI out, 2 channels of Balanced Mic Audio in + 48v Phantom power, Headphone out, Power in, RS-242, Genlock/GPIO, all on the Brain itself.”

Absolutely incredible.

Incidentally, sorry about things being a little slow lately here at Indie4K. There hasn’t been a huge amount of Red-related news since Final Cut Studio 3. The good news is, things seem to be heating up again.

We’re also about to head into production on a round of our own short projects (we’re shooting the first of them next week) which I can actually post interesting stuff about (unlike most of the projects we work on for other people), and I expect some interesting blog material to come out of that.

New Final Cut Studio Rundown

Release Scope

So, this isn’t the huge rewrite some have been expecting. As noted here, this doesn’t even seem to be Final Cut Studio 3; Apple is just calling it “The new Final Cut Studio” everywhere.

Update: Hmm… except in a couple of the screencasts they do call if FCS3. Which suggests this branding decision may have been last-minute.

That major rewire is undoubtably still coming; when Apple axed 64-bit Carbon they implicitly committed themselves to eventually rewriting Final Cut (their last major mostly-Carbon app, other than iTunes), but it looks like that will have to wait for the next version. The good news is, the fact that Apple isn’t calling this FCS3 might very well mean that we won’t have to wait two full years for that next release. I’d assume that, if this is just an interim update, they’ve been working on the larger release in parallel with it. Perhaps next year?

Notable Features

As I see it, there are basically five features of major significance to Red users here.

ProRes 4444 – A new 320 Mb (40 MB/s) variant of ProRes that supports 4:4:4 chroma sampling and full-resolution alpha channels. You can sort of think of this as being to DPX what ProRes 4:2:2 was to uncompressed HD: a format that makes minor compromises to quality, when compared with uncompressed material, in exchange for footage that’s vastly easier to work with. Testing will, of course, be required, but it’s possible this might be a plausible — and very convenient — finishing format for indie projects, perhaps even indie features.

4K support in Color — Not much explanation required here.

Better R3D Support — Final Cut still can’t (as far as I can tell) edit R3D files natively. But it looks like you can now use CinemaTools to manage the relationship between ProRes proxies and R3D files, and more easily move from a Final Cut timeline using the former to a Color project using the latter.

Generally better Color/Final Cut integration — Not applicable solely to Red workflow, of course, but it looks like a lot of work has been done to make Color smarter about dealing with complex Final Cut timelines. It should no longer get confused with speed changes, stills, and other things that currently confuse the hell out of Color.

Automatic importing of file-based recording media — It looks like Final Cut can now detect when a drive or card is mounted, and start automatically importing media from it. There also seem to be some new features for retaining more metadata from imported file-based media, but it’s not clear if that applies to R3D files.

Cheaper Color control surface options — Again, not Red-specific, but Color now supports the ~$1800 Tangent Wave control surface, among others, lowering the price barrier to using a control surface to about 1/5th of of where it was previously.

Blu-ray & the future

Apparently, DVD Studio Pro still doesn’t support actual Blu-ray authoring. What we have instead is sort of strange and, I think, rather telling. Compressor can encode Blu-ray compatable H.264 now, and create Blu-ray discs using pre-built Apple menu templates. These templates are apparently in some sort of XML format, so anyone comfortable with a bit of XML slinging can build their own. I have a sneaking suspicion that what we’re looking at here is an early version of the file format of a new application that will eventually replace DVD Studio Pro.

More as I discover it.