Blackmagic Forum

Hello,

There really seems to be an issue with the Web Presenter Firmware 2.1 when using it with the Constellation 8K. I work with a 1080p25 signal.

Here is the workflow I tested to generate the screenshot attached:

A. Media Player 1 still image in the ATEM Mini Extreme media pool -> Direct Stream to Youtube using built in encoder (Streaming High)
B. Media Player 1 still image in the ATEM Constellation media pool -> SDI IN Web Presenter HD (Streaming High) ->Stream to Youtube

Live stream B is way more saturated. Does that with anything you put into the Constellation 8K (cameras / computers...)

Anyone found a way to fix it ?



Thanks,

Actually you could just loop back the monitor output of the Webpresenter HD into the constellation and put it next the mediaplayer on Multiviewer.

You will see that the Output is oversatured of the Webpresenter.

Buddy my says the WPHD also says REC2020 in the display with HD signal on it.. But when you change the output of the Constellation to 1080P Level A the Webpresenter says Rec 709 and its fine..

Not tested this myself because still waiting on my delivery of the WPHD units....

Indeed thanks ! Just tried setting to Level A and it's fine... but that means we cannot use 25P / 30P / 24P etc... only 50p / 50i / 59.94i.... not good.

That is strange.. So you say that in 50i and 25P it will say Rec2020 instead of Rec709??

To be more precise

24p / 25p / 30p ---> Rec2020
50i / 50p / 59.94i AND Level A---> Rec709

I'm seeing the same problem.
Constellation at 1080p50 into Web Presenter HD - result is everything looks too saturated , and I personally look like I've been in the sun too long !
I cannot use Level A because my Audio Monitor doesn't support Level A.

Sigh , my transition to the constellation is looking troubled already.

I have the same problem

Ai, hopefully this will get fixed with a software update. Shouldn't be too hard really?

I just noticed another issue - as well as the BT2020 issue , timecode appears to stop being detected when using 1080p25 or 1080p50 level B.

I was in the middle of responding to a BM support request for more info when I noticed.

Yep experiencing the same issues with my Constellation and WP-HD. Somewhat disappointing. Somewhat embarrassing as I was blaming my captions/subtitles provider.

Vectorscope picture showing the problem

I note that the problem is not there with the Constellation set to UHD resolutions.

Andy Coulthurst wrote:Vectorscope picture showing the problem

661E4AF3-7461-4E2F-A261-8211520CF8E4.jpeg

That is an interesting scope, what is the function of the mirroring? Typically full field bars are 100% and SMPTE/ARIB Bars are 75%.

Good Luck

Howard Roll wrote:

Andy Coulthurst wrote:Vectorscope picture showing the problem

The attachment 661E4AF3-7461-4E2F-A261-8211520CF8E4.jpeg is no longer available

That is an interesting scope, what is the function of the mirroring? Typically full field bars are 100% and SMPTE/ARIB Bars are 75%.

Good Luck

I'm an ancient BBC engineer , so for me , Red patch VT bars are normally 75% ( 100% would be difficult for old analogue tape ).
The mirroring is just a hangover for a view similar to the old analogue Vectorscopes ( adding the look of the Pal 180 subcarrier switch on each line. I can turn that off by setting to component view ).
And I think you may be correct that the bars are100% out of the constellation , my mistake , I have the vectorscope set to the correct mode for the bars to match, either 75 or 100%

When viewing the direct signal out of the Constellation , this is the result.

Anyway - the bottom line appears to be that the Web Presenter HD is incorrectly choosing BT2020 when interpreting incoming colourspace for HD resolutions ( except 1080p50 Level A ) - it should be choosing BT709. For UltraHD it appears to be correctly using BT2020.

It would be interesting to see if its some strange interaction with the Constellation, or purely a Web Presenter HD problem.

I might dig out the TV Studio HD tomorrow and do another test.

Hope to get my units soon.. They are payed for last week.. But no shipping notice yet..

