Strange comping behavior

Author
stevesweat
Max Output Level: -83 dBFS
  • Total Posts : 360
  • Joined: 5/12/2016
  • Location: Austin
  • Status: offline
September 16, 16 0:27 PM (permalink)

Strange comping behavior

I am in the quest to figure out how to turn a comped track into a normal track with no take lanes or old takes remaining, just a good old normal track. I was doing some melodyne on a comped track earlier today and when I bounced to tracks a blank clip was introduced in front of the clip I just Melo'd.  If I deleted this blank clip the Melo'd clip became visible where beforehand the blank clip appeared to be producing sound when in actuality the clip behind it was producing the sound.
I swear a project I was working on today had one comp track and at some point all the tracks in the project had "take lanes" and acted as comp tracks when previously only the one had actually been instigated as a comp track. I have begun NOT using comp lanes and just dragging old school to avoid comp weirdness.
Using comp lanes seems to introduce wonky results

Steve
Sweaty Productions
http://www.youarentweird.com/
https://soundcloud.com/user-978097986-982906152
https://sweatyproductions.bandcamp.com/
Windows 10 x64
SONAR Platinum x64
AMD FX6300 3.5gig 6core
HYPERx FURY 16gigRam
PNY GeForce GT730
WD Caviar 1TB 7200rpm
Gigabyte ATX AM3+ AMD 970 chipset
Roland Studio Capture
#1

