Print

[usrfriendly]

I'm using Milkytracker 0.90.85, on Arch Linux with Deltafire's PKGBUILD, modified to add --with-jack, and using JACK 0.118.0.  Everything I post is done with Jack running in the background, with a working setup for MilkyTracker and my keyboard doing it's midi in, and output through my laptop's speakers.

The issue I have is when I start Milkytracker with Jack as the default sound driver, I get the following output:

Code: [Select]

ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA: Failed to open device 'default' (Device or resource busy)
JACK: Mixer frequency: 48000
JACK: Latency = 1024 frames
cannot lock down memory for RT thread (Cannot allocate memory)
[arin@eee ~]$ milkytracker
JACK: Mixer frequency: 48000
JACK: Latency = 1024 frames

RtMidiIn::openPort: error starting MIDI input thread!


RtMidiIn::openPort: error starting MIDI input thread!
I would've just left it there, if I didn't manage to trick MilkyTracker by starting it up with ALSA as the sound driver, which gives the following:

Code: [Select]

ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA: Failed to open device 'default' (Device or resource busy)
And then changing the driver to Jack, which add this to the output:

Code: [Select]

JACK: Mixer frequency: 48000
JACK: Latency = 1024 frames
cannot lock down memory for RT thread (Cannot allocate memory)
Thus allowing me to add notes with my midi keyboard when I set it's input to 129:RtMidi Input Client, which in turn points to 0:Midi Through Port-0 in my qjackctl "Connections" window (see diagram attached to post).

I think I was rather thorough, but if there's any links I happen to have left out, I'll fill them in.

[PROGRAM_IX]

JACK isn't working for me either, but it's at the Sound Driver Initialisation phase that it fails. It says it can't load libjack. So I went to check if it was installed. The only packages of a similar name are labelled libjack0 - is there some ambiguity somewhere?

[Deltafire]

arinlares:

I'm not quite sure I have understood your report, it's left me a little confused

Anyway, for Midi support Milkytracker uses a 3rd-party library called RTMidi - this has nothing to do with Jack or the audio driver.

For audio, there are 4 drivers for Linux iirc:
Alsa
Jack
RTAudio - a closely related cousin to RTMidi, but it provides cross-platform audio support
SDL

So selecting Jack as the audio driver should make no difference to Milkytracker's Midi functionality, as it is entirely separate.


PROGRAM_IX:

I don't know what name the Jack audio driver has on your distribution, but libjack0 seems a likely candidate (perhaps it's version 0.xx).

[usrfriendly]

That's what I get for writing it at 3 AM, as I have to stumble through it. 

So, should midi input work with the Alsa driver?

[Deltafire]

Yes, I think there's a command line tool named 'aconnect' which allows you to route midi devices to Milkytracker.