Recherche avancée

Médias (0)

Mot : - Tags -/serveur

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

Autres articles (46)

  • 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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (6659)

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

    


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

    


    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.

    


    the test MOV file is 186 MB in size.

    


    The system uploaded the file fine.

    


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

    


    Then it called streamio-ffmpeg's transcode method.

    


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

    


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

    


    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 ?

    


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

    


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

    


    enter image description here

    


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

    


    enter image description here

    


    Any help is appreciated. Thanks !

    


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