Warning: audio error: Already initialized in win simulator 2013.1225

Hello latest build today 2450

Windows 8.1 pro (not sure if that makes much difference as happened on Vista and XP and Windows 7)

Using laptop always. 

“Warning: Audio Error: Cannot open sound device for openAL”

Files to create sound (blah blah . wav)

AlMixer_init::Already initialized.

ALMixer_Init:build with SDL_sound: 1.0.1

ALMixer_Init: linked Dll version: 1.0.1

I cant get this anytime you want. Perhaps you could send me a debug version of Corona?

What kind of sound “card” does your laptop have?  (for that matter, what’s the brand and model of the laptop?)

Does Windows Update say the drivers are up to date for your sound card?

Do other programs (especially games) play sounds successfully on the computer?

Googling around some people have reported that something as simple as having the sound turned off in the Control Panel or system tray on some computers can cause the system to report a failure of the sound system (we use OpenAL as our sound library so I was looking for reports linked to that).

Its most definitely not the sound being turned off. I have had this problem for god knows how long spanning two computers. All I can say is the same as I have mentioned before. I always have up to date drivers, has always happened since your auto-reload on code change(although i turn that off now and it still happens when I manually reload. Sound ALWAYS resumes after I exit and re-open Corona and re-open the project.

Currently I have an Envy 17 . This uses an IDT codec driver it seems. Not heard of that before . 

This happened on my previous laptop while it had XP and Windows Vista on . That had a Realtek device I think. It was a Toshiba P200 17 inch 

Im sure its to do with Corona flushing out or reserving audio or something. Perhaps its not releasing the files properly. I mean if I can close Corona and open it back up with the project and it works fine, then the moment that you reload the project something isnt closing properly.

I know everyone can just close Corona if this happens but it effects other things from working and sometimes Im tweaking away for ages looking for the bug before I realize its this as sometimes the warning goes off the console.

For me it’s simple to reproduce I just enable my hd audio on my nvidia card and within a few minutes I will get the error until I reboot then it goes away.

I can also get this if I unplug and re plugin my hd ear phones

Daily Builds 2014.2401 and above have additional error reporting for the audio module so if you get this error I’d appreciate seeing your console output.  Include everything in the session (in a PM if you don’t want it visible to everyone).  Thanks!

Since this thread is apparently still alive, a quick update from my recent experiences:

I maintain all of my working code in a Google Drive-synced folder. Last week, I was working on one of my projects on my secondary Windows machine (7 Pro 64 bit). Everything was as normal, and I went to lunch and locked my workstation. Coming back, I noticed that Google Drive was in the process of syncing, but thought nothing of it. I started back working on a particularly annoying bit of code, and after a restart, I started getting those pesky audio errors.

Not putting two and two together, I assumed there was something wrong with my audio files and commented out all music in the particular scene. No joy. No matter what I did, from stopping play to niling references to the “music” module I have, had any affect. Then I stopped the Google Drive sync.

Wonder of wonders, the errors went away. I started the sync again, and lo and behold, the same audio errors.

This is far from scientific, but anecdotally, one might conclude that, if the audio file and/or directory which holds the audio file is in a state of flux (owned by the operating system, being modified, being scanned by spyware program, etc.) then one is going to encounter these errors.

Again, nothing scientific and I’m not at a point where I can stop and test my hypothesis, but it’s something to keep in mind if anyone gets these errors, and maybe gives a startpoint for Corona testing.

Based on how rarely this is reported I doubt that it’s as simple as a file locking issue though it might be some combination of that and a particular audio driver.  Try your setup with a current Daily Build and let me know what happens.

The same problem here. This issue is so long (even in the newest build) than even don’t remember if that was for ages ;(

 
As I said earlier:

Daily Builds 2014.2401 and above have additional error reporting for the audio module so if you get this error I’d appreciate seeing your console output.  Include everything in the session (in a PM if you don’t want it visible to everyone).  Thanks!

Saying “me too” will get us no closer to fixing this.

Hello latest build today 2450

Windows 8.1 pro (not sure if that makes much difference as happened on Vista and XP and Windows 7)

Using laptop always. 

“Warning: Audio Error: Cannot open sound device for openAL”

Files to create sound (blah blah . wav)

AlMixer_init::Already initialized.

ALMixer_Init:build with SDL_sound: 1.0.1

ALMixer_Init: linked Dll version: 1.0.1

I cant get this anytime you want. Perhaps you could send me a debug version of Corona?

What kind of sound “card” does your laptop have?  (for that matter, what’s the brand and model of the laptop?)

Does Windows Update say the drivers are up to date for your sound card?

Do other programs (especially games) play sounds successfully on the computer?

Googling around some people have reported that something as simple as having the sound turned off in the Control Panel or system tray on some computers can cause the system to report a failure of the sound system (we use OpenAL as our sound library so I was looking for reports linked to that).

Its most definitely not the sound being turned off. I have had this problem for god knows how long spanning two computers. All I can say is the same as I have mentioned before. I always have up to date drivers, has always happened since your auto-reload on code change(although i turn that off now and it still happens when I manually reload. Sound ALWAYS resumes after I exit and re-open Corona and re-open the project.

Currently I have an Envy 17 . This uses an IDT codec driver it seems. Not heard of that before . 

This happened on my previous laptop while it had XP and Windows Vista on . That had a Realtek device I think. It was a Toshiba P200 17 inch 

Im sure its to do with Corona flushing out or reserving audio or something. Perhaps its not releasing the files properly. I mean if I can close Corona and open it back up with the project and it works fine, then the moment that you reload the project something isnt closing properly.

I know everyone can just close Corona if this happens but it effects other things from working and sometimes Im tweaking away for ages looking for the bug before I realize its this as sometimes the warning goes off the console.

For me it’s simple to reproduce I just enable my hd audio on my nvidia card and within a few minutes I will get the error until I reboot then it goes away.

I can also get this if I unplug and re plugin my hd ear phones