Recherche avancée

Sur d’autres sites (10318)

• cbs_h265 : Fix ranges of prediction weight offsets

  28 août 2017, par Mark Thompson

  cbs_h265 : Fix ranges of prediction weight offsets
  The bracketing was wrong - ’-’ binds before ’<<’.  This would
  
  previously incorrectly reject the streams in the WP_A and WP_B
  
  conformance tests.
  

  • [DBH] libavcodec/cbs_h265_syntax_template.c

• Piwik 2 reaches end of life soon (December 2017), update now !

  7 décembre 2017, par Piwik Core Team — Community

  In less than three weeks, Piwik 2 will be no longer supported. This means that no further (security) updates will be released for this version. As per our Long Term Support announcement, Piwik 2.X is supported for 12 months after the initial release of Piwik 3.0.0 which was on December 18th 2016. Therefore, Piwik 2 will no longer receive any updates after December 18th 2017.

  It has been almost a year since we released Piwik 3 and we highly recommend updating to Piwik 3 ASAP. The major new release came with a new UI, performance and security improvements. If you are still on Piwik 2, the security improvements alone should be worth updating your Piwik to Piwik 3 now. We cannot recommend this enough.

  The update to Piwik 3 should be smooth, but may take a while depending on the amount of data you have.

  • If you have any problem with the update, feel free to get in touch with us, or ask in the forums.
  • If you are currently using Piwik self-hosted and would like to be upgraded, plus your Piwik managed in the official Cloud-hosted service, contact InnoCraft Cloud and they will migrate your database.

  At Piwik and InnoCraft, the company of the makers of Piwik, we have seen many thousands of Piwik installations upgraded over the past year and look forward to an exciting future for Piwik 3 and beyond !

• Libavcodec "the procedure entry point for av_frame_alloc could not be located" error in Visual Studio 2017 C++ project

  25 novembre 2019, par Aves

  I am trying to use libavcodec from ffmpeg library in C++ with Visual Studio 2017 Community. I downloaded the latest x64 dev and shared builds from zeranoe (version 20171217), set up include directories and additional libraries in Visual Studio for x64 build, added DLL files from shared package to my PATH.

  This is my sample test code :

  extern "C" {
  
  #include 
  
  }
  
  int main() {
  
      avcodec_register_all();
  
      AVFrame *pAvFrame = av_frame_alloc();
  
      av_frame_free(&pAvFrame);
  
      return 0;
  
  }

  The code compiles without problems but when I run the application I see a dialogue window with error message "the procedure entry point for av_frame_alloc could not be located in DLL" (actual message is not in English, this is the translated version).

  I tried to set Linker->Optimization->References to /OPT:NOREF as it was advised in the similar questions but it did not help.

  Dependency walker shows that av_frame_alloc is exported, "Entry Point" is not bound. A little bit strange is that av_frame_alloc is displayed in both avcodec-58.dll (as red) and avutil-56.dll (as green). Maybe the reason is that the application is trying to get this function from avcodec instead of avutil, but I’m not sure, since I did not check the source code of these libraries.

  So the question is how to set up such a simple FFMPEG-based C++ project in VS2017, where I’m wrong ?

  UPD. 1.

  Linker flags : /OUT :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.exe" /MANIFEST /NXCOMPAT /PDB :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pdb" /DYNAMICBASE "c :\work\dev\ffmpeg-20171217-387ee1d-win64-dev\lib*.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" /DEBUG:FULL /MACHINE:X64 /OPT:NOREF /PGD :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pgd" /MANIFESTUAC :"level=’asInvoker’ uiAccess=’false’" /ManifestFile :"x64\Release\TestFfmpeg.exe.intermediate.manifest" /OPT:ICF /ERRORREPORT:PROMPT /NOLOGO /TLBID:1