Recherche avancée

Médias (0)

Mot : - Tags -/xml-rpc

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

Autres articles (105)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Création définitive du canal

    12 mars 2010, par

    Lorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
    A la validation, vous recevez un email vous invitant donc à créer votre canal.
    Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
    A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...)

Sur d’autres sites (4510)

  • avcodec/hevcdec : apply H.274 film grain

    29 septembre 2021, par Niklas Haas
    avcodec/hevcdec : apply H.274 film grain
    

    Similar in spirit and design to 66845cffc3bbb, but slightly simpler due
    to the lack of interlaced frames in HEVC. See that commit for more
    details.

    For the seed value, since no specification for this appears to exist, I
    semi-arbitrarily decided to base it off the POC id alone, since there's
    no analog of the idr_pic_id in HEVC's I-frames. This design is stable
    across remuxes and seeks, but changes for adjacent frames with a period
    that's typically long enough not to be noticeable, which makes it
    satisfy all of the requirements that a film grain seed should have.

    Tested with and without threading, using a patch to insert film grain
    metadata artificially (for lack of real files containing film grain).

    • [DH] libavcodec/hevc_refs.c
    • [DH] libavcodec/hevcdec.c
    • [DH] libavcodec/hevcdec.h
  • Convert DTS to AC3 but only if there is no AC3 track already present in container

    24 mars, par Domagoj

    I have sound system that does not support DTS only AC3. I'm automating the process using bash that detects when movie was added to folder, downloads subtitles and converts audio track to AC3 using this command (one part of it) :

    


    ffmpeg -i "{{episode}}" -map 0:v -map 0:a:0 -map 0:a -map 0:s -c:v copy -c:a copy -c:s copy -c:a:0 ac3 -b:a:0 640k "{{directory}}"/{{episode_name}}temp2.mkv

    


    This works without issue and I end up with a .mkv file that contains original DTS audio track and newly created AC3 audio track. The issue is that some files already contain both AC3 and DTS tracks and in those cases I end up with two AC3 tracks and one DTS track. Another issue is that this command is triggered every time there is update to subtitles. So it's possible that the command will execute multiple times in a period of a few days and the container will have X number of the AC3 tracks.

    


    I need a way to detect if file already contains AC3 track before I initiate command from above, but I'm not sure what the command would be. Any help is appreciated !

    


  • AWS Lambda tmp memory limit with ffmpeg

    19 avril 2022, par Almaju

    I am using AWS Lambda to render videos using ffmpeg. It is a basic function that downloads external clips, merges those, then uploads the result to S3.

    


    This function needs to be able to scale quickly because I need to generate a lot of videos in a short time period.

    


    The problem is that I reach the /tmp disk limit of 512MB because the same lambda environment is reused by the different requests. I have increased that memory limit to temporarily solve the problem but it does not feel scalable.

    


    I have looked into EFS but the requirement to use a VPC and a NAT to have internet access sounds really heavy for my simple needs.

    


    Is there a way to output the result of ffmpeg directly in S3 (thus not needing the temporary folder) ? Or perhaps force to respawn a clean lambda environment if the memory is about to be full ?