11 Sep
2002
11 Sep
'02
6:53 a.m.
Paul Davis wrote:
For midi: wouldn't it be possible to allocate block of the upper bound-size.
I mean midi is constrained by the transfer-rate. Commands can be placed into
the buffer at the point in time when they should occure. Ofcourse they need to check
if the time-slot is still free and should use the next free one.
Stefan
--
\|/ Stefan Kost
<@ @> private business
+-oOO-(_)-OOo------------------------------------------------------ - - - - -
| __ Address Zwenkauer Str. 24 HTWK Leipzig, Fb IMN, Postfach 300066
| /// 04277 Leipzig 04277 Leipzig
| __ /// Germany Germany
| \\\/// Phone +49341 3910483 +49341 30766101
| \__/ EMail st_kost(a)gmx.net kost(a)imn.htwk-leipzig.de
| WWW www.sonicpulse.de www.imn.htwk-leipzig.de/~kost/about.html
===-=-=--=---=---------------------------------- - - - - -
that doesn't solve the generic malloc problem (strings of arbitrary
size) but it does look attractive for the common case of fixed-size
events.
yes, and it would be less than a few hours to get it working.
the problem is that many of the interesting data types are variable
sized. MIDI is the most obvious.
11 Sep
11 Sep
1:19 p.m.
New subject: LADPA (was Re: [linux-audio-dev] emagic (logic) drops VST support under OS X)
Stefan,
I would think that known buffer sizes would be a reasonable approach.
MIDI data isn't that dense, assuming you're not recording or playing back
controller information. Notes, sustain pedals, program changes, etc. are
pretty minimal. You could probably just buffer that in a known sized buffer
and use as much as you need.
I'm glad there's someone else here talking up MIDI.
Before we go there, I think we should look at the tempo/time
signature/measure marker issues. I don't think they effect audio recording
much (unless we want to talk sample stretching...) but they strongly effect
MIDI data, and how MIDI data is set against audio data. Right now I'd really
like to be able to drag an audio sample to the beginning of a measure, but
we're not at that point yet. I think having that sort of capability will
simplify the actual MIDI integration significantly.
My 2 cents,
Mark
-----Original Message-----
From: linux-audio-dev-admin(a)music.columbia.edu
[mailto:linux-audio-dev-admin@music.columbia.edu]On Behalf Of Stefan
Kost
Sent: Wednesday, September 11, 2002 1:50 AM
To: linux-audio-dev(a)music.columbia.edu
Subject: Re: LADPA (was Re: [linux-audio-dev] emagic (logic) drops VST
support under OS X)
Paul Davis wrote:
For midi: wouldn't it be possible to allocate block of the upper bound-size.
I mean midi is constrained by the transfer-rate. Commands can be placed into
the buffer at the point in time when they should occure. Ofcourse they need
to check
if the time-slot is still free and should use the next free one.
Stefan
--
\|/ Stefan Kost
<@ @> private business
+-oOO-(_)-OOo------------------------------------------------------ - - - -
-
| __ Address Zwenkauer Str. 24 HTWK Leipzig, Fb IMN, Postfach
300066
| /// 04277 Leipzig 04277 Leipzig
| __ /// Germany Germany
| \\\/// Phone +49341 3910483 +49341 30766101
| \__/ EMail st_kost(a)gmx.net kost(a)imn.htwk-leipzig.de
| WWW www.sonicpulse.de
www.imn.htwk-leipzig.de/~kost/about.html
===-=-=--=---=---------------------------------- - - - - -
_______________________________________________
linux-audio-dev mailing list
linux-audio-dev(a)music.columbia.edu
http://music.columbia.edu/mailman/listinfo/linux-audio-dev
that doesn't solve the generic malloc problem (strings of arbitrary
size) but it does look attractive for the common case of fixed-size
events.
yes, and it would be less than a few hours to get it working.
the problem is that many of the interesting data types are variable
sized. MIDI is the most obvious.
8044
days inactive
8044
days old
linux-audio-dev@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Mark Knecht -
Stefan Kost