PianoTEQ's performance of MIDI renditions from notation software.

Greetings,

I've noticed a few posts related to the problem of pedaling being "glued" when exporting MIDI files from a user's notation program, specifically Musescore, and playing either through import or as a plugin into PianoTeq. This might also be an issue from other notation programs, but no experience is had with that.

Musescore exports connected/continuous pedaling in such a way that the [on/off events] of the sustain pedal are sent at the same event-time/tick, and this, with how PianoTEQ handles events, doesn't work at all well.

The reason for this post is to make mention of a workaround in fixing the issue, but it requires just a bit of manual MIDI editing.

After exporting a MIDI file from MuseScore, there are two programs so far that I've found that can fix the problem quickly: Cocko's Reaper (very affordable and cross-platform) and Bandlab Cakewalk (completely free for Windows). I specifically tried a few other free editors/DAWS for this and couldn't get it to work: e.g., [Tracktion 7 + Linux's Muse or the free MidiEditor.org].

Anyways, it's purely logical what needs to happen: separate the pedal-offs from the pedal-ons by a small amount of time, either by nudging the pedal-on events forward, or nudging the pedal-off events backward. It'd be terrible if you had to do this by hand under certain circumstances.

The MIDI software must be able to:
1) Select CC events through a filter (min/max values)
2) Allow for moving CC Events without touching noteOn events.

Reaper and Sonar both have a MIDI Event Filter function that allows the user to choose specific CC#s and minimum/maximum values.

1) Utilize the software's MIDI Filter: CC#64 (Hold/Sustain) + [0 Min/Max value] events (or 127 if nudging to the right)

2) Reaper allows the user to merely mouse-drag the selection, so drag to the left a tad or use an action event for movement based on a small grid size (like 1/32nd or 1/64th)

3) Sonar doesn't allow for mouse-dragging CC events, but it does have a specific nudge function which is an equivalent command that can be set as a keyboard-shortcut.

This didn't get into the gritty-details, but the purpose here is to have a post so that if someone finds the problem in the future and doesn't know what to do and searches this forum, at least they ought to know that they can fix this and for free, but it will require a little bit of learning some software and some manual workaround-age. If someone tries this and still has a problem, maybe a Reaper/Sonar user can help them out here, or I'd be glad to help further if need be.

Good luck.

P.S. Maybe in the future Musescore will fix this and the workaround mentioned here will be antiquated, e.g., maybe they'll separate pedal on/off values by a few ticks in a future update.