Csound Csound-dev Csound-tekno Search About

[Csnd]
Date2012-03-17 08:10
Fromfrancesco
Subject[Csnd] 
Hello All,
a quick info: using
Date2012-03-17 09:08
FromTito Latini
SubjectRe: [Csnd]
AttachmentsNone  
Date2012-03-17 09:26
FromRichard Dobson
SubjectRe: [Csnd] 
On 17/03/2012 09:08, Tito Latini wrote:
> The behavior depends on your filter command.
> For example, a dummy filter is `cp'
>
>    
>    ...
>    
>
> and nil is changed. Other cases: you can import external score in
> your script or add `#include "external.sco"' from your script.
>
> tito
>
>...
>> I cannot merge external generated score and 'traditional' score.
>>

I don't know if this happens already, but if not:
since both scores get sorted to the same final representation, this 
would be very possible, and often useful - just need an intermediate 
internal merging stage to which both write, which can then be sorted 
into time order in the usual way. The one requirement would be (e.g. in 
the case of using csbeats) that users take care to maintain compatible 
use of the first 5 pfields.

Richard Dobson
Date2012-03-17 10:18
FromTito Latini
SubjectRe: [Csnd]
AttachmentsNone  
Date2012-03-17 15:47
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] 
It would be helpful and inspiring to document all these new and exciting possibilities in the manual with examples of different use scenarios.  

Sent from my iPhone.

On Mar 17, 2012, at 6:18 AM, Tito Latini  wrote:

>> I don't know if this happens already, but if not:
>> since both scores get sorted to the same final representation, this 
>> would be very possible, and often useful - just need an intermediate 
>> internal merging stage to which both write, which can then be sorted 
>> into time order in the usual way. The one requirement would be (e.g. in 
>> the case of using csbeats) that users take care to maintain compatible 
>> use of the first 5 pfields.
> 
> Yes, in general the filter command can
> 
>  1) filter only a word (macro preprocessor)
> 
>  2) interpret a score language (like csbeats)
> 
>  3) add/remove score chunks based on the input score statement,
>     for example:
> 
>        if (...) add '#include "chunk1.sco"'
>        else if (...) '#include "chunk2.sco"
>        ...
>        else if (...) add `i123 ...'
>    ...
>        else if (...) remove/modify score statement
>        ...
>    etc
> 
>   4) create new chunks to be included, possibly with AI, neural network, etc
> 
>   5) send the score to csound-list and to get a correct version
> 
>   ....
> 
> And the `scsort' utility can be applied in the filter command.
> I see it like a "pipe" in the unix environment (but with temp files).
> 
> tito
> 
> 
> 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"
>
Date2012-03-17 16:42
FromTito Latini
SubjectRe: [Csnd]
AttachmentsNone  
Date2012-03-17 17:50
Fromjpff@cs.bath.ac.uk
SubjectRe: [Csnd] 
Not sure I have time before release but a Journal article on score
processing would seem to be in order


> It would be helpful and inspiring to document all these new and exciting
> possibilities in the manual with examples of different use scenarios.
>
> Sent from my iPhone.
>
> On Mar 17, 2012, at 6:18 AM, Tito Latini  wrote:
>
>>> I don't know if this happens already, but if not:
>>> since both scores get sorted to the same final representation, this
>>> would be very possible, and often useful - just need an intermediate
>>> internal merging stage to which both write, which can then be sorted
>>> into time order in the usual way. The one requirement would be (e.g. in
>>> the case of using csbeats) that users take care to maintain compatible
>>> use of the first 5 pfields.
>>
>> Yes, in general the filter command can
>>
>>  1) filter only a word (macro preprocessor)
>>
>>  2) interpret a score language (like csbeats)
>>
>>  3) add/remove score chunks based on the input score statement,
>>     for example:
>>
>>        if (...) add '#include "chunk1.sco"'
>>        else if (...) '#include "chunk2.sco"
>>        ...
>>        else if (...) add `i123 ...'
>>    ...
>>        else if (...) remove/modify score statement
>>        ...
>>    etc
>>
>>   4) create new chunks to be included, possibly with AI, neural network,
>> etc
>>
>>   5) send the score to csound-list and to get a correct version
>>
>>   ....
>>
>> And the `scsort' utility can be applied in the filter command.
>> I see it like a "pipe" in the unix environment (but with temp files).
>>
>> tito
>>
>>
>> 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"
>
>
>
>
Date2012-03-17 19:59
FromJacob Joaquin
SubjectRe: [Csnd] 
I've been experimenting creating a streamlined python preprocessor
that is integrated into the score.. I'll have to package the code up,
but I can go ahead and share my findings.

