Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (47)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (9612)

  • Encoder (codec mp3) not found for output stream #0:0 , ffmpeg

    14 juillet 2014, par AreKay

    i am running ffmpeg on mac os x.
    while extracting audio file from a video i am getting an error as Encoder (codec mp3) not found for output stream #0:0

    this question was already asked but that was for ubuntu and i did try (using macports) port install libavcodec-extras-53 but it showed an error as libavcodec-extras-53 was not found.

    this was what came in terminal.

    Rajaths-MacBook-Pro:desktop RK$ ffmpeg -i 1.mp4 3.mp3<br />
    ffmpeg version N-64663-ga65d6e1 Copyright (c) 2000-2014 the FFmpeg developers<br />
     built on Jul 15 2014 02:20:47 with Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM    3.4svn)<br />
     configuration:<br />
     libavutil      52. 92.100 / 52. 92.100<br />
     libavcodec     55. 69.100 / 55. 69.100<br />
     libavformat    55. 47.100 / 55. 47.100<br />
     libavdevice    55. 13.102 / 55. 13.102<br />
     libavfilter     4. 10.100 /  4. 10.100<br />
     libswscale      2.  6.100 /  2.  6.100<br />
     libswresample   0. 19.100 /  0. 19.100<br />
    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '1.mp4':<br />
     Metadata:<br />
       major_brand     : isom<br />
       minor_version   : 512<br />
       compatible_brands: isomiso2mp41<br />
       encoder         : Lavf55.47.100
     Duration: 00:00:39.05, start: 0.020227, bitrate: 408 kb/s<br />
       Stream #0:0(und): Video: mpeg4 (Simple Profile) (mp4v / 0x7634706D), yuv420p, 640x360 [SAR 1:1 DAR 16:9], 274 kb/s, 30 fps, 30 tbr, 15360 tbn, 30 tbc (default)<br />
       Metadata:<br />
         handler_name    : VideoHandler<br />
       Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 127 kb/s        (default)<br />
       Metadata:<br />
         handler_name    : SoundHandler<br />
    Output #0, mp3, to '3.mp3':<br />
     Metadata:<br />
       major_brand     : isom<br />
       minor_version   : 512<br />
       compatible_brands: isomiso2mp41<br />
       encoder         : Lavf55.47.100<br />
       Stream #0:0(und): Audio: mp3, 0 channels, 128 kb/s (default)<br />
       Metadata:<br />
         handler_name    : SoundHandler<br />
    Stream mapping:<br />
     Stream #0:1 -> #0:0 (aac (native) -> ? (?))<br />
    Encoder (codec mp3) not found for output stream #0:0

    any help would be appreciated.

  • Progress with rtc.io

    12 août 2014, par silvia

    At the end of July, I gave a presentation about WebRTC and rtc.io at the WDCNZ Web Dev Conference in beautiful Wellington, NZ.

    webrtc_talk

    Putting that talk together reminded me about how far we have come in the last year both with the progress of WebRTC, its standards and browser implementations, as well as with our own small team at NICTA and our rtc.io WebRTC toolbox.

    WDCNZ presentation page5

    One of the most exciting opportunities is still under-exploited : the data channel. When I talked about the above slide and pointed out Bananabread, PeerCDN, Copay, PubNub and also later WebTorrent, that’s where I really started to get Web Developers excited about WebRTC. They can totally see the shift in paradigm to peer-to-peer applications away from the Server-based architecture of the current Web.

    Many were also excited to learn more about rtc.io, our own npm nodules based approach to a JavaScript API for WebRTC.

    rtcio_modules

    We believe that the World of JavaScript has reached a critical stage where we can no longer code by copy-and-paste of JavaScript snippets from all over the Web universe. We need a more structured module reuse approach to JavaScript. Node with JavaScript on the back end really only motivated this development. However, we’ve needed it for a long time on the front end, too. One big library (jquery anyone ?) that does everything that anyone could ever need on the front-end isn’t going to work any longer with the amount of functionality that we now expect Web applications to support. Just look at the insane growth of npm compared to other module collections :

    Packages per day across popular platforms (Shamelessly copied from : http://blog.nodejitsu.com/npm-innovation-through-modularity/)

    For those that – like myself – found it difficult to understand how to tap into the sheer power of npm modules as a font end developer, simply use browserify. npm modules are prepared following the CommonJS module definition spec. Browserify works natively with that and “compiles” all the dependencies of a npm modules into a single bundle.js file that you can use on the front end through a script tag as you would in plain HTML. You can learn more about browserify and module definitions and how to use browserify.

    For those of you not quite ready to dive in with browserify we have prepared prepared the rtc module, which exposes the most commonly used packages of rtc.io through an “RTC” object from a browserified JavaScript file. You can also directly download the JavaScript file from GitHub.

    Using rtc.io rtc JS library
    Using rtc.io rtc JS library

    So, I hope you enjoy rtc.io and I hope you enjoy my slides and large collection of interesting links inside the deck, and of course : enjoy WebRTC ! Thanks to Damon, JEeff, Cathy, Pete and Nathan – you’re an awesome team !

    On a side note, I was really excited to meet the author of browserify, James Halliday (@substack) at WDCNZ, whose talk on “building your own tools” seemed to take me back to the times where everything was done on the command-line. I think James is using Node and the Web in a way that would appeal to a Linux Kernel developer. Fascinating !!

  • file.mov : No such file or directory (Converting .mov to mp4)

    10 août 2014, par Dena

    I am trying to convert .mov files over to mp4 using ffmpeg however, I keep getting the error below within my terminal. Any ideas why ? I am new to rails so any help is appreciated. Thanks.

    Error

    Denas-MacBook-Pro:desktop Dena$ ffmpeg -i file.mov newfile.mp4
    **ffmpeg version 2.3.1** Copyright (c) 2000-2014 the FFmpeg developers
     built on Aug  7 2014 16:08:43 with Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
     configuration: --prefix=/usr/local/Cellar/ffmpeg/2.3.1 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --enable-avresample --enable-vda --cc=clang --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-libmp3lame --enable-libxvid --enable-libfreetype --enable-libtheora --enable-libvorbis --enable-libvpx --enable-librtmp --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-aacenc --enable-libass --enable-ffplay --enable-libspeex --enable-libschroedinger --enable-libfdk-aac --enable-libopus --enable-frei0r --enable-libopenjpeg --disable-decoder=jpeg2000 --extra-cflags='-I/usr/local/Cellar/openjpeg/1.5.1_1/include/openjpeg-1.5 '
     libavutil      52. 92.100 / 52. 92.100
     libavcodec     55. 69.100 / 55. 69.100
     libavformat    55. 48.100 / 55. 48.100
     libavdevice    55. 13.102 / 55. 13.102
     libavfilter     4. 11.100 /  4. 11.100
     libavresample   1.  3.  0 /  1.  3.  0
     libswscale      2.  6.100 /  2.  6.100
     libswresample   0. 19.100 /  0. 19.100
     libpostproc    52.  3.100 / 52.  3.100
    file.mov: No such file or directory

    Path

    Denas-MacBook-Pro:desktop Dena$ which ffmpeg
    /usr/local/bin/ffmpeg

    Version

    Denas-MacBook-Pro:desktop Dena$ ffmpeg -version
    ffmpeg version 2.3.1 Copyright (c) 2000-2014 the FFmpeg developers
    built on Aug  7 2014 16:08:43 with Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
    configuration: --prefix=/usr/local/Cellar/ffmpeg/2.3.1 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --enable-avresample --enable-vda --cc=clang --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-libmp3lame --enable-libxvid --enable-libfreetype --enable-libtheora --enable-libvorbis --enable-libvpx --enable-librtmp --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-aacenc --enable-libass --enable-ffplay --enable-libspeex --enable-libschroedinger --enable-libfdk-aac --enable-libopus --enable-frei0r --enable-libopenjpeg --disable-decoder=jpeg2000 --extra-cflags='-I/usr/local/Cellar/openjpeg/1.5.1_1/include/openjpeg-1.5 '
    libavutil      52. 92.100 / 52. 92.100
    libavcodec     55. 69.100 / 55. 69.100
    libavformat    55. 48.100 / 55. 48.100
    libavdevice    55. 13.102 / 55. 13.102
    libavfilter     4. 11.100 /  4. 11.100
    libavresample   1.  3.  0 /  1.  3.  0
    libswscale      2.  6.100 /  2.  6.100
    libswresample   0. 19.100 /  0. 19.100
    libpostproc    52.  3.100 / 52.  3.100