Ability to change audio buffer size to different values within software settings. (Currently 512)

Useful for reducing latency.

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●●○○ — A few weeks of work

Comments

Just a question @Steve, would

alexmitchellmus's picture
Submitted by

Just a question Steve (@smokris), would this be best as a node or a preferences item? If we export Apps there may be pros and cons for each implementation?! For example you may want your app to be able to check the hardware of computer then assign a buffer value. (maybe check hardware node could be future node request?)

Also if its a menu item then people can change manually (in app).

Possibly it should be both?! Or at least preferences item first.

would this be best as a node

smokris's picture
Submitted by

would this be best as a node or a preferences item?

I envision this being a port on nodes that receive or send audio data (e.g., Receive Live Audio, Play Audio File, Play Movie, Send Live Audio). Then the composition can statically or algorithmically decide which buffer size to use (or expose it as a preference for the person using the composition, using Make Button or other forthcoming UI widgets).

Is that to say you could mix

smokris's picture
Submitted by

Is that to say you could mix audio buffer settings? A small size for midi computations and control inlets- yet a large buffer for summing etc?

Yes, this would enable a single composition to have multiple independent audio event streams with different buffer sizes. (I'm not yet sure whether OS X allows opening the same device with different buffer sizes though.)

Is there an easy way to make this happen without changing all audio nodes?

(Not that I know of.)

@Steve are we sure multiple

alexmitchellmus's picture
Submitted by

Steve (@smokris) are we sure multiple size buffers is the best road to take? Are there any examples of other software that has this solution? I can imagine that they may get out of time?

Considering that each buffer needs to be computed before handing it to the next node- it sounds complex.

Maybe simply allow a user to set the block size and buffer multiples in the .vuo file?

That way someone could then make a composition a node and simply change that #define (or however it is encoded)

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

Votes

10 votes so far!

Who voted?

Kewl's picture
timwessman's picture
alexmitchellmus's picture