Become a Site Supporter and Never see Ads again!

Author Topic: Matrix in post best practice workflow  (Read 7078 times)

0 Members and 1 Guest are viewing this topic.

Online tim in jersey

  • Site Supporter
  • Trade Count: (8)
  • Needs to get out more...
  • *
  • Posts: 3795
  • Gender: Male
Matrix in post best practice workflow
« on: December 21, 2011, 11:37:52 PM »
n00b to the matrix in post thing...

Scenario:

Deck 1 is a SBD feed, Deck 2 is my aud recording. Neither is jammed to timecode. I mix/correct for drift in post using Vegas.

I run levels on each very conservatively. About -9 to -6 dbfs, peak.

Should I normalize/amplify each file prior to bringing it in to the DAW or just mix and then amplify?



Offline justink

  • Trade Count: (4)
  • Taperssection All-Star
  • ****
  • Posts: 1973
  • Gender: Male
Re: Matrix in post best practice workflow
« Reply #1 on: December 21, 2011, 11:44:41 PM »
i amplify both sources to about -5 or -4 db (for a 50/50 mix).  then align.  then mix/render (the joining will amplify some waves).

there's a great thread about this using audacity, pretty easy.
Mics:
DPA 4023 (Cardioid)
DPA 4028 (Subcardioid)
DPA 4018V (Supercardioid)
Earthworks TC25 (Omni) 

Pres and A/D's:
Grace Design Lunatec V3 (Oade ACM)
Edirol UA-5 (bm2p+ Mod)

Recorders:
Sound Devices MixPre10 II
Edirol R-44 (Oade CM)
Sony PCM‑M10

Offline page

  • Trade Count: (25)
  • Needs to get out more...
  • *****
  • Posts: 8388
  • Gender: Male
  • #TeamRetired
Re: Matrix in post best practice workflow
« Reply #2 on: December 22, 2011, 12:45:41 AM »
I use the following:

1) Align via preferred method (stretch in Vegas/Reaper or time-align in Audacity)
2) Determine what I like about either source (sbd has less reverberation in the 1-3khz range, aud has a warm gooey bass, etc), and EQ to bring out what I like about both, maybe a net change of 2db tops, just enough to nudge it in a direction. Don't overdo it.
3) Make sure the peaks in either are at least -6 or lower.
3.5) double check alignment.
4) Render to 2ch. (Assuming a render is required to apply editing to both sources equally)
5) EQ/process anything else.
6) Amplify the remaining db and do any limiting and dither.

I used to keep the peaks between -3 and -6 which mathematically should bring your render to just under 0, but I kept having the occasional overage and having to redo the render so I figured the additional few DB of amping in Ozone or whatever is clean enough I'm not worried about it. Make sure to double check your alignment, I prefer to check mine now over the course of a couple of listening sessions and in both loud and quiet sections throughout the recording since non-clocked sources can drift at different speeds (ever so slightly which is a pisser but usually not much of a problem). I don't think I've forgotten anything....
"This is a common practice we have on the bus; debating facts that we could easily find through printed material. It's like, how far is it today? I think it's four hours, and someone else comes in at 11 hours, and well, then we'll... just... talk about it..." - Jeb Puryear

"Nostalgia ain't what it used to be." - Jim Williams

Offline justink

  • Trade Count: (4)
  • Taperssection All-Star
  • ****
  • Posts: 1973
  • Gender: Male
Re: Matrix in post best practice workflow
« Reply #3 on: December 22, 2011, 12:52:01 AM »
I use the following:

1) Align via preferred method (stretch in Vegas/Reaper or time-align in Audacity)
2) Determine what I like about either source (sbd has less reverberation in the 1-3khz range, aud has a warm gooey bass, etc), and EQ to bring out what I like about both, maybe a net change of 2db tops, just enough to nudge it in a direction. Don't overdo it.
3) Make sure the peaks in either are at least -6 or lower.
3.5) double check alignment.
4) Render to 2ch. (Assuming a render is required to apply editing to both sources equally)
5) EQ/process anything else.
6) Amplify the remaining db and do any limiting and dither.

I used to keep the peaks between -3 and -6 which mathematically should bring your render to just under 0, but I kept having the occasional overage and having to redo the render so I figured the additional few DB of amping in Ozone or whatever is clean enough I'm not worried about it. Make sure to double check your alignment, I prefer to check mine now over the course of a couple of listening sessions and in both loud and quiet sections throughout the recording since non-clocked sources can drift at different speeds (ever so slightly which is a pisser but usually not much of a problem). I don't think I've forgotten anything....

