I'm NOT a network specialist, so please show some patience :-)

I have a minor network for video mixing. It has four PTZ cameras (video signal is send by SDI, but cameras are controlled using Visca/IP), one Windows tower PC (video mix cameras, movies etc.), one streaming PC, two NDI->HDMI-converters and one PTZ controller. So it is quite simple.
The PC has 3 NDI outputs. Two NDI-outputs goes from the tower-PC to two seperate NDI->HDMI converters (monitors). One NDI-output goes from the tower-PC to the streaming PC and one NDI-output goes from the streaming PC to the tower-PC.
When I turn on the PTZ-contoller every thing is fine, but when I turn og the cameras and the streaming PC's, the PTZ-keybord breaks down (after 10 minutes - 2 hours). I had long discussion with the vendor of the keyboard and they claims that it is a network issue and that the keyboard is overloaded with data.
I was deperate and tried to install a Unify-switch (out of the box) - enabled igmp and flow-control and everything works perfectly.
(I know I perhaps should disable flow-control. It is only enabled because it was a recommendation from NewTek the founder of NDI.)

I really woul like to go back to Mikrotik (I hate the Unify interface), but I have no clue to why the PTZ-controller (ether7) is overloaded with data. Did I do something fundemental wrong?

# feb/19/2021 16:04:26 by RouterOS 6.48
# software id = R8PN-LIAU
#
# model = CRS328-24P-4S+
# serial number = D7610C192C10
/interface bridge
add comment=LAN igmp-snooping=yes name=bridge1
/interface ethernet
set [ find default-name=ether1 ] comment=WAN
set [ find default-name=ether2 ] comment=CAM1 rx-flow-control=on \
tx-flow-control=on
set [ find default-name=ether4 ] comment=CAM2 rx-flow-control=on \
tx-flow-control=on
set [ find default-name=ether5 ] comment=CAM3
set [ find default-name=ether6 ] comment=CAM4
set [ find default-name=ether7 ] auto-negotiation=no comment=Controller \
full-duplex=no rx-flow-control=on speed=100Mbps tx-flow-control=on
set [ find default-name=ether8 ] comment=vMix1 rx-flow-control=on \
tx-flow-control=on
set [ find default-name=ether10 ] comment=vMix2 rx-flow-control=on \
tx-flow-control=on
set [ find default-name=ether12 ] rx-flow-control=on tx-flow-control=on
set [ find default-name=ether22 ] rx-flow-control=on tx-flow-control=on
/interface list
add name=WAN
add name=LAN
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=dhcp ranges=192.168.1.100-192.168.1.254
/ip dhcp-server
add address-pool=dhcp disabled=no interface=bridge1 name=dhcp1
/interface bridge port
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=ether6
add bridge=bridge1 interface=ether7
add bridge=bridge1 interface=ether8
add bridge=bridge1 interface=ether9
add bridge=bridge1 interface=ether10
add bridge=bridge1 interface=ether11
add bridge=bridge1 interface=ether12
add bridge=bridge1 interface=ether13
add bridge=bridge1 interface=ether14
add bridge=bridge1 interface=ether15
add bridge=bridge1 interface=ether16
add bridge=bridge1 interface=ether17
add bridge=bridge1 interface=ether18
add bridge=bridge1 interface=ether19
add bridge=bridge1 interface=ether20
add bridge=bridge1 interface=ether21
add bridge=bridge1 interface=ether22
add bridge=bridge1 interface=ether23
add bridge=bridge1 interface=ether24
add bridge=bridge1 interface=sfp-sfpplus1
add bridge=bridge1 interface=sfp-sfpplus2
add bridge=bridge1 interface=sfp-sfpplus3
add bridge=bridge1 interface=sfp-sfpplus4
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/interface list member
add interface=ether1 list=WAN
add interface=bridge1 list=LAN
/ip address
add address=192.168.1.1/24 comment="LAN IP-subnet" interface=ether2 network=\
192.168.1.0
/ip arp
add address=192.168.1.20 interface=bridge1 mac-address=F8:75:A4:50:B3:89
/ip dhcp-client
add disabled=no interface=ether1
/ip dhcp-server config
set store-leases-disk=3d
/ip dhcp-server lease
add address=192.168.1.20 client-id=1:f8:75:a4:50:b3:89 mac-address=\
F8:75:A4:50:B3:89 server=dhcp1
add address=192.168.1.21 mac-address=00:D0:B8:11:A8:13 server=dhcp1
add address=192.168.1.8 mac-address=80:1F:12:FA:18:C4 server=dhcp1
add address=192.168.1.7 mac-address=80:1F:12:FA:63:C2 server=dhcp1
add address=192.168.1.10 mac-address=80:1F:12:FA:7A:AB server=dhcp1
add address=192.168.1.9 mac-address=80:1F:12:FA:81:48 server=dhcp1
add address=192.168.1.31 client-id=1:24:4b:fe:58:db:ac mac-address=\
24:4B:FE:58:DB:AC server=dhcp1
add address=192.168.1.30 client-id=1:74:da:38:ff:41:1a mac-address=\
74:DA:38:FF:41:1A server=dhcp1
add address=192.168.1.35 client-id=1:92:a1:da:a:b7:69 mac-address=\
92:A1:DA:0A:B7:69 server=dhcp1
/ip dhcp-server network
add address=192.168.1.0/24 gateway=192.168.1.1 netmask=24
/ip firewall address-list
add address=192.168.1.0/24 list=OurLocalLan
/ip firewall filter
add action=accept chain=input comment=\
"Allow access to the router from the LAN using address list" \
src-address-list=OurLocalLan
add action=accept chain=input comment=\
"Allow established and releated connections" connection-nat-state="" \
connection-state=established,related
add action=drop chain=input comment="Drop all other trafic o the router"
/ip firewall nat
add action=masquerade chain=srcnat out-interface-list=WAN
/ip service
set ftp disabled=yes
set www disabled=yes
set api disabled=yes
set api-ssl disabled=yes
/system clock
set time-zone-name=Europe/Copenhagen
/system identity
set name=vMixMikrotik1
/system ntp client
set enabled=yes primary-ntp=99.104.170.138 secondary-ntp=92.246.24.228
/system routerboard settings
set boot-os=router-os
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN

