the-drunk-coder / ruffbox Goto Github PK

I try to understand your code cause I would like to implement a web sequencer. Why do you need to use JS setTimeout? Doesn't Rust have an timer system? Or would this timer need separate thread to don't block the whole Rust process?

Have you thought about using non blocking timer like it is often done on microcontroller? I remember to have used this on esp-open-rtos https://github.com/SuperHouse/esp-open-rtos
Have a look there: https://en.wikipedia.org/wiki/FreeRTOS#Implementation

FreeRTOS implements multiple threads by having the host program call a thread tick method at regular short intervals. The thread tick method switches tasks depending on priority and a round-robin scheduling scheme. The usual interval is 1 to 10 milliseconds (1/1000 to 1/100 of a second), via an interrupt from a hardware timer, but this interval is often changed to suit a particular application.

I guess you might still need to somehow trigger the tick on regular interval and for this you might need setTimeout. Or maybe it would be possible to run the Rust code in loop and regurlarly call a yield() function to check if a timer is ready.

When starting server.sh, the following output is printed:

Serving HTTP on 0.0.0.0 port 1234 (http://0.0.0.0:1234/) ...

When opening that link in a browser, the following error message appears in a popup:

AudioWorklet isn't supported... It cannot work.

I believe the reason is that AudioWorklet is only available in a secure context (see https://developers.google.com/web/updates/2017/12/audio-worklet). The workaround I found is to connect to http://localhost:1234/ instead, as http://localhost is considered secure for local testing (as per the previous link).

The demo wasn't working. I found this error in the console:

Uncaught TypeError: Cannot perform %TypedArray%.prototype.set on a detached ArrayBuffer
    at Float32Array.set (<anonymous>)
    at AudioWorkletProcessor.process (worklet.js?t=1600116398531:185)