Tim McNamara writes:
> Is there a syntax for running convert-ly on a directory without having
> to cd into the directory and invoking
>
>convert-ly -e *.ly
>
> There doesn’t seem to be a recursive option. Since I’ve got .ly files
> in 158 different directories it’d be really nice to be a
OT: How long would it take on this computer:
https://www.youtube.com/watch?v=n3wPBcmSb2U
;-)
Francois
2014-05-16 18:18 GMT-05:00, efa...@faswebdesign.com :
> Yup, Windows 8 and I just installed the standard windows installation
> package.
>
>
>
>
>
>
> Sent from Windows Mail
>
>
>
>
>
> From: Coli
On May 16, 2014, at 1:54 PM, David Kastrup wrote:
> Tim McNamara writes:
>
>> Is there a syntax for running convert-ly on a directory without having
>> to cd into the directory and invoking
>>
>> convert-ly -e *.ly
>>
>> There doesn’t seem to be a recursive option. Since I’ve got .ly
Tim McNamara writes:
> On May 16, 2014, at 1:54 PM, David Kastrup wrote:
>
>> Tim McNamara writes:
>>
>>> Is there a syntax for running convert-ly on a directory without having
>>> to cd into the directory and invoking
>>>
>>> convert-ly -e *.ly
>>>
>>> There doesn’t seem to be a recur
On Fri, May 16, 2014 at 1:32 PM, Tim McNamara wrote:
> Message: 3
> Date: Fri, 16 May 2014 13:32:28 -0500
> From: Tim McNamara
> To: LilyPond Users
> Subject: convert-ly question
> Message-ID:
> Content-Type: text/plain; charset=windows-1252
>
> Is there a syntax for running convert-ly on a d
On 17.05.2014 18:20, Tim McNamara wrote:
On May 16, 2014, at 1:54 PM, David Kastrup wrote:
Tim McNamara writes:
Is there a syntax for running convert-ly on a directory without having
to cd into the directory and invoking
convert-ly -e *.ly
There doesn’t seem to be a recursive opti
On May 17, 2014, at 11:41 AM, Malte Meyn wrote:
> On 17.05.2014 18:20, Tim McNamara wrote:
>>
>> On May 16, 2014, at 1:54 PM, David Kastrup wrote:
>>
>>> Tim McNamara writes:
>>>
Is there a syntax for running convert-ly on a directory without having
to cd into the directory and in
Thanks for this hint - the problem for me was caused by an old version
of the emmentaler font that was in the system directory which the
character map was using. U+E18D was a mordent and I guess it dates
before that glyph was invented.
Richard
On Fri, 2014-05-16 at 15:24 -0700, tisimst wrote:
> R
Tim McNamara writes:
> On May 17, 2014, at 11:41 AM, Malte Meyn wrote:
>
>> On 17.05.2014 18:20, Tim McNamara wrote:
>>>
>>> On May 16, 2014, at 1:54 PM, David Kastrup wrote:
>>>
Tim McNamara writes:
> Is there a syntax for running convert-ly on a directory without having
Hi:
I'm using Lilypond 2.16.2 I get the above warning sometimes.
Is this a bug? Or am I doing something wrong? I can't detect the error,
and the midi seems OK.
Sebastisn
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/
Ah! That would make sense.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/emmentaler-font-codes-tp162465p162519.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
h
On Sat, 2014-05-17 at 11:37 -0500, Patrick or Cynthia Karl wrote:
>
> If you are on a unix machine (Mac, PC with Ubuntu, etc) you could do that by
> issuing the following command in a terminal window:
>
> find . -name \*.ly -print | xargs -n 1 convert-ly -e
>
> There is also a (possibly
My situation is I need to transcribe a crescendo starting without a dynamic
marking. If I put in a \mf then I don't get warning. If I can hide the
dynamic mark, all will be fine. Is there a \hide syntax that will work?
Knute Snortum
(via Gmail)
On Fri, May 16, 2014 at 3:14 PM, Conor Cook wr
On 05/17/2014 07:15 PM, Knute Snortum wrote:
My situation is I need to transcribe a crescendo starting without a
dynamic marking. If I put in a \mf then I don't get warning. If I
can hide the dynamic mark, all will be fine. Is there a \hide syntax
that will work?
Knute Snortum
(via Gmail)
Knute Snortum wrote
> My situation is I need to transcribe a crescendo starting without a
> dynamic
> marking. If I put in a \mf then I don't get warning. If I can hide the
> dynamic mark, all will be fine. Is there a \hide syntax that will work?
\version "2.18.2"
\once \omit DynamicText c-\mf
Knute Snortum wrote
> (De)crescendo with unspecified starting volume in MIDI.
>
> programming error: Impossible or ambiguous (de)crescendo in MIDI.
> continuing, cross fingers
BTW, I've run into this type of error before as well (with Mutopia files),
and hadn't taken the time to figure out the ca
Phil, I used your advice and made it to work.
I added an extra voice, a hidden note to push the staves further apart, then
used \tag to suppress the hidden note from MIDI, plus added an extra \score
block to generate the midi.
What an involved workaround, but I understand the special situation.
Knute Snortum writes:
> My situation is I need to transcribe a crescendo starting without a dynamic
> marking. If I put in a \mf then I don't get warning. If I can hide the
> dynamic mark, all will be fine. Is there a \hide syntax that will work?
Anything wrong with
\version "2.18.0"
\score
On Sun, 18 May 2014, Graham King wrote:
If you're going to use xargs, be careful of .ly files containing whitespace
in the filename. The GNU implementations of find and xargs support an
option for that:
find . -name \*.ly -print0 | xargs -0 -n 1 convert-ly -e
The commandline solution for t
19 matches
Mail list logo
