Categories
Apple Pro Apps Interesting Technology The Technology of Production Video Technology

Why Final Cut Pro specific cameras?

At the MacWorld Final Cut Pro User Group Supermeet on Wednesday night (Jan 7th) JVC announced two new ProHD camcorders. The 1/4″ progressive sensor 3-CCD compact (prosumer form factor) GY-HM100 and the shoulder mounted 1/3″ sensor GY-HM700.

There are a couple of things that make these two cameras interesting. They record in QuickTime native format ready for native editing in FCP. No import, no conversion – just copy and edit (or edit off the card). They also use SDHC compact memory cards instead of expensive proprietary formats. Both cameras have two card slots and with two 32 GB cards, can record up to 6 hours continuously for just a couple of hundred dollars.

You can read up on the rest of the specs but there are three points I’d want to make.

As far as I know this is the first camcorder made specifically for Final Cut Pro. While there have been some earlier attempts to make Avid-friendly camcorders, they didn’t hit it off in the marketplace. Clearly JVC see Final Cut Pro as a big enough market, with at least 1 million unique registered users (and probably twice that if unauthorized copies are counted) to justify doing a specific camcorder.

Secondly, increased use of SDHC. As well as these two new cameras the AVCHD/AVCCAM (Panasonic HMC-150) use compact flash as does the Red One camera. These are multi-vendor, non-proprietary formats that are readily available up to 32 GB. Take that P2 and SxS media! Of course, all these sources use compressed video of some format.

The third point is the most interesting one. JVC acknowledge that the camera does 720P at 19 or 35 Mbit/sec; 1080i at 25 Mbit/sec (aka HDV) and 1080P at 35 Mbit/sec using an “Enhanced MPEG2 Long GOP Encoder”. Traditionally ProHD has been working within the HDV specifications but there is no 35 Mbit/sec spec for HDV, particularly not one that’s already supported by Final Cut Pro. It appears that JVC are using Sony’s XDCAM EX format or something very like it, for these two new cameras.

This is not the first time JVC has worked with the Sony format. Back in September 2008 JVC announced support for XDCAM EX media and created a version for 720P licensed from Sony, which only supports 1080 in XDCAM EX.

Increasingly, Sony’s XDCAM EX format – at 35 Mbit/sec – is the grown up version of HDV.

Categories
Assisted Editing

Additional First Cuts documentation

Logging

More logging is good up to a point. I learned that you don’t overload story keywords as the same clips keep coming up in many edits, often not so successfully. So my advice now would be to keep the story keywords for each clip to the minimum that really describe the clip’s value to the story.  Initially I tended to load on any possible story keyword I could think of but as we got First Cuts closer to finished, and with the ability to selectively add as many story keywords as you want, I can really make the decisions of what I want to include on a much more fine-grained basis that way.

That multiple select also means I don’t have to be overly anal about always using the same keyword. It’s obvious when I’m building an edit that “Austria” and “Austrian” will probably both be included together or excluded together. Ditto “McDonald School” and “McDonald College” both refer to the same place – where my subject was “discovered”. In my examples there are many inconsistencies among story keywords.

Names and locations do have to match. Variations will be considered to be different people. We use the name to fill in lower third titles and to avoid jump cuts. Likewise location needs to match. Again it’s used to avoid jump cuts. Fortunately, FCP makes it easy to be consistent with these fields. After entering a name, for example, you can right-click (control click) into any other name field and pick the existing entries from the list. For Name and Location this makes entering the metadata very fast, and very accurate. It’s not like you have to type them twice.

The same trick works with entering Event and Theme log notes but I’ll come back to that.

How many clips are necessary?

The challenge is that First Cuts doesn’t do so well with small numbers of clips. You’d probably want to give it at least 20 A-roll or A+ and a similar number of b-roll options to start seeing how it can generate multiple different editions quickly and interactively. With small numbers of clips the results tend to all end up very similar – pushing duration can force variation though.

With small numbers of clips, you might get the optimal results by doing a quick A-roll (aka ‘radio’) cut and using Finisher to complete the job.

What should I do with the clips from which I made thought sized subclips for A-roll? Should they be deleted or can they be left without description?