Got a Phabrix QX 12G here... That does Rec 2020 and Rec709 so it would be easy to find out which one is the culprit..

UK Support have confirmed they have reproduced the issue and the developers are looking to fix it.

Hello,

Anyone from Blackmagic has an ETA for this fix ? If it is actually fixable hopefully.

For the moment, the Web Presenter HD cannot be used with the Constellation.

Thibaud wrote:Hello,

Anyone from Blackmagic has an ETA for this fix ? If it is actually fixable hopefully.

For the moment, the Web Presenter HD cannot be used with the Constellation.

They wont tell you until it's there.. Sorry but that is how they operate..

Has anyone tried downgrading to version 2.0?

jri1234 wrote:Has anyone tried downgrading to version 2.0?

8.0 is the earliest with support for the Constellation.

Andy Coulthurst wrote:

jri1234 wrote:Has anyone tried downgrading to version 2.0?

8.0 is the earliest with support for the Constellation.

Sorry. Version 2.0 of Web Presenter HD firmware. Version 2.1 changelog says "Improve compatibility with Rec. 2020 video input signals." I'm wondering if 2.1 actually introduced the problem.

I think the problem is not specifically with the web presenter HD , it seems related to the constellation incorrectly marking REC2020 even in such resolutions as 1080p25.

I've tried to read up on how rec2020 is signaled , but I haven't found anything describing it. I've only seen mention that only 4k UHD should use rec2020 and in fact a tektronix document seems to indicate to manually select the colour gamut. Sadly my vectorscope only supports 1.5G so I cannot perform definitive tests to confirm exactly where the issue is. I may try some other equipment soon. It could be that this requires the Webpresenter to select rec709 for hd , and offer a manual choice of rec2020/rec709 for UHD.
I suspect this also means the Constellation might need a manual option.

If anyone has any detail on how or if rec2020 is signaled (ancillary packet) please comment.

This poster https://www.telestream.net/pdfs/technical/Creating-4K-UHD-Content-Poster_11W-60274-2-2.pdf suggests there is a flag in the VPID ancillary packet to indicate colour space.

I have now done some further checks and according to the Decklink SDK example app "Capture Preview" the Constellation is marking the video as Rec2020 when it should not.

Brilliant work. Here's hoping BMD fixes quickly.

Andy Coulthurst wrote:I have now done some further checks and according to the Decklink SDK example app "Capture Preview" the Constellation is marking the video as Rec2020 when it should not.

This is the case with multiple products from BMD that they dont send the correct Payload ID's.. So i'm not suprised...

So yes it probably an update that needs to be happening to the constellation rather then the webpresenter..

With the new Hyperdecks supporting HDR /Rec2020 - the Constellation might be incompatible. I've ordered two of the Hyperdeck HD Plus units ( I have had the Mini on back order for months ). I hope the Constellation firmware is corrected before they arrive.

Question for you Andy. We have a new build in progress with 1080p29.97. It goes Constellation (which we know incorrectly marks Rec 709 as Rec 2020), then to 2 x AJA 3G-AM embedders (only take up to 3G-SDI), then to an encoder (not the Web Presenter HD, but this encoder takes up to 4K60... so maybe/definitely Rec 2020). Do you think we'll have an issue? Or will the 3G-SDI embedders compensate for this issue?

jri1234 wrote:Question for you Andy. We have a new build in progress with 1080p29.97. It goes Constellation (which we know incorrectly marks Rec 709 as Rec 2020), then to 2 x AJA 3G-AM embedders (only take up to 3G-SDI), then to an encoder (not the Web Presenter HD, but this encoder takes up to 4K60... so maybe/definitely Rec 2020). Do you think we'll have an issue? Or will the 3G-SDI embedders compensate for this issue?

Sorry - I have no idea if the embedders modify the problem data , I would suggest they do not as they have no reason to.

You would probably have better chance going sdi->hdmi hdmi->sdi.

