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.
Showing posts with label ProTools. Show all posts
Showing posts with label ProTools. Show all posts
Thursday, June 20, 2013
Putting "Excellence" Into Perspective
Labels:
level,
Logic,
meter,
mixing,
music,
ProTools,
recording,
sound design,
sound edit,
soundtrack,
studio,
video
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.
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.
Wednesday, January 18, 2012
MIDI Orchestration
I've just finished a first read-through of the 4th edition of Paul Gilreath's The Guide to MIDI Orchestration, published by Focal Press. Coming in at 600 pages, it's a pretty thorough introduction to the subject of orchestrating a musical composition using MIDI-based equipment and instrument sample libraries.
Several topics of interest to non-MIDI orchestrators and project studio folks alike are covered here, including instrument ranges and playing techniques, notation, voice leading, distribution of melodies and accompaniments to different instruments in the various sections, combining instruments to create different sounds, and achieving specific moods with orchestrations.
For the MIDI producer, there's a wealth of information on equipment, software, choosing sample libraries, and sequencing strings, woodwinds, brass, percussion, piano, harp and voices.
The author illustrates portions of the text with screenshots from his favourite digital audio workstations: Cubase/Nuendo, Logic, Digital Performer and Sonar. Unfortunately, Gilreath dismisses ProTools, saying it's "still working to catch up" in this area, which is too bad, given its market penetration together with the strides that ProTools has made in the whole area of MIDI sequencing and sampling since version 8 was released at the end of 2008.
In any event, readers working with ProTools can easily adapt the material to their way of working, which, in most respects, is not too different from the others.
Supplementary material is available online at www.midi-orchestration.com, including reviews of several good instrument sample libraries, supplementary tutorials, and audio examples, but you have to sign in to access it.
Much of this material—including several full-length, uncut chapters—is still freely available for download as a single zip file from Focal Press at www.focalpress.com/midiorchestrationfiles.aspx.
The book is a terrific reference, and it's refreshing that the author combines description and prescription in almost equal amounts, which is a rare feat. Anyone looking for a grounding in MIDI orchestration would do well to own this book, and will check in with it on a regular basis, if not frequently. It's a beautiful volume, well designed and easy to read, with a crisp and clear layout, and it should be on every music producer's reference shelf.
My criticisms are few. There are numerous errors relating to missing or misplaced illustrations or examples, including a missing reference section with bibliographical apparatus that the author himself refers to twice yet, strangely, is nowhere to be found!
There are also too many proofreading errors, not many of them spelling mistakes, which leads me to believe that spell-check may have served as a convenient substitute for a thorough proofing. This is a tad disappointing in a 600-page book priced at US$82.50 ($86.50 Canadian).
Fortunately, these shortcomings are overshadowed by the author's monumental achievement in turning out what was surely the crowning achievement of his career as a composer for film and television. May his new life as a dentist in Atlanta be as fulfilling!
The Guide to MIDI Orchestration, 4th Edition, by Paul Gilreath, published by Focal Press, 2010. ISBN: 978-0-240-81413-1
Several topics of interest to non-MIDI orchestrators and project studio folks alike are covered here, including instrument ranges and playing techniques, notation, voice leading, distribution of melodies and accompaniments to different instruments in the various sections, combining instruments to create different sounds, and achieving specific moods with orchestrations.
For the MIDI producer, there's a wealth of information on equipment, software, choosing sample libraries, and sequencing strings, woodwinds, brass, percussion, piano, harp and voices.
The author illustrates portions of the text with screenshots from his favourite digital audio workstations: Cubase/Nuendo, Logic, Digital Performer and Sonar. Unfortunately, Gilreath dismisses ProTools, saying it's "still working to catch up" in this area, which is too bad, given its market penetration together with the strides that ProTools has made in the whole area of MIDI sequencing and sampling since version 8 was released at the end of 2008.
In any event, readers working with ProTools can easily adapt the material to their way of working, which, in most respects, is not too different from the others.
Supplementary material is available online at www.midi-orchestration.com, including reviews of several good instrument sample libraries, supplementary tutorials, and audio examples, but you have to sign in to access it.
Much of this material—including several full-length, uncut chapters—is still freely available for download as a single zip file from Focal Press at www.focalpress.com/midiorchestrationfiles.aspx.
The book is a terrific reference, and it's refreshing that the author combines description and prescription in almost equal amounts, which is a rare feat. Anyone looking for a grounding in MIDI orchestration would do well to own this book, and will check in with it on a regular basis, if not frequently. It's a beautiful volume, well designed and easy to read, with a crisp and clear layout, and it should be on every music producer's reference shelf.
My criticisms are few. There are numerous errors relating to missing or misplaced illustrations or examples, including a missing reference section with bibliographical apparatus that the author himself refers to twice yet, strangely, is nowhere to be found!
There are also too many proofreading errors, not many of them spelling mistakes, which leads me to believe that spell-check may have served as a convenient substitute for a thorough proofing. This is a tad disappointing in a 600-page book priced at US$82.50 ($86.50 Canadian).
Fortunately, these shortcomings are overshadowed by the author's monumental achievement in turning out what was surely the crowning achievement of his career as a composer for film and television. May his new life as a dentist in Atlanta be as fulfilling!
The Guide to MIDI Orchestration, 4th Edition, by Paul Gilreath, published by Focal Press, 2010. ISBN: 978-0-240-81413-1
Labels:
Cubase,
Digital Performer,
film music,
Gilreath,
Logic,
MIDI,
music,
Nuendo,
orchestration,
ProTools,
recording,
scoring,
Sonar,
studio
Friday, November 19, 2010
When a studio's clients want to leave—and take you with them
As a freelance recording engineer, what do you do when artists approach you directly and ask you to produce their recordings in your own right, after you've made their acquantance in someone else's studio and on someone else's dime?
This is a situation I've found myself in a few times over the years. On two occasions, clients told me that the studio we met in didn't sound good and wanted to go elsewhere—with me—to record in the future. In another case, a performer said that the producer was too hyper, "not laid back enough," and could we record somewhere else where the atmosphere was more relaxed. Similarly, in another instance, an artist complained of being stressed out in the presence of the studio owner, and consequently couldn't turn in a first-rate performance.
When this started happening, I thought it best to speak frankly with the producer or studio owner, one of whom told me that none of his other freelancers would ever dream of "poaching" his clients, whose business he had worked diligently to acquire over months and years.
I pointed out that I wasn't in the habit of poaching clients—the industry is far too small and such behaviour is ruinous to one's reputation. I suggested that those who were dissatisfied were eventually going to go elsewhere anyway, and rather than lose their business entirely, why not work out a finder's fee arrangement for him—call it a commission or kick-back if you will—so that his role in securing the business was recognized tangibly.
He rejected this suggestion out of hand, insisting they were HIS clients, and that I should endeavour to convince them to stay despite their expressed concerns.
Well, no one is automatically entitled to a client's business for life, and as the saying goes, whatever it took to get you here isn't enough to keep you here—you're only as good as your last gig. Clients are free to go where they will.
Knowing that some clients may approach competent staff members directly in an attempt to secure their services at more favourable rates, some employers insist that their employees sign a non-compete agreement.
But this doesn't wash with many freelancers, something studio owners should bear in mind when building a business based on out-sourcing the work. It's a two-edged sword—freelancers are not employees, and do not enjoy the same benefits and security that employees do, and turnabout is fair play.
Some savvy studio owners offer freelance engineers a piece of the action—participation in the business akin to stock options—in order to make it more attractive for freelancers to discourage the studio's clients from going elsewhere. I have suggested this on several occasions, with mixed results.
In the end, it's difficult, if not impossible, to maintain a good working relationship with a studio when its clients become dissatisfied and want you to take them elsewhere to record. But for a studio owner, recognizing that you're in a business relationship with freelance engineers, and not a social one, is a necessary first step in arriving at a business solution to what might otherwise become a thorny personal problem.
For a studio owner, it should serve as a wake-up call that all is not as it should be when clients express their dissatisfaction to a sympathetic ear behind the board. The solution may be as simple as staying away from the session, however tempting it may be for a studio owner to participate in the proceedings. From a "strictly-business" perspective, this is the most straightforward solution.
In the case of a home or project studio, this is not as easily accomplished, and sharing a business with a home may open up the studio operation to a level of personal micromanagement that may be detrimental to its success, exposing clients to everything from a simple request to remove their shoes, to disagreeable cooking odors emanating from the kitchen.
When home studio rates are well below prevailing commercial rates, such irritants may well be tolerable, but if home studio owners set their rates equivalent to—or higher than—commercial operations, they may need to adjust their expectations and behaviour accordingly.
This is a situation I've found myself in a few times over the years. On two occasions, clients told me that the studio we met in didn't sound good and wanted to go elsewhere—with me—to record in the future. In another case, a performer said that the producer was too hyper, "not laid back enough," and could we record somewhere else where the atmosphere was more relaxed. Similarly, in another instance, an artist complained of being stressed out in the presence of the studio owner, and consequently couldn't turn in a first-rate performance.
When this started happening, I thought it best to speak frankly with the producer or studio owner, one of whom told me that none of his other freelancers would ever dream of "poaching" his clients, whose business he had worked diligently to acquire over months and years.
I pointed out that I wasn't in the habit of poaching clients—the industry is far too small and such behaviour is ruinous to one's reputation. I suggested that those who were dissatisfied were eventually going to go elsewhere anyway, and rather than lose their business entirely, why not work out a finder's fee arrangement for him—call it a commission or kick-back if you will—so that his role in securing the business was recognized tangibly.
He rejected this suggestion out of hand, insisting they were HIS clients, and that I should endeavour to convince them to stay despite their expressed concerns.
Well, no one is automatically entitled to a client's business for life, and as the saying goes, whatever it took to get you here isn't enough to keep you here—you're only as good as your last gig. Clients are free to go where they will.
Knowing that some clients may approach competent staff members directly in an attempt to secure their services at more favourable rates, some employers insist that their employees sign a non-compete agreement.
But this doesn't wash with many freelancers, something studio owners should bear in mind when building a business based on out-sourcing the work. It's a two-edged sword—freelancers are not employees, and do not enjoy the same benefits and security that employees do, and turnabout is fair play.
Some savvy studio owners offer freelance engineers a piece of the action—participation in the business akin to stock options—in order to make it more attractive for freelancers to discourage the studio's clients from going elsewhere. I have suggested this on several occasions, with mixed results.
In the end, it's difficult, if not impossible, to maintain a good working relationship with a studio when its clients become dissatisfied and want you to take them elsewhere to record. But for a studio owner, recognizing that you're in a business relationship with freelance engineers, and not a social one, is a necessary first step in arriving at a business solution to what might otherwise become a thorny personal problem.
For a studio owner, it should serve as a wake-up call that all is not as it should be when clients express their dissatisfaction to a sympathetic ear behind the board. The solution may be as simple as staying away from the session, however tempting it may be for a studio owner to participate in the proceedings. From a "strictly-business" perspective, this is the most straightforward solution.
In the case of a home or project studio, this is not as easily accomplished, and sharing a business with a home may open up the studio operation to a level of personal micromanagement that may be detrimental to its success, exposing clients to everything from a simple request to remove their shoes, to disagreeable cooking odors emanating from the kitchen.
When home studio rates are well below prevailing commercial rates, such irritants may well be tolerable, but if home studio owners set their rates equivalent to—or higher than—commercial operations, they may need to adjust their expectations and behaviour accordingly.
Tuesday, October 26, 2010
How much headroom do you need when recording? Part 1
Some years back, I recorded a Stravinsky symphonic work to analog tape running at 15 ips half-track, dbx type 1. When I transferred the recording to digital for archiving, the big orchestral bass drum gave me problems. Had I been recording to digital on location, it would have been a mess: I would have needed to set 0 VU at -25 dBFS to keep the digital meter out of the red. That's how much energy the bass drum was putting out.
Standards organizations specify how much headroom should be available above operating level (0 VU) in the digital domain. In my experience, the European EBU standard of 0 VU = -18 dBFS does not afford nearly enough headroom, and neither does the North American SMPTE standard of -20 dBFS. Granted, these were "reasonable" compromises in the days of 16-bit technology, when 93dB dynamic range was about all you could expect to get in the real world (as opposed to the theoretical 96 dB, calculated at 6 dB per bit).
Analog headroom of 24 dB—which many manufacturers of professional grade equipment achieve with maximum output levels of +28 dBu (ref 0 VU = +4 dBu)—should be considered the minimum standard during production. Even then, the Stravinsky would have been into overload by about 1 dB, so you might occasionally require even more headroom.
In our current 24-bit world, I would say that it's not unreasonable to demand 28 dB headroom when recording wide dynamic range program material, such as symphonic works. It still gives you a working signal-to-noise ratio of better than 100 dB, and 28 dB of headroom includes a small comfort margin so you can enjoy the program without stressing over the levels during recording, knowing that you will most likely never go into the red.
Incidentally, I see a lot of "analog channels" being marketed as quality front end processing for recording into ProTools and other DAWs. Many of these boxes include a compressor after the mic preamp, probably because few recordists stop to consider how much analog headroom is really needed in a given situation. Instead of backing the level off to allow for enough headroom without compression, they tend to run the ProTools meters high up into the yellow, recording with compression on individual tracks at 24-bit resolution. It's as if a little bit of green flickering at the low end of the meter must be avoided at all costs. This is foolishness.
24-bit technology allows you to record at a moderate level with 28 dB of headroom and still accumulate no perceptible noise in the recording. Save the compression for mixing and mastering, when it becomes a creative tool rather than a protective device. And then, whatever else you do, don't normalize! Oversampling digital-to-analog converters, which are pretty much the norm these days, routinely create signal peaks greater than 0 dBFS between samples that measure 0 dBFS on disc. But that's another subject for another time.
Standards organizations specify how much headroom should be available above operating level (0 VU) in the digital domain. In my experience, the European EBU standard of 0 VU = -18 dBFS does not afford nearly enough headroom, and neither does the North American SMPTE standard of -20 dBFS. Granted, these were "reasonable" compromises in the days of 16-bit technology, when 93dB dynamic range was about all you could expect to get in the real world (as opposed to the theoretical 96 dB, calculated at 6 dB per bit).
Analog headroom of 24 dB—which many manufacturers of professional grade equipment achieve with maximum output levels of +28 dBu (ref 0 VU = +4 dBu)—should be considered the minimum standard during production. Even then, the Stravinsky would have been into overload by about 1 dB, so you might occasionally require even more headroom.
In our current 24-bit world, I would say that it's not unreasonable to demand 28 dB headroom when recording wide dynamic range program material, such as symphonic works. It still gives you a working signal-to-noise ratio of better than 100 dB, and 28 dB of headroom includes a small comfort margin so you can enjoy the program without stressing over the levels during recording, knowing that you will most likely never go into the red.
Incidentally, I see a lot of "analog channels" being marketed as quality front end processing for recording into ProTools and other DAWs. Many of these boxes include a compressor after the mic preamp, probably because few recordists stop to consider how much analog headroom is really needed in a given situation. Instead of backing the level off to allow for enough headroom without compression, they tend to run the ProTools meters high up into the yellow, recording with compression on individual tracks at 24-bit resolution. It's as if a little bit of green flickering at the low end of the meter must be avoided at all costs. This is foolishness.
24-bit technology allows you to record at a moderate level with 28 dB of headroom and still accumulate no perceptible noise in the recording. Save the compression for mixing and mastering, when it becomes a creative tool rather than a protective device. And then, whatever else you do, don't normalize! Oversampling digital-to-analog converters, which are pretty much the norm these days, routinely create signal peaks greater than 0 dBFS between samples that measure 0 dBFS on disc. But that's another subject for another time.
Labels:
0 dBFS,
16-bit,
24-bit,
analog channel,
audio,
compression,
compressor,
digital,
distortion,
dynamic range,
headroom,
level,
meter,
ProTools,
recording
Subscribe to:
Posts (Atom)
