Windows 10 - Dynamic backgrounds will not render

Hello Proclaim team,

I'm having a strange behavior on a fairly new Windows 10 laptop. Whenever I load an animated slide background, or embed something such as a video, this specific system will briefly (less than a second) show the content, and then display a black background where the animated content would be. Text super-imposed over this (such as lyrics) displays as expected, but the dynamic content simply doesn't display.

This occurs in both preview and on-air display. Other systems render the content properly from the same presentation, and I've tried several presentations/backgrounds with same result.

Recommendations on how to troubleshoot this? I've tried adjusting my scaling, hardware acceleration, etc to no effect. Also, video drivers are modern and up to date.

Kindest Regards

Find more posts tagged with

Comments

Peter June

Hi, Ryan, and welcome to the forums. This is a known issue which should only impact Windows machines that are in the "Edit" mode (it should not affect your presentation when it goes on air). So far we're still trying to track down the cause of the bug; if you have any further information that could help us reliably reproduce the error please let us know.

Ryan Smith

https://community.logos.com/discussion/comment/775055#Comment_775055

Hi Peter -- thanks for the response (and the welcome)

For me, this happens in Preview & Edit mode, and also happens when I go on-air unfortunately, so even a live presentation has the same end result. I first believed my videos were corrupt until I saw them running properly via another machine sync'd to the group.

The issue has effectively made it impossible for me to use this machine as a review/edit/backup presentation system in our workflow. Right now, not a horrible issue, but certainly hampers my ability to help our collective presentation team :-(

I'm happy to help collect system info for the issue if it assists.

Peter June

Ryan, are you able to reproduce the black screen 100% of the time on the Windows 10 machine? We've had trouble finding any kind of reliable reproduction, short of knowing that it happens from time to time.

A copy of your dxdiag could be helpful. Instructions for posting that can be found here.

Ryan Smith

https://community.logos.com/discussion/comment/775137#Comment_775137

Peter, it is unfortunate for me that it happens all the time, but sounds like this might help you. Attached are my DXDiag outputs in hopes it will help you find the root cause

I've tried multiple monitor configurations (using internal display only, using a mini-dp to vga, mini-dp to DVI converter, etc). . I'll be the guinea pig to help sort this out. To clarify, it only happens on slides with motion backgrounds or embedded video content (nearest I can isolate). The OSB appears to work just fine.

0410.DxDiag.txt

Thank you greatly for your responses and support.

Scott Alexander

https://community.logos.com/discussion/comment/775186#Comment_775186

Thanks for posting the dxdiag file. I can see that you have an integrated Intel video card with 128mb of dedicated memory. This is pretty low for dedicated memory, we like to see 1gb. There are also issues with onboard Intel video cards, more info in this article http://support.proclaimonline.com/hc/en-us/articles/205975795-What-should-I-know-about-my-graphics-hardware-

You may be more successful if you run fewer applications at once (free up shared video memory) while running Proclaim.

Even in 2015 video playback on Windows is a tricky thing. The wide variety of card manufacturers and hardware specs make it impossible for us to pin down an exact minimum system requirements for Proclaim.

Ryan Smith

https://community.logos.com/discussion/comment/775236#Comment_775236

Scott, thanks for the thorough explanation. I hadn't considered the fact I'm using integrated graphics on this system, and there'd likely be limitations.I'll keep this as ammo for me to build a dedicated tower for use at home vs an ultrabook. Meanwhile -- our primary author and presentation system works wonderfully, so we're good.

Thanks for closing the loop on the suspected cause of this.