My recommendation would be to move source or master clips to their own Bin or Bins within a single “masters” bin. Then when you export the XML file select all Bins *except* that master bin of masters. That will leave them out of consideration by First Cuts, because First Cuts doesn’t ever get them.

Tip: If you’re cutting a master clip down to though-sized subclips, enter as much metadata as you can – name, location, maybe event or theme – to the master clip first. Then the subclips will all inherit the common log notes and only need their individual variations entered.

Same for B-roll. If I leave the master clips in the bins will First Cuts use them?

If clips are included in the XML export then First Cuts will attempt to use them.  Excluding Bin or Bins from the export to XML would be my current recommended practice. It’s a fairly simple matter to select all in the Browser, then Command click (that’s the Apple key) on the Bins you want to exclude. Then Export XML. FCP will only export what was selected.

Is there a minimum length of A-roll needed?

As a consequence of this question being asked, First Cuts was changed. There is no minimum duration required for any story keyword. However, if there is insufficient A-roll First Cuts will do what it can with it, but it won’t necessarily be useful. Experiment.

Is there a minimum proportion required of B-roll to A-roll?

No there is no minimal proportion of B-roll to A-roll. You can send no b-roll and it will still do the best possible job on an A-roll edit.

In fact one of the benefits I’ve noticed with First Cuts is that it makes it really clear where there’s no b-roll coverage on a subject, because First Cuts will place as much b-roll as possible (within certain guidelines so people get face time) That’s another benefit that’s hard to put into a user guide or marketing pitch, but it’s really useful.

Events or Themes confuse me. In the manual you refer to story arc which implies that they are in part about position in time within the development of plot. But I am unclear if changing the numbering of the events has an impact on the sequences generated by FC. It seems that order is affected by the choices made in the Story Keywords Selected panel.

There are many things that affect the way the story evolves in First Cuts. Story keywords are important in determining what will be included in the edit, but the actual sequencing within the story arc is affected by a Events or Themes and some other minor factors. Truth is, the Serendipity algorithm at the heart of First Cuts is now so complex that neither Greg nor I totally understand exactly how results evolve. Greg can trace a particular example and determine the decision making process behind why a particular clip is included, but to trace out how a particular edit evolved would probably take days. Both Story Keywords and Events and Themes interact to determine the story arc of a particular edit.

But I do understand your confusion on Events or Themes. It was another of those concepts that evolved over development. Originally only Events it was supposed to be a way to bring together clips around a particular events within the documentary. The project I used during development is the story of a young singer (dancer, actor) from Sydney called Tim Draxl. The documentary covers his early career and into his first CD and performance deals, before he got movie roles.  So, my Events and Themes look like this (there are 20 in total, I haven’t included all)

010 Growing Up and Family

020 Master Class

035 Tim the person

040 Beginning Career

055 Tim’s Talent at Cabaret

100 Tim’s Future

060 Recording in LA

075 Performing and Audiences

065 Developing Career

and so on.  The numbers give chronology to the overall story arc and a way to group or associate ideas as material is logged.

The Events and Themes can really be whatever you want. Events was originally intended to group content around the events that occurred during the documentary production. In Tim’s case “Recording in LA” was  a discrete event, as was “Cabaret Convention” “Sound of Music”. But as we went on in development I found I wanted to use the same mechanism to group other than events – what eventually became themes. Often the numbering is fairly arbitrary. Probably 00 to 99 is enough. I start with themes or events on the 10’s so that I have slots between if I decide (as I did) that I wanted to put the theme “Tim the person” between the Master Class and Beginning Career. It seemed to fit there. But I could just as easily renumber it to fit between Recording in LA and Developing Career by changing the number to 063, for example.

Keep the questions coming – they help us improve the documentation and/or the software.

Categories
Apple Pro Apps Interesting Technology

Assisted Editing – the beginning

I originally wrote this to a friend over the weekend and I thought that, with a bit of an edit, it might be interesting to some others.

Last week we released two new pieces of software through my long-time company, Intelligent Assistance, Inc: First Cuts and Finisher. Collectively we call the category “Assisted Editing” because they, well, assist the editor and going with Assistant Editor was getting confusing.

What I think makes this so exciting is that it’s the first real innovation in editing since Non-Linear Editing was popularized with the release of Avid’s Media Composer version 1, 19 years ago. 19 years is a long time in the computer business. Non-Linear Editing has certainly developed since that first release of Media Composer. Then 160 x 120 16 gray images were the “state of the art” while now we effortlessly manipulate High Definition (and beyond) images in our systems. But, despite this development, the way NLE systems work today is much the same as they did 20 years ago.

What Media Composer did, was to make the “cost” (time, effort, expense) of an edit much more affordable. With linear editing bays, making small changes to, or alternate versions, of a program was difficult (read expensive). Non-linear dropped the cost of a change, revision or alternate edit dramatically. Assisted Editing achieves similar dramatic cost reductions by allowing the computer (and specifically our software) to do some of the work of the editor.

Back at NAB in April we announced “The Assistant Editor” for long form documentary editing. After three months of beta testing we have now released that application as “First Cuts”. First Cuts (for Final Cut Pro right now but we’re exploring other platforms) take the log notes made by a documentary editor (or their assistant) and turns them into very, very fast first cuts. This allows editors and producers to explore the stories that are available in the material, and to juxtapose different versions while they seek inspiration and direction.

First Cuts take the log notes that long-form documentary editors have traditionally made (and their workflow) and makes them much more useful. The logged clips are exported from FCP as XML and opened in First Cuts, where the editor chooses opening title and lower third template (Motion templates preferred), the duration and story keywords that will be used for this edit. Within seconds it creates an edit with beginning, middle and end to the story arc, with opening title placeholder and fully finished Lower Third titles used appropriately to identify speakers on camera. The edit will also have b-roll used appropriately and the audio on the b-roll is lowered in volume and faded in and out. It’s an edit a producer or finance person can watch without being distracted by jump cuts or lack of visual interest from the absent b-roll. You can see the process in a quick five minute tour at the First Cuts home page.

First Cuts is primarily focused on long form documentary editors because they have the discipline to enter log notes (if they don’t they will have a very hard time of it) and because they need to explore a lot of material. The payback is significant. Fortunately there are a lot of documentary editors working with Final Cut Pro.

We discovered that one way of working with First Cuts would be to find a cut that was close to what was desired, and then the skilled editor would add the polish, trim and emotion that a first cut lacks. In doing that we discovered that blowing away the b-roll and titles was the cleanest workflow. Since that removes a lot of the time saving, we decided to make a product that restores that finishing effort. Hence, Finisher.

Finisher takes a project with an edited a-roll sequence (aka “radio edit”) and adds Lower Third titles and b-roll as above. This is the perfect bookend product to First Cuts.

But we worked out that we could do a lot more with Finisher for those who don’t want/need to enter a lot of log notes. Finisher will work with any of the log notes that are provided for First Cuts, but does not require them. In fact Finisher can randomly choose b-roll to place in a Sequence. Location of b-roll can be forced with Sequence Markers, so obvious jump cuts are covered first. While it can run with random selection it will use b-roll search terms in the comment field of those Sequence Markers and search for matching b-roll if available.

You can see some examples of Finisher’s work, including a guided tour that shows a couple of different ways it can work, at the Finisher home page. Particularly interesting is the final example – ‘Ode to the Beach’ – because that is a simple audio recording, some b-roll pulled out of my stock collection from Final Cut Server, and Finisher adds b-roll to the cut (with Sequence Markers) randomly. The result – for almost zero effort – is quite acceptable and may even be useful in some situations.

Not too shabby for a version 1 product.

Categories
Assisted Editing

First Cuts and Finisher released tonight

At the Los Angeles Final Cut Pro User Group this evening we announced the availability of two products: First Cuts for FCP and Finisher for FCP.

The Assistant Editor product demonstrated at NAB 2008 was renamed “First Cuts for FCP” to better reflect its main function. “Finisher for FCP” was shown publicly for the first time tonight, and came about from conversations with users in the beta program for The Assistant Editor. It’s a tool that does the same finishing work that was done by The Assistant Editor: finding b-roll, lowering the b-roll volume, building and placing lower third titles, fade-in and fade-out of lower thirds… There’s more details about Finisher for FCP at its product page: http://www.theassistanteditor.com/Finisher/.

