I got inspired by this article to write my first Applescript:
"Simplify media transcription with hotkeys and AppleScript" - The Unofficial Apple Weblog
The article talks about setting up hotkeys to control Quicktime Player. A hotkey is when you assign a command to a keystroke. That way you can transcribe or log in a Microsoft Word or some other word processor and still control the movie playing back without switching applications. The article describes how to create hotkeys by using a freeware app Spark to create hotkeys that run an Applescript.
Well, at Link we tend to have stuff logged from DVD with timecode burned-in to the video. So I set up some simple, one-line Applescripts to play, pause, rewind, and fast forward DVD's.
Play
tell application "DVD Player" to play dvd
Pause
tell application "DVD Player" to pause dvd
Rewind
tell application "DVD Player" to rewind dvd
Fast Foward
tell application "DVD Player" to fast forward dvd
I checked it out with Word, and assigning the scripts to option+J, option+K, option+L, and option+space bar seemed to work fine.
If you do log/transcribe from a Quicktime movie then I blogged about a free app last year that combines logging and playback in one app, QT Movie Notetaker. The program makes time notations based on how far into the movie you are but doesn't read timecode. If you want to spend $99, InqScribe has a unified playback and logging interface and has timecode support for Quicktime movies. That's sort of the complete package for handy transcribing and logging.
Thursday, June 26, 2008
Sunday, June 22, 2008
Guides on Audio EQ and Compression
"Basic Guide to Understanding EQ"
"Taming Your Audio Signal with Compression"
I've always thought of myself as a visually-attuned person, but much less sensitive to sound. So while I think I have a natural proclivity to catching things with my eye, I think I have to work much harder for sound--I think I learned much quicker what looked right and how to make it that way than I was to learn when something sounded right and how to make it so.
After level changes, the next basic tool in your audio kit is EQ. Back in the day, when someone told you that she or he wanted to make something sound better in the edit room, you were going to turn to the EQ. I've done a fair amount of linear editing, and that meant using the EQ knobs on your mixer. I still turn to the mixer from time to time. It's a quick way to check out how adjusting different frequencies will affect your audio. The Mackie VLZ mixer, which most of our editors have, has low-end, mid-range, and high-end adjustments. If may not really improve the track, but it's a quick way to check if you can make something sound better by raising or lowering the level of particular frequencies (just remember to turn those pots back to unity when you're done testing--so you don't screw up someone else's audio.) Then once I've found a setting that I like, I'll recreate it with an EQ filter in Final Cut. The B&H article Basic Guide to Understanding EQ describes different kinds of EQ beyond what you'll find on your basic mixer. Shelving and cutting are also available in Final Cut Pro as filters.
Nowadays I usually find myself turning to compression first when I want to help an audio track--especially a clean track, like one recorded in a VO booth or a quiet studio. I'm pretty conservative on compression. I think it's overused on a lot of TV and radio, especially when annoying white guys are yelling to be the loudest person in the world. But even in milder forms, it can give a voice some punch. So for example, this article Taming Your Audio Signal with Compression recommends compression ratios of 2 to 4, whereas I usually keep my ratio at below 2. BTW, a ratio of 1 does nothing. Of course, this is the default setting, so if you're not familiar with compression then the first time you use it, you might think it does nothing.
Final Cut Pro does compression, but Soundtrack Pro's multipressor effect is even more powerful. I use multipressor to have a little noise gate in the effect, and I like the graph display so I can the audio levels where the noise gate is working and where the compressor is working. If I have the time then I'll often take a track to Soundtrack Pro. If it's shot in our studio, then I'll want to do some noise reduction first, then I'll do a multipressor, and then I'll apply the limiter in Soundtrack Pro. Soundtrack Pro's limiter works much better than FCP's. I like how you can see how much the limiter is working in the filter settings window. The limiter works similarly, but more crudely, than the compressor in that it can be used to give your track more punch.
I found these articles over at FreshDV. These articles are part of the B&H Pro Audio Newsletter, which you can subscribe to on their homepage. Most of what I have learned about audio I learned from the writings of a guy called Jay Rose . I keep a copy of his "Audio for Post Production" around the office, which I recommend for both beginners and experienced editors who want to dig deep into sound issues.
Saturday, June 14, 2008
Maintenance Tips for Your Mac
MacWorld: "Essential Mac Maintenance: Rev up your routines"
This a good article at MacWorld.com. A bunch of tips on how to get your Mac in good condition for the long run. I highly recommend the article.
One useful tip I liked was using SMART tests to regularly check on the health of your hard drives. Apparently these tests can give you a heads-up on ailing hard drives (before you lose data.) It's not bullet-proof, but it's supposed to protect against some of the more common types of hard drive failures. Michael Kinimoto says he has had good luck with doing regular SMART tests. The article recommends installing some freeware that regularly checks your hard drive's SMART status: Smart Reporter. Unfortunately, SMART tests don't work over firewire. It may work on an external hard drive hooked up through SATA, but that depends on what kind of hardware connection you have for your external SATA drive. The Firmtek Seritek PCI and PCI-E cards I've used pass along SMART data. But at the very least, you can be checking your internal drives on your Mac.
This a good article at MacWorld.com. A bunch of tips on how to get your Mac in good condition for the long run. I highly recommend the article.
One useful tip I liked was using SMART tests to regularly check on the health of your hard drives. Apparently these tests can give you a heads-up on ailing hard drives (before you lose data.) It's not bullet-proof, but it's supposed to protect against some of the more common types of hard drive failures. Michael Kinimoto says he has had good luck with doing regular SMART tests. The article recommends installing some freeware that regularly checks your hard drive's SMART status: Smart Reporter. Unfortunately, SMART tests don't work over firewire. It may work on an external hard drive hooked up through SATA, but that depends on what kind of hardware connection you have for your external SATA drive. The Firmtek Seritek PCI and PCI-E cards I've used pass along SMART data. But at the very least, you can be checking your internal drives on your Mac.
Labels:
freeware,
hard drive,
Macintosh,
maintenance,
storage
Cheap Tip for Matching Cameras
This sounds like a good tip for shooting, QP Card. Cheap cards with black, grey, and white swatches. Shoot these, and the in FCP use the 3-way Color Corrector to quickly color balance.
Seems like it would be particularly good for matching cameras. Under the light that you will shoot in, have all cameras record a couple of seconds of this. Then the cameras should match very well (assuming the cameras are the same models using the same settings.)
Saturday, May 31, 2008
Link TV's Next Camera
"Review: Sony HVR-Z7 & HVR-S270 1/3” 3-CMOS HDV camcorders" by Adam Wilt
I don't make many predictions on my blogs, but if I had to guess I think the Sony HVR-Z7 will be Link TV's next camera. Why you ask? First, it's Sony, and folks at Link in SF seem to like Sony. Second the price is right for us--well below the $10,000 mark, now about $5700 street price. Second it's a significant improvement on the Z1 camera that we have now. The Z1 has been out for over 3 years and Sony has finally released a true successor to the Z1. It's supposed to be faster than the Z1. It's all supposed to have a good LCD and viewfinder (areas where the Z1 is seriously lacking)
I'm basing this on Adam Wilt's excellent review of the Z7 and its bigger sibling the S270. It seems like there are some other good cameras out there, namely the Sony EX1, which records only onto flash memory. But for Link the lack of tape recording is sort of a deal breaker. At least as a post guy I don't want to have to deal with the headache of worrying about all of that media on hard drives with no other backup. Plus the EX1' s SxS Pro recording cards are still pretty pricey. For big shoots, that leaves options like a hard drive recorder, lugging around a laptop to shoots, or renting more storage. So much easier to pack a bunch of cheap tapes for a shoot.
If you want tapeless storage, the Z7 can even record to Compact Flash using the included HVR-MRC1 unit, which attaches at the back of the camera. That's a nice feature if you want the quick turnaround of material, which is a big benefit with tapeless workflows. Compact Flash is much cheaper than Panasonic's P2 and Sony's SxS Pro too.
The EX1 has 1/2" chips--the only sub-$10K HD camera with that. And it's supposed to have the sharpest picture in this price range. Too bad they couldn't match 1/2" chips along with the HDV format. The S270, which is reviewed in the same article, has one big feature that I'd like to see on the Z7--it can take large cassettes. That means 4.5 hours of HDV on a tape. But that camera is over the 10K point. But all things considered, the Z7 looks like a good camera, and from what Adam Wilt says, the champ of the sub-$10K HDV cameras.
Here's Adam's summary of the pros and cons of both the Z7 and the S270:
Pros
- Interchangeable lenses with standard 1/3” mounts.
- ISO 400 sensitivity.
- 800+ TVl/ph resolution with smooth, natural detail.
- DV, DVCAM, and 1080-line HDV recording.
- Interlaced and true progressive modes.
- Killer EVF and very good LCD; good peaking control.
- Best-in-the-business viewfinder data displays.
- Unique in-viewfinder tilt indicator.
- Z7: well balanced and easy to handhold.
- S270: no-nonsense, full-sized shoulder-mount camcorder; 4 channels of audio; 4.5 hour record times.
- Sensible ergonomics on both cameras: controls are where they should be.
- Sony Steadyshot.
- HVR-MRC1 CF card recorder included.
- Comprehensive Picture Profile tweaks, most with 15 steps of adjustment.
- Very good shotgun mike included.
Cons
- Stock lenses have only average chromatic aberration performance.
- Resolution drops with increased gain.
- Smooth Slow Motion clips have low resolution, many compression artifacts.
- Lens iris ring isn’t labeled or calibrated.
- Fastest power zoom isn’t very fast.
- MRC1: buttons lack a “hold” switch and are subject to inadvertent activation.
- MRC1: no single-frame mode in interval recording.
Labels:
Camcorder,
flash media,
HVR-S270,
HVR-Z1,
HVR-Z7,
pmw-ex1,
production,
Sony
Good Info on Mac Backup Software
"The Evolving World of Backup"
A few years back I bought my first online book "Taking Control of Mac OS X Backups." I basically just copied my plans for backing up at Link TV from this book. A good $10 purchase.
A new version isn't out yet, but the guy who wrote the book has posted some thoughts about trends in the Mac backup realm. I would have thought that Time Machine would have thinned out the available software (you can't beat free.) But apparently, backup software is proliferating and there are lots of new features coming out.
For example he mentions some workable online backup options, namely involving Amazon's S3. Sounds interesting.
Backup is still very confusing, and it takes a real strategy to handle it thoroughly and efficiently. Until the next version of "Taking Control of Mac OS X Backups" comes out, this article has some of the best backup info that I've seen.
A few years back I bought my first online book "Taking Control of Mac OS X Backups." I basically just copied my plans for backing up at Link TV from this book. A good $10 purchase.
A new version isn't out yet, but the guy who wrote the book has posted some thoughts about trends in the Mac backup realm. I would have thought that Time Machine would have thinned out the available software (you can't beat free.) But apparently, backup software is proliferating and there are lots of new features coming out.
For example he mentions some workable online backup options, namely involving Amazon's S3. Sounds interesting.
Backup is still very confusing, and it takes a real strategy to handle it thoroughly and efficiently. Until the next version of "Taking Control of Mac OS X Backups" comes out, this article has some of the best backup info that I've seen.
Saturday, May 17, 2008
Final Cut Server--Extra Credit
I did a big post on Final Cut Server last month. If you have not read it, please do. It covers what FC Server is and also lays out how we could use it at Link. This article is extra credit for folks who are really interested in the software.
I went to a presentation on Final Cut Server. It was hosted by Advanced Systems Group. They had a guy from Apple there to talk about the software. Then another guy gave a spiel about how you really want an expert to set up and customize FC Server. They gave some examples where you'll want an expert--setting up a web interface to videos, interacting with automation/playout servers.
One thing I realized at the presentation is that our metadata situation with our Final Cut projects is poor to useless. I know I rarely label clips with helpful info. I try to name projects accurately with the title of a project, but sometimes I don't get it right or the project name changes. Even tape numbers are not always entered or done so accurately. What's the point of having a giant database if you can't search with confidence that you'll actually find what you are looking for? Not to mention an ideal functionality like having files indexed with useful metadata so you could do keyword searches, say "insurgent attacks" and get some dramatic footage from Mosaic.
At our office editors usually haven't collaborated. I usually took an attitude of "if I can find it/figure it out, that's all that matters." But that kind of attitude is the opposite of what's needed for asset management. Extra work needs to go into getting good metadata with your media. Since we don't have the option of hiring a librarian to organize things, that means more work for the editors probably who have to have bought into the process. If they haven't then things will slack off and the metadata won't get entered.
While Final Cut Server does everything that I wrote about in my last post on it, the Apple guy and the ASG folks were really pushing that you have to have an expert to set it up. I think I could get it to do everything that I discussed in my last post with the caveat about searching through poor metadata.
We've talked about hosting media from Mosaic on the web. Again, FC Server won't do this on its own. But it seems like it would be a good spot to organize that media. Then with automation scripting in FC Server, you could hand off the media to a website that handles the front-end, movie hosting, etc. FC Server would be where staff would import media and attach metadata to make it useful for users. FC Server could automatically hand it off to a system to handle the web part with scripting done by somebody knowledgeable.
Below are the notes that I took at the session:
Once a project is imported into FC Server you need to check in and check out. If you keep a copy locally and work with it again after import, then FC Server will think it's a new file when you try to put it back into FC Server. So basically it adds an extra step to opening a project--you have to check it out of FC Server first. Then you have to check it back in to get it to FC Server to update the media for it. Looks like more work for the editor, who has to have bought into the process--otherwise, he or she will just keep everything locally.
Showed a cool video about Radical Media
Translation done in China and FC Server handled ftp for cutting in New York. Complex workflow with steps and notification automated. Required scripting to make FC Server work with ftp server. Process also described in this white paper called "Final Cut Server in Depth" (PDF download.) Translation was added as subtitles using the title tool in Final Cut Pro. BTW, that's extra work for the translator. For Latin Pulse we do subtitles and it takes a lot of time. Translation is done first by someone with good Spanish and English, then spotting and creation of titles is done afterwards by someone who doesn't need language skills that are that strong. (Another step is me reviewing all of the subtitles, suggesting rewrites, adjusting the layout of the titles, and editing if the translation is too long to get read in real time.)
Check out Final Cut Pro projects from Server
Options to handle media when you check out a project
-Edit in place (doesn't do anything really)
-Edit proxies (good for taking a project home for the weekend or on the road)
-Disconnected use (makes a copy of the project and its media, like media manager)
Can't use project until it is checked back in. That is folks can't work on the same FCP project at the same time.
Media manager only recommended if you are creating a whole new version of a project. Again you have to play by FC Server's rule if you want it to track your stuff well.
Demo'd a web interface to log and annotate clips. But this was only a demo version and is not part of the softare. This was a "what you could do" if you are web developer or could afford to hire one. Hmm, well I'm not and we can't for what I do.
FC Server Strategy Meeting--topics for discussion
-Storage plan (for proxy files)
-Type of proxies
-Workflow strategy (what do you do with your media, where does it go, how does it get there, who does what with the media, aka Who, What, Where, Why, When, and How)
-Users
-Advanced automation
-email notifications
-Compression & distribution
-Web review (again not part of the product)
-"Customer" access to FCS
Automated backup can be done--setup rules for when to backup
For example: if file hasn't been touched in a certain amount of time, move to backup storage
Don't have to do an initial scan that sucks in all of your media, it may be better to add project by project. That way, you can be more thorough with metadata.
Annotate is where you can tag in and out markers and comments on clips. Apple guy said that this is supposed to be for transfer of this info back to FCP, but he didn't know how to do it/if it could be done now. Originally, there was going to be similar functionality to make simple edited sequences--I think those would have been transfered back through XML files. But Apple guy said no editing functionality but he "hoped" that they would add that feature because they touted it last year. Annotate is where producers could check out clips for editing and mark ins and outs for editors. It would be great if that could get into FCP. It would still be great for the producers to mark ins and outs on media directly on the clips as opposed to making notes on paper based on time code from a Beta or DV or timer from DVD. But without sending that info back to FCP, editor has to manually transfer in and out points.
Does it work with stills? Sure. FC Server is based on the Artbox software, which was originally written for still images. Also useful for getting producers to sign off on graphics. No need to drag Wendy into the editing room for her to look at something, which (I hope) she will just say OK to anyway. Yeah, for real collaboration you have to be in the same room but for quick and dirty this would be really nice to speed things up.
Suggestions from presenters that FC Serve can read After Effects files to get the links to the media that the project uses. That would be cool.
I went to a presentation on Final Cut Server. It was hosted by Advanced Systems Group. They had a guy from Apple there to talk about the software. Then another guy gave a spiel about how you really want an expert to set up and customize FC Server. They gave some examples where you'll want an expert--setting up a web interface to videos, interacting with automation/playout servers.
One thing I realized at the presentation is that our metadata situation with our Final Cut projects is poor to useless. I know I rarely label clips with helpful info. I try to name projects accurately with the title of a project, but sometimes I don't get it right or the project name changes. Even tape numbers are not always entered or done so accurately. What's the point of having a giant database if you can't search with confidence that you'll actually find what you are looking for? Not to mention an ideal functionality like having files indexed with useful metadata so you could do keyword searches, say "insurgent attacks" and get some dramatic footage from Mosaic.
At our office editors usually haven't collaborated. I usually took an attitude of "if I can find it/figure it out, that's all that matters." But that kind of attitude is the opposite of what's needed for asset management. Extra work needs to go into getting good metadata with your media. Since we don't have the option of hiring a librarian to organize things, that means more work for the editors probably who have to have bought into the process. If they haven't then things will slack off and the metadata won't get entered.
While Final Cut Server does everything that I wrote about in my last post on it, the Apple guy and the ASG folks were really pushing that you have to have an expert to set it up. I think I could get it to do everything that I discussed in my last post with the caveat about searching through poor metadata.
We've talked about hosting media from Mosaic on the web. Again, FC Server won't do this on its own. But it seems like it would be a good spot to organize that media. Then with automation scripting in FC Server, you could hand off the media to a website that handles the front-end, movie hosting, etc. FC Server would be where staff would import media and attach metadata to make it useful for users. FC Server could automatically hand it off to a system to handle the web part with scripting done by somebody knowledgeable.
Below are the notes that I took at the session:
Once a project is imported into FC Server you need to check in and check out. If you keep a copy locally and work with it again after import, then FC Server will think it's a new file when you try to put it back into FC Server. So basically it adds an extra step to opening a project--you have to check it out of FC Server first. Then you have to check it back in to get it to FC Server to update the media for it. Looks like more work for the editor, who has to have bought into the process--otherwise, he or she will just keep everything locally.
Showed a cool video about Radical Media
Translation done in China and FC Server handled ftp for cutting in New York. Complex workflow with steps and notification automated. Required scripting to make FC Server work with ftp server. Process also described in this white paper called "Final Cut Server in Depth" (PDF download.) Translation was added as subtitles using the title tool in Final Cut Pro. BTW, that's extra work for the translator. For Latin Pulse we do subtitles and it takes a lot of time. Translation is done first by someone with good Spanish and English, then spotting and creation of titles is done afterwards by someone who doesn't need language skills that are that strong. (Another step is me reviewing all of the subtitles, suggesting rewrites, adjusting the layout of the titles, and editing if the translation is too long to get read in real time.)
Check out Final Cut Pro projects from Server
Options to handle media when you check out a project
-Edit in place (doesn't do anything really)
-Edit proxies (good for taking a project home for the weekend or on the road)
-Disconnected use (makes a copy of the project and its media, like media manager)
Can't use project until it is checked back in. That is folks can't work on the same FCP project at the same time.
Media manager only recommended if you are creating a whole new version of a project. Again you have to play by FC Server's rule if you want it to track your stuff well.
Demo'd a web interface to log and annotate clips. But this was only a demo version and is not part of the softare. This was a "what you could do" if you are web developer or could afford to hire one. Hmm, well I'm not and we can't for what I do.
FC Server Strategy Meeting--topics for discussion
-Storage plan (for proxy files)
-Type of proxies
-Workflow strategy (what do you do with your media, where does it go, how does it get there, who does what with the media, aka Who, What, Where, Why, When, and How)
-Users
-Advanced automation
-email notifications
-Compression & distribution
-Web review (again not part of the product)
-"Customer" access to FCS
Automated backup can be done--setup rules for when to backup
For example: if file hasn't been touched in a certain amount of time, move to backup storage
Don't have to do an initial scan that sucks in all of your media, it may be better to add project by project. That way, you can be more thorough with metadata.
Annotate is where you can tag in and out markers and comments on clips. Apple guy said that this is supposed to be for transfer of this info back to FCP, but he didn't know how to do it/if it could be done now. Originally, there was going to be similar functionality to make simple edited sequences--I think those would have been transfered back through XML files. But Apple guy said no editing functionality but he "hoped" that they would add that feature because they touted it last year. Annotate is where producers could check out clips for editing and mark ins and outs for editors. It would be great if that could get into FCP. It would still be great for the producers to mark ins and outs on media directly on the clips as opposed to making notes on paper based on time code from a Beta or DV or timer from DVD. But without sending that info back to FCP, editor has to manually transfer in and out points.
Does it work with stills? Sure. FC Server is based on the Artbox software, which was originally written for still images. Also useful for getting producers to sign off on graphics. No need to drag Wendy into the editing room for her to look at something, which (I hope) she will just say OK to anyway. Yeah, for real collaboration you have to be in the same room but for quick and dirty this would be really nice to speed things up.
Suggestions from presenters that FC Serve can read After Effects files to get the links to the media that the project uses. That would be cool.
Sunday, May 11, 2008
24p vs. 30p
So we are moving away (slowly all be it) from interlaced video to progressive video. There are a number of framerates common with progressive. Here's a brief breakdown
24 fps--what's used on film
30 fps--half as many samples per second as regular TV (e.g., 60 interlaced)
25 fps--half the frame rate of regular TV in Europe (e.g., 50 fps)
50 fps--the samples of images per second used in European TV
60 fps--the samples of images per second used in North America TV ( which is usually interlaced)
So people generally prefer the slower frame rates in documentaries and dramatic material because it reminds people of film and the cinema--in short it looks classy. The faster frame rates look like TV and are a must have for sports where things are moving fast.
This post is primarily concerned with the technological differences (and not aesthetic) between different frame rates. (If you want to brush up on your basic knowledge of interlaced versus progressive, check out their definitions from this glossary from Quantel.) So let me outline a couple of the technical advantages of progressive video versus interlaced video:
1) Monitors are rapidly turning progressive--LCD's (both TV's and computers) and plasmas. These monitors can't natively display interlaced video. So some processing has to be done to de-interlace, and very often you end of losing resolution (and lots of it) when the de-interlacing happens. It depends partly on how good the hardware is that does the de-interlacing, but this happens at the consumer's end--so you never quite know how it will look. In short, a cheap TV will do a bad job of this.
2) Better effects work on progressive footage. Lots of effects, including scaling, require the video to be de-interlaced. Final Cut Pro does a lousy job of de-interlacing. If your footage is progressive (and FCP knows it), then it won't de-interlace to do simple things like scaling up the video. This past week, I had to include some letterboxed standard-def video in a high-def show. It looked super soft in FCP. So I used Compressor to do a very slow but very good de-interlacing of the footage, which I then scaled up (but again I didn't even scale this footage in FCP). It looked a lot better with the de-interlacing that Compressor does than the de-interlacing that FCP does.
3) Progressive distribution of video. Computer monitors were never interlaced--so anything for distribution on computers benefits from being progressive. Also DVD's will handle 24 fps. This is great if the video is going to a progressive display, e.g., LCD or Plasma. As mentioned above, interlaced footage needs to de-interlaced to be scaled, but progressive doesn't. So a 24fps DVD will usually look much better on a high-def display than a comparable 60i video.
Important note: DVD doesn't have a standard for 30 fps--it's either 60i or 24 fps. So your DVD player and your TV treat 30 fps just like 60i--if it gets scaled up then you could lose resolution (but not always--again it depends on the display.)
Now let me move on to outline some advantages and drawbacks of different framerates:
24 fps: So if you're going to make a film print, then you should shoot in this framerate. OK .001 per cent of anything shot by professionals will ever end up on film. But because 24fps has been very hot for many years (essentially the Panasonic DVX-100 set that off) there are a lot of post workflows for working with 24 fps. 30 fps is gaining ground though--there are now lots of setups in FCP for it.
24 fps is very close to 25 fps. So a general option for converting for a European master is to just speed up the movie by 4%. No elaborate and/or expensive standards conversion. I think Compressor will handle this 4% speed up for you. I recently did a post of a technology guide from Quantel and they recommend 24fps as a universal format because it is so easy to transfer across the Atlantic.
And it's important that your software knows that you want to work progressive. You can put 24fps or 30fps in a 60i timeline, but then you've lost all of the technological advantages of working progressive. Your editing software, your computer, your DVD player, your TV will treat it like interlaced video. So as a general rule, pick a frame rate and stick to it throughout post and distribution. Obviously this can sometimes be really problematical--what about archival footage that's 60i? Or you want to work with a shooter and they don't own a camera that shoots progressive. You can convert that to 24fps using Compressor, but it's a real pain. No easy answer for this one.
As or 30 fps, one advantage is that is has more samples per second than 24 fps. 24 fps can look kind of choppy--you especially have to be careful with panning quickly. 30 fps is no walk in the park in this regards, but you have 25% more samples of the image per second than with 24 fps--so definitely less choppy.
In general for cameras, especially with CCD chips, it is easier to create 30 fps than 24 fps. CCD's have been doing 60i for so long that a lot of cameras out there are still based around that technology. Namely, the Sony HVR-Z1, which Link owns. The Z1 doesn't do real progressive imaging, but with the Cineframe modes you can get video that has 24, 25, or 30 images per second. Basically the camera blends the interlaced video to get progressive-looking video. Apparently, the Cineframe 24 with the Sony Z1 is supposed to be really crummy. The Cineframe 30 is supposed to be better, as is the Cineframe 25. Basically the camera is capturing video in an interlaced manner 60 time per second and has to figure out how to make progressive frames with it. With all Cineframe modes, this means tossing out some resolution. The Canon XL-H1 also does a similar process to get progressive frame rates. But going to 30 fps from 60i is easier--basically is the image is moving than you throw about every other field. And the Z1 does Cineframe 30 reasonably but fails with Cineframe 24 (Caveat: this is definitely true for HD, but if you are downconverting to SD it might be OK.)
One option I saw discussed over at a great post and discusion, which talks about frame rates, at HD for Indies is to shoot with the Z1 Cineframe 25 and then slow it down to get 24 fps. I think the easiest way to do this would be with Compressor, but these Compressor workflows are a hassle. However, if quality is important than this is an option.
By the way, Sony is moving from CCD's to CMOS, and the CMOS sensors are much more versatile with frame rates. So the HVR-V1 chips natively captures at 24 fps, as does the new EX-1, the HVR-Z7 and HVR-S270.
One problem is that even if the camera can capture images at 24 fps (or 30 fps), the camera often actually records in video that is actually 60i. With 24 fps that is recorded in a signal of 60i, the camera adds pulldown (see the definition in this Quantel post I did). In post you need to remove the pulldown, otherwise your editing software just treats it like 60i and you lose all the technological advantages of working with progressive video. So to post at 24 fps, you may have to convert the footage to remove the pulldown. This can make post-production very complex. FCP has added a setup for version 6.0.2, which is supposed to automatically remove the pulldown from the V1's 24 fps footage. Newer gear from Sony like the Z7 and S270 are doing a native framerate of 24fps recording in HDV. Tapeless cameras like the Panasonic HVX-200 and the Sony PMW EX-1 handle progressive footage in a much more straight-forward manner.
One drawback with 30 fps is that it doesn't convert well to 24 fps or 25 fps. 60i is easier to convert to 25 fps because it has a lot more samples across time to work with. Basically when you are doing a major standards conversion, a computer needs to generate frames that don't exist by analyzing the image information that is available. The more samples of images, the better that this process can be handled. In short if you have to make 25 fps video or 50i video, than 60 images per second is much better than 30 images per second. (Remember that going from 24 fps to 25 fps can be done in a much easier way by simply speeding up the video by 4%.)
UPDATE
I thought I should add a caveat about the above comments on standards conversion. The workflow that I desribe for speeding up 24 fps to make it a European-friendly 25 fps is a workflow that I've only heard discussed as a step done in a computer, e.g., Final Cut Pro or Compressor. So you could convert the footage on your Mac--but you'd still have to make a master on a 25 fps or 50 fps format, usually tape like DigiBeta or if HD, HDCam or DVCProHD. The traditional way to do standards conversion is that folks just make an NTSC master of their program and then send it to a high-end dub house to get a PAL copy done. This is obviously easier than having to make a master on your own for formats designed to work in Europe. I don't know of a dub scenario that exists for taking a 24 fps master and speeding it up during a transfer to make it 25 fps. If you want a standards conversion done during a dub, then 24 fps may not be any better than 30 fps.
In short, there is no easy answer to this question. First you got to know your camera, know your post options, and know your distribution plans. From there, it's a matter of trade-offs, for quality, time, and money.
24 fps--what's used on film
30 fps--half as many samples per second as regular TV (e.g., 60 interlaced)
25 fps--half the frame rate of regular TV in Europe (e.g., 50 fps)
50 fps--the samples of images per second used in European TV
60 fps--the samples of images per second used in North America TV ( which is usually interlaced)
So people generally prefer the slower frame rates in documentaries and dramatic material because it reminds people of film and the cinema--in short it looks classy. The faster frame rates look like TV and are a must have for sports where things are moving fast.
This post is primarily concerned with the technological differences (and not aesthetic) between different frame rates. (If you want to brush up on your basic knowledge of interlaced versus progressive, check out their definitions from this glossary from Quantel.) So let me outline a couple of the technical advantages of progressive video versus interlaced video:
1) Monitors are rapidly turning progressive--LCD's (both TV's and computers) and plasmas. These monitors can't natively display interlaced video. So some processing has to be done to de-interlace, and very often you end of losing resolution (and lots of it) when the de-interlacing happens. It depends partly on how good the hardware is that does the de-interlacing, but this happens at the consumer's end--so you never quite know how it will look. In short, a cheap TV will do a bad job of this.
2) Better effects work on progressive footage. Lots of effects, including scaling, require the video to be de-interlaced. Final Cut Pro does a lousy job of de-interlacing. If your footage is progressive (and FCP knows it), then it won't de-interlace to do simple things like scaling up the video. This past week, I had to include some letterboxed standard-def video in a high-def show. It looked super soft in FCP. So I used Compressor to do a very slow but very good de-interlacing of the footage, which I then scaled up (but again I didn't even scale this footage in FCP). It looked a lot better with the de-interlacing that Compressor does than the de-interlacing that FCP does.
3) Progressive distribution of video. Computer monitors were never interlaced--so anything for distribution on computers benefits from being progressive. Also DVD's will handle 24 fps. This is great if the video is going to a progressive display, e.g., LCD or Plasma. As mentioned above, interlaced footage needs to de-interlaced to be scaled, but progressive doesn't. So a 24fps DVD will usually look much better on a high-def display than a comparable 60i video.
Important note: DVD doesn't have a standard for 30 fps--it's either 60i or 24 fps. So your DVD player and your TV treat 30 fps just like 60i--if it gets scaled up then you could lose resolution (but not always--again it depends on the display.)
Now let me move on to outline some advantages and drawbacks of different framerates:
24 fps: So if you're going to make a film print, then you should shoot in this framerate. OK .001 per cent of anything shot by professionals will ever end up on film. But because 24fps has been very hot for many years (essentially the Panasonic DVX-100 set that off) there are a lot of post workflows for working with 24 fps. 30 fps is gaining ground though--there are now lots of setups in FCP for it.
24 fps is very close to 25 fps. So a general option for converting for a European master is to just speed up the movie by 4%. No elaborate and/or expensive standards conversion. I think Compressor will handle this 4% speed up for you. I recently did a post of a technology guide from Quantel and they recommend 24fps as a universal format because it is so easy to transfer across the Atlantic.
And it's important that your software knows that you want to work progressive. You can put 24fps or 30fps in a 60i timeline, but then you've lost all of the technological advantages of working progressive. Your editing software, your computer, your DVD player, your TV will treat it like interlaced video. So as a general rule, pick a frame rate and stick to it throughout post and distribution. Obviously this can sometimes be really problematical--what about archival footage that's 60i? Or you want to work with a shooter and they don't own a camera that shoots progressive. You can convert that to 24fps using Compressor, but it's a real pain. No easy answer for this one.
As or 30 fps, one advantage is that is has more samples per second than 24 fps. 24 fps can look kind of choppy--you especially have to be careful with panning quickly. 30 fps is no walk in the park in this regards, but you have 25% more samples of the image per second than with 24 fps--so definitely less choppy.
In general for cameras, especially with CCD chips, it is easier to create 30 fps than 24 fps. CCD's have been doing 60i for so long that a lot of cameras out there are still based around that technology. Namely, the Sony HVR-Z1, which Link owns. The Z1 doesn't do real progressive imaging, but with the Cineframe modes you can get video that has 24, 25, or 30 images per second. Basically the camera blends the interlaced video to get progressive-looking video. Apparently, the Cineframe 24 with the Sony Z1 is supposed to be really crummy. The Cineframe 30 is supposed to be better, as is the Cineframe 25. Basically the camera is capturing video in an interlaced manner 60 time per second and has to figure out how to make progressive frames with it. With all Cineframe modes, this means tossing out some resolution. The Canon XL-H1 also does a similar process to get progressive frame rates. But going to 30 fps from 60i is easier--basically is the image is moving than you throw about every other field. And the Z1 does Cineframe 30 reasonably but fails with Cineframe 24 (Caveat: this is definitely true for HD, but if you are downconverting to SD it might be OK.)
One option I saw discussed over at a great post and discusion, which talks about frame rates, at HD for Indies is to shoot with the Z1 Cineframe 25 and then slow it down to get 24 fps. I think the easiest way to do this would be with Compressor, but these Compressor workflows are a hassle. However, if quality is important than this is an option.
By the way, Sony is moving from CCD's to CMOS, and the CMOS sensors are much more versatile with frame rates. So the HVR-V1 chips natively captures at 24 fps, as does the new EX-1, the HVR-Z7 and HVR-S270.
One problem is that even if the camera can capture images at 24 fps (or 30 fps), the camera often actually records in video that is actually 60i. With 24 fps that is recorded in a signal of 60i, the camera adds pulldown (see the definition in this Quantel post I did). In post you need to remove the pulldown, otherwise your editing software just treats it like 60i and you lose all the technological advantages of working with progressive video. So to post at 24 fps, you may have to convert the footage to remove the pulldown. This can make post-production very complex. FCP has added a setup for version 6.0.2, which is supposed to automatically remove the pulldown from the V1's 24 fps footage. Newer gear from Sony like the Z7 and S270 are doing a native framerate of 24fps recording in HDV. Tapeless cameras like the Panasonic HVX-200 and the Sony PMW EX-1 handle progressive footage in a much more straight-forward manner.
One drawback with 30 fps is that it doesn't convert well to 24 fps or 25 fps. 60i is easier to convert to 25 fps because it has a lot more samples across time to work with. Basically when you are doing a major standards conversion, a computer needs to generate frames that don't exist by analyzing the image information that is available. The more samples of images, the better that this process can be handled. In short if you have to make 25 fps video or 50i video, than 60 images per second is much better than 30 images per second. (Remember that going from 24 fps to 25 fps can be done in a much easier way by simply speeding up the video by 4%.)
UPDATE
I thought I should add a caveat about the above comments on standards conversion. The workflow that I desribe for speeding up 24 fps to make it a European-friendly 25 fps is a workflow that I've only heard discussed as a step done in a computer, e.g., Final Cut Pro or Compressor. So you could convert the footage on your Mac--but you'd still have to make a master on a 25 fps or 50 fps format, usually tape like DigiBeta or if HD, HDCam or DVCProHD. The traditional way to do standards conversion is that folks just make an NTSC master of their program and then send it to a high-end dub house to get a PAL copy done. This is obviously easier than having to make a master on your own for formats designed to work in Europe. I don't know of a dub scenario that exists for taking a 24 fps master and speeding it up during a transfer to make it 25 fps. If you want a standards conversion done during a dub, then 24 fps may not be any better than 30 fps.
In short, there is no easy answer to this question. First you got to know your camera, know your post options, and know your distribution plans. From there, it's a matter of trade-offs, for quality, time, and money.
Labels:
24fps,
30 fps,
Compressor,
Final Cut Pro,
HVR-S270,
HVR-Z7,
interlaced,
standards conversion
Saturday, May 10, 2008
Adobe--Photoshop and Future Technologies
PHOTOSHOP FOR VIDEO
With Photoshop CS3 Extended, you can now bring in video to Photoshop. Why would you want to do that you ask? What about After Effects? What about Color? Well I just came across a cool site/podcast that gives you a number of interesting ideas about how to harness Photoshop to make your video better.
Here's a video from the Photoshop for Video site that shows you how to use the Shadows-Highlights command on video. I recently used the shadows and highlights command in iPhoto to save some snapshots, and I was thinking "if I can do this on software that's practically free, why can't I do this in Final Cut Pro?". Well I still don't know how to do it with FCP, but I could correct my video this way with the latest & greatest version of Photoshop.
Back to the issue about Color. I haven't used it yet and frankly I'm not thrilled about learning a new interface. Now I have the option of harnessing my knowledge of Photoshop to do some cool tweaking. Also, for you folks who don't know Photoshop, I think this website/podcast is good way to pick up knowledge about the best image editing application out there.
Here are some other cool videos from Photoshop for Video at Adobe TV that I recommend:
Spot Color Grading
Making Alpha Channels for Logos (I do this lots)
So this appears to be regularly updated via a podcast--good way to use podcast subscription to do some regular learning if you're interested in Photoshop. Oh, video in Photoshop only just got added to the Extended verison of the latest Photoshop. But not everything on this site is about this feature, good stuff that can be done in older versions of Photoshop is available too (e.g., the alpha channels for logos movie.)
ADOBE'S FUTURE TECHNOLOGIES
While on the topic of Adobe, there's another interesting video from NAB where Adobe talks about some future technologies. The most interesting one for me is what they call "End to End Metadata". In particular, they were demoing speech recognition that generates transcripts for movies. Then that transcript can be leveraged in editing (Premiere Pro) and in delivery to the web (Flash video.)
Avid has already deployed some of these tools with their Script Sync, which I wrote about on this post. Basically you can hop around in the text of a script or transcript, and the software know where people are saying that bit of dialogue. But I like how Adobe takes it another step further by allowing delivery of the text too--think subtitles, think closed captioning, think searchable text on the web.
I don't know about the voice recognition engine creating automatic transcriptions. I can't believe voice recognition is that good--on the other hand, I'm sure our government is spending billions on voice recognition software so that they can monitor everyone's phone calls. Eventually that technology will filter down to us mere mortals--just another great benefit brought to us by the Bush Administration.
Here's the outline of the Adobe technology presentation if you are interested in any of the other stuff:
1. Cinema DNG
2. End to End Metadata
3. Mobile Delivery
4. Interactivity without scripting
So I found out about these video over at Pro Video Coalition, which is turning into my main source for video news.
With Photoshop CS3 Extended, you can now bring in video to Photoshop. Why would you want to do that you ask? What about After Effects? What about Color? Well I just came across a cool site/podcast that gives you a number of interesting ideas about how to harness Photoshop to make your video better.
Here's a video from the Photoshop for Video site that shows you how to use the Shadows-Highlights command on video. I recently used the shadows and highlights command in iPhoto to save some snapshots, and I was thinking "if I can do this on software that's practically free, why can't I do this in Final Cut Pro?". Well I still don't know how to do it with FCP, but I could correct my video this way with the latest & greatest version of Photoshop.
Back to the issue about Color. I haven't used it yet and frankly I'm not thrilled about learning a new interface. Now I have the option of harnessing my knowledge of Photoshop to do some cool tweaking. Also, for you folks who don't know Photoshop, I think this website/podcast is good way to pick up knowledge about the best image editing application out there.
Here are some other cool videos from Photoshop for Video at Adobe TV that I recommend:
Spot Color Grading
Making Alpha Channels for Logos (I do this lots)
So this appears to be regularly updated via a podcast--good way to use podcast subscription to do some regular learning if you're interested in Photoshop. Oh, video in Photoshop only just got added to the Extended verison of the latest Photoshop. But not everything on this site is about this feature, good stuff that can be done in older versions of Photoshop is available too (e.g., the alpha channels for logos movie.)
ADOBE'S FUTURE TECHNOLOGIES
While on the topic of Adobe, there's another interesting video from NAB where Adobe talks about some future technologies. The most interesting one for me is what they call "End to End Metadata". In particular, they were demoing speech recognition that generates transcripts for movies. Then that transcript can be leveraged in editing (Premiere Pro) and in delivery to the web (Flash video.)
Avid has already deployed some of these tools with their Script Sync, which I wrote about on this post. Basically you can hop around in the text of a script or transcript, and the software know where people are saying that bit of dialogue. But I like how Adobe takes it another step further by allowing delivery of the text too--think subtitles, think closed captioning, think searchable text on the web.
I don't know about the voice recognition engine creating automatic transcriptions. I can't believe voice recognition is that good--on the other hand, I'm sure our government is spending billions on voice recognition software so that they can monitor everyone's phone calls. Eventually that technology will filter down to us mere mortals--just another great benefit brought to us by the Bush Administration.
Here's the outline of the Adobe technology presentation if you are interested in any of the other stuff:
1. Cinema DNG
2. End to End Metadata
3. Mobile Delivery
4. Interactivity without scripting
So I found out about these video over at Pro Video Coalition, which is turning into my main source for video news.
Labels:
Adobe,
Avid,
Color correction,
Flash,
Photoshop,
Transcription
Tuesday, May 6, 2008
Apple Rumors (and a little news)
I try not to pass along rumors, but there's a scary one that's been floating around enough that I thought I'd mention it. I think it started around the time that Apple said that it was going to skip NAB. The word from the grapevine is that Apple is going to sell its Pro Apps, which includes Final Cut Pro.
The rumor has been pretty persistent, enough for Apple to officially deny it. In Robert Cringely's latest article he says that Apple spent the NAB conference looking for buyers for their Pro Apps. He's been saying for a while that Apple will buy Adobe in order to get Flash. If that's the case, then Cringely thinks that Apple can't keep both their Pro Apps and Adobe's competing products, like Premiere, After Effects, and their other audio-video apps because of anti-trust concerns. He's more convincing than any of the other sources that I've heard with this rumor or similar ones, so I'm a little more concerned about it. Although, Cringely goes on to to suggest that if Apple really did buy Adobe, then it would sell the Adobe apps that compete with Apple's.
I still think it's unlikely that Apple would sell Final Cut Pro, and for that viewpoint there's a short blog at Final Cut User.
For a bit of official news, there was a statement from an Apple employee on why Final Cut Server took so long to appear on the market--nearly a year after it was announced. According to this interview at TVBEurope, Apple went back to the drawing board to make Final Cut Server easy to administer. Apple's marketing director for professional video apps said that they were reworking Final Cut Server so that it could run "without an IT department to support it." Final Cut Server seems to have been based on asset management software that Apple acquired late in 2006 from a company called Proximity. If they were simplifying the software, I can appreciate that. I'm not interested in becoming an IT professional, but I'm the most likely person to set up and run Final Cut Server at Link TV.
In the same article, Apple's marketing guy says that they have sold a million licenses of FCP. He also said that FCP had 49% market share in 2007 versus Avid's 22% share.
The rumor has been pretty persistent, enough for Apple to officially deny it. In Robert Cringely's latest article he says that Apple spent the NAB conference looking for buyers for their Pro Apps. He's been saying for a while that Apple will buy Adobe in order to get Flash. If that's the case, then Cringely thinks that Apple can't keep both their Pro Apps and Adobe's competing products, like Premiere, After Effects, and their other audio-video apps because of anti-trust concerns. He's more convincing than any of the other sources that I've heard with this rumor or similar ones, so I'm a little more concerned about it. Although, Cringely goes on to to suggest that if Apple really did buy Adobe, then it would sell the Adobe apps that compete with Apple's.
I still think it's unlikely that Apple would sell Final Cut Pro, and for that viewpoint there's a short blog at Final Cut User.
For a bit of official news, there was a statement from an Apple employee on why Final Cut Server took so long to appear on the market--nearly a year after it was announced. According to this interview at TVBEurope, Apple went back to the drawing board to make Final Cut Server easy to administer. Apple's marketing director for professional video apps said that they were reworking Final Cut Server so that it could run "without an IT department to support it." Final Cut Server seems to have been based on asset management software that Apple acquired late in 2006 from a company called Proximity. If they were simplifying the software, I can appreciate that. I'm not interested in becoming an IT professional, but I'm the most likely person to set up and run Final Cut Server at Link TV.
In the same article, Apple's marketing guy says that they have sold a million licenses of FCP. He also said that FCP had 49% market share in 2007 versus Avid's 22% share.
Monday, April 28, 2008
Blu-ray and Macs
Right now, 3rd party software is providing support for burning. Toast 8 and 9 let you burn data Blu-ray. Toast 9 is supposed to let you burn high-def video to Blu-ray that will playback on Blu-ray players. But Adobe's Encore, part of Production Premium CS3, is now the best solution for putting high-def video onto Blu-ray. With a Blu-ray burner on the way to Link TV, and a copy of CS3 Production Premium available, we are on our way to burning our first Blu-ray discs. (Now if I can only convince my boss to buy a high-def TV and a PS3, so we could play the darn things.)
Adobe can encode your video for you, but there's a recent blog post Apple's Compressor & Encore Blu-Ray from Adobe that helps you figure out how to encode your high-def in Compressor. Adobe gets kudos for playing well with others. They don't pretend like they are the end-all and be-all of post-production software and that anything you would ever want to do can be done on their software. And I like the concept of an Adobe blog as a personable way to distribute info about software. The closest thing Apple gets to providing updated info on their software is their antiseptic support documents.
Adobe can't find a way to get h.264 encoding from Compressor working with Blu-ray, so they are using MPEG-2 encoding. Adobe will encode your high-def to h.264 for you, but it's nice not to have to do an export of your entire high-def show before you even start to encode.
I found this blog post over at Final Cut User who is also bemoaning Apple's lame response to Blu-ray.
Labels:
Adobe,
Blu-ray,
Compressor,
Creative Suite,
Encore,
h.264
Sunday, April 27, 2008
NAB 2008
Well, 2 weeks after it started, I'm finally coming out with a NAB post. It wasn't a huge post-production year at NAB--Apple and Avid didn't have booths. And no new products from Adobe. All the major camera manufacturers had some new models. But I've been blogging too much about cameras that I'll probably never work with, and none of the new cameras introduced any real post ramifications. I found the best coverage of NAB at two sites: Pro Video Coaltion and FreshDV. They have good coverage of new stuff from Sony, Panasonic, Canon, JVC, and RED.
There were a couple of post-production things that were interesting, but not earth shattering. Blackmagic Design added HDMI in and out to their $1000 Decklink HD Extreme card. They keep cramming more and more features into their cards. At this point AJA only matches Decklink's in and out on the aprrox. $3000 Io HD (which stole the show last year). I like AJA's gear but they aren't staying competitive feature-wise with Blackmagic. Heck, the analog-only and standard-def only IOLA is still selling for $1K.
Blackmagic also announced a little USB thingy called simply Video Recorder that captures standard-def video straight to h.264. So there's digitizing hardware and h.264 compression in a tiny piece of plastic that plugs right into a USB port. For $120 you get analog capture with the Blackmagic Video Recorder. For $300, you get SDI-only input and RS-422 deck control. Sort of like Elgato's Turbo.264 with video capture too. Not sure how we would use this. It's basically like a quick-and-dirty way to capture really compressed video. Hopefully it will do a good job with the compression. Seems like they should have it work with some PVR software like Elgato's EyeTV.
Matrox came out with a something like a competitor to the Io HD. The MXO2 is portable I/O hardware for about $1600. Unlike the Io HD, you can do uncompressed HD if you want. But unlike the Io HD there's no built-in codec support. A great thing about the Io HD is that it will transcode to ProRes in the box. ProRes is pretty processor-intensive to transcode in real-time--for HD you need 4 Intel Xeon cores at a minimum. So I don't see how you could capture HD on a laptop with the MXO2. It hooks up to a tower through a PCI-E card and to MacBook Pro through Expresscard slot (so no support on iMac's or Macbooks.) It also is supposed to do up/down/cross-conversion and claims support for Adobe Premiere Pro and of course FCP.
Last year, Telestream announced Pipeline, a network encoder/capture-device. It basically has an SDI input, SDI output, rs-422, port, and an ethernet port. Because it's on an ethernet network and any computer can use it--it doesn't need a host computer to run. It could be a good way to share a deck with SDI in/out between different computers. It also can layback to tape, but I'd like to see it as the capture and lay off are done through Telestream's software. A cool thing they were showing at NAB was the ability to start working on video while it was being captured. They demo'd an encode in Telestream Episode Pro of video that was being captured. HD support is supposed to be on the way for Pipeline. They also announced Pipeline support for Final Cut Server.
Finally in the "Shape of the Things to Come?" category, there's Maximum Throughput and their MAXedit systems. It's network and web-based editing. No beefy computer needed to edit your footage. Maximum Throughput hosts all of the heavy-lifting on the a server and then the editor is accessing all of the footage and the heavy-lifting through the network using any-old PC as a simple client. There's also a web version too for remote editing. Sounds cool. If you read my last post on Final Cut Server, I was bemoaning a crucial missing feature--editing. Last year Apple said that Final Cut Server clients could do some editing of footage on the server. But this year, not a mention of editing for Final Cut Server. I'm hoping that we'll see the feature in a year, but I'm worried that Apple is protecting sales of Final Cut Pro and Mac's. Network-based editing not only undercuts sales of licenses for expensive editing software, but also hardware-sales. With network-based editing, you don't have to worry about each editor having the latest and greatest Mac. Now, I don't know about you, but I've never heard about of Maximum Throughput. But I think they are really on to something.
There were a couple of post-production things that were interesting, but not earth shattering. Blackmagic Design added HDMI in and out to their $1000 Decklink HD Extreme card. They keep cramming more and more features into their cards. At this point AJA only matches Decklink's in and out on the aprrox. $3000 Io HD (which stole the show last year). I like AJA's gear but they aren't staying competitive feature-wise with Blackmagic. Heck, the analog-only and standard-def only IOLA is still selling for $1K.
Matrox came out with a something like a competitor to the Io HD. The MXO2 is portable I/O hardware for about $1600. Unlike the Io HD, you can do uncompressed HD if you want. But unlike the Io HD there's no built-in codec support. A great thing about the Io HD is that it will transcode to ProRes in the box. ProRes is pretty processor-intensive to transcode in real-time--for HD you need 4 Intel Xeon cores at a minimum. So I don't see how you could capture HD on a laptop with the MXO2. It hooks up to a tower through a PCI-E card and to MacBook Pro through Expresscard slot (so no support on iMac's or Macbooks.) It also is supposed to do up/down/cross-conversion and claims support for Adobe Premiere Pro and of course FCP.
Finally in the "Shape of the Things to Come?" category, there's Maximum Throughput and their MAXedit systems. It's network and web-based editing. No beefy computer needed to edit your footage. Maximum Throughput hosts all of the heavy-lifting on the a server and then the editor is accessing all of the footage and the heavy-lifting through the network using any-old PC as a simple client. There's also a web version too for remote editing. Sounds cool. If you read my last post on Final Cut Server, I was bemoaning a crucial missing feature--editing. Last year Apple said that Final Cut Server clients could do some editing of footage on the server. But this year, not a mention of editing for Final Cut Server. I'm hoping that we'll see the feature in a year, but I'm worried that Apple is protecting sales of Final Cut Pro and Mac's. Network-based editing not only undercuts sales of licenses for expensive editing software, but also hardware-sales. With network-based editing, you don't have to worry about each editor having the latest and greatest Mac. Now, I don't know about you, but I've never heard about of Maximum Throughput. But I think they are really on to something.
Labels:
Blackmagic,
Decklink,
Final Cut Server,
h.264,
Matrox MXO,
mxo2,
pipeline,
telestream
Monday, April 21, 2008
Final Cut Server
Seems like since it was first announced a year ago a few important features have been stripped from it. But I'm still pretty excited about this program. It seems like it adds a whole new powerful set of organizational tools for editors and producers. It could help in complex workflows or complex projects where multiple personnel are working with media. Apple is describing Final Cut Server as both an asset management application and an automation workflow program.
The asset management part of FC Server basically sets up a giant database that's a library for any and all media that you have on your Mac's--the library is in one spot (a Mac) but accessible to just about anyone on your network (including Windows users).
For editors, it's easy enough to get started with asset management. Tell it where you keep your Final Cut Pro projects are and FC Server will go through all of the clips in the projects. Any metadata associated with that clip in Final Cut Project will be copied over into FC Server. FC Server will also keep track when a clip is in more than one project--nice if you are ever wondering if you borrowed a clip from one project to put in another when it's time to clear old media off of drives. FC Server creates proxies versions of all this media--basically smaller versions of the original media. These proxies are easy to playback over a network and can even remain on the server when the original media has been deleted. So even if you can't keep all of the original media, you can still see a proxy on the server. Examples of formats for proxies are h.264 and Apple ProRes.
All of the data is fully searchable. Movies, graphics, most any file can be added in FC Server. You can also sort assets under productions. So once you do this, FC Server lets any client access any of this info. Up to 10 concurrent users for the $1K version and unlimited users for the $2K version. The server part of FC Server runs on Mac Pro's, MacBook Pro's, most iMac's, and Power Macs made within the last 3 years or so. But it looks like the client will run on just about any decent Mac and on Windows XP and Vista. That means a producer on a PC can browse through assets through the proxies. Also, FC Server requires Final Cut Studio 2.
In the pre-release info from last year, Apple said that some basic cutting could be done on the client. I can't seem to find anything about that on Apple's website now. I really hope they didn't pull that feature permanently. Editing on the FC Server client would be a great way for producers to be able to do simple assemblies of things. I hope a great feature didn't get cut because somebody at Apple complained that an editing feature would cut too much into sales of Final Cut Studio.
FC Server also tracks movies for approval and notes. Put a movie on the server, and FC Server can host it to any client. That way, a producer can quickly check something out on their PC without leaving their office and then post notes through the FC Server interface. Notes can be attached to a movie and attached at specific time codes. FC Server can also keep track of multiple versions of a project. So editors can make notes on a project, so other folks can know quickly what work has been done.
The automation workflow seems most helpful for encoding tasks. FC Server can watch a folder for any files that pop up. Once a file appears (e.g., after it's been exported from FCP), FC Server can begin encoding it through Compressor or run a script to send to, for example, send it to another app. If you are lucky to have enough to have access to a broadcast server, FC Server can send files there with some extra help available with Telestream's Episode. It's nice that all of these deliverables can be tracked in one place too. For example, I'd use it to track MPEG-2 files encoded for DVD's, which now are stored all over my hard drives.
Final Cut Server also helps you delete and backup media. For example you can delete media directly through FC Server, and it will tell you all of the projects that a clip is used in. It will help you archive media or move projects around the network. I'm not going to cover all of the features in this article. More good info on how you might use it at Apple's website.
OK, so here are some specific ideas about how Final Cut Server could help at Link.
EDITORS
As an editor, I'm always looking for media. Often, I'll need something on another system. Our current solution is for me to network to that computer. Then I have to figure out which project the media was stored in. I can often play back those files over the network. But if the other computer is older and/or busy with a big encode or render, then I might have some problems. With FC Server, I could search by file name, project name, reel # across anything that we've ever edited. Instead of trying to use another editor's computer as a file server, I can check out clips using FC Server's proxy files. So streamlined searching for media. Plus, the proxies can hang around even after the original media has been deleted. So it really opens up the amount of media that I can scan through without relying on tapes. Yippee!
Plus, FC Server sounds like it's easy to get up and running to catalog your existing media and projects. I just tell it where the Final Cut Pro projects are, and it start cataloging and making proxies. Now it's going to take a long time for the server to make all those proxies files--lots of encoding to h.264 to make proxies that are small enough to store and move quickly over the network. That's not going to happen overnight.
PRODUCERS
Producers will have the same ability to search and watch media as editors. Producers can watch through proxies video that's been captured. No more waiting to use a Beta deck or, even trickier at our facility, a DVCam deck. If the footage has been captured then producers have as much access to the media as editors.
Busy producers no longer have to come by the edit room to review materials. The editor drops an exported movie into FC Server, and FC Server creates a proxy. Then the producer can watch the proxy movie over the network. Notes are added through the FC Server client app and are stored on the server.
NEWS ARCHIVES
We have three large projects of monitoring international news. FC Server allows the option of adding proxy movies to a database of news. The FC Server interface allows for a centralized database that is connected directly to actual media. I could see news reports getting converted to h.264 proxy movies. A producer could quickly search for stories, then organize them into a project. This info can be seen by an editor or assistant who can begin converting the video to DV for editing in Final Cut Pro.
As far as I can tell, FC Server is being billed for in-house use I'm not sure how open it is to the internet. Maybe it's not internet-friendly or maybe Apple is being conservative about those features because of security concerns or the hassles of streaming media over the internet. To put that valuable of a server on the internet must carry some significant security risks (not that I'm a network and/or server expert.)
Like the simple editing feature, last year Apple was touting client access over the internet. Now, Final Cut Server doesn't say anything about the internet. I can only hope that internet access to the FC Server is coming in the future.
CAVEAT
OK, as an Apple fanboy, I'm usually onboard with Apple as soon as a product is announced (or even rumored.) But I've been burned before, and it's good to be wary of 1.0 products. Especially something this complex--a giant database with 1,000's of associated media files. I'll look forward to hearing some reports of folks who are actually using it, and even better see it in action. At this point, everything I know about Final Cut Server I've gleaned from their website. If you are interested in the product, I encourage you to check it out--there are some good video tutorials/demo movies there where you can see Final Cut Server in action.
Tuesday, April 1, 2008
Will Your Next Project Come from a $150 Camcorder?
"Flip Video Vlog: A Tale of Two Formats"
This guy literally taped a $150 Flip camcorder to a Canon XH-A1 and made the same exact film on both cameras. You can watch them back to back on his website. Basically, there's not too much difference when watching them in web video, and I couldn't hear much difference on my MacBook Pro's speakers (the audio for the Flip footage was recorded on an iPod using a microphone accessory.)
Now on a TV, I'm sure the difference would be readily apparent (not to mention the fact that the XH-A1 is a nice high-def camera and the Flip only records 640x480.) Oh and the Flip doesn't even have an optical zoom not to mention dozens of features that a $3000 camcorder has. But it does make you think about how cheaply and easily someone can make something now that is very watchable.
If you are interested more in reading more about the Flip camcorder, check out this review at the New York Times (registration req'd.) Their tech guy David Pogue shoots his video blog on the Flip phone.
Monday, March 17, 2008
Camera Blogwad
First Look: Sony HVR Series
Good info on the new Sony HVR-Z7 and HVR-S270 HDV cameras, as well as their companion deck, the HVR-M35. More detail on how Sony is doing progressive recording and playback with this gear.
CompactFlash Media Test Results
The HVR-Z7 and HVR-S270 will record HDV onto Compact Flash memory cards. But there are some performance issues, especially with cheaper cards. The test found delays in starting recording, dropouts, and even lockups.
Another review of the Sony PMW-EX1 at DV.com (registartion req'd.)
Three good posts from Adam Wilt at his new blog at the ProVideo Coalition:
Three three-letter cameras: EX1, F23, RED
The new Sony XDCAM EX1 and the $250,000 Sony HDCAM SR F23, versus the upstart Red.
Whither The HVX200?
Adam says: "Does the EX1 render the HVX200 obsolete? Don’t be too sure!"
2008 FAA rules on battery transport
Frankly, I don't understand all of this. But if you're a production person who travels on planes, then you should.
Labels:
24fps,
flash media,
HDV,
HVR-M35,
HVR-S270,
HVR-Z7,
pmw-ex1,
production,
Red,
XDCAM EX
Subscribe to:
Posts (Atom)