Recherche avancée

Sur d’autres sites (13285)

• how to make cloud services for camera device iot monitoring and control

  16 novembre 2019, par guardian presence

  Looking to use ffmpeg to pull video trsp stream over tcp pass the video feeds to opencv for object recognition and tracking passing the output to ardunio serial control systems like alarm systems drones ardunio controlled lawn mores.

  Lets say some one has a cctv system and a drone laying around if they connect to my cloud the system can pull the stream from the cctv cameras pull the stream from the drone if object moves in on camera zone the cloud can control the drone to move to that zone and take a closer look at a face if face detected send alert return drone to docking . if ptz camera opencv tracking zooming to face

  if ros can turn into a cloud service need to know about hosting and
  building front end user login and device login.

  i’m a cctv installer new to programming and want to setup cloud login for camera iot devises were users can control and monitoring of devices from a central cloud

• How to scale the YUV image from MediaCodec output with any color format ?

  17 octobre 2014, par Frank Bush

  I’m using MediaCodec to decode the video and using sws_scale(from ffmpeg) to rescale it.I can deal with one special color format,eg. YUV420P, and rescale it to destination size. But I have to do some preparing work, such as getting the linesize and memcpy the output buffer to three plain slices(data[0],data[1],data[2]).And the decoder output color format varies on different devices.If I get the colorformat,is there a method in ffmpeg to rescale it automatically without special dealing(Of course, the color format should be supported by ffmpeg) ?

• How to (properly) use the ExtendRtspStream command in Google's Nest Device Access API ?

  19 juillet 2021, par 6twenty

  Using Google's Nest Device Access API, I can generate an RTSP camera stream using the GenerateRtspStream command and subsequently stop the stream using the StopRtspStream command. Makes sense, however these streams are only alive for 5 minutes by default - so the API also features another command : ExtendRtspStream.

  


  On the face of it, this sounds like it should "extend" the stream you had originally created, however these RTSP stream urls include an auth query parameter and extending a stream simply issues a new token to use for this, which means that the url for the stream changes every time it gets extended. So in reality the stream isn't getting extended at all as the url you use to access the stream still gets invalidated, and you have to restart it with a new url to continue watching the stream. So what's the point ? You may as well just call the GenerateRtspStream command and switch over to that one once the first expires. Is there some way to seamlessly change the RTSP url mid-stream that I'm not aware of using FFMPEG, perhaps ? Or to have a proxy server that broadcasts a static RTSP url and seamlessly switches the actual url each time it gets extended ?

  


  ---

  


  Rant starts here : I'm really hoping that this behaviour is actually a bug or oversight in the design of the API, and that ExtendRtspStream is supposed to keep the same url alive for as long as needed, because it's awfully pointless to have an RTSP stream that only stays alive for a max of 5 minutes. Heck, it'd be more useful to have an API that just returns the latest single-image snapshot from the camera every 10 seconds or so - but alas, there's no API for that either.