6 Replies Related Threads

    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 9/14/2007
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Strange comping behavior September 16, 16 1:25 PM (permalink)
    Right-click on the Comp Clip in the parent track with lanes showing, and choose Flatten Comp. This will create a new lane with all the active clips in comped lanes rendered into one new clip. The comped lanes can then be deleted. Note that the Flattened Comp clip will be locked by default; if you want to do further editing, you'll need to right-click and unlock it. Then close lanes, and you'll be working with a 'normal' track. I suggest you do this on a clone of the track (or a copy of the project), to allow recovering the original clip/take structure later on if needed.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #2
    d_in_conduct
    Max Output Level: -86 dBFS
    • Total Posts : 226
    • Joined: 3/3/2004
    • Status: offline
    Re: Strange comping behavior September 17, 16 2:02 AM (permalink)
    Bounce to tracks, either the comped track alone or without even flattening.  Then archive and hide the original track so you can go back to it later, if you need to.
     

    ------------------------------------------------
    All your base are belong to us...
    #3
    stevesweat
    Max Output Level: -83 dBFS
    • Total Posts : 360
    • Joined: 5/12/2016
    • Location: Austin
    • Status: offline
    Re: Strange comping behavior September 17, 16 8:26 AM (permalink)
     So I think I have this all figgered out now. The crux of my biscuit I do believe is deleting the muted clips. If you retain the unused portions of your comp track, these unused parts will exist in a layer below the used portions and if/when you do any editing the unused portions become a major nuisance. If you slip edit a phrase out of the song, for example, then you will see the unused take of that edited-out take beneath the clip as you slip edit. This can be confusing. While the exposed unused clip seems "grayed out" and I'm not sure it is audible, it IS possible to delete the unused track beneath the used comp track, and I REALLY don't want to be seeing waveforms that are silent (even if grayed out). This is really confusing! The big biscuit is Melodyne. When you Melo a phrase on a comped track which still has the old takes remaining beneath the used takes - best case scenario is that Melo will properly edit your clip but will leave a blank clip ON TOP of it (I won't swear the blank clips were actually blank as another user indicated that redrawing waveforms on these blank portions showed them to contain audio - so quite possibly the "blank" clips I deleted were actually the Melo'd clips and the clips beneath were actually unused takes from comping that I unwittingly brought back into the fold) or perhaps Melo is a bit confused(?) by what it may (rightfully) perceive as multiple clips in one track. I also encountered some corrupted phrases after Melo'ing and the only way these corrupt phrases could have come about was through Melo - as they were split individually and consistently with my methodology of Melo'ing line by line to avoid a) overworking my computer b) ensuring all changed notes SHOULD be changed. (It takes a major leap of faith to Melo a whole track at once, right? A note or two correcting the wrong way etc...) I deleted the corrupt phrases - just three fortunately, but now whenever I open this project I get a "corrupt audio file detected and replaced with silence" message. 
     My second flash of <s>genius</s>,er, stupidity correction, was the realization that all tracks are comp tracks. Any track can be used to comp, so my quest to convert a comped track to a normal track was a bit misguided. I will be deleting unused clips as quickly as I confirm they are unneeded from now on. 
     And yes the clip being locked after flattening seems counter-intuitive but perhaps it is good to be reminded that it was a comped track and MAY contain extraneous information in the tracks below - proceed with caution! 

    Steve
    Sweaty Productions
    http://www.youarentweird.com/
    https://soundcloud.com/user-978097986-982906152
    https://sweatyproductions.bandcamp.com/
    Windows 10 x64
    SONAR Platinum x64
    AMD FX6300 3.5gig 6core
    HYPERx FURY 16gigRam
    PNY GeForce GT730
    WD Caviar 1TB 7200rpm
    Gigabyte ATX AM3+ AMD 970 chipset
    Roland Studio Capture
    #4
    stevesweat
    Max Output Level: -83 dBFS
    • Total Posts : 360
    • Joined: 5/12/2016
    • Location: Austin
    • Status: offline
    Re: Strange comping behavior September 17, 16 8:47 AM (permalink)
    addendum
     It would be nice and elegant if a flattened comp track saved the old takes but kept them hidden and entirely uneditable. The most surprising fact to me in this situation is that the unused lanes are visible and editable. For example, play two guitar takes on one track then just select one and make it your "comped take" then flatten. Unlock the clip then delete the clip. You will see another grayed out kind of looking clip. then delete that clip. That really shouldn't be possible if the end goal is to save the unused takes for posterity. 
     And if you bounce to clips a comped track with unused lanes intact the bounced to clip will still contain those unused takes (I'm 95% sure I encountered that behavior)
     

    Steve
    Sweaty Productions
    http://www.youarentweird.com/
    https://soundcloud.com/user-978097986-982906152
    https://sweatyproductions.bandcamp.com/
    Windows 10 x64
    SONAR Platinum x64
    AMD FX6300 3.5gig 6core
    HYPERx FURY 16gigRam
    PNY GeForce GT730
    WD Caviar 1TB 7200rpm
    Gigabyte ATX AM3+ AMD 970 chipset
    Roland Studio Capture
    #5
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 9/14/2007
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Strange comping behavior September 17, 16 12:14 AM (permalink)
    stevesweat
    And if you bounce to clips a comped track with unused lanes intact the bounced to clip will still contain those unused takes (I'm 95% sure I encountered that behavior)
     

     
    That sounds like the result of using Bounce to Track(s) rather than Bounce to Clip(s), and specifying the source track as the target track.
     
    Bouncing always writes a single new audio file and creates a single new clip referencing that file. In the case of Bounce to Clip(s), the original clips will be deleted, and the the file(s) referenced by those clips will be 'orphaned', though they continue to exist in the project audio folder.
     
    But if you Bounce to Track(s) with the source track as the target, the original clips and take lanes will continue to exist, and SONAR will drop the new clip on top of existing clips in the uppermost take lane if you don't pre-create a new empty lane to hold the bounce.
     
    Bounce to Track(s), specifying a new target track, is another way to flatten a comp, but only if the original track doesn't already have altered Gain/Volume/Pan, Sends, FX etc. on it.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #6
    Keni
    Max Output Level: -17.5 dBFS
    • Total Posts : 5769
    • Joined: 11/4/2003
    • Location: Willits, CA USA
    • Status: offline
    Re: Strange comping behavior September 17, 16 7:29 PM (permalink)
    I prefer to clone the track, archive the original and hide it, then in the cloned track create a single lane with my selected clips and finally deleting the unused.

    I like to know I can go back to square 1 if need be...

    Flattening the cloned track would do the same but I prefer to have the track chopped into clips instead of a single clip... Most often...

    Keni Fink
    Keni - Facebook
    Deep Space Records
    http://www.reverbnation.com/inexile
    http://www.cdbaby.com/artist/inexile
    Out Of My Head Music (BMI)

    SPlat/MacPro/Dual Xeon 3.06GHz 6-core (12 total)/64GB/Win8.1X64/Presonus 1818VSL/Soundscape SS8IO-1
    #7
    Jump to:
    © 2025 APG vNext Commercial Version 5.1