There's a rewind score method. Won't you know when a performance has
ended or failed as soon as performKsmps() returns true?

On 16 June 2014 22:36, David Worrall  wrote:
> I'm generating and playing  (10s of 1000's of) score events for  Real Time
> performance on OSX under csnd6 in Python.
>
> I'd be grateful if anyone can answer a couple of questions:
>
> 1. Is it possible to 'rewind' the RT score and play it again? If so, how?
>
> 2. What is the best way to indicate to csnd that the RT performance has
> ended - and is should be rewound, as per Q1 above.
>
> Many thanks,
>
> David
>
>
>
>
> ______________________________________
> Prof. Dr. David Worrall
> Emerging Audio Research (EAR)
> Audio Department
> International Audio Laboratories Erlangen
> Fraunhofer-Institut für Integrierte Schaltungen IIS
> Am Wolfsmantel 33
> 91058 Erlangen
> Internet: www.iis.fraunhofer.de
> ---
> Adjunct Senior Research Fellow
> School of Music, Australian National University
> david.worrall@anu.edu.au
>
>
>
>

Good point! Ok. For this I would put in an instrument in my Csound
code that will stop and restart any other instrument when I send the
signal to do so over a named channel. That would work wouldn't it?

On 16 June 2014 23:02, Andres Cabrera  wrote:
> But that method doesn't apply to realtime scores, unfortunately.
>
> A
>
>
> On Mon, Jun 16, 2014 at 4:48 PM, Rory Walsh  wrote:
>>
>> There's a rewind score method. Won't you know when a performance has
>> ended or failed as soon as performKsmps() returns true?
>>
>> On 16 June 2014 22:36, David Worrall 
>> wrote:
>> > I'm generating and playing  (10s of 1000's of) score events for  Real
>> > Time
>> > performance on OSX under csnd6 in Python.
>> >
>> > I'd be grateful if anyone can answer a couple of questions:
>> >
>> > 1. Is it possible to 'rewind' the RT score and play it again? If so,
>> > how?
>> >
>> > 2. What is the best way to indicate to csnd that the RT performance has
>> > ended - and is should be rewound, as per Q1 above.
>> >
>> > Many thanks,
>> >
>> > David
>> >
>> >
>> >
>> >
>> > ______________________________________
>> > Prof. Dr. David Worrall
>> > Emerging Audio Research (EAR)
>> > Audio Department
>> > International Audio Laboratories Erlangen
>> > Fraunhofer-Institut für Integrierte Schaltungen IIS
>> > Am Wolfsmantel 33
>> > 91058 Erlangen
>> > Internet: www.iis.fraunhofer.de
>> > ---
>> > Adjunct Senior Research Fellow
>> > School of Music, Australian National University
>> > david.worrall@anu.edu.au
>> >
>> >
>> >
>> >
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>>
>

Good point!. Ok for this I would put in an instrument in my Csound code that will stop and restart another when I send it the signal over a channel.

On 16 June 2014 23:02, Andres Cabrera <mantaraya36@gmail.com> wrote:
> But that method doesn't apply to realtime scores, unfortunately.
>
> A
>
>
> On Mon, Jun 16, 2014 at 4:48 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
>>
>> There's a rewind score method. Won't you know when a performance has
>> ended or failed as soon as performKsmps() returns true?
>>
>> On 16 June 2014 22:36, David Worrall <david.worrall@iis.fraunhofer.de>
>> wrote:
>> > I'm generating and playing (10s of 1000's of) score events for Real
>> > Time
>> > performance on OSX under csnd6 in Python.
>> >
>> > I'd be grateful if anyone can answer a couple of questions:
>> >
>> > 1. Is it possible to 'rewind' the RT score and play it again? If so,
>> > how?
>> >
>> > 2. What is the best way to indicate to csnd that the RT performance has
>> > ended - and is should be rewound, as per Q1 above.
>> >
>> > Many thanks,
>> >
>> > David
>> >
>> >
>> >
>> >
>> > ______________________________________
>> > Prof. Dr. David Worrall
>> > Emerging Audio Research (EAR)
>> > Audio Department
>> > International Audio Laboratories Erlangen
>> > Fraunhofer-Institut für Integrierte Schaltungen IIS
>> > Am Wolfsmantel 33
>> > 91058 Erlangen
>> > Internet: www.iis.fraunhofer.de
>> > ---
>> > Adjunct Senior Research Fellow
>> > School of Music, Australian National University
>> > david.worrall@anu.edu.au
>> >
>> >
>> >
>> >
>>
>>
>> Send bugs reports to
>> https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>>
>

RT events are not stored as a score by Csound, they are just played and forgotten. So the solution would be
to keep and manage them outside Csound, e.g. python lists etc.

On 16 Jun 2014, at 22:36, David Worrall wrote:

