Re: 48 and 72 ET

Graham Breed writes: > It's unfortunate that my library is out of date. It's good that > convert-ly fixes it. One issue with this is that libraries (at least > the way I use them, which may also be out of date) don't declare the > Lilypond version. It's in the including

Re: 48 and 72 ET

Simon Albrecht writes: > On 10.02.2017 00:19, Hans Åberg wrote: >> If LilyPond knows how to run the code via convert-ly, why does it not do it? > > LilyPond itself doesn’t change the code it is reading. convert-ly is a > separate Python script. > It might be a valid

Re: 48 and 72 ET

I'm answering the whole thread here. You should be able to do 48 ET with the standard Lilypond font. You can, for example, start with 12 ET and add arrowed accidentals to get 12*3=36. Then add 12 quartertones to get 48 ET. All you need is to define new note names. I found the font wasn't

long `instrument' names in frenched scores

In vocal scores it is common that singer parts that were omitted for some sytems are introduced again with its full name – not written in front of the system but at the beginning of the line. Do we have support for this feature already? Werner

Re: New LilyPond website

+ 1 to include lilybin not just a link but include the ability to try lilypond directly from the browser without having to open another window. Like the Haskell or like the ruby lang website ( https://www.ruby-lang.org/en/ see the link on the right "Try Ruby") . 2 user stories 1. a ) as a

Re: 48 and 72 ET

On 09/02/2017 17:22, Hans Åberg wrote: > 1. > https://secure2.storegate.com/Shares/Home.aspx?ShareID=35e0b920-6910-4e4f-8340-7d8290115dda > > thank you! ___ lilypond-user mailing list lilypond-user@gnu.org

Re: New LilyPond website

> > in total. After enabling scripts this problem vanishes. > > In Vivaldi I don't see the background image at the top of the page at all. > I test using all major browsers including Vivaldi (my main browser) and I am not getting any of these issues. -- John Roper Freelance Developer and

Re: New LilyPond website

> Ok, I changed the image to something that made more sense. What do you > guys think about everything else? I've looked at it with current versions of Firefox and Vivaldi: On Firefox without allowing scripts all the boxes "Download 2.18.2", "Release Notes" at the top are partly overlapping and

Re: 48 and 72 ET

On 10.02.2017 00:19, Hans Åberg wrote: If LilyPond knows how to run the code via convert-ly, why does it not do it? LilyPond itself doesn’t change the code it is reading. convert-ly is a separate Python script. It might be a valid feature request, though, to have a command-line option which

Re: New LilyPond website

On 09.02.2017 23:50, u...@openlilylib.org wrote: Urs Best user that and why for this page to be viewed JavaScript has to be switched on. requires JavaScript but has a decent option, telling the What I can imagine would work well is that a given "Try it out" page for the website to work

Re: 48 and 72 ET

On Fri, 10 Feb 2017, David Kastrup wrote: > enthused. Why wouldn't we want to have best practices pointed out and > promoted on the user list? Best practices do not include attacking other list users. -- Matthew Skala msk...@ansuz.sooke.bc.ca People before principles.

Re: 48 and 72 ET

Hans Åberg writes: >> On 10 Feb 2017, at 00:16, David Kastrup wrote: >> >> So is there any reason people don't use convert-ly when upgrading to >> a newer version? > > For libraries, you would want to keep track of the changes, but > running convert-ly and do

Re: 48 and 72 ET

Am 10.02.2017 um 00:22 schrieb Hans Åberg: >> So is there any reason people don't use convert-ly when upgrading to a >> newer version? > For libraries, you would want to keep track of the changes, but running > convert-ly and do a diff is a good suggestion. Though doing it by hand was >

Re: 48 and 72 ET

msk...@ansuz.sooke.bc.ca writes: > On Thu, 9 Feb 2017, David Kastrup wrote: >> I'll stick with my "that doesn't even make sense" verdict, thank you >> very much. > > Don't ask the question if you're going to attack the answer. When I ask for a reason why one would _not_ use documented best

Re: 48 and 72 ET

> On 10 Feb 2017, at 00:16, David Kastrup wrote: > > Hans Åberg writes: > >>> On 9 Feb 2017, at 23:53, David Kastrup wrote: >>> >>> Hans Åberg writes: >>> > On 9 Feb 2017, at 23:44, David Kastrup wrote:

Re: 48 and 72 ET

> On 10 Feb 2017, at 00:05, msk...@ansuz.sooke.bc.ca wrote: > > On Thu, 9 Feb 2017, David Kastrup wrote: >> I'll stick with my "that doesn't even make sense" verdict, thank you >> very much. > > Don't ask the question if you're going to attack the answer. Your > contributions to LilyPond

Re: 48 and 72 ET

Hans Åberg writes: >> On 9 Feb 2017, at 23:53, David Kastrup wrote: >> >> Hans Åberg writes: >> On 9 Feb 2017, at 23:44, David Kastrup wrote: Hans Åberg writes: >> On 9 Feb

Re: 48 and 72 ET

On Thu, 9 Feb 2017, David Kastrup wrote: > I'll stick with my "that doesn't even make sense" verdict, thank you > very much. Don't ask the question if you're going to attack the answer. Your contributions to LilyPond development don't excuse you from practicing basic civility. -- Matthew Skala

Re: 48 and 72 ET

> On 9 Feb 2017, at 23:53, David Kastrup wrote: > > Hans Åberg writes: > >>> On 9 Feb 2017, at 23:44, David Kastrup wrote: >>> >>> Hans Åberg writes: >>> > On 9 Feb 2017, at 23:24, David Kastrup wrote:

Re: 48 and 72 ET

Hans Åberg writes: >> On 9 Feb 2017, at 23:44, David Kastrup wrote: >> >> Hans Åberg writes: >> On 9 Feb 2017, at 23:24, David Kastrup wrote: Hans Åberg writes: >> On 9 Feb

Re: 48 and 72 ET

> On 9 Feb 2017, at 23:44, David Kastrup wrote: > > Hans Åberg writes: > >>> On 9 Feb 2017, at 23:24, David Kastrup wrote: >>> >>> Hans Åberg writes: >>> > On 9 Feb 2017, at 23:10, David Kastrup wrote:

Re: 48 and 72 ET

Hans Åberg writes: >> On 9 Feb 2017, at 23:24, David Kastrup wrote: >> >> Hans Åberg writes: >> On 9 Feb 2017, at 23:10, David Kastrup wrote: Hans Åberg writes: >> On 9 Feb

Re: New LilyPond website

On Thu, Feb 09, 2017 at 05:34:38PM -0500, John Roper wrote: >Sadly the community does not want JavaScript to be used because >most of the users don't like using it. I had that idea already but >did not bring it up. I would love to though. > >On Feb 9, 2017 5:12 PM, "Bernardo

Re: New LilyPond website

On 09/02/2017 17:34, John Roper wrote: > Sadly the community does not want JavaScript to be used because most > of the users don't like using it. I had that idea already but did > not bring it up. I would love to though. I think as long as the website has a fallback option without js, and js

Re: 48 and 72 ET

> On 9 Feb 2017, at 23:24, David Kastrup wrote: > > Hans Åberg writes: > >>> On 9 Feb 2017, at 23:10, David Kastrup wrote: >>> >>> Hans Åberg writes: >>> > On 9 Feb 2017, at 22:47, Cole Ingraham

Re: New LilyPond website

Sadly the community does not want JavaScript to be used because most of the users don't like using it. I had that idea already but did not bring it up. I would love to though. On Feb 9, 2017 5:12 PM, "Bernardo Barros" wrote: > lilybin.com could be included into the

Re: 48 and 72 ET

Hans Åberg writes: >> On 9 Feb 2017, at 23:10, David Kastrup wrote: >> >> Hans Åberg writes: >> On 9 Feb 2017, at 22:47, Cole Ingraham wrote: I've used Sagittal notation based on

Re: 48 and 72 ET

> On 9 Feb 2017, at 23:13, Bernardo Barros wrote: > > On 09/02/2017 16:46, Hans Åberg wrote: >> Yes, I have. I use it for E53 Helmholtz-Ellis notation, which >> requires the Bravura font... > > Have you publish this code somewhere? I just put it up at [1]. You need to

Re: 48 and 72 ET

On 09/02/2017 16:46, Hans Åberg wrote: > Yes, I have. I use it for E53 Helmholtz-Ellis notation, which > requires the Bravura font... Have you publish this code somewhere? ___ lilypond-user mailing list lilypond-user@gnu.org

Re: 48 and 72 ET

Hans Åberg writes: >> On 9 Feb 2017, at 22:47, Cole Ingraham wrote: >> >> I've used Sagittal notation based on http://x31eq.com/lilypond/ >> before. I don't know if that still works with more recent versions >> though. Haven't touched it in a while.

Re: 48 and 72 ET

> On 9 Feb 2017, at 23:10, David Kastrup wrote: > > Hans Åberg writes: > >>> On 9 Feb 2017, at 22:47, Cole Ingraham wrote: >>> >>> I've used Sagittal notation based on http://x31eq.com/lilypond/ >>> before. I don't know if that

Re: New LilyPond website

lilybin.com could be included into the official website as part of its new design. Something like "Try it - Type Haskell expressions in here" in Haskell website https://www.haskell.org/ ___ lilypond-user mailing list lilypond-user@gnu.org

Re: 48 and 72 ET

> On 9 Feb 2017, at 23:00, Hans Åberg wrote: > > >> On 9 Feb 2017, at 22:47, Cole Ingraham wrote: >> >> I've used Sagittal notation based on http://x31eq.com/lilypond/ before. I >> don't know if that still works with more recent versions though.

Re: 48 and 72 ET

> On 9 Feb 2017, at 22:47, Cole Ingraham wrote: > > I've used Sagittal notation based on http://x31eq.com/lilypond/ before. I > don't know if that still works with more recent versions though. Haven't > touched it in a while. I get an error in LilyPond 2.19.45, with

Re: 48 and 72 ET

> On 9 Feb 2017, at 22:47, Bernardo Barros wrote: > > On 09/02/2017 16:29, Bernardo Barros wrote: >> It indeed looks like LilyPond default font doesn't have all the >> necessary glyphs. > > You're right, SMuFL implements Sims’s accidental system for 72-ET, and >

Re: 48 and 72 ET

> On 9 Feb 2017, at 22:47, Cole Ingraham wrote: > > I've used Sagittal notation based on http://x31eq.com/lilypond/ before. I > don't know if that still works with more recent versions though. Haven't > touched it in a while. I was able to tweak regular.ly so it

Re: 48 and 72 ET

I've used Sagittal notation based on http://x31eq.com/lilypond/ before. I don't know if that still works with more recent versions though. Haven't touched it in a while. -Cole On Thu, Feb 9, 2017 at 4:29 PM, Bernardo Barros wrote: > On 09/02/2017 14:59, Hans Åberg

Re: 48 and 72 ET

On 09/02/2017 16:29, Bernardo Barros wrote: > It indeed looks like LilyPond default font doesn't have all the > necessary glyphs. You're right, SMuFL implements Sims’s accidental system for 72-ET, and "Extended Stein-Zimmermann" which could be used for 48-ET.

Re: 48 and 72 ET

> On 9 Feb 2017, at 22:29, Bernardo Barros wrote: > > On 09/02/2017 14:59, Hans Åberg wrote: >> Multiples of 12 are straightforward, though LilyPond glyphs are >> limited. For other ETs, use Graham Breed's regular.ly. More glyphs >> can be gotten using SMuFL.org with

Re: 48 and 72 ET

On 09/02/2017 14:59, Hans Åberg wrote: > Multiples of 12 are straightforward, though LilyPond glyphs are > limited. For other ETs, use Graham Breed's regular.ly. More glyphs > can be gotten using SMuFL.org with OpenLilyPond. Thank you for your reply, Hans Yes, it looks like all the tools are

Re: 48 and 72 ET

> On 9 Feb 2017, at 22:18, Simon Albrecht wrote: > > On 09.02.2017 20:59, Hans Åberg wrote: >> Multiples of 12 are straightforward, though LilyPond glyphs are limited. For >> other ETs, use Graham Breed's regular.ly. More glyphs can be gotten using >> SMuFL.org with

Re: 48 and 72 ET

On 09.02.2017 20:59, Hans Åberg wrote: Multiples of 12 are straightforward, though LilyPond glyphs are limited. For other ETs, use Graham Breed's regular.ly. More glyphs can be gotten using SMuFL.org with OpenLilyPond. read: openLilyLib, right? Best, Simon

Re: example(s) of the power of Lilypond

MarcM wrote > Lilypond is a very powerful music score writing software. > > I'd like to ask the community what is/are your best example(s) of the > power of Lilypond? For one, I can tell you that most (if not all) of Trevor Bača's compositions use LilyPond and they look beautiful. The scores

Re: 48 and 72 ET

> On 9 Feb 2017, at 20:18, Bernardo Barros wrote: > Quarter-tones (24ET) work very well and use the most used symbols. > > Is there any implementation of eighth-tone (48ET) with arrows for the > 8th-tone alterations, or even better, 72ET? Multiples of 12 are

48 and 72 ET

Hello, Quarter-tones (24ET) work very well and use the most used symbols. Is there any implementation of eighth-tone (48ET) with arrows for the 8th-tone alterations, or even better, 72ET? I know "makam.ly" could be a good start, I'm just wondering if anyone has done it already. Thank you!

example(s) of the power of Lilypond

Lilypond is a very powerful music score writing software. Today examples of this power are buried in the documenation. I'd like to see featured on the website, examples of the power of Lilypond. To select the best or most useful, I'd like to ask the community what is/ are your best example(s) of

tuplet slurs

For voices with lyrics it is common to put triplet indications always above the staff, using the following rules. . stems up or down, no beam: as usual (i.e., a number and a bracket at the top, as if using \tupletUp) . stems up, with beam: as usual (i.e., a number over the beam) The

Re: New LilyPond website

First, I want to thank John for his contribution. The new design looks more modern and gives a feeling that lilypond's community is alive. I deal with UI at work on a daily basis and no two persons will agree on the look and feel of a website of application. So IMHO we should focus on making sure

Re: multiple dynamics contexts

Thanks, Simon. That worked. << \new Dynamics \with { \override VerticalAxisGroup.staff-affinity = #DOWN } { % content above staff } \new Staff { % music } \new Dynamics \with { \override VerticalAxisGroup.staff-affinity = #UP } { % content below staff } >> Mason On 9

Re: New LilyPond website

On 09.02.2017 08:35, Mats Behre wrote: On 2017-02-09 07:41, Werner LEMBERG wrote: . I like the sans-serif font more that you've used in the previous version. Please restore it. I would actually recommend not specifying a specific font at all. This leaves the font selection to the user (and

Re: New LilyPond website

On 09.02.2017 14:52, David Kastrup wrote: John Roper writes: The standard human does not want to read that much text. Which makes the standard human unsuitable for working with LilyPond Taking everything literally is not going to help communication, David. The

Re: Re: New LilyPond website

On 2017-02-09 07:41, Werner LEMBERG wrote: . I like the sans-serif font more that you've used in the previous version. Please restore it. I would actually recommend not specifying a specific font at all. This leaves the font selection to the user (and we will not have to debate the choice

Re: New LilyPond website

I just pushed a new version of Blended which allows you to get other (HTML) file contents as variables. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: New LilyPond website

> > It's also worth noting that only part of a website's job is to garner > initial interest (and it requires referals to be found in the first > place). Another is as a portal for people who already know what > LilyPond is and want to get work done. I belive that my design does both. The

Re: New LilyPond website

John Roper writes: > I changed the header size to be smaller. As for the overall design, again, > the front page of the website is supposed to make the user want to take a > look at it. A design such as this does that while a page full of serif text > and two images does

Re: New LilyPond website

Am 2017-02-09 13:43, schrieb John Roper: > I changed the header size to be smaller. As for the overall design, > again, the front page of the website is supposed to make the user want > to take a look at it. A design such as this does that while a page full > of serif text and two images does

Re: New LilyPond website

I changed the header size to be smaller. As for the overall design, again, the front page of the website is supposed to make the user want to take a look at it. A design such as this does that while a page full of serif text and two images does not. As for the separation of templates and content,

Re: New LilyPond website

On Thu, 09 Feb 2017 09:44:58 +0100 (CET), Werner LEMBERG wrote: > What I want is the explicit command line that I > have to call to convert the input data in the git repository to the > output html, where to expect the output files, etc., so that I can > actually try to generate

Re: multiple dynamics contexts

On 09.02.2017 08:20, Mason Hock wrote: there is too much space between the staff and the content below it. To adjust the spacing between Staff and Dynamics, please have a look at . HTH, Simon

Re: New LilyPond website

>>> Just for the record: With Firefox on Linux there's *no* problem. >> >>Indeed, sigh. This is one of the reasons I don't like working with >>HTML. Hopefully Blended can be improved to completely hide such >>issues for Joe User. > > I assume this doesn't have anything to do with Blender (or

Re: New LilyPond website

Am 09.02.2017 um 09:44 schrieb Werner LEMBERG: >>> . At the top, I get something like the attached image (using >>> Chrome), regardless of the magnification. This looks bad. Isn't >>> it possible to have the button size changed dynamically? >> Just for the record: With Firefox on Linux

Re: New LilyPond website

>> . At the top, I get something like the attached image (using >> Chrome), regardless of the magnification. This looks bad. Isn't >> it possible to have the button size changed dynamically? > > Just for the record: With Firefox on Linux there's *no* problem. Indeed, sigh. This is one of