Recherche avancée

Médias (91)

Autres articles (59)

  • 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 (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

Sur d’autres sites (3853)

  • lavfi/curves : introduce "all" field in presets and use it.

    11 avril 2013, par Clément Bœsch

    lavfi/curves : introduce "all" field in presets and use it.

  • Revision 2f19cd03aa : Merge "Remove unused vp9_recon_mb{y,uv}_s" into experimental

    12 avril 2013, par John Koleszar

    Changed Paths : Modify /vp9/common/vp9_rtcd_defs.sh Merge "Remove unused vp9_recon_mby,uv_s" into experimental

  • FFMPEG : extracting jpegs at 1 fps rate with "-r 1" or "vf fps=fps=1" causes first three frames to be wrong [closed]

    11 avril 2013, par Stefan

    I need to use ffmpeg to extract video stills from a video, one picture per second, starting with second 0. I created a 4min test video with a running timecode (25fps, starting with 00:00:00 running to 03:59:24) If I use either

    ffmpeg -i input.mp4 -f image2 -r 1 still-%d.jpeg

    or

    ffmpeg -i input.mp4 -f image2 -vf fps="fps=1" still-%d.jpeg

    I fail because the first three images do not display expected time codes 00:00:00, 00:01:00, 00:02:00, but 00:00:00, 00:00:01, 00:00:13, and all subsequent images show having frame 13 in their timecode (and not :00). This causes my video preview to be off by 1-2 seconds.

    I had to resort to invoke ffmpeg for each frame, using -ss 0..240 and -vframes 1 to extract exactly one frame at the exact time. This works perfectly, all output files show the timecode of the first frame of that second.

    This method is considerably slower, however, and I'd rather not use it.

    Is there something I missed with the -r option or fps filter ? I tried specifying fps=fps=1:round=zero, but I got an error saying that the key "round" was not found.

    Thank you in advance !

Navigation