Ok thanks

While we're in functions, I'am also working on adding:

SetOutputExternal2
SetOutputFullscreen2

So far it is not perfect but it works. Here's what I did:



My idea was to pick in the dropdown which input to use --> {0}. This is fine when Type is set to Input.

When Type is Output, Preview or Multiview it makes no sense but it works anyway... So I don't know what's best.

I tested two solutions

1 . create 2 separate functions
- the 1st one is for Output, Preview or Multiview ONLY with <FormatString>Function=SetOutputExternal2&amp;Value={2}</FormatString>
- the 2nd one is for Input ONLY. It could be called Set Input to Output External2 with <FormatString>Function=SetOutputExternal2&amp;Value={2}&amp;Input={0}</FormatString>

2 . stick to a single function for all use case but instead of picking the input in the dropdown, do :
<vMixFunctionReference>
<Description>Set Output External2</Description>
<Function>SetOutputExternal2</Function>
<FormatString>Function=SetOutputExternal2&amp;Value={2}&amp;Input={1}</FormatString>
<StringDescription>Type</StringDescription>
<IntDescription>Input Number</StringDescription>
</vMixFunctionReference>

where {2} can be Output, Preview, Multiview AND input and {1} is the input number

For this solution I think there are 2 cons:
- it is not presented in the logical order
- it is less "cool"

But you know better...

I'd like to implement these 2 new functions to extend vMix for a second operator to be able to make a 2nd switching for a beamer on external2 for example.
Also it is useful via NDI so that vMix UTC can select NDI source to monitor without affecting program.

Hi Elgarf!

Thanks for this new version.

I think "State Dependent" feature doesn't work anymore... But new look (circle leds instead of squares) is OK.

Regarding this feature, is it "safe" to invert initial ActiveStateValue so that it's red when active and green when not active?

I thought you would have added SetMultiViewOverlay, SetTextNative & SetImageNative (and maybe SetOutputExternal2, SetOutputFullscreen2) in functions.xml. Did you change your mind or simply forgot?



Also I didn't find this. Maybe it's related to not updating functions.xml?

Bien à toi,
Guillaume

PS : If you forgot to update functions.xml, maybe you can just attach it here...

Hi Elgarf

Yeah it works much better with a valid functions.xml.

However I noticed some "things"

- State Dependent works for some buttons but not all of them. It's ok for overlay toggle, but not for StartStreaming or StartRecording for example.

- SetMultiViewOverlay is OK unless we need an empty value for input (to remove one of the inputs in the multiview)
As soon as I use an empty field for an overlay, the small status led on the button turns red and most of the time UTC connection status LED also turns red.

Also there are 5 overlay possibilities in multiview, you only put 4 options in functions.xml. It's from 0 to 4 in API index, 1 to 5 in vMix GUI.
I added a 5th one in functions.xml. It's easy now!

- I'm a little confused with SetTextNative and SetImageNative. If I got it right I think you inverted these with regular SetText and SetImage.
So far when you used the term Native it's for internal UTC functions. But here Native seems to be for vMix. Is this what you wanted?

First I don't see any difference with SetText. Text indexes are always in 1st position, so Native or not, it's always the same index to use.
But for images, there is a difference. With SetImageNative, I must use the "image index" number as indicated by vMixAPI. With SetImage, I must use index number like before since you introduced the new state feature.

So basically, it works the opposite way I was expecting. But it works fine.

One more thing : what you call "title" for SetImage should be called "Index" I think. Title refers to xaml input. Here we must give the index number.


2 more observations:

- is it possible to invert state dependent colors? I asked about it before (if it was safe to do it 'cos I did it already)
I mean it would make more sense to have a red light when record or streaming are active. It is a standard. RED means ON...

- why not using StartStopRecording StartStopStreaming StartStopMultiCorder StartStopExternal instead of getting Start and Stop separate functions ?
I tried these, they work but the ActiveState is not happy. I always get a small red led in the buttons.

Here it is so far. Not tested the new MIDI feature yet...

Have a good day
Guillaume

Just sent you my log file for SetMultiviewOverlay issue.

I now understand better when/why it occurs, here's info on my multiview content :

background : color white
overlay 1 : other color input OR EMPTY (I have red light only when it's empty)
overlay 2 : NDI source (always on)
overlay 3 : xaml title OR EMPTY
overlay 4 : other xaml title OR EMPTY

I have these buttons:
button1 remove overlay1
button2 activates overlay1 with input
button3 removes overlay3
button4 activates overlay3 with input
button5 removes overlay4
button6 activates overlay4 with input

So now I understand that when overlay 1 is empty, UTC state gets wrong for all other overlays.
Same behaviour when overlay 3 is empty, 4 goes red

BTW it all works fine, only LED is wrong...

@JAIRODJ, at now there is no way to make this, maximum you can take name of the input by XmlDataProvider and put it to the title.

I think this task is for scheduler, but maybe someday I introduce full scripting into UTC. I'm thinking about IFStart/IFEnd commands for button scripts.

Hi Elgarf

quick feedback with new version

- the small leds in buttons seem to be broken. Only when it checks vMix states. Buttons with internal functions work fine.
> a simple button with only an overlay toggle has red small led

- for all overlay functions, you define 5 overlay options from 0 to 4. Should be 1 to 4.

- the state dependent LEDS seem to be broken for some functions:
> with startstoprecording it's ok
> with an overlay toggle it's not
(I did not check them all)

- there is a small typo in start/stop MultiCoRder

- vMix 19 now supports 10 inputs on multiviews overlays

Will do more testing later
Guillaume

@DWAM, ok, I fixed LEDs. Now all should be good.
Thank's for testing =)

Hi. How to add multicorder buttons, so I can start and stop recording for each input separately?

Hi Elgarf

Feature request:
would it be possible to add an OnCompletion command for Timers Widget so that we can trigger something when time is elapsed and still keep the OnStop for other triggers.
For example I would like to be able to trigger "StartRecording" "OnCompletion" but not if I stop or reset the timer manually or from another button.
Or I would like to start a different Overtime Clock when Period Time is elapsed.

At the moment the OnStop command also triggers the Stop hotkey which is not convenient when it is set for other purpose.

Also do you think it's possible to have something that could do time calculation. For example "if countdown reaches 2 minutes before the end, do something"

One question
I'm having a countdown where format for field mapping is "m\ \m\i\n\u\t\e\s"
It works perfectly for 1 hour countdowns max , but I would like "mm\ \m\i\n\u\t\e\s" (so that it shows "128 minutes" for example). But this doesn't work, when I indicate mm it won't show the word "minutes" anymore, just 128.


спасибо
Guillaume

Just gave it a try

Oncompletion works great for new timers but I think it broke compatibility with previous timers widgets in saved VMC projects.
Impossible to open a timer widget by clicking on the config icon, it makes UTC crash.

Sorry!

Remove the download link, there is no hurry for this.