INTERACT FORUM

Please login or register.

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

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

jmone

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 14497
  • I won! I won!
Re: Blackmagic Design devices - how do we support them better
« Reply #150 on: December 13, 2024, 03:11:29 pm »

You don't.  In fact it will not work if it is mismatched (you will only get a black screen).  So, if you are using the SDK method, you have to set it to match.
Logged
JRiver CEO Elect

alext77

  • Recent member
  • *
  • Posts: 36
Re: Blackmagic Design devices - how do we support them better
« Reply #151 on: December 13, 2024, 04:11:37 pm »

Hello guys.

Tomorrow I should get an hdmi device allowing to force its output in a given resolution (let say 2160p23) and it should be also able to send LPCM up to 7.1. This should make my tests easier.

I know how to copy paste the directshow filter graph and start a log file.

It’s 23:00 in France, bye bye.
Logged
I’m a Windows 10 pro user. Currently enjoying JRiver 33.

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10978
  • Dogs of the world unite!
Re: Blackmagic Design devices - how do we support them better
« Reply #152 on: December 13, 2024, 04:23:48 pm »

My question is why would you want something other than what the source provides?

Ie you have some source device, it will.have it's own configuration that controls what it outputs. Why would you want the capture to do anything other than pass that through to MC which deals with anything required to fit the output format?

It's all I did with the magewell SDK so just wondering what I am missing, if anything.

The source usually is configurable. With "Blackmagic WDM Capture" device, the user can run the filter property page and set the format. But with "DeckLink Video Capture", as Nathan discovered, the property page does not offer all formats.

I was thinking the same thing when I started, but I can not wrap my head around it when their API offers a list of possible formats, but does not tell which format the source sends. Or I did not find the right API function?
Logged
Yaobing Deng, JRiver Media Center

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10978
  • Dogs of the world unite!
Re: Blackmagic Design devices - how do we support them better
« Reply #153 on: December 13, 2024, 04:34:55 pm »

Please try this new DLL.

Nathan, for you there is not much change, as I only made sure I initialized the structure. So don't be surprised that it does not make any difference.

The dll should be used with the latest beta.

alext77, you can download and install this version first, before you copy the DLL:

MediaCenter For test

I added some code to insert LAV Audio Decoder during graph building.
Logged
Yaobing Deng, JRiver Media Center

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4300
Re: Blackmagic Design devices - how do we support them better
« Reply #154 on: December 13, 2024, 04:50:35 pm »

Fwiw I decide that based on a few values coming in on the signal

https://github.com/3ll3d00d/mwcapture/blob/main/mwcapture/mwcapture.cpp#L1098

I guess this same info is mostly found somewhere in BMDDeckLinkStatusID by the looks of it
Logged

jmone

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 14497
  • I won! I won!
Re: Blackmagic Design devices - how do we support them better
« Reply #155 on: December 13, 2024, 07:13:23 pm »

Nathan, for you there is not much change, as I only made sure I initialized the structure. So don't be surprised that it does not make any difference.

Did a quick test. Seemed the same.
Logged
JRiver CEO Elect

alext77

  • Recent member
  • *
  • Posts: 36
Re: Blackmagic Design devices - how do we support them better
« Reply #156 on: December 14, 2024, 07:23:55 am »

Please try this new DLL.

Nathan, for you there is not much change, as I only made sure I initialized the structure. So don't be surprised that it does not make any difference.

The dll should be used with the latest beta.

alext77, you can download and install this version first, before you copy the DLL:

MediaCenter For test

I added some code to insert LAV Audio Decoder during graph building.

Hello,

Yaobing, have you received my private message ?

Installation of MC 51 is done but I still cannot see LAV audio decoder in the directshow filters :

below the copy/paste :

