You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really like the performance and footprint of the current bassoonplayer.
The planned features are awesome, but is it an idea to somehow implemented all this in a modular way?
The thing is that the current MOD/XM player works 100% CRACKLE-FREE on lowcpu browsers, which ALL (emscripten) mod/xm players fail to do.
I'm probably preaching to the converted already, but how about being able to 'build' the player-directory with only the desired formats?
xm/mod: core
s3m, it, octamed, etc: opt in using cli flag
The pattern i noticed across mobile webbrowsers is: as soon as emscripten, polyphony or synthesis is introduced, all bets are off concerning cracklefree playback. Even highly optimized engines like https://ide.csound.com can't seem to escape this.
Anyways, my suggestion is that eventually we could basically prebuild:
player/bassoonplayer.core.min.js <-- xm/mod in case you want to run graphics on the same thread, small filesize e.g.
player/bassoonplayer.full.min.js <-- dont care, give me everything
That way developers can scale up/down depending on their usecase.
Thanks for all the great work so far!
The text was updated successfully, but these errors were encountered:
Hi,
I really like the performance and footprint of the current bassoonplayer.
The planned features are awesome, but is it an idea to somehow implemented all this in a modular way?
The thing is that the current MOD/XM player works 100% CRACKLE-FREE on lowcpu browsers, which ALL (emscripten) mod/xm players fail to do.
I'm probably preaching to the converted already, but how about being able to 'build' the player-directory with only the desired formats?
Anyways, my suggestion is that eventually we could basically prebuild:
That way developers can scale up/down depending on their usecase.
Thanks for all the great work so far!
The text was updated successfully, but these errors were encountered: