Mattb

Thanks Carl, That’s exactly what I wanted to hear. Pelco makes some nice product, but it is time to explore some less expensive PTZ cameras.

Great information survtech, I see there are some physical differences in the standards, like input and output voltage, termination etc. Have you ever put an RS-485 PTZ camera on a RS-422 controller?

Has anyone used PTZ cameras listed as RS-485 on an RS-422 controller? I want to add additional PTZ cameras to a Pelco 97xx system that is native RS-422, Pelco-P protocol @ 4800 baud. I don’t want to use a protocol converter – I am looking for manufacturers cameras other than Pelco to add to the system. I am looking specifically at the GE/UTC TruVision Mini PTZ, which has a "RS-485 communication DIP switch" supporting a "Digiplex RS-422 mode." There is also a “Pelco-P” mode. The manual clearly states “RS-485 is the interface that connects the dome camera to the control device. Consequently the RS-485 setup of the dome camera and the control device must be identical.” A call to the manufacturer’s support group gave a positive answer, but I have some concerns after reviewing the manual. My Vendor can not say for sure either. Internet searches of RS-485 and RS-422 compatibility haven’t specifically addressed camera compatibility, but have provided enough information that I am not eager to experiment. So, can anyone share experiences using PTZ cameras listed as RS-485 on Pelco RS-422 systems without a converter? Pelco systems would be the 6700, 6800, 97xx matrix systems,or even a KBD300A. Thanks.

Does anyone know the back-up battery type for a Katalel DVMRe CT? One of the DVMRes I service has reached a point where the back-up battery doesn’t retain the clock after a power outage. It seems to retain all the recording configurations & names, but the time resets. I hope there is just a battery problem. I seem to recall they have a 2032, but it has been a long time since I have opened one. Kalatel’s DVMRe line was a reliable product. I hate to make a second trip. Thanks

Ver 8.3.0 - One of several Geovision 1480 has suddenly started retrieving only the video marked as ‘do not recycle’ when accessed locally with the F10 Viewlog key. The ‘always record’ video from several cameras continues to record, but isn’t accessible using the local Viewlog. The complete database will show if the ‘connect to multi-hosts’ option is selected, and then the recorder and associated cameras selected. The database appears correctly when retrieved from a remote machine, just not locally when the F10 key is pressed. The system had worked great for 4+ years and several upgrades. I have tried rebuilding the database a few times, relocated the database, deleted the database & complete rebuild and every option I could find unsuccessfully. Any suggestions?

The problem is actually files not indexed in the database, but actually on the hard drive. The integrity of the video files is excellent. Line power quality is not an issue in this environment. Video files don’t show up in the Viewlog, but are on the disk – If the Viewlog is in a 16-panel mode, the “missing” video is in a blue panel or several blue panels. After the database repair utility is run, the “missing” video becomes available. The “missing” video files become “orphaned”, and do not recycle – the initial post describes the problem in detail. The computers are re-booted and chkdsk’ed every 3-4 weeks. All video is recorded 24x7 in 5-minute segments using the motion detection for ‘economic round-the-clock’ recording. Naturally, all the DVRs are have only Windows, GeoVision, and the DVD writing software – Nero or Roxio The dedicated video storage disks are configured as one storage group, with a path pointing to a uniquely named storage folder on each dedicated video storage disk. Storage Group 1 will contain Drive-D/path-1, then Drive-E/path-2 etc for up to five drives. I have considered creating a storage group for each drive, but I don’t think that is the intention of GeoVision. My understanding is that a storage group would be all local drives, a second NAS, a third storage group a removable USB drive etc. When I performed an upgrade when the software automatically put all the drives in one storage group. ----Version 8.2.0.0 - Released date: 02/22/2008 features ----Up to 8 storage groups with different storage locations can be created. Any suggestion would be appreciated – Still no response from the USA GeoVision distributor Usavisionsys, although they have been really helpful in the past, even to the point of providing patches ahead of releases.

Nate, Pity the drives were formatted. Did you save any of the corrupt video files? Big test: was stored video that was viewable previously now corrupt? Is there a video backup on a CD/DVD that was corrupt on the server? That would conclusively imply a hardware issue. If there isn’t a baseline backup for comparison, I would be inclined to believe somehow the video files were not being properly encoded, or not being decoded correctly. How frequently are evidence CDs created, and does the client keep an archive of backups? Was there a successful backup from the corrupt video era? Naturally, you could try copying some other files to the drive to see if Word documents (or something else) become corrupt over time. If you are using Vista, have the automatic Disk Defragmenter disabled. Geovision has indicated it isn’t useful. Did you try exporting some sample corrupt video files only for playback on a different machine with the GeoVision codecs already installed? Were the corrupted files the size you would expect for a normal file? Somewhere in a GeoVision forum the advice was given to move the card to a different slot, but I haven’t ever had the need. I always enlarge the unused space to 2.5 or 3 gigabytes on the storage drives. You could toggle whatever state the PCI-IDE bus-mastering BIOS state is in. I never overclock or push any components. If you deploy a new machine, swapping the video storage hard drives, I would suggest manually configuring the GeoVision software and not using the FBR. I only use FBR on identical hardware platforms, and a FBR that originated from a no-problem install. I never make dynamic drives in Windows, and don’t RAID. I tried hardware SCSI raid early in the game, back in 2006, and didn’t see any performance change. One other thing, I have stopped using the Seagate Barracuda 7200.11 series drives and have been replacing failed drives with WD RE3 WD1002FBYS. I haven’t had a WD drive fail, but have lost some Seagate Barracudas. Probably a personal choice though. As for the imaging, Norton Ghost 2K3 will let you create a self-booting DVD that will bare-metal install in an hour or less. Acronis is faster, but my organization’s IT department is married to Symantec. I keep a Windows only DVD (after users are created, services disabled, etc) and Windows with Geovision DVD. The FBR is saved in a separate archive, and updated as needed, with parent and grand-parent FBRs available. I wish I could offer more insight. As mentioned, I have had issues the GeoVision was able to resolve, some times here in the US and sometimes in Taiwan. There is typically a bit of communication problems, and they often have difficulty addressing more than one issue in a single trouble ticket. I would send succinct descriptions and images to GeoVision if possible. They usually want to connect to your server and view the configuration. Good luck, & Keep us posted if you find the cause.

It sounds unusual, particularly that the older files seem to have been affected. Was there a Geovision update around the time corrupt files appear? I had issues with the Geo-H.264_V2 - playback on workstations that were members of a domain failed – produced a blue panel. I don’t have any suggestion other than try changing the codec, and checking to see if any unusual codec-pack or DVD playback software has been installed A clean install of both Windows and GeoVision MAY solve the problem, although time-consuming. Swapping the server out with a working demo machine may be the easiest way to maintain customer relations and determine the cause of the problem at your leisure. If there is evidence on the storage drives, move them to the other machine and rebuild the database again. Unless the configuration is really complex, I wouldn’t use the FBR for a swap-out or O/S re-install. Other thoughts: I’m sure you can view the real-time images and they appear OK. Are the corrupt video files a comparable size to a valid file? If they are, have you tried taking just the .AVI files to another GeoVision DVR for playback? What do the corrupt files look like when played back? I have found digital recorders are more sensitive to poor video quality. I use a meter check luminance color-burst and proper termination. There isn’t a T-tap to split signal off to a monitor? Another guess would be conflicting codecs installed if the computer has internet access and a used was downloading movies of some type. There may be a codec pack in the Control Panel add-remove programs if a user brought something from home too. I had problems when a DVD I keep a functional operating system image for each server model for a fast restore. A public domain program, G4U, is available if Norton or Acronis isn’t an option. Keeping an O/S disk image DVD in each client’s computer to restore the system to sales-day condition is a thought. Let us know if you discover anything. GeoVision sometimes is slow responding to problems, but will help once you get a contact name.

Are the video files actually corrupted, or is the database not properly indexing the files? I have a problem where the video files are on the dedicated storage disks, but not all are indexed. Is the video file actually retrieved when a backup is performed? Does the video file play back with the Windows Media Player? The folder and file name will identify the camera and time on the storage hard drive. You can manually navigate to the video clip with the Windows Explorer and give it a try. The issue I am experiencing impacts older recordings, usually a month or two back. When the Viewlog is used, some of the multi-view 16 camera panels are blue panels. (but everything is recorded 24x7) The Viewlog program will not locate the video files, but the video files are there. The repair database utility usually repairs the problem once all the empty folders have been removed. If the files are present on the hard drive but not indexed in the Viewlog, they can be manually copied to a backup and the backup database rebuilt. If the video is truly a corrupted recording, maybe changing the codec would help. If you problem is files missing in the index when the files are actually on a storage drive, I can offer some more suggestions. I asked, but I haven’t heard anything from Geovision yet. My problem: viewtopic.php?f=36&t=19928

We have several Geovision 1120 and 1480 version 8.3 systems with two to five dedicated video storage drives that are not reliably recycling older video. Sometimes there be a few of the date folders containing a couple of random video files for a few different cameras. As an example, a 16-camera system may have deleted (recycled) all of June, except for camera-12 folder 0611 containing eight video segments and camera-10 folder 0619 containing four video segments. The video in these ‘orphan’ folders is not indexed in the Viewlog. Compounding the problem, when reviewing video in a previous month with the Viewlog, some cameras are not available in the Viewlog, and come up with blue panels. Again, the ‘missing’ camera playbacks are random with different recorders. The video is really on the disk, just not in the database. The video will usually be from the same cameras that had orphaned date folders. The oldest recorders were first deployed in 2006; there has been occasional database issues, but since the 8.3 upgrades/fresh installs the database problems have become routine on recorders with over two dedicated storage drives. For now, my solution has been to run a utility to delete the empty folders, and then run the database repair utility full rebuild. Performing a complete ‘rebuild all information’ will usually correct the problems – the video segments in the oldest, orphan date folders is recycled appropriately, in the but a month or two later the same problems occur. The faster database repair will often skip a camera or three in previous month’s recording (never in the current month.) With a dozen recorders, some containing 5 or so terabytes of video spanning a few months, this becomes time consuming. The issue is uncommon on a recorder that has just two or three dedicated video drives. Everything records round-the-clock, recycle is on, and the hardware is typical, the software is XP & Geo 8.3, some computers are ‘fresh installs’ and some upgrade installs. There is a dedicated O/S drive that holds the Geovision database. Every recorder is rebooted and check-disked every two or three weeks. All computers are set up with one storage container, with a path pointing to a uniquely named storage folder on each dedicated video storage disk. I have even tried deleting the database folder contents to no avail. Should each disk drive be set up as a storage container, with one path to the storage folder? Any suggestions would be appreciated.

Hi – The best way to display recordings from the GeoVision recorder on a different computer is to use the playback software included on a video backup created by the GeoVision recorder. The playback program will allow much better control. The playback program will also allow exporting the video in a single .AVI file that can be viewed on any computer that has had the GeoVision codecs installed (but sacrificing the ability to reverse, slow, step-by-frame, etc) You will have a lot of difficulty using any other playback software on the time-lapse AVI files, particularly if some cameras were set to record on motion only. A video backup is created by pressing the F10 key (or the backup button), selecting the time and cameras. Be sure the 'include playback software' box is checked. Older Geovision versions default to saving on the C:\ drive - the newer versions allow navigating to a different drive. Since your video has been copied to the external drive, I would suggest these steps to play back the video with the GeoVision software: - First create a backup with the same number of cameras from any GeoVision recorder to a different portable hard drive. Study the directory structure; you may need to change some folders to reflect the actual date of the recording. Delete the .AVI files on the new backup, and replace them with the files you saved initially. Next, run the ‘repair database utility’. The name is something like EZRepair (I don’t have a disk with me). When you run the repair utility, you will need to click the square icon to search the desired location. Then run the executable for the backup - EZViewlog500.exe. Use the pull-down on the upper left to select a camera, or select ’multiview’ and all cameras will be on-screen. If you are having difficulty, one other option would be to just copy the original files to the folder where you have created a new backup and run the repair utility with the box checked to ‘search entire drive’. The repair utility seems to do a good job locating and identifying video files. After the repair, again run the executable for the backup - EZViewlog500.exe. I have seen video submitted successfully on DVD. The original was exported as an AVI using the GeoVision playback program, then rendered into DVD with NERO or Roxio DVD creating software. Again, the GeoVision software was necessary to create the exported AVI file. The Geovision playback codec is necessary to replay a Geovision exported video. A user with administrator rights can install the codecs. An instillation program is available on this forum under the topic “Free Software for GeoVision DVRs >> Install Geo Codecsâ€

