ba_midi

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 ;)

You're not implying I should not have posted this because it might be damaging to SONAR's sales are you? I figure that decision is out of my hands. Cakewalk took on the bad-publicity risk themselves when they released such a raw product to the public.
 
This was a very basic project as you can pretty much see from the screenshot. The only plugs were PX 64 and a disabled Sonitus Gate on a an empty track, and a Lexicon Pantheon on the Effects bus. All the inputs were from hardware synths with no soft synths yet inserted. I have little doubt this is a Screenset-related bug.  As I recall, I had hidden all but those first two recorded tracks, then changed to a acreenset with the CV open, and when I came back to the TV screenset, the headers for the hidden tracks were displaying again with the mismatch shown.
 
I'm kind of burned out on chasing X1 bugs, and dealing with Cakewalk's awkward, and too frequently unrewarding, problem reporting process so I didn't spend any time trying to reproduce it or submit a problem report.

Wow Steve that's a pretty bizarre Screen Set. Can you change it back at all? Or do you have to reload the project? Does that fix it? Does it happen a lot?

HumbleNoise


Wow Steve that's a pretty bizarre Screen Set. Can you change it back at all? Or do you have to reload the project? Does that fix it? Does it happen a lot?

 
Thankfully it's only happened the once - I thought I'd take a shot for posterity though!
 
I think I was trying to see if I could drag the Pro-Channel strip into the Multidock or something daft and I must have grabbed something else 
 
I just had to close X1 and re-open it and it was fine.

Maybe I can get inspired to come up with other useful terms - Like the "setthesnapresolutionnosetitagainsorrygottadoitagain" syndrome.

 
Now with illustrations:
 

brundlefly

Maybe I can get inspired to come up with other useful terms - Like the "setthesnapresolutionnosetitagainsorrygottadoitagain" syndrome.

 
Now with illustrations:
 

hehe.

Here's another one:  The "dragaudiofromthebrowsernodoitagain" syndrome. 

Randy B.

trimph1

Supercomposer


Don´t worry.
That is just # 79 of the 541 bugs that will be fixed by the X1b patch next week.
The remaining ones (542-1688) will be fixed by c,d and e

Dang...I keep thinking it seems more like 3,670 bugs were listed....must be a new bug then.

guys, don´t forget the new ones which will be introduced by the patch! (just kidding.. but, remember the ASIO disaster with X1a) ?
Still shaking. My head. 

brundlefly

ba_midi

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 ;)

You're not implying I should not have posted this because it might be damaging to SONAR's sales are you? I figure that decision is out of my hands. Cakewalk took on the bad-publicity risk themselves when they released such a raw product to the public.
 
This was a very basic project as you can pretty much see from the screenshot. The only plugs were PX 64 and a disabled Sonitus Gate on a an empty track, and a Lexicon Pantheon on the Effects bus. All the inputs were from hardware synths with no soft synths yet inserted. I have little doubt this is a Screenset-related bug.  As I recall, I had hidden all but those first two recorded tracks, then changed to a acreenset with the CV open, and when I came back to the TV screenset, the headers for the hidden tracks were displaying again with the mismatch shown.
 
I'm kind of burned out on chasing X1 bugs, and dealing with Cakewalk's awkward, and too frequently unrewarding, problem reporting process so I didn't spend any time trying to reproduce it or submit a problem report.

Dave, in no way did I mean you shouldn't bring this up.  I was actually trying to offer a suggestion in that maybe some plugin is having contention with X1.   The PX64, btw, has had a number of graphic issues since it came out, so anything is possible.
 
And, that doesn't excuse the poor handling of such situations in X1.
 
Like you, I've grown tired of having to be debugging so much, and that's another reason I wanted to try other hosts (even though they have their own problems).
 
I don't blame you regarding the bug reporting system.  It's antiquated at best, and I haven't really used it that much either because it's frustrating.
 

ba_midi

SteveStrummerUK

HumbleNoise


Wow Steve that's a pretty bizarre Screen Set. Can you change it back at all? Or do you have to reload the project? Does that fix it? Does it happen a lot?

 
Thankfully it's only happened the once - I thought I'd take a shot for posterity though!
 
I think I was trying to see if I could drag the Pro-Channel strip into the Multidock or something daft and I must have grabbed something else 
 
I just had to close X1 and re-open it and it was fine.

Steve,
 
I had that happen more than once - and when it did, it looked almost exactly like your screenshot.
 
 

He he, I'm glad I'm not the only one it's happened to Billy
 
The weird thing was I could still play the project, I just couldn't change the view on screen.
 
 

CakeAlexS


Are these issues being reported?
http://www.cakewalk.com/Support/ProblemReporter/

I generally report only those issues I can consistently replicate. These have all been a little slippery.