3 ms·
The demo I linked uses a slowed down profile with lots of error correction applied in an attempt to get longer ranges working. I've tried to expose all the knob
by brian-armstrong 6y ago
The demo I linked uses a slowed down profile with lots of error correction applied in an attempt to get longer ranges working. I've tried to expose all the knobs for this on the profile system to make it configurable though. Looks like yours is quite a bit faster.
Have you done much testing with long range and non line-of-sight transmission? The acoustic echoes present some interesting challenges.
edit: Oh also it'd be nice to compare notes about mobile devices sometimes. At least for Quiet I've found the transmission quality is very dependent on specifically how the mic/speakers are set up and it can be tricky to avoid hidden resamplers and noise cancelation.
- ggerganov 6y ago> Have you done much testing with long range and non line-of-sight transmission? Not much. I tested this today at home and ggwave does not perform too bad. Even without direct line-of-sight it is still able to pick up the data. Hard to give quantitative description of the performance - it's good enough to make me satisfied :) > Oh also it'd be nice to compare notes about mobile devices sometimes. At least for Quiet I've found the transmission quality is very dependent on specifically how the mic/speakers are set up and it can be tricky to avoid hidden resamplers and noise cancelation. True. I am still not sure if noise cancellation helps or not. I guess it also depends on the noise cancellation implementation. When running in a browser, I usually disable it.