z90210 wrote: ↑Thu Jan 02, 2020 7:56 am
Is it possible to mirror the content 90 degrees?
I just merged a PR from user Steven Hickson that enables rotating the image. You now just pass the desired degree (a multiple of 90 deg) as argument to the new -r flag, e.g. ./rpiplay -r 90
liminal wrote:
So I've installed this on a Pi Zero and exactly as per the instructions and its worked great, installed fine.
Ive now tried the exact same thing on a Pi 3 running OSMC and i'm getting this an error.
Yeah, I only support using RPiPlay on Raspbian. Running it on OSMC might well be possible, but you're on your own getting it to work. You should be able to install Kodi on top of Raspbian and have it work with RPiPlay in this way.
eppi wrote:
Hi everybody,
I tried to compile the AirPlay Server on a freshly installed and updated Raspbian on a RPi2B and I received the following error:
Code: Select all
pi@raspberrypi:~/RPiPlay/build $ cmake ..
...
CMake Error at /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the
system variable OPENSSL_ROOT_DIR (missing: OPENSSL_CRYPTO_LIBRARY
OPENSSL_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.13/Modules/FindOpenSSL.cmake:412 (find_package_handle_standard_args)
lib/CMakeLists.txt:20 (find_package)
-- Configuring incomplete, errors occurred!
See also "/home/pi/RPiPlay/build/CMakeFiles/CMakeOutput.log".
What is wrong?
Just read what the error message says and you'll recognise that OpenSSL could not be found, which is a dependency of RPiPlay. You can install it with sudo apt-get install libssl-dev. You could have avoided seeing the error by closely following the instructions from the Readme.
DaithiMcBuan wrote:
I have this up and running on some Pis at the office where I work, and it works alright. Screesharing via Airplay works, though casting from a program such as QuickTime tries, times out and fails (though funnily enough, the videos on the BBC app on iOS work just fine, while the YouTube app etc. does not).
The second problem I have encountered is that while this solution works, after a number of hours (overnight), it stops working. So while the device is detected by a Mac or iOS device the next day, sharing fails and I need to restart the Pis. Needless to say, my boss is not impressed.
Just some feedback.
1) As discussed on GitHub (I suggest browsing the open issues if an open source program doesn't work in some way), video-only is not supported, since it uses a different protocol that's not implemented. See
https://github.com/FD-/RPiPlay/issues/7.
2) Well, this was not written with the intention of impressing your boss. It's an open source project developed by users contributing code voluntarily. There is a whole array of known issues (though I'd invite you to file a detailed report for this one, since it hasn't been recorded yet), but no-one found them worth their time to fix. You're very welcome to fix any bugs you come across, if you feel like having them fixed justifies the effort for investigating the problem.
vital wrote: ↑Thu Feb 13, 2020 4:56 pm
i have some problems. I execute instructions without errors. Start app and try to play music. And see decoding errors for .acc file
after tryinfg ctrl+c program stay in STOPPING for long time... i try to ctrl+z but id it proper way? if i start program afterwards i cant connect need to reboot pi.
1) That usually means you try to connect to RPiPlay as an audio receiver, which requires a different protocol that's not implemented. RPiPlay is an AirPlay _Mirroring_ receiver. See
https://github.com/FD-/RPiPlay/issues/2.
2) This is a known issue, but its cause remains a mystery.
