Hi,
I just received my copy of 1337 today and upon starting Hydrogen, it quickly started WINE and then opened Hydrogen and then crashed five seconds later (the window just dropped off the screen). I repeated it, same thing. I restarted, same thing. I tried JACK first, same thing. I am rather lowlytechly, but not lowtech, so I do need some help with this problem.
As I am a noob, my hand will need to be held a bit, but I'll wear a glove!
Thanks, please reply ASAP
Signed,
A stratocaster turned sadocaster.

Hydrogen should not run through wine. It got a native linux programm. We are talking about the drum machine hydrogen are we?

Hi zhjim, thanks for your quick response.
Ah, sarcasm so early in the morning? Yes, we are talking about the Hydrogen drum machine and not the element.
Not 100 percent sure what the "WINE window" said when it flashed up - i.e. if it was a notification from WINE or Hydrogen.
What I'll do is take this noob time to learn a bit more about bug reporting, since I have no clue.
Can you, in the meantime, give me some help?

I did a factory reset to see what the window said and here it is:
The Wine configuration in /root/.wine is being updated, please wait.

I also noticed JACK isn't starting either.

One thing it said in the Ubuntu Forums on bugtracking was that I should first ensure my BIOS is updated before I report anything, so I'll look into that first.

Let me know if you want me to post any log data but I'll need help knowing how to do that. Thanks!

As I have no experience with your OS I can't tell you much. I just suppose that jack needs to be started before hydrogen. And just to repeat my self hydrogen should not be run through wine. Not sure why this happens but thats not the way to go. Especially as hydrogen in wine will have a hard time to use jack.

So try to start hydrogen without wine. Just fire up a console and put in hydrogen followed by enter. Then we go on.

And this bs about the bios has to be update before filling in a bug report is bs.

also before you get to used to the old "leet" version
you might want to install 14.1 instead of the old version 13

http://www.slackware.com/getslack/

also there IS a linux version
http://www.hydrogen-music.org/hcms/node/21

(--- the OLD code from 2011 --- )
the STABLE source code for 0.9.5.1
http://sourceforge.net/projects/hydr...ar.gz/download

However installing the newer the 0.9.6 beta3 would be better
http://sourceforge.net/projects/hydr...Hydrogen/0.9.6
http://sourceforge.net/projects/hydr...ar.gz/download


there is NO NEED to use the Microsoft windows .exe version
But if you MUST use the Microsoft windows version then install it on a MS OS like Windows7

Hi DiggerD, there seems to be some confusion here. Some people seem to think you're running Slackware 13.37 instead of Studio 13.37, but Studio 13.37 is based on Slacko 5.3, which was based on Slackware 13.37 at time of release. Studio 13.37 has its own packages and doesn't use the Slackware ones, although it is compatible with them.

You're not using a Windows version of Hydrogen, you're using the latest stable version for Linux. A newer beta version is available here. You can just click that and it will automatically install. The reason it is showing the window saying WINE is updating is that Hydrogen (and lots of other programs in the JACK Software Suite) has been compiled with VST support. It should show that window for a few seconds the first time you run any of those programs, once, and then never show it again. Hydrogen should open right after it disappears.

What worries me is that you say JACK won't start. That might be your problem right there. Are you using a super-old computer? Does it have 512 MB of RAM?

Before starting JACK or Hydrogen, try clicking the silver and purple icon on the bar the bottom of the screen labeled "Load Extras". The "Extras" are loaded by default first boot, and clicking that also unloads it. Unloading the Extras pack will decrease the footprint 13.37 uses in terms of RAM.

As for updating your bios, that shouldn't be necessary under normal conditions. You could try it, but if your pc isn't ancient it should be fine.

Here is another thread that someone started about JACK not working that the OP got sorted. That is the thing you have to solve.

If all else fails, you can of course send it back for a full refund.

Cheers

1 members found this post helpful.

Hi, thanks for all your reponses!

The computer is a Dell Latitude D820 and I recently upgraded to 4GB of RAM from the 1G it had in it. T5500 1.66 Ghz processor. I think it's from 2008.

I won't try unloading the extras because it has enough RAM.

I'll try starting Hydrogen again later today and it if continues to crash I'll research the thread on JACK.

I don't want to hand it back in without giving it at least a few weeks trying to get it in order. I don't expect everything to be working because of all the variables.

Cheers, Big Ears!

See if you can get JACK working. Sometimes it's just the wrong audio card (like an internal modem or something) selected by default. You can select your audio card under "interfaces" in JACK settings. You can also set it system-wide by using the Multiple Sound Card Wizard (may require a reboot to take effect).

Hi,
The sound card was set to 'default' so I went ahead and chose mine, and no luck. Checked the wizard too, no go.
Here's the log:

20:30:23.353 Patchbay deactivated.
20:30:23.374 Statistics reset.
20:30:23.790 Startup script...
20:30:23.792 artsshell -q terminate
20:30:23.836 ALSA connection graph change.
sh: artsshell: command not found
20:30:24.311 Startup script terminated with exit status=32512.
20:30:24.313 JACK is starting...
20:30:24.315 /usr/bin/jackd -R -dalsa -dhw:0,0 -r48000 -p1024 -n2
20:30:24.323 JACK was started with PID=11270.
jackd 0.121.2
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
20:30:24.518 ALSA connection change.
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0,0|hw:0,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
20:30:26.746 Server configuration saved to "/root/.jackdrc".
20:30:26.761 Statistics reset.
20:30:26.880 Client activated.
20:30:26.883 JACK connection change.
20:30:26.929 Buffer size change (1024).
20:30:26.936 XRUN callback (1).
20:30:28.909 XRUN callback (45 skipped).
20:30:30.924 XRUN callback (45 skipped).
20:30:32.932 XRUN callback (44 skipped).
jackd watchdog: timeout - killing jackd
DebugModuleManager::unregisterModule: Could not unregister DebugModule ( cannot read server event (Success)
cannot continue execution of the processing graph (Bad file descriptor)
zombified - calling shutdown handler
20:30:34.821 Shutdown notification.
20:30:34.822 JACK is stopping...
20:30:34.823 JACK is being forced...
20:30:34.825 JACK has crashed.
20:30:35.023 JACK was stopped successfully.
20:30:35.023 Post-shutdown script...
20:30:35.024 killall jackd
killall: jackd: no process killed
20:30:35.439 Post-shutdown script terminated with exit status=256.

I checked out the link on JACK and I'll continue looking into it.