Over the past few weeks we’ve been exploring how forScore uses MIDI in all sorts of different ways. First, we detailed the process for setting up shortcuts so you can trigger any of forScore’s most popular functions from your MIDI device. Then, we discussed using an incoming message to open a particular score. Finally, we showed you how to set up MIDI messages to be sent automatically when you open a score. That last example is particularly powerful, but it has one drawback: as soon as you change songs your MIDI setup will change. That can be a problem if you’re using a setlist and you accidentally flip over to the next song, or if you’d just like to take a look at the next piece before the current one is finished.
That’s why we introduced Buttons in forScore 9. Buttons can do a lot (if you haven’t had a chance to use them yet be sure to check out the user guide for complete instructions), but today we’ll focus on their MIDI capabilities. Just like scores can send messages immediately when they’re opened, buttons can send messages when they’re tapped. They can be set up to send program change messages, song select messages, or raw hexadecimal codes, and they can even memorize incoming commands or add a delay between messages.
Since Buttons wait to send their messages until they’re tapped, you can even use them to change your settings partway through a piece. They’re incredibly flexible, and next week we’ll be discussing Presets which make sending common MIDI messages even easier, so be sure to check back next Friday for even more!