Thanks John T (my name and initials as well) After the educational post from Ryan I understand that. As I have explained to him, I didn't see this in the documentation, but I'm sure it's there. I don't like the design though. My carpal tunnel makes accidental clicks a common occurance.

The Console view is even worse with unintentional behavior. I was wondering why my mixes were changing and noticed weird changes to parameters on the console strip. As it turns out, the first time you activate or change any setting on a channel, the entire strip becomes active. If you scroll up and click on the input gain and scroll back, all controls are active. You don't have to click on anything, just mouse over and move the scroll wheel. Whatever you mouse is over will change. If you're not over any controls, the entire console view will scroll. Click on another view or another channel and the console is inactive until you click a control.

Is this more pilot error or another thread??

Pedro! More Gordon's pour favor!

John T

ampfixer


The first time I open PC on a given track, moving any of the controls will turn on their respective section of the PC. A careless click turns on that section and I have to shut that section off with the little blue button. If I then go to another track and come back this will not happen. I have to deliberately turn on that section of PC with said button. I made up a project with 50 tracks and the issue was repeatable on every track, every time.

As discussed elsewhere, that's the intended behaviour, not a bug. For what it's worth, I don't think it's a good design.

There is in fact a bug or Ryan is wrong and here's why ...

Read again what Ryan said ...

"This means that when you create a project and a ProChannel module is auto-enabled once, it will never auto-enable again."

That's not what is happening though ...

What is happening is ... when you save and close your project, then re-open it, the auto-enable feature that was supposed to only activate "once" and "never auto-enable again." actually in fact does become enabled again.

So, again, it's one of two things ...

A. A bug.
B. Ryan is wrong.

I'm starting to think some of you are just seeing what you want to see to benefit your point even though the facts are staring you in the face.

Bub

John T

ampfixer


The first time I open PC on a given track, moving any of the controls will turn on their respective section of the PC. A careless click turns on that section and I have to shut that section off with the little blue button. If I then go to another track and come back this will not happen. I have to deliberately turn on that section of PC with said button. I made up a project with 50 tracks and the issue was repeatable on every track, every time.

As discussed elsewhere, that's the intended behaviour, not a bug. For what it's worth, I don't think it's a good design.

There is in fact a bug or Ryan is wrong and here's why ...

Read again what Ryan said ...

"This means that when you create a project and a ProChannel module is auto-enabled once, it will never auto-enable again."

That's not what is happening though ...

What is happening is ... when you save and close your project, then re-open it, the auto-enable feature that was supposed to only activate "once" and "never auto-enable again." actually in fact does become enabled again.

So, again, it's one of two things ...

A. A bug.
B. Ryan is wrong.

I'm starting to think some of you are just seeing what you want to see to benefit your point even though the facts are staring you in the face.

Here's the way it is supposed to work, and the reason why.
 
You decide if yours works like this or if there's a bug...
 
------------------------
 
ProChannel has its own section of code in the software, its own .DLL  For each track that you activate PC, a new instance of the code is loaded.  If you haven't activated PC on ANY track then NO instances of PC will be running or even loaded, so it can't turn itself on or off.  Simply displaying the PC GUI does not load/activate PC.
If you start a new project and PC opens up and activates/turns on without you touching it, then there is a bug in the base X1 code that activates PC.  It cannot be a bug in PC as that will not even be loaded.
 
To make workflow easier it is assumed that the first time you adjust ANY of the controls in a PC module that you actually intend the PC to be turned on.  You wouldn't sit around turning the knobs on a hardware mixer without it being switched on, (other than to pretend to your boss that you're actually working...) and you wouldn't sit tapping away on your keyboard without turning on your computer first.  This saves 3 click per track times the number of tracks in your project.  More importantly it means you just open the PC and start using it without having to even look to see if it is on or not.
 
Once a module is activated/on, if you deliberately turn it off (with the off button) the auto-on feature is disabled for that module.  You've made the point that you want the module turned off and any accidental touches of the controls will not turn it on. You must press the on button.
 
Edit to add: 
 If you save the project and close down,  next time you open the project the auto-on flag for each module that is turned off will be reset.  
 
 It appears that the state of the auto-on flag is not being stored in the project.  This may be an oversight (bug) or it may be deliberate.  For me, when I come back to a project after 3 months I don't remember which of the PC modules on which tracks I didn't use and which ones I did use but turned off..   So it is logical for the auto-on feature to work.

Karyn

Bub

John T

ampfixer


The first time I open PC on a given track, moving any of the controls will turn on their respective section of the PC. A careless click turns on that section and I have to shut that section off with the little blue button. If I then go to another track and come back this will not happen. I have to deliberately turn on that section of PC with said button. I made up a project with 50 tracks and the issue was repeatable on every track, every time.

As discussed elsewhere, that's the intended behaviour, not a bug. For what it's worth, I don't think it's a good design.

There is in fact a bug or Ryan is wrong and here's why ...

Read again what Ryan said ...

"This means that when you create a project and a ProChannel module is auto-enabled once, it will never auto-enable again."

That's not what is happening though ...

What is happening is ... when you save and close your project, then re-open it, the auto-enable feature that was supposed to only activate "once" and "never auto-enable again." actually in fact does become enabled again.

So, again, it's one of two things ...

A. A bug.
B. Ryan is wrong.

I'm starting to think some of you are just seeing what you want to see to benefit your point even though the facts are staring you in the face.

Here's the way it is supposed to work, and the reason why.
 
You decide if yours works like this or if there's a bug...
 
------------------------
 
ProChannel has its own section of code in the software, its own .DLL  For each track that you activate PC, a new instance of the code is loaded.  If you haven't activated PC on ANY track then NO instances of PC will be running or even loaded, so it can't turn itself on or off.  Simply displaying the PC GUI does not load/activate PC.
If you start a new project and PC opens up and activates/turns on without you touching it, then there is a bug in the base X1 code that activates PC.  It cannot be a bug in PC as that will not even be loaded.
 
To make workflow easier it is assumed that the first time you adjust ANY of the controls in a PC module that you actually intend the PC to be turned on.  You wouldn't sit around turning the knobs on a hardware mixer without it being switched on, (other than to pretend to your boss that you're actually working...) and you wouldn't sit tapping away on your keyboard without turning on your computer first.  This saves 3 click per track times the number of tracks in your project.  More importantly it means you just open the PC and start using it without having to even look to see if it is on or not.
 
Once a module is activated/on, if you deliberately turn it off (with the off button) the auto-on feature is disabled for that module.  You've made the point that you want the module turned off and any accidental touches of the controls will not turn it on. You must press the on button.
 
Edit to add: 
 If you save the project and close down,  next time you open the project the auto-on flag for each module that is turned off will be reset.  
 
 It appears that the state of the auto-on flag is not being stored in the project.  This may be an oversight (bug) or it may be deliberate.  For me, when I come back to a project after 3 months I don't remember which of the PC modules on which tracks I didn't use and which ones I did use but turned off..   So it is logical for the auto-on feature to work.

Hi Karyn,

That makes total sense. The point I was trying to make to John T was, what Ryan had posted said it will 'never' auto-enable again once it is turned off. If they intended for it to re-enable after you re-open your saved project then you would think they would state that it resets.

That particular function I never noticed before, ampfixer brought it to my attention and asked me to test my system and see if I could repeat it and I could. Ryan mentioned it in the other thread thinking it may help, but it's unrelated to the problems skullsession, myself and others are seeing.

Bub :)

Sometimes I turn the dials and the PC doesn't activate so I try to turn it on manually and it is still dead. It's a drag that it's still a bit wiggy and the fact the Cakewalk guys can't emulate the problem doesn't give me hope that the problem will be addressed in x1c. But life goes on...