Skip to content

Why does a sound have to be played first before setting the instance's volume and spatial position? #1768

@repulsio

Description

@repulsio

The Problem

Please see @singfisher 's comment: #1209 (comment)

I don't understand why the API forces us to have to play a sound first before we can set the instance's volume, spatial position, and more?

This causes the sound to play for a split second on its default settings, then the actual settings we want kicks in a split second later. This is extremely noticeable for spatial sounds, since the sound starts at some default position and then jarringly moves to the position we want a split second later...

Can we simply have the ability to set the instance's settings before playing it? We can't set it on the Howl, since that will apply the settings on all of its existing instances.

@goldfire I'd be super grateful you could please help here, thank you!


Possible Solution

Please see a possible solution for setting an initial volume in @singfisher 's comment: #1209 (comment)

Perhaps this workaround could be applied to setting an initial spatial position too.


Howler.js Version

v2.2.4

Affected Browser(s)/Versiuon(s)

Chrome 142.0.7444.60 (Latest)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions