Rank: Member
Groups: Registered
Joined: 9/12/2021(UTC) Posts: 22   Location: Medicine Hat, AB Thanks: 1 times
|
One of the issues I always have is, when I'm building a VMIX session from scratch, there is always lots of trial and error as I can scripting and shortcuts set up (Buttons on my Streamdeck)
As I move through the design phase, lots of things change. Channels get re-arranged and renamed as I hone in on the final session.
I find, though, when I move channels around and/or rename them, the initial scripts and shortcuts I setup have to inevitably be re-done so that they stay operational.
What would be REALLY nice is, when a channel is created (regardless of its function) an ID is assigned to it. One that stays with it no matter what, and is not editable. This ID could be referenced to instead of INPUT # or INPUT NAME. This would create the ability to build scripts that are INPUT specific regardless of their name or INPUT number and when they're moved around and/or changed, the script stays working. Obviously this wouldn't be the case if the input TYPE changed (audio vs. camera vs. image, etc...) but that's obvious, and the script wouldn't work.
I'm sure there are issues with this suggestion that I'm not thinking of... but it would make setting scripts and shortcuts much easier during the development phase.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 12/24/2021(UTC) Posts: 508  Location: athens Thanks: 123 times
Was thanked: 71 time(s) in 67 post(s)
|
Hello. The input key that exist and is unique for every input. Also in many cases you can use input names. Personally the problem i see is with mix inputs where if we have for example 3 mix input 2/3/4 and you move them around back-forward they change numbers so there exist problem. Hope in a future version vmix team will fix this
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 9/12/2021(UTC) Posts: 22 Location: Medicine Hat, AB Thanks: 1 times
|
Originally Posted by: nikosman88  Hello. The input key that exist and is unique for every input. Also in many cases you can use input names. Personally the problem i see is with mix inputs where if we have for example 3 mix input 2/3/4 and you move them around back-forward they change numbers so there exist problem. Hope in a future version vmix team will fix this Of course. Having a machine-assigned ID on an input would solve this problem. If I set a script to utilize "&Input=3" then re-arrange the inputs... that script will no longer work. Similarly, if I set a script to utilize "&Input=INPUT NAME" and that Name changes... the script will stop working. However, if the input has a Machine coded ID number... I can use that ID in the script, and know that regardless of whether I move or rename the input, it will ALWAYS work.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 7/4/2021(UTC) Posts: 308  Thanks: 8 times
Was thanked: 40 time(s) in 35 post(s)
|
As stated, this already exists.
Open your XML by going to the web controller address and append /api to the end of it.
The input key is a GUID that you can use in shortcuts and scripts. It will also persevere across multiple presets if you append the input.
Personally, I find it easier to use input names, by giving each input I need to control a unique name and then not changing it, but using the input key is something that a lot of people do.
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 9/12/2021(UTC) Posts: 22 Location: Medicine Hat, AB Thanks: 1 times
|
Originally Posted by: WaltG12 As stated, this already exists.
Open your XML by going to the web controller address and append /api to the end of it.
The input key is a GUID that you can use in shortcuts and scripts. It will also persevere across multiple presets if you append the input.
Personally, I find it easier to use input names, by giving each input I need to control a unique name and then not changing it, but using the input key is something that a lot of people do.
Sorry. I misunderstood the previous post. I didn't realize you could get an input ID by opening the XML. It would be nice if that ID was visible from the front end. This is good to know. Thank you to both.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 11/23/2020(UTC) Posts: 170 Location: Wichita Thanks: 10 times
Was thanked: 24 time(s) in 20 post(s)
|
Originally Posted by: WaltG12 As stated, this already exists.
Open your XML by going to the web controller address and append /api to the end of it.
The input key is a GUID that you can use in shortcuts and scripts. It will also persevere across multiple presets if you append the input.
Personally, I find it easier to use input names, by giving each input I need to control a unique name and then not changing it, but using the input key is something that a lot of people do.
Only one thing to note, if you Delete an input and then add it again, it will get a NEW key, and of course not be restored to any other uses you had previously set up for it. But if you don't do that to any major input you should not run into that as an issue.
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 9/12/2021(UTC) Posts: 22 Location: Medicine Hat, AB Thanks: 1 times
|
Originally Posted by: Roy Sinclair
Only one thing to note, if you Delete an input and then add it again, it will get a NEW key, and of course not be restored to any other uses you had previously set up for it. But if you don't do that to any major input you should not run into that as an issue.
Makes perfect sense. You can't delete an input and add it again. It will always be a new input you're adding. Thanks for the reply.
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
Important Information:
The vMix Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close
