Adds support for JS to configure ring-buffer size. #37
Conversation
The default buffer sizes chosen, at least in Win32, are extremely conservative. Sure, a skip in audio will be extremely rare, but for any type of real-time application (video-games), the audio is near-unusable, because sounds will play several seconds after the event that triggered them. I've exposed the buffer-size fields all the way up to the JS api, so that the application developer can choose the best balance between reliability and performance to fit their needs. So far this is only supported on Win32 (and ignored on other platforms), but I plan on implementing additional platforms in the future.
|
I desire a similar change for Linux. I would like to use smaller buffers so there is less latency at startup and more immediate stops when end is called. On Jul 9, 2014, at 9:14 PM, anprogrammer [email protected] wrote:
|
|
I just tested this branch on my macbook pro. The example does not play. There is no sound, no errors. |
|
Exit status of the above example is 0. Can I grab any debug logs to help track this down? The previous commit (0888eb8) plays fine. |
The default buffer sizes chosen, at least in Win32, are extremely
conservative. Sure, a skip in audio will be extremely rare, but for any
type of real-time application (video-games), the audio is near-unusable,
because sounds will play several seconds after the event that triggered
them.
I've exposed the buffer-size fields all the way up to the JS api, so
that the application developer can choose the best balance between
reliability and performance to fit their needs. So far this is only
supported on Win32 (and ignored on other platforms), but I plan on
implementing additional platforms in the future.