Recherche avancée

Médias (1)

Mot : - Tags -/biomaping

Autres articles (36)

  • Liste des distributions compatibles

    26 avril 2011, par

    Le tableau ci-dessous correspond à la liste des distributions Linux compatible avec le script d’installation automatique de MediaSPIP. Nom de la distributionNom de la versionNuméro de version Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    Si vous souhaitez nous aider à améliorer cette liste, vous pouvez nous fournir un accès à une machine dont la distribution n’est pas citée ci-dessus ou nous envoyer le (...)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • Automated installation script of MediaSPIP

    25 avril 2011, par

    To overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
    You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
    The documentation of the use of this installation script is available here.
    The code of this (...)

Sur d’autres sites (3695)

  • Merge commit ’b34257eefd98cb768ea2f53a390b8684d51e689a’

    10 mai 2015, par Michael Niedermayer
    Merge commit ’b34257eefd98cb768ea2f53a390b8684d51e689a’
    

    * commit ’b34257eefd98cb768ea2f53a390b8684d51e689a’ :
    nut : Check chapter creation in decode_info_header

    Conflicts :
    libavformat/nutdec.c

    See : 3ff1af2b0db7132d5717be6395227a94c8abab07
    Merged-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavformat/nutdec.c
  • ffprobe or avprobe returning plain text errors in JSON output

    6 mai 2015, par Justin Jenkins

    I’m running avprobe to get stream infomation about a video in JSON ...

    avprobe -loglevel quiet -show_format -show_streams file.m4v -of json

    This is basically the exact same thing as ffprobe or ffmpeg -i (and I get the same error.)

    ffprobe -loglevel quiet -show_format -show_streams file.m4v -print_format json

    The command works most of the time ... however, on occation I’ll have a video that has an odd stream in it that is "unsupported" and I’ll get back something like this (abbreviated.)

    Unsupported codec with id 94213 for input stream 2
    {  "format" : {
       "filename" : "file.m4v",
       "nb_streams" : 3,
       "format_name" : "mov,mp4,m4a,3gp,3g2,mj2" ...

    When I run the command I get back JSON + an error in plain text, which makes the result invalid JSON and I have to "clean it up" later.

    I’m suppressing errors from the output -loglevel quiet but the error still show up.

    How can I tell avprobe/ffprobe to not show this error and hence get back a proper JSON object ?


    Longer Output Examples

    ffprobe, from source, MacOS

    ffprobe version 0.9.1-subsplash, Copyright (c) 2007-2012 the FFmpeg developers
     built on Feb  5 2012 01:35:36 with gcc 4.2.1 (Apple Inc. build 5664)
     configuration: --prefix=/Volumes/Ramdisk/sw --as=yasm --extra-version=subsplash --disable-shared --enable-static --disable-ffplay --disable-ffserver --enable-gpl --enable-pthreads --enable-version3 --enable-libspeex --enable-libvpx --disable-decoder=libvpx --enable-libmp3lame --enable-libfaac --enable-libvorbis --enable-libtheora --enable-libx264 --enable-avfilter --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-filters --arch=x86_64 --enable-runtime-cpudetect --enable-nonfree
     libavutil    51. 32. 0 / 51. 32. 0
     libavcodec   53. 42. 4 / 53. 42. 4
     libavformat  53. 24. 2 / 53. 24. 2
     libavdevice  53.  4. 0 / 53.  4. 0
     libavfilter   2. 53. 0 /  2. 53. 0
     libswscale    2.  1. 0 /  2.  1. 0
     libpostproc  51.  2. 0 / 51.  2. 0
    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'file.m4v':
     Metadata:
       major_brand     : mp42
       minor_version   : 0
       compatible_brands: mp42isomavc1
       creation_time   : 2012-01-01 06:38:43
       encoder         : HandBrake 0.9.5 2011010300
     Duration: 00:30:47.53, start: 0.000000, bitrate: 1558 kb/s
       Chapter #0.0: start -0.066733, end 17.784433
       Metadata:
         title           : Chapter  1

    ...

       Stream #0:2(und): Subtitle: mov_text (text / 0x74786574)
       Metadata:
         creation_time   : 2012-01-01 06:38:43
         handler_name    :
    Unsupported codec with id 94213 for input stream 2
    {

    ...

    avprobe, from source, Ubuntu Linux

    avprobe version 10_alpha1-6:10~~git20130307.4be368b-1~quantal1, Copyright (c) 2007-2013 the Libav developers
     built on Mar  7 2013 22:12:44 with gcc 4.7 (Ubuntu/Linaro 4.7.2-2ubuntu1)
    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'file.m4v':
     Metadata:
       major_brand     : mp42
       minor_version   : 0
       compatible_brands: mp42isomavc1
       creation_time   : 2012-01-01 06:38:43
       encoder         : HandBrake 0.9.5 2011010300
     Duration: 00:30:47.53, start: 0.000000, bitrate: 1558 kb/s
       Chapter #0.0: start -0.066733, end 17.784433
       Metadata:
         title           : Chapter  1

    ...

       Stream #0.2(und): Subtitle: text / 0x74786574
       Metadata:
         creation_time   : 2012-01-01 06:38:43
    Unsupported codec with id 94213 for input stream 2
    {

    ...
  • Debugging an MP4 opened by VLC but not by ffplay

    15 mai 2017, par MaMazav

    I’m writing a code which creates MP4 files. To check it I’ve created an MP4 file.

    The file is played correctly by VLC and Firefox, but not by ffplay or by Chrome. I guess the file contains error which VLC can cope with but more aggressive MP4 reader cannot.

    I’ve thought about repairing the file and check what are the differences to fix my code. However I tried some programs to repair MP4 files, without success until now.

    Can someone reccommend another way to debug the problem, or a good tool to fix MP4 files ? The file is a fragmented MP4 contains both the init section (ftyp, moov boxes) and one fragment section (moof and empty sidx).

    Here is the video file :

    https://www.dropbox.com/s/rojxzvkfxfj31u8/400k00001-3_serialized.mp4?dl=0

    EDIT : It doesn’t work also in Firefox, when using Media Source Extensions like in this example :
    http://people.mozilla.org/ jyavenard/tests/mse_mp4/paper.html

    (don’t forget to enable MSE on Firefox, as explained here :
    http://www.linuxveda.com/2015/04/02/enable-mse-native-html5-support-firefox-linux/)

    EDIT2 : In chrome ://media-internals, I see the following error with the above example :
    Append : stream parsing failed. Data size=131072 append_window_start=0 append_window_end=inf

    (Change the URL to be the file and change the codec to be ’avc1.4d401f’ instead of ’avc1.64000d,mp4a.40.2’).