Recherche avancée

Médias (3)

Mot : - Tags -/image

Autres articles (111)

  • 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

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (13854)

  • Piping cURL output to FFmpeg doesn't work with mp4 files

    8 novembre 2015, par Konstantin

    I would like to pipe cURL output to FFmpeg the following way in my Ruby script to strip off metadata, chapters and maybe set other metadata too in the future :

    #!/usr/bin/ruby
    url=ARGV[0]

    fname=url.split("/").last
    extension=File.extname(fname)
    options=""
    case extension
     when /mp4/i
       format="mp4"
       options=" -movflags frag_keyframe+empty_moov "
     when /avi/i
       format="avi"
     when /mkv/i
       format="matroska"
     when /wmv/i
       format="asf"
     else
       format="matroska"
    end

    cmd=%Q{ curl -b cookie-file.txt #{url} -L -o - | ffmpeg -y -i - -map 0:v -map 0:a -c:v copy -c:a:0 copy -map_metadata -1 -map_chapters -1 #{options} -f #{format} - | cat > #{fname} }

    system cmd

    When the url (ARGV[0]) points to an .avi, .wmv or .mkv file the script do its job. However when it points to an .mp4 or .mov file it doesn’t work, because the input isn’t seekable and FFmpeg at first try to read the whole input. When url points to an mp4 file, output to stdout even doesn’t work, only when options " -movflags frag_keyframe+empty_moov " is used for the output format. Otherwise I got an error message : "muxer does not support non seekable output". Last cat command is needed because this command pipe will work in a CGI script, and will write its output to STDOUT with appropriate HTTP headers. What options should I use for the input pipe to make my script work with mp4 files too ?

  • aacenc : partially revert previous commits to set options via a profile

    17 octobre 2015, par Rostislav Pehlivanov
    aacenc : partially revert previous commits to set options via a profile
    

    It didn’t work out because of the exceptions that needed to be made
    for the "-1" cases and was overall more confusing that just manually
    checking and setting options for each profile.

    • [DH] libavcodec/aacenc.c
    • [DH] libavcodec/aacenc_utils.h
    • [DH] libavcodec/aacenctab.h
  • aacenc : add support for changing options based on a profile

    12 octobre 2015, par Rostislav Pehlivanov
    aacenc : add support for changing options based on a profile
    

    This commit adds the ability for a profile to set the default
    options, as well as for the user to override such options
    by simply stating them in the command line while still keeping
    the same profile, as long as those options are still permitted by
    the profile.

    Example : setting the profile to aac_low (the default) will turn
    PNS and IS on. They can be disabled by -aac_pns 0 and -aac_is 0,
    respectively. Turning on -aac_pred 1 will cause the profile to be
    elevated to aac_main, as long as no options forbidding aac_main
    have been entered (like AAC-LTP, which will be pushed soon).

    A useful feature is that by setting the profile to mpeg2_aac_low,
    all MPEG4 features will be disabled and if the user tries to enable
    them then the program will exit with an error. This profile is
    signalled with the same bitstream as aac_low (MPEG4) but some devices
    and decoders will fail if any MPEG4 features have been enabled.

    • [DH] libavcodec/aaccoder_twoloop.h
    • [DH] libavcodec/aacenc.c
    • [DH] libavcodec/aacenc.h
    • [DH] libavcodec/aacenc_utils.h
    • [DH] libavcodec/aacenctab.h