Re: Removing manual beams when multiplying note values

[Nicholas Moe]

I would like to keep the option of using either system. And after
further thought, I wouldn't want to remove every beam since the few
sixteenth notes I have would be converted to eighth notes, and I would
want to keep those beams. I did a search for "16" and created these
commands to place before and after those instances:

removeBeams = \override Beam #'stencil = ##f
showBeams = \override Beam #'stencil = ##t

If I'm compiling without multiplying note values, I can set these to
null and get back to where I began.

Since I'm working off of a score with modernised rhythms, I'm content
with doing my compilation checks without multiplying. After everything
is typed in, I can switch on the multiplication and just ignore the
warnings, since I already know I got everything else right!

Nick

On Thu, Jun 9, 2011 at 3:54 AM, Phil Holmes <address@hidden> wrote:
> ----- Original Message ----- From: "Nicholas Moe" <address@hidden>
> To: <address@hidden>
> Sent: Wednesday, June 08, 2011 9:40 PM
> Subject: Removing manual beams when multiplying note values
>
>
>> Hello,
>>
>> I am replicating a handwritten score of Renaissance polyphony. I
>> entered the notes with \autoBeamOff and manually entered the beams
>> where they were needed using square brackets. Later, I decided I
>> wanted to double the values of the notes, as is common with this type
>> of music. I figured out how to do it by using a snippet in "The
>> LilyPond Report #19" and removing the beam stencils. But now I get all
>> sorts of errors. How do I suppress these?
>>
>> Thanks,
>>
>> Nick
>>
>> %%%% BEGIN MINIMAL EXAMPLE %%%%
>> \version "2.13.61"
>>
>> looksSlower =
>> #(define-music-function (parser location music) (ly:music?)
>> (let ((new-music (ly:music-deep-copy music)))
>>  (shift-duration-log new-music -1 0)
>>  new-music))
>>
>> \relative c' {
>> \looksSlower{
>> \autoBeamOff
>> \override Beam #'stencil = ##f
>> a8[ b]
>> }
>> }
>
>
> Since you're removing the beam stencil and therefore stopping displaying any
> form of beam, wouldn't the simplest solution be to remove the manual beams
> ([]) with a text editor search and replace?
>
> --
> Phil Holmes
>
>