he said it best.
Mics:
DPA 4023 (Cardioid)
DPA 4028 (Subcardioid)
DPA 4018V (Supercardioid)
Earthworks TC25 (Omni) 

Pres and A/D's:
Grace Design Lunatec V3 (Oade ACM)
Edirol UA-5 (bm2p+ Mod)

Recorders:
Sound Devices MixPre10 II
Edirol R-44 (Oade CM)
Sony PCM‑M10

runonce

  • Guest
  • Trade Count: (0)
Re: Matrix in post best practice workflow
« Reply #4 on: December 22, 2011, 07:45:46 AM »
n00b to the matrix in post thing...

Scenario:

Deck 1 is a SBD feed, Deck 2 is my aud recording. Neither is jammed to timecode. I mix/correct for drift in post using Vegas.

I run levels on each very conservatively. About -9 to -6 dbfs, peak.

Should I normalize/amplify each file prior to bringing it in to the DAW or just mix and then amplify?


If they are 16 bit sources - you might want to skip normalization until the end (as recommened by page in the last post) - You're going to need about -6db of extra headroom to handle the higher peaks that result when you combine sources.

Online tim in jersey

  • Site Supporter
  • Trade Count: (8)
  • Needs to get out more...
  • *
  • Posts: 3795
  • Gender: Male
Re: Matrix in post best practice workflow
« Reply #5 on: December 22, 2011, 10:51:18 AM »
That answers my questions. Thank you, gentlemen.

Offline Walstib62

  • Site Supporter
  • Trade Count: (32)
  • Needs to get out more...
  • *
  • Posts: 3266
  • Gender: Male
Re: Matrix in post best practice workflow
« Reply #6 on: December 23, 2011, 11:40:36 AM »
I could be totally wrong on this, and if so, please someone let me know. But, I have always imported the tracks and normalized them first. The reason being that normalizing removes any possible dc offset. That way, all tracks are nulled to 0 offset prior to any other processing. To make things easier level-wise, I normalize to -6bB. Then, when the tracks are combined, the result is always a little below 0 without going over.

Offline justink

  • Trade Count: (4)
  • Taperssection All-Star
  • ****
  • Posts: 1973
  • Gender: Male
Re: Matrix in post best practice workflow
« Reply #7 on: December 23, 2011, 01:00:08 PM »
I could be totally wrong on this, and if so, please someone let me know. But, I have always imported the tracks and normalized them first. The reason being that normalizing removes any possible dc offset. That way, all tracks are nulled to 0 offset prior to any other processing. To make things easier level-wise, I normalize to -6bB. Then, when the tracks are combined, the result is always a little below 0 without going over.

nothing wrong with that.
Mics:
DPA 4023 (Cardioid)
DPA 4028 (Subcardioid)
DPA 4018V (Supercardioid)
Earthworks TC25 (Omni) 

Pres and A/D's:
Grace Design Lunatec V3 (Oade ACM)
Edirol UA-5 (bm2p+ Mod)

Recorders:
Sound Devices MixPre10 II
Edirol R-44 (Oade CM)
Sony PCM‑M10

Offline page

  • Trade Count: (25)
  • Needs to get out more...
  • *****
  • Posts: 8388
  • Gender: Male
  • #TeamRetired
Re: Matrix in post best practice workflow
« Reply #8 on: December 23, 2011, 02:34:45 PM »
I could be totally wrong on this, and if so, please someone let me know. But, I have always imported the tracks and normalized them first. The reason being that normalizing removes any possible dc offset.

I just checked in Audacity and there is an option to remove the offset when you do it (news to me). I don't recall there being one in reaper, and I know in RX it's a separate function. In Ozone, they have it chained to occur at the end before dither or the output gain structure.

but you bring up a good point; do you strip it before you do anything or at the end? All of my current gear produces so little offset naturally that I haven't had much reason to do it any earlier in the chain, but from a best practices standpoint, it's a valid question.
"This is a common practice we have on the bus; debating facts that we could easily find through printed material. It's like, how far is it today? I think it's four hours, and someone else comes in at 11 hours, and well, then we'll... just... talk about it..." - Jeb Puryear

