Parsec daemon not running6/8/2023 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. After updating yum database, We can install parsecusing dnfby running the following command: sudo dnf -y install parsec Install parsec on Fedora 34 Using yum Update yum database with yumusing the following command. ![]() 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. Please check the Contributing to know more about the contribution process.I've spoken with Parsec support. This project uses the following third party libraries: Contributions to this project are accepted under the same license. The software is provided under Apache-2.0. parsec This is the public interface of the Parsec Go client.This provides the underlying interface to parsec, but is not intended for client application use. interface The Google Protocol Buffers basic client for communicating with the parsec daemon.e2etest End to End testing - Docker containers to fire up parsec and run end to end tests. ![]() github/workflows Github Build CI action definitions - CI testing, build, unit test, static analysis. This folder General files that must be at the top level - readmes, licence, lint configurations, etc.Internal tests for packages will be in the relevant package folders as required by go, and will be called xxx_internal_test.go Folder Structure On ubuntu 20.04, the following will install the tools you need:Īll code for the end to end tests is in the e2etest folder.īlack box unit tests for folders are found in a test folder under the main package folder (e.g. You will also need the go plugin for protoc ![]() You will need protoc 3+ installed as well as gcc. The protocol buffers files are used to generate translation golang code which is checked into this repository to remove the requirement for developers using this library to install protoc. This submodule is currently pinned to parsec-operations v0.6.0 proto files, included in the parsec operations, which is included as a git submodule in the interface/parsec-operations folder in this repository. The parsec interface is defined in google protocol buffers. If the PARSEC_SERVICE_ENDPOINT environment variable is not set, then the default value of unix:/run/parsec/parsec.sock is used. This URL must be for the unix scheme (no other schemes are supported at this time). This client will, connect to the parsec service on a URL defined using the PARSEC_SERVICE_ENDPOINT environment variable. Sample usage can be found in the end to end tests in the e2etest folder Parsec Service Socket Configuration There are ommissions and testing is very minimal at this stage. The current status of this interface is suitable only for review of the API. The library contains methods to communicate using the wire protocol. The HOST functionality works fine (if the host is running the latest AMD 23.2.1 drivers, or older AMD Radeon drivers) if youre connecting to the device from a system running drivers prior to 23.2.1, but clients cannot connect. This repository contains a PARSEC Go Client library. Just a FYI that Parsec is broken, from the client side, after installing the latest 23.2.1 AMD Radeon drivers.
0 Comments
Leave a Reply. |