Re: Horizontal beam parallel to staff
On 2021-05-10 9:10 pm, Pierre Perol-Schneider wrote:
Hi Ahanu,
How about:
\version "2.20.0"
{
%\override Beam.damping = #5
\override Beam.positions = #'(5 . 5)
g''8 b b c'' c'' b b g''
}
And for an automated approach:
\version "2.22.0"
#(define NEAR -1)
#(define FAR 1)
flattenPositions =
#(define-scheme-function
(rel-pos) (number?)
(grob-transformer 'positions
(lambda (grob orig)
(let* ((dir (ly:grob-property grob 'direction))
(ys (ordered-cons (car orig) (cdr orig)))
(y (interval-index ys (* dir rel-pos
(cons y y)
{
\override Beam.positions = \flattenPositions #NEAR
g''8 b b c'' a' b'' b'' d'
\override Beam.positions = \flattenPositions #CENTER
g''8 b b c'' a' b'' b'' d'
\override Beam.positions = \flattenPositions #(* 2 FAR)
g''8 b b c'' a' b'' b'' d'
}
-- Aaron Hill
Re: Horizontal beam parallel to staff
Hi Ahanu,
How about:
\version "2.20.0"
{
%\override Beam.damping = #5
\override Beam.positions = #'(5 . 5)
g''8 b b c'' c'' b b g''
}
Cheers,
Pierre
Le mar. 11 mai 2021 à 04:04, Ahanu Banerjee a
écrit :
> I know it is not standard practice, but I am looking for a way to make
> beams parallel to staff despite the noteheads on either side of the beam
> having different vertical positions on the staff.
>
> Setting beam damping to a high value reduces the slope substantially, but
> it doesn't go to zero. Can someone suggest a way to do this?
>
> \version "2.20.0"
> { \override Beam.damping = #5
> g''8 b b c'' c'' b b g'' }
>
>
> Thanks,
> -Ahanu
>
Re: Tempo marking with 2 notes
> "Ahanu" == Ahanu Banerjee writes:
Ahanu> Can anyone provide a simple way to make a tempo marking like
Ahanu> this: "♩= 텞 " ?
Something like this?
\version "2.22.0"
\score {
\new Staff { \time 3/4 r2.^
\markup {
\note {2.} #UP
=
\note {2} #UP
}
|
\time 2/4 r2
}
}
See http://lilypond.org/doc/v2.22/Documentation/notation/music for the
markup syntax. Earlier versions used #"2." instead of {2.} for the
durations.
Peter C
Horizontal beam parallel to staff
I know it is not standard practice, but I am looking for a way to make
beams parallel to staff despite the noteheads on either side of the beam
having different vertical positions on the staff.
Setting beam damping to a high value reduces the slope substantially, but
it doesn't go to zero. Can someone suggest a way to do this?
\version "2.20.0"
{ \override Beam.damping = #5
g''8 b b c'' c'' b b g'' }
Thanks,
-Ahanu
Re: Tempo marking with 2 notes
On 2021-05-10 6:41 pm, Ahanu Banerjee wrote: Hello, Can anyone provide a simple way to make a tempo marking like this: "♩= 텞 " ? You should be able to adapt LSR 574 [1] to achieve that. [1]: https://lsr.di.unimi.it/LSR/Item?id=574 -- Aaron Hill
Re: Tempo marking with 2 notes
Please disregard, I missed the answer in the documentation.. thanks On Mon, May 10, 2021 at 9:41 PM Ahanu Banerjee wrote: > Hello, > > Can anyone provide a simple way to make a tempo marking like this: "♩= 텞 > " ? > > Thanks, > -Ahanu >
Tempo marking with 2 notes
Hello, Can anyone provide a simple way to make a tempo marking like this: "♩= 텞 " ? Thanks, -Ahanu
Re: Part text vs Score text
Sorry Jacques, I wasn't able to do it through my phone when I first wrote the email. So, here it is. First, there is a selection of the alto part. The text "Samba" coincides in its position in all the parts, so in the Score I would like to get it just once.On the other hand, some parts get the text "open" in different places (for example, the soloist of that specific section gets it just before the repeat sign, while the others have silence). With that scenario, I couldn't write a variable with all the markings, since they would vary. My problems now is that, since I imported the text in all the parts (I created a variable to each of them), when I include it in the Score, it becomes messy and redundant (as you can see from the second image). How would be a better way to approach this? GB Em seg., 10 de mai. de 2021 às 17:03, Jacques Menu escreveu: > Hello Gabriel, > > Can you post an image of what you’re after? > > JM > > > On 10 mai 2021, at 21:00, Gabriel Borin > wrote: > > > > Hello, > > > > I have a question regarding the best way to manage score texts and part > text: after migrating to Lilypond from Musescore (an other WYSIWYG > editors), I miss the functionality of the Score Texts that affects all > parts, and the part text that is not displayed in the score. How is the > best way to achieve this in Lilypond? > > > > Also, some of the text I put on parts seem to misalign when transported > to the score, and I don't know how to fix it without affecting the part. > How can I handle this better? > > > > > > Sincerely, > > > > Gabriel > > > >
Re: Part text vs Score text
Hello Gabriel, Can you post an image of what you’re after? JM > On 10 mai 2021, at 21:00, Gabriel Borin wrote: > > Hello, > > I have a question regarding the best way to manage score texts and part text: > after migrating to Lilypond from Musescore (an other WYSIWYG editors), I miss > the functionality of the Score Texts that affects all parts, and the part > text that is not displayed in the score. How is the best way to achieve this > in Lilypond? > > Also, some of the text I put on parts seem to misalign when transported to > the score, and I don't know how to fix it without affecting the part. How can > I handle this better? > > > Sincerely, > > Gabriel >
Re: Piano: partial pedalling
(Please make sure to keep the mailing list on all messages.)
On 2021-05-10 1:42 pm, Dijkhuizen, J.F. van wrote:
Many thanks for this. When I paste the code into Frescobaldi and
compile it, I'm getting the following error message:
error: syntax error, unexpected end of input
{ s4 s4*6\gradualSustain #'((0 2 2 0)(0.3)(0.4 0 5 -3 3)) s4\sustainOff
Do you know what went wrong?
Well, there's a missing closing brace in what you quoted above. But
most likely you are hitting an issue where the >> is missing when you
copy/paste from the lists.gnu.org archive site. See this version hosted
on lilybin [1].
[1]: http://lilybin.com/kq9t97/1
-- Aaron Hill
Re: Piano: partial pedalling
On 2021-05-10 11:38 am, Dijkhuizen, J.F. van wrote: Dear All, I was wondering if anybody knows if it's possible to notate partial sustain pedalling in LilyPond (essentially 1/4. half-pedal, 3/4 pedal), and if so how. There seems to be nothing about it in the manual, and I've not been able to find anything online that I am able to use. Ideally, I'd like to be able to notate pedal level changes by means of a line, as is possible in Dorico, for example: However, just being able to specify '1/2' at the beginning of a pedal line, and, for example, 'release pedal slowly' at tthe end of a pedal line, would be great too. Any help with this would be really appreciated! There are a few ad hoc solutions if you search the archives. You can see if my hack [1] to the PianoPedalBracket stencil a few years ago would be of any use. [1]: https://lists.gnu.org/archive/html/lilypond-user/2019-01/msg00522.html -- Aaron Hill
Re: Microtonal midi output
Hi Graham, Am 10.05.21 um 18:40 schrieb Graham Breed: I didn't write any C++ but I looked at the C++ code and it looks trivial to change the pitch bend messages to MTS. "Trivial" is in the eye of the beholder :-), but it was easy enough for me to succeed. I tested with FluidSynth, and there's an update that I don't think I pushed. I think it was that you need to use the all devices Device ID (0x7f) instead of the channel number. That information literally saved my life just now: I'm in the process of creating some teaching material for tomorrow; timidity behaves strangely on my system, and FluidSynth didn't seem to use all of the tuning information in the MIDI file. The change in the Device ID you described was what did the trick, and there's no way I could have found this out by myself this evening. Thanks much! What would be more difficult is adding all the options so that either pitch bends or MTS would work — or remembering the current state so you only need to send a message when something changes. Yes, that's what I had in mind also. Conceptually, it seems clear what to do (keep track of the 'current' tuning for each key for each channel), but one has to find the right place to hook this into LilyPond's rather involved wiring. That's a task for the upcoming holidays. Best Lukas
Part text vs Score text
Hello, I have a question regarding the best way to manage score texts and part text: after migrating to Lilypond from Musescore (an other WYSIWYG editors), I miss the functionality of the Score Texts that affects all parts, and the part text that is not displayed in the score. How is the best way to achieve this in Lilypond? Also, some of the text I put on parts seem to misalign when transported to the score, and I don't know how to fix it without affecting the part. How can I handle this better? Sincerely, Gabriel
Piano: partial pedalling
Dear All, I was wondering if anybody knows if it's possible to notate partial sustain pedalling in LilyPond (essentially 1/4. half-pedal, 3/4 pedal), and if so how. There seems to be nothing about it in the manual, and I've not been able to find anything online that I am able to use. Ideally, I'd like to be able to notate pedal level changes by means of a line, as is possible in Dorico, for example: [cid:5fc29545-b07a-4416-b824-05b22139aba9] However, just being able to specify '1/2' at the beginning of a pedal line, and, for example, 'release pedal slowly' at tthe end of a pedal line, would be great too. Any help with this would be really appreciated! Thanks, Jan
Re: Microtonal midi output
On 09/05/2021, Hans Åberg wrote: > >> On 9 May 2021, at 19:31, Lukas-Fabian Moser wrote: >> >> I looked into it a bit today, and I can gladly report that (while the code >> still needs some cleaning up), I managed to patch my LilyPond to >> automatically generate the MTS messages that Graham's Python script adds >> in post-processing. (Of course, that wouldn't have been possible without >> being able to use Graham's code as a cheat sheet!) > > Graham also wrote some C++ code for generating MTS pitches that was not > integrated into LilyPond, I think. I didn't write any C++ but I looked at the C++ code and it looks trivial to change the pitch bend messages to MTS. What would be more difficult is adding all the options so that either pitch bends or MTS would work — or remembering the current state so you only need to send a message when something changes. I tested with FluidSynth, and there's an update that I don't think I pushed. I think it was that you need to use the all devices Device ID (0x7f) instead of the channel number. Graham
French-speaking virtual meeting
Hi all, For your information, the lilypond-user-fr community is organizing a French-speaking virtual meeting, planned somewhere between late May and June. It is being discussed on that list: http://lilypond-french-users.1298960.n2.nabble.com/Cafe-Lily-2021-td7591082.html We will have presentations, as well as a moment of free discussion. If you are interested in participating, feel free to join that thread and connect on D-day! Cheers, Jean
