Archived

This topic is now archived and is closed to further replies.

OpenAL ... one or many updates?

This topic is 5129 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hey all, I''m just getting into working with OpenAL and trying to design it into my engine. I''m not sure how this works... there are functions alListenerfv() and alSourcefv(), which permit the developer to (respectively) update the players'' "ears" and ingame objects'' "sound emitters" (for lack of better terms). But should these functions be called once per frame? Once at sound play-time? Or does OpenAL assume that the ''fv'' pointers belong to live data that OpenAL reads constantly, internally? How many times, or how often, should the listener and sources be updated with alListenerfv() and alSourcefv()? Any help would be appreciated, as I am stuck designing this part until I understand this concept matrix³ [ email | web | apple gl | linux gl | opengl | freeglut | glui | lua ]

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
It''s been a few months since i last used OpenAL, but i believe OpenAL follows the state machine metaphor like OpenGL, so you should only change the values when there is a change.

It is likely that once you have set up your sound emitters, you wont need to change their values again unless of course they are moving objects.

I''ll double check when i get home later and post here, but im pretty sure you wont need to call them every frame.

Share this post


Link to post
Share on other sites