JoeBobKing

I joined this forum if only to participate in this discussion. Return to JPEG? **** YES! These delta/temporal format video schemes are undermining the very core of the security world. I have been trumpeting the virtues of discreet video formats (ones that contain all needed information, like JPEG) for many years... ever since the first mpeg1 encoders arrived on security market from a major manufacturer you may well know.... There are many issues that the Mpeg Series bring to the table. i will make a short list of these issues 1) Can be defeated / forced to crash/ degrade significantly. Documented and publicly shown. 2) Can cause significant artifacting and image fragmentation. 3) Takes a huge CPU load to encode and even more to decode. 4) Utilizes RTSP (for the most part) to transmit the video. Most corporate backbones discourage this function wholesale 5) Has an extremely complex header architecture. 6) Has almost NO third part tools to manipulate and integrate (Live555 has a monopoly /VLC) 7) Significant latency in most implementations was designed for teleconferencing D1 or less quality video from day 1.. This house has too many rooms added on.... 9) Dropped SPS or PPS header data packets can mean no video for You. ( many camera MFGS do not periodically send down these headers.... requiring any server/client to cache and send as needed. 10) any dropped packet, such as a Iframe packet or p/B frame can trash the entire sequence until the next I frame arrives... That can be 30 seconds or more of gray screens. 11) Date time stamps are a derived function of stream start offsets.... no hh:mm:ss here! 12) We may see a wall for image sizes above 20 MP... too much to handle 13) a Snapshot is a JPEG ( usually) 14) The powers that be are already planning a replacement SOON (read the standards) 15) Don't forget you must buy licenses to engage additional streams! All this distilled from years of development and extensive application-coding research. Not just reading the blogs. Now on to JPEG. 1) Has only a few simple tags to identify all of the components. 2) Tags can be easily read. 3) Since nearly 100% HTTP/TCP, pac test are not lost. You get your images every time 4) Cant be defeated or forced to crash. 5) hundreds of tools can be used to decode/encode and utilize it. 6) Singe frames are already a JPEG. 7) JPEG is everywhere on most every device. Comment tags, which can be multiple can contain audio, telemetry data or other info synchronized to the video itself... without touching the video fields. 9) JPEG can do most anything... so why mess with it?.... BECAUSE ITS TOO FAT.. THEY SAY... Well it ain't.... Lets take a look at a system of oh... lets say 2,500 JPEG 1-2 MP cameras ( yes, they exist) 1) all 2500 cameras consume less than 7% f a 1GBPS network at 5 FPS x 1.3 - 2.0 MP each 2) How is this possible? SIMPLE: 3) Not all cams are on one fiber.... several hundred per fiber maybe 4) this hub/spoke design allows the gal work to be performed by the backplane of the switch... where speed is almost limitless.... 5) Ip data is not all set simultaneously.... There are milliseconds when the wire is actually quiet.... This is the real world now... what you get is a reliable system running on a corporate backbone eating a fraction of the 'computed' values. As for disk... how much is a 2 TB disk drive lately.... Disk is almost free... building a disk system to accommodate 10TB ,100TB or even 1000TB is not a big deal. One will find that using the proper NVMS that the COST for JPEG is actually LESS than the H264 equivalent... and more so with the higher MP cameras.... Due to the following factors 1) The camera delivering JPEG is much less CPU powered and memory loaded; therefore it is cheaper. 2) The CPU needed to Decode/display the H264 is several times that of JPEG. One CPU can decode 200+ cameras on a single machine in JPEG mode... MAYBE 20-50 in H264 Mode...This means you trade DISKS for CPUS, MEMORY and BTU LOADING.... a losing proposition. As a last note... 1) Disks keep getting cheaper and higher density 2) Networks of 1GBPS and 10+ GBPS are getting cheaper The JPEG issue is a manufactured one... or should i say manufacturer?