Recherche avancée

Médias (1)

Mot : - Tags -/musée

Autres articles (50)

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

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (8981)

  • Running frei0r filters with ffmpeg - "Could not find module 'pixeliz0r'."

    4 avril 2016, par ksloan

    I installed frei0r using homebrew

    MacK:tmp kevin$ brew list frei0r
    /usr/local/Cellar/frei0r/1.4/include/frei0r.h
    /usr/local/Cellar/frei0r/1.4/lib/frei0r-1/ (119 files)
    /usr/local/Cellar/frei0r/1.4/lib/pkgconfig/frei0r.pc
    /usr/local/Cellar/frei0r/1.4/share/doc/ (4 files)

    Then I installed ffmpeg with the --with-frei0r flag, and everything compiled fine

    brew install ffmpeg --with-fdk-aac --with-ffplay --with-freetype --with-libass --with-libquvi --with-libvorbis --with-libvpx --with-opus --with-x265 --with-frei0r

    I tried telling ffmpeg where my frie0r filters were installed with

    export FREI0R_PATH=/usr/local/Cellar/frei0r/1.4/lib/frei0r-1/

    I even created symlinks from the default locations ffmpeg checks...

    MacK:tmp kevin$ ls -l  /usr/local/lib/frei0r-1
    lrwxr-xr-x  1 kevin  admin  33  4 Apr 04:43 /usr/local/lib/frei0r-1 -> ../Cellar/frei0r/1.4/lib/frei0r-1

    But I’m still seeing this error :

    [Parsed_frei0r_0 @ 0x7f8938f003c0] Could not find module 'perspective'.
    [AVFilterGraph @ 0x7f8938f00160] Error initializing filter 'frei0r' with args 'perspective'
    Error initializing complex filters.
    Invalid argument

    Full output :

    MacK:tmp kevin$ ffmpeg -i 1.mp4 -filter_complex "frei0r=perspective" out.mp4
    ffmpeg version 3.0.1 Copyright (c) 2000-2016 the FFmpeg developers
     built with Apple LLVM version 7.0.2 (clang-700.1.81)
     configuration: --prefix=/usr/local/Cellar/ffmpeg/3.0.1 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-opencl --enable-libx264 --enable-libmp3lame --enable-libxvid --enable-libfreetype --enable-libvorbis --enable-libvpx --enable-libass --enable-ffplay --enable-libfdk-aac --enable-libopus --enable-frei0r --enable-libx265 --enable-nonfree --enable-vda
     libavutil      55. 17.103 / 55. 17.103
     libavcodec     57. 24.102 / 57. 24.102
     libavformat    57. 25.100 / 57. 25.100
     libavdevice    57.  0.101 / 57.  0.101
     libavfilter     6. 31.100 /  6. 31.100
     libavresample   3.  0.  0 /  3.  0.  0
     libswscale      4.  0.100 /  4.  0.100
     libswresample   2.  0.101 /  2.  0.101
     libpostproc    54.  0.100 / 54.  0.100
    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '1.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 512
       compatible_brands: isomiso2avc1mp41
       encoder         : Lavf57.25.100
     Duration: 00:00:08.34, start: 0.023220, bitrate: 4293 kb/s
       Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720, 4161 kb/s, 60 fps, 60 tbr, 15360 tbn, 120 tbc (default)
       Metadata:
         handler_name    : VideoHandler
       Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 129 kb/s (default)
       Metadata:
         handler_name    : SoundHandler
    [Parsed_frei0r_0 @ 0x7f8938f003c0] Could not find module 'perspective'.
    [AVFilterGraph @ 0x7f8938f00160] Error initializing filter 'frei0r' with args 'perspective'
    Error initializing complex filters.
    Invalid argument

    I’ve run out of ideas to try next, what am I missing ? Any help would be greatly appreciated.

  • ffmpeg compilation error in windows 10 x64 for Visual Studio 2015 CE

    12 avril 2016, par Anqush

    So i was trying to use FFmpegInterop for win10 UWP application. And followed the specification given on https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT.

    here is some environment information :

    VS2015 Community Edition with 10.0.10240.0 SDK

    OS : Windows 10 Enterprise x64

    PATH were set to:Program Files (x86)/Microsoft Visual Studio 14.0/VC/BIN/x64_ARM

    So when i did this in msys2_shell.bat

    ../../../configure \
    --toolchain=msvc \
    --disable-programs \
    --disable-d3d11va \
    --disable-dxva2 \
    --arch=x86_64 \
    --enable-shared \
    --enable-cross-compile \
    --target-os=win32 \
    --extra-cflags="-MD -DWINAPI_FAMILY=WINAPI_FAMILY_APP -D_WIN32_WINNT=0x0A00" \
    --extra-ldflags="-APPCONTAINER WindowsApp.lib" \
    --prefix=../../../Build/Windows10/x64

    I got a warning regarding some pkg file that can’t be found and may cause library detection issues.

    For then i ignored it. After that i entered

    make

    this started a series of processing in which there is a lot of possibly harmful warnings. Like :-

    c:\ffmpeginterop\ffmpeg\libavcodec\get_bits.h(307): warning C4101: 're_cache': unreferenced local variable
    CC libavformat/srtdec.o
    srtdec.c
    c:\ffmpeginterop\ffmpeg\libavutil\libm.h(438): warning C4211: nonstandard extension used: redefined extern to static
    c:\ffmpeginterop\ffmpeg\libavformat\subtitles.h(189): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data

    So my question is that. Is this dangerous to proceed with. Can you help me for i should proceed with my project without any worry or not ? And i would be gratefull if anyone can guide me to watc out for specific errors that this could generate.

    I know this is a lot to ask. But i would be gratefull.
    Thanks

    Edit : Now i cant run the samples included in the ffmpeginterop package. The sample project wont debug. saying these are out of date.

  • videoshow npm module not working fine

    14 avril 2016, par Anshul

    I have used videoshow NPM module for creating a video using images but it is not working fine for me it is running twice or thrice and creating multiple videos for same images sometimes. If i am changing the value of loop in the code to ’1’ it is running fine but the slide duration is only one second.

    Here is my code :-

    var images = [
       'public/images/1.png',
       'public/images/2.png',
       'public/images/3.png',
       'public/images/4.png',
       'public/images/5.png',
       'public/images/6.png',
       'public/images/7.png',
       'public/images/8.png',
       'public/images/9.png'
    ]

    var videoOptions = {
       fps: 25,
       loop: 3, // seconds
       transition: true,
       transitionDuration: 1, // seconds
       videoBitrate: 1024,
       videoCodec: 'libx264',
       size: '640x480',
       audioBitrate: '128k',
       audioChannels: 2,
       format: 'mp4'
    }

    var videoPath = 'public/video/test.mp4';

    videoshow(images, videoOptions)
    .audio('public/audio/1.mp3')
    .save(videoPath)
    .on('start', function (command) {
       console.log('ffmpeg process started:', command)
    })
    .on('error', function (err, stdout, stderr) {
       res.send({status : false, message: 'Something went wrong. Please try again.'});
       res.end();
       return;
    })
    .on('end', function (output) {
       res.send({status : true, message: ''});
       res.end();
       return;
    });