I've been using the attached instr50 for quite a while and I've just
noticed it now causes some odd behaviour to Csound(I'm using 5.11).
I've had to uproot it from it's original setting to put it into a csd
some of you may be able to try. I'm not using any of instr50's
processing, I'm simply using it to output a straight signal. When
running the audio stops after about 7/8 seconds, not just on instr50
but across ALL instruments. Csound doesn't spit out any errors except
for an interrupt message. As you can see it's a midi instrument but
you don't need MIDI hooked up to appreciate the problem here. Would
someone mind trying it on their PC to see if they get the same
behaviour? Cheers,

Rory.

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"

Also running on (a sort of) 5.11 doubles on Win,
it does behave the same each time I run it,
sometimes it might choke (for lack of a better word) after less than one second,
but it's also possible to let it render the full 100 seconds.
I can't spot the error immediately, but I think there's some "shooting
oneself in the foot" in here somewhere ;-)
Since it's processing live input, the actual input signal may affect
how long it's allowed to run. When I run it on my laptop, it
immediately goes into a thin and piercing feedback, as the mic and the
speakers are close.
When it choked after less than a second (this happened many times in a
row), finally I tapped the laptop mic at the same time as starting
csound, and that seemed to "push"  the process just enough to create a
feedback loop instead of a choke.
Interesting puzzle, how much more can you strip it down before it does
not randomly choke anymore ?

best
Oeyvind


2010/4/29 Rory Walsh :
> I've been using the attached instr50 for quite a while and I've just
> noticed it now causes some odd behaviour to Csound(I'm using 5.11).
> I've had to uproot it from it's original setting to put it into a csd
> some of you may be able to try. I'm not using any of instr50's
> processing, I'm simply using it to output a straight signal. When
> running the audio stops after about 7/8 seconds, not just on instr50
> but across ALL instruments. Csound doesn't spit out any errors except
> for an interrupt message. As you can see it's a midi instrument but
> you don't need MIDI hooked up to appreciate the problem here. Would
> someone mind trying it on their PC to see if they get the same
> behaviour? Cheers,
>
> Rory.
>
> 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 meant ,... it does *not* behave the same each time I run it,
sorry

2010/4/29 Oeyvind Brandtsegg :
> Also running on (a sort of) 5.11 doubles on Win,
> it does behave the same each time I run it,
> sometimes it might choke (for lack of a better word) after less than one second,
> but it's also possible to let it render the full 100 seconds.
> I can't spot the error immediately, but I think there's some "shooting
> oneself in the foot" in here somewhere ;-)
> Since it's processing live input, the actual input signal may affect
> how long it's allowed to run. When I run it on my laptop, it
> immediately goes into a thin and piercing feedback, as the mic and the
> speakers are close.
> When it choked after less than a second (this happened many times in a
> row), finally I tapped the laptop mic at the same time as starting
> csound, and that seemed to "push"  the process just enough to create a
> feedback loop instead of a choke.
> Interesting puzzle, how much more can you strip it down before it does
> not randomly choke anymore ?
>
> best
> Oeyvind
>
>
> 2010/4/29 Rory Walsh :
>> I've been using the attached instr50 for quite a while and I've just
>> noticed it now causes some odd behaviour to Csound(I'm using 5.11).
>> I've had to uproot it from it's original setting to put it into a csd
>> some of you may be able to try. I'm not using any of instr50's
>> processing, I'm simply using it to output a straight signal. When
>> running the audio stops after about 7/8 seconds, not just on instr50
>> but across ALL instruments. Csound doesn't spit out any errors except
>> for an interrupt message. As you can see it's a midi instrument but
>> you don't need MIDI hooked up to appreciate the problem here. Would
>> someone mind trying it on their PC to see if they get the same
>> behaviour? Cheers,
>>
>> Rory.
>>
>> 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'm just stripping it down now. You're right, if there is a signal
when the process starts it works much better, if there is silence when
the process starts it chokes.

On 29 April 2010 22:05, Oeyvind Brandtsegg  wrote:
> I meant ,... it does *not* behave the same each time I run it,
> sorry
>
> 2010/4/29 Oeyvind Brandtsegg :
>> Also running on (a sort of) 5.11 doubles on Win,
>> it does behave the same each time I run it,
>> sometimes it might choke (for lack of a better word) after less than one second,
>> but it's also possible to let it render the full 100 seconds.
>> I can't spot the error immediately, but I think there's some "shooting
>> oneself in the foot" in here somewhere ;-)
>> Since it's processing live input, the actual input signal may affect
>> how long it's allowed to run. When I run it on my laptop, it
>> immediately goes into a thin and piercing feedback, as the mic and the
>> speakers are close.
>> When it choked after less than a second (this happened many times in a
>> row), finally I tapped the laptop mic at the same time as starting
>> csound, and that seemed to "push"  the process just enough to create a
>> feedback loop instead of a choke.
>> Interesting puzzle, how much more can you strip it down before it does
>> not randomly choke anymore ?
>>
>> best
>> Oeyvind
>>
>>
>> 2010/4/29 Rory Walsh :
>>> I've been using the attached instr50 for quite a while and I've just
>>> noticed it now causes some odd behaviour to Csound(I'm using 5.11).
>>> I've had to uproot it from it's original setting to put it into a csd
>>> some of you may be able to try. I'm not using any of instr50's
>>> processing, I'm simply using it to output a straight signal. When
>>> running the audio stops after about 7/8 seconds, not just on instr50
>>> but across ALL instruments. Csound doesn't spit out any errors except
>>> for an interrupt message. As you can see it's a midi instrument but
>>> you don't need MIDI hooked up to appreciate the problem here. Would
>>> someone mind trying it on their PC to see if they get the same
>>> behaviour? Cheers,
>>>
>>> Rory.
>>>
>>> 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"

Denorm! Excellent, can you explain why one needs to "Mix low level
(~1e-20 for floats, and ~1e-56 for doubles) noise to a list of a-rate
signals"?

On 29 April 2010 22:57,   wrote:
> I think it's probably a denormal problem. Have you tried using the denormal opcode on the input signal?
>
> Victor
>
> ----- Original Message -----
> From: Rory Walsh 
> Date: Thursday, April 29, 2010 10:45 pm
> Subject: [Csnd] Re: Re: little help needed...
> To: csound@lists.bath.ac.uk
>
>> I'm just stripping it down now. You're right, if there is a signal
>> when the process starts it works much better, if there is
>> silence when
>> the process starts it chokes.
>>
>> On 29 April 2010 22:05, Oeyvind Brandtsegg
>>  wrote:
>> > I meant ,... it does *not* behave the same each time I run it,
>> > sorry
>> >
>> > 2010/4/29 Oeyvind Brandtsegg :
>> >> Also running on (a sort of) 5.11 doubles on Win,
>> >> it does behave the same each time I run it,
>> >> sometimes it might choke (for lack of a better word) after
>> less than one second,
>> >> but it's also possible to let it render the full 100 seconds.
>> >> I can't spot the error immediately, but I think there's some
>> "shooting>> oneself in the foot" in here somewhere ;-)
>> >> Since it's processing live input, the actual input signal may
>> affect>> how long it's allowed to run. When I run it on my
>> laptop, it
>> >> immediately goes into a thin and piercing feedback, as the
>> mic and the
>> >> speakers are close.
>> >> When it choked after less than a second (this happened many
>> times in a
>> >> row), finally I tapped the laptop mic at the same time as starting
>> >> csound, and that seemed to "push"  the process just enough to
>> create a
>> >> feedback loop instead of a choke.
>> >> Interesting puzzle, how much more can you strip it down
>> before it does
>> >> not randomly choke anymore ?
>> >>
>> >> best
>> >> Oeyvind
>> >>
>> >>
>> >> 2010/4/29 Rory Walsh :
>> >>> I've been using the attached instr50 for quite a while and
>> I've just
>> >>> noticed it now causes some odd behaviour to Csound(I'm using
>> 5.11).>>> I've had to uproot it from it's original setting to
>> put it into a csd
>> >>> some of you may be able to try. I'm not using any of instr50's
>> >>> processing, I'm simply using it to output a straight signal. When
>> >>> running the audio stops after about 7/8 seconds, not just on
>> instr50>>> but across ALL instruments. Csound doesn't spit out
>> any errors except
>> >>> for an interrupt message. As you can see it's a midi
>> instrument but
>> >>> you don't need MIDI hooked up to appreciate the problem
>> here. Would
>> >>> someone mind trying it on their PC to see if they get the same
>> >>> behaviour? Cheers,
>> >>>
>> >>> Rory.
>> >>>
>> >>> 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"
>>
>
> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
> National University of Ireland, Maynooth
>
>
>
> 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 spoke too soon. I'm afraid that doesn't work either. It does however
stop it from choking at the very start, now it's much more erratic!

On 29 April 2010 23:03, Rory Walsh  wrote:
> Denorm! Excellent, can you explain why one needs to "Mix low level
> (~1e-20 for floats, and ~1e-56 for doubles) noise to a list of a-rate
> signals"?
>
> On 29 April 2010 22:57,   wrote:
>> I think it's probably a denormal problem. Have you tried using the denormal opcode on the input signal?
>>
>> Victor
>>
>> ----- Original Message -----
>> From: Rory Walsh 
>> Date: Thursday, April 29, 2010 10:45 pm
>> Subject: [Csnd] Re: Re: little help needed...
>> To: csound@lists.bath.ac.uk
>>
>>> I'm just stripping it down now. You're right, if there is a signal
>>> when the process starts it works much better, if there is
>>> silence when
>>> the process starts it chokes.
>>>
>>> On 29 April 2010 22:05, Oeyvind Brandtsegg
>>>  wrote:
>>> > I meant ,... it does *not* behave the same each time I run it,
>>> > sorry
>>> >
>>> > 2010/4/29 Oeyvind Brandtsegg :
>>> >> Also running on (a sort of) 5.11 doubles on Win,
>>> >> it does behave the same each time I run it,
>>> >> sometimes it might choke (for lack of a better word) after
>>> less than one second,
>>> >> but it's also possible to let it render the full 100 seconds.
>>> >> I can't spot the error immediately, but I think there's some
>>> "shooting>> oneself in the foot" in here somewhere ;-)
>>> >> Since it's processing live input, the actual input signal may
>>> affect>> how long it's allowed to run. When I run it on my
>>> laptop, it
>>> >> immediately goes into a thin and piercing feedback, as the
>>> mic and the
>>> >> speakers are close.
>>> >> When it choked after less than a second (this happened many
>>> times in a
>>> >> row), finally I tapped the laptop mic at the same time as starting
>>> >> csound, and that seemed to "push"  the process just enough to
>>> create a
>>> >> feedback loop instead of a choke.
>>> >> Interesting puzzle, how much more can you strip it down
>>> before it does
>>> >> not randomly choke anymore ?
>>> >>
>>> >> best
>>> >> Oeyvind
>>> >>
>>> >>
>>> >> 2010/4/29 Rory Walsh :
>>> >>> I've been using the attached instr50 for quite a while and
>>> I've just
>>> >>> noticed it now causes some odd behaviour to Csound(I'm using
>>> 5.11).>>> I've had to uproot it from it's original setting to
>>> put it into a csd
>>> >>> some of you may be able to try. I'm not using any of instr50's
>>> >>> processing, I'm simply using it to output a straight signal. When
>>> >>> running the audio stops after about 7/8 seconds, not just on
>>> instr50>>> but across ALL instruments. Csound doesn't spit out
>>> any errors except
>>> >>> for an interrupt message. As you can see it's a midi
>>> instrument but
>>> >>> you don't need MIDI hooked up to appreciate the problem
>>> here. Would
>>> >>> someone mind trying it on their PC to see if they get the same
>>> >>> behaviour? Cheers,
>>> >>>
>>> >>> Rory.
>>> >>>
>>> >>> 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"
>>>
>>
>> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
>> National University of Ireland, Maynooth
>>
>>
>>
>> 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"