
Recherche avancée
Médias (2)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
-
Carte de Schillerkiez
13 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (111)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (6314)
-
How to link libav* libraries of FFmpeg in my own program ?
20 août 2019, par zuguoruiI am new to FFmpeg, now I want to use the FFmpeg codec compenet in my own program. I’ve followed the guide on FFmpeg wiki to complie the libraries the FFmpeg and get them done. But when I compile my own program it always tips
ld: library not found for -lavutil
or something like this.Environment:MacOS 10.14.6
Compile tool : clang++
steps :
(1)Install all needed libraries follow the wiki.
(2)
./configuure --prefix=host --enable-shared --disable-static
(3)
make
(4)
make install
, after this step, I got compiled files in dictionaryhost
.(5)copy the source code in FFmpeg/doc/examples/decode_audio.c to create a new project, and copy includes and dylib files to my project dictionary. The structure of my project is :
./
|----FFmpeg
|----include
|----libavcodec
|----*headers*
|----libavformat
|----*headers*
|----libavutil
|----*headers*
|----lib
|----libavutil.dylib
|----libavcodec.dylib
|----libavformat.dylib
|----main.cpp(6)compile the project.
clang++ *.cpp -L./FFmpeg/lib/ -lavutil -lavformat -lavcodec -I ./FFmpeg/include -o main.out
But it always fail with tip
ld: library not found for -lavutil
or something like this. I don’t know why. Do I need to install those libraries in/usr/local
dictionary instead ofhost
? Or I miss some variables when configing or compiling ?update:I solved this problem, I copyed the links of dylib files but not dylib itself, which caused this problem. But a new problem rised, when I run the program, it tips
dyld: Library not loaded: @executable_path/lib/libavcodec.dylib. Reason: image not loaded
. -
CANNOT LINK EXECUTABLE error with required libs loaded. How to link them properly ? [duplicate]
11 septembre 2019, par dentexThis question already has an answer here :
edit : I’m aware of the possible duplicate, but the answer it’s not directly applicable. I’m using ProcessBuilder and not Runtime.getRuntime().exec :
public int execProcess(List<string> cmds, ShellUtils.ShellCallback sc) {
StringBuilder cmdlog = new StringBuilder();
for (String cmd : cmds) {
cmdlog.append(' ');
}
Utils.logger("v", cmdlog.toString(), DEBUG_TAG);
ProcessBuilder pb = new ProcessBuilder();
pb.directory(mBinFileDir);
pb.command(cmds);
Process process = null;
int exitVal = 1; // Default error
try {
process = pb.start();
StreamGobbler errorGobbler = new
StreamGobbler(process.getErrorStream(), "ERROR", sc);
StreamGobbler outputGobbler = new
StreamGobbler(process.getInputStream(), "OUTPUT", sc);
errorGobbler.start();
outputGobbler.start();
exitVal = process.waitFor();
sc.processComplete(exitVal);
} catch (Exception e) {
Log.e(DEBUG_TAG, "Error executing ffmpeg command!", e);
} finally {
if (process != null) {
Utils.logger("w", "destroyng process", DEBUG_TAG);
process.destroy();
}
}
return exitVal;
}
</string>
I have two versions on FFmpeg compiled for android : with and without
liblame
enabled.When I load in
/data/data/<>/app_bin/
the FFmpeg binary compiled with NO lame support, it extracts audio from video without an issue. But when I use the one with lame support enabled, I get the error below into the log.Required libs, also compiled for android, are correctly loaded when shipped into the
libs
project folder withSystem.loadLibrary("lame")
.I was wondering if there is something else to do in order to properly make the FFmpeg binary find the libs.
Those are the same libs given to the NDK to build the FFmpeg binary.D/dalvikvm(13741): Trying to load lib /data/app-lib/<>/liblame.so 0x40ffed08
D/dalvikvm(13741): Added shared lib /data/app-lib/<>/liblame.so 0x40ffed08
D/dalvikvm(13741): No JNI_OnLoad found in /data/app-lib/<>/liblame.so 0x40ffed08, skipping init
D/FfmpegController(13741): Trying to chmod '/data/data/<>/app_bin/ffmpeg' to: 755
V/FfmpegController(13741): /data/data/<>/app_bin/ffmpeg -y -i /storage/sdcard0/Download/video.webm -vn -acodec copy /storage/sdcard0/Download/audio.ogg
>>>>>> ---------- <<<<<<
D/DownloadsService(13741): soinfo_link_image(linker.cpp:1673): could not load library "liblame.so" needed by "/data/data/<>/app_bin/ffmpeg"; caused by load_library(linker.cpp:771): library "liblame.so" not foundCANNOT LINK EXECUTABLE
>>>>>> ---------- <<<<<<
I/DownloadsService(13741): FFmpeg process exit value: 255I’m not attaching code because it’s fairly straightforward :
- download the FFmpeg binary (it’s not shipped with the app) ;
- copy the binary from the download folder to
/data/data/<>/app_bin/
; - chmod 755 ;
- execute from there and read the output.
Please comment if something else is required.
-
avfilter/vf_unsharp : rename config_props -> config_input, link -> inlink
14 octobre 2019, par Limin Wang