My goal is to find a way to introduce user made / pre-made library
value converters into the score, and to make the whole thing user
friendly.

The first thing was to eliminate the need for users to open files; It
now does this automagically as far as a user is concerned

The second was for users to be able to use a premade function from a
premade library. For this example, I recreated cpspch.

The third was to allow users to create their own value converters,
which is done with the function divide_by_2.

To mix Csound and python, I've created the markup tag  to
encapsulate a traditional score.

Still needs work, but it's getting there.



sr = 44100
kr = 4410
ksmps = 10
nchnls = 1
0dbfs = 1.0

instr 1
    idur = p3   ; Duration
    iamp = p4   ; Amplitude
    ifreq = p5  ; Frequency

    kenv line iamp, idur, 0       ; Line envelope
    a1 vco2 kenv, ifreq, 12, 0.5  ; Triangle wave
    out a1
endin




def foo(x):
	return x / 2.0

# Apply cpspch to all p5s for instr 1
pfunc('i', 1, 5, cpspch)
pfunc('i', 1, 4, foo)

# Score is placed between  tags

t 0 180

i 1 0 0.5 0.5 9.02
i 1 + .   .   8.07
i 1 + .   .   8.09
i 1 + .   .   8.11
i 1 + .   .   9.00
i 1 + .   .   8.09
i 1 + .   .   8.11
i 1 + .   .   8.07




Best,
Jake

On Sat, Mar 17, 2012 at 9:42 AM, Tito Latini  wrote:
> Of course, I can write some examples in the next days.
>
> On Sat, Mar 17, 2012 at 11:47:14AM -0400, Dr. Richard Boulanger wrote:
>> It would be helpful and inspiring to document all these new and exciting possibilities in the manual with examples of different use scenarios.
>>
>> Sent from my iPhone.
>>
>> On Mar 17, 2012, at 6:18 AM, Tito Latini  wrote:
>>
>> >> I don't know if this happens already, but if not:
>> >> since both scores get sorted to the same final representation, this
>> >> would be very possible, and often useful - just need an intermediate
>> >> internal merging stage to which both write, which can then be sorted
>> >> into time order in the usual way. The one requirement would be (e.g. in
>> >> the case of using csbeats) that users take care to maintain compatible
>> >> use of the first 5 pfields.
>> >
>> > Yes, in general the filter command can
>> >
>> >  1) filter only a word (macro preprocessor)
>> >
>> >  2) interpret a score language (like csbeats)
>> >
>> >  3) add/remove score chunks based on the input score statement,
>> >     for example:
>> >
>> >        if (...) add '#include "chunk1.sco"'
>> >        else if (...) '#include "chunk2.sco"
>> >        ...
>> >        else if (...) add `i123 ...'
>> >    ...
>> >        else if (...) remove/modify score statement
>> >        ...
>> >    etc
>> >
>> >   4) create new chunks to be included, possibly with AI, neural network, etc
>> >
>> >   5) send the score to csound-list and to get a correct version
>> >
>> >   ....
>> >
>> > And the `scsort' utility can be applied in the filter command.
>> > I see it like a "pipe" in the unix environment (but with temp files).
>> >
>> > tito
>> >
>> >
>> > 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"
>



-- 
codehop.com | #code #art #music