MIDI clock and maximum number of devices on a USB hub - is this a bug or a feature?

bagaeta · September 17, 2026, 2:00am

This may be a known feature but I couldn’t find anything in the forum with my keyword searches so thought I’d report it…

My Bome box runs the latest firmware.

My setup is moderately complex and all the routing is currently handled directly in the Bomebox rather than using MIDI Translator projects. I have attached a diagram showing 2 variations in the setup. One uses 2 USB hubs, one of which has 10 devices attached to it. The second uses 3 USB hubs and the maximum number of devices on each hub is now 8.

In the first setup, two of the devices attached to the hub with 10 devices receive and send MIDI fine, except they do not receive MIDI clock. In the second setup, where these devices are plugged into a third USB hub, they receive all MIDI including clock.

So it looks like there is a limit of 8 USB devices per USB hub for MIDI clock (but not other types of MIDI messages as far as I have tested).

Is this a bug or a feature?

Bruno

MIDI setups diagram.pdf (27.1 KB)

SteveC · September 17, 2026, 2:50am

Hi, I’m not aware of anything on BomeBox that restricts just MIDI clock. Have you tried moving your devices to a different port on the hub (one that is receiving clock) to see if the problem moves with the port or stays with the device?

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

bagaeta · September 17, 2026, 3:07am

Yes I have swapped ports on the hub. It’s a 10 port powered hub. I noticed that the 2 devices that fail to receive clock are the last 2 when the devices are listed alphabetically based on the name they show on the Bome box.

I’ve worked around the issue by using DIN ports for their clock but it had me stumped for a while and I was wondering if others had observed the behavior.

SteveC · September 17, 2026, 3:15am

What version of BomeBox firmware are you running?
Also, try making your 10 port hub your first instead of your second and see if the problem follows the hub.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

bagaeta · September 17, 2026, 6:17am

Firmware is 1.6.1. I can’t swap the hubs (logistics and cable sizes) but I tried different hubs and number of devices plugged in them. With a third hub everything syncs as I mentioned in my initial post. But I also found that if I unplug everything from the 10 port hub then plug them back one by one with the Prophet and the Osmose first, everything syncs as well (all 10 devices). It still syncs after I restart the Bome box. But if I turn the devices (synths) off and on again then the Prophet and the Osmose again stop syncing. I have only one 10 ports hub so I can’t check if it’s an issue with the hub.

FlorianBome · September 17, 2026, 2:00pm

The BomeBox supports up to 30 USB devices with any number of hubs.

It’s important to know that internally, USB only allows for 4-port hubs. A 10-port hub is really 3x 4-port hubs plugged into each other.

Can you send us two logs:

the BomeBox web config log (copy/paste)
the BomeBox advanced web config (link at bottom of web config), menu Status → Kernel Log.

Thanks!

PS: In general, we have seen these kind of problems with USB:

power: when using more than 2 USB devices, all involved USB hubs should be powered.
Note: you can power the BomeBox via a port of a powered USB hub, saving a dedicated BomeBox power supply.
cables: we have seen and thrown away a lot of bad USB cables.
the BomeBox USB host is USB 2.0, but we’ve tested it to work well with USB 3.0 hubs. Nevertheless, you depend on the manufacturer of the hub to correctly implement the USB 2.0 layer.
there exist very few USB hub models that don’t work with the BomeBox. We have not been able to find out why. Out of hundreds that we tested, one did not work (a very cheap 4-port model).

bagaeta · September 18, 2026, 3:41am

Here’s the log as I turned on the system today. The prophet 6 was not plugged through USB at the time and I plugged it into the 10 port hub. The Osmose was plugged in the 10 port hub already.Both the Osmose and the P6 do not sync to MIDI clock in that configuration:

