Recherche avancée

Médias (91)

Autres articles (47)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Configuration spécifique pour PHP5

    4 février 2011, par

    PHP5 est obligatoire, vous pouvez l’installer en suivant ce tutoriel spécifique.
    Il est recommandé dans un premier temps de désactiver le safe_mode, cependant, s’il est correctement configuré et que les binaires nécessaires sont accessibles, MediaSPIP devrait fonctionner correctement avec le safe_mode activé.
    Modules spécifiques
    Il est nécessaire d’installer certains modules PHP spécifiques, via le gestionnaire de paquet de votre distribution ou manuellement : php5-mysql pour la connectivité avec la (...)

  • 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

Sur d’autres sites (5289)

  • Consume FFmpeg XCFramework from Objective-C, headers not found

    19 novembre 2020, par jamone

    I built FFmpeg for Apple's platforms as an XCFramework. I used the script in https://github.com/kewlbear/FFmpeg-iOS-build-script/pull/147 to do so.

    



    I'm trying to now consume that framework inside a traditional iOS/macOS framework (named VideoEditing), that then is used inside my iOS app (soon to try and be Catalyst).

    



    In VideoEditing I have linked to FFmpeg.xcframework and then in the app that uses VideoEditing I have linked & embedded FFmpeg.xcframework. Previously I was building FFmpeg as a standard static library, and using that from inside VideoEditing in a Objective-C++ wrapper so I can use it all from Swift.

    



    In that Objective-C++ file I would import FFmpeg headers like #import <libswscale></libswscale>swscale.h> To make that work, I had to set header search paths. How are you supposed to do it once you convert to the XCFramework ? I've tried @import FFmpeg, #import <ffmpeg></ffmpeg>libswscale/swscale.h>, #import <ffmpeg></ffmpeg>swscale.h> as well as #import <libswscale></libswscale>swscale.h>. In every case I just get a file not found error on the import line.

    &#xA;&#xA;

    All of Apple's examples are showing it just in Swift with the framework vending a module. If I was to try and still set a header search path, you now have different headers per architecture.

    &#xA;&#xA;

    Overview of contents of XCFramework

    &#xA;

  • Java process use more memory than VisualVM shows

    16 juillet 2021, par Dinexpod

    my java application works 1 day,&#xA;(I use different libs for processing photo like ffmpeg, javacv, javacpp)&#xA;and then I see that my app use 9,5Gb RAM.

    &#xA;

    system monitoring tools

    &#xA;

    I don't understand why my app use so a lot of memory.

    &#xA;

    I set -Xmx6G

    &#xA;

    In VisualVM I see that heap space size 188M

    &#xA;

    heap space in visualVM

    &#xA;

    Meta Space use 141M

    &#xA;

    metaspace in visualVM

    &#xA;

    May be this helps

    &#xA;

    allocated bytes in visualVM

    &#xA;

    I read articles that Java use more RAM than heap space because there are JIT, Heap space, meta space, code, ant etc. But 9.5Gb is a lot of on my mind

    &#xA;

    Edited :

    &#xA;

      &#xA;
    • Yes my app some times have exceptions java.lang.OutOfMemoryError : Java heap space
    • &#xA;

    &#xA;

  • What is the difference between yuv420p and yuv420p(tv) ?

    9 novembre 2018, par Aleksandr Shemetillo

    I am trying to implement Fairplay ready browser player (Apple’s DRM).
    A stream that has h264(Main) yuv420p(tv) settings becomes non-working after drm decryption (crashed picture of green color). Converting again the video with a "Main" ffmpeg profile changes the setting to a simple yuv420 and this solves the problem.
    Please explain the difference.
    Or maybe some other changes I don’t see can happen during the conversion ?

    Of course, since we are talking about Fairplay, the problem is observed in Safari on Os X