On Mon, 25 May 2020, Valentin Villenave wrote:
Thanks Martin; I’ve opened this tracker page:
https://gitlab.com/lilypond/lilypond/-/issues/5994
It seems weird that such a problem wasn’t caught by our
pretty-extensive test suite, so I’m wondering what might be particular
to your test file.
M
(My comments are below the quoted message)
On Fri, 6 Mar 2020, alex wrote:
I am using `abc2ly`, provided in the lilypond packaging, to convert the
following ABC to Lilypond:
C: Alex Hansen
L: 1/128
V:TI clef=treble name="Voice 1" snm="V.1"
V:TII clef=bass name="Voice 2" snm="V.2"
[V:T
On Fri, 6 Mar 2020, alex wrote:
Are there plans to implement dynamics? In the ABC standard, it is noted
that while not all attributes are considered required when parsing ABC,
dynamics are part of the core set.
I don't think abc2ly is very actively supported and developed currently.
The fu
On Wed, 27 Nov 2019, Peter Toye wrote:
I'm not sure how many LP user use the MIDI output anyway, given its
restrictions. Personally, I use it for proof-reading only, so lack of repeats
isn't an issue.
I use MIDI output mainly for proofreading, but at occasions where I need
better MIDI out
On Sun, 14 Apr 2019, Malte Meyn wrote:
r1\fermata works fine, R1\fermata doesn't. No fermata sign is printed.
Is this a bug?
That’s the third time in a few weeks that someone asks why that doesn’t work
at a list/forum/… that I read.
Looks like I should continue my work on issue 5486
(ht
Hi,
This is strange:
%%% start of tiny example
\version "2.19.83"
{
r1\fermata
R1\fermata
}
%%% end of tiny example
r1\fermata works fine, R1\fermata doesn't. No fermata sign is printed.
Is this a bug?
--
MT
___
bug-lilypond mailing list
bu
On Sun, 24 Mar 2019, Martin Tarenskeen wrote:
See attached example "staffsize14.ly" and "staffsize14.pdf" output.
Using lilypond 2.19.82 on Linux Fedora.
What's happening here?
I tried some more staffsizes. I'm seeing dispositioned noteheads when
staffsize
Hi,
A bumped into a strange bug with a dispositioned notehead.
See attached example "staffsize14.ly" and "staffsize14.pdf" output.
Using lilypond 2.19.82 on Linux Fedora.
What's happening here?
--
MT\version "2.19.82"
\pointAndClickOff
mymusic = \relative c{
\clef bass
4| |
}
\
BTW, if you google "lilypond install", that is the second page listed after
downloads page.
Let me remind you that Google might not give identical search results to
different persons/computers even when they type the exacts same search
string. If I type "Lilypond" I get stuff related to ou
On Sun, 16 Apr 2017, Christopher Heckman wrote:
I like the idea and really appreciate your efforts, but I tried your patch
and it doesn't seem to work (yet), at least not on my system. I can't
Hm. My Python might be a bit rusty, but the syntax doesn't differ from
the original code. However,
On Thu, 13 Apr 2017, Christopher Heckman wrote:
I have written a patch to fix this. Inside of the class Duration (line
129), replace the dump function with:
Hi Chris, thanks for trying to improve the midi2ly tool.
I like the idea and really appreciate your efforts, but I tried your patch
a
On Mon, 4 Apr 2016, Maria Jesus Marin wrote:
Good afternoon,
I have one problem with one composition. My problem is that I have writted
the composition in Musescore, but when I export to xml and I import the xml
file in to Frescobaldi the staff duplicate lines.
I attach the musescore file, xm
Where do I report translation errors?
Please in nl.po:3700 replace "verkeert" by "verkeerd"
verkeert is wrong.
wrong is verkeerd
:-)
--
MT
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi,
Try to compile the following example:
\version "2.19.25"
\relative {
d''-.( d-. d-. d-.)
d-_( d-_ d-_ d-_)
d--( d-- d-- d--)
d-^( d-^ d-^ d-^)
d-+( d-+ d-+ d-+)
d-!( d-! d-! d-!)
d->( d-> d-> d->)
\break
\override Slur.outside-staff-priority = #500
d-.( d-. d-. d
Hi,
I just updated fontconfig from 2.11.93 to version-2.11.94 (now in
updates-testing) on Fedora 22
$ sudo dnf update --enablerepo=*testing update fontconfig*
And a quick test shows Lilypond started working again :-)
--
MT
___
bug-lilypond maili
Hi,
I just updated fontconfig from 2.11.93 to version-2.11.94 (now in
updates-testing) on Fedora 22
$ sudo dnf update --enablerepo=*testing update fontconfig*
And a quick test shows Lilypond started working again :-)
--
MT
___
bug-lilypond mail
so why is it not failing with Fedora 21? Fedora 21 and 22 use the same
Pango version?
MT
On 29 mei 2015 2:05:16 PM Jon Ciesla wrote:
On Thu, May 28, 2015 at 9:04 PM, Masamichi HOSODA
wrote:
> > The Fedora 22 package fails for everyone, the www.lilypond.org version
> > works.
> >
> > I tri
On Tue, 12 May 2015, pls wrote:
For example what happened with the Philomenos musixcml2ly-dev fork?
Yes, Philomelos is still alive and I’m about to update the musicxml2ly-dev
Github repo. Over at least three years I have written almost 100 bug
reports and many test cases for
On Mon, 11 May 2015, James Lowe wrote:
https://code.google.com/p/lilypond/issues/detail?id=4390
Bug reports are a good thing, but is anyone actually working on
musicxml2ly?
For example what happened with the Philomenos musixcml2ly-dev fork?
--
MT
__
bugreport / change request
%%% tiny example "example.ly": %%%
\version "2.19.19"
{c' d' e' f'}
%%% commandline actions --> result %%%
$ lilypond --ps example.ly --> creates example.ps, which I want to keep
$ lilypond example.ly --> creates example.pdf, without telling me it
On Fri, 1 May 2015, Martin Tarenskeen wrote:
The bug would be fixed if lilypond would make ghostscript use a complete path
to the intermediate lines.ps file for the ps to pdf conversion.
The issue has brought me to another problem:
LilyPond by default takes *.ly file as input and produces
for example create a file "lines.ly" with a minimal content
\version "2.19.19"
{c' d' e' f'}
and compile ...
I'm trying to narrow down the issue
It seems that on some systems (like mine).
# gs lines.ps
is expanded to something like
# gs /usr/share/ghostscript/9.15/lines.ps
but
# gs /c
-- Forwarded message --
Date: Fri, 1 May 2015 09:47:25 +0200 (CEST)
From: Martin Tarenskeen
To: lilypond-user mailinglist
Subject: my favorite bug :-)
This issue has been reported in the mailing list some time ago - I think it was
David Kastrup who discovered it - but I
On Wed, 29 Oct 2014, Gerard wrote:
I think the file is too large...
I had almost forgotten about the existence of abc2ly.
I am not sure it is very actively maintained. (Is it?)
Have you tried
1. abc2xml (http://wim.vree.org/svgParse/abc2xml.html)
2. musicxml2ly
The result from this 2-step
On Mon, 22 Sep 2014, David Kastrup wrote:
Martin Tarenskeen writes:
Hi,
Using Lilypond 2.19.14 I see the "composer" field is completely
misplaced in the output.
https://code.google.com/p/lilypond/issues/detail?id=4102>
Will be fixed in 2.19.15. I quote the announcement of
Hi,
Using Lilypond 2.19.14 I see the "composer" field is completely misplaced
in the output.
short example showing misplaced composer field
\version "2.19.14"
\header {
title = "title"
subtitle = "subtitle"
poet = "poet"
meter = "meter"
piece = "piece"
composer = "comp
On Sat, 19 Jul 2014, Francisco Vila wrote:
Sure? I know there is a message for encoding the key signature, but the clef?
Yesterday I was messing with a MIDI imported in Rosegarden and edited
a bass segment with the event editor, and one of the first events was
a clef event. Let me look at i
On Sun, 13 Jul 2014, James wrote:
I have no preferences either way - we have done this for articulate.ly
for instance - but unless we know that philomelos and LilyPond's
versions are reasonably close to start with we could end up with each
version becoming so far apart in terms of codebase tha
Hi,
If I type:
lilypond -w
I see (among other things):
Copyright (c) 1996--2012
If I type:
convert-ly -w
I see (among other things):
Copyright (C) 2001--2012
Shouldn't 2012 be bumped to 2013, or better yet, 2014?
--
MT
On Mon, 30 Dec 2013, Martin Tarenskeen wrote:
" view ps with ghostview
map :!gv --watch "%<.pdf" &
the comment should be fixed also :-) :
" view pdf with ghostview
(Personally I would choose another PDF viewer, but tha
Hi,
in lilypond-2.18.0/vim/lilypond-ftplugin.vim
I see:
" view ps with ghostview
map :!gv --watch "%<.ps" &
This will not work, and hasn't for some time, because Lilypond's default
output is pdf these days and the ps file is only temporary.
So now it should be:
" view ps with ghostvi
I'm not top-posting
The *.ly files that are produced using musicxml2ly use an indentation
style that does not conform to LilyPond's common practice.
Musicxml2ly does not un-indent closing brackets.
--
Martin Tarenskeen
___
bug-lilypo
I'm not top-posting
Hi,
Usage manual, 4.4 (Lilypond 2.17.96) says:
Inserting LilyPond output into OpenOffice.org
LilyPond notation can be added to OpenOffice.org with OOoLilyPond.
Maybe these days it should be "OpenOffice.org or LibreOffice" ?
OooLilypond works equally fine in Libreoffice.
On Fri, 30 Aug 2013, Zack Macomber wrote:
Martin,
Thanks. Guess I should have read the manual a little closer...if I update
my path (I'm on Windows) to include the LilyPond bin directory, should I be
able to run muxicxml2ly anywhere?
I am not a Windows user, but I guess musicxml2ly is also
On Thu, 29 Aug 2013, Zack Macomber wrote:
I have several Finale Allegro 2007 compositions that I would like to see in
LilyPond. I can save my compositions as a MIDI file. When I drag that MIDI
file onto the LilyPond shortcut on my desktop, a file gets written to where
the MIDI file is with t
On Wed, 21 Aug 2013, der_jo wrote:
OK, I've installed Python (3.3.2 x64) ... no changes.
Don't know if it will fix anything, but LilyPond uses Python 2.x as far as
I know. Try Python 2.7
--
MT
___
bug-lilypond mailing list
bug-lilypond@gnu.or
On Mon, 25 Feb 2013, David Kastrup wrote:
Francisco Vila writes:
2013/2/25 David Kastrup :
I think this mainly depends on the version of Ghostscript that is being
used for converting PS to PDF (used internally by LilyPond when
generating PDF). The version of LilyPond, in contrast, is most
In the following example the boxed rehearsal marks collide with the
slashSeparator at the beginning of each system
%%% start of tiny example %%%
\version "2.16.0"
\paper {
system-separator-markup = \slashSeparator
}
example = \relative c' {
\set Score.markFormatter = #format-mark-box-al
On Wed, 3 Oct 2012, Marek Klein wrote:
Hello
2012/9/30 Federico Bruni
In NR 3.5.7, The Articulate script:
"After altering your input file this way, the visual output is heavily
altered, but the standard \midi block will produce a better MIDI file."
This alteration refers to the use of \un
On Tue, 2 Oct 2012, Graham Percival wrote:
If not, perhaps it's worth subscribing bugs-lilypond to trackers for
the major distros (Debian, Ubuntu, Fedora, etc.) so that the
development team at least gets alerted to the issues out there?
Those distros can come talk to us if they want to send
On Thu, 24 May 2012, Janek Warchoł wrote:
I need help on this one, too. Does LilyPond support .MXL to .ly to .pdf
conversion? In other words, I guess, is .mxl equivalent to .xml?
I suppose so: MXL = MusicXmL = .xml
but i'm guessing, too.
.xml and .mxl are both filename extensions for MusicX
> I'm not top posting
Hi,
In the following example the spacing between the last staff on the page and the
"lyrics" below it( in this case only "---", but that does not matter ) is too
small. It does not collide, but I think the spacing should be identical to the
other staves on the the page. AT l
not know how
to create a proper "tiny example" to demonstrate the problem.
For the time being the problematic example can be downlaoded from here:
http://members.tele2.nl/m.tarenskeen/tmp/khatch-err.ly
I hope this helps.
--
Martin Tarenskeen
_
rs.tele2.nl/m.tarenskeen/tmp/khatch-err.ly
I hope this report will be helpful anyway.
--
Martin Tarenskeen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Mon, 19 Apr 2010, Graham Percival wrote:
On Sun, Apr 18, 2010 at 07:25:29PM +0200, Martin Tarenskeen wrote:
OK. Here is a tiny example (attached).
Thanks! This looks like a great report. Bug squad, could
somebody add this to the tracker?
To add one remark: It might have something
The following example demonstrates a problem with \easyHeadsOn in combination
with sharps or flats. This problem was introduced recently: I'm having no such
problems with lilypond 2.12.3.
\version "2.13.7"
\relative c' {
c d ees fis
\easyHeadsOn
c d ees fis
}
___
46 matches
Mail list logo
