Print statements often cause audio glitches in realtime performance. I'd 
minimize (or eliminate) print as much as possible.

Art Hunkins

----- Original Message ----- 
From: "Jan Jacob Hofmann" 
To: 
Sent: Friday, April 01, 2011 8:26 AM
Subject: [Csnd] Re: Signal Flow Graph Opcodes, Initialisation and Sean


> Dear Michael,
>
> I changed the test.csd like you suggested and could solve the problem.
>
> So I reordered roughly my rather complicated collection of sound 
> processing instruments. But the clicks and bursts persisted there. It 
> turned out, that a statement much later in the code, several  instruments 
> behind the location where I listened to the sound caused  mostly all of 
> the clicks and bursts now. Strange enough the clicks  were only audible 
> after having gone though a link done by an outleta -  inleta -pair. In the 
> original sound producing instrument everything  was fine.
>
> The clicks and bursts seem to be caused by a bunch of statements in  the 
> code of an alwayson instrument like this:
> ;[...]
>
> kpeak_1 peak aw
>
> printk p3, kpeak_1,0
> ;[...]
>
>
>
> The output in the Csound output window then runs wild and produces  pages 
> and pages of output like this:
> [...]
> i  80 time    10.39896:     0.00000
>  i  80 time    10.39917:     0.00000
>  i  80 time    10.39937:     0.00000
>  i  80 time    10.39958:     0.00000
>  i  80 time    10.39979:     0.00000
>  i  80 time    10.40000:     0.00000
>
> [...]
> To be precise, it's the p3 argument, wich no longer works in an 
> alwayson-driven instrument. it has to be a number.
>
> I will redesign my code completely now. Are there any other known or 
> probable "don'ts" which I should try to avoid?
>
> What about reinit-passes in an alwayson instrument?
> Can I use UDO's?
> Should I change from Zak-Patch System totally to outleta-inleta-pairs?
> What about goto statements in an alwayson instrument? May they cause 
> problems?
>
> I would be glad to get some advices here.
>
> All the best,
>
> Jan Jacob
>
>
>
>
>
>
>
> Am 01.04.2011 um 01:03 schrieb csound-request@lists.bath.ac.uk:
>
>> ------------------------------
>>
>> Date: Thu, 31 Mar 2011 12:42:33 -0400
>> From: Michael Gogins 
>> Subject: Re: [Csnd] Signal Flow Graph Opcodes, Initialisation and Sean
>>
>> Why are you using the alwayson opcode within the scope of another
>> instrument? Of course this will cause clicks. The idea is to turn the
>> reverb instrument on only the instrument header. It will remain on
>> during the entire performance. Every new instr 1 will automatically
>> copy the connection to the reverb instrument and all will go well. You
>> will need to extend performance with the s and e statements at the end
>> of the score to prevent a click with a reverb tail at the end of the
>> entire performance.
>>
>> I repeat, both the connections and the always on instruments should be
>> defined only in the orchestra header. When the score creates new
>> instrument instances, they will automatically inherit the declared
>> connections.
>>
>> If this is not clear, let me know and I will rewrite your example so  it 
>> works.
>>
>> Regards,
>> Mike
>
>
>
> 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"