![]() Maybe next month.) to see just how it works as a composition tool. finally got to the point that I could start using it to write music (not to complete a piece. without any reasonable documentation (most of us got through the documentation before lunch) the first few days were spent on the forum and bothering support. It’s not all one-way traffic - the next version of Lilypond should have a pretty good interface to Smufl-compatible fonts, and the public domain version of Bravura… Looking forward a few years from now, the most “interesting” competitors to Dorico might be MuseScore and Lilypond - companies can legally protect their actual code, but you can’t patent ideas!Īctually, some of the “not in any other commercial notation software” features in Dorico have been in Lilypond, in embryonic form, for a long time already - for example a basic structure similar to “players,” “flows,” and “frame-based layouts”, automatically merging two parts onto one staff in a score, etc. On the other hand, there are some developers out there who have plenty of enthusiasm and knowledge, and don’t do what they do for the money. I think it’s a fairly safe bet it will overtake the “dinosaurs” pretty soon - it’s already done so in some areas. However, my instinct tells me Dorico will have overtaken the competition fairly soon So, if you’re a composer my advice is get stuck in - you’d be mad not to since, in my opion and for my uses, Finale and Sibelius are going absolutely nowhere. ![]() Equally, I think you’re losing out if you don’t buy into it now and also try to influence its future path. If you’re a composer it’s my opinion you should be migrating to the new software, as of now, but sensibly you simply cannot expect to commit your precious work totally to this software yet. So, for me, Dorico is the only way forward. The future: at least Dorico has one! - and we’re told the design under the hood is ready wired for many fascinating new innovations.Functionality: I can already do things using Dorico I couldn’t dream of in either Sibelius or Finale. ![]() I couldn’t do anything in Finale better than I could in Sibelius, and, for the most part, a lot more easily in the latter. Some people will tell you it’s all singing, all dancing. In my Finale days I spent far too much time setting things up and looking for the right tool to use just to edit things. It was never really a composer’s tool anyway (I know composers use it, goodness knows how). Economically and artistically Sibelius does not make sense to me anymore, neither does it hold any promise for the future and the future of my software is important to me Sibelius: there was so much more I needed from that software but now it’s dead in the water and any meaningful development has ceased.My reasons, as a composer, for going Dorico are simple: We didn’t have to go ahead but many of us did and we went in with eyes wide open. Effectively we were being asked to buy into Dorico on a promise. We were warned Dorico was work in progress from the onset and, as I understand it, this first version was released with the caveat that it would not be fully featured yet but there would be a series of free point releases and enhancements during the life of version 1. So wherever the command to update the preview pane is issued, that needs to be adjusted to use this synatx.I struggle to see where the problem is. Zooming would be nice to implement here, but I suppose it's not crucial.) It is crucial that there not be spaces between the two sides of each equality. (The image size is way too big at the moment, with lilypond in 20 point-this can be fixed by changing to -dresolution=90 or so, but that might affect drag-to-offset. Lilypond-windows.exe -dgui %1 %2=%3 %4=%5 %6 %7 %8 %9Īnd now the print view pane works. As a hack fix, I changed denemo-lilypond.bat to read Indeed, I have confirmed that fixing this fixes the problem. The command issued by denemo lacks the = signs. The crucial difference being in: -dbackend=eps -dresolution=180. However, this works executed from the command line, producing the png:Ĭ:\"Program Files"\Denemo\usr\bin\lilypond-windows.exe -dgui -png -dbackend=eps -dresolution=180 -o ".\.denemo\denemoprint_" ".\.denemo\denemoprint_.ly" Running this command from the commandline (after explicitly specifying the path for lilypond-windows as needed) does not work, and produces some kind of error about ps-to-png.ly not being there. Lilypond-windows.exe -dgui -png -dbackend eps -dresolution 180 -o ".\.denemo\denemoprint_" ".\.denemo\denemoprint_.ly" ![]() Specifically, here's what denemo currently does when you try to update the print view in the windows dos box: I've tried to track this down a bit, and apparently the problem is that when denemo issues the lilypond command, it doesn't use the right syntax for the commandline options, and consequently no.
0 Comments
Leave a Reply. |