megapixel man

It does not all come down to pixels on target. There are other factors that must be considered, such as low light performance. 3 mp is worthless if it's too dark to see an image on the monitor. Good CCTV system design requires an understanding of issues beyond simple pixel count. Best, Christopher You have missed the point. amirim has not and is trying to school you, join the class.

Oh, my bad English skills I will try to explain once more what I meant. Lets say you calculated that you need 3mpix camera to see number plates of cars entering gates. When it switches to 1.3mpix at nigth, you wont have enough resolution to see number plates. Whats the point of that 1.3mpix if its no good? There should be two sensors, both 3mpix. 1.3 is better than 3mp at night. and recording at 1.3 still has a very good res than any analog camera. meaning you can zoom in from footage. have a look at this live camera 3mp day 1.3 at night. this is a mobotix M12 http://www.mobotix.ro/ro/index.php?id=10055&lang=en&camid=1521 Robert, you are 100% correct. It all comes down to pixels on target. Just because a sensor has larger pixels giving a greater "well capacity" for low light performance does not mean that a 1.3MP sensor has the same pxiels on target for the same scene as a 3MP sensor.

Yea that is the only one that I know of for Mobotix. Thanks for your help, I dont need to know from a calculator how much storage I need, I just need to know the bit rates for each of the cameras in MJPEG for the various compression levels available. Also is that right about only 4ips MJPEG 3MP resolution? as that may be a show stopper for the upgrade I am looking at. Any way of pushing them to minimum 8ips in MJPEG 3MP res if they are going straight to a server for the processing, or is it really limited by the cameras on board processor? Cheers..

Need to find out the bit rates of the following Mobotix Cameras in MJPEG, 3MP resolution 8 images per second. Not going into MX Control Centre so MJPEG bit rates required. Q24. D12, D22 Any help appreciated.

Wireguys, that calculator does not give the camera bit rate when using MJPEG. Also upon investigation of the Mobotix Web site it appears that the max yo can get is 4 images per second in MJPEG 3MP resolution, is this correct? cuz thats pretty slow image rates.

Woody, the boys at Orion know their stuff. Have met with them a number of times. We have done a fair share of long range testing with numerous cameras and lenses. I second their advise of using the EF mount Canon Lenses or similar. Best coupled with high MP rated cameras: The Camera in the shot has RS-485 on the back, would be hard to find and housing and PT head for that one though I know one of the copper mines are using these cameras with smaller lenses, 24-70mm, 70-200 and 400mm.

Joe, Your idea for the first part of your problem may help, increasing the shutter speed will help, a manual iris lens may assit further. Going to a good day/night megapxiel camera will assit even further. To read plates or any text it's all about the pixels on target. For night time, yes blast out the IR, and keep a fast shutter speed. Then you could try a visable light cut filter if just adding the IR isnt enough. See this: there is no light other than a good IR Illuminator. The plate looks flared out. There is no visable light cut filter. The car is moving. Then if you've got the pixels on target right you can zoom into the live or recorded image and hey presto: let me know if you need more info

Yes Rory, it does exist. On the cheap NO. You would be looking at something like the Avigilon 1080p PRO Camera with CCD Sensor and a high performace EF Mount Lens like the Canon L series 50mm or 85mm f/1.2 running at 30ips visually lossless compression. A kicking PC with a bucket load of storage and a High End Graphics Card. Cheapest for this would be Soundy's suggestion of a good HD Camcorder for a DIY option. Best would be to hire someone in the broadcast game to do it, and probably cheaper than buying all the gear yourself.

With most IP systems, if you record the same stream that your live viewing then you should have the same ability to zoom into the recorded footage as you do with the live footage. The higher the MP and the less compression the better. A Losless Compression codec is better than a lossy one for digital zooming on the recorded footage also. Dont know much about Geovision to answer your specific question about that platform.

1.3 Megapixel (1280x1024) is not a HD format. HD formats are 720p and 1080p with an aspect ratio of 16:9. Some what agree with Soundy, dont confuse Megapixel CCTV with HDTV.

Hi Robert, LED White Light works. I have a few systems out there with the Raylux Units, Easy to install and set up. http://www.rayteccctv.com/products-category.aspx?categoryid=2. Highly recommend these units.

No, they use a variety of the standard cctv codecs and some use their own: MPEG4 JPEG H.264 JPEG2000 MxPEG (Mobotix) There's probably others, but the above come to mind quickly.

The single lens 360 degree cameras with wide angle fisheye lenses IMO are not the goods for 360 degree coverage, a multi sensor approach is the best way to acheive the best image quality without requiring a heavy processor dependant algorithim to de warp and display the image. Also due to the fisheye lenses used on a single sensor 360 camera there are a number of pixels on the sensor that do not come into play. There fore the images look "washed out" and lack detail in the perimiter of the scene. A single camera with 4x 2MP sensors with each acheiving 90 degree FOV is a far better solution than a single 3MP sensor with a wide angle fisheye lens.

