Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Billy Biggs <vektor@DIV8.NET>
To: linux-sound@vger.kernel.org
Subject: External MIDI Sync using OSS/Free
Date: Tue, 26 Oct 1999 15:35:56 +0000	[thread overview]
Message-ID: <marc-linux-sound-94095430923870@msgid-missing> (raw)

Hi,

  My sequencer (http://www.div8.net/ttrk) mainly runs off of external MIDI
sync, and drives a mess of synths and stuff.  I use /dev/sequencer for
MIDI input and output.

  Since I'm both reading incomming MIDI, and sending outgoing MIDI, and
since I like to change the tempo on the fly, I have to do annoying
predictions in order to stay in sync.  Blech.

  Anyways, one thing I've found is that the /dev/sequencer clock is
different for incomming and outgoing.  So, in order to do a prediction a
few ticks ahead, I can't just add to the incomming time and blast out
messages.  As well, the outgoing clock seems difficult to predict.

  This is really annoying for song starts.  Every time I get a song start,
I call SNDCTL_SEQ_GETTIME, and take the difference between it and the
timecode on the start message.  I then apply that difference to every
outgoing packet.

  Is there a way that I could do this more efficiently?  Since my app
might not get swapped in until late after the start arrived, and then I
have to call the ioctl.  This error then remains for the entire duration
of the song.

  Any advice?
--
Billy Biggs                         vektor@div8.net
http://www.div8.net/billy       wbiggs@uwaterloo.ca

                 reply	other threads:[~1999-10-26 15:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-sound-94095430923870@msgid-missing \
    --to=vektor@div8.net \
    --cc=linux-sound@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox