Recherche avancée

Sur d’autres sites (11378)

• End of Piwik Mobile 1 – Focus is on Piwik Mobile 2

  2 septembre 2014, par Piwik Core Team — Community, Piwik Mobile Releases

  More than four years after its initial release, we will remove Piwik Mobile 1 from the Apple App Store and Google Play Store in one week. During that time the app was downloaded more than 60.000 times with an average rating of 4.6 and over 2000 ratings. Thank you to our community of users for all of this !

  Why we must focus on Piwik Mobile 2

  Unfortunately we do not have the resources to maintain Piwik Mobile 1 to be compatible with the latest iOS and Android updates (namely iOS 8 and Android L). The last update of Piwik Mobile 1 was over one year ago and the underlying framework, which we are using to develop the app, is nearly two years old. Making the code compatible with the current version of the underlying framework to support the latest platform versions would take us many weeks. As a little background : From the beginning Piwik Mobile 1 has been a free app and was developed by a single person Thomas in his spare time who is now focussing on Piwik Mobile 2.

  Can I still get it ?

  We are announcing this today so you get a chance to install the app via the Apple App Store and Google Play Store while it is still available.

  If you are one of the 87% of our Piwik Mobile 1 users who are already using Android 4+ or iOS 7+ then you can install Piwik Mobile 2 (make sure you upgrade your Piwik platform to 1.12 or 2.x recommended).

  What happens after the app is removed ?

  If you have already installed the app it won’t be removed from your device and you will still be able to use it. Android users can still download Piwik Mobile 1 but we cannot guarantee it will work on all devices. Lastly the code our free software is available on GitHub and you can build it from the source if you have to.

  The future of Piwik Mobile

  Piwik Mobile version 2.1 is currently in beta testing phase. This new version includes several useful new features such as support for Segmentation. If you use Android, give it a try !

• vdpau : do not use buggy HEVC support by default

  1er juillet 2017, par wm4

  vdpau : do not use buggy HEVC support by default
  NVIDIA broke its own API when using VDPAU decoding. If you retrieve the
  
  decoded YUV data, or if you map the surfaces with GL interop, the result
  
  are interlacing artifacts. The only way to get non-broken data is by
  
  using the vdpau video mixer to convert it to RGB. There is no way to
  
  block the non-working operations in a reasonable way (a VdpVideoSurface
  
  has to support all operations).
  NVIDIA refuses to fix this issue (they "fixed" it by making it work with
  
  the video mixer, but the rest is still broken). There is no sign of that
  
  changing.
  Do not use HEVC by default with the generic hwaccle API. Detect whether
  
  it's the NVIDIA native implementation, and exit with an error. (The same
  
  thing work with the MESA implementation.)
  As an escape hatch and to allow applications to use the decoder if they
  
  really want to (perhaps because they make sure to explicitly use the
  
  video mixer), reuse AV_HWACCEL_FLAG_ALLOW_PROFILE_MISMATCH to disable
  
  this check.
  Once NVIDIA fixes the bug, working driver versions could be detected,
  
  and it could be allowed again.
  

  • [DH] libavcodec/vdpau.c

• avcodec/mediacodecdec : add workaround for buggy amlogic mpeg2 decoder

  26 avril 2018, par Aman Gupta

  avcodec/mediacodecdec : add workaround for buggy amlogic mpeg2 decoder
  I tested the previous mediacodec changes on seven different Android
  
  TV devices, with both mpeg2 and h264 content. All except one worked
  
  as expected. The exception was the MiBox3 running Android 6.0.1,
  
  where playback would freeze on a frame every few seconds. I tested
  
  two other AMLogic devices with newer Android versions that did not
  
  show the same problem. H264 decoding on the MiBox3 was also not affected,
  
  so this workaround applies only to OMX.amlogic.mpeg2.decoder.awesome
  
  on Android API22.
  There is a rumor that Xiaomi is planning to release Android Oreo for
  
  the MiBox3, so I will revisit in a few months to confirm whether this
  
  is specific to os/driver version or the chipset used in that device.
  Signed-off-by : Aman Gupta <aman@tmm1.net>
  
  Signed-off-by : Matthieu Bouron <matthieu.bouron@gmail.com>
  

  • [DH] libavcodec/mediacodecdec.c