Recherche avancée

Sur d’autres sites (8371)

• Official Debian Package for Piwik now available

  15 avril 2014, par Matthieu Aubry — Community, Meta

  We are excited to announce the release of Piwik package for Debian based linux distributions !

  There are several ways to use Piwik :
  
   Download and upload to your server
  
   or use 1-click Piwik installers
  
   or use Microsoft web app gallery
  
   or buy Piwik Cloud
  
   or as of today, you may get Piwik using our Debian package

  What are the benefits of using Debian package over direct download ?

  For some system administrators, using Debian package is an easier alternative than directly downloading the code. It allows sysadmins to deploy Piwik within seconds using “apt-get install piwik -V”.

  How do I install Piwik using official debian package ?

  The package supports Apache and Nginx web servers. Read the documentation at debian.piwik.org.

  Do I have to use the Debian Package on my debian system ?

  No, you may still want to use Piwik using the direct download approach. You can keep Piwik upgraded quite easily using the popular 1-click automatic update.

  How do I report a bug or feedback ?

  Create a ticket on the Github project Issues page.

  Will the debian repository be maintained in the future ?

  Yes, Aurélien Requiem (github) along with the Piwik team are committed to maintain the Debian Piwik repository in the future.

  Thank you to Aurélien for his great work on preparing, testing, and maintaining the Debian repository for Piwik.

  References

  • Source code for the Debian package is on Github : piwik/package-debian
  • How do I enable automatic updates to latest development release ?
  • How do I install Piwik on Debian type servers ?

• lavu/hwcontext_vaapi : Add Windows/VAAPI support with vaGetDisplayWin32

  14 avril 2023, par Sil Vilerino

  lavu/hwcontext_vaapi : Add Windows/VAAPI support with vaGetDisplayWin32
  Libva 2.17+ adds a new libva-win32 node and Mesa 22.3 adds a VAAPI driver
  
  based on Direct3D 12 for Windows. Both of them are available at :
  
  https://www.nuget.org/packages/Microsoft.Direct3D.VideoAccelerationCompatibilityPack
  Initial review at https://github.com/intel-media-ci/ffmpeg/pull/619/
  Signed-off-by : Sil Vilerino <sivileri@microsoft.com>
  
  Reviewed-by : Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
  
  Reviewed-by : Wu, Tong1 <tong1.wu@intel.com>
  

  • [DH] Changelog
  • [DH] configure
  • [DH] libavutil/hwcontext_vaapi.c
  • [DH] libavutil/tests/hwdevice.c

• Warning VSP2005 & Error VSP1048 when instrumenting C++ code dynamically linked to FFMPEG

  20 juin 2018, par TTJG

  I am trying to profile my project with the Instrumentation profiler of Visual Studio 2013 Ultimate. I have a 64bit C++ project which is dynamically linked to FFMPEG. However, the profiler is giving me the following error Error VSP1048: Internal instrumentation error. I don’t want to profile FFMPEG but only analyze the performance of my code. I downloaded the pre-built FFMPEG libs from this site ffmpeg.zeranoe.com/builds/. The project is also linking against Boost, live555 and x264. It is running and debugging fine. The full output of the profiler is :

  Profiling started.
  
  Instrumenting ...\Player.exe in place
  
  Info VSP3049: Small functions will be excluded from instrumentation.
  
  Microsoft (R) VSInstr Post-Link Instrumentation 12.0.21005 x64
  
  Copyright (C) Microsoft Corp. All rights reserved.
  
  Warning VSP2005: Internal instrumentation warning: The object '...\ffmpeg-20150506-git-a2190de-win64-dev\lib\avutil.lib(dbyqh.o)' was built without debug information.
  
  File to Process:
  
  \Player.exe --> ...\Player.exe
  
  Original file backed up to ...\Player.exe.orig
  
  Warning VSP2005: Internal instrumentation warning: The object '...\ffmpeg-20150506-git-a2190de-win64-dev\lib\avutil.lib(dbyqh.o)' was built without debug information.
  
  Error VSP1048: Internal instrumentation error.
  
  PRF0002: Instrumentation failed with these options: /u "...\Player.exe"   /excludesmallfuncs.  Please check the output window for additional details.
  
  Data written to ...\Player150506.vsp.
  
  Profiling finished.
  
  File contains no data buffers
  
  File contains no data buffers
  
  Analysis failed
  
  Profiling complete.

  Any ideas how this could be solved ? I have found very little about this issue on the Internet.