-
Notifications
You must be signed in to change notification settings - Fork 22
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
A question... RPi as a renderer/slave for Field #57
Comments
Well, this seems like a splendid idea --- and one that solves a real problem --- but we have no experience at all with the RPi. There are two ways we can do this: 1. we can get all of Field's graphics system running on the RPi and then send code to the slaves for execution. 2. we can get something much smaller (Python + GStreamer) and send code to that for execution.
|
If there's a use case that entails render-outs from a Field server or I think both stats and video are useful cases here. I had thought I'd seen something on these lines before (but I'm not finding Thx, Al On Mon, Mar 23, 2015 at 10:25 AM, Marc Downie [email protected]
|
Hi All
a quick question
With the availability of a [cheap] 4-core (HD video capable) Raspberry Pi 2
I'm looking back again at Field...
and am wondering if there are any thoughts or plans for incorporating RPi(Debian) into Field
(many parts are already there)
(and I hope to sit-down and do the hard research next month - when I have some time)
what I'm most interested in is
control and/or remote rendering,
multichannel video playback,
communications to and from a RPi2 (master:slave with frame/code-execution sync )
and finally a possible overall port of the system [or a strip down version]
PD (and some times PD-Extended) at the moment is really the only thing going for this purpose (other than direct system programming)
I'm currently having good success with GStreamer 1.0 and python on the RPi
(yay) and it made me long for the programmable timeline surface of Field
Thoughts and discussion welcome
and thanks again
really glad to see it's still being developed
g
The text was updated successfully, but these errors were encountered: