And your egg breaker sample. Anything with sound. So finally this bug is 100% recreatable.
Which versions of Corona SDK are you referring to? Does the behavior revert back if you go back to the older version? The audio code hasn’t changed in a very long time so it’s quite surprising you’d see any difference between recent releases.
Has anything else changed on your system? New audio driver? Significant Windows update? I assume you’ve restarted Windows to see if that makes any difference.
I understand you can reproduce it on your system, what I need to do is reproduce it on a system here.
Ahhh. I recently only changed to Pro/Enterprise for other Corona reasons. I hadnt noticed my drivers are now screwed!
Okay then what we need to do is go back in time/pretend I didnt send that last message 
works now lol
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.
hi, i was also getting same issue, while i just some hours before started simulator.
but when i closed the corona simulator and again re opened then its working fine.
i don,t know what is exact problem
It always “fixes” when you re open simiulator. Im still getting it 9 months later. My guess is that on reload, the audio files/buffer/allocation or whatever is not getting released up on reload/code change so it tries to load again.
Same here. It hasn’t caused any significant problems for me. I suspect it has to do with high-bitrate files being cached, as BeatsnBobs references. Either way, a restart solves it and I’m back into lua coding.
Right now I am getting this error everytime I open a project. This has not happened before. I am now getting this on the console even if I exit Corona and restart with an app. This didnt happen a couple of days ago so its gotten worse since yesterdays daily build. "Warning: audio error: Cannot open sound device for OpenALWarning "…“Failed to create sound”… and then the same old error after about the audio being already initialized. repeated about 30 times for each wav file its supposed to be loading.
This is happening with the sample projects:AudioPlayer and Simple Mixer. Simple Mixer comes up with this error:
And your egg breaker sample. Anything with sound. So finally this bug is 100% recreatable.
Which versions of Corona SDK are you referring to? Does the behavior revert back if you go back to the older version? The audio code hasn’t changed in a very long time so it’s quite surprising you’d see any difference between recent releases.
Has anything else changed on your system? New audio driver? Significant Windows update? I assume you’ve restarted Windows to see if that makes any difference.
I understand you can reproduce it on your system, what I need to do is reproduce it on a system here.
Ahhh. I recently only changed to Pro/Enterprise for other Corona reasons. I hadnt noticed my drivers are now screwed!
Okay then what we need to do is go back in time/pretend I didnt send that last message
works now lol
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.