On Friday 20 December 2002 21:09, Clemens Ladisch wrote:
Takashi Iwai wrote:
Mark Knecht wrote:
I was wondering what would happen in this process if someone had two r
three identical USB devices, like the MidiMan 2X2? OR also two
identical cards like the RME HDSP 9652?
when a
At 18 Dec 2002 05:11:36 -0800,
Mark Knecht wrote:
On Wed, 2002-12-18 at 03:17, Takashi Iwai wrote:
At Wed, 18 Dec 2002 11:46:45 +0100,
I wrote:
It would be better to make the alsasound script more robust (and
independent of the startup order) and able to deal with partially
At Fri, 20 Dec 2002 23:53:13 +0100,
Pedro Lopez-Cabanillas wrote:
Clemens, I remember that /proc/asound/cards returned this bus/device
information for USB MIDI devices some time ago (rc3?), like it does for my SB
128 PCI.
it would be nice to provide a new generic proc file which shows the
At 17 Dec 2002 11:36:10 -0800,
Fernando Pablo Lopez-Lezcano wrote:
On Tue, 2002-12-17 at 03:06, Takashi Iwai wrote:
At 16 Dec 2002 19:46:55 -0800,
Mark Knecht wrote:
On Mon, 2002-12-16 at 18:51, Paul Davis wrote:
i think it would something like this:
options snd-hdsp
At Wed, 18 Dec 2002 11:46:45 +0100,
I wrote:
It would be better to make the alsasound script more robust (and
independent of the startup order) and able to deal with partially loaded
modules, so instead of just checking for the /proc/asound directory it
would actually see what modules
At 16 Dec 2002 19:46:55 -0800,
Mark Knecht wrote:
On Mon, 2002-12-16 at 18:51, Paul Davis wrote:
i think it would something like this:
options snd-hdsp snd_index=0
options snd-usb-foo snd_index=1
i'm sure that takashi or jaroslav will correct me if i got this wrong.
--p
Paul Davis wrote:
yes, thnx, it's much clearer now. my converter is external with no
rate switches and from the manual i just discovered it always
operates at 48000 (Alesis AI-3). i'm s till uncertain how to change
the card's configuration though. alsactl doesn't seem to provide
an
On Sun, Dec 15, 2002 at 08:38:54PM -0800, Mark Knecht wrote:
Paul,
I'm using two Hammerfalls in separate boxes. Please try to come up
with a solution, either automatically or by asking questions in some
configuration process, that allows two Linux boxes to choose which to
make the master.
Martin,
That might certainly be an answer. How would this amixer switch get
st in the first place? I wouldn't mind doing it by hand once as long as
it was then loaded after that.
I'm having an interesting problem with this setup with now that's
probably based in this area. If I bring up
Martin,
That might certainly be an answer. How would this amixer switch get
st in the first place? I wouldn't mind doing it by hand once as long as
it was then loaded after that.
what you want is a short startup script (typically in somewhere under
/etc/rc.d, but unfortunately this varies
At Mon, 16 Dec 2002 08:49:35 -0500,
Paul Davis wrote:
Martin,
That might certainly be an answer. How would this amixer switch get
st in the first place? I wouldn't mind doing it by hand once as long as
it was then loaded after that.
what you want is a short startup script (typically in
the standard alsasound init script can call a card-dependent script
that reminds me. the last version of the alsasound script that i saw
did something very dangerous. it seemed to try to install *every*
snd-card module it could find. if you have a system with an ISA bus,
this can prove fatal to
On Mon, Dec 16, 2002 at 04:04:23AM -0800, Mark Knecht wrote:
I'm having an interesting problem with this setup with now that's
probably based in this area. If I bring up these two systems with the
main DAW in Linux, and the slave system in Windows everything is fine.
The DAW controls the
IMHO this is a design bug of all rme cards. The documents about rme32 and
rme96 where identical in this point. They were talking about one master-mode
and nothing about the frequency. I don't know anything about rme9652 or
hdsp, but the sourcecode looks not very different to the older rme96.
But
At Mon, 16 Dec 2002 09:29:05 -0500,
Paul Davis wrote:
the standard alsasound init script can call a card-dependent script
that reminds me. the last version of the alsasound script that i saw
did something very dangerous. it seemed to try to install *every*
snd-card module it could find. if
paul davis wrote:
does any of this make it any clearer? its really a bit of problem that
the rate setting code doesn't do a full 100% check on all this
stuff. an app can set the rate to 44100, and appear to have succeeded,
but it will have no difference on the actual rate if the sync source
Patrick,
I believe the AI-3 operates at 48K if it is not receiving a clock via
it's ADAT input. If the ADAT input is applied and provides 44.1K, then
it is my understanding that the AI-3 operates at 44.1K.
Mark
On Mon, 2002-12-16 at 14:53, patrick reardon wrote:
yes, thnx, it's much
hi everyone:
i'm running on a PIII with kernel 2.4.18 and Alsa 0.9.0rc6 and a Hammerfall 9636 card.
Alsa has been working fine for the last year, or so it seems. recently a scsi CD
burner
was installed. i have some recordings of live performances made with arecord,
version
0.9.0beta8a. they
Patrick,
I'm not an Alsa expert so take all of this with a grain of salt. The
difference between 48K and 44.1K is indeed about a whole step, so that's
consistent with your results. You have 48000 samples that are supposed
to take one second to play, but you are taking more than one second to
Latency: 4096 samples (2 periods of 16384 bytes)
Hardware pointer (frames): 0
Passthru: no
Clock mode: autosync
Pref. sync source: ADAT1
IEC958 input: Coaxial
IEC958 output: Coaxial only
IEC958 quality: Consumer
IEC958 emphasis: off
IEC958 Dolby: off
IEC958 sample rate: error flag set
ADAT
Paul,
I'm using two Hammerfalls in separate boxes. Please try to come up
with a solution, either automatically or by asking questions in some
configuration process, that allows two Linux boxes to choose which to
make the master. It is important in my case.
Thanks,
Mark
On Sun, 2002-12-15 at
21 matches
Mail list logo
