Alexandre, if nobody else sees this issue with the object it's probably ok? I noticed it because I was opening the file many times . It was a heartbeat wav fIle triggered by a heartbeat. I am wondering however if I open a file , play it , then open another file , is the first file closed when opening a different file? If not, that could be an issue.
I guess it doesn't close the file after playing
| I guess I can improve it then?
Em qua., 26 de nov. de 2025 às 23:04, Jim Ruxton jim.ruxton@gmail.com escreveu:
I figured out what the issue below was caused by. Following on what IOhannes said it turned out there were too many opened files. To play files with the Else player~ object I was banging open a file each time it played. I guess it doesn't close the file after playing and I only had to bang the player~ object rather than the open command again. It would be nice if possible to print out a message to the console saying the file is already open to avoid such crashes . Anyway all is good now. Thanks for all the suggestions of what may be causing the issue
Am 27. November 2025 03:59:06 MEZ schrieb Jim Ruxton jim.ruxton@gmail.com:
Alexandre, if nobody else sees this issue with the object it's probably ok?
I don't think so. you might be using the object ad extremum, but that doesn't mean, that is your fault.
it basically boils down to: does the object keep track of all the opened files and can make some use of them (in which case your probably *is* the fault of the user; or at least of the documentation), or is it a resource leak in the object (which is simply a bug)
mfg.sfg.jfd IOhannes