Filter Graph Info (TV graph):

    Filter 'JRiver Audio Renderer'
        CLSID: {A4002F8E-510F-442C-8AD3-F9C7B23FB394}
        Host:
        Input Pin 'In'
            Connected to pin 'Capture' of filter 'Decklink Audio Capture'
            Major type MEDIATYPE_Audio  Sub type MEDIASUBTYPE_PCM, Format type FORMAT_WaveFormatEx

    Filter 'JRVR'
        CLSID: {555E6803-14EF-4946-8646-B6EF9E9121E2}
        Host:
        Input Pin ''
            Connected to pin 'XForm Out' of filter 'AVIDecompressor'
            Major type MEDIATYPE_Video  Sub type MEDIASUBTYPE_RGB32, Format type FORMAT_VideoInfo

    Filter 'Decklink Audio Capture'
        CLSID: {AAA22F7E-5AA0-49D9-8C8D-B52B1AA92EB7}
        Host: c:\program files\blackmagic design\blackmagic desktop video\decklink64.dll
        Output Pin 'Capture'
            Connected to pin 'In' of filter 'JRiver Audio Renderer'
            Major type MEDIATYPE_Audio  Sub type MEDIASUBTYPE_PCM, Format type FORMAT_WaveFormatEx

    Filter 'AVIDecompressor'
        CLSID: {CF49D4E0-1115-11CE-B03A-0020AF0BA770}
        Host: c:\windows\system32\quartz.dll
        Input Pin 'XForm In'
            Connected to pin 'Capture' of filter 'Decklink Video Capture AFF3E920987F1D8D'
            Major type MEDIATYPE_Video  Sub type Unknown GUID Name: {43594448-0000-0010-8000-00AA00389B71}, Format type FORMAT_VideoInfo
        Output Pin 'XForm Out'
            Connected to pin '' of filter 'JRVR'
            Major type MEDIATYPE_Video  Sub type MEDIASUBTYPE_RGB32, Format type FORMAT_VideoInfo

    Filter 'Decklink Video Capture AFF3E920987F1D8D'
        CLSID: {44A8B5C7-13B6-4211-BD40-35B629D9E6DF}
        Host: c:\program files\blackmagic design\blackmagic desktop video\decklink64.dll
        Output Pin 'Capture'
            Connected to pin 'XForm In' of filter 'AVIDecompressor'
            Major type MEDIATYPE_Video  Sub type Unknown GUID Name: {43594448-0000-0010-8000-00AA00389B71}, Format type FORMAT_VideoInfo
        Output Pin '~VANC'
        Output Pin '~Timecode'
Logged
I’m a Windows 10 pro user. Currently enjoying JRiver 33.

alext77

  • Recent member
  • *
  • Posts: 36
Re: Blackmagic Design devices - how do we support them better
« Reply #157 on: December 14, 2024, 09:19:44 am »

Some news :

My source can send 2160p23 HDR, I can check it with my VERTEX that I have installed in between my source and the blackmagic board. I can see the metadata sent to the board. The issue is JR video renderer don’t see the meta data.

About audio : my source can send LPCM up to 7.1 but JR audio renderer can see only 2 channels. With LPCM 2.0 it is consistent but with moré Channel I can hear only the side or the rear channels.
Logged
I’m a Windows 10 pro user. Currently enjoying JRiver 33.

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10978
  • Dogs of the world unite!
Re: Blackmagic Design devices - how do we support them better
« Reply #158 on: December 14, 2024, 09:38:04 am »

Some news :

My source can send 2160p23 HDR, I can check it with my VERTEX that I have installed in between my source and the blackmagic board. I can see the metadata sent to the board. The issue is JR video renderer don’t see the meta data.

About audio : my source can send LPCM up to 7.1 but JR audio renderer can see only 2 channels. With LPCM 2.0 it is consistent but with moré Channel I can hear only the side or the rear channels.

Did you copy the JRTelevision.dll over after you installed the new version of MC?

You can email me a log if you prefer. yaobing at jriver
Logged
Yaobing Deng, JRiver Media Center

alext77

  • Recent member
  • *
  • Posts: 36
Re: Blackmagic Design devices - how do we support them better
« Reply #159 on: December 14, 2024, 09:43:33 am »

