![]() ![]() Linux/macOS: vcpkg install libvpx libyuv opus aomīuild How to build on Linux Ubuntu 18 (Debian 10).Windows: vcpkg install libvpx:圆4-windows-static libyuv:圆4-windows-static opus:圆4-windows-static aom:圆4-windows-static.Install vcpkg, and set VCPKG_ROOT env variable correctly Prepare your Rust development env and C++ build env Please download Sciter dynamic library yourself. Dependenciesĭesktop versions use Sciter or Flutter for GUI, this tutorial is for Sciter only. Go through DEVCONTAINER.md for more info. Clicking will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use. If you already have VS Code and Docker installed, you can click the badge above to get started. If you are not close to one of these, your network may be slow. See CONTRIBUTING.md for help getting started.īelow are the servers you are using for free, they may change over time. RustDesk welcomes contribution from everyone. You can use our rendezvous/relay server, set up your own, or write your own rendezvous/relay server. You have full control of your data, with no concerns about security. Works out of the box, no configuration required. Yet another remote desktop software, written in Rust. We need your help to translate this README, RustDesk UI and RustDesk Doc to your native language FFmpeg is more CPU-intensive and much more laggy than AMD decode on 22.11.2, so ffmpeg is not ideal on a laptop utilizing an iGPU. I've rolled back to 22.11.2 on my AMD laptop (Ryzen 7 4700U w/Vega iGPU) as I use the Parsec client frequently from that laptop. The other workaround is to roll back to AMD Radeon driver 22.11.2, as that driver has zero problems from the Parsec client side. The workaround using ffmpeg (as the decode method within the Parsec client, requires some files to be installed) continues to be the only choice while this issue is being sorted out with the newest drivers, 23.x.x. The AMD overlay now pops up when connecting to a host in fullscreen mode, but no frames are returned/decoded. The driver seems to be getting further than it did before. What you'll see is the image below instead of an error being thrown. ![]() The error -14 is gone but what happens is a complete frame is never returned when attempting to connect to a Parsec host. Parsec Client decoding is still broken under 23.3.1 when AMD is chosen as the decoder method, whether h.264 or HEVC h.265 is used. As of this post, the AMD Link client app is broken in Windows 11. Today I launched the app and it says an update is available, but I can't for the life of me figure out how to get the app to update as it will not update within the Microsoft app store. As of yesterday AMD Link refused to connect to any of my AMD systems running the latest 23.2.1 driver. The AMD Link app for Windows is also broken. OBS Studio is also impacted and does not run properly under 23.2.1. I rely on Parsec for streaming, remote desktop access, and remote gaming, so it's a big inconvenience in my case having decode broken in AMD's latest drivers. Steam Remote Play, which utilizes some form of hardware GPU decoding, is also working fine. From the testing I've done with the new 23.2.1 drivers, games and other 3D graphics apps involving the GPU seem to run fine. I'm not sure how many other applications will be affected by decode being broken in 23.2.1. Adrenalin 23.2.1 included a number of rolled-up changes that were implemented for the 7000 series AMD Radeon GPU's, including a broken decode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |