Re: removing time signatures engravers locally
I was finally able to get my real code to function as your example does.
Thank you very much,
Paul
On 3/5/23 11:29 AM, Jean Abou Samra wrote:
Le dimanche 05 mars 2023 à 11:19 -0700, Paul Scott a écrit :
Thank you for your quick reply.
I need/the first situation of NR 1.2.3: "Different time signatures
with equal-length measures." enablePolymeter defeats this./
/
/
Some instruments have all 2/4; some have 2/4, then 6/8 and then 2/4
again.
Well, this is where you see the point of giving a code example. I
still cannot reproduce your problem.
\version "2.25.2"
<<
\new Staff {
\time 2/4
c'8 8 8 8 8 8 8 8
c'8 8 8 8 8 8 8 8
c'8 8 8 8 8 8 8 8
}
\new Staff {
\time 2/4
c'8 8 8 8 8 8 8 8
\set Staff.timeSignatureFraction = 6/8
\scaleDurations 2/3 { c'8 8 8 8 8 8 8 8 8 8 8 8 }
\set Staff.timeSignatureFraction = 2/4
c'8 8 8 8 8 8 8 8
}
>>
For me, this gives
Jean
Re: Discourse proposal status
Andrew Bernard writes: > Well you can dynamically increase CPU or RAM or both on Digitalocean > that I use. You can do it on a temporary basis - but I'm not sure if > you get charged for a month or on a strict time basis, it's hard to > find out!. It's not a matter of needing a separate system. My only > issue is that I am very financially constrained and I can't afford the > experiment. > > But the bigger fish to fry is the issue with the irregularities in the > mbox archives. I need to study this in depth before trying a load. I > did have the same problem with similar erratic mbox archives quite > some years ago but I can't easily recall the solution. Probably just a > more refined regex to pick up the 'From:' delimiters. There isn't really much finesse involved. Messages start at the pattern "^From ". Any "From " inside of a message that would end up at the start of a line is changed to ">From ", so the pattern "^From " should be foolproof regarding splitting into messages. I don't remember what happens to "^>From " but consider it most likely that any "^>*From " inside of a message gets one ">" prepended when put into an mbox file, and one taken out again when displayed/processed. -- David Kastrup
Re: Discourse proposal status
Well you can dynamically increase CPU or RAM or both on Digitalocean that I use. You can do it on a temporary basis - but I'm not sure if you get charged for a month or on a strict time basis, it's hard to find out!. It's not a matter of needing a separate system. My only issue is that I am very financially constrained and I can't afford the experiment. But the bigger fish to fry is the issue with the irregularities in the mbox archives. I need to study this in depth before trying a load. I did have the same problem with similar erratic mbox archives quite some years ago but I can't easily recall the solution. Probably just a more refined regex to pick up the 'From:' delimiters. Andrew On 6/03/2023 1:52 pm, David Kastrup wrote: Is it necessary to run the import on the same machine that is going to run the server?
Re: Discourse proposal status
Andrew Bernard writes: > I should add that a normal fresh install does not require large > RAM. It's only the mbox import script. I think it's poorly written and > does not constrain itself when it comes to memory. Is it necessary to run the import on the same machine that is going to run the server? -- David Kastrup
Re: Discourse proposal status
I should add that a normal fresh install does not require large RAM. It's only the mbox import script. I think it's poorly written and does not constrain itself when it comes to memory. Andrew On 6/03/2023 1:29 pm, Andrew Bernard wrote: On 6/03/2023 3:04 am, Valentin Petzel wrote: I suppose a system that requires by a large factor more resources for installation that it requires to run is not really a good way to do it.
Re: Discourse proposal status
No. You misunderstand. Discourse is quite compact. The 8GB of RAM is only required temporarily for importing 20+ years worth of mbox files. My Discourse servers all run fine in 2GB of RAM, with unlimited posts, which are just in a database on disk. On 6/03/2023 3:04 am, Valentin Petzel wrote: I suppose a system that requires by a large factor more resources for installation that it requires to run is not really a good way to do it.
Re: vertical placement of trillspan and upbow
Thanks! On Sun, Mar 5, 2023 at 1:47 PM Jean Abou Samra wrote: > Le dimanche 05 mars 2023 à 13:43 -0500, Mark Mathias a écrit : > > My guess as to why the script-priority isn't a solution is that it decides > between competing scripts and the trill spanner isn't a script. Whereas > outside-staff-priority evaluates competing values of all objects of > whatever type outside the staff. Hopefully someone will correct me if my > understanding is foggy. > > Yes, that sounds correct. >
Re: vertical placement of trillspan and upbow
Le dimanche 05 mars 2023 à 13:43 -0500, Mark Mathias a écrit : > My guess as to why the script-priority isn't a solution is that it decides > between competing scripts and the trill spanner isn't a script. Whereas > outside-staff-priority evaluates competing values of all objects of whatever > type outside the staff. Hopefully someone will correct me if my understanding > is foggy. Yes, that sounds correct. signature.asc Description: This is a digitally signed message part
Re: vertical placement of trillspan and upbow
As I might have guessed, Jean's solution is even easier! Also, I presumed
you wanted the trill to extend through the upbow to the acciaccatura, but
that was probably not what you wanted.
My guess as to why the script-priority isn't a solution is that it decides
between competing scripts and the trill spanner isn't a script. Whereas
outside-staff-priority evaluates competing values of all objects of
whatever type outside the staff. Hopefully someone will correct me if my
understanding is foggy.
Thanks,
Mark
On Sun, Mar 5, 2023 at 1:05 PM Jean Abou Samra wrote:
> Le dimanche 05 mars 2023 à 15:56 +0100, Arjen a écrit :
>
> Hello,
>
> I am trying to switch the vertical stacking order of the upbow symbol and
> the trillspan in the following fragment by overriding the script-priority
> of the upbow symbol.
> The upbow symbol should be the topmost.
>
> \version "2.22.1"
> \relative a'' {
> g1\startTrillSpan ( ~
> \once \override Script.script-priority = #1000
> g2\upbow\stopTrillSpan ~ \acciaccatura fis8 g8 e8)
> }
>
>
> I tried replacing "Script" with "TextScript", but it did not work either.
> And I tried overriding TrillSpanner.script-priority to -1000 (placing it
> before the g1), which also didn't work.
>
> Can someone please be so kind to explain how to accomplish this?
>
>
>
>
> What about just using a more up-to-date LilyPond version?
>
> In 2.24, trill spanners stop before the ending note (as is best practice),
> so you don't need to tweak anything, as your code gives
>
>
> Jean
>
>
>
Re: removing time signatures engravers locally
Le dimanche 05 mars 2023 à 11:19 -0700, Paul Scott a écrit :
> Thank you for your quick reply.
>
> I need the first situation of NR 1.2.3: "Different time signatures
> with equal-length measures." enablePolymeter defeats this.
>
> Some instruments have all 2/4; some have 2/4, then 6/8 and then 2/4
> again.
Well, this is where you see the point of giving a code example. I still
cannot reproduce your problem.
\version "2.25.2"
<<
\new Staff {
\time 2/4
c'8 8 8 8 8 8 8 8
c'8 8 8 8 8 8 8 8
c'8 8 8 8 8 8 8 8
}
\new Staff {
\time 2/4
c'8 8 8 8 8 8 8 8
\set Staff.timeSignatureFraction = 6/8
\scaleDurations 2/3 { c'8 8 8 8 8 8 8 8 8 8 8 8 }
\set Staff.timeSignatureFraction = 2/4
c'8 8 8 8 8 8 8 8
}
>>
For me, this gives
Jean
signature.asc
Description: This is a digitally signed message part
Re: removing time signatures engravers locally
Thank you for your quick reply.
I need/the first situation of NR 1.2.3: "Different time signatures with
equal-length measures." enablePolymeter defeats this./
/
/
Some instruments have all 2/4; some have 2/4, then 6/8 and then 2/4 again.
/
/
Paul
/
/
On 3/5/23 10:41 AM, Jean Abou Samra wrote:
Le dimanche 05 mars 2023 à 10:17 -0700, Paul Scott a écrit :
2.25.2:
I understand polymetric notation (NR 1,2,3). I have a piece which has a
polymetric section in the middle where the rest of the piece is not
polymetric. Some parts have the same time signature for the whole piece.
At the point where the polymetric section begins and ends I want to
remove the time signature from the parts whose time signature doesn't
change.
TIA for any help with this including Lilypond manual references if
relevant.
I don't quite understand the question since this is pretty much what
happens by default.
|\version "2.25.2" \layout { \enablePolymeter } filler = { c'4 4 4 4 4
4 } << \new Staff { \time 3/4 \filler \time 2/4 \filler \time 3/4
\filler } \new Staff { \time 3/4 \filler \filler \filler } >> |
What am I missing?
/
/
Re: vertical placement of trillspan and upbow
Le dimanche 05 mars 2023 à 15:56 +0100, Arjen a écrit :
> Hello,
>
> I am trying to switch the vertical stacking order of the upbow symbol
> and the trillspan in the following fragment by overriding the script-
> priority of the upbow symbol.
> The upbow symbol should be the topmost.
>
> \version "2.22.1"
> \relative a'' {
> g1\startTrillSpan ( ~
> \once \override Script.script-priority = #1000
> g2\upbow\stopTrillSpan ~ \acciaccatura fis8 g8 e8)
> }
>
>
> I tried replacing "Script" with "TextScript", but it did not work
> either.
> And I tried overriding TrillSpanner.script-priority to -1000 (placing
> it before the g1), which also didn't work.
>
> Can someone please be so kind to explain how to accomplish this?
What about just using a more up-to-date LilyPond version?
In 2.24, trill spanners stop before the ending note (as is best
practice), so you don't need to tweak anything, as your code gives
Jean
signature.asc
Description: This is a digitally signed message part
Re: vertical placement of trillspan and upbow
On Sun, Mar 5, 2023 at 9:56 AM Arjen wrote:
> Hello,
>
> I am trying to switch the vertical stacking order of the upbow symbol and
> the trillspan in the following fragment by overriding the script-priority
> of the upbow symbol.
> The upbow symbol should be the topmost.
>
> \version "2.22.1"
> \relative a'' {
> g1\startTrillSpan ( ~
> \once \override Script.script-priority = #1000
> g2\upbow\stopTrillSpan ~ \acciaccatura fis8 g8 e8)
> }
>
>
>
> I tried replacing "Script" with "TextScript", but it did not work either.
> And I tried overriding TrillSpanner.script-priority to -1000 (placing it
> before the g1), which also didn't work.
>
> Can someone please be so kind to explain how to accomplish this?
>
> Regards,
> Arjen
>
Try using outside-staff-priority instead. Also, I moved your
\stopTrillSpanner over so it extends underneath the upbow.
\version "2.22.1"
\relative a'' {
g1\startTrillSpan ( ~
\once \override Script.outside-staff-priority = #1000
g2\upbow ~ \acciaccatura fis8\stopTrillSpan g8 e8)
}
Someone else will have to explain why script-priority hasn't any effect.
That would enlighten both of us.
Hope This Helps!
Mark
Re: removing time signatures engravers locally
Le dimanche 05 mars 2023 à 10:17 -0700, Paul Scott a écrit :
> 2.25.2:
>
> I understand polymetric notation (NR 1,2,3). I have a piece which has a
> polymetric section in the middle where the rest of the piece is not
> polymetric. Some parts have the same time signature for the whole piece.
>
> At the point where the polymetric section begins and ends I want to
> remove the time signature from the parts whose time signature doesn't
> change.
>
> TIA for any help with this including Lilypond manual references if relevant.
I don't quite understand the question since this is pretty much what happens by
default.
```
\version "2.25.2"
\layout {
\enablePolymeter
}
filler = { c'4 4 4 4 4 4 }
<<
\new Staff { \time 3/4 \filler \time 2/4 \filler \time 3/4 \filler }
\new Staff { \time 3/4 \filler \filler \filler }
>>
```
What am I missing?
signature.asc
Description: This is a digitally signed message part
removing time signatures engravers locally
2.25.2: I understand polymetric notation (NR 1,2,3). I have a piece which has a polymetric section in the middle where the rest of the piece is not polymetric. Some parts have the same time signature for the whole piece. At the point where the polymetric section begins and ends I want to remove the time signature from the parts whose time signature doesn't change. TIA for any help with this including Lilypond manual references if relevant. Paul
Re: Discourse proposal status
Hello Andrew, I suppose a system that requires by a large factor more resources for installation that it requires to run is not really a good way to do it. Renting an 8GB Server when you only need that 8GB for setup sounds a bit daft. I do not know if renting a server dedicated to managing a handful of messages per day is really a good use of resources. In my opinion the best way would be to have Lilypond use a small share of the resources of a company or communiy stable enough to grant that the system will be around some time. This is exactly what is currently done by GNU infastructure. Renting a dedicated server would really only make sense if we had a handful of web services that really make use of these resources. Such a server might also be used for example to host something like Paolo’s Spontini editor. I mean, sure, it wouldn’t cost much individually if a few of us rented a Server together, but I think if we do something like this we should make full use of that server. Cheers, Valentin Am Sonntag, 5. März 2023, 06:04:40 CET schrieb Andrew Bernard: > I'm still keen on Discourse for our community and have been giving it > some attention. People have right;y said the full historical archive is > important. David Kastrup usefully pointed out all the mbox archives are > freely available, back to the beginning. Discourse can import mbox > archives and there is a special import instance with scripts to load them. > > So I downloaded the complete set of archives and attempted to load them > into Discourse. One problem that arose is that the documentation for the > import script explicitly mentions that you need a system with 8GB of RAM > (only for the import, not for normal running) and my linux servers are > only configured with 2GB. Consequently the import fails. I use Vultr and > Digitalocean and unfortunately upping the specification to 8GB plus is > too expensive for me in my situation. Servers with extra RAM get > expensive very quickly at these companies. So this is a problem. I am > working towards a solution to work around this, perhaps doing it on my > home server and uploading to a 2GB server later (but there are > complexities with this). > > But, the next current issue is this, and I have come across this before > when importing mbox archives into GNU Mailman 2 and 3. The mbox format > is rather loosely defined, and there are lots of small variations. But > worse, even when you look at our archive set the format seems to vary > slightly over the years. Some messages don't get unpacked properly due > to inconsistencies in headers and my import of a sizeable batch showed > quite a few messages with the initial message fine, but then follow up > replies just appended in raw mailbox format rather than separate > messages. I'll have to study this in more depth and write some scripts > to pre-process the mbox files. Tedious, but I've had to do this in the past. > > If I can load the whole history, then people can have a play with it to > see if they like it. I also think I can get the Discourse instance to be > a subscriber to the present list so ti would keep up to date. Of course, > if people replied on the Discourse interface the lists would diverge, > but this is just for proopf of concept. > > As to operational matters, there is cost involved by going outside the > GNU infrastructure. An adequate server costs around USD$20 per month to > run. The way I handle this in the communities that I support is to ask > for donations. Generally if a moderate number of people chip in it can > be the cost of a cup of coffee a month. It's not excessive. > > I think there have been some comments here indicating some > dissatisfaction with this aging and somewhat limited email > infrastructure, so I am encouraged to setup my proof of concept to > demonstrate a modern system. I am also compelled to say that in > practical terms the email list functionality of Discourse from the end > user point of view is identical to what we have now with GNU Mailman 2, > and you'd be hard pressed to find any operational/functional difference. > So for people who reject web interfaces, in effect very little would change. > > Finally, I'd just mention that Discourse of course supports plain text, > but also HTML, and has full support for Markdown, both from email > initiated files and web initiated topics. This means you can do nice > formatting if required, and in particular you can make clear tables. And > as with most forums now, you can mark code blocks so that they stand out > clearly. > > I'll post regular updates as I make progress towards a full proof of > concept for people. And of course, if this was Discourse these posts > would be in a distinct and separate category so as not to be noise in > the main flow of the stream. :-) > > Andrew signature.asc Description: This is a digitally signed message part.
vertical placement of trillspan and upbow
Hello,
I am trying to switch the vertical stacking order of the upbow symbol
and the trillspan in the following fragment by overriding the
script-priority of the upbow symbol.
The upbow symbol should be the topmost.
\version "2.22.1"
\relative a'' {
g1\startTrillSpan ( ~
\once \override Script.script-priority = #1000
g2\upbow\stopTrillSpan ~ \acciaccatura fis8 g8 e8)
}
I tried replacing "Script" with "TextScript", but it did not work either.
And I tried overriding TrillSpanner.script-priority to -1000 (placing it
before the g1), which also didn't work.
Can someone please be so kind to explain how to accomplish this?
Regards,
Arjen
Re: Message size limit
It was a joke. Andrew On 6/03/2023 12:43 am, David Kastrup wrote: I don't really see how "schadenfreude" scales to the problem space.
Re: Message size limit
Andrew Bernard writes: > Hello All, > > I can't help feeling a twinge of schadenfreude on hearing this. :-) > > Although one can impose such restrictions in Discourse, you don't have > to unless you are constrained by organisational problems as here with > GNU. Do you really think that the number of mailing lists supported by the GNU mailing list server could be supported on the same hardware by the same number of Discourse forums? I don't really see how "schadenfreude" scales to the problem space. -- David Kastrup
Re: removing `--show-rules` option of `convert-ly`?
On 2023-03-04 19:15, Werner LEMBERG wrote: who has ever used option `--show-rules` of `convert-ly`, except for being curious what this option does? In https://gitlab.com/lilypond/lilypond/-/merge_requests/1854 we are discussing whether it would make sense to remove it. I've definitely used it a number of times over the years, [...] Regarding the discussion in the merge request, I don't see any reason to translate these messages. I wouldn't expect a lot of users who use the feature and don't know English sufficiently well to be able to decipher what it's about, especially since the Lilypond syntax itself is language independent. I agree, thus suggesting the following: * Remove translation marks (will soon push this to the above merge request). * Replace `--show-rules` with a more common `--verbose` option to show rule descriptions while `convert-ly` is running. Right now, `--show-rules` only emits the rules but doesn't do a conversion at the same time, which is rather useless IMHO. Not sure whether my Python abilities are good enough to implement this feature; anyway, this will be a separate merge request. Werner I don't fully agree with your second item. In the use cases I described, I have used "convert-ly -s" without any input file, to see the list of changes, so please keep a possibility to easily list the rules without an input file. /Mats
Re: Message size limit
At 15:28 on 05 Mar 2023, Andrew Bernard wrote: > Hello All, > I can't help feeling a twinge of schadenfreude on hearing this. :-) > Although one can impose such restrictions in Discourse, you don't have > to unless you are constrained by organisational problems as here with > GNU. As to my suggestion about implementing Discourse, I'd be > proposing running it on a dedicated linux server at one of the hosting > providers, well clear of GNU infrastructure and limitations. Discourse > also handles attachments and images very well, both in the web > interface and in the email interface, no problems, and you can set > maximum size allowed with ease to whatever your system can handle in > terms of disk space. Whilst the discussion regarding Discourse emerged from a general thread about the mailing list infrastructure, I think it's unfair to score this as a point against the current Mailman/GNU setup. We are currently benefiting from the GNU project's provision of disk space and bandwidth for the mailing lists - and indeed have "set maximum size allowed with ease" on this occasion to avoid wasting that provision. As you say in your next email regarding Discourse, that itself would rely on user donations to fund it - it seems likely that a similar maximum size limit would be set. -- Mark Knoop
