From: Bob Ham <node@users.sourceforge.net>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: ALSA Development Mailing List <alsa-devel@lists.sourceforge.net>,
Ardour Devel Mailing List <ardour-dev@lists.sourceforge.net>
Subject: Re: [ardour-dev] Re: guitar + sblive + ardour + ladspa effects
Date: 29 Jul 2002 22:09:04 +0100 [thread overview]
Message-ID: <1027976945.10076.95.camel@insanity> (raw)
In-Reply-To: <3D45A636.4030000@boosthardware.com>
On Mon, 2002-07-29 at 21:31, Patrick Shirkey wrote:
> Have a read of the arecord quicktoot
>
> http://www.boosthardware.com/LAU/quicktoots
>
> That will give you some info about using alsamixer correctly.
Getting ardour to be able to record/modify the incoming sound isn't the
issue. It's getting ardour to do that without it going through the
speakers beforehand. I don't want to hear any sound if I put the mixer
slider down to nothing in ardour. At the moment, I hear the original,
clean guitar signal. I assume the line input is getting routed to both
jack's alsa_pcm inputs and the soundcard's amp. I want it only to go to
jack, and then the ladspaified signal to the amp afterwards.
Bob
--
Bob Ham: bob@ham.org http://pkl.net/~node/
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
next prev parent reply other threads:[~2002-07-29 21:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 20:08 guitar + sblive + ardour + ladspa effects Bob Ham
2002-07-29 20:31 ` Patrick Shirkey
2002-07-29 21:09 ` Bob Ham [this message]
2002-07-29 20:53 ` Paul Davis
2002-07-30 6:40 ` Mark Constable
2002-07-31 14:52 ` Takashi Iwai
2002-07-31 15:56 ` Bob Ham
2002-10-18 17:53 ` sblive line capture woes Bob Ham
2002-10-18 17:22 ` Jaroslav Kysela
2002-10-18 20:03 ` Bob Ham
2002-10-18 18:31 ` Jaroslav Kysela
2002-10-18 21:17 ` Bob Ham
2002-10-18 19:36 ` Jaroslav Kysela
2002-10-18 19:52 ` Takashi Iwai
2002-10-18 18:10 ` Bob Ham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1027976945.10076.95.camel@insanity \
--to=node@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ardour-dev@lists.sourceforge.net \
--cc=pshirkey@boosthardware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox