I am very happy that the final release of v17 is so close :)
(And hope to perform a really cool test with NDI soon, tell you more about that as soon as I can).

But first two "oldies".

First, I have previously pointed out that there is a strange behaviour in how vMix stores Titles in the Preset. If a preset with Titles is saved, any alterations in the xaml file is not performed until that Title is either Changed (by clicking the Input's coq wheel and then OK) or closed and added again. Perhaps it is difficult to monitor changes in the xaml file (as is the case for Images), but in my humble opinion if a Preset is loaded the Titles should be loaded from the xaml file content, not what might be in the vMix preset file. Except of course for the Title Inputs Preset fields (eg Headline, Description, etc).

Second, while testing out v17 I have again frequently been puzzled by seemingly impossible errors (eg an Input is offline). Until I realize that the cause is I am running two instances of vMix. Please enlight me, are there any use cases where the possibility to run multiple instances of vMix is useful? If not I suggest that vMix inhibit this, or at least warns if a second instance is started.

Thanks.

Any changes to the XAML are saved in the preset to avoid overwriting the original file.
Overwriting the original file is problematic from a reliability standpoint but I am open to ideas on how to deal with this dilemma.



If others agree, I think I can get a warning added before release.

BIG BUG !!
Select NDI sources as Replay. Looks good in the live monitor, but the playbacks are black or distorted with horizontal trash lines in it.

This is one the best ways we were going to use NDI, and buy more copies of vMix. :-)

Steve

This isn't going to be a very helpfull post.

I have a VIX pro system that has been running without issue 24x7 for 6 months. The only down time was for routine maintenance, and planned upgrades. In short SOLID AS A ROCK, and an absolute testament to Studio Coast's excellence. Last night I upgraded to VMIX17.0.0.72 (Set it up in new folder so could roll back to V16 if any issues). Upgraded Desktop Capture to V17 (NDI version) on outboard PC's, and enabled NDI output of all 8 Decklink (Dual Quads) Input channels - No receivers enabled no the network so minimum CPU usage (1280 x 720 @ 50p) getting 50fps, CPU 11%. Approximately 6 hours later VMIX locked up (not responding), no obvious errors displayed, or in the log files (VMIX or Windows). PC itself was responding, sso shutdow, and broght back up as a V16 machine for todays live broadcasts.

I have a second system using 1 x Decklink Quad, and receiving NDI output from Caspar CG (with alpha), which has been running V17 without failure (apart from known bugs), since first Beta Release.

Oh if you want to install Desktop Capture V17 on a PC without installing the whole of VMIX you will need to download and install Visual C++ Re distributable Packages for Visual Studio 2013 - available HERE directly from Microsoft, if you don't already have it installed. (Martin maybe worth putting this on your NDI help page).

Will Try the same again tonight, and will report back - Sorry I couldn't provide any further information, and hoping this is just one of those random cosmic events, especially has this system has been used for active live production for a minimum of 16 hours each and every days since last November, without a single crash, lockup, or major issue.

All The Best

Keith

Screenshot of my laptop I am on:

Desktopcapture.

if Newtektools testpattern works should the desktopcapture not work also ?
Was able to uses someones little laptop ( allowed to install the tools) and the testpattern tools works perfectly. Trying to run the desktopcapture I quickly and very short get the message that windows is looking for a solution of the failing to start/run.

Guy

Installed vMix on other laptop starting destopcap from vMix directory --> works. little problem: doesnt properly display chooses open windows ie displays window that is on top of it also.

did same on own old crappy one and capture is running but only blak screen probably due to lack of aero

is the goal that desktopcapture wil be able to work as previously without having to install vMix there? ( sticking usb stick in to capture pc )

Guy

ok a little setback , but in case one would be allowed which .dll's woud need to be installed ? (dispite the NDItools working )

hope in some way the old deskstopcature will still be available (for none video capture)

ps desktopcapture only runs in previous situation when started from wihtin vmix directory not from other location like stick

I agree with that when producing live. But when opening a new preset I think that the configuration should come from the Title's xaml file, not what is stored in the preset.


That would be great!

In vMix 16, a Basic HD license could bring in 3 cameras and a desktop capture (perhaps a skype window).
This is a configuration we have been recommending for a particular use case.
Is this still possible in vMix 17, or is the NDI desktop capture always counted as a camera input?
If the latter, could the license terms be reconsidered to allow one NDI stream in addition to the 3 cameras?

Thanks for a great product!