
Recherche avancée
Autres articles (32)
-
Utilisation et configuration du script
19 janvier 2011, parInformations 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 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 -
Les formats acceptés
28 janvier 2010, parLes 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 DreamcastSome 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 CodyI 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 statuswhere the output of
pkg-config
is...$ pkg-config --cflags --libs libavutil
-I/usr/local/include -L/usr/local/lib -lavutilThe
objdump
shows that the shared object libavutil.so does haveav_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_flagsPlease 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 withinotifywait
if the other version provided by the distro were called. They were not, and the one being opened during execution ofg++
was /usr/local/lib/libavutil.so.Summary :
-
/usr/local/lib/libavutil.so does have the symbol.
-
-rpath
was used to force to link against the shared library. -
Why link-time error ? T_T
Any suggestion or information would be highly appreciated ! Thanks !
REEDIT :
ffplay
works fine andldd
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 CodyI 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 haveav_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 withinotifywait
if the other version provided by the distro were called. They were not, and the one being opened during execution ofg++
was /usr/local/lib/libavutil.so.


Summary :



- 

-
/usr/local/lib/libavutil.so does have the symbol.
-
-rpath
was used to force to link against the shared library. -
Why link-time error ? T_T









Any suggestion or information would be highly appreciated ! Thanks !



REEDIT :
ffplay
works fine andldd
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.

-