I am re-creating our view only camera kiosks (we have multiple) and wanted to start off using Ubuntu 24.
I successfully install Client v3 but am wondering how to achieve the same effects as in v2.
Can you set the View Window to Full Screen?
Can you set the client to Auto-Start and at Full Screen?
Edit: I tried to install v2 client on ubuntu 24 but there’s a lot of dependencies that cannot be installed and I don’t know how to add the appropriate sources list for them:
The following packages can’t be found with the base sources on Ubuntu 24
When the next version of the client does come out, please consider an administrator setting or mechanism to prevent general users of the client, and in particular kiosk users, from viewing or gaining access to the camera details and especially the RTSP URLs as these URLs contain the user names and passwords for accessing the RTSP streams. This is not information that the general users should have access to. Currently the RTSP URLs can be viewed from several places within the client tool.
Hello, @mrosu! I welcome you to try our bleeding edge release. Under Settings > Application > Window, you can set the app to launch at startup and make it fullscreen. If both options are checked, the app will start in fullscreen mode. You can optionally enable Immersive Mode, which will hide the top bar and the sidebar of the Layouts View. With a mouse, you can hover over these extremities to display them.
@brett.gamlin, when a user tries to view the camera-specific details, the system authentication is required—it can be biometrics, facial recognition, or a password. On systems where this isn’t available, such as Linux and the Web, this authentication is not requested, and the operation is allowed. If you use Linux on your kiosks, please feel free to share your thoughts on the best solution for this case.
We appreciate your feedback on this pre-release and are eager to release the Stable 3.0.0 client version. Thank you!
@bdlukaa, I installed the latest available bleeding edge windows client but still find it lacking in some usability features as described below:
Please add an option to the devices list on the main screen to allow the list of cameras on each device to be collapsed and expanded in a similar way as was available in the version 2 client.
Please consider making the separator bar between the view list and the devices list movable so that it can be dragged up or down by the user to change how much of each list is displayed before scrolling is required.
Please add an option to allow defined external streams to be edited and also allow them to be deleted indivually when more than one are defined. Currently one must delete all external streams if you wish to change just one.
Please consider placing defined external streams into the devices list section and listing them indiviudally under an “external streams” heading instead of lumping them all in together as a single view called “External Stream”.
Please allow individual external streams to be able to be dragged into any defined view.
There is an issue when refreshing server devices under the settings menu. When a server changes the displayed camera name of a device, the device name is not updated in the devices list of the bluecherry client. I found I had to remove the server from the client completely and re-add it before the device list would reflect the change in camera name.
Finally, as for displaying RTSP connection credentials in the client, there are currently at least 4 or 5 different ways in the client to display the RTSP stream information and usernames and passwords used to connect to servers and cameras. This is not a problem for small or home sites where a single user is responsible for setting up the server(s), maintaining the cameras and using the client. However, in a larger environment such as a business it is common for the servers and cameras to have restricted access and be maintained by an IT department, and the clients are often preconfigured for the relevant users with only the access they require. This is particularly relevant in the case of kiosk displays where the RSTP stream details should absolutely be restricted and hidden from users, and this should apply regardless of whether the kiosk or client device is linux, windows or a tablet. Perhaps a password restricted checkbox in the client settings to enable or disable the display of RTSP stream information could be added. Alternately each bluecherry server already has a user configuration page with checkboxes for granting admin access, web access, remote access and archived video to various user accounts. The client application already uses this information to restrict access to event history. Why could it not also check the user’s admin status and only display the RTSP stream information and credentials when the user is listed as an admin of the bluecherry server? Note that the latter may not necessarily work for arbitrary external streams from random devices though.
@brett.gamlin thank you for your feedback, but these are unrelated to the original ticket. Please file a new ticket for us to discuss these features.
@mrosu Now, on the v3 client, you can open it using command line options, such as --layout and --cycle. You can see all the options here. Please try the latest bleeding edge release. Thank you.