:harpsichord

Discussion:

:harpsichord

rob canning

2007-04-28 19:33:58 UTC

hi

i am writing a piece for a harpsichord with two manuals

part 1 :name "harpsichord" :abbrev "hpschd." :instr :harpsichord;

what is the best way to do this - atm i am sending :voice 1 and :voice 2
to send the two different parts to the two different manuals

both manuals start in bass clef and both climb in to treble clef -

the problem is the bottom stave stays in bass clef and the music jumps
into the manual 1 part.

i would like to be able to switch between single line cross-stave
writing and two part writing.

so to summarise... i want to lock voice two to stave two of :harpsichord
and have it so it changes into treble clef where necessary.

anyone know how to do this?

thanks

rob

once again...
many thanks for fomus i am finding it incredibly useful :)
very soon i hope to become very prolific ;)

David Psenicka

2007-04-28 20:49:42 UTC

Permalink

I've had a "force-staff" mark on the TODO list for a while--I think this
should solve your problem and should be quick to implement--update will
come shortly -DP

Post by rob canning
hi
i am writing a piece for a harpsichord with two manuals
part 1 :name "harpsichord" :abbrev "hpschd." :instr :harpsichord;
what is the best way to do this - atm i am sending :voice 1 and :voice
2 to send the two different parts to the two different manuals
both manuals start in bass clef and both climb in to treble clef -
the problem is the bottom stave stays in bass clef and the music jumps
into the manual 1 part.
i would like to be able to switch between single line cross-stave
writing and two part writing.
so to summarise... i want to lock voice two to stave two of
:harpsichord and have it so it changes into treble clef where necessary.
anyone know how to do this?
thanks
rob
once again...
many thanks for fomus i am finding it incredibly useful :)
very soon i hope to become very prolific ;)
_______________________________________________
fomus-devel mailing list
http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel

rob canning

2007-05-16 14:55:32 UTC

Permalink

hi,

in the mean time how do i create an :instrument ? is there a file full
of all the definitions somewhere i can't add to?

i need to create an instrument that jumps between bass and treble clef
on one stave - most instruments i have tried so far go into tenor or
alto clef on the way

also with :force-staff it would be nice to be able to change this "on
the fly" like :timesig
so that for example four bars of harpsichord or piano could be
cross-stave single voice and then four bars could be two part staff-forced.

thanks

rob

Post by David Psenicka
I've had a "force-staff" mark on the TODO list for a while--I think this
should solve your problem and should be quick to implement--update will
come shortly -DP

_______________________________________________
fomus-devel mailing list
http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel

David Psenicka

2007-05-23 21:18:22 UTC

Permalink

Sorry for the long delay!--You can do this when you specify an
instrument for a part (this would go in the input file):

PART 1 :name "Harpsichord" :instr (:harpsichord :staves 1 :clefs
(:treble :bass))

the (:treble :bass) is unnecessary because it's the default for that
instrument anyways (those are the possible clefs for that
instrument)--the :staves 1 modifies it so there's only one staff

You can also put in a line like this:

INIT :instruments ((MAKE-INSTR :myinst :clefs (:treble :bass) :staves 2
:minp nil :maxp nil :simultlim nil :tpose 0 :cleflegls 2 :8uplegls nil
:8dnlegls nil :percs nil :midiprgch-im nil :midiprgch-ex nil))

which defines an instrument with ID :myinst that's added to the
predefined list (those are all of the options, you probably only need to
specify :clefs and :staves).

Also, you can put something like this in a file named .fomus in your
home directory:

:instruments (list (make-instr :myinst :clefs '(:treble :bass) :staves 2
:minp nil :maxp nil :simultlim nil
:tpose 0 :cleflegls 2 :8uplegls nil :8dnlegls nil :percs
nil :midiprgch-im nil :midiprgch-ex nil))

This adds :myinst to the predefined list everytime fomus loads (also you
can override existing instrument by using the same ID--if you call it
:harpsichord it will override the existing :harpsichord)--you can put as
many (make-instr ...) calls inside the enclosing (list ...)

The development branch has an almost working :staff mark (you use it by
specifying (:staff 1) in each note or (:startstaff- 1) then :endstaff-
over a range of notes)--it's "almost" working because it's still
stubborn about certain things (like when only one or two notes cross
staves)... but at any rate the :staff mark should be usable at this point