Since your setup is really small - do you really need multicast? Looks like every NDI source connects to one destination only. Quickest way would be going unicast.
Apart from this, your config looks good to me.
-Chris

My two cents:

/ip neighbor discovery-settings set discover-interface-list=none

Given that the largest volumes of data in the network should be the video streams, I'd assume there's rather some kind of packets the keyboard doesn't know how to handle, which may cause an overflow of some buffer despite a negligible volume. So disabling MNDP, CDP and LLDP the way above might help.

Since your setup is really small - do you really need multicast? Looks like every NDI source connects to one destination only. Quickest way would be going unicast.
Apart from this, your config looks good to me.
-Chris

No I don't need (have) multi cast, but it is a NDI-recommendation to enable IGMP.

Apply the following settings when possible:
• DISABLE Quality of Service
• DISABLE Jumbo Frames
• ENABLE Flow Control as Asymmetrical or simply as On (required for TCP data transfer
using versions prior to NDI® 3.5)
• ENABLE IGMP Snooping if using multicast (mDNS is automatically blocked by many
switches when snooping is enabled—refer to documentation from your switch vendor)
• CONFIGURE IGMP Querier and Query Interval for each switch in multi-switch networks
when using multicast

My two cents:

/ip neighbor discovery-settings set discover-interface-list=none

Given that the largest volumes of data in the network should be the video streams, I'd assume there's rather some kind of packets the keyboard doesn't know how to handle, which may cause an overflow of some buffer despite a negligible volume. So disabling MNDP, CDP and LLDP the way above might help.

I'll look into that. Will SwOS make something good for me?

Man, I know - I'm working with NDI almost daily ;-)
We made very good experience with UDP unicast (tcp tends to be laggy from time to time).Even two or three destinations work well in this setup.
Unfortunately, I don't have any experience with MikroTik switching (using them as routers only), all our switching is Cisco 9300...
-Chris

My two cents:

/ip neighbor discovery-settings set discover-interface-list=none

Given that the largest volumes of data in the network should be the video streams, I'd assume there's rather some kind of packets the keyboard doesn't know how to handle, which may cause an overflow of some buffer despite a negligible volume. So disabling MNDP, CDP and LLDP the way above might help.

That is a very good point, good you spotted this. Wouldn't be the first device freaking out on neighbor discovery. Definitely worth a shot.