Ah, that's a shame. Guess I'll just have to remove Windows XP from the compatibility list. We're releasing on Steam next Friday.
Please have the tester running on Windows XP to try again with this plugin. It's kind of makeshift and rushed a bit, but with my testing it was working out alright. The only issue I had with this is that BGSs looped slightly oddly, like there was a gap between it looping, but I did not notice the same thing for BGM. This plugin should also allow Internet Explorer to play web games alright, so I suppose I might still work on and maintain this plugin, but so far I have not decided.
Not the log, no. The DOM is the Document Object Model, and is the way your web page is structured. When you press F8 and go to the Elements tab, that's pretty much the DOM, it shows you all the HTML tags on your page, what order they're in, and such. I originally had some issues with the Html5 audio not saying that it had finished loading into the game, so I thought that maybe it was because the audio tags weren't in the DOM, but it was actually caused by something else. I realized that around the time I was posting the plugin for you, but decided to leave it as it is for now. If it works for you, then it's doing its job, so there's no need to change it, currently. Like I said, if you have issues with it later on, please just let me know so I can look into fixing them.
What is "it" that said WebAudio wasn't supported?
I think that it should be ok. What I basically did was just copy the Html5Audio class, and pop a '.prototype' on ever Html5Audio.<whatever> bit, and then I had to change the AudioManager a bit to accommodate the change, since it didn't expect there to be instances of Html5Audio. May I ask why you were thinking about using Html5Audio instead of WebAudio?
var CrossfadeSample = {};CrossfadeSample.play = function() { try { context = new webkitAudioContext(); this.gainNode = context.createGainNode(); } catch(e) { alert("Web Audio API is not supported in this browser"); } bufferLoader = new BufferLoader(context, [ "sounds/organ-echo-chords.wav", "sounds/blueyellow.wav" ], finishedLoading); bufferLoader.load(); var ctx = this; function finishedLoading(bufferList) { // Create two sources. ctx.ctl1 = createSource(bufferList[0]); ctx.ctl2 = createSource(bufferList[1]); // Mute the second source. ctx.ctl2.gainNode.gain.value = 0; // Start playback in a loop ctx.ctl1.source.noteOn(0); ctx.ctl2.source.noteOn(0); // Set the initial crossfade to be just source 1. ctx.crossfade(0); } function createSource(buffer) { var source = context.createBufferSource(); var gainNode = context.createGainNode(); source.buffer = buffer; // Turn on looping source.loop = true; // Connect source to gain. source.connect(gainNode); // Connect gain to destination. gainNode.connect(context.destination); return { source: source, gainNode: gainNode }; }};CrossfadeSample.stop = function() { this.ctl1.source.noteOff(0); this.ctl2.source.noteOff(0);};// Fades between 0 (all source 1) and 1 (all source 2)CrossfadeSample.crossfade = function(element) { var x = parseInt(element.value) / parseInt(element.max); // Use an equal-power crossfading curve: var gain1 = 0.5 * (1.0 + Math.cos(x * Math.PI)); var gain2 = 0.5 * (1.0 + Math.cos((1.0 - x) * Math.PI)); this.ctl1.gainNode.gain.value = gain2; this.ctl2.gainNode.gain.value = gain2;}; Funny, I was just reading about this yesterday. you see, NwJS uses Chrome 41. Support for "webkitAudioContext" was dropped after chrome 36m. You just need to drop the webkit prefix.