Post by rob canning
hi,
in the mean time how do i create an :instrument ? is there a file full
of all the definitions somewhere i can't add to?
i need to create an instrument that jumps between bass and treble clef
on one stave - most instruments i have tried so far go into tenor or
alto clef on the way
also with :force-staff it would be nice to be able to change this "on
the fly" like :timesig
so that for example four bars of harpsichord or piano could be
cross-stave single voice and then four bars could be two part
staff-forced.
thanks
rob

Post by David Psenicka
I've had a "force-staff" mark on the TODO list for a while--I think this
should solve your problem and should be quick to implement--update will
come shortly -DP

_______________________________________________
fomus-devel mailing list
http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel

David Psenicka

2007-05-25 05:30:32 UTC

Permalink

v0.2.26
Improvements to spanners
Some documentation that can be called up by the Lisp DOCUMENTATION
function
:STAFF, :STARTSTAFF-, :STAFF-, :ENDSTAFF- marks to override staff
choices

rob canning

2007-06-19 17:25:45 UTC

Permalink

hi!

i can't figure out how to get at the lisp documentation (i never use
lisp directly)

could someone help me out with an example...

how to force the low A appearing in the lower staff to appear in the
upper staff with the relevant clef change

part 1 :name "harpsichord" :abbrev "harpsichord" :instr :harpsichord;

(note 1 :voice 2 :off 0 :dur 0.25 :notes (45) :marks (:staccato :ppp));
(note 1 :voice 2 :off 0.5 :dur 0.25 :notes (86) :marks (:staccato));

can this be done as a :mark or does it have to be set as an :init default

it would nice to see an example of a bar of single line cross stave
writing followed by a bar of two part :staff forced writing with both
staffs exploiting both bass and treble clef

thanks

rob

Post by David Psenicka
v0.2.26
Improvements to spanners
Some documentation that can be called up by the Lisp DOCUMENTATION
function
:STAFF, :STARTSTAFF-, :STAFF-, :ENDSTAFF- marks to override staff
choices
_______________________________________________
fomus-devel mailing list
http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel

d***@public.gmane.org

2007-06-20 09:06:04 UTC

Permalink

Rob,

The lisp documentation won't be helpful at all unless you work with lisp--lisp
has a built in function "describe" that calls up brief documentation strings for
functions if they exist

You can force the staff using a :STAFF mark (like this: (:staff 1) or (:staff 2)
--you should also be able to specify a choice (:staff 1 2) (:staff 2 3) (maybe
useful for notating a piano part onto 3 staves, etc..) Soon it'll get easier as I put
some of these things into parts and instruments--right now you have to stick it
in every note or put (:startstaff- 1) in the very first note

I'll put more examples up soon (plus organize the ones that are there now) The
examples pages will soon evolve into an indexed list with keywords (click on
"staves" and see three or four examples of how to control staves, etc..)

Since I'm (slowly) getting in the last of the main feature I originally wanted to
put in, I'd be curious to know what I should start improving in general (besides
documentation)... Here is my list in more or less order of priority:

Finishing up:
Polymeters (I'm getting to this now...)
"Chunks" (should be working now--can use them to output different sections of
the score with completely different settings)

Improvements:
tuplets (finding, notating correctly, etc.)
speed (large orchestra-size score still can take a while, especially if the notation
is complex--I've thought of porting the whole program but I don't think it's
worth the effort)

Additions:
FOMUS as a Finale plugin (as an alternative to XML importing)
GUI interface showing updated score samples
structures such as "chord," "sequence" or other similar structures that will make
it easier to specify information more efficiently

-David

---- Original message ----

Date: Tue, 19 Jun 2007 17:25:45 +0000
Subject: :staff
hi!
i can't figure out how to get at the lisp documentation (i never use
lisp directly)
could someone help me out with an example...
how to force the low A appearing in the lower staff to appear in the
upper staff with the relevant clef change
part 1 :name "harpsichord" :abbrev "harpsichord" :instr :harpsichord;
(note 1 :voice 2 :off 0 :dur 0.25 :notes (45) :marks (:staccato :ppp));
(note 1 :voice 2 :off 0.5 :dur 0.25 :notes (86) :marks (:staccato));
can this be done as a :mark or does it have to be set as an :init default
it would nice to see an example of a bar of single line cross stave
writing followed by a bar of two part :staff forced writing with both
staffs exploiting both bass and treble clef
thanks
rob

