My A-Pro 800 has started spitting out midi controller data. It happens at random and it can be different CCs.

On occasions the Midi input "meter" on the Sonar MIDI track is flickering when the keyboard is untouched.

Any ideas would be appreciated. My fear is the Keyboard has a fault.

Just a couple troubleshooting questions:
Do you have an expression or other pedals attached?
Are you using MIDI merge/thru with any other devices?
Are you still using the same Control template? If you have accidentally switched to one that uses encoder simulation, that will send CC data whenever the pots aren't dead center. Super irritating. You can also use the A-Pro editor to see if encoder simulation is being used on your current template.
 
I believe it's possible to re-flash the firmware. It's downloadable from Roland's website. You could try that if none of these other ideas bear fruit.
 
 

I have this issue on occasion with an Axiom Pro 61 controller, and it is quite annoying.  Seems to generate random mod wheel events all on its own.
 
Bob Bone

mesayre
Just a couple troubleshooting questions:
Do you have an expression or other pedals attached?
Are you using MIDI merge/thru with any other devices?
 

Thanks. I disconnected every thing. Connected the A-PRO Worked fine. I then connected the hold and expression pedals. Worked OK. Turned on the old XP10 connected through the MIDI port of my Quadcapture. Still OK. I will keep it like this for a couple of seasons and see if it reoccurs.

I have yet to connect a AKAI Lp25 mini keyboard, It will be tomorrow before I try that.

I spoke too soon. Its back, its always been radom in any case so there have been trouble free periods.
 
I left Sonar recording unattended for a couple of hours and got 53 events (CC77 ad CC66) which is less frequent than previously observed.
 
Incidentally I notice the effects using some VSTi in standalone, particularly EW Play when a parameter chances for no apparent reason.
 
I can't see firmware on the website, only drivers and I have the latest WIN 10 driver. I have opened a support ticket with Roland to see what they suggest.
 

A case of blindness last night. I found the firmware here http://roland.com/support/article/?q=downloads&p=A-500PRO&id=62152876
 
I will wait until this evening to see if there is any response from Roland before trying the update. 

A quick response from Roland, who said as the board is over 3 years old I need to refer it to a third party engineer, they provided contacts for the closest to me.
 
So I reloaded the firmware, a much newer version than it was running. But its still the same. Looks like its going to cost money, given the age (6 years) I wonder if a replacment is a better option?
 

Could you identify which controls are assigned to that CCs? If that are "not important" controls, you can filter them out using MIDI FX or other methods.

Well it had mostly been throwing out CC 65 (Portmento) and CC 77 (Vibrato Depth), but i have just seen some CC 76 (Vibrato depth). In the past there have been others. I have a feeling that CC 7 (volume) or some other CC that affects volume is also being randomly transmitted as i have had unexplained changes in volume both in Sonar and stand alone VSTi's
 
I think filtering is going to be a long shot!  Best work around to date is to put up with it and edit out the spurious events after the fact.

A bit more on this - I changed the driver setting "Midi In" to "Light Load". The help file or manual does not specify what this does, only that you would not normally use it. But so far I have not seen spurious data blip since making the change.
 
I did find this definition of Light Load in UA20 documentation.

while the Light Load tick box for the MIDI In lowers the polling frequency at the expense of a slightly higher MIDI latency.

 
I don't see how latency settings would result in spurious data but I have my fingers crossed!