[PD] MIDI triggered samples
pkstone at ucdavis.edu
Fri Mar 25 21:16:27 CET 2011
Thanks for the suggestion, and for further clarifying (in my mind) what
I'll need. I think readsf~ won't do because of the "open before play"
requirement -- it will introduce latency and prevent re-triggering, if
I'm not mistaken.
I guess it's going to be a matter of loading as many tables in memory as
I can get away with and using tabread4~ with a phasor.
Thanks for writing,
On 3/24/11 11:37 PM, Jaime Oliver wrote:
> Hi Phil,
> if they'll always play from the beginning and the only control you
> need is amplitude, then I would try readsf~.
> On Thu, Mar 24, 2011 at 1:57 PM, Phil Stone<pkstone at ucdavis.edu> wrote:
>> OK, this was probably too broad a way to pose this. Let me try it this way:
>> I'm not concerned with looping, re-sampling or sample-rate changing. I
>> simply want a low-latency trigger of a sound file from an incoming event.
>> The file(s) may, however, be quite large.
>> So, is a phasor-scanned [tabread4~] the best way to go about this? Will
>> memory management become an issue if I have 44 or 88 of these large samples
>> in memory at once?
>> On 3/24/11 11:30 AM, Phil Stone wrote:
>>> Hello collective PD mind,
>>> Despite having worked with PD for years, I've never used it as a sample
>>> player. I have a project coming up where I will need to build a bank of
>>> MIDI-keyboard-triggered samples to play in real-time, with velocity
>>> sensitivity and one sample per key. Rather than reinvent the wheel, is there
>>> something someone has already done along this line? If not, can anyone give
>>> me a basic outline from which I can start?
>>> Phil Stone
>>> Pd-list at iem.at mailing list
>>> UNSUBSCRIBE and account-management ->
>> Pd-list at iem.at mailing list
>> UNSUBSCRIBE and account-management ->
More information about the Pd-list