Recherche avancée

Médias (0)

Mot : - Tags -/albums

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

Autres articles (90)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

  • Mediabox : ouvrir les images dans l’espace maximal pour l’utilisateur

    8 février 2011, par

    La visualisation des images est restreinte par la largeur accordée par le design du site (dépendant du thème utilisé). Elles sont donc visibles sous un format réduit. Afin de profiter de l’ensemble de la place disponible sur l’écran de l’utilisateur, il est possible d’ajouter une fonctionnalité d’affichage de l’image dans une boite multimedia apparaissant au dessus du reste du contenu.
    Pour ce faire il est nécessaire d’installer le plugin "Mediabox".
    Configuration de la boite multimédia
    Dès (...)

Sur d’autres sites (7362)

  • What is data anonymization in web analytics ?

    11 février 2020, par Joselyn Khor — Analytics Tips, Privacy

    Collecting information via web analytics platforms is needed to help a website grow and improve. When doing so, it’s best to strike a balance between getting valuable insights, and keeping the trust of your users by protecting their privacy.

    This means not collecting or processing any personally identifiable information (PII). But what if your organisation requires you to collect PII ?

    That’s where data anonymization comes in.

    What is data anonymization ?

    Data anonymization makes identifiable information unidentifiable. This is done through data processing techniques which remove or modify PII data. So data becomes anonymous and can’t be linked to any individual.

    In the context of web analytics, data anonymization is handy because you can collect useful data while protecting the privacy of website visitors.

    Why is data anonymization important ?

    Through modern threats of identity theft, credit card fraud and the like, data anonymization is a way to protect the identity and privacy of individuals. As well as protect private and sensitive information of organisations. 

    Data anonymization lets you follow the many laws around the world which protect user privacy. These laws provide safeguards around collecting personal data or personally identifiable information (PII), so data anonymization is a good solution to ensure you’re not processing such sensitive information.

    In some cases, implementing data anonymization techniques means you can avoid having to show your users a consent screen. Which means you may not need to ask for consent in order to track data. This is a bonus as consent screens can annoy and stop people from engaging with your site.

    GDPR and data anonymization

    Matomo Analytics GDPR Google Analytics

    The GDPR is a law in the EU that limits the collection and processing of personal data. The aim is to give people more control over their online personal information. Which is why website owners need to follow certain rules to become GDPR compliant and protect user privacy. According to the GDPR, you can be fined up to 4% of your yearly revenue for data breaches or non-compliance. 

    In the case of web analytics, tools can be easily made compliant by following a number of steps

    This is why anonymizing data is a big deal.

    Anonymized data isn’t personal data according to the GDPR : 

    “The principles of data protection should therefore not apply to anonymous information, namely information which does not relate to an identified or identifiable natural person or to personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable.”

    This means, you still get the best of both worlds. By anonymizing data, you’re still able to collect useful information like visitor behavioural data.

    US privacy laws and data anonymization

    In the US, there isn’t one single law that governs the protection of personal data, called personally identifiable information (PII). There are hundreds of federal and state laws that protect the personal data of US residents. As well as, industry-specific statutes related to data privacy, like the California Consumer Privacy Act (CCPA) and the Health Insurance Portability and Accountability Act (HIPAA).

    Website owners in the US need to know exactly what laws govern their area of business in order to follow them.

    A general guideline is to protect user privacy regardless of whether you are or aren’t allowed to collect PII. This means anonymizing identifiable information so your website users aren’t put at risk.

    Data anonymization techniques in Matomo Analytics

    If you carry these out, you won’t need to ask your website visitors for tracking consent since anonymized data is no longer considered personal data under the GDPR.

    The techniques listed above make it easy for you when using a tool like Matomo, as they are automatically anonymized.

    Tools like Google Analytics on the other hand don’t provide some of the privacy options and leave it up to you to take on the burden of implementation without providing steps.

    Data anonymization tools

    If you’re a website owner who wants to grow your business or learn more about your website visitors, privacy-friendly tools like Matomo Analytics are a great option. By following the easy steps to be GDPR compliant, you can anonymize all data that could put your visitors at risk.

  • FFMPEG command on Android Jave Process does fully execute

    8 novembre 2014, par user2491598

    The issue I am having is very strange. I have an FFMPEG executable binary library installed on my Android and I am trying to execute this command

    ffmpeg -loop 1 -i /storage/emulated/0/image.jpg -i /storage/emulated/0/input.mov -filter_complex '[0:v][1:v] overlay' -shortest /storage/emulated/0/output.mp4

    and my JAVA code looks like

    try {
               Runtime.getRuntime().exec("chmod 700 " + mFfmpegPath);
               cmd.add(mFfmpegPath);
               cmd.add("-loop");
               cmd.add("1");
               cmd.add("-i");
               cmd.add("/storage/emulated/0/image.jpg");
               cmd.add("-i");
               cmd.add("/storage/emulated/0/pizza.mov");
               cmd.add("-filter_complex");
               cmd.add("'[0:v][1:v] overlay'");
               cmd.add("-shortest");
               cmd.add("-vcodec");
               cmd.add("-libx264");
               cmd.add("-strict");
               cmd.add("experimental");
               cmd.add("/storage/emulated/0/output22.mp4");

               final ProcessBuilder pb = new ProcessBuilder(cmd);
               pb.redirectErrorStream();
               ProcessRunnable run =  new ProcessRunnable(pb);
               final Process p = pb.start();
               Log.i("FFMPEG","stdError= " + getSTD(p.getErrorStream()));
               p.waitFor();
               return run;
           } catch (IOException e1) {
               // TODO Auto-generated catch block
               e1.printStackTrace();
           } catch (InterruptedException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
           }

    For some reason I the execution does not fully finish and it stops. It does not even create an output file in my Android storage. Here is the log file from the process stream

    11-07 20:34:21.636: I/FFMPEG(6259): stdError= WARNING: linker: /data/data/za.jamie.androidffmpegcmdline/app_bin/ffmpeg has text relocations. This is wasting memory and is a security risk. Please fix.
    11-07 20:34:21.636: I/FFMPEG(6259): ffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
    11-07 20:34:21.636: I/FFMPEG(6259):   built on Nov  8 2014 00:21:33 with gcc 4.8 (GCC)
    11-07 20:34:21.636: I/FFMPEG(6259):   configuration: --target-os=linux --cross-prefix=/home/ubuntu/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/ubuntu/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-avcodec --enable-avformat --enable-swresample --enable-swscale --enable-postproc --enable-avfilter --enable-avresample --disable-libfreetype --enable-libfribidi --disable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --enable-ffplay --enable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/ubuntu/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/ubuntu/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/home/ubuntu/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/home/ubuntu/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
    11-07 20:34:21.636: I/FFMPEG(6259):   libavutil      54.  7.100 / 54.  7.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libavcodec     56.  1.100 / 56.  1.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libavformat    56.  4.101 / 56.  4.101
    11-07 20:34:21.636: I/FFMPEG(6259):   libavdevice    56.  0.100 / 56.  0.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libavfilter     5.  1.100 /  5.  1.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libavresample   2.  1.  0 /  2.  1.  0
    11-07 20:34:21.636: I/FFMPEG(6259):   libswscale      3.  0.100 /  3.  0.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libswresample   1.  1.100 /  1.  1.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libpostproc    53.  0.100 / 53.  0.100
    11-07 20:34:21.636: I/FFMPEG(6259): Input #0, image2, from '/storage/emulated/0/image.jpg':
    11-07 20:34:21.636: I/FFMPEG(6259):   Duration: 00:00:00.04, start: 0.000000, bitrate: 35211 kb/s
    11-07 20:34:21.636: I/FFMPEG(6259):     Stream #0:0: Video: mjpeg, yuvj420p(pc, bt470bg), 640x640 [SAR 1:1 DAR 1:1], 25 fps, 25 tbr, 25 tbn, 25 tbc
    11-07 20:34:21.636: I/FFMPEG(6259): Input #1, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/input.mov':
    11-07 20:34:21.636: I/FFMPEG(6259):   Metadata:
    11-07 20:34:21.636: I/FFMPEG(6259):     major_brand     : qt  
    11-07 20:34:21.636: I/FFMPEG(6259):     minor_version   : 537199360
    11-07 20:34:21.636: I/FFMPEG(6259):     compatible_brands: qt  
    11-07 20:34:21.636: I/FFMPEG(6259):     creation_time   : 2014-10-30 23:57:31
    11-07 20:34:21.636: I/FFMPEG(6259):     xmp             : <?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
    11-07 20:34:21.636: I/FFMPEG(6259):                     :
    11-07 20:34:21.636: I/FFMPEG(6259):                     :  
    11-07 20:34:21.636: I/FFMPEG(6259):                     :   FFMPEG(6259):                     :     xmlns:xmp="http://ns.adobe.com/xap/1.0/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:xmpDM="http://ns.adobe.com/xmp/1.0/DynamicMedia/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:stDim="http://ns.adobe.com/xap/1.0/sType/Dimensions#"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:stEvt="http://ns.adobe.com/xap/1.0/sType/ResourceEvent#"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:creatorAtom="http://ns.adobe.com/creatorAtom/1.0/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:dc="http://purl.org/dc/elements/1.1/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmp:CreateDate="2014-10-30T16:57:31-07:00"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmp:ModifyDate="2014-10-30T15:57:57-07:00"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmp:CreatorTool="Adobe After Effects CC 2014 (Windows)"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmp:MetadataDate="2014-10-30T15:57:57-07:00"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:startTimeScale="30"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:startTimeSampleSize="1"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:videoFrameRate="30.000000"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:videoFieldOrder="Progressive"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:videoPixelAspectRatio="1/1"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:audioSampleRate="48000"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:audioSampleType="16Int"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:audioChannelType="Stereo"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpMM:InstanceID="xmp.iid:b791d2dc-6759-ee45-b5a2-692ecba2c4fd"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpMM:DocumentID="xmp.did:d3fde073-8716-144a-acbd-7676f27002a0"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpMM:OriginalDocumentID="xmp.
    11-07 20:34:21.836: E/ViewRootImpl(6259): sendUserActionEvent() mView == null

    Please help :(

  • FFMPEG command on Android Jave Process does not fully execute

    8 novembre 2014, par user2491598

    The issue I am having is very strange. I have an FFMPEG executable binary library installed on my Android and I am trying to execute this command

    ffmpeg -loop 1 -i /storage/emulated/0/image.jpg -i /storage/emulated/0/input.mov -filter_complex '[0:v][1:v] overlay' -shortest /storage/emulated/0/output.mp4

    and my JAVA code looks like

    try {
               Runtime.getRuntime().exec("chmod 700 " + mFfmpegPath);
               cmd.add(mFfmpegPath);
               cmd.add("-loop");
               cmd.add("1");
               cmd.add("-i");
               cmd.add("/storage/emulated/0/image.jpg");
               cmd.add("-i");
               cmd.add("/storage/emulated/0/pizza.mov");
               cmd.add("-filter_complex");
               cmd.add("'[0:v][1:v] overlay'");
               cmd.add("-shortest");
               cmd.add("-vcodec");
               cmd.add("-libx264");
               cmd.add("-strict");
               cmd.add("experimental");
               cmd.add("/storage/emulated/0/output22.mp4");

               final ProcessBuilder pb = new ProcessBuilder(cmd);
               pb.redirectErrorStream();
               final Process p = pb.start();
               Log.i("FFMPEG","stdError= " + getSTD(p.getErrorStream()));
               p.waitFor();
               return run;
           } catch (IOException e1) {
               // TODO Auto-generated catch block
               e1.printStackTrace();
           } catch (InterruptedException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
           }

    For some reason I the execution does not fully finish and it stops. It does not even create an output file in my Android storage. Here is the log file from the process stream

    11-07 20:34:21.636: I/FFMPEG(6259): stdError= WARNING: linker: /data/data/za.jamie.androidffmpegcmdline/app_bin/ffmpeg has text relocations. This is wasting memory and is a security risk. Please fix.
    11-07 20:34:21.636: I/FFMPEG(6259): ffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
    11-07 20:34:21.636: I/FFMPEG(6259):   built on Nov  8 2014 00:21:33 with gcc 4.8 (GCC)
    11-07 20:34:21.636: I/FFMPEG(6259):   configuration: --target-os=linux --cross-prefix=/home/ubuntu/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/ubuntu/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-avcodec --enable-avformat --enable-swresample --enable-swscale --enable-postproc --enable-avfilter --enable-avresample --disable-libfreetype --enable-libfribidi --disable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --enable-ffplay --enable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/ubuntu/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/ubuntu/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/home/ubuntu/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/home/ubuntu/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
    11-07 20:34:21.636: I/FFMPEG(6259):   libavutil      54.  7.100 / 54.  7.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libavcodec     56.  1.100 / 56.  1.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libavformat    56.  4.101 / 56.  4.101
    11-07 20:34:21.636: I/FFMPEG(6259):   libavdevice    56.  0.100 / 56.  0.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libavfilter     5.  1.100 /  5.  1.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libavresample   2.  1.  0 /  2.  1.  0
    11-07 20:34:21.636: I/FFMPEG(6259):   libswscale      3.  0.100 /  3.  0.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libswresample   1.  1.100 /  1.  1.100
    11-07 20:34:21.636: I/FFMPEG(6259):   libpostproc    53.  0.100 / 53.  0.100
    11-07 20:34:21.636: I/FFMPEG(6259): Input #0, image2, from '/storage/emulated/0/image.jpg':
    11-07 20:34:21.636: I/FFMPEG(6259):   Duration: 00:00:00.04, start: 0.000000, bitrate: 35211 kb/s
    11-07 20:34:21.636: I/FFMPEG(6259):     Stream #0:0: Video: mjpeg, yuvj420p(pc, bt470bg), 640x640 [SAR 1:1 DAR 1:1], 25 fps, 25 tbr, 25 tbn, 25 tbc
    11-07 20:34:21.636: I/FFMPEG(6259): Input #1, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/input.mov':
    11-07 20:34:21.636: I/FFMPEG(6259):   Metadata:
    11-07 20:34:21.636: I/FFMPEG(6259):     major_brand     : qt  
    11-07 20:34:21.636: I/FFMPEG(6259):     minor_version   : 537199360
    11-07 20:34:21.636: I/FFMPEG(6259):     compatible_brands: qt  
    11-07 20:34:21.636: I/FFMPEG(6259):     creation_time   : 2014-10-30 23:57:31
    11-07 20:34:21.636: I/FFMPEG(6259):     xmp             : <?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
    11-07 20:34:21.636: I/FFMPEG(6259):                     :
    11-07 20:34:21.636: I/FFMPEG(6259):                     :  
    11-07 20:34:21.636: I/FFMPEG(6259):                     :   FFMPEG(6259):                     :     xmlns:xmp="http://ns.adobe.com/xap/1.0/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:xmpDM="http://ns.adobe.com/xmp/1.0/DynamicMedia/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:stDim="http://ns.adobe.com/xap/1.0/sType/Dimensions#"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:stEvt="http://ns.adobe.com/xap/1.0/sType/ResourceEvent#"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:creatorAtom="http://ns.adobe.com/creatorAtom/1.0/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :     xmlns:dc="http://purl.org/dc/elements/1.1/"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmp:CreateDate="2014-10-30T16:57:31-07:00"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmp:ModifyDate="2014-10-30T15:57:57-07:00"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmp:CreatorTool="Adobe After Effects CC 2014 (Windows)"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmp:MetadataDate="2014-10-30T15:57:57-07:00"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:startTimeScale="30"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:startTimeSampleSize="1"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:videoFrameRate="30.000000"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:videoFieldOrder="Progressive"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:videoPixelAspectRatio="1/1"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:audioSampleRate="48000"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:audioSampleType="16Int"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpDM:audioChannelType="Stereo"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpMM:InstanceID="xmp.iid:b791d2dc-6759-ee45-b5a2-692ecba2c4fd"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpMM:DocumentID="xmp.did:d3fde073-8716-144a-acbd-7676f27002a0"
    11-07 20:34:21.636: I/FFMPEG(6259):                     :    xmpMM:OriginalDocumentID="xmp.
    11-07 20:34:21.836: E/ViewRootImpl(6259): sendUserActionEvent() mView == null

    Please help :(