Recherche avancée

Médias (1)

Mot : - Tags -/bug

Autres articles (58)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • 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

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (11198)

  • Is there a way to crop a video given a videoURL in node js ?

    30 mars 2021, par Radespy

    I’m building an electron-react app and need to crop [x, y, width, height] a video in the main process.

    


    The video URL and buffer have been generated in a react rendering component using mediaStream / mediaRecorder and a URL / buffer generated in the render process using URL.createObjectURL.

    


    I need to crop the video buffer directly (i.e. select a region of interest within the video) without having to download a file.

    


    I would then like to create a buffer from the cropped video to save in MongoDB as a base64 encoded string.

    


    I’ve looked at fluent-ffmpeg but this doesn’t seem to work with a URL or buffer and requires a path to a downloaded video file.

    


    Does anyone know of a way to do this ?

    


    Many thanks

    


  • InvalidArgumentException : Missing required client configuration options Laravel + FFmpeg + ubuntu 20 + Lamp

    9 août 2020, par Ahmed Al-Rayan

    I have an upload site on a Linux VPS server, Ubuntu, the new version, which is used by Laravel and the packaged fmpeg for the upload client

    


    A problem appears to me that I will attach, but I explain the type of problem. When I upload a video, the video is supposed to be uploaded, and then it goes to the processing, but times it raises and stops, and the error appears 500 times, it is raised and goes to treatment, but it stops here and the error appears to me that I will attach it and it is a problem in the country and does not match the information please Thank you for help

    


    InvalidArgumentException: Missing required client configuration options:   region: (string)    

A "region" configuration value is required for the "s3" service   (e.g., "us-west-2"). A list of available public regions and endpoints can be   found at http://docs.aws.amazon.com/general/latest/gr/rande.html.
in /var/www/html/vendor/aws/aws-sdk-php/src/ClientResolver.php:399 


Stack trace: #0 /var/www/html/vendor/aws/aws-sdk-php/src/ClientResolver.php(295): Aws\ClientResolver->throwRequired() #1 /var/www/html/vendor/aws/aws-sdk-php/src/AwsClient.php(195): Aws\ClientResolver->resolve() #2 /var/www/html/vendor/aws/aws-sdk-php/src/S3/S3Client.php(327): Aws\AwsClient->__construct() #3 /var/www/html/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemManager.php(212): Aws\S3\S3Client->__construct() #4 /var/www/html/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemManager.php(129): Illuminate\Filesystem\FilesystemManager->createS3Driver() #5 /var/www/html/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemManager.php(101): Illuminate\Filesystem\FilesystemManager->resolve() #6 /var/www/html/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemManager.php(78): Illuminate\Filesystem\FilesystemManager->get() #7 /var/www/html/vendor/pbmedia/laravel-ffmpeg/src/FFMpeg.php(66): Illuminate\Filesystem\FilesystemManager->disk() #8 /var/www/html/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(261): Pbmedia\LaravelFFMpeg\FFMpeg->fromDisk() #9 /var/www/html/app/Jobs/StreamMovie.php(53): Illuminate\Support\Facades\Facade::__callStatic() #10 [internal function]: App\Jobs\StreamMovie->handle() #11 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(32): call_user_func_array() #12 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Util.php(36): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}() #13 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(90): Illuminate\Container\Util::unwrapIfClosure() #14InvalidArgumentException: Missing required client configuration options


    


  • Optimizing x264 based remote desktop by dirty regions

    17 novembre 2016, par useprxf

    I was using x264 to achieve remote desktop, but had some problems on handling P_SKIP detection.

    Dirty regions indicate changed areas. For those 16x16 macroblocks which don’t intersect any dirty region, I would like to encode them as P_SKIP macroblocks.

    I tried to add the following code into x264_macroblock_prob_skip_internal function :

    if (! h->isdirty[h->mb.i_mb_x][h->mb.i_mb_y])       // isdirty is a 2-dim array indicating dirty macroblocks
    
    return 1;

    but there is almost no speed-up. I think it may be the information preparation for the macroblock analysis that take influence.

    How to speed up x264 by considering dirty regions ?

Navigation