-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plexamp Support #15
Comments
Hm, unsure. Running node.js software is probably beyond both the RAM and CPU of the S3 SoC. Additional problems:
|
Makes sense. How would one go about loading the binary to the ottercast? Once I get all the parts to build my own ottercast, I can write a simple document on how to install it. I've got a plex pass, so I can test. |
You could probably try to just "scp" the Plexamp-Linux-headless-v4.6.1.tar.bz2 file (more specifically it's contents) to the root FS of the Ottercast and try to run it. |
Sweet, once I have time to order and build the Ottercast, I'll try it. Thanks for the help. I'll keep you posted. |
Recently saw that Plexamp can be installed as a node.js server on a Raspberry Pi. Wondering if it would be possible on an Ottercast, this would be incredibly helpful, and would likely bring in a bunch of Plex fans, given the possibility of multi-room support in Plexamp.
Thoughts?
https://github.com/odinb/bash-plexamp-installer
The text was updated successfully, but these errors were encountered: