On 31/01/2023 05:52, Rajesh Baskar wrote:
> Hello Experts,
>
> I'm facing a unique issue or it would be because of my limited knowledge of
> Lilypond. I have 2 identical Lilypond files, the only difference being that
> one has \omit Accidental in it. You can see in the mage attached that
>
Hello Experts,
I'm facing a unique issue or it would be because of my limited knowledge
of Lilypond. I have 2 identical Lilypond files, the only difference
being that one has \omit Accidental in it. You can see in the mage
attached that Lilypond generates them a bit differently. The line
On 30/01/2023 23:08, Ahanu Banerjee wrote:
> Perhaps the documentation could be amended to clarify how neutral direction
> is handled for slurs? There are two documentation pages here that mention
> slur orientation but don't describe the calculation that occurs in
> \slurNeutral:
>
Perhaps the documentation could be amended to clarify how neutral direction
is handled for slurs? There are two documentation pages here that mention
slur orientation but don't describe the calculation that occurs in
\slurNeutral:
Thanks Valentin and Federico for your suggestions and examples -
I needed to tweak things a little bit in order to line up the letters to
the tablature lines.
This is what I came up with:
\new TabStaff \with {
\override InstrumentName.self-alignment-X = #RIGHT
instrumentName = \markup
On 30/01/2023 22:26, Immanuel Asmus wrote:
> Hello Jean,
>
> actually, I /did/ subscribe. I wonder why my subscription was unsuccessful. I
> just tried again.
It didn't work this time either. I approved your message again.
Did you receive the confirmation email after filling the subscription
Hello Jean,
actually, I /did/ subscribe. I wonder why my subscription was
unsuccessful. I just tried again.
I finally found the cause of this error: It seems I checked only the
paper variables of my main document and Wetterlied.ly, whereas I didn’t
llok carefully into the other tqo source
Le lundi 30 janvier 2023 à 10:35 +0100, Jean Abou Samra a écrit :
>
>
> > Le 30 janv. 2023 à 09:26, Valentin Petzel a
> > écrit :
> >
> >
> > Hello Jean,
> >
> > This seems to come from PyQt5, so maybe downgrading that one will
> > solve this. Also you might want to report the problem
On Mon, Jan 30, 2023 at 9:34 AM Jean Abou Samra wrote:
> Hello Immanuel,
>
> Welcome to this list. For your information, I had to approve your message
> manually as a list administrator because you are not subscribed to the list
> yet. Please fix this by subscribing on
>
Dear Immanuel,
Sorry, I’m having trouble finding what would be the problem from the
provided snippets. Could you please reduce the files to a minimum
working example that we can compile that reproduces the problem? This
might help find what is the problem. In my experience when this kind of
Hello Immanuel,
Welcome to this list. For your information, I had to approve your message
manually as a list administrator because you are not subscribed to the list
yet. Please fix this by subscribing on
https://lists.gnu.org/mailman/listinfo/lilypond-user (note that once
subscribed, you can
Dear community,
I’ve been using lilypond for a fair amount of time, and even though I
sometimes use non-standard notation, I’ve never had any problem finding
a solution. Until now.
It’s my first time typesetting a song cycle I wrote. I want (as what I
understand is recommended) to typeset
Considering the commit in question
https://gitlab.com/lilypond/lilypond/-/commit/f75fe46f1727ea0d28840781b0db54474c61442d[1]
is 12 years old I do not believe anything has changed too recently :)
The earliest Lilypond version I’ve started with was 2.18, and I do not remember
if this at some time
> I've always terminated my cresc/decres with \!
> I found that in the docs a while ago, but is that still the case?
>
> e1\< | a2\!\ff b2
>
> Is the way I'd have done it.
AFAIK, this has never worked. If `\!` and `\ff` are at the same
moment, `\!` gets ignored.
Note that
I've always terminated my cresc/decres with \!
I found that in the docs a while ago, but is that still the case?
e1\< | a2\!\ff b2
Is the way I'd have done it.
On Mon, Jan 30, 2023, 6:41 AM Jean Abou Samra wrote:
> On 30/01/2023 12:38, Werner LEMBERG wrote:
> >
> > What is the 'official'
On 2023-01-30 13:04, Wols Lists wrote:
A
quick search tells me the violin plays in the treble clef, which I
doubt is what you mean?
I'm guessing the violin clef is one of the C clefs, but which one?
I know Tenor and Alto.
On 2023-01-30 10:43, Lukas-Fabian Moser
wrote:
By the way, there
also
exists the opposite: In (older?) scores of symphonies by Anton
Bruckner, the violoncello part, if using the violin clef, is
notated
On 30/01/2023 12:37, Werner LEMBERG wrote:
Strange transposition rules also exist for horns, where in the
violin clef you transpose down, and in the bass clef you transpose
up.
Violin clef?
Sorry, bad translation from German: I meant horn parts notated with a
treble clef.
That's fine :-)
>> Strange transposition rules also exist for horns, where in the
>> violin clef you transpose down, and in the bass clef you transpose
>> up.
>
> Violin clef?
Sorry, bad translation from German: I meant horn parts notated with a
treble clef.
Werner
On 29/01/2023 20:39, Werner LEMBERG wrote:
Strange transposition rules also exist for horns, where in the violin
clef you transpose down, and in the bass clef you transpose up.
Violin clef?
A quick search tells me the violin plays in the treble clef, which I
doubt is what you mean?
I'm
>> What is the 'official' way to break the alignment between, say, a
>> crescendo wedge and a subsequent forte sign? What I want is
>> automatic placement of the 'f' by LilyPond as if there were no
>> crescendo wedge.
>
> \version "2.24.0"
>
> {
> e1\< | g''1\breakDynamicSpan\ff |
> }
Aah,
>> But the user shouldn't see an assertion error even in case of a wrong
>> argument, right?
>
> Yeah,
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1828
Thanks!
Werner
On 30/01/2023 12:38, Werner LEMBERG wrote:
>
> What is the 'official' way to break the alignment between, say, a
> crescendo wedge and a subsequent forte sign? What I want is automatic
> placement of the 'f' by LilyPond as if there were no crescendo wedge.
>
> ```
> {
> e1\< | g''1\ff |
> }
>
What is the 'official' way to break the alignment between, say, a
crescendo wedge and a subsequent forte sign? What I want is automatic
placement of the 'f' by LilyPond as if there were no crescendo wedge.
```
{
e1\< | g''1\ff |
}
```
Werner
On 30/01/2023 08:19, Werner LEMBERG wrote:
>
>>> When I attempt to change the "direction" property of a slur,
>>> whether that is with \tweak or \override, I cannot set the
>>> direction to neutral (0). UP (1) and DOWN (-1) work fine, but when
>>> setting to 0, I get the following error:
>>>
>>>
By the way, there also
exists the opposite: In (older?) scores of symphonies by Anton
Bruckner, the violoncello part, if using the violin clef, is notated
one octave higher than sounding.
This is also common in Dvorak, for example. Strauss-Berlioz describe a
precise rule for this (according
> Le 30 janv. 2023 à 09:26, Valentin Petzel a écrit :
>
>
> Hello Jean,
>
> This seems to come from PyQt5, so maybe downgrading that one will solve this.
> Also you might want to report the problem directly to Frescobaldi:
>
> https://github.com/frescobaldi/frescobaldi/issues
>
> so it
Better to give all the versions and platforms.
Andrew
On 30/01/2023 6:20 pm, Jean Bréfort wrote:
Since a python upgrade, Frescobaldi has a serious issue:
Hello Jean,
This seems to come from PyQt5, so maybe downgrading that one will solve this.
Also you
might want to report the problem directly to Frescobaldi:
https://github.com/frescobaldi/frescobaldi/issues[1]
so it can be fixed.
Cheers,
Valentin
Am Montag, 30. Jänner 2023, 08:20:10 CET
It think the problem here is not that the error happens, but that the error
message is absolutely unusable for a user.
If the error message was somthing like "direction must not be 0" it would be
much clearer for the user.
Still maybe this should be handled before passing this to the drul
Thank you, Werner!
On Sun, Jan 29, 2023 at 11:17 PM Werner LEMBERG wrote:
>
>
> > The "R.H." instruction with 45 degree slope down and up from treble
> > to bass clef: How?
>
> Look up 'staff-change lines' in the Notation Reference index to get
> details on the `\showStaffSwitch` command.
>
>
>
31 matches
Mail list logo
