Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (111)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Script d’installation automatique de MediaSPIP

    25 avril 2011, par

    Afin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
    Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
    La documentation de l’utilisation du script d’installation (...)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

Sur d’autres sites (11020)

  • dnxhddec : decode and use interlace mb flag

    25 septembre 2015, par Christophe Gisquet
    dnxhddec : decode and use interlace mb flag
    

    This bit is 1 in some samples, and seems to coincide with interlaced
    mbs and CID1260. 2008 specs do not know about it, and maintain qscale
    is 11 bits. This looks oversized, but may help larger bitdepths.

    Currently, it leads to an obviously incorrect qscale value, meaning
    its syntax is shifted by 1. However, reading 11 bits also leads to
    obviously incorrect decoding : qscale seems to be 10 bits.

    However, as most profiles still have 11bits qscale, the feature is
    restricted to the CID1260 profile.

    The encoder writes 12 bits of syntax, last and first bits always 0,
    which is now somewhat inconsistent with the decoder, but ends up with
    the same effect (progressive + reserved bit).

    Partially fixes ticket #4876.

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/dnxhddec.c
  • lavc/vaapi_decode : add missing flag when picking best pixel format

    5 août 2022, par Philip Langdale
    lavc/vaapi_decode : add missing flag when picking best pixel format
    

    vaapi_decode_find_best_format currently does not set the
    VA_SURFACE_ATTRIB_SETTABLE flag on the pixel format attribute that it
    returns.

    Without this flag, the attribute will be ignored by vaCreateSurfaces,
    meaning that the driver's default logic for picking a pixel format will
    kick in.

    So far, this hasn't produced visible problems, but when trying to
    decode 4:4:4 content, at least on Intel, the driver will pick the
    444P planar format, even though the decoder can only return the AYUV
    packed format.

    The hwcontext_vaapi code that sets surface attributes when picking
    formats does not have this bug.

    Applications may use their own logic for finding the best format, and
    so may not hit this bug. eg : mpv is unaffected.

    • [DH] libavcodec/vaapi_decode.c
  • AWS Lambda. Error=20 (Not a directory) when moving FFmpeg to /tmp

    18 novembre 2017, par Omar Riaz

    I am using the ffmpeg-cli-wrapper to run FFmpeg from an application I upload onto AWS lambda. I was initially getting the

    error=13 Permission Denied

    when trying to call it via the wrappers ProcessBuilder. My inital solution was to chmod 755 ffmpeg before uploading, but it didn’t help.

    For information, my FFmpeg and ffprobe files are located in the following classpath : static/ffmpeg/ffmpeg and static/ffmpeg/ffprobe. They are also statically linked.

    AWS Lambda permission denied when trying to use ffmpeg

    I’ve tried to follow the instructions given in the example above, but when I try to perform either mv or cp command :Runtime.exec("mv " + pathToFFmpeg + " /tmp"), I get the

    error=20, Not a directory

    error.

    I know that I have the correct path for FFmpeg because the following command mv *pathToFFmpeg* *an arbitrary name* runs without error, meaning that the file is there and so the mv command just renames it as it’s supposed to do.