I know it’s probably no comfort but my sustain pedal data is handled just fine and my specs/platform are similar to yours. Can you give more data of how exactly everything is setup or show a video of how the issue is occurring? Things that I’m wondering:

- what sustain pedal are you using and how is your sustain pedal connected to your computer?

- Does a sustain pedal function via any other hardware? You can easily test this with the QWERTY Keyboard device in Studio One- I think the Tab key is mapped to sustain in that situation.

- Can you write CC64 with a knob on any other control surface and test it that way? It may sound silly but one time I accidentally assigned CC64 to a global parameter with Control Link and it would intercept it before it reached the instrument...

Side note, I’m pretty sure the “since 2016” issue you mentioned was one where sustain pedal data would not record properly on Loop 2+ when loop recording on an Empty Instrument Track. Are you using an Empty Instrument Track?

robertgray3 wroteI know it’s probably no comfort but my sustain pedal data is handled just fine and my specs/platform are similar to yours. Can you give more data of how exactly everything is setup or show a video of how the issue is occurring?

Ugh... correct, no comfort
But yes, I can definitely provide more info

robertgray3 wrote- what sustain pedal are you using and how is your sustain pedal connected to your computer?

Just a regular ProLine Foot pedal connected directly to my Yamaha XF8 keyboard which is connected to the iMac via a USB port

robertgray3 wrote- Does a sustain pedal function via any other hardware? You can easily test this with the QWERTY Keyboard device in Studio One- I think the Tab key is mapped to sustain in that situation.

The sustain pedal functions as expected outside of Studio One with every other application I have. I can affirm that the QWERTY keyboard sustains the note just fine using the tab key although I would think that only affirms that a software keyboard controller works.

robertgray3 wrote- Can you write CC64 with a knob on any other control surface and test it that way? It may sound silly but one time I accidentally assigned CC64 to a global parameter with Control Link and it would intercept it before it reached the instrument...

Unfortunately I can't as I use the XF8 as my only controller interface and it is only for triggering MIDI keys, sustain, pitch bend and modulation info. I don't really have any need of additional controller interfaces. Aside from it, I only use Console1 on occasion as a Channel strip.

I'm providing a screenshot of the MIDI setup for the XF8 within SO5 and have also recording a short video showing the issue.

You will note in the video that SO5 is actually receiving the Sustain MIDI event during the record; it simply doesn't record it. Even after manually adding the event to the editor there is no info showing.
I recorded a pitch bend near the end just to show that both types of events are being recognized but SO5 is only recording the pitch bend.

The MIDI event indicator on the transport and the External device window (also included in the vid) both affirm the sustain pedal event is being acknowledged but neither during the play or record is SO5 sustaining the event.

SO5 External MIDI Setup

SO5 Not recording pedal sustain events

Hopefully its a simple fix that I'm missing but I can't identify any SO5 setting to resolve the problem and I'd accept it as a hardware or software related issue with my Keyboard or drivers only if it were not for the fact that I have no issue with this in Cubase or any standalone of the identical VST instruments. Only in SO5

Thanks for helping out.

The QWERTY Keyboard device is software but it is functionally sending the same MIDI message if I remember correctly.

This happens with all plugins right, not just a few?

Also this might sound silly but have you tried deleting the User Device, closing Studio One, and making a new one? If you’ve mapped a lot of stuff you should back it up first.

Have you opened up the Studio One MIDI monitor and see if Studio One thinks that it's received it? I'm not near my DAW right now, but IIRC, you click on the MIDI icon at the bottom of the screen to open it.

robertgray3 wrote.....This happens with all plugins right, not just a few?

Also this might sound silly but have you tried deleting the User Device, closing Studio One, and making a new one? If you’ve mapped a lot of stuff you should back it up first.

This "happened" across all plugins that would support sustaining notes.
Notice the past tense here

I don't rule any advice out as being silly so I did delete the User Device, closed SO5 and created a new one per your suggestion and I'm glad to report the issue is resolved.

Though it doesn't give me a very confident feeling that it even occurred because I don't abuse the DAW in any way and having random issues crop up can be very frustrating. Especially those types that have no logical explanation except that they just "happen"

Thanks again! I can now resume my work having the functionality I expected

j0001s wroteHave you opened up the Studio One MIDI monitor and see if Studio One thinks that it's received it? I'm not near my DAW right now, but IIRC, you click on the MIDI icon at the bottom of the screen to open it.

Thanks for the suggestion j0001s!

Yeah, I did confirm that SO received the MIDI message

Occasionally going from a major version to a major version there can be odd behaviour with external devices but once you do delete and make a new one there will rarely be any issues from that point on.

Does your sustain pedal have a polarity reverse switch?

Note that some keyboards (including Yamaha) reverse close to sustain/open to sustain pedal response depending on if the pedal is plugged in before or after the keyboard is powered up. If your pedal has a polarity reverse switch then try using it reversed (and reverse your plug-in/power up routine too). See if that makes S1 register the pedal input

mivey wroteThanks again! I can now resume my work having the functionality I expected

No problem. Corrupted external device maps (at least I think that’s what they are) are an annoying issue but luckily they’re pretty rare, the fix is easy, and as Jemusic mentioned it usually only happens when upgrading to a major version. At least that’s the only time I’ve seen it happening outside of when I’m building custom devices, but during that process I’m constantly changing the Device maps anyway.

Unfortunately I am running into the same issue, and removing and re-adding the User Device doesn't fix it. The MIDI Monitor does register my pedal, so the signal is getting to Studio One, but apparently isn't reaching my plugins... Any ideas?

robertgray3 wroteAlso this might sound silly but have you tried deleting the User Device, closing Studio One, and making a new one? If you’ve mapped a lot of stuff you should back it up first.

Can you explain what the User Device would be? Do you mean the keyboard which the pedal is connected to?

Any update to this? Seems like such a silly thing not to work. I have 2 sustain pedals...they both work fine, except for with Studio One.