EDITED FOR CLARITY Actually, I've been told repeatedly that you are the developers is are in fact unwilling to research issues if I cannot present you them with a replicable problem.

Where and when were you ever told this? We might ask you for more information, but we'd never say we were unwilling to investigate. I will say, however, that if I pester a developer to research something without a good place to get started, they will do the same thing support does to customers, they'll just ask us for more questions before they begin to research.

I believe that I said that a programmer CAN'T correct a problem that he/she can't reproduce.  Nothing about their intentions and willingness. 
 

Last time I remember PC muted when I was slip editing during playback and clicked timeline on the fly.

 
This sounds exactly like the bug we fixed. Look at your prochannel track carefully and check if you have an envelope for the enable accidently created. The envelope can be created if you have write enable turned on for the track and then accidently clicked the enable button on the prochannel module accidently during playback.
 

Bub,
 
  I'm sure that somewhere along the line I may have said something like what you paraphrased.  I spend a lot of my life trying to get my users to tell me what they did so I can chop their fingers off to keep them from doing it again.  Fortunately, my users have to put up with me.
 
  I am impressed that the CTO (Noel) has taken the time to come by here.  It really does show a deep commitment on Cakewalk's part to listen to their customers.  My CTO spends his time playng golf with the other corporate executives. 

gcolbert

Interesting that this seems to be happening to people who also run 8.x. Is there anyone who id only using X1 who is seeing this issue?

At one point I only had X1b 32/64 (no Quick Fixes) installed. It was before the QuickFix thing was started. It was one of the times I formatted to do a fresh install thinking that maybe something got corrupted and that might help.

After the format and reinstall of X1b not helping with the PC things I was seeing, I put 8.5 back on, so at that point I had X1b 32/64 and 8.5 32/64.

Thanks.

Bub

Noel Borthwick [Cakewalk
]

Last time I remember PC muted when I was slip editing during playback and clicked timeline on the fly.

 
This sounds exactly like the bug we fixed. Look at your prochannel track carefully and check if you have an envelope for the enable accidently created. The envelope can be created if you have write enable turned on for the track and then accidently clicked the enable button on the prochannel module accidently during playback.
 

mmmmmm...sounds like something I might have done here.....

PC (ProChannel)

I've had the unpredictable on/off occur on a fresh install on a WIN 7 x64 system with only X1b shortly after starting a new project from a template and also starting a new project without using a template. No envelopes activated even accidently. Checked, double checked and checked again and again.

It's also occurred with a fully loaded system as it would be in my studio with all my software.

Q fixes applied or bare X1b all the same as far as PC random on/off.

My problem in being able to report what happens is that it is so unpredictable but having spent so much time on X1 and going through the forums I have tried all the suggestions with no solution.

The other issue I have is that X1B was the first version I could run for more than a few minutes without it disappearing. I still have that problem and can't use X1 for any more than experimentation to try to learn the various changes from 8.5 to X1.

i'm not having a whinge. - just confirming that i too have the PC random on/off problem.

BTW I have a purpose built system that runs 8.5.3 perfectly smoothly. X1 is the first version since Cakewalk 7 that has been unusable for me.

I'm looking forward to X1C

Ryan Munnis [Cakewalk

---

Instead of going down this path again, why don't we collectively ask codamedia some questions, like:

1. What version of SONAR X1 was this project created in? You can find out the exact build by going to Project > Info and clicking on the [File Stat...] button. If the project is a .cwp file (not a .cwb file), it will list the exact build number the project was created in of the project next to "File Version".

2. Can you still reproduce the issue? If so, why not create a Problem Report and send us a copy of a project so that we can have the hard proof we're looking for.

3. Can you replicate this on a brand new project? It's important to find out if ProChannel is processing audio at all. It's also importing to find out if we're dealing with an issue that is related to a project made from a previous template in a previous build of SONAR.
 

Ryan - Thanks for taking the time to jump in on this thread.
 
1: X1b Producer Build 255
2: No I cannot reproduce this. I've tried many times but can't do it. Please see post #17 regarding this.
3: I always start with a custom template (build in X1b), and it does not exhibit this behavior. I opened a new project with this template again last evening and the PC was responsive on all tracks I tested.
 
I am very aware of the Steve Strummer example, and referenced that earlier in this thread. My experience was similar, but I'm sure not it's the exact same (I'm 32 bit, and other than this one time - the PC is responsive). On this occassion, like Steves problem, my Pro Channel was unresponsive. When I turned the knobs, the plot was not changing, the sound was not changing and there was no indication signal was even hitting the pro channel (yes - the indicator said it was on). As soon as I turned PC off, then back on - it worked and responded. 
  
Luckily this was on a bass track it was very obvious something was wrong when I re-opened the track. With the PC not working, the HPF was not engaged, and the bass was extremely over powering in the sub area. I didn't check, so I don't know if it was just this track - or all the PC's used in the project.
 
User error? Possible, but I can't see how or where! I am a creature of habit and work the same way on all projects. This was the first (and so far only) time I experienced this. I'm led to believe this is software related, and something prevented the ProChannel from waking up when the project was loaded.
 
I hope you can tell my my OP that I am not angry, just a little disappointed. I've seen the ghost myself.

Julien....I'm not nearly as "amused" as I was when I first loaded up X1 a few months ago to find that the ProChannel didn't even come close to working properly - while users were here telling us that it worked perfectly for them since day one.

Leaving aside the ridiculous changes to the GUI and moved placement of long-established tools, the fact that one of the main bragging points about X1 - the ProChannel - would self-determine its involvement in the mix was absolutely unforgivable.

At this point, I've lost total faith.  The release of this software in that condition was negligent and reckless.

And the fact that users are still reporting a ghost in the machine with ProChannel is quite telling.  I fully plan to give X1c another shot when it's released.  If it's not the software I was promised, X1 will simply get dumped into the growing pile of Sonar software that I've purchased but never been able to use in my professional environment.

I'm not easily pleased with "work arounds" and random behavior.  I didn't intend to pay Roland so that I could beta test their software.  I don't even have time to do that for free.  A bug is a bug.  Broken is broken....and we simply have no recourse.

And the reason I'm amused TODAY is that just now, basically on the eve of the release of X1c...and basically the same day that someone I've traditionally found very reliable at Cakewalk tells us the problem with ProChannel is (and has been) FIXED (and if you're having a problem it's most likely user error)...we have folks still saying things like... "Holy crap!  This really is happening!"

Add to that the unprecedented amount of damage control that's been happening on the forums by Roland employees....from belligerent users, to moderators, and all they way to the top of the Cakewalk hierarchy...it just makes me giggle.

Somebody's wrong here.  The software is either broken, or they've made things so convoluted that people don't realize they're screwing things up.