>
>
>
> When doing \musicxml \simplescore the scheme function gets an object of the
> type ly:score.
>
>
>
> By digging in code I found out that from this score music can be extracted
> using ly:score-music
>
> Also header can be extracted using ly:score-header an
-music
Also header can be extracted using ly:score-header and output-defs using
ly:score-output-defs
The extracted music can be used without a problem.
However I can not figure out how to use the extracted header and
output-defs.
I want to be able to extract information like composer and
Urs,
On Fri, Jan 23, 2015 at 11:17 AM, Urs Liska wrote:
> Hi David,
>
> thanks, that works great.
> It did *not* write to a file, but that's not the issue here.
> The main point is that it listens to implicit break events.
>
The only time it doesn't write to a file for me is when I don't save
aks, page breaks
and page turns have been placed in LilyPond?
I'm sure this information has to be present at one point, but
someone (I think it may have been David Nalesnik) expressed the
opinion that engravers could only access explicit \break-s.
I would like to write o
e at which positions (in terms of barnumber and
> measure-position) the final line breaks, page breaks and page turns have
> been placed in LilyPond?
> I'm sure this information has to be present at one point, but someone (I
> think it may have been David Nalesnik) expressed the opini
reaks, page breaks and page turns
have been placed in LilyPond?
I'm sure this information has to be present at one point, but someone (I
think it may have been David Nalesnik) expressed the opinion that
engravers could only access explicit \break-s.
I would like to write out a log file cont
2014-02-16 12:51 GMT+01:00 David Kastrup :
> Conversion works after normalizing the awful Scheme formatting. Try
> convert-ly on the following:
>
Thanks David
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bu
version "2.14.0"
%{ Display ly file information on the score, including file name, file size,
LilyPond version, date processed, time processed, time last modified, and
the LilyPond command line. %}
#(define comml(object->string (command-line)))
#(define loc (+ (string-rindex c
Hi Squad,
The following snippet :
http://lsr.dsi.unimi.it/LSR/Item?id=197
partially compile with warnings :
Processing...
Parsing...
.../file-information.ly:14:2: error: GUILE signaled an error for the
expression beginning here
#
( define siz ( object->string ( stat:size ( stat filen
.../fil
>> [...] it seems that Pango doesn't support this currently out of the
>> box which means that lilypond doesn't directly benefit.
>
> Well, I'm not sure about that anymore.
>
> The feature makes sense if you have several variants of the same
> family, and these variants are designed to be used at
the inner
workings of OpenType (or any) font technologies.
Aah. Look up the `size' feature on this page:
http://www.microsoft.com/typography/otspec/features_pt.htm
I wasn't aware that such a feature exists. The necessary information
could be rather easily added using FontForge, I
font technologies.
Aah. Look up the `size' feature on this page:
http://www.microsoft.com/typography/otspec/features_pt.htm
I wasn't aware that such a feature exists. The necessary information
could be rather easily added using FontForge, I think. Your request
definitely deserves a
Hello,
2012/9/6 Urs Liska
> Is there any information about optical sizes in the OpenType fonts used by
> LilyPond?
> And if not, would it be complicated to add this?
>
You should ask on devel list first...
Marek
bug squad member
___
Hello,
2012/9/6 Werner LEMBERG
> > - -dno-point-and-click was exactly what I was looking for;
> > lilypond --help had not revealed that wisdom.
>
> Indeed, it is missing for `lilypond -dhelp'. Looks like a bug...
>
Tthis was added as
http://code.google.com/p/lilypond/issues/detail?id=2814by Co
Is there any information about optical sizes in the OpenType fonts used
by LilyPond?
And if not, would it be complicated to add this?
To explain:
I have an Adobe OpenType font family containing its font faces in four
sets: text, caption, subhead and display, each set designed for use at
69038.n5.nabble.com/dno-point-and-click-undocumented-was-PDF-information-issues-tp132343p132358.html
Sent from the Bugs mailing list archive at Nabble.com.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
> - -dno-point-and-click was exactly what I was looking for;
> lilypond --help had not revealed that wisdom.
Indeed, it is missing for `lilypond -dhelp'. Looks like a bug...
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.
Comment #3 on issue 2385 by harmathdenes: Translated donwnload page does
not show correct information for MacOSX
http://code.google.com/p/lilypond/issues/detail?id=2385
Done in Hungarian (commit 3f1432a63bf849f003b67e8b481f4e38405f6253).
___
bug
Updates:
Status: Started
Comment #2 on issue 2385 by paconet@gmail.com: Translated donwnload
page does not show correct information for MacOSX
http://code.google.com/p/lilypond/issues/detail?id=2385
Done in Japanese.
___
bug-lilypond
Updates:
Owner: paconet@gmail.com
Comment #1 on issue 2385 by paconet@gmail.com: Translated donwnload
page does not show correct information for MacOSX
http://code.google.com/p/lilypond/issues/detail?id=2385
(No comment was entered for this change
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 2385 by pkx1...@gmail.com: Translated donwnload page does not
show correct information for MacOSX
http://code.google.com/p/lilypond/issues/detail?id=2385
On 10 March 2012 10:38, Hans Aikema wrote:
On 9-3-2012 18:39, Graham
Updates:
Status: Verified
Comment #18 on issue 2320 by philehol...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320
Verified that these changes are in current git master
Updates:
Status: Fixed
Comment #17 on issue 2320 by philehol...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320
Reverted to fixed, since this needs reverifying by checking the source as
pulled from git
Updates:
Status: Verified
Comment #16 on issue 2320 by colingh...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320
Verified patch included in 2.15.32 by checking the commitish with git log
origin.
Also
Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_15_32
Comment #15 on issue 2320 by janek.li...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320
pushed as 90ee61d5b681295b8b401128ca9bc48554eee66a
Updates:
Labels: -Patch-countdown Patch-push
Comment #14 on issue 2320 by colinpkc...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320
Counted down to 20120301, please push
Updates:
Labels: Patch-review
Comment #12 on issue 2320 by d...@gnu.org: Patch: CG: add information about
Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320#c12
Patchy the autobot says: LGTM.
___
bug-lilypond
Updates:
Labels: Patch-new
Comment #11 on issue 2320 by janek.li...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320#c11
CG: add information about Regtest Checking Project
Phil Holmes wrote a nice web app
Updates:
Labels: Patch-review
Comment #10 on issue 2320 by julien.r...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320#c10
Patchy the autobot says: LGTM.
___
bug
Comment #9 on issue 2320 by janek.li...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320#c9
CG: add information about Regtest Checking Project
Phil Holmes wrote a nice web app that allows people to
review regtests
Updates:
Labels: Patch-new
Comment #7 on issue 2320 by janek.li...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320#c7
CG: add information about Regtest Checking Project
Phil Holmes wrote a nice web app that
Comment #6 on issue 2320 by d...@gnu.org: Patch: CG: add information about
Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320
Relevant part of the logfile:
Please check the logfile contributor.makeinfotxt.log for errors
make[1]: *** [out/contributor.txt] Error
Updates:
Labels: Patch-needs_work
Comment #5 on issue 2320 by d...@gnu.org: Patch: CG: add information about
Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320#c5
Patchy the autobot says: warning: 1 line adds whitespace errors.
Problem with issue 2320
Updates:
Labels: Patch-new
Comment #4 on issue 2320 by janek.li...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320#c4
CG: add information about Regtest Checking Project
Phil Holmes wrote a nice web app that
Comment #3 on issue 2320 by julien.r...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320
It also uses undefined macros @docLinkSplit and @docLinkBig (those are
defined in web.texi but not in contributor.texi
Updates:
Labels: -Patch-new Patch-needs_work
Comment #2 on issue 2320 by d...@gnu.org: Patch: CG: add information about
Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320
This patch introduces a new node without entering it in the menu structure
Comment #1 on issue 2320 by janek.li...@gmail.com: Patch: CG: add
information about Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320#c1
CG: add information about Regtest Checking Project
Phil Holmes wrote a nice web app that allows people to
review regtests
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2320 by janek.li...@gmail.com: Patch: CG: add information about
Regtest Checking Project
http://code.google.com/p/lilypond/issues/detail?id=2320
CG: add information about Regtest Checking Project
Phil Holmes wrote a nice
Status: Accepted
Owner:
Labels: Type-Other
New issue 2241 by philehol...@gmail.com: Book only puts copyright
information on the first page
http://code.google.com/p/lilypond/issues/detail?id=2241
Reported by Christopher Maden:
When using multiple bookparts within a book, it would be
Updates:
Labels: -fixed_2-14_0 fixed_2_14_0
Comment #11 on issue 1502 by carl.d.s...@gmail.com: Document information in
PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
(No comment was entered for this change
Updates:
Labels: fixed_2-14_0
Comment #10 on issue 1502 by carl.d.s...@gmail.com: Document information in
PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
(No comment was entered for this change
Updates:
Status: Verified
Comment #9 on issue 1502 by philehol...@googlemail.com: Document
information in PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
Thanks for this, Keith. Took me a while to research the fact that
Comment #8 on issue 1502 by k-ohara5...@oco.net: Document information in
PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
Sounds like cut-and-paste did not result in a proper UTF8-encoded .ly file
for Phil. I get a good PDF file
Updates:
Summary: Document information in PDF headers requires escapes for accented
characters
Comment #7 on issue 1502 by philehol...@googlemail.com: Document
information in PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
If I
Updates:
Status: Fixed
Comment #6 on issue 1502 by colinpkc...@gmail.com: DOcument information in
PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
Unverified in 2.13.61
___
bug
Updates:
Status: Verified
Comment #5 on issue 1502 by colinpkc...@gmail.com: DOcument information in
PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
Verified 2.15.0
___
bug
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_0
Comment #4 on issue 1502 by percival.music.ca: DOcument information in PDF
headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
(No comment was entered for this
Updates:
Status: Started
Comment #3 on issue 1502 by reinhold...@gmail.com: DOcument information in
PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
Pushed to master with commit
dffe04e8e1a7c0b94fdfc30e44fe141dfbe7cbec
Updates:
Labels: -Patch-new Patch-review
Comment #2 on issue 1502 by colinpkc...@gmail.com: DOcument information in
PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
Compiles and clean regtest on 2.13.60
Updates:
Labels: Patch-new
Comment #1 on issue 1502 by reinhold...@gmail.com: DOcument information in
PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
Patch is up for review:
http://codereview.appspot.com/4398046
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1502 by colinpkc...@gmail.com: DOcument information in PDF
headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
An example:
\version "2.13.48"
\header
Updates:
Status: Verified
Comment #29 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
No complaints yet, so I'm declaring it "good enough", with the
Updates:
Status: Fixed
Labels: fixed_2_13_32
Comment #28 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Neil: technically the "one last look" should
Comment #27 on issue 989 by pkx1...@hotmail.com: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
?
All the reg tests were listed, and as I (and others) docced them the list
was reviewed by Phil who removed the
Comment #26 on issue 989 by n.puttock: ensure that no information about
2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I've added "scheme" and "symbols and glyphs" to that snippet
These aren't used in the docs.
Comment #25 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Sorry for the pronoun misuse.
Apparently a snippet only makes it into our docs if it's tagged with "docs
Comment #24 on issue 989 by bealingsplayfordnews: ensure that no
information about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
http://lsr.dsi.unimi.it/LSR/Item?id=706
As stated a few times, it's not "them
Comment #23 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I just did a LSR update, but didn't see them. Were they tagged with "docs"
Comment #22 on issue 989 by PhilEHolmes: ensure that no information about
2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
The one that remained that needs to be done has just been uploaded to the
LSR. The other that remained outstanding
Comment #21 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
LSR is now up; have those two snippets been added? I can't recall seeing
them in a LSR update. If they&#x
Comment #20 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
LSR seems to be down; we won't have the latest 2 snippets until it's back
up and we can download from th
Comment #19 on issue 989 by pkx1...@hotmail.com: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I think this is now done.
of the 6 remaining snippets, 4 were committed yesterday and the last 2 have
been put
Updates:
Summary: ensure that no information about 2.12.3 features is only in the
regtests
Comment #18 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
As Han-Wen pointed out
Updates:
Owner: ---
Comment #17 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
A lot of these things were never added to the 2.12 docs (or 2.10, or
2.8...). But with the old doc system
Comment #16 on issue 989 by hanwenn: ensure that no information is only in
the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
graham,
not wanting to rain on anyone's parade, but why are you holding back the
release for this? Have these things been removed from the
I'd also like someone to review the entries (in the wiki) for
markup-eyeglasses.ly - this is already documented
lyric-hyphen.ly - half the ly file is not shown in the reg tests
and I am not sure what to do here.
font-postscript.ly - this i believe is already documented
I've added comments
Comment #15 on issue 989 by pkx1...@hotmail.com: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Just an update as I have been doing most of the work here.
According to:
http://wiki.lilynet.net/index.php/Regtests
I have left to do
"Phil Holmes" wrote in message
news:i05ajd$18...@dough.gmane.org...
wrote in message
news:14-9567054385019064696-7381504033751444317-lilypond=googlecode@googlecode.com...
Comment #14 on issue 989 by percival.music.ca: ensure that no information
is only in the regt
wrote in message
news:14-9567054385019064696-7381504033751444317-lilypond=googlecode@googlecode.com...
Comment #14 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
PS the easiest way to figure
Comment #14 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
PS the easiest way to figure out what's "blocking work" would just be to go
to the top of the list and find the first reg
Comment #13 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
The biggest problem right now is the lack of somebody organizing this
effort. See
http://lists.gnu.org/archive/html/lilypond-devel/2010
Comment #12 on issue 989 by kie...@alumni.rice.edu: ensure that no
information is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Can I help with this issue?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
Comment #11 on issue 989 by kie...@alumni.rice.edu: ensure that no
information is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Can I do this one?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
Comment #10 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
postfix \cresc should be documented elsewhere than the regtests.
___
bug-lilypond mailing
Updates:
Status: Started
Comment #9 on issue 989 by pnorcks: ensure that no information is only in
the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
(No comment was entered for this change.)
___
bug-lilypond mailing
Comment #8 on issue 989 by percival.music.ca: ensure that no information is
only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Comment 7: committed.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred
Comment #7 on issue 989 by pkx1...@hotmail.com: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Graham, here is a patch to show the non-integer example for \bendAfter in
the NR i
haven't touched any snippets though - they
Comment #6 on issue 989 by v.villenave: ensure that no information is only
in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Thanks for posting this howto, Graham. I've been ill for a few days and
it's not
getting any better, but I'll go on with the re
Comment #5 on issue 989 by percival.music.ca: ensure that no information is
only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Unfortunately, most of the regtests that Valentin picked out don't have
anything to
do with the NR, so it's not your concern.
Comment #4 on issue 989 by pkx1...@hotmail.com: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I can help with the NR stuff. I have looked at the Wiki but don't really
understand
what it is that needs documenting. Sorry to be
Comment #3 on issue 989 by v.villenave: ensure that no information is only
in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I have begun an extensive review of the regtests, my current progression
may be seen
on http://wiki.lilynet.net/index.php/Regtests
We need
Comment #2 on issue 989 by percival.music.ca: ensure that no information is
only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Great! A few more tidbits:
- you don't need to write the docs yourself; just keep track of regtest
filenames
with info we shoul
Updates:
Owner: v.villenave
Comment #1 on issue 989 by v.villenave: ensure that no information is only
in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I'm taking ownership of this one. Not that I won't welcome any help in
handling it;
any (
On Sun, Feb 21, 2010 at 1:37 AM, Robin Bannister wrote:
> Patrick McCarty wrote:
>>
>> I will try to see what's going on.
>
> See here for an overview
> http://lists.gnu.org/archive/html/bug-lilypond/2010-02/msg00124.html
Thanks, submitted:
http://code.google.com/p/lilypond/issues/detail?id=1022
Patrick McCarty wrote:
I will try to see what's going on.
See here for an overview
http://lists.gnu.org/archive/html/bug-lilypond/2010-02/msg00124.html
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/
Hi,
I'm attaching smaller versions of the screenshots you sent me off
list, so that it will be easier for everyone to see what's going on.
On 2010-02-20, Patrick McCarty wrote:
> On Sat, Feb 20, 2010 at 7:59 AM, Rudi Radler
> wrote:
> > For explaining screen shots pls. check
> > http://www.lilyp
On Sat, Feb 20, 2010 at 7:59 AM, Rudi Radler
wrote:
> For explaining screen shots pls. check
> http://www.lilypondforum.de/index.php?action=dlattach;topic=563.0;attach=557
Hi,
Please attach the screenshots to this list, since I cannot access
those attachments you are linking to.
Thanks,
Patrick
For explaining screen shots pls. check
http://www.lilypondforum.de/index.php?action=dlattach;topic=563.0;attach=557
kind regards
Radler
Hannover, Germany
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilyp
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Critical
New issue 989 by percival.music.ca: ensure that no information is only in
the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Some information can only be found in regtests... even worse, it's
h does display
>> the meter as 3/4.
>
> Hm.
>
> I don't know about midi time sigs, can anyone else verify? This looks
> weird indeed.
>
> % \time information is not rendered in the midi file
>
> \version "2.12.0"
> \score {
> \relative c'&
#x27;t know about midi time sigs, can anyone else verify? This looks
weird indeed.
% \time information is not rendered in the midi file
\version "2.12.0"
\score {
\relative c''' {
\time 3/4
g
}
\midi { }
}
Regards,
Valentin
__
2009/1/28 Marten Visser :
> Dear developers,
Greetings and sorry for the delay,
> The \time information is not being output to midi file.
> See the example.
Hmm... /What/ example? :-)
Regards,
Valentin
___
bug-lilypond mailing list
bug
Dear developers,
The \time information is not being output to midi file.
See the example.
I use Anvil Studio verison 2008.09.04 to view the contents of the midi file.
Best,
Marten
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
This is an autoresponder. I'll never see your message.
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
In my old score I had:
\property ChoirStaff.autoBeamSettings \override #'(end * * * *)
= #(make-moment 1 4)
convert-ly converts this to
#(override-auto-beam-setting '(end * * * *) 1 4)
To get the same semantics that should be
#(override-auto-beam-setting '(end * * *
Dies ist eine automatisch generierte Meldung - auto-generated email .
Die Mail mit folgenden Eigenschaften - original mail header :
Subjekt: Re: Document
Absender / from: <[EMAIL PROTECTED]>
Empfänger / to : <[EMAIL PROTECTED]>
Path :
Received:
something is going wrong
<>
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
Are interested in Working Full time at home?
If so just take one moment to see how you can start today.
http://www.ecom-universe.net/splash1/FF.htm
- No cold calling - No sales calls
- Put your computer to work
- No Boring Meetings to Attend.
- A Simple Turnkey System.
- You Can Earn Money Quick
o Pacific Rim
Address: munnari.oz.au (128.250.1.21)
o Europe
Address: nic.nordu.net (192.36.148.17)
Look for the file /rfc/rfc1521.txt
Another source of informat
o Pacific Rim
Address: munnari.oz.au (128.250.1.21)
o Europe
Address: nic.nordu.net (192.36.148.17)
Look for the file /rfc/rfc1521.txt
Another source of informat
1 - 100 of 101 matches
Mail list logo
