-
Notifications
You must be signed in to change notification settings - Fork 3
Making It Usable
The idea of making the raspberry-pi jacktrip client/server usable by "ordinary" users, especially non-technical musicians, depends on clearing a few hurdles, some are logistical, (it must be easy to acquire a complete hardware solution at a reasonable price) some are technical. (Folks need to be able to simply plug the hardware in and get a working audio bridge without a lot of effort.) This page sketches some of the ideas in play for addressing these roadblocks.
Carlos has been talking with a US supplier, pishop.us, about bundling a hardware package together that could be ordered as a unit, and simply assembled be the end user. They are even willing to burn a custom image onto an SD card and shipt that along with the parts, which gets us pretty close to a turnkey solution!
I recently came across a similar bundle being sold out of Europe for the ELK Audio project, very intrigued by their software as well: https://www.hifiberry.com/shop/bundles/hifiberry-elk-audio-bundle/
Once we have a stable/optimal configuration, a novice-level step-by-step guide would be useful, as we already have folks who are buying hardware and do not yet have a working client because there are just too many things to learn in order to get rolling with jacktrip.
Inbound connections would need to be opened up on the user's home router, which we may simply need to document. It may be worth seeing if some of the VOIP methodology applies here. (STUN/TURN/ICE?)
One way to lower the barriers to entry is to have the units connect to a central server at boot time. This could serve a number of different purposes, and is a rich enough topic to warrant its own page.
Two ideas here: First, each unit could include a web UI for local user interaction. It's also conceivable that a simple http(s) responder could be used to provide controls and/or status or notifications, and perhaps provide access to controls to the trusted server.
Second, the client could pull web content from peer units it connects to, either for control or for social purposes, e.g., photos/avatars/bios for each user.