Re: 64-bit version of Lilypond?

[Yentl Tijssens]

Thank you. I hope there will be one for 10.15 soon. Or by the time Catalina 
comes out, a Lilypond build that doesn’t require MacPorts. I know a lot of 
people who will update without knowing Lilypond will not work anymore.

On 17 Jul 2019, at 17:46, Hans Åberg  wrote:
> 
> [Please keep the cc to the list, so that others can follow the issue.]
> 
> For MacOS 10.14 or earlier, install MacPorts, and issue in Terminal the 
> command
>  port install lilypond-devel
> 
> There is probably no MacPorts for 10.15, though.
> 
> 
>> On 17 Jul 2019, at 16:53, Yentl Tijssens  wrote:
>> 
>> Yes I read about the slow updating, but I guess that’s better than having 
>> nothing. Is there a place that I could download that build?
>> 
 On 1 Jul 2019, at 00:11, Hans Åberg  wrote:
>>> 
>>> 
 On 30 Jun 2019, at 22:49, Yentl Tijssens  wrote:
 
 Hey,
 
 I’m a bit of a nooby tech enthusiast and upgraded to the Catalina Beta. Of 
 course Lilypond doesn’t work on that version because it is a 32-bit 
 application.
 I saw your post and was wondering if you could provide me your way to use 
 a functional lilypond 64-bit version with Frescobaldi. 
>>> 
>>> I added the devel list, as there is an issue to consider when using 
>>> MacPorts for LilyPond, namely that it tends to be slow updating with the 
>>> new MacOS’s, typically some month after the official public release.
>>> 
>>> 
>> 
> 


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: lilypond-devel Digest, Vol 200, Issue 23

[Carl Sorensen]

On 7/17/19, 2:04 PM, "lilypond-devel on behalf of Christopher Heckman" 
 wrote:

> f:aug is clearly wrong, aes:aug has the right notes but the root note is
> awkward, not being the lowest.  I have no idea how guitarists would feel
> about that.

My guess is: not too good. The C aug, E aug, and G# aug all have the
same notes, so it's vital to have the correct root.

Please give me a recommended diagram (or string-fret-finger set) for F aug and 
aes aug.

Thanks,

Carl
 

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: lilypond-devel Digest, Vol 200, Issue 23

[Christopher Heckman]

On Wed, Jul 17, 2019 at 11:00 AM  wrote:
>
> From: David Kastrup 
> To: James 
> Cc: lilypond-devel 
> Subject: Re: problem with predefined-guitar-fretboards.ly?
> Message-ID: <87woggstw8@fencepost.gnu.org>
> Content-Type: text/plain
>
> James  writes:
>
> > Hello,
> >
> > I saw arecent update by a LP user to an 'already-fixed' tracker
> >
> > 
> >
> > That made it into my inbox thus:
> >
> > On 06/07/2019 21:54, Christopher Heckman wrote:
> >> It's isn't just the website; the boards for augmented and diminished
> >> chords are calculated incorrectly.
> >>
> >> \include "predefined-guitar-fretboards.ly"
> >> \new FretBoards \chordmode { b:dim f:aug aes:aug g:dim }
> >>
> >> The F aug chord is incorrect; it actually shows a G augmented
> >> chord.
>
> >> In all four cases, the numbers at the bottom do not match up with the
> >> diagram. The B dim number should be 2343, the A flat aug 032110, and
> >> G dim should be 3131.
>
> This is just a misunderstanding of the numbers: they are not fret
> numbers but fingering numbers.

Yes, that's a mistake on my part. However, the G+ chord still doesn't
display correctly.

> It is a bit unusual that they are
> present by default: typically players are expected to figure them out on
> their own, and sometimes they are just inscribed in the dots.
>
> f:aug is clearly wrong, aes:aug has the right notes but the root note is
> awkward, not being the lowest.  I have no idea how guitarists would feel
> about that.

My guess is: not too good. The C aug, E aug, and G# aug all have the
same notes, so it's vital to have the correct root.

--- Christopher Heckman

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 64-bit version of Lilypond?

[Hans Åberg]

[Please keep the cc to the list, so that others can follow the issue.]

For MacOS 10.14 or earlier, install MacPorts, and issue in Terminal the command
  port install lilypond-devel

There is probably no MacPorts for 10.15, though.


