Ableton Forum

Hi guys, each time I add a new track in Push it helpfully tells me there are no devices loaded and I must hit browse. Trouble is, each time I do so, I then have to wait at least 40 seconds before the menu will apppear on Push's screen. And if I then want to scroll down to Places, I have to wait another 40 seconds before that Menu will appear. In the meantime, the Live screen on my computer freezes. I don't think this is an issue with my Macbook pro, which otherwise works superfast and has plenty of spare storage/memory etc (I turn wifi off and shut down all other programs - same problem). And this has happened pretty much since I got my Push back in October. Moreover, it doesn't happen only when I am beginning a session, but all the way through it. Does anyone else have this problem/did anyone manage to solve it? I've tried using a different USB cable into the Macbook but no luck there either. Could it be connected with where I have my Live content stored? Does it look in the default folder first? (I moved mine some time ago)
Thanks guys

Slow as hell here as well...Takes 5-10 seconds to load categories and such....thus I never browse on the Push. Until they fix all the issues and implement standard features, I can only use it as your "classical" MIDI keyboard. Sorry, no solution here.

that's not normal behaviour though. the forum would be full of complaints about it if it was.

Hey guys I solved this by following miekwave's advice on another thread. What i did was to shut down ableton (or force quit which was pretty much the only way to avoid waiting 20 mins) locate the most recent files.db file for ableton (i used easyfind for this) then delete it. Then restart my MBP and restart Live. Live is now working great and so is Push. By the way, I had also moved my user library and some other items away from their default paths. Although in theory you should be able to do this without problems, when I moved them back this also helped with Push's browsing latency.
Hope some of this is useful

Nice to report back.

There have been issues since Push was released with the new DB system if it gets data corruption it could cause massive slowdowns and other weird behaviour. I know they have been improving on it a lot and personally I haven't had any issues with massive librarys, only a couple of seconds when adding a new instrument which with over 30,000 preset files and at least 100,000 sample files is acceptable to me.

What would be handy is a simple "db flush" button in the settings which could delete the database so it could rebuild in the event it had a big issue.