Back to Silas S. Brown's home page
Manuscript Writer (1993-99)
Manuscript Writer was a C++ music notation program I made in the mid-1990s to help with school music work. Its input was based on SMX code (e.g. O2L4cdL8efL4g) with many additions.
Manuscript Writer is rarely needed nowadays, because:
Manuscript Writer also had support for Braille music, graphical Braille tutorials, and various old PC hardware and file formats, but I no longer distribute Manuscript Writer because:
If anyone is desperate then I could ship a version of Manuscript Writer with the dubious parts removed but it will have to be Unix. Meanwhile I highly recommend Lilypond, and I hope Lilypond's Braille support is coming soon.
- The text-to-phonemes table for its built-in speech synthesiser was derived from a commercial BBC Micro speech program (this was supposed to be temporary while I wrote my own table, but I forgot and left it in), plus its low-level driver for Creative Labs soundcards was based on code that wasn't mine and I've forgotten what the license was. I could remove those features, but I no longer have the compiler needed by the DOS version of Manuscript Writer, so at the very least I have to discontinue the DOS version.
- The Unix version lacks the support for various esoteric DOS devices and fancy user interfaces, and the only thing it does that's still special is Braille output, but:
- Manuscript Writer's Braille is now out of date: the various Braille authorities agreed on a new international standard just after the time I stopped working on Manuscript Writer, and the number of people wanting their Braille music to be done in the old style has now dwindled. Anyway, if Braille conversion is what you want then you are probably better off finding a program that reads a more standard input format. Manuscript Writer has its own language and can also import a bunch of other formats, but all of these are quite old and no longer widely used (except the ones it doesn't handle very accurately), and it might be quicker to write the Braille yourself unless you also want print at the same time.
AnecdotesYou might find these entertaining:
- One of the formats for outputting a score was in HP's plotter language. Until I figured out raster printing, that was the only way I knew of driving the school's laser printer. But I didn't know how to do filled solids, so I emulated them with thousands of lines, and at one point my scores were tying up the printer for 10+ minutes per page and I had to schedule them at intervals to allow others to print in between, which led to a lot of running around fetching and collating pages. In early versions it sometimes failed to tell the printer to actually finalise a page, with the result that my music was printed over the top of the work of whichever hapless student happened to be using the printer next.
- There was also a function to broadcast MIDI over the network using a protocol I made up. That's because only one of the PCs had a sound card, and that one was usually in use (but not for its sound), so I wrote a TSR program to sit in the background and receive MIDI from whichever other PC I was using. The person on the sound machine didn't usually mind as long as I remembered to ask! (I did of course try to co-ordinate a chorus of beeping PCs as well; it's the sort of thing you do at that age.)
- There was a feature called the Graphical Orchestral Positioning System (GOPS), which let you set the virtual location of each instrument by dragging coloured boxes around with the mouse (I was never any good at graphics but I wanted to use a fancy-sounding name for some reason).
- Early versions were so bad at drawing accidentals on my inkjet printer that I added an option to miss them out and leave space for them to be penned in by hand. It got better later, but I never did get rid of that option.
- My spelling wasn't always good, but when I discovered I had something wrong, I'd make a funny error message to pop up if I should make that particular mistake again.
- The "print preview" was rotated because I couldn't see the point of monitors being landscape while printouts are portrait. I'd lean my head over to check the layout, and my father once said I'll end up being locked in that position as an old man. (Just as well Lilypond and larger monitors came out.)
- One complication with the Braille code was that, despite being in a specialist blind college for the last two years of my schooling (1995-97), I couldn't locate a Braille ASCII table until after I had left. So while I was there I used the proprietary binary protocol of each of their Braille machines, which meant you had to match up the options to the machine you were using as well as setting the musician's preferred parameters, and there were some very strange failure modes. My "tutor" feature could put colour-coded dots on the screen with mouseover explanations (like Wenlin's "instant lookup" before its time---I got the idea from Skyglobe), or it could draw diagrams showing which keys to press on a manual Braille machine (handy if I couldn't get to use an automatic one, as for some unknown reason I never did get the hang of which key punched which dot, and could barely manage a tenth of the speed some students did). I did get some of my compositions played but I can't remember how many of my Braille parts were used without editing.
All material © Silas S. Brown unless otherwise stated.