I just spent over an hour researching and commenting on a bug report, and when I went to file the results, the browser took a crap, and then I got "Logging in to SourceForge.net is currently disabled" displayed in the top right corner.
Fortunately I managed to rescue this rather lengthy text from the browser page, so I might eventually be able to post this comment, but this whole thing is completely ridiculous! I didn't get a service outage notification. I didn't hear a damn thing about any of this until SourceForge just decided to take a shit in its own pants right in the middle of my trying to get some work done. That and the long-running lack of "remember me" is driving me to the point of wanting to abandon this ship and say to hell with everything. Working for free is tedious enough without having to deal with broken tools along the way, dammit! Paste: OK, I see three obvious problems with this. 1) The segments are different lengths. You can't export less than an entire segment, and if the segments don't have the same length, the LilyPond exporter pads out the short segments. (There is also a bug in this logic, but it isn't relevant here, so I won't discuss that aspect of things.) The solution to this should be to make all the segments the same length before you start, so you can control the padding yourself. 2) You have a lot of overlapping voices in the top part. I wouldn't have thought this was the case myself until I experimented, but apparently chords of mixed durations count as separate voices too. The way to fix this problem everywhere that it occurs (and fixing the first one just moves the problem until the next time the same figure appears) is to draw some new overlapping segments (easy to do with 1.7.0) and shuffle notes around so that the two voices are separated from each other cleanly. See http://rosegarden.sourceforge.net/tutorial/supplemental/piano/index.html for a walkthrough of the concepts. In this situation, you want to have one segment with all the bottom 4. notes, and one segment with all the top 4 8 notes, with the holes in each mating segment patched by hidden/invisible rests so that everything comes out at the correct time. You won't be able to make proper chords out of a 4. on the bottom and a 4 on top, due either to limitations in Rosegarden, LilyPond, or the vagaries of our export mechanism. I don't see any way to resolve that particular issue, and the best I can suggest is that you play with stem directions. If you fake out the stems, you might get results that look like proper chords, even though they aren't, and if the results don't look like this, then there isn't much you can do except flip the stems away from each other intentionally, in order to avoid conflicts. 1.7.0 is highly recommended for working out this particular puzzle, because we've made dealing with this sort of thing much easier than it used to be. That should be explained in the tutorial I referenced, which used the new features as they were emerging during development. 3. When you export Rosegarden's beaming, you get a lot of ugly problems. This is because Rosegarden can't actually display all the beaming you have applied, but the properties are still there. There are many situations with an 8th rest beamed to an 8th note, or a quarter note beamed to an 8th note. Rosegarden will let you apply these properties, even though it doesn't display any result (except in the advanced event editor, where the non-displayable properties are visible,) and LilyPond tries to take all of this too literally, resulting in complete chaos. Probably the easiest solution is to un-beam everything, and then carefully re-beam only the notes that should be beamed. Don't beam flagged notes to non-flagged notes, and don't beam anything to rests. (I understand that notes can be beamed to rests in real music notation, but the Rosegarden/LilyPond export combination cannot handle this situation at all, and you must avoid creating that scenario.) Alternatively, you could try un-beaming everything, and then just let LilyPond do its own automatic beaming. LilyPond is much more intelligent about automatic beaming than Rosegarden. Our automatic beaming has been horribly broken and on our "must fix" list for years, but we have never quite found the time to gut this code and redo it with code that actually works in more cases. That's all I see wrong off the top of my head. I hope you can make do with my explanations here, in conjunction with the tutorial I referenced. I'm afraid I don't have time to clean the file up and mail it back to you at the moment. It does look like everything can be corrected, and I don't see anything here that constitutes a bug in Rosegarden per se. It's more a matter of needing to learn how Rosegarden works. We'd agree that several aspects of this whole scenario place a burden on the user in terms of dealing with a complicated pain in the ass instead of just drawing out the damn music, but I'm afraid this is the best we've managed to do in years and many hundreds of hours of development, and this is what we have, and what we will continue to have for the foreseeable future, stretching out to years, decades, or even centuries. We've had many discussions about brilliant theoretical ways to make all of this less complicated, but we don't have the manpower or brainpower to actually implement any of it, and we have to settle for making things possible, no matter how complicated it can be to achieve the end result in confusing situations like this one. -- D. Michael McIntyre ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
