USB hubs - a bad idea?
Moderators: MattKingUSA, khz
- sysrqer
- Established Member
- Posts: 2527
- Joined: Thu Nov 14, 2013 11:47 pm
- Has thanked: 320 times
- Been thanked: 153 times
- Contact:
USB hubs - a bad idea?
I've got a few usb midi controllers and a usb soundcard that I use with a laptop. It's a bit of a pain to plug/unplug it all if I want to take the laptop somewhere else so I've been thinking about getting a hub so I just have one thing to plug in. I have no idea what effect this would have in terms of audio though, does anyone here have experience using these? I would be using it with Windows as well so any experience on that side would also be helpful.
- lilith
- Established Member
- Posts: 1706
- Joined: Fri May 27, 2016 11:41 pm
- Location: bLACK fOREST
- Has thanked: 123 times
- Been thanked: 57 times
- Contact:
Re: USB hubs - a bad idea?
Midi input devices shouldn't be a problem. It might be a problem with the interface, but this you have to check out. Also the maximum current it can deliver is important. So, an active USB hub might make sense if you need more than 500 mA. And here I would buy quality, cause the cheap ones can back power the motherboard which might destroy the USB controller in the worst case.
I heard good things about this one: https://www.thomann.de/de/elektron_overhub.htm
Personally I'm using a D-Link Hub: https://www.amazon.de/D-Link-DUB-H7-7-p ... d-link+hub
I heard good things about this one: https://www.thomann.de/de/elektron_overhub.htm
Personally I'm using a D-Link Hub: https://www.amazon.de/D-Link-DUB-H7-7-p ... d-link+hub
- bluebell
- Established Member
- Posts: 1927
- Joined: Sat Sep 15, 2012 11:44 am
- Location: Saarland, Germany
- Has thanked: 113 times
- Been thanked: 122 times
Re: USB hubs - a bad idea?
My experiences with Linux, active "CSL – USB 3.0 Hub" (7 port) and Focusrite USB-Interfaces are good.sysrqer wrote:I've got a few usb midi controllers and a usb soundcard that I use with a laptop. It's a bit of a pain to plug/unplug it all if I want to take the laptop somewhere else so I've been thinking about getting a hub so I just have one thing to plug in. I have no idea what effect this would have in terms of audio though, does anyone here have experience using these? I would be using it with Windows as well so any experience on that side would also be helpful.
On one of my notebook computers it's much more important which USB port on the computer I choose. One doesn't work with buffer sizes <= 128.
Linux – MOTU UltraLite AVB – Qtractor – http://suedwestlicht.saar.de/
Re: USB hubs - a bad idea?
I just tested my interface with a hub and it didn't work:
My interface is picky with the USB ports. It doesn't work on any port on the back of the chassis, just the frontal ones. I connected the hub to a frontal port and it still didn't work.
Code: Select all
Fri May 18 10:35:44 2018: Starting jack server...
Fri May 18 10:35:44 2018: JACK server starting in realtime mode with priority 10
Fri May 18 10:35:44 2018: self-connect-mode is "Don't restrict self connect requests"
Fri May 18 10:35:44 2018: Acquired audio card Audio3
Fri May 18 10:35:44 2018: creating alsa driver ... hw:Omega,0|hw:Omega,0|2048|4|48000|0|0|hwmon|hwmeter|soft-mode|32bit
Fri May 18 10:35:44 2018: Using ALSA driver USB-Audio running on card 3 - Lexicon Lexicon Omega at usb-0000:00:1a.0-1.4.4, full speed
Fri May 18 10:35:44 2018: configuring for 48000Hz, period = 2048 frames (42.7 ms), buffer = 4 periods
Fri May 18 10:35:44 2018: ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
Fri May 18 10:35:44 2018: ALSA: use 4 periods for capture
Fri May 18 10:35:44 2018: ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
Fri May 18 10:35:44 2018: ALSA: use 4 periods for playback
Fri May 18 10:35:44 2018: ERROR: ALSA: could not start playback (Broken pipe)
Fri May 18 10:35:44 2018: ERROR: Cannot start driver
Fri May 18 10:35:44 2018: ERROR: JackServer::Start() failed with -1
Fri May 18 10:35:44 2018: ERROR: Failed to start server
Fri May 18 10:35:44 2018: Released audio card Audio3
Fri May 18 10:35:55 2018: Controller deactivated.
Fri May 18 10:35:55 2018: ------------------
Fri May 18 10:35:55 2018: Controller activated. Version 1.9.11-RC1 (unknown) built on Sat Jul 22 07:03:22 2017
Fri May 18 10:35:55 2018: Loading settings from "/home/luc/.config/jack/conf.xml" using expat_2.2.0 ...
Fri May 18 10:35:55 2018: setting parameter 'engine':'driver':'(null)' to value "alsa"
Fri May 18 10:35:55 2018: setting parameter 'engine':'self-connect-mode':'(null)' to value " "
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'device' to value "hw:Omega,0"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'capture' to value "none"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'playback' to value "none"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'rate' to value "48000"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'period' to value "2048"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'nperiods' to value "4"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'hwmon' to value "true"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'hwmeter' to value "true"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'duplex' to value "true"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'softmode' to value "true"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'monitor' to value "true"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'dither' to value "s"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'inchannels' to value "0"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'outchannels' to value "0"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'midi-driver' to value "none"
Fri May 18 10:35:55 2018: setting parameter 'drivers':'alsa':'hw-alias' to value "true"
Fri May 18 10:35:55 2018: Listening for D-Bus messages
Fri May 18 10:35:57 2018: ------------------
Fri May 18 10:35:57 2018: Controller activated. Version 1.9.11-RC1 (unknown) built on Sat Jul 22 07:03:22 2017
Fri May 18 10:35:57 2018: Loading settings from "/home/luc/.config/jack/conf.xml" using expat_2.2.0 ...
Fri May 18 10:35:57 2018: setting parameter 'engine':'driver':'(null)' to value "alsa"
Fri May 18 10:35:57 2018: setting parameter 'engine':'self-connect-mode':'(null)' to value " "
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'device' to value "hw:Omega,0"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'capture' to value "none"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'playback' to value "none"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'rate' to value "48000"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'period' to value "2048"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'nperiods' to value "4"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'hwmon' to value "true"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'hwmeter' to value "true"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'duplex' to value "true"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'softmode' to value "true"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'monitor' to value "true"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'dither' to value "s"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'inchannels' to value "0"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'outchannels' to value "0"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'midi-driver' to value "none"
Fri May 18 10:35:57 2018: setting parameter 'drivers':'alsa':'hw-alias' to value "true"
Fri May 18 10:35:57 2018: Listening for D-Bus messages
Fri May 18 10:35:58 2018: Starting jack server...
Fri May 18 10:35:58 2018: JACK server starting in realtime mode with priority 10
Fri May 18 10:35:58 2018: self-connect-mode is "Don't restrict self connect requests"
Fri May 18 10:35:58 2018: Acquired audio card Audio3
Fri May 18 10:35:58 2018: creating alsa driver ... hw:Omega,0|hw:Omega,0|2048|4|48000|0|0|hwmon|hwmeter|soft-mode|32bit
Fri May 18 10:35:58 2018: Using ALSA driver USB-Audio running on card 3 - Lexicon Lexicon Omega at usb-0000:00:1a.0-1.4.4, full speed
Fri May 18 10:35:58 2018: configuring for 48000Hz, period = 2048 frames (42.7 ms), buffer = 4 periods
Fri May 18 10:35:58 2018: ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
Fri May 18 10:35:58 2018: ALSA: use 4 periods for capture
Fri May 18 10:35:58 2018: ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
Fri May 18 10:35:58 2018: ALSA: use 4 periods for playback
Fri May 18 10:35:58 2018: ERROR: ALSA: could not start playback (Broken pipe)
Fri May 18 10:35:58 2018: ERROR: Cannot start driver
Fri May 18 10:35:58 2018: ERROR: JackServer::Start() failed with -1
Fri May 18 10:35:58 2018: ERROR: Failed to start server
Fri May 18 10:35:58 2018: Released audio card Audio3
Re: USB hubs - a bad idea?
Got a similar issue with my old computer. It turned out that the ports on the front of the chassis (the ones that did not work in my case) were connected to the motherboards with long wires that would drop too much voltage on the 3.3V, making impossible for the interface to powerup properly.Luc wrote:My interface is picky with the USB ports. It doesn't work on any port on the back of the chassis, just the frontal ones. I connected the hub to a frontal port and it still didn't work.
To me they always been an hit or miss. I tried the last one on a Mac Book Pro running Mac OS El Capitan, just a cheap passive USB one. It was pretty weird: when using the hub you would record background noise triggered by other USB devices, even if not on the hub. For example, I could make noise appear by moving the trackpad. Not a lot of noise, but very evident with Baudline.sysrqer wrote:I have no idea what effect this would have in terms of audio though, does anyone here have experience using these?
That's it: you can expect any range of hardware quirks and problems, and how well they work will not depend just on the hub, but also on those internal to your computer. The only way is to try really.
Re: USB hubs - a bad idea?
I have two sets of dirty cheap speakers, and they have to be connected to the computer directly. If I have them share the hub with the mouse, I can hear it through the speakers when the mouse is moved.CrocoDuck wrote:(...) It was pretty weird: when using the hub you would record background noise triggered by other USB devices, even if not on the hub. For example, I could make noise appear by moving the trackpad. Not a lot of noise, but very evident with Baudline.
Re: USB hubs - a bad idea?
I decided to check that up and quickly realized that the ports on the front are the ones that have wires, and they work. The ones on the back are soldered directly to the motherboard, and they don't work. ¯\_(ツ)_/¯CrocoDuck wrote:Got a similar issue with my old computer. It turned out that the ports on the front of the chassis (the ones that did not work in my case) were connected to the motherboards with long wires that would drop too much voltage on the 3.3V, making impossible for the interface to powerup properly.
Re: USB hubs - a bad idea?
Go figure... Voltage regulators maybe? Who knows...Luc wrote:I decided to check that up and quickly realized that the ports on the front are the ones that have wires, and they work. The ones on the back are soldered directly to the motherboard, and they don't work. ¯\_(ツ)_/¯