Recherche avancée

Médias (91)

Autres articles (55)

  • 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 ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

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

  • FFMPEG failing in AWS Lambda

    18 février 2019, par Zaid Amir

    I am trying to create a transcoding function for short videos. The function is hosted on AWS Lambda. The problem is that AWS lambda seems to be missing something that FFMPEG requires, at least according to Amazon.

    I contacted Amazon earlier and this is their response to the issue :

    We found that the FFMPEG operations require at least libx264 and an
    acc library, both of which will have dependencies of their own. To
    troubleshoot the issue it will involve diving deeper into the full
    dependency chain. We can see that it works in the Amazon Linux
    environment however, the environment is similar but not identical to
    the lambda environment. There can be some dependencies that exist in
    Amazon Linux but not in lambda environment as Lambda runs on the
    container. Here, as FFmpeg is a third party software, diving deeper
    into the dependency chain and verifying the version compatibilities is
    very hard to do. Unfortunately going further, this is bound to go into
    architecture and code support which is out of AWS Support scope 1. I
    hope you understand our limitations. However should FFmpeg support
    have any questions specific to the Lambda platform, please do let us
    know and we will be happy to assist. We will be in better position to
    investigate further once you receive an update from the FFmpeg support
    suggesting an issue from Lambda end.

    Upon AWS suggestion, I contacted FFMPEG on the developers mailing list, my message was rejected with the reason being that its more suited to ffmpeg users mailing list than developers. I sent an email to ’ffmpeg-user@ffmpeg.org’ a week ago and did not get any response yet.

    I then went and built a dynamically linked ffmpeg version making sure to package all libraries, checked ddl on each one, then made a small lambda function that looped over all binaries and ddled each one of them, compared that to the output I got from Amazon Linux and the same dependencies/versions exists on both lambda and the AWS Linux instance yet ffmpeg still fails on lambda.

    You can find a detailed log file here : https://www.datafilehost.com/d/6e5e21bb

    And this is a sample of the errors I’m getting, repeated across the entire log file :

    2018-08-14T12:27:10.874Z [h264 @ 0x65c2fc0] concealing 2628 DC, 2628
    AC, 2628 MV errors in P frame

    2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] channel element 2.11 is not
    allocated

    2018-08-14T12:27:10.874Z Error while decoding stream #0:1 : Invalid
    data found when processing input

    2018-08-14T12:27:10.874Z [h264 @ 0x67e86c0] Invalid NAL unit size
    (108085662 > 1649).

    2018-08-14T12:27:10.874Z [h264 @ 0x67e86c0] Error splitting the input
    into NAL units.

    2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] channel element 2.0 is not
    allocated

    2018-08-14T12:27:10.874Z Error while decoding stream #0:1 : Invalid
    data found when processing input

    2018-08-14T12:27:10.874Z [h264 @ 0x68189c0] Invalid NAL unit size
    (71106974 > 1085).

    2018-08-14T12:27:10.874Z [h264 @ 0x68189c0] Error splitting the input
    into NAL units.

    2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] Pulse tool not allowed in
    eight short sequence.

    This log is generated when trying to perform an HLS transcoding on this file : https://www.datafilehost.com/d/999a4492

    Note that the issue is not related to that file alone nor is it related to HLS, its general and happen on all videos and any ffmpeg command that tries to seek the stream, even tried extracting a single frame from a video using the simplest form possible for example : ffmpeg -ss 00:00:02 -I file.mp4 -vframes 1 -y output.jpg also fails with the same errors in the log file.

    Not sure how to debug this further. Tried enabling debug logs with ‘-loglevel debug’ but did not give me any extra info. Any help or suggestions

  • How to implement FFMEG library for android video streaming

    10 mai 2014, par Kabir

    I am trying to create online streaming video player in android.
    I am trying to compile the appunite/AndroidFFmpeg library for android application to play HLS videos online. I am using linux-ubuntu OS I also have set the NDK path.
    I have executed all command one by one given on the link :

    https://github.com/appunite/AndroidFFmpeg

    But when I executed the following script :

    ./build_android.sh

    I got the following error :

    abi-gcc —sysroot=/home/singsys-063/android-ndk-r9d/platforms/android-5/arch-arm/
    checking whether the C compiler works... no
    configure : error : in
    /home/singsys-063/AndroidFFmpeg/FFmpegLibrary/jni/vo-amrwbenc :
    configure : error : C compiler cannot create executables
    See config.log for more details

  • how to use the H264 video encoder with ffmpeg / opencv2 ?

    30 août 2023, par Vince

    I am on ubuntu 22.04.

    


    I installed ffmpeg with apt.

    


    I am creating a video from some image files using python/opencv2 (installed via pip)

    


    When I use :

    


    cv2.VideoWriter_fourcc(*"mp4v")


    


    the video is successfully created, but is not supported by firefox.

    


    I read online that the H264 encoder would be a better fit for web-browsers supports.

    


    ffmpeg -codecs | grep h264 


    


    shows :

    


    


    DEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders : h264 h264_v4l2m2m h264_qsv h264_cuvid ) (encoders : libx264 libx264rgb h264_nvenc h264_omx h264_qsv h264_v4l2m2m h264_vaapi nvenc nvenc_h264 )

    


    


    but

    


    cv2.VideoWriter_fourcc(*"h264")


    


    results in :

    


    


    OpenCV : FFMPEG : tag 0x34363268/'h264' is not supported with codec id 27 and format 'mp4 / MP4 (MPEG-4 Part 14)'

    


    


    I could not find online what was wrong (h264 is not installed, how to install it ? the 'fourcc' of h264 is not 'h264' ? I should not create a *.mp4 file ?)