MING TSANG writes:
> Anders: Thank you for the info about convert-ly in frecobaldi. I
> will wait for the new version.David: The LSR 619 do not contain
> \version statement. So I added to it and run and it's OK.. Then I
> change the \version to "2.19.83"
Do not change the \version to
On 21.06.19 17:01, MING TSANG wrote:
David: The LSR 619 do not contain \version statement. So I added to it
and run and it's OK.. Then I change the \version to "2.19.83" and
compile - error occurs. Then I try to use frecobaldi to do the
convert-ly and it fails.
If you want to update an LSR
On 2019-06-21 17:01, MING TSANG wrote:
Anders: Thank you for the info about convert-ly in frecobaldi. I will
wait for the new version.
David: The LSR 619 do not contain \version statement. So I added to it
and run and it's OK.. Then I change the \version to "2.19.83" and
compile - error
Anders: Thank you for the info about convert-ly in frecobaldi. I will wait
for the new version.David: The LSR 619 do not contain \version statement. So I
added to it and run and it's OK.. Then I change the \version to "2.19.83" and
compile - error occurs. Then I try to use frecobaldi to do
For my particular situation, I think maybe I had created some kind of
render problem with the #'formidi block.
I've observed that lilypond doesn't throw warnings about bars without
enough beats or other notation problems in #'formidi blocks. A feature like
this might help to catch some bad
Samuel Burt writes:
> Hi David. For the group record, I accidentally replied only to David.
>
> All the \consists in this project were already commented out.
Oh.
> I can remove them completely. Being new to Lilypond, would that have
> any effect?
Quite unlikely. This is not likely to have a
Hi David. For the group record, I accidentally replied only to David.
All the \consists in this project were already commented out. I can remove
them completely. Being new to Lilypond, would that have any effect?
Here's how I've got things working temporarily. I removed a "\tag
#'formidi" from
Hello,
There is a bug in Frescobaldi 3.0.1 on Windows that makes running the
convert.ly not work!
See this thread at Frescobaldi's support site
https://groups.google.com/forum/#!msg/frescobaldi/9BN23eKkxws/ZgnUKBzBBgAJ
Running convert.ly from the command line works of cause!
// Anders
On
MING TSANG writes:
> Hi, all
> At frecobaldi I try to do convert-ly and it seems not working
> Three steps taken:1. I run the LSR=619 with lily v2.18 -- it
> works 2. I change version to 2.19.83
What do you mean? You change the \version header?
> and run and I gor the following error
Samuel Burt writes:
> Here's an update. When using Frescobaldi, I can check a box for "Display
> Control Points". I'm guessing this is a Lilypond command line flag. When I
> turn it on, it compiles my music with no error. Does that help anyone in
> figuring out what my problem is?
Garbage
10 matches
Mail list logo