Yes I did. I will send you an email.

Have you reveived my private message ?
Logged
I’m a Windows 10 pro user. Currently enjoying JRiver 33.

alext77

  • Recent member
  • *
  • Posts: 36
Re: Blackmagic Design devices - how do we support them better
« Reply #160 on: December 14, 2024, 10:26:57 am »

Did you copy the JRTelevision.dll over after you installed the new version of MC?

You can email me a log if you prefer. yaobing at jriver

Log sent by email. (alex_xxxxx at yahoo fr, check your spam)
Logged
I’m a Windows 10 pro user. Currently enjoying JRiver 33.

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10978
  • Dogs of the world unite!
Re: Blackmagic Design devices - how do we support them better
« Reply #161 on: December 14, 2024, 10:55:35 am »

Yes I got your PM.
Logged
Yaobing Deng, JRiver Media Center

alext77

  • Recent member
  • *
  • Posts: 36
Re: Blackmagic Design devices - how do we support them better
« Reply #162 on: December 15, 2024, 02:14:18 pm »

Hello

If you want me to test anything, I’m ready :)
Logged
I’m a Windows 10 pro user. Currently enjoying JRiver 33.

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10978
  • Dogs of the world unite!
Re: Blackmagic Design devices - how do we support them better
« Reply #163 on: December 16, 2024, 10:59:58 am »

Hello

If you want me to test anything, I’m ready :)

I received the log by email.

The log shows that the audio was PCM. That is why LAV Audio decoder filter was not involved. I believe LAV decoder filters are designed to connect to only compressed media formats, not uncompressed ones.

Here is the sequence of what went on:

1. We try connecting LAV. It failed to connect because the audio is PCM.
2. We try connecting without an intermediate filter (from the capture filter to the renderer directly). That succeeded.

The video format is 'HDYC' which is not in our code. So somehow the filter's output already got that.

We are currently not messing with the audio output pin yet, so whatever format configured at the audio output pin must be the default, which would be plain PCM.
Logged
Yaobing Deng, JRiver Media Center

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4300
Re: Blackmagic Design devices - how do we support them better
« Reply #164 on: December 16, 2024, 12:20:14 pm »

Are you sending pcm or compressed?

Logged

alext77

  • Recent member
  • *
  • Posts: 36
Re: Blackmagic Design devices - how do we support them better
« Reply #165 on: December 16, 2024, 01:18:51 pm »

Hello.

The source sends LPCM multichannel or stereo but it can send DD 5.1 as well, I tested LPCM 2.0 and DD 5.1 and LAV audio decoder was not in the filter list in both cases, I will redo the test later on with a log file.

Thanks.
Logged
I’m a Windows 10 pro user. Currently enjoying JRiver 33.

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10978
  • Dogs of the world unite!
Re: Blackmagic Design devices - how do we support them better
« Reply #166 on: December 18, 2024, 01:39:04 pm »

Hello.

The source sends LPCM multichannel or stereo but it can send DD 5.1 as well, I tested LPCM 2.0 and DD 5.1 and LAV audio decoder was not in the filter list in both cases, I will redo the test later on with a log file.

Thanks.

After you try this and produce a log, I would like you to try the following too:

Go to TV Options, select your Blackmagic device and click Configure button.

In Advanced section, there is a list of DirectShow property pages. Look for "Audio Capture Pin...", "Video Capture Pin...", and "Video Capture Filter...". You may or may not have all of them. If you find "Audio Capture Pin...", double click it to bring up the property page.  If you don't find it, try "Video Capture Filter...". On the property page, do you see anything that allows you to select an audio format? If so, what are the choices?
Logged
Yaobing Deng, JRiver Media Center

alext77

  • Recent member
  • *
  • Posts: 36
Re: Blackmagic Design devices - how do we support them better
« Reply #167 on: December 19, 2024, 01:37:00 am »

After you try this and produce a log, I would like you to try the following too:

Go to TV Options, select your Blackmagic device and click Configure button.

