Do not proceed unless you know what you are doing and your machine is fully backed up. What I did was to find all folders and files with XQuartz in the name:ģ) Now remove the folders/files with xquartz in their name from step 2.ĭISCLAIMER: deleting system files could break your operating system and/or result in data loss if you make a mistake. This is easier said than done, since it places itself throughout your system files. It’s ok – proceed to the next step.Ģ) Next, completely remove any trace of XQuartz from your Mac. You may receive errors from the above steps if your XQuartz installation is broken. Sudo launchctl unload \ /Library/LaunchDaemons/_ist Launchctl unload /Library/LaunchAgents/.plist Issue the following command in a terminal: This is how I fixed it (adapting procedure from which itself did not work):ġ) First, you want to unload the XQuartz service. XQuartz would launch ok, but no window would open. HOMEBREW_SDKROOT: /Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX13.After upgrading XQuartz to 2.8.0_beta3 I found that it completely stopped working with Terminal-issued commands. PKG_CONFIG_PATH: /usr/lib/pkgconfig:/opt/homebrew/Library/Homebrew/os/mac/pkgconfig/13 Git: 2.39.2 => /Applications/Xcode.app/Contents/Developer/usr/bin/gitĬMAKE_PREFIX_PATH: /Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX13.sdk/System/Library/Frameworks/amework/Versions/Current/HeadersĬMAKE_LIBRARY_PATH: /Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX13.sdk/System/Library/Frameworks/amework/Versions/Current/Libraries Homebrew Ruby: 2.6.10 => /System/Library/Frameworks/amework/Versions/2.6/usr/bin/rubyĬPU: octa-core 64-bit arm_blizzard_avalanche The xorgxrdp module is very similar, it just uses the Xorg server to feed XRDP data instead.Īnyway, feel free to start chatting with us on the for any technical questions or assistance. What did was capture the Mac OS screen, then built a module that plugs into XRDP's server network architecture in such a way that it can feed the XRDP server RemoteFX-compatible (JPEG compatible) bitmaps that are then transformed into the Microsoft Remote Desktop network messages that anything that speaks RDP can connect to (FreeRDP and any of Microsoft's clients). With my prototype of H264 on XRDP I can watch 1440p YouTube videos with sound at ~10 MS latency. Most of that is built into OpenH264, FFMPEG, X264, libva (Intel), and Nvidia's libraries like cuda. We don't have to write these encoders/decoders, they are complex and take years of work and Ph.D.-level expertise to build. There are other derivatives such as H265, VP8, and VP9 as well, and I believe AV1 is coming out soon which promises to put all of what I listed to shame. This is also what YouTube, Netflix, OBS, and any other modern video streaming tech uses. ![]() This turns out to be WAY faster than JPEG, so much so it's why we have Nvidia's NVENC encoder and Intel's QuickSync decoder implemented in hardware, but hardware accelerated JPEG? That's nowhere to be found, the best XRDP has in that regard is assembly-written encoders/decoders, which are still fast, but not as blistering as H264. ![]() ![]() It sends a "key" (full) frame, and then for a long while after the fact it sends compressed diffs (and then occasionally another key frame to make sure things are in sync). The insight for H264 is it's a diff-ing protocol. The reason H264 is superior to JPEG is that while JPEG compression is super efficient, with every frame you are still sending a full frame. RemoteFX is full-frame JPEG compression (JPEG 2000 I believe), and it was a precursor to Microsoft's H264 acceleration. Protocol is a funny word with respect to this situation.
0 Comments
Leave a Reply. |