562: MT Player Headless on BomeBox started.
566: MT Player Headless (built Jul 31 2026 02:11:45) on BomeBox (Linux (Bome) 1.6.1)
599: load settings OK: last modified=2026-08-14 19:41:55 filesize=8009 filename:/etc/mt/playerheadless.bmts
622: Loaded settings file: /etc/mt/playerheadless.bmts
831: Parsing settings done.
986: MIDIRouter: added Route #0: IN “BomeBox DIN” → OUT “J-6” 0 blockers
987: MIDIRouter: added Route #1: IN “BomeBox DIN” → OUT “JD-XA” 0 blockers
988: MIDIRouter: added Route #2: IN “BomeBox DIN” → OUT “mio10 [9]” 0 blockers
989: MIDIRouter: added Route #3: IN “iConnectMIDI4+ [1]” → OUT “Bass Station II” 0 blockers
992: MIDIRouter: added Route #4: IN “iConnectMIDI4+ [1]” → OUT “HYDRASYNTH KB” 0 blockers
993: MIDIRouter: added Route #5: IN “iConnectMIDI4+ [1]” → OUT “KAOSSILATOR PRO” 0 blockers
994: MIDIRouter: added Route #6: IN “iConnectMIDI4+ [1]” → OUT “KP3” 0 blockers
995: MIDIRouter: added Route #7: IN “BomeBox DIN” → OUT “mio10 [1]” 0 blockers
997: MIDIRouter: added Route #8: IN “BomeBox DIN” → OUT “mio10 [2]” 0 blockers
998: MIDIRouter: added Route #9: IN “iConnectMIDI4+ [1]” → OUT “iConnectMIDI4+ [3]” 0 blockers
999: MIDIRouter: added Route #10: IN “BomeBox DIN” → OUT “mio10 [6]” 0 blockers
1013: MIDIRouter: added Route #11: IN “iConnectMIDI4+ [1]” → OUT “mio10 [8]” 0 blockers
1015: MIDIRouter: added Route #12: IN “BomeBox DIN” → OUT “iConnectMIDI2+ [1]” 0 blockers
1016: MIDIRouter: added Route #13: IN “BomeBox DIN” → OUT “iConnectMIDI4+ [2]” 0 blockers
1017: MIDIRouter: added Route #14: IN “iConnectMIDI4+ [1]” → OUT “Moog Sub 37” 0 blockers
1018: MIDIRouter: added Route #15: IN “mio10 [10]” → OUT “mio10 [9]” 0 blockers
1019: MIDIRouter: added Route #16: IN “mio10 [10]” → OUT “mio10 [5]” 0 blockers
1057: MIDIRouter: added Route #17: IN “mio10 [10]” → OUT “mio10 [3]” 0 blockers
1058: MIDIRouter: added Route #18: IN “mio10 [10]” → OUT “mio10 [7]” 0 blockers
1076: Warning Added (UnassignedAlias): MIDI devices are not plugged in or used aliases are not assigned to a device.
1080: MIDIRouter: added Route #19: IN “mio10 [10]” → OUT “mio10 [8]” 0 blockers
1082: MIDIRouter: added Route #20: IN “mio10 [10]” → OUT “mio10 [11]” 0 blockers
1083: MIDIRouter: added Route #21: IN “mio10 [10]” → OUT “mio10 [6]” 0 blockers
1084: MIDIRouter: added Route #22: IN “mio10 [10]” → OUT “mio10 [4]” 0 blockers
1086: MIDIRouter: added Route #23: IN “mio10 [2]” → OUT “iConnectMIDI4+ [3]” 0 blockers
1087: MIDIRouter: added Route #24: IN “mio10 [2]” → OUT “iConnectMIDI4+ [4]” 0 blockers
1088: MIDIRouter: added Route #25: IN “mio10 [2]” → OUT “iConnectMIDI2+ [1]” 0 blockers
1092: MIDIRouter: added Route #26: IN “mio10 [2]” → OUT “iConnectMIDI4+ [2]” 0 blockers
1093: MIDIRouter: added Route #27: IN “mio10 [2]” → OUT “Moog Sub 37” 0 blockers
1095: MIDIRouter: added Route #28: IN “mio10 [2]” → OUT “Bass Station II” 0 blockers
1096: MIDIRouter: added Route #29: IN “mio10 [2]” → OUT “J-6” 0 blockers
1097: MIDIRouter: added Route #30: IN “USB 45” → OUT “HYDRASYNTH KB” 0 blockers
1099: MIDIRouter: added Route #31: IN “iConnectMIDI4+ [1]” → OUT “KRONOS” 0 blockers
1112: MIDIRouter: added Route #32: IN “iConnectMIDI4+ [1]” → OUT “Prophet 6” 0 blockers
1114: MIDIRouter: added Route #33: IN “iConnectMIDI4+ [1]” → OUT “Osmose [1]” 0 blockers
1186: TCP_MIDI_Server: now listening on TCP port 37000
1187: BNetMIDI: server started. Local identity: BomeBox
1187: NetDirectory added local identity ‘BomeBox’ at UDP port 37000
1188: NetDirectory → device:BomeBox (BomeBox) app:‘MT Player Headless’ id:0531017C3C5E432633BD os:Linux (Bome) 1.6.1
1209: Discovered MIDI INPUT : BomeBox DIN
1231: Discovered MIDI OUTPUT: BomeBox DIN
1864: Opened MIDI INPUT “BomeBox DIN”
1865: MIDIManager started.
1901: mDNS (avahi): failed to start: client
1901: mDNS (avahi): could not initialize yet (client), will retry
1901: NetMIDI2: mDNS discovery started
1902: NetMIDI2: Host “BomeBox”: started, listening on UDP port 47038.
1903: NetMIDI2: Host “BomeBox”: exposed on mDNS (ProductInstanceId=0531017C3C5E432633BD, ServiceName=bomebox-bomebox-9u9y8c-0, Port=47038)
2483: created settings file backup: /etc/mt/playerheadless_Backup.bmts
2484: save settings OK: last modified=2026-08-14 19:41:56 filesize=8009 filename:/etc/mt/playerheadless.bmts
2932: mDNS (avahi): - restarting service
2943: mDNS (avahi): service “bomebox-bomebox-9u9y8c-0”: markAsRemoved
2943: mDNS (avahi): stopped.
2944: mDNS (avahi): failed to start: client
3787: created settings file backup: /etc/mt/playerheadless_Backup.bmts
3787: save settings OK: last modified=2026-08-14 19:41:58 filesize=8009 filename:/etc/mt/playerheadless.bmts
3869: UBUS: object “bome” registered
7564: Discovered MIDI INPUT : iConnectMIDI2+ [1],iConnectMIDI2+ [2],iConnectMIDI2+ [3],iConnectMIDI2+ [4],J-6
7564: Discovered MIDI OUTPUT: iConnectMIDI2+ [1],iConnectMIDI2+ [2],iConnectMIDI2+ [3],iConnectMIDI2+ [4],J-6
7763: Opened MIDI OUTPUT “iConnectMIDI2+ [1]”
7765: Opened MIDI OUTPUT “J-6”
7936: mDNS (avahi): - restarting service
7946: mDNS (avahi): stopped.
7947: mDNS (avahi): failed to start: client
12901: mDNS (avahi): - restarting service
12912: mDNS (avahi): stopped.
12974: mDNS (avahi): server state: CONNECTING.
12974: mDNS (avahi): init
12974: mDNS (avahi): service “bomebox-bomebox-9u9y8c-0”: restore
12975: mDNS (avahi): started advertising local services
12975: mDNS (avahi): local service #0 “bomebox-bomebox-9u9y8c-0”: checking changes: isDeleted=0, temporaryRemoval=0, temporaryRemovalDone=0, isUpdated=0, isCreated=1
12975: mDNS (avahi): local service #0 “bomebox-bomebox-9u9y8c-0”: error creating entry group (Bad state)
12975: mDNS (avahi): error advertising service “bomebox-bomebox-9u9y8c-0” (Bad state), will retry
13515: mDNS (avahi): server state: RUNNING.
13516: mDNS (avahi): server state: REGISTERING.
13516: mDNS (avahi): server state: RUNNING.
13517: mDNS (avahi): - republish local services…
13517: mDNS (avahi): local service #0 “bomebox-bomebox-9u9y8c-0”: checking changes: isDeleted=0, temporaryRemoval=0, temporaryRemovalDone=0, isUpdated=0, isCreated=1
13632: mDNS (avahi): local service #0 “bomebox-bomebox-9u9y8c-0”: advertise (new)
13640: mDNS (avahi): local service #0 “bomebox-bomebox-9u9y8c-0”: state update: updated
15803: BNetWatcher: 1 added and 0 removed addresses
15803: added 1: 192.168.1.1
15803: NetDirectory: network interfaces have changed. Reset discovery.
15803: TCP_MIDI_Server: network interfaces have changed. Closing socket, triggering re-opening.
16011: NetDirectory: adding new broadcast: 192.168.1.255 (netmask:255.255.255.0)
16290: TCP_MIDI_Server: invalid socket. Create a new listening socket.
16290: TCP_MIDI_Server: now listening on TCP port 37000
20607: BNetWatcher: trigger IP address change
20607: NetDirectory: network interfaces have changed. Reset discovery.
20607: TCP_MIDI_Server: network interfaces have changed. Closing socket, triggering re-opening.
21309: TCP_MIDI_Server: invalid socket. Create a new listening socket.
21390: TCP_MIDI_Server: now listening on TCP port 37000
21522: created settings file backup: /etc/mt/playerheadless_Backup.bmts
21522: save settings OK: last modified=2026-08-14 19:42:15 filesize=8009 filename:/etc/mt/playerheadless.bmts
30609: BNetWatcher: trigger IP address change
30609: NetDirectory: network interfaces have changed. Reset discovery.
30609: TCP_MIDI_Server: network interfaces have changed. Closing socket, triggering re-opening.
31384: created settings file backup: /etc/mt/playerheadless_Backup.bmts
31385: save settings OK: last modified=2026-08-14 19:42:25 filesize=8009 filename:/etc/mt/playerheadless.bmts
31390: TCP_MIDI_Server: invalid socket. Create a new listening socket.
31390: TCP_MIDI_Server: now listening on TCP port 37000
901865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 37910 bytes sent
901865: MIDI OUTPUT “J-6”: 37910 bytes sent
901865: MIDI INPUT “BomeBox DIN”: 38160 bytes received
1801865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38160 bytes sent
1801865: MIDI OUTPUT “J-6”: 38160 bytes sent
1801866: MIDI INPUT “BomeBox DIN”: 38159 bytes received
2701865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38159 bytes sent
2701866: MIDI OUTPUT “J-6”: 38159 bytes sent
2701866: MIDI INPUT “BomeBox DIN”: 38159 bytes received
3601865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38159 bytes sent
3601866: MIDI OUTPUT “J-6”: 38159 bytes sent
3601866: MIDI INPUT “BomeBox DIN”: 38159 bytes received
4501865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38159 bytes sent
4501865: MIDI OUTPUT “J-6”: 38159 bytes sent
4501865: MIDI INPUT “BomeBox DIN”: 38159 bytes received
5401865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38159 bytes sent
5401866: MIDI OUTPUT “J-6”: 38159 bytes sent
5401866: MIDI INPUT “BomeBox DIN”: 38159 bytes received
6301865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38160 bytes sent
6301866: MIDI OUTPUT “J-6”: 38160 bytes sent
6301866: MIDI INPUT “BomeBox DIN”: 38160 bytes received
7201865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38159 bytes sent
7201865: MIDI OUTPUT “J-6”: 38159 bytes sent
7201865: MIDI INPUT “BomeBox DIN”: 38159 bytes received
8101865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38159 bytes sent
8101866: MIDI OUTPUT “J-6”: 38159 bytes sent
8101866: MIDI INPUT “BomeBox DIN”: 38159 bytes received
9001865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38159 bytes sent
9001865: MIDI OUTPUT “J-6”: 38159 bytes sent
9001866: MIDI INPUT “BomeBox DIN”: 38159 bytes received
9901865: MIDI OUTPUT “iConnectMIDI2+ [1]”: 38159 bytes sent
9901865: MIDI OUTPUT “J-6”: 38159 bytes sent
9901866: MIDI INPUT “BomeBox DIN”: 38159 bytes received
10309683: Discovered MIDI INPUT : Moog Sub 37,Osmose [1],Osmose [2]
10309683: Discovered MIDI OUTPUT: Moog Sub 37,Osmose [1],Osmose [2]
10309698: Opened MIDI OUTPUT “Moog Sub 37”
10309699: Opened MIDI OUTPUT “Osmose [1]”
10312266: Discovered MIDI INPUT : iConnectMIDI4+ [10],iConnectMIDI4+ [11],iConnectMIDI4+ [12],iConnectMIDI4+ [13],iConnectMIDI4+ [14],iConnectMIDI4+ [15],iConnectMIDI4+ [16],iConnectMIDI4+ [1],iConnectMIDI4+ [2],iConnectMIDI4+ [3],iConnectMIDI4+ [4],iConnectMIDI4+ [5],iConnectMIDI4+ [6],iConnectMIDI4+ [7],iConnectMIDI4+ [8],iConnectMIDI4+ [9],KRONOS
10312266: Discovered MIDI OUTPUT: iConnectMIDI4+ [10],iConnectMIDI4+ [11],iConnectMIDI4+ [12],iConnectMIDI4+ [13],iConnectMIDI4+ [14],iConnectMIDI4+ [15],iConnectMIDI4+ [16],iConnectMIDI4+ [1],iConnectMIDI4+ [2],iConnectMIDI4+ [3],iConnectMIDI4+ [4],iConnectMIDI4+ [5],iConnectMIDI4+ [6],iConnectMIDI4+ [7],iConnectMIDI4+ [8],iConnectMIDI4+ [9],KRONOS
10312337: Opened MIDI INPUT “iConnectMIDI4+ [1]”
10312339: Opened MIDI OUTPUT “iConnectMIDI4+ [2]”
10312341: Opened MIDI OUTPUT “iConnectMIDI4+ [3]”
10312343: Opened MIDI OUTPUT “iConnectMIDI4+ [4]”
10312344: Opened MIDI OUTPUT “KRONOS”
10313592: created settings file backup: /etc/mt/playerheadless_Backup.bmts
10313593: save settings OK: last modified=2026-08-14 22:33:47 filesize=8009 filename:/etc/mt/playerheadless.bmts
10314740: Discovered MIDI INPUT : Bass Station II,JD-XA,KAOSSILATOR PRO,KP3,mio10 [10],mio10 [11],mio10 [12],mio10 [13],mio10 [14],mio10 [15],mio10 [16],mio10 [1],mio10 [2],mio10 [3],mio10 [4],mio10 [5],mio10 [6],mio10 [7],mio10 [8],mio10 [9]
10314741: Discovered MIDI OUTPUT: Bass Station II,KAOSSILATOR PRO,KP3,mio10 [10],mio10 [11],mio10 [12],mio10 [13],mio10 [14],mio10 [15],mio10 [16],mio10 [1],mio10 [2],mio10 [3],mio10 [4],mio10 [5],mio10 [6],mio10 [7],mio10 [8],mio10 [9]
10314902: Opened MIDI INPUT “Osmose [2]”
10314904: Opened MIDI INPUT “mio10 [2]”
10314907: Opened MIDI INPUT “mio10 [10]”
10314909: Opened MIDI OUTPUT “KP3”
10314911: Opened MIDI OUTPUT “mio10 [1]”
10314913: Opened MIDI OUTPUT “mio10 [2]”
10314914: Opened MIDI OUTPUT “mio10 [3]”
10314916: Opened MIDI OUTPUT “mio10 [4]”
10314918: Opened MIDI OUTPUT “mio10 [5]”
10314919: Opened MIDI OUTPUT “mio10 [6]”
10314921: Opened MIDI OUTPUT “mio10 [7]”
10314924: Opened MIDI OUTPUT “mio10 [8]”
10314925: Opened MIDI OUTPUT “mio10 [9]”
10314927: Opened MIDI OUTPUT “mio10 [11]”
10314929: Opened MIDI OUTPUT “KAOSSILATOR PRO”
10314931: Opened MIDI OUTPUT “Bass Station II”
10316101: created settings file backup: /etc/mt/playerheadless_Backup.bmts
10316102: save settings OK: last modified=2026-08-14 22:33:50 filesize=8009 filename:/etc/mt/playerheadless.bmts
10319913: Discovered MIDI INPUT : HYDRASYNTH KB
10319914: Discovered MIDI OUTPUT: HYDRASYNTH KB,JD-XA
10320049: Opened MIDI INPUT “Osmose [1]”
10320052: Closed MIDI INPUT “Osmose [2]”
10320055: Opened MIDI OUTPUT “JD-XA”
10320056: Opened MIDI OUTPUT “HYDRASYNTH KB”
10321242: created settings file backup: /etc/mt/playerheadless_Backup.bmts
10321243: save settings OK: last modified=2026-08-14 22:33:55 filesize=8009 filename:/etc/mt/playerheadless.bmts
10329278: BNetWatcher: trigger IP address change
10329278: NetDirectory: network interfaces have changed. Reset discovery.
10329278: TCP_MIDI_Server: network interfaces have changed. Closing socket, triggering re-opening.
10329390: TCP_MIDI_Server: invalid socket. Create a new listening socket.
10329390: TCP_MIDI_Server: now listening on TCP port 37000
10330033: created settings file backup: /etc/mt/playerheadless_Backup.bmts
10330033: save settings OK: last modified=2026-08-14 22:34:04 filesize=8009 filename:/etc/mt/playerheadless.bmts
10362216: NetDirectory: adding new unicast: 192.168.1.86:37000
10362217: NetDirectory added remote identity ‘macbookpro’ at address 192.168.1.86:37000
10362218: NetDirectory → app:‘Bome Network 1.7.0’ id:4E57D14567A840C8E85E os:macOS Sequoia 15.7.9
10363367: NetMIDI2: BomeBox RX: 0x01 “macbookpro” id=4E57D14567A840C8E85E from 192.168.1.86:52169
10363368: Network MIDI 2.0 Host: device “macbookpro” discovered (instanceId=“4E57D14567A840C8E85E” at 192.168.1.86:52169)
10363368: NetMIDI2: Host “BomeBox”: add host IP for client “macbookpro”: 192.168.1.86:52169
10363379: NetMIDI2: macbookpro TX: 0x10 “BomeBox” id=0531017C3C5E432633BD to 192.168.1.86:52169
10363548: Discovered MIDI INPUT : macbookpro
10363549: Discovered MIDI OUTPUT: macbookpro
10364452: created settings file backup: /etc/mt/playerheadless_Backup.bmts
10364453: save settings OK: last modified=2026-08-14 22:34:38 filesize=8009 filename:/etc/mt/playerheadless.bmts
10372210: NetDirectory: removing stale remote identity ‘macbookpro’
10373822: TCP_MIDI_Server: client connecting…
10373823: Incoming ClientConnection (192.168.1.86:49202) has been instantiated.
10373830: ClientConnection started.
10373831: Client ‘macbookpro’ is connecting…
10373832: BNetMIDIServer: incoming connection request from client “macbookpro”
10373832: BNetMIDIServer: auto-accepting incoming connection from “macbookpro” because it was connected before (currentlyAutoAcceptClients)
10373833: BNetMIDIServer: accepting client: macbookpro (192.168.1.86:49202)
10373833: NetMIDI Server: accepting session with “macbookpro”.
10373833: [ClientConnection 1]: established session with client “macbookpro”. Remote caps=25
10373834: Client ‘macbookpro’ has MIDI connected.
10373834: BNetMIDIServer: connection authenticated with remote client “macbookpro” (192.168.1.86:49202)
10374046: Discovered MIDI INPUT : macbookpro
10374047: Discovered MIDI OUTPUT: macbookpro
10374186: Connected to “macbookpro” (“macbookpro” at 192.168.1.86:49202).
10374950: created settings file backup: /etc/mt/playerheadless_Backup.bmts
10374950: save settings OK: last modified=2026-08-14 22:34:49 filesize=8009 filename:/etc/mt/playerheadless.bmts
10388462: NetDirectory added remote identity ‘macbookpro’ at address 192.168.1.86:37000
10388462: NetDirectory → app:‘Bome Network 1.7.0’ id:4E57D14567A840C8E85E os:macOS Sequoia 15.7.9
10679212: Discovered MIDI INPUT : Prophet 6
10679212: Discovered MIDI OUTPUT: Prophet 6
10679356: Opened MIDI OUTPUT “Prophet 6”
10679700: Warning Removed (UnassignedAlias): MIDI devices are not plugged in or used aliases are not assigned to a device.

