Henrik Enquist
Henrik Enquist
Ping @pavhofman The new rate adjust feature of next11 gives a buffer level and rate adjust that oscillate. When using the following config: ``` --- devices: samplerate: 192000 chunksize: 4096...
should process one waveform based on a control input from another channel
I played a bit with iai yesterday and was really impressed by the stable results. Then I also made a quick attempt to use the iai_macro but couldn't figure out...
This adds a simple example to the readme for iai_macro, using the existing fibonacci bench.
This is a prototype that exposes a control for adjusting the sample rate of the Blackhole device by +- 1%. This functionality is provided by the standard Alsa loopback device...
## Expected Behavior (Mandatory) Running `CALL apoc.export.json.all(null, {stream: true})` streams useful data. ## Actual Behavior (Mandatory) Running `CALL apoc.export.json.all(null, {stream: true})` completes without error but returns no data. ## How...
I'm working on adding neon support to RustFFT, and wanted to try the `vld*` and `vst*` instrinsics added here: https://github.com/rust-lang/stdarch/pull/1224 First results were promising, but now I'm having a hard...
The existing volume control relies on having Volume filters in the pipeline. If the filter for some reason is missing (forgotten, wrong config loaded, etc), then volume control isn't enabled...
There is no limit for the Volume setting via the websocket. Giving a crazy value like +10000 dB overflows the max value of f64. Limit the range to something reasonable!