> On 17 Jul 2019, at 16:53, Yentl Tijssens  wrote:
> 
> Yes I read about the slow updating, but I guess that’s better than having 
> nothing. Is there a place that I could download that build?
> 
>> On 1 Jul 2019, at 00:11, Hans Åberg  wrote:
>> 
>> 
>>> On 30 Jun 2019, at 22:49, Yentl Tijssens  wrote:
>>> 
>>> Hey,
>>> 
>>> I’m a bit of a nooby tech enthusiast and upgraded to the Catalina Beta. Of 
>>> course Lilypond doesn’t work on that version because it is a 32-bit 
>>> application.
>>> I saw your post and was wondering if you could provide me your way to use a 
>>> functional lilypond 64-bit version with Frescobaldi. 
>> 
>> I added the devel list, as there is an issue to consider when using MacPorts 
>> for LilyPond, namely that it tends to be slow updating with the new MacOS’s, 
>> typically some month after the official public release.
>> 
>> 
> 


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: problem with predefined-guitar-fretboards.ly?

[Carl Sorensen]

On 7/17/19, 6:55 AM, "lilypond-devel on behalf of David Kastrup" 
 
wrote:

James  writes:

> Hello,
>
> I saw arecent update by a LP user to an 'already-fixed' tracker
>
> 
>
> That made it into my inbox thus:
>
> On 06/07/2019 21:54, Christopher Heckman wrote:
>> It's isn't just the website; the boards for augmented and diminished
>> chords are calculated incorrectly.
>>
>> \include "predefined-guitar-fretboards.ly"
>> \new FretBoards \chordmode { b:dim f:aug aes:aug g:dim }
>>
>> The F aug chord is incorrect; it actually shows a G augmented
>> chord.

>> In all four cases, the numbers at the bottom do not match up with the
>> diagram. The B dim number should be 2343, the A flat aug 032110, and
>> G dim should be 3131.

This is just a misunderstanding of the numbers: they are not fret
numbers but fingering numbers.  It is a bit unusual that they are
present by default: typically players are expected to figure them out on
their own, and sometimes they are just inscribed in the dots.

I agree with David's assessment that the reporter misunderstood the numbers, 
which are fingering numbers.  The presence or absence of fingering numbers is a 
house style decision.   Most of the popular music piano/guitar/vocal books that 
I have use finger numbers; they are about equally split between having the 
numbers at the bottom of the diagram  and having numbers in the dots.

f:aug is clearly wrong, aes:aug has the right notes but the root note is
awkward, not being the lowest.  I have no idea how guitarists would feel
about that.

The diagrams and fingerings came from my reference "The Big Gig Bag Book of 
Guitar Chords".  I don't have enough experience to vouch for the diagrams; I 
just copied the information.  I would be happy to replace any diagrams with 
correct diagrams as reported by somebody with more expertise than me.

Thanks,

Carl
 

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: problem with predefined-guitar-fretboards.ly?

[David Kastrup]

James  writes:

> Hello,
>
> I saw arecent update by a LP user to an 'already-fixed' tracker
>
> 
>
> That made it into my inbox thus:
>
> On 06/07/2019 21:54, Christopher Heckman wrote:
>> It's isn't just the website; the boards for augmented and diminished
>> chords are calculated incorrectly.
>>
>> \include "predefined-guitar-fretboards.ly"
>> \new FretBoards \chordmode { b:dim f:aug aes:aug g:dim }
>>
>> The F aug chord is incorrect; it actually shows a G augmented
>> chord.

>> In all four cases, the numbers at the bottom do not match up with the
>> diagram. The B dim number should be 2343, the A flat aug 032110, and
>> G dim should be 3131.

This is just a misunderstanding of the numbers: they are not fret
numbers but fingering numbers.  It is a bit unusual that they are
present by default: typically players are expected to figure them out on
their own, and sometimes they are just inscribed in the dots.

f:aug is clearly wrong, aes:aug has the right notes but the root note is
awkward, not being the lowest.  I have no idea how guitarists would feel
about that.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

problem with predefined-guitar-fretboards.ly?

[James]

Hello,

I saw arecent update by a LP user to an 'already-fixed' tracker



That made it into my inbox thus:

On 06/07/2019 21:54, Christopher Heckman wrote:

It's isn't just the website; the boards for augmented and diminished chords are 
calculated incorrectly.

\include "predefined-guitar-fretboards.ly"
\new FretBoards \chordmode { b:dim f:aug aes:aug g:dim }

The F aug chord is incorrect; it actually shows a G augmented chord. In all 
four cases, the numbers at the bottom do not match up with the diagram. The B 
dim number should be 2343, the A flat aug 032110, and G dim should be 3131.

Others might be incorrect as well.

--- Christopher Heckman


I've just built current master and ran it on this person's tiny example 
(see attached screenshot of output), I have zero knowledge about 
guitar/frets and wondered if someone could check the output to see if, 
as claimed, the output is wrong?


I can then go from there and create a new ticket.

James


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: PATCHES - Countdown for July 16th

[Knut Petersen]

Hi James!



 Push:

5533 Add tex/txi-pt.tex - Knut Petersen
https://sourceforge.net/p/testlilyissues/issues/5533
http://codereview.appspot.com/562920043



I do not have write access to the repository - please push.

Knut


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel