logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
richardgatarski  
#1 Posted : Wednesday, August 27, 2014 10:03:50 AM(UTC)
richardgatarski

Rank: Advanced Member

Groups: Registered
Joined: 2/18/2014(UTC)
Posts: 1,811
Location: Stockholm

Thanks: 137 times
Was thanked: 292 time(s) in 246 post(s)
Perhaps it's only me, but many times I by mistake start vMix even though it is already running. Of course every time I soon find out when I try to use a camera input that's already in use. My first thought was that vMix should not allow multiple instances and say "vMix is already running". But perhaps I am missing some points with having multiple instances of vMix.

Any thoughts?
rrpro  
#2 Posted : Wednesday, August 27, 2014 6:29:33 PM(UTC)
rrpro

Rank: Advanced Member

Groups: Registered
Joined: 5/17/2014(UTC)
Posts: 54
Location: Lisbon

Thanks: 5 times
Was thanked: 1 time(s) in 1 post(s)
In one hand I don't see the usage of 2 instances if most video sources are only allowed at 1 app but If we are mixing 2 different projects on 3, 4, 5 monitors it makes sense to have multiple instances running.
lbgaus  
#3 Posted : Thursday, August 28, 2014 12:59:18 AM(UTC)
lbgaus

Rank: Advanced Member

Groups: Registered
Joined: 11/30/2013(UTC)
Posts: 164
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)
I believe vMix is only intended for single-instance usage.

I find running multiple instances potentially problematic as the external outputs that present virtual DirectShow capture devices to other programs would have a conflict, as each new instance of vMix would not have exclusive control over that virtual capture device. (I believe you only get one "vMix Video Device" for External 1 and one "vMix Video Device #2" for External 2 if you have the 4K version)

Additionally, there is only one set of vMix global app settings (user.config file stored in AppData\StudioCoast_Pty_Ltd) which could cause manageability/confusion problems with identical settings at launch for things like Fullscreen/Fullscreen2 screen position, etc...

Third, the vMix webserver binds to TCP port 8088, and if that port is already bound that service will fail to start. Changing that port changes the global app settings file, which will not really do anything good because other instances will eventually read from the same settings, maybe during runtime but definitely during initial loading.

While vMix could theoretically function in limited capacities in multiple instances, based on what I've learned with the program I would just build a second switching system because it will avoid a lot of headaches.
Users browsing this topic
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.