Bizarre Export Problem, Resolved and Noted for Future Reference

Author
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
  • Total Posts : 26036
  • Joined: 9/17/2006
  • Location: Everett, WA USA
  • Status: offline
December 10, 11 5:51 PM (permalink)

Bizarre Export Problem, Resolved and Noted for Future Reference

Today I experienced a bizarre and entirely new behavior exporting under 8.5: there were no vocals in my exported mix

I had exported this same song many times before; this problem only began after changing the effects chain on the vocal bus. 

I assumed I'd muted the bus or something equally trivial so I went back in and verified that the song played back OK and that every submix was properly routed to the master bus. I examined the export options to make sure I was using my standard settings, and I was: Entire Mix, all automations enabled. Tried it with Fast Bounce disabled, then with the 64-bit option turned off, neither of which made any difference.

After eliminating routing issues and export options, I figured it must be one of the plugins on the vocal bus. Sure enough, after bypassing all bus effects the export now included vocals again. So I then started bypassing them one at a time to isolate the culprit.

I bypassed just the first plugin, FabFilter Pro-C, and the vocals came back. Hmm. This is my go-to compressor and has never given me trouble before. And it's being used here solely for de-essing. Disturbing, if this reputable plugin turns out to have some weird bug.

Not wanting to accept a problem with my beloved Pro-C, I then bypassed the second plugin, Kjaerhus Classic Compressor. To my surprise, the vocals were once again present in the export - even after re-enabling Pro-C! So it wasn't Pro-C after all.

Then I bypassed the third plugin, Ozone 4 (used for the exciter only). And oh sh*t, this is getting weird now...my vocals came back with Ozone out of circuit, too. Bypassing any of the first 3 plugins seemed to cure the problem!

So now I'm thinking maybe there's a bug in SONAR that shows up when you have 6 or more plugins on a bus (not as improbable as it sounds), or a particular combination of plugins. I saw that I had two already-bypassed plugins (Sonitus Multiband and Voxengo SPAN) in the bin so I deleted them. The vocals then came back in the export, even with all the previously-active plugins restored. I am now cursing Cakewalk but happy to have a workaround. The answer appeared to be in the number of plugins in the bin.

So now with an apparent workaround in place, I exported the entire song. You can imagine my response when the exported file again contained no vocals. Nothing had been touched since the prior export, but my workaround did not work twice in a row. SONAR seemed to be randomly muting the vocal bus, only during exports and doing so just to piss me off!

Some intuition made me go back to the export options and disable the "Bus Mute/Solo" option. As no busses were muted or soloed, it was simply a safe thing to try. Lo and behold, my vocals came back to the exported file. Maybe, at last, a real workaround!

Alas, it was not the solution. I immediately did a second export - without changing anything - and the second export had no vocals. Two exports, one after the other, one with vocals and the other without.

I currently have no explanation for this odd behavior, aside from the observation that it is probably an obscure bug. I only relate it here for purposes of documentation, in case anyone else encounters a similar problem. Or maybe, just maybe, somebody might throw out an observation that will break my mental logjam and lead to an explanation.


All else is in doubt, so this is the truth I cling to. 

My Stuff
#1

