Re: Key signatures in MIDI output

On Sat, 11 May 2024, Giles Boardman wrote: > I have now been more systematic in my approach and conclude that \key is not > reflected in MIDI output. I tried various positions for events and in each Well, it definitely is reflected in the output in my own tests. The example code I posted, when

Re: Key signatures in MIDI output

On Sat, 11 May 2024, Giles Boardman wrote: > When I create MIDI output from Lilypond, if I have imported a MIDI file and > then resaved it with changes made in LilyPond, the output is like that, too. Lilypond as such does not import MIDI files. I think you must be using some piece of software

Re: Key signatures in MIDI output

On Fri, 10 May 2024, Hans Åberg wrote: > > signature. The MIDI file does not contain that information; it is up to > > whatever software reads the MIDI file, to display it appropriately. > > So to go back to staff notation from MIDI, one must know what enharmonic > equivalences that have been

Re: Key signatures in MIDI output

On Fri, 10 May 2024, Hans Åberg wrote: > Programs like ABC work so that one writes the music without accidentals, > and then apply a key signature to get them. It was my reading that the > OP asked for that. Okay. I didn't read it that way because the OP said he was getting correct output in

Re: Key signatures in MIDI output

On Fri, 10 May 2024, Hans Åberg wrote: > To change the MIDI output, you will need to change the notes, say by > transposing or something else. MIDI files can include events ("key-change meta messages") for key signatures, each specifying a root and whether it's major or minor (which actually

Re: Is there a more complete predefined-guitar-fretboards.ly?

On Mon, 29 Apr 2024, Kevin Cole wrote: > "predefined-guitar-ninth-fretboards.ly" get the job done. But on a few > occasions I've had to resort to studying some online tutorial and > constructing the diagrams from scratch. Not a complete solution, but my chord database at

Re: subscript in lyrics

On Sat, 20 Apr 2024, David Olson wrote: > I'm a lyric poet writing songs about science. > > "CO2" is three syllables and often works better than "carbon dioxide". > > It's acceptable even if "2" doesn't appear as a subscript (one sees this > usage frequently), but subscript would be cool.  > > A

Re: Time measurement

On Thu, 14 Mar 2024, Jean Abou Samra wrote: > > “This sounds like a job for… Custom Engraver!!”  :) > > #(define (Custom_engraver!! context) >(define (format-time seconds) Thanks! I haven't tested this extensively, but so far it looks like it works well. -- Matthew Skala

Time measurement

Is there any easy way to find out the time in seconds from the start of a score to a specified point, corresponding to the timing of the MIDI output? I can count measures and do math on the tempo, but that's less than ideal in the face of multiple tempo changes. Another idea would be to just cut

Re: { } not sounding right.

On Fri, 19 Jan 2024, Werner LEMBERG wrote: > This is a limitation of MIDI: You can only have a single pitch bend > per time step per channel. LilyPond's rather primitive MIDI 1.0 > output provides no means to circumvent this limitation. I've sometimes gotten good use out of LilyPond code from

Re: Grandstaff multi-bar rest count shared between staves

On Wed, 17 Jan 2024, Martin Brown wrote: > To answer my own question, I've fudged this with: >     \omit MultiMeasureRestNumber at the start of the bass line >     \override MultiMeasureRestNumber.Y-offset = -5 at the start of the > treble line > but that seems a bit fragile. Eg. if the staves

Re: Transpose from major to minor key

On Thu, 11 Jan 2024, Wol wrote: > You need to remember lilypond thinks in terms of pitch, not note names. Unlike > some (most?) other music software. So "\transpose g e" says "transpose EVERY > note up A TONE". I'm not sure it's quite right to say that Lilypond thinks in terms of pitch, not note

Re: zero-duration s to hold marks

On Wed, 10 Jan 2024, Raphael Mankin wrote: > That strikes me as being a programmer's response, and I speak as a programmer > for over 50 years. Using <> works, but it is unintuitive. If s0 is more > intuitive then that should be considered for future inclusion. It's intuitive to me that s0 means

Re: Output PDF to stdout

On Fri, 5 Jan 2024, Dr. Arne Babenhauserheide wrote: > > intermediate "files" will be written to and read from the buffer cache at > > RAM speed and only later go to the disk in the background. > > That depends on the file system and its synchronization model. I once > sped up a script to control

Re: Output PDF to stdout

On Thu, 4 Jan 2024, Volodymyr Prokopyuk wrote: > My motivation behind using lilypond in a pipeline is to speed up PDF > generation by avoiding storing intermediary files on disk. The pipeline I'd Is that issue real? In Linux and most other operating systems, intermediate "files" will be written

Re: Is there a property that would set all of the "above staff" text to "above chordnames"

On Mon, 1 Jan 2024, Kevin Cole wrote: > What I mean is, I often have a situation where there's only a wee bit > o' text occasionally, above the staff. But I frequently have > ChordNames. It seems to me that the ChordNames would be better placed > below the occasional text, and I was hoping that,

Re: Hide chords

On Tue, 5 Dec 2023, Jan wrote: > What is the recommended method to “hide” chord names for a couple of > measures? For example, in the snipped below I’d like to hide the chords for > measures 5 to 8. Depending on exactly how you're generating the chord names in the first place, it may be easy

Re: Articulate has trouble with grace note at time signature change

On Wed, 22 Nov 2023, Werner LEMBERG wrote: > Please check the looong list of bugs related to `\articulate` whether > it has already been reported. Seems to be #3696, reported - by you - in 2013. -- Matthew Skala msk...@ansuz.sooke.bc.ca People before tribes.

Articulate has trouble with grace note at time signature change