Since Finisher would be incredibly useful for editors doing many changes to a sequence produced by First Cuts, we’ve included the Finisher product in First Cuts. And, for the first three weeks after launch, we’re offering discounted pricing on both these new products!

Categories
Apple Interesting Technology

QuickTime X???

Boy, it’s dusty in here!! Been busy with lots of things, including just this week releasing The Hd Survival Handbook, but there was one thing from WWDC that caught my eye.

Using media technology pioneered in OS X iPhone™, Snow Leopard introduces QuickTime X, which optimizes support for modern audio and video formats resulting in extremely efficient media playback. Snow Leopard also includes Safari® with the fastest implementation of JavaScript ever, increasing performance by 53 percent, making Web 2.0 applications feel more responsive.*

Now, I’m surprised at myself for even bothering to attempt to second guess Apple by hypothesizing wildly, but that doesn’t stop my friend James Gardiner so it won’t stop me!

There are few clues and most of my usual sources are cold. There’s the rub, anyone who has Snow Leopard is under NDA and won’t talk. Anyone who is talking is guessing – we should keep that in mind.

Tim Robertson hopes that “modern codec support” would include .AVI, which is funny because .AVI has not been developed since being abandoned by Microsoft in 1996 – 12 years ago, just after QuickTime was introduced! James Gardiner thinks it might be a Flash/Silverlight competitor. Who knows they could be right as we’re all guessing wildly.

In Apple’s world “Modern codec support” means H.264 in .mp4 wrappers, and just maybe H.264 in .mov wrappers but that’s depricated as they say. (You can still use it but it’s not the recommended method.) Apple have totally moved away from all the rich interactive features that attracted me to the technology in the first place. (Much of what was added to Flash 9, was available in QT3 but never pushed by Apple.)

Then there’s this on Apple’s Snow Leopard page

Using media technology pioneered in OS X iPhone…

The media playback support on iPhone is very basic: H.264 video, AAC audio, MPEG-4 Simple Profile video, mp3 in .mp4 containers with limited support for .mov playback of those codecs. That’s it. A simplified form of media player with none of the older codecs not supported by MPEG-4. None of the wired sprite features, no VT objects or panoramas. A simple, lightweight media player that developers can draw on. (I should note that Flash Player and Adobe Media Player now support those exact same codecs.)

Looking also at what Apple have been doing with Javascript, and knowing there’s already limited Javascript support in QuickTime, my further guess is that QT X will be very open to Javascript, Apple’s new favorite browser language thanks to Sproutcore and the new Webkit Javascript engineSquirelfish. It’s interesting that Apple announced QuickTime X and the new Javascript engine for Safari in Snow Leopard in the same paragraph. Other features went into separate paragraphs.

So my guess is that QuickTime X is a newly optimized media player engine with hooks to good Javascript for interactive programming. Perhaps even to Ruby/Ruby on Rails since Apple’s also adopting that.

But who knows for sure? Only those who can’t tell.

Categories
Distribution Interesting Technology Video Technology

Little boxes, on the set top, little boxes full of ticky tacky!

So, Netflix and LG announce yet another set top box. Well, actually they announced that LG would include the Netflix service on “selected devices”. Best guesses are that the service will be added to a dual mode (HD DVD and Blu-ray) player, or even the Television itself.

Here’s the problem with this: it’s Netflix on LG devices and only Netflix. No slight on Netflix, the service is good and the company needs to provide for a non-disc future. However, the industry should be gathering together for a single standard for delivering from the Interent to the lounge room, not proprietary deals with single suppliers. If we want movies from Apple then it’s another set top box (Apple TV). Vudu have their own movie service and their own proprietary box. Tivo is a little more open – it has an API for programmers – but it’s still another box on top of the cable or satellite box you’ll probably still have.

We need a single standard or interoperable standards for delivery of “Internet TV” to Televisions. It has to be simple. TV would not have caught on if we’d needed separate Television sets for CBS, NBC and ABC – but that’s exactly where these companies think we’re heading.

It won’t work. Any device(s) that link the Internet sources with a TV are good, but it needs an open standard – perhaps that’s what google are working on, but even then it won’t help integrate with cable or satellite boxes unless those providers have a significant change of heart.

