• bklindgren

    thank you all for the replies! some great info here - going to dive in with this information. thank you all again

    posted in technical issues read more
  • bklindgren

    ahh sorry for the very late reply :) yes, fellow violist! -Brian

    posted in pixel# read more
  • bklindgren

    I'm trying to program a patch patch that does sample by sample calculations on a 20 minute audio file, which ends up using some pretty big numbers toward the middle/end of the file (as the file has 50 million or so samples).

    I'm using an until object, int object and (+) object to advance sample by sample, but the function is maxing out at "1.67772e+07" samples for some reason. It doesn't seem like any of these objects alone have a number size that would create this limit, but when they're used together like this my 'counter' stops at "1.67772e+07".

    I've attached a test/demo patch. Any ideas? test.pd

    posted in technical issues read more
  • bklindgren

    You can find the pix2sig help file in: ⁨~ ▸ Documents⁩ ▸ ⁨Pd⁩ ▸ ⁨externals⁩ ▸ ⁨Gem⁩

    You might be getting "no method for gem-state" if you connect an object that takes signal input to the first outlet of the pix2sig object - the signal outputs are outlets 2, 3 and 4. Outlet 1 is for the gem data to pass through.

    "bad vector size" could be because you've used block~ or switch~ to something other than the vector size you've set in your prefs. I believe PD adc and dac need to run at the same vector size as what's in the preferences. To do this you could route the signal into another pd window, and there have your dac object.

    posted in pixel# read more
Internal error.

Oops! Looks like something went wrong!