No, I’m saying raspistill works in stretch on my camera - so I know thats all good.
I understand you may want it - but I have to question the second part… Agreed there are plenty of pi users with camera’s but are they looking to use HG because it can display a web page with jpg’s streamed to it… and not a H264 / 265 video stream?
Please don’t take this the wrong way but…
if you want to use that then use Motion to do that - as thats what its good at - then let’s look at how we integrate motion’s events with Homegenie…
I don’t particularly have the time or inclination to make a camera integrate with hg in the way that was - it feels wrong to be taking a 4mb capture every second or so and then have the web page refreshing every second to pull that image… just doesn’t smell great when you want lights to turn on when walking in a room with ms latency - not seconds! - however there is a library I linked to which ‘could’ be used - I don#t quite like the fact that it proxies wiringPI as this feels wrong - but if it works… There is also the mig interface template project that can be used for this or the and happy to help point you in the correct direction.
I have been an bought a HikVision DVR which supports a streaming API - I haven’t even written an interface dll for this yet.
Again as you have been quite vocal of how bad you think it is but I think its worth focusing effort on the ‘higher priority’ issues - such as the stats db interop dll issue / migrating to a different db engine etc etc.
Again please dont take that the wrong way, just trying to get my thoughts out…
For me, my personal goals are:
Ability to replace interface modules without issues of locked files.
Better code editing experience with intellisense (not necessarlly through the gui)
Hierarchical location support… (prototyped -just need to implement)
State Machine Support.
Serialisation of state.