I’ve recently been investigating whether it’s possible to make the web version of FMOD work in a background thread, once in a while when I have a free moment.
The reason is that when heavy synchronous work is being handled on the main thread, fmod also stops updating its buffer, causing the sound to loop briefly and then release.
Of course, I’ve checked the documentation and don’t expect official support, but I’m wondering if there might be a workaround if NW.js is a standalone program that doesn’t need to support all web browsers and is a fixed version of Node.
The most effective way would be to build a Node native extension, but I don’t have the skills to do that, so I’ve been looking into other ways and found the following issue, which shows that NW.js can use the native API as is in the web worker. (fs)
Other than this, I’d be interested to hear if anyone else has any techniques for preventing web fmods from being interrupted, and the level of difficulty of the problems you have to solve to do so.
Also is there any updates fmod web on Node.js?
Just curious that is there any key performance wise difference of fmod’s behavior between Node.js and web browsers.
Because I remember when I first tried to put it in NW.js a long time ago, there was a feature to detect the Node.js platform and do something different (which of course didn’t work in these days), what about the latest version?