Kernel Log: note that I deleted lots of the ‘br-lan: received packet on eth1 with own address as source address’ lines due to the forum post length limitations:

[10302.010000] br-lan: received packet on eth1 with own address as source address
[10302.010000] br-lan: received packet on eth1 with own address as source address
[10315.010000] br-lan: received packet on eth1 with own address as source address
[10315.010000] br-lan: received packet on eth1 with own address as source address
[10315.010000] br-lan: received packet on eth1 with own address as source address
[10323.490000] usb 1-1.6.1.1.1: new full-speed USB device number 9 using ehci-platform
[10324.000000] usb 1-1.6.3: new full-speed USB device number 10 using ehci-platform
[10325.010000] usb 1-1.4: new full-speed USB device number 11 using ehci-platform
[10326.550000] usb 1-1.6.1.2: new high-speed USB device number 12 using ehci-platform
[10326.660000] usb 1-1.6.1.2: config 1 interface 4 altsetting 0 bulk endpoint 0x82 has invalid maxpacket 64
[10326.670000] 12:1:1: cannot get freq at ep 0x1
[10327.010000] br-lan: received packet on eth1 with own address as source address
[10327.010000] br-lan: received packet on eth1 with own address as source address
[10327.010000] br-lan: received packet on eth1 with own address as source address
[10327.590000] usb 1-1.6.1.3: new full-speed USB device number 13 using ehci-platform
[10327.750000] usb-storage 1-1.6.1.3:1.1: USB Mass Storage device detected
[10327.750000] scsi0 : usb-storage 1-1.6.1.3:1.1
[10328.000000] usb 1-1.3: new full-speed USB device number 14 using ehci-platform
[10328.390000] usb 1-1.6.1.4: new full-speed USB device number 15 using ehci-platform
[10328.580000] usb-storage 1-1.6.1.4:1.1: USB Mass Storage device detected
[10328.580000] scsi1 : usb-storage 1-1.6.1.4:1.1
[10328.750000] scsi 0:0:0:0: Direct-Access GENERIC KORG KP3 R/W 0010 PQ: 0 ANSI: 2
[10328.770000] sd 0:0:0:0: [sda] Attached SCSI removable disk
[10328.820000] usb 1-1.6.4: new full-speed USB device number 16 using ehci-platform
[10329.380000] usb 1-1.6.1.1.4: new full-speed USB device number 17 using ehci-platform
[10329.580000] scsi 1:0:0:0: Direct-Access GENERIC KORG KO-1PRO R/W 0010 PQ: 0 ANSI: 2
[10329.600000] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[10330.640000] usb 1-1.6.1.1.3: new high-speed USB device number 18 using ehci-platform
[10330.750000] usb 1-1.6.1.1.3: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
[10330.750000] usb 1-1.6.1.1.3: config 1 interface 1 altsetting 0 bulk endpoint 0x2 has invalid maxpacket 64
[10340.010000] br-lan: received packet on eth1 with own address as source address
[10340.010000] br-lan: received packet on eth1 with own address as source address
[10340.010000] br-lan: received packet on eth1 with own address as source address
[10342.600000] eth0: link up (1000Mbps/Full duplex)
[10342.600000] br-lan: port 1(eth0) entered forwarding state
[10342.600000] br-lan: port 1(eth0) entered forwarding state
[10344.510000] br-lan: received packet on eth1 with own address as source address
[10344.510000] br-lan: received packet on eth1 with own address as source address
[10344.510000] br-lan: received packet on eth1 with own address as source address
[10344.600000] br-lan: port 1(eth0) entered forwarding state
[10348.640000] br-lan: received packet on eth1 with own address as source address
[10352.600000] eth0: link down
[10352.600000] br-lan: port 1(eth0) entered disabled state
[10354.100000] eth0: link up (1000Mbps/Full duplex)
[10354.100000] br-lan: port 1(eth0) entered forwarding state
[10354.100000] br-lan: port 1(eth0) entered forwarding state
[10356.100000] br-lan: port 1(eth0) entered forwarding state
[10358.640000] br-lan: received packet on eth1 with own address as source address
[10361.020000] br-lan: received packet on eth1 with own address as source address
[10361.020000] br-lan: received packet on eth1 with own address as source address
[10361.020000] br-lan: received packet on eth1 with own address as source address
[10361.440000] br-lan: received packet on eth1 with own address as source address

