Recherche avancée

Médias (91)

Autres articles (53)

  • 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

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

Sur d’autres sites (8707)

  • AWS Rekognition error : Chunk video failed

    14 juin 2022, par Stefano Leone

    I'm using and launching Amazon Rekognition on my videos uploaded into my S3 with python. Every video is converted with FFMPEG with AAC Audio Codec and H264 Video Codec and then given to Rekognition. Videos are always fine, the problem is that only 60-70% of videos are processed successfully, while the rest of videos goes into error. In particular, inside the JSON returned from Rekognition :

    


    {&#x27;JobId&#x27;: &#x27;<id of="of" my="my" job="job">&#x27;, &#x27;Status&#x27;: &#x27;FAILED&#x27;, &#x27;API&#x27;: &#x27;StartFaceDetection&#x27;, &#x27;Message&#x27;: &#x27;Chunk video failed: Only 1 I-frames found in video&#x27;, &#x27;Timestamp&#x27;: 1655118632996, &#x27;Video&#x27;: {&#x27;S3ObjectName&#x27;: &#x27;<my video="video" inside="inside" s3="s3">&#x27;, &#x27;S3Bucket&#x27;: &#x27;<my s3="s3">&#x27;}, &#x27;ErrorCode&#x27;: &#x27;VideoNotDecodable&#x27;}&#xA;</my></my></id>

    &#xA;

    As you can see, I get an error "Chunk video failed: only 1 I-Frames found in video". Honestly I don't know what is that, but the fact that I convert every video in the same way, but Rekognition fails only with some, makes me crazy. Googling was not helpful, hope you can tell me what's wrong.

    &#xA;

  • Thumbnails from S3 Videos using FFMPEG - "No such file or directory : '/bin/ffmpeg'"

    28 juin 2022, par Nico

    I am trying to generate thumbnails from videos in an S3 bucket every x frames by following this documentation : https://aws.amazon.com/blogs/media/processing-user-generated-content-using-aws-lambda-and-ffmpeg/

    &#xA;

    I am at the point where I'm testing the Lambda code provided in the documentation, but receive this error in CloudWatch Logs :

    &#xA;

    enter image description here

    &#xA;

    Here is the portion of the Lambda code associated with this error :

    &#xA;

    enter image description here

    &#xA;

    Any help is appreciated. Thanks !

    &#xA;

  • FFMPEG on Heroku exceeds memory quota in testing

    5 juillet 2022, par Patrick Vellia

    After following this tutorial, and getting it to work locally on my own development environment, before really getting my hands dirty and working deeper on my own project implementation, I decided to push it up to Heroku to test in a staging environment.

    &#xA;

    I had to have Heroku add the FFMPEG build-pack and turn on the Redis Server for ActionCable to work.

    &#xA;

    I didn't link the staging to a cloud storage bucket on Google or Amazon yet, just allowed it to upload directly to the dymo disk for testing. So it would go into the storage directory as it would in development for now.

    &#xA;

    the test MOV file is 186 MB in size.

    &#xA;

    The system uploaded the file fine.

    &#xA;

    According to the logs, it then copied the file from storage to tmp as the tutorial has us do.

    &#xA;

    Then it called streamio-ffmpeg's transcode method.

    &#xA;

    At this point, Heroku forcibly kills the dymo because it far exceeds the memory quota.

    &#xA;

    As this is a test environment, it's only on the free tier of Heroku.

    &#xA;

    I'm thinking I won't be able to directly process video projects on Heroku itself, unless I'm wrong ? Would it be better to call an API like Cloud Functions or Amazon Lambda, or spin up a Compute Engine long enough to process the FFMPEG command ?

    &#xA;