Betcha Haven't Seen This Before

mmmm...what happened there?

I see three tracks look like the mute tool has been used on them, thus the dotted waves and lines.

If one thing is for sure:  It must be your system´s fault. Or User error. Or both.

I'm going to have to start looking a little closer at what happen here.... 

Thanks for posting the screenshot.  I haven't figured that out, yet, but I hope that it's unnecessary in the future.

Hey there we are for all you that want lanes. At last!

That is disturbing.

I'm really digging this new graphics subsystem.

*turns back to the DAW running 8.5.3 and continues working*

I say its a stealth lane. Cubase is infecting your system.

I'm surprised people on the thread haven't seen this before.  It's somekindawierdgraphicalissuethathappenswithX1.  I've seen that often, and as you said, HumbleNoise, you just twiddle with your mouse wheel and it straightens out.

It's just another bug in the program.  At least it's a fairly minor one since it's easily corrected.  Funky though, and obviously something that shouldn't happen.  --It's part of the Not Ready For Prime Time Syndrome.

Randy B.

One of the many bad behaviors that sent me back to 8.5.3. I saw this after changing screen sets with some tracks hidden, and then coming back to the first screenset. It returned to normal as soon as I resized a track. 

PeterMc

rbowser


I'm surprised people on the thread haven't seen this before.  It's somekindawierdgraphicalissuethathappenswithX1.  I've seen that often, and as you said, HumbleNoise, you just twiddle with your mouse wheel and it straightens out.

It's just another bug in the program.  At least it's a fairly minor one since it's easily corrected.  Funky though, and obviously something that shouldn't happen.  --It's part of the Not Ready For Prime Time Syndrome.

Randy B.

Add this line to your cakewalk.ini file in the [Options] section:

somekindawierdgraphicalissuethathappenswithX1=0

That should fix it :)

LOL!

shawnbulen


I was able to reproduce this on my first try.   I have NEVER used screensets before, so I have the default install screensets.   (I like the multidock, & have been using that extensively.  In fact, I removed the screensets module from the control bar to make room.)   Reading this thread, I just opened a recent project, added the 'screenset module' to my control bar, pressed '1', and got almost this exact same result.  

I can reproduce it easily.  Just open up the TV & start hitting all the screenset buttons on the control bar.  Just keep hitting 'em, you'll find one that will do it...  

It's easily fixed by scrolling or zooming with the vertical scrollbar.

Thanks Shawnbulen - now we do know what not to do and/or how to fix it...

brundlefly


From before I got tired of saving screenshots of somekindawierdgraphicalissuethathappenswithX1 every 10 minutes:
 

Funny thing happened to me - with another host (Studio One, sorry) ...  I kept getting similar 'graphic' issues (actually worse) until I really set in to debug it.
 
Turns out it was ONE plugin (Nugen Visualizer in this particular case).   It never gave me problems in Sonar but it does in Studio One.
 
Sometimes these things are REALLY hard to debug -- they take so much of our time.
 
But I bring it up because a) it happens, and b) MAYBE this will open some thought in this Sonar issue.
 
Dunno, but maybe.
X1 has a lot of re-write in it -- and we all know what that means..... lots of potential for not only ITS problems, but it may expose problems in OTHER things.
 
 
EDIT:   btw, if I showed a screenshot of what I was seeing in Studio One (without knowing what was the REAL cause) - no one would want to buy it.
 
SO these are tricky times ;)
 

double post