Silvan wrote: > My experience has been that it's rather difficult to figure out just what's > wrong on the Rosegarden side. Looks good here, looks terrible there. Now, > sometimes it's obviously wrong in RG, but that's another matter.
Well... yes. The notation editor has it's moods. However... In my experience the main problem is not that I have to spend time in the notation editor before I get it right, but that I have to spend (too much) time tweaking the Lilypond file. Because... changes I make to the Lilypond file has to be redone if I later change something in RG and re-export. There's two kind of changes I make to the Lilypond file: 1) because of missing RG features. Most of these could be avoided or at least made easier. 2) because I just want it to "look better" and I know Lilypond can do it. These are hard to avoid unless RG does all printing it self. But it would make RG at lot more useful for arranging orchestra scores for daily use if type 1 are minimized. Some features need to be added to RG (like repeats). Others (like cue notes) would probably have to be done in Lilypond, but I hope the new export will make it a lot easier to do this kind of changes to the exported file. Type 2 changes (making it pretty) will have to be made when you no longer expect to change the RG file. Peter ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
