Profile photo of ahjeff

Hi clarocque

Firstly, the net bridge warning (it is intended to be a warning, and later metalwork aims to reflect this by using a yellow LED with a warning triangle) comes on for ~3 seconds when the network bridge has discarded a control packet. This would happen because the net bridge packet buffer did not have space for said packet, and is not related to the cable used in any way. These packet drops can safely be ignored if there is no problem with the operation of the surface.

Some tasks use more control bandwidth, for example recalling a show, causing the net bridge LED to come on. However, because the control communication uses TCP/IP, any discarded packets are simply resent, with no noticeable effect to the user (the show might take a few milliseconds longer to recall, for example).

The audio has complete priority over any control messages, so even if the network bridge warning was permanently on, the audio would not be interrupted.

The net bridge has around 10 megabits/second of bandwidth. Normal iLive operation uses around 1.5, as does an Editor session. So you should be fine running Editor via the ACE connection.

If many packets were being dropped by the network bridge, the associated LED would be permanently on, but you still might not notice anything unusual on the surface. The first noticeable effect of network bridge packet drops would be metering on the surface appearing to ‘stutter’, but this should only happen if the net bridge is being heavily loaded, for example by somebody copying a large file, or trying to stream video through it.

hope this helps

– Jeff, A&H