Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Jander <manuel.jander@usm.cl>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Using hardware timers for the ALSA sequencer
Date: Wed, 16 Mar 2005 20:21:13 -0400	[thread overview]
Message-ID: <1111018873.3239.1.camel@localhost> (raw)
In-Reply-To: <1110845236.15588.23.camel@mindpipe>

Hi,

At least the aureal vortex has a high resolution hardware timer too. So
if this leads to some code to support hardware timers, i would suggest
something useable for other hardware too.

Best Regards

Manuel J. 

On Mon, 2005-03-14 at 19:07 -0500, Lee Revell wrote:
> Hey,
> 
> The emu10k1 timer thread reminded me of an idea I had.
> 
> Currently the ALSA sequencer always uses the system timer by default.
> If your sound cards timer is supported by ALSA (emu10k1 and ymfpci),
> this provides 50-100x better resolution.  But in order to get the ALSA
> sequencer to use it you have to use the seq_default_timer_*  options
> (which BTW I had never heard of on the list, I stumbled across them
> reading the source).
> 
> How hard would it be to get the sequencer to prefer the hardware timer
> by default and fall back to the system timer otherwise?  Probably would
> not be noticeable for a MIDI keyboard, but for applications like sending
> MIDI clock/MTC, the system timer resolution can be inadequate.
> 
> Would this be a good idea?
> 
> Lee
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
-- 
Manuel Jander
Electronic Engineer



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-03-17  0:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15  0:07 Using hardware timers for the ALSA sequencer Lee Revell
2005-03-15  8:55 ` Clemens Ladisch
2005-03-15 19:10   ` Lee Revell
2005-03-16  8:26     ` Clemens Ladisch
2005-03-15 19:12   ` Lee Revell
2005-03-17  0:21 ` Manuel Jander [this message]
2005-03-17  4:31   ` Lee Revell

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=1111018873.3239.1.camel@localhost \
    --to=manuel.jander@usm.cl \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mjander@users.sourceforge.net \
    /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