[Bug] Capture visualiser not working

[renebiemans]

Titan Two
Dell E6540 (Intel I5-4200m, 8gb ram, Intel HD Graphic 4600)
Windows 10 with last updates
Titan V14 Beta 44
TitanFixtureLibrary V14 30-7-2020 23:00.
Happens both in Dutch and English language

Test steps:
- New show
- patch 4 dimmers
- open capture
- manual dimmer at 100%
Capture grey screen
Changing settings (for example ambient lighting): still same gery screen.

[phb]

Hi Rene,

I wasn't able to reproduce this. When you say you see a "capture grey screen" - is this rendering the capture theatre but with no reaction when you activate the lights? Or is this the "capture visualiser not installed" error screen?

Are you definitely exiting patch? You cannot put fixture levels in the programmer whilst in patch.

Can you confirm what is shown in the "DMX" workspace window when you activate the lights?

Best,

[niclights]

Could this be driver related? Have you checked to see if there are any updates available for your display drivers?

[TWC]

I'm getting the same. Created a new show file for v14 with some 40 or so fixtures. Absolutely nothing appears on the internal vizualiser. Everything is working fine on capture running in a separate pc however, It seems much happier when you send sACN rather than artnet but that's nothing new.

[niclights]

Tom - are you able to try running v14 on the machine that the stand-alone Capture is working?

[TWC]

I don't have an avokey for that machine. I'm not 100% sure How the key works. Is it locked to the avo hardware or to a specific computer.?

[niclights]

The AvoKey is not locked to a machine. You should be able to move it without any problems.

[TWC]

Ive ran titan on my dedicated capture of and the internal vizualiser in titan works fine, that machine has a monster spec nvidia gpu though.

I see the other guy that said it doesn't work also has an Intel hd series gpu. It could be a driver issue I suppose. I'll try and find an updated driver for mine and see if It fixes it.

[TWC]

follow up, it's definitely an issue with the intel hd series graphics driver, there are certain driver revisions of the intel HD series driver that do not work at all with the internal visualizer, also it seems to affect some of the intel UHD series as well, stupidly i've written the offending driver revision numbers in my notepad and left it somewhere else but I will report back on this. it's also pertinent to report in my case where the Dell pc i'm using originally had an oem dell driver for the onboard gpu chip, when i switched to using the very latest driver from intel's website I ran into the dreaded fault where titan will not start till you turn off the igcgraphics update service or whatever it's called..

regards, Tom

[renebiemans]

Also an small update from my side:
I have two almost simular Dell laptops both with same graphic card (Intel HD Graphic 4600) with the same driver version (20.19.15.4835 date: 16-10-2017). Laptop 1 is working and Laptop 2 is not working both running the latest Beta 61 downloaded today.

[PBudd]

Rene is this with the same show file on both?

It would be potentially interesting to see the log files off of your laptop that isn't working. My email address is peter.budd [at] avolites.com if you want to send them over. I have seen an issue with a very similar symptom.

Pete

[renebiemans]

At first it was the same show file with the second test an empty showfile only patching some identical fixtures.

I have sent the log files to you.

[TWC]

The driver I have found produces the best results and all round stability for the Intel hd series gpu is 10.18.10.5059 which is dated 16/08/2018. Everything works, internal viz, NDI previews etc etc.

Hope this might help somebody else out in he future.

[renebiemans]

I had the same problem now also with an different computer which has one real graphic card and was connected to an dell d6000 usb-c docking station (also with graphic card). When I disconnected the D6000 capture was working. I have uploaded the log files to avolites and they have now reported this as an bug.

[phb]

Thanks all for your help reproducing this. We believe we may have now resolved this issue - we are probably going to release another beta before release, so if you were able to test this in that build that'd be great.

Best,