Chris Rolfe

Gen~ objects inside poly~'s need a 'reload' message on loadbang. This prevents the extra leading zeroes.

loadbang

message

comment

gen~

sig~

out~

-----------------------------------------------------

Using gen~ within a poly~ appears to introduce a number of zeroes at the start of the first run.

Here's an example comparing two poly~ voices, one without gen~ and one with gen~. The gen~ doesn't actually do anything. It just sits there. Both poly~s should theoretically produce the same output — a constant value of 1.0. On my machine (Max 6/7, El Capitan, MB Pro 2015 model), the poly~ with gen~ produces extra zeroes the first time it runs. The number is sometimes equal to vector size, sometimes more. Subsequent DSP restarts behave as expected.

Any thoughts on what is happening here and/or workarounds? It's a puzzle to me.

Here's the test patcher and poly~ voices as attachments (download and remove the .txt file extension to open in Max):

TEST gen~ in poly~.maxpat

test-vox-with-gen.maxpat

test-vox.maxpat


-----------------------------------------------------
Using gen~ within a poly~ appears to introduce a number of zeroes at the start of the first run. 

Here's an example comparing two  poly~ voices, one without gen~ and one with gen~. The gen~ doesn't actually do anything. It just sits there. Both poly~s  should theoretically produce the same output — a constant value of 1.0. On my machine (Max 6/7, El Capitan, MB Pro 2015 model), the poly~ with gen~  produces extra zeroes the first time it runs. The number is  sometimes equal to vector size, sometimes more. Subsequent DSP restarts behave as expected. 

Any thoughts on what is happening here and/or workarounds? It's a puzzle to me. 

Here's the test patcher and poly~ voices as attachments (download and remove the .txt file extension to open in Max): 

edit: Problem solved! 
Gen~ objects inside poly~'s need a 'reload' message on loadbang. This prevents the extra leading zeroes.
 

---------

gen~ in poly~ padding extra zeroes on first run