13 Replies Related Threads

    mixsit
    Max Output Level: -75 dBFS
    • Total Posts : 789
    • Joined: 4/30/2004
    • Location: CathouseSound
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 11, 11 3:58 PM (permalink)
    I take it none of this string on plugs was new to the party?

    Wayne Smith
    Part time long time..
    CathouseSound 
    Mother Ships  - StudioCat DAWs   
    Portals - RME
    #2
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 9/17/2006
    • Location: Everett, WA USA
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 12, 11 0:15 PM (permalink)
    Nope.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #3
    Bristol_Jonesey
    Max Output Level: 0 dBFS
    • Total Posts : 16775
    • Joined: 10/8/2007
    • Location: Bristol, UK
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 12, 11 4:21 AM (permalink)
    Could be a track corruption Bit.

    Try copying the clips & Fx & automation to a new track and see what happens.

    How many tracks of vocals are there?

    Or maybe even a bus corruption. Route them all to a new bus and try exporting again.

    CbB, Platinum, 64 bit throughout
    Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
    #4
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 9/17/2006
    • Location: Everett, WA USA
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 12, 11 3:07 PM (permalink)
    Never heard of "bus corruption" before, but that's actually not a bad idea. It would actually have to be corruption in the cwp file, and perhaps creating a new bus would force SONAR to recreate the bus definition. Thanks, I'll experiment with that.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #5
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 9/17/2006
    • Location: Everett, WA USA
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 12, 11 8:56 PM (permalink)

    Interesting development. I now know where the vocal is disappearing, but not why.

    Today I tried an audible slow bounce for the export. This saved time because I didn't have to wait for the export to complete in order to know if the vocal was going to be there or not. 

    As before, 4 out of 5 exports had no vocals. There was no obvious pattern to it, and nothing was being changed between export attempts.

    But along the way I happened to have the Pro-C interface up on the screen and noticed a peculiar symptom: the transfer graph turned solid red, as if the compressor was being bombarded with an off-the-scale blast of extremely loud sound. This is how the vocal track was being suppressed: by a compressor being overwhelmed by extreme volume levels. We're talking off-the-scale, mathematically improbable levels.



    In Pro-C, the red-shaded portion indicates the incoming audio level relative to the transfer curve. Here it's showing complete saturation. 



    The input level is displayed below the input level knob. Here it's showing +36db, although Pro-C's meters and knobs all max out at +36db so it's probably higher than that.. (The actual peak value of the track feeding it is -3.7db. 

    This instance of Pro-C was being driven by a side chain signal, so the outrageously-loud signal displayed was actually being seen on its sidechain input. That signal was coming from an audio track with no effects.

    I still do not know if the bug is in Pro-C or SONAR, though, nor do I know how to trigger or prevent it. But one of the two is doing some bad math.
    post edited by bitflipper - December 12, 11 9:20 PM


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #6
    timidi
    Max Output Level: -21 dBFS
    • Total Posts : 5449
    • Joined: 4/11/2006
    • Location: SE Florida
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 12, 11 9:11 PM (permalink)
    Bit, how about just 'bouncing to track'? And then export that mix. does that work?

    ASUS P8P67, i7-2600K, CORSAIR 16GB, HIS 5450, 3 Samsung SSD 850, Win7 64, RME AIO.
     
    https://timbowman.bandcamp.com/releases
     
    #7
    Beagle
    Max Output Level: 0 dBFS
    • Total Posts : 50621
    • Joined: 3/29/2006
    • Location: Fort Worth, TX
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 12, 11 10:56 PM (permalink)
    what is Pro-C?  is that a Fab compressor plugin?  what happens if you remove that compressor from the project?

    http://soundcloud.com/beaglesound/sets/featured-songs-1
    i7, 16G DDR3, Win10x64, MOTU Ultralite Hybrid MK3
    Yamaha MOXF6, Hammond XK3c, other stuff.
    #8
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 9/17/2006
    • Location: Everett, WA USA
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 13, 11 1:20 AM (permalink)
    If I remove the compressor I get vocals.

    What was happening was I was driving the sidechain input on the compressor with a de-essing key track, but for some reason SONAR would occasionally spit that track out at like 99 decibels, overwhelming the compressor. That's what was killing the vocals in the export.

    It only happened during the export, never during playback, and it was intermittent. I'd get a proper export about 20% of the time.

    Ultimately I just reverted to a more convenient but less effective de-essing scheme, using the Pro-C's internal sidechain filter. That got me to where I could get a proper export 100% of the time, at the cost of slightly more sibilance.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #9
    Bristol_Jonesey
    Max Output Level: 0 dBFS
    • Total Posts : 16775
    • Joined: 10/8/2007
    • Location: Bristol, UK
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 13, 11 4:28 AM (permalink)
    Shame, I can't see the images you posted, our company firewall tends to block certain stuff off.

    If you're halfway there with your sibilance taming, try putting another de-esser on the Vocal bus.

    I sometimes find that one level of de-essing isn't enough - this is analogous to having several layers of compression (and very similar in concept) - so I end up de-essing at track & bus level.

    CbB, Platinum, 64 bit throughout
    Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
    #10
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 9/17/2006
    • Location: Everett, WA USA
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 13, 11 1:11 PM (permalink)
    This was a particularly difficult de-essing job. It wasn't that the "S"s were too hot, but that there was an awful 8KHz resonance buried within not only the "S"s but the hard consonants as well, particularly "T"s and "K"s, and even occasionally on some vowels.

    This had been caused by a broken (borrowed) microphone wherein some internal component had broken loose and was resonating inside the mic. I did not catch this until 30 vocal takes had been recorded.

    I resolved the problem by going old-school. I bounced all the vocals to a single mono track. Then I put an extreme filter on it to hugely emphasize the resonance, and aggressively compressed it. Now I had a track consisting of just the unwanted resonances, which I then routed to the sidechain input of the Sonitus Compressor on the vocal bus. 

    That worked surprisingly well. But later on I decided I needed to automate the bus EQ. That was going to be a problem, because the Sonitus Compressor has a bug in which it will suppress automation to downstream effects if there are more than two effects after it. So the Sonitus had to go. What I did not expect was the subsequent weirdness after replacing it with the FabFilter Pro-C compressor.

    I still do not know if the problem was caused by SONAR, by Pro-C, or by the specific combination of the two. But one or the other was adding 1 + 1 and getting 1,000,000.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #11
    sakis_us
    Max Output Level: -90 dBFS
    • Total Posts : 20
    • Joined: 3/30/2005
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 19, 11 5:14 PM (permalink)
      I was reading your thread last Friday and "funny" thing... it happened to me next day! Although not identical but similar. I am using the Marquis Compressor from Voxengo. It is a 6 track song, not heavy on plug ins, and I used the compressor on the bass track. I was happy with the mix,I saved it, played back the song one more time, and I exported it. Got in to my car for a ride to listen to it and there was no bass on the second verse! I had 3 different mixes of the song. All same plug ins but slightly different settings. Only one version had the issue, the other ones where fine. Went home, fired up the PC played back the song and the bass on second verse for some reason wasnt playing. Exit/restart it is playing! I was going nuts! Anyways I opened it up again today and it exported fine, which is good but I have never experienced such an issue.

    Asus P5K Premium, Intel(R)Core 2 Quad Q9550 @ 3.80GHz, BIOS:AMI 1101, 4X Kingston KHX8500D21GN 1GB DIMM DDR2 PC2-8500U DDR2-1066 (5-5-5-18 3-23-6-3), GeForce 8800 GTS 320MB 320-bit GDDR3 PCI Express x16 HDCP, Seagate 250GB Serial ATA w/NCQ 7200/8MB/SATA-3G (OS drive), WDC WD1001FALS-00J7B0 (1TB, SATA150, 7200rpm, NCQ, 32MB Cache), WDC WD3200AAJS-00RYA0 (320GB, SATA150, 7200rpm, NCQ, 8MB Cache), ANTEC NEO HE550 (PSU), Scarlett 18i6, MBOX 2, SONAR X3P, ProTools 8.5
    #12
    DonM
    Max Output Level: -34 dBFS
    • Total Posts : 4129
    • Joined: 4/26/2004
    • Location: Pittsburgh
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 20, 11 7:07 AM (permalink)
    bitflipper


    What was happening was I was driving the sidechain input on the compressor with a de-essing key track, but for some reason SONAR would occasionally spit that track out at like 99 decibels, overwhelming the compressor. That's what was killing the vocals in the export.

    Wow ...  The thing that came to mind while I was reading this was ....


    It seems the Side Chain input would just go full scale and then trash the output, right?  So I wonder if the SC Input (again whether it is Sonar or the Plug not known yet) can consistently track any signal without making erratic processing levels? Obviously the full scale result is 'easy' to notice -  but what about a few db here and there that could alter a great mix?  I don't know the plug - but since you're a fan it definitely has my interest now.  


    I just wonder if you copied a bunch of clips with needed de-essing and linearly scaled their level into the plug what would happen.


    Best


    -D

    ____________________________________
    Check out my new Album  iTunesAmazonCD Baby and recent Filmwork, and Client Release
     
    #13
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 9/17/2006
    • Location: Everett, WA USA
    • Status: offline
    Re:Bizarre Export Problem, Resolved and Noted for Future Reference December 20, 11 11:28 AM (permalink)
    Don, that's probably worth a test, and shouldn't be difficult to set up. My instinct says that if the compressor works properly in normal (internal sidechain) mode it should also be equally predictable when keyed from an external source. But that assumes the plugin is coded properly.

    This particular compressor and the company that makes it are both highly-regarded, and it's not a new product. However, this behavior was not observed when I was using the Sonitus compressor. The weirdness only appeared after switching to FabFilter Pro-C. However, there have been past reports of SONAR suddenly sending ridiculously high levels from tracks, as if there was some accidental internal feedback loop.
    post edited by bitflipper - December 20, 11 11:41 AM


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #14
    Jump to:
    © 2025 APG vNext Commercial Version 5.1