rob canning

2007-06-20 14:58:41 UTC

Permalink

hi david,
this example using :staff doesn't seem to work as i think it should...
it seems that it doesn't obey the :staff mark unless there is nothing
going on at the same offset time - at the last note for example. i have
even tried putting the parts in different voices but they still seem to
interfere with one another.
thanks
rob

(init :output ((:musicxml-finale :filename "test.xml")(:lilypond :view
t)) :filename "test" :title "test" :subtitle
"for-harpsichord-and-prepared-piano"
:composer "rob canning" :auto-accidentals NIL :auto-cautionary-accs
t :tuplet-style :ratio :verbose 2 :max-tuplet 11);
TIMESIG :OFF 0 :TIME (4 4);
part 1 :name "harpsichord" :abbrev "harpsichord" :instr :harpsichord
;
(note 1 :voice 2 :off 0 :dur 0.25 :notes (84) :marks (:staccato :ppp
(:staff 2)));
(note 1 :voice 1 :off 0 :dur 0.5 :notes (81) :marks (:staccato :ppp
(:staff 1)));
(note 1 :voice 2 :off 0.25 :dur 0.25 :notes (85) :marks (:staccato
:ppp (:staff 2)));
(note 1 :voice 1 :off 0.5 :dur 0.25 :notes (83) :marks (:staccato :ppp
(:staff 1)));
(note 1 :voice 2 :off 0.5 :dur 0.25 :notes (86) :marks (:staccato :ppp
(:staff 2)));
(note 1 :voice 1 :off 0.75 :dur 0.25 :notes (84) :marks (:staccato
:ppp (:staff 1)));
(note 1 :voice 2 :off 0.75 :dur 0.25 :notes (87) :marks (:staccato
:ppp (:staff 2)));
(note 1 :voice 1 :off 1 :dur 0.25 :notes (86) :marks (:staccato :ppp
(:staff 1)));
(note 1 :voice 2 :off 1 :dur 0.25 :notes (88) :marks (:staccato :ppp
(:staff 2)));
(note 1 :voice 1 :off 1.25 :dur 0.25 :notes (89) :marks (:staccato
:ppp (:staff 1)));
(note 1 :voice 2 :off 1.25 :dur 0.25 :notes (89) :marks (:staccato
:ppp (:staff 2)));
(note 1 :voice 1 :off 1.5 :dur 0.25 :notes (80) :marks (:staccato :ppp
(:staff 1)));
(note 1 :voice 2 :off 1.5 :dur 0.25 :notes (90) :marks (:staccato :ppp
(:staff 2)));
(note 1 :voice 1 :off 1.75 :dur 0.25 :notes (81) :marks (:staccato
:ppp (:staff 1)));
(note 1 :voice 2 :off 1.75 :dur 0.25 :notes (91) :marks (:staccato
:ppp (:staff 2)));
(note 1 :voice 1 :off 2 :dur 0.25 :notes (83) :marks (:staccato :ppp
(:staff 1)));