Apple TV, for all the people who claim it to be a “failure” is the leading device to connect computers and televisions. While its sales are disappointing by Apple’s mega-hit standard, it’s estimated to have about 800,000 units sold in 10 months (took Tivo 4 years to get that far) and it’s way ahead of the competitors, other than Xbox or PS3 which both act at media extenders.

My mantra for 2008 – proprietary bad, open standards (even from one company) good.

Categories
Apple Apple Pro Apps Video Technology

ProRes 422 Explained

One of the currently popular memes is the “wisdom of the crowds” and if by crowd we mean a lot of people then there’s a lot of wisdom at CreativeCOW.net. Trouble is, it’s spread across a whole bunch of their forums so it takes a smart writer to take that wisdom and filter it down into something much more useful.

Well, the Cow’s Tim Wilson has done just that in two excellent articles:

Apple’s ProRes 4:2:2 Codec, Part 1 and
Apple’s ProRes 4:2;2 Codec, with a splash of Color, Part 2.

Highly recommended and well worth the read.

Categories
Video Technology

Want more information on Sony’s NAB releases?

With Sony appearing to have a format for any market segment, DV User in the UK have done a great job in bringing it all together in a comprehensive article.

Categories
Apple Pro Apps Interesting Technology

XML Article at kenstone.net

Ken Stone has released an article I wrote on XML in the Final Cut Studio. The article is What is XML and what does it mean for Final Cut Studio users?

Also, Steve Douglas reviewed my company’s Pro Apps Tips, also at KenStone.net in the Pro Apps Tips Review.

Just thought you’d like to know. Oh, and in 2007, I’ll be posting more regularly as I evolve some of the thoughts around a book I’m working on, tentatively titled “Television 3.0”.

Categories
Business & Marketing Interesting Technology

Why Revver Gets it

For those who don’t know Revver.com, at the simplest level it’s “yet another video sharing site” except it has two distinct differences: it has a revenue model based on advertising and it’s entirely driven by an API. Why are these distinctions important? They’re important because they essentially mean that Revver.com itself is irrelevant to their business.

Most “Web 2.0” websites are built on advertising support – Google Adsense at the simplest level, display advertising if they have an advertising sales force or by sponsorship. YouTube tried the latter – sponsorship of channels by the large content providers, or even “The Brittney Channel” and to are working on recognizing content and sharing revenue from advertising on the same page with the large conglomerates that own the content. Neither are innovative and both require the visitor to actually be on YouTube.com to see the advertising. Trouble is, one of YouTube’s greatest appeals is the embedded player which puts the content on another site (where the site owner could display ads and collect the revenue).

The use of embedded players or more commonly RSS driven technology is a problem for site owners looking to advertising-on-the-website models. As RSS becomes more widely adopted (because of the huge value add to subscribers) that tension increases. A site like creativecow.net or 2-pop.com requires visitors to be at the site to read their forums, tutorials or other content because that’s what pays the sites’ expenses and provides a return to the owners. This is a huge problem for content creators if podcasts/video podcasts, which are RSS driven, takes off.

If RSS/embedded players become successful, as they inevitably will because they provide the biggest payoff to the user/viewer, then the website becomes irrelevant, even dead. That’s why Revver’s model shows they understand the direction the web is taking. Revver provides a very comprehensive API so anyone can set up a full Revver.com clone, or customize content out of Revver’s collection to a subject-specific site. Revver.com is built on the same API and (with few exceptions) anything Revver can do on their own site, can be done on any site, without any “permissions” required from Revver.

This is because Revver serves up ads at the end of the video. The revenue from the ads is shared with affiliates (anyone using the API to drive traffic) who get 20% and the balance is split between Revver and the content provider. Ads are short and unobtrusive and pay on click through, not on ad impression.

So, it doesn’t matter how people use the content, wherever they use the content – either through an embeddable Flash player or through downloads (or even if the content is aggregated into an RSS feed) all parties still benefit and there’s no “must drive traffic to website” model involved.

In my (probably not so humble) opinion Revver is one model that will sustain. The other would be direct payment between viewers and content owners in an RSS-driven (Podcast/Video Podcast like) feed. But that model doesn’t exist until klickTab.com launches.