Skip to Content

irregular timing, permission issues ?

1 reply [Last post]
Joined: 05/04/2014

Dear hydrogen team and forum users,

I tried 0.9.6-svn from the ubuntu package and now 0.9.6.-beta3 from your ppa on a 32-bit laptop running ubuntu (12.4 LTS).

The playback is irregular in timing and some notes get distorted (also due to timing I would say). I use jack as sound server, also tried ALSA.

When the program is run as root, the timing is ok and everything sounds fine. I then hear the drums through my laptop speakers instead of my USB mixer. When running as root I get no connection with jack, although the audio info window says "Jackoutput". Getting no connection means Hydrogen doesn't show up as readable client in qjackctl.

here is stderr from the console when starting up:


JACK server starting in realtime mode with priority 10
control device hw:0
control device hw:0
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
Unknown destination port in attempted (dis)connection src_name [Hydrogen:out_L] dst_name [alsa_pcm:playback_1]

The jack server was already running when I launched up H.

I also tried suid and sgid bits. This didn't work either (as expected), but I got an error "cannot open audio device" when trying suid.

Thanks for the programm! I like the user interface, it's very useable. I'm looking forward to use Hydrogen, but for now it's far worse at drumming than myself (I'm a bass player)


thijs's picture
Joined: 04/20/2010

Hi Jaychris

in Tools > Preferences > Audio setup  you have JACK selected, right ?

could you post the output of 'cat .hydrogen/hydrogen.conf | grep audio_driver' ?

the output should include <audio_driver>Jack</audio_driver>


if not, you have run into a known issue (that has been fixed already)