Sound doesn't play when created as an object about swiftysound HOT 5 CLOSED

@slifty This is exactly the reason why the object is released immediately. Creating an object and releasing it right after it's created is not currently supported but it might make sense in some cases. I'll think about it, maybe there is a point of retaining the object whenever it starts playing

from swiftysound.

Sorry -- it was just me doing something silly.

The sound object fell out of scope before the sound had a chance to resolve.

from swiftysound.

Hi! @slifty I'm facing the same problem when creating an instance of a sound object. How did you solve it?

from swiftysound.

@Fedenieto90 So caveat that I'm not an expert on Swift, but it seems that if you create the object within a method, the object loses scope and gets cleaned up immediately after the function ends. This is different from how things work out in, for instance, Node, where you can trigger a promise and it will resolve later.

I had to make the instance a class variable, so that it wouldn't get removed from memory right after the method finished.

Here is the commit / line where I played the sound -- BadIdeaFactory/arobotherapy@7de5bbc#diff-e3089959bce5859a9a8a8e6f0e5af7abR83

from swiftysound.

Thanks! 👍

from swiftysound.