Hi,

Have you tried the latest vMix Desktop Capture download? (17.0.0.62)
A fix was added a week or so back that means it can now be run on most systems without needing to install anything.

I tested this by running it on a brand new Windows 7 SP1 installation with nothing else installed.

Just need to extract the zip file into a directory, or even have that directory on a flash drive and you are good to go!

Regards,

Martin
vMix

Can you install NDI Tools (ndi.newtek.com) on that system and see if NDI Monitor will see the output of the desktop capture tool? It would let you know if the problem is network related or with the system itself?

Kane Peterson
NewTek

I had the same problem of black NDI Desktop Capture last weekend.

At times it's just not possible to install special apps to other computers :/

doggy,

While vMix Desktop Capture is running but you see black for Display 1 in vMix double click the "Ready (x connections)" text
and it should bring up an error log window if there is an error preventing the screen from being captured.

I will have to investigate why it is not showing the windows, might be an older Windows 7 thing, less likely to be because something isnt installed (try enabling aero if its not enabled already)

To have the old capture also integrated into V17 would be really nice — the old capture catch almost every old PC :-).

(DesktopCapture17 != DesktopCapture15)

DesktopCapture17 looks to be a very promising new option, however, it after testing it on a variety of systems, we have deemed it's functionality to be of beta (not release) quality. Simply put, while it is very fast, we found it very unreliable, and difficult to work with as a replacement for our use.

The design decision to remove support for the "legacy" desktop capture also breaks all customer presets that made use of that major feature.

Customers that purchased copies of VMix for it's excellent desktop capture feature may find Version 17 to currently be un-workable for thier setup.

The design decision to suddenly remove support for a major feature is an unusual move in software publishing. The common industry practice is to "fork" the code, and continue to permit the limited use of the legacy feature, while encouraging the adaptation of the new replacement feature.

This allows customers time to adapt to the new feature, and allows the publisher time to work out any major adaptation issues that users report. Futher, this ensures that users can place faith in the product's given major features will not suddenly change in a way that might render the software to be unusable.

This is especially important for "big ticket" software, where a company invests into a given system and builds onto the system with high dollar hardware and training.

Simply put, business invest into systems they can rely on, and they expect publishers to follow industry standards in producing upgrades that are reasonably compatible with their investment.

As a software developer and publisher, I see no technical reason why the code could not have been easily forked to provide both the legacy desktop capture, and the new desktop capture. I am also reasonably certain that the new desktop capture feature was not sufficiently tested as a working replacement before release.

The only reason I can come up with for the decision to remove legacy capture support is some sort of unknown licensing or legal issue.

If licensing is not the issue, then in my professional opinion, this was a poor design decision, and there is little technical reason why it could also not be easily remedied.

Since we do not know the reason, customers must now question their investment in VMix, since major feature changes may not be handled in an industry standard way.

In other words, can your business afford to invest into a system that may change on a whim?

I do hope we get some support for legacy capture.

If it is a licensing issue, then perhaps Martin would share the specifications for the input, perhaps a code example snippet, and allow users to compile their own version of the capture app, or provide a dll that would connect it somehow to vMix.

Actually, the specifications for "userInput" dll is a great idea, regardless of the status of the legacy desktop capture issue.

What do you say Martin? Can you give us an easy hook?

Do that, and you might find a really nice 3rd party marketplace for VMix add on's!

I will start a seperate thread for that request :)

Joe

Trying to get Desktop Capture in vMIx 17 to work with MacBook pro.

vMix PC = i5 6600K @ 3.5GHz, 16GB RAM, Nvidia GTX 750 Ti

MacBook Pro = MacBook Pro (13-inch, Late 2011), 2.8 GHz Intel Core i7, 8 GB RAM, Intel HD Graphics 3000 512 MB
latest Desktop Capture is running.

vMix PC and Macbook are connected directly with 1 Ethernet cable.

vMix PC show, MacBook Pro with multiple NDI source options from the MacBook including the Google Chrome as an input.

All inputs remain black all the time.

What should I do to resolve this?

Thanks!

OSX 10.11
Windows 10 on the PC

That's interesting, is it 32bit windows?

Most of the increased CPU cases I have seen have been a result of the faster capturing frame rate now possible.
For example on some older machines that would capture the entire desktop at around 8fps can now do 20+fps but at a higher CPU usage as a result.

Can you double check to confirm both old and new reach 25fps?

It's win7 32bit.

edit:
I was comparing 2 different PC's.

The old desktop capture does on this PC also 60% cpu and max 4 fps.
The new desktop capture does 7 fps, therefore it works better anyway :)
Don't know why this PC has such problems with the desktop capture.

Tested both desktop capture program on a HP DC7800 (core2duo 3GHZ E8400):
old: 17fps (35% cpu)
new: 25fps (40% cpu)