> I'm generating and playing  (10s of 1000's of) score events for  Real Time performance on OSX under csnd6 in Python.
> 
> I'd be grateful if anyone can answer a couple of questions:
> 
> 1. Is it possible to 'rewind' the RT score and play it again? If so, how?
> 
> 2. What is the best way to indicate to csnd that the RT performance has ended - and is should be rewound, as per Q1 above.
> 
> Many thanks,
> 
> David
> 
> 
> 
> 
> ______________________________________
> Prof. Dr. David Worrall
> Emerging Audio Research (EAR)
> Audio Department
> International Audio Laboratories Erlangen
> Fraunhofer-Institut für Integrierte Schaltungen IIS
> Am Wolfsmantel 33
> 91058 Erlangen
> Internet: www.iis.fraunhofer.de 
> ---
> Adjunct Senior Research Fellow
> School of Music, Australian National University
> david.worrall@anu.edu.au
> 
> 
> 
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

So treat CS just as a 'dumb' player and track the time info  on the first run of the events and then resubmit them. Quite cumbersome, especially if the instrument is making stochastic choices and spawning extra events.
Is there a way of getting CS to trigger RT-CS to end? i.e. to tell itself it needs to implode/self immolate -:) 
or to check how long it has been since it has played an event?
Or what is the maximum number of events that can be submitted to the 'score' input queue in one hit? )-B or -b perhaps)

Just interested in exploring different options - 

Thanks,
David.
On 17.06.2014, at 00:59, Victor Lazzarini  wrote:

> RT events are not stored as a score by Csound, they are just played and forgotten. So the solution would be
> to keep and manage them outside Csound, e.g. python lists etc.
> 
> On 16 Jun 2014, at 22:36, David Worrall wrote:
> 
>> I'm generating and playing  (10s of 1000's of) score events for  Real Time performance on OSX under csnd6 in Python.
>> 
>> I'd be grateful if anyone can answer a couple of questions:
>> 
>> 1. Is it possible to 'rewind' the RT score and play it again? If so, how?
>> 
>> 2. What is the best way to indicate to csnd that the RT performance has ended - and is should be rewound, as per Q1 above.
>> 
>> Many thanks,
>> 
>> David
>> 
>> ______________________________________
>> Prof. Dr. David Worrall
>> Emerging Audio Research (EAR)
>> Audio Department
>> International Audio Laboratories Erlangen
>> Fraunhofer-Institut für Integrierte Schaltungen IIS
>> Am Wolfsmantel 33
>> 91058 Erlangen
>> Internet: www.iis.fraunhofer.de 
>> ---
>> Adjunct Senior Research Fellow
>> School of Music, Australian National University
>> david.worrall@anu.edu.au
>> 
> 
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
...

I've often thought storing realtime events would be nice to have. If you could also bottle up all the other incoming signals (control signals, orchestra strings... ), you could record entire performances. That'd be a nice way to share pieces with other Csounders, and get away from only sharing static orcs and scores. Could make for nice compositional environments, (realtime recording with multiple takes), Could potentially be a good collaborative way of working too....   Well... nice to speculate :), but I'm afraid I don't have the chops to make it.

Thorin

On Tue, Jun 17, 2014 at 9:26 AM, David Worrall <david.worrall@iis.fraunhofer.de> wrote:

So treat CS just as a 'dumb' player and track the time info  on the first run of the events and then resubmit them. Quite cumbersome, especially if the instrument is making stochastic choices and spawning extra events.
Is there a way of getting CS to trigger RT-CS to end? i.e. to tell itself it needs to implode/self immolate -:)
or to check how long it has been since it has played an event?
Or what is the maximum number of events that can be submitted to the 'score' input queue in one hit? )-B or -b perhaps)

Just interested in exploring different options -

Thanks,
David.

On 17.06.2014, at 00:59, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:

> RT events are not stored as a score by Csound, they are just played and forgotten. So the solution would be
> to keep and manage them outside Csound, e.g. python lists etc.
>
> On 16 Jun 2014, at 22:36, David Worrall wrote:
>
>> I'm generating and playing  (10s of 1000's of) score events for  Real Time performance on OSX under csnd6 in Python.
>>
>> I'd be grateful if anyone can answer a couple of questions:
>>
>> 1. Is it possible to 'rewind' the RT score and play it again? If so, how?
>>
>> 2. What is the best way to indicate to csnd that the RT performance has ended - and is should be rewound, as per Q1 above.
>>
>> Many thanks,
>>
>> David
>>
>> ______________________________________
>> Prof. Dr. David Worrall
>> Emerging Audio Research (EAR)
>> Audio Department
>> International Audio Laboratories Erlangen
>> Fraunhofer-Institut für Integrierte Schaltungen IIS
>> Am Wolfsmantel 33
>> 91058 Erlangen
>> Internet: www.iis.fraunhofer.de
>> ---
>> Adjunct Senior Research Fellow
>> School of Music, Australian National University
>> david.worrall@anu.edu.au
>>
>
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie

...

Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"