
Recherche avancée
Autres articles (85)
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)
Sur d’autres sites (16239)
-
Generating number of thumbnails depending on video size using AWS MediaConvert
1er décembre 2020, par sakhunzaiAfter reading this article I get the sense that AWS media convert job template cannot be re-used to generate thumbnails of arbitrary video size. The article assumes that we know the size/duration of video uploaded upfront hence the number of thumbnails we desire.


What I am looking for is to generate a random number of thumbnails based of video size (e.g large number of thumbnails for large video and small number of thumbnails for small video). I approached this solution using lambda trigger and ffmpeg lambda layer but lambda function timeouts (15 minutes max) for videos larger than 150MB (since it takes time to read the video from the s3 bucket).


What are my options to process large number of video , generate a variable number of thumbnails, merge those thumbs to generate a sprite ?


I tried lambda trigger with ffmpeg/ffprob to generate sprite, but that has timeout issue. Now I have setup a cloud watch event rule to trigger lambda function on mediaconvert job status change( completed)
and merge the thumbs to generate sprite, which seems much lighter but I need an arbitrary number of thumbs.


-
avformat/hls : Be more picky on extensions
16 janvier, par Michael Niedermayeravformat/hls : Be more picky on extensions
This blocks disallowed extensions from probing
It also requires all available segments to have matching extensions to the format
mpegts is treated independent of the extensionIt is recommended to set the whitelists correctly
instead of depending on extensions, but this should help a bit,
and this is easier to backportFixes : CVE-2023-6602 II. HLS Force TTY Demuxer
Fixes : CVE-2023-6602 IV. HLS XBIN Demuxer DoS AmplificationThe other parts of CVE-2023-6602 have been fixed by prior commits
Found-by : Harvey Phillips of Amazon Element55 (element55)
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc> -
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 ?