Split clips unwantedly mirroring edits...

Hi, all.
 
This is an issue I've experienced on occasion over the years, but have never written about as it's more of an annoyance than anything else, and I usually just work around it. But experiencing it again today has prompted me to bring it up.
 
When I split a clip into two smaller clips (let's call them clip "A" and clip "B"), and then I edit clip "A" (if I crop the beginning of the clip, for example), sometimes clip "B" will mirror the same edit, almost as if the clips were linked... but they're not... They were simply split from the same original clip.
 
First, has anyone else experienced this? And if so, what's the deal? Is it a bug? Is there a remedy?
 
Any input is appreciated. Thanks!
 
 
SONAR X3e Producer
Win 7 64-bit

are you using linked clips ? clip groups ?
any kind of grouping ? there also may be a setting in preferences under editing I believe
for the way clips are treated.
someone else might be aware of it, right now though, im blanking.

SGodfrey
Yes, I've had this a lot and I've never properly understood why it's doing it.  At the moment I'm finding that Bounce To Clip before I make any changes is the way to go.  Doesn't mean I understand why though!

yes, I was thinking of this too. possibly a groove clip.
I also bounce to clips before splitting and editing as well.
 
though I don't think groove clips, would edit both clips the same unless im not understanding the OP

Hi, guys. Thanks for the replies.
 
Yes, I'm totally sure I only have the desired clip selected when doing the edit(s). I've even done the Select None command before trying, just to be sure.
 
No linked clips, no groove clips, no grouping of any kind, just your run-of-the-mill straight audio recordings. Most recently, I've noticed the odd behavior happening within take lanes, although I'm pretty sure it's happened in parent tracks as well in the past.
 
Bouncing to clips may work, but I do a LOT of splitting and slip-cropping edits, so that could add up to take a lot more time/work...

Thanks for the tip, Colin.
 
I'll just have to keep an eye out for future occurrences of the behavior, see if I can figure out anything more about it, and apply bouncing if necessary.