Recherche avancée

Médias (0)

Mot : - Tags -/xmp

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

Autres articles (101)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • Emballe Médias : Mettre en ligne simplement des documents

    29 octobre 2010, par

    Le plugin emballe médias a été développé principalement pour la distribution mediaSPIP mais est également utilisé dans d’autres projets proches comme géodiversité par exemple. Plugins nécessaires et compatibles
    Pour fonctionner ce plugin nécessite que d’autres plugins soient installés : CFG Saisies SPIP Bonux Diogène swfupload jqueryui
    D’autres plugins peuvent être utilisés en complément afin d’améliorer ses capacités : Ancres douces Légendes photo_infos spipmotion (...)

Sur d’autres sites (11616)

  • Video Conferencing in HTML5 : WebRTC via Socket.io

    http://mirror.linux.org.au/linux.conf.au/2013/mp4/Code_up_your_own_video_conference_in_HTML5.mp4
    1er janvier 2014, par silvia

    Six months ago I experimented with Web sockets for WebRTC and the early implementations of PeerConnection in Chrome. Last week I gave a presentation about WebRTC at Linux.conf.au, so it was time to update that codebase.

    I decided to use socket.io for the signalling following the idea of Luc, which made the server code even smaller and reduced it to a mere reflector :

     var app = require(’http’).createServer().listen(1337) ;
     var io = require(’socket.io’).listen(app) ;
    

    io.sockets.on(’connection’, function(socket)
    socket.on(’message’, function(message)
    socket.broadcast.emit(’message’, message) ;
    ) ;
    ) ;

    Then I turned to the client code. I was surprised to see the massive changes that PeerConnection has gone through. Check out my slide deck to see the different components that are now necessary to create a PeerConnection.

    I was particularly surprised to see the SDP object now fully exposed to JavaScript and thus the ability to manipulate it directly rather than through some API. This allows Web developers to manipulate the type of session that they are asking the browsers to set up. I can imaging e.g. if they have support for a video codec in JavaScript that the browser does not provide built-in, they can add that codec to the set of choices to be offered to the peer. While it is flexible, I am concerned if this might create more problems than it solves. I guess we’ll have to wait and see.

    I was also surprised by the need to use ICE, even though in my experiment I got away with an empty list of ICE servers – the ICE messages just got exchanged through the socket.io server. I am not sure whether this is a bug, but I was very happy about it because it meant I could run the whole demo on a completely separate network from the Internet.

    The most exciting news since my talk is that Mozilla and Google have managed to get a PeerConnection working between Firefox and Chrome – this is the first cross-browser video conference call without a plugin ! The code differences are minor.

    Since the specification of the WebRTC API and of the MediaStream API are now official Working Drafts at the W3C, I expect other browsers will follow. I am also looking forward to the possibilities of :

    The best places to learn about the latest possibilities of WebRTC are webrtc.org and the W3C WebRTC WG. code.google.com has open source code that continues to be updated to the latest released and interoperable features in browsers.

    The video of my talk is in the process of being published. There is a MP4 version on the Linux Australia mirror server, but I expect it will be published properly soon. I will update the blog post when that happens.

  • How to compile a static FFmpeg binary on OS X

    29 juillet 2014, par Chitanda_Eru

    I want to compile a static ffmpeg binary by myself. I follow this guide, and then built one successfully.

    ./configure --extra-version=Chitanda_Eru --prefix=/Volumes/Chitanda_Eru/ --enable-gpl --enable-version3 --enable-nonfree --disable-shared --enable-static --enable-ffplay --disable-ffserver --enable-pthreads --enable-avisynth --enable-libvo-aacenc --enable-libfaac --enable-libfdk-aac --enable-libmp3lame --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libxvid --enable-libbluray --enable-libtheora --enable-libcelt --enable-openssl --enable-libspeex --enable-postproc --enable-libvpx --enable-libgsm --enable-libopenjpeg --enable-libopus --enable-fontconfig --enable-libfreetype --enable-libass --enable-filters --disable-indev=qtkit --enable-runtime-cpudetect --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libtwolame --enable-openal --enable-libsoxr --enable-libwavpack --enable-libvidstab --enable-libilbc --enable-libschroedinger --enable-libcaca --enable-opengl --enable-frei0r --enable-libquvi

    But I come across a problem, the FFmpeg binary is only 15.5MB which is much smaller than the official builds, what’s more, it can’t work on my second Mac and with errors below.

    Library not loaded: /usr/local/lib/libx264.142.dylib
     Referenced from: /Applications/CLI/ffmpeg
     Reason: image not found
    Trace/BPT trap: 5

    And then I use otool command to see what the dynamic libraries ffmpeg rely on.

    otool -L /Applications/CLI/ffmpeg | grep local

       /usr/local/lib/libSDL-1.2.0.dylib (compatibility version 12.0.0, current version 12.4.0)
       /usr/local/lib/libx265.25.dylib (compatibility version 25.0.0, current version 1.2.0)
       /usr/local/lib/libx264.142.dylib (compatibility version 0.0.0, current version 0.0.0)
       /usr/local/lib/libvorbisenc.2.dylib (compatibility version 3.0.0, current version 3.10.0)
       /usr/local/lib/libvorbis.0.dylib (compatibility version 5.0.0, current version 5.7.0)
       /usr/local/lib/libogg.0.dylib (compatibility version 9.0.0, current version 9.2.0)
       /usr/local/lib/libvo-aacenc.0.dylib (compatibility version 1.0.0, current version 1.3.0)
       /usr/local/lib/libvidstab.0.9.dylib (compatibility version 0.9.0, current version 0.0.0)
       /usr/local/lib/libtheoraenc.1.dylib (compatibility version 3.0.0, current version 3.2.0)
       /usr/local/lib/libtheoradec.1.dylib (compatibility version 3.0.0, current version 3.4.0)
       /usr/local/lib/libspeex.1.dylib (compatibility version 7.0.0, current version 7.0.0)
       /usr/local/lib/libquvi.7.dylib (compatibility version 8.0.0, current version 8.1.0)
       /usr/local/lib/libopus.0.dylib (compatibility version 6.0.0, current version 6.0.0)
       /usr/local/lib/libopenjpeg.1.dylib (compatibility version 7.0.0, current version 7.0.0)
       /usr/local/lib/libopencore-amrwb.0.dylib (compatibility version 1.0.0, current version 1.3.0)
       /usr/local/lib/libopencore-amrnb.0.dylib (compatibility version 1.0.0, current version 1.3.0)
       /usr/local/lib/libmp3lame.0.dylib (compatibility version 1.0.0, current version 1.0.0)
       /usr/local/lib/libgsm.1.0.13.dylib (compatibility version 1.0.0, current version 1.0.13)
       /usr/local/lib/libfreetype.6.dylib (compatibility version 18.0.0, current version 18.2.0)
       /usr/local/lib/libfontconfig.1.dylib (compatibility version 10.0.0, current version 10.0.0)
       /usr/local/lib/libfdk-aac.0.dylib (compatibility version 1.0.0, current version 1.4.0)
       /usr/local/lib/libfaac.0.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
       /usr/local/lib/libcaca.0.dylib (compatibility version 100.0.0, current version 100.19.0)
       /usr/local/lib/libcelt0.2.dylib (compatibility version 3.0.0, current version 3.0.0)
       /usr/local/lib/libbluray.1.dylib (compatibility version 8.0.0, current version 8.0.0)
       /usr/local/lib/libass.5.dylib (compatibility version 6.0.0, current version 6.0.0)

    Most of my packages are installed by Homebrew, and Homebrew will install them with "—enable-static —enable-shared". And my guess is : when I compile ffmpeg, ffmpeg rather use the dynamic libraries than the static libraries, so the binary won’t work on other Macs.How can I build a static binary of ffmpeg ? Thanks.

    update : I successfully build static ffmpeg after moving all the dylibs which have static libraries as well to other dictionary and disable all the libraries that ./configure can’t find.

    ./configure --extra-version=Chitanda_Eru --prefix=/Volumes/Chitanda_Eru/ --enable-gpl --enable-version3 --enable-nonfree --disable-shared --enable-static --enable-ffplay --disable-ffserver --enable-pthreads --enable-avisynth --enable-libvo-aacenc --enable-libfaac --enable-libfdk-aac --enable-libmp3lame --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libtheora --enable-libcelt --enable-openssl --enable-libspeex --enable-postproc --enable-libvpx --enable-libgsm --enable-libopenjpeg --enable-filters --disable-indev=qtkit --enable-runtime-cpudetect --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libtwolame --enable-libsoxr --enable-libwavpack --enable-libilbc --enable-opengl --enable-frei0r
  • Use Google Analytics and risk fines, after CJEU ruling on Privacy Shield

    27 août 2020, par Joselyn Khor — Privacy

    EU websites using Google Analytics and Facebook are being targeted by European privacy group noyb after the invalidation of the Privacy Shield. They filed a complaint against 101 websites for continuing to send data to the US. 

    “A quick analysis of the HTML source code of major EU webpages shows that many companies still use Google Analytics or Facebook Connect one month after a major judgment by the Court of Justice of the European Union (CJEU) - despite both companies clearly falling under US surveillance laws, such as FISA 702. Neither Facebook nor Google seem to have a legal basis for the data transfers.”

    noyb website
    CJEU invalidates the Google Privacy Shield

    The Privacy Shield previously allowed for EU data to be transferred to the US. However, this was invalidated by the Court of Justice of the European Union (CJEU) on July 16, 2020. The CJEU deemed it illegal for any websites to transfer the personal data of European citizens to the US. 

    They also made it clear in a press release that “data subjects can claim compensation for inadmissible data exports (marginal no. 143 of the judgment). This should in particular include non-material damage (“compensation for pain and suffering”) and must be of a deterrent amount under European law.” Which puts extra financial pressure on websites to take the new ruling seriously.

    Immediate action is required after Google Privacy Shield invalidation

    The Berlin Commissioner for Data Protection and Freedom of Information therefore calls on all those responsible under its supervision to observe the decision of the ECJ [CJEU]. Those responsible who transfer personal data to the USA - especially when using cloud services - are now required to immediately switch to service providers in the European Union or in a country with an adequate level of data protection.

    The Berlin Commissioner for Data Protection and Freedom of Information

    As the ruling is effective immediately, there’s a pressing need for websites using Google Analytics to act, or face getting fined.

    What does this mean for you ?

    If you’re using Google Analytics the safest bet is to stop using it immediately

    "Neither Google Analytics nor Facebook Connect are necessary for the operation of these websites and could therefore have been replaced or at least deactivated in the meantime."

    Max Schrems, Honorary Chairman of noyb 

    If you still need to use it, then you’ll need to inform your visitors via a clear consent screen. This banner needs to make clear their personal data will be sent to the US, and to educate them about any potential risk related to this. They will then need to explicitly agree to this. 

    Another downside of cookie consent screens is that you may also suffer a damaging loss of visitors. After implementing cookie consent best practices, the UK’s data regulator the Information Commissioner’s Office (ICO) found a 90% drop in traffic, “implying a ninety percent drop in opt-in rates.”

    With an acceptance rate for such consent screens being lower than 10% your analytics becomes guesswork rather than science. 

    Looking for a privacy-respecting alternative to Google Analytics ?

    Privacy compliant Matomo Analytics is one of the best Google Analytics alternatives availalble. 

    With Matomo you’re able to continue using analytics without facing the wrath of both the GDPR and the CJEU. Matomo On-Premise lets you choose where your data is stored, so you can ensure no data is processed in the US. 

    Matomo is privacy-friendly and can be tweaked to comply with all privacy laws. Including the GDPR, HIPAA, CCPA and PECR. The benefits of this include : not needing to use tracking or cookie consent screens (like with GA) ; and avoiding fines because no personal data is collected. You also get 100% accurate data and the ability to protect your user’s privacy.

    Matomo is the privacy-respecting Google Analytics alternative

    Is your EU business at risk of being fined for using Google Analytics ?