Re: adding other numbering systems to the LilyPond TAB score function

2019-01-01 Thread Thomas Morley 
Am So., 30. Dez. 2018 um 18:51 Uhr schrieb BLAINE SCOTT
:
>
>  I've looked over the Learning manual and found the custom tabulatures note 
> on page 331 answered my question as to how a clef/TABstaff was generated. I 
> was interested to see that LilyPond has predefined string tunings for violin, 
> viola, cello and DB. I'm anticipating that the numbers on the TABstaff are 
> the 'fret' numbers, for the violin/viola/cello, similar to the mandolin fret 
> numbers.
>  I'm hoping that the numbers used for unfretted string instruments could be 
> altered to match the system I'm using. The pitch of each note and string 
> remains the same but my system avoids the fret number problem on the 
> violin/viola/cello; one where the TAB fret numbers have no practical 
> reference for students gaining accuracy in finger placement.
> The numbering system for the violin/viola, treble/alto clefs I've developed 
> uses 0-4 to indicate what fingers of the left hand are used. The open string 
> note uses the numeral 0. The 1 fret is indicated by the number 1 and what 
> looks like a 0 exponent with it because the 1st finger is placed close to the 
> nut of the instrument where the "Open" position is. The 2nd fret is given the 
> number 1 (for the first finger), the 3rd fret is given the number 2 with an 
> exponent 1(meaning that it is the 2nd finger near [in front of] the 1 finger 
> position) the 4th fret is given the number 2 with the exponent 3 (meaning the 
> 2nd finger is placed behind the 3 finger position), the 5th fret is given the 
> number 3 alone. The 6th fret is a 3 with the exponent 4 added to it. The 4th 
> finger (7th fret) plays the same note as the next string.This does limit the 
> use of this numbering system to the Open and First finger positions however, 
> by the time my students have mastered all the Open keys they have the 
> technical skills to more quickly pick up the shift to clef only score reading.
>  I use three strips of tape on the fingerboard of their violin/viola or cello 
> at the 1st finger position, the 2nd near the 3 finger position and at the 3rd 
> finger position.
> The numbering system above is placed on a 4 line TAB score. The treble and 
> alto clef are used as the music line above each TAB line for later reference 
> and initial theory introduction for violin and viola. These numbers then 
> provide direction for what finger goes where on the fingerboard.  The Cello 
> bass clef version of the TAB line uses only the numbers 0-4, not requiring 
> the exponent looking number.
>
> Could a version of LilyPond be adapted so that the string orchestra 
> instruments could use the alternate numbering systems described above for the 
> same note pitches and positions on the fingerboards.
> I look forward to any comment the LilyPond development community can provide, 
> particularly where the code section is located for the TABscore numbering 
> systems. I hope to be able to add my violin, viola and cello numbered TAB 
> versions to what LilyPond can provide or find a code maker who could insert 
> the specific adaptions to the TABscores I am discussing.
> Sincerely,
> Blaine Matthew ScottSistema Huronia music teacherMidland ON Canada

Hi,

I don't understand how it should look.

Is this post of any help?
http://lilypond.1069038.n5.nabble.com/Custom-tabulature-for-Shamisen-td218454.html#a218458
You would need to replace the signs in 'my-signs' with your own.

Cheers,
  Harm

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

Re: GUB lilypond build fails

2019-01-01 Thread Werner LEMBERG 


>> Please cherry-pick 8067320145662554d85e59e6b9e6df3770f9e4a3 also;
>> I'm going to submit fontconfig changes to gub that rely on the
>> availability of this feature.
> 
> Well, I am not happy with such fresh changes in the stable-2.20
> branch but a 2.20 that we don't manage to get through GUB is
> pointless.  So also done.

Thanks!


Werner

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

Re: adding other numbering systems to the LilyPond TAB score function

2019-01-01 Thread Karlin High 
On Sun, Dec 30, 2018 at 11:51 AM BLAINE SCOTT 
wrote:

> Could a version of LilyPond be adapted so that the string orchestra
> instruments could use the alternate numbering systems described above for
> the same note pitches and positions on the fingerboards.
>

I will not be able to answer your question directly. But if things like
Clairnote  are possible with LilyPond, it seems
like special tab staffs also should be.
-- 
Karlin High
Missouri, USA
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

ulimits for `lilypond-test' in gub

2019-01-01 Thread Werner LEMBERG 

Folks,


running `lilypond-test' in gub uses the following ulimit values for
creating the regression EPS files:

  ulimit -m 524288
  ulimit -d 524288
  ulimit -v 2097152

Interestingly, this is not sufficient on my 64bit openSuSE 42.3
GNU/Linux box with my forthcoming changes to restrict fontconfig to
fonts from gub only: Handling the file name list file
`out/lybook-testdb/snippet-names-5692165138572845334.ly' fails in
job 1 while processing file `40/lily-dee14dc0.ly' (i.e.,
`paper-twosided.ly')

Generously increasing ulimit parameters

  ulimit -m 1048576
  ulimit -d 1048576
  ulimit -v 3145728

did work, however.  How shall I proceed?  Is there an easy way to find
the minimum ulimit values that are necessary and/or sufficient?  I can
imagine this influences the settings needed for creating and running
VMs...

Attached is a script that exactly replicates the problematic lilypond
command (with all the necessary environment variables) in case people
want to play with it.


Werner
# manual execution of `lilypond-test' EPS file generation within gub
#
# tested with lilypond git commit 8947c1ce3f3295e786c3d722dcb7b24087f50600
#
# original ulimit values:
#
#   ulimit -m 524288
#   ulimit -d 524288
#   ulimit -v 2097152

GUBDIR=/home/wl/git/gub

cd 
$GUBDIR/target/linux-64/build/lilypond-git.sv.gnu.org--lilypond.git-master/out/lybook-testdb
 \
&& ulimit -m 1048576 \
&& ulimit -d 1048576 \
&& ulimit -v 3145728 \
&& PATH=\
$GUBDIR/target/tools/root/usr/bin\
:$GUBDIR/target/linux-64/root/usr/bin:$PATH \
   MALLOC_CHECK_=2 \
   LD_LIBRARY_PATH=\
$GUBDIR/target/tools/root/usr/lib\
:$GUBDIR/target/linux-64/root/usr/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} \
   GS_FONTPATH=\
$GUBDIR/target/linux-64/root/usr/share/ghostscript/9.21/fonts\
:$GUBDIR/target/linux-64/root/usr/share/gs/fonts \
   GS_LIB=\
$GUBDIR/target/linux-64/root/usr/share/ghostscript/9.21/Resource/Init\
:$GUBDIR/target/linux-64/root/usr/share/ghostscript/9.21/Resource \
   FONTCONFIG_FILE=$GUBDIR/target/linux-64/root/usr/etc/fonts-gub/fonts.conf \
   FONTCONFIG_PATH=$GUBDIR/target/tools/root/usr/etc/fonts-gub \
   $GUBDIR/target/linux-64/root/usr/bin/lilypond \
 -I 
$GUBDIR/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/input/regression
 \
 -dbackend=eps \
 --formats=ps \
 -djob-count=2 \
 -dseparate-log-files \
 -dinclude-eps-fonts \
 -dgs-load-fonts \
 --header=texidoc \
 -I 
$GUBDIR/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/Documentation/included/
 \
 -ddump-profile \
 -dcheck-internal-types \
 -ddump-signatures \
 -danti-alias-factor=1 \
 
-dfont-export-dir=$GUBDIR/target/linux-64/build/lilypond-git.sv.gnu.org--lilypond.git-master/out-fonts
 \
 -O TeX-GS \
 -I "./" \
 -I 
"$GUBDIR/target/linux-64/build/lilypond-git.sv.gnu.org--lilypond.git-master/input/regression"
 \
 -I 
"$GUBDIR/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/input/regression"
 \
 --formats=eps \
 -deps-box-padding=3.00 \
 -dread-file-list \
 -dno-strip-output-dir \
 
"$GUBDIR/target/linux-64/build/lilypond-git.sv.gnu.org--lilypond.git-master/out/lybook-testdb/snippet-names-5692165138572845334.ly"
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel