Cycling 74 » Topic: dspstate~ bug or feature? http://cycling74.com/forums/topic/dspstate-bug-or-feature/feed Thu, 20 Jun 2013 04:59:19 +0000 http://bbpress.org/?v=2.2.4 http://cycling74.com/forums/topic/dspstate-bug-or-feature/#post-44848 <![CDATA[dspstate~ bug or feature?]]> http://cycling74.com/forums/topic/dspstate-bug-or-feature/#post-44848 Thu, 23 Jul 2009 07:54:14 +0000 stefantiedje I need the actual signal vector size within all kinds of patches, but dspstate~ doesn’t report the correct signal vector size inside pfft~ or poly~. I think it should…
I haven’t found a way to do this directly. Within a pfft~ there is fftinfo~ but it doesn’t work inside of subpatchers, and waisting extra inputs for feeding it into a subpatcher lacks the required beauty…Wink

My favorite answer to this issue would be: it’s a bug, will be fixed for the next incremental…
but useful workarounds are welcome as well…

If there are worries about backward compatibility for a fixed dspstate~, I suggest to add an attribute/message to allow the real vs to be reported. (That object has not too many attributes yet…Wink
But I can’t imagine that a correct vs would hurt anywhere. All patches I know which want to deal with the global dsp settings use adstatus…

Stefan

]]>