Re: Tracks keep mysteriously splitting in the take lanes
2017/11/17 20:07:24
(permalink)
Hey Sylvan, thanks for your helpful reply!
Yeah. So, apparently, the only way to avoid inserting an unnecessary split would be to hit the "stop" control exactly at the very end of the loop point. I am a few feet away from the computer, so by the time I set down my guitar or get back from the mic to hit stop control this can occur anywhere in the recording, and that's where a random split is inserted. I have to admit that while this is the way it works, I don't see anything "intentional" about the point at which I stop recording. I haven't even begun comping things together at that point. Clearly, when I'm in the midst of a recording session, I'm not even thinking about how I might comp the takes together, until after I listen to them. When I am ready to split take lanes to build a comp track, I'd like to pick the spots and split with intention.
That said, I realize that this extra and unnecessary split is not heard when I eventually create a flattened comp. From a programming standpoint, Cakewalk must not consider this unnecessary split destructive. Regardless, it still seems like a destructive, rather than productive, way for this to work and that's why I was curious if anyone else had encountered this. As a programmer, the logic or value of inserting a useless split in all the takes, because I stop recording, just escapes me.
From a user perspective, I'm not a fan. When I decide that I need to start over and recreate a previously created comp or come back to a project the next day, I find myself thinking, "Hmm, why did I put that split there... Oh yeah, is that the one that Sonar arbitrarily inserts when I stop comp recording?" I know this might sound trivial or petty, but I just prefer it when software features perform the function associated with their actual name. Stop means "stop", not "split". Thankfully, they didn't program it so that splits are inserted in take lanes whenever we hit the "play" control!
Anyway, you answered my question by indicating that this is how Sonar behaves and likely has always worked, so that was very helpful. I'll just work around it. Thanks! ;)
DAW Specs & Software: Asus P6TD Deluxe Motherboard, i7 920, 12 GB OCZ DDR3 1600Mhz RAM, Windows 7 64bit, Sonar Platinum, Scarlett Focusrite 8i6