VMIX PTZOPTICS UPDATE
VMIX PTZOPTICS WINDOWS 10

Step 9: In VMIX add input NDI / Desktop Capture – Local Desktop – select NDI2 Step 8: In VMIX add input NDI / Desktop Capture – Local Desktop – select NDI Step 7: Start Studio monitor again – confirm that Pixel 2 camera image is selected Step 5: Start Studio monitor – confirm that Proclaim screen is being picked up (Sanctuary-1 screen 2) Step 4: Start NDI 5 tools and then screen capture Step 3: (and following on VMIX computer unless otherwise noted) Start VMIX and load BASIC settings (just main cam and audio) Step 2: On proclaim computer start NDI 5 Tools and then Screen capture – close the tools window – capture leaves a tray ICON Step 1: Boot up both computers and Pixel 2 Xl (any order) It is very sequence specific and if steps are executed out of sequence, then the NDI source doesn't show up as available to be selected for input. I could be blaming the updates unfairly.Īfter some more testing, I have a work around solution but I am not thrilled with it. Just never had a problem like this before.

VMIX PTZOPTICS UPDATE

I will also see if there is a GPU driver update and I understand what you are saying about a backup before updates.

If the problem really is linked to the MS software updates, then LOTS of other folks should be running into this problem soon. I will go back today and continue to hack away at it. Both machines received additional MS feature upgrades, apparently just released yesterday, but nothing so far makes any difference.

VMIX PTZOPTICS WINDOWS 10

I haven't really tried this yet with our 'roving' WIFI camera (a repurposed Pixel 2 XL smartphone) but I will today.Īlso I upgraded the Windows 10 Home (sending) computer to Windows 10 Enterprise (been meaning to do that for some time). I sized the ROI as small as I could but it is still a problem. It would all work better if I had a second monitor on the VMIX machine so I would be less likely to move or open something over the ROI. The drawback is that I have to be careful not to open or move anything else into that ROI because it then shows up in the stream. VMIX then see that marked area as an NDI source for input. Then I start desktop capture and mark the studio monitor window as the ROI. Then I place the monitor window on a clear spot on my screen.

ON the receiving machine I start NDI 5 tools and studio monitor.

On the sending machine I start desktop capture and mark the region of interest (ROI) In fact I worked out a somewhat awkward solution for part of the problem (only temporary I hope). Yes, I can 'see' at least one of my NDI inputs using Studio Monitor.

Vmix ptzoptics