Recherche avancée

Sur d’autres sites (4684)

• Video Conferencing in HTML5 : WebRTC via Socket.io

  
  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 :

  • multi-peer video conferencing like the efforts around webrtc.io,
  • the media stream recording API,
  • and the peer-to-peer data API.

  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.

• Can I Config FFMEG-2.4.3 to use in android windows 64 ?

  13 novembre 2014, par Ngo Ky

  I want to build ffmpeg-2.4.3 (lastest c lib) to use it on android for managing video.
  my OS is windows 7 Utimate x64
  cywin64 in directory : C :/cywin64/ have make installed.
  NDK in directory : D :\solfware\Programming\android-ndk-r10c

  i follow toturial form : http://www.roman10.net/how-to-build-ffmpeg-for-android/comment-page-1/
  my project struture like :

  

  i create build_android.sh like roman10 as following code :

  # ARMv7+Neon (Cortex-A8)
  
  # Customizing:
  
  # 1. Feel free to change ./configure parameters for more features
  
  # 2. To adapt other ARM variants
  
  # set $CPU and $OPTIMIZE_CFLAGS 
  
  # call build_one
  
  ######################################################
  
  NDK=D:\solfware\Programming\android-ndk-r10c
  
  PLATFORM=$NDK/platforms/android-8/arch-arm/
  
  PREBUILT=$NDK/prebuilt/windows-x86_64
  
  function build_one
  
  {
  
  ./configure --target-os=linux \
  
      --prefix=$PREFIX \
  
      --enable-cross-compile \
  
      --extra-libs="-lgcc" \
  
      --arch=arm \
  
      --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \
  
      --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \
  
      --nm=$PREBUILT/bin/arm-linux-androideabi-nm \
  
      --sysroot=$PLATFORM \
  
      --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \
  
      --disable-shared \
  
      --enable-static \
  
      --extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog" \
  
      --disable-everything \
  
      --enable-demuxer=mov \
  
      --enable-demuxer=h264 \
  
      --disable-ffplay \
  
      --enable-protocol=file \
  
      --enable-avformat \
  
      --enable-avcodec \
  
      --enable-decoder=rawvideo \
  
      --enable-decoder=mjpeg \
  
      --enable-decoder=h263 \
  
      --enable-decoder=mpeg4 \
  
      --enable-decoder=h264 \
  
      --enable-parser=h264 \
  
      --disable-network \
  
      --enable-zlib \
  
      --disable-avfilter \
  
      --disable-avdevice \
  
      $ADDITIONAL_CONFIGURE_FLAG
  
  
  
  make clean
  
  make  -j4 install
  
  $PREBUILT/bin/arm-linux-androideabi-ar d libavcodec/libavcodec.a inverse.o
  
  $PREBUILT/bin/arm-linux-androideabi-ld -rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib  -soname libffmpeg.so -shared -nostdlib  -z,noexecstack -Bsymbolic --whole-archive --no-undefined -o $PREFIX/libffmpeg.so libavcodec/libavcodec.a libavformat/libavformat.a libavutil/libavutil.a libswscale/libswscale.a -lc -lm -lz -ldl -llog  --warn-once  --dynamic-linker=/system/bin/linker $PREBUILT/lib/gcc/arm-linux-androideabi/4.4.3/libgcc.a
  
  }
  
  
  
  #arm v6
  
  #CPU=armv6
  
  #OPTIMIZE_CFLAGS="-marm -march=$CPU"
  
  #PREFIX=./android/$CPU 
  
  #ADDITIONAL_CONFIGURE_FLAG=
  
  #build_one
  
  
  
  #arm v7vfpv3
  
  CPU=armv7-a
  
  OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=$CPU "
  
  PREFIX=./android/$CPU
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  build_one
  
  
  
  #arm v7vfp
  
  #CPU=armv7-a
  
  #OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU "
  
  #PREFIX=./android/$CPU-vfp
  
  #ADDITIONAL_CONFIGURE_FLAG=
  
  #build_one
  
  
  
  #arm v7n
  
  #CPU=armv7-a
  
  #OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=neon -marm -march=$CPU -mtune=cortex-a8"
  
  #PREFIX=./android/$CPU 
  
  #ADDITIONAL_CONFIGURE_FLAG=--enable-neon
  
  #build_one
  
  
  
  #arm v6+vfp
  
  #CPU=armv6
  
  #OPTIMIZE_CFLAGS="-DCMP_HAVE_VFP -mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU"
  
  #PREFIX=./android/${CPU}_vfp 
  
  #ADDITIONAL_CONFIGURE_FLAG=
  
  #build_one

  i have set my path like above
  I built it in Eclipse Everything is ok. but when i ran it in Android it crashed Unfortunately.
  I found the errors in Logcat monitor :

  E/AndroidRuntime(1931) : java.lang.UnsatisfiedLinkError : Couldn’t load avcodec-55 from loader dalvik.system.PathClassLoader[DexPathList [1]] : findLibrary returned null

  E/AndroidRuntime(1931) : at java.lang.Runtime.loadLibrary(Runtime.java:358)

  In my activity i just call add Library from C preference like :

  static {
  
          //System.loadLibrary("avutil-52");
  
          System.loadLibrary("avcodec-55");
  
          System.loadLibrary("avformat-55");
  
          System.loadLibrary("swscale-2");
  
          System.loadLibrary("tutorial02");
  
      }

  i check in DDMS in app-lib there is no existing Library in there.

  The question is : Can i can compile the ffmpeg on windows ?
  if ok. how can i config build_android.sh to point to Android $PREBUILT

  PLATFORM=$NDK/platforms/android-8/arch-arm/
  
      PREBUILT=$NDK/prebuilt/windows-x86_64
  
      function build_one
  
      {
  
      ./configure --target-os=linux \
  
          --prefix=$PREFIX \
  
          --enable-cross-compile \
  
          --extra-libs="-lgcc" \
  
          --arch=arm \
  
          --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \
  
          --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \
  
          --nm=$PREBUILT/bin/arm-linux-androideabi-nm \
  
          --sysroot=$PLATFORM \
  
          --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \
  
          --disable-shared \

  i found that in $NDK/prebuilt/windows-x86_64/bin did not exist arm-linux-androideabi-gcc\
  How can i config to be suitable to run on windows ?

  Thank in advanced

• 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 :

  • [fr] Sites web, cookies et autres traceurs
  • [fr] Comment me mettre en conformité avec la recommandation “Cookies” de la CNIL ?
  • [fr] Recommandation sur les cookies : obligations pour les responsables de sites ?
  • CNIL Starts Controlling Cookie Settings in October 2014
  • CNIL recommends Piwik for compliance with data protection laws

  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.