strange sfplay~ behaviour on Windows??

cobtob's icon

Hi Everybody
I am fairly new to Max/Msp and I

Jakob Riis's icon

22/11/06, kl. 11:27 +0100 , skrev Jacob Sello:

>Hi Everybody
>I am fairly new to Max/Msp and IZ?m experiencing some strange
>difficulties with SfPlay~.
>IZ?m preparing a Thater-Production on the upcoming Weekend, so I need to
>solve my Problem quickly...
>I built a simple Player for Wave-Files. I just need to press "Enter"
>and next File is played.
>But at longer Files playback (sometimes!!) and unpredictably(!!) stops
>(not having finished playing the file). I just donZ?t have a clou.

>The "openerPlayer" is working belong a fairly complex Live-sampling Patch.
>Windows System-Monitor tells very high (up to 99% Processor-usage), but
>Max internal Recources-Display is about 60%.
>I guess Max-Display is the on to trust, right??

DSP status only monitors cpu usage in the DSP chain (MSP), all activity
in the Max domain is not included, so i guess your Windows System-
Monitor could be right.

Other than that it sounds like a harddisk related issue. What about your
live sampling patch, do you write and read from the disk, or do you use
buffer~ ?

/J

cobtob's icon

I use a buffer for the live-sampling..
The disc is usually pretty fast and not in use for any other streming issues,,,
j.

Jakob Riis's icon

22/11/06, kl. 15:20 +0100 , skrev Jacob Sello:

>
>I use a buffer for the live-sampling..
>The disc is usually pretty fast and not in use for any other streming
>issues,,,

OK. Maybe it's the high cpu load then...
Anyway, the only thing I can think of is to try different diskbuffer
sizes. (Can be specified as an additional optional argument to sfplay~,
check the help file).

/J

cobtob's icon

Hi Jakob
Thanks for your help.
I think you are right. HIgh CPU-Load is my main Issue..
I

Joshua Kit Clayton's icon

In addition to diskbuffer size, I would highly recommend that you set
your HD to not sleep when you're doing live audio performance. This
is a big factor of sfplay~ stopping especially in patches where one
only accesses disk occasionally.

If your diskbuffer size is large enough, you might never have to
worry about this, but large disk buffer's require more memory.

-Joshua