Re: OOoLilyPond trouble 2
Hi David, David Bobroff wrote: New problem. I had saved the small test file in *.doc format as I'm doing some work for someone who is using Word on Windows (this may or may not be relevant). When I reopened the test file and tried to edit one of the little music snippets, or add a new one, I get an error box: A Scripting Framework error occured while running the Basic script vnd.sun.star.script:OOoLilypond.OOoLilyPondMusic.main?language=Basic&locaction=application. Message: BasicProviderlmpl::getScript: no script! What happened? I tried that too. I don't get the "BasicProviderlmpl::getScript: no script!" Error. And I can start LilyPond to creat new music snippets. But it is not possible to reopen the already existing music snippets which I expected. See below an explanation for this. May be your problem is that script cannot be called. Check the installation of the script. Open the Dialog "Tools --> Macros --> Organize Macros --> OpenOffice.org Basic" and check whether the macro is still there. You can also try to run the macro using this dialog. Now why OOoLilyPond cannot be used in .doc files: OOoLilyPond stores the LilyPond code as additional attribute in the odt file. When unziping and the odt file and opening content.xml you can see the code for the OOoLilyPond Image: OOoLilyPondArgs="default16§AsCharacter§NoWrap§c' d' e'" draw:stroke="none" svg:stroke-width="0in" svg:stroke-color="#00" draw:marker-start="" draw:marker-start-width="0.1181in" draw:marker-start-center="false" draw:marker-end="" draw:marker-end-width="0.1181in" draw:marker-end-center="false" draw:fill="none" draw:fill-color="#99ccff" draw:textarea-horizontal-align="center" draw:textarea-vertical-align="middle" fo:padding-top="0.0492in" fo:padding-bottom="0.0492in" fo:padding-left="0.0984in" fo:padding-right="0.0984in" draw:shadow="hidden" draw:shadow-offset-x="0.1181in" draw:shadow-offset-y="0.1181in" draw:shadow-color="#808080" draw:color-mode="standard" draw:luminance="0%" draw:contrast="0%" draw:gamma="100%" draw:red="0%" draw:green="0%" draw:blue="0%" fo:clip="rect(0in 0in 0in 0in)" draw:image-opacity="100%" style:mirror="none" fo:margin-top="0in" fo:margin-bottom="0in" style:run-through="foreground" style:wrap="none" style:vertical-pos="from-top" style:horizontal-pos="from-left" style:horizontal-rel="paragraph"/> The lilypond code ist stored in the additional graphic-property OOoLilyPondArgs="default16§AsCharacter§NoWrap§c' d' e'" I assume that this property is lost when converting to the .doc format and back again to .odt. I think it is not easy to find a clean way to store the lilypond code such that it remains correct when converting to .doc. I will one have a closer look at this issue, but this does not have priority for the development of OOoLilyPond. regards, Samuel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
tuplet bracket collides with beam and goes in wrong direction
I had been thinking that this bug was combined with another tuplet bug
but looking at the bug listings I see I was wrong.
This code produces a tuplet bracket that slopes the opposite way as it
should and collides with the beam.
\version "2.9.19"
\relative c' { ees16[ g \times 2/3 { r16 dis cis] } c4 d e f f e d }
I would consider sponsoring a fix if necessary as this bug keeps me from
delivering an arrangement unless I change the beaming.
Thanks,
Paul Scott
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
OOoLilyPond trouble 2
In the midst of having trouble with OOoLilypond I decided it was time to go ahead and update my Linux installation. I did a fresh install of Fedora Core 5 (was using FC3 before). I updated everything and then installed LilyPond 2.8.7 from the install.sh. Then I installed OOoLilyPond. Then I followed the instructions and perhaps got it right this time. I was able to make it work as advertised. Yay! It was pretty cool. New problem. I had saved the small test file in *.doc format as I'm doing some work for someone who is using Word on Windows (this may or may not be relevant). When I reopened the test file and tried to edit one of the little music snippets, or add a new one, I get an error box: A Scripting Framework error occured while running the Basic script vnd.sun.star.script:OOoLilypond.OOoLilyPondMusic.main?language=Basic&locaction=application. Message: BasicProviderlmpl::getScript: no script! What happened? -David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Documentation or programming error?
Here: http://www.lilypond.org/doc/v2.9/Documentation/user/lilypond/ Font-selection.html it says that make-pango-font-tree should be placed in \paper. At least on my system with LilyPond 2.9.21 it works only in \layout. Could someone test/correct this please? BTW: What does the / in (/ staffsize 20) mean? Greetlings from Lake Constance --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ http://www.cacert.org (I'm an assurer) smime.p7s Description: S/MIME cryptographic signature ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: highest possible pitch
Yes, if I r c you could find an example in Tips & Tricks. Generally you need to override the print function of the notehead. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re:warning: Ignoring grob for slur. avoid-slur not set?
>>> {c'( d'^\flageolet)}
>>>
>>> gives the warning:
>>>
>>> Ignoring grob for slur. avoid-slur not set?
>>
>> Michael: you can't get rid of this warning right now. Maybe in a
future
>> version.
>>
>>
>> Devel: could we set avoid-slur to something by default? If
there isn't
>> a specific value in scm/script.scm, use (avoid-slur . around) ?
> perhaps we should just remove the warning.
Please do. I get tons of them at the moment and it makes it really
difficult to see the important warnings.
/Henrik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: highest possible pitch
> I would like to notate an arbitrarily high pitch using an upward arrow as a > notehead, but note-head-style.ly does not contain such a symbol. As an alternative, you might try c''1 :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
highest possible pitch
Howdy. Sorry if this has been addressed before, but I couldn't find a simple solution on the archives (although perhaps I'm not searching for the correct terms). I would like to notate an arbitrarily high pitch using an upward arrow as a notehead, but note-head-style.ly does not contain such a symbol. Setting the notehead to "do" gives me a somewhat useful symbol, but I would prefer arrowheads.close.11 from the feta font for the notehead. Is there a simple method for using any arbitrary symbol as a notehead? Thanks for your help, Julian Peterson ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: OOoLilyPond problem
Hi Dave, Dave Phillips wrote: I'd love to get this working but I hit a problem when I get to the rendering. I've installed everything according to directions, I'm using LP 2.8.4 and OOo 2.0.3 on a Debian Etch system. The dialog panes appear, and I've configured everything properly (AFAICT) but when I click on the LilyPond button I receive this cryptic error: terminate called after throwing an instance of 'std::logic_error' what():basic_string::_S_construct NULL not valid The error appears to be related to C++. Any suggestions towards a solution ? I have no idea, what this error message means. I did not use any C code, only OOoBasic and Bash. I propose, you wait for the next version of OOoLilyPond. I changed most of the code. I will release the next version in one or two weeks. regards, Samuel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
OOoLilyPond problem
Hi Samuel: I'd love to get this working but I hit a problem when I get to the rendering. I've installed everything according to directions, I'm using LP 2.8.4 and OOo 2.0.3 on a Debian Etch system. The dialog panes appear, and I've configured everything properly (AFAICT) but when I click on the LilyPond button I receive this cryptic error: terminate called after throwing an instance of 'std::logic_error' what():basic_string::_S_construct NULL not valid The error appears to be related to C++. Any suggestions towards a solution ? Best, Dave Phillips ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Figured Bass question: Why is <5 4> upside down?
> "Trent" == Trent Johnston <[EMAIL PROTECTED]> writes: Trent> I don't think these are bugs as such. It's got to do Trent> aligning the extender line. If you place a spacer (s8 etc) Trent> between the figures the figures are printed the right way. Trent> is sent a reply to the Lilypond user list a while ago with Trent> a solution to this problem. Trent> http://lists.gnu.org/archive/html/lilypond-user/2006-07/msg00052.html This message says: Trent> The figured bass figures are aligned so if you have a 6 4 Trent> then a 4 3 the fours get aligned together so the 4 3 Trent> becomes 3 4. To get around this put a spacer between the Trent> figures. For example if they are <6 4>8 <4 3> to get rid of Trent> the alignment use instead <6 4>16 s <4 3>8. Trent> This is not a bug but a feature for extender lines. This seems like an undesirable feature to me. It puts a lot of burden on transcribers of figures to notice whether figures are repeated, when most figured bass that I know anything about doesn't use extender lines at all. And transcribing figures with no support for MIDI review is difficult enough without the figures being reordered on you. In any case, even if there were an extender line, you would still want the numbers to be in the correct order; you would just want the vertical spacing to be different. So you would still want <4 3> and not <3 4>. If there were an extender, you would want 6 4 3 But if you weren't trying to extend, you would rather have 6 4 4 3 So that the figures would be closer to the notes. So I still think it's a bug. The fact that it's a bug with a workaround makes it less critical, but it's still not what anyone would expect to see. Is there any way the behavior could be removed, at least for cases when useBassFigureExtenders is false? If the bug can't be fixed, I think the workaround should be better documented. Here's the current explanation; 2.20> When using continuation lines, common figures are always put 2.20> in the same vertical position. When this is unwanted, you 2.20> can insert a rest with r. The rest will clear any previous 2.20> alignment. For example, you can write 2.20> <4 6>8 r8 2.20> instead of 2.20> <4 6>4 I think this isn't quite correct, since the problem currently occurs whether you're using continuation lines or not. I propose that it be changed to: new> When two immediately adjacent columns of figures share a common new> number, Lily sometimes gets confused about what order to set new> the second column in. If this happens to you, you can remove the new> confusion by inserting a rest or spacer between the figures. new> For example, if you have new> <7 5>4 <5 4> new> and lily is putting the 4 above the 5 instead of below, you new> can work around this problem by instead writing: new><7 5>8 s8 <5 4>4 -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: collision between rest of one voice and the notes of the other voice
Hi, Mats: I would rather recommend to set the staff-position property: Perfect! I was looking (quickly, I must admit!) for such a property -- I tried #'position, and it didn't work, so I moved on. Thanks for providing the better solution. Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: warning: Ignoring grob for slur. avoid-slur not set?
Graham Percival schreef:
Michael Kiermaier wrote:
{c'( d'^\flageolet)}
gives the warning:
Ignoring grob for slur. avoid-slur not set?
Michael: you can't get rid of this warning right now. Maybe in a future
version.
Devel: could we set avoid-slur to something by default? If there isn't
a specific value in scm/script.scm, use (avoid-slur . around) ?
perhaps we should just remove the warning.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: collision between rest of one voice and the notes of the other voice
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
>
>
> Henrik Frisk wrote:
> >> \relative c' { << {c c c c} \\ {R1} >> }
> >>
> >> In the output there is a collision between the rest of the second
> >> voice and the notes of the first voice.
> >>
> >> The right solution would be to put the rest on a ledger line and to
> >> lower it until no collision occures.
> >>
> >> Is there a reason why lilypond doesn't to that?
> >> Is it possible to force lilypond to put the rest on a ledger line?
> >> Or at least to correct the output somehow manually?
> >>
> >
> > You can always put the rest at the position of a note e.g. d'1\rest
> >
> That's not a good idea, considering the difference between r1 and R1
> (the former
> should never be used in 4/4 music, according to typesetting practice).
>
Right... but it is an option
/Henrik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: collision between rest of one voice and the notes of the other voice
Henrik Frisk wrote:
\relative c' { << {c c c c} \\ {R1} >> }
In the output there is a collision between the rest of the second voice and
the notes of the first voice.
The right solution would be to put the rest on a ledger line and to lower it
until no collision occures.
Is there a reason why lilypond doesn't to that?
Is it possible to force lilypond to put the rest on a ledger line? Or at least
to correct the output somehow manually?
You can always put the rest at the position of a note e.g. d'1\rest
That's not a good idea, considering the difference between r1 and R1
(the former
should never be used in 4/4 music, according to typesetting practice).
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Instrument transposition and score transposition confusion
Hello OROD,
I do it like this:
fluteNotes = \relative c''' {
\transposition c % this indicates the correct pitch for cues and midi
\key c \major
... the music in c ...
}
clarinetNotes = \relative c'' {
\transposition bes % this indicates the correct pitch for cues and midi
\key d \major
... the music in bes ...
}
hornNotes = \relative c {
\transposition f % this indicates the correct pitch for cues and midi
\key g \major
... the music in f ...
}
For a score in C you do:
\score {
<<
\new Staff \fluteNotes
\new Staff \transpose c bes, \clarinetNotes % this transposes your
Bb-Voice into C
\new Staff \transpose c f, \hornNotes
>>
\layout {}
\midi {}
}
Cheers,
Markus
"OnionRingOfDoom" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
>
> I'm writing an orchestral score out, and I have a large piece.ly file in
> which all the individual instrument parts music is written out. Every
> instrument's part starts with something like varInstrumentNotes =
\relative
> c'' { . Every part is entered with \relative c, then there are template
> files for each part which are used to actually print the invidual parts.
The
> structure is as follows:
>
> \new Staff \with {
>
> } % end with
> {
> \clef "treble"
> \set Score.skipBars = ##t
> \override MultiMeasureRest #'expand-limit = 1
> \override Score.RehearsalMark #'Y-offset = #0.08
> \varKey
> \varTime
> \varInstrumentNotes
> }
>
> But now I have to write out the Bb Clarinet parts, and the Bb Clarinet is
> obviously in the key of Bb. Now, in the score, I want to write it out in
C,
> and then in the template file have it transpose to Bb. The key of the
entire
> piece is A Minor. How would I go about transposing the Bb Clarinet into
the
> propper key? I cannot seem to figure out if I use the \transpose command
or
> the \transposition command.
> --
> View this message in context:
http://www.nabble.com/Instrument-transposition-and-score-transposition-confusion-tf2386295.html#a6652042
> Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
