Hey @Basstor,
Let’s go through both issues.
Regarding Canvases in older versions: Yes, this is known. A Canvas that has been opened or edited in 3.2 can’t necessarily be opened by older versions as of 3.2 Beta 1.
For the future, I’d recommend two things:
- Keep a backup copy of your Canvas files before opening or editing them in a beta, especially on a redundant setup.
- Make sure all machines in your rig (studio computer and both stage laptops) run the exact same AbleSet version.
Unresponsive setlist on beta 11
To figure out what happened here, it would help to know a bit more about your stage setup:
- Were you controlling AbleSet directly on the laptop running Live, or from a tablet or another device?
- How are your devices connected on stage: a network switch, a router, WiFi, or a direct cable?
- Are you using AbleNet between the two stage laptops, and were both of them running beta 11 at the time?
- Did the issue happen on both laptops or only on one of them?
- Have you been able to reproduce it since, either on stage or back in the studio?
The most useful thing would be to try reproducing the issue the same way it happened at the show (same laptop, same project, same way of connecting and controlling AbleSet), and then create a Log Package right after it happens.
You can create a log package by opening AbleSet’s icon tray, clicking the gear icon, and then selecting “Create Log Package”.
Please make sure to include your project files as well (just the .als files, no audio needed).
To send the files, you can upload them to AbleSet’s support inbox.
I’m looking forward to your reply!