Regarding icons, this is how I did it for anyone interested:
- create an illustrator template with lots of artboards in the correct size (I think I created one using one of the supplied graphics, then duplicated it).
- in Dorico, find the element that I want to turn into an icon
- print screen
- in IrfanView (quick and dirty photo editor) quickly crop the element to size
- paste into illustrator, then size and align onto a blank artboard
- export all the buttons from illustrator in one hit
It’s tempting to create nice vector graphics, but the LCDs behind the buttons are pretty low DPI anyway, so a screen resolution is actually totally fine.
I’ve attached my illustrator file in case anyone’s interested.
I still haven’t had time to think through a comprehensive implementation of StreamDeck, but I did put it to pretty solid use while I transcribed a book of 50 or so leadsheet charts, and my general thoughts were:
-
create button sets which are context dependent, not necessarily category dependent. It might be nice to have all your articulations in one place, but perhaps for most note input tasks you overwhelmingly only use three or four. So a ‘note input’ set might include those three or four and leave plenty of room for other note inputty things like changing the grid resolution and switching triplets on and off. It might make total sense for the same button to appear in lots of different folders, if it gets used in lots of different contexts. It’s much much quicker than navigating through folders to find the button that you created in some other category. I have a “Score setup” folder which includes my most common time signatures and key signatures, and lets me add multiples of 8, 16, 32, 64 and -100 bars (the last one for deleting remaining, usually empty, bars at the end of a flow). But a couple of those I also have in my “Note input” folder, for when I find I’ve suddenly run out of bars at the end of a score, so I don’t have to change folders.
-
almost all my buttons are substitutes for popovers. If something can be accomplished using a one- or two-stroke key sequence, I’d rather learn the key sequence, not least because I work across two computers and the SD is only there for one of them. Popovers are great for accessing features which I seldom use, because they save me having to either remember a key sequence or dig through a menu, but for things I do repetitively, like add a repeat bar, there are just too many keystrokes. I think some popovers can be bypassed by programming a direct key sequence, but others can’t. SD words well for turning 10 keystrokes into 1.
-
It seems like it should be possible to get toggles working for things like rest input and tuplet input, but of course the SD can’t interrogate Dorico to find out the current state of that button, so if it gets out of sync for some reason, it will stay out of sync.
-
I’ve so far avoided using AHK, even though I’m pretty familiar with it and I could see how it could be tempting. As I get older, I’m finding that it’s best if my workflow relies on a minimum of awkwardly bodged-on software of my own creation.
-
I think perhaps with some head scratching, it might be possible to come up with a pretty fast and efficient means of note input using nothing but the Stream Deck (i.e. not even the computer keyboard). I could imagine it might be fun notating out in the park with a Surface Tablet and a StreamDeck and nothing else. Clearly, I haven’t thought this through.
Dan’s Icons.zip (88.1 KB)