Currently the ScriptProcessorNode legal bufferSize values are all multiples of the default renderQuantumSize (128).
However, we now have configurable render quantum sizes which may not divide or be divided by the selected bufferSize.
It's not clear what implementations should do in this case. Should they add additional buffering internally, which will increase latency? Should they reject ScriptProcessorNodes created with bufferSizes that are not multiples of the renderQuantumSize? Or perhaps something else?
Specifying it precisely will help with interoperability between implementations.
Currently the ScriptProcessorNode legal bufferSize values are all multiples of the default renderQuantumSize (128).
However, we now have configurable render quantum sizes which may not divide or be divided by the selected bufferSize.
It's not clear what implementations should do in this case. Should they add additional buffering internally, which will increase latency? Should they reject ScriptProcessorNodes created with bufferSizes that are not multiples of the renderQuantumSize? Or perhaps something else?
Specifying it precisely will help with interoperability between implementations.