Snap to grid is already off. What i'm referring to is very slight - like one or two 'bits', not 'bytes', being off after i move a clip. I've been using the nudge feature with my arrows to compensate. I would have to upload a short video to explain what i'm talking about. Again it's only a few bits (there's 8 bits in a byte).
Yes, i'm already aware of everything your saying John. And thanks for trying to help out, but as i said, i've been working with Sonar since v1, teach music, daw setups, recording, have already released 2 CDs, etc, etc, what i'm referring to is an increase in complaints and bugs reports over and above that of the usual ones that appear, after each version which has been released via the past 13 incarnations of Sonar now.
I vividly remember last year or so when X3 came out, the complains of bugs, idiosyncrasies, etc, were greater than that which other incarnations of Sonar have incurred. That's what i meant. I know all software has bugs, i program some myself in object pascal. I'm referring to a increase in bug reports, etc, particularly with X2. Cake only released one freakin update (a), and many here complained about it, myself included, that Cake/Roland should tie up the loose ends - just as they've done on every other version they're released - and that we shouldn't have to pay for that.
Anyway, it's late where i live. I'm off to bed. It's not that big a deal. I was just wondering, to put it a different more simplistic way, has CW/Roland smoothed out, in X3, most of what didn't get ironed out in an expected "a, b, c, or d" build? It seems they have, if the love you guys have of it is any indication. I've used nothing else since v1 for all my projects. I may just upgrade yet :)
Anyway, thanks guys..
Tim