In looking for an oddity (issue #648) we noticed that some of the
print seem to limit the printout to once per k-cycle. This may lead to
unexpected results in loops, so I am not sure whether that is right to
restrict it like that.  Before removing this I am asking the community
if they have and thoughts.

i can imagine that removing it for printks can bring some existing csd 
in mess, so i am wondering whether it would be a good solution to leave 
printks as it is, but state it clearly in the manual and point to printf 
as alternative (which does not have this restriction).

for printk i'd vote to remove the restriction because i think it is 
mainly for debugging code and it would be useful to have it printing all 
values in a loop.

	joachim


On 31/05/16 15:39, jpff wrote:
> In looking for an oddity (issue #648) we noticed that some of the
> print seem to limit the printout to once per k-cycle. This may lead to
> unexpected results in loops, so I am not sure whether that is right to
> restrict it like that.  Before removing this I am asking the community
> if they have and thoughts.
>
> ==John ffitch

I agree with Joachim,
since these opcodes already have a time granularity argument, it would
make sense that they are meant to be used for lower rate printing.
Contrary to Joachim, I think the same applies to printk, due to the
time granularity argument.
The print opcodes that are triggered by changes in the value to be
printed, like printk2 and printks2 can be used to debug loops. And
also puts can be used in the same manner.

best
Oeyvind

2016-05-31 22:53 GMT+02:00 joachim heintz :
> i can imagine that removing it for printks can bring some existing csd in
> mess, so i am wondering whether it would be a good solution to leave printks
> as it is, but state it clearly in the manual and point to printf as
> alternative (which does not have this restriction).
>
> for printk i'd vote to remove the restriction because i think it is mainly
> for debugging code and it would be useful to have it printing all values in
> a loop.
>
>         joachim
>
>
>
> On 31/05/16 15:39, jpff wrote:
>>
>> In looking for an oddity (issue #648) we noticed that some of the
>> print seem to limit the printout to once per k-cycle. This may lead to
>> unexpected results in loops, so I am not sure whether that is right to
>> restrict it like that.  Before removing this I am asking the community
>> if they have and thoughts.
>>
>> ==John ffitch
>>
>



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://soundcloud.com/brandtsegg
http://flyndresang.no/