Recherche avancée

Sur d’autres sites (6548)

• ffmpeg with partial motion detection

  2 mars 2021, par Silentfury

  I have video files from a static surveillance camera and I try to re-encode them using some sort of motion detection filter (keeping the movements, droping the stills) in order to save space and play time.

  


  I have successfully tried the two below filter options but it still feels not good enough. :

  


  

  • mpdecimate e.g. -vf "mpdecimate=hi=6480:lo=6420:frac=0.1,setpts=N/(15*TB)"

  


  • select (e.g. -vf "select=gt(scene,0.4)")

  


  


  The main problem is a moving bush in the camera view, that I would like to exclude from the motion detection.

  


  Is there other/better ways of applying motion detection (and stills dropping) to ffmpeg ?
Is there any way to mask areas of the video that will be ignored in the above mentioned (or any other) motion detection filter/method ?

  


  Many thanks in advance !

  


  Edit :
in the mean time I found this excellent answer from Gyan

  


  I am testing this now but would still appreciate other ideas

  


• FFmpeg RTSP stream to remote MediaMTX server disconnects after a few seconds [closed]

  13 juin, par Rorschy

  I'm new to RTSP and MediaMTX, and I'm trying to live stream my screen using FFmpeg and MediaMTX for a specific use case.

  


  Everything works perfectly when both FFmpeg and MediaMTX run on the same machine.
However, when I move MediaMTX to a remote server, the stream becomes unstable — I can't maintain a connection or view the stream reliably.

  


  Here is the FFmpeg command I'm using from the client machine :

  


  ffmpeg -f gdigrab -framerate 10 -offset_x 0 -offset_y 0 -video_size 1920x1080 -i desktop -f lavfi -i anullsrc -vcodec libx264 -tune zerolatency -g 30 -sc_threshold 0 -preset ultrafast -tune zerolatency -f rtsp rtsp:///live/stream


  


  And here’s the relevant MediaMTX log output on the remote server :

  


  2025/06/12 14:28:44 INF [RTSP] [conn :35798] opened
2025/06/12 14:28:44 INF [RTSP] [session 2e487869] created by :35798
2025/06/12 14:28:44 INF [RTSP] [session 2e487869] is publishing to path 'live/stream', 2 tracks (H264, MPEG-4 Audio)
2025/06/12 14:28:45 INF [WebRTC] [session 8a909818] created by :47296
2025/06/12 14:28:45 WAR [WebRTC] [session 8a909818] skipping track 2 (MPEG-4 Audio)
2025/06/12 14:28:47 INF [WebRTC] [session dd0d3af7] created by :46306
2025/06/12 14:28:47 WAR [WebRTC] [session dd0d3af7] skipping track 2 (MPEG-4 Audio)
2025/06/12 14:28:49 INF [WebRTC] [session 5f853024] created by :46320
2025/06/12 14:28:49 WAR [WebRTC] [session 5f853024] skipping track 2 (MPEG-4 Audio)
2025/06/12 14:28:51 INF [WebRTC] [session 3edba9a8] created by :46342
2025/06/12 14:28:51 WAR [WebRTC] [session 3edba9a8] skipping track 2 (MPEG-4 Audio)
2025/06/12 14:28:53 INF [WebRTC] [session 4be5bd9b] created by :46352
2025/06/12 14:28:53 WAR [WebRTC] [session 4be5bd9b] skipping track 2 (MPEG-4 Audio)
2025/06/12 14:28:54 INF [RTSP] [conn :35798] closed: terminated
2025/06/12 14:28:54 INF [RTSP] [session 2e487869] destroyed: session timed out
2025/06/12 14:28:54 INF [WebRTC] [session 8a909818] closed: terminated
2025/06/12 14:28:54 INF [WebRTC] [session 3edba9a8] closed: terminated
2025/06/12 14:28:54 INF [WebRTC] [session 5f853024] closed: terminated


  


  My questions :

  


  

  1. What could be causing the RTSP stream to disconnect when streaming to a remote MediaMTX server ?

  


  2. Are there any recommended network settings or MediaMTX configuration tweaks to ensure a stable stream over the internet ?

  


  


  Any help or guidance would be greatly appreciated. Thanks !

  


• Announcement : Piwik to focus on Reliability, Performance and Security

  7 octobre 2014, par Matthieu Aubry — About, Community

  To our valued team and community,

  Well, we have moved fast and achieved so much during the past few months. Relentlessly releasing major version after major version… We got a lot done including several major new features !

  The speed of adding new features was a great showcase of how agile our small teams and the larger community are. And I’m so proud to see automated testing becoming common practice among everyone hacking on Piwik !

  For the next few months until the new year we will focus on making what we have better. We will fix those rare but longstanding critical bugs, and aim to solve all Major issues and other must-have performance and general improvements. The core team and Piwik PRO will have the vision of making the existing Piwik and all plugins very stable and risk free. This includes edge cases, general bugs but also specific performance issues for high traffic or issues with edge case data payloads.

  We’ll be more pro-active and take Piwik platform to the next level of Performance, Security, Privacy & Reliability ! We will prove to the world that Free/Libre Web software can be of the highest standard of quality. By focusing on quality we will make Piwik even easier to maintain and improve in the future. We are building the best open platform that will let every user liberate their data and keep full control of it.

  If you have any feedback or questions get in touch or let’s continue the discussion in the forum.

  Thank you for your trust and for liberating your data with Piwik,

  Matthieu Aubry
  Piwik founder

  More information

  • How long is each release of Piwik maintained for ? (FAQ)
  • When is the next release of Piwik ? What is the release schedule ? (FAQ)
  • Pulse of Piwik : our monthly pulse report shows 27 different people contributed to Piwik core in the last month !

  

  This is an amazing testament of the power of free/libre software and yet we think this is just the beginning. We hope more developers will join and contribute to the Piwik project !