I'm fairly new to Max/MSP 6.1.2 and ran into a problem with dspstate~ when working on a latency compensation for a looper patch.
I searched the forum and the reference but did not find any answers, so I hope you can shed some light on this.
According to the documentation, outlet 3 is supposed to give the DSP signal vector size, and outlet 4 the IO Vector size.
However, from both outlets I always get the same values with correspond to the DSP signal vector size.
See the screenshot for a comparison with the audio settings window.
What's going on there?
And I'm also not quite sure what the correct value for latency compensation is.
2 * IO-vector + 1 * DSP-vector seems to be close, but not perfect. What's the correct way of computing this?
Thanks for any hints…
I confirm the same behavior in Max 6.0.8 on Mac OS 10.7.5, MacBook Pro. Suggest to file a bug report.
I did, and they replied to me:
Sorry for the inconvenience – I can indeed see some weirdness here.
We’ll take a look at it – in the meantime, hopefully you will be able to get by with the adstatus object
And indeed, the adstatus object does the job…
Cool. Thanks for making the report.
Christopher, do you know about latency calculation?
From my original post:
And I’m also not quite sure what the correct value for latency compensation is.
2 * IO-vector + 1 * DSP-vector seems to be close, but not perfect. What’s the correct way of computing this?
C74 RSS Feed | © Copyright Cycling '74