morgan/UxPlay
1
0
Fork 0
mirror of https://github.com/morgan9e/UxPlay synced 2026-04-15 00:34:05 +09:00
Code Issues Packages Projects Releases Wiki Activity

edit README troubleshooting advice

Browse Source
This commit is contained in:
fduncanh
2022-01-02 03:52:05 -05:00
parent 0c4f02b61a
commit d772d1b6a2
3 changed files with 24 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.html
View File

@@ -88,8 +88,9 @@
<p>This shows that a <em>DNS-SD</em> service is working, but a firewall on the server is probably blocking the connection request from the client. (One user who insisted that the firewall had been turned off turned out to have had <em>two</em> active firewalls (<em>firewalld</em> and <em>ufw</em>) <em>both</em> running on the server!) If possible, either turn off the firewall to see if that is the problem, or get three consecutive network ports, starting at port n, all three in the range 1024-65535, opened for both tcp and udp, and use “uxplay -p n” (or open UDP 6000, 6001, 6011 TCP 7000,7001,7100 and use “uxplay -p”).</p>
<h3 id="problems-after-the-client-server-connection-has-been-made">3. Problems <em>after</em> the client-server connection has been made:</h3>
<p>For such problems, use “uxplay -d” (debug log option) to see what is happening: it will show how far the connection process gets before the failure occurs.</p>
<p><strong>Most of such problems are due to a GStreamer plugin that doesn’t work on your system</strong>: (by default, GStreamer uses an algorithm to guess what is the “best” plugin to use on your system).</p>
<p>The most common of these problems are connected to the GStreamer VAAPI plugin (for hardware-accelerated intel graphics), Your first attempt to resolve a problem should be to find out if the VAAPI plugin is installed, and if so, uninstall it. (If this does not fix the problem, you can reinstall it.)</p>
<p><strong>Most of such problems are due to a GStreamer plugin that doesn’t work on your system</strong>: (by default, GStreamer uses the “autovideosink” algorithm to guess what is the “best” plugin to use on your system).</p>
<p>Sometimes “autovideosink” may select the OpenGL renderer “glimagesink” which may not work correctly on your system. Try the options “-vs ximagesink” or “-vs xvimagesink” to see if using one of these fixes the problem.</p>
<p>Other reported problems are connected to the GStreamer VAAPI plugin (for hardware-accelerated Intel graphics, but not NVIDIA or AMD graphics). Your next attempt to resolve a problem should be to find out if the gstreamer1.0-vaapi plugin is installed, and if so, uninstall it. (If this does not fix the problem, you can reinstall it.)</p>
<p>There are some reports of other GStreamer problems with hardware-accelerated Intel graphics. One user (on Debian) solved this with “sudo apt install intel-media-va-driver-non-free”. This is a driver for 8’th (or later) generation "*-lake" Intel chips, that seems to be related to VAAPI accelerated graphics.</p>
<p>You can try to fix audio problems by using the “-as <em>audiosink</em>” option to choose the GStreamer audiosink , rather than have autoaudiosink pick one for you. The command “gst-inspect-1.0 | grep Sink | grep Audio” " will show you which audiosinks are available on your system. (Replace “Audio” by “Video” to see videosinks). Some possible audiosinks are pulsesink, alsasink, osssink, oss4sink, and osxaudiosink (macOS).</p>
<p>If you ran cmake with “-DZOOMFIX=ON”, check if the problem is still there without ZOOMFIX. ZOOMFIX is only applied to the default videosink choice (“autovideosink”) and the two X11 videosinks “ximagesink” and “xvimagesink”. ZOOMFIX is only designed for these last two; if autovideosink chooses a different videosink, ZOOMFIX is now ignored. If you are using the X11 windowing system (standard on Linux), and have trouble with screen-sharing on Zoom, use ZOOMFIX and “-vs xvimagesink” (or “-vs ximagesink” if the previous choice doesn’t work).</p>

13
README.md
View File

@@ -365,12 +365,17 @@ For such problems, use "uxplay -d " (debug log option) to see what is happenin
the failure occurs.
**Most of such problems are due to a GStreamer plugin that doesn't work on your system**: (by default,
GStreamer uses an algorithm to guess what is the "best"
GStreamer uses the "autovideosink" algorithm to guess what is the "best"
plugin to use on your system).
The most common of these problems are connected to the GStreamer VAAPI plugin
(for hardware-accelerated intel graphics),
Your first attempt to resolve a problem should be to find out if the VAAPI plugin is installed, and if so, uninstall it.
Sometimes "autovideosink" may select the OpenGL renderer "glimagesink" which
may not work correctly on your system. Try the options "-vs ximagesink" or
"-vs xvimagesink" to see if using one of these fixes the problem.
Other reported problems are connected to the GStreamer VAAPI plugin
(for hardware-accelerated Intel graphics, but not NVIDIA or AMD graphics).
Your next attempt to resolve a problem should be to find out if the
gstreamer1.0-vaapi plugin is installed, and if so, uninstall it.
(If this does not fix the problem, you can reinstall it.)
There are some reports of other GStreamer problems with hardware-accelerated Intel graphics. One user

19
README.txt
View File

@@ -460,14 +460,19 @@ happening: it will show how far the connection process gets before the
failure occurs.
**Most of such problems are due to a GStreamer plugin that doesn't work
on your system**: (by default, GStreamer uses an algorithm to guess what
is the "best" plugin to use on your system).
on your system**: (by default, GStreamer uses the "autovideosink"
algorithm to guess what is the "best" plugin to use on your system).
The most common of these problems are connected to the GStreamer VAAPI
plugin (for hardware-accelerated intel graphics), Your first attempt to
resolve a problem should be to find out if the VAAPI plugin is
installed, and if so, uninstall it. (If this does not fix the problem,
you can reinstall it.)
Sometimes "autovideosink" may select the OpenGL renderer "glimagesink"
which may not work correctly on your system. Try the options "-vs
ximagesink" or "-vs xvimagesink" to see if using one of these fixes the
problem.
Other reported problems are connected to the GStreamer VAAPI plugin (for
hardware-accelerated Intel graphics, but not NVIDIA or AMD graphics).
Your next attempt to resolve a problem should be to find out if the
gstreamer1.0-vaapi plugin is installed, and if so, uninstall it. (If
this does not fix the problem, you can reinstall it.)
There are some reports of other GStreamer problems with
hardware-accelerated Intel graphics. One user (on Debian) solved this