i already use excel file as list input. that works fine (drop down thingie) just asking about if there ase some sort of quicker way of selecting the right row in the list. if there is something i've missed. works great otherwise

I've added non-executable commands to use them into state dependency without executing, also I rewrite some code, so there can be errors, report them, please.
NDI monitor now works in low-bandwidth mode.

Download

@David Kaz, that's why it's not toggled by default. But count of buttons are not affect on CPU so much.

Try latest version, NDI monitor consume lot less CPU.

P.S. I don't see high CPU usage with only one state dependent button. In my case it's 9% in peak, 1-5% average.
My CPU is Intel Core i7 8750h.

Hi,

I have an issue with function "SetPanY" - does not work with any number combination (tried comma and dot, nothing worked) - Only accepts Integer, but not decimal numbers. "SetPanX" works fine tho.
My version is 8/27/2020.
Also, SetImage does not work unless I add timeout and then set blank image. Otherwise UTC crashes.

Thanks in advance!

Thanks, works fine now.
Unfortunatelly I'm not able to reproduce yesterdays problem - now seems to work just fine. Found nothing useful in logs directory (I'm looking in documents, correct me if wrong).

I have one more question. Would it be possible to link multiple timers together to "tick" in sync? I'm trying to make a hockey scoreboard. Everything works fine, but when I add penalty in middle of a match and then resume the play, both timers count at slightly different pace (tens or hundreds milliseconds) - it looks very bad even though the difference is minimal. When I add penalty at the start of a period, the problem is not there so it's not problem with delay in resuming. I suppose the problem is that the main clock counts even milliseconds and when add a new penalty timer, that penalty has milliseconds set to 0 and that's the cause of this offset. Some "link with" that would sync the ticking frequency with selected clock would be awesome. Maybe even rounding the milliseconds down in the clock widget would solve this issue.

Thanks again!

@elgarf Yes, I use ExecLink as it should be used. But the problem is not in starting at the same time (ExecLink does that perfectly) but in the pause time with milliseconds.
That would be awesome.

@Hall3008,
That's because UTC think, that value was not changed. You should use UpdateState command after SetText or Score widget.

Because of text changes in vMix, UTC should read new value from API, and push it to all mapped text fields, etc.

If you want just add some value, you can use UTC expressions, so changing will be executed at UTC side. Something like,

1 * _('Inputs[Input-Key].Elements[0].Text') + 1

P.S.

{0} works only in expressions =(

Greetings to all and thanks for the update. I have a question: what should I change to return with the NDI Monitor widget to a wider band, with reduced bandwidth is seen badly. Thank you very much once again! All good to all!

@elgarf, for me it is essential NDI Monitor because I transposed in UTC all the functions that I use from Vmix. In Vmix I load my graphics and that's it, the rest makes UTC and datasource. Thank you once again for all your support