Rank: Member
Groups: Registered
Joined: 2/9/2019(UTC) Posts: 27  Location: Berlin Was thanked: 2 time(s) in 2 post(s)
|
We recently ran a show with over 150 inputs. It worked well with the High input performance mode, but GPU Mem still went up to over 60%.
It would be really good to have the inputs ready for building a rundown of the show but enabling the inputs only for the timeslots needed, so vmix does not have to render the multiviews the whole time. For now I could use hotkeys to change multiviews from simple colors to camera inputs but that takes quite some time to setup.
Another use case would be for incoming connections. We might have a show with up to 50 SRT inputs soon. Same idea. Build your rundown to the show but only enable the connections needed for the moment to save bandwidth.
Found the feature request for that also here:
/posts/t21495-Pause-SRT-input--or-allow-API-to-enable-disable-SRT
Anyways thanks for the great software. I've been pushing the use of vmix in our company for several years now and at the moment our business mainly runs on vmix in these corona times. Keep up the great work!
Paul
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/20/2014(UTC) Posts: 2,721   Location: Bordeaux, France Thanks: 243 times
Was thanked: 794 time(s) in 589 post(s)
|
vMix already provides everything you're talking about.
You can add and remove inputs via the API which makes it possible to have various sets evolving through time
You can build your multiviews dynamically to switch inputs as you need and use the Mix inputs to switch directly within your multiviews
Check the shortcuts command list - there's already everything you need - and maybe use some external comtrollers like Panel Builder or UTC (or just a webpage) to design the specific interface you need to have a easy way to manage your project inputs on the fly.
Alternatively you can also "hide" some inputs so that there's no need to render their thumbnail view, you can move inputs from one place to another with simple mouse drags during your production.
For very large projects, I also recommend to use several vMix instances (one dedicated for incoming SRT for example) with submix or NDI bridge in between the primary and the auxilliary vMix.
Guillaume
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 4/23/2017(UTC) Posts: 1,214 Location: Germany Thanks: 3 times
Was thanked: 168 time(s) in 150 post(s)
|
What I do is to use the color tags. This way you can drill down to just the inputs needed.
For the multivies you might want to use the build in mini mixers. maybe they make it simpler.
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 2/9/2019(UTC) Posts: 27 Location: Berlin Was thanked: 2 time(s) in 2 post(s)
|
Originally Posted by: DWAM  vMix already provides everything you're talking about.
You can add and remove inputs via the API which makes it possible to have various sets evolving through time
You can build your multiviews dynamically to switch inputs as you need and use the Mix inputs to switch directly within your multiviews
Check the shortcuts command list - there's already everything you need - and maybe use some external comtrollers like Panel Builder or UTC (or just a webpage) to design the specific interface you need to have a easy way to manage your project inputs on the fly.
Alternatively you can also "hide" some inputs so that there's no need to render their thumbnail view, you can move inputs from one place to another with simple mouse drags during your production.
For very large projects, I also recommend to use several vMix instances (one dedicated for incoming SRT for example) with submix or NDI bridge in between the primary and the auxilliary vMix.
Guillaume Hi Guillaume, I think you got me wrong on that part. I know this all works with moving around inputs, but this is my workaround. And the workaround takes too much time to setup. I am not running a reocurring show where I can perfect the setup on the go. We work with different clients every other day and have to quickly be able to setup a rundown. What is needed is an actual DISABLE and ENABLE. Also hiding them or moving them to groups does, as far as i can tell, still use system resources. So this would not help. For the 50 SRT inputs I will definitely use more than one vmix machine anyway. But then sending extra NDI over would clog the network even more.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 8/21/2017(UTC)
Posts: 319
Location: Uk
Thanks: 26 times
Was thanked: 33 time(s) in 29 post(s)
|
+1 we have an issue to do with the network where we need a back up mode if things are playing up but we cant have both open throughout the production - if we need too and the cameras keep dropping out we could disable the main way and enable the other method
|
|
|
|
|
|
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
