-
Notifications
You must be signed in to change notification settings - Fork 11
Chiaki for the Raspberry Pi
This is a Fork for getting the excellent PS4 and PS5 remote play program Chiaki to work on your Raspberry Pi 4. Iv'e been working and testing on Raspberry Pi4 with Raspbian Buster and Bullseye Desktop 32bit OS installed. It should work with some older RPi's too I believe. In fact someone is using it on a RPi Zero, although it skirting the limits on that one.
these instructions are designed to work on a fresh Raspbian, but of course you don't need a fresh os card.
NEW!
If you have a recent Raspi OS install which might be the one called 'Bullseye' there's additional steps you'll need to follow. So if you do the following in a terminal,
uname -r
and get a version number like this **5.10.63-v7l+ ** or higher then you're likely on Bullseye. If that's the case please look out for and follow those extra steps!
1. Update your System I really recommend using an Ethernet connection for this as there's going to be quite a bit of downloading if your OS install is fresh. It'll also be easier to verify that Chiaki is working ok if you're testing over Ethernet first.
sudo apt update
sudo apt upgrade
If you think it looks like it's stuck its probably just taking its time. You can start a new bash shell, run 'top' and look for an active 'dpkg' or 'dpkg-deb' process.
2. Install cmake (might be installed already with your system update, or it might fail then try rebooting)
sudo apt install cmake
3. install protobuf
sudo apt install python3-protobuf protobuf-compiler
4. install avcodec
sudo apt install libavcodec-dev
5. install opus
sudo apt install libopus-dev
6. install SDL2
sudo apt install libsdl2-dev
7. install OpenSSL
sudo apt install libssl-dev
8. install Qt5
sudo apt install qt5-default (not for Bullseye users)
sudo apt install qtmultimedia5-dev
sudo apt install libqt5svg5-dev
sudo apt install libqt5multimedia5-plugins
For BULLSEYE users only, you'll need to install the legacy graphics/display libraries,
git clone https://github.com/raspberrypi/userland
cd userland
./buildme
then in a text editor, as super user, make this change to revert to the legacy display stack,
sudo geany /boot/config.txt
and change
dtoverlay=vc4-kms-v3d
to
dtoverlay=vc4-fkms-v3d
You'll now need to reboot. Then continue.
I actually now have a new Raspberry Pi version of Chiaki that will not need these fixes.
https://github.com/Fredrum/chiaki/wiki/rpi02---branch-for-Bullseye,-64bit,-h265-and-kmsdrm
you might want to 'cd' first to some folder where you keep software installs?
9. clone this fork - from the 'rpi release' branch
git clone --recursive --single-branch --branch rpi01 https://github.com/Fredrum/chiaki.git chiaki
cd chiaki
10. Build!
mkdir build
cd build
cmake ..
make
Run the executable
gui/chiaki
Do the setup steps needed for the Raspberry to find and communicate with your PS4/PS5.
Phew, I think it should work now!?
If you want to run Chiaki without Desktop (X11), for example under Retropie see these instructions
F11 is for toggling fullscreen, or you can
Double Tap DS4's touch pad to toggle full screen
The game stream window will display black if its not active , or 'in focus'. This is due to me having trouble getting the layer ordering to work with the RPis hardware decode+display pipeline.
If your PS4 screen is really off from the underlying window please check that you are not running with the black overscan border around your desktop/screen.
If you lose the executable it's found here: chiaki/build/gui/chiaki. Iv'e now tested this over WiFi too and it works really well and Iv'e had reports of people saying that 1080p on PS4-Pro works fine too!
In the Audio device popup menu, "default" should equal both Alsa and PulseAudio. I'd recommend to try that first.
Iv'e tested playing with DS4 and XBox One controllers and they both work great! Just make sure that you're not so close to your PS4 console that your controller's bluetooth signals reaches it. As you'll then be sending the PS4 conflicting signals and you'll get some bad input behaviour.
See here for a bit more info on controllers!
If you're having problems and are sure that you have not missed any of the numerous steps, feel free to post in the 'issues' section.
There's a config file with your ID and connection details (so don't share it with anyone) saved as ~/.config/Chiaki/Chiaki.conf. This file can be saved and just copied back to the same location to avoid having to re-do the ID setup.
Cheers!