
Recherche avancée
Médias (1)
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (45)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Other interesting software
13 avril 2011, parWe don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
We don’t know them, we didn’t try them, but you can take a peek.
Videopress
Website : http://videopress.com/
License : GNU/GPL v2
Source code : (...)
Sur d’autres sites (5377)
-
ffmpeg unexpected exit code 1 for -list_devices and -list_options
8 janvier 2024, par djvgDescription


If I run any of the following commands from the examples in the documentation, using
ffmpeg
4.2.2 on Windows 10, the requested information is successfully displayed in the console, but the process exits with exit code1
, instead of the expected0
(success).

ffmpeg -list_devices true -f dshow -i dummy

ffmpeg -list_options true -f dshow -i video="MyCamera"



As far as I know, exit code
1
on Windows implies "Incorrect function", so I consider this behavior to be unexpected.

If I stream camera input to disk, using e.g.
ffmpeg -f dshow -i video="MyCamera" "myfile.mp4"
, then stop using q, the exit code is0
, as expected.

Question


Does the exit code
1
constitute normal behavior forffmpeg
, or am I doing something wrong ?

Relevance


When running the commands manually, from the command line, the exit code does not make much difference, as long as the requested information is displayed.


However, when running the commands programmatically, it may cause trouble. For example, using Python's
subprocess.run(..., check=True)
, the nonzero exit code causes a CalledProcessError.

Of course there are ways around this, e.g. use
check=False
, but the point is that a workaround would not be necessary ifffmpeg
behaved as expected, i.e. returned0
.

-
CentOS 7.4.1708 : ERROR : x265 not found using pkg-config
16 novembre 2017, par AdrianI’m trying to compile ffmpeg with Nvidia support following the guides on https://trac.ffmpeg.org/wiki/CompilationGuide/Centos and https://developer.nvidia.com/ffmpeg. I’ve ended up with the following command :
PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure --enable-pthreads --disable-w32threads --prefix="$HOME/ffmpeg_build" --pkg-config-flags="--static" --extra-cflags="-I$HOME/ffmpeg_build/include -I/usr/local/cuda/include" --extra-ldflags="-L$HOME/ffmpeg_build/lib -L/usr/local/cuda/lib64" --extra-libs='-lpthread -lm' --bindir="$HOME/bin" --enable-gpl --enable-libfdk_aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree --enable-cuda --enable-cuvid --enable-nvenc --enable-nonfree --enable-libnpp
I’m getting the wonderful error
ERROR : x265 not found using pkg-config
looking in
ffbuild/config.log
reveals the following error :gcc -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -I/home/agilbert/ffmpeg_build/include -I/usr/local/cuda/include -std=c11 -fomit-frame-pointer -pthread -I/home/agilbert/ffmpeg_build/include -I/usr/include/freetype2 -I/home/agilbert/ffmpeg_build/include/opus -I/home/agilbert/ffmpeg_build/include/opus -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -L/home/agilbert/ffmpeg_build/lib -c -o /tmp/ffconf.MfrVBc4k/test.o /tmp/ffconf.MfrVBc4k/test.c
In file included from /tmp/ffconf.MfrVBc4k/test.c:1:0:
/home/agilbert/ffmpeg_build/include/x265.h:1753:40: error: expected ';', ',' or ')' before '&' token
FILE* x265_csvlog_open(const x265_param& param);
^
/home/agilbert/ffmpeg_build/include/x265.h:1757:40: error: expected ';', ',' or ')' before '&' token
void x265_csvlog_frame(const x265_param& param, const x265_picture& pic);
^
/home/agilbert/ffmpeg_build/include/x265.h:1762:64: error: expected ';', ',' or ')' before '&' token
void x265_csvlog_encode(x265_encoder *encoder, const x265_stats& stats, int argc, char** argv);
^
/home/agilbert/ffmpeg_build/include/x265.h:1766:36: error: expected ';', ',' or ')' before '&' token
void x265_dither_image(x265_picture& pic, int picWidth, int picHeight, int16_t *errorBuf, int bitDepth);
^
/home/agilbert/ffmpeg_build/include/x265.h:1815:50: error: expected ';', ',' or ')' before '&' token
FILE* (*csvlog_open)(const x265_param&);
^
/home/agilbert/ffmpeg_build/include/x265.h:1816:51: error: expected ';', ',' or ')' before '&' token
void (*csvlog_frame)(const x265_param&, const x265_picture&);
^
/home/agilbert/ffmpeg_build/include/x265.h:1817:67: error: expected ';', ',' or ')' before '&' token
void (*csvlog_encode)(x265_encoder*, const x265_stats&, int, char**);
^
/home/agilbert/ffmpeg_build/include/x265.h:1818:47: error: expected ';', ',' or ')' before '&' token
void (*dither_image)(x265_picture&, int, int, int16_t*, int);
^
/home/agilbert/ffmpeg_build/include/x265.h:1820:1: warning: no semicolon at end of struct or union [enabled by default]
} x265_api;
^gcc version is gcc-4.8.5-16.el7.x86_64
As per a question below : Yes - x265 is installed as per https://trac.ffmpeg.org/wiki/CompilationGuide/Centos and yes pkg-config is finding it. The compilation error makes me think that I’m missing a flag to the —pkg-config-flags optnion, but I can’t find one that works.
Does anyone know what I should be passing to pkg-config to get it to enable x265 ?
-
Evolution #2594 : Webservice
12 mars 2012, par sébastien chandonayInfo concernant le problème d’authentification : chez OVH, PHP est compilé en CGI et donc les variables $_SERVER[’PHP_AUTH_USER’] et $_SERVER[’PHP_AUTH_PW’] ne sont pas disponibles. Or, l’authentification HTTP BASIC de Spip se base dessus. Les informations seraient disponibles via (...)