Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (21)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

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

  • French CNIL recommends Piwik : the only analytics tool that does not require Cookie Consent

    29 octobre 2014, par Matthieu Aubry — Press Releases

    There has been recent and important changes in France regarding data privacy and the use of cookies. This blog post will introduce you to these changes and explain how you make your website compliant.

    Cookie Consent in the data freedom law

    Since the adoption of the EU Directive 2009/136/EC “Telecom Package”, Internet users must be informed and provide their prior consent to the storage of cookies on their computer. The use of cookies for advertising, analytics and social share buttons require the user’s consent :

    It is necessary to inform users of the presence, purpose and duration of the cookies placed in their browsers, and the means at their disposal to oppose it.

    What is a cookie ?

    Cookies are tracers placed on Internet users’ hard drives by the web hosts of the visited website. They allow the website to identify a single user across multiple visits with a unique identifier. Cookies may be used for various purposes : building up a shopping cart, storing a website’s language settings, or targeting advertising by monitoring the user’s web-browsing.

    Which cookies are exempt from the Cookie Consent rule ?

    France has exempted certain cookies from the cookie consent rule : for those cookies that are strictly necessary to offer the service sought after by the user you do not need to ask consent to user. Examples of such cookies are :

    • the shopping cart cookie,
    • authentication cookies,
    • short lived session cookies,
    • load balancer cookies,
    • certain first party analytics (such as Piwik cookies),
    • persistent cookies for interface personalisation.

    Asking users for consent for Analytics (tracking) Cookies

    For all cookies that are not exempted from the Cookie Consent then you will need to :

    • obtain consent from web users before placing or reading cookies and similar technologies,
    • clearly inform web users of the different purposes for which the cookies and similar technologies will be used,
    • propose a real choice to web users between accepting or refusing cookies and similar technologies.

    You don’t need Cookie Consent with Piwik

    The excellent news is that there is a way to bypass the Cookie Consent banner on your website :

    If you are using another analytics solution other than Piwik then you will need to ask users for consent. If you do not want to ask for consent then download and install Piwik or signup to Piwik Cloud to get started.

    If you are already using Piwik you need to do two simple things : (1) anonymise visitor IP addresses (at least two bytes) and (2) include the opt-out iframe solution in your website (learn more).

    Note that these recommendations currently only apply in France, but because the law is European we can expect similar findings in other European countries.

    CNIL recommends Piwik

    We are proud that the CNIL has identified Piwik as the only tool that respects all privacy requirements set by the European Telecom law.

    About the CNIL

    The CNIL is an independent administrative body that operates in accordance with the French data protection legislation. The CNIL has been entrusted with the general duty to inform people of the rights that the data protection legislation allows them.

    The role and responsabilities of the CNIL are :

    • to protect citizens and their data
    • to regulate and control processing of personal data
    • to inspect the security of data processing systems and applications, and impose penalties

    Piwik and Privacy

    At Piwik we love Privacy – our open analytics platform comes with built-in Privacy.

    Future of Privacy at Piwik

    Piwik is already the leader when it comes to respecting user privacy but we plan to continue improving privacy within the open analytics platform. For more information and specific ideas see Privacy enhancing issues in our issue tracker.

    References

    Learn more in these articles in French [fr] or English :

    Contact

    To learn more about Piwik, please visit piwik.org,

    Get in touch with the Piwik team : Contact information,

    For professional support contact Piwik PRO.

  • arm-linux-androideabi/bin/ld : error : cannot find -lpolarssl while compiling rtmp library for Android (host os -Debian)

    24 octobre 2014, par trololo

    I’m trying to build rtmp library for ffmpeg for my Android app.
    In order to compile ffmpeg I have to compile rtmp-library.
    For librtmp.a I need to compile polarssl. I got polarssl library (libpolarssl, -lpolarssl)
    script for polarssl :

    #!/bin/bash
    ANDROID_NDK=/home/sla/work/android-ndk-r10b86/android-ndk-r10b/
    TOOLCHAIN=/home/sla/ffmpeg_build/polarssl/
    $ANDROID_NDK/build/tools/make-standalone-toolchain.sh --toolchain=arm-linux-androideabi-4.8 \
     --system=linux-x86 --platform=android-3 --install-dir=$TOOLCHAIN
    cd /home/sla/ffmpeg_sources/polarssl-1.2.11

    export CROSS_COMPILE=arm-linux-androideabi
    export CC="${CROSS_COMPILE}-gcc"
    export CXX="${CROSS_COMPILE}-g++"

    export PATH=$TOOLCHAIN/bin:$PATH
    #export CC="arm-linux-androideabi-gcc"
    #export CXX="arm-linux-androideabi-g++"
    export LD=arm-linux-androideabi-ld
    export STRIP=arm-linux-androideabi-strip

    export CFLAGS="-std=c99 -O3 -Wall -mthumb -pipe -fpic -fasm \
     -march=armv7-a -mfpu=neon -mfloat-abi=hard -mvectorize-with-neon-quad \
     -finline-limit=300 -ffast-math -fmodulo-sched -fmodulo-sched-allow-regmoves \
     -mhard-float -D_NDK_MATH_NO_SOFTFP=1 -fdiagnostics-color=always \
     -Wno-psabi -Wa,--noexecstack \
     -D__ARM_ARCH_5__ -D__ARM_ARCH_5E__ -D__ARM_ARCH_5T__ -D__ARM_ARCH_5TE__ \
     -DANDROID -DNDEBUG"

    export LDFLAGS="-lm_hard -lz -Wl,--no-undefined -Wl,-z,noexecstack -Wl,--fix-cortex-a8 -Wl,--no-warn-mismatch"
    #cd /home/sla/ffmpeg_sources
    #autoreconf -fiv
    #./configure --host=arm-linux-androideabi --prefix="`pwd`/build/"
    #--disable-shared
    #rm -r build
    make lib -j7 SYS=android CC="$CC" APP=
    make install DESTDIR=/home/sla/ffmpeg_sources/polarssl

    It works fine and creates correspond lirary but when I try to compile rtmplib (rtmpdump) using script

    #!/bin/bash
    ANDROID_NDK=/home/sla/work/android-ndk-r10b86/android-ndk-r10b/
    TOOLCHAIN=/home/sla/ffmpeg_build/rtmp/
    $ANDROID_NDK/build/tools/make-standalone-toolchain.sh --toolchain=arm-linux-androideabi-4.8 \
     --system=linux-x86 --platform=android-3 --install-dir=$TOOLCHAIN
    cd /home/sla/ffmpeg_sources/rtmpdump

    export CROSS_COMPILE=arm-linux-androideabi
    #export CC=${CROSS_COMPILE}-gcc
    #export CXX=${CROSS_COMPILE}-g++

    export PATH=$TOOLCHAIN/bin:$PATH
    export CC="arm-linux-androideabi-gcc"
    export CXX="arm-linux-androideabi-g++"
    export LD=arm-linux-androideabi-ld
    export STRIP=arm-linux-androideabi-strip

    export CFLAGS="-std=c99 -O3 -Wall -mthumb -pipe -fpic -fasm \
     -march=armv7-a -mfpu=neon -mfloat-abi=hard -mvectorize-with-neon-quad \
     -finline-limit=300 -ffast-math -fmodulo-sched -fmodulo-sched-allow-regmoves \
     -mhard-float -D_NDK_MATH_NO_SOFTFP=1 -fdiagnostics-color=always \
     -Wno-psabi -Wa,--noexecstack \
     -D__ARM_ARCH_5__ -D__ARM_ARCH_5E__ -D__ARM_ARCH_5T__ -D__ARM_ARCH_5TE__ \
     -DANDROID -DNDEBUG"

    export LDFLAGS="-lm_hard -lz -Wl,--no-undefined -Wl,-z,noexecstack -Wl,--fix-cortex-a8 -Wl,--no-warn-mismatch"
    #cd /home/sla/ffmpeg_sources
    #autoreconf -fiv
    #./configure --host=arm-linux-androideabi --prefix="`pwd`/build/"
    #--disable-shared
    rm -r build
    make -j7 SYS=android CROSS_COMPILE=arm-linux-androideabi- INC="-I/home/sla/ffmpeg_sources/polarssl-1.2.11/include/ -L/home/sla/ffmpeg_sources/polarssl-1.2.11/library/" CRYPTO=POLARSSL SHARED=
    make install
    make distclean

    I recieve such error :

    /home/sla/ffmpeg_build/rtmp/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lpolarssl

    More :

    Copying prebuilt binaries...
    Copying sysroot headers and libraries...
    Copying c++ runtime headers and libraries...
    Copying files to: /home/sla/ffmpeg_build/rtmp/
    Cleaning up...
    Done.
    rm: cannot remove `build': No such file or directory
    make[1]: Entering directory `/home/sla/ffmpeg_sources/rtmpdump/librtmp'
    make[1]: Nothing to be done for `all'.
    make[1]: Leaving directory `/home/sla/ffmpeg_sources/rtmpdump/librtmp'
    arm-linux-androideabi-gcc -Wall  -o rtmpdump rtmpdump.o -Llibrtmp -lrtmp -lpolarssl -lz  
    arm-linux-androideabi-gcc -Wall  -o rtmpgw rtmpgw.o thread.o  -Llibrtmp -lrtmp -lpolarssl -lz  
    arm-linux-androideabi-gcc -Wall  -o rtmpsrv rtmpsrv.o thread.o  -Llibrtmp -lrtmp -lpolarssl -lz  
    arm-linux-androideabi-gcc -Wall  -o rtmpsuck rtmpsuck.o thread.o  -Llibrtmp -lrtmp -lpolarssl -lz  
    /home/sla/ffmpeg_build/rtmp/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lpolarssl
    librtmp/librtmp.a(rtmp.o):rtmp.c:function isValidPublicKey: error: undefined reference to 'mpi_init'
    librtmp/librtmp.a(rtmp.o):rtmp.c:function isValidPublicKey: error: undefined reference to 'mpi_lset'
    librtmp/librtmp.a(rtmp.o):rtmp.c:function isValidPublicKey: error: undefined reference to 'mpi_cmp_mpi'
    librtmp/librtmp.a(rtmp.o):/rtmp.c:function homeisValidPublicKey/:sla /errorffmpeg_build:/ rtmpundefined/ binreference/ .to. /'libmpi_copy/'gcc
    /librtmparm/-librtmp.alinux(-rtmp.oandroideabi)/:4.8rtmp.c/:.function. /isValidPublicKey.:. /error.:. /undefined. .reference/ armto- linux'-mpi_sub_intandroideabi'/
    binlibrtmp//ldlibrtmp.a:( rtmp.oerror):: rtmp.ccannot: functionfind  isValidPublicKey-:lpolarssl
    errorlibrtmp:/ librtmp.aundefined( rtmp.oreference) :tortmp.c :'functionmpi_cmp_mpi 'isValidPublicKey
    :librtmp /errorlibrtmp.a:( rtmp.oundefined) :referencertmp.c :tofunction  'isValidPublicKeympi_init:'
    errorlibrtmp:/ librtmp.aundefined( rtmp.oreference) :tortmp.c :'functionmpi_exp_mod 'isValidPublicKey
    :librtmp /errorlibrtmp.a:( rtmp.oundefined) :referencertmp.c :tofunction  'isValidPublicKeympi_lset:'
    errorlibrtmp:/ librtmp.aundefined( rtmp.oreference) :tortmp.c :'functionmpi_cmp_int 'isValidPublicKey
    :librtmp /errorlibrtmp.a:( rtmp.oundefined) :referencertmp.c :tofunction  'isValidPublicKeympi_cmp_mpi:'
    errorlibrtmp:/ librtmp.aundefined( rtmp.oreference) :tortmp.c :'functionmpi_free 'isValidPublicKey
    :librtmp /errorlibrtmp.a:( rtmp.oundefined) :referencertmp.c :tofunction  'DHGenerateKeympi_copy:'
    errorlibrtmp:/ librtmp.aundefined( rtmp.oreference) :tortmp.c :'functionmpi_copy 'isValidPublicKey
    :librtmp /errorlibrtmp.a:( rtmp.oundefined) :referencertmp.c :tofunction  'DHGenerateKeympi_sub_int:'
    errorlibrtmp:/ librtmp.aundefined( rtmp.oreference) :tortmp.c :'functionmpi_copy 'isValidPublicKey
    :librtmp /errorlibrtmp.a:( rtmp.oundefined) :referencertmp.c :tofunction  'DHGenerateKeympi_cmp_mpi:'

    ETC..... A LOT OF ERRORS

    Hot to fix this error ?

  • Add partial_tukey and punchout_tukey apodization functions

    10 août 2014, par Martijn van Beurden
    Add partial_tukey and punchout_tukey apodization functions
    

    Adds two new apodization functions that seem to perform better than
    the apodization functions currently in the codebase and fixes three
    existing windows as well.

    Its important to note that this patch only affects the encoder stage
    that evaluates various possible predictors. Audio encoded with these
    new windows will still decode with existing legacy decoders.

    = Theory =
    These functions are used to window the audio data at the predictor
    stage. These news functions enable the use of only part of the signal
    to generate a predictor. This helps because short transients can
    introduce noise into the predictor. The predictor becomes very good
    at prediciting one part of the signal, instead of mediocre for the
    whole block.

    Signed-off-by : Erik de Castro Lopo <erikd@mega-nerd.com>

    • [DH] doc/html/documentation_tools_flac.html
    • [DH] include/FLAC/stream_encoder.h
    • [DH] man/flac.1
    • [DH] man/flac.sgml
    • [DH] src/libFLAC/include/private/window.h
    • [DH] src/libFLAC/include/protected/stream_encoder.h
    • [DH] src/libFLAC/stream_encoder.c
    • [DH] src/libFLAC/window.c