Bug in `ursina.audio` prevents loading audio files when in a different directory than root.

[jgreenemi]

Bug in `ursina.audio` prevents loading audio files when in a different directory than root.

[pokepetter]

The recommended project structure is this:

    +---project
        \---resources
        |   \---select-long.wav
        +---main.py

By default ursina will load things from the root directory or a directory underneath.
It doesn't normally make sense to hard code paths to external resources.
The reason for just using names to load assets is so you can sort assets into
folders or make compressed versions without having to change the code.

If you really do need to change the root folder however, you can change application.asset_folder to the path you want.

I can't get it to error silently, but I'll look into making a more descriptive error message.

[jgreenemi]

Thank you for the quick response! I lifted the main.py out of src and passing in os.path.join('resources', 'select-long') now loads and plays the audio file as expected. For a number of reasons I will continue to use my original project structure, and keep the bug open as os.path.join('..', 'resources', 'select-long') is a valid path that shouldn't be failing, regardless if it's uncommon to reference audio assets in this way.

I wasn't aware of the existence of "application.asset_folder", that is something I'll look into to better understand the canonical approach to loading audio files, and possibly other assets. Where can I find documentation describing its use, where it gets consumed, etc.?

The context around the reasoning for using names is helpful, I appreciate your sharing that! Can this be persisted somewhere in the code documentation? While the code explains the "how" of a decision it doesn't necessarily explain the "why". This benefit was not obvious to me as I didn't anticipate having to frequently change the format of existing resources, so much as changing their contents without changing the format (for example, it's more likely I'll change a wav to another wav with a different sound effect as opposed to changing a wav to ogg).

On the note about the error, are you saying you were unable to reproduce the error following the steps I provided? To be explicit, I want to know that a resource fails to load - but right now it appears to just print the fact that it failed to load, rather than actually throwing an exception. (The message could be more verbose about why it could not be loaded but that is beside the point.) I want to see an exception get thrown when a resource fails to load because this is an error state that needs to be handled. How a developer handles a resource loading failure in the code should be up to the developer, not swallowed by the library. Is this a behaviour from ShowBase, Ursina, or Panda3d?