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

Darcy Kahle darcykahle at sympatico.ca
Fri Aug 20 10:52:45 PDT 2004


Thanks for this suggestion.  Rosegarden and ardour are now synching up
nicely.  What I now have to do is work out the sound routing, so that what
is played in rosegarden is recorded in ardour.  A few days ago, someone
pointed out that Rosegarden is supposed to be connected to Ardour's tracks,
which in turn connect to Ardour's master bus, which plays out to Alsa_pcm.
For the life of me, I cannot puzzle through setting this up inside the
respective packages.

The tracks in Rosegarden use the Soundblaster Live! Synth #1.  I have tried
setting the instrument to Jack, where you have the choice of setting In/Out.
Needless to say, when playing to Jack, no sound comes out.  Probably due to
the fact that Jack is not routing the sound through Ardour to the soundcard.
The problem with this, is I loose control over the selection of the
instrument's voice.  I have also tried setting the MMC Transport Mode from
MMC Slave to either Off or MMC Master, but I saw no change.

I am quite certain that ardour's connections are not set up correctly, as I
am not yet comfortable with the connection interface, and I cannot seem to
find relavant documentation that would assist me.  What would be useful is
something like "go to this tab in this dialog in Ardour and set this field".
Once it is working, I should be able to see how and why it works, but
without a working base, it is difficult for me to figure out the
configurations.

-----Original Message-----
From: R Parker [mailto:rtp405 at yahoo.com]
Sent: Monday, August 09, 2004 1:52 PM
To: Darcy Kahle; ardour-users-ardour.org at lists.ardour.org
Subject: Re: [ardour-users] RE: Problems recording through Jack --
update


Hi,

--- Darcy Kahle <darcykahle at sympatico.ca> wrote:

> 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.

Without looking at Ardour or Rosegarden:
Configure Rosegarden to be the JACK transport Time
Master and Ardour to use JACK transport Syncronization
(not master). When properly configured, either will be
able to control the JACK Transport and cause the other
to follow suit.

If you're using MMC for transport control from a
hardware mixer then enable external MMC control in
Ardour. Use the qjackctl MIDI interface to route
incoming MMC to the Ardour "Seq" interface. If there's
more than one MIDI port specified in ardour.rc, delete
all but the "Seq" interface--"hw:0" or whatever.

In theory, any combonation of master and slave should
work but I'm not sure about the state of Ardour Time
Master and Rosegarden Sync to JACKD. The above
configuration has worked for me.

ron

  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.
>
>
> _______________________________________________
> ardour-users-ardour.org mailing list
> ardour-users at lists.ardour.org
>
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
>




__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail





More information about the Ardour-Users mailing list