logo

Live Production Software Forums

www.vmix.com

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

Notification

Icon
Error
GPU usage, NDI sources on AWS - Trying to improve performance on a big production
Options
Go to last post Go to first unread
Previous Topic Next Topic
Geoff B  
#1 Posted : Monday, June 1, 2020 9:34:54 AM(UTC)
Geoff B

Rank: Advanced Member

Groups: Registered
Joined: 5/10/2020(UTC)
Posts: 104
Man
United States
Location: Sacramento, California

Thanks: 13 times
Was thanked: 5 time(s) in 5 post(s)
In my test, I'm running 3 vMix instances on the same VPC, sharing sources via NDI. Our AWS machines (g4dn.8xlarge) seem to be able to handle the massive amount of NDI inputs (24) as long as the GPU memory is below 100%. As soon as the "GPU Usage" indicator his 100%, we start getting dropped frames.

I do have "High Input Performance Mode" checked. Unfortunately, the number of video files in the show puts us over 100%.

Is there anything I could do (other than jettisoning half of our video assets) to help this?

Thanks so much, mates!
Back to top
WWW

Wanna join the discussion?! Login to your vMix Forums forum account, or Register a new forum account.
Back to top  
ask  
#2 Posted : Tuesday, June 2, 2020 8:26:39 AM(UTC)
ask

Rank: Advanced Member

Groups: Registered
Joined: 10/13/2012(UTC)
Posts: 1,161
Australia
Location: Melbourne

Thanks: 220 times
Was thanked: 199 time(s) in 181 post(s)
Try putting the video into list inputs rather than individual video inputs. Note. It is not recommended to run multiple instances of vMix on one PC (or VPC).
Back to top
Geoff B  
#3 Posted : Tuesday, June 2, 2020 8:32:48 AM(UTC)
Geoff B

Rank: Advanced Member

Groups: Registered
Joined: 5/10/2020(UTC)
Posts: 104
Man
United States
Location: Sacramento, California

Thanks: 13 times
Was thanked: 5 time(s) in 5 post(s)
Thanks for the tip about list inputs! I'm going to try that out!

Originally Posted by: ask Go to Quoted Post
It is not recommended to run multiple instances of vMix on one PC (or VPC).


I should have been more clear: Separate virtual machines, running in the same Virtual Private Cloud (so they can share sources via NDI)
Back to top
WWW
Geoff B  
#4 Posted : Thursday, June 4, 2020 11:59:27 AM(UTC)
Geoff B

Rank: Advanced Member

Groups: Registered
Joined: 5/10/2020(UTC)
Posts: 104
Man
United States
Location: Sacramento, California

Thanks: 13 times
Was thanked: 5 time(s) in 5 post(s)
Update: The trick that @ask suggested worked great! I'm able to keep my GPU memory < 100% and I've got 24 NDI sources working with render times in the single digits!
Back to top
WWW
jb-uk  
#5 Posted : Saturday, June 6, 2020 9:27:46 PM(UTC)
jb-uk

Rank: Newbie

Groups: Registered
Joined: 6/6/2020(UTC)
Posts: 5
United Kingdom
Location: London
Hi Geoff,

How did you achieve NDI connectivity between the EC2 instances? I have network connectivity (can ping, move files etc..) between EC2s in my single VPC but no NDI sources appear in the NDI Virtual Input tool when running test patterns out of either EC2. I have added them as remote sources in the NDI Access Manager too.

Just wondering if you had any tips? Or which EC2 instance types are best for NDI?

Regards,

Jon
Back to top
Geoff B  
#6 Posted : Saturday, June 6, 2020 11:08:16 PM(UTC)
Geoff B

Rank: Advanced Member

Groups: Registered
Joined: 5/10/2020(UTC)
Posts: 104
Man
United States
Location: Sacramento, California

Thanks: 13 times
Was thanked: 5 time(s) in 5 post(s)
Originally Posted by: jb-uk Go to Quoted Post
Hi Geoff,

How did you achieve NDI connectivity between the EC2 instances? I have network connectivity (can ping, move files etc..) between EC2s in my single VPC but no NDI sources appear in the NDI Virtual Input tool when running test patterns out of either EC2. I have added them as remote sources in the NDI Access Manager too.

Just wondering if you had any tips? Or which EC2 instance types are best for NDI?

Regards,

Jon


Jon,

You also need to open up the right ports in your security group(s). Port 5353 needs to be open for mDNS, which is how NDI sources are discovered. Then ports 5960+ (one for each NDI source on the network) need to be open for the actual signal.

More NDI troubleshooting tips can be found here.

I don't know if there is a "best" EC2 instance type. The real bottleneck is the GPU, and all the g4dn instances have the same GPU.
Back to top
WWW
mlange221  
#7 Posted : Tuesday, June 16, 2020 6:19:30 AM(UTC)
mlange221

Rank: Newbie

Groups: Registered
Joined: 6/4/2020(UTC)
Posts: 6
United States
Location: Madison, WI
NDI relies on multicast for the Auto-Discovery of sources to work properly. AWS does not support multicast workflows by default.

You need to open NDI Access Manager and enter the Private IP of the remote sources in the "Remote Sources" Tab.
Then you need to turn on UDP Send and Receive in the vMix NDI Config.

That will allow you to share sources on the subnet in AWS.
Back to top
WWW
Users browsing this topic
Guest
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.

Privacy Policy | Powered by YAF.NET | YAF.NET © 2003-2024, Yet Another Forum.NET
This page was generated in 0.212 seconds.