Linear pedal markings
I have been unable to find this subject in prior posts. I have yet to find a feature in MuseScore which allows this. Some may find this useful.
I have found a free text font which has characters allowing you to indicate piano pedal marks using lines instead of the traditional Ped. and * characters. They include pedal down (L-shaped), pedal up/down (inverted V) and pedal up (backward L), plus an extender line. Of course, since these are text characters, they have no effect on playback.
(see attachment)
It is called “DVMarticulations” and can be downloaded from http://www.ffonts.net
| Attachment | Size |
|---|---|
| Linear pedal markings.mscz | 1.84 KB |
Comments
It occurred to me that no one could see the example properly who had not already downloaded and installed the font I mentioned.
So I am attaching a .PDF file for viewing the final results.
By the way, for those who prefer, the text can be changed to Bold to make the pedal markings more prominent.
In reply to Linear pedal markings by Bill Watkins
Bill did your PDF originally have "%20" in the file name when you attached it or were those added by the website?
The reason I ask is to try and narrow down a bug. When I click on the link for the PDF it says "Page Not Found" but if I go to the following URL it works:
//musescore.org/sites/musescore.org/files/Linear%2520pedal%2520markings[1].pdf
In reply to Bill did your PDF originally by David Bolton
I did not add the "%20" to the file name.
I created the PDF file in MuseScore in the usual way using "Save As." I did not notice if it added the extra characters.
I just duplicated my efforts again on my computer. The file name did not have any extra characters. Of course, the extension was changed to ".pdf" but no other changes were made to the file name.
Hope this is of use.
In reply to "%20" by Bill Watkins
FWIW, %20 is the ASCII representation of the space character (in hexadecimal - base 16). Many browsers will automatically convert spaces to %20 when uploading / downloading files with spaces in their names, because on a lot of older systems, spaces in filenames were not allowed or would cause problems. And even today, while spaces are normally OK in filenames, and the translation between space and %20 is normally handled automatically by browsers, it's not foolproof. So it's still generally a good idea not to include spaces in filenames you intend to share online.
Ah, yes. Good old ASCII 32 -- the space. I didn't realize the entire world had not caught up with it.
Attached is file "Linear_pedal_markings.pdf"
In reply to Ah, yes. Good old ASCII 32 -- by Bill Watkins
can't wait for it to be part of the program now!
Hello Mr Watkins
Thanks for this post - it really made matters simple for me. Even though this is not a solution, your method fixes the issue reasonably well.
In order to help the next newbie that comes across this post and/ or issue, I'm attaching pictures that list the steps I took to successfully generate linear pedal markings.
--------------
Step 1: see "installFonts_windows.png"
![installFonts_windows.PNG]( "installFonts_windows.PNG")
Step 2: see "pedalUp_linearPedalMarkings.png" (instructions in blue; output in green)
![pedalUp_linearPedalMarkings.PNG]( "pedalUp_linearPedalMarkings.PNG")
In reply to Hello Mr Watkins Thanks for by nsawkar
For the record, 2.0 will support these markinga with no need for special fonts or workarounds, and they will play back correctly too.
In reply to For the record, 2.0 will by Marc Sabatella
What's the tentative release date for MuseScore 2.0?
In reply to What's the tentative release by nsawkar
"When it's ready" is still the only answer. But Beta 1 was released a few months ago, Beta 2 is tentatively scheduled for the end of the month, I'd expect the final release within the next weeks/months after that.
In reply to "When it's ready" is still by Marc Sabatella
:) Cool .. looking forward to it