From: Bob D. <rl...@ya...> - 2010-04-28 16:45:18
|
I'm writing out a lead sheet, and am breaking it into segments to facilitate repeats and such. However, the chord symbols for my second and subsequent segments are printed BELOW the staff. The first segment has the chord symbols above the staff, as expected. Help! How can I get the chords to always be above the staff? |
From: Bob D. <rl...@ya...> - 2010-05-03 13:19:45
|
Bob Diss <rldiss@...> writes: > > I'm writing out a lead sheet, and am breaking it into segments > to facilitate repeats and such. However, the chord symbols for > my second and subsequent segments are printed BELOW the > staff. The first segment has the chord symbols above the staff, > as expected. > > Help! How can I get the chords to always be above the staff? > > ------------------------------------------------------------------------------ > Is anyone else having this problem, where the chord symbols areprinted below the staff for segments after the first? Is this something that you correct in the exported lilypond file? How? |
From: Julie S <msj...@ya...> - 2010-05-03 15:07:25
|
Hello Bob, Concerning: > > Help! How can I get the chords to always be > above the staff? I just tried a simple example. * Created a two measure segment * Filled it with half notes (C F G C) * Used The Text Tool to add Chords to each note * Copied and pasted the segment to measures 3 and 4 * Viewed a Lilypond preview This worked fine. Chords for both segments where printed above the chord. Next I overlapped the segments and tried the preview again. Both sets of chords were on top of the staff. I can't seem to duplicate the issue with what I know so far about the issue. Can you give a simple example that illustratates the issue you are having? Sincerely, Julie S. |
From: Bob D. <rl...@ya...> - 2010-05-03 16:27:57
|
Julie S <msjulie_s@...> writes: > > Hello Bob, > > Concerning: > > > Help! How can I get the chords to always be > > above the staff? > > Can you give a simple example that illustratates the issue you are having? > > Sincerely, > Julie S. > Sample at http://www.sendspace.com/file/kcv5o0 I created a segment of 4 measures and used the notation editor to add the notes and chords. Then I went back to the main display and split the segment. The end result is that the first two measures have chords above, and the last two have chords below. |
From: Julie S <msj...@ya...> - 2010-05-03 18:04:13
|
Hello Bob, Concerning: > Sample at http://www.sendspace.com/file/kcv5o0 I just tried this on the development snapshot and I did not get the result you reported. Everything is fine here. I've attached a .png -- I hope it make it through the list. I'm using Ubuntu Karmic RG dev. snapshot revision 11894 with lilypond 2.12.2 What are your specs? Maybe there is a lilypond versioning issue to deal with...but we are quickly moving out of my area of expertise. Sincerely, Julie S. |
From: Bob D. <rl...@ya...> - 2010-05-03 18:17:35
|
Julie S <msjulie_s@...> writes: > > Hello Bob, > > Concerning: > > Sample at http://www.sendspace.com/file/kcv5o0 > > I just tried this on the development snapshot and I did not get > the result you reported. Everything is fine here. Sample PDF: http://www.sendspace.com/file/huvi7g Sample Lilypond Export: http://www.sendspace.com/file/f4k3h4 Here's the results I get when doing a Print Preview (saved), and an Export to Lilypond. Versions: rg 10.04.1 lilypond 2.12.2 Print/Export set to use Lilypond 2.12 compatibility Why are your chords lowercase, and mine uppercase? Is that perhaps a clue? |
From: Clem, B. T. <bri...@oc...> - 2010-05-03 18:49:59
|
I could not get the chords to appear on top and bottom. Mine were all lower-case and on top. My RG is 10.06. I will have to re-read the instructions as to how to make this chord flop. Could it have been fixed with 10.06? ♫♫♫♫ Brian Clem ♫♫♫♫ Music Teacher Durrance Elementary School ________________________________________ From: Bob Diss [rl...@ya...] Sent: Monday, May 03, 2010 2:17 PM To: ros...@li... Subject: Re: [Rosegarden-user] chord symbols below staff? Julie S <msjulie_s@...> writes: > > Hello Bob, > > Concerning: > > Sample at http://www.sendspace.com/file/kcv5o0 > > I just tried this on the development snapshot and I did not get > the result you reported. Everything is fine here. Sample PDF: http://www.sendspace.com/file/huvi7g Sample Lilypond Export: http://www.sendspace.com/file/f4k3h4 Here's the results I get when doing a Print Preview (saved), and an Export to Lilypond. Versions: rg 10.04.1 lilypond 2.12.2 Print/Export set to use Lilypond 2.12 compatibility Why are your chords lowercase, and mine uppercase? Is that perhaps a clue? ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-user mailing list Ros...@li... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user ---------------------------------------------------------------------- The information contained in this e-mail message is intended solely for the recipient(s) and may contain privileged information. Tampering with or altering the contents of this message is prohibited. This information is the same as any written document and may be subject to all rules governing public information according to Florida Statutes. Any message that falls under Chapter 119 shall not be altered in a manner that misrepresents the activities of Orange County Public Schools. [References: Florida State Constitution I.24, Florida State Statutes Chapter 119, and OCPS Management Directive A-9.] If you have received this message in error, or are not the named recipient notify the sender and delete this message from your computer. |
From: D. M. M. <mic...@ro...> - 2010-05-03 20:08:17
|
On Monday 03 May 2010, Bob Diss wrote: > Why are your chords lowercase, and mine uppercase? Is that > perhaps a clue? Yes, that is a clue. You have "[x] Interpret chord texts as lead sheet chord names" turned on. This feature takes LilyPond syntax chord names and exports them in such a way that they look pretty as lead sheets. I have no idea why--when this feature is turned on--it's printing the chords in the second segment below the staff. I looked at the LilyPond code, and it was not enlightening at all. Anyway, the immediate solution to your problem is to turn that option off if you're trying to print chords in lowercase. Otherwise, who knows. I tried to hack the LilyPond manually to fix this, and I can't do it. You'll have to consult a LilyPond expert, and a LilyPond expert might need to tweak this export feature. Nobody around here these days is much able to be of help in this matter I'm afraid. -- D. Michael McIntyre |
From: Julie S <msj...@ya...> - 2010-05-04 01:45:21
|
Hello Bob, I just submitted a fix for your issue. Again I did not thoroughly test the fix. Committed revision 11895. Please give it a try. Sincerely, Julie S. |
From: Bob D. <rl...@ya...> - 2010-05-04 13:25:01
|
Julie S <msjulie_s@...> writes: > > Hello Bob, > > I just submitted a fix for your issue. > > Again I did not thoroughly test the fix. > > Committed revision 11895. > > Please give it a try. > > Sincerely, > Julie S. > That does indeed correct the issue for me -- thanks! fwiw: I determined that another way to fix this problem was to move all of the chord blocks to the outer Lilypond context, rather than having only the first segment's chords at the outer context and the later segments inside the "Staff" context. This results in not having to force the positioning on the chords. Dunno if that's more "correct" or not -- I'm just satisfied with being able to print my lead sheet properly! |
From: Julie S <msj...@ya...> - 2010-05-04 14:58:24
|
Hello Bob, Concerning: > That does indeed correct the issue for me -- thanks! Great to hear. Enjoy the feature. > fwiw: I determined that another way to fix this problem was > to > move all of the chord blocks to the outer Lilypond context, > rather > than having only the first segment's chords at the outer > context > and the later segments inside the "Staff" context. > This results in > not having to force the positioning on the chords. > Dunno if that's > more "correct" or not -- I'm just satisfied with being able > to print > my lead sheet properly! Yes, I ran across that as well. I'm certain output wise, it would be more elegant to have them all in one place and not have the context directive. If the current fix doesn't hold, we'll have to consider this option. I went, for the quick fix. I certainly did not want to add another round of iterations to pull out the chord names ahead of the track information. I like lilypond, but only use it for simple stuff. So every time I have to do anything out of the ordinary with it, I have to read the user documentation or look at other code snippets for help. As Michael mentioned eariler, the people who worked on the lilypond code have not been active lately so the work is left to less knowledgeable folks. Sincerely, Julie S. |