Optional two-way live audio is now possible with WebRTC!
This new feature in UV4L allows your Raspberry Pi to optionally receive an audio stream from a browser or from any WebRTC-compliant peer (e.g. with microphone) and automatically play it through the speakers connected to audio out of the Rpi. This is possible while (optionally) transmitting audio and/or video to the browser, as before!
It's ideal for a cheap and simple softphone solution. It can probably be enhanced to live stream music to your Raspberry Pi!
Upgrade, attach your speakers and have fun!
A new release of UV4L for Raspberry Pi is out! It includes a number of improvements and fixes, especially about the connection to Jitsi Meet Web services
Thanks to a new, special module for UV4L, it is now possible to join a room of any Jitsi Meet Web Conference anywhere (including those on the free, public meet.jit.si service) and broadcast live video and audio from your camera and microphone to all the participants or viewers in the room without the need of any browser or other GUI installed!
The first release of this module supports the Raspberry Pi 2 (e.g. with camera module or usb cam + microphone). Packages for other architectures will be provided in the future.
To know how to install the necessary modules for Raspbian, please follow these instructions.
An example is here
Have you ever wanted to live stream your Rpi Desktop to the browser? Here is how to do it.
It's clear that embedded computers like the Raspberry Pi 1 or the Raspberry Pi 2 do not have the necessary power to perform all the funny media processing stuff such as motion detection, speech recognition, recording, mixing, broadcasting, etc... that we would expect from a modern PC or workstation. Yes, UV4L already natively implements things like on-the-fly Text Overlay and Face Detection at full fps and resolution, but what if we also wanted to do a little bit more magic than that, like processing an additional audio stream and recording the resulting output at the same time, for example? The answer is that the RPi should not be doing any processing at all, really. What we need is a way to simple define the media processing pipeline we prefer and delegate all the job to an external media server such as Kurento. So interfacing with Kurento or even with the Nubomedia cloud built on the top of it will be the objective of the next (major) releases of UV4L.
"Kurento is a WebRTC media server and a set of client APIs making simple the development of advanced video applications for WWW and smartphone platforms. Kurento features include group communications, transcoding, recording, mixing, broadcasting and routing of audiovisual flows.
Kurento also provides advanced media processing capabilities involving computer vision, video indexing, augmented reality and speech analysis. Kurento modular architecture makes simple the integration of third party media processing algorithms (i.e. speech recognition, sentiment analysis, face recognition, etc.), which can be transparently used by application developers as the rest of Kurento built-in features."