CollinR

Not so much with MJPEG but with MPEG4/H.264 yeah it can become a huge burden to decompress for on screen viewing. I also have an MPEG4 camera on that system but I have it set to only decode keyframes. The local display looks like maybe 5 fps but the recordings are much closer to 25fps and the CPU load was dropped quite a bit. Granted this is a VGA camera not megapixel. I'll make you a deal on a little valley if you wanna play with one.

Well since thats quite a bit less load a little valley should handle that with some left over. It's shortcoming for you would be in LAN capability, I would add a gigabit NIC and be done. Then you can run your cameras on the gigabit NIC and your local and web access on the onboard 10/100 NIC. Basically all you are doing is writing the file to disk, so not much CPU is needed for recording.

Another key factor is as mentioned if you need to decode the video for motion detection or just for local display. If neither of these is happening and you are either reling on the camera for motion detection or you really don't need much of a machine at all. I have a 2100 and a 3131 running on an Intel Little Valley which only has a 1Ghz CPU. It is running motion detection, transcoding for streaming and displaying it and 5 analogs which it's also software compressing. Now once Arecont converts all over to h.264 it'll be an entiely different beast, that takes loads of power to decode for motion and display.

Baluns have nothing to do with netrowking or LAN, it is mearly a way to swap RG for Cat5 cable. If his house is wired up and you have an easy enough to rewire patch panel you can use baluns but that will make the wall plate and plug of the patch no longer for networking use. Also the house would need to be homerun wired as this would not cross a router or switch. Basically some baluns have an RJ45 connector and use Cat5/6 cable but they have nothing to do with networking/ethernet at all.

Not IMO when comparing cost:performance, do they even have a real daynight cam? Anyway you can fix your troubles with a section of PVC pipe thats OD is about the same as the dome and wall thickness is enough to support screws. You can then use a saw and cut the required angles with relative ease. Then paint the PVC to either matchthe dome or wall. The best method is as was mentioned, use the wall mounting bracket. It will not only solve this problem but also keep water spots off the bubble as now that part is pointing straight down.

1st turn that off and make sure you have it set for the proper auto iris lens DC or video driven. AES is the internal electronic shutter you use when you have a fixed iris lens which I'm guessing you do not.

Also part of being a good installer is positioning the camera in a way that it has to tolerate as little of this as possible. Do you have AES enabled? What did you exepect from that camera, to me the vehicles especially the closer one is the focus of the camera. Surely you don't expect any identification past where the bright section is. This is an NTSC camera after all.

You can post things that you personally own and are normally used for sale in this section. If you are a dealer then you may not post items for sale as a function of business.

On the setup page of the router you will see the router's IP 10.10.10.1 and below that youwill see the DHCP IP address pool and pool size. Probably looks something like pool size 15 and start address 10.10.10.100 or 10.10.10.10. This would give you a DHCP pool of 15 addresses. You need to pick an address NOT inside the pool but below it. So 10.10.10.2 should work in both cases. Set the DVR IP to: 10.10.10.2 mask 255.255.255.0 gateway 10.10.10.1 DNS 10.10.10.1 On the applications and gaming section of the router use the IP address 10.10.10.2 App = CCTVDVR, Ext Port = 8000, protocol = TCP, Int Port = 8000 IP = 10.10.10.2, enable checked.

Good alll around the panasonic WV-CP484 is really hard to beat. Combined with a low F IR corrected lens and you have a real winner. Heck the 484 doesn't even need the IR corrected lens it will automatically rebackfocus when the filter opens. However it's like x2 you price range, but "good" and "all-around" costs money x2. Maybe you should consider a BW option or changing the mounting location. Also super dark and pointed into the sun is not a good combination. If you think the cam you have now is good enough just get a day/night lens for it to minimize the focus shift.

Interesting read. http://en.wikipedia.org/wiki/NTSC#Lines_and_refresh_rate

PM me I have an open box camera you may be interested in.

If you have an NV5000 and add a zone expander but only connect/enable 4 cameras your framerate is reduced like you had all 8 connected/enabled/monitored.

802.11a with WEP 64 so you can basically recreate this with ease on your own. The security of WEP is kinda lacking but I doubt many actually care.

Well that somewhat defeats all the goodness of embedded but retains all the bad. Inversely I don't think anything says you can't run a RTOS like QNX on cheap and readily available x86 hardware. Which although doesn't fit that definition (and many other people's I'm sure) ~could~ actually be the best of both worlds. RTOS stability and cheap readily available hardware.

Use a covert illuminator and BW cameras, totally invisable.

You might look at the Geovision IP cam thats the only IP cam that you can add without spending more then a whole different setup would cost.

Dunno about the breakroom but if changing is taking place I think you are on very thin ice.

You will probably need an Svideo to RCA adapter and then an RCA to BNC adapter. I have never seen an Svideo to BNC adapter but if you find one it should work. VGA down a single coax would be much more $, over Cat5 more $ but much more reasonable. The cheapest option is baseband adapters as discribed. 1st check and make sure Svideo and VGA still work, I would think lighting would fry both if it got one. Also check the cable, hook up a VCR to it and try to play across to the display.

Don't forget insects and spiders, both seem to like IR and both will botch your picture and nothing much you can do about it.

Sure, you can also simply disguise it too.

You should also have errors and omissions coverage, this protects you fro liability in the design phase. ie You sell someone some crappy IR on the cam bullets and they get knocked over, they cannot identify the subject because of the whiteout or internal bounceback. They sue you for the cost of the system because it was designed poorly and hence failed to serve it's intended purpose. Also spend some coin on a bombproof contract in the first place.

In my experience Cat5 has better interference rejection when compared to RG59, never tried RG6 as the correct stuff is so hard to find. I've been Cat5 only for over a year now and no regrets, when going building to building or runs to camera clusters Cat5 is the only logical choice. I have never used a "UTP hub" dunno what that is. I am thinking it's marketing speak for multibalun and power distribution in a 1-2U form factor. I just build my own.

Me personally I would rather have the ABF of the analog version then having it all integrated as one. It's basically a set it and forget it camera you shouldn't need to be making changes to it after it's installed.