I use Ableset 3.1.3. on two Lenovo Laptops. One on Win 11, the other one on Win 10. On Win 11, the section cues during playback do work, the count-ins are there and everything is awesome.
Using the same show, the same Ableset config on Win 10, when playback is paused, the section cues are spoken (“verse”, “instrumental”, etc). But during playback, no countins, no sections are announced anymore. The settings are activated of course.
I’m syncing the project between two different PCs using a cloud provider, but I’m only running one of the two laptops per time. And I’m taking care that the sync is done.
Any ideas where to start? Can I debug the issue?
Does Ableset attempt any run-time optimizations, checks the CPU flag or something? Then Win 10 PC is significantly slower.
Thanks!
Please fill out these values to make it easier to troubleshoot:
I checked your logs and it seems that AbleSet wasn’t able to parse your project for some reason, but there were no explicit errors. Without the data from your project file, AbleSet can’t generate count-ins.
I just released AbleSet 3.1.4 which adds more logging around the parsing of project files. Could you try running this new version and send me another log package?
Hey @jankap, my guess is that this is a permissions issue of some kind. AbleSet might have sufficient permissions to access the project file on your other laptop, but not on this one.
Regarding your 2nd point, AbleSet can retrieve information about locators and clips directly from Live using their API which is why the announcements work when jumping between songs or sections while playback is stopped. However, for count-ins to work, AbleSet needs to know where each bar begins and ends, which Live doesn’t make available through their API, so it can only parse this information out of the project file.
I’m looking forward to your next log package and hope to be able to resolve this issue quickly
Oh yes, that might make sense. Didn’t know that there are two different methods to get the data needed by AbleSet. So that means if Ableton can read it doesn’t mean AbleSet can? Any chance to add those checks to AbleSet or is this already part of 3.1.4?
Indeed, I’m running as admin on the win 11 PC but I don’t want to run my stage/live account on win 10 PC with admin permissions. Also, the sync users might differ. I’ll check this out right when I’m back.
Is it recommended to run AbleSet using an admin account? Or is it more about the owner/permissions of the project file?
PS, is the project data format documented? Thinking about batch jobs/modifications via LLMs. It’s XML based, right?
AbleSet 3.1.4 now logs with more detail why a project file couldn’t be parsed, so if it is a permissions issue, we’ll see it in the logs. There might be scenarios where Live can access a file but AbleSet can’t, but I’m not too familiar with file permissions in Windows so I can’t say for sure that this is the issue.
It shouldn’t be necessary to run AbleSet as an admin, but doing so when the project file can’t be accessed might be a good way to find out if it’s actually a permissions issue.
Yes, project files are just large XML documents that are gzipped to save space. I don’t think there’s any documentation for it, but I found the structure quite easy to understand.
I just installed 3.1.4 and the error is gone. Which is weird because somewhere else you wrote there was no change but logging. Was there a change to the installer?
