PS4 Remote Play for Mac, free and safe download. PS4 Remote Play latest version: Play PS4 Anytime, Anywhere! So, you wanted to play your PlayStation. Open Remote Play v1.2 BETA (MAc OS X) Filename ORP1.2BETAOSX.zip Date Posted. Tools and Utilities, PS3: Tags PS3: Downloads 2827 Description: Download File.

Remote Play (download) for the PlayStation 3 (PS3) enables you to display the system screen on your computer and remotely operate the PS3 system via a network connection. Sony today announced plans to bring the PlayStation 4's Remote Play capabilities to the PC and Mac through an update that will be released.

It has been suggested that this article or section be merged with PS3_Remote. (Discuss)

An angled view of the Sony PS3 Bluetooth remote control.

Sony uses Bluetooth for wireless controllers including the BD Remote (Blue-ray Disc remote control). This makes for a decent remote option.

Here are the advantages:

Inexpensive (< $25 USD)
Reasonable layout (51 buttons with separate arrows/seeking controls)
Radio Frequency operation (better range - 30 feet/10 metres or better, non-line-of-sight)
Bluetooth pairing - multiple remotes don't interfere, no picking channels to use
Good feel to the control

Note: Some remotes (such as that pictured, have a 'back' label on the 'cross'/X key, others have it on the 'circle'/O. And there are newer PS3 remote controls which are significantly different - they are slightly longer, they can control multiple devices (PS3/AMP/TV) and they have a row of lights to show which device is being controlled.

2Linux installation process
3Other Linux resources (may be out of date)
- 3.2The Sony PS3 Remote Package
- 3.3bdremoted method
4Mac OS X

There are two different Sony PS3 remote controls around, and they appear to require different processes to get them working.The older ones look like the picture above and take two AA batteries.The newer ones look like this one on Amazon.com: http://www.amazon.com/Media-Blu-ray-Remote-Control-Playstation-3/dp/B0050SX9I2/ - they are slightly longer, take two AAA batteries, and have a row of lights to show which device is being controlled (PS3/AMP/TV).

The PS3 Bluetooth remote control can be put into a 'pairable' state by pressing the START and ENTER buttons on it simultaneously for about five seconds; on the newer PS3 remote control the 'PS3' light will start flashing at this point. The newer PS3 remote controls appear to lose their pairing data if you change/remove their batteries, so it's necessary to re-run part of the pairing process after a battery change.

In case anyone is interested, the power consumption of the newer Sony PS3 remote controls is about 14 mA when there is a bluetooth connection in place, and 0.05 mA when in standby; the power consumption of the older Sony PS3 remote controls is about 14 mA when connected and 0.12 mA when in standby.

The software described below will disconnect after a configurable inactivity timeout expires (say 10 minutes) in order to preserve the remote control battery life. After the connection has been dropped, the first time a user presses a button on the remote control the connection needs to be re-established, which takes a second or so. After that the button presses act practically instantaneously.

Note: these instructions were written in July 2015 and tested on Mythbuntu 12.04 and Mythbuntu 14.04

1. Ensure that your bluetooth receiver (dongle or built in) is listed when you run lsusb. It should display something similar to this:

2. Install the bluetooth software as a service together with various other pre-requisites:

3. The bluetooth stack needs to patched to enable some additional functionality, namely:

disconnect the bluetooth connection after a configurable timeout period. (This is to preserve the battery life in the remote controllers and avoid the batteries going flat after just a few days.)
configurable mapping from PS3 remote control buttons to key presses (without requiring LIRC).

These patches were originally developed by Kitlaan (Ted M Lin) and Ruff and subsequently updated/repackaged by readers of this forum: http://forum.kodi.tv/showthread.php?tid=50717

Carry out the following commands:

4. Check that the bluetooth service is running - if you type:

it should display something similar to this:

5. It's not essential, but when carrying out the following steps it can be useful to run the bluetooth daemon in foreground, as this gives a few more clues as to what is happening. Start another ssh session and type the following:

6. Download a utility for helping perform the pairing:

7. Pair the remote control with the system - type the following:

Hold the START and ENTER buttons on the PS3 remote control for about five seconds. The result should be similar to the following:

Type the number corresponding to the PS3 remote control or hit return to take the default. The result should be similar to the following:

(Among other things, this causes data about the paired device to be stored in a directory off /var/lib/bluetooth.)

The timing can be quite sensitive - so it may be necessary to re-run this operation or else try holding the START and ENTER buttons on the PS3 remote control before running sudo python ps3_pair.py.

8. Run the following command:

This should show something similar to the following:

In this example:
00:15:83:15:A3:10 is the MAC address of the bluetooth receiver
34:C7:31:04:25:1A is the MAC address of the PS3 remote control

It should show Trusted = 1 -- if it does not then re-run the sudo python ps3_pair.py command.

If the output from running /usr/share/doc/bluez/examples/list-devices shows Connected = 1 then it is not necessary to run the next bluez-test-input connect step.

9. This step usually needs to be run to connect the newer PS3 remote controls, and sometimes needs to be run on the older PS3 remote controls.

Hold the START and ENTER buttons on the PS3 remote control for about five seconds, then type the following:

where '<device MAC address>' is the device MAC address shown when running the ps3_pair.py command - for example:

Remote Play Ps3 Download Mac Pro

If the command completes without displaying any messages then it has completed successfully.

If when running the command you get the message org.bluez.Error.DoesNotExist: Does Not Exist then it means that the device MAC address is not correct.

10. At this point the system should be receiving key presses from the remote control. If you are running bluetoothd in foreground you should see messages like the following when you press buttons on it:

The system should be responding to the button presses, and if you run /usr/share/doc/bluez/examples/list-devices it should show 'Connected = 1'.

This forum post may be useful https://forum.mythtv.org/viewtopic.php?f=2&t=3230 if problems are found after upgrading the kernel.

11. If at a later point you change/remove the batteries from the newer PS3 remote controls then it will be necessary to re-run the sudo bluez-test-input connect 34:C7:31:04:25:1A step.

12. Run the following commands:

This will update the comment about the IdleTimeout parameter (which is specified in seconds) and it will set up the XBMC/Kodi key map.

13. Edit /etc/bluetooth/input.conf and introduce a line in the [General] stanza similar to the following:

This species the idle timeout (in seconds) before the connection will be disconnected. ('IdleTimeout=600' means 600 seconds, i.e. 10 minutes.) (The IdleTimeout setting is commented out by default.)

14. Edit /etc/bluetooth/input.conf and copy into the [PS3 Remote Map] stanza the contents from below (in place of the XBMC/Kodi key map) and tailor it as you like. The newer PS3 remote controls have two extra buttons (INSTANT back and INSTANT forward) whose codes are not listed in the default input.conf - their values are 0x76 and 0x75 respectively.

15. Restart the bluetooth service in order to make the updates to /etc/bluetooth/input.conf take effect. (Run sudo service bluetooth restart or if running bluetoothd in foreground type Ctrl-C and then sudo bluetoothd -n -d.)