From the documentation I see that there's ways to play, pause, and stop audio through the group IDs, but do the other commands work for those group IDs as well? I'm trying to fadeout all playing audio rather than hard-code the fadeout by hand but this:
<<audio ":playing" fadeoverto 3 0>>
doesn't appear to do anything.
Is the playlist method the only way to accomplish this?
Comments
All actions should be available to all track IDs, including group IDs, except where specifically noted—more on that below.
If you have tracks playing at that point, then that should have worked upon them. The only exceptions should be if either the playing tracks are playlist copies or you've found another browser snafu—though I just tested in all of the major browsers and it seems to be working as intended in all of them.
If the playing tracks are not playlist copies, then we have a conundrum and I need to don my deerstalker.
If the playing tracks are playlist copies—meaning those set up via <<createplaylist>> with its copy action or all tracks set up via, the deprecated, <<setplaylist>>—then the documentation for <<audio>> clearly notes that they will not be affected by group IDs—although, it should actually say that they will not be affected by the <<audio>> macro at all; I'll clear up the docs there. As to why, each playlist copy is an independent copy of the track in question which is solely under the control of its playlist. Just in case that's tripped you out, I've gone ahead and cleared up the documentation for all of the macros involved.
That's a hot-off-the-presses beta version. Any reason you're using that instead of a stable NW.js release?
It's what web2exe updated me to on its own. I went back and rebuilt it against 0.19.1, which was the last stable version I didn't have problems with, and that worked fine but for good measure I tried again with the latest version that it used previously and it worked as well.
¯\_(ツ)_/¯
I have found audio can be a bit finnicky so maybe it was just a glitch on my end. I don't even know anymore.
If it works it works though. No reason to rock the boat now I guess.
I hadn't heard of nw-builder, although web2exe has its own GUI which makes this all a lot easier to do. It sometimes switches the nwjs build on its own if I haven't moved to a more recent version in a while, but I didn't realise it was also building against a beta of Chromium as well.