

- #Xeoma grey in recording bar archive#
- #Xeoma grey in recording bar software#
- #Xeoma grey in recording bar free#
Xeoma is a practical piece of software designed as a video surveillance tool that includes various video monitoring options, remote control functions and motion detection features.

This would fix problems in start syncing of fat streams from HD.ĮDIT: most of the time I get "Sorry but the board is temporarily unavailable, please try again in a few minutes.".Xeoma: A video surveillance tool that’s user-friendly, customizable and offers remote control functions Maybe its better to grab/perform the stream the whole time by the server and only bypass the pure writing process if not in continous mode. I think there is a problem during record start of such a stream. It would be great the developers found a solution for this, so a complete background mode without running GUI/client and background recording by the server with the configuration the user build in the - now closed - GUI/client! And please keep an eye and some tests on recording of HD streams. And most of the times on a detected motion the recording does not restart, I think for the same reasons. Non-continous recording with motion detection simply does not work for me because the stream is scrambled on each recording start, possibly the same reason here is the resolution of the camera. This possibly belongs to the resolution of my HD camera (1920x1080) but with less resolution it makes no sense for me to monitor my car or my garden because you can only see, that something happened but not WHO it was. It always produces many scrambled seconds of video stream. Fact is: also in continous recording the motions are only tagged in the stream (and can only be searched if tagged) if the GUI/client is running and opened on the screen! If the GUI/client is closed or even if it is minimized to the task list, motion detection does not work!Īlso the client (and the server) has very big problems to re-catch the camera image after beeing recalled from minimized in the task list. If this is so, my suggestion to the developers: create a complete background mode where you can stop/close the GUI and only the recording server is running, storing data and storing motion tags according to the user defined areas and so on. Possibly that's my failure, I stopped the GUI and so no motion marks are stored.

With continous recording yon can stop the GUI and save some machine power for other work.īut I think I understand the software a bit more now: I'll test wether the GUI has to run even if you are in continous rec mode to put motion marks into the database. Otherwise nothing is detected and recorded. The problem with non-continous recording is, that the GUI frontend has to run all the time on any PC/workstation.
#Xeoma grey in recording bar archive#
Xeoma is working perfect, but I need the feature to detect motion in the archive if I sometimes have to control my archive stream.ĭirk higginsd Posts: 3 Joined: Thu 1:12 pmĪs I understood the documentation you can start a permanent recording by tagging "Continous work." in the motion detection modul and then search for motion in the archived video. What can be the problem? Shall I use a smaller object size in the filter parameters again? Shall I scan the whole picture and not only a subarea (the door)? Now in commercial version no motion - or only the first motion after reconfiguring the detection filter - is detected in the archive stream!
#Xeoma grey in recording bar free#
While using the free version this works perfect, every detected motion was marked in the timeline by a green area. My problem is: I go to the archive of the recorded stream and choose "search detected motion", after that I'm asked to mark an area where to search on the video screen. I want to mark every detected motion in the stream 1 second before and 10 seconds after detection and pushed the corresponding sliders to that positions. I defined a motion detection for the camera: marked a part of the picture (a door) with the brush in red and choose an object size a little bit bigger than the default size (because the default seems to be only a few pixels). I've installed the Xeoma server on a Centos-6-system and record permanently (by using the marker in the motion detection filter) the H264 stream from one IP camera.
