Recherche avancée

Médias (0)

Mot : - Tags -/clipboard

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (42)

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

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

  • How to use ffmpeg with h.265 (or h.264) codec ?

    6 octobre 2022, par randomuser1

    Normally I start recording the camera image with the command :

    



    ffmpeg -y -f vfwcap -r 25 -i 0 OUT.mp4

    



    but I'm not sure which coded do I use in here (I'm just beginning my adventure with ffmpeg), however I found on this webpage this command :

    



    ffmpeg -i INPUT -c:a copy -x265-params crf=25 OUT.mov

    



    But when I run it - I get the following error :
INPUT: No such file or directory"

    



    I changed the INPUT word above also to 0, so the command is

    



    ffmpeg -i 0 -c:a copy -x265-params crf=25 OUT.mov,
but error stays similar (0: no such file or directory).
How can I grab the camera image and save it to a file while using the H.265 ?

    


  • Adding mp3 metadata with space in ffmpeg using bash [duplicate]

    15 septembre 2019, par ctrlnot

    This question already has an answer here :

    I have this bash script on downloading youtube videos then convert it to mp3 using youtube-dl and ffmpeg.

    #!/bin/bash

    ytlink=""
    outputFileName=""
    title=""
    artist=""
    album=""

    while getopts l:o:t:r:b: flag; do
     case "${flag}" in
       l) ytlink="${OPTARG}";;
       o) outputFileName="${OPTARG}";;
       t) title="${OPTARG}";;
       r) artist="${OPTARG}";;
       b) album="${OPTARG}";;
     esac
    done

    youtube-dl "$ytlink" --add-metadata --extract-audio --audio-format mp3 --output "temp.%(ext)s"

    tempFilename="temp.mp3"
    outputFileName="$outputFileName.mp3"

    args+=("-i" "$tempFilename" "-metadata" "title='$title'" "-metadata" "artist='$artist'" "-metadata" "album='$album'" "-metadata" "comment=Source:$ytlink")
    ffmpeg -loglevel debug ${args[@]} -acodec copy "$outputFileName"
    rm "$tempFilename"

    This script is fine if I have one word title/artist/album. However, if I have a space, ffmpeg interprets each word before space as another parameter. This is how I use this on command line :

    ./yttomp3.sh -l "https://www.youtube.com/watch?v=KwQnSHAilOQ" -o "Lee - Autumn Day" -t "Autumn Day" -r "Lee" -b "(Free) Lo-fi Type Beat - Autumn Day"

    The debug output of ffmpeg :

    Splitting the commandline.
    Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
    Reading option '-i' ... matched as input url with argument 'temp.mp3'.
    Reading option '-metadata' ... matched as option 'metadata' (add metadata) with argument 'title='Autumn'.
    Reading option 'Day'' ... matched as output url.
    Reading option '-metadata' ... matched as option 'metadata' (add metadata) with argument 'artist='Lee''.
    Reading option '-metadata' ... matched as option 'metadata' (add metadata) with argument 'album='(Free)'.
    Reading option 'Lo-fi' ... matched as output url.
    Reading option 'Type' ... matched as output url.
    Reading option 'Beat' ... matched as output url.
    Reading option '-' ... matched as output url.
    Reading option 'Autumn' ... matched as output url.
    Reading option 'Day'' ... matched as output url.
    Reading option '-metadata' ... matched as option 'metadata' (add metadata) with argument 'comment=Source:https://www.youtube.com/watch?v=KwQnSHAilOQ'.
    Reading option '-acodec' ... matched as option 'acodec' (force audio codec ('copy' to copy stream)) with argument 'copy'.
    Reading option 'Lee - Autumn Day.mp3' ... matched as output url.
    Finished splitting the commandline.

    I tried enclosing the arguments to quotes on the script but it’s still not working. How should I deal with this ? Thanks.

  • png_parser : Fix parsing on big endian

    18 décembre 2013, par Martin Storsjö
    png_parser : Fix parsing on big endian
    

    Since pc.state is populated by shifting in from the end of the
    32 bit word, the content within pc.state is already in native endian
    and should not be read with the AV_RL,B functions.

    This was already done correctly for state64 above.

    This fixes the fate-corepng test on big endian.

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DBH] libavcodec/png_parser.c