[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [iiwusynth-devel] Lates CVS changes
From: |
Peter Hanappe |
Subject: |
Re: [iiwusynth-devel] Lates CVS changes |
Date: |
Tue, 03 Dec 2002 20:45:45 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 |
Antoine Schmitt wrote:
:::::::::3/12/02::::14:43 +0100::::Peter Hanappe:::::::::
Maybe there's
no need for on demand load and caching if streaming is available.
Mmm, these are really different, especially when using the media from a
slow medium (CD-Rom, Internet). On these slow medium, it is best of the
client app can decide when to do the file access (i.e. explicit
loads/unloads).
I didn't think of that.
My basic idea for the streaming back-office is a cache
of sample buffers. These sample buffers store a part of the full
sample and have the same size, for example 8k.
Maybe some optimization for samples/instruments/presets with loops would
be nice : if a loop happens during the sustain phase, dont access the
file system all the time. It would argue for a custom buffer length for
each sample...
Yes, the loop should best be contained in one buffer, if not too large.
However, the synth needs some way to specify which buffer is needed
next. And the soundfont needs some efficient way to test whether the
buffer is in the cache. A buffer number, based on buffers of fixed size,
is an easy way to specify buffers. I'll thinker a bit more about the
problem and the use of variable buffer sizes.
P
++ as
_______________________________________________
iiwusynth-devel mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/iiwusynth-devel