odd poke~ behaviour in m4l, working fine in when open in max…

hi there, getting back to an older issue which is still giving me stress.

I had posted earlier on this (http://cycling74.com/forums/topic.php?id=34746) but please pay this no mind (much obliged to leckerfisch for responding though), must have put the post together late at night, and foolishly said peek~ when i meant poke~.

So: the issue is this: i’m using poke~ to write a buffer. Works as expected when open in max, but when i close the m4l patch and run it in live, the last 1/10 or so of the buffer will not have anything written to it.

I attach a patch which shows this behaviour on my machine. Simply set the ms length, and the scope~ object shows the poke~ input, and the buffer displays the sample written. As i said, when i have it open in max it writes the full buffer. When closed and running in live, there is a gap of silence. Any ideas what might be causing this behaviour? Much obliged for any input…

http://lokeymassive.net/misc/poketest.amxd