Judging from the [readsf~] help patch, [readsf~] takes two optional arguments:
I think argument 2 might be worth investigating ...
Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Nov 19, 2015, at 4:55 PM, pd-list-request@lists.iem.at wrote:
From: Achim Bornhoeft <achim@bornhoeft.org mailto:achim@bornhoeft.org> Date: November 19, 2015 at 12:32:11 PM MST To: Py Fave <pyfave@gmail.com mailto:pyfave@gmail.com> Cc: "pd-list@iem.at mailto:pd-list@iem.at List" <pd-list@iem.at mailto:pd-list@iem.at> Subject: Re: [PD] [hdplay~] problem
also i see in soundfiler help:
read - resize should help
-maxsize <maximum number of samples we can resize to>
The abstraction uses [readsf~] because I want to play the soundfiles directly from disk without reading them into an array. How can I change the soundfiler -maxsize in this case ? Achim
On 11/20/2015 07:07 AM, Dan Wilcox wrote:
Judging from the [readsf~] help patch, [readsf~] takes two optional arguments:
- number of channels
- buffer size per channel in bytes
I think argument 2 might be worth investigating ...
it is, but you might discover that it is about something else: [readsf~] reads the data from harddisk in a separate thread. the "buffer size" defines how much the reading thread can read ahead of the playback.
gfmrdsa IOhannes