For playback, it is best to manage the .AVI files using the GeoVision recording software. The Geovision playback software offers faster/slower playback, forward or reverse play, zoom-in, brightness/contrast etc. A time frame can be extracted from the original recording for playback using the GeoVision software for Windows media player. The playback computer will need to have the GeoVision codec installed. The GeoVision playback program will load the codec (sometimes administrator rights may be necessary) The monitor’s resolution should be 1024x768 or greater. Pressing the “ k â€

Re the 8.22 update: The problem occurs in the Viewlog program, but I can not say for sure if the symptom can be remedied in a remote view with the patch. The update may not be applicable for your problem. If the mosaic problem is reduced when you reduce the keyframe setting, the patch may help. Your vender should be able to offer more insight. A different codec may also help. Repeat the process that caused the problem now that you have changed the codec, and see if that helped. Also, do a test on the network local to the GeoVision DVR. If the problem only occurs when you are on the internet, the upgrade may not help. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Storage paths: I wouldn’t put a TEMP folder or anything on a drive for video. Taking up disk space on a video storage drive can lead problems. I configure one storage group folder that has a path to a single folder on each dedicated video storage drive. The GeoVision default may put a storage location on your C: drive. I create a second group with all my storage drives and delete the first group that had the C drive. For each drive, I have a single folder in the root labeled something like GV_PATH_1-d on drive D, GV_PATH_2-e on drive E etc so I can insure at a glance that I have used each drive. Make sure no video storage group or folder path is on your C: drive. Don’t add anything to the drives dedicated to video storage, and enlarging the reserved space may help. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I let all the GeoVision database folders sit on the C: drive, but I make sure they have a dedicated folder. Some of them default just into the GeoVision folder, I think. Yes, the recorder will overwrite the oldest video. The first storage group folder will fill (filling the drive), and then the second etc. Once all the drives are full, the oldest video is deleted, maybe a few hours at a time, I am not sure. So test the codec you just switched to and also test on a local connection, make sure the video storage drives are dedicated, and no video storage folders occur on the C: drive - Got to go to work - sorry if this response is disjointed!

