
Recherche avancée
Médias (1)
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (37)
-
La sauvegarde automatique de canaux SPIP
1er avril 2010, parDans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...) -
Script d’installation automatique de MediaSPIP
25 avril 2011, parAfin 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 (...) -
Automated installation script of MediaSPIP
25 avril 2011, parTo overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
The documentation of the use of this installation script is available here.
The code of this (...)
Sur d’autres sites (6586)
-
Error : ffmpeg exited with code 1 on AWS Lambda
16 juin 2022, par Hassnain AlviI am using fluent-ffmpeg nodejs package to run ffmpeg for audio conversion on AWS Lambda. I am using this FFmpeg layer for lambda.
Here is my code


const bitrate64 = ffmpeg("file.mp3").audioBitrate('64k');
 bitrate64.outputOptions([
 '-preset slow',
 '-g 48',
 "-map", "0:0",
 '-hls_time 6',
 '-master_pl_name master.m3u8',
 '-hls_segment_filename 64k/fileSequence%d.ts'
 ])
 .output('./64k/prog_index.m3u8')
 .on('progress', function(progress) {
 console.log('Processing 64k bitrate: ' + progress.percent + '% done')
 }) 
 .on('end', function(err, stdout, stderr) {
 console.log('Finished processing 64k bitrate!')
 })
 .run() 



after running it via AWS lambda I get following error message


ERROR Uncaught Exception 
{
 "errorType": "Error",
 "errorMessage": "ffmpeg exited with code 1: Conversion failed!\n",
 "stack": [
 "Error: ffmpeg exited with code 1: Conversion failed!",
 "",
 " at ChildProcess.<anonymous> (/var/task/node_modules/fluent-ffmpeg/lib/processor.js:182:22)",
 " at ChildProcess.emit (events.js:198:13)",
 " at ChildProcess.EventEmitter.emit (domain.js:448:20)",
 " at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)"
 ]
}
</anonymous>


I don't get any more info so I am not sure what's going on. Can anyone tell me what's wrong here and how can I enable more detailed logs ?


-
What's the best FFMPEG method for frequent, automated compilation of timelapse videos ?
5 août 2020, par GoOutsideI have a web application running on a not-particularly beefy Ubuntu Amazon Lightsail instance that uses FFMPEG to build a timelapse video generated from downloaded .jpg webcam photos taken every 2 minutes throughout the day (720 total images each day, which grows throughout the day as new images are downloaded).


The code I'm running every 20 minutes is this :


ffmpeg -y -r 24 -pattern_type glob -I 'picturefolder/*.jpg' -s 1024x576 -vcodec libx264 picturefolder/timelapse.mp4


This mostly works, but it is often quite slow, taking 30-60 seconds to run and getting slower as the day goes on, of course.


Recently, I tried to use
concat
instead ofglob
bing the entire folder over and over. I did not see a noticeable performance improvement, ass it appears theconcat
processes the entire video in order to add even just a few frames to the end of it.

My question for any FFMPEG experts out there : what is the most efficient way to handle this kind of automated timelapse creation, given my setup ? Is there a flag I'm missing ? Perhaps a different, more efficient method ? Or maybe a way to have the FFMPEG process just crawl through this at a more 'slow and steady' pace instead of big bursts of CPU usage.


Or am I stuck with this and should just deal with it ? My ultimate goal would be to continue using my current tier (2 GB RAM, 1 vCPU) without the expense of upgrading. Thank you very kindly for your help !


-
InvalidArgumentException : Missing required client configuration options Laravel + FFmpeg + ubuntu 20 + Lamp
9 août 2020, par Ahmed Al-RayanI 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