Hi,
i try to take value from checkbox widget for trig on/off with a loop but it don't work and have a strange behavior.
i already signal this and Mr Joachim Heintz have found (much more precisely than me ;) the same strange behavior.
i thought with new version of csound and csoundqt the bug will disappear but not....

this possibility of take value from many checkbox is very important for me for doing some real time FL Studio like improvisation environment.
yo'll find my test code (ReadWrite.....csd) and the test code of Joachim as a demonstration of the bug (joachimReadWrite.......csd).
i hope this help.

thanks in advance

stf

Hello,

Thanks for the exapmles, especially Joachim's one made it very clear.

I thnink this is a bug in csound, not csoundqt:

1) looks like invalue (and also chnget) cannot read the string that has been evaluated at k-time.

like in lines

Sslot sprintfk "sq1-%i", kstep

kstepval invalue Sslot

the good workaround is to call the new instrument like Joachim did:

Sslot sprintf "sq1-%i", istep

Scorlin sprintf {{i 3 0 1 "%s"}}, Sslot

instr 3

Sslot = p4

kstepval invalue Sslot

printf "kstepval = %d\n", 1, kstepval

endin

2) chn_k does not like character "-", perhaps there are other limitations as well

when i tried to replcae invalue wit chnget

line

chn_k "sq1-1",3

caused error:

INIT ERROR in instr 0: invalid channel name

chn_k "sq1-1" 3 0 0 0 0

I have had similar problem with channel names before

I hope it is easy to fix?

greetings,

tarmo

On Thursday 29 March 2012 10:51:55 Gmail wrote:

> Hi,

> i try to take value from checkbox widget for trig on/off with a loop but it

> don't work and have a strange behavior. i already signal this and Mr

> Joachim Heintz have found (much more precisely than me ;) the same strange

> behavior. i thought with new version of csound and csoundqt the bug will

> disappear but not....

>

> this possibility of take value from many checkbox is very important for me

> for doing some real time FL Studio like improvisation environment. yo'll

> find my test code (ReadWrite.....csd) and the test code of Joachim as a

> demonstration of the bug (joachimReadWrite.......csd). i hope this help.

>

> thanks in advance

>

> stf

>

> 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"

On Saturday 31 March 2012 09:17:00 Tito Latini wrote:
> chn_k "the---char-in-git", 20120331
> 
> tito

thanks, that's great!

> It is not a bug really. Strings are i-time variables generally speaking
> (although there are a couple of situations where they can be changed in
> performance, but I can't remember which). Maybe the manual should be
> clearer about this.
> 
> Regards
> 
> Victor

Victor,  I understand, it is not a bug. But it is a bit unlogical  in some 
situations - if it is possible to create or change strings in k time (like 
sprintf, strcatk etc) there should be possibility to use the results in k-
time?

Is it so that a string in csound is rather a constant evaluated in init-time 
(like it happened in   kval invalue Sstring  - the value insterted to Sstring 
in ktime cannot be reached)? 

I imagine it would make more sense to be able to handle string more like in C  
- it could be rather address or pointer  and any opcode can read the 
information from that address in any moment? So that the k-time string 
modifications make sense.

Maybe there is something internal that I do not undertand.

tarmo

I haven't looked, but I assume the issue is not string variable but
the invalue opcode is coded to read the string variable only at i-time
in its init function (OOps/aops.c:invalset).  So it's just how invalue
is coded I think.

On Sat, Mar 31, 2012 at 5:24 PM, Tarmo Johannes
 wrote:
> On Saturday 31 March 2012 09:17:00 Tito Latini wrote:
>> chn_k "the---char-in-git", 20120331
>>
>> tito
>
> thanks, that's great!
>
>> It is not a bug really. Strings are i-time variables generally speaking
>> (although there are a couple of situations where they can be changed in
>> performance, but I can't remember which). Maybe the manual should be
>> clearer about this.
>>
>> Regards
>>
>> Victor
>
> Victor,  I understand, it is not a bug. But it is a bit unlogical  in some
> situations - if it is possible to create or change strings in k time (like
> sprintf, strcatk etc) there should be possibility to use the results in k-
> time?
>
> Is it so that a string in csound is rather a constant evaluated in init-time
> (like it happened in   kval invalue Sstring  - the value insterted to Sstring
> in ktime cannot be reached)?
>
> I imagine it would make more sense to be able to handle string more like in C
> - it could be rather address or pointer  and any opcode can read the
> information from that address in any moment? So that the k-time string
> modifications make sense.
>
> Maybe there is something internal that I do not undertand.
>
> tarmo
>
>
> 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"
>