
Recherche avancée
Médias (91)
-
#3 The Safest Place
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#4 Emo Creates
15 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#2 Typewriter Dance
15 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#1 The Wires
11 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
ED-ME-5 1-DVD
11 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Audio
-
Revolution of Open-source and film making towards open film making
6 octobre 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (41)
-
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.
Sur d’autres sites (6930)
-
How to use FFMPEG Binaries within an Android App built with Android Studio for Windows
17 février 2016, par ValtinhoI’ve read hundreds of pages on how to use ffmpeg in Android Studio all over the internet and none of them managed to give actual working solutions. I need to be able to trim a video selected from the gallery down to only the first 5 seconds. Ffmpeg is extremely user-unfriendly and I can’t even get it to compile successfully.
The closest I got to compiling ffmpeg was running the app from uday-rayala called video-trimmer on github : https://github.com/uday-rayala/video-trimmer
I downloaded the code, imported it into Eclipse and it runs and cuts videos once (it always crashes if you try a second time...). Anyway, I tried to replicate uday’s video-trimmer setup in my Android Studio app by moving the ffmpeg source files into a jni folder, and the armeabi folder inside a jniLibs folder, but the entire thing falls apart and doesn’t compile.
Has anyone implemented ffmpeg source code within their apps ??? If so, could you please provide some working examples ? The internet is in desperate need of complete working examples for the extremely common task of video editing.
-
Using ffmpeg static libraries in an visual studio explress C++ 2010 project
29 octobre 2015, par Yvo GötzAs the title says, I have been trying to get ffmpeg/libav libraries to work in MSVC++ 2010.
However, I keep running in the following error while coding on debug mode.code :
extern "C"
{
#ifndef __STDC_CONSTANT_MACROS
#define __STDC_CONSTANT_MACROS
#endif
#include
#include
#include
#include
}
int main( int argc, char* argv[] )
{
av_register_all();
return 0;
}console :
1>------ Build started: Project: ffmpeg, Configuration: Debug Win32 ------
1>ffmpeg.obj : error LNK2019: unresolved external symbol _av_register_all referenced in function _main
1>C:\Users\okki\documents\visual studio 2010\Projects\ffmpeg\Debug\ffmpeg.exe : fatal error LNK1120: 1 unresolved externals
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========I used zeranoe’s latest build git-56ba331 (2013-05-14).
And I have tried the following to fix this :
- configuring the project to look for both the x64 and x86 libraries.
- Add the DLLs from the ’shared’ package to both library folders.
- Add the library directory to both the linker options and VC++ Directories.
I have been stuck on this for a while, and any suggestion can help.
If any extra info is needed I will happily provide. -
Compile FFmpeg Zeranoe Build with Visual Studio 2013
19 janvier 2016, par mFeinsteinI downloaded the most recent Zeranoe dev build here, included the header files to my code, placed
extern "C"
around the includes, since this is a C++ project and FFmpeg is a C library, and added the libs to Visual Studio as well, and I get this linker error :1>Camera.obj : error LNK2019 : unresolved external symbol _av_free referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _av_freep referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _av_frame_alloc referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _av_frame_free referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _avcodec_register_all referenced in function __catch$ ??0Camera@MicroDFV_Camera@@QAE@V ?$basic_string@DU ?$char_traits@D@std@@V ?$allocator@D@2@@std@@0PAX@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _avcodec_alloc_context3 referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _avcodec_open2 referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _avcodec_close referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _av_init_packet referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _av_packet_unref referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _avcodec_find_encoder referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _avcodec_encode_video2 referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _av_opt_set referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>Camera.obj : error LNK2019 : unresolved external symbol _av_image_alloc referenced in function __catch$ ?NewFrameReceived@Camera@MicroDFV_Camera@@AAEXKKKGPAE@Z$0
1>M :\Desktop\OpenCVTest\Debug\OpenCVTest.exe : fatal error LNK1120 : 14 unresolved externalsSearching here and on Google I found many recommendations, such as to add
#pragma comment(lib,...)
, and that the libs are static, so their order is important, and none of this helps.So I scratched my head even more and realized that the Zeranoe build is made with MinGW-w64, so probably it won’t link with Visual Studio. I inspected the lib using
dumpbin
and the symbols on the libs don’t have the underscore, so I am pretty sure it won’t work.The other Zeranoe builds for Windows don’t have libs, they are just plain .exe or exe + .dll.
Will I have to make my own VS2013 build of FFmpeg to link it, or is there some alternative way ?