I Agree – storage, memory and processing power are cheap. I always attempt to save the best quality video without regard to storage. I record all cameras 24/7. A blue panel is disconcerting during multi-camera playback. Your computer hardware should allow 32 inputs when software version 8.3 is released (using PCI and PCIe 1480 combo cards). Your storage capacity should provide months of video unless your application requires a high frame rate 24/7. To remedy your mosaic issue, try reducing the key frame rate on the troublesome camera. If the duration of the mosaic problem is shorter during playback, try an update the host and client to version 8.22. I started reducing the keyframe when version 8.2 created mosaics during playback from backup disks on remote workstations. (Your vendor can provide the 8.22 patch if required.) Each time it came on a keyframe, the mosaic cleared for a while. I did not notice a quality change or performance difference with a lower keyframe. The Mpeg4-ASP codec may also eliminate the problem. H.264 has also caused mosaic issues on underpowered machines. It MAY be a problem on the network connection you have. Also, connect to the DVR on a local network instead of Internet as a test as well. There is an option to encode the live video with different codecs for remote viewing. I am not near a system now, and do not rember just where, but it is an option in the client - I am using notes for this reply. The settings I have found satisfactory are below. I welcome any input. Question 1: Geo-Mpeg4 ASP seems to deliver the best quality. The H.264 codecs don’t provide as much detail for distant objects, and the plain Mpeg4 is only a little better than H.264. (H.264 does save an enormous amount of disk space). General – Enable direct draw overlay Enable deinterlace Render Panel resolution = monitor native resolution Event Log Size = 5 minutes (better playback for lengthy segments – video can jump between segments) Monitor Options (I’m not sure if this is active with Round-the-clock recording with the motion detection option, but I set it anyway) Pre-record setup Performance = extra 35/11 frames (or whatever you think is appropriate) Camera record setting Record quality = 5 (highest) 720x480 Rec. frame setting – Limit Rate Rec. of Motion - Max frame rate of motion 5 to 8 per sec (that covers anything but card tricks) Max frame rate of non-motion 1 to 2 per second (I think a lower frame rate during times of no motion permits faster review of mutiple cameras, besides the disk savings, particularly when backed up to CD/DVD. Round-the-clock recording with Geo Mpeg4-ASP Apply Advanced codec setting – advanced codec settings: Enable multithread encoding - fixed Advanced user defined Half-pixel (better quality per manual – Haven’t experimented much with quarter-pixel) Quantizer 2 (higher reduces quality slightly per manual – can not go lower) Inter-frame threshold 1 (higher value reduces quality slightly per manual) Keyframe at 30 or 60 (higher slightly reduces quality) A separate hard drive is necessary for the OS and Geovision software. I use a Basic disk for every drive, one partition per drive. If you don’t have a small disk for the OS, partition 40-60 gigs from a large drive to dedicate to the OS. Use NTSF for all drives (exception: a USB drive that may be used for backup review on a different workgroup or a domain should be FAT-32 to avoid permission issues). Dynamic disks or hardware RAID doesn’t seem to alter record or playback performance. If there were a hundred concurrent connections, a RAID array may make a difference. When (not if) a serious incident occurs, the investigation may require the original storage media. A RAID array may require the entire DVR for successful playback. In earlier days, a SCSI RAID 0 did make a difference on last century’s hardware. There are storage options to record selected cameras to different locations, but I just dump them all together. GeoVision may split a day to different drives as it deletes the oldest video, but always seems to record all connected cameras to the same disk simultaneously. Question 2: There is a mechanism to alter the resolution when using Live view and webcam. I think the options are visible when using the client. I am happy with the GeoVision defaults on a multi-view. I do not use much live Geo - I use the Remote ViewLog. For a local connection, use a gigabit LAN with an appropriate switch, enable jumbo frames on the NICs and use a public domain test tool to determine the optimum MTU. Question 3: I think the GeoVision will save as much as 999 days. The video log storage offers options to delete after xxx days or recycle, which should fill the disks before deletion. I haven’t had an issue with GeoVision on leap years or daylight savings time changes since Windows handles that part. In the Viewlog program, previous months and year open from a Windows-like tree. Also, I enlarge the recycle threshold to 2500 MB on large drives. ^^^^^^^^^^^^^^^^^^^^^ There are some great performance tweaks in Rory’s sticky. A good video signal is essential. Use a video signal meter for adjustment when using any amplified UTP video – I am satisfied with the ‘FM Systems Camera Master’ that provides a digital readout of color burst, composite, luminance, sync and focus. Correct video will provide optimal recording. If a long-haul coax camera provides a poor image, there are several products that can restore the levels as much as possible at the receiving end. (I suppose amplified transmitter would be better, but that entails two technicians.) I think the GeoVision noise reduction option results in a softer image. There are many Windows settings also. Rory has a great sticky at the top of the main GeoVision forum. There are also lots of unnecessary services in WIndows. Don't forget to configure the BIOS to restart after a power outage is detected. Thats all I have time for now. I'm sure others will offer more tips.

Thanks, Is anyone starting the Geovision system as a service in a domain (or even just as a service)? I am doing the automatic login with the GeoVisions in a workgroup presently using the Start>>Run>>Control userpasswords2 feature. Almost the video retrieval/review is over the network. for some reason, the Remote View log retains the last password used, which creates some accountability issues and grounds to start another thread. Thanks again