That's exactly what was happening to me except it was across tracks. I'd highlight or select something and other stuff got selected too. I don't recall it happening in lanes though but when I first noticed it I was working on a MIDI track and started locking everything down immediately so I wasn't actually messing with lanes too much. You know what... come to think of it it may have been effecting the very few lanes in the MIDI track. I have not had it happen since though.

This only started happening with X2 (build 306). X1 was fine.

I'm curious... do you happen to use a mouse that requires a driver? I'm using a Kensington Expert Mouse (trackball) and I'm taking a wild guess that it might be a driver issue considering more people aren't talking about this.

Just a thought.

And the new lanes are probably being created because it's selecting the unwanted lanes and then when you move them it forces a new lane.

I could be completely misinterpreting it but really the behavior in your vid is very very similar to what was happening to me. Cheers.

Beepster


That's exactly what was happening to me except it was across tracks. I'd highlight or select something and other stuff got selected too. I don't recall it happening in lanes though but when I first noticed it I was working on a MIDI track and started locking everything down immediately so I wasn't actually messing with lanes too much. You know what... come to think of it it may have been effecting the very few lanes in the MIDI track. I have not had it happen since though.

This only started happening with X2 (build 306). X1 was fine.

I'm curious... do you happen to use a mouse that requires a driver? I'm using a Kensington Expert Mouse (trackball) and I'm taking a wild guess that it might be a driver issue considering more people aren't talking about this.

Just a thought.

It's always worth entertaining any suggestion as you never know what edge-cases we are running into, but although I need a driver for my Logitech mouse I don't think that's the issue.  If I change the screen resolution or resize the tracks and lanes, the selections I make are consistently affecting the exact same tracks and lanes, rather than anything random.  It appeared to be random when I first encountered the issue, but since then I've been able to distill this down to repeatable, deterministic steps and obtain the same result with the same projects.
 
I'm almost certain that my conclusion that there's some internal index issues is correct.  Each take lane needs an internal index that is unique so that the program knows how to pass a reference to it to various functions.  But if an internal index is duplicated, then it would exactly explain the behavior I am seeing.  I realize that there can be many causes for the same symptom, but this one fits the crime too perfectly.
 
Hopefully with the project I sent to Cakewalk, along with my video, there should be enough for a "quick fix" to this.  I hope so, because I want to dive into X2a more but I'm a little reticent at the moment

After Google giving me a real hard time I managed to dig up my original thread on this. 

http://forum.cakewalk.com...;m=2702185&mpage=1

A few others had similar problems.

If this is different then what you are talking about my apologies. 

Re-reading the thread it seems I was actually working with lanes. Apparently my memory is going wonky with age.

Beepster


After Google giving me a real hard time I managed to dig up my original thread on this. 

http://forum.cakewalk.com/tm.aspx?&m=2702185&mpage=1

A few others had similar problems.

If this is different then what you are talking about my apologies. 

Sounds VERY similar to my issue.  However, I still get the same problems even after locking clips (position, data) and even using the Isolate Clip tool.  Maybe there is still some underlying issue that is the same for both cases though, so I am going to cross-reference my thread in your original post so that maybe we can provide a more comprehensive picture for Cake....

Sounds VERY similar to my issue.  However, I still get the same problems even after locking clips (position, data) and even using the Isolate Clip tool.  Maybe there is still some underlying issue that is the same for both cases though, so I am going to cross-reference my thread in your original post so that maybe we can provide a more comprehensive picture for Cake....

I'm in. Let me know any info you need. You seem to have a better understanding of things than I so I'll let you drive.

Cheers and thanks. I'd really like to get this solved.

I've seen very similar behaviour to this going right back to Sonar 7, well before take lanes, wrong clips being selected and random movements on tracks when cloning or moving stuff and random clip lengths when making splits.
 
IIRC messing with some of the different Editing options 'Blend Old With New' etc, mitigated some of the problems but there's definitely been gremlins underlying in this area for some time.
 
I just have 'Replace old with New' set now which seems trouble free and leave it a that.  Try that see if it makes a difference.   It might help narrow down where the problem lies if it only happens under certain circumstances.
 
It might also be helpful being as you've posted a video for other X2 users to try and replicate the problem and help identify the causes and ultimately produce a fix, rather than stating everything is fine at their end and that there are workarounds.
   
Thanks to the vid we can ALL see there ARE problems.

FastBikerBoy

So while working at "curing" the "screen clutter" some complained of in earlier Sonar releases, now we have the opposite... Lots of space wasted and lots of extra work created to manage that space all the time....

I now spend far more time adjusting the display in Sonar than ever before and it takes away from the music mind/work....

That's where screensets become really useful, setup the views you want as screensets and switch between them. Changes are really quick that way.

I can see why you are frustrated if you stay on one screenset and adjust that as needed. That'd send me crazy too.

Hi Karl...

No, I use screensets as well... The problem isn't a matter of which windows open where/when... It's a matter of how much data can I see on screen at one time. I'm used to seeing (essentially) my whole project while I work and with X this has become increasingly difficult. It was bad in X1, but in X2 it's become almost impossible with the way Lanes use screen space...

Happy New Year!
Keni

Beepster


That's exactly what was happening to me except it was across tracks. I'd highlight or select something and other stuff got selected too. I don't recall it happening in lanes though but when I first noticed it I was working on a MIDI track and started locking everything down immediately so I wasn't actually messing with lanes too much. You know what... come to think of it it may have been effecting the very few lanes in the MIDI track. I have not had it happen since though.

This only started happening with X2 (build 306). X1 was fine.

I'm curious... do you happen to use a mouse that requires a driver? I'm using a Kensington Expert Mouse (trackball) and I'm taking a wild guess that it might be a driver issue considering more people aren't talking about this.

Just a thought.

Hi Beepster...

Yup... I've been experiencing this too... but until I heard you guys talking about it I just kept thinking I must have accidentally left something selected and used a ctl-click (accidentally) when selecting what I thought was the only clip being selected... I had not seen the rhyme or reason behind what was going on...

Happy New Year!

Keni