"Nostalgia ain't what it used to be." - Jim Williams

Offline morst

  • I think I found an error on the internet; #UnionStrong
  • Trade Count: (2)
  • Needs to get out more...
  • *****
  • Posts: 5969
Re: Matrix in post best practice workflow
« Reply #9 on: January 01, 2012, 01:56:02 PM »
I could be totally wrong on this, and if so, please someone let me know. But, I have always imported the tracks and normalized them first. The reason being that normalizing removes any possible dc offset. That way, all tracks are nulled to 0 offset prior to any other processing.
I think you might be totally wrong. Normalization just brings up overall output levels, DC Offset Removal is a separate function. Unless you are using some offset-correcting normalizer plugin?

You'll get WAY better results mixing 24-bit signals if you can master that way...
https://toad.social/@morst spoutible.com/morst post.news/@acffhmorst

Offline kubacheck

  • Trade Count: (3)
  • Needs to get out more...
  • *****
  • Posts: 2244
    • My Flickr site
Re: Matrix in post best practice workflow
« Reply #10 on: January 01, 2012, 02:40:48 PM »
I could be totally wrong on this, and if so, please someone let me know. But, I have always imported the tracks and normalized them first. The reason being that normalizing removes any possible dc offset. That way, all tracks are nulled to 0 offset prior to any other processing.
I think you might be totally wrong. Normalization just brings up overall output levels, DC Offset Removal is a separate function. Unless you are using some offset-correcting normalizer plugin?

You'll get WAY better results mixing 24-bit signals if you can master that way...

the one time I tried to do a matrix in Vegas, it wouldn't let me render the matrix of the two 24 bit sources as a resultant 24 bit output file, it automatically dithered it down to 16/44.1.... if there was a way to keep it at 24/48, I couldn't figure it out....

Offline morst

  • I think I found an error on the internet; #UnionStrong
  • Trade Count: (2)
  • Needs to get out more...
  • *****
  • Posts: 5969
Re: Matrix in post best practice workflow
« Reply #11 on: January 01, 2012, 04:52:48 PM »
it automatically dithered it down to 16/44.1.... if there was a way to keep it at 24/48, I couldn't figure it out....
If that's really true, I would advise you to find something other than Vegas to do your work. No sense in wrecking your bits like it's the only option!!?
https://toad.social/@morst spoutible.com/morst post.news/@acffhmorst

Offline kubacheck

  • Trade Count: (3)
  • Needs to get out more...
  • *****
  • Posts: 2244
    • My Flickr site
Re: Matrix in post best practice workflow
« Reply #12 on: January 01, 2012, 05:35:43 PM »
it automatically dithered it down to 16/44.1.... if there was a way to keep it at 24/48, I couldn't figure it out....
If that's really true, I would advise you to find something other than Vegas to do your work. No sense in wrecking your bits like it's the only option!!?

its been a couple years, but as I recall, the pull down menus only went up to 16 and 44.1, I could've rendered at lower bit rates, but 16/44.1 were the highest quality values I could select..... perhaps that was specific to the version of Vegas I was using, I think it was Vegas 8.....

Offline beatkilla

  • Trade Count: (70)
  • Needs to get out more...
  • *****
  • Posts: 2114
  • Gender: Male
Re: Matrix in post best practice workflow
« Reply #13 on: January 01, 2012, 05:44:23 PM »
Thats definetely not true for Sony Vegas. You can work with and render up to 24bit 192khz.      I just checked and you must have the lite version of vegas and that one goes no higher than 16  48.
« Last Edit: January 01, 2012, 05:53:34 PM by beatkilla »

Offline kubacheck

  • Trade Count: (3)
  • Needs to get out more...
  • *****
  • Posts: 2244
    • My Flickr site
Re: Matrix in post best practice workflow
« Reply #14 on: January 01, 2012, 05:52:15 PM »
Thats definetely not true for Sony Vegas. You can work with and render up to 24bit 192khz.

well, like I said, if there was a way ( and I looked and looked), I could not figure it out..... the details are not fresh since it's been a couple years, but I recall I could not find any options anywhere that allowed me to render the output audio file at 24/48..... as I mentioned, I was using Vegas 8, if that means anything....

