Recherche avancée

Médias (1)

Mot : - Tags -/Rennes

Autres articles (55)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • 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

Sur d’autres sites (8257)

  • avplay : Handle pixel aspect ratio properly

    6 juillet 2014, par Martin Storsjö
    avplay : Handle pixel aspect ratio properly
    

    This was broken (left half-implemented) in 354468fc12.

    CC : libav-stable@libav.org
    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] avplay.c
  • PyAV inconsistency when parsing packets from h264 frames

    3 avril 2022, par Shlomi Uziel

    When producing H.264 frames and decoding them using pyAV, packets are parsed from frames only when invoking the parse methods twice.

    &#xA;

    Consider the following test H.264 input, created using :

    &#xA;

    ffmpeg -f lavfi -i testsrc=duration=10:size=1280x720:rate=30 -f image2 -vcodec libx264 -bsf h264_mp4toannexb -force_key_frames source -x264-params keyint=1:scenecut=0 "frame-%4d.h264"

    &#xA;

    Now, using pyAV to parse the first frame :

    &#xA;

    import av&#xA;codec = av.CodecContext.create(&#x27;h264&#x27;, &#x27;r&#x27;)&#xA;with open(&#x27;/path/to/frame-0001.h264&#x27;, &#x27;rb&#x27;) as file_handler:&#xA;    chunk = file_handler.read()&#xA;    packets = codec.parse(chunk) # This line needs to be invoked twice to parse packets&#xA;

    &#xA;

    packets remain empty unless the last line is invoked again (packets = codec.parse(chunk))

    &#xA;

    Also, for different real life examples I cannot characterize, it seems that decoding frames from packets also require several decode invocations :

    &#xA;

    packet = packets[0]&#xA;frames = codec.decode(packet) # This line needs to be invoked 2-3 times to actually receive frames.&#xA;

    &#xA;

    Does anyone know anything about this incosistent behavior of pyAV ?

    &#xA;

    (Using Python 3.8.12 on macOS Monterey 12.3.1, ffmpeg 4.4.1, pyAV 9.0.2)

    &#xA;

  • How to make multiple ffmpeg commands run in parallel [duplicate]

    9 février, par Kim Mỹ

    I'm using the following ffmpeg command to compress video :

    &#xA;

    `nice -n 10 ${ffmpegPath} -i "${chunkPath}" -c:v libx264 -preset fast -crf 28 "${compressedPath}"`&#xA;

    &#xA;

    However, when I run two instances of ffmpeg of this command to achieve parallelism :

    &#xA;

    Either in two child processes within a single Node.js application or in two separate Node.js applications running at the same time, it seems only one command is processed, and the other is skipped.

    &#xA;

    I've noticed that 2 FFmpeg instances are loaded into RAM and both create a starting file for the final compressed video, they finish compression around the same time. However, the total processing time is effectively doubled compared to compressing a single video file alone, which only takes half the time.

    &#xA;

    I also try to pass the -threads argument but it produces same result.

    &#xA;