Construct 2 Sound Inconsistency

I was wondering if anyone else out there is developing with Construct 2 and having similar problems with volume inconsistency for music? Sometimes its fine, and other times it drowns out the rest of my sounds. If you refresh the game its fine, but on the first play this happens often. I've tried playing the sound once, then restarting it after giving it a moment to load, but that doesn't seem to solve it either. Thanks, and I'd appreciate any help on this matter I can get.

Thanks for responding JHill. I don't think its a looping issue, unless I misunderstand your meaning. While the music track does loop, its a fairly long track. The volume problems are present from the beginning.

Using Construct 2 for a long time and I like to think I'm somehow good with it.

Unfortunately, I never encountered any similar problem to yours. I have a few ideas like:- You are messing up the music with some events- Try to keep the track of the music using debugging- Make sure sounds are Preloaded (and you are using latest C2)- With some devices, audio wont play at all unless the screen has been touched.- What JHII said. You have a silent track, but your code keeps adding another BGM tracks to the loop so you get the feeling of sound inconsistency. For example: at 0:00 you play BGM "nature" and its silent, at 0:01 your code play another BGM "nature" so you have 2 tracks running simultaneously and with each another it sounds like its getting louder.- Your sound device messes audio (there is an option like "communication muting" or something like this)

That's all I can think of. Try these things out. The best way to check it would be the debugger and filtering event sheet by "Audio" to see if by any chance you are not messing events up.

Glad to hear you got it sorted; I was going to recommend that. One of the (minor) issues with Construct 2 is that there's so many releases and they release so fast that stuff tends to get broken from time to time. Luckily, since they do release so fast, things also tend to get fixed relatively quickly!

Just wondering, but do games using the latest construct release pass QA? The double canvas bug for stock browsers is still there on older android devices(Samsung S3) with the newest Construct release, and it seems that fgl still uses the S3 for testing. Is the stock browser still used as part of the test?

On Aug 30, 2014, FGL_Dave said:

Maybe someone should recommend that Scirra switch to using howlerjs instead of the Web Audio API.

They should do - it's a known issue (though Construct 2 updates so fast we struggle to keep up). We do actually have a recommendation for how to fix that particular issue. The idea is you flip the opacity of the whole game back and forth between 1 and 0.999999, forcing the device to re-flush the canvas. This has a minimal impact on performance (almost none) and provided you have enough 9's won't have any visible effect, but it will fix the Galaxy S3 double canvas drawing issue.

One issue we haven't been able to figure a fix to is that the samsung devices' stock browsers seem to register two events for every touch in Construct 2 games - one about 1 second later than the real touch.

Anyway, all that said, since we know about these issues I believe we should be skipping over them during QA and allowing C2 games through!

They should do - it's a known issue (though Construct 2 updates so fast we struggle to keep up). We do actually have a recommendation for how to fix that particular issue. The idea is you flip the opacity of the whole game back and forth between 1 and 0.999999, forcing the device to re-flush the canvas. This has a minimal impact on performance (almost none) and provided you have enough 9's won't have any visible effect, but it will fix the Galaxy S3 double canvas drawing issue.

I'd like a fix for this as well. I'll probably look for a fix once I get my current games and its bugs fixed and working for QA.

FGL_Dave said:

One issue we haven't been able to figure a fix to is that the samsung devices' stock browsers seem to register two events for every touch in Construct 2 games - one about 1 second later than the real touch.

Construct 2 was recently updated to R181. It contains the fix mentioned above so I recommend updating to it. If you plan to use a version between R169 to R180 then make sure to use the fix if you want to support stock browser, Otherwise update to R181 which solves most problems already.

Construct 2 was recently updated to R181. It contains the fix mentioned above so I recommend updating to it. If you plan to use a version between R169 to R180 then make sure to use the fix if you want to support stock browser, Otherwise update to R181 which solves most problems already.