Thomas Charbonnel wrote:
Ed Wildgoose wrote:
Can anyone suggest how to script the controls to default to some known
values?
This is not a standard mixer control, alsactl is of no use here.
Ed, here's a script for 1:1 routing (hdspmixer preset 1)
Aha, at last the penny drops
...is driving me nuts. Everytime I turn on the PC I need to find a PC
with SSH to adjust the mixer controls so that I can hear some sound (no
mouse and a tiny TV resolution on the box itelf)
Can anyone suggest how to script the controls to default to some known
values? I'm using alsa from aro
Joachim Deguara wrote:
The good news: you don't have a driver problem! But it sounds like
you have a Wordclock problem. Namely, your rme 9632 has a different
clock than your playback device (D/A) and they are not in Sync. Check
the setting for who is (and should be) Wordclock Master and take
Orm Finnendahl wrote:
Hi,
hope this is the right list to post: I installed to RME Pci Cards with
a Multiface each. Running hdsploader finds and initializes both and
hdspmixer can also get used with both cards using the card select
buttons for card1 and card2. However after startup of jack, I only
You can also simulate this simply by turning up the mixer controls so
that normal music starts to clip. Same effect.
At risk of creating noise. Further experimentation shows that you need
to set the output levels to +4db in hdspconf for this crackling to
occur. So in fairness this could re
Hi, I'm running kernel 2.6.5-mm1 with built-in alsa drivers. Also, v
1.04 of the various alsa utils, etc.
I'm playing (for example) Dido - No Angel, track "Isobel", and according
to the hdspmixer tool, at the end of the track the drums have transients
that go greater than 0db, and this causes
> Thanks, this is good news. Could you also please test hdspmixer with the
> expansion board and confirm there's no problem here either ?
Yes, hdspmixer does all the right things with the extra channels.
There appears to be a minor bug in that the input channels 8 and 9 (I
think?), ie the top rig
> > I haven't had time to try and get any sound out of it yet! However, it
is
> > detected correctly in the mixer, and the driver thinks that there are 4
> > extra channels. I need to get some jack socket convertors to get some
sound
> > out, but will let you know.
> >
>
> Please do so, thanks.
> > > Florin Andrei wrote :
> > > > Anyone using the latest RME HDSP 9632 driver in ALSA, while also
using
> > > > the expansion cards? I mean, the newer AI4S-192 and/or AO4S-192
which
> > > > are required to get the 192kHz sampling on all analogs.
>
> > I have a 9632 now and also the 4 port analog
> Florin Andrei wrote :
> > Anyone using the latest RME HDSP 9632 driver in ALSA, while also using
> > the expansion cards? I mean, the newer AI4S-192 and/or AO4S-192 which
> > are required to get the 192kHz sampling on all analogs.
> >
> > Do the latest expansion cards (192kHz) work with the lates
> I plan to add an option to export a shell script restoring the current
> setup in the next hdspmixer release.
Yes, this would be extremely nice if alsa could save the mixer settings at
shutdown and restore them later.
I think the issue is that the mixer setting is not readable. Perhaps there
i
> I wish I could! But no other PCI card I've found so far has 192kHz AES/EBU
IO
> I need for linking it to dCS converters we have in studio on our
University.
Can't you do this through the various RME cards? The latest ones have
192khz analogue, but I haven't looked at the digital performance...?
> Hi, I'm having some problems getting the alsa input into Jack working
> correctly.
>
> The soundcard is an RME96/8 PAD, Alsa from Kernel 2.6 pre9, and Jack
version
> 0.91.1 - I'm firing up Jackd with:
>
> jackd -R -t 2000 -d alsa -d rme96 -r 44100 -p 1024 -n 8 -m -zs -H -M &
>
> ...and I have a
> I don't know how alsa patches drivers when it has to compile on kernel
> 2.6, so I don't know how to fix it.
See my message in Alsa-Users posted a few hours ago with title: "Can not
patch 2.6 kernel"
The answer is listed on the first page of the alsa website in fact! I failed
to read it at firs
> >"You cannot set callbacks on an active client
> >cannot connect alsaP:out_000
> > to alsa_pcm:playback_1"
>
> if these clients really do call snd_pcm_close() when ffwd'ing, then
> there must be some mistake in the ALSA JACK plug, because it should
> close the client down. if they do not call snd
Hi, I'm having some problems getting the alsa input into Jack working
correctly.
The soundcard is an RME96/8 PAD, Alsa from Kernel 2.6 pre9, and Jack version
0.91.1 - I'm firing up Jackd with:
jackd -R -t 2000 -d alsa -d rme96 -r 44100 -p 1024 -n 8 -m -zs -H -M &
...and I have an asound config (
Hi,
I have an RME 96/8 PAD card and I have tried various versions of the
alsa driver from 0.9 up to 0.94 and I'm seeing a consistent problem with
simultaneous play and record at 16 bit sample levels with OSS
For example running:
sox -r 44100 -t ossdsp -w -s -c 2 /dev/dsp test.wav
is fine, but t
17 matches
Mail list logo