I work as a research analyst for zintro, and am compiling an article about trends in the digital camera industry. I am looking for expert feedback to the following question: “how will the digital camera industry fair with smart-phones' ever increasing capabilities, including high mega pixel cameras built in? Will digital cameras go the way of the dinosaur?"
the purpose of this article (which will be posted on zintro's blog) is to promote zintro experts in this space. Would you be interested in participating (there is no charge for doing so)? If interested, please comment on the above question asap by znote.
--danielle+11 Other Responses
i am looking for someone with the skill (or know the right people) to help me create a device with code which is to be installed on *my own* ip camera cctv system (4 cameras, i have all passwords, access to any settings, etc.).
Presumably a microcontroller/development platform of your choice, two wired ethernet cat5 jacks, one of which is used for line *in* (cat5-line from the foscam hd ip cameras) and also one for line *out* (cat5 out to the tp-link router and then the foscam network video recorder - nvr). There should be some small amount of memory for the mjpeg frame buffer (a few minutes of hd).
For the software side, most importantly is that it must be able to re-create and output a video stream (preferably identical in all ways) but that is based on the last captured incoming frame -- but only in the event of a disruption of the original source (such as power cut to the ip cameras). In other words, the main purpose is to ensure a stable non-stop or near to non-stop video stream to the nvr even if it has to recreate the video stream from a single last good frame. It does not have to be absolutely real-time, it can have a constant rolling buffer of 10 seconds (or whatever value) between the incoming lan and outgoing lan... And if the device detects that the incoming stream has suddenly stopped, it will instantly recall the still image from memory, loop it around into a video stream which is then outputted via the cat5-out to continue its journey to the router and nvr for recording. The device sits between the ip camera and the network router. One device for each ip camera for the sake of simplicity.
From the point of view of the nvr, there would never be any break in video source because the "blackout time" would have been replaced with the video stream made by the custom device. I only need the schematics and code or shopping list and instructions. I can buy the necessary parts and fabricate it. If there is a ready made board with good enough specs to handle hd video encoding, please go ahead and suggest.
If such dev board does not exist and you think it is better to custom make a pcb, and choose our own mcu, that is ok too. The other good use for such a custom board is to add on things like on screen display info. I did not suggest any existing board because i have not found one that has 2 on-board cat5 jacks.
Of course when the ip camera original "real" stream resumes, then the device can discontinue the re-creation job and just allow the mjpeg stream to flow as normal to the nvr, then the device switches back to standby mode and keeps monitoring for another fault to occur.
Hope this makes sense. Feel free to ask questions/concerns! thank you all for your time.+5 Other Responses
We are a management consulting firm based out of cleveland, ohio. We are currently working for a client who is pursuing a novel camera lens technology for automotive advanced driver assistance system (adas) cameras.
We are looking for experts in autonomous vehicles or people who have worked on adas systems in the past to describe what the industry is looking for from adas cameras and what lens improvements could help benefit these systems.+11 Other Responses