All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rivera <marr@lumin.us>
To: alsa-devel@alsa-project.org
Subject: Source of timing for MIDI and/or audio synchronization
Date: Tue, 12 Jun 2007 01:17:57 -0500	[thread overview]
Message-ID: <466E3A95.8070900@lumin.us> (raw)


Hello (new to list), and thank you for the work you have been doing. As 
an end-user of the ALSA project's development, I am very grateful for 
being able to use softwares which provide audio functionality to Linux.

I have been reading up on the docs and list archives, but I still have 
an open question for which I hope you can lead me to an answer.

I designed and built a MIDI sequencer based around a Microchip PIC18 
MCU, and used the built-in hardware timers and interrupt levels to drive 
the 'scheduler' for initiating MIDI output (EUSART) routines. In this 
same vein, I would like to write a software sequencer with as 'tight' 
timing as possible. So, in a similar concept for Linux - from where does 
the timing of audio and MIDI events come from?

It occurred to me that it would be nice to have a loadable kernel module 
(LKM) to which userland programs could subscribe for receiving 'soft 
interrupts' based on some timer (cpu ticks?) so that various software 
could all reference the same notion of the "current time" - a sort of 
"master clock" with start/stop/continue as well.

Does ALSA provide this functionality? Can someone point me in the right 
direction for learning more about this?

Many thanks.

Mark

             reply	other threads:[~2007-06-12  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  6:17 Mark Rivera [this message]
2007-06-12 12:23 ` Source of timing for MIDI and/or audio synchronization Dmitry Baikov
2007-06-12 12:29 ` Takashi Iwai

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=466E3A95.8070900@lumin.us \
    --to=marr@lumin.us \
    --cc=alsa-devel@alsa-project.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.