Recherche avancée

Médias (91)

Autres articles (19)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (4764)

  • Compile ffmpeg for WinRT with libvpx ?

    7 janvier 2018, par Sean O'Neil

    Following this guide :
    https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT

    Can anyone tell me if it’s possible to build and include libvpx into this ?

  • Bash script : Cycle script until ffmpeg command restarts successfully

    13 août 2023, par Bellacoda

    I have a IP Camera and the recordings are saved with ffmpeg RTSP into a raspberry pi.

    


    Sometimes, when the electricity shuts off and comes back on, the raspberry boots faster than the IP Camera and the ffmpeg command (saved on a crontab to run every reboot) fails to execute because it can't reach the IP Camera (that is still turning on).

    


    I tried to put a sleep command before the command but that doesn't work either.

    


    It also happened that when the IP Camera reboots, the raspberry closes the command, but when the camera comes back online, I have to manually lauch the command.

    


    Is there a way to make a script that waits to run the ffmpeg command until the camera is fully online (I assume with the $ ? variable for command exit status), and to wait to restart the ffmpeg command when the camera reboots ?

    


    The setup I have now is a crontab :
SHELL=/bin/bash
@reboot sleep 120s ; sudo ffmpeg ...

    


  • Camera Rendering Buffers and Stutters When Processing Large Video Files with FFmpeg

    20 avril 2023, par TIANYU HU

    When rendering a real-time camera, I use ffmpeg to process a large video file(like 4G or even larger) at the same time. However, I noticed that the video frames are buffering and stuttering, indicated they are probably competing for limited system resources, like cpu, memory or I/O bandwidth etc.

    


    I‘ve tried a lot of experiments to figure out the root cause. Firstly I limit the cpu usage of ffmpeg to 25%, but sadly it’s not getting better.

    


    Then I suspect that ffmpeg would read the large video file from disk to page cache in memory as much as it can before processing, and the generated files are going to be written back from page cache to disk. The RAM of our computer is 8G, apparently it needs to swap in and swap out pages between memory and disk. This process is costly for the CPU, and other processes are likely to trigger an interrupt named “Page Fault” when they access pages that are not actually loaded into memory. If the time taken for “page fault” is too long, the program may lag.

    


    Lastly I configure the system parameters related to “write back dirty pages to disk”, such as vm.dirty_writeback_centisecs and vm.dirty_background_ratio, to try to write back the dirty (Disk I/O) more frequently or infrequently. But I’m not quite sure what would happen if I modify these parameters.

    


    Expection :
The requirement can be summarized as “real-time video rendering has higher priority, and the low rate of large file processing is accepted”, are there any possible solutions of this issue from your perspective ? Thanks in advance.

    


Navigation