Han-Wen Nienhuys wrote:
>
> Try this patch (or try CVS)
This fixes the problem. Thanks for the fast response time!
Thomas
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
[EMAIL PROTECTED] writes:
> (gdb) backtrace
> #0 0x0805e96c in _ZNK14Music_iterator8self_scmEv (this=0x2) at
> include/music-iterator.hh:66
> #1 0x080c4285 in _ZNK28Lyric_combine_music_iterator12derived_markEv
> (this=0x83dc748) at lyric-combine-music-iterator.cc:81
> #2 0x080deadb in _ZN14M
Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
>> Hello,
>>
>> lilypond 2.0.0 (own compilation on SuSE Linux 8.2) kindly asks me to
>> send my file to this list, because it crashes with signal 11. The funny
>> thing about this problem is that it vanishes, if you change something
>> non-trivi
Hi,
Mats Bengtsson writes:
> The values are customizable, see the file scm/midi.scm for
> the default settings.
Thanks. I wonder why the default dynamic is "ff" (as
indicated by the lines below)? If I were playing some music
without any dynamics on it, I'd go for "mf" (or listen to
the other pl
Mats Bengtsson writes:
> Could we have an compressed_dynamics option (set true by default)?
The midi backend has not been guilified, lots of hardcoded stuff
there, otherwise it would be real simple to specify lower and upper
bounds for volume:
midi-item.cc:
static Real const full_scale = 127;
The values are customizable, see the file scm/midi.scm for the
default settings.
I can confirm the same problem on a Crystal Semiconductor
sound card. With the software sequencer timidity, the differences
are smaller, though. On the other hand, a good orchestra would
maybe make an even bigger diffe
[EMAIL PROTECTED] writes:
> Hello,
>
> lilypond 2.0.0 (own compilation on SuSE Linux 8.2) kindly asks me to
> send my file to this list, because it crashes with signal 11. The funny
> thing about this problem is that it vanishes, if you change something
> non-trivial like using "--verbose", remov
Hello,
lilypond 2.0.0 (own compilation on SuSE Linux 8.2) kindly asks me to
send my file to this list, because it crashes with signal 11. The funny
thing about this problem is that it vanishes, if you change something
non-trivial like using "--verbose", remove the midi part or delete
a lyrics ex
[EMAIL PROTECTED] writes:
> I got a SIGSEGV when trying Lily 2.1.0 on an old file.
> The following small example gives the same problem.
> Of course, I know that the property doesn't exist anymore
> but Lily shouldn't crash anyway.
Thanks, fixed.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] |
