Recherche avancée

Médias (0)

Mot : - Tags -/metadatas

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (96)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • HTML5 audio and video support

    13 avril 2011, par

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

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (9220)

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

    


    


    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 :

    


      

    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;

  • Support Digital Voodoo SD 8 Bit in mov (ticket 195).

    13 mai 2011, par Carl Eugen Hoyos

    Support Digital Voodoo SD 8 Bit in mov (ticket 195).

  • mov : Support Digital Voodoo SD 8 Bit and DTS codec identifiers.

    13 mai 2011, par Carl Eugen Hoyos

    mov : Support Digital Voodoo SD 8 Bit and DTS codec identifiers.

Navigation