Linux Problem With Jack And Renoise

I’m sorry if this is in the wrong forum.

So, after upgrading from the regular Ubuntu 7.10 to get some new programs after finding out the repositories for 7.10 weren’t being supported anymore I can’t seem to get realtime and jack working now. Could be some Ubuntu configuration thing.

Shortly: I load a song, no problem, I load another song - jack kicks Renoise out and Renoise freezes completely and I have to crash it.

Long version:
I start jack

loading driver .. apparent rate = 44100 creating alsa driver ... hw:0|hw:0|128|2|44100|0|0|nomon|swmeter|-|32bit control device hw:0 configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 2 periods ALSA: final selected sample format for capture: 16bit little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 16bit little-endian ALSA: use 2 periods for playback [b]JACK: unable to mlock() port buffers: Cannot allocate memory JACK: unable to mlock() port buffers: Cannot allocate memory[/b] 03:19:27.408 Server configuration saved to "/home/nanapo/.jackdrc". 03:19:27.410 Statistics reset. 03:19:27.412 Client activated. 03:19:27.415 JACK connection change. 03:19:27.441 JACK connection graph change.

The bold part might be something, but it starts fine.
I start Renoise 2.1 RC (the public demo) and load a song, yay everything works.

I load another song and Renoise won’t do anything (play the song or any instrument).
I go to jack and the messages window says:

subgraph starting at qjackctl timed out (subgraph_wait_fd=16, status = 0, state = Running, pollret = 0 revents = 0x0)  

And Renoise isn’t in the Connections list anymore.
I figure, maybe it’ll help to re-initialize jack in the Renoise settings and it freezes. I crash Renoise and check the logfile even though I understand nothing of it:

[code]============================================================
Version : Renoise V2.1.0rc1 (May 14 2009)
Date : 2009-05-23
Time : 03:25:58
OS : Linux version 2.6.28-3-rt (buildd@vernadsky) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #12-Ubuntu SMP PREEMPT RT Fri Apr 17 10:09:11 UTC 2009

============================================================

CPU: Found 1 enabled unit(s) with 1 core(s) / 1 logical processor(s) per unit. 1 cores are enabled in total.

Application: Showing the splash window…

StartupWindow: Initialiting the startup window…

Graphport: Initialising XThreads…
Graphport: Opening XDisplay ‘:0.0’ (configured via ‘DISPLAY’ env)…
Graphport: XDisplay was successfully opened
Graphport: Initializing Freeimage…

StartupWindow: Startup window successfully initialized…

Application: Initializing the API…

GraphPort: Loading cursor images (libXcursor is present)…

System: Running from ‘/usr/local/bin’…

GraphPort: Initializing the Font Engine…

Graphport: Initializing Keyboard mappings…
Graphport: Initializing XAtoms…

Application: Initializing Icon Bitmaps…

ALSA: Enumerating Devices…
ALSA: PLAYBACK info: card 0: nForce2 [NVidia nForce2], device 0: Intel ICH [NVidia nForce2]
ALSA: CAPTURE info: card 0: nForce2 [NVidia nForce2], device 0: Intel ICH [NVidia nForce2]
ALSA: CAPTURE info: card 0: nForce2 [NVidia nForce2], device 1: Intel ICH - MIC ADC [NVidia nForce2 - MIC ADC]
ALSA: PLAYBACK info: card 0: nForce2 [NVidia nForce2], device 2: Intel ICH - IEC958 [NVidia nForce2 - IEC958]

MIDI-IO: Starting the input thread…
MIDI-IO: Adding unlinked virtual MIDI in ports…
MIDI-IO: Adding unlinked virtual MIDI out ports…
MIDI-IO: Enumerating external input devices…
MIDI-IO: Adding Input device ‘Midi Through Port-0’…
MIDI-IO: Enumerating external output devices…
MIDI-IO: Ignoring client 'OSS sequencer’s port ‘Receiver’ (blacklisted device)…
MIDI-IO: Adding Output device ‘Midi Through Port-0’…

DspDevices: Registering native DSP effects…

Application: Creating the main application…
Application: Start running…
Application: Loading the preferences…
Application: Init…

VSTPlugs: VST_PATH environment variable not set. Using ‘/usr/lib/vst:/usr/local/lib/vst:~/.vst’…
VSTPlugs: Searching for new VST plugins in ‘/usr/lib/vst/’…
VSTPlugs: Skipping VST path ‘/usr/local/lib/vst/’ (Directory does not exist)…
VSTPlugs: Skipping VST path ‘/home/nanapo/.vst/’ (Directory does not exist)…

