Mackie MCU Pro + X1 users with record button issues

I've got two record buttons that don't work.  One is on my Mackie MCU Pro and the other is on the Extender.  Both buttons are on the leftmost fader channel (#1 and #9 in my case).

The buttons work in a competitive DAW program so it's not a bad switch.

I'd like to see a show of hands of who has this hardware and whether or not you are seeing this issue.  I only got the unit a week ago and I swear it was working at one time.  I'm trying to figure out what I may have changed to make the behavior pop up or if this is a know issue that I have to ignore.  

FastBikerBoy


Sorry Dave,  not a clue what's going on there. I racked my brains since I first saw you mention this but nothing came to mind.

Only thing I could think of is as it's a PRO and mine is a ?? "Amateur" is that the pro might have additional settings or switches somewhere. 

I'd give up my "Pro" status to not have to pick up my mouse and click on the Record Enable widget for those tracks.  

WDI


You have this set up as a Mackie Control in Sonar control surfaces? Perhaps the key acts as a function key or footswitch and needs to be mapped? Totally guessing of course...

Yes, I'm familiar with the Mackie Control support screen.  In fact, I have my on preset saved.  I am wondering if any of my F button actions is affecting SONAR and making it lose the first channel on the hardware.  However, the select, mute and solo buttons work as intended and that's what has me perplexed.

John


It could be because you have the extender. It could be that the last and first record button are not synced right to X1. 

I disconnected the Extender and removed it from the Control Surfaces in the Preferences.


I've also deleted both units and set them up in the Control Surface preferences and changed the order in which they were installed.  No joy.


Thanks and keep the ideas coming.

Dave. Does the non-record channel on the MCU follow the SOnar track as you step through Sonar's tracks via the MCU?

i.e. Press the move right channel switch on the MCU does the "faulty" channel move as well or stay on the MCU's first channel?

Very strange. You'd think if it's always the same channels that it'd be a setting on the units but as it only happens with Sonar that rules that out. By the same token if it doesn't change with the track in Sonar it'd suggest that it's not that either.

I'm sure John's using the older model as I am. I wonder if there's any pro more users. I wonder what FreeX is using? Just in case it's specific to the pro model.

Seems to be a SONAR X1 issue to some sort of extent.  I loaded SONAR 8.5 and I configured the control surfaces and the record buttons worked as expected.

stonehedge

homemade PDF paper cutout SONAR template

Mod Bod


Maybe it's because I'm using a homemade PDF paper cutout SONAR template held on with Scotch tape?

Hi Dave
No it can't be that. My "homemade PDF paper cutout SONAR template" is working just fine here . 
Did you by chance activate something in ACT?
Have you filtered any SYX EX info on any of the midi ports?
Any chance the fader banks channel arrows have moved you by one.
Would you still have 8.5 on your machine to cross reference with.
Just trying to come up with ideas to help
 

ACT's not it - Mackie doesn't do ACT.
Sysex is set to record
Moving the fader banks or moving the channel still gives the same result
The unit operates properly in 8.5


I've also deleted the TTSEQ.ini and the ctrlsurface.dat files and let them be rebuilt.  

FastBikerBoy


I'm clutching at straws here but have a look at your track manager sync settings and the "Ctrl strips visible in" setting in the control surface dialogue.

Still wouldn't explain why all the other controls on that channel are working though. 

All those settings check out.  I even tried some variations on the theme.


Last night I noticed that on my Frontier Tranzport, non of the SONAR channels would respond to the REC enable button it has.


I disabled the Tranzport to see if that was conflicting with the MCU but it didn't resolve the problem.

Getting even more frustrated here as SONAR X1 battles me over control of the MCU faders.  I move the fader and X1 pushes it back into where it is set.

Mod Bod


Getting even more frustrated here as SONAR X1 battles me over control of the MCU faders.  I move the fader and X1 pushes it back into where it is set.

Sounds like you already have an automation envelope on that track. if you want to change it with the fader, enable write mode on the track and move the fader

Mod Bod

I've also deleted the TTSEQ.ini and the ctrlsurface.dat files and let them be rebuilt.  

I wonder if temporarily renaming the ctrlsurface.dat in X1 and replacing it with the one from 8.5 might fix the issue

stonehedge

Mod Bod

I've also deleted the TTSEQ.ini and the ctrlsurface.dat files and let them be rebuilt.  

I wonder if temporarily renaming the ctrlsurface.dat in X1 and replacing it with the one from 8.5 might fix the issue

Tried that but it didn't work.


Solved the fader control issue.  I had turned off recording pitch wheel because it was doing weird things to my softsynths last night.  Evidently, the MCU uses pitch wheel messages for the volume faders.  Haven't got a clue why they would do that.

Hi Dave,
You said:
"I move the fader and X1 pushes it back into where it is set."

I sometimes have that on my MCU but when I move the fader again it stays where I moved it. I always thought it was just waiting to receive the position update back from sonar.

From reading this entire thread it does sound like somehow X1 got hosed and is not responding to the CC or note# that the MCU Rec/Rdy 1 switch is sending out yet, 8.5 does.

Have you talked to Cakewalk support about it yet?