[Csnd] csound6: getting i-value of a kArray member
Date | 2013-11-14 14:27 |
From | Tarmo Johannes |
Subject | [Csnd] csound6: getting i-value of a kArray member |
Hi, It seems, that using i(gkArr[member]) does not work and returns always 0. Or perhaps I have misunderstood something. Here a simple example: |
Date | 2013-11-14 22:37 |
From | Jim Aikin |
Subject | [Csnd] Re: csound6: getting i-value of a kArray member |
print runs at i-time. I think you're trying to print data from an array that has not yet been filled with data. (I'm not an expert. I could be wrong.) -- View this message in context: http://csound.1045644.n5.nabble.com/csound6-getting-i-value-of-a-kArray-member-tp5729623p5729670.html Sent from the Csound - General mailing list archive at Nabble.com. |
Date | 2013-11-16 19:34 |
From | Steven Yi |
Subject | Re: [Csnd] Re: csound6: getting i-value of a kArray member |
I think the issue is that the code gets compiled into something like: #k1 array_get gkArr, 0 #i1 i #k1 and that the version of the array_get opcode is only run at k-time. At i-time, the value would be just 0 as the results have shown as the k-var is uninitialized. Tarmo: Could you file a bug with the CSD attached? I think it wouldn't be too much work to fix but just needs some thought to ensure the fix won't break anything. Thanks! steven On Thu, Nov 14, 2013 at 5:37 PM, Jim Aikin |
Date | 2014-01-16 14:11 |
From | Tarmo Johannes |
Subject | Re: [Csnd] Re: csound6: getting i-value of a kArray member |
After very long time, I filed now a ticket. Hopefully it is easy to fix. tarmo On Saturday 16 November 2013 14:34:28 Steven Yi wrote: > I think the issue is that the code gets compiled into something like: > > #k1 array_get gkArr, 0 > #i1 i #k1 > > and that the version of the array_get opcode is only run at k-time. At > i-time, the value would be just 0 as the results have shown as the > k-var is uninitialized. > > Tarmo: Could you file a bug with the CSD attached? I think it > wouldn't be too much work to fix but just needs some thought to ensure > the fix won't break anything. > > Thanks! > steven > > On Thu, Nov 14, 2013 at 5:37 PM, Jim Aikin |