Kieren MacMillan writes:
> Hi Valentin (et al.),
>
> This is looking marvellous!
>
> Agreed! This is the kind of mechanism I’ve been seeking for quite a
> while now. Beyond the obvious (dynamics), I have lots of applications:
> sending text/markup “past” an intervening context; sharing items
> a
On 28/10/2021 14:39, Carl Sorensen wrote:
*From: *lilypond-user
on behalf of
Charlie Boilley
*Date: *Thursday, October 28, 2021 at 1:37 AM
*To: *"lilypond-user@gnu.org"
*Subject: *Licensing and custom lines
Dear Lilypond community,
Then, how can be 100% sure that I can keep :
- my musi
> Am 29.10.2021 um 13:47 schrieb Wol :
>
>
> Copyright exists SEPARATELY in the composition, the arrangement, the
> performance, and the edition.
>> As long as you distribute only engravings (output from LilyPond), there is
>> no assertion in GPL of a need to release source, as described in m
Hi David,
>> My *big* question is: Can notes be pushed *with timing
>> synchronization* between context?
>
> Without storing events, how would it even be possible without timing
> synchronisation? Iteration happens in time order. Well, apart from
> grace timing quirks.
1. That was my intuition
Hi all! I just needed to state that this thread completely blew my mind.
Sorry for the spam, I found this too awesome to watch silently.
El vie, 29 oct 2021 a las 10:25, Kieren MacMillan (<
kieren_macmil...@sympatico.ca>) escribió:
> Hi David,
>
> >> My *big* question is: Can notes be pushed *wit
Hi Stefano,
> I just needed to state that this thread completely blew my mind.
I’ve become almost totally immune to Lilypond — the application and the
community — blowing my mind…
But even my jaw dropped a little because of this thread. =)
Cheers,
Kieren.
Kiere
Hi all,
Is there any technical reason this kind of thing shouldn’t be in the codebase,
with the end-goal to replace the current “Piano with centred dynamics”
template/mechanism with a \with-driven improvement?
If it’s simply ;) a matter of getting the code polished up and pushed through
the su
Hi Kira,
> I am also a new user
Nice to have you in the ’Pond!
> what draws me to Lilypond is the sheer aesthetics of it. Even the most basic
> thing created with Lilypond looks 1000 times more professional and attractive
> than MuseScore, in my opinion!
Oh, for sure. I have a choral octavo s
Hi Kieren,
Is there any technical reason this kind of thing shouldn’t be in the codebase,
with the end-goal to replace the current “Piano with centred dynamics”
template/mechanism with a \with-driven improvement?
If it’s simply ;) a matter of getting the code polished up and pushed through
t
Hello Kieren,
I guess the main problems are:
1) The user interface to this method is maybe not optimal. After all, this is
not a ready developed solution, but a quick test implementation. We do not
want to change the user interface if possible, as that breaks working scores.
So before pushing
Hi Valentin,
> 1) The user interface to this method is maybe not optimal. After all, this is
> not a ready developed solution, but a quick test implementation. We do not
> want to change the user interface if possible, as that breaks working scores.
> So before pushing such a thing to master we
Hi Lukas,
> based on my recent experience with \after, I think it might be reasonable to
> develop and test something like that outside of the regular codebase, in
> order to see how it fares in everyday heavy use.
For sure.
> (To be honest, it's not clear to me yet what you're describing.)
W
So. I have a piece with a few sections where there are two "voices" as
I understand things. And according to the manual, the solution, which
works fine is:
melody = {
\relative {
\global
\new Voice = "melody" {
\partial 4 bf4^\f | % 0
Hello everybody,
in one song in \key gf I have four consecutive g notes that become natural but
I don't know why the program puts again the natural sign in front of the second
note. Is it possible to hide the natural sign?
Thank you.
Mahanidhi
Hello Mahandihi,
It is possible to do that, e.g. By
\once\override Accidental.stencil = ##f
But it would be better to fix the underlying problem. Can you send us a small
example of when that happens? Are you perhaps using g! (thus forcing a natural
accidental)?
Cheers,
Valentin
Am Freitag, 29
Hi Kevin,
Am 29.10.21 um 20:17 schrieb Kevin Cole:
So. I have a piece with a few sections where there are two "voices" as
I understand things. And according to the manual, the solution, which
works fine is:
Could you please post a compilable example? (Preferably as short as
possible, but if a
It's a known bug. I think you can shorten your solution to:
\once \omit Accidental
--
Knute Snortum
On Fri, Oct 29, 2021 at 11:36 AM Valentin Petzel wrote:
>
> Hello Mahandihi,
>
> It is possible to do that, e.g. By
> \once\override Accidental.stencil = ##f
>
> But it would be better to fi
Hi Mahanidhi,
Am 29.10.21 um 20:24 schrieb Mahanidhi:
Hello everybody,
in one song in*\key gf *I have four consecutive g notes that become
natural but I don't know why the program puts again the natural sign
in front of the second note. Is it possible to hide the natural sign?
Please post a
Hello Josh,
I don’t know of a good way to get this, but it might be worth a specific
engraver. We might have some sort of instrument group name engraver that
properly handles such stuff. Maybe.
Cheers,
Valentin
Am Freitag, 29. Oktober 2021, 14:58:36 CEST schrieb josh:
> Hello. I have been tryi
Hello Kieren,
Using stylesheets is a powerful option in Lilypond. For example I’ve got a
cosmetic include that takes care of fonts and many small details, like paper
margins, offsetting ^\markup in Dynamics contexts to have them centered. Also
I have slightly heavier Beams (Lilypond’s Beams are
Hi Valentin,
> I’ve been thinking about maybe we should create a collection of high quality
> style sheets users can simply include to get really nice, different styles. I
> think that might open up the customizabilty of Lilypond Scores to new users.
If you search the archives, you’ll see that
Hi Lukas,
First, I'm using LilyPond v. 2.20.0. (I often seem to end up at 2.18
and 2.21 when searching for documentation -- though explicitly
changing the URL to 2.20 works.)
Second, I guess I'm not sure what you mean by a compatible example: I
thought that's what I provided. But the URL below is
On Fri, Oct 29, 2021 at 3:03 PM Kevin Cole wrote:
>
> Hi Lukas,
>
> First, I'm using LilyPond v. 2.20.0. (I often seem to end up at 2.18
> and 2.21 when searching for documentation -- though explicitly
> changing the URL to 2.20 works.)
>
> Second, I guess I'm not sure what you mean by a compatibl
Hi all,
> I don’t know of a good way to get this
There are a whole bunch of ways to clothe that particular cat… Here’s one:
%%% SNIPPET BEGINS %%%
\version "2.22.1"
\paper { indent = 1\in }
\layout {
\context {
\Score
\override InstrumentName.self-alignment-X = #RIGHT
Kevin,
You're encountering an known situation with polyphonic contexts like
this one. A change in 2.20.x modified how lyrics are calculated in these
polyphonic contexts. You need to manually add to the *lyrics* \skip1 to
position the lyrics where you want them. Like so:
words = \lyricm
Hi Kevin,
Am 29.10.21 um 21:03 schrieb Kevin Cole:
First, I'm using LilyPond v. 2.20.0. (I often seem to end up at 2.18
and 2.21 when searching for documentation -- though explicitly
changing the URL to 2.20 works.)
Yes, that's a bit of a nuisance.
Second, I guess I'm not sure what you mean by
On 10/29/21, 12:44 PM, "lilypond-user on behalf of Knute Snortum"
wrote:
It's a known bug. I think you can shorten your solution to:
\once \omit Accidental
Can you point me to the issue of the known bug?
I couldn't find it in my search.
Thanks,
Carl
On Fri, Oct 29, 2021 at 3:37 PM Guy Stalnaker wrote:
> Kevin,
>
> You're encountering an known situation with polyphonic contexts like this
> one. A change in 2.20.x modified how lyrics are calculated in these
> polyphonic contexts. You need to manually add to the *lyrics* \skip1 to
> position
Am 29.10.21 um 22:14 schrieb Guy Stalnaker:
Whoa! What is this magic you're doing Master Moser??
- I made sure that the bf4. on "days" stays in the voice called
melody. There are various ways to do this; I chose a "modern" way
using \voices and \\ inside << >> which allows to autom
Whoa! What is this magic you're doing Master Moser??
- I made sure that the bf4. on "days" stays in the voice called
melody. There are various ways to do this; I chose a "modern" way
using \voices and \\ inside << >> which allows to automatically add
a "second" voice
This is a techni
The problem sounds an awful lot like my problem in this thread:
https://lists.gnu.org/archive/html/lilypond-user/2021-08/msg00243.html
The issue is:
https://gitlab.com/lilypond/lilypond/-/issues/3466#note_344003849
--
Knute Snortum
On Fri, Oct 29, 2021 at 1:10 PM Carl Sorensen wrote:
>
>
>
p.s.
> This would mean that dynamics in either the \lower or \upper variables would
> be centred “automagically”, and pedal markings entered in the \lower variable
> would “automagically” appear below the staff — all without having to use
> extra \dynamics and \pedal variables (with all the req
I'll probably keep the \noBeam rather than the \autoBeamOff, since I'm
trying to faithfully reproduce the original, as much as I can.
Non sequitur (I think).
Consider:
\version "2.22"
\language "english"
\relative {
\time 3/4
\key d \major
d'8\noBeam d e16( fs) g8\noBeam a\noBeam fs
On Fri, Oct 29, 2021 at 3:51 PM Lukas-Fabian Moser wrote:
>
> Hi Kevin,
>
> Am 29.10.21 um 21:03 schrieb Kevin Cole:
> > First, I'm using LilyPond v. 2.20.0. (I often seem to end up at 2.18
> > and 2.21 when searching for documentation -- though explicitly
> > changing the URL to 2.20 works.)
> Ye
Again, much thanks. I would not have known this without your post. The
Documentation page you reference clearly shows use of the "older" type
of temporary polyphonic context and in the text explicitly mentions its
use for lyric continuation. Yet doing so does require the use of \skip1
in lyrics
On Fri, Oct 29, 2021 at 4:53 PM Lukas-Fabian Moser wrote:
> > I'll probably keep the \noBeam rather than the \autoBeamOff, since I'm
> > trying to faithfully reproduce the original, as much as I can.
> Non sequitur (I think).
>
> Consider:
>
> \version "2.22"
> \language "english"
>
> \relative
36 matches
Mail list logo
