MIDIHub stops responding?

Midihub Support
1

This has happened a few times to me, not too often, though. Suddenly, the devices supposed to receive MIDI messages through the Midihub’s DIN ports stop playing, and restarting the Midihub fixes it.

The last time this happened I didn’t think of trying connecting using USB, to see if the device had completely crashed or somehow responding. that would have been interesting. Sorry.

I see that no new firmware has been release since summer '22, so I must presume that the current version is considered reliable enough. Am I alone experiencing this? Thanks!

G.

1 Like
2

Hey. there’s been no recent reports of any similar issue. It would be great if you could provide as much information as possible on the issue - how easy it is to reproduce, how do you do it, is Midihub connected to a PC or just a power supply, also it’d be great to inspect various parts within Midihub via the Editor’s MIDI Monitor pane to help see what’s going on.

3

Since my original post it hasn’t happened again, it’s very rare. The Midihub is connected and powered via USB, connected to a passive USB hub, connected to a MacBook Pro. As I wrote the first time, when I realized it was frozen I wasn’t smart enough to try connecting with the Midihub Editor, I’m sorry. This is all I know.

4

Is it possible the passive hub got underpowered if too much things were connected? (or it might be enough to activate a certain set of functions on connected devices so there’s insufficient power for all of them to operate properly)

Anyway, please let us know if you ever reproduce the problem and provide as much details as possible.

5

Giedrius so do you recommend that the Midihub is on a ‘Powered Hub’ I’m guessing it doesn’t matter if its USB 3 or 2 ?

6

You should be mindful of the total power consumption on a particular USB port. If you connect a lot of devices without injecting additional power via a powered hub, issues may occur.

7

Thank You I have a ‘Monster Hub’ RSH USB3 13 port 72w “overkill” maybe but most of my external drives and other gubbins on MacOS and everything I have plugged into it has worked so.

8

Yeah this has happened to me too on occasion. As far as I can recall only when plugged into my Mac via USB. When I take it to perform with my DAWless setup I dont recall it crashing.

9

power consumption on MIDIHUB seems to be quite high:

patch@rpifour:~ $ lsusb -v 2>&- | grep -E ‘Bus 00|MaxPower’
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

  • MaxPower 0mA*
    Bus 001 Device 024: ID 16d0:0d4a MCS MicroMonsta 2
  • MaxPower 300mA*
    Bus 001 Device 021: ID 0a67:5119 Medeli Electronics Co., Ltd HYDRASYNTH DR
  • MaxPower 10mA*
    Bus 001 Device 023: ID 16d0:0ce2 MCS Deluge
  • MaxPower 500mA*
    Bus 001 Device 018: ID a600:e340 ASIX s.r.o. Vector Synthesizer
  • MaxPower 0mA*
    Bus 001 Device 016: ID 1a40:0101 Terminus Technology Inc. Hub
  • MaxPower 100mA*
    Bus 001 Device 015: ID 16d0:0c9c MCS MIDIHUB
  • MaxPower 500mA*
    Bus 001 Device 014: ID 16c0:0489 Van Ooijen Technische Informatica NDLR
  • MaxPower 100mA*
    Bus 001 Device 013: ID 1a40:0101 Terminus Technology Inc. Hub
  • MaxPower 100mA*
    Bus 001 Device 022: ID 13b2:005f Alesis Vortex Wireless 2
  • MaxPower 100mA*
    Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  • MaxPower 100mA*
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  • MaxPower 0mA*

so this is over the limit from RPi4 which has 1200mA

10

It’s just a “max power” attribute, not the actual power usage. Does it cause any observable issues?

1 Like
11

yes, it is how the device is specified and not the actual consumption. Hardware or OS does not support any monitoring so I´ve got to go another way - but for now all works fine though all the devices together are specified up to 2000 mA.