I’m building an Ableset plugin using React for the UI. With a few tweaks to my webpack compiler and using createPortal , everything is working like a charm! I’m fetching the setlist from Ableset’s API since the song information has already been parsed. What is needed is each section clip’s end_time …

Hmm, that’s an interesting one! If you’d like to get raw data about all clips, you can use the /api/setlist/debug endpoint. This returns all six steps in which cues and clips are parsed: parsed: Step 1 – Concatenated points with meta. Clips following an auto cue are removed. deduped: Step 2 – Dedu…

I should read my own code more thoroughly haha :smiley: The parsed property already removes the clips following an automatically placed marker. I’ll see if I can add more information to the /debug endpoint, but in the meantime, it might be easiest to create an endpoint in your own script that queri…

Thanks so much Leo! I’ve been using an endpoint of my own but it seemed redundant since Ableset already had a parsed list. I’ll look forward to that clip information being included in the “/debug” endpoint whenever it’s convenient to add it. I can’t thank you enough for adding the scripts.js funct…

The latest beta of AbleSet ( AbleSet 2.4.0-beta.8 ) now includes a raw property on the /debug endpoint which contains a list of all locators and section clips exactly as they were received from ableton-js. Let me know if this helps!

Oh man, this timing couldn’t be better! I was in the middle of writing logic for a 2nd call to my ableset-js api. It’s awesome to have all the the data in one endpoint. Thanks a million!

@leolabs The only other thing that would seal the deal is if the activeSongId and activeCueId could be in this /debug endpoint. This may not fit into your specific usage but it’d sure be nice on this end! Right now, I’m just making another fetch() call to /api/setlist which has the above mentioned…

To remove the need for an additional call to the API, I could expose the internal data stores on the window object so you can access them from your scripts. I use TanStack Query to manage data from the API and that store is already updated in real-time so you wouldn’t have to open another socket to…

Those hooks would be incredible for the front end code! Unfortunately, I still need that information for my express() based code. The server side code is required to make Transitions work because I’m triggering jumps based on the offset length of what I’m calling “Auxillary Sections.”

Hey @RichardB , I’ve split your feature request off into a separate thread so we can discuss it there. I just released AbleSet 2.4.0 which exposes a bunch of useful objects on the global ableset object. Apart from the ones I mentioned in my previous post, I’ve added getSocket which returns an insta…

AbleSet Forum

Ableset Plugin - Setlist property

Support

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled