
Recherche avancée
Médias (91)
-
Géodiversité
9 septembre 2011, par ,
Mis à jour : Août 2018
Langue : français
Type : Texte
-
USGS Real-time Earthquakes
8 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
-
SWFUpload Process
6 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
-
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
-
Podcasting Legal guide
16 mai 2011, par
Mis à jour : Mai 2011
Langue : English
Type : Texte
-
Creativecommons informational flyer
16 mai 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (68)
-
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 -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
L’utiliser, en parler, le critiquer
10 avril 2011La première attitude à adopter est d’en parler, soit directement avec les personnes impliquées dans son développement, soit autour de vous pour convaincre de nouvelles personnes à l’utiliser.
Plus la communauté sera nombreuse et plus les évolutions seront rapides ...
Une liste de discussion est disponible pour tout échange entre utilisateurs.
Sur d’autres sites (8033)
-
Compiling ffmpeg with NVDIA GPU enabled for windows
12 octobre 2017, par GuruI am working on decoding video using ffmpeg with NVDIA GPU enabled on windows platform.
Followed below steps as per the document provided by ffmpeg to compile ffmpeg software
- Install msys2 from www.msys2.org.
- Clone FFMPEG’s public GIT repository. git clone https://git.ffmpeg.org/ffmpeg.git
- Create a folder named nv_sdk in the parent directory of FFMPEG and copy all the libraries from C :\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\include to and C :\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\lib\x64 to nv_sdk folder.
- Launch the Visual Studio x64 Native Tools Command Prompt.
- From the Visual Studio x64 Native Tools Command Prompt, launch the MinGW64 environment by running mingw64.exe from the msys2 installation folder.
- In the MinGW64 environment, install the necessary packages. pacman -S diffutil make pkg-config yasm
- Add the following paths by running the commands. export PATH="/c/Program Files (x86)/Microsoft Visual Studio 12.0/VC/BIN/amd64/" :$PATH export PATH="/c/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v8.0/bin/" :$PATH
- Go to the FFMPEG installation folder and run the following command. ./configure —enable-nonfree —enable-nvenc —enable-cuda —enable-cuvid —enable-libnpp —extra-cflags=-Ilocal/include —extra-cflags=-I../nv_sdk —extra-ldflags=-L../nv_sdk
- Compile the code by executing the following command. make -j 8
But In the 8th step I am getting below error, please let me know what could be the possible solution for the issue.
admin@ADMIN-PC MINGW64 /c/ffmpeg
$ ./configure —enable-nonfree —enable-nvenc —enable-cuda —enable-cuvid —ena ble-libnpp —extra-cflags=-Ilocal/include —extra-cflags=-I../nv_sdk —extra-ldf lags=-L../nv_sdk
gcc is unable to create an executable file.
If gcc is a cross-compiler, use the —enable-cross-compile option.
Only do this if you know what cross compiling means.
C compiler test failed.If you think configure made a mistake, make sure you are using the latest
version from Git. If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
Include the log file "ffbuild/config.log" produced by configure as this will hel p
solve the problem. -
Vcpkg building FFmpeg with libxml2
15 décembre 2019, par SubestimaFirst off all im a newbie in this area so if im asking something really stupid or non sense im sorry in advance, so lets get right to the point... im trying to add features to the ffmpeg, and by what i know i have to modify CONTROL file and portfile.cmake but as it seems its not enough i dont understand the errors and i cant get more info about this in the internet so if you could give me some info how to do it properly it would allready mean a lot to me ! i will leave the portions of code and error file
**portfile.cmake:**
if("libxml2" IN_LIST FEATURES)
set(OPTIONS "${OPTIONS} --enable-libxml2")
endif()
**CONTROL:**
Feature: libxml2
Description: Libxml2 is the XML C parser and toolkit developed for the Gnome project (but usable outside of the Gnome platform)
Build-Depends: zlib, libiconv, liblzma
**Command Prompt after (vcpkg install ffmpeg[libxml2]:x64-windows)**
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
Command failed: C:/vcpkg/downloads/tools/msys2/msys64/usr/bin/bash.exe --noprofile --norc C:/vcpkg/ports/ffmpeg\build.sh C:/vcpkg/buildtrees/ffmpeg/x64-windows-rel C:/vcpkg/buildtrees/ffmpeg/src/n4.2-02d8c63f80 C:/vcpkg/packages/ffmpeg_x64-windows "--enable-asm --enable-yasm --disable-doc --enable-debug --enable-runtime-cpudetect --enable-libxml2 --disable-openssl --disable-ffmpeg --disable-ffplay --disable-ffprobe --disable-libvpx --disable-libx264 --disable-opencl --disable-lzma --disable-bzlib --enable-avresample --disable-static --enable-shared --extra-cflags=-DHAVE_UNISTD_H=0 --extra-cflags=-MD --extra-cxxflags=-MD"
Working Directory: C:/vcpkg/buildtrees/ffmpeg/x64-windows-rel
Error code: 1
See logs for more information:
C:\vcpkg\buildtrees\ffmpeg\build-x64-windows-rel-out.log
Call Stack (most recent call first):
ports/ffmpeg/portfile.cmake:197 (vcpkg_execute_required_process)
scripts/ports.cmake:94 (include)
Error: Building package ffmpeg:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: ffmpeg:x64-windows
Vcpkg version: 2019.09.12-nohash**strong text**
**Log Error file:**
=== CONFIGURING === ERROR: libxml-2.0 not found using pkg-config
If you think configure made a mistake, make sure you are using the latest version from Git. If the latest version fails, report the problem to the ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. Include the log file "ffbuild/config.log" produced by configure as this will help solve the problem.Thank you for your attention,
Regards Pedro Cunha ! -
Aubio (aubioonset.exe) on Windows - can't find ffmpeg libraries
7 octobre 2024, par Peter WirdemoI have installed Aubio on Windows but when trying to use the tools, like aubioonset.exe, I am faced with the following error message :


C:/Peter/aubio/aubio/aubio-0.4.6-win64-ffmpeg/bin/aubioonset.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory



I assume it looks after ffmpeg libraries. I have FFmpeg installed and bin-dir added to PATH environment variable. FFMPEG is working flawless globally.


After searching internet for answers to my issue I find "answers" like :
"install chosen libraries (for instance ffmpeg, with header files)"


That vague answer doesn't help me at all. Exactly how do I install ffmpeg libraries, with header files, so that the Aubio-tools can find them ? I need specifics about what environmental-variables must be set - or - should the ffmpeg lib-files be placed in the Aubio Build folder somewhere, or what should I do ?


And after doing that I am supposed to recompile and reinstall Aubio. I can do that.


This is btw. the result from
./waf configure
when building my own Aubio-binaries (instead of downloading pre-builds) :

peter@DESKTOP-I0KNADQ MINGW64 /c/Peter/aubio/aubio (master)
$ ./waf configure
Setting top to : C:\Peter\aubio\aubio
Setting out to : C:\Peter\aubio\aubio\build
Checking for 'msvc' (C compiler) : C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\CL.exe
Checking for header stdlib.h : yes
Checking for header stdio.h : yes
Checking for header math.h : yes
Checking for header string.h : yes
Checking for header errno.h : yes
Checking for header limits.h : yes
Checking for header stdarg.h : yes
Checking for header getopt.h : not found
Checking for header unistd.h : not found
Checking for library m : not found
Checking for C99 __VA_ARGS__ macro : yes
Checking for size of smpl_t : float
Checking for size of lsmp_t : double
Checking if complex.h is enabled : no
Checking for FFT implementation : ooura
Checking for program 'pkg-config' : not found
Checking for program 'pkg-config' : not found
Checking for program 'pkg-config' : not found
Checking for program 'pkg-config' : not found
Checking for program 'pkg-config' : not found
Checking for program 'pkg-config' : not found
Checking for program 'pkg-config' : not found
Checking for program 'pkg-config' : not found
Checking for all libav libraries : not found (missing avcodec)
Checking for program 'pkg-config' : not found
Checking for program 'pkg-config' : not found
Checking if using source_wavread : yes
Checking if using sink_wavwrite : yes
Checking for program 'txt2man' : not found
Checking for program 'doxygen' : not found
Checking for program 'sphinx-build' : not found
'configure' finished successfully (7.590s)



As can be seen above I have no problem building Aubio without external libraries.


So my guess is that I can go down two different paths for a solution here : either try building with all external libraries somehow prepared (I have tried but can't change the output of
./waf configure
no matter what I do. I have cloned the ffmpeg source from github. I can't figure out where./waf configure
is looking for it). Or I can get the precompiled binaries to work, by somehow installing the external libraries.

I have tried both solutions in multiple ways, but fail getting any one of them to work.