Developing app for NodeWebkit here. Currently I have a looping music that requires looping, but it got a long intro that is not a part of the loop.
For example,
This music here got a very long intro of 69 seconds, and at about 4:02, the music loop back to the 69th second.
I got a music like that, so I would like to check the music's time position every tick, and if the music exceeds certain time, I would like to seek back by x seconds to make it sound seamless. These could be simply accomplished with Audio.PlaybackTime("music") and { Seek Tag "music" to x seconds } event.
However, I notice that sometimes "seek to" causes the music to stop playing for several hundred millisec and it's as if the program requires a bit of time to load this particular part of music into memory first. It may or may not happen, but when it happened, it is not good for looping music. Music should be seamless.
Yet I found one possible hack for this, and that is to import the music in as a "sound effect" instead. This time, the music runs flawlessly with "seek to". I can "seek to" anywhere and there are no stuttering.
However, this hack comes with the following penalty: high memory usage and longer preload time. Instead of less than a sec preload, this time, it takes about 3-4 seconds. (My music is 7 minutes long) Checking into Task Manager, I see that the Node Webkit takes 220 MB memory now. On the contrary, it was only 61 MB, when I imported this music as "music" and not "sound effect".
While this hack works, the memory consumption just for one music alone is way too harsh, and I got other music as well. I can accept the 3-4 seconds preload time, but not the memory consumption with only just one music. Is there a way to unload or are there some better alternatives for this?