Collisions don’t happen – networks are full duplex with store and forward, so there is only ever one packet going in each direction along a particular piece of cable.

Now a switch might have to hold a packet for a small fraction of a second, but that isn’t a collision.

For collisions you need either a non duplex system or a hub.
Both are now considered stone age.

Indeed, we’re running off topic, so I’ll also put a final note. 😉

Using TP cables and switches there only are peer-to-peer connections with separated transmit and receive paths (full duplex connection). Technically there is no chance for collisions, even if plenty devices are concurrently connected to the same switch and sending data.
The switch exactly knows to which port he has to forward particular packets and keeps them inside internal send buffers until the target port is idle. There are also priority queues to decide which packet will be sent next and which may have to wait even longer.
The switch takes care of this, nothing the Qu or the stagebox has to bother with.
While there are no collisions, packet loss may still occur if the bandwith of the target port can’t handle the traffic in time and the switch runs out of packet buffers.
That’s why it is essential to prioritize dSnake traffic over anything else when building VLANs to ensure nothing gets lost there. Other communication like QuPad control are running via TCP which easily deals with lost (and even duplicated) packets.