Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webbased editor + qr/html export #131

Open
coderofsalvation opened this issue Feb 4, 2024 · 2 comments
Open

webbased editor + qr/html export #131

coderofsalvation opened this issue Feb 4, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@coderofsalvation
Copy link

I know its a stretch, but I overheard it in a gio videocall about sointu.
Such a cool usecase for non democoders.

@vsariola vsariola added the enhancement New feature or request label Feb 6, 2024
@vsariola
Copy link
Owner

vsariola commented Feb 6, 2024

I have compiled sointu for wasm & ran it inside browser in the past; it shouldn't take too much effort. It might require updating to a newer version of Gio and getting rid of the recovery file mechanism.

However... the past experience was that audio was stuttering heavily and the UI was laggy. I don't know if sointu synthesizer or Gio UI was the bigger culprit. Thus, I gave up on this quite quickly: giving users a stuttering, laggy preview is not a very good advertisement of a software :)

Maybe it would be worthwhile to check what's the status now; perhaps optimizations in Gio or elsewhere have made this realistic nowadays.

The hand-written sointu wasm VM is fast enough to render audio in browser at least; Peter Salomonsen has been working on integrating that synthesizer in his live-coding environment. #90 His idea was to just run the sointu-compile as a web service, taking care of all UI himself, but using the sointu create wasm synth modules & use these to render audio within browser. The pull request was never finished, but this at least proves that it is theoretically possible run the synth in browser.

@coderofsalvation
Copy link
Author

Thanks for getting back to me.
OK, so for now one could just use the native editor to produce the wasm.
Audio-stuttering is something which is bugging many wasm-compiled dsp-libraries, I guess it's just a matter of time before this all will work smooth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants