Recherche avancée

Médias (0)

Mot : - Tags -/objet éditorial

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

Autres articles (23)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

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

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

Sur d’autres sites (4344)

  • Simples loop to iterate over files and send them to ffmpeg

    25 octobre 2019, par user2752471

    I want to do a shell script that will iterate over several video files in a directory, send everyone of them to ffmpeg, that will then reencode each one, producing a reencoded file that will have the same name as the original, except with .avi extension instead .mkv or .mp4.

    I found a fairly simple script in another topic here on SO, tried to change it slightly to take into account the file extension and the destination directory.

    However my script only produces countless "anything : No such file or directory"

    Here is it :

    $ for f in $(find -type f -name *.mkv); do ffmpeg -n -i "$f" -c:v copy ".$f" ; done

    And these is the ffmpeg command that I usually use :

    ffmpeg -y -i  -vf scale=720:-2 -c:v mpeg4 -vtag xvid -b:v 969k -pass 1 -an -f avi /dev/null && ffmpeg -i -c:a libmp3lame -b:a 48k -ac 1 -vf scale=720:-2 -c:v mpeg4 -vtag xvid -b:v 969k -pass 2  .avi

    So I need to identify what is incorrect in the first script, that is considering each small word of the file’s name as a file, and then change it as to add all these ffmpeg parameters.

    Somethings that I do not understand in the script :

    1)Are the -type and f in find command necessary. From what I read of the documentation, all it does is to tell find that it shall look for normal files, something that seems irrelevant for my case. When I use find, I do : find starting dir -name filename. So do I have to keep it ?

    2)What -n means for ffmpeg ? I am currently without a man entry for ffmpeg. Is it necessary for my needs ?

    3)Do I need to have "" around $f ? What it does ?

    4)As far as I understand $ denotes a variable. But what the "f" after it does ? Do I need it ?

    5)The " ;" after the closing ")" and the ".$f" are necessary ? The first is used to indicate the end of the for loop,and the second the end of the ffmpeg command ?

    6)The "do" and the "does" are also necessary for the same motives behind the " ;"

    Here is my attempt of the ffmpeg part of the script. Please tell me what to change on it, as in the find part of it.

    do ffmpeg -n -y -i "$f.mkv" -vf scale=720:-2 -c:v mpeg4 -vtag xvid -b:v 969k -pass 1 -an -f avi /dev/null && ffmpeg -n -i "$f" -c:a libmp3lame -b:a 48k -ac 1 -vf scale=720:-2 -c:v mpeg4 -vtag xvid -b:v 969k -pass 2  ".$f.avi" ; done

    If I would like the script to also look for ".mp4" besides ".mkv" how I would need to change it ?

    Thanks for any input.

  • avcodec/mips : Improve hevc uni-w horiz mc msa functions

    9 octobre 2017, par Kaustubh Raste
    avcodec/mips : Improve hevc uni-w horiz mc msa functions
    

    Load the specific destination bytes instead of MSA load and pack.
    Pack the data to half word before clipping.
    Use immediate unsigned saturation for clip to max saving one vector register.

    Signed-off-by : Kaustubh Raste <kaustubh.raste@imgtec.com>
    Reviewed-by : Manojkumar Bhosale <Manojkumar.Bhosale@imgtec.com>
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/mips/hevc_macros_msa.h
    • [DH] libavcodec/mips/hevc_mc_uniw_msa.c
  • avformat/mvdec : read frame rate from data stream

    18 décembre 2021, par John-Paul Stewart
    avformat/mvdec : read frame rate from data stream
    

    Prior to this patch, for version 2 of the file format the frame rate was
    hard-coded at 15 fps. This uses the 64-bit floating-point value from
    the data stream, similar to what is already done for version 3 of the
    file format (around line 206).

    Signed-off-by : John-Paul Stewart <jpstewart@personalprojects.net>
    Reviewed-by : Peter Ross <pross@xvid.org>

    • [DH] libavformat/mvdec.c