I think they can do better than the L8 Browser because lets face it - it wasn't very good really. There was no kind of decent reliable search and the database kept getting fouled and needed rebuilding all the time.spacecat wrote:I would be so happy if they added a legacy mode browser (browser of live 8 ) option...
Selectable from the preferences menu...
I would do (almost) anything for this...
What it did have is a simplicity in use . For example - showing more than one attribute column. Or the ability to have three browsing marbles set up to different locations. Or the ability to save custom folders directly, etc. In use is was quick, but functionally it was under-nourished.
Stepping backwards to L8 is not a good fix for the current problems.
Of course it's worried me for years that Ableton signed off on so many bizarre things in the L9 browser, like single attribute columns, Or the "search" is so poor that it can make users think the library is empty! The way users become resigned to using "Places" as a parallel user library for the bizarrely uncontrollable upper categories which are really filters on the Db. And many, many more. What worried me is that they didn't see them as problems!
But those issues can't be fixed by stepping backwards. Any resolution the many Browser issues have to be forward looking, and cater to Push and the API. But there it is. It exists now. To resolve it requires moving forward. I really really hope that there are now a few database people now on Ableton staff who will have spent the last 4 years rectifying past wrongs.
(to the tune of "Windmills of your mind")