Recherche avancée

Médias (0)

Mot : - Tags -/interaction

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (71)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • La sauvegarde automatique de canaux SPIP

    1er avril 2010, par

    Dans 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 (...)

Sur d’autres sites (15587)

  • Problems in my sample C code using FFmpeg API

    11 juillet 2019, par Tina J

    I’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.04037

    However, 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 a display_metadata function. Looks like the frame variable has a metadata 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 David

    I'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 Antonio

    I 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 for enable-gray, the only entry I find is in the configure 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.