
Recherche avancée
Médias (1)
-
La conservation du net art au musée. Les stratégies à l’œuvre
26 mai 2011
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (74)
-
Publier sur MédiaSpip
13 juin 2013Puis-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 -
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 (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)
Sur d’autres sites (9523)
-
Problems in my sample C code using FFmpeg API
11 juillet 2019, par Tina JI’ve been trying to change an FFmpeg’s example code HERE to call other filters using its C APIs. Say the filter be
freezedetect=n=-60dB:d=8
which normally runs like this :ffmpeg -i small.mp4 -vf "freezedetect=n=-60dB:d=8" -map 0:v:0 -f null -
And prints outputs like this :
[freezedetect @ 0x25b91c0] lavfi.freezedetect.freeze_start: 5.005
[freezedetect @ 0x25b91c0] lavfi.freezedetect.freeze_duration: 2.03537
[freezedetect @ 0x25b91c0] lavfi.freezedetect.freeze_end: 7.04037However, the original example displays frames, not these metadata information. How can I change the code to print this metadata information (and not the frames) ?
I’ve been trying to change the
display_frame
function below into adisplay_metadata
function. Looks like theframe
variable has ametadata
dictionary which looks promising, but my attempts failed to use it. I’m also new to C language.Original
display_frame
function :static void display_frame(const AVFrame *frame, AVRational time_base)
{
int x, y;
uint8_t *p0, *p;
int64_t delay;
if (frame->pts != AV_NOPTS_VALUE) {
if (last_pts != AV_NOPTS_VALUE) {
/* sleep roughly the right amount of time;
* usleep is in microseconds, just like AV_TIME_BASE. */
delay = av_rescale_q(frame->pts - last_pts,
time_base, AV_TIME_BASE_Q);
if (delay > 0 && delay < 1000000)
usleep(delay);
}
last_pts = frame->pts;
}
/* Trivial ASCII grayscale display. */
p0 = frame->data[0];
puts("\033c");
for (y = 0; y < frame->height; y++) {
p = p0;
for (x = 0; x < frame->width; x++)
putchar(" .-+#"[*(p++) / 52]);
putchar('\n');
p0 += frame->linesize[0];
}
fflush(stdout);
}My new
display_metadata
function that needs to be completed :static void display_metadata(const AVFrame *frame)
{
// printf("%d\n",frame->height);
AVDictionary* dic = frame->metadata;
printf("%d\n",*(dic->count));
// fflush(stdout);
} -
ffmpeg failed with code 1 firebase cloud functions
17 octobre 2020, par DavidI'm trying to add a logo overlay to a video in firebase-cloud-functions using ffmpeg. I have sucessfully run this command on my local machine. I can't seem to access more indepth logging that just
failed with code 1
, and unsure what might be causing this issue ( the source files referenced exist in their location ).

await spawn('ffmpeg', ['-i', filePath, '-i', logofilepath, '-filter_complex', '"overlay=20:20"', targetFilePath]);

console.log('Video with logo @', targetFilePath)



Error :




ChildProcessError :
ffmpeg -i /tmp/input.mp4 -i /tmp/logo.png -filter_complex "overlay=20:20" /tmp/output.mp4
failed with code 1



-
FFmpeg : Reading the source code, how do I understand the impact of a given configuring option ?
25 février 2016, par AntonioI was trying to investigate the impact of the
--enable-gray
configuring option on the ffmpeg code. However, if I download the source and grep the entire project forenable-gray
, the only entry I find is in theconfigure
file, in the help section. Is this option used at all ? If it is used, how do I find the section of code which are activated by using this option ?Even using a regex search with
enable.*gray
doesn’t bring any additional results.