Hi, happy to see that it is working!
I’ll take note of that deceiving “No source available” message, thanks for the feedback 
So, for the Cockpit, that message is expected. Try to follow those instructions, they are made so we guarantee that the video will be sent through your tether/cabled connection and not via WiFi/radio, meaning that for your setup, you’d have to select only the 192.168.2.2.
About adding more redirect videos, this can be done, but for now, not in the BlueOS interface (you’ll be able to on the next BlueOS beta), so you need to use the development/test interface for the video service. You can access it at http://blueos.local/mavlink-camera-manager. On this interface, each column represents a possible video source, and the column on most right shows the configured streams.
To add a new redirect source, find the “Camera: Redirect source” one, which should be on the right. Choose a unique name, and add the RTSP endpoint there, and click “Configure stream”, ending up with something like this:
And in BlueOS video page:
Regarding CPU usage, I’ve used 2 redirected IP cameras in the past and it was working fine.
In Cockpit, I’d suggest you only try to record one of the video streams, there is an issue regarding recording multiple video streams (which should be possible using two “Video recorder” MiniWidgets). We’ll be working on this to make it possible in the next two weeks.
Note that each recording will act as a new streaming, consuming an additional bandwidth usage. This is something that is also on top of our priority list, and soon it will not result in more bandwidth use
Of course, you can use the VLC or other software to record each of your streams directly from the RTSP endpoint, but this will have the same additional bandwidth usage implication as today’s Cockpit.
I hope it helps, feel free to ask further questions!
