Jump to content

Sustain Pedal Issue - CbB 2014.07 Build 108, Roland A-800PRO


Recommended Posts

I am using CbB with a Roland A-800Pro and a MGear sustain pedal on Win11. This setup has worked for years with no problems.

My sustain pedal recently stopped functioning in CbB and I'm going crazy trying to troubleshoot it.

It seems that CbB simply stopped seeing the CC data from the input. This MAY be caused by my latest CbB update (2014.07 Build 108), but I can't say with certainty that's the case since I've worked on projects before and after that mostly haven't used sustain at all.

Here are some of the things I've tried/considered:

1) MidiOx shows sustain pedal activity (screenshot attached)
2) Pedal works fine with other DAWs
3) Event List in CbB shows no pedal activity while recording or playing
4) I added some sustain events manually in CbB and they play back properly (screenshot attached)
5) Polarity on the pedal wasn't changed and isn't an issue. (see 1-2)
6) This issue may have started with the latest CbB update but I'm unsure
7) I haven't touched any CbB settings in a long time.
8) I've restarted my computer, CbB, and A800Pro multiple times in various orders. Nothing.
9) Based on other sustain pedal threads, I've sifted through all the MIDI functions under Preferences in CbB and everything seems in order.
10) Every other function of my A-800 works fine in CbB and any other DAW.
11) I have no clear reason at this point to suspect either the pedal or A-800 are a factor.

I'm just lost. I've spent so much time with this that I'm about ready to just switch DAWs but I've used Cakewalk/Sonar for over 20 years and don't WANT to change.

Please save me!


1) Midi Ox
MidiOx.png.905c0b8d9294501ff8bf1b728277dc4e.png

2) Event View in CbB - manual entry
CbBEventView.png.bf8d203c5f8fce87c45c0fa1f1268e86.png

Link to comment
Share on other sites

1 hour ago, D_Maynard said:

9) Based on other sustain pedal threads, I've sifted through all the MIDI functions under Preferences in CbB and everything seems in order.

Sorry for asking the obvious, but that includes verifying that the Controller checkbox in Preferences > MIDI > Playback and Recording | Record is checked?

Link to comment
Share on other sites

31 minutes ago, Canopus said:

Sorry for asking the obvious, but that includes verifying that the Controller checkbox in Preferences > MIDI > Playback and Recording | Record is checked?

No need to be sorry, I've been very thorough, but sometimes it's the simple misses! I think you meant to say is the "Controller" box checked, and it is. Here are my settings on that page.

PrefsCW.png.75a12ee836f45b8011b43d2ed7c5fd93.png

Link to comment
Share on other sites

16 hours ago, msmcleod said:

The most common reason for this:

(image in previous post)

Best to set the controller to something you're unlikely to use, e.g. 120.

If you're not using MIDI events for triggering commands at all, uncheck "Enabled".

I saw that and this is my current setting for that page:

Keyboardshorts.png.46224e72e00b57ac29469a752bbc7601.png

Link to comment
Share on other sites

  • 2 weeks later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...