Hey all,
plus 'moment should be enough to combine them, but having all the
articulations to a note as a property on that note event would save
me a bit of time.
Are you familiar with `Rhythmic_music_iterator::process` in
lily/rhythmic-music-iterator.cc?
(On LilyPond mailing lists, pleas
Hey all,
I am trying to add articulations to my music braille generator. As
stated before, I am using the event listening system proposed by the
"event-listener.ly" example.
Browsing through the documentation, I found the music property
articulations on
https://lilypond.org
> Le 21 avr. 2023 à 15:18, Jean Abou Samra a écrit :
>
> The idea is that rather than putting all the .otf file in one directory, you
> make one subdirectory per font. Cf. the bit about recursive searching.
By the way, this is what we’re heading toward with SMuFL anyway. It doesn’t
specify
> Now to the second approach, which I prefer. [...]
Me too. All your suggestions are sound, thanks.
Werner
> Le 21 avr. 2023 à 14:48, Wols Lists a écrit :
> Just to add to bikeshed colours, please DON'T call it "stylesheet". Call it
> the same name as the font, or something like that.
> If I've got a bunch of custom fonts I use, I just want to dump them in a
> directory and forget about them. If
On 21/04/2023 12:03, Kieren MacMillan wrote:
If, next to the .otf font file, a file called stylesheet.ily (or another
bikeshed color) is found, it is read and defines the style parameters. Because
we want to be able to apply it both globally and locally to one
score/bookpart/book, we take it i
Le vendredi 21 avril 2023 à 07:03 -0400, Kieren MacMillan a écrit :
> How modular and adaptable will that be? In a robust stylesheet system, there
> would be “inheritance”, “cascading”, etc., rather than the “include and
> overwrite” that happens with [ad-hoc] stylesheets now.
"Inheritance" is
Hi Jean,
> For those who haven't followed the (long) story, this MR basically lets
> LilyPond search for music fonts in the same way as it searches for text
> fonts. It thus makes it possible to make music fonts found with
> ly:font-config-add-font or ly:font-config-add-direc
Hi,
With [!1957](https://gitlab.com/lilypond/lilypond/-/merge_requests/1957) that
will soon become ready, I think it's about time to discuss how we want the “big
picture” user experience and font developer experience to be with respect to
alternative music fonts.
For those who ha
> Le 3 avr. 2023 à 15:34, Werner LEMBERG a écrit :
>
> Yes. There is no equivalent to `glyphshow` in PDF. For some comments
> on that see, for example,
>
> https://bugs.ghostscript.com/show_bug.cgi?id=698305#c10
> https://bugs.ghostscript.com/show_bug.cgi?id=695259
OK, thanks.
> BTW,
>>> Essentially, this option switches between the `show` and `glyphshow`
>>> PostScript operators to access Emmentaler glyphs. The former is
>>> considered the 'standard' method for accessing glyphs in a PS file
>>> (according to the GS developers); however, it needs properly set up
>>> encoding
Jean Abou Samra writes:
> Le dimanche 02 avril 2023 à 18:20 +, Werner LEMBERG a écrit :
>> Essentially, this option switches between the `show` and `glyphshow`
>> PostScript operators to access Emmentaler glyphs. The former is
>> considered the 'standard' method for accessing glyphs in a PS
Le dimanche 02 avril 2023 à 18:20 +, Werner LEMBERG a écrit :
> Essentially, this option switches between the `show` and `glyphshow`
> PostScript operators to access Emmentaler glyphs. The former is
> considered the 'standard' method for accessing glyphs in a PS file
> (according to the GS dev
> Would anyone be able to explain me what the purpose of the
> music-font-encodings option is? I'm trying to understand how the
> generation of the Emmentaler font works. I see that there is quite
> a bit of infrastructure for this option, which is used in
> `--pspdfopt`, b
Hi,
Would anyone be able to explain me what the purpose of the music-font-encodings
option is? I'm trying to understand how the generation of the Emmentaler font
works. I see that there is quite a bit of infrastructure for this option, which
is used in `--pspdfopt`, but it's not c
post as a response to my question about which
> available participants in the LilyPond community could advise on code reviews
> for Oriental microtonal music.
>
> A threading disconnect at worst.
Deliberately a new thread, as it is a wholly different topic:
I supplied the information
tml>
Therefore, I understood that post as a response to my question about
which available participants in the LilyPond community could advise on
code reviews for Oriental microtonal music.
A threading disconnect at worst.
--
Karlin High
Missouri, USA
Hans Åberg writes:
> Graham Breed wrote a file regular.ly <http://regular.ly/> that allows
> for retuning into any ET (around C4, not A4), but Adam Good is expert
> on Turkish music specifically.
>
> There are some issues with Turkish, Persian and Arabic music that must
Graham Breed wrote a file regular.ly <http://regular.ly/> that allows for
retuning into any ET (around C4, not A4), but Adam Good is expert on Turkish
music specifically.
There are some issues with Turkish, Persian and Arabic music that must be dealt
with when adapting for LilyPond: No
Well,
I reordered what I consider erroneous behaviors in the GitLab issue page
On Sun, Dec 25, 2022 at 7:55 PM Jean Abou Samra wrote:
>
>
> Le 25 déc. 2022 à 19:44, Paolo Prete a écrit :
>
>
>
>
> On Sun, Dec 25, 2022 at 7:22 PM Jean Abou Samra
> wrote:
>
>>
>>
>> > Le 25 déc. 2022 à 19:10,
Le 25 déc. 2022 à 19:44, Paolo Prete a
écrit :
On Sun, Dec 25, 2022 at 7:22 PM Jean Abou Samra <[1]j...@abou-samra.fr>
wrote:
> Le 25 déc. 2022 à 19:10, Paolo Prete <[2]paolopr...@gmail.com> a
écrit :
>
>
> BTW:
>
> {
> \override T
On Sun, Dec 25, 2022 at 7:22 PM Jean Abou Samra wrote:
>
>
> > Le 25 déc. 2022 à 19:10, Paolo Prete a écrit :
> >
> >
> > BTW:
> >
> > {
> > \override TupletBracket.bracket-visibility = ##f
> > \tuplet 3/2 { s8 s8 s8 }
> > }
> >
> > In 2.24.0 and previous versions this raises the "omitting
> Le 25 déc. 2022 à 19:28, Thomas Morley a écrit :
>
> Am So., 25. Dez. 2022 um 18:18 Uhr schrieb Jean Abou Samra
> :
>>
>>
>>
Le 25 déc. 2022 à 18:08, Paolo Prete a écrit :
>>>
>>>
>>> Hello Jean,
>>>
>>> I just verified that 2.25 doesn't accept a tuplet of skips ( i.e: \tuple
Am So., 25. Dez. 2022 um 18:18 Uhr schrieb Jean Abou Samra :
>
>
>
> > Le 25 déc. 2022 à 18:08, Paolo Prete a écrit :
> >
> >
> > Hello Jean,
> >
> > I just verified that 2.25 doesn't accept a tuplet of skips ( i.e: \tuplet
> > 3/2 { s s s }, while all the previous versions do.
> > Is this re
> Le 25 déc. 2022 à 19:10, Paolo Prete a écrit :
>
>
> BTW:
>
> {
> \override TupletBracket.bracket-visibility = ##f
> \tuplet 3/2 { s8 s8 s8 }
> }
>
> In 2.24.0 and previous versions this raises the "omitting tuplet bracket with
> neither left nor right bound" warning, even if the b
uot;
>
> \tuplet 3/2 { s s s }
>
>
> gives (in 2.24.0)
>
> Interpreting music...
>
> warning: omitting tuplet bracket with neither left nor right bound
>
> (OK, not a programming error but a warning, I misremembered).
>
>
>
> > > I understand that a tuplet
Thanks, all clear.
On Sun, Dec 25, 2022 at 6:44 PM Jean Abou Samra wrote:
> Le 25/12/2022 à 18:40, Paolo Prete a écrit :
>
Le 25/12/2022 à 18:40, Paolo Prete a écrit :
What error are you referring to, exactly? In case of my last snippet,
which produces a tuplet of three skips, it compiles fine with previous
versions.
For me,
\version "2.24.0"
\tuplet 3/2 { s s s }
gives (in 2.24.0)
Interpre
On Sun, Dec 25, 2022 at 6:18 PM Jean Abou Samra wrote:
>
>
> > Le 25 déc. 2022 à 18:08, Paolo Prete a écrit :
> >
> >
> > Hello Jean,
> >
> > I just verified that 2.25 doesn't accept a tuplet of skips ( i.e:
> \tuplet 3/2 { s s s }, while all the previous versions do.
> > Is this really inten
> Le 25 déc. 2022 à 18:08, Paolo Prete a écrit :
>
>
> Hello Jean,
>
> I just verified that 2.25 doesn't accept a tuplet of skips ( i.e: \tuplet
> 3/2 { s s s }, while all the previous versions do.
> Is this really intended?
No, as I wrote on a comment in the issue. It was not an inte
}, but how?
%---
test = #(define-music-function (parser location music) (ly:music?)
(let
((musiccpy (ly:music-deep-copy music)))
(map-some-music (lambda (evt)
(let ((nameUp (ly:music-property evt 'name)))
(cond
((eq? nameUp 'NoteEvent)
https://gitlab.com/lilypond/lilypond/-/issues/6482
Using \displayLilyMusic, you can see that your music ends up
equivalent to
\tuplet 3/2 { s8 s }
which is an unterminated tuplet.
Actually this variant still compiles fine:
\version "2.25.0"
\tuplet 3/2 { s8 c'8 }
so skips have som
Using \displayLilyMusic, you can see that your music ends up equivalent to
\tuplet 3/2 { s8 s }
which is an unterminated tuplet.
I expect that you need to fix something in your score to make tuplets
correct, and the error will disappear.
Jean
OpenPGP_signature
Description: OpenPGP digital signature
t know if there is a hidden problem inside it, but
> > it worked for all the versions prior to 2.25:
>
> Nope, on my machine it failed for all versions.
>
> >
> > %---
> >
> > test = #(define-m
oblem inside it, but
> it worked for all the versions prior to 2.25:
Nope, on my machine it failed for all versions.
>
> %---
>
> test = #(define-music-function (parser location music) (ly:music?)
> (let
> ((mu
Hello,
I just noticed an inconsistent behavior with 2.25.0. The snippet below
doesn't compile; I don't know if there is a hidden problem inside it, but
it worked for all the versions prior to 2.25:
%---
test = #(de
See
https://gitlab.com/lilypond/lilypond/-/merge_requests/1708#note_1170171295
In a nutshell, this change makes tweaks stored using a dedicated
music type in order to make them taggable.
The change isn't very complicated, but does modify LilyPond in
a somewhat deep way in that it introdu
Le 09/08/2022 à 14:31, Dan Eble a écrit :
It could be a bug in the \alternative iterator. Please create a ticket and
assign it to me. Thanks.
Here you go:
https://gitlab.com/lilypond/lilypond/-/issues/6402
Best,
Jean
On Aug 9, 2022, at 02:31, Jean Abou Samra wrote:
>
> \new Staff {
> \alternative {
> \volta 2 c'1
> }
This unfolds better (but not well):
\alternative {
\volta 2 \new Staff ...
}
Conditional (folded/unfolded) context creation is something I t
\version "2.23.12"
\layout {
\context {
\Score
\remove Volta_engraver
\remove Staff_collecting_engraver
}
\context {
\Staff
\consists Volta_engraver
\consists Staff_collecting_engraver
}
}
{
\repeat volta 2 {
c'1
<<
\alternative {
\volta 1
On 2022-06-28 7:10 pm, Aaron Hill wrote:
Implementing \seriesMusic amounts to [...]
Proof of concept below, but note that this code lacks any safety/sanity
checks.
\version "2.22.0"
%% BEGIN FUNCTION DEFINITION
#(define (sequential-music? arg)
(and (ly:music? arg)
ere's little
difference in doing it this way from enclosing each measure in braces
and putting "\\" between them.
\parallelMusic defines music variables, which is significantly different
than the << \\ >> construct which only instantiates voices.
What's more, even
Dan wrote:
Are you aware of \parallelMusic ?
AFAIK, \parallelMusic requires me to write one full measure of each
voice while interleaving the voices.
As long as I'm writing it all into one stave, there's little difference
in doing it this way from enclosing each measure in braces and putt
On Jun 28, 2022, at 19:44, Petr Pařízek wrote:
>
> Would it ever be possible (perhaps in a future version) to make some syntax
> adjustments in LilyPond which would make writing multiple-voiced music at
> least slightly easier for people like me?
Are you aware of \parallelMusic ?
—
Dan
e were a few text-based file formats for music
notation which all had one common feature.
The events that were supposed to occur all at the same time were given
on the same line of text, while the events that were supposed to occur
later were given on subsequent lines.
This had one strong advantage
Tim's Bitstream writes:
>> On Mar 20, 2022, at 2:24 AM, Werner LEMBERG wrote:
>>
>> What about providing a new command `\upbeat` and moving `\partial`
>> into oblivion? Compare this to `\tuplet` vs. `\times`.
>
> Perhaps this is an American jazzism, but we would refer to those as
> \pickup not
rds
> > > compatibility would only need to exist for a time. A warning could
> > > be issued whenever a user applies the older syntax; this would
> > > inform the user of the impending breaking change while still
> > > allowing existing code to compile. Wh
> On Mar 20, 2022, at 2:24 AM, Werner LEMBERG wrote:
>
> What about providing a new command `\upbeat` and moving `\partial`
> into oblivion? Compare this to `\tuplet` vs. `\times`.
Perhaps this is an American jazzism, but we would refer to those as \pickup
notes.
Le 20/03/2022 à 10:01, Aaron Hill a écrit :
All of those things *are* music, as far as LilyPond is concerned. It
is just that commands like \tempo have no duration, so the following
is nonsensical since the music has zero length:
\partial \tempo 4 = 90
Your "global" variable l
only music as
argument would have to move to each part, which would introduce unnecessary
typing and disrupt the logic of the structure. Sure it can be worked around,
but I would see it as a step backwards. Or have I misunderstood?
> 20 mars 2022 kl. 05:36 skrev Aaron Hill :
>
> Fair poin
What if instead of `\upbeat` (which is weirdly named when used in the
end-of-music/phrase/hymn/passage scenario) this new thing is just called
`\partialMusic`?
It's backward compatible, does something easy to use in some simple
scenarios, leaves everything else in place for more refined use
I do not really like the idea that much to be honest. Of course it would be
cool if we just have to specify the music and no duration, but in the end
\partial is not really a command about the music, but about the measure
structure. Binding it to some music would be a bit like having \time take
variables, expressions like \partial 4 s4
are common. Certainly \partial 4 would be most succinct, but it creates
no actual duration in sequential music. Naturally, the spacer rest is
used so later commands occur when I need them. My proposal leads to
\partial s4 as a reasonable construct t
essions. As such, \partial might need to support
>>>>> both
>>>>> duration and music arguments. Initially I thought this might not be
>>>>> possible, given that a naked duration can be treated as music;
>>>>> but the
>>>>> follow
To me, upbeat (opposite the term downbeat) describes
articulation/emphasis more than it does timing. \anacrusis or \pickup
are better options though still too strongly linked to the beginning
of a piece.
That's a point where my English music terminology skills a lacking: In
German
On 2022-03-20 1:56 am, Lukas-Fabian Moser wrote:
What about providing a new command `\upbeat` and moving `\partial`
into oblivion? Compare this to `\tuplet` vs. `\times`.
Werner
... Or you could use the brand new command \upbeat when music follows,
keep \partial, and you don't ha
such. As I understand it having
\partial to accept only music as argument would have to move to each
part, which would introduce unnecessary typing and disrupt the logic
of the structure. Sure it can be worked around, but I would see it as
a step backwards. Or have I misunderstood?
All of those
What about providing a new command `\upbeat` and moving `\partial`
into oblivion? Compare this to `\tuplet` vs. `\times`.
Werner
... Or you could use the brand new command \upbeat when music follows,
keep \partial, and you don't have to worry about backwards
compatibility.
issued whenever a user applies the older syntax; this would
> > inform the user of the impending breaking change while still
> > allowing existing code to compile. When it is convenient, a future
> > release would only support music as the argument.
>
> What about providin
What if you rotate them instead?
Rename the current \partial \partialDuration,
convert.ly now is just s/partial/partialDuration/
and \partial always takes music from now on
It's the same as Werner said, but keeps the good name
L
On Sun, 20 Mar 2022, 08:24 Werner LEMBERG, wrote:
>
&
>>>>> A convert-ly rule would probably not be possible given the
>>>>> limited power of regular expressions. As such, \partial might
>>>>> need to support both duration and music arguments. Initially I
>>>>> thought this might not b
On 2022-03-19 7:53 pm, Dan Eble wrote:
On Mar 19, 2022, at 20:53, Aaron Hill wrote:
...
A convert-ly rule would probably not be possible given the limited
power
of regular expressions. As such, \partial might need to support
both
duration and music arguments. Initially I thought this might
On Mar 19, 2022, at 20:53, Aaron Hill wrote:
...
>>> A convert-ly rule would probably not be possible given the limited power
>>> of regular expressions. As such, \partial might need to support both
>>> duration and music arguments. Initially I thought this might not
> >>
> >>
> >> \version "2.22.0"
> >>
> >> partial =
> >> #(define-music-function (mus) (ly:music?)
> >>(_i "Make a partial measure.")
> >>(let* ((mom (ly:music-length mus))
> >>
On 2022-03-19 5:46 pm, Thomas Morley wrote:
Am So., 20. März 2022 um 00:02 Uhr schrieb Aaron Hill
:
Here would be a possible refactoring:
\version "2.22.0"
partial =
#(define-music-function (mus) (ly:music?)
(_i "Make a partial measure.")
(let* ((mom
Hello folks,
Here is a first presentation of one of the two current projects aiming at a
powerful tool for Braille music writing.
Sao Mai is a foundation in Vietnam, the other project is being done by the
MuseScore team.
JM
> Début du message réexpédié :
>
> De: Sarah Morle
Jean Abou Samra writes:
> Le 07/02/2022 à 21:18, David Kastrup a écrit :
>> The obvious thing would be to do process-music like we do
>> process-acknowledged: translators should be robust against multiple
>> calls; and whenever new events are announced to some translato
Le 07/02/2022 à 21:18, David Kastrup a écrit :
The obvious thing would be to do process-music like we do
process-acknowledged: translators should be robust against multiple
calls; and whenever new events are announced to some translator, it gets
another round of process-music to deal with it
Jean Abou Samra writes:
> To fill this hole, I am musing about adding a new translator slot
> called pre-process-music. The principle should be clear from the
> name: pre-process-music is called on all translators after all
> listeners, and before all process-music slots. It can
Translators use a two-step mechanism for reacting to stream
events whereby they first record them in listeners, waiting to
have gathered them all and for some early effects to happen like
property sets, and then turn to their grob creation actions in
process-music, at a point where writes are
Dear LilyPond community,
based on Kees van den Doel's `persian.ly`, I've submitted a Merge
Request to integrate support for Iranian classical music into
LilyPond.
https://gitlab.com/lilypond/lilypond/-/merge_requests/1060
Please comment (and ideally, revise)!
You have to
> The page breaker is the single one area I've always been afraid of
> looking at :-) It's all C++, the algorithms are not entirely
> trivial, and it is very performance-sensitive.
What about slurs? This is really black art IMHO :-)
Werner
Jean Abou Samra writes:
> The page breaker is the single one area I've
> always been afraid of looking at :-) It's all
> C++, the algorithms are not entirely trivial,
> and it is very performance-sensitive.
It would go a long way if the page _builder_ was moved from C++ to
Scheme and got under
Hi Kieren,
Le 25/11/2021 à 16:02, Kieren MacMillan a écrit :
Hi all,
I've always wanted Lilypond to have the following (related) abilities:
1. Consider header and music separately in the spacing/breaking
calculations; and
Could you say a bit more? In what respect would
they differ?
Hi all,
I've always wanted Lilypond to have the following (related) abilities:
1. Consider header and music separately in the spacing/breaking calculations;
and
2. Be able to force systems-on-first-page separately from systems-per-page
[et al.].
Obviously the equivalent behaviour c
Le 11/09/2021 à 16:43, Richard Shann a écrit :
I came across a situation where LilyPond crashes caused by a badly
placed \pageBreak. I've chopped most of the music out of the example
but when I tried to remove more the crash stopped.
The error message ends:
Finding the ideal number of
I came across a situation where LilyPond crashes caused by a badly
placed \pageBreak. I've chopped most of the music out of the example
but when I tried to remove more the crash stopped.
The error message ends:
Finding the ideal number of pages...
Fitting music on 1 page...lilypond:
/hom
I have been using the music-map function for years.
I was very surprised to find, with the French list, that this function
did not behave in the way I had always thought it would.
%%%
\version "2.22.0"
music = c4->
#(display-scheme-music music)
#(display "----
Am So., 7. März 2021 um 13:11 Uhr schrieb Thomas Morley
:
>
> Hi all,
>
> I cross-post this to user- and devel-list:
>
> The unapproved LSR-snippet:
> https://lsr.di.unimi.it/LSR/Item?u=1&id=1122
> basically duplicates the doc-tagged:
> https://lsr.di.unimi.it/LSR/Snippet?id=266
>
> If nobody speak
Hi all,
I cross-post this to user- and devel-list:
The unapproved LSR-snippet:
https://lsr.di.unimi.it/LSR/Item?u=1&id=1122
basically duplicates the doc-tagged:
https://lsr.di.unimi.it/LSR/Snippet?id=266
If nobody speaks up I'll delete it soon.
Cheers,
Harm
Am Sa., 6. März 2021 um 20:42 Uhr schrieb Dan Eble :
>
> Lately, I've been trying to contribute self-contained, well-tested
> enhancements to repeated music in bottom-up fashion. In the code review for
> the `\section` command, Harm expressed interest in what's still in
Lately, I've been trying to contribute self-contained, well-tested enhancements
to repeated music in bottom-up fashion. In the code review for the `\section`
command, Harm expressed interest in what's still in the queue. I don't want to
clutter the review with tangential dis
Hello all,
I was catching up on the blog posts for GNU Guix, and I thought that one in
particular might be interesting to some members of the LilyPond community.
There was a post about music production on a Guix system that utilized
LilyPond. The process integrated usage of both the PDF and
On 2020-11-16 9:48 pm, K.L. wrote:
P.S. I can't imagine some guys in a band using a music sheet with
different
measure indices for every track😂. How will they tell each other where I
am
playing? If there are some repeat marks, will they be uniform in
position?
If they are, solely decl
P.S. I can't imagine some guys in a band using a music sheet with different
measure indices for every track😂. How will they tell each other where I am
playing? If there are some repeat marks, will they be uniform in position?
If they are, solely declaring the first track's layout is e
n as a grammar
token.
Personally, I don't think this is very necessary.
On Mon, Nov 16, 2020 at 9:16 PM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> Hi,
>
> >> How does that work with polymetric music?
> > Sorry, I don't know what is polymetr
Hi,
>> How does that work with polymetric music?
> Sorry, I don't know what is polymetric music exactly. Can you show an example?
See the second example (“Different time signatures with unequal-length
measures”) in this section of the Lilypond docs:
<http://lilypond.org/doc/v2
>
> How does that work with polymetric music?
>
>
Sorry, I don't know what is polymetric music exactly. Can you show an
example?
Hi K.L.,
> Without layout structures, we can store music staff in a more regular way,
> like this:
How does that work with polymetric music?
Thanks,
Kieren.
Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ emai
I doubt that it is necessary to increase complexity so much to take care of
typical D.C. and D.S. repeats. I've had it in mind to try adding a new repeat
type, \repeat segno N {…}. It would lay out the music like a volta repeat, but
using the appropriate marks and jump instructions rather than vo
The blog link is missed, appended here:
https://findlab.github.io/2020/11/15/music-layout-language/
On Sun, Nov 15, 2020 at 6:20 PM K.L. wrote:
> Hi all.
>
> For a multiple voices music score, all voices share the same repeat
> positions. Such as:
>
> <<
>> {
>
Hi all.
For a multiple voices music score, all voices share the same repeat
positions. Such as:
<<
> {
> \repeat volta 2 { g1 g g g }
> \repeat volta 2 { g g g g }
> }
> {
> \repeat volta 2 { c1 c c c }
> \repeat volta 2 { c c c c }
>
Hello. I am Associate Professor Emre Pınarbaşı, one of the lecturers of
Samsun Ondokuz Mayıs University State Conservatory. I specialize in
Traditional Turkish Music. I have been writing my notes using Lilypond for
many years.
However, the program should expand the MAKAM.LY content a little more
Hello. I am Associate Professor Emre Pınarbaşı, one of the lecturers of
Samsun Ondokuz Mayıs University State Conservatory. I specialize in
Traditional Turkish Music. I have been writing my notes using Lilypond for
many years.
However, the program should expand the MAKAM.LY content a little more
Hello. I am Associate Professor Emre Pınarbaşı, one of the lecturers of
Samsun Ondokuz Mayıs University State Conservatory. I specialize in
Traditional Turkish Music. I have been writing my notes using Lilypond for
many years.
However, the program should expand the MAKAM.LY content a little more
David Kastrup writes:
> David Kastrup writes:
>
>> Graham Percival writes:
>>
>>> On Sun, Jan 22, 2012 at 11:49:06AM +0100, David Kastrup wrote:
>>>>
>>>> Anybody actually using the "music-cause"? Inside of LilyPond, t
Am Donnerstag, den 20.02.2020, 17:12 +0100 schrieb David Kastrup:
> David Kastrup writes:
>
> > Graham Percival writes:
> >
> > > On Sun, Jan 22, 2012 at 11:49:06AM +0100, David Kastrup wrote:
> > > > Anybody actually using the "music-c
David Kastrup writes:
> Graham Percival writes:
>
>> On Sun, Jan 22, 2012 at 11:49:06AM +0100, David Kastrup wrote:
>>>
>>> Anybody actually using the "music-cause"? Inside of LilyPond, the only
>>> appearance (apart from its declaration)
commit a19aed147bf1605b21cbe7b1909ff6cbf519fb64
Author: Han-Wen Nienhuys
Date: Sat Feb 8 21:02:12 2020 +0100
GUILE2: Scale GC heap with the number of smobs
https://codereview.appspot.com/561390043/
On 2020/02/09 10:08:20, hanwenn wrote:
> A way around that is to change all instances of vectors holding SCM
values to a
> new
> gc_vector type that has a custom allocator. That will be significant
work, but
> probably
> desirable in the long term.
I'd recommend a two-pronged approach for now,
1 - 100 of 1839 matches
Mail list logo
