From: Paul Davis <paul@linuxaudiosystems.com>
To: Tim Blechmann <TimBlechmann@gmx.net>
Cc: Jesse Chappell <jesse@essej.net>,
alsa list <alsa-devel@lists.sourceforge.net>,
alsa-user@lists.sourceforge.net,
linux-audio-user@music.columbia.edu
Subject: Re: hdsp problem
Date: Thu, 15 Jan 2004 15:02:09 -0500 [thread overview]
Message-ID: <200401152002.i0FK29cm014929@dhin.linuxaudiosystems.com> (raw)
In-Reply-To: Your message of "Thu, 15 Jan 2004 21:30:42 +0100." <20040115213042.5011ee58.TimBlechmann@gmx.net>
>it's not working on my system (i tried 64, 128, 256) ... but playing
then i guess there is more than one problem. i would also recommend
checking into whatever is sharing the interrupt that the hdsp is
on. on my laptop, way too many things are on IRQ10 (USB, CardBus,
Wifi, HDSP). this seems hard to change, but it might have some effect.
>with the different settings, i figured out, that i can't change the
>number of periods in the hardware buffer ... it's always 2 times the
>number of frames per period ...
thats the hardware design of all the hammerfall series devices. RME
calls its "ASIO in hardware". snicker.
>jack returns as error message:
>ALSA: cannot set number of periods to 1 for capture
that would make no sense whatsoever.
>nearly giving up the hope ...
never give up. there are lots of people using the h/w you have with
100% success. i have to pack up and run off to NAMM now. sorry i can't
be more helpful for now.
--p
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
prev parent reply other threads:[~2004-01-15 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 12:23 hdsp problem Tim Blechmann
2004-01-15 16:11 ` Jesse Chappell
2004-01-15 20:30 ` Tim Blechmann
2004-01-15 20:02 ` Paul Davis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401152002.i0FK29cm014929@dhin.linuxaudiosystems.com \
--to=paul@linuxaudiosystems.com \
--cc=TimBlechmann@gmx.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=jesse@essej.net \
--cc=linux-audio-user@music.columbia.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox