
Recherche avancée
Médias (1)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
Autres articles (62)
-
Installation en mode ferme
4 février 2011, parLe 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 (...) -
Formulaire personnalisable
21 juin 2013, parCette page présente les champs disponibles dans le formulaire de publication d’un média et il indique les différents champs qu’on peut ajouter. Formulaire de création d’un Media
Dans le cas d’un document de type média, les champs proposés par défaut sont : Texte Activer/Désactiver le forum ( on peut désactiver l’invite au commentaire pour chaque article ) Licence Ajout/suppression d’auteurs Tags
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire. (...) -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...)
Sur d’autres sites (8243)
-
install ffmpeg on amazon ecr linux python
27 mai 2024, par Luka SavicI'm trying to install ffmpeg on docker for amazon lambda function.
Code for Dockerfile is :


FROM public.ecr.aws/lambda/python:3.8

# Copy function code
COPY app.py ${LAMBDA_TASK_ROOT}

# Install the function's dependencies using file requirements.txt
# from your project folder.

COPY requirements.txt .
RUN yum install gcc -y
RUN pip3 install -r requirements.txt --target "${LAMBDA_TASK_ROOT}"
RUN yum install -y ffmpeg

# Set the CMD to your handler (could also be done as a parameter override outside of the Dockerfile)
CMD [ "app.handler" ]



I am getting an error :


> [6/6] RUN yum install -y ffmpeg:
#9 0.538 Loaded plugins: ovl
#9 1.814 No package ffmpeg available.
#9 1.843 Error: Nothing to do



-
Extract thumbnail from video in amazon s3 and store it in amazon s3 [closed]
24 juin 2021, par Kanav RainaI want to extract thumbnail from video and store it on s3.


import ffmpeg

url="https://link_to_s3_video.mp4"

(
 ffmpeg
 .input(url, ss='00:00:03') 
 .output("frame.png", pix_fmt='rgb24', frames='1') 
 .overwrite_output()
 .run()
)



I am able to extract image but now how should I pass this image to file_upload function and store it on s3


def file_upload(file, filename):
 link = f"https://{PUBLIC_BUCKET_NAME}.s3.us-east-2.amazonaws.com/images/{filename}"
 try:
 s3.Object(PUBLIC_BUCKET_NAME, f"images/{filename}").load()
 except ClientError as e:
 if e.response['Error']['Code'] == "404":
 try:
 s3_client.upload_fileobj(
 file,
 PUBLIC_BUCKET_NAME,
 f"images/{filename}",
 ExtraArgs={'ACL': 'public-read'}
 )

 return 200, link
 except ClientError as e:
 logging.error(e)
 return 500, ""
 else:
 return 500, ""
 else:
 return 409, link



Thanks


-
fluent-ffmpeg sometimes crashes entire amazon ec2 instance
24 octobre 2020, par Mick MarsdenI have a nodejs application where I'm using fluent-ffmpeg to convert captured video files via the html
<input file="file" />
tag to mp4 format. I'm also using ffmpeg-static to provide static binaries for fluent-ffmpeg's file path. But in order for the conversion to happen, I upload the captured video file via multer, and when that completes, multer passes the video url to fluent-ffmpeg. The code looks like this :

app.post("/upload-and-convert", async function(req, res) {

 var filepath;
 var path;

 try {

 const upload = util.promisify(uploadVideo());

 await upload(req, res);

 console.log(req.file);
 console.log("Success");
 filepath = req.file.filename;
 console.log(filepath);
 path = './public/uploads/' + filepath;
 console.log(path);

 } catch (e) {
 let response_json = {
 success: false,
 };
 res.setHeader("content-type", "application/json");
 res.send(response_json);
 }

 if(path != undefined)
 {

 console.log("Path not undefined, going to start FFMPEG");
 ffmpeg(path)
 .format('mp4')
 .size('720x720').autopad()
 .on('end', function() {
 console.log('file has been converted successfully');
 })
 .on('error', function(err) {
 console.log('an error happened: ' + err.message);
 let response_json = {
 success: false,
 };
 res.setHeader("content-type", "application/json");
 res.send(response_json);
 })
 .save('./public/uploads/video.mp4')
 .on('end', function() {
 console.log('file has been saved successfully');
 let response_json = {
 success: true,
 fileURL: 'https://websiteurl/uploads/video.mp4'
 };
 res.setHeader("content-type", "application/json");
 res.send(response_json);
 })

 } else
 {
 let response_json = {
 success: false,
 };
 res.setHeader("content-type", "application/json");
 res.send(response_json);
 }
});



Most times, the code runs fine and returns the fileURL as intended. Sometimes however, it completely crashes the amazon ec2 instance, and requires the instance be rebooted before it works again. I've checked the logs, and the server-error logs output no issues. The server-out logs when it crashes outputs the final console log before ffmpeg starts :


console.log("Path not undefined, going to start FFMPEG");



The moment it reaches the
ffmpeg(path)
, it goes down. It doesn't log any error, even though I have included error handling on the operation.

This has stumped me for days. I cannot figure out the commonality to explain why sometimes it crashes, and sometimes it does not. Note that this even happened before I started using the ffmpeg-static package. My node version is 12.19.0, and ffmpeg-static currently installs ffmpeg at version 4.3.1 if I recall correctly.


If anyone could help that would be great.