On 7 Feb 2013, at 23:33 , Joseph Rushton Wakeling wrote:
The regular one doesn't, the full-Boehm instrument does. See e.g.
this example:
http://www.clarinetsdirect.biz/RC-F279670.html
But that also has the low-ees, because it still is a soprano it
sounds higher then the low-ees in the
On 02/08/2013 10:11 AM, Wim van Dommelen wrote:
But that also has the low-ees, because it still is a soprano it sounds higher
then the low-ees in the bass-clarinet. The key lay-out is similar as the
basset-clarinet (which is in A, not B flat). Confusing all this is ...
Not really ... ?
Wim van Dommelen m...@wimvd.nl writes:
On 7 Feb 2013, at 23:33 , Joseph Rushton Wakeling wrote:
That is not that easy, it is not ly-code, but Scheme code and
tougher (more and
more stacked upon another) as I expected. The basic files involved
are together
already 3200 lines (some are
But it also looks like we should look into autoload here. There is
no point loading this sort of baggage into every LilyPond run.
Does guile support autoload out of the box?
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
And hopefully loads once then :-)
Regards,
Wim.
On 8 Feb 2013, at 10:49 , Werner LEMBERG wrote:
But it also looks like we should look into autoload here. There is
no point loading this sort of baggage into every LilyPond run.
Does guile support autoload out of the box?
Werner
Werner LEMBERG w...@gnu.org writes:
But it also looks like we should look into autoload here. There is
no point loading this sort of baggage into every LilyPond run.
Does guile support autoload out of the box?
Seemingly in connection with modules.
--
David Kastrup
Does guile support autoload out of the box?
Seemingly in connection with modules.
IIRC, there are attempts to have lilypond modules as soon as we
migrate to guile2, so this would be a nice benefit...
Werner
___
lilypond-user mailing list
Werner LEMBERG w...@gnu.org writes:
Does guile support autoload out of the box?
Seemingly in connection with modules.
IIRC, there are attempts to have lilypond modules as soon as we
migrate to guile2, so this would be a nice benefit...
Reality check: the current codebase already uses
Hi Joseph, Mike,
I've looked into different brand/models (as far as my friends and
knowledge reaches) and had my thoughts on it (so it is may be not
exhausting enough!). Meanwhile I also studied the underlying code
(which is both daunting and haunting) and I see the following model(s)
On 02/07/2013 02:26 PM, Wim van Dommelen wrote:
clarinet-family -- clarinet (what we have now, but without the hole)
hole ? I guess you mean the extra touchpiece on the LH 1st finger?
Ideally you'd like to have some backwards compatibility, so I suggest keeping
clarinet for the base
On 7 Feb 2013, at 18:46 , Joseph Rushton Wakeling wrote:
On 02/07/2013 02:26 PM, Wim van Dommelen wrote:
clarinet-family -- clarinet (what we have now, but without the
hole)
hole ? I guess you mean the extra touchpiece on the LH 1st
finger?
Internally it is coded as hole, h :-)
On 02/07/2013 09:22 PM, Wim van Dommelen wrote:
Mmmh, that (lh . (gis)) is already taken for the upper key, using the same, not
completly describing name will again confuse others.
OK, fair enough, clarinet-lh-low-gis is better, then.
I'd use clarinet-full-boehm as the name for the clarinet
12 matches
Mail list logo
