Recherche avancée

Médias (29)

Mot : - Tags -/Musique

Autres articles (38)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une 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 (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-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

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

Sur d’autres sites (9360)

  • CoCreateInstanceFromApp undefined with WinRT + Visual Studio 2013

    7 novembre 2014, par Hyndrix

    I am experimenting with ffmpeg and Windows RT (ARM). First I run configure in a MinGW/MSYS shell :

    ./configure --enable-shared --disable-static --toolchain=msvc --extra-cflags="-D_M_ARMM -D_ARM_WINAPI_PARTITION_DESKTOP_SDK_AVAILABLE -DWINAPI_FAMILY=WINAPI_FAMILY_APP" --enable-cross-compile --target-os=win32 --arch=win32 --extra-ldflags="-MACHINE:ARM" --arch=arm --cpu=armv7

    followed by a "make" (in the same shell) which ends with the following error :

    C:\Program Files (x86)\Windows Kits\8.1\include\um\combaseapi.h(1157) : 
    
error C4013: 'CoCreateInstanceFromApp' undefined; assuming extern returning int
    
make: *** [libavformat/format.o] Error 2

    The environmental variables in the shell are set to ARM Visual Studio 2013.

    What does this error mean ? Can someone point me in the correct direction how to fix this problem ?

    Regards,

  • avcodec/mpeg4videodec : Clear interlaced_dct for studio profile

    15 février 2019, par Michael Niedermayer
    avcodec/mpeg4videodec : Clear interlaced_dct for studio profile

    Fixes : Out of array access
    
Fixes : 13090/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_MPEG4_fuzzer-5408668986638336
    

    Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
    
Reviewed-by : Kieran Kunhya <kierank@obe.tv>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/mpeg4videodec.c

  • Unable to build solution in Visual Studio 2019 : The BaseOutputPath/OutputPath property is not set for project

    23 juillet 2022, par mhadi

    In 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 :

    &#xA;

    &#xA;

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

    &#xA;

    &#xA;

    I have tried a number of solutions, including :

    &#xA;

      &#xA;
    1. Manually adding the OutputPath in 'FFmpegUnityInterop.vcxproj'&#xA;<outputpath>bin/Build/</outputpath>.

      2. &#xA;

    2. 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).

      3. &#xA;

    3. Building with different configuration and platforms.

      4. &#xA;

    4. Trying to build from VS Dev Command prompt using the following command :&#xA;MSbuild.exe "FFmpegUnityInterop.sln" /p:Configuration=Release /p:Platform="x64", as well as from the Visual Studio IDE.

      5. &#xA;

    5. Tried setting the OutputPath in the command line command&#xA;(>MSbuild.exe FFmpegUnityInterop.sln /p:Configuration=Release /p:Platform="AnyCPU" /p:OutputPath = bin\Debug), only to have&#xA;MSbuild throw error MSB1008 (MSBUILD : error MSB1008 : Only one&#xA;project can be specified.)

      6. &#xA;

    6. Setting the configuration and platform manually in the Configuration Manager GUI in&#xA;Visual Studio.

      7. &#xA;

    &#xA;

    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.

    &#xA;

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

    &#xA;

Navigation