In Advanced section, there is a list of DirectShow property pages. Look for "Audio Capture Pin...", "Video Capture Pin...", and "Video Capture Filter...". You may or may not have all of them. If you find "Audio Capture Pin...", double click it to bring up the property page.  If you don't find it, try "Video Capture Filter...". On the property page, do you see anything that allows you to select an audio format? If so, what are the choices?

Hello, I will do/check in few days. Thanks for your support.
Logged
I’m a Windows 10 pro user. Currently enjoying JRiver 33.

alext77

  • Recent member
  • *
  • Posts: 36
Re: Blackmagic Design devices - how do we support them better
« Reply #168 on: January 11, 2025, 01:34:17 pm »

Hello everyone.

I’m still there and motivated for testing my black magic device. I was sick during almost a month, next week I should be able to play with JRiver again.
Logged
I’m a Windows 10 pro user. Currently enjoying JRiver 33.

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10978
  • Dogs of the world unite!
Re: Blackmagic Design devices - how do we support them better
« Reply #169 on: January 15, 2025, 10:41:54 am »

Hello everyone.

I’m still there and motivated for testing my black magic device. I was sick during almost a month, next week I should be able to play with JRiver again.

I am sorry about your illness. Hope you have recovered well. Welcome back!

Currently I don't have anything to test. I will let you know when I make some changes. Thanks.
Logged
Yaobing Deng, JRiver Media Center

jsmith967

  • Junior Woodchuck
  • **
  • Posts: 74
Re: Blackmagic Design devices - how do we support them better
« Reply #170 on: January 15, 2025, 04:16:09 pm »

I'm also ready to test anything to move this project forward.
Logged

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4300
Re: Blackmagic Design devices - how do we support them better
« Reply #171 on: January 16, 2025, 02:01:52 am »

am I right in thinking that these devices/cards only support 48kHz audio? the specs and sdk manual would say this is true but would be good to know for sure
Logged

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10978
  • Dogs of the world unite!
Re: Blackmagic Design devices - how do we support them better
« Reply #172 on: January 16, 2025, 09:11:55 am »

I don't know.
Logged
Yaobing Deng, JRiver Media Center

claw

  • Recent member
  • *
  • Posts: 17
Re: Blackmagic Design devices - how do we support them better
« Reply #173 on: January 16, 2025, 11:01:59 am »

A year and a half ago, I was somewhat active in this thread...

https://yabb.jriver.com/interact/index.php/topic,131791.0.html

At that time, I used the WDM device and was trying to get HDR10 metadata applied since the DeckLink cards do not pass metadata.   I configured this metadata filter but it was only called for disk media playback and not for live input.

https://github.com/defl/directshow_metadata_injector_filter

That was when I halted my testing.

Has direction changed to use the Decklink device instead of WDM?
Logged

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4300
Re: Blackmagic Design devices - how do we support them better
« Reply #174 on: January 17, 2025, 02:05:11 am »

I realised recently that no capture card (that I can find) reliably supports 192kHz audio, they either support it but have implementation issues (magewell pro) or simply do not support it (everything else). Given this it must mean you're reliant on the source device to decode and produce LPCM audio or can only support AC3 (which seems unrealistic given how widespread eac3 is) hence I was wondering what source devices people are intending to use with this setup?
Logged

jsmith967

  • Junior Woodchuck
  • **
  • Posts: 74
Re: Blackmagic Design devices - how do we support them better
« Reply #175 on: January 17, 2025, 07:56:18 am »

I think the typical use case for this capturing feature is for the capturing HTPC to render only the video, not decode the audio too. As is the case with VideoProcessor w/ MadVR that many users want to replace with JRiver w/ JRVR, the capture device only processes the video and the audio goes to the AVR for decoding and processing. So for my setup, for example:

Streamer > AVR > HTPC Capture card > Display

The most desirable outcome sought here is Dynamic Tone Mapping (and secondarily scaling) for streaming sources. I am only interested in JRVR capturing 4K HDR and rendering using JRVR.
Logged

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4300
Re: Blackmagic Design devices - how do we support them better
« Reply #176 on: January 17, 2025, 12:57:06 pm »

