20 Jun
2006
20 Jun
'06
2:37 p.m.
After removing my Multiface II and switching back to my nVidia onboard
audio, qjackctl will not run at 44100. I can set it in the setup window
and it reports starting 44100 in the messages:
11:07:46.232 Patchbay deactivated.
11:07:46.322 Statistics reset.
11:07:46.498 MIDI connection graph change.
11:07:46.528 MIDI connection change.
11:07:47.580 Startup script...
11:07:47.580 artsshell -q terminate
11:07:47.861 Startup script terminated with exit status=256.
11:07:47.861 JACK is starting...
11:07:47.862 jackd -R -dalsa -dhw:1,0 -r44100 -p512 -n2 -S
11:07:47.870 JACK was started with PID=3071 (0xbff).
jackd 0.101.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
Enhanced3DNow! detected
SSE2 detected
apparent rate = 44100
creating alsa driver ... hw:1,0|hw:1,0|512|2|44100|0|0|nomon|swmeter|-|16bit
control device hw:1
configuring for 44100Hz, period = 512 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
11:07:49.953 Server configuration saved to "/home/bozone/.jackdrc".
11:07:49.954 Statistics reset.
11:07:49.979 Client activated.
11:07:49.980 Audio connection change.
11:07:49.981 Audio connection graph change.
Enhanced3DNow! detected
SSE2 detected
11:10:21.095 MIDI connection graph change.
11:10:21.123 Audio connection graph change.
11:10:26.482 Audio connection graph change.
11:10:26.504 MIDI connection graph change.
But then both qjackctl and Ardour report 48000 as the samplerate.
All help is appreciated.
Link
--
e-mail is . . .
20 Jun
20 Jun
3:24 p.m.
Many built-in/inexpensive sound cards are stuck at 48K. Possibly this
one is also?
- Mark
On 6/20/06, Link Swanson <link(a)sumerianbabyl.com> wrote:
After removing my Multiface II and switching back to
my nVidia onboard
audio, qjackctl will not run at 44100. I can set it in the setup window
and it reports starting 44100 in the messages:
11:07:46.232 Patchbay deactivated.
11:07:46.322 Statistics reset.
11:07:46.498 MIDI connection graph change.
11:07:46.528 MIDI connection change.
11:07:47.580 Startup script...
11:07:47.580 artsshell -q terminate
11:07:47.861 Startup script terminated with exit status=256.
11:07:47.861 JACK is starting...
11:07:47.862 jackd -R -dalsa -dhw:1,0 -r44100 -p512 -n2 -S
11:07:47.870 JACK was started with PID=3071 (0xbff).
jackd 0.101.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
Enhanced3DNow! detected
SSE2 detected
apparent rate = 44100
creating alsa driver ... hw:1,0|hw:1,0|512|2|44100|0|0|nomon|swmeter|-|16bit
control device hw:1
configuring for 44100Hz, period = 512 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
11:07:49.953 Server configuration saved to "/home/bozone/.jackdrc".
11:07:49.954 Statistics reset.
11:07:49.979 Client activated.
11:07:49.980 Audio connection change.
11:07:49.981 Audio connection graph change.
Enhanced3DNow! detected
SSE2 detected
11:10:21.095 MIDI connection graph change.
11:10:21.123 Audio connection graph change.
11:10:26.482 Audio connection graph change.
11:10:26.504 MIDI connection graph change.
But then both qjackctl and Ardour report 48000 as the samplerate.
All help is appreciated.
Link
--
e-mail is . . .
3:29 p.m.
On Tue, 2006-06-20 at 10:24 -0700, Mark Knecht wrote:
Many built-in/inexpensive sound cards are stuck at
48K. Possibly this
one is also?
It's still a bug for JACK not to report any error.
Does aplay report any errors with a 44100Hz file?
- Mark
On 6/20/06, Link Swanson <link(a)sumerianbabyl.com> wrote:
After removing my Multiface II and switching back
to my nVidia onboard
audio, qjackctl will not run at 44100. I can set it in the setup window
and it reports starting 44100 in the messages:
11:07:46.232 Patchbay deactivated.
11:07:46.322 Statistics reset.
11:07:46.498 MIDI connection graph change.
11:07:46.528 MIDI connection change.
11:07:47.580 Startup script...
11:07:47.580 artsshell -q terminate
11:07:47.861 Startup script terminated with exit status=256.
11:07:47.861 JACK is starting...
11:07:47.862 jackd -R -dalsa -dhw:1,0 -r44100 -p512 -n2 -S
11:07:47.870 JACK was started with PID=3071 (0xbff).
jackd 0.101.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
Enhanced3DNow! detected
SSE2 detected
apparent rate = 44100
creating alsa driver ... hw:1,0|hw:1,0|512|2|44100|0|0|nomon|swmeter|-|16bit
control device hw:1
configuring for 44100Hz, period = 512 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
11:07:49.953 Server configuration saved to "/home/bozone/.jackdrc".
11:07:49.954 Statistics reset.
11:07:49.979 Client activated.
11:07:49.980 Audio connection change.
11:07:49.981 Audio connection graph change.
Enhanced3DNow! detected
SSE2 detected
11:10:21.095 MIDI connection graph change.
11:10:21.123 Audio connection graph change.
11:10:26.482 Audio connection graph change.
11:10:26.504 MIDI connection graph change.
But then both qjackctl and Ardour report 48000 as the samplerate.
All help is appreciated.
Link
--
e-mail is . . .
4:27 p.m.
On Tue, 20 Jun 2006 13:29:18 -0400
Lee Revell <rlrevell(a)joe-job.com> wrote:
On Tue, 2006-06-20 at 10:24 -0700, Mark Knecht wrote:
Hmm, is this it:
Index: drivers/alsa/alsa_driver.c
===================================================================
--- drivers/alsa/alsa_driver.c (revision 976)
+++ drivers/alsa/alsa_driver.c (working copy)
@@ -445,13 +445,13 @@
frame_rate = driver->frame_rate ;
err = snd_pcm_hw_params_set_rate_near (handle, hw_params,
&frame_rate, NULL) ;
- driver->frame_rate = frame_rate ;
- if (err < 0) {
+ if (err < 0 || (driver->frame_rate != frame_rate)) {
jack_error ("ALSA: cannot set sample/frame rate to %"
PRIu32 " for %s", driver->frame_rate,
stream_name);
return -1;
}
+ driver->frame_rate = frame_rate ;
if (!*nchns) {
/*if not user-specified, try to find the maximum
* number of channels */
--
Palimm Palimm!
http://tapas.affenbande.org
Many built-in/inexpensive sound cards are stuck
at 48K. Possibly this
one is also?
It's still a bug for JACK not to report any error.
Does aplay report any errors with a 44100Hz file? 
4:37 p.m.
New subject: [Jackit-devel] [linux-audio-user] JACK samplerate stuck at 48000
On Tue, 2006-06-20 at 20:27 +0200, Florian Paul Schmidt wrote:
On Tue, 20 Jun 2006 13:29:18 -0400
Lee Revell <rlrevell(a)joe-job.com> wrote:
no, that doesn't work.
the lack of any "retval != requested_val" test was changed a year or two
back, on purpose. if we want to test this, the test has to be flexible:
some h/w will report as real rate of 44099 rather than 44100.
On Tue, 2006-06-20 at 10:24 -0700, Mark Knecht
wrote:
Hmm, is this it:
Index: drivers/alsa/alsa_driver.c
===================================================================
--- drivers/alsa/alsa_driver.c (revision 976)
+++ drivers/alsa/alsa_driver.c (working copy)
@@ -445,13 +445,13 @@
frame_rate = driver->frame_rate ;
err = snd_pcm_hw_params_set_rate_near (handle, hw_params,
&frame_rate, NULL) ;
- driver->frame_rate = frame_rate ;
- if (err < 0) {
+ if (err < 0 || (driver->frame_rate != frame_rate)) { Many built-in/inexpensive sound cards are stuck
at 48K. Possibly this
one is also?
It's still a bug for JACK not to report any error.
Does aplay report any errors with a 44100Hz file? 
10:10 p.m.
New subject: [Jackit-devel] [linux-audio-user] JACK samplerate stuck at 48000
Paul Davis wrote:
On Tue, 2006-06-20 at 20:27 +0200, Florian Paul Schmidt
wrote:
Wouldn't be ok to have:
+ if (err < 0 || ( abs(driver->frame_rate - frame_rate) < 10 )) {
The fact that jack didn't report that he couldn't set a choosen rate caused a bit
of an headache to me too when I tried it for the first time on my laptop.
c.
--
www.cesaremarilungo.com
On Tue, 20 Jun 2006 13:29:18 -0400
Lee Revell <rlrevell(a)joe-job.com> wrote:
no, that doesn't work.
the lack of any "retval != requested_val" test was changed a year or two
back, on purpose. if we want to test this, the test has to be flexible:
some h/w will report as real rate of 44099 rather than 44100.
On Tue, 2006-06-20 at 10:24 -0700, Mark Knecht
wrote:
Hmm, is this it:
Index: drivers/alsa/alsa_driver.c
===================================================================
--- drivers/alsa/alsa_driver.c (revision 976)
+++ drivers/alsa/alsa_driver.c (working copy)
@@ -445,13 +445,13 @@
frame_rate = driver->frame_rate ;
err = snd_pcm_hw_params_set_rate_near (handle, hw_params,
&frame_rate, NULL) ;
- driver->frame_rate = frame_rate ;
- if (err < 0) {
+ if (err < 0 || (driver->frame_rate != frame_rate)) {
Many built-in/inexpensive sound cards are stuck at
48K. Possibly this
one is also?
It's still a bug for JACK not to report any error.
Does aplay report any errors with a 44100Hz file?
10:01 p.m.
Lee Revell wrote:
--
www.cesaremarilungo.com
On Tue, 2006-06-20 at 10:24 -0700, Mark Knecht wrote:
In fact it happens on my laptop (it has a VIA AC97 chip). Jack does
report the sample rate you choose but the other applications connect to
it at 48000Hz.
I guess it is because they're designed to play dvds (which are at
48000Hz) and they don't have a built-in sample rate converter. Maybe
JACK assumes they always have one since it is designed for high end cards?
Many built-in/inexpensive sound cards are stuck at
48K. Possibly this
one is also?
It's still a bug for JACK not to report any error.
Does aplay report any errors with a 44100Hz file?
- Mark
On 6/20/06, Link Swanson <link(a)sumerianbabyl.com> wrote:
>After removing my Multiface II and switching back to my nVidia onboard
>audio, qjackctl will not run at 44100. I can set it in the setup window
>and it reports starting 44100 in the messages:
>
>11:07:46.232 Patchbay deactivated.
>11:07:46.322 Statistics reset.
>11:07:46.498 MIDI connection graph change.
>11:07:46.528 MIDI connection change.
>11:07:47.580 Startup script...
>11:07:47.580 artsshell -q terminate
>11:07:47.861 Startup script terminated with exit status=256.
>11:07:47.861 JACK is starting...
>11:07:47.862 jackd -R -dalsa -dhw:1,0 -r44100 -p512 -n2 -S
>11:07:47.870 JACK was started with PID=3071 (0xbff).
>jackd 0.101.0
>Copyright 2001-2005 Paul Davis and others.
>jackd comes with ABSOLUTELY NO WARRANTY
>This is free software, and you are welcome to redistribute it
>under certain conditions; see the file COPYING for details
>JACK compiled with System V SHM support.
>loading driver ..
>Enhanced3DNow! detected
>SSE2 detected
>apparent rate = 44100
>creating alsa driver ... hw:1,0|hw:1,0|512|2|44100|0|0|nomon|swmeter|-|16bit
>control device hw:1
>configuring for 44100Hz, period = 512 frames, buffer = 2 periods
>nperiods = 2 for capture
>nperiods = 2 for playback
>11:07:49.953 Server configuration saved to "/home/bozone/.jackdrc".
>11:07:49.954 Statistics reset.
>11:07:49.979 Client activated.
>11:07:49.980 Audio connection change.
>11:07:49.981 Audio connection graph change.
>Enhanced3DNow! detected
>SSE2 detected
>11:10:21.095 MIDI connection graph change.
>11:10:21.123 Audio connection graph change.
>11:10:26.482 Audio connection graph change.
>11:10:26.504 MIDI connection graph change.
>
>But then both qjackctl and Ardour report 48000 as the samplerate.
>
>All help is appreciated.
>
>Link
>
>
>--
>e-mail is . . .
>
>
>
10:14 p.m.
On Wed, 2006-06-21 at 02:02 +0000, Cesare Marilungo wrote:
Lee Revell wrote:
I think cards defaulted to 48000Hz before DVDs existed. I believe the
AC97 spec requires it and it's cheapest to support a single sample rate
and rely on a software sample rate converter for everything else.
Lee
On Tue, 2006-06-20 at 10:24 -0700, Mark Knecht
wrote:
In fact it happens on my laptop (it has a VIA AC97 chip). Jack does
report the sample rate you choose but the other applications connect to
it at 48000Hz.
I guess it is because they're designed to play dvds (which are at
48000Hz) and they don't have a built-in sample rate converter. Maybe
JACK assumes they always have one since it is designed for high end cards?
Many built-in/inexpensive sound cards are stuck at
48K. Possibly this
one is also?
It's still a bug for JACK not to report any error.
Does aplay report any errors with a 44100Hz file?
- Mark
On 6/20/06, Link Swanson <link(a)sumerianbabyl.com> wrote:
>After removing my Multiface II and switching back to my nVidia onboard
>audio, qjackctl will not run at 44100. I can set it in the setup window
>and it reports starting 44100 in the messages:
>
>11:07:46.232 Patchbay deactivated.
>11:07:46.322 Statistics reset.
>11:07:46.498 MIDI connection graph change.
>11:07:46.528 MIDI connection change.
>11:07:47.580 Startup script...
>11:07:47.580 artsshell -q terminate
>11:07:47.861 Startup script terminated with exit status=256.
>11:07:47.861 JACK is starting...
>11:07:47.862 jackd -R -dalsa -dhw:1,0 -r44100 -p512 -n2 -S
>11:07:47.870 JACK was started with PID=3071 (0xbff).
>jackd 0.101.0
>Copyright 2001-2005 Paul Davis and others.
>jackd comes with ABSOLUTELY NO WARRANTY
>This is free software, and you are welcome to redistribute it
>under certain conditions; see the file COPYING for details
>JACK compiled with System V SHM support.
>loading driver ..
>Enhanced3DNow! detected
>SSE2 detected
>apparent rate = 44100
>creating alsa driver ... hw:1,0|hw:1,0|512|2|44100|0|0|nomon|swmeter|-|16bit
>control device hw:1
>configuring for 44100Hz, period = 512 frames, buffer = 2 periods
>nperiods = 2 for capture
>nperiods = 2 for playback
>11:07:49.953 Server configuration saved to "/home/bozone/.jackdrc".
>11:07:49.954 Statistics reset.
>11:07:49.979 Client activated.
>11:07:49.980 Audio connection change.
>11:07:49.981 Audio connection graph change.
>Enhanced3DNow! detected
>SSE2 detected
>11:10:21.095 MIDI connection graph change.
>11:10:21.123 Audio connection graph change.
>11:10:26.482 Audio connection graph change.
>11:10:26.504 MIDI connection graph change.
>
>But then both qjackctl and Ardour report 48000 as the samplerate.
>
>All help is appreciated.
>
>Link
>
>
>--
>e-mail is . . .
>
>
>
10:35 p.m.
Lee Revell wrote:
--
www.cesaremarilungo.com
On Wed, 2006-06-21 at 02:02 +0000, Cesare Marilungo
wrote:
Not all. On my desktop pc (which has a VIA 8237, an AC97 based card -
the mb is a ASUS K8V-X) jack lets me choose both sample rates.
c.
Lee Revell wrote:
I think cards defaulted to 48000Hz before DVDs existed. I believe the
AC97 spec requires it and it's cheapest to support a single sample rate
and rely on a software sample rate converter for everything else.
Lee
On Tue, 2006-06-20 at 10:24 -0700, Mark Knecht
wrote:
In fact it happens on my laptop (it has a VIA AC97 chip). Jack does
report the sample rate you choose but the other applications connect to
it at 48000Hz.
I guess it is because they're designed to play dvds (which are at
48000Hz) and they don't have a built-in sample rate converter. Maybe
JACK assumes they always have one since it is designed for high end cards?
Many built-in/inexpensive sound cards are stuck at
48K. Possibly this
one is also?
It's still a bug for JACK not to report any error.
Does aplay report any errors with a 44100Hz file?
- Mark
On 6/20/06, Link Swanson <link(a)sumerianbabyl.com> wrote:
>After removing my Multiface II and switching back to my nVidia onboard
>audio, qjackctl will not run at 44100. I can set it in the setup window
>and it reports starting 44100 in the messages:
>
>11:07:46.232 Patchbay deactivated.
>11:07:46.322 Statistics reset.
>11:07:46.498 MIDI connection graph change.
>11:07:46.528 MIDI connection change.
>11:07:47.580 Startup script...
>11:07:47.580 artsshell -q terminate
>11:07:47.861 Startup script terminated with exit status=256.
>11:07:47.861 JACK is starting...
>11:07:47.862 jackd -R -dalsa -dhw:1,0 -r44100 -p512 -n2 -S
>11:07:47.870 JACK was started with PID=3071 (0xbff).
>jackd 0.101.0
>Copyright 2001-2005 Paul Davis and others.
>jackd comes with ABSOLUTELY NO WARRANTY
>This is free software, and you are welcome to redistribute it
>under certain conditions; see the file COPYING for details
>JACK compiled with System V SHM support.
>loading driver ..
>Enhanced3DNow! detected
>SSE2 detected
>apparent rate = 44100
>creating alsa driver ... hw:1,0|hw:1,0|512|2|44100|0|0|nomon|swmeter|-|16bit
>control device hw:1
>configuring for 44100Hz, period = 512 frames, buffer = 2 periods
>nperiods = 2 for capture
>nperiods = 2 for playback
>11:07:49.953 Server configuration saved to "/home/bozone/.jackdrc".
>11:07:49.954 Statistics reset.
>11:07:49.979 Client activated.
>11:07:49.980 Audio connection change.
>11:07:49.981 Audio connection graph change.
>Enhanced3DNow! detected
>SSE2 detected
>11:10:21.095 MIDI connection graph change.
>11:10:21.123 Audio connection graph change.
>11:10:26.482 Audio connection graph change.
>11:10:26.504 MIDI connection graph change.
>
>But then both qjackctl and Ardour report 48000 as the samplerate.
>
>All help is appreciated.
>
>Link
>
>
>--
>e-mail is . . .
>
>
>
>
>
10:45 p.m.
On Wed, 2006-06-21 at 02:35 +0000, Cesare Marilungo wrote:
Yeah, some VIA chipsets have a hardware sample rate converter. But it's
getting less and less common. And a hardware SRC is almost never as
good as the best software SRCs.
IMHO it's best to run JACK at the highest sample rate your hardware
supports then downsample with a high quality software SRC if your target
sample rate is 44.1Khz.
Lee
I think cards
defaulted to 48000Hz before DVDs existed. I believe
the
AC97 spec requires it and it's cheapest to
support a single sample
rate
and rely on a software sample rate converter for
everything else.
Lee
Not all. On my desktop pc (which has a VIA 8237, an AC97 based card -
the mb is a ASUS K8V-X) jack lets me choose both sample rates. 
10:47 p.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
I've been doing some Mastering work stuck at 44100 and have been using
ecasound combined with the .asoundrc jackplug extension as well as the
jack dummy driver to get some rudimentary support for Jack sample rate
conversion.
Of course it would be nice for Jack to do this by itself and simply
display a warning.
Carlo
10:53 p.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
On Wed, 2006-06-21 at 02:46 +0200, Carlo Capocasa wrote:
I've been doing some Mastering work stuck at 44100
and have been using
ecasound combined with the .asoundrc jackplug extension as well as the
jack dummy driver to get some rudimentary support for Jack sample rate
conversion.
Of course it would be nice for Jack to do this by itself and simply
display a warning.
You can do it already, just run JACK with a plughw device rather than
hw.
But, why do you want this? You'll get better results running at a
hardware supported sample rate then resampling at the end.
Lee
10:59 p.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
You can do it already, just run JACK with a plughw
device rather than
hw.
Cool!
But, why do you want this? You'll get better results running at a
hardware supported sample rate then resampling at the end.
I have sources that were recorded at 48kHz. I figured that if I
downsampled before mastering the processing would possibly obscure the
conversion noise for the finished product (CD), at the cost of having
conversion noise during monitoring.
Thanks for the tip!
Carlo
11:05 p.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
On Wed, 2006-06-21 at 02:58 +0200, Carlo Capocasa wrote:
Maybe not so cool - the ALSA sample rate converter is definitely not
high quality. It's designed to be fast. Good for desktop stuff but not
so good for pro audio.
You have a soundcard that can't do 48KHz in hardware? That's unusual.
Lee
You can do it
already, just run JACK with a plughw device rather than
hw.
Cool!
But, why do you want this? You'll get better results running at a
hardware supported sample rate then resampling at the end.
I have sources that were recorded at 48kHz. I figured that if I
downsampled before mastering the processing would possibly obscure the
conversion noise for the finished product (CD), at the cost of having
conversion noise during monitoring.
11:16 p.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
I have one of the usual consumer cards that will only support 48kHz. I
want to master 44.1kHz audio using Jack and Jamin, and for this I need
to run Jack at 44.1kHz. I also need some way to monitor (ie upsample to
48kHz and output through ALSA), but this need not be high quality since
I will be testing on other equipment as well.
Carlo
11:29 p.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
On Wed, 2006-06-21 at 03:16 +0200, Carlo Capocasa wrote:
I have one of the usual consumer cards that will only
support 48kHz. I
want to master 44.1kHz audio using Jack and Jamin, and for this I need
to run Jack at 44.1kHz. I also need some way to monitor (ie upsample to
48kHz and output through ALSA), but this need not be high quality since
I will be testing on other equipment as well.
Why don't you just master at 48Khz then resample at the end? I think
you'll get better quality this way than using the ALSA SRC.
Lee
11:41 p.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
Why don't you just master at 48Khz then resample
at the end? I think
you'll get better quality this way than using the ALSA SRC.
mastering with an onboard consumer card that only supports 16bit/48khz? no thanks :)
11:51 p.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
On Wed, 2006-06-21 at 01:41 +0000, carmen wrote:
Mastering at 16 bit/48Khz was the norm for the first 15 years or so of
digital audio, and those CDs sound fine to me.
Lee
Why don't
you just master at 48Khz then resample at the end? I think
you'll get better quality this way than using the ALSA SRC.
mastering with an onboard consumer card that only supports 16bit/48khz? no thanks :)
7:55 a.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
Again, the ALSA conversion process is not in the final product, only in
the monitoring, which is fine since I will be testing on other devices
anyway. I figured downsampling after mixdown before mastering would give
me better quality since compression and equalization would compensate
for downsampling noise. This is only a hypothesis though, which I am
testing now.
Carlo
11:28 p.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
On Wed, 2006-06-21 at 03:01 +0200, Carlo Capocasa wrote:
That should be enough. I don't know why it would not work. Something
must have been changed recently. I would report it on the JACK list.
Lee
You can do it
already, just run JACK with a plughw device rather than
hw.
Just running plughw:0 won't let me select 44.1kHz. Can you be more
specific on what needs to be done?
10:38 a.m.
New subject: [linux-audio-user] Re: JACK samplerate stuck at 48000
Update:
Setting jack to playback only mode re-sets the sampling rate to 48000,
while duplex mode renders the following error message:
ALSA: cannot set period size to 128 frames for capture
ALSA: cannot configure capture channel
Complete output:
jackd 0.100.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ...
plughw:0|plughw:0|128|2|44100|2|2|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 128 frames, buffer = 2 periods
ALSA: cannot set period size to 128 frames for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
no message buffer overruns
Carlo
6547
days inactive
6548
days old
linux-audio-user@lists.linuxaudio.org
23 comments
8 participants
participants (8)
-
Carlo Capocasa -
carmen -
Cesare Marilungo -
Florian Paul Schmidt -
Lee Revell -
Link Swanson -
Mark Knecht -
Paul Davis