Recherche avancée

Médias (0)

Mot : - Tags -/content

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (49)

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

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

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (5677)

  • hevc : Track long and short term RPS size for VDPAU

    12 février 2016, par Philip Langdale
    hevc : Track long and short term RPS size for VDPAU

    Today, we track the short term RPS size for DXVA, but only if the
    
SliceHeader RPS is being used. Otherwise it’s left uninitialized.
    

    NVIDIA’s VDPAU implementation requires that the size be accurately
    
tracked even if an SPS RPS is being used. In this case, it’s really
    
counting the size of the RPS idx information, but you end up with
    
mangled output if the value is not accurate.
    

    VDPAU also needs the size of the long term RPS.
    

    Signed-off-by : Philip Langdale <philipl@overt.org>
    
Signed-off-by : Rémi Denis-Courmont <remi@remlab.net>
    
Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
    • [DBH] libavcodec/hevc.c
    • [DBH] libavcodec/hevc.h

  • Announcing Long Term Support in Piwik 2 – The analytics platform for your mission critical projects

    11 janvier 2016, par Matthieu Aubry — About, Development

    We are proud to announce our Long Term Support (LTS) for Piwik 2.X !

    Why Long Term Support (LTS) ?

    Part of our mission is to ready Piwik for the enterprise — and ready the enterprise for Piwik. Our fast release cycle and our ability to quickly innovate has served us well for the past seven years and has lead Piwik to being one of the most popular open source projects, used by over one million websites worldwide. But Piwik’s success today has also shown us that this fast release cycle is not suited for all users and customers. Like most large open source projects (such as Ubuntu, Firefox, Debian, Symfony, Node.js, etc.) at Piwik we now also offer a Long Term Support release which gives users the confidence that Piwik can be used for mission critical projects for months to come.

    What does LTS mean for Piwik ?

    For the duration of the LTS period, Piwik 2.X will continue to receive the following fixes :

    • Critical bugs causing data loss or data corruption.
    • Major and Critical security issues.

    Our goal is to offer you a Piwik LTS release that you can trust for all your mission critical projects.

    How long will Piwik 2.X be supported ?

    Piwik 2.X will be supported for at least 12 months after the initial release of Piwik 3.0.0.
    Piwik 3.0.0 is expected to be released in the second half of 2016.
    This means that Piwik 2.X will be supported at least until the second half of 2017.

    Which Piwik version is LTS ?

    The latest Piwik 2.16.X release is our Long Term Support version.

    How do I benefit from the LTS version ?

    To get the full benefits of Piwik LTS, please make sure you are using the latest LTS version. First, update to the latest Piwik 2.X version, then Configure Piwik to use the LTS release channel and then update to the latest LTS version.

    How do I configure Piwik to use the LTS version ?

    By default, Piwik will not use the LTS version. When you use the one-click update your Piwik instance will be updated to the very latest release : when Piwik 3.0.0 will be released, the one click update will update your instance to 3.0.0. It is however possible to configure your Piwik so that you will stay on Piwik 2.X and keep using the LTS Long Term Support version :

    • Login Piwik as the Super User,
    • Go to Settings > General > Update settings,
    • Under “Release channel” click “Latest stable 2.X Long Term Support version”, and click “Save”.

    How do I get professional Piwik Support ?

    If you need professional support for your Piwik service get in touch with the Piwik experts.

    For other questions, feedback or discussion, feel free to join our forums and comment on this LTS forum post.

    We wish you all a fantastic year 2016 !

  • FFMPEG : extract images from video with fixed interval, first few frames messed up

    22 octobre 2015, par Imperishable Night

    I wanted to extract some frames from a video with a fixed interval, so I used command lines like :

    ffmpeg.exe -i input.mp4 -r 5 results\%d.jpg`

    However, the interval between the first few frames are different from that of the rest.

    For example, if I do both ffmpeg.exe -i input.mp4 -r 25 -t 5 test\%d.jpg and ffmpeg.exe -i input.mp4 -r 5 -t 5 test2\%d.jpg (for a fps 25 video), I would expect that the results in test2 is a subsequence of the results in test with interval 5. However what I got are :
    Screenshot of results

    From the thumbnails, it is obvious that images 112 125 in test does not appear in test2. Some close inspection reveals that the correspondence between the two set of results are as follows :

    test  | test2
    
  1&amp;2 |   1&amp;2 (Those two frames are identical)
    
  3   |   3
    
  4   |   4
    
  9   |   5
    
 14   |   6
    
 19   |   7
    
...   | ...
    
104   |  24
    
109   |  25

    (Actually, when comparing the last frames, I just realized the results in test had too much mosaic. I fixed this by adding the option -q:v 1.)

    As can be seen, the first few frames from test2 actually have interval 1, instead of the expected value 5.

    What is the reason for this behavior, and how to fix it ?

    In case someone want to see the ffmpeg outputs :

    PS C:\Users\<username>\Documents\New folder> ffmpeg.exe -i input.mp4 -r 25 -t 5 test\%d.jpg
    
ffmpeg version N-50911-g9efcfbe Copyright (c) 2000-2013 the FFmpeg developers
    
  built on Mar 13 2013 21:26:48 with gcc 4.7.2 (GCC)
    
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfi
    
g --enable-frei0r --enable-gnutls --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libg
    
sm --enable-libilbc --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --ena
    
ble-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-lib
    
twolame --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxa
    
vs --enable-libxvid --enable-zlib
    
  libavutil      52. 19.100 / 52. 19.100
    
  libavcodec     55.  0.100 / 55.  0.100
    
  libavformat    55.  0.100 / 55.  0.100
    
  libavdevice    54.  4.100 / 54.  4.100
    
  libavfilter     3. 45.103 /  3. 45.103
    
  libswscale      2.  2.100 /  2.  2.100
    
  libswresample   0. 17.102 /  0. 17.102
    
  libpostproc    52.  2.100 / 52.  2.100
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mp4':
    
  Metadata:
    
    major_brand     : mp42
    
    minor_version   : 0
    
    compatible_brands: isommp42
    
    creation_time   : 2015-05-05 04:46:16
    
  Duration: 00:49:04.96, start: 0.000000, bitrate: 386 kb/s
    
    Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 524x360 [SAR 1:1 DAR 131:90], 287
    
 kb/s, 25 fps, 25 tbr, 25 tbn, 50 tbc
    
    Metadata:
    
      handler_name    : VideoHandler
    
    Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 96 kb/s
    
    Metadata:
    
      creation_time   : 2015-05-05 04:46:21
    
      handler_name    : IsoMedia File Produced by Google, 5-11-2011
    
Output #0, image2, to 'test\%d.jpg':
    
  Metadata:
    
    major_brand     : mp42
    
    minor_version   : 0
    
    compatible_brands: isommp42
    
    encoder         : Lavf55.0.100
    
    Stream #0:0(und): Video: mjpeg, yuvj420p, 524x360 [SAR 1:1 DAR 131:90], q=2-31, 200 kb/s, 90k tbn, 25 tbc
    
    Metadata:
    
      handler_name    : VideoHandler
    
Stream mapping:
    
  Stream #0:0 -> #0:0 (h264 -> mjpeg)
    
Press [q] to stop, [?] for help
    
frame=  125 fps=0.0 q=0.0 Lsize=N/A time=00:00:05.00 bitrate=N/A
    
video:1140kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.001884%
    
PS C:\Users\<username>\Documents\New folder> ffmpeg.exe -i input.mp4 -r 5 -t 5 test2\%d.jpg
    
ffmpeg version N-50911-g9efcfbe Copyright (c) 2000-2013 the FFmpeg developers
    
  built on Mar 13 2013 21:26:48 with gcc 4.7.2 (GCC)
    
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfi
    
g --enable-frei0r --enable-gnutls --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libg
    
sm --enable-libilbc --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --ena
    
ble-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-lib
    
twolame --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxa
    
vs --enable-libxvid --enable-zlib
    
  libavutil      52. 19.100 / 52. 19.100
    
  libavcodec     55.  0.100 / 55.  0.100
    
  libavformat    55.  0.100 / 55.  0.100
    
  libavdevice    54.  4.100 / 54.  4.100
    
  libavfilter     3. 45.103 /  3. 45.103
    
  libswscale      2.  2.100 /  2.  2.100
    
  libswresample   0. 17.102 /  0. 17.102
    
  libpostproc    52.  2.100 / 52.  2.100
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mp4':
    
  Metadata:
    
    major_brand     : mp42
    
    minor_version   : 0
    
    compatible_brands: isommp42
    
    creation_time   : 2015-05-05 04:46:16
    
  Duration: 00:49:04.96, start: 0.000000, bitrate: 386 kb/s
    
    Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 524x360 [SAR 1:1 DAR 131:90], 287
    
 kb/s, 25 fps, 25 tbr, 25 tbn, 50 tbc
    
    Metadata:
    
      handler_name    : VideoHandler
    
    Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 96 kb/s
    
    Metadata:
    
      creation_time   : 2015-05-05 04:46:21
    
      handler_name    : IsoMedia File Produced by Google, 5-11-2011
    
Output #0, image2, to 'test2\%d.jpg':
    
  Metadata:
    
    major_brand     : mp42
    
    minor_version   : 0
    
    compatible_brands: isommp42
    
    encoder         : Lavf55.0.100
    
    Stream #0:0(und): Video: mjpeg, yuvj420p, 524x360 [SAR 1:1 DAR 131:90], q=2-31, 200 kb/s, 90k tbn, 5 tbc
    
    Metadata:
    
      handler_name    : VideoHandler
    
Stream mapping:
    
  Stream #0:0 -> #0:0 (h264 -> mjpeg)
    
Press [q] to stop, [?] for help
    
frame=   25 fps=0.0 q=0.0 Lsize=N/A time=00:00:05.00 bitrate=N/A dup=0 drop=88
    
video:375kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.005728%
    
</username></username>

Navigation