From: Juan Linietsky <coding@reduz.com.ar>
To: alsa-devel@alsa-project.org
Subject: Forcing an absolute timestamp for every midi event.
Date: Sun, 18 Aug 2002 05:57:40 -0300 [thread overview]
Message-ID: <20020818055740.2af8e3e7.coding@reduz.com.ar> (raw)
Hi! I wanted to ask, how about forcing
an absolute timestamp for _every_ midi event?
I think this would be great for softsynths,
so they dont need to work with root/schedfifo/lowlatency
to have a decent timing. Not allways you are willing
to process midi at the lowest latency possible.
I say because you dont really need all that if you
sequence in the computer and control softsynths and maybe
some external device.
This way, the softsynth gets the event with the timestamp,
gets the current time, substracts the audio delay (latency) to that
and just mixes internally in smaller blocks processing each
event in the right time.
Juan Linietsky
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
next reply other threads:[~2002-08-18 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-18 8:57 Juan Linietsky [this message]
2002-08-18 10:08 ` Forcing an absolute timestamp for every midi event Patrick Shirkey
2002-08-18 12:48 ` Frank van de Pol
2002-08-18 22:17 ` Juan Linietsky
2002-08-19 15:47 ` Takashi Iwai
2002-08-18 20:12 ` Martijn Sipkema
2002-08-18 21:18 ` [linux-audio-dev] " Frank van de Pol
2002-08-19 6:43 ` Martijn Sipkema
2002-08-19 7:52 ` Jaroslav Kysela
2002-08-18 22:58 ` Juan Linietsky
2002-08-19 6:41 ` Martijn Sipkema
2002-08-19 8:07 ` Juan Linietsky
2002-08-19 12:39 ` Martijn Sipkema
2002-08-19 13:01 ` aside - alsa-docs Patrick Shirkey
2002-08-20 21:11 ` Forcing an absolute timestamp for every midi event Frank van de Pol
2002-08-21 1:10 ` Martijn Sipkema
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=20020818055740.2af8e3e7.coding@reduz.com.ar \
--to=coding@reduz.com.ar \
--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.