3 ms·
Thanks for your feedback! I honestly did not expect Weylus to get that much attention. Unfortunately my time is limited and I am not too comfortable taking dona
by HMH 6y ago
Thanks for your feedback! I honestly did not expect Weylus to get that much attention. Unfortunately my time is limited and I am not too comfortable taking donations then.
> 1) From the video, latency would need to go way down.
On the encoding side the only thing I can think of to improve latency is to try hardware encoding if available. Something like NVENC might bring it down. That leaves optimization for the network protocol to use, something based on udp is likely better suited than websockets. And finally mobile apps probably leave more room for improving playback latency (and enable other protocols than using websockets).
> 2) Pressure support is important, if not critical.
It is pretty straightforward to add new input methods, I will add some instructions to the Readme, maybe someone will step forward and add support for macOS and Windows.
> 3) Packaging.
There already is a .deb, although I still need to fix some dependency issue [1].
> Next step would be to go from mirroring to second display.
Apparently this is almost possible right now (at least with X11), see [2].
> breadcrumbs
I think this is the way to go, I will add some more info on how to contribute soon.
[1]: https://github.com/H-M-H/Weylus/issues/6 https://github.com/H-M-H/Weylus/issues/6
[2]: https://github.com/H-M-H/Weylus/issues/5 https://github.com/H-M-H/Weylus/issues/5
- wegs 6y agoThank you! On latency, the thing other tools used to really bring it down is a wired USB connection. And yes: This is something in which there will be an almost desperate amount of interest in some communities. I think the bottleneck on how much attention it receives is, quite frankly, whether individuals in those communities find out about it. I'm committed at about 160% capacity for the rest of the fiscal year, but if this were a more normal time, I'd probably hack on this myself.