[maxmsp] Re: Re: cycle~ size limit
volker böhm
vboehm at gmx.ch
Thu Jun 21 02:18:27 MDT 2007
- Previous message: [maxmsp] Re: Re: cycle~ size limit
- Next message: [maxmsp] cycle~ size limit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 20 Jun 2007, at 22:29, Roman Thilenius wrote: >> >> How about sending the set message? ;-) > > > yeah, no, it works in all situaiton but not when a running cycle > reads from a buffer. > the new buffer is written from load, but cycle still reads from the > old (physically) buffer. > if you have luck they even play both, the old and the new version. maybe i get you wrong, but this works just fine: #P window setfont "Sans Serif" 9.; #P flonum 122 238 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; #P window linecount 1; #P newex 91 265 41 196617 *~ 0.1; #P newex 103 105 68 196617 buffer~ x 12; #P message 103 73 30 196617 read; #P message 161 147 33 196617 set x; #P user led 68 300 17 17 0 150; #P newex 85 300 30 196617 dac~; #P flonum 91 151 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; #P newex 91 187 70 196617 cycle~ 250 x; #P connect 4 0 0 0; #P connect 1 0 0 0; #P connect 0 0 7 0; #P connect 5 0 6 0; #P connect 6 1 4 0; #P connect 7 0 2 0; #P connect 7 0 2 1; #P connect 8 0 7 1; #P hidden connect 3 0 2 0; #P window clipboard copycount 9;
- Previous message: [maxmsp] Re: Re: cycle~ size limit
- Next message: [maxmsp] cycle~ size limit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
