From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] anyone using sunshine?
Date: Tue, 30 Jan 2024 10:25:56 +1300 [thread overview]
Message-ID: <CAKiAkGS8=GXD9r1ut-8+oOEKzCsTJcSpZ3uvztEH0HiAYTF4AQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw59xg6V5nkvwxUtS1XZw9zoyK7Bx2M9hd1KFHR2=mZj+A@mail.gmail.com>
Yes I have been using it successfully for the last couple of years and
it works well. However the vaapi encoder path needed for non nvidia
encoding has some bugs with how bandwidth calculation works for FEC
insertion. So YMMV for anything above around 30mbit encodes (which is
plenty for 4K streaming with h265). I use this for streaming to my
Lounge TV for Videoconfs/Games etc.
I've also managed to get it to work headless with Sway and seatd for
pseudo cloud gaming to a server downstairs with a GPU in it.
Would really like to see someone improve the non nvenc pathway.
Having spent a lot of time using various remote framebuffer solutions
over the years i can safely say sunshine is the first system which
truely makes accelerated remote desktops viable options; works with
containers too so long as you expose the host /dev/drm node to the
container.
On Sun, 28 Jan 2024 at 00:38, Dave Taht via Cerowrt-devel
<cerowrt-devel@lists.bufferbloat.net> wrote:
>
> https://arstechnica.com/gaming/2023/04/nvidias-gamestream-is-dead-sunshine-and-moonlight-are-better-replacements/
>
> --
> 40 years of net history, a couple songs:
> https://www.youtube.com/watch?v=D9RGX6QFm5E
> Dave Täht CSO, LibreQos
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
prev parent reply other threads:[~2024-01-29 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 11:38 [Make-wifi-fast] " Dave Taht
2024-01-29 21:25 ` Joel Wirāmu Pauling [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKiAkGS8=GXD9r1ut-8+oOEKzCsTJcSpZ3uvztEH0HiAYTF4AQ@mail.gmail.com' \
--to=joel@aenertia.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox