INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 2 [3]   Go Down

Author Topic: Blackmagic Design devices - how do we support them better  (Read 953 times)

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4226
Re: Blackmagic Design devices - how do we support them better
« Reply #100 on: November 18, 2024, 02:27:38 pm »

OK, will be great if it can be done in an open manner that lets a user provided filter give the info required to drive it
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72437
  • Where did I put my teeth?
Re: Blackmagic Design devices - how do we support them better
« Reply #101 on: November 18, 2024, 04:37:42 pm »

Matt,
I think you know that we don't intend for JRVR to be used by other applications.  I hope you understand.
Logged

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4226
Re: Blackmagic Design devices - how do we support them better
« Reply #102 on: November 18, 2024, 04:46:06 pm »

You misunderstand as it's not another application

I'm talking about a directshow capture filter to use as channel within MC television. I can already use the microsoft provided one for the card but that only supports stereo audio and doesn't expose the colourspace in a way that lets a renderer understand it, you have to use the api provided by the card manufacturer to do all that. Hence write one and then be able to use MC to fully access the card capabilities.

Put simply, it's exactly what Yaobing is doing for the blackmagic cards (which I don't use because they have limited support for the resolution/frame rate output by my cable box. I can't imagine why you'd want to restrict support to a particular card but obviously it's your software so that's your choice.
Logged

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4226
Re: Blackmagic Design devices - how do we support them better
« Reply #103 on: Today at 03:19:41 pm »

We are working on HDR metadata.  It is still not clear how we are approaching it.
regardless of whether you make it public api or not, I'm curious what are the downsides of the method of packing data into IMediaSideData (https://github.com/Nevcairiel/LAVFilters/blob/81c5676cb99d0acfb1457b8165a0becf5601cae3/include/IMediaSideData.h) are? it seems commonly used and pretty straightforward
Logged
Pages: 1 2 [3]   Go Up