Live 9 browser NIGHTMARE : this time it's enough !

[pencilrocket]

This library contains almost 500GB. It is used only for Sound effects.
http://www.blastwavefx.com/p2/The%20BLA ... _info.html

One thing that is clear is Live no longer supports browsing inside Live's browser.

[SuburbanThug]

Not the "go-to", no. But I've personally surveyed over 93% of all music studios worldwide and can confidently say that a at least 27% of those are rocking some form of Live. Perhaps once we reach 30%, simple folk like you would start to read about us in Cosmo. Then you'd wish you had been nicer to us in kindergarden. If you keep up with these racist and bigoted claims of yours, I'll start linking to someone else's SoundCloud in my signature. YOU WOULDN'T BE WHERE YOU ARE TODAY WITHOUT YOUR MARKETING TEAM!

Let me try to be crystal clear before I quit derailing this thread. I'm not saying that Live can't or shouldn't be used in the studio or that it isn't better at some things. I'm saying that as a DAW it is not ready to compete with Logic, ProTools, or Cubase. Close, but no cigar. The midi section is just now getting into shape. It actually has some really cool features now but a version or two ago midi could be a nightmare for someone trying to work quickly. As far as mixing and mastering go... still needs some work to attain a high level of usability. Dual monitoring??? I mean, damn. The native plugins in Live are frustratingly cramped into that little box. Don't get me wrong, it's nice to have everything on one screen but you can't even stretch that box open for a better view when you need it? Pretty great for the (pro) consumer, good for getting around in, just not ready for the big race yet.

[BoddAH]

Breaking news, indexing a 2.5 TB sound library with millions of samples takes a lot of time on a mechanical HDD.
More news at eleven!

In all seriousness I love the new browser. You can't blame Ableton for the hardware limitations of your setup. Indexing such a huge library isn't going to happen quickly, no matter how good the programmers are.

[androids]

Breaking news, indexing a 2.5 TB sound library with millions of samples takes a lot of time on a mechanical HDD.
More news at eleven!

In all seriousness I love the new browser. You can't blame Ableton for the hardware limitations of your setup. Indexing such a huge library isn't going to happen quickly, no matter how good the programmers are.

WhereIsIt create a browsable databse of my 'huge' lib in less than 45minutes.

Live is taking 13 hours ...

So what ?

[Blendton]

Breaking news, indexing a 2.5 TB sound library with millions of samples takes a lot of time on a mechanical HDD.
More news at eleven!

In all seriousness I love the new browser. You can't blame Ableton for the hardware limitations of your setup. Indexing such a huge library isn't going to happen quickly, no matter how good the programmers are.

WhereIsIt create a browsable databse of my 'huge' lib in less than 45minutes.

Live is taking 13 hours ...

So what ?

androids, I write in english for understanding purpose for all readers, and apologize in your case since I'm surely more accurate and understood in native language :

Live's, by extension Ableton'sabilities and capabilioties are focused on, that, this, and that thing.

That's why, for instance, you can read Ableton's recurring advising users to do their audio/video conversions with a more specific and specialized program.

But unlike that example above, we're not talking about some industy standard--made digital material being universaly usable and therefore being free to traveil from a program where it's born then another to apply X and one for Y, then back to Live for the end-product to continue being in progress.

Since any other program could, today, create that database eexcept Live, and because I'm sure you could understand Abletons staff is totally incompetent in that totally off-topic (because being largely far away from their ebd-user focused work) because creating a database is a more "OS-grade coding and programming" kind of work.

So I understand what Ableton lacks here : a dicated team to manage all "above Ableton Live's tasks" like database creating which is extremely relying on optimized and specialized source code.

I didn't find in any user/llegal/imprint/etc document, and I swear having checked all user available document, any company quoted being working in THAT domain of indexing/database managing. Not even in the list of techs and societies implied in Live's existence, where you can see everything from Steinberg for VSTs property or Microsoft for DirectX and DirectMusic, or Cytomic for borrowing some of their algorythms in Glue Comp.

So androids, if you should do a call to Abe soon, why not suggesting that thing to your interlocutor, asking for precisions about how the thing is managed as for today (in brief : lame) and how abbout collaborating with specialized partners since if not they could severly affect and destruct all what's had been built, but most important t heir image of a Live performing thing being disabled by a freeze-related matter being even not in their competences ?

Warm regards.