Recherche avancée

Médias (1)

Mot : - Tags -/publishing

Autres articles (101)

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

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Mise à disposition des fichiers

    14 avril 2011, par

    Par défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
    Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
    Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)

Sur d’autres sites (8433)

  • Video encoded with ffmpeg not playing in Chrome

    15 décembre 2014, par Meep3D

    I’ve been trying just about every single permutation of options on ffmpeg to try to get a transcoded video to display on Chrome - OSX 39.0.2171.71 (64-bit) - so far nothing has worked.

    The settings I am currently using look like :

    /usr/local/Cellar/ffmpeg/2.4.3/bin/ffmpeg -i source.m4v -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -level 3.0 -preset slower -crf 23 -vf scale=640:360 target.mp4

    but I’ve tried various options from various other answers with no success.

    The video-js demo video works fine, so it must be possible somehow. Here’s a dump of the encoded video :

    *** General Parameters ***
    - Name:  test-1 (2).mp4
    - Container:  MP4 - QuickTime
    - Size:  3.45 MB
    - Duration:  32s 299ms
    - Bitrate:  856 Kbps

    *** Video Track Parameters ***
    - Format:  H.264/MPEG-4 AVC
    - Bitrate:  Max.: --- / Average: 721 Kbps / Min.: ---
    - Frame rate (fps):  Max.: --- / Average: 30.000 / Min.: ---
    - Encoding profile:  Baseline@L3.0
    - Image size:  640*360
    - Pixel Aspect Ratio:  Undefined
    - Display Aspect Ratio:  16:9
    - Interlacing:  Progressive

    *** First Audio Track Parameters ***
    - Format:  AAC - MPEG-4 audio
    - Bitrate:  128 Kbps
    - Resolution:  Undefined
    - Rate:  44.1 KHz
    - Channel(s):  2 (stereo)
    - Position:  Front: L R
  • Chrome struggles to play videos

    11 décembre 2017, par Cameron

    I have some video files I want to display on a webpage using the HTML5 video player. The videos were sent to me at 1920x1080 in H.254 MP4 format.

    Using FFMPEG I have converted them so I have a smaller Mp4 file, an OGV file, and a WebM file using the following commands :

    ffmpeg -i FILE.mp4 -vcodec h264 FILE.mp4

    ffmpeg -i FILE.mp4 -acodec libvorbis -vcodec libtheora -f ogv FILE.ogv

    ffmpeg -i FILE.mp4 -c:v libvpx -crf 10 -b:v 1M -c:a libvorbis FILE.webm

    And then the video is embedded into the page like so :

    <video preload="metadata" crossorigin="anonymous" poster="poster.jpg" controls="controls" playsinline="playsinline">
       <source src="FILE.webm" type="video/webm">
       <source src="FILE.ogv" type="video/ogv">
       <source src="FILE.mp4" type="video/mp4">
    </source></source></source></video>

    However when I click to play the video in Chrome, it stops after a few seconds and then if I click play again it restarts. If I right click and open the video in a new tab I just see a tiny player and not the video e.g.
    enter image description here

    The same happens for all three formats. But if I refresh the browser enough times I can get the MP4 file to show up in the new tab though it still suffers from the aforementioned bug of playing for a few seconds before failing.

    I have tested this in Firefox and Safari and it works fine ! In fact it even works in IE and Edge :D And I can also play the videos in a player on the machine itself... e.g. QuickTime.

    Any ideas why Chrome is acting this way ? Or any resolutions ? I’m seeing the same behaviour on Chrome for Windows and Mac. Is the way I have converted the videos using FFMPEG in anyway a cause that could affect Chrome but not other browsers ?

    Chrome version tested on : Version 63.0.3239.84 (Official Build) (64-bit)

    Output from ffprobe as per the comments on the one of the webm files :

    ffprobe version 3.4 Copyright (c) 2007-2017 the FFmpeg developers
     built with Apple LLVM version 7.3.0 (clang-703.0.31)
     configuration: --prefix=/usr/local/Cellar/ffmpeg/3.4 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-ffplay --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --enable-openssl --disable-lzma --enable-libopenjpeg --disable-decoder=jpeg2000 --extra-cflags=-I/usr/local/Cellar/openjpeg/2.3.0/include/openjpeg-2.3 --enable-nonfree
     libavutil      55. 78.100 / 55. 78.100
     libavcodec     57.107.100 / 57.107.100
     libavformat    57. 83.100 / 57. 83.100
     libavdevice    57. 10.100 / 57. 10.100
     libavfilter     6.107.100 /  6.107.100
     libavresample   3.  7.  0 /  3.  7.  0
     libswscale      4.  8.100 /  4.  8.100
     libswresample   2.  9.100 /  2.  9.100
     libpostproc    54.  7.100 / 54.  7.100
    Input #0, matroska,webm, from 'FILE.webm':
     Metadata:
       COMPATIBLE_BRANDS: mp42mp41
       MAJOR_BRAND     : mp42
       MINOR_VERSION   : 0
       ENCODER         : Lavf57.83.100
     Duration: 00:00:52.57, start: 0.000000, bitrate: 910 kb/s
       Stream #0:0(eng): Video: vp8, yuv420p(progressive), 1920x1080, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 1k tbn, 1k tbc (default)
       Metadata:
         HANDLER_NAME    : Alias Data Handler
         ENCODER         : Lavc57.107.100 libvpx
         DURATION        : 00:00:52.563000000
       Stream #0:1(eng): Audio: vorbis, 48000 Hz, stereo, fltp (default)
       Metadata:
         HANDLER_NAME    : Alias Data Handler
         ENCODER         : Lavc57.107.100 libvorbis
         DURATION        : 00:00:52.568000000
  • 1.3.8 release & fixed a bug where images were rendered at 0 width 0 height in latest versions of Chrome.

    21 juin 2010, par Jack Moore

    m README m colorbox/jquery.colorbox-min.js m colorbox/jquery.colorbox.js 1.3.8 release & fixed a bug where images were rendered at 0 width 0 height in latest versions of Chrome.