The dreaded “sometimes” word comes into this support email (oh no!)
Sometimes when I launch Ableset, and then tell it to launch " the last Ableton Liveset", Ableset does successfully assess which last (more recent) LIVE project to load, but then goes into a tailspin and says “waiting Ableton to finish loading”…and never recovers.
Sometimes I can “quit” AS, and restart AS, and that fixes it. Sometimes a laptop reboot fixes it (but not always…odd).
And then, sometimes when I do the opposite, launch Ableton first, then Ableset, and sometimes Ableset will say “Connecting with Ableton”, followed by the same adventure .
In both these situations, I can go to Ableset Settings, and it says “Fetching License”.
Sometimes I can resolve this by logging into my AS account (by sending the lic#, then waiting for the AS email, hitting the link, and getting into my AS account). But today, that is not working.
I have tried this with my NordVPN on or off.
A reboot fixes it.
Hmmmm.
So my question is, on a computer that does not have this (sometimes) problem, does Ableset only need to get to the License file in the \appdata folder, or does AS need to have a Logged-In connection with the AS online User Account (and thus, it must have internet to connect)? Or perhaps is there some cookie/sometime that expires in X days?
{{ I am also interested in the answer from a Live GIG viewpoint, wondering about what I will need if a reboot is ever necessary…thanks Leo }}
— I have uploaded a log-package.
----note: I am a heavy Google Drive user, but my Ableset \appdata folder is not on “G:” (only some setlist .json files). And when my “G” drive fails, Ableton and all else craters (so my 1st guess is that I don’t think the “G” drive is related to the occasional endless “fetching” ).
- **OS and Version: Windows 11
- **Version of AbleSet: 2.7.5
- **Version of Ableton Live: 11.3.41 (I just noticed, I thought I had .3.3, but it looks like Ableton is now at .41 on this laptop)