• SONAR
  • [SOLVED?] Speed Comping Not Working
2017/12/12 21:23:16
Larry Jones
This issue was not actually solved for me (I just worked around it and moved on) but I'm marking the headline [Solved?] because there are some good and potentially useful answers here for anyone who runs into these difficulties in the future. Thanks, everyone!
*************************************************
I do this so rarely these days that I almost always have to watch a video tutorial to get started, so I was pretty sure I was doing it right. Here's my story:
  • I have five complete vocal tracks, recorded in "comp" mode.
  • I open the take lanes and use the smart tool in the bottom half of a lane to create "logical" split points throughout the song.
  • I set up dim solo and solo the vocal track. Now I can hear the band, but "dimly."
  • I press shift+spacebar to start playback for comping. Playback loops within the first split section.
  • I can move playback to the next section, and the next, etc., using left and right arrows.
  • Up and down arrows move to the various lanes.
  • But I can't hear any of the takes except for the most recently recorded one, which is on top.
When I look at the waveform, it appears to be kind of a "ghost" waveform. If I click on any one of the sections, it does not get promoted. All takes are silent except for the most recent one. I haven't been able to get any of the earlier takes to play, much less to participate in the comping.
Anybody know what could be wrong?
2017/12/12 21:28:43
mettelus
Any chance it relates to this VIC (Virtual Ink Cartridge) post?
 
[The real answer is linked inside it, but that is one of the funniest posts ever made here.]
2017/12/12 22:00:01
rj davis
Verify that ALL the takes have neither Solo nor Mute buttons active.  I was able to duplicate your situation if the most recent take was in Solo mode:  None of the other takes could be heard, even though the Speed Comping function appeared to be working.  If this isn't it, send me a screen shot of what yours looks like and I'll give it a look.  I used Speed Comping every day until recently.  :)
2017/12/12 22:13:58
Larry Jones
mettelus
Any chance it relates to this VIC (Virtual Ink Cartridge) post?
 
[The real answer is linked inside it, but that is one of the funniest posts ever made here.]

That's not it. I couldn't get the "hollow" takes to play back, with or without the region mute tool, which did not seem to do anything at all. It didn't mute anything, or unmute anything. Maybe I'm using it wrong, but it seems like a pretty useless function.


I'm just recording a stupid cover of a Christmas song, and it's easy to sing, so I simply deleted all the takes and started over. This time everything worked fine, until it didn't, which was about half way through the song, at which point the ghost waveform reappeared and the sound went away on all takes.
 
rj davis
Verify that ALL the takes have neither Solo nor Mute buttons active.  I was able to duplicate your situation if the most recent take was in Solo mode:  None of the other takes could be heard, even though the Speed Comping function appeared to be working.  If this isn't it, send me a screen shot of what yours looks like and I'll give it a look.  I used Speed Comping every day until recently.  :)

I appreciate the offer, but I need to get this finished and I'm going to do it the old fashioned way -- punching in the parts that need fixing, in "overwrite" mode. If I have time to troubleshoot later I'll PM you, if that's OK. But why the heck would a random solo or mute button be turned on, anyway?
 
I would be less cranky about this if I were using a DAW that had a future.
2017/12/12 22:53:13
Larry Jones
OK, I went back and messed with the region mute tool. You don't use it above the timeline, and you don't use it on the bottom of an individual track (or lane), and don't expect it to work on multiple tracks (or lanes), either. It works if you swipe it on the top half of a track (or lane) and if somehow you've accidentally muted a stack of lanes, you get to unmute them with this tool one lane at a time.
 
So I did this, and I could see the waveforms normally and hear the takes. Then I tried to comp the vocal again. This time all was well, until it wasn't, which happened at a different place near the end of the timeline, at which point I was hearing all the takes at once. (Also, randomly during comping the backing tracks were muted for a few bars, although luckily not erased.)
 
I deleted the end of the vocal and sang it again, punching in in overwrite mode where necessary. Maybe I've had too much coffee. Something in SONAR is screwed up, and this forum has always been a great place to get help, thank you all, but with the developers all gone it just seems pointless to spend a lot of time figuring this out. I've got what I need right now, so I guess I'll count my blessings and mix it down before something else goes south.
 
2017/12/13 00:00:38
rj davis
That is weird behavior that I've never seen in (literally) hundreds of hours of speed comping.  At times like these, I save the file, close Cakewalk, reboot my DAW and say a little prayer...
 
A trick that shouldn't work (but might) is to open the song in "safe mode" by holding down the Shift key when selecting the file.  After that (and the prayer) I'm stuck.  SORRY!
2017/12/13 14:37:36
mettelus
If worse comes to worst, another option is to shift drag the entire takes into individual tracks. Not as convenient, but you can comp using tracks (and should be immune to the odd behavior you are seeing).
2017/12/15 16:34:34
vanceen
Have you tried clicking K on the silent takes?
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account