tha same goes for me… this new beta is making this startup error wherever I install the beta
I have this same thing happening as well
Hi Leo, short feedback to Setlist import from Bandhelper.
RTF documents still not possible to import by Finder. (See screenshot)
By Drag´n`Drop nothing happens to the Setlist. Only the setlistname changes correctly but no files get activated.
Also if there are songs that start with a number (99 Red Ballons) an error occurs.
Hey @ioi, @Gerson_Benjamin_Sobe, and @iamderkis,
I’ve just managed to reproduce this issue on my end and will release a fix with the next beta soon 
2 Likes
@Michael_Sommerer that’s strange. Could you DM me the RTF file you’re trying to import so I can try to reproduce this issue on my end?
1 Like
Installed the latest beta on my MacMini M1 3hrs before the gig. Everything worked. Selecting songs, lyrics scrolling and all of that stuff. The only thing that didn’t respond was the “Play” Button.
I noticed that during the gig itself. I normally start/stop the songs with a midi footswitch but noticed that the Start/Stop button on my iPad didn’t respond for some reason.
I used Beta 3.0.0-beta.4 before, which worked ok, (except that sometimes a song would look like it’s selected, when it wasn’t. That’s why i decided to update.
Everything else worked flawlessly.
Any idea what might have caused this?
I don’t have the MacMini M1 with me, as it’s built inside our tour rack.
Are you using the Canvas view? If so, I had to update the buttons I had pre-existing this beta so that they worked. Just had to make them an OSC Button again (now there’s options for different types of buttons).
Oh, I’ll check on that. Yes, i created a canvas view with setlist on the right, lyrics on the left and transport controls on the bottom center.
I used the canvas view since the day it was released. So it became second nature for me to use it, that i thought it was a default layout 
One more thing:
No matter how many setlist i save, when i click “load setlist” only the most recent one is displayed. As if the previous setlists are gone.
Aber they being stored within the ableton project file?
I’m having a few issues since moving from .10 to .13
Not sure if these have already been submitted yet
The track lengths are not calculated correctly - sometimes a song that’s over 3 mins shows up as maybe half the time
‘Add a song’ in set list view only allows for the text to be selected when clicking - instead of the entire bar
Had lots of disconnections and drop outs when using a wired Ethernet set up to a 2nd MacBook running chrome on canvas mode (I’m not 100% why this is happening as I updated a few things on my 2nd MacBook so it could be another issue)
The browser keeps scrolling past the screen - kinda hard to explain but I’ll try and attach an image
Really enjoying Ableset 3 so far! I need to explore canvas mode and build a layout that includes OSC and MIDI buttons for extra control within my set up
Hi Leo,
I am using the windows version.
Unfortunately the mode “Multi-File Project” seems not to work as planned. It worked without any issues until Beta10. Now in Beta13, it stopped working, although my project folders worked flawlessly before:
“Your multi-file project folder doesn’t contain any project files or doesn’t exist:
E:\AbletonLiveProjekte[…]
Add some project files or disable the multi-file project mode to use AbleSet.”
I am not able to work around this error.
Additionally, I get the same JavaScript Error that was already posted by another user.
Anyways, AbleSet is fantastic and I am looking forward to beta 14 
Best Regards
Dennis
I’m having an issue with this beta where sometimes when I tap a button on an iPad, it doesn’t register and only brings up the hidden buttons of the canvas. I was having this issue in an earlier beta and it was fixed, but I’m having issues with it again.
Secondly, I’ve double-tapped to try to bypass this above issue and actually tap the button, but then it zooms in that section of the canvas and I cannot reset it back to normal zoom. I’m aware that it may not be an Ableset issue, but rather Chrome, but thought I’d bring it up anyways.
I’m loving the new input box, I’m using it to input a custom BPM at the moment!
Just having an issue with it when exiting out of the keyboard on an iPad, the screen is permanently shifted down.
Thanks for your help in advance!
Hi! Thanks for all the work! Ableset 3 is working pretty well for us, but on the new beta, two older iPads (8th and 9th generation IOS 12.5.7) don’t seem to load anything. I’m using Safari as well as chrome and nothing. A loading screen appears, but nothing happens. Do you know if it’s a bug or a problem on our side? Thanks a lot!
Hey @Dens82, thank you for reporting this!
This has to do with the JavaScript error you’re seeing. I’ve fixed it and will release a new beta soon
1 Like
Hey @Adam_Molinaro, thank you for reporting these issues!
I’ve tried to reproduce the button and double-tap issues on Chrome, but couldn’t get it to behave in the way you described, unfortunately. If you like, could you send me the canvas you’re experiencing this with? Maybe it’s related to that.
The scrolling issue with text fields seems to be specific to Chrome on iPadOS, it doesn’t happen on Safari. I’ll see if there’s a way to fix it, but in the meantime you might be better off using Safari
1 Like
After changing back to beta .10 I’m still having drop out issues with my 2nd MacBook so I think it’s an issue with the LAN rather than Ableset 
1 Like
Mr. Leo already explain he already worked that error and will release a fixed version next beta…
Hey @Michael_Sommerer, thank you for the RTF file!
I’ve fixed the file picker issue and will release it with the next beta. Regarding the error with “99 Luftballons”, I couldn’t reproduce it on my end, unfortunately. What kind of error do you see exactly when you try to import a setlist that contains this song?
I’m looking forward to your reply!