Originally Posted by 3Z3VH
It's either use separate VLANs, or you need to do a bunch of QoS settings to prioritize the HDMI bandwidth.
One could VLAN one's IP video but not require that it use multiple VLAN segments or that one use moving among segments to switch.
VLANing it off is typically easier.
Setting up one VLAN is easy, creating many and trying to manage them through the (typically) miserable interface of the switch is much harder.
I wouldn't want my HDMI stream fighting for priority and bandwidth every time a new DHCP user joins the network and the entire subnet gets spammed with broadcast traffic, or little joey wants to watch the latest Disney video online, and gets inundated with UDP packets.
I would be more concerned about the installer of this gear creating problems with my data network. I have yet to see an Ethernet switch with multiple layers of security so that an installer or control box can only affect a limited set of VLAN segments. I also dislike non-standard implementations of a protocol. Given what is happening, why even do IP at all? Why not just use an Ethernet based protocol? Since these devices are not really routable, that would keep them protocol compliant.
Either one is sharing this infrastructure between regular IP traffic or one is just using a dedicated Ethernet switch. Either way, using standards like multicast would make controlling this easier as it would all be done on the just add power boxes, rather than requiring different drivers for each Ethernet switch.
The only scalability you will lack with VLANs is the ability to traverse a Layer 3 device such as a Router...
One also lacks the ability to easily change Ethernet switches, upgrade their firmware, requires that the person maintaining one's AV infrastructure is also maintaining one's data network infrastructure. All issues eliminated with a standard implementation.