This fails in 2.24.1 with messages about mid-measure time signature change and failed barcheck: \include "articulate.ly" \articulate { \time 4/4 c'1 | \time 3/2 \grace d'8 c'1. | } Succeeds if \articulate is not used. I can work around it by tagging MIDI and non-MIDI versions of the

Re: Still failing to operate lilypond 2.20.0 64-bit version.

On Fri, 6 Oct 2023, Werner LEMBERG wrote: > Thanks. I think it's ghostscript – there are no pre-built packages > available either. While LilyPond doesn't link to it in normal builds, > gs is needed for converting LilyPond's EPS output files to PDF. In > other words, a MacPorts user still needs

Re: Merging dynamics with music

On Sat, 16 Sep 2023, Knute Snortum wrote: > Try moving the Dynamic performer to the Staff level.  Cutting and pasting this code produces two pages of error messages because it's full of "non-breaking space" characters which LilyPond can't process, but I was able to get the desired results by

Re: Merging dynamics with music

On Sat, 16 Sep 2023, David Kastrup wrote: > > With the following code, the notes in the MIDI file still are both at > > default velocity. Explicitly instantiating the Staff does make a > > difference in the visual output. > > > > MyMusic = { c'1 c'1 } > > MyDynamics = { s1\ppp s1\fff } > > > >

Re: Merging dynamics with music

On Sat, 16 Sep 2023, David Kastrup wrote: > Try > > \new Staff << \MyMusic \MyDynamics >> > > since otherwise the variables will end up in separate Staff contexts. With the following code, the notes in the MIDI file still are both at default velocity. Explicitly instantiating the Staff does

Merging dynamics with music

I'm trying to use a Dynamics context to put dynamics between the staves of a PianoStaff. As such, I've got my notes and my dynamics in two separate variables. For MIDI output, I'd like to merge the contents of the music variable and the dynamics variable and generate MIDI from the result. But I

Re: Doubling a note makes MIDI output louder

On Sun, 9 Jul 2023, Knute Snortum wrote: > note out of the other hand.  This is why I suggested that the MIDI performer > could ignore \parenthesize notes.  Would this create a pile of workarounds > for you? Not as long as I don't use \parenthesize. But I think it's preferable not to have a

Re: Doubling a note makes MIDI output louder

On Sun, 9 Jul 2023, David Wright wrote: > players. But that's the problem here. When two real voices happen on > the same note, the result doesn't sound like one louder voice, yet > that's the effect you get from MIDI,¹ where the "two" voices are Not on *my* MIDI synthesizer. Two notes are two

Re: Doubling a note makes MIDI output louder

On Sun, 9 Jul 2023, Knute Snortum wrote: > In the MWE the instrument is a piano, so you wouldn't want the note to sound > louder than the surrounding notes, because the doubled note is played by > only one hand.  But I can see this might be a problem if the two staves were > for two voices. 

Re: Doubling a note makes MIDI output louder

On Sun, 9 Jul 2023, Knute Snortum wrote: > I'm not sure exactly how one would deal with this problem, other than with > tags.  Maybe \parenthesize could not produce MIDI output?  Or is there a way Is that a problem? If these are two notes in different MIDI channels, then the MIDI output is just

Re: chord.ly to extract notes from chords breaks with new Guile

On Wed, 31 May 2023, Gilles Thibault wrote: > Not hardly tested but this should work : Thanks for looking at it further. I hate to impose on you because I've already decided to solve this problem in external postprocessing of the MIDI files, so I hope you won't put a lot of effort into trying

Re: chord.ly to extract notes from chords breaks with new Guile

On Mon, 29 May 2023, Gilles Thibault wrote: > chord.ly has been renamed to chordsAndVoices.ly (it deals also now with > Voices) > You can donwload it here : Thanks a lot! As far as I know, the new version works fine. The problem in the old version was just because of the non-breaking spaces in

Re: chord.ly to extract notes from chords breaks with new Guile

On Sat, 27 May 2023, David Kastrup wrote: > which contains a delirious number of unbreakable spaces, code \xa0 > instead of \x20 as for a normal, breakable space. Thanks! Correcting these seems to have fixed the problem, at least for the moment. I don't know why the old version needed *some*

Re: chord.ly to extract notes from chords breaks with new Guile

On Sat, 27 May 2023, Jean Abou Samra wrote: > Are you sure that this is the correct example? That the file chord.ly it > uses is the same as the one you sent? That LilyPond is the one you believe > and unpatched, etc. ? Yes, using the chord.ly file I attached to my message, extracted from the

chord.ly to extract notes from chords breaks with new Guile

Back in 2015 people on the list helped me with extracting notes from chords, in this thread: https://lists.gnu.org/archive/html/lilypond-user/2015-09/msg00394.html The solution from 2015 has broken now, in the transition between versions 2.21.0 and 2.24.1. I think it's because of changes in

Re: Fyi: this list, lilypond-user, just had it's subject [tag] and footer removed

On Fri, 25 Oct 2019, Andrew Bernard wrote: > complex part of this, along with SPF and DKIM. The change that is being made > here is clearly necessary to me, and explains some of the list issues people > were having lately. Sadly, it's probably unintelligible to non-experts. I run a mail server

Re: Fyi: this list, lilypond-user, just had it's subject [tag] and footer removed

On Thu, 24 Oct 2019, sysad...@gnu.org wrote: > Any list administrator for this list is free to change these settings > back, instructions are below. I hope that it will be changed back. The subject tag is useful for automatic categorization of incoming messages. -- Matthew Skala

Re: Creating MP3 files

On Tue, 15 Oct 2019, Martin Tarenskeen wrote: > On Mon, 14 Oct 2019, msk...@ansuz.sooke.bc.ca wrote: > > > There are free soundfonts available, and other commercial ones for sounds > > other than piano, but I don't have specific recommendations. > > You will need a General Midi (GM/GS/XG)

Re: Creating MP3 files

On Mon, 14 Oct 2019, Lisa C Lewis wrote: > It appears that LilyPond only creates MIDI output. Given that I need to > share the audio with other people who may not have MIDI players, is > there a means of generating MP3 files? If not, what do folks recommend > for converting MIDI to MP3? I've

Re: Input syntax question

On Mon, 30 Sep 2019, David Kastrup wrote: > The respective lines in lily/lexer.ll read > > A [a-zA-Z\200-\377] > SYMBOL{A}([-_]{A}|{A})* > COMMAND \\{SYMBOL} Interesting that this disagrees with the item from the Notation Reference cited elsewhere in the

Re: Input syntax question

On Mon, 30 Sep 2019, Andrew Bernard wrote: > The grammar is in Appendix A of the Lilypond Contributor's Guide. Thanks. How about the definitions of the terminals, such as STRING and SYMBOL? -- Matthew Skala msk...@ansuz.sooke.bc.ca People before tribes.

Re: Input syntax question

On Sun, 29 Sep 2019, Thomas Morley wrote: > > What characters are allowed in variable names? > > From NR: > "The name of a [LilyPond-]variable should have alphabetic characters > only; no numbers, underscores or dashes." Thanks. I had a hard time finding this in the manual. > Note the "yet"!!

Input syntax question

What characters are allowed in variable names? -- Matthew Skala msk...@ansuz.sooke.bc.ca People before tribes. https://ansuz.sooke.bc.ca/ ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Links in PDF-Files

On Fri, 20 Sep 2019, sir.teddy.the.fi...@gmail.com wrote: > Why does lilypond add these links and is there a way to prevent it from > doing so? Use the "-dno-point-and-click" option on the command line when you run LilyPond to turn off these links. The links are intended to make it easier to

Re: Migrating from commercial music notation software to free alternative

On Wed, 12 Jun 2019, David Kastrup wrote: > > LaTeX users are accustomed to writing macros in a Turing-complete language > > with, for instance, if statements. > > LaTeX or TeX users? I said LaTeX users because you did, but the statement is true about both. TeX users were the original topic of

Re: Migrating from commercial music notation software to free alternative

On Wed, 12 Jun 2019, David Kastrup wrote: > > nor conceptually TeX-like, despite the fact that it uses backslashes. > > It's a batch processing system with plain text input syntax. That makes > for workflows not unaccustomed to LaTeX users. By the way, it did LaTeX users are accustomed to

Re: Migrating from commercial music notation software to free alternative

On Wed, 12 Jun 2019, ah wrote: > ... using a TeX-based or TeX-like (free) music composition system, if > available and doing all programming, templating etc. in this myself. > Advantages: platform independent and free. Lilypond is not TeX-based nor conceptually TeX-like, despite the fact that it

Re: Vertical spacing of numeric time signature

On Thu, 9 May 2019, Malte Meyn wrote: > Am 09.05.19 um 16:53 schrieb msk...@ansuz.sooke.bc.ca: > > Is there any simple way to modify the vertical spacing between numerator > > and denominator in a numeric time signature? > > > > Not really simple. But it can be done by redefining the stencil:

Vertical spacing of numeric time signature

Is there any simple way to modify the vertical spacing between numerator and denominator in a numeric time signature? -- Matthew Skala msk...@ansuz.sooke.bc.ca People before tribes. https://ansuz.sooke.bc.ca/ ___ lilypond-user mailing

Re: Fine bar line \break before repeat sign

On Tue, 7 May 2019, Adam Good wrote: > I'm baffled by bar lines. In the example below, I would like for the f1 bar > to use a "final" bar line as in \bar "|." the \break then on the next line > begin with a repeat sign. The manual doesn't hint at this > >

Re: tag issue

On Sat, 13 Apr 2019, Gianmaria Lari wrote: >   \tag #'testOne a  >   \tag #'testTwo b > ~ >   \tag #'testOne a  >   \tag #'testTwo b > > } > > > But then why lilypond removes the tie? Shouldn't just remove the expression > following testTwo that is "b" ? The tie is not a separate

Re: Flat flared hairpins

On Tue, 1 Jan 2019, Andrew Bernard wrote: > American floors: 11 12 14 15 > English floors: 11 12 13 14 > > I saw this a lot when I worked in new York. I think this custom has persisted in the USA because large buildings need to have "mechanical" or "service" floors not directly visited by the

Re: Not Nice Review of the LilyPond

On Sun, 2 Dec 2018, David Kastrup wrote: > Have you looked at tags? Please read my messages before responding to them. -- Matthew Skala msk...@ansuz.sooke.bc.ca People before tribes. http://ansuz.sooke.bc.ca/ ___ lilypond-user mailing

Re: Not Nice Review of the LilyPond

On Sun, 2 Dec 2018, David Sumbler wrote: > > But MusiXTeX can do "if" statements. > I felt that an "if" would be useful, so I eventually came up with: That is useful for conditional includes, but it can't be embedded in the data structure that LilyPond calls "music" and stores in variables. As

Re: Not Nice Review of the LilyPond

On Sun, 2 Dec 2018, David Kastrup wrote: > is hard. At least LilyPond is a better starting point than MusiXTeX. But MusiXTeX can do "if" statements. -- Matthew Skala msk...@ansuz.sooke.bc.ca People before tribes. http://ansuz.sooke.bc.ca/

Re: Octave shifts in polyphonic setting

On Tue, 25 Sep 2018, Jogchum Reitsma wrote: > Restoring this from the first bars affected by adding or deleting apostrophes > or comma's, sometimes lead again to side effects. Rather frustrating... > > Is there a way to prevent this? Are you using relative mode? I only use absolute, myself;

Re: OT: typewriter LaTeX package

On Fri, 16 Feb 2018, Karlin High wrote: > Have you ever seen Luc Devroye's "On Snot and Fonts" website, with info on > over 70,000 fonts? Looks like he picked up the Vintage Type collection at some > point. Yes, I'm even listed in there myself. Great resource. Doesn't look like he has more

Re: OT: typewriter LaTeX package

On Fri, 16 Feb 2018, Shane Brandes wrote: > Got it to work. Figured out you can change to what ever font you want > in the sty file. Lessening the the grayscale variability and some of > the other variables with the use of a historical font yields really > convincing period style documents. This

Re: OT: typewriter LaTeX package

On Thu, 15 Feb 2018, Torsten Hämmerle wrote: > Let me assure you that Urs is right: in Germany, without any doubt, there is > no double space. > It says that there is only ONE space after punctuation marks according to > German standards. > Finally Associated Press Stylebook (!): "Use a single

Re: OT: typewriter LaTeX package

On Thu, 15 Feb 2018, Urs Liska wrote: > > that may not be standard for proportional typesetting (even LaTeX's > > standard 1.33 factor is no longer popular) but the double-width sentence > > space was universal in typewritten texts when typewriters were common. > > > > Are you sure this is not

Re: OT: typewriter LaTeX package

On Thu, 15 Feb 2018, Urs Liska wrote: > Sorry for the OT post, but I just have to share this new LaTeX package: > http://www.ctan.org/pkg/typewriter > > I really hope I'll find an opportunity to use it soon:-) Cute. For the genuine typewriter feel, it's important for the between-sentences space

Re: Pitch inflection

On Tue, 30 Jan 2018, David Kastrup wrote: > > as closely as possible I don't want to substitute quarter-tone symbols. Is > > there a simple way to insert arrows in place of accidentals? Playback is > > not an issue. > > Quarter notes wouldn't work anyway since you'd not be able to > distinguish a

Re: [OT] Linux Users

On Fri, 17 Nov 2017, Brett M. Gilio wrote: > How many Linux users are out there in the Lilypond community? Do any of > you use other type-setting software such as LaTeX or Csound rather than > graphical tools? One here. I'm not sure Csound qualifies as typesetting software, but I use it often

Re: [OT] Grammatic gender

On Fri, 17 Nov 2017, J Martin Rushton wrote: > There is a similar issue with the "apologetic apostrophe" in Scots. > From the 18thC to mid-20thC writers inserted apostrophes where Scots > didn't have a consonant that English does. For instance the English > word "give" is equivalent to the Scots

Re: Text listing output in .txt file

On Wed, 2 Aug 2017, Daniel Sanmartín Nieto wrote: > Is it possible to get a .txt output with a listing of text inputs written > throughout the music file? Does this have to be done all in Lilypond? Because it would be trivial to write your bits of text as comments with "%" and then extract them

Re: Help changing chord names

On Mon, 17 Jul 2017, Tom Swan wrote: > Hi. How do I change the chord name to just D13, not D9 13, as in the > following snippet? This is probably rudimentary, but I'm a bit rusty and > just getting back into lp. Thanks. -- Tom Looks like the use case for this thread:

Re: ChordMarkup context

On Wed, 5 Jul 2017, Thomas Morley wrote: > So I tried a proof of concept, although I'm not convinced of the idea > to have chords as markup only. Thank you! This seems to be a big improvement and I hope it'll reduce the perennial confusion people have with chord names, if we can simply point

Re: Circular dependencies - Deadlock

On Wed, 21 Jun 2017, caag...@gmail.com wrote: > On 06/21/2017 11:10 PM, Johan Vromans wrote: > > If you have a non-infinite recursive include it will continue. > > I think that would require solving the Halting Problem first. That's true if it has to determine whether the recursion is infinite,

Re: Circular dependencies - Deadlock

On Wed, 21 Jun 2017, Johan Vromans wrote: > Instead of aborting, LP could issue a warning that it detected a circular > include. If it then hangs, you have a clue what is going on. If you have a > non-infinite recursive include it will continue. If it's only a warning (we need not get back into

Re: Circular dependencies - Deadlock

On Wed, 21 Jun 2017, Simon Albrecht wrote: > It would be even better, I think, if Lily noticed the circular dependency and > aborted with an informative message instead of just running on forever. This may be a problem if there's any possibility of an include being conditional. Then, someone

Re: Circular dependencies - Deadlock

On Wed, 21 Jun 2017, Michael Käppler wrote: > foo.ily: > \include "bar.ly" > bar.ly: > \include "foo.ily" > Am I right to consider this a bug? I don't think so - at least not a bug in Lilypond. It's just doing what you told it to do, and most other language parsers that have an "include"

Re: lilypondblog.org: A Simple Trick to Help all Musicians

On Wed, 21 Jun 2017, Urs Liska wrote: > Do you think you can come up with a topic that actually relates to music > notation and still allows you to introduce your article? As it is I'm not I would advise caution here. It sounds to me like the person didn't know she was writing to a mailing list,

Re: Chords in LilyPond

On Fri, 26 May 2017, Kieren MacMillan wrote: > And I must say, I see his point: your implication seems to be that the > tolerance the “ordinary user” apparently has for working in a > notoriously uninviting and unfriendly [other people’s words, not mine!] > non-GUI-based batch-processed music

Re: Chords in LilyPond

On Fri, 26 May 2017, Kieren MacMillan wrote: > You do know that you’re not *forced* to use ChordNames, right? (Of > If you want to type something and simply have it appear as you typed it > (i.e., with no use or need for manipulations like transposition), why > not just use Lyrics? It already

Re: Chords in LilyPond

On Fri, 26 May 2017, Simon Albrecht wrote: > Am 26.05.2017 um 15:48 schrieb msk...@ansuz.sooke.bc.ca: > > On Fri, 26 May 2017, Simon Albrecht wrote: > > > Well, input syntax does not equal desired output. > > For ordinary users, it does. > > I have no idea what you’re talking about. Chords. As

Re: Chords in LilyPond

On Fri, 26 May 2017, Henning Hraban Ramm wrote: > I would manually write C/a if I want to let the player chose between c major > and a minor. > (Lowercase letters for minor chords needed a while to be possible with > LilyPond, but they are.) It's fine if you want to write that and you and the

Re: Chords in LilyPond

On Fri, 26 May 2017, Simon Albrecht wrote: > Well, input syntax does not equal desired output. For ordinary users, it does. -- Matthew Skala msk...@ansuz.sooke.bc.ca People before principles. http://ansuz.sooke.bc.ca/ ___

Re: Chords in LilyPond

On Fri, 26 May 2017, Thomas Morley wrote: > (Close to) all requested stuff is possible even right know. Ofcourse The problem is not that LilyPond cannot print the desired symbols. The problem is that the input to print those symbols does not match the output, and the mapping from input to output

Re: Chords in LilyPond

On Thu, 25 May 2017, Mats Behre wrote: > While this is true, in order to support things like transposition (which I for > one use frequently) I think you will have to devise formats for input and > internal representation (they may be the same) that identifies both all Yes, if you're doing

Re: Chords in LilyPond

On Thu, 25 May 2017, Thomas Morley wrote: > I vaguely remember such threads. > Though, could you give some examples (or links) so it is present here as well? Request for "rootless slash chords" from 2014 but brought up in a thread here last month:

Re: Chords in LilyPond

On Thu, 25 May 2017, Charles Winston wrote: > > On May 25, 2017, at 12:26 AM, Kieren MacMillan > > wrote: Except contains a > > huge amount of information that cannot currently be input in > > \chordmode (as far as I know). > > > > Ultimately, as long as we end up

Re: Permission for music

On Wed, 24 May 2017, David Wright wrote: > Perhaps this is because educators are pandering to their ignorance, > thus decreasing the likelihood they'll ever encounter the term. > I'm glad that LilyPond's authors know precisely what it does so well. Removing the advertisement is much easier than

Re: Chords in LilyPond

On Wed, 24 May 2017, Charles Winston wrote: > I’m participating in the Google Summer of Code working on improving > LilyPond’s internal representation of chords. The goal here is to create a > data structure that will represent a chord’s semantics beyond just a list of > notes in the chord. The

Re: Permission for music

On Wed, 24 May 2017, Simon Albrecht wrote: > > This is one reason that putting advertising for the LilyPond Web site in > > every PDF document by default may not be such a great idea. It makes > > LilyPond appear to have a meaningful connection with the content. > > Only if you overlook that the

Re: Permission for music

On Wed, 24 May 2017, Manuela Gößnitzer wrote: > Which website would that be? AFAIK this here is a mailing list, there is no > website with music sheets. This is one reason that putting advertising for the LilyPond Web site in every PDF document by default may not be such a great idea. It makes

Re: compile time linux/windows

On Thu, 4 May 2017, Orm Finnendahl wrote: > Does somene have similar experiences and could someone with a Windows > computer maybe compile the score and report back to the list so that > we can narrow down the culprit? > > Is it the lilypond version or could it be a wrong setup? Seems to me that

Re: Parallel Square Premusic

On Thu, 23 Mar 2017, David Kastrup wrote: > Punch cards seem to the best medium for your format. Not just that they > are rigidly column-based, but you'll also easily distinguish letters With careful programming you can probably get the card punch to serve as a musical instrument, too. --

Re: What can Premusic do that others can't?

On Tue, 21 Mar 2017, Flaming Hakama by Elaine wrote: > The only time I've even seen an attempt at irrational durations was in the > one other thread on this list that was actually more annoying, more > aggressive and differently clueless.  I believe the intended durations were > 1/sqrt(71) or

Re: Re: What can Premusic do that others can't?

Please trim quotes in replies. On Mon, 20 Mar 2017, Jeffery Shivers wrote: > On Mon, Mar 20, 2017 at 7:04 PM, wrote: > > me out? And what about my code is so cryptic? Can't anyone read a > > "dadadaaa"? > > No. Probably for the same reason *anyone* can't just read binary

Re: 13th chord?

On Sun, 26 Feb 2017, Wols Lists wrote: > The OP complained that when he asked for "C13" he got "C 9 13". Sounds > to me like now, if he asks for "C13" that's what he'll get, but if he > asks for "C13 (A13)" he's going to get "C 9 13 (A 9 13)". That's almost > worse!!! What do you mean by "now"?

Re: 13th chord?

On Sun, 26 Feb 2017, Wols Lists wrote: > > I don't know what that refers to. Are you confusing me with someone else? > > > "I imagine it would make sense for most of its code to derive from the > code currently used for lyrics, but that fact would preferably NOT be > visible to users." The

Re: 13th chord?

On Sun, 26 Feb 2017, Anthony Youngman wrote: > Replying to myself - remember, you said the user shouldn't notice any > difference. With my code, if you want to change the capo key, it's a I don't know what that refers to. Are you confusing me with someone else? -- Matthew Skala

Re: 13th chord?

On Sun, 26 Feb 2017, Anthony Youngman wrote: > EXCEPT. > > This is *exactly* the scenario in which you will want my chord transposition > code, and that doesn't make sense in a lyrics scenario. Then they can use the existing code. -- Matthew Skala msk...@ansuz.sooke.bc.ca People

Re: 13th chord?

On Sun, 26 Feb 2017, Thomas Morley wrote: > If the chordNameFunction (ignatzek-chord-names) does not do what we > want, we should improve it, but not drop a plethora of > lily-functionality. I'm not proposing to "drop a plethora of lily-functionality" but only to provide something that will be

Re: 13th chord?

On Sun, 26 Feb 2017, David Kastrup wrote: > To me it would seem that the default mode of operation should be for > them to have matched rules where feasible, in order to have least > element of surprise. I agree, but A. it may not be feasible in some important cases, and B. even matched rules

Re: 13th chord?

On Sun, 26 Feb 2017, Wols Lists wrote: > I'm guessing lily is taking *in* his request for "C 13", converting it > into the chord, and then converting that chord *back* into what it > thinks is called "C 9 13". With the result that lily's output does *not* > match the user's input. Frustrating!

Re: 13th chord?

On Sat, 25 Feb 2017, Rob Torop wrote: > 13 chord would be rendered as C13 in Ignatzek notation. My question is - is > there a way for me to omit the "9" in the chord name?  My experience is There's no "9" in the chord name "C13", so what are you really asking? Do you want to enter a chord name

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

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: Trolling and unacceptable behaviour on the list

On Sat, 19 Nov 2016, Andrew Bernard wrote: > The people making it a big deal is just me. Now having lost all credibility, > it's time I unsubscribed and stopped contributing. Your call, but I didn't say "all." Only your real point would be stronger without the distraction. -- Matthew Skala

Re: Trolling and unacceptable behaviour on the list

On Fri, 18 Nov 2016, Andrew Bernard wrote: > when asked politely refuses to give his name, refuses to provide minimal This "real name" business is completely irrelevant and the people trying to make it a big deal lose credibility on the other, much more important, points they make. -- Matthew

Re: Skyfonts

On Mon, 7 Nov 2016, Simon Albrecht wrote: > On 07.11.2016 12:31, msk...@ansuz.sooke.bc.ca wrote: > You might even say it was unethical by the provider of the font to not provide > for use in free software like LilyPond… ...or to put encrypted files in a hidden location on someone's machine.

  1   2   >