Offer 2 different options at the end of your standard warranty period. 1. Preventative Maintenance agreement - 2 - 4 visits per annum, clean, adjust , test and report any faults found in a maintenance report with itemised cost to repair any faults. 2. Comprehenive maintenance agreement, preventative maintenance visits + rectify any faults at no additional cost. Go back to back with extended warranty from your equipment supplier.

Only due to two factors: 1. Many cameras suffer from noise in low light. 2. Alot of NVR software detects noise as motion / changes within the scene. Same as if it rains.

It's not about what the cameras support, it's what the switch supports and whats required to support the number of cameras and bit rates on the network. At this stage of the game cameras are sending less than 100Mbps each so dont require GIG NIC's, as resolutions and frame rates increase then this may change, however compression codecs will also become more efficent over time.

Its not a question that can be answered that easy. Depends on your server spec, and the application software. Compression codec, frame rate and resolution all relate to a total bit rate, which needs to be known to determine how many cameras, regardless if they are Megapixel or not. Are you going to run a true server client relationship or just a server with viewing client also installed on the server? You can get more cameras on a sever that is only being used as the server then you need a workstation to run the client application, if you put the client application on the server as well then the total number of cameras will decrease. Talk to your application provider to get their recommendations, as it varies from one to another. Rule of thumb for a server only, approx 250Mbit total for a standard machine with GIG NIC and single Quad Core processor.

Axis use the chproducts joystick, as do alot of the IP Systems on the market.

Done it lots of times, which IP PTZ Cameras are you looking at using, I can then give more info on software platforms. In the meantime have a look at these http://www.chproducts.com/oem/finger_ip_desktop.html Depending on the software platform and how it supports the Joystick you can control Conventional PTZ, IP PTZ and Digital PTZ on the Megapixel Cameras. Also most of the mouse functions, almost taking away the need for the keyboard.

Even with the overview cameras, if you've got the FOV set up so that the widest scene width still gives the correct PPF for good facial images then all good. Issue is that most don't, which means when you zoom in on a face off the recorded footage all you see is MR. Fuzzy. Problem is most "punters" want the result but dont want to pay for the number of or quality of cameras to acheive it. (ok thats my whinge for the day).

Hi JD, I put it into 2 seperate sections, 1. Recognition, 2. Identification. Recognition where the person is known or can be recognised by someone by the recorded footage. Identification where the person is not known and requires comparison of the recorded footage to a person or other images in detail. For Recoginition I try for the person to be clear with face ocupying 30-50% of vertical screen size. Generally in the 75-100 ppf range. For identification with the face to be clear ocupying 100% of the vertical screen. Minimum of 150ppf but try to get 200+ ppf to get minor details clear, like scars and markings, eye colour, etc.. While giving an approx PPF, other considerations need to be taken into account, level of compression (always use the recorded footage as your reference if for example your camera dual streams), lighting etc.. I have some installations where the choke point cameras are giving 250+ PPF for identification, and they do their job well with a lossles compression.

True, is the lens your using IR corrected? Good question... I'll have to check the spec sheet. It's an integrated lens, so there's no changing it out, unless one of you knows a trick. ************** Edit **************** It doesn't say if it's an IR corrected lens. mmmmm, if it doesn't say then its probably not, as most lens manufacturers would advertise that feature. With an IR cut filter and a non IR corrected lens, under IR the focal point shift may be to great for any real use of the camera in that environment. Its not as though you can go and re focus a camera every time it gets dark and the IR is on.

True, is the lens your using IR corrected?

Without going with too much of details, if YOUR camera streams H.264, it takes it and stores as such and if you stream any other format, then actual conversion takes place at the server side... Any other questions mate? Thanks for the response, and yes your response has raised many questions. Are you re-encoding prior to committing to disk or post? Have you considered latency with such a task? also processing requirements? questions just to start with.... No need to answer these questions here as I dont want to hyjack this thread, maybe if you could start a new thread with your proposed system, features and benifits. Thanks.

Can you please explain what you mean "native H.264 compression at the server side"? this does not make any sense to me. What cameras does this software curently support? Guys, lets not change the topic of this thread... if you do not understand the comments, then we will address it in a different thread about it. At the moment, it works with 33 different cameras (including IP PTZ domes) that we could get our hand on... and more should come soon... some manufacturers give them to us and some we buy... So, what is your favorite and why... Geez mate, I understand very well you you said, do you? Compression at the Server in H.264, REALLY? pass...... So no compression at the cameras or encoders eh? Stream staight to the server before compression eh? wow