Dante

So i have a patch where you bang and select a random file from a folder, Also bang for random line start, end, duration. It seems to work for 2 or 3 plays then silence forever. I started using Groove~, then i read about its limitations and que-ing into RAM so I switched to sfplay~ and still same problem.

I'm hoping this is just a tiny error that I am overlooking, and that someone could please help me with. I've been digging in the forum archives for 5 hours.

My plan was to bpatch two of the patches to play from two folders. 1 folder is 16mb the other is 45mb. all .Aif, 4 - 16 seconds long, stereo.

I guess a second question would be I should make the files mono to cut down on my "40K of memory per sfplay~ channel"??

So i have a patch where you bang and select a random file from a folder, Also bang for random line start, end, duration. It seems to work for 2 or 3 plays then silence forever.  I started using Groove~, then i read about its limitations and que-ing into RAM so I switched to sfplay~ and still same problem. 

I'm hoping this is just a tiny error that I am overlooking, and that someone could please help me with. I've been digging in the forum archives for 5 hours. 

My plan was to bpatch two of the patches to play from two folders.  1 folder is 16mb the other is 45mb. all .Aif,  4 - 16 seconds long, stereo. 

sfplay-and-groove-both-wont-play-files

Ok so maybe helpful to other beginners out there, I found this bit from 2008.

>>>> Yes, sfplay’s name is not an argument.

>> By the way, there is a problem in the design of this "name" feature in

>> [sfplay~]. When you give a name (with a message), it is stored in

>> (open such a Max patch later with a text editor to check).

>> But there is then no way to say "no name, please".

>> Result: when you name a sfplay~ to be used in an abstraction or

>> it’s used several times in the main patch, you get a "name already

>> Workaround: instantiate a [sfplay~] and never name it before saving

> Another workaround is to send the name message without argument.

I guess my problem is that I cannot fathom how to use sflist~ while using sfinfo~ , because not naming sfplay~ seems to disconnect it from sflist~ . And they can't all have the same name because then i 'get name already used' or name not found in Max Console.

It may be better illustrated in this patch

Ok so maybe helpful to other beginners out there, I found this bit from 2008. 

>>>> Yes, sfplay’s name is not an argument.
>> By the way, there is a problem in the design of this "name" feature in
>> [sfplay~]. When you give a name (with a message), it is stored in
>> the object
>> (open such a Max patch later with a text editor to check).
>> But there is then no way to say "no name, please".
>> Result: when you name a sfplay~ to be used in an abstraction or
>> bpatcher, if
>> it’s used several times in the main patch, you get a "name already
>> used"
>> error.
>> Workaround: instantiate a [sfplay~] and never name it before saving
>> your
>> abstraction patch.
>
> Another workaround is to send the name message without argument.
>

I guess my problem is that I cannot fathom how to use sflist~ while using sfinfo~ , because not naming sfplay~ seems to disconnect it from sflist~ . And they can't all have the same name because then i 'get name already used' or name not found in Max Console. 

It may be better illustrated in this patch


sfplay~ and groove~ both won't play files