LADSPA: LADSPA_PATH environment variable not set. Using ‘/usr/lib/ladspa:/usr/local/lib/ladspa:~/.ladspa’…
LADSPA: Searching for LADSPA plugins in ‘/usr/lib/ladspa/’…
LADSPA: Scanning ‘/usr/lib/ladspa/sc4_1882.so’…
LADSPA: Scanning ‘/usr/lib/ladspa/sifter_1210.so’…
(etc)

ALSA: Opening ALSA Playback Device ‘hw:0,0 (NVidia nForce2)’…
ALSA: Open ALSA Output Device FAILED!

Error Message: Failed to open the ALSA device ‘hw:0,0 (NVidia nForce2)’ (Device or resource busy).

Error Message: ALSA failed to open. Trying to open Jack instead…

Jack: Trying to open client ‘renoise’…
Jack: Running as conditional timebase master…
Jack: Sample rate: 44100
Jack: Using Buffersize 128…
Jack: Configuring the Player…
Jack: Successfully connected port ‘system:capture_1’ to port renoise:input_01_left
Jack: Successfully connected port ‘system:capture_2’ to port renoise:input_01_right
Jack: Successfully connected port ‘system:playback_1’ to port renoise:output_01_left
Jack: Successfully connected port ‘system:playback_2’ to port renoise:output_01_right
Jack: Up and running

MIDI-IO: Opening MIDI in device ‘Renoise MIDI In Port A’…
MIDI-IO: Opening MIDI in device ‘Renoise MIDI In Port B’…
MIDI-IO: Opening MIDI in device ‘Renoise MIDI In Sync’…
MIDI-IO: Opening MIDI out device ‘Renoise MIDI Out Sync’…

Application: Creating a new document…

Player: Constructing…
Player: Creating the slave threads…
Player: Start running…

GUI: Creating the Document GUI…
GUI: Successfully constructed

Application: A new document was created.

GraphPort: Initializing in WindowedMode…
GraphPort: Successfully initialized

Application: Init OK

StartupWindow: Closing the window…

Application: Enter MainLoop…

Application: Releasing the old document…

Player: Constructing…
Player: Creating the slave threads…
Player: Start running…

GUI: Creating the Document GUI…
GUI: Successfully constructed

Application: Loading ‘78.xrns’…

Player: Constructing…
Player: Creating the slave threads…
Player: Start running…

GUI: Creating the Document GUI…
GUI: Successfully constructed

Application: Successfully loaded ‘78.xrns’.

Application: Releasing the old document…

Player: Constructing…
Player: Creating the slave threads…
Player: Start running…

GUI: Creating the Document GUI…
GUI: Successfully constructed

Application: Loading ‘42.xrns’…

Player: Constructing…
Player: Creating the slave threads…
Player: Start running…

GUI: Creating the Document GUI…
GUI: Successfully constructed

Application: Successfully loaded ‘42.xrns’.

Jack: Deactivate…
[/code]

So the error maybe occurred while loading the 42.xrns.

I tried this with the previous version of Renoise by accident, and it does the same thing, except when re-initializing jack it doesn’t freeze and everything works.

Maybe it’s worth noting too that both of these songs were made in the previous version of the Renoise demo.

And like I said, it’s possible I have something in Linux configured wrong so if there’s a way to check things like that it’d be great. I tried searching for similar problems with jack or realtime but I couldn’t find any help really.

Hello,

looks like Jack auto-terminates Renoise, when its using temporarily too much CPU, then freezes. This can be avoided by setting jacks client timeout value to something like 1000 or 2000.

Still strange though that it doesn’t disconnect cleanly, but crashes instead. You don’t get a message by Renoise that it got disconnected by jack?
Suva got the same problem as well: http://www.renoise.com/board/index.php?showtopic=20580

Probably this only happens on 64bit OSs?

Oh yeah I forgot to mention that when I did this with 2.0 it did tell me that it couldn’t find jack and was switching to alsa, but now I can’t get that to happen.

But as far as I know I’m on a 32bit. Wouldn’t bet on it but I always thought so. Changing the timeout value seemed to do the trick though, thanks.

EDIT: I started to go through the Renoise tutorial for setting things up. While checking if jack is working properly it gave me:

no message buffer overruns  
jackd: unknown driver 'your_backend'  
  

And I have jack set to use alsa in the settings. I don’t know what to do.