# Clarification on ASIO Spec for buffer size granulatity

**URL:** <https://forums.steinberg.net/t/clarification-on-asio-spec-for-buffer-size-granulatity/201896>\
**Category:** ASIO\
**Created:** [June 14, 2019, 2:09am UTC](https://forums.steinberg.net/t/clarification-on-asio-spec-for-buffer-size-granulatity/201896 "2019-06-14T02:09:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bradr](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/bradr/32/129833_2.png) [@bradr](https://forums.steinberg.net/u/bradr)\
**Post date:** [June 14, 2019, 2:09am UTC](https://forums.steinberg.net/t/clarification-on-asio-spec-for-buffer-size-granulatity/201896/1 "2019-06-14T02:09:02Z")

</div>

Hi,

I was wondering if someone from Steinberg could clarify the meaning of the granularity setting returned from ASIOGetBufferSize. I have a customer with an Focusrite device that’s returning the following:

```nohighlight
asio - getBufferSize returned min=8 max=1024 pref=56 granularity=16

```

Which could be interpreted two ways. Either:

a) starting at 8 and increasing by 16 ie: 8, 24, 40, 56, 72, 88, 104 etc…  
b) multiples of 16 between 8 and 1024. ie: 16, 32, 48, 64, etc…

Note that the driver is returning 56 as the preferred buffer size, which is not a valid buffer size if you take the second interpretation - that to me suggests the first interpretation is what they mean.

The response from the drive is ambiguous but it’d be great to get some clarification on how a host should treat such a response.

Brad

---

<div class="post-metadata">

**Author:** ![Arne\_Scheffler](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/arne_scheffler/32/92023_2.png) [@Arne\_Scheffler](https://forums.steinberg.net/u/Arne_Scheffler)\
**Post date:** [June 18, 2019, 8:56am UTC](https://forums.steinberg.net/t/clarification-on-asio-spec-for-buffer-size-granulatity/201896/2 "2019-06-18T08:56:42Z")

</div>

it’s a)