Andy Coulthurst wrote:You would probably have better chance going sdi->hdmi hdmi->sdi.

So - I tested this theory. I took one of the new bi-directional sdi/hdmi 3G converters and connected the hdmi input to the hdmi output. Feeding the sdi input from the Constellation and examining the 3G sdi output of the converter by sending to a decklink Quad2 capture card on a pc running the "CapturePreview" sample application ( it can show the Static Colorspace Flag ).

The output of the constellation shows "Rec2020" and the output of the converter shows "Rec.709".
Tested at 1080p25 , 720p50, 1080p50,1080p59.94,1080p24,1080i50.

However this does not appear to work at 1080p29.97,1080p23.98,720p59.94,( no video output from the converter )

Maybe this is helpful to some people as a workaround for the problem.

Andy Coulthurst wrote:

Andy Coulthurst wrote:You would probably have better chance going sdi->hdmi hdmi->sdi.

So - I tested this theory. I took one of the new bi-directional sdi/hdmi 3G converters and connected the hdmi input to the hdmi output. Feeding the sdi input from the Constellation and examining the 3G sdi output of the converter by sending to a decklink Quad2 capture card on a pc running the "CapturePreview" sample application ( it can show the Static Colorspace Flag ).

The output of the constellation shows "Rec2020" and the output of the converter shows "Rec.709".
Tested at 1080p25 , 720p50, 1080p50,1080p59.94,1080p24,1080i50.

However this does not appear to work at 1080p29.97,1080p23.98,720p59.94,( no video output from the converter )

Maybe this is helpful to some people as a workaround for the problem.

That is very sad. Unfortunate that it doesn't work for 1080p29.97. Even more unfortunate that it appears the converter doesn't even output video at 1080p29.97??

It may be a problem with the CapturePreview app - as I did manage to convert the output.
I may be able to test later , as my Vectorscope can manage 1080p29.97

Andy Coulthurst wrote:It may be a problem with the CapturePreview app - as I did manage to convert the output.
I may be able to test later , as my Vectorscope can manage 1080p29.97

Just checked with my vectorscope and all resolutions work , but I cannot check the rec2020 flag on the vectorscope.

Andy Coulthurst wrote:

Andy Coulthurst wrote:It may be a problem with the CapturePreview app - as I did manage to convert the output.
I may be able to test later , as my Vectorscope can manage 1080p29.97

Just checked with my vectorscope and all resolutions work , but I cannot check the rec2020 flag on the vectorscope.

Re-cabled my Constellation/Webpresenter HD , looking at the Webpresenter HD monitoring output all resolutions from 720p50 to 1080p60 work , and the monitoring states BT.709. I also note that timecode is passed through as well ( presumably because the 3G BiDirectional converter supports timecode over hdmi ).

So - for me it seems like a good solution , the resolution is automatic , and no up/down conversion. And all options are converted to BT709. The only gotcha would be that 3G A/B signaling would need to be manually selected in the Converter setup utility.

Andy Coulthurst wrote:

Andy Coulthurst wrote:

Andy Coulthurst wrote:It may be a problem with the CapturePreview app - as I did manage to convert the output.
I may be able to test later , as my Vectorscope can manage 1080p29.97

Just checked with my vectorscope and all resolutions work , but I cannot check the rec2020 flag on the vectorscope.

Re-cabled my Constellation/Webpresenter HD , looking at the Webpresenter HD monitoring output all resolutions from 720p50 to 1080p60 work , and the monitoring states BT.709. I also note that timecode is passed through as well ( presumably because the 3G BiDirectional converter supports timecode over hdmi ).

So - for me it seems like a good solution , the resolution is automatic , and no up/down conversion. And all options are converted to BT709. The only gotcha would be that 3G A/B signaling would need to be manually selected in the Converter setup utility.

Awesome. So this is SDI in to HDMI out. What about SDI in to SDI loop out?

