Pure data uses two audio buffer settings:

  • audiobuffer (set in Milliseconds- but converts that value to the nearest multiple of the blocksize)
  • blocksize (typically set to 64 samples)

The audiobuffer multiplies the blocksize buffer to accommodate system I/O, so the blocksize is the internal audio buffer size set typically to 64 samples.

http://booki.flossmanuals.net/pure-data/_full/

This allows greater accuracy when control rate operations are interlacing with audio nodes. Such as controlling volume from midi slider etc. Currently Vuo's audiobuffer runs at 512 samples- and only allows maximum accuracy of 93.75 control events per second. It would be fantastic for Vuo to use this dual buffer approach to improve audio control accuracy. Settings for buffers can also be published in preference menu.

EDIT: fixed explanation about blocksize v's buffers to correct explanation that Steve mentioned below- otherwise confusing.

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●○○○ — Up to a few days of work

Comments

If I understand correctly, Pd

smokris's picture
Submitted by
Feature status:
Waiting for review by Team Vuo
»
Open for community voting

If I understand correctly, Pd's -blocksize parameter specifies the number of samples per buffer, and Pd's -audiobuf specifies the number of buffers (it converts milliseconds to a power of 2 quantity of buffers).

In Vuo:

…so I'll interpret this feature request as allowing the composition to change the number of output buffers from its default of 8. I updated the title and opened it for community voting. I envision this being a port on nodes that output audio (currently just Send Audio Data).

I'm unsure whether in Vuo the port's value should be specified in milliseconds (which would be easier to understand from a latency perspective, but is imprecise since it requires rounding to a multiple of the buffer size), or an integer number of buffers (which directly specifies what Vuo should do, but may be more difficult to understand).

Thanks for clarifying that

alexmitchellmus's picture
Submitted by

Thanks for clarifying that @Steve. So that means that the I/O audio buffer for vuo currently is 4096 samples large?

I am interested in being able to change both- however currently being able to change the buffer would hugely improve MIDI timing etc (for example using an ADSR node- currently we only get ~100 events a second, we really need more as the data only enters the node once per event- unless it's buffered)

I'm unsure whether in Vuo the

alexmitchellmus's picture
Submitted by

I'm unsure whether in Vuo the port's value should be specified in milliseconds (which would be easier to understand from a latency perspective, but is imprecise since it requires rounding to a multiple of the buffer size), or an integer number of buffers (which directly specifies what Vuo should do, but may be more difficult to understand).

I think that keep it to Milliseconds, that way there will never be any confusion- if you are technically minded then you would know how to do it.

Feature status

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for. Vote your favorite features to the top! (How do Vuo feature requests work?)

  • Submitted to vuo.org
  • Reviewed by Team Vuo
  • Open for community voting
  • Chosen to be implemented
  • Released