18 months ago it was suggested to me that a simple score language
might be of interest, and so I created one following earlier macro
packages.  I think I never did much with it, but now on holiday \nd
with composer's block, I have dusted off and improved the language.

It is called Beats, and I have written a manual chapter for it.
Basically it  has only 4 kinds of statement:

         beats = 120      // bpm; bpm = 120 is also allowed
         permeasure = 6   // beats in a bar
         i 123  // a note event
         end              // ...
         quit             // these two are the same and end


a note attribute can be any of
  amplitude      {fff,ff,f,mf,mp,p,pp,ppp}
  pitch          {Abb, Ab, A, A#, Ax, Bbb, Bb, B, B#, Bx, Cbb, Cb, C,
                  C#, Cx, Dbb, Db, D, D#, Dx, Ebb, Eb, E, E#, Ex, Fbb,
                  Fb, F, F#, Fx, Gbb, Gb, G, G#, Gx, R, Z} followed by octave
                  Z and R are rests
  duration       {ed,et,e,hd,ht,h,qd,qt,q,sd,st,s,th,w}
  measure        m 
  beat           b 

Repeated durations add (or one can say s+e as + is treated as white space)
If any are omitted they are repeated from previous except that beats
add the duration.

A simple (tweaked for educational purposes) example below.  Can be
used with the  form.

Any suggestions for improvements welcome; some may be acted upon.  I
am aware of a lack of f tables in the score for example, but am not
sure the best way to do it.

==John ffitch

; Bach - Goldberg Variations - Variato 3
; by Brian Baughn 3-14-05
; bbaughn@berklee.net
beats = 120
permeasure = 6

i101    m1 b1 B4 mp qd+s
i101          C5    s
i101          D5
i101          C5
i101          D5
i101          E5
i101          A4    qd+s
i101          B4    s
i101          C5
i101          B4
i101          C5
i101          D5

i101    m2 b1 G4    qd
i101          G5    qd+e
i101          A5    s
i101          G5
i101          F#5
i101          G5
i101          A5    e

i101  m3 b1.5 D5    s
i101          C5
i101          B4
i101          A4
i101          B4    e
i101          C5    s
i101          B4
i101          A4
i101          B4
i101          G4    e
i101          E5
i101          D5
i101          C5
i101          F#5
i101          A5

i101  m4 b1   B4    q
i101          G5    e
i101          G5    q
i101          F#5   e
i101          Z     e   // Z is a rest (zzzzz..)
i101                e
i101          B5    e
i101          A5    q
i101          D5    e

end

------------------------------------------------------------------------
or complete....





sr      =           44100
nchnls 	= 		2

gi1 ftgen 1, 0, 4096, 10, 1
gi2 ftgen 2, 0, 4096, 7, -1, 4096, 1    ; sawtooth
gi3 ftgen 3, 0, 4096, 7,  0, 1024, 1, 2048, -1, 1024, 0  ;triangle

instr 101,102,103
  iamp =      ampdbfs(p5)
  a1   oscil  iamp, p4, p1-100
  kenv expseg 1, p3, .01
  a1   =      a1 * kenv
       outs   a1, a1
endin
 


; by Brian Baughn 3-14-05
; bbaughn@berklee.net

beats = 100
permeasure = 4

i101    m1 b1   q    mp   D3
i101                      F3
i101                      D3

i101    m2 b1             D3
i101       b3             D3

i101    m3 b1             D3
i101                      F3
i101                      D3

i101    m4 b1             D3
i101       b3             D3

i101    m5 b1             D3
i101       b4             G5

i101    m6 b1             E5
i101       b2             F5
i101       b3     e       Eb5
i101       b3.5   e          
i101       b4     q          

i101    m7 b1     e       D5
i101                            
i101                q          
i101                e     Db5
i101                            
i101                q          

i101    m8 b1     q       D5
i101                      E5
i101                      D5

i102    m1 b2      q      D4
i102       b4             E4
i102       b4             Bb3

i102    m2 b2             F4
i102       b2             B3
i102       b4             C#4
i102       b4             Bb3

i102    m3 b2      q      D4
i102       b4             E4
i102       b4             Bb3

i102    m4 b2             F4
i102       b2             B3
i102       b4             C#4
i102       b4             Bb3

i103    m5 b2      e     F6
i103       b2      e     A5
i103       b2.5    e     D6
i103       b3      e     F6
i103       b3      e     A5
i103       b4      e     E6

i103    m6 b1      q     C#6
i103               q     D6
i103               e     C6
i103                           
i103               q        

i103    m7 b1      e     B5
i103                            
i103                 q         
i103                 e    Bb5
i103                            
i103                 q         

i103     m8 b1     e     F5
i103        b1     e     A5
i103        b1.5   e     D6
i103        b2     e    Bb5
i103        b2.5   e     D6
i103        b3     q     F5
i103        b3           A5
end





Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

John,

You should take more vacations!

WOW.

This is great.

And all the bug fixes too.  WOW.

Welcome back after having what seems like a great recharge.

Good luck too with your composing.

Sending a thousand of the most perfect "score-events" in your direction
to get things rolling again, and hoping that they catch you and light  
a fire
in your most beautiful soul.

Rick

On Sep 19, 2010, at 7:02 AM, john ffitch wrote:

> 18 months ago it was suggested to me that a simple score language
> might be of interest, and so I created one following earlier macro
> packages.  I think I never did much with it, but now on holiday \nd
> with composer's block, I have dusted off and improved the language.
>
> It is called Beats, and I have written a manual chapter for it.
> Basically it  has only 4 kinds of statement:
>
>         beats = 120      // bpm; bpm = 120 is also allowed
>         permeasure = 6   // beats in a bar
>         i 123  // a note event
>         end              // ...
>         quit             // these two are the same and end
>
>
> a note attribute can be any of
>  amplitude      {fff,ff,f,mf,mp,p,pp,ppp}
>  pitch          {Abb, Ab, A, A#, Ax, Bbb, Bb, B, B#, Bx, Cbb, Cb, C,
>                  C#, Cx, Dbb, Db, D, D#, Dx, Ebb, Eb, E, E#, Ex, Fbb,
>                  Fb, F, F#, Fx, Gbb, Gb, G, G#, Gx, R, Z} followed  
> by octave
>                  Z and R are rests
>  duration       {ed,et,e,hd,ht,h,qd,qt,q,sd,st,s,th,w}
>  measure        m 
>  beat           b 
>
> Repeated durations add (or one can say s+e as + is treated as white  
> space)
> If any are omitted they are repeated from previous except that beats
> add the duration.
>
> A simple (tweaked for educational purposes) example below.  Can be
> used with the  form.
>
> Any suggestions for improvements welcome; some may be acted upon.  I
> am aware of a lack of f tables in the score for example, but am not
> sure the best way to do it.
>
> ==John ffitch
>
> ; Bach - Goldberg Variations - Variato 3
> ; by Brian Baughn 3-14-05
> ; bbaughn@berklee.net
> beats = 120
> permeasure = 6
>
> i101    m1 b1 B4 mp qd+s
> i101          C5    s
> i101          D5
> i101          C5
> i101          D5
> i101          E5
> i101          A4    qd+s
> i101          B4    s
> i101          C5
> i101          B4
> i101          C5
> i101          D5
>
> i101    m2 b1 G4    qd
> i101          G5    qd+e
> i101          A5    s
> i101          G5
> i101          F#5
> i101          G5
> i101          A5    e
>
> i101  m3 b1.5 D5    s
> i101          C5
> i101          B4
> i101          A4
> i101          B4    e
> i101          C5    s
> i101          B4
> i101          A4
> i101          B4
> i101          G4    e
> i101          E5
> i101          D5
> i101          C5
> i101          F#5
> i101          A5
>
> i101  m4 b1   B4    q
> i101          G5    e
> i101          G5    q
> i101          F#5   e
> i101          Z     e   // Z is a rest (zzzzz..)
> i101                e
> i101          B5    e
> i101          A5    q
> i101          D5    e
>
> end
>
> ------------------------------------------------------------------------
> or complete....
>
> 
> 
>
> 
> sr      =           44100
> nchnls 	= 		2
>
> gi1 ftgen 1, 0, 4096, 10, 1
> gi2 ftgen 2, 0, 4096, 7, -1, 4096, 1    ; sawtooth
> gi3 ftgen 3, 0, 4096, 7,  0, 1024, 1, 2048, -1, 1024, 0  ;triangle
>
> instr 101,102,103
>  iamp =      ampdbfs(p5)
>  a1   oscil  iamp, p4, p1-100
>  kenv expseg 1, p3, .01
>  a1   =      a1 * kenv
>       outs   a1, a1
> endin
>
> 
> 
> ; by Brian Baughn 3-14-05
> ; bbaughn@berklee.net
>
> beats = 100
> permeasure = 4
>
> i101    m1 b1   q    mp   D3
> i101                      F3
> i101                      D3
>
> i101    m2 b1             D3
> i101       b3             D3
>
> i101    m3 b1             D3
> i101                      F3
> i101                      D3
>
> i101    m4 b1             D3
> i101       b3             D3
>
> i101    m5 b1             D3
> i101       b4             G5
>
> i101    m6 b1             E5
> i101       b2             F5
> i101       b3     e       Eb5
> i101       b3.5   e
> i101       b4     q
>
> i101    m7 b1     e       D5
> i101
> i101                q
> i101                e     Db5
> i101
> i101                q
>
> i101    m8 b1     q       D5
> i101                      E5
> i101                      D5
>
> i102    m1 b2      q      D4
> i102       b4             E4
> i102       b4             Bb3
>
> i102    m2 b2             F4
> i102       b2             B3
> i102       b4             C#4
> i102       b4             Bb3
>
> i102    m3 b2      q      D4
> i102       b4             E4
> i102       b4             Bb3
>
> i102    m4 b2             F4
> i102       b2             B3
> i102       b4             C#4
> i102       b4             Bb3
>
> i103    m5 b2      e     F6
> i103       b2      e     A5
> i103       b2.5    e     D6
> i103       b3      e     F6
> i103       b3      e     A5
> i103       b4      e     E6
>
> i103    m6 b1      q     C#6
> i103               q     D6
> i103               e     C6
> i103
> i103               q
>
> i103    m7 b1      e     B5
> i103
> i103                 q
> i103                 e    Bb5
> i103
> i103                 q
>
> i103     m8 b1     e     F5
> i103        b1     e     A5
> i103        b1.5   e     D6
> i103        b2     e    Bb5
> i103        b2.5   e     D6
> i103        b3     q     F5
> i103        b3           A5
> end
> 
>
> 
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

hi

this is a great idea. i have 2 suggestions that may or may not be interesting.

On Sun, Sep 19, 2010 at 7:02 AM, john ffitch  wrote:
> a note attribute can be any of
>  amplitude      {fff,ff,f,mf,mp,p,pp,ppp}
>  pitch          {Abb, Ab, A, A#, Ax, Bbb, Bb, B, B#, Bx, Cbb, Cb, C,
>                  C#, Cx, Dbb, Db, D, D#, Dx, Ebb, Eb, E, E#, Ex, Fbb,
>                  Fb, F, F#, Fx, Gbb, Gb, G, G#, Gx, R, Z} followed by octave
>                  Z and R are rests
>  duration       {ed,et,e,hd,ht,h,qd,qt,q,sd,st,s,th,w}
>  measure        m 
>  beat           b 

what about having a numerical representation of durations? so instead of
'qd' followed by 'e'
you might have
'd1.5' followed by 'd.5'

and while this clashes with the namespace for dynamics, what about
frequency digits for those that aren't so constrained by equal
temerament
'f440' would be A4

[and even amplitude digits? a100, ...]

in human languages, we have many ways to say the same thing. this is
part of what makes speaking to different people interesting. computer
languages, on the other hand, often benefit from more restricted
syntax: making learning and maintenance easier. so, while i wouldn't
want to lose out on the elegant simplicity of the language you have
proposed, i'd encourage you to think about a digital representation of
the rhythmic values [at least].

and keep taking vacations- it seems to work well for you ... [and csound users]

-- 
\js : "verbing weirds language." -calvin  [http://or8.net/~johns/]


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

John,

This is very exciting stuff, which I think can lead to some major new
developments for Csound.

The thing that caught my eye in particular was this:  . What if this concept could be extended so a user could
choose the parser/preprocessor in which they would like to use? For
example:



sine = tSine(8192, 1)

@0 fmSynth(0, 4, 0.707, cpspch(7.00), 1, 1.1618, sine)
@4 fmSynth(0, 4, 0.707, cpspch(7.07), 1, 1.1618, sine)



The idea is that the content between in the  tags is passed
to the python script "customScore.py," which translates the content
into a valid Csound score.  This approach also wouldn't limit users to
a particular language, and could use C, Ruby, Lisp, Java, etc.  Taking
this idea one step farther, what if a new tag or directive could be
used to embed multiple types of preprocessors within a single Csound
score, like this?


f 1 0 8192 10 1

i 1 0 1 1
i 1 + . .
i 1 + . .
i 1 + . .


beats = 120
permeasure = 4

i101    m1 b1   q    mp   E3
i101                      E3
i101                      B3


i 1 4 1 1
i 1 + . .
i 1 + . .
i 1 + . .



I believe that formalizing a system in which users could create their
own score environments, and share them, would be very beneficial to
just about everyone. In a way, this would be similar to what Max
Mathews did with Music III, when he modularized unit generators so
others could design and build their own instruments and signal graphs,
except this would be applied to the score rather than the orchestra.

Best,
Jake
-- 
The Csound Blog - http://csoundblog.com/
Slipmat - http://slipmat.noisepages.com/




On Sun, Sep 19, 2010 at 4:02 AM, john ffitch  wrote:
> 18 months ago it was suggested to me that a simple score language
> might be of interest, and so I created one following earlier macro
> packages.  I think I never did much with it, but now on holiday \nd
> with composer's block, I have dusted off and improved the language.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

> John,
>
> This is very exciting stuff, which I think can lead to some major new
> developments for Csound.
>
> The thing that caught my eye in particular was this:   bin="beats">. What if this concept could be extended so a user could
> choose the parser/preprocessor in which they would like to use? For
> example:
>
>
> 
> sine = tSine(8192, 1)
>
> @0 fmSynth(0, 4, 0.707, cpspch(7.00), 1, 1.1618, sine)
> @4 fmSynth(0, 4, 0.707, cpspch(7.07), 1, 1.1618, sine)
> 
>


This has been there for over a year.  Any program that reads stdin and
writes stdout is OK.  Must produce csound scores though


>
> The idea is that the content between in the  tags is passed
> to the python script "customScore.py," which translates the content
> into a valid Csound score.  This approach also wouldn't limit users to
> a particular language, and could use C, Ruby, Lisp, Java, etc.  Taking
> this idea one step farther, what if a new tag or directive could be
> used to embed multiple types of preprocessors within a single Csound
> score, like this?
>
> 
> f 1 0 8192 10 1
>
> i 1 0 1 1
> i 1 + . .
> i 1 + . .
> i 1 + . .
>
> 
> beats = 120
> permeasure = 4
>
> i101    m1 b1   q    mp   E3
> i101                      E3
> i101                      B3
> 
>
> i 1 4 1 1
> i 1 + . .
> i 1 + . .
> i 1 + . .
>
> 
>
> I believe that formalizing a system in which users could create their
> own score environments, and share them, would be very beneficial to
> just about everyone. In a way, this would be similar to what Max
> Mathews did with Music III, when he modularized unit generators so
> others could design and build their own instruments and signal graphs,
> except this would be applied to the score rather than the orchestra.
>
> Best,
> Jake
> --
> The Csound Blog - http://csoundblog.com/
> Slipmat - http://slipmat.noisepages.com/
>
>
>
>
> On Sun, Sep 19, 2010 at 4:02 AM, john ffitch  wrote:
>> 18 months ago it was suggested to me that a simple score language
>> might be of interest, and so I created one following earlier macro
>> packages.  I think I never did much with it, but now on holiday \nd
>> with composer's block, I have dusted off and improved the language.
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>
>




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

This should be advertised, which I'll do with the blog, and mentioned
in the manual.  This is too good to be a hidden feature.

Best,
Jake
-- 
The Csound Blog - http://csoundblog.com/
Slipmat - http://slipmat.noisepages.com/


On Mon, Sep 27, 2010 at 8:51 AM,   wrote:
> This has been there for over a year.  Any program that reads stdin and
> writes stdout is OK.  Must produce csound scores though


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Been in the manual for some time as well



> This should be advertised, which I'll do with the blog, and mentioned
> in the manual.  This is too good to be a hidden feature.
>
> Best,
> Jake
> --
> The Csound Blog - http://csoundblog.com/
> Slipmat - http://slipmat.noisepages.com/
>
>
> On Mon, Sep 27, 2010 at 8:51 AM,   wrote:
>> This has been there for over a year.  Any program that reads stdin and
>> writes stdout is OK.  Must produce csound scores though
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>
>




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I see that it is, but only after looking for it for 10 minutes.

Best,
Jake
-- 
The Csound Blog - http://csoundblog.com/
Slipmat - http://slipmat.noisepages.com/



On Mon, Sep 27, 2010 at 9:11 AM,   wrote:
> Been in the manual for some time as well
>
>
>
>> This should be advertised, which I'll do with the blog, and mentioned
>> in the manual.  This is too good to be a hidden feature.
>>
>> Best,
>> Jake
>> --
>> The Csound Blog - http://csoundblog.com/
>> Slipmat - http://slipmat.noisepages.com/
>>
>>
>> On Mon, Sep 27, 2010 at 8:51 AM,   wrote:
>>> This has been there for over a year.  Any program that reads stdin and
>>> writes stdout is OK.  Must produce csound scores though
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>>
>>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Sorry about the confusion.  I thought I had sent mail about this months
ago and no one was interested (except I wanted to complet ethe simple
beats thing, and allow other score-generators.  Clearly I failked th
epublicity stakes again.
  Apologies.

I wonder what else I have not told peopl eabout?
My curent version uses the new parser by default, and this moning I
implemented constant folding.  Will mail the developer list about that
....

So much to learn
==J

> I see that it is, but only after looking for it for 10 minutes.
>
> Best,
> Jake
> --
> The Csound Blog - http://csoundblog.com/
> Slipmat - http://slipmat.noisepages.com/
>
>
>
> On Mon, Sep 27, 2010 at 9:11 AM,   wrote:
>> Been in the manual for some time as well
>>
>>
>>
>>> This should be advertised, which I'll do with the blog, and mentioned
>>> in the manual.  This is too good to be a hidden feature.
>>>
>>> Best,
>>> Jake
>>> --
>>> The Csound Blog - http://csoundblog.com/
>>> Slipmat - http://slipmat.noisepages.com/
>>>
>>>
>>> On Mon, Sep 27, 2010 at 8:51 AM,   wrote:
>>>> This has been there for over a year.  Any program that reads stdin
>>>> and
>>>> writes stdout is OK.  Must produce csound scores though
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>            
>>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>> "unsubscribe
>>> csound"
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>          
>>  https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>
>




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Perhaps around the time of a new release, some of us could create
examples/demos showcasing any and all new features. It would be a way
to promote not only the new stuff, but Csound in general. And this
would make sure that the hard work of the dev team doesn't go
unnoticed, which is kind of a travesty when it happens.

I will do my best to help out in this regard in the future.

Best,
Jake
-- 
The Csound Blog - http://csoundblog.com/
Slipmat - http://slipmat.noisepages.com/


On Mon, Sep 27, 2010 at 9:56 AM,   wrote:
> Sorry about the confusion.  I thought I had sent mail about this months
> ago and no one was interested (except I wanted to complet ethe simple
> beats thing, and allow other score-generators.  Clearly I failked th
> epublicity stakes again.
>  Apologies.
>
> I wonder what else I have not told peopl eabout?
> My curent version uses the new parser by default, and this moning I
> implemented constant folding.  Will mail the developer list about that
> ....
>
> So much to learn
> ==J


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Ah nice!!! (re: constant folding)

Does the new parser handle parsing errors now?

On Mon, Sep 27, 2010 at 12:56 PM,   wrote:
> Sorry about the confusion.  I thought I had sent mail about this months
> ago and no one was interested (except I wanted to complet ethe simple
> beats thing, and allow other score-generators.  Clearly I failked th
> epublicity stakes again.
>  Apologies.
>
> I wonder what else I have not told peopl eabout?
> My curent version uses the new parser by default, and this moning I
> implemented constant folding.  Will mail the developer list about that
> ....
>
> So much to learn
> ==J
>
>> I see that it is, but only after looking for it for 10 minutes.
>>
>> Best,
>> Jake
>> --
>> The Csound Blog - http://csoundblog.com/
>> Slipmat - http://slipmat.noisepages.com/
>>
>>
>>
>> On Mon, Sep 27, 2010 at 9:11 AM,   wrote:
>>> Been in the manual for some time as well
>>>
>>>
>>>
>>>> This should be advertised, which I'll do with the blog, and mentioned
>>>> in the manual.  This is too good to be a hidden feature.
>>>>
>>>> Best,
>>>> Jake
>>>> --
>>>> The Csound Blog - http://csoundblog.com/
>>>> Slipmat - http://slipmat.noisepages.com/
>>>>
>>>>
>>>> On Mon, Sep 27, 2010 at 8:51 AM,   wrote:
>>>>> This has been there for over a year.  Any program that reads stdin
>>>>> and
>>>>> writes stdout is OK.  Must produce csound scores though
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>
>>>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>> "unsubscribe
>>>> csound"
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>
>>>  https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>>
>>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Maybe I missed the discussion, but is there a consensus that there's
something wrong with the present score format?

Not criticizing, just wondering if I should stop laboring over the
standard score file format.
It looks like people are doing everything they can to avoid using it.
Greg


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"