So , the bidirectional converter can operate as two converters , sdi to hdmi AND hdmi to sdi.
In this configuration the HDMI in is looped to the HDMI out with a short cable.

Then feed the Constellation output ( upto 3G resolutions only ) to the bi-directional converter SDI input.
Feed the SDI converter output to the Webpresenter HD.

Hope that makes it clear enough.

Big fat warning when you buy the BiDirectional converters , SCAN in the Uk has sent me the wrong item on two occasions, in the end I bought from Thoman.de

Andy Coulthurst wrote:So , the bidirectional converter can operate as two converters , sdi to hdmi AND hdmi to sdi.
In this configuration the HDMI in is looped to the HDMI out with a short cable.

Then feed the Constellation output ( upto 3G resolutions only ) to the bi-directional converter SDI input.
Feed the SDI converter output to the Webpresenter HD.

Hope that makes it clear enough.

This is clear yeah. I knew it was bidirectional but never thought to loop the HDMI out to HDMI in. Clever.

So........ is BMD even working on this?

jri1234 wrote:So........ is BMD even working on this?

I was about to ask the same question , this taking too long. I can only hope they are creating a big update which will include this fix.

Mines are just sitting there on a shelf... useless. Thinking of reselling those.

Anyone knows if this has been fixed in the 4K version of the Web Presenter ?

Thibaud wrote:Mines are just sitting there on a shelf... useless. Thinking of reselling those.

Anyone knows if this has been fixed in the 4K version of the Web Presenter ?

It seems the problem is with the Constellation. The Constellation incorrectly marks it's Rec. 709 output as Rec. 2020. Any device that can take in and auto-detect Rec 2020 (such as the Web Presenter HD) will have the issue. Assuming my understanding is correct.

I can confirm that switching the Constellation to Level A will result in a 709 in the Web Presenter HD and 4k.

Andre Augustin wrote:I can confirm that switching the Constellation to Level A will result in a 709 in the Web Presenter HD and 4k.

I think this is only for 1080p50 and 1080p60 , not a solution for non 3G modes.

Found an interim hack that fixes this issue. You'll need a bi-directional SDI/HDMI micro converter. Just loop the signal through SDI/IN->HDMI/OUT->HDMI/IN->SDI/OUT to the Web Presenter and it seems to strip the gamma flag.

Has there been any movement on this issue? Would love to get the web presenter working with my constellation without outboard converters.

Ben Doyle wrote:Has there been any movement on this issue? Would love to get the web presenter working with my constellation without outboard converters.

No, there has been zero update or fix from Blackmagic Design..... could be that they just don't care. The niche of users with a Constellation and a Web Presenter is too small. So we have all these unusable web presenters sitting in a rack for a year now and we have to do our encoding with ATEM Minis instead.

Having issue with the timecode out of Constellation 8K, when it is running at 1080p59.94 Level B. This is a huge issue with HyperDecks and it is also apparent on the Teranex SDI Distro. I believe it is the same reason. The timecode would flash from the actual timecode then back to zeros.

I tried using the trick with a BiDirectional Converter (both 12G one and the 3G one), and I'm still seeing the issue. The converter does have 3 settings (SDI Level, HDMI Output & Audio Mapping) & it should just be the SDI Level - but I tried all different combinations & it hasn't seem to be fixed with any.

Norm Clare wrote:Found an interim hack that fixes this issue. You'll need a bi-directional SDI/HDMI micro converter. Just loop the signal through SDI/IN->HDMI/OUT->HDMI/IN->SDI/OUT to the Web Presenter and it seems to strip the gamma flag.

What settings do you have setup on that converter? And what version?

_____
I've managed to get it fixed by using a combination of Video Assist + a converter. I had an OUT from ATEM go into the Video Assist, HDMI out of Video Assist into the Converter, SDI out of Converter into any other gear. This has solved the issue, but this is also a very expensive solution & I would prefer not have to use a Video Assist.
Tried it also with a MDHX, but it strips the timecode.

Any help will be appreciated!