Offline F.O.Bean

  • Team Schoeps Tapir that
  • Trade Count: (126)
  • Needs to get out more...
  • *****
  • Posts: 40690
  • Gender: Male
  • Taperus Maximus
    • MediaFire Recordings
Re: Matrix in post best practice workflow
« Reply #15 on: January 02, 2012, 01:58:26 AM »
I have used WaveLab in the past w/ the Audio Montage to do my post matrix's. I had to sync up every few minutes on one of my matrix's :P That was a TOTAL PITA :P
Schoeps MK 4V & MK 41V ->
Schoeps 250|0 KCY's (x2) ->
Naiant +60v|Low Noise PFA's (x2) ->
DarkTrain Right Angle Stubby XLR's (x3) ->
Sound Devices MixPre-6 & MixPre-3

http://www.archive.org/bookmarks/diskobean
http://www.archive.org/bookmarks/Bean420
http://bt.etree.org/mytorrents.php
http://www.mediafire.com/folder/j9eu80jpuaubz/Recordings

Offline Walstib62

  • Site Supporter
  • Trade Count: (32)
  • Needs to get out more...
  • *
  • Posts: 3266
  • Gender: Male
Re: Matrix in post best practice workflow
« Reply #16 on: January 02, 2012, 10:40:24 PM »
I could be totally wrong on this, and if so, please someone let me know. But, I have always imported the tracks and normalized them first. The reason being that normalizing removes any possible dc offset. That way, all tracks are nulled to 0 offset prior to any other processing.
I think you might be totally wrong. Normalization just brings up overall output levels, DC Offset Removal is a separate function. Unless you are using some offset-correcting normalizer plugin?

You'll get WAY better results mixing 24-bit signals if you can master that way...
In audacity, you can check a box to remove dc offset during normalizing. There is another box to manually select the dB value to normalize to.

Chimney Top

  • Guest
  • Trade Count: (0)
Re: Matrix in post best practice workflow
« Reply #17 on: January 31, 2012, 10:15:35 AM »
n00b to the matrix in post thing...

Scenario:

Deck 1 is a SBD feed, Deck 2 is my aud recording. Neither is jammed to timecode. I mix/correct for drift in post using Vegas.

I run levels on each very conservatively. About -9 to -6 dbfs, peak.

Should I normalize/amplify each file prior to bringing it in to the DAW or just mix and then amplify?


If they are 16 bit sources - you might want to skip normalization until the end (as recommened by page in the last post) - You're going to need about -6db of extra headroom to handle the higher peaks that result when you combine sources.



once they are synced, i think it adds +3db.

Offline drivingwheel

  • Trade Count: (8)
  • Taperssection Member
  • ***
  • Posts: 445
    • Driving Wheel
Re: Matrix in post best practice workflow
« Reply #18 on: February 06, 2012, 11:22:57 PM »
n00b to the matrix in post thing...

Scenario:

Deck 1 is a SBD feed, Deck 2 is my aud recording. Neither is jammed to timecode. I mix/correct for drift in post using Vegas.

I run levels on each very conservatively. About -9 to -6 dbfs, peak.

Should I normalize/amplify each file prior to bringing it in to the DAW or just mix and then amplify?


If they are 16 bit sources - you might want to skip normalization until the end (as recommened by page in the last post) - You're going to need about -6db of extra headroom to handle the higher peaks that result when you combine sources.

I keep everything digital at -6, whether it's 16-or 24-bit...and I try to do that for both the actual source recordings and any final post mixed 'master'; in the digital world, it seems good to stay at -6.  Everything I listen to music on has a volume knob...
http://www.drivingwheelmusic.com
http://www.archive.org/details/DrivingWheel
http://www.facebook.com/drivingwheel

open : Peluso CEMC-6 (cards)>Edirol ua-5 (d-mod)/Fostex FR-2LE (Busman t-mod)/Tascam DR-2D

covert operations : CA-14 (cards)/AT853 (cards)>Church Audio 9100>Tascam DR-2D
'

Offline acidjack

  • Site Supporter
  • Trade Count: (37)
  • Needs to get out more...
  • *
  • Posts: 5845
  • Gender: Male
