csound score helpers
| Date | 2007-09-05 20:34 |
| From | "Steven Yi" |
| Subject | Re: csound score helpers |
| Attachments | None |
| Date | 2007-09-05 20:45 |
| From | "Michael Rhoades" |
| Subject | Re: csound score helpers |
|
FWIW, I use Excel for score editing, manipulation and creation. It allows for both vertical and horizontal editing of sections of data plus allows me to use formulae and macros for transpositions and etc. I simply do my saves as text files…
-----Original Message-----
I am trying out scot.. is there anything similar to it? what do people use as text based score language usually? is using scot a good idea? not that there is anything wrong with scot just that it seems abandoned and i cant find a decent manual for it. No virus found in this incoming message. |
| Date | 2007-09-06 12:41 |
| From | Tim Mortimer |
| Subject | Re: csound score helpers |
Yep, at the risk of banging on like a broken record....
i've currently developing my own score language which executes csound score
via Python (including midi via csound sco also as a further option...)
more or less based on Csound score, but souped up with many additional
features other useful bits i've wanted over the last few years,
i run my score through a python script & bam! convoluted Feldmanian
conniptions of gaussified csound score out the other end.
just implemented a basic tempo system for it this eve. tempo ramping being
the next step.
heres an example few bars that targets garritan to give you some idea
optionally putting durations & start times in num/denom aka "timesignature"
style notation also will be something to come in the near future...
obviously if the tabbing was all correct it'd look a bit neaterer.
i've been writing the scores in txt using scite. if u copy & paste it in the
formatting might line up for you.
i actually came to csound to try & sort out my score writing dilemmas. piano
roll wasn't cutting it on so many levels.
but for me, python is definately where it's all coming to fruition.
so you may not like this below, but it does hopefully illustrate an example
of how python can allow you to massage score into whatever format u find
useful
a brief legend:
t = tied note
le = legato
GC = global controller (for poly instruments) mono instruments have their
controllers linked to the note duration
linearbkpts defined in {....} (probably define expsegs in [...] & transegs
in (...) eventually..)
the n:n stuff is to log analysis of the scores in a "pattern book" - so you
can algorithmically generate more material, & go looking for existing
similarities....
pitches expressed in oct pchint
times expressed in milliseconds
~ = take value from previous
there are other codes & symbols too, not used in the example below....
1:1
0 violin1 mute
0 violin2 mute
0 cello mute
0 dbass mute
0 vibes sus on
0 vibes GC 100 VibD{50}
0 vibes GC 100 VibS{50}
0 coangl 9 08 3250 pp {0:pp,-1000:~,e:si}
0 violin2 9 08 3250 pp {0:si,1000:pppp,-1000:~,e:si}
0 oboe 9 11 3250 pp {0:pp,-1000:~,e:si}
0 clar1 8 11 3250 pp {0:pp,-1000:~,e:si}
0 horn2 8 11 3250 pp {0:pp,-1000:~,e:si}
0 horn1 7 07 3250 pp {0:pp,-1000:~,e:si}
0 bclar 6 07 3250 pp {0:pp,-1000:~,e:si}
0 contrab 5 07 3250 pp {0:pp,-1000:~,e:si}
0 cello 6 07 3250 pp {0:pp,-1000:~,e:si}
0 dbass 5 07 3250 pp {0:pp,-1000:~,e:si}
13/16
#(3250)
1:2
0 coangl 9 07 1750 pp {0:pp,-1000:~,e:si}
0 violin2 9 07 1750 pp {0:si,500:pppp,-1000:~,e:si}
0 oboe 9 08 1750 pp {0:pp,-1000:~,e:si}
0 clar1 8 08 1750 pp {0:pp,-1000:~,e:si}
0 horn2 8 08 1750 pp {0:pp,-1000:~,e:si}
0 horn1 7 11 1750 pp {0:pp,-1000:~,e:si}
0 bclar 6 11 1750 pp {0:pp,-1000:~,e:si}
0 contrab 5 11 1750 pp {0:pp,-1000:~,e:si}
0 cello 6 11 1750 pp {0:pp,-1000:~,e:si}
0 dbass 5 11 1750 pp {0:pp,-1000:~,e:si}
0 violin1 9 02 le:40 fff {pppp} PB{0:-1,50:0}
0 vibes 8 02 500 pp
250 violin1 9 00 250 fff {~}
250 vibes 8 00 500 pp
500 violin1 9 05 le:40 fff {~} PB{0:-1,50:0}
500 vibes 8 05 500 pp
750 violin1 9 03 250 fff {~}
750 vibes 8 03 500 pp
1000 violin1 9 10 500 fff {0:~,500:si}
1000 vibes 8 10 500 pp
7/16
#(1750)
1:3
0 coangl 9 11 3250 pp {0:pp,-1000:~,e:si}
0 violin2 9 11 3250 pp {0:si,1000:pppp,-1000:~,e:si}
0 oboe 9 07 3250 pp {0:pp,-1000:~,e:si}
0 clar1 8 07 3250 pp {0:pp,-1000:~,e:si}
0 horn2 8 07 3250 pp {0:pp,-1000:~,e:si}
0 horn1 7 08 t pp {0:pp}
0 bclar 6 08 t pp {0:pp}
0 contrab 5 08 t pp {0:pp}
0 cello 6 08 t pp {0:pp}
0 dbass 5 08 t pp {0:pp}
13/16
#(3250)
1:4
0 coangl 9 07 1750 pp {0:pp,-1000:~,e:si}
0 violin2 9 07 1750 pp {0:si,500:pppp,-1000:~,e:si}
0 oboe 9 11 1750 pp {0:pp,-1000:~,e:si}
0 clar1 8 11 1750 pp {0:pp,-1000:~,e:si}
0 horn2 8 11 1750 pp {0:pp,-1000:~,e:si}
0 horn1 7 08 1750 pp {0:~,-1000:~,e:si}
0 bclar 6 08 1750 pp {0:~,-1000:~,e:si}
0 contrab 5 08 1750 pp {0:~,-1000:~,e:si}
0 cello 6 08 1750 pp {0:~,-1000:~,e:si}
0 dbass 5 08 1750 pp {0:~,-1000:~,e:si}
0 violin1 10 02 le:40 fff {pppp} PB{0:-1,50:0}
0 vibes 9 02 500 pp
250 violin1 10 00 250 fff {~}
250 vibes 9 00 500 pp
500 violin1 10 05 le:40 fff {~} PB{0:-1,50:0}
500 vibes 9 05 500 pp
750 violin1 10 03 250 fff {~}
750 vibes 9 03 500 pp
1000 violin1 10 10 500 fff {0:~,500:si}
1000 vibes 9 10 500 pp
7/16
#(1750)
1:5
0 coangl 9 08 3250 pp {0:pp,-1000:~,e:si}
0 violin2 9 08 3250 pp {0:si,1000:pppp,-1000:~,e:si}
0 oboe 9 07 3250 pp {0:pp,-1000:~,e:si}
0 clar1 8 07 3250 pp {0:pp,-1000:~,e:si}
0 horn2 8 07 3250 pp {0:pp,-1000:~,e:si}
0 horn1 7 08 1750 pp {0:pp,-1000:~,e:si}
0 bclar 6 11 3250 pp {0:pp,-1000:~,e:si}
0 contrab 5 11 3250 pp {0:pp,-1000:~,e:si}
0 cello 6 11 3250 pp {0:pp,-1000:~,e:si}
0 dbass 5 11 3250 pp {0:pp,-1000:~,e:si}
3250 vibes sus off
13/16
#(3250)
0 EOF
Steven Yi wrote:
>
> You might want to try nGen, Cmask, or Common Music. For myself, I
> typically use straight score or python code (in conjunction with
> blue).
>
> On 9/5/07, phundamental unaudio |
| Date | 2007-09-08 22:00 |
| From | "Steven Yi" |
| Subject | Re: csound score helpers |
| Attachments | None |
| Date | 2007-09-08 22:28 |
| From | Dave Seidel |
| Subject | Re: csound score helpers |
Hey Tim,
This looks really cool, expressive but (it appears) at least as easily
parse-able as the canonic score language. I hope you're thinking in
terms of making this code available in a form that could be plugged into
programs like blue as a score-preprocessor -- as long as there's a
text-in/text-out interface, I should think it would be doable.
- Dave
Tim Mortimer wrote:
> Yep, at the risk of banging on like a broken record....
>
> i've currently developing my own score language which executes csound score
> via Python (including midi via csound sco also as a further option...)
>
> more or less based on Csound score, but souped up with many additional
> features other useful bits i've wanted over the last few years,
>
> i run my score through a python script & bam! convoluted Feldmanian
> conniptions of gaussified csound score out the other end.
>
> just implemented a basic tempo system for it this eve. tempo ramping being
> the next step.
>
> heres an example few bars that targets garritan to give you some idea
>
> optionally putting durations & start times in num/denom aka "timesignature"
> style notation also will be something to come in the near future...
>
> obviously if the tabbing was all correct it'd look a bit neaterer.
>
> i've been writing the scores in txt using scite. if u copy & paste it in the
> formatting might line up for you.
>
> i actually came to csound to try & sort out my score writing dilemmas. piano
> roll wasn't cutting it on so many levels.
>
> but for me, python is definately where it's all coming to fruition.
>
> so you may not like this below, but it does hopefully illustrate an example
> of how python can allow you to massage score into whatever format u find
> useful
>
> a brief legend:
>
> t = tied note
> le = legato
> GC = global controller (for poly instruments) mono instruments have their
> controllers linked to the note duration
> linearbkpts defined in {....} (probably define expsegs in [...] & transegs
> in (...) eventually..)
>
> the n:n stuff is to log analysis of the scores in a "pattern book" - so you
> can algorithmically generate more material, & go looking for existing
> similarities....
>
> pitches expressed in oct pchint
>
> times expressed in milliseconds
>
> ~ = take value from previous
>
> there are other codes & symbols too, not used in the example below....
>
> 1:1
>
> 0 violin1 mute
> 0 violin2 mute
> 0 cello mute
> 0 dbass mute
>
> 0 vibes sus on
> 0 vibes GC 100 VibD{50}
> 0 vibes GC 100 VibS{50}
>
> 0 coangl 9 08 3250 pp {0:pp,-1000:~,e:si}
> 0 violin2 9 08 3250 pp {0:si,1000:pppp,-1000:~,e:si}
>
> 0 oboe 9 11 3250 pp {0:pp,-1000:~,e:si}
> 0 clar1 8 11 3250 pp {0:pp,-1000:~,e:si}
> 0 horn2 8 11 3250 pp {0:pp,-1000:~,e:si}
>
> 0 horn1 7 07 3250 pp {0:pp,-1000:~,e:si}
> 0 bclar 6 07 3250 pp {0:pp,-1000:~,e:si}
> 0 contrab 5 07 3250 pp {0:pp,-1000:~,e:si}
>
> 0 cello 6 07 3250 pp {0:pp,-1000:~,e:si}
> 0 dbass 5 07 3250 pp {0:pp,-1000:~,e:si}
>
> 13/16
> #(3250)
>
> 1:2
>
>
> 0 coangl 9 07 1750 pp {0:pp,-1000:~,e:si}
> 0 violin2 9 07 1750 pp {0:si,500:pppp,-1000:~,e:si}
>
> 0 oboe 9 08 1750 pp {0:pp,-1000:~,e:si}
> 0 clar1 8 08 1750 pp {0:pp,-1000:~,e:si}
> 0 horn2 8 08 1750 pp {0:pp,-1000:~,e:si}
>
> 0 horn1 7 11 1750 pp {0:pp,-1000:~,e:si}
> 0 bclar 6 11 1750 pp {0:pp,-1000:~,e:si}
> 0 contrab 5 11 1750 pp {0:pp,-1000:~,e:si}
>
> 0 cello 6 11 1750 pp {0:pp,-1000:~,e:si}
> 0 dbass 5 11 1750 pp {0:pp,-1000:~,e:si}
>
> 0 violin1 9 02 le:40 fff {pppp} PB{0:-1,50:0}
> 0 vibes 8 02 500 pp
>
> 250 violin1 9 00 250 fff {~}
> 250 vibes 8 00 500 pp
>
> 500 violin1 9 05 le:40 fff {~} PB{0:-1,50:0}
> 500 vibes 8 05 500 pp
>
> 750 violin1 9 03 250 fff {~}
> 750 vibes 8 03 500 pp
>
> 1000 violin1 9 10 500 fff {0:~,500:si}
> 1000 vibes 8 10 500 pp
>
> 7/16
> #(1750)
>
> 1:3
>
> 0 coangl 9 11 3250 pp {0:pp,-1000:~,e:si}
> 0 violin2 9 11 3250 pp {0:si,1000:pppp,-1000:~,e:si}
>
> 0 oboe 9 07 3250 pp {0:pp,-1000:~,e:si}
> 0 clar1 8 07 3250 pp {0:pp,-1000:~,e:si}
> 0 horn2 8 07 3250 pp {0:pp,-1000:~,e:si}
>
> 0 horn1 7 08 t pp {0:pp}
> 0 bclar 6 08 t pp {0:pp}
> 0 contrab 5 08 t pp {0:pp}
>
> 0 cello 6 08 t pp {0:pp}
> 0 dbass 5 08 t pp {0:pp}
>
> 13/16
> #(3250)
>
> 1:4
>
>
> 0 coangl 9 07 1750 pp {0:pp,-1000:~,e:si}
> 0 violin2 9 07 1750 pp {0:si,500:pppp,-1000:~,e:si}
>
> 0 oboe 9 11 1750 pp {0:pp,-1000:~,e:si}
> 0 clar1 8 11 1750 pp {0:pp,-1000:~,e:si}
> 0 horn2 8 11 1750 pp {0:pp,-1000:~,e:si}
>
> 0 horn1 7 08 1750 pp {0:~,-1000:~,e:si}
> 0 bclar 6 08 1750 pp {0:~,-1000:~,e:si}
> 0 contrab 5 08 1750 pp {0:~,-1000:~,e:si}
>
> 0 cello 6 08 1750 pp {0:~,-1000:~,e:si}
> 0 dbass 5 08 1750 pp {0:~,-1000:~,e:si}
>
>
> 0 violin1 10 02 le:40 fff {pppp} PB{0:-1,50:0}
> 0 vibes 9 02 500 pp
>
> 250 violin1 10 00 250 fff {~}
> 250 vibes 9 00 500 pp
>
> 500 violin1 10 05 le:40 fff {~} PB{0:-1,50:0}
> 500 vibes 9 05 500 pp
>
> 750 violin1 10 03 250 fff {~}
> 750 vibes 9 03 500 pp
>
> 1000 violin1 10 10 500 fff {0:~,500:si}
> 1000 vibes 9 10 500 pp
>
> 7/16
> #(1750)
>
> 1:5
>
> 0 coangl 9 08 3250 pp {0:pp,-1000:~,e:si}
> 0 violin2 9 08 3250 pp {0:si,1000:pppp,-1000:~,e:si}
>
> 0 oboe 9 07 3250 pp {0:pp,-1000:~,e:si}
> 0 clar1 8 07 3250 pp {0:pp,-1000:~,e:si}
> 0 horn2 8 07 3250 pp {0:pp,-1000:~,e:si}
>
> 0 horn1 7 08 1750 pp {0:pp,-1000:~,e:si}
> 0 bclar 6 11 3250 pp {0:pp,-1000:~,e:si}
> 0 contrab 5 11 3250 pp {0:pp,-1000:~,e:si}
>
> 0 cello 6 11 3250 pp {0:pp,-1000:~,e:si}
> 0 dbass 5 11 3250 pp {0:pp,-1000:~,e:si}
>
> 3250 vibes sus off
>
> 13/16
> #(3250)
>
> 0 EOF
>
>
>
> Steven Yi wrote:
>> You might want to try nGen, Cmask, or Common Music. For myself, I
>> typically use straight score or python code (in conjunction with
>> blue).
>>
>> On 9/5/07, phundamental unaudio |
| Date | 2007-09-09 01:13 |
| From | Tim Mortimer |
| Subject | Re: csound score helpers |
Hi Dave,
The code can definately be made available to anyone who is interested.
Hopefully the payback for me is somebody can actually clean it up & improve
it substantially! "if" & the occasional "while" are about the limits of my
insight into python syntax & program workflow i'm afraid ; )
I'm still finding the occasional bug, & there's no error handling other than
what the interpreter prints to screen - my program is littered therefore
with "#" out print statements that can be revealed as needed to trace
errors.
The list of additions & changes i wish to make is ever growing, although as
of yesterday i think i have finally done enough with it to start composing
with the thing. & i have tried to structure it in such a way that Modules
can be added to handle generic statements in software / instrument specific
ways, so Absynth for example is one i might write a module for eventually.
even I have considered that armed with this, i could then begin to use Blue
as an "arrangement surface".....
Thanks for the expression of interest & vote of support. As someone who has
worked in a completely isolated & self driven way on music & ideas for a
number of years now, it makes me very happy to recieve advice & / or
encouragement from people on this list.
ps - i'm also looking forward to having this score sytem impose some sort of
standardisation on my Csound instrument design. Of what little i know of
Blue, this may well also be pretty compatible with it's ethos - as basically
any "controller" style statement {0:value,nn:valueetc...} will point to a
global variable in the Csound code. (just as Blue does with it's bkpt line
tools?)
it is possible to place multiple {...} statements on the one line of score
statement incidentally. the unlabeled bracket is my default syntax for an
amplitude related curve... others can be preceded by pan{....} etc....
there's also a wee little aleatory system generator that's part of the
package - & a "composition pitch set generator" that delivers a selection of
sets & all their union subsets from the PC universe to begin working with /
from.
Athena has been a big influence, but rather than concentrating on
flexibility - i wanted to begin to approach the exercise from the standpoint
of composition & a universally enforceable scoring convention.
Hey Tim,
This looks really cool, expressive but (it appears) at least as easily
parse-able as the canonic score language. I hope you're thinking in
terms of making this code available in a form that could be plugged into
programs like blue as a score-preprocessor -- as long as there's a
text-in/text-out interface, I should think it would be doable.
- Dave
Tim Mortimer wrote:
--
View this message in context: http://www.nabble.com/csound-score-helpers-tf4387590.html#a12574820
Sent from the Csound - General mailing list archive at Nabble.com. |