[ardour-users] RE: Problems recording through Jack -- update

[Darcy Kahle]

A couple of people recommended qjackctl to launch Jack, so I downloaded the
latest version of that, and configured it to launch Jack with the same
arguments as I was launching it via Rosegarden.  R. Parker thought that the
ardour error message was due to an old rc file.  I renamed that file and let
ardour regenerate it, and the error message went away.  What I am seeing
now, is no synching at all.  I press play in ardour, and nothing happens in
Rosegarden.  The only changes that I made to either ardour or rosegarden was
to tell rosegarden not to launch jack.  The following is what the connection
screen in qjackctl shows.  Forgive the formatting, but it is difficult to
recreate in ascii the connection window.  This format should provide the
info.

Audio tab:
Alsa_pcm
- capture1 --> Ardour->master/in1, rosegarden->record in 1 L
- capture2 --> rosegarden->record in 2 R
Ardour
- Audio 1/out 1 --> Alsa_pcm->playback_1
- auditioner/out 1 --> Alsa_pcm->playback_1
- auditioner/out 2 --> Alsa_pcm->playback_2
- click/out 1 --> Alsa_pcm->playback_1, rosegarden->record in 1 L,
rosegarden->record in 1 R
- master/out 1 --> Alsa_pcm->playback_1
- master/out 2 --> Alsa_pcm->playback_2
Rosegarden
- master out L --> Alsa_pcm->playback_1, ardour->Audio 1/in 1
- master out R --> Alsa_pcm->playback_2
- record monitor out L -->
- record monitor out R -->

Midi tab:
129:Rosegarden sequencer
- 0:Rosegarden --> 64:emu10k1 mpu-401(uart)-rawmidi 0->0:emu10k1 mpu-401
(uart),
.................. 65:emu10k1 wavetable->0:emu10k1 port 0,
.................. 65:emu10k1 wavetable->1:emu10k1 port 1,
.................. 65:emu10k1 wavetable->2:emu10k1 port 2,
.................. 65:emu10k1 wavetable->3:emu10k1 port 3,
.................. 72:midisport 2x2-rawmidi 1->0:midisport 2x2 midi 1,
.................. 72:midisport 2x2-rawmidi 1->1:midisport 2x2 midi 2
130:ardour
- 0:seq -->
64:emu10k1 mpu-401(uart)-rawmidi 0
- 0:emu10k1 mpu-401(uart) --> 129:rosegarden sequencer->0:rosegarden
72:midisport 2x2-rawmidi 1
- 0:midisport 2x2 midi 1 -->
- 1:midisport 2x2 midi 2 -->

-----Original Message-----
From: Darcy Kahle [mailto:darcykahle at sympatico.ca]
Sent: Tuesday, August 03, 2004 9:26 PM
To: ardour-users-ardour.org at lists.ardour.org
Subject: Problems recording through Jack


Forgive me if this is the wrong place to be asking this.

I am running Rosegarden 4-0.9.8, Jack Audio Connection Kit 0.98.1, and
Ardour 0.9beta18.1 on White Box Linux 3.0. I have a Soundblaster Live! (not
OEM) and a Midiman Midisport 2x2 installed and working under Alsa 1.0.2.

When Rosegarden launches, it starts up Jack using the following command:

/usr/local/bin/jackd -d alsa -d hw -r 44100 -p 2048 -n 2

What I am trying to do is record midi files created in Rosegarden as a wave
file under Ardour. I have gotten it to the point where I have both apps
launched at the same time, and I press play under Ardour, play starts under
Rosegarden, and I hear the piece that I am trying to record. The only thing
that gets recorded, is the heartbeat that Ardour generates. I know that I am
doing something wrong. Either I have started Jack up incorrectly, I am not
setting Ardour up to record properly, or Rosegarden is not playing through
Jack. Or a combo of all three. I believe that the issue is with Ardour,
because of the output I get when I launch it (below). Please note, that I
launch Rosegarden through sudo first, then I launch ardour, also through
sudo.

Does anyone have any tips that could help me get this working? I have
reviewed many sites concerning this issue, and have not gotten very far. I
think that I am missing something small. Something that the manuals and
other howtos gloss over. Any help or pointers would be greatly appreciated.

Darcy
----------------
$ sudo ardour
Ardour/GTK 0.524.0 running with libardour 0.823.0
Loading UI configuration file /usr/local/etc/ardour/ardour_ui.rc
Loading system configuration file /usr/local/etc/ardour/ardour_system.rc
Loading user configuration file /home/luser/.ardour/ardour.rc
ardour: [ERROR]: MIDI: port device in use
ardour: [WARNING]: No MMC control (MIDI port "hw:0" not available)
ardour: [ERROR]: KeyboardTarget: unknown action
"edit-cursor-to-selection-start"ardour: [ERROR]: KeyboardTarget: unknown
action "edit-cursor-to-selection-end"
ardour: [ERROR]: KeyboardTarget: unknown action "set-mouse-mode-scrub"
ardour: [ERROR]: KeyboardTarget: unknown action "start-selection"
ardour: [ERROR]: KeyboardTarget: unknown action "finish-selection"
ardour: [ERROR]: KeyboardTarget: unknown action
"extend-selection-to-end-of-region"
ardour: [ERROR]: KeyboardTarget: unknown action
"extend-selection-to-start-of-region"
ardour: [ERROR]: KeyboardTarget: unknown action "duplicate-selection"
ardour: [ERROR]: KeyboardTarget: unknown action "split-region"
stopping peak file builder thread
stopping signal thread
Ardour is done. Come again. Have a nice day. Etc.