Pianoteq doesn't see Musescore's pedal off.

• May 27, 2016 - 23:08

Pianoteq, which I have to say is perhaps the finest software experience I have ever encountered does not recognize pedal off MIDI signals generated by Musescore. Pianoteq does respond to the pedal on, but once it goes on, it's stuck forever. These pedals do work with the Musescore MIDI player when playing a score directly from the .mscz scores. The Pianoteq sees the sustain pedal as Controller 64, and responds properly to a Casio keyboard pedal. Presumably this is a General MIDI standard. Does anyone know a fix to get the Musescore pedal marks to work with Pianoteq from an exported Musescore .MID file?

This is off topic, but also Musescore does not respond to the Casio PX-150 output, which works perfectly with Pianoteq. This means I cannot use the Casio to enter notes into Musescore, at least until a cure is found.

Comments

• May 27, 2016 - 23:33

You may find this discussion helpful, particularly my post about the possibility that the pedal on/off events are too close together for PianoTeq to pick up.

https://musescore.org/en/node/109176

Incidentally Controller 64 has been defined as Sustain (or Hold) since MIDI version 1.0 was defined in 1983.

How is your PX-150 connected to the computer? And are you using JACK or Portaudio MuseScore drivers?

Reply

• May 29, 2016 - 14:42

I just plug it into the USB port on my Laptop, and it works perfectly at least with the Pianoteq software. I think my audio set up is ALSA on Linux. The Control Center says I'm using built in Audio. The pedals do work with the Musescore playback, but not when exported to a MIDI file played back by Pianoteq. I see someone else had the same issue. I'll try adding space between pedals in Musescore and see if that helps.

Put space in between pedals in Musescore, but it didn't help with Pianoteq playback. The pedal is stuck down in Pianoteq.

Reply

• May 29, 2016 - 19:22

Merely putting in visual space wouldn't help - you'd have to actually end the pedal befopre the start of the next, rather than having them occur at the same time. But you shouldn't need to do any of this. Any program that specializes in playing MIDI files should be able to handle this correctly; probably there is just some setting you need to find in Pianoteq.

Reply

• May 30, 2016 - 09:01

I'm suspecting a tick resolution or latency issue here.

Or in plain language MuseScore is placing the events too close together in time for PianoTeq to respond to.

Currently MuseScore's tick resolution is (unless it has been changed in 2.0.3) 960 ticks per quarter note. So consequently a 128th note (or semihemidemisemiquaver for non Americans) occupys 30 ticks.

MuseScore is placing the Hold on event 1 tick after the Hold off event. I would try going into your MIDI sequencer and changing Hold On events to occur 10 ticks after the preceding Hold off event.

A real performer would not be able to operate the sustain pedal in 1 tick even at slower speeds.

Let us know if this works, and we can perhaps get a feature request going to change the default tick spacing of the Hold events.

Reply

• Dec 5, 2016 - 20:06

Hi @ChurchOrganist, I am running into the same issue.

If you do Pedal on and off, wait for one bar and then Pedal on and off again, it works.

I would try going into your MIDI sequencer and changing Hold On events to occur 10 ticks after the preceding Hold off event.

how to do this?

I guess we (Users of Pianotek) needs to extend the "Pedal Off Midi" time when doing export a sheet as midi file from Musescore.

Any idea about that (settings?) would be great

Thanks for any help
Tom

P.S.: You will find a sample and PDF Sheet attached.

Attachment Size
Scarborough_Fair.pdf 150.55 KB
Scarborough_Fair.mid 731 bytes

Reply

Do you still have an unanswered question? Please log in first to post your question.