Comping/Loop Recording Issue

Author
streckfus
Max Output Level: -84 dBFS
  • Total Posts : 339
  • Joined: 2013/11/22 15:29:47
  • Location: Minneapolis, MN
  • Status: offline
2015/03/03 09:48:33 (permalink)

Comping/Loop Recording Issue

When I set up loop recording in comping mode, it works perfectly the first time through.  All takes are recorded new take lanes, the previous takes muted as the next one records, etc.  However, if I stop loop recording then decide to go back and record additional takes, Sonar no longer creates new take lanes for each consecutive take.  It'll store all new takes in a single take lane, so then I need to go back, manually create new take lanes, then drag/drop individual clips from the cluttered take lane into the new, empty ones I created.
My workaround is to bypass loop recording altogether and just manually start/stop recording, create a new take lane, record enable and solo it, then record again.  It's cumbersome but manageable when recording another person's vocals, but when I'm recording my own vox, it's a major time suck to have to manually create a new take lane each time I want to record a new take.
 
Am I making some sort of dumb mistake, or is this a known bug in Sonar?  I haven't seen anything about it on the forums, which is strange because I imagine loop recording is a pretty common practice, especially when paired with the comping feature.
 
Thoughts?
#1

4 Replies Related Threads

    stevec
    Max Output Level: 0 dBFS
    • Total Posts : 11546
    • Joined: 2003/11/04 15:05:54
    • Location: Parkesburg, PA
    • Status: offline
    Re: Comping/Loop Recording Issue 2015/03/03 21:07:23 (permalink)
    Which version of SONAR are you using?   I believe starting with X3 new clips can't occupy the same space as other clips on the same lane.   At least not under normal circumstances...  
     

    SteveC
    https://soundcloud.com/steve-cocchi
    http://www.soundclick.com/bands/pagemusic.cfm?bandID=39163
     
    SONAR Platinum x64, Intel Q9300 (2.5Ghz), Asus P5N-D, Win7 x64 SP1, 8GB RAM, 1TB internal + ESATA + USB Backup HDDs, ATI Radeon HD5450 1GB RAM + dual ViewSonic VA2431wm Monitors;
    Focusrite 18i6 (ASIO);
    Komplete 9, Melodyne Studio 4, Ozone 7 Advanced, Rapture Pro, GPO5, Valhalla Plate, MJUC comp, MDynamic EQ, lots of other freebie VST plugins, synths and Kontakt libraries
     
    #2
    streckfus
    Max Output Level: -84 dBFS
    • Total Posts : 339
    • Joined: 2013/11/22 15:29:47
    • Location: Minneapolis, MN
    • Status: offline
    Re: Comping/Loop Recording Issue 2015/03/03 21:17:23 (permalink)
    Sonar Platinum actually. The particular project I'm working on was created in X3 though.
    #3
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Comping/Loop Recording Issue 2015/03/04 10:55:58 (permalink)
    Make sure you have Create New Lanes on Overlap checked in Record preferences. This setting is largely superfluous now that SONAR doesn't normally allow same-lane overlaps, but there are some situations - like the one you've encountered - in which you can still get overlaps if this option isn't checked.
     
    EDIT: That said, I just tried to reproduce this with a new project started in Platinum build 37 with Create New Lanes unchecked, and could not. So what your encountering could be a holdover from a project started in an earlier release.
    post edited by brundlefly - 2015/03/04 11:13:19

    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
    #4
    streckfus
    Max Output Level: -84 dBFS
    • Total Posts : 339
    • Joined: 2013/11/22 15:29:47
    • Location: Minneapolis, MN
    • Status: offline
    Re: Comping/Loop Recording Issue 2015/03/05 19:50:09 (permalink)
    Yep, that box was indeed checked, but you must be right.  I kept the same settings and started a new project in Platinum (build 37 as well), loop-recorded a handful of takes, stopped, auditioned some takes, then went back in and recorded more takes, and it worked as expected, no overlap.
     
    As you said, the issue must be a holdover from X3.  Kind of a pain because I have several in-progress projects that were created in X3, but at least I have a workaround and know that any fresh projects created in Platinum will loop record as expected.
     
    Thanks for the feedback!
    #5
    Jump to:
    © 2025 APG vNext Commercial Version 5.1