Bug Fix and Suggestions: Jukebox Needs Love

Roll20 API layer we're scripting against simply doesn’t surface that metadata from the track to the sandbox, and it also doesn’t give you a “track ended” event. 1) Playing flag does not reliably reflect reality Need: playing should automatically flip to false when a non-looping track naturally ends (and this should be consistent). 2) No “track ended” event / callback for API scripts Need: Emit an event when a jukebox track ends (or errors) with track id and metadata. 3) No duration/length metadata exposed to the API Need: Expose duration (and ideally currentTime or position) for each track. 4) No playback position/time controls Need: Add readable currentTime and writable currentTime (seek) or at least read-only position. 5) Softstop semantics unclear / insufficient for SFX Need: Add support for multiple instances of the same SFX (virtual instances), or provide a restart/retrigger flag that reliably restarts from 0 and plays once. 6) No API-visible “is actually audible” indicator Need: A truthy signal from the audio engine like isAudible, isActive, or playbackState (playing, ended, stalled, etc.) 7) Inadequate documentation of jukeboxtrack fields & guarantees Need: Document all jukeboxtrack properties (readable/writable), lifecycle, event timing, and any known limitations. 8) No Mass Track Management Needed: Interface for editing, adding, remove tracks on a scale that's not one at a time.

Guess.. we just don't answer because Roll20 devs don't intend to do anything to fix these problems or they just don't know how?

HI Aaron! Have you created a Suggestion in the suggestion forum for this? Is so, posting it might come up with enough votes, including mine. Have you filed a  Help Center Request  for the points which are actual bugs? I'll also see if I can direct some attention this way. In the case of of the devs, it's difficult to tell. They have long lists of fixes and improvements that they are constantly filling or amending, so it's difficult to tell where any particular project's priorities are. It might seem like they are ignoring project A, but that might be because the development focus is on project B and C, which requires groundwork to be laid first with projects D, E, and F.  Or that the whole project might require an overhaul of the underlying engine.  It might also be that of the things you list above, that 5 of the 8 are rather easy to implement, 2 are considered problematic, and 1 requires a complete overhaul of something else. And that rather than apply a half fix, the whole project is slated for a later sprint. This is all speculation on my part of course, based on past projects. Nevertheless, I'l see if I can find someone to answer this thread.

I appreciate the response. All I wanted was someone to say We have seen this, and we intend to fix it later or we never intend to fix it. I didn't know which board to put this on. I just figured the bugs I pointed out were more important than the suggestions.

Jukebox DEFINITELY needs some attention or should I say rewriting? There is STILL no option to sort Playlists (neither in nor outgame; manually or automatic). If you upload a track highlighting STILL stays on "add to game" instead of highlighting the option where the cursor hovers over... and the interface is outdated to say the least... When will the jukebox finally be updated?!