On a current project I automated the "PC-Bus EQ Enable" on the prochannel EQ on a buss.  Automation Read is enabled for the buss but the automation will not work unless the ProChannel inspector is open for that buss.  Can anyone else confirm this?
 
Sonar Producer X3a - 64
Intel i7; 32GbRam; GeForce GT630; Windows 7

Unfortunately, the automation did not work when rendering with or without the prochannel displayed in the inspector.  I had to use a different EQ in the buss effects bin and disable the ProChannel EQ.  I do not know if this is a failure of all ProChannel FX automation or not.  Hopefully not - I kind of liked the fly-out EQ.

I came across the same problem ages ago, but with the ProChannel FX Chain enable/disable. The automation would not work unless the ProChannel in question was open (I think it worked if the PC was open on the console). Cakewalk replied on the forum that they were aware of this limitation but that fixing it would break a bunch of other stuff, so there was no fix planned. I don't know how they feel about it now.

There is a similar problem with the arpeggiator on/off - automating it does nothing unless the track it's on is in focus.

PS I guess the only viable workaround would be to automate all of the EQ parameters and reset them all to default instead of triggering an EQ disable. Not very helpful, I know!

Thanks for the reply.  I wonder if this is for all automatable parameters or just the enables.  With the amount of automation I use, the ProChannel would not get much use if all automation is broken.  I wonder why they do not just not expose a parameter which does not work.  Many plugins do not expose an enable/disable parameter (I had to hunt to find an EQ with one so I could use that envelope).  I'll start a bug report.

As far as I know the problem only applies to the enable.

sharke
I came across the same problem ages ago, but with the ProChannel FX Chain enable/disable. The automation would not work unless the ProChannel in question was open (I think it worked if the PC was open on the console). Cakewalk replied on the forum that they were aware of this limitation but that fixing it would break a bunch of other stuff, so there was no fix planned. I don't know how they feel about it now.

There is a similar problem with the arpeggiator on/off - automating it does nothing unless the track it's on is in focus.

Hmm, and you have to turn off "Fast Bounce". At least I do anyway - that's in X3b.
 
My workaround is having the ProChannels open in the CV, and doing a slow bounce - doesn't have to be audible bounce, just not a fast bounce.
 
Cheers - Cliff