> It is only a little confusion, from the man page: > > "tabplay plays back a group of k-rate signals, previously > recorded by tabrec into a table." > > me However, with test.txt 0 1.0e-2 2.0e-2 3.0e-2 4.0e-2 1e+2 2e+2 3e+2 4e+2 1e+3 2e+3 3e+3 4e+3 and -d sr = 44100 ksmps = 64 instr 1 k1 init 0 k2 init 0 tabplay 1, 6, 1, k1, k2 printk2 k1 printk2 k2 endin f1 0 16 -23 "test.txt" i1 0 .05 e we get new alloc for instr 1: i1 0.01000 i1 0.02000 i1 0.03000 i1 0.04000 i1 100.00000 i1 200.00000 i1 300.00000 i1 400.00000 i1 1000.00000 i1 2000.00000 i1 3000.00000 i1 4000.00000 i1 0.01000 i1 0.02000 i1 0.03000 i1 0.04000 i1 100.00000 i1 200.00000 i1 300.00000 i1 400.00000 i1 1000.00000 i1 2000.00000 i1 3000.00000 i1 4000.00000 tito On Thu, May 31, 2012 at 12:58:26PM +0200, Anders Genell wrote: > Hi! > > I am testing tabplay in combination with GEN23 for a project, and in the manual it says > > Syntax > > tabplay ktrig, knumtics, kfn, kout1 [,kout2,..., koutN] > Since there are several kouts, is there a way the create matrix f-tables, so that each column corresponds to a separate kout? > I can't seem to figure out how. If that's not possible, what then is the intended use for the multiple kouts? > > Also, I have filled a table using GEN23 with an ASCII file generated by GNU/Octave. Octave stores values in "scientific" format, i.e. something like 5.89345e+2, and GEN23 does not seem to support that fully since when using tabplay I get different values than what's actually stored. I might be doing something wrong, but if not, maybe such support could added to csound6 :-) > > In the meanwhile I will have to figure out how to get Octave to store non-scientific format to an ASCII file... > > Best regards, > > /Anders