Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

Roll20’s API cannot see or delete items in Manage Audio → My Audio. That’s an account-level library, not a game object.

This is extremely annoying because under My Audio library it doesn't allow you to just simply check audio you want gone and hit a single delete button. Instead you have to click on the name and then click on the trash can and then confirm the delete just to delete a single audio file. Am I doing this wrong or is this just how it is? I'd apprecaite any insight or help on this matter as the current system allows you to drop alot of tracks to the library but doesn't allow you to delete as easy and you can't write a script to help with that at least not that I have found. 
You'd also think there would be an easy way to conserve on space by making it easier to delete tracks which take up a good amount per file compared to other file types. :/
1770176911
Victor B.
Pro
Sheet Author
API Scripter
My Audio interface was done quickly years ago because of sudden and unforeseen change.  And though they did a good job considering the speed of development, it could use some love.  Mass management of tracks is missing completely.  Select tracks, delete or select tracks and assign to a playlist.  Something that shows the playlists a track has been assigned to.  These are really needed if you have hundreds or in my case, thousands of tracks.  Right now, it's a very labor and error prone effort to manage audio.  
Roll20 API layer we're scripting against simply doesn’t surface that metadata 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.