13 Feb
2013
13 Feb
'13
3:58 a.m.
Okay guys ... a few weeks ago I got jack running with audacity.
Couldn't have done it without your help.
But, this was with a dirt cheap Behringer usb interface. Which I
thought might not be the greatest.
Today, my new and improved Presonus audiobox USB arrived. After
changing a few names in my startup script ... it all seemed to be
working. Until I tried to record using audacity. Remember, this worked
fine with the cheapie.
Now I get a series of xruns:
This is snipped from my terminal. Not sure where the audacity stuff
stops, but better too much?
Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1670
Expression 'AlsaOpen( &alsaApi->baseHostApiRep, params, streamDir,
&self->pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1830
Expression 'PaAlsaStreamComponent_Initialize( &self->capture, alsaApi,
inParams, StreamDirection_In, NULL != callback )' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 2092
Expression 'PaAlsaStream_Initialize( stream, alsaHostApi,
inputParameters, outputParameters, sampleRate, framesPerBuffer,
callback, streamFlags, userData )' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 2764
Expression 'stream->playback.pcm' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 4541
Expression 'stream->playback.pcm' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 4541
Expression 'stream->playback.pcm' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 4541
Expression 'stream->playback.pcm' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 4541
JackEngine::XRun: client = PortAudio was not run: state = 2
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
The recording works, but it compressed/expanded and is totally
useless. I'm having audacity play back a stereo track while recording
one.
So, did I but the wrong bit or hardware? I did check and it seems to
be a workable unit.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
13 Feb
13 Feb
4:01 a.m.
why are you running JACK with a PortAudio backend? or ... why are you
running Audacity with PortAudio trying to talk to JACK via ALSA?
On Tue, Feb 12, 2013 at 9:58 PM, Bob van der Poel <bob(a)mellowood.ca> wrote:
Okay guys ... a few weeks ago I got jack running with
audacity.
Couldn't have done it without your help.
But, this was with a dirt cheap Behringer usb interface. Which I
thought might not be the greatest.
Today, my new and improved Presonus audiobox USB arrived. After
changing a few names in my startup script ... it all seemed to be
working. Until I tried to record using audacity. Remember, this worked
fine with the cheapie.
Now I get a series of xruns:
This is snipped from my terminal. Not sure where the audacity stuff
stops, but better too much?
Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line:
1670
Expression 'AlsaOpen( &alsaApi->baseHostApiRep, params, streamDir,
&self->pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line:
1830
Expression 'PaAlsaStreamComponent_Initialize( &self->capture, alsaApi,
inParams, StreamDirection_In, NULL != callback )' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 2092
Expression 'PaAlsaStream_Initialize( stream, alsaHostApi,
inputParameters, outputParameters, sampleRate, framesPerBuffer,
callback, streamFlags, userData )' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 2764
Expression 'stream->playback.pcm' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 4541
Expression 'stream->playback.pcm' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 4541
Expression 'stream->playback.pcm' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 4541
Expression 'stream->playback.pcm' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 4541
JackEngine::XRun: client = PortAudio was not run: state = 2
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
The recording works, but it compressed/expanded and is totally
useless. I'm having audacity play back a stereo track while recording
one.
So, did I but the wrong bit or hardware? I did check and it seems to
be a workable unit.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
4:14 a.m.
On Tue, Feb 12, 2013 at 8:01 PM, Paul Davis <paul(a)linuxaudiosystems.com> wrote:
why are you running JACK with a PortAudio backend? or
... why are you
running Audacity with PortAudio trying to talk to JACK via ALSA?
I have no idea. My jack command is
jackd -d alsa -d hw:CARD=USB &
and aplay -L shows:
bob$ aplay -L
default
Playback/recording through the PulseAudio sound server
sysdefault:CARD=SB
HDA ATI SB, ALC883 Analog
Default Audio Device
front:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Front speakers
surround40:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=SB,DEV=0
HDA ATI SB, ALC883 Digital
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Direct sample mixing device
dmix:CARD=SB,DEV=1
HDA ATI SB, ALC883 Digital
Direct sample mixing device
dsnoop:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Direct sample snooping device
dsnoop:CARD=SB,DEV=1
HDA ATI SB, ALC883 Digital
Direct sample snooping device
hw:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Direct hardware device without any conversions
hw:CARD=SB,DEV=1
HDA ATI SB, ALC883 Digital
Direct hardware device without any conversions
plughw:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Hardware device with all software conversions
plughw:CARD=SB,DEV=1
HDA ATI SB, ALC883 Digital
Hardware device with all software conversions
sysdefault:CARD=USB
AudioBox USB, USB Audio
Default Audio Device
front:CARD=USB,DEV=0
AudioBox USB, USB Audio
Front speakers
surround40:CARD=USB,DEV=0
AudioBox USB, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=USB,DEV=0
AudioBox USB, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=USB,DEV=0
AudioBox USB, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=USB,DEV=0
AudioBox USB, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=USB,DEV=0
AudioBox USB, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=USB,DEV=0
AudioBox USB, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=USB,DEV=0
AudioBox USB, USB Audio
Direct sample mixing device
dsnoop:CARD=USB,DEV=0
AudioBox USB, USB Audio
Direct sample snooping device
hw:CARD=USB,DEV=0
AudioBox USB, USB Audio
Direct hardware device without any conversions
plughw:CARD=USB,DEV=0
AudioBox USB, USB Audio
Hardware device with all software conversions
Should I use a different "-d"?
I do have pulse running, but the usb device is set to "off" in the
pavucontrol. So, I'm assuming that this should not be the problem ?
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
4:19 a.m.
JACK looks OK, except that you want hw:USB not hw:CARD=USB (i think, or
maybe based on later output, hw:SB)
it appears that you are running audacity *without* JACK support or telling
it explicitly not to use JACK; instead it opens the default ALSA device,
which is pulseaudio, which is probably not working (correctly) while JACK
is running.
On Tue, Feb 12, 2013 at 10:14 PM, Bob van der Poel <bob(a)mellowood.ca> wrote:
On Tue, Feb 12, 2013 at 8:01 PM, Paul Davis
<paul(a)linuxaudiosystems.com>
wrote:
why are you running JACK with a PortAudio
backend? or ... why are you
running Audacity with PortAudio trying to talk to JACK via ALSA?
I have no idea. My jack command is
jackd -d alsa -d hw:CARD=USB &
and aplay -L shows:
bob$ aplay -L
default
Playback/recording through the PulseAudio sound server
sysdefault:CARD=SB
HDA ATI SB, ALC883 Analog
Default Audio Device
front:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Front speakers
surround40:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=SB,DEV=0
HDA ATI SB, ALC883 Digital
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Direct sample mixing device
dmix:CARD=SB,DEV=1
HDA ATI SB, ALC883 Digital
Direct sample mixing device
dsnoop:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Direct sample snooping device
dsnoop:CARD=SB,DEV=1
HDA ATI SB, ALC883 Digital
Direct sample snooping device
hw:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Direct hardware device without any conversions
hw:CARD=SB,DEV=1
HDA ATI SB, ALC883 Digital
Direct hardware device without any conversions
plughw:CARD=SB,DEV=0
HDA ATI SB, ALC883 Analog
Hardware device with all software conversions
plughw:CARD=SB,DEV=1
HDA ATI SB, ALC883 Digital
Hardware device with all software conversions
sysdefault:CARD=USB
AudioBox USB, USB Audio
Default Audio Device
front:CARD=USB,DEV=0
AudioBox USB, USB Audio
Front speakers
surround40:CARD=USB,DEV=0
AudioBox USB, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=USB,DEV=0
AudioBox USB, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=USB,DEV=0
AudioBox USB, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=USB,DEV=0
AudioBox USB, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=USB,DEV=0
AudioBox USB, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=USB,DEV=0
AudioBox USB, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=USB,DEV=0
AudioBox USB, USB Audio
Direct sample mixing device
dsnoop:CARD=USB,DEV=0
AudioBox USB, USB Audio
Direct sample snooping device
hw:CARD=USB,DEV=0
AudioBox USB, USB Audio
Direct hardware device without any conversions
plughw:CARD=USB,DEV=0
AudioBox USB, USB Audio
Hardware device with all software conversions
Should I use a different "-d"?
I do have pulse running, but the usb device is set to "off" in the
pavucontrol. So, I'm assuming that this should not be the problem ?
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
14 Feb
14 Feb
2:07 a.m.
On Tue, Feb 12, 2013 at 8:19 PM, Paul Davis <paul(a)linuxaudiosystems.com> wrote:
JACK looks OK, except that you want hw:USB not
hw:CARD=USB (i think, or
maybe based on later output, hw:SB)
it appears that you are running audacity *without* JACK support or telling
it explicitly not to use JACK; instead it opens the default ALSA device,
which is pulseaudio, which is probably not working (correctly) while JACK is
running.
Thanks Paul! I just tried it, briefly, with -d hw:USB and that seems
to be the solution.
If I live long enough I might actually figure out alsa naming :)
BTW, the earlier test with hw:CARD=USB did have audacity running jack.
I double checked that a few times. So, where the PA stuff was coming
from ... who knows.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
13 Feb
13 Feb
6:28 a.m.
On Tue, February 12, 2013 7:14 pm, Bob van der Poel wrote:
On Tue, Feb 12, 2013 at 8:01 PM, Paul Davis
<paul(a)linuxaudiosystems.com>
wrote:
Exactly. Audacity has no need of jack... or low latency. It is a tool that
is very good at what it does... record audio, not track over track, just
record. It does not need low latency, it can do any effects in the
application. It is and audio editor, cut/paste/morf audio. but not always
real time. It is not a good tool to listen to one track/set of tracks
while recording more. If you wish to do that use ardour. It will set up
and run jack for you with reasonable defaults for your first use. You can
lower the latency on the fly if you need to, all from ardour's menus. Good
place to start.
--
Len Ovens
www.OvenWerks.net
why are you running JACK with a PortAudio
backend? or ... why are you
running Audacity with PortAudio trying to talk to JACK via ALSA?
I have no idea. My jack command is 
2:09 p.m.
On Wed, Feb 13, 2013 at 5:28 AM, Len Ovens <len(a)ovenwerks.net> wrote:
Exactly. Audacity has no need of jack...
Perhaps, but I need Audacity to work with JACK. I'm not starting and
stopping JACK every time I want to switch between Ardour and Audacity.
Ardour affords much more professional multi-tracking features, but Audacity
excels in finalizing and error checking the final master: therefore I need
both at the same time, do an export, check for improvements, do
improvements in Ardour, export, check for improvements, etc.
@ Bob,
Audacity works fine here, there's "JACK" in the audio I/O drop down box
here..? Found this image online that shows what I'm talking about:
http://1.bp.blogspot.com/-lb_EleEc6BQ/UGx3NmrxypI/AAAAAAAABgc/4KMi9fdnw-Q/s…
Hth, -Harry
2:18 p.m.
On Wed, 13 Feb 2013 13:08:56 +0000
Harry van Haaren <harryhaaren(a)gmail.com> wrote:
On Wed, Feb 13, 2013 at 5:28 AM, Len Ovens
<len(a)ovenwerks.net> wrote:
For what it's worth, my workflow is to use timemachine to record - this
follows the unix principle of do just one thing but do it well. It is actually
dependent on jack on the input side, and will save to several different
formats. It also gives you a handy 10 second pre-record. Once I have the
recording safely on disk I then use whatever programs I like to do the
processing.
The greatest bugbear of using audacity directly for recording is that it uses
portaudio which doesn't create any connections until you actually send it data.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Exactly. Audacity has no need of jack...
Perhaps, but I need Audacity to work with JACK. I'm not starting and
stopping JACK every time I want to switch between Ardour and Audacity.
Ardour affords much more professional multi-tracking features, but Audacity
excels in finalizing and error checking the final master: therefore I need
both at the same time, do an export, check for improvements, do
improvements in Ardour, export, check for improvements, etc.
@ Bob,
Audacity works fine here, there's "JACK" in the audio I/O drop down box
here..? Found this image online that shows what I'm talking about:
http://1.bp.blogspot.com/-lb_EleEc6BQ/UGx3NmrxypI/AAAAAAAABgc/4KMi9fdnw-Q/s…
Hth, -Harry
14 Feb
14 Feb
2:40 a.m.
On Wed, Feb 13, 2013 at 6:18 AM, Folderol <folderol(a)ukfsn.org> wrote:
For what it's worth, my workflow is to use
timemachine to record - this
follows the unix principle of do just one thing but do it well. It is actually
dependent on jack on the input side, and will save to several different
formats. It also gives you a handy 10 second pre-record. Once I have the
recording safely on disk I then use whatever programs I like to do the
processing.
Hadn't see this program before. Interesting. Not for me, but it's nice
to know. I'm playing a live track over a prerecording background
generated from a MMA midi.
The greatest bugbear of using audacity directly for
recording is that it uses
portaudio which doesn't create any connections until you actually send it data.
Yeah, I've heard others mention this. Why is it a problem?
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
3:14 a.m.
On Wed, February 13, 2013 5:40 pm, Bob van der Poel wrote:
Probably means with jack. Part of the reason for using jack is to be able
to change routing and add audio blocks in the middle of the audio signal.
For example:
Sax -> mic->jack->eq->jack->reverb->jack->audacity
So the user starts jack and has the mic sound on capture-1. The user can
hook that up to one of the meter programs to see the signal and set the
the audio card inputs to the right amount below clipping... Or better use
the Audio IFs meters.
Next they try out some eq and decide they want to leave that in. (actually
I normally record dry) so now they have:
Sax->jack->eq->jack->headphones
Anyway they end up with:
Sax -> mic->jack->eq->jack->reverb->jack
And start audacity and try to connect jack to it.... but there is no
audacity ports (actually they would be portaudio ports)... Those ports
don't show up till you hit the record button in audacity... then they show
up, but they are auto connected to the capture channels. The user while
recording (hope they know how to use pause) has to disconnect the
portaudio input ports from the capture ports and reconnect them to the
reverb output ports. Fine now they can record a track.
Having recorded a track (one or two channels as may be) they decide to
record another track. The expectation is that the connections will be the
same... but they aren't. As soon as you stopped recording the portaudio
ports vanish and when you start again they are connected back to the
capture ports instead of what you did before, so the reconnect to reverb
has to be done over again.
The user thinks maybe I can use some session management to do the
connections for me. Only one problem, portaudio renames the ports to a
different name every time it creates them by adding a number as part of
the name.
A good jack aware application opens jack ports as soon as it starts up and
leaves them open for as long as the application remains open unless the
user asks other wise.
--
Len Ovens
www.OvenWerks.net
The greatest
bugbear of using audacity directly for recording is that it
uses
portaudio which doesn't create any connections until you actually send
it data.
Yeah, I've heard others mention this. Why is it a problem?
3:41 a.m.
On Wed, Feb 13, 2013 at 7:14 PM, Len Ovens <len(a)ovenwerks.net> wrote:
On Wed, February 13, 2013 5:40 pm, Bob van der Poel wrote:
Probably means with jack. Part of the reason for using jack is to be able
to change routing and add audio blocks in the middle of the audio signal.
For example:
Sax -> mic->jack->eq->jack->reverb->jack->audacity
So the user starts jack and has the mic sound on capture-1. The user can
hook that up to one of the meter programs to see the signal and set the
the audio card inputs to the right amount below clipping... Or better use
the Audio IFs meters.
Oh, I see. Makes sense. And, truly I'm really not using jacks power at
all. The only reason I'm using it at all is that I find that if I have
auacity play back a single track and record a 2nd it crashes and
burns. But, with jack it appears to be okay.
I'll have to do some more testing with the Presonus interface. But
that's for tomorrow.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
The
greatest bugbear of using audacity directly for recording is that it
uses
portaudio which doesn't create any connections until you actually send
it data.
Yeah, I've heard others mention this. Why is it a problem?
3:38 a.m.
One more discovery. If I set the audacity rate to 44100 I get the
compressed/expanded recording. However, using 48000 (sounds like it)
works perfectly.
Now, returning to my terminal I see a number of lines:
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
However, I don't know if this was with 44100 or 48K. I'll have to try
again tomorrow. I'm assuming (bad me) that the personus audiobox might
have a preference for 48k???
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
5:48 a.m.
On Wed, February 13, 2013 6:38 pm, Bob van der Poel wrote:
One more discovery. If I set the audacity rate to
44100 I get the
compressed/expanded recording. However, using 48000 (sounds like it)
works perfectly.
Now, returning to my terminal I see a number of lines:
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = PortAudio was not run: state = 1
However, I don't know if this was with 44100 or 48K. I'll have to try
again tomorrow. I'm assuming (bad me) that the personus audiobox might
have a preference for 48k???
Jack and audacity may have to be set to the same rate. (some programs
don't care and adjust their output to whatever the "card" is... in jacks
case jack is the card) If portaudio is just acting like a pipe for the
sound without resampling as needed that may be a problem.
--
Len Ovens
www.OvenWerks.net
13 Feb
13 Feb
2:27 p.m.
On Wed, 2013-02-13 at 13:08 +0000, Harry van Haaren wrote:
there's "JACK" in the audio I/O drop
down box here..? Found this image
online that shows what I'm talking about:
http://1.bp.blogspot.com/-lb_EleEc6BQ/UGx3NmrxypI/AAAAAAAABgc/4KMi9fdnw-Q/s…
FWIW a note: It's only there, if you first start jackd and then
Audacity ;).
3:24 p.m.
On Wed, February 13, 2013 5:08 am, Harry van Haaren wrote:
On Wed, Feb 13, 2013 at 5:28 AM, Len Ovens
<len(a)ovenwerks.net> wrote:
Ok, that is reasonable. Jack's latency will need to at least match what
audacity is using. I was playing around with bios settings and jack last
night (yes turning hyperthreading off does allow lower latency) and had
jack's latency set to 32 frames. I was able to play audacious through
pulse then jack with no problems (cpu was quite high, but no xruns). When
I tried gtreamer though (an ogg from a web page), the sound started to
chop up or stutter. There were still no xruns in jack, but I would guess
pulse was hiding the problem from jack. Raising the latency to even 64
frames (128 is better) takes care of this. In the case of Audacity,
portaudio is used to connect to jack (or alsa or pulse). As a mentioned
before Ardour does allow changing latency on the fly, it may be less
convenient to change this every time before using audacity, but it may
work too.
I don't know about your work flow, but in mine I change latency from
tracking to mixing anyway. I track with no effects and then as I add
effects I relax latency so my older computer can handle the extra workload
of eq, amp/box emulation, reverb, etc. Just getting the most out of what I
have.
--
Len Ovens
www.OvenWerks.net
Exactly. Audacity has no need of jack...
Perhaps, but I need Audacity to work with JACK. I'm not starting and
stopping JACK every time I want to switch between Ardour and Audacity.
Ardour affords much more professional multi-tracking features, but
Audacity
excels in finalizing and error checking the final master: therefore I need
both at the same time, do an export, check for improvements, do
improvements in Ardour, export, check for improvements, etc.
14 Feb
14 Feb
2:11 a.m.
Exactly. Audacity has no need of jack... or low
latency. It is a tool that
is very good at what it does... record audio, not track over track, just
record. It does not need low latency, it can do any effects in the
application. It is and audio editor, cut/paste/morf audio. but not always
real time. It is not a good tool to listen to one track/set of tracks
while recording more. If you wish to do that use ardour. It will set up
and run jack for you with reasonable defaults for your first use. You can
lower the latency on the fly if you need to, all from ardour's menus. Good
place to start.
--
Len Ovens
www.OvenWerks.net
Thanks for the comments, Lee. I don't know why you think that audacity
isn't up to the task? I've used it to do multi track stuff in the past
without issues. And, I've tried ardour in the past ... and this is not
a criticism of ardour, but most likely a comment on my brain size ...
but I really couldn't get it to work. Perhaps if I had more experience
with DAWs I'd be a lot happier with it. As it is, I use audacity to
play back a track (background) while I record myself playing my horn.
Easy.
Best,
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
4241
days inactive
4242
days old
linux-audio-user@lists.linuxaudio.org
15 comments
6 participants
participants (6)
-
Bob van der Poel -
Folderol -
Harry van Haaren -
Len Ovens -
Paul Davis -
Ralf Mardorf