2 Oct
2003
2 Oct
'03
3:14 a.m.
Hello again - I hope this is the right list for this topic (so far I can only
get subscribed to two and I keep bouncing back and forth between them...)
first off, may I say thank you to the list members for bearing me, and extra
thank you still to those who take the time to respond - amazing gentlemen and
ladies you all are; I realize I have written what amounts to several novels
worth of emails in the past couple weeks! :)
well I started a couple threads earlier about strangeness (or what I think was
strangeness) with compiling and installing hdspmixer and such...the questions
I had I didn't figure out, but somehow hdspmixer was able to run - whether
it's ACTUALLY working, I don't know for sure sure...
THAT having been said,
I only know of a couple people who are using the HDSP 9652, along with a
couple who've developed for it - Mark K, Thomas, Kevin, et al - does any of
this sound familiar? :
--
a) I've been doing a lot of back and forth and reading but I'm a bit confused
as to what hdspmixer is DOING (which makes it harder to tell if it's working
:) )
b) my goal, as I may have said on other threads, is to be running ardour with
my HDSP 9652, sending each of 24 individual adat optical channels out to 1
channel input in my behringer ddx3216 (outfitted with adat i/o). An earlier
thread I started was solved by me adding -d hw:0 to my jackd command line
(duh), where I wasn't seeing 24 (actually 26) possible outputs when I clicked
on "output" in the mixer in ardour
now I'm able to see the outputs, and assign them as they should be, meanwhile
in hdspmixer i've picked the preset which assigns ins, out and "playback"
(what would be the difference between "out" and "playback" I wonder)
to adat
outputs, etc:
--
first I used hdspconf to change the HDSP to 44.1 for purposes of these tests
next I ran hdspmixer
I kept hdspmixer running, then started jack from a terminal using:
su
jackd -R -d alsa -d hw:0 -r 44100 -p 2048
then started ardour from a terminal:
su
ardour -n <--- that's so no splash screen will appear
but what was showing up at the board wasn't what I was expecting *laugh* if I
routed a track to channel 1, then it showd up a 3 db too quiet at channel 1
on the mixer, and at the right volume on channel 2 (I was using a -12 1khz
test tone that I generated with the board and was able to record to ardour -
ardour indeed is playing it at -12.1 - I think the point 1 is explanable but
I'll skip that 'cause it doesn't matter just now) if I routed the track to
channel 2, it didn't show up anywhere. odd numbered tracks after that seemed
to be showing up on 1-2 just like 1 did (although I can't confirm the
consistancy of this)
I experimented with opening up qjackconnect, which was the only one of the
many patch bay programs from planet that showed 24 capture and playback
channels and connecting captures to playbacks. this didn't seem to do
anything, which made me wonder just what qjackconnect was for.
then I closed all, closed the hdspmixer program, and started just jack and
ardour. the results from that are:
routed to channel 1, it shows up at channel 1, 3 db quiet, channels 3, 7, 9,
11, 17, 19 and 23 at 30 db quiet and channels 5, 13 and 21 at 12 dbs quiet -
wha?
routed to channel 2, it shows up only at channel 2! 3 dbs under - actually,
this 3 dbs may be a non-problem issue in the board, so possibly it can be
ignored
routed to channel 3, it shows up on 1, 2, 3 and 4 and some other channels at
half volume - wha wha?
channel 4, nothing
channel 5 --> 4, 5, 6 and others
ok you get the picture. randomness. a weird mess.
I don't know if this is a driver problem, a HDSP 9652/alsa driver patch
problem, an hdspmixer problem (I did, as I mentioned, have oddities on
compiling that program), a jack issue, an alsa issue, a bug in ardour, a bug
in alsa drivers, etc. etc. etc.
I only know of a couple people who are using the HDSP 9652 - Mark K, does any
of this sound familiar?
clearly there are thousands of details - anyone who wants to talk about this
and wants other info, as usual, ask and ye shall receive :) (although in
some cases, a request for details may yield first the question "how do I find
that?" :) )
thanks and I hope this is interesting and stimulating, maybe even
educational!!! :)
--
--------------
Aaron Trumm
NQuit
www.nquit.com
--------------
2 Oct
2 Oct
9:11 a.m.
On Wed, 2003-10-01 at 22:04, Aaron Trumm wrote:
<SNIP>
--
a) I've been doing a lot of back and forth and reading but I'm a bit confused
as to what hdspmixer is DOING (which makes it harder to tell if it's working
:) )
hdspmixer is taking each and every one of the 52 inputs (26 ADAT
channels and 26 software channels) and it is 'mixing' them to each and
every one of the 26 output channels. It is capable of setting an routing
volume for each path separately. (Which could have something to do with
your -3db thing)
Whether a specific input is routed to a specific output is made visible
when you click on the black square below a name like In 1 where it
probably says A1 1+2 on your setup if you're running default conditions.
You'll get a list of outputs. Any output with a check mark has some
amount of this inputs signal routed to that output.
but what was showing up at the board wasn't what I was expecting *laugh* if I
routed a track to channel 1, then it showd up a 3 db too quiet at channel 1
on the mixer, and at the right volume on channel 2 (I was using a -12 1khz
test tone that I generated with the board and was able to record to ardour -
ardour indeed is playing it at -12.1 - I think the point 1 is explanable but
I'll skip that 'cause it doesn't matter just now) if I routed the track to
channel 2, it didn't show up anywhere. odd numbered tracks after that seemed
to be showing up on 1-2 just like 1 did (although I can't confirm the
consistancy of this)
I think I maybe did see something like this with older versions of
hdspmixer.
I experimented with opening up qjackconnect, which was the only one of the
many patch bay programs from planet that showed 24 capture and playback
channels and connecting captures to playbacks. this didn't seem to do
anything, which made me wonder just what qjackconnect was for.
then I closed all, closed the hdspmixer program, and started just jack and
ardour. the results from that are:
routed to channel 1, it shows up at channel 1, 3 db quiet, channels 3, 7, 9,
11, 17, 19 and 23 at 30 db quiet and channels 5, 13 and 21 at 12 dbs quiet -
wha?
OK, so now I need to ask what you mean by 'channels'. There are three
'channel 1's ' in hdspmixer - In 1, Out 1 and A1 1. Are you seeing this
audio on Out 1 when Ardour plays audio? Do you see Out 1 audio making it
to A1 1?
routed to channel 2, it shows up only at channel 2! 3 dbs under - actually,
this 3 dbs may be a non-problem issue in the board, so possibly it can be
ignored
routed to channel 3, it shows up on 1, 2, 3 and 4 and some other channels at
half volume - wha wha?
channel 4, nothing
channel 5 --> 4, 5, 6 and others
ok you get the picture. randomness. a weird mess.
This sounds like you're possibly not running hdspmixer 1.3. In an xterm
type 'which hdspmixer'. IF you get /usr/bin/hdspmixer, I think you have
the wrong one. IF you get usr/local/bin/hdspmixer then you are probably
OK.
In any case, unless you did something special when you did the
./configure step I think the new one (at least on my system is in
/usr/local/bin, so make sure you are running that.
Provide an lspci output so we can see that you've got the right
firmware.
Provide the output of 'cat /proc/asound/card0/hdsp '. If you see 2
status and two control registers then you have at least partially the
new driver. (I think) If you don't, then something is definitely a bit
off.
<SNIP>
I only know of a couple people who are using the HDSP 9652 - Mark K, does any
of this sound familiar?
It does actually. I mostly think that if you are doing things right with
the tools them you are still running the wrong software somewhere.
Probably your hdsp.o file isn't the right one is my guess, but we'll
just have to find out.
Good luck,
Mark
1:38 p.m.
Whether a specific input is routed to a specific
output is made visible
when you click on the black square below a name like In 1 where it
probably says A1 1+2 on your setup if you're running default conditions.
You'll get a list of outputs. Any output with a check mark has some
amount of this inputs signal routed to that output.
hmmm - this makes me think to go check if things aren't routed to multiple
places
OK, so now I need to ask what you mean by
'channels'. There are three
'channel 1's ' in hdspmixer - In 1, Out 1 and A1 1. Are you seeing this
audio on Out 1 when Ardour plays audio? Do you see Out 1 audio making it
to A1 1?
ahh - to clarify (if I can!) - when I'm referring to channel/track 1 on
ardour, that's in ardour, of course, and then when I say it shows up at
channel 1 on the board, that's on my digital mixer - not on hdspmixer -
during the tests where hdspmixer was running, I wasn't looking at it, partly
because I'm a dolt, partly because it didn't matter to me for some reason,
and partly because I believe in my make, the part that was broken was
metering, so I'm not sure I would've been able to see the signal (this is
something that I just remembered upon waking up this morning)
of course, I also did a bunch of testing with hdspmixer not running
This sounds like you're possibly not running
hdspmixer 1.3. In an xterm
type 'which hdspmixer'. IF you get /usr/bin/hdspmixer, I think you have
the wrong one. IF you get usr/local/bin/hdspmixer then you are probably
OK.
huh. duh. I didn't think of that. I assumed I had no copy of hdspmixer
before I downloaded your 1.3 tarball. perhaps 1.3 never did install, and I
had 1.1, and that's what I'm running. thanks :) (remember I had unclean
making going on when I was compiling and installing)
Provide an lspci output so we can see that you've
got the right
firmware.
firmware rev 65 - I'll go get an lspci later to confirm
Provide the output of 'cat /proc/asound/card0/hdsp
'. If you see 2
status and two control registers then you have at least partially the
new driver. (I think) If you don't, then something is definitely a bit
off.
*nod*
It does actually. I mostly think that if you are doing
things right with
the tools them you are still running the wrong software somewhere.
Probably your hdsp.o file isn't the right one is my guess, but we'll
just have to find out.
*nod* ok this is good info - thanks :) I'll be back atcha with a report in
a while...
1:41 p.m.
a ps to this - I may need to clean out all versions of hdspmixer and start
over with 1.3 - can somebody give me a low down on how to make sure I've got
everything cleaned out? rpm makes this so easy that I have yet to be
confident when I'm not using rpm...
---------------------------------------------------------------
Houston Poetry Slam Team
www.houstonpoetryslam.com
NQuit Records
www.nquit.com
---------------------------------------------------------------
----- Original Message -----
From: "Mark Knecht" <markknecht(a)comcast.net>
To: "Linux-Audio-User" <linux-audio-user(a)music.columbia.edu>
Sent: Thursday, October 02, 2003 5:55 AM
Subject: Re: [linux-audio-user] more about HDSP 9652/jack/ardour/hdspmixer
if I
the
actually,
does any
On Wed, 2003-10-01 at 22:04, Aaron Trumm wrote:
<SNIP>
> --
> a) I've been doing a lot of back and forth and reading but I'm a bit
confused
> as to what hdspmixer is DOING (which makes it
harder to tell if it's
working
:) )
hdspmixer is taking each and every one of the 52 inputs (26 ADAT
channels and 26 software channels) and it is 'mixing' them to each and
every one of the 26 output channels. It is capable of setting an routing
volume for each path separately. (Which could have something to do with
your -3db thing)
Whether a specific input is routed to a specific output is made visible
when you click on the black square below a name like In 1 where it
probably says A1 1+2 on your setup if you're running default conditions.
You'll get a list of outputs. Any output with a check mark has some
amount of this inputs signal routed to that output.
>
> but what was showing up at the board wasn't what I was expecting *laugh*
> routed a track to channel 1, then it showd up a 3
db too quiet at
channel 1
> on the mixer, and at the right volume on channel
2 (I was using a -12
1khz
> test tone that I generated with the board and was
able to record to
ardour -
> ardour indeed is playing it at -12.1 - I think
the point 1 is explanable
but
> I'll skip that 'cause it doesn't
matter just now) if I routed the
track to
> channel 2, it didn't show up anywhere. odd
numbered tracks after that
seemed
to be showing
up on 1-2 just like 1 did (although I can't confirm the
consistancy of this)
I think I maybe did see something like this with older versions of
hdspmixer.
>
> I experimented with opening up qjackconnect, which was the only one of > many patch bay programs from planet that showed
24 capture and playback
> channels and connecting captures to playbacks. this didn't seem to do
> anything, which made me wonder just what qjackconnect was for.
>
> then I closed all, closed the hdspmixer program, and started just jack
and
> ardour. the results from that are:
>
> routed to channel 1, it shows up at channel 1, 3 db quiet, channels 3,
7, 9,
> 11, 17, 19 and 23 at 30 db quiet and channels 5,
13 and 21 at 12 dbs
quiet -
wha?
OK, so now I need to ask what you mean by 'channels'. There are three
'channel 1's ' in hdspmixer - In 1, Out 1 and A1 1. Are you seeing this
audio on Out 1 when Ardour plays audio? Do you see Out 1 audio making it
to A1 1?
>
> routed to channel 2, it shows up only at channel 2! 3 dbs under - > this 3 dbs may be a non-problem issue in the
board, so possibly it can
be
> ignored
>
> routed to channel 3, it shows up on 1, 2, 3 and 4 and some other
channels at
half volume -
wha wha?
channel 4, nothing
channel 5 --> 4, 5, 6 and others
ok you get the picture. randomness. a weird mess.
This sounds like you're possibly not running hdspmixer 1.3. In an xterm
type 'which hdspmixer'. IF you get /usr/bin/hdspmixer, I think you have
the wrong one. IF you get usr/local/bin/hdspmixer then you are probably
OK.
In any case, unless you did something special when you did the
./configure step I think the new one (at least on my system is in
/usr/local/bin, so make sure you are running that.
Provide an lspci output so we can see that you've got the right
firmware.
Provide the output of 'cat /proc/asound/card0/hdsp '. If you see 2
status and two control registers then you have at least partially the
new driver. (I think) If you don't, then something is definitely a bit
off.
<SNIP>
>
> I only know of a couple people who are using the HDSP 9652 - Mark K, of this sound
familiar?
It does actually. I mostly think that if you are doing things right with
the tools them you are still running the wrong software somewhere.
Probably your hdsp.o file isn't the right one is my guess, but we'll
just have to find out.
Good luck,
Mark
2:11 p.m.
Aaron Trumm wrote:
a ps to this - I may need to clean out all versions of
hdspmixer and start
over with 1.3 - can somebody give me a low down on how to make sure I've got
everything cleaned out? rpm makes this so easy that I have yet to be
confident when I'm not using rpm...
Basically check /usr/lib /usr/include /usr/bin usr/local/lib
/usr/local/include /usr/local/bin
for files that belong to the package.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
2:20 p.m.
On Thursday 02 October 2003 09:29, Patrick Shirkey wrote:
Aaron Trumm wrote:
*nod*
--
--------------
Aaron Trumm
NQuit
www.nquit.com
--------------
a ps to this - I may need to clean out all
versions of hdspmixer and
start over with 1.3 - can somebody give me a low down on how to make sure
I've got everything cleaned out? rpm makes this so easy that I have yet
to be confident when I'm not using rpm...
Basically check /usr/lib /usr/include /usr/bin usr/local/lib
/usr/local/include /usr/local/bin
for files that belong to the package.
2:30 p.m.
New subject: [linux-audio-user] REPORT HDSP 9652/jack/ardour/hdspmixer
ok Mark (and others) -
reporting - lspci:
00:0c.0 Multimedia audio controller: Xilinx Corporation RME Hammerfall DSP
(rev 65)
which hdspmixer:
/usr/bin/hdspmixer
checked /usr/local/bin and no hdspmixer in there
cat /proc/asound/card0/hdsp:
RME Hammerfall HDSP 9652 (Card #1)
Buffers: capture dde00000 playback ddc00000
IRQ: 11 Registers bus: 0xe7000000 VM: 0xe097f000
Control register: 0x1008098
Control2 register: 0x800
Status register: 0x207000e
Status2 register: 0xffff8041
FIFO status: 0
MIDI1 Output status: 0xffffff00
MIDI1 Input status: 0xffffff00
MIDI2 Output status: 0xffffff00
MIDI2 Input status: 0xffffff00
<SNIP>
2 status and control registers
hmmmmmm guess I was using old hdspmixer...
--
--------------
Aaron Trumm
NQuit
www.nquit.com
--------------
3:06 p.m.
New subject: [linux-audio-user] REPORT HDSP 9652/jack/ardour/hdspmixer
reporting - lspci:
00:0c.0 Multimedia audio controller: Xilinx Corporation RME
Hammerfall DSP
(rev 65)
Looks good.
which hdspmixer:
/usr/bin/hdspmixer
Old version, probably.
checked /usr/local/bin and no hdspmixer in there
cat /proc/asound/card0/hdsp:
RME Hammerfall HDSP 9652 (Card #1)
Buffers: capture dde00000 playback ddc00000
IRQ: 11 Registers bus: 0xe7000000 VM: 0xe097f000
Control register: 0x1008098
Control2 register: 0x800
Status register: 0x207000e
Status2 register: 0xffff8041
FIFO status: 0
MIDI1 Output status: 0xffffff00
MIDI1 Input status: 0xffffff00
MIDI2 Output status: 0xffffff00
MIDI2 Input status: 0xffffff00
<SNIP>
2 status and control registers
Looks good
hmmmmmm guess I was using old hdspmixer...
/ls /usr/local/bin
is hdspmixer there?
/usr/local/bin/hdspmixer
to run version 1.3, or put /usr/local/bin at the front of your path
settings.
- Mark
3:22 p.m.
New subject: [linux-audio-user] REPORT HDSP 9652/jack/ardour/hdspmixer
is hdspmixer there?
nope
near as I can tell, it's not compiling correctly...I get this when I make:
Making all in src
make[1]: Entering directory `/home/aaron/hdspmixer/hdspmixer-1.3/src'
c++ -DPACKAGE=\"hdspmixer\" -DVERSION=\"1.3\" -DSTDC_HEADERS=1 -I.
-I.
-O2 -g -pipe -march=i386 -mcpu=i686 -I/usr/X11R6/include -fno-exceptions -c
hdspmixer.cxx
hdspmixer.cxx: In function `int main(int, char**)':
hdspmixer.cxx:80: `fl_open_display' undeclared (first use this function)
hdspmixer.cxx:80: (Each undeclared identifier is reported only once for each
function it appears in.)
make[1]: *** [hdspmixer.o] Error 1
make[1]: Leaving directory `/home/aaron/hdspmixer/hdspmixer-1.3/src'
make: *** [all-recursive] Error 1
--
--------------
Aaron Trumm
NQuit
www.nquit.com
--------------
3:46 p.m.
New subject: [linux-audio-user] REPORT HDSP 9652/jack/ardour/hdspmixer
is hdspmixer
there?
nope
near as I can tell, it's not compiling correctly...I get this when I make:
4:10 p.m.
New subject: [linux-audio-user] REPORT HDSP 9652/jack/ardour/hdspmixer
OK then do NOT run ANY version of hdspmixer as the
older versions will do
weird routing and mess up all your tests. You probably need to do a cold
boot or something to make sure you have everything back to default.
that'll be done next time I go in there, as I had to leave the studio for a
bit and power down :)
You need to do everything with amixer commands until
you get version 1.3
compiled correctly.
ok - we're on the same page on this - (whew! :) ) - I actually sometimes am
more comfortable on the command line and in code. I wouldn't mind
configuring on the command line and skipping hdpsmixer altogether. but I
too do like the flashing lights and pretty GUI sometimes :)
I'll just say this again for clarity. Do not run
ANY version of hdspmixer
OTHER THAN version 1.3 or the results are weird and the whole card acts
crazy. (Audio data gets written to control registers using version 1.2.
;-)
Crazy results! ;-)
Righto!
Fernando supplies alsa-tools, which is where I think
you got your 1.2
version, or whatever you are running. Maybe you can figure out from that
how
to get this built. On Gentoo it builds fine for me. I
haven't tried it on
Redhat.
yes
so summary
configure using amixer commands
get to work
get hdspmixer 1.3 to work
when I open it, expect to see it show up however I've configured the card
using amixer commands
that brings up question. if I am using amixer commands, skipping hdsp for a
moment, how am I going to test (without opening ardour)?
3:07 p.m.
New subject: [linux-audio-user] another report HDSP 9652/jack/ardour/hdspmixer
Another short addendum - I tried doing a bunch of:
amixer cset numid=5 27,0,32768
incrementing the first 2 numbers (27,0) so that it would route all the adat
outs -
that yielded the same results in ardour - I'm not even sure if Mark was sure
if this was the right wording for the amixer command
--
--------------
Aaron Trumm
NQuit
www.nquit.com
--------------
3:41 p.m.
New subject: [linux-audio-user] another report HDSP 9652/jack/ardour/hdspmixer
Another short addendum - I tried doing a bunch of:
amixer cset numid=5 27,0,32768
incrementing the first 2 numbers (27,0) so that it would route
all the adat
outs -
that yielded the same results in ardour - I'm not even sure if
Mark was sure
if this was the right wording for the amixer command
No, I think that wording was right, but maybe we need to do a bit of a reset
to better understand exactly where you are at this point, what's working,
what's not, and then figure out what to do.
(In the above example, since the hardware input group is 0-25, and the
software group (output from Ardour, input to HDSP 9652) is 26-51, I think
you are routing the second playback channel to the first ADAT output
channel. It works, but I'm not sure you meant to do that.
In other threads (not this one) I've mentioned that I made headway faster
with this card by focusing on input signals before output signals. On the
HDSP 9652 the 26 inputs you see in hdspmixer in the top line are the inputs.
Are those working correctly? Can you send data input each of those from your
mixer and see meters operating correctly on all 26 inputs? (Or only 24 if
you don't have some spdif equipment.)
I made a mistake wasting weeks trying to get sound out when it was never
going to work. When I shifted to inputs Thomas and I worked out most of the
bugs pretty quickly.
OK, so assuming you check the inputs, and that they all work, then can you
route hardware input audio using hdspmixer to a hardware output? If all 26
inputs do NOT work, then you still have a driver or hdspmixer issue we need
to solve.
Assuming you get an input signal routed to an output, then you should be
able to drive whatever ADAT device you have that will create sound and hear
what's going on.
Only AFTER all of that works would I bother with Ardour at all. When the
stuff above works perfectly, then it will take you very little time to get
Ardour working. If the above stuff doesn't work, Ardour doesn't have a
chance.
- Mark
4:05 p.m.
New subject: [linux-audio-user] another report HDSP 9652/jack/ardour/hdspmixer
(In the above example, since the hardware input group
is 0-25, and the
software group (output from Ardour, input to HDSP 9652) is 26-51, I think
you are routing the second playback channel to the first ADAT output
channel. It works, but I'm not sure you meant to do that.
I think I probably typo'd in the email, but not on the actual command... :)
In other threads (not this one) I've mentioned
that I made headway faster
with this card by focusing on input signals before output signals. On the
HDSP 9652 the 26 inputs you see in hdspmixer in the top line are the
inputs.
Are those working correctly? Can you send data input
each of those from
your
mixer and see meters operating correctly on all 26
inputs? (Or only 24 if
you don't have some spdif equipment.)
hmmm. yeah. that would be a different tact than I've been taking.
I'm trying to figure what I would do to test this. the only hardware input
I have going to the card is the adat lightpipes coming from the behringer
board. the behringer docs aren't that clear as to how stuff is going out -
is each channel outputting directly out, as if the adat lightpipes are tape
outputs? or what? it gets a little confusing, you can imagine, if the board
is routing things to multiple outputs. I'll have to futz with this to
see...
hmm I guess I could take the lightpipes from my old darwin into the hdsp
card too. this part I can figure out no prob
Only AFTER all of that works would I bother with
Ardour at all. When the
stuff above works perfectly, then it will take you very little time to get
Ardour working. If the above stuff doesn't work, Ardour doesn't have a
chance.
yeah, I feel ya. this make sense. ground up. I guess I keep going back to
ardour because of not knowing exactly how to see anything - are there
supposed to be meters in hdspmixer?
hmmm.
I think the first step is to get hdspmixer 1.3 to compile, which it's not.
this is quite weird. you mentioned hdsp.o - I found it and hdsp.c and
friends in /usr/src/redhat/BUILD/alsa-driver-0.9/something/rme9652 (excuse
inaccurate directory, I'm at a different machine), but I don't know if this
has anything to do with things. I tried moving what is apparently an old
version of hdspmixer out of /usr/bin to /usr/bin/oldhdsp just to get it gone
without actually deleting it, and that didn't effect compiling of 1.3 (I
didn't expect it to)
saving THAT, it seems to me it would be time to skip that and configure the
hdsp with the command line - so I actually expected to see results when I
tried amixer. but you're right, there needs to be a bit of reset happening.
coming dangerously close to the 'ol red hat reinstall trick ;)
4:34 p.m.
New subject: [linux-audio-user] another report HDSP 9652/jack/ardour/hdspmixer
On Thu, 2003-10-02 at 10:47, Aaron Trumm wrote:
yeah, I feel ya. this make sense. ground up. I guess I keep going back to
ardour because of not knowing exactly how to see anything - are there
supposed to be meters in hdspmixer?
hdspmixer is really nothign but meters. All of the values that show up
in the GUI are just read from the hardware and displayed, but I promise
you, what's displayed in version 1.2 or lower is not of much value.
hmmm.
I think the first step is to get hdspmixer 1.3 to compile, which it's not.
this is quite weird. you mentioned hdsp.o - I found it and hdsp.c and
friends in /usr/src/redhat/BUILD/alsa-driver-0.9/something/rme9652 (excuse
inaccurate directory, I'm at a different machine), but I don't know if this
has anything to do with things. I tried moving what is apparently an old
version of hdspmixer out of /usr/bin to /usr/bin/oldhdsp just to get it gone
without actually deleting it, and that didn't effect compiling of 1.3 (I
didn't expect it to)
I think I mentioned that earlier, and possibly I shouldn't have. Your
system is obviously loading something since you see snd-hdsp in memory.
(lsmod) The *question* was *what version of hdsp.c/hdsp.o is the system
loading? Since you have all the status and control registers, then it
appears you have successfully loaded the version with Thomas's patch.
However, there is a possibility that you are still loading some earlier
version. If you want to be VERY careful, you might take the snd-hdsp
entry out of your modules.conf file, reboot, and then load it by hand
using modprobe snd-hdsp. You would want to make sure you point to the
right one though, which would be where ever you built it.
Also, take a look at
/lib/modules/2.4.20-gentoo-r7/kernel/sound/pci/rme9652
(except change the Gentoo part to your kernel)
and make sure that the snd-hdsp.o file is the right date. If it is not,
then you might have correctly built the driver but you might still be
loading an older one.
saving THAT, it seems to me it would be time to skip that and configure the
hdsp with the command line - so I actually expected to see results when I
tried amixer. but you're right, there needs to be a bit of reset happening.
coming dangerously close to the 'ol red hat reinstall trick ;)
Well, you can see things using amixer, but it has no meters. alsamixer
does nothing with this driver and card, so do not bother with that.
What I did before Thomas and I got hdspmixer working was to use Jack and
Steve Harris's meterbridge to wire up meters for test purposes. That
will work assuming Jack will run for you. Use qjackctl and you'll be
able to wire the meterbridge meters to the ADAT hardware inputs, and the
Ardour outputs for that matter) very easily.
Since you have Ardour working, you could also just use it for input
meters. (This presumes you figure out how to get audio from the mixer to
the Linux box over ADAT.)
I'll be out of touch for the next few hours as I have some networking
problems here that I'm taking care of today.
Good luck!
Cheers,
Mark
7522
days inactive
7522
days old
linux-audio-user@lists.linuxaudio.org
14 comments
4 participants
participants (4)
-
Aaron Trumm -
Mark Knecht -
Mark Knecht -
Patrick Shirkey