Tuesday, 19 June 2018

Drum Score Editor Release Notes 2.6.5

New Features

Floaty Swiss Ghost Notes

Added at the last minute, the capability appeared from nowhere, very spooky. So currently all grace notes are attached to the note that they are gracing. I.E. the little note in a flam is attached to it’s main note, the 3 little notes of a swiss rough are attached to their main note. What this means is if the first note in a bar has grace notes they must be on the right hand side of the bar line. There is no way to move the grace notes before the bar. Some people specifically have a written style where the 3 grace notes of the swiss rough are written before the bar. So we still can’t do that. Well we can, but not in any way other than the sucky hack that this apparition of a feature is. What we’ve done is introduce a ghost note, ie it’s a note you can enter like any other, using i and shift-i for left and right hands, and the ghost note always has a swiss rough attached to it’s invisible main note. It’s main note has no value, so doesn’t upset bar warnings, and beautify doesn’t get a fright either.

So how do you use it? If you want the first note in a bar to be a swiss rough where the grace notes are to go in the bar before, enter the note without a swiss rough in that bar, then go to the previous bar and enter the floaty swiss ghost note. Go try it, spookily it’s easier than it sounds!

Linked Variables in Text Areas

Previously in Drum Score Editor you could always use a % substitution in a text area and it would perform a one time load of the value of the property into the text area. After that if you edited the text area, any changes did not reflect back in the property for example. Similarly changing a property wouldn’t result in the info in the text area changing. Consider the title for example, when you used the New Score Wizard it would ask for the title, it would put it in the properties and in the text area as %title which would result in a one time load of the title and nothing else. Now if a text area is set to a % variable, then it’s linked to the score property it represents, e.g. %title, %author ….

Link Tune Type in New Scores

When a new score is generated the chosen tune type is just text that’s added. There was no connection between the tune type property and the generated text area - now there is, edit the property and the text area on the screen updates, and vice versa.

Auto Increment the Version Number

There’s always been a version number as a property of each score. Nothing happened with it, it was a manual, documentary thing that was just for book keeping purposes. Now we increment the version number (if it’s a number, you can put anything you like in it), on first edit after a score is opened. And if you undo that edit then yep, it tracks all your edits and resets it back. There’s also a variable name you can use in a text area called %version.

Read Only Text Areas

Wanted a read only text area, for data such as the date last updated. What’s this about a date last updated I hear you say? See below, it’s another new thing.

Date Last Updated

Thought it might be useful. Tracks the date the last update to the score was made. You can use it in a read only text area.

External Mono Microphone

Added support for external mono microphones plugged into any orifice your compute permits.

macOS Full Screen Mode

When pressing the maximise button on the main window frame, on macOS the usual behaviour is to use the native full screen mode. We now obey our Apple masters and do as expected.

Sextuplets, Septuplets

Nothing to do with lots of babies. Sometimes some people write two triplets as a sextuplet, well they wanted to but we interpreted wrongly. It now beautifies and warns for bar content properly. Same for septuplets.

Fixes

  • Made it less error prone when manually pasting a license key in, strips white space from start and end
  • Some tweaks to try and make it a bit prettier. There’s an icon in your face in the middle of the workspace when empty. It scales to fit up to a certain size and the Windows libraries seem to be a bit jaggedy (technical term) but rather than delay more I’ll work on that in the background. Talking of backgrounds on macOS the background is a cool day grey colour but Windows makes it white on my test machine. Not sure why on that but again, more background background work
  • Other updates in this area include making sure the screen location and windows is preserved properly between sessions in the software. It seemed to creep up the screen if not using full screen, and sometimes start in the bottom corner of the screen at some bizarrely minimum size.
  • Should remember if you’ve maximised your window too now