Re: Matrix in post best practice workflow
« Reply #19 on: February 17, 2012, 11:49:34 AM »
I can't believe I find myself differing (I hesitate to say "disagree", since I don't, really) with page on something related to a topic he knows 10x as much about, but I actually like to hold off on EQ until the sources are mixed down.  IME, trying to EQ each separately sometimes resulted in a less desirable result in mixdown.  Page's method is totally logical, I just found it easier to get the right balance of sources, then EQ and do other things on the combined file.  EXCEPT in some circumstances where something was really off on one of the two files - for example, an SBD that required compression or other tweaks because it was so horribly off balance.
Mics: Schoeps MK4V, MK41V, MK5, MK22> CMC6, KCY 250/5, KC5, NBob; MBHO MBP603/KA200N, AT 3031, DPA 4061 w/ d:vice, Naiant X-X, AT 853c, shotgun, Nak300
Pres/Power: Aerco MP2, tinybox v2  [KCY], CA-UBB
Decks: Sound Devices MixPre 6, Zoom F8, M10, D50

My recordings on nyctaper.com: http://www.nyctaper.com/?tag=acidjack | LMA: http://www.archive.org/bookmarks/acidjack | twitter: http://www.twitter.com/acidjacknyc | Soundcloud: https://soundcloud.com/acidjacknyc

Offline page

  • Trade Count: (25)
  • Needs to get out more...
  • *****
  • Posts: 8388
  • Gender: Male
  • #TeamRetired
Re: Matrix in post best practice workflow
« Reply #20 on: February 17, 2012, 11:58:13 PM »
I can't believe I find myself differing (I hesitate to say "disagree", since I don't, really) with page on something related to a topic he knows 10x as much about, but I actually like to hold off on EQ until the sources are mixed down.  IME, trying to EQ each separately sometimes resulted in a less desirable result in mixdown.  Page's method is totally logical, I just found it easier to get the right balance of sources, then EQ and do other things on the combined file.  EXCEPT in some circumstances where something was really off on one of the two files - for example, an SBD that required compression or other tweaks because it was so horribly off balance.

yeah, I did that for a while, and to a degree I still sort of do. I didn't write out every little nuance to keep it somewhat simple, but thats why I align them first. Then I can listen to the natural combination (via the wonderful fairy land of non-destructive editing/rendering) and hear what works and what doesn't. Occasional muting of one source then gives me a better sense of what each one brings to the table and I can start to tweak the individual ones pre-mix. The reason for doing the pre-mix adjustments is so you can retain stuff that is micro-detail oriented in one source that would be overblown in another and lost when you EQ or compensate for that amount coming from the overblown source. For example, lets say you have a fast attack and fast decay on the sbd bass, and a warm creamy attack-less bass on the aud courtesy of a boomy room. If you amp the bass in the sbd first, do the render, then reduce it, you can retain that initial thwack a little more and then let the warm reverb/boom constitute the decay tail and fill around the note. It's not perfect by any means, but I find it an improvement the majority of time I try it but ymmv of course. Again, you're not doing large adjustments, just a touch here and there to benefit you.

The other trade off is time, I've been tinkering with post production techniques for a good year or so now and this sort of stuff still kills time. If I was taping zman-quantity, I'd probably give up on this sort of stuff, but I'm not, so it's not bad.
"This is a common practice we have on the bus; debating facts that we could easily find through printed material. It's like, how far is it today? I think it's four hours, and someone else comes in at 11 hours, and well, then we'll... just... talk about it..." - Jeb Puryear

"Nostalgia ain't what it used to be." - Jim Williams

runonce

  • Guest
  • Trade Count: (0)
Re: Matrix in post best practice workflow
« Reply #21 on: February 18, 2012, 08:35:47 AM »
Thats why I gave up on post matix (for the moment) - too much time in post...back to using a mixer and OTF (on the fly) matirxing.

I usually run partial SBD + Wide Stage/Pan.
Often my mics end up almost where the soundman might put his mic on the guitar cab -  but not as close, so get a little more leak -  and get the some bass/drums.
So, I can live with that little delay there...

That approach greatly increases the chances that I will have listenable recording by the end of the next day.

When I have to capture a complete board mix and add AUD - generally in that situation...I just keep the AUD mic levels low enough that the delay is barely audible...sucks for tapers as we all love to hear our mics. ;D
But in this situation - just a touch to add some room bass, add some "slop" so the board doesn't sound so dry...kinda sounds like an old live FM show this way...which works for one country act I work with...

 

RSS | Mobile
Page created in 0.116 seconds with 47 queries.
© 2002-2024 Taperssection.com
Powered by SMF