Post by d***@public.gmane.org
Rob,
The lisp documentation won't be helpful at all unless you work with lisp--lisp
has a built in function "describe" that calls up brief documentation strings for
functions if they exist
You can force the staff using a :STAFF mark (like this: (:staff 1) or (:staff 2)
--you should also be able to specify a choice (:staff 1 2) (:staff 2 3) (maybe
useful for notating a piano part onto 3 staves, etc..) Soon it'll get easier as I put
some of these things into parts and instruments--right now you have to stick it
in every note or put (:startstaff- 1) in the very first note
I'll put more examples up soon (plus organize the ones that are there now) The
examples pages will soon evolve into an indexed list with keywords (click on
"staves" and see three or four examples of how to control staves, etc..)
Since I'm (slowly) getting in the last of the main feature I originally wanted to
put in, I'd be curious to know what I should start improving in general (besides
Polymeters (I'm getting to this now...)
"Chunks" (should be working now--can use them to output different sections of
the score with completely different settings)
tuplets (finding, notating correctly, etc.)
speed (large orchestra-size score still can take a while, especially if the notation
is complex--I've thought of porting the whole program but I don't think it's
worth the effort)
FOMUS as a Finale plugin (as an alternative to XML importing)
GUI interface showing updated score samples
structures such as "chord," "sequence" or other similar structures that will make
it easier to specify information more efficiently
-David
---- Original message ----

_______________________________________________
fomus-devel mailing list
http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel

d***@public.gmane.org

2007-06-25 10:10:51 UTC

Permalink

I have a fix in the dev. branch now--once I get a change to test it a bit more I'll
wrap up another tarball

---- Original message ----

Date: Wed, 20 Jun 2007 14:58:41 +0000
Subject: Re: [fomus-devel] Re: :staff
hi david,
this example using :staff doesn't seem to work as i think it should...
it seems that it doesn't obey the :staff mark unless there is nothing
going on at the same offset time - at the last note for example. i have
even tried putting the parts in different voices but they still seem to
interfere with one another.
thanks
rob
(init :output ((:musicxml-finale :filename "test.xml")(:lilypond :view
t)) :filename "test" :title "test" :subtitle
"for-harpsichord-and-prepared-piano"
:composer "rob canning" :auto-accidentals NIL :auto-cautionary-accs
t :tuplet-style :ratio :verbose 2 :max-tuplet 11);
TIMESIG :OFF 0 :TIME (4 4);
part 1 :name "harpsichord" :abbrev "harpsichord" :instr :harpsichord
;
(note 1 :voice 2 :off 0 :dur 0.25 :notes (84) :marks (:staccato :ppp
(:staff 2)));
(note 1 :voice 1 :off 0 :dur 0.5 :notes (81) :marks (:staccato :ppp
(:staff 1)));
(note 1 :voice 2 :off 0.25 :dur 0.25 :notes (85) :marks (:staccato
:ppp (:staff 2)));
(note 1 :voice 1 :off 0.5 :dur 0.25 :notes (83) :marks (:staccato :ppp
(:staff 1)));
(note 1 :voice 2 :off 0.5 :dur 0.25 :notes (86) :marks (:staccato :ppp
(:staff 2)));
(note 1 :voice 1 :off 0.75 :dur 0.25 :notes (84) :marks (:staccato
:ppp (:staff 1)));
(note 1 :voice 2 :off 0.75 :dur 0.25 :notes (87) :marks (:staccato
:ppp (:staff 2)));
(note 1 :voice 1 :off 1 :dur 0.25 :notes (86) :marks (:staccato :ppp
(:staff 1)));
(note 1 :voice 2 :off 1 :dur 0.25 :notes (88) :marks (:staccato :ppp
(:staff 2)));
(note 1 :voice 1 :off 1.25 :dur 0.25 :notes (89) :marks (:staccato
:ppp (:staff 1)));
(note 1 :voice 2 :off 1.25 :dur 0.25 :notes (89) :marks (:staccato
:ppp (:staff 2)));
(note 1 :voice 1 :off 1.5 :dur 0.25 :notes (80) :marks (:staccato :ppp
(:staff 1)));
(note 1 :voice 2 :off 1.5 :dur 0.25 :notes (90) :marks (:staccato :ppp
(:staff 2)));
(note 1 :voice 1 :off 1.75 :dur 0.25 :notes (81) :marks (:staccato
:ppp (:staff 1)));
(note 1 :voice 2 :off 1.75 :dur 0.25 :notes (91) :marks (:staccato
:ppp (:staff 2)));
(note 1 :voice 1 :off 2 :dur 0.25 :notes (83) :marks (:staccato :ppp
(:staff 1)));

Post by d***@public.gmane.org
Rob,
The lisp documentation won't be helpful at all unless you work with lisp--

lisp

Post by d***@public.gmane.org
has a built in function "describe" that calls up brief documentation strings

for

Post by d***@public.gmane.org
functions if they exist
You can force the staff using a :STAFF mark (like this: (:staff 1) or (:staff

Post by d***@public.gmane.org
--you should also be able to specify a choice (:staff 1 2) (:staff 2 3)

(maybe

Post by d***@public.gmane.org
useful for notating a piano part onto 3 staves, etc..) Soon it'll get easier as I

put

Post by d***@public.gmane.org
some of these things into parts and instruments--right now you have to

stick it

Post by d***@public.gmane.org
in every note or put (:startstaff- 1) in the very first note
I'll put more examples up soon (plus organize the ones that are there now)

The

Post by d***@public.gmane.org
examples pages will soon evolve into an indexed list with keywords (click on
"staves" and see three or four examples of how to control staves, etc..)
Since I'm (slowly) getting in the last of the main feature I originally wanted to
put in, I'd be curious to know what I should start improving in general

(besides

Post by d***@public.gmane.org
Polymeters (I'm getting to this now...)
"Chunks" (should be working now--can use them to output different

sections of

Post by d***@public.gmane.org
the score with completely different settings)
tuplets (finding, notating correctly, etc.)
speed (large orchestra-size score still can take a while, especially if the

notation

Post by d***@public.gmane.org
is complex--I've thought of porting the whole program but I don't think it's
worth the effort)
FOMUS as a Finale plugin (as an alternative to XML importing)
GUI interface showing updated score samples
structures such as "chord," "sequence" or other similar structures that will

make

Post by d***@public.gmane.org
it easier to specify information more efficiently
-David
---- Original message ----

Post by David Psenicka
v0.2.26
Improvements to spanners
Some documentation that can be called up by the Lisp

DOCUMENTATION

Post by d***@public.gmane.org

Post by David Psenicka
function
:STAFF, :STARTSTAFF-, :STAFF-, :ENDSTAFF- marks to override staff
choices
_______________________________________________
fomus-devel mailing list
http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel

_______________________________________________
fomus-devel mailing list
http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel

rob canning

2007-06-27 15:00:14 UTC

Permalink

Post by d***@public.gmane.org
I have a fix in the dev. branch now--once I get a change to test it a bit more I'll
wrap up another tarball

thanks david thats working well for me now
rob

Post by d***@public.gmane.org
---- Original message ----

Post by d***@public.gmane.org
Rob,
The lisp documentation won't be helpful at all unless you work with lisp--

lisp

Post by d***@public.gmane.org
has a built in function "describe" that calls up brief documentation strings

for

Post by d***@public.gmane.org
functions if they exist
You can force the staff using a :STAFF mark (like this: (:staff 1) or (:staff

Post by d***@public.gmane.org
--you should also be able to specify a choice (:staff 1 2) (:staff 2 3)

(maybe

Post by d***@public.gmane.org
useful for notating a piano part onto 3 staves, etc..) Soon it'll get easier as I

put

Post by d***@public.gmane.org
some of these things into parts and instruments--right now you have to

stick it

Post by d***@public.gmane.org
in every note or put (:startstaff- 1) in the very first note
I'll put more examples up soon (plus organize the ones that are there now)

The

(besides

Post by d***@public.gmane.org
Polymeters (I'm getting to this now...)
"Chunks" (should be working now--can use them to output different

sections of

Post by d***@public.gmane.org
the score with completely different settings)
tuplets (finding, notating correctly, etc.)
speed (large orchestra-size score still can take a while, especially if the

notation

make

Post by d***@public.gmane.org
it easier to specify information more efficiently
-David
---- Original message ----

Post by David Psenicka
v0.2.26
Improvements to spanners
Some documentation that can be called up by the Lisp

DOCUMENTATION

Post by d***@public.gmane.org

_______________________________________________
fomus-devel mailing list
http://common-lisp.net/cgi-bin/mailman/listinfo/fomus-devel

rob canning

2007-06-27 15:11:49 UTC

Permalink

it might be useful (well it would be for me ;)) to have a feature that
creates a rest if, for example, an x is placed in (:notes(x))
which will take all the same :marks as a note

(note 1 :voice 1 :off 0 :dur 0.25 :notes (x) :marks (:staccato :ppp
(:staff 1 2)));

this way one could create scales or modes which include rests which
would be handy (for the way i'm working at least).

perhaps putting articulations or dynamics on rests is not allowed in
lilypond - if its not maybe it could just ignore them and create a naked
rest rather than creating an error

i know the other methods of creating rests but perhaps this alternative
might be handy

just a thought

thanks

rob

rob canning

2007-06-27 15:42:29 UTC

Permalink

also a :text mark that stays attached to a note once imported into
finale via xml would be nice

and maybe a :text mark that creates text as articulations in finale -
this way some analytical data that i like to write to my score can be in
finale in a "display on screen only - do not print)" mode

again just a thought

thanks

rob