Recherche avancée

Médias (91)

Autres articles (89)

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

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Librairies et logiciels spécifiques aux médias

    10 décembre 2010, par

    Pour un fonctionnement correct et optimal, plusieurs choses sont à prendre en considération.
    Il est important, après avoir installé apache2, mysql et php5, d’installer d’autres logiciels nécessaires dont les installations sont décrites dans les liens afférants. Un ensemble de librairies multimedias (x264, libtheora, libvpx) utilisées pour l’encodage et le décodage des vidéos et sons afin de supporter le plus grand nombre de fichiers possibles. Cf. : ce tutoriel ; FFMpeg avec le maximum de décodeurs et (...)

Sur d’autres sites (8205)

  • New cookie behaviour in browsers may cause regressions

    24 février 2020, par Matomo Core Team — Community, Development

    Last year the Chromium browser team announced they would change their default behaviour for cookies. In particular about a property called samesite. Over the last few months, we have made various changes to our cookie handling to get Matomo ready for this. Depending on your setup and the features you use, some things may not work anymore.

    You can avoid most of the issues by using HTTPS on your Matomo, and ideally also use HTTPS on your website(s).

    If you are not running the latest version of Matomo yet (3.13.3 at the time of writing), then we highly recommend that you upgrade as soon as possible. Previous versions are not compatible with these cookie browser changes.

    Opt out screen

    If you embed the opt out screen on your website running on HTTP, there is a chance the Matomo opt out no longer works. In these cases it may still work over http:

    • when the privacy policy page that embeds the opt out screen (via iframe) also has the Matomo JavaScript tracker embedded,
    • and when both the opt out and the JS tracker point to the same Matomo installation.

    In other cases when HTTP is used, the opt out feature will likely be broken.

    We recommend you test whether the opt out on your site still works by opening your privacy policy page in an incognito browser window. Then test to opt out of tracking, and then reload the page. If the checkbox “You are not opted out. Uncheck this box to opt out.” is still ticked, then your opt out is not working.

    If the opt out is not working anymore, it is most likely due to HTTP being used. In that case you should change the opt out URL to HTTPS. For example change from &lt;iframe src=”<strong>http://</strong>…” to &lt;iframe src=”<strong>https://</strong>...” . If your Matomo doesn’t support HTTPS yet, you will need to contact your webhoster or system administrator to get SSL enabled on your Matomo domain.

    JavaScript tracker

    In most cases, everything related to the JavaScript Tracker will still work as expected.

    But there is an edge case : when you are also reading Matomo’s cookie server side. You may be affected by this edge case issue when :

    • you track part of the user behaviour in the browser (using Matomo JS Tracker),
    • and also track user behavior in your server (for example using one of Matomo SDKs in PHP, Java, Python, C#, etc.).

    In that case, for you to still be able to read the so-called visitorId on your server, we recommend you add this line to your JS tracking code :

    _paq.push([‘setSecureCookie’, location.protocol === 'https:']);

    The cookie can be only retrieved if your website is loaded through HTTPS.

    Should you have any questions, or notice anything isn’t working as expected, please visit our forum.

    Third party cookies

    If you are using third party cookies, using HTTPS on your Matomo is now a requirement to make them work across different domains. Otherwise Chrome and in the near future other browsers would not accept the cookie. If you don’t know if you are using third party cookies or first party cookies, you’re likely using first party cookies and this does not affect you.

  • Anomalie #3212 : Problème function gzopen dans librairie PclZip

    6 mai 2014, par b b

    Avec le même environnement j’obtiens :

    bb@tybook : $ apt-cache policy php5
    php5 :
      Installé : 5.5.9+dfs- 1ubuntu4
      Candidat : 5.5.9+dfs- 1ubuntu4
     Table de version :
     *** 5.5.9+dfs- 1ubuntu4 0
            500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
            100 /var/lib/dpkg/status
    bb@tybook : $ php -r ’var_dump(function_exists("gzopen")) ;’
    bool(true)
    

    Je regarderai en détail plus tard, mais je pense que ça ne doit pas poser de problème.

  • Creating a thumbnail from MP4 video crashes on shared hosting but working fine locally

    15 juillet 2019, par Mariam Nagy

    i am working on a web page to upload MP4 video and getting a thumbnail from the video

    i am using NReco FFMpeg Converter to achieve this . it is working fine locally but upload it on a shared hosting it crashes at ffMpeg.GetVideoThumbnail

           string VideoUrl = dataMediaUrl.ImageUrl;
           string extension = VideoUrl.Split('.')[VideoUrl.Split('.').Length - 1];
           var ffMpeg = new NReco.VideoConverter.FFMpegConverter();
           string thumbnailJPEGpath = Server.MapPath(VideoUrl.Replace("~/upload/MediaGallery/", "~/upload/MediaGallery/Thumb_").Replace("." + extension, ".jpg"));
           ffMpeg.GetVideoThumbnail(Server.MapPath(VideoUrl), thumbnailJPEGpath);
           dataThumbUrl.ImageUrl = VideoUrl.Replace("~/upload/MediaGallery/", "~/upload/MediaGallery/Thumb_").Replace("." + extension, ".jpg");

    This is the error I am getting :

    Server Error in '/' Application.
    This program is blocked by group policy. For more information, contact your system administrator
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.ComponentModel.Win32Exception: This program is blocked by group policy. For more information, contact your system administrator

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:


    [Win32Exception (0x80004005): This program is blocked by group policy. For more information, contact your system administrator]
      System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) +1889
      System.Diagnostics.Process.Start() +119
      System.Diagnostics.Process.Start(ProcessStartInfo startInfo) +49
      NReco.VideoConverter.FFMpegConverter.ConvertMedia(Media input, Media output, ConvertSettings settings) +1163
      NReco.VideoConverter.FFMpegConverter.GetVideoThumbnail(String inputFile, String outputFile, Nullable`1 frameTime) +155
      Admin_MediaGalleryVideoUpload.InsertButton_Click(Object sender, EventArgs e) +591
      System.Web.UI.WebControls.Button.OnClick(EventArgs e) +9782698
      System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +204
      System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +12
      System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +15
      System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +35
      System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1639

    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3394.0