kerberos-io/machinery

MultiCam Dashboard/Overview

bazzly1 asked for this feature over 2 years ago — 11 comments

bazzly1 commented over 2 years ago

A screen that shows all your Kerberos cams. So if you have 10 cams, you can view all live video and cam names on one screen. And if possible, if you click on the cam name, it will direct you to that cams dashboard.

| bazzly1 commented over 2 years ago

Not sure how possible this is, but to extend the Dashboard/Overview...When an update is released, have an option to be able to select all the Kerberos Cams that you want to be updated, and update them. A one stop shop to do updates to all machines. Make sense?

| znorris commented over 2 years ago

I'd love to see more robust multi-camera support. The current suggestion of running a set of docker containers (1 web, 1 machine) is a nice work around for the issue but silly.

| wcomartin commented over 2 years ago

I'd love to see multi-cam support in the web-ui as well, even if you had to have multiple machine docker instances.

| estechnical commented about 2 years ago

The model of containers per service is great :) I really like this aspect the most, as it allows us to run a cluster of readily available computers to support any number of cameras. Ideally, another container (or another instance of the web interface) would provide the multi camera viewer and would be the only place end users need to see.

| Toasty27 commented about 2 years ago

I'd like to be able to deploy this for my clients who typically have 50+ cameras, but the current architecture makes that infeasible. Having a separate web interface for each camera is....beyond inconvenient for this scenario. Honestly, I think even having a separate container for each camera is also a bit ridiculous, but I can see some advantages to it as far as scalability is concerned.

In the long run, it might be best to have a master that's in charge of creating containers for cameras when prompted by the web interface. At least for scenarios like warehouse surveillance.

| nicosto commented almost 2 years ago

The only thing that stop me to use Kerberos is this multicamera limitation. One web server by camera with no aggregation is a deal breaker. One container by camera is great for machinery, not for the GUI.

| nicosto commented almost 2 years ago

The only thing that stop me to use Kerberos is this multicamera limitation. One web server by camera with no aggregation is a deal breaker. One container by camera is great for machinery, not for the GUI.

Flole998 commented almost 2 years ago

I also really need this feature, that's why I am staying with my current solution for now, even though it's causing so many issues. It would be awesome to have that client server structure which is used in Macroscop. It makes so many things so easy, so implementing a native win/mac/linux client would be a cool thing to do.

| mikeys4u commented over 1 year ago

Multi-camera: This looks so simple to implement, if I knew what I was doing? Can't what ever you do for one just double the process, and connect another webview type of live image? What is it exactly that cant be done? Really annoying as I have been trying to follow the instructions but cant get two different IP cams to work on same pi. Great GUI but only one camera, I would have seen this as there biggest goal?

cedricve commented over 1 year ago Admin

Thanks all for your comments, I've opened an issue to work on this. Any suggestions are welcome! https://github.com/kerberos-io/web/issues/116

Join the discussion!

Sign-in with GitHub to comment