bagaeta · September 19, 2026, 6:52am

After trying many more things including swapping hubs, trying different hubs etc, I noticed that the Prophet 6 lost sync sometimes when I plugged the Kronos into the hub. Which reminded me that there has been some reports of issues with the Kronos USB port as it is used for audio in addition to MIDI and possibly other issues. So I took the Kronos out of the hub and instead plugged it into the host port of the iConnectMIDI 4+, making sure that it only received and did not send USB MIDI. That seems to have fixed the problem (fingers crossed). So it may be that the Kronos sends a lot of USB garbage on its device port which overwhelms many hubs to the point where they can’t cope with an ongoing signal like MIDI clock…

Let’s see…

FlorianBome · September 19, 2026, 10:03am

That’s very interesting, and good to hear! Crossing my fingers that this was the cause.

SteveC · September 19, 2026, 12:09pm

Thanks for the update!

helen.marsh · September 25, 2026, 8:14am

Your follow-up points to a topology or USB-load edge case rather than a simple eight-device rule. The cleanest confirmation is to leave the Kronos on the iConnect host, then add devices back one at a time while watching whether clock drops only when the Kronos USB is enumerated; compare the same hub and ports with a different device. If the clock stays solid with the Kronos isolated, keeping its USB connection on the host (or using DIN for clock) is a sensible workaround while the other MIDI paths remain on the BomeBox.

For anyone debugging similar timing issues, a short frequency reference can also help when checking periodic drift: KYMA frequency reference

bagaeta · September 27, 2026, 7:25am

Well after extensive testing of multiple configurations I can reasonably confidently say that the main problem was the Kronos USB port being a d**k and overwhelming whatever was connected to it. The Bomebox was not the only victim - the iConnectMIDI4+ also behaved erratically until I gave up and connected the Kronos through its DIN ports instead of USB. The other difficult machine in my setup is the Osmose (see my other recent post) after its latest firmware update, which I’ve also fixed by connecting it through the DIN ports, which allows me to plug the USB port directly into the MacBook to make use of the wonderful new DAW control features which I don’t think the Bomebox would be able to handle as they are not MIDI as such.

SteveC · September 27, 2026, 10:02pm

Yes, as I said on your other post, I’m glad you got it working!

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz