
Recherche avancée
Médias (1)
-
The Slip - Artworks
26 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (68)
-
MediaSPIP Core : La Configuration
9 novembre 2010, parMediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...) -
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras. -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs
Sur d’autres sites (12338)
-
Writing an MPEG video to S3 using the Lambda FFmpeg Layer
12 avril 2020, par GracieI am using AWS Lambda with the FFmpeg layer to try and convert an existing local MP4 file (beach.mp4) - that is within my upload deployment zip to S3 - into to MPEG video and then write that file to S3.



I have used ffprobe, which works, so the FFmpeg layer is setup correctly.



I am writing a file to S3, but it is blank, only 15 bytes. So doesn't contain the MPEG file created by FFmpeg.



I think this has something to do with sync or streaming the video file so it can be written, but not sure.



Here is my code, if anyone could help figure this out :



const util = require('util');
const AWS = require('aws-sdk');
const s3 = new AWS.S3();
const { readFileSync, writeFileSync, unlinkSync, writeFile, readdir } = require('fs');
//const fs = require('fs');
const path = require('path');
const { spawnSync } = require('child_process');

exports.handler = async (event, context, callback) => {

 const outputBucket = 'mys3bucket';

 const mpegcreate = await spawnSync(
 '/opt/bin/ffmpeg',
 [
 '-i',
 'beach.mp4',
 'beach.mpeg'
 ]
 );

 // Write ffmpeg output to a file in /tmp/
 const writeMPEGFile = util.promisify(writeFile);
 await writeMPEGFile('/tmp/beach.mpeg', mpegcreate, 'binary');
 console.log('MPEG content written to /tmp/');

 // Copy MPEG data to a variable to enable write to S3 Bucket
 let result = mpegcreate;
 console.log('MPEG Result contents ', result);

 const vidFile = readFileSync('/tmp/beach.mpeg');

 // Set S3 bucket details and put MPEG file into S3 bucket from /tmp/
 const s3 = new AWS.S3();
 const params = {
 Bucket: outputBucket,
 Key: 'beach.mpeg',
 ACL: 'private',
 Body: vidFile
 };

 // Put MPEG file from AWS Lambda function /tmp/ to an S3 bucket
 const s3Response = await s3.putObject(params).promise();
 callback(null, s3Response);

};



-
avcodec/jpeg2000dec : error check when processing tlm marker
26 mars 2020, par Gautam Ramakrishnan -
Libav (ffmpeg) HW decoding problem with frames at the end of file - missing or corrupted
25 mars 2020, par HitokageMy goal is to utilize HW accelerated decoding (using vdpau, h265 and Nvidia RTX) getting number of frames from video. Everything works unless the frames get to the end of the video. I am getting less frames than I try to decode usually the last but one is missing (I know strange, the last one is OK just not getting all of them) and sometimes neighboring frames are corrupted. I followed the docs regarding end of file situation. Here is the code :
//getting first packet
if (!packet.data)
av_read_frame(formatContext, & packet);
AVFrame * frame = av_frame_alloc();
if (!frame)
throw std::runtime_error("Cannot allocate packet/frame");
//now trying to get frames from the video
for (int i = 0; i < number; i++) {
int err = 0;
//feeding the codec
while (err == 0) {
if (packet.stream_index == videoStreamId)
if ((err = avcodec_send_packet(codecContext, & packet)) != 0)
break;
av_packet_unref( & packet);
err = av_read_frame(formatContext, & packet);
//sending null packet to flush the buffers
if (err == AVERROR_EOF) {
packet.data = NULL;
packet.size = 0;
}
}
bool waitForFrame = true;
while (waitForFrame) {
int err = avcodec_receive_frame(codecContext, frame);
if (err == AVERROR_EOF)
waitForFrame = false;
else if (err < 0)
throw std::runtime_error("Cannot receive frame");
if (frame -> format == pixFmt)
//I get here only number-1 timesPlease note that the problem is happening only when I request the same number of frames as is the length of the video. Seems like the end of file situation is not handled properly. The frames get decoded ok if I try to get for example length-1 frames.
I also tried to log the events and everything looks OK, just one frame is not there. This is a case where 64 frames long video is being decoded asking for 64 frames :
Send packet 0 == 0
Read frame status: Success
Send packet 1 == 0
Read frame status: Success
Send packet 2 == 0
Read frame status: Success
Send packet 3 == 0
Read frame status: Success
Send packet 4 !=0
Send packet status: Resource temporarily unavailable
Processing frame:0
Send packet 4 !=0
Send packet status: Resource temporarily unavailable
Processing frame:1
Send packet 4 == 0
Read frame status: Success
Send packet 5 == 0
Read frame status: Success
Send packet 6 !=0
Send packet status: Resource temporarily unavailable
Processing frame:2
Send packet 6 !=0
Send packet status: Resource temporarily unavailable
Processing frame:3
...
Processing frame:56
Send packet 60 !=0
Send packet status: Resource temporarily unavailable
Processing frame:57
Send packet 60 == 0
Read frame status: Success
Send packet 61 == 0
Read frame status: Success
Send packet 62 !=0
Send packet status: Resource temporarily unavailable
Processing frame:58
Send packet 62 !=0
Send packet status: Resource temporarily unavailable
Processing frame:59
Send packet 62 == 0
Read frame status: Success
Send packet 63 == 0
Read frame status: End of file
Set null packet
Processing frame:60
Send packet 64 == 0
Read frame status: End of file
Set null packet
Processing frame:61
Send packet 65 !=0
Send packet status: End of file
Processing frame:62
Send packet 65 !=0
Send packet status: End of file
End of file at receive frame