Adding acoustic guitar (steel) to MIDI

I did mean the source code. You directed me to all those sources. Thanks again. David Landt On Tue, Mar 15, 2016 at 7:01 PM -0700, "Simon Albrecht-2 [via Lilypond]" wrote: Hello David, we use to keep communication on-list, except to

Re: Adding acoustic guitar (steel) to MIDI

Hello David, we use to keep communication on-list, except to send really private information. On 16.03.2016 02:53, david_la...@hotmail.com wrote: Simon, I didn't know how to write any code prior to using LilyPond. Ok, so I misunderstood you from your speaking of the ‘source code’. I

Dashed Tie Design Improvement

Hi folks, The default shape of the tie's dashes looks a bit strange to me, is there a way to modify it to look a bit like the second one which in my opinion looks fuller on page? Also how can I increase and thicken the dashes between the tie end points? Thank you

Adding acoustic guitar (steel) to MIDI

Hello Simon. Simon Albrecht-2 wrote >> That makes so much more sense now! No wonder nobody else experienced >> the problem you described since no ChordNames were included in your >> original file. Initially, I was trying to follow the forum etiquette by only including what is pertinent;

Re: Adding acoustic guitar (steel) to MIDI

On 15.03.2016 23:31, Abraham Lee wrote: David, On Tue, Mar 15, 2016 at 4:14 PM, David Landt > wrote: Hello David. David Kastrup wrote > ChordName or FretBoard context? Yes, I used ChordNames. I think the grand piano

Adding acoustic guitar (steel) to MIDI

David Kastrup wrote > ChordName or FretBoard context? Yes, I used ChordNames context. Attached is my code. HereComestheSun.ly It seems that the grand piano on channel 1 was created because of using ChordNames. The

Re: Adding acoustic guitar (steel) to MIDI

David, On Tue, Mar 15, 2016 at 4:14 PM, David Landt wrote: > Hello David. > > > David Kastrup wrote > > ChordName or FretBoard context? > > Yes, I used ChordNames. I think the grand piano instrument sounded on > channel 1 because it was following the chord progression.

Adding acoustic guitar (steel) to MIDI

Hello David. David Kastrup wrote > ChordName or FretBoard context? Yes, I used ChordNames. I think the grand piano instrument sounded on channel 1 because it was following the chord progression. I only wanted to display chord names. To shut off the sound of the chord "names" being played as

Re: Adding acoustic guitar (steel) to MIDI

David Landt writes: > Trevor, I installed CoolSoft VirtualMIDISynth and the font bank you > mentioned. After setting the CoolSoft as the default synthesizer in > Frescobaldi, I did notice a difference in the sound of various instruments > when compared with Microsoft GS

Adding acoustic guitar (steel) to MIDI

Trevor, I installed CoolSoft VirtualMIDISynth and the font bank you mentioned. After setting the CoolSoft as the default synthesizer in Frescobaldi, I did notice a difference in the sound of various instruments when compared with Microsoft GS Wavetable Synth, which is my OS's default synthesizer.

Re: Set beam subdivision to #t by default

Hi Urs, > Are there any strong (and reasoned) objections against changing the default > here? No. Your new default seems the superior choice. Thanks! Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info

Re: Capturing inconsistency in beam subdivision length

Hi Urs, > Opinions? I agree with Gould: (b), with the one adjustment, is superior. > what this seems to call for is an update > to the beaming pattern calculation, something like (an optional) "do not > further subdivide a group that already has exactly four notes" rule. But > somehow I'm

Re: Dynamics context and vertical positions

Gilberto, On Tue, Mar 15, 2016 at 11:15 AM, Gilberto Agostinho [via Lilypond] < ml-node+s1069038n188571...@n5.nabble.com> wrote: > > The problem I have with it is that I often find the distance between the > dynamics and the staff to be very large and for no apparent reason. > ... [SNIP] ... > So

Adding acoustic guitar (steel) to MIDI

Trevor, thank you for letting me know about the Windows default settings. It seems that my OS is the culprit. I thought that I heard a very slight difference between the acoustic guitar and default piano, but wasn't sure. You and Abraham have confirmed that it is the case. I will try to figure

Dynamics context and vertical positions

Hi all, I have been using the Dynamics context since short time ago, and I think it substantially helps to improve the overall look of the score with its horizontal alignment of all dynamics in a system. The problem I have with it is that I often find the distance between the dynamics and the

Re: OT help with midi2ly on command line mac os blind user

Hello David, Thanks for pointing this out. I don’t use bash often in fact, since my default shell is tcsh. And it turns out I have a lot of bash left-overs from the machines I was in charge professionally some time ago… JM > Le 15 mars 2016 à 17:15, David Wright a

Re: OT help with midi2ly on command line mac os blind user

On Tue 15 Mar 2016 at 09:09:38 (+0100), Jacques Menu Muzhic wrote: >bash-3.2$ echo $PATH > >

Re: OT help with midi2ly on command line mac os blind user

On Mon 14 Mar 2016 at 22:16:28 (-0500), Daniel Contreras wrote: >Hello all,  >I am trying to wrap my head around this whole command line terminal. I am >attempting to follow the steps that are listed on the �Mac OS� section on >the lilypond website. I ,think, I have followed each

Re: no text

Bernhard, On Tue, Mar 15, 2016 at 9:38 AM, Dr. Bernhard Kleine [via Lilypond] < ml-node+s1069038n188565...@n5.nabble.com> wrote: > I do not see what is wrong, the text is not displayed. It is close to > what I used before. I am stymied. > > [SNIP] > > texttext= \lyricmode { > \set stanza = "Er

Re: no text

On 15.03.2016 16:27, Bernhard Kleine wrote: I do not see what is wrong, the text is not displayed. It is close to what I used before. I am stymied. All you do in the ‘texttext’ variable is set the stanza number to a very long string. So no text is displayed. HTH, Simon Bernhard \version

no text

I do not see what is wrong, the text is not displayed. It is close to what I used before. I am stymied. Bernhard \version "2.19.33" \language "deutsch" \header { title = "Erstanden ist der Herr" subtitle = "Ostermotette für gemischte Stimmen" subsubtitle = "Bearbeitung und Textfassung:

Re: Set beam subdivision to #t by default

On 15.03.2016 09:44, Urs Liska wrote: I would strongly suggest to switch the default setting so that subdivideBeams is set to #t by default. Agreed. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Set beam subdivision to #t by default

On Tue, Mar 15, 2016 at 6:11 AM, Urs Liska wrote: > > > Am 15.03.2016 um 10:58 schrieb Trevor Daniels: > >> So, before integrating that into my code I would collect opinions. Are > >> > there any strong (and reasoned) objections against changing the > default > >> > here? >

Re: Adding acoustic guitar (steel) to MIDI

David you wrote Tuesday, March 15, 2016 5:35 AM > On Mon, Mar 14, 2016 at 10:23 PM -0700, "tisimst [via Lilypond]" wrote: >> Frescobaldi doesn't actually provide the MIDI sound >> font, just the player interface. So, if you are only >> hearing piano, regardless of your choice of

Re: Set beam subdivision to #t by default

Am 15.03.2016 um 10:58 schrieb Trevor Daniels: >> So, before integrating that into my code I would collect opinions. Are >> > there any strong (and reasoned) objections against changing the default >> > here? > I agree we should switch the default, as long as it is clearly stated in > Changes,

Re: Set beam subdivision to #t by default

Urs Liska wrote Tuesday, March 15, 2016 8:44 AM > I would like to ask for your opinion on the matter of switching beam > subdivisions on or off by default. > > I would strongly suggest to switch the default setting so that > subdivideBeams is set to #t by default. I know that will affect

Re: Set beam subdivision to #t by default

> So, before integrating that into my code I would collect opinions. > Are there any strong (and reasoned) objections against changing the > default here? Your suggestions looks sensible. Werner ___ lilypond-user mailing list

Re: creating chords like F/A(D/F#) with \chordmode { }

2016-03-15 9:49 GMT+01:00 David Kastrup : > Eby Mani writes: > >> I'm getting the following error on Lilypond 2.18.2 while trying your >> "\altChord" function. Are those functions limited to Lilypond 2.19 ?. >> >>

Re: Set beam subdivision to #t by default

Am 15.03.2016 um 10:08 schrieb David Kastrup: > Urs Liska writes: > >> Hi all, >> >> at least mentally I'm starting to get back to the beaming pattern code. >> >> I would like to ask for your opinion on the matter of switching beam >> subdivisions on or off by default. >>

Capturing inconsistency in beam subdivision length

Another puzzle/quiz/poll on beaming patterns for today. Consider the attached renderings of a phrase with many notes, many beams and inconsistent note durations (=> beam count). a) is rendered with a base duration of 1/8 b) with 1/16. (Note that unlike my previous post this is *not* about

Re: creating chords like F/A(D/F#) with \chordmode { }

Eby Mani writes: > I'm getting the following error on Lilypond 2.18.2 while trying your > "\altChord" function. Are those functions limited to Lilypond 2.19 ?. > > "Parsing.../opt/lilypond/usr/share/lilypond/current/scm/ly-syntax-constructors.scm:56:23: > In expression (apply

Re: Set beam subdivision to #t by default

Urs Liska writes: > Hi all, > > at least mentally I'm starting to get back to the beaming pattern code. > > I would like to ask for your opinion on the matter of switching beam > subdivisions on or off by default. > > I would strongly suggest to switch the default setting

Set beam subdivision to #t by default

Hi all, at least mentally I'm starting to get back to the beaming pattern code. I would like to ask for your opinion on the matter of switching beam subdivisions on or off by default. I would strongly suggest to switch the default setting so that subdivideBeams is set to #t by default. I know

Re: OT help with midi2ly on command line mac os blind user

Hello Daniel, The contents of variable PATH (i.e. $PATH) is a sequence of directories names separated by colons : bash-3.2$ echo $PATH

Re:

Hi Paul, Since this is simple polyphony, use voices throughout, instead of just occasionally. The Notation Reference (NR) has a lot of information on this. Section 1.5.2 (for 2.19.38). This addresses your slur problem. Then \override Notehead.color = #blue Andrew

[no subject]

Dear All, here is perhaps a silly little question. I am trying to get a slur from a crotchet "into" one of the voices in a polyphonic voicing. In measure 1 the third blue note should have a slur connecting it to the next blue note, which is in the polyphonic part. I tried ( ) and \( \) with no