Recherche avancée

Sur d’autres sites (7275)

• Inaccurate sleep using C++11 on Windows

  15 février 2017, par Ashe the human

  I’ve been using C++11 sleep to give the interval between video frames. This method I’ve been using makes playback elongated on Windows.

  #include <iostream>
  
  #include <thread>
  
  #include <sstream>
  
  
  
  
  
  int main(const int argc, const char **args)
  
  {
  
      std::stringstream sb;
  
  
  
      if(argc &lt; 2)
  
          return 1;
  
      int fps = 0;
  
      sb &lt;&lt; args[1];
  
      sb >> fps;
  
  
  
      if(fps &lt;= 0)
  
          return 1;
  
      int i;
  
  
  
  
  
      while(true)
  
      {
  
          std::chrono::high_resolution_clock::time_point start, end;
  
  
  
          start = std::chrono::high_resolution_clock::now();
  
          for(i=0; i fps));
  
          }
  
          end = std::chrono::high_resolution_clock::now();
  
  
  
          auto c = std::chrono::duration_cast(end - start).count();
  
          std::cerr &lt;&lt; c &lt;&lt; std::endl;
  
      }
  
  
  
      return 0;
  
  }
  
  </sstream></thread></iostream>

  Running that program with 60 gives about 1004 1006 on Linux and 1065 1075 on Windows. So, I’m guessing, after playing a 2-hour long video, more than a minute is passed than just 2 hours.

  timeBeginPeriod() has no effect. Is using timer(like this one ?) is the only way to implement media players on Windows ? What about on Linux ? I think it’s the right way considering the fact that ffplay uses av_usleep().

  So sad that there’s no portable way.

• FFmpegInteropX in Unity Hololens 2

  25 juin 2024, par CocoaMilka

  I'm building a UDP video stream decoder for the Hololens 2 in Unity 2021. I've compiled FFmpegInteropX for ARM64 UWP, however I'm having issues setting it up within Unity. With the binaries included in /Plugins/WSA I get the following error :

  


  ArgumentException: The Assembly WinRT.Runtime is referenced by FFmpegInteropX.DotNet ('Assets/Plugins/WSA/FFmpegInteropX.DotNet/Release/FFmpegInteropX.DotNet.dll'). But the dll is not allowed to be included or could not be found.

  


  I've wrapped all of my WinRT dependent code with the appropriate preprocessor directive as shown here, and I've also set all my plugins to target WSAPlayer and UWP.

  


  #if ENABLE_WINMD_SUPPORT
using FFmpegInteropX;
using WinRT;
using Windows.Foundation;
using Windows.Media.Core;
using Windows.Media.Playback;
using System.Threading.Tasks;
#endif


  


  If I include WinRT.Runtime.dll in the plugins folder, the issue spreads asking for more dependencies then the new dependencies (such as Microsoft.Windows.SDK.NET.dll) starts conflicting with the MRTK packages due to it also depending on WinRT.

  


  How can I use this library within Unity without constantly running into dependency hell ?

  


• XCode 5 is not linking Static Library to Cocoa Application

  4 septembre 2014, par aaronljx

  Basically I am building a Cocoa (OSX) application that uses some of the encoding/decoding libraries from ffmpeg (e.g. libavcodec.a, libavformat.a). For these libraries, I have explicitly configured it to be compiled as static library.. there were no dylibs created when I ran the make after configuring the package. Hence I am quite certain that these libraries would work as a static library.

  As usual I added these libraries to my xcode project via the Build Phases and Framework section. The .a files are there and when I build my project, there were no linking errors. Everything is fine and dandy until I run otool against the executable file of my application and realised that it needs the ffmpeg library dylibs to run. An attempt to run the application would fail since there is no dylib installed on my machine. If I run it on another machine that has ffmpeg installed (compiled with dynamic library) the application would work.

  Therefore, my question is, am I missing out on any of the configuration on the xcode part to instruct the linker to statically link those libraries that are used in my application ? (I remember when I develop C/C++ applications in Microsoft Visual Studio, all I need to do is to just add the static libraries (*.lib) files to my project’s linker settings and it will be automatically linked to my final assembly.)

  Thanks.