In My Movie, we let players play audio from AssetService:SearchAudio. I track LogService.MessageOut to give a popup if a user doesn’t have access to use a given sound. Through this, I have discovered that the results of AssetService:SearchAudio very very frequently give you audio that cannot be played in the place. It should never do this.
2 Likes
I’d argue that it should still be able to return audio which is not granted permission to be played because there are solid use-cases for using the API in plugins. Having conflicting behaviour between the API being used in plugins vs. in experience would also be odd and confusing for many developers. Plus, in some rare cases, the API may be used for searching audio in-experience but not necessarily playing it; for example, a song suggestion feature which allows players to suggest songs to the developer to implement (playing the song would be nice to have in this case but certainly not necessary so it is a feasible usage of the API).
Perhaps an option could be provided that omits these results, but it shouldn’t be the only behaviour for the API. The current behaviour should at least remain as an option for the many use-cases that rely on it.