Recherche avancée

Sur d’autres sites (10230)

• Location of the amd64 compiler in Visual Studio 2022 | Compiling FFmpeg with NVENC

  6 juin 2022, par Gal Grünfeld

  I'm trying to follow Nvidia's guide to compile FFmpeg with nvenc support on Windows and it has a stage to export the path of Visual Studio's 2013 SP2 amd64 compiler to the global path variable of the compilation dev environment :

  


  


  export PATH="/c/Program Files (x86)/Microsoft Visual Studio 12.0/VC/BIN/amd64/" :$PATH

  


  


  They say earlier in the guide that for different versions of Visual Studio different path might be required. I'm trying to use Visual Studio 2022 Community, but don't know where its amd64 compiler directory is.
I also don't know what that VC stands for ("Visual C", maybe, whatever that "Visual" might mean ?).

  


  I found in the installation directory of Visual Studio 2022 a few directories named amd64 but none of them were under one with VC or something similar in its name.
The one I think is the most likely candidate to be the updated compiler is at /MSBuild\Current\Bin\amd64.

  


  If anyone knows, please tell me if if this is the right path, and if not, what is the right path.

  


  Microsoft does offer a version of Visual Studio 2013 Update 2, though (I assume they changed their naming scheme from "service packs" to "updates, which would make it the same software), but it doesn't offer a 64-bit version of it, and I want to compile a 64-bit software - so I assume it doesn't come with one. Please do correct me if I'm wrong, it'd save me needing to use a version of Visual Studio that is different than the one in the guide.

  


• FATE : add MSS2 tests

  17 décembre 2013, par Anton Khirnov

  FATE : add MSS2 tests
  

  • [DH] tests/fate/microsoft.mak
  • [DH] tests/ref/fate/mss2-pal
  • [DH] tests/ref/fate/mss2-pals
  • [DH] tests/ref/fate/mss2-rgb555
  • [DH] tests/ref/fate/mss2-rgb555s
  • [DH] tests/ref/fate/mss2-wmv

• Registration free (sxs) COM DirectShow filter

  21 septembre 2015, par caesay

  There are questions asking on how to get Registration free COM working, and this is not one of those. I have a DirectShow video source filter (catagory 860BB310-5D01-11d0-BD3B-00A0C911CE86) implemented in .Net with the help of an edited version of the code available here : Pure .Net DirectShow Filters by Maxim Kartavenkov.

  I need to get ffmpeg to recognize my .Net DirectShow filter as a video source using Registration Free COM (Side by Side / sxs). Built into the .Net framework is support for COM component servers, so theoretically as long as the manifests are correct, ffmpeg should detect the filters.

  Here is a snippet of the relevant sections of my manifest files currently.

  <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  
  <assembly manifestversion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1">
  
  <assemblyidentity version="1.0.0.0" type="win32" processorarchitecture="*"></assemblyidentity>
  
  <dependency>
  
   <dependentassembly>
  
    <assemblyidentity version="1.0.0.0" publickeytoken="26A05D7C90FBA3E8"></assemblyidentity>
  
   </dependentassembly>
  
  </dependency>
  
  </assembly>

  <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  
  <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestversion="1.0">
  
     <assemblyidentity version="1.0.0.0" publickeytoken="26A05D7C90FBA3E8"></assemblyidentity>
  
     <clrclass clsid="{65722BE6-3449-4628-ABD3-74B6864F9739}" progid="DShowVideoFilter.VideoCaptureFilter" threadingmodel="Both" runtimeversion="v2.0.50727"></clrclass>
  
     <file>
  
     </file>
  
     <file>
  
       <typelib tlbid="{B618E67B-64C8-48E9-9F94-F13214B76808}" version="1.0" helpdir="" flags="hasdiskimage"></typelib>
  
     </file>
  
  </assembly>

  So, I get no errors when running ffmpeg (like you would if there was a manifest error) - and I am confident that everything that is configured correctly (related to traditional sxs com loading), the problem I think (unconfirmed) is that ffmpeg loads DShow filters via DirectShow’s intelligent connect system, which requires the filter and pins to be registered. Here are some documents that talk about how filters need to be registered that I’ve found :

  • #1 Registering DirectShow Filters
  • #2 Implementing DllRegisterServer

  Now, in Maxim Kartavenkov’s DShow base classes, he takes care of #2 automatically. Here is a significantly shortened version of the method that registers the filters implementing BaseFilter.

  [ComRegisterFunction]
  
  public static void RegisterFunction(Type _type)
  
  {
  
      AMovieSetup _setup = (AMovieSetup)Attribute.GetCustomAttribute(_type, typeof(AMovieSetup));
  
      BaseFilter _filter = (BaseFilter)Activator.CreateInstance(_type);
  
      string _name = _filter.Name;
  
      DsGuid _category = new DsGuid(_setup.Category);
  
      IFilterMapper2 _mapper2 = (IFilterMapper2)new FilterMapper2();
  
  
  
      RegFilter2 _reg2 = new RegFilter2();
  
      _reg2.dwVersion = (int)_setup.Version;
  
      _reg2.dwMerit = _setup.FilterMerit;
  
      _reg2.rgPins = IntPtr.Zero;
  
      _reg2.cPins = 0;
  
  
  
      IntPtr _register = Marshal.AllocCoTaskMem(Marshal.SizeOf(_reg2));
  
      Marshal.StructureToPtr(_reg2, _register, true);
  
  
  
      hr = _mapper2.RegisterFilter(_type.GUID, _name, IntPtr.Zero, _category, _instance, _register);
  
  
  
      Marshal.FreeCoTaskMem(_register);
  
  }

  That is the method (particularly mapper2.RegisterFilter) that allows ffmpeg to find the DShow filter when it is registered traditionally (with RegAsm) into the registry, which creates registry keys for the filter and pins as described by #2 link.

  tldr ;
  So the question is, how to emulate the function of RegisterFilter or the intelligent connect registry entries this within a manifest file as to allow the sxs context to find my DirectShow filter when ffmpeg searches for it.