Recherche avancée

Médias (91)

Autres articles (48)

  • Qu’est ce qu’un masque de formulaire

    13 juin 2013, par

    Un masque de formulaire consiste en la personnalisation du formulaire de mise en ligne des médias, rubriques, actualités, éditoriaux et liens vers des sites.
    Chaque formulaire de publication d’objet peut donc être personnalisé.
    Pour accéder à la personnalisation des champs de formulaires, il est nécessaire d’aller dans l’administration de votre MediaSPIP puis de sélectionner "Configuration des masques de formulaires".
    Sélectionnez ensuite le formulaire à modifier en cliquant sur sont type d’objet. (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (4026)

  • ffmpeg is preferring to encode in VP9 but I'm trying to encode in VP8

    1er septembre 2016, par user1689634

    I’m trying to encode webm video files specifically in VP8, but ffmpeg is forcing VP9. I’m using -c:v libvpx, which to my knowledge is supposed to be VP8, but when it encodes I see it’s encoding in VP9 instead :

    ffmpeg -framerate 7 -loop 1 -i "C:\converted\cover.jpg" -c:v libvpx
    -i "C:\converted\Image.wav" -b:v 50k -c:a libvorbis -b:a 96k
    -vf scale=-1:300 -shortest -metadata title="%artist% - %album%"
    -metadata author="%artist%" -threads 8 -y "C:\converted\%artist% - %album%.webm"

    ffmpeg version N-81489-ga37e6dd Copyright (c) 2000-2016 the FFmpeg developers
     built with gcc 5.4.0 (GCC)
     configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dx
    va2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-lib
    ebur128 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --ena
    ble-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfree
    type --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enab
    le-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-lib
    openh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschr
    oedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheor
    a --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvo
    rbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --ena
    ble-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --e
    nable-decklink --enable-zlib
     libavutil      55. 29.100 / 55. 29.100
     libavcodec     57. 54.101 / 57. 54.101
     libavformat    57. 48.101 / 57. 48.101
     libavdevice    57.  0.102 / 57.  0.102
     libavfilter     6. 57.100 /  6. 57.100
     libswscale      4.  1.100 /  4.  1.100
     libswresample   2.  1.100 /  2.  1.100
     libpostproc    54.  0.100 / 54.  0.100
    Input #0, image2, from 'C:\converted\cover.jpg':
     Duration: 00:00:00.14, start: 0.000000, bitrate: 3159 kb/s
       Stream #0:0: Video: mjpeg, yuvj420p(pc, bt470bg/unknown/unknown), 500x495 [S
    AR 1:1 DAR 100:99], 7 fps, 7 tbr, 7 tbn, 7 tbc
    Guessed Channel Layout for Input Stream #1.0 : stereo
    Input #1, wav, from 'C:\converted\Image.wav':
     Metadata:
       artist          : ???????
       genre           : Alternative Rock
       title           : goodnight, wonderend
       date            : 2014
     Duration: 00:04:48.00, bitrate: 1421 kb/s
       Stream #1:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, 2 channels,
    s16, 1411 kb/s
    [swscaler @ 055f7d60] deprecated pixel format used, make sure you did set range
    correctly
    [libvpx-vp9 @ 0312d8e0] v1.6.0
    [webm @ 0316e380] Using AVStream.codec to pass codec parameters to muxers is dep
    recated, use AVStream.codecpar instead.
       Last message repeated 1 times
    Output #0, webm, to 'C:\converted\カラスヤサボウ - goodnight, wonderend.w
    ebm':
     Metadata:
       title           : カラスヤサボウ - goodnight, wonderend
       author          : カラスヤサボウ
       encoder         : Lavf57.48.101
       Stream #0:0: Video: vp9 (libvpx-vp9), yuv420p, 303x300 [SAR 10000:9999 DAR 1
    00:99], q=-1--1, 50 kb/s, 7 fps, 1k tbn, 7 tbc
       Metadata:
         encoder         : Lavc57.54.101 libvpx-vp9
       Side data:
         cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
       Stream #0:1: Audio: vorbis (libvorbis), 44100 Hz, stereo, fltp, 96 kb/s
       Metadata:
         encoder         : Lavc57.54.101 libvorbis
    Stream mapping:
     Stream #0:0 -> #0:0 (mjpeg (native) -> vp9 (libvpx-vp9))
     Stream #1:0 -> #0:1 (pcm_s16le (native) -> vorbis (libvorbis))
    Press [q] to stop, [?] for help
    frame=   30 fps=0.0 q=0.0 size=      29kB time=00:00:00.71 bitrate= 333.4kbits/s
    frame=   37 fps= 36 q=0.0 size=      49kB time=00:00:01.71 bitrate= 233.6kbits/s
    frame=   45 fps= 27 q=0.0 size=      60kB time=00:00:02.85 bitrate= 170.6kbits/s
    frame=   53 fps= 23 q=0.0 size=      84kB time=00:00:04.00 bitrate= 172.7kbits/s
    frame=   57 fps= 21 q=0.0 size=     102kB time=00:00:04.57 bitrate= 183.5kbits/s
    frame=   62 fps= 19 q=0.0 size=     112kB time=00:00:05.28 bitrate= 173.4kbits/s
    frame=   64 fps= 12 q=0.0 Lsize=     141kB time=00:00:09.00 bitrate= 128.1kbits/
    s speed=1.69x
    video:87kB audio:47kB subtitle:0kB other streams:0kB global headers:4kB muxing o
    verhead: 4.908199%
    Exiting normally, received signal 2.

    The build I have does have --enable-libvpx and --enable-libvpx-vp9 flags. It is also the latest default static build, I made no changes, just extracted it : ffmpeg-20160828-a37e6dd-win32-static.zip

    I was using an outdated build for a long time and updated today. I can’t find any documentation online to help me with this problem.

  • Ffmpeg not able to access file on aws labmda

    1er septembre 2016, par Surendra Agarwal

    I am using ffmpeg to create video thumbnails on AWS Lambda. I downloaded the file in /tmp directory but ffmpeg is not able to access it and giving error

    [Error : meta data contains no duration, aborting screenshot creation]

    when I am checking the media info using ffmpeg then it is giving the output

    { ffmpegversion: 0, title: '', artist: '', album: '', track: '', date: '', durationraw: '', durationsec: 0, synched: false, major_brand: undefined, video: { container: '', bitrate: 0, codec: '', resolution: { w: 0, h: 0 }, resolutionSquare: { w: 0, h: NaN }, rotate: 0, fps: 0, stream: 0, aspect: 0, pixel: 0 }, audio: { codec: '', bitrate: 0, sample_rate: 0, stream: 0 } }

    I used fs module to check file existance on that location and it is giving the output

    { dev: 1793, mode: 33204, nlink: 1, uid: 496, gid: 495, rdev: 0, blksize: 4096, ino: 11, size: 21152, blocks: 48, atime: Thu Sep 01 2016 13:30:46 GMT+0000 (UTC), mtime: Thu Sep 01 2016 13:30:46 GMT+0000 (UTC), ctime: Thu Sep 01 2016 13:30:46 GMT+0000 (UTC), birthtime: Thu Sep 01 2016 13:30:46 GMT+0000 (UTC) }
  • Piwik 3 Development Update #2 – Git master branch will become Piwik 3

    2 septembre 2016, par Piwik Core Team — Community, Development

    As mentioned in the Piwik 3 Development Update #1 we are actively working on the new major Piwik 3 release.

    This blog post is an announcement regarding an upcoming change on our Git repository.

    On October 4th CET, we will merge the current changes done for Piwik 3 from the “3.x-dev” branch into the “master“ branch across our Piwik projects and plugin repositories. While this is not important for most of our users, it can be a problem if you have installed and deployed Piwik from git.

    • If you are currently on “master” branch and want to continue using Piwik 2, you need to checkout the newly created “2.x-dev” branch instead of “master” anytime within the next 4 weeks. Don’t forget to update your scripts and scheduled tasks (cronjobs) that may reference “master” branch.
    • If you want to receive an early version of Piwik 3 via git automatically, you won’t have to change anything.

    The final Piwik 3 release will be ready before the end of the year. If you want to give it a try, you can either use Piwik from Git and check out the “3.x-dev” branch, or download Piwik 3 from GitHub.

    Until our next Piwik 3 dev update, Happy analysis !