This shows that a DNS-SD 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 two active firewalls (firewalld and ufw) both 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”).
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.
+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. You can compare your debug output to that from a successful start of UxPlay in the UxPlay Wiki.
Most of such problems are due to a GStreamer plugin that doesn’t work on your system: (by default, GStreamer uses the “autovideosink” algorithm to guess what is the “best” plugin to use on your system).
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.)
diff --git a/README.md b/README.md index 54c208e1..419261a7 100644 --- a/README.md +++ b/README.md @@ -362,7 +362,8 @@ starting at port n, all three in the range 1024-65535, opened for both tcp and ### 3. Problems _after_ the client-server connection has been made: 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. +the failure occurs. You can compare your debug output to +that from a successful start of UxPlay in the [UxPlay Wiki](https://github.com/FDH2/UxPlay/wiki). **Most of such problems are due to a GStreamer plugin that doesn't work on your system**: (by default, GStreamer uses the "autovideosink" algorithm to guess what is the "best" diff --git a/README.txt b/README.txt index 2b4e905c..8b5fbb48 100644 --- a/README.txt +++ b/README.txt @@ -458,7 +458,9 @@ use "uxplay -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. +failure occurs. You can compare your debug output to that from a +successful start of UxPlay in the [UxPlay +Wiki](https://github.com/FDH2/UxPlay/wiki). **Most of such problems are due to a GStreamer plugin that doesn't work on your system**: (by default, GStreamer uses the "autovideosink"