Recherche avancée

Médias (0)

Mot : - Tags -/interaction

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

Autres articles (32)

  • Utilisation et configuration du script

    19 janvier 2011, par

    Informations spécifiques à la distribution Debian
    Si vous utilisez cette distribution, vous devrez activer les dépôts "debian-multimedia" comme expliqué ici :
    Depuis la version 0.3.1 du script, le dépôt peut être automatiquement activé à la suite d’une question.
    Récupération du script
    Le script d’installation peut être récupéré de deux manières différentes.
    Via svn en utilisant la commande pour récupérer le code source à jour :
    svn co (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-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

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

Sur d’autres sites (5022)

  • Dreamcast Development Desktop

    28 mars 2011, par Multimedia Mike — Sega Dreamcast

    Some people are curious about what kind of equipment is required to program a Sega Dreamcast. This is my setup :



    It’s a bit overcomplicated. The only piece in that picture which doesn’t play a role in the Dreamcast development process is the scanner. The Eee PC does the heavy lifting of development (i.e., text editing and cross compilation) and uploads to the Dreamcast via a special serial cable. Those are the most essential parts and are really the only pieces necessary for a lot of algorithmic stuff (things that can be validated via a serial console). But then I have to go up a level where I output video. That’s where things get messy.



    The Mac Mini and giant monitor really just act as a glorified TV in this case. Ideally, it will be more than that. The DC outputs audio and video via composite cables to a Canopus DV capture bridge. That’s connected via FireWire to the external hard drive underneath the Mac Mini, which is connected to the Mac. Adobe Premiere Pro handles the DV capture / display.

    One day I hope to have something worthwhile to capture.

  • Unable to link against FFmpeg libaries

    28 octobre 2015, par Cody

    I tried to build this, but always got link-time error.

    #include <libavutil></libavutil>log.h>    
    int main(int argc, char *argv[])
    {
       ::av_log_set_flags(AV_LOG_SKIP_REPEATED);
       return 0;
    }

    My distro is Debian GNU/Linux 8 (jessie). The FFmpeg was built by myself, and the configure command was...

    $ ./configure --prefix=/usr/local --disable-static --enable-shared \
    > --extra-ldflags='-Wl,-rpath=/usr/local/lib'

    The link-error is as follows.

    $ g++ foo.cpp -D__STDC_CONSTANT_MACROS -Wall \
    > -Wl,-rpath=/usr/local/lib \
    > $(pkg-config --cflags --libs libavutil)
    /tmp/ccKzgEFb.o: In function `main':
    foo.cpp:(.text+0x17): undefined reference to `av_log_set_flags(int)'
    collect2: error: ld returned 1 exit status

    where the output of pkg-config is...

    $ pkg-config --cflags --libs libavutil
    -I/usr/local/include -L/usr/local/lib -lavutil

    The objdump shows that the shared object libavutil.so does have av_log_set_flogs inside.

    $ objdump --dynamic-syms /usr/local/lib/libavutil.so | grep 'av_log_set_flags'
    000260f0 g    DF .text  0000000a  LIBAVUTIL_54 av_log_set_flags

    Please note that the g++ command used to build the above application had a linker option -Wl,-rpath=/usr/local/lib, though it still doesn’t work. Also, I’ve tried to monitor with inotifywait if the other version provided by the distro were called. They were not, and the one being opened during execution of g++ was /usr/local/lib/libavutil.so.

    Summary :

    1. /usr/local/lib/libavutil.so does have the symbol.

    2. -rpath was used to force to link against the shared library.

    3. Why link-time error ? T_T

    Any suggestion or information would be highly appreciated ! Thanks !

    REEDIT : ffplay works fine and ldd shows it use /usr/local/lib/libavutil.so. So, the libraries seems not broken, and the problem becomes how to build my own codes to use the libraries.

  • Unable to link against FFmpeg libaries

    2 mars 2023, par Cody

    I tried to build this, but always got link-time error.

    &#xA;&#xA;

    #include <libavutil></libavutil>log.h>    &#xA;int main(int argc, char *argv[])&#xA;{&#xA;    ::av_log_set_flags(AV_LOG_SKIP_REPEATED);&#xA;    return 0;&#xA;}&#xA;

    &#xA;&#xA;

    My distro is Debian GNU/Linux 8 (jessie). The FFmpeg was built by myself, and the configure command was...

    &#xA;&#xA;

    $ ./configure --prefix=/usr/local --disable-static --enable-shared \&#xA;> --extra-ldflags=&#x27;-Wl,-rpath=/usr/local/lib&#x27;&#xA;

    &#xA;&#xA;

    The link-error is as follows.

    &#xA;&#xA;

    $ g&#x2B;&#x2B; foo.cpp -D__STDC_CONSTANT_MACROS -Wall \&#xA;> -Wl,-rpath=/usr/local/lib \&#xA;> $(pkg-config --cflags --libs libavutil)&#xA;/tmp/ccKzgEFb.o: In function `main&#x27;:&#xA;foo.cpp:(.text&#x2B;0x17): undefined reference to `av_log_set_flags(int)&#x27;&#xA;collect2: error: ld returned 1 exit status&#xA;

    &#xA;&#xA;

    where the output of pkg-config is...

    &#xA;&#xA;

    $ pkg-config --cflags --libs libavutil&#xA;-I/usr/local/include -L/usr/local/lib -lavutil&#xA;

    &#xA;&#xA;

    The objdump shows that the shared object libavutil.so does have av_log_set_flogs inside.

    &#xA;&#xA;

    $ objdump --dynamic-syms /usr/local/lib/libavutil.so | grep &#x27;av_log_set_flags&#x27;&#xA;000260f0 g    DF .text  0000000a  LIBAVUTIL_54 av_log_set_flags&#xA;

    &#xA;&#xA;

    Please note that the g&#x2B;&#x2B; command used to build the above application had a linker option -Wl,-rpath=/usr/local/lib, though it still doesn't work. Also, I've tried to monitor with inotifywait if the other version provided by the distro were called. They were not, and the one being opened during execution of g&#x2B;&#x2B; was /usr/local/lib/libavutil.so.

    &#xA;&#xA;

    Summary :

    &#xA;&#xA;

      &#xA;
    1. /usr/local/lib/libavutil.so does have the symbol.

    2. &#xA;

    3. -rpath was used to force to link against the shared library.

    4. &#xA;

    5. Why link-time error ? T_T

    6. &#xA;

    &#xA;&#xA;

    Any suggestion or information would be highly appreciated ! Thanks !

    &#xA;&#xA;

    REEDIT : ffplay works fine and ldd shows it use /usr/local/lib/libavutil.so. So, the libraries seems not broken, and the problem becomes how to build my own codes to use the libraries.

    &#xA;