quinn VS opus

Since it lives on top of UDP, I believe all you need is SOCK_DGRAM, right? The rest of QUIC can be in a userspace library ergonomically designed for your programming language e.g. https://github.com/quinn-rs/quinn - and can interoperate with others who have made different choices.

Alternately, if you need even higher performance, DPDK gives the abstractions you'd need; see e.g. https://dl.acm.org/doi/abs/10.1145/3565477.3569154 on performance characteristics.

> Making things thread safe for runtime-agnostic utilities like WebSocket is yet another price we pay for making everything multi-threaded by default. The standard way of doing what I'm doing in my code above would be to spawn one of the loops on a separate background task, which could land on a separate thread, meaning we must do all that synchronization to manage reading and writing to a socket from different threads for no good reason.

Why so? Libraries like quinn[1] define "no IO" crate to define runtime-agnostic protocol implementation. In this way we won't suffer by forcing ourselves using synchronization primitives.

Also, IMO it's relatively easy to use Send-bounded future in non-Send(i.o.w. single-threaded) runtime environment, but it's almost impossible to do opposite. Ecosystem users can freely use single threaded async runtime, but ecosystem providers should not. If you want every users to only use single threaded runtime, it's a major loss for the Rust ecosystem.

Typechecked Send/Sync bounds are one of the holy grails that Rust provides. Albeit it's overkill to use multithreaded async runtimes for most users, we should not abandon them because it opens an opportunity for high-end users who might seek Rust for their high-performance backends.

[1]: https://github.com/quinn-rs/quinn

quicssh-rs is quicssh rust implementation. It is based on quinn and tokio

Regarding Quinn, I had a blast this week resurrecting an old PR. Looking forward to the next!

By studying u/djcu/hachyderm.io (and others!) excellent work in Quinn, doing a sans I/O implementation of QUIC https://github.com/quinn-rs/quinn we have a way forward.

QUIC isn't web/wasm-compatible because of https://github.com/quinn-rs/quinn/issues/1388, so durian wouldn't either since it's built on top of it.

Quinn, as in the implementation of QUIC? https://github.com/quinn-rs/quinn

You are right, I am planning to switch the transport to UDP + quic using the awesome QUINN library, https://github.com/quinn-rs/quinn .

Hi, I am new to the community, I just started learning rust and created a secure UDP tunnel based on the Quinn library, thanks to Quinn, I didn't need to go into the detail of the QUIC protocol and quickly created a UDP tunnel, and thanks to the BBR congestion control algorithm it uses, the tunnel performs quite well with lousy and long fat network, I didn't do any benchmark, but it performs a lot better (higher throughput with LFN) than most of other TCP tunnel implementations I used before.

Opus doesn't support 44.1 kHz because compatibility and effort/benefit ratio:

https://github.com/xiph/opus/issues/43

The browser audio limitation is presumably a workaround to some bug or performance limitation that was relevant at some point in history (the site was created in 2014).

There is a pattern here (that also goes with the author's prior article on inverting gauss' sum formula): Generally if if you can make a formula that counts the combination of things you can convert that into a code to encode and decode those combinations into indexes.

So for example the opus audio codec needs to encode/decode vectors of dimension n whos absolute values sum to k. https://github.com/xiph/opus/blob/master/celt/cwrs.c#L74

Or this rolling cuckoo filter that optimally encode/decode four sorted numbers in a range 0..2N with the constraint that the they span a range of N. https://github.com/sipa/bitcoin/blob/202006_cuckoo_filter/sr...

If you're lucky there will be closed form expressions for the encoding and decoding equations. (There for both of the above, at least for some parameters, but in both those examples the implementations use small tables because for the ranges involved the tables end up being faster than sqrts).

Too bad 10Hz is a too slow to generate audio-rate bitops music.

(e.g. https://github.com/xiph/opus/blob/master/tests/test_opus_enc... )

Could anyone help me get a disk image files for older Global Underground CDs? I encoded my old CDs into subpar mp3 files, and I'd now like to have high-quality Opus encodings and experiment across various bitrates.

Presumably, OP is referring to the Opus audio codec versus Dolby's AC3 codec.

Indeed. https://opus-codec.org/

If there are multiple tags with the same name, Ffmpeg will only use the last tag. If you really need to have multiple tags with the same name in your OPUS files, use opusenc instead (https://opus-codec.org/). Beware that some playback software does not display multiple artists gracefully.

AFAIK ogg isn't really suitable for low latency audio streaming. Consider the Opus codec instead.

I have asked on GitHub also https://github.com/xiph/opus/issues/263 in anyone wants to respond there.