
Recherche avancée
Médias (91)
-
GetID3 - Boutons supplémentaires
9 avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
-
Core Media Video
4 avril 2013, par
Mis à jour : Juin 2013
Langue : français
Type : Video
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
-
Exemple de boutons d’action pour une collection collaborative
27 février 2013, par
Mis à jour : Mars 2013
Langue : français
Type : Image
-
Exemple de boutons d’action pour une collection personnelle
27 février 2013, par
Mis à jour : Février 2013
Langue : English
Type : Image
Autres articles (35)
-
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...) -
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
Sur d’autres sites (9281)
-
Can't link FFMPEG dynamically to VS 2019 project
10 février 2021, par Maya SelaI downloaded the source code of FFMPEG 3.4.8 and built with MSVC as such :

After unzipping, open x86_x64 Cross Tools Command Prompt for VS 2019 and runmsys2_shell.cmd
. From there, run

./configure --toolchain=msvc --arch=x86_64 --enable-yasm --enable-asm --enable-shared --disable-static

and
make



I then created a new project in VS 2019.

In Properties > C/C++ > General > Additional Include Directories :

(Where all the headers are)

E:\ffmpeg-3.4.8\libavutil
E:\ffmpeg-3.4.8\libavcodec
E:\ffmpeg-3.4.8\libavdevice
E:\ffmpeg-3.4.8\libavfilter
E:\ffmpeg-3.4.8\libavresample
E:\ffmpeg-3.4.8\libpostproc
E:\ffmpeg-3.4.8\libswscale
E:\ffmpeg-3.4.8\libswresample
E:\ffmpeg-3.4.8\libavformat



In Properties > Linker > General > Additional Library Directories :

(Where the .lib files are)

E:\ffmpeg-3.4.8\libavutil
E:\ffmpeg-3.4.8\libavcodec
E:\ffmpeg-3.4.8\libavdevice
E:\ffmpeg-3.4.8\libavfilter
E:\ffmpeg-3.4.8\libavresample
E:\ffmpeg-3.4.8\libpostproc
E:\ffmpeg-3.4.8\libswscale
E:\ffmpeg-3.4.8\libswresample
E:\ffmpeg-3.4.8\libavformat



In Properties > Linker > Input > Additional Dependencies :


avcodec.lib
avdevice.lib
avfilter.lib
avformat.lib
swresample.lib
swscale.lib



For good measure, I copied the .dll files of each library to the Release folder of the project. There is one source file I am trying to build and run :



extern "C" {
#include <libavformat></libavformat>avformat.h>
}

int main() {
 AVFormatContext* pFormatContext = avformat_alloc_context();
}



The result is as follows :


1>------ Build started: Project: FFMPEG_example, Configuration: Release x64 ------
1>Source.cpp
1>Source.obj : error LNK2001: unresolved external symbol avformat_alloc_context
1>C:\Users\maya.s\source\repos\FFMPEG_example\x64\Release\FFMPEG_example.exe : fatal error LNK1120: 1 unresolved externals
1>Done building project "FFMPEG_example.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========



Does anyone have an idea ?

Thanks !

-
Setup FFMpegCore in Visual Studio 2019
27 juillet 2022, par DsiakMondalaI am confused on the basics of using a library. I understand that there is a library called FFMpeg and a wrapper called FFMpegCore so we can use FFMpeg with C#, correct ? I downloaded both FFMpeg and FFMpegCore and I have them in my project's folder. Although I didn't perceive any class named FFMpegOptions in either of the file's folders.
I am stuck on how to actually set it up so I can use it in my little project, I never downloaded someone's library before. Can somebody please walk me though the motions of connecting the three of them together ?


So far I experimented with :


- 

- Add a reference to my project, but there doesn't seem to be any .dll, .tlb, .olb, .ocx or .exe files to add
- Add an existing project to my solution. There is a project called FFMpegCore.csproj but adding it raises a missing SDK error. Weirdly enough, opening the same project as a standalone doesn't raise any issues which makes me thing the operation I am trying is inadequate.






I am sure this is a silly and easy setup to perform but I just don't know enough to find a solution.


-
Unable to build solution in Visual Studio 2019 : The BaseOutputPath/OutputPath property is not set for project
23 juillet 2022, par mhadiIn an effort to integrate FFmpeg with Unity, I have been trying to build a solution file in Visual Studio 2019. However, I am currently unable to resolve the following error when I try to build in Visual Studio :




The BaseOutputPath/OutputPath property is not set for project
'FFmpegUnityInterop.vcxproj'. Please check to make sure that you have
specified a valid combination of Configuration and Platform for this
project. Configuration='Release' Platform='x64'. This error may
also appear if some other project is trying to follow a
project-to-project reference to this project, this project has been
unloaded or is not included in the solution, and the referencing
project does not build using the same or an equivalent Configuration
or Platform.




I have tried a number of solutions, including :


- 

- Manually adding the OutputPath in 'FFmpegUnityInterop.vcxproj'

<outputpath>bin/Build/</outputpath>
. - In the FFmpegUnityInterop.vcxproj file, moving the ProjectProperty with my preferred configuration and platform combination to the very top of the list of ProjectProperties (there are 8 of them).
- Building with different configuration and platforms.
- Trying to build from VS Dev Command prompt using the following command :

MSbuild.exe "FFmpegUnityInterop.sln" /p:Configuration=Release /p:Platform="x64"
, as well as from the Visual Studio IDE. - Tried setting the OutputPath in the command line command
(
>MSbuild.exe FFmpegUnityInterop.sln /p:Configuration=Release /p:Platform="AnyCPU" /p:OutputPath = bin\Debug
), only to have
MSbuild throw error MSB1008 (MSBUILD : error MSB1008 : Only one
project can be specified.) - Setting the configuration and platform manually in the Configuration Manager GUI in
Visual Studio.














I may have missed an attempted solution or two above, but I've tried most of the suggestions I found online, only to get the error pasted above. Part of me suspects that my compilation of FFmpeg libraries didn't execute fully, but I unfortunately do not have enough experience to verify that. Any suggestions to resolve this would be much appreciated.


PS. The project was developed privately by a private entity that is currently unreachable


- Manually adding the OutputPath in 'FFmpegUnityInterop.vcxproj'