Yeah I know people do that but I am interested in the pure htpc solution, I have no interest in needing to spend storm or trinnov money just to get enough channels and (barely enough) dsp capability
Logged

claw

  • Recent member
  • *
  • Posts: 17
Re: Blackmagic Design devices - how do we support them better
« Reply #177 on: January 17, 2025, 09:42:19 pm »

I realised recently that no capture card (that I can find) reliably supports 192kHz audio, they either support it but have implementation issues (magewell pro) or simply do not support it (everything else). Given this it must mean you're reliant on the source device to decode and produce LPCM audio or can only support AC3 (which seems unrealistic given how widespread eac3 is) hence I was wondering what source devices people are intending to use with this setup?

I too don't care about audio capabilities.  I have an Atmos sound system that the AVR feeds.  I won't give up Atmos for LPCM or less.
Logged

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4300
Re: Blackmagic Design devices - how do we support them better
« Reply #178 on: January 18, 2025, 02:43:03 am »

just to be clear, I know people want a videoprocessor replacement, I don't and my Q is not to those people. My Q is addressed to the people, if any exist, who also want audio put through here.
Logged

mastermind

  • Member
  • *
  • Posts: 4
Re: Blackmagic Design devices - how do we support them better
« Reply #179 on: January 18, 2025, 04:52:35 am »

I'm one of them. Ready to test!
Logged

OverTheAir

  • Recent member
  • *
  • Posts: 44
Re: Blackmagic Design devices - how do we support them better
« Reply #180 on: January 18, 2025, 01:09:24 pm »

just to be clear, I know people want a videoprocessor replacement, I don't and my Q is not to those people. My Q is addressed to the people, if any exist, who also want audio put through here.
It might be helpful for your purposes and enable more qualified responses from others, if you outlined more about potential use cases for audio through these cards, including potential limitations, so responders would know whether it would fit their anticipated requirements. A 100 people saying they want something, only to turn into zero because of other limitations probably wouldn't help you.
 
To illustrate with my example. Your earlier post suggested a pure HTPC solution with Storm/Trinnov channel counts and greater processing. If such a solution also had a robust way to decode Atmos (i.e. not relying on getting access to Dolby Reference Player unless Dolby changes its position on this) then I would be interested in such a solution and hence would want audio through the card. I ran a pure HTPC solution with soundcard direct to a power amp for decade with no AVR needed for up to 5.1 playback of Blu-ray, music, and recorded over the air TV, so I'm not a stranger to this solution. However, what caused me to get an AVR was a desire for Atmos, so if that wasn't also part of the HTPC solution then I wouldn't be interested in audio through the card.
Logged

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4300
Re: Blackmagic Design devices - how do we support them better
« Reply #181 on: January 18, 2025, 02:22:11 pm »

there's no known card that supports 192kHz audio reliably (the magewell supports it but, in my system at least, it can't do it reliably, have a ticket open with them to see if it's something they reproduce) so you have to route audio via an AVR if the source doesn't decode (as all modern codecs bitstream at 192kHz) hence I'm just curious what source devices people are using that happily decode everything to 48kHz multichannel lpcm

Logged

claw

  • Recent member
  • *
  • Posts: 17
Re: Blackmagic Design devices - how do we support them better
« Reply #182 on: January 18, 2025, 03:59:26 pm »

With an Apple TV 4K, if you set Audio Format to Auto and Dolby Atmos to OFF, it will output 24 bit 48kHz LPCM.  Depending on the content, it can be from 2 channel up to 7.1 channel LPCM.   Apple TV does not support anything higher than 48kHz.

Video and Audio format reported by HDfury VRROOM while playing a Netflix Atmos title:

VIDEO TX0:
4K59.941 593MHz 422 BT2020 12b HDR

AUDIO OUT:
L-PCM 48kHz 7.1ch 24bit
Logged
Pages: 1 2 3 [4]   Go Up