Recherche avancée

Médias (1)

Mot : - Tags -/pirate bay

Autres articles (79)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (10318)

  • Matomo 2 reaches end of life soon (December 2017), update now !

    7 décembre 2017, par Matomo Core Team — Community

    In less than three weeks, Matomo (Piwik) 2 will be no longer supported. This means that no further (security) updates will be released for this version. As per our Long Term Support announcement, Matomo 2.X is supported for 12 months after the initial release of Matomo 3.0.0 which was on December 18th 2016. Therefore, Matomo 2 will no longer receive any updates after December 18th 2017.

    It has been almost a year since we released Matomo (Piwik) 3 and we highly recommend updating to Matomo 3 ASAP. The major new release came with a new UI, performance and security improvements. If you are still on Matomo 2, the security improvements alone should be worth updating your Matomo to Matomo 3 now. We cannot recommend this enough.

    The update to Matomo (Piwik) 3 should be smooth, but may take a while depending on the amount of data you have.

    • If you have any problem with the update, feel free to get in touch with us, or ask in the forums.
    • If you are currently using Matomo (Piwik) self-hosted and would like to be upgraded, plus your Matomo managed in the official Cloud-hosted service, contact InnoCraft Cloud and they will migrate your database.

    At Matomo (Piwik) and InnoCraft, the company of the makers of Matomo, we have seen many thousands of Matomo installations upgraded over the past year and look forward to an exciting future for Matomo 3 and beyond !

  • lavc/aarch64/h264dsp_init_aarch64 : Fix weight function prototypes.

    21 janvier 2018, par Carl Eugen Hoyos
    lavc/aarch64/h264dsp_init_aarch64 : Fix weight function prototypes.

    Fixes the following warnings :
    
libavcodec/aarch64/h264dsp_init_aarch64.c : In function ‘ff_h264dsp_init_aarch64’ :
    
libavcodec/aarch64/h264dsp_init_aarch64.c:84:38 : warning : assignment from incompatible pointer type [enabled by default]
    
         c->weight_h264_pixels_tab[0] = ff_weight_h264_pixels_16_neon ;
    
                                      ^
    
libavcodec/aarch64/h264dsp_init_aarch64.c:85:38 : warning : assignment from incompatible pointer type [enabled by default]
    
         c->weight_h264_pixels_tab[1] = ff_weight_h264_pixels_8_neon ;
    
                                      ^
    
libavcodec/aarch64/h264dsp_init_aarch64.c:86:38 : warning : assignment from incompatible pointer type [enabled by default]
    
         c->weight_h264_pixels_tab[2] = ff_weight_h264_pixels_4_neon ;
    
                                      ^
    
libavcodec/aarch64/h264dsp_init_aarch64.c:88:40 : warning : assignment from incompatible pointer type [enabled by default]
    
         c->biweight_h264_pixels_tab[0] = ff_biweight_h264_pixels_16_neon ;
    
                                        ^
    
libavcodec/aarch64/h264dsp_init_aarch64.c:89:40 : warning : assignment from incompatible pointer type [enabled by default]
    
         c->biweight_h264_pixels_tab[1] = ff_biweight_h264_pixels_8_neon ;
    
                                        ^
    
libavcodec/aarch64/h264dsp_init_aarch64.c:90:40 : warning : assignment from incompatible pointer type [enabled by default]
    
         c->biweight_h264_pixels_tab[2] = ff_biweight_h264_pixels_4_neon ;
    
                                        ^
    • [DH] libavcodec/aarch64/h264dsp_init_aarch64.c

  • Building FFMPEGINTEROP with Visual Studio 2017 ?

    25 septembre 2018, par Francois Gagnon

    I’m working on a project that requires a video player. I’ve been using the standard UWP MediaPlayerElement but it refuses to read many types of videos, including ASF and FLV and some older MPG.

    I’ve read that ffmpeginterop is more compatible with a variety of codecs. However building it is a finicky and all the instructions are designed for VS2015 and command prompt for ARM processor, which does not exist for VS2017. I can’t find an updated version of the instructions (Left a message on their GIT site as well... no answers).

    So my question is two-fold :

    1. Is there any way to download the missing/updated codecs to include them in my project that uses the standard UWP approach ?

    2. Is there an updated way/tutorial/instructions of building ffmpeginterop with VS2017 ?

    3. Is ffmpeginterop too old and I should not build using it going forward ?

    Thanks !

Navigation