> On Jan 17, 2022, at 5:04 PM, Adam M. Griggs wrote:
>
> I haven't tried building from development branch, but from experience, the
> stable branch only works with JRE 11, not "11 or greater."
Yes, I did use the default stable branch.
> I use MX Linux and JRE 11 is readily available. Not
> On Jan 15, 2022, at 4:56 AM, Adam M. Griggs wrote:
>
> Try Audiveris.
I downloaded the stuff from git but had failure at the build step. I looked for
a mail group like this one for Audiveris but didn't find anything. Can somebody
point me to a source of help building Audiveris?
thanks
I'm looking at getting an OCR program to recognize scans in pdf files and
create MusicXML files representing the contents. I would then use the
musicxml2ly or perhaps some other script to translate the MusicXML to Lilypond
files, I imagine that some of you are already doing this, and I wonder
> On Jan 14, 2022, at 6:37 PM, Valentin Petzel wrote:
>
> ...
> Lilypond uses these GM names, which makes Lilypond a somewhat GM compatible
> source. This means that as long as we use a GM compatible synth everything
> should have the right sound.
I was using VLC to play it. Does this mean
I'm working on an arrangement fordable-reed quartet. Here's the score block:
\score
{
\new StaffGroup
<<
\new Staff = "oboe1" \with { instrumentName = "oboe1" midiInstrument =
"oboe" }
{ \clef "treble" \soprano }
\new Staff = "oboe2" \with { instrumentName = "oboe2"
I fat-fingered the keyboard on my laptop and got this:
flute-notes = {
\override BreathingSigh.Y-offset = #2.6 %% also tried
#5.0 and some really big numbers; no effect
7 bars of music in 4/4
}
AND I never got an error message. This seems to mean that Scheme has no
lily
> On Jan 29, 2021, at 12:37 PM, Jean Abou Samra wrote:
>
>> I got a .ly file claiming to be version 2.18.0 and opened it in LP version
>> 2.22.0-1. When I did “Update syntax” I got these errors, and the version in
>> the file did not change.
>>
>>
>> [Image showing AttributeError:
I got a .ly file claiming to be version 2.18.0 and opened it in LP version
2.22.0-1. When I did “Update syntax” I got these errors, and the version in the
file did not change.
I can typeset the file with no problems.
I thought you should know.
