Hello all,
I'm just now putting together my first linux box and need somebody to hold
my hand and walk me through the setup of my sound card. (BTW if there is
already a thread on this that I didn't catch on my quick search of the list
archives, please point me to it.)
I'm currently using a RME 96/8 PAD on a RH8 distro. I installed the alsa
packages available from freshrpms.net. After getting everything installed I
started up alsamixer and the only controls available is a volume control for
the DAC. Please tell me that I'm missing something and that there is much
more control functionality available than just levels for the DAC. Shouldn't
I have at least some sort of controls for the digital IOs and the ADAT? Is
there some sort of fancy config I need to do in /etc/asoundrc? Have I missed
something in configuration of devices, subdevices, some package not
installed etc?
Also, (slightly off topic) this card is very picky about the buffer settings
(i.e. fixed buffersize of 64KBytes). I know what settings work when setting
number of periods and frame size, but how do I work that out when programs
only let you set the buffer size in units of time rather than actual size?
Any help is appreciated.
Reguards,
-Reuben
Hi Mark,
Thanks very much for your those hints. Do you have any idea (or where I
can find the documentation) on how to play through the SPDIF or ADAT ports?
Where is the matrix mixer controls (amixer) documented for these cards?
DS
Mark Knecht wrote:
dsen,
Hi. I'm messing with similar things this evening. (And not doing
great, but not failing either.) I'm using a HDAP 9652, not the
Multiface, but it's the same driver I believe. The difference is I have
no 'headphone output'. Just 26 outputs.
I'm in KDE. Inside of a Konquerer window, I have set the file
associations for wav and x-wave to be
aplay -device="plughw"
This seems to work all the time in a Konquerer window, but doesn't work
on a file just sitting on my desktop. Don't ask me why.
FYI#1 - make sure you don't have a blocking aplay sitting around. Do a
ps -aux | grep aplay
and make sure nothing is there.
FYI#2 - My headphones and main speakers are running off of playback_1 &
2.
Good luck,
Mark
On Wed, 2002-12-18 at 20:29, D. Sen wrote:
/> Hi,/
/> /
/> I have just bought myself the Cardbus+Multiface RME system. I think I /
/> have finally gotten the alsa modules (snd-hammerfall-mem and snd-hdsp) /
/> to load correctly along with the OSS emulation modules. BUT I cant seem /
/> to play anything out of the Lineout/Headphone output. I have tried /
/> various 'amixer cset' commands but all I get is silence (trying to play /
/> a simple wav file using aplay)./
/> /
/> Any suggetsions?/
/> /
--
---------------------------------------
D. Sen, PhD
21 Woodmont Drive
Randolph
NJ 07869
Home Email: dsen(a)homemail.com Tel: 973 216 2326
Work Email: dsen(a)ieee.org Web: http://www.auditorymodels.org/~dsen
Hej to all,
I used to work with the really nice loopbased timestretching music
application ACID on windows. Is there any equivalent on linux ?
Thanks a lot
-- A l e x
Paul,
Great info. I didn't know about modinfo. Is there a way to query what the
current setting of these parameters are? It seems that I'm told I have a
range to work in, like 1-8, but no indication of how they are currently set
or what they do. (Maybe only read the code?)
I'm sure that many are just on/off sorts of things, but some clearly are
not.
Mark
-----Original Message-----
From: linux-audio-dev-admin(a)music.columbia.edu
[mailto:linux-audio-dev-admin@music.columbia.edu]On Behalf Of Paul Davis
Sent: Thursday, December 19, 2002 6:21 AM
To: linux-audio-dev(a)music.columbia.edu
Cc: Alsa-List
Subject: Re: [linux-audio-dev] RME Hammerfall DSP Cardbus+Multiface
>dsen,
> Hi. I'm messing with similar things this evening. (And not doing
>great, but not failing either.) I'm using a HDAP 9652, not the
>Multiface, but it's the same driver I believe. The difference is I have
>no 'headphone output'. Just 26 outputs.
>
> I'm in KDE. Inside of a Konquerer window, I have set the file
>associations for wav and x-wave to be
>
>aplay -device="plughw"
>
actually, i doubt that this is the issue at all. the hdsp driver has a
module option:
snd_line_outs_monitor
(possibly changed in recent versions to just "line_outs_monitor"). if
set to a non-zero value, all other outputs will be monitored on the
headphone/line out channels. you can find out about module options
using the modinfo command. for example:
% modinfo snd-hdsp
filename: /lib/modules/2.4.19/kernel/sound/pci/rme9652/snd-hdsp.o
description: "RME Hammerfall DSP"
author: "Paul Davis <pbd(a)op.net>"
license: "GPL"
parm: snd_index int array (min = 1, max = 8), description "Index
value for RME Hammerfall DSP interface."
parm: snd_id string array (min = 1, max = 8), description "ID string
for RME Hammerfall DSP interface."
parm: snd_enable int array (min = 1, max = 8), description
"Enable/disable specific Hammerfall DSP soundcards."
parm: snd_precise_ptr int array (min = 1, max = 8), description
"Enable precise pointer (doesn't work reliably)."
parm: snd_line_outs_monitor int array (min = 1, max = 8), description
"Send all input and playback streams to line outs by default."
parm: snd_force_firmware int array (min = 1, max = 8), description
"Force a reload of the I/O box firmware"
the parameter defaults to zero, so by default, you hear nothing.
there is no way to use any existing linux audio mixer to control
*what* you hear - the hdsp has 1542 mixer controls arranged in a
matrix, and its just not possible to make sense of this with mixers
designed around a few channels with direct routing. work is proceeding
on an equivalent to RME's TotalMix to offer ways of controlling this.
--p
Hi,
I have just bought myself the Cardbus+Multiface RME system. I think I
have finally gotten the alsa modules (snd-hammerfall-mem and snd-hdsp)
to load correctly along with the OSS emulation modules. BUT I cant seem
to play anything out of the Lineout/Headphone output. I have tried
various 'amixer cset' commands but all I get is silence (trying to play
a simple wav file using aplay).
Any suggetsions?
--
---------------------------------------
D. Sen, PhD
21 Woodmont Drive
Randolph
NJ 07869
Home Email: dsen(a)homemail.com Tel: 973 216 2326
Work Email: dsen(a)ieee.org Web: http://www.auditorymodels.org/~dsen
Hi,
On Wednesday 18 December 2002 18:00, Chris Cannam wrote:
> The Rosegarden team have the pleasure of announcing the
> latest release of their MIDI and audio sequencer and score
> editor for Linux.
Well done, guys!
Im really impressed, being able now to play and record from/to several MIDI
sources, and work with a long session without a single crash. Thank you very
much!
Regards,
Pedro
--
ALSA Library Bindings for Pascal
http://alsapas.alturl.com
Thanks for the info but I still have a few questions.
Does the AI3 support 96 KHz like the ADI-8 DS does? I know it supports
24 bit, which is useful. Does the ADI-8 DS do anything the AI3 can't?
the price difference is huge, and I don't really see all that much of a
difference.
Thanks!
Robert Cohen
Also, where can I find a copy of the HDSP 9652 drivers?
i dont quite know how to do this any more.. getting to wits end
still going with usb audio stuff
have tried with and without the devfs stuff in modules.conf
have tried with alsa tarballs and without them
have tried instructions as per kevin's site
nothing seems to be working: xmms says this:
[root@hamish miriam]#
** WARNING **: oss_open(): Failed to open audio device (/dev/dsp): No
such device
similiar results for alsaplayer
please help! i'm at my wits end! ;-)
cant explain why it would work 2 days ago and wont work now
i've tried repeating everything i did then (which was just to make sure
mandrake libalsa2-devel and libalsa-data rpms were installed and then
clean out modules and install again from tarballs. it worked, i dont
know how it worked but it did).
the only thing i can think of is those weird warning messages i got when
building alsa-driver, it was something about the records in
/lib/modules/2.4.19-16mdk/kernel/sound/ saying that this was the same
location i have used before
does anyone know what this means? or how i should proceed?
thanks
m~
--
iriXx
www.iriXx.org
copyleft: creativity, technology and freedom?
info(a)copyleftmedia.org.uk
www.copyleftmedia.org.uk
_
( ) ascii ribbon against html email
X
/ \ cat /dev/sda1 > /dev/dsp
*** stopping make sense ***
Hi,
i convert a live-stream with ecasound to MP3s; but
mpg123 has a lot of problems with the stream. i have
discovered that here and then there's an mp3 frame
with Padding set to 1 and as soon as the first
padding-frame appears mpg123 starts to get a hickup.
The only lame-option i use is the following:
ext-mp3-output-cmd = lame -b 64 -a -m m -x -S - %f
(i need a mono-64kbit-stream)
I have searched the lame man-page but haven't found
any switch to disable the padding.
any idea what i could do?
Thanks
Chris
=====
http://www.crupp.de
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
The Rosegarden team have the pleasure of announcing the
latest release of their MIDI and audio sequencer and score
editor for Linux.
The source code is available now from the project homepage:
http://www.all-day-breakfast.com/rosegarden
The availability of binary packages depends on their various
maintainers; please check the project homepage for more
information.
New features since the 0.8 release include:
o Improved MIDI file I/O: better support for banks and
merging in import, better support for delay, transpose
etc in export
o MIDI device Bank and Program editor, including import
and export of Studio data
o MIDI Panic Button for clearing down stuck notes
o Added some keyboard controls to matrix
o Added real-time segment delays
o Progress display completely overhauled
o ALSA clients can be added dynamically (you can change
your soft synth configuration while Rosegarden is running)
o MIDI events filter dialog for MIDI THRU and MIDI record
o MIDI/ALSA recording bug fixed (stopping after so many
recorded events)
o Many bug fixes, tweaks and performance improvements
Unfortunately we've had to drop KDE2 support from this release
onwards as it was getting too difficult to maintain both KDE2
and KDE3 in the same development tree. We're hoping this won't
affect too many users in the long term.
Finally, we would like to thank the cachegrind/kcachegrind team
for a truly useful development tool.
Chris