Re: [192]ERROR: In procedure ly:trampoline: | Adding any more code throws error!

[Samuel Burt]

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 problems.

Sam

On Fri, Jun 21, 2019 at 9:16 AM Samuel Burt <address@hidden> wrote:

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 the cello part. This seems to have done fixed it. I was using #'written and #'formidi so I could notate <a d\harmonic> artificial harmonics and have correct a'' playback. I'll have to spend a little more time with the #'formidi code to see if something I did broke it in a way it couldn't report a human readable error.

Sam

On Fri, Jun 21, 2019 at 4:58 AM David Kastrup <address@hidden> wrote:

Samuel Burt <address@hidden> 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 collection errors can appear or disappear with random additions
or deletions.  The last report was connected with the use of
Melody_engraver but you don't use it here and it is not related to Midi
anyway.  Is this possibly related to using _any_ custom engraver?  This
error has been reported only fairly recently, and we had some
restructures in the corresponding code.

If you remove all \consists declarations (unfortunately also likely
changing the output significantly), does this help?

--
David Kastrup