Showing posts with label video. Show all posts
Showing posts with label video. Show all posts

Thursday, June 20, 2013

Putting "Excellence" Into Perspective

One of the hard lessons learned while working on an episodic TV series is that there is neither the time nor the budget to make everything "perfect." It's been said that a show is never finished, just abandoned when you run out of time or money or both.

In a recent blog entry on the ProTools Expert site, editor Russ Hughes wrote, "Perfection is said to be as much a curse as it is a blessing, especially for creative types. We record, edit, mix audio or shoot, cut and grade video and often we just can’t leave it alone, or indeed be satisfied with the end results.

"Our clients often never know the lengths we go to when working on their projects; they certainly won’t pay for half the work we did in the name of perfection. It’s a difficult balance being a creative professional with a budget on the one hand and a personal desire to do the best we can on the other. It’s the little things that take a project from good to great, as I’ve already alluded to most of us seldom feel we have done that, despite our best efforts," he said. (http://bit.ly/11IioLh)

One of the areas that causes us the most grief is all those annoying, unwanted noises that plague our recordings, especially production tracks for film and TV shows.

As supervising sound editor on 66 episodes of Relic Hunter a few years back, I calibrated our edit rooms to 82 dBA SPL and worked on eliminating unwanted noise perceptible at that level, and not at a higher level, since 82 was the level set in the mix theatre at Deluxe. Of course you would hear every little glitch and tick if you were to boost the monitor pot, but the average audience won't, and we're not going for absolute perfection, just doing the appropriate job for our client, the production company, within the available time and budgetary constraints without killing ourselves.

One takeaway from this is that for picture work, calibrate your monitor level appropriate for the program type and then DON'T TOUCH IT AGAIN. That's how it's done on the mix stage. In fact, I've seen film consoles with the monitor pot removed. Seasoned mixers know when dialog is at the right level just using their ears and never looking at a meter. If you mix consistently to, say, feature film level of 85 dB SPL each and every day for as little as 4 weeks without ever changing the level, you'll soon train yourself to accurately gauge level, and you'll love the freedom this brings to the work, along with a concomitant lack of stress over little things that will never be heard in the intended listening environment.

This is also the antidote to level creep in music mixes, where the monitor level goes up as the hours stretch on, and ultimately changes the track's spectral content due to the way we perceive the amount of bass and treble at different listening levels (due to the equal-loudness contours). Try to avoid this temptation at all costs and leave the monitor pot alone. Failing that, calibrate it to something like 85 or 90 dBA SPL and remove the knob. Try it. You may like it.

Saturday, March 23, 2013

To Mix or Not to Mix? That is the Question

In the Monty Python film, The Meaning of Life, there is an unforgettable scene in an upscale French restaurant featuring this exchange between John Cleese’s fawning waiter and Terry Jones’ more-than-morbidly obese patron, Mr. Creosote:

“Today we have for appetizers moules mariniers, pâté de fois gras, beluga caviar, eggs benedict, tarte de poivre—that’s leek tart—frogs’ legs amandine, or oeufs de cailles—little quails’ eggs on a bed of pureéd mushrooms. It’s very delicate, very subtle.”

“I’ll have the lot,” replies Mr. Creosote.

“A wise choice, monsieur. And now, how would you like it served—all mixed up together in a bucket?”

“Yeah . . . with the eggs on top.”

While the humour in the scene is partly visual, the Pythons’ unique stamp of taking things to the brink of the ridiculous, and then vaulting over it, contrasts the list of the individual, highly refined dishes on the menu—representing the pinnacle of classic French cuisine—and the way these “very delicate, very subtle” elements are offered to the patron in a gross, vulgar, and repulsive manner, “all mixed up together in a bucket.”

Of course, no-one would willingly order a meal this way, much less be served in this fashion by a trained professional. Yet, that is much the way sound is often presented to theatre patrons: all mixed up together, with the eggs—or rather, the voices—on top. Occasionally delicate, not often subtle.

What is at issue here is the very notion of mixing, of combining disparate elements into a single channel (center cluster), two channels (L, R), a combination of these (L, C, R) or perhaps even on very rare occasions, a surround mix of four or five channels.

While mixing a large number of individual audio signals together into a few channels may be a very real requirement for the limited channel count of broadcast radio and television, as well as channel-restricted media such as consumer audio playback systems, this is certainly not the case for theatre and other staged entertainment. Until recently, however, theatrical and similar live events have largely been mixed in much the same way as broadcasts and recorded music.

This may be attributed in part to the large overlap in the designs of traditional recording, broadcast and live consoles; schools teaching audio (i.e., “recording schools”) continue to focus on the art and techniques of the mixdown; even one of the audio industry’s leading magazines proudly heralds the practice in its name, Mix. Originating in broadcast and recording sessions involving multiple microphones, and refined in multitrack recording studios producing mono or stereo masters, mixing has become entrenched in the industry and in the minds of many who dream of working in it, to the point where it’s almost as if no other way of working with sound is even remotely conceivable.

A great many shows are presented as if the audience were listening to a gargantuan stereo system, with massive line arrays hung to the left and right of the stage. Now this might not be inappropriate for a touring band well known from its recordings or for a big, dynamic rock musical where the design calls for a larger-than-life aspect.

Even so, many of the blockbuster musicals from the past quarter century benefited greatly from the creativity of such esteemed sound designers as Olivier Award winner Mick Potter, who, in the quest for more natural sound, have opted for separate vocal and orchestra mixes, striving simultaneously for clarity in the voices and power in the orchestra. Moreover, two voice mixes are sometimes derived, with one going to a duplicate set of loudspeakers in an A-B configuration pioneered in 1988 by Martin Levan for Aspects of Love, to eliminate electrical summing of mic signals and the ensuing phase problems that arise when performers are in close proximity to each other’s microphones.

For other production styles, however, an approach based on mixing may not be the most appropriate technique for conveying the nuances of theatre—including musical theatre, where sound systems have become ubiquitous—if the purpose of sound reinforcement is to allow every performer’s voice to be heard as it would unamplified in an optimum seat.

Wednesday, February 29, 2012

Leap year and drop-frame time code are conceptually the same

For those in the media production industries, February 29th is a good day to revisit drop-frame SMPTE time code, because both leap year and drop-frame time code came into being for the sole purpose of reconciling two different time bases on which we do things with mundane regularity.

Take the calendar first: our calendar simply charts the sequence of the individual days that comprise a single year. The day is based, of course, on a single rotation of the earth on its axis, whereas the year is based on a single revolution of the earth around the sun. Rotation and revolution are the two different time bases on which our calendar is constructed.

Since it takes about 365.25 days for the earth to revolve around the sun, we collect four of those quarter days and add them together into a single day—February 29—that appears on the calendar once every four years.

We do this because there's no such thing as a quarter-day: you couldn't start a New Year at 6:00 a.m. After all, a day is a day and cannot be partitioned like that. It's an integer.

It's important to see that the concept of the yearly calendar comprises 366 days—February 29 is not imaginary. But rather than adding it every four years, what we are really doing is dropping it from the calendar in every year that is not a multiple of four. If the year is not divisible by 4, then we drop February 29 from our count of days in that year.

It's exactly the same with drop-frame time code, where frames are analogous to days, and hours to years. A video frame is a whole thing, an integer, and we count 30 of them in one second. But the rate at which they proceed is a bit less than 30 per second, more like 29.97 frames per second.

This is the same sort of fractional discrepancy that exists in the annual rate of 365.25 days per year.

We deal with it the same way, by dropping 2 frames from the count at the very beginning of every minute that is not a multiple of 10. In that first second, there are only 28 frames.

So frames 00 and 01 simply do not exist at the beginning of every minute of time code that doesn't have a zero at the end of it (10, 20, 30, 40, 50, and 00 minutes being the exceptions), just as February 29 does not exist in any year that can't be divided by 4. It's as simple as that.

Why go to the bother of doing this? For the calendar, it's long been considered important that the seasons start at roughly the same time every year: if we didn't have February 29 as a corrective, then the beginning of Spring, for example, would progress steadily back through February, January, December, and so on as the years rolled by.

For producers, it's important that the time displayed by your time code reader agrees with the real-time clock on the control room wall. Without drop-frame time code, a one-hour program as measured by your time code would actually run 3 seconds and 18 frames too long, and that would wreak havoc with broadcast schedules.

Note that what we are NOT doing is cutting out frames from our program and leaving them on the cutting room floor, as some of my former students at the Toronto Film School used to believe. Those "dropped" frames are simply never there in the first place, just as February 29 will not "be there" in 2013, 2014, and 2015. The calendar works as "drop-day" code.

The takeaway from this blog entry is that if you can intuitively grasp the concept of leap year, then you've already got the essence of drop-frame time code. Conceptually, they are one and the same.

Sunday, May 8, 2011

Message to You by Catherine Bacque

Here's a track co-written with Catherine Bacque and produced for her upcoming release, inspired by the script for the short film "More Than Words," in pre-production by Raindance Canada's James Cooper, screenplay by Yaw Attuah and Zachary Herrmann. (Members of our creative team are featured in this slide-show video.)

Tuesday, September 14, 2010

Plan ahead for split-track recording when making documentary videos

A wedding videographer came to me last week with an audio problem in a wedding video he was editing. Just before their first dance as husband and wife, the happy couple had taken to the dance floor with handheld mics to sing a torch ballad over a karaoke track. A huge crowd-pleaser, this would have been a "highlight" of the wedding video. Unfortunately, on tape the backing track was so loud that the lyrics were completely unintelligible—in fact, you couldn't hear the man's voice at all. Could I save the track? And his reputation?

In a nutshell, no, not this time. The voices were so faint in the two-track mono mix and the electric piano so loud  that no amount of EQ could bring them forward. The client even sent me the original wav file of the karoake track, hoping that if I mixed it out of phase (reversed polarity) with the botched recording, it would cancel out some of the music track, leaving the voices more intelligible.

For the cancellation trick to work, the music in the end recording would have to be almost identical to the original karoake file. It wasn't: the karaoke was in stereo not mono, and it ran slightly faster than in the final recording.

Moreover, there was tons of ambience in the duet recording, because the karaoke playback was picked up not only directly from the audio mixer at line level, but also from the loudspeakers in the hall by the singers' microphones. So the final recording is muddied and colored by the reproduced sound from the loudspeakers and all sorts of reflection from the walls and floor, which, of course, is not present in the original track. 

This also partially explains why the music was so much louder than the vocals: the music was being picked up twice, once as a direct feed, and secondly from the singers' microphones. 

What should the operator have done? Since the goal was apparently not to make a stereo recording—no attempt was made to preserve the original left-right stereo of the instrumental track in making a two-track mono recording—the operator should have fed both sides of the original instrumental track to track 1 of the camera, and the microphones to track 2.

This simple split-track technique would have allowed for the voices to be properly balanced with the music in post production. It's done all the time in recording dialog for films and TV on 2 tracks, especially when there is a mic on a boom or fishpole, and the actors are wearing lavs. Boom goes to track 1, lavs to track 2. 

When shouting and screaming are anticipated in a scene (perhaps not at a wedding), the same audio is printed on both tracks but at a reduced level—say, 10 dB lower than normal—on track 2. So if the scream is distorted on track 1, the sound editor can lay up the lower, undistorted scream from track 2, and match the levels during mixdown.

It's simple and it works. It just requires a little planning ahead, but when you only have one shot at it, split-track recording can save the day. And your reputation.

Wednesday, May 19, 2010

Studio Fatigue

Fatigue can creep up on you in unexpected ways. I had been in the edit room for over 24 hours, cutting sound for a TV show and a feature, both on a tight deadline. The scene I was working on was a 3-second establishing shot, and included streetcars passing each other. I was trying to sync the Doppler pitch shift of the sound effect (streetcar passing at 40 km/h) with the moving image on the screen, but couldn't get it right—when it's right, a kind of lock happens in the mind and the action comes together almost magically as a single event, and not as separate visual and aural cues. No matter how I tried, the sound was always out of sync with the picture, so I decided a break was in order, and took a walk up to Queen and John to get a chocolate bar and a coffee.

As I was standing on the corner waiting for the light to change, a streetcar passed by. And it was out of sync. I was shocked. The sound and image did not coalesce as one to me. I realized that the problem in the edit room was me, that no matter how long I tried to fit the sound to picture, I wouldn't be able to get it right that night. I was just too fatigued from too many long days hunched over  a monitor. And I realized that if I did get it to look "right" that night, I'd probably have to redo it all in the morning anyway.

After a good night's sleep, I went in the next morning, put up the scene, and had it looking and sounding right in less than 5 minutes. Sometimes the most efficient way to get things done right is to stop trying, take a break, and come back at it later—especially when you've been at it longer than usual.