Recherche avancée

Médias (1)

Mot : - Tags -/biographie

Autres articles (90)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, 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 (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (7692)

  • vc-1 : Optimise parser (with special attention to ARM)

    23 avril 2014, par Ben Avison
    vc-1 : Optimise parser (with special attention to ARM)
    

    The previous implementation of the parser made four passes over each input
    buffer (reduced to two if the container format already guaranteed the input
    buffer corresponded to frames, such as with MKV). But these buffers are
    often 200K in size, certainly enough to flush the data out of L1 cache, and
    for many CPUs, all the way out to main memory. The passes were :

    1) locate frame boundaries (not needed for MKV etc)
    2) copy the data into a contiguous block (not needed for MKV etc)
    3) locate the start codes within each frame
    4) unescape the data between start codes

    After this, the unescaped data was parsed to extract certain header fields,
    but because the unescape operation was so large, this was usually also
    effectively operating on uncached memory. Most of the unescaped data was
    simply thrown away and never processed further. Only step 2 - because it
    used memcpy - was using prefetch, making things even worse.

    This patch reorganises these steps so that, aside from the copying, the
    operations are performed in parallel, maximising cache utilisation. No more
    than the worst-case number of bytes needed for header parsing is unescaped.
    Most of the data is, in practice, only read in order to search for a start
    code, for which optimised implementations already existed in the H264 codec
    (notably the ARM version uses prefetch, so we end up doing both remaining
    passes at maximum speed). For MKV files, we know when we’ve found the last
    start code of interest in a given frame, so we are able to avoid doing even
    that one remaining pass for most of the buffer.

    In some use-cases (such as the Raspberry Pi) video decode is handled by the
    GPU, but the entire elementary stream is still fed through the parser to
    pick out certain elements of the header which are necessary to manage the
    decode process. As you might expect, in these cases, the performance of the
    parser is significant.

    To measure parser performance, I used the same VC-1 elementary stream in
    either an MPEG-2 transport stream or a MKV file, and fed it through ffmpeg
    with -c:v copy -c:a copy -f null. These are the gperftools counts for
    those streams, both filtered to only include vc1_parse() and its callees,
    and unfiltered (to include the whole binary). Lower numbers are better :

    Before After
    File Filtered Mean StdDev Mean StdDev Confidence Change
    M2TS No 861.7 8.2 650.5 8.1 100.0% +32.5%
    MKV No 868.9 7.4 731.7 9.0 100.0% +18.8%
    M2TS Yes 250.0 11.2 27.2 3.4 100.0% +817.9%
    MKV Yes 149.0 12.8 1.7 0.8 100.0% +8526.3%

    Yes, that last case shows vc1_parse() running 86 times faster ! The M2TS
    case does show a larger absolute improvement though, since it was worse
    to begin with.

    This patch has been tested with the FATE suite (albeit on x86 for speed).

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavcodec/vc1_parser.c
  • Batch or Bulk Combining jpg with audio files ?

    2 octobre 2014, par John Maker

    I want to combine batch jpg with audio files ?
    example : I have a folder with 100 .jpg files & 100 .mp3 files in it.
    if 1st jpg file is dog.jpg then corresponding audio file is dog.mp3,
    2nd file is cat.jpg then there will be a audio file in same folder naming cat.mp3

    okay now coming to point. i want to Batch combine jpg with audio to produce video file like dog.mp4 , cat.mp4 etc. as i have described in the example. could anybody suggest me a better method ??
    can i use ffmpeg ?? then what is command ?

    For (1 image + 1 audio file = 1 video) case i know the answer its here : ffmpeg : 1 image + 1 audio file = 1 video

    I have a windows system with ffmpeg installed.
    thank you in advance for answer.

  • Combining voices while considering their start time

    21 juillet 2023, par user3405291

    Combine voices and add them to a video

    &#xA;

    I have this FFMPEG command to :

    &#xA;

      &#xA;
    1. Remove current video audio.
    2. &#xA;

    3. Combine some voices and add them to the video.
    4. &#xA;

    &#xA;

    ffmpeg -i vid.mp4 -i voice1.mp3 -i voice2.mp3 -filter_complex "[1:a] [2:a] amix=inputs=2:duration=longest:dropout_transition=0" -c:v copy -an vid.mkv&#xA;

    &#xA;

    The above command works great.

    &#xA;

    Each voice has a start time

    &#xA;

    I have a new requirement. Each voice should start at its own specific start time. Like :

    &#xA;

      &#xA;
    1. Voice 1 starts at 2 sec of the video.
    2. &#xA;

    3. Voice 2 starts at 1 sec of the video.
    4. &#xA;

    &#xA;

    How can I modify my FFMPEG command so that each voice would be at its own proper start time ?

    &#xA;