John


That was supposed to be fixed in X1b. Do you have the X1b patch?

I certainly have and I'd like to think most people would keep up to date. It definitely made no difference to me.
 
Grum.
 

I'm still seeing it too. I also noticed that a fix for it wasn't listed in the list of X1C fixes.

-e.B

I have - literally - spent days trying to reproduce this bug and Bub's reports of the Pro Channel having a mind of its own.  This is running on a virgin install of Windows 7 (x64) Pro, and X1 installed and patched to X1b.   No other software, VSTs, add ons - either music related or otherwise.  Been running this configuration for a month and have not seen either problem manifest itself.
 
Is it possible that these are bad drug interactions between X1 and other software and not a direct problem with the X1 code per se?
Having been a developer in a much larger software house than Cakewalk, I can guarantee everyone on this forum that nothing will get done to fix these problems until one of the bakers can regularly recreate the problem.  They don't have time to chase ghosts.  Possibly those of you who are having this problem can compare notes to determine what you have in common (hardware, drivers, other software (Reaper?)) and see if those of us who aren't seeing the problem possibly don't have something installed that is causing the problem?
 
I'm sure that if anyone here can determine how to reproduce the problem in such a way that one of the Bakers can reproduce it that Cakewalk will get the fix in their schedule.
 

I can confirm I've had it happen a number of times, X1 b build 255, 

Just because you haven't seen the problem doesn't mean it doesn't exist and isn't confirmed. The reason 99% of these arguments come up is because people don't take the time to read, or misinterpret things either intentionally or unintentionally.

Bub,  I do believe that there is a rather serious bug (probably more than one) here.  I spent a lot of time trying to verify that it wasn't causing problems for me (yet).  I'm not saying that this isn't happening, just that it isn't happening consistently.  This is happening in your environment, but not in mine, What is making the difference?  I have tried to recreate the problem and have not been able to.  I imagine that the X1 developers are in the same boat.  Following the threads related to these items it is clear that you have also spent a lot of time trying to determine what may be making this happen.
 
Before Cakewalk can do anything about it, one of their programmers needs to be able to recreate the problem on his/her developer workstation.  Once they can recreate the problem in debug mode it is usually a (relatively) simple process for them to fix it. 
 
So what has to happen to get the problem to a point where Cakewalk can make it happen?  It really comes down to those people who are experiencing the problem isolating what the conditions are that make it happen.  Possibly this is only happening on computers that have X1 and 8.5 installed.  Possibly it is only happening on computers with M-Audio MIDI drivers or G-Force 8500 video cards. 
 
It may be that we need to have everyone who is encountering these problems compare notes to see what they are doing in common.  This may lead to a set of conditions that will allow the programmers to get to the root cause of the problem.  I believe completely that they would fix this if they knew what was causing it.  If we - the users - can't identify the conditions that create the problem I don't think Cakewalk will ever be able to correct the problem.

gcolbert

Just because you haven't seen the problem doesn't mean it doesn't exist and isn't confirmed. The reason 99% of these arguments come up is because people don't take the time to read, or misinterpret things either intentionally or unintentionally.

Bub,  I do believe that there is a rather serious bug (probably more than one) here.  I spent a lot of time trying to verify that it wasn't causing problems for me (yet).  I'm not saying that this isn't happening, just that it isn't happening consistently.  This is happening in your environment, but not in mine, What is making the difference?  I have tried to recreate the problem and have not been able to.  I imagine that the X1 developers are in the same boat.  Following the threads related to these items it is clear that you have also spent a lot of time trying to determine what may be making this happen.

What part of Cakewalk has been able to recreate the problems we're talking about and has released patches to fix some of them, and have acknowledged they were able to recreate another and are working on it, don't you understand? (By the way ... these are all good things, not bad!)

The part where they have been able to recreate problems and released patches, or the part where they have acknowledged some and were able to recreate it and are working on it?

This is what I mean when I say, "The reason 99% of these arguments come up is because people don't take the time to read, or misinterpret things either intentionally or unintentionally."

Sorry gcolbert, but this stuff is getting really old. I'm so sick and tired of people coming on here telling everyone there's no way a problem can be fixed unless Cakewalk can reproduce when in fact there is a recognized problem and there has been a patch put out for it. Can you see why that gets old? Think real hard about it and then get back to me. Ok?

Thanks,

Bub.

JFC

X1b build 255... still random missing control bar here too.

Control bar disappears for me when I minimize a project and then open it.  Happens about half the time.  Control bar comes back if I close Sonar and reopen it.  Solution, I don't minimize projects.

Yep, it still happens here in X1C. It was supposedly fixed in X1b.

Or maybe there was another condition that caused it to disappear that was fixed.

The steps have been outlined in a few threads and several bug reports have been submitted.

Steps:

1. Go into preferences
2. Go to File-->Advanced
3. Turn on autosave, ie: Switch autosave to 1 minute for example.
4. Create a new project
5. Minimize Sonar and then maximize it a couple minutes later

I just did it again on my machine (Sonar Producer X1C, X64)

Note: Control bar must be docked for this to take place. Dragging the Control bar will fix the glitch.

Where's Bub when you need him...  
 
I thought the "final" fix for this didn't quite make X1c?
 

I have this issue on my X1C install.  Happens every time I switch to another user account in WinXP, then switch back.