Ableton Forum

ezelkow1 wrote:

skatr2 wrote:

Ableton Denver wrote: This is the typical lack of holistic understanding that is endemic with Ableton, speaking from 3+ years of foolish user group collaboration I have bimonthly stories recorded of correspondence and phone calls that make rational people want to cry. There is a huge disconnect on the true use patterns and via Live9 and absolutely the Push controller there is an additional migration to satisfy the rookie bedroom producers and a solid pattern of ignoring live (stage) performance.

BTW - thanks for the "scene" superclass in the remote scripts. Way to break all of our work.

ya know one would think someone with such an extensive negative background experience and opinion of a company as yourself, you would have ran the trial before you bought live 9. I'm honestly shocked you still are taking the time to complain with the level of problems, irritation, and disgruntlement you have shown with the company. If I was at that point, I would seek other venues for my loot than here.

I guess Ill just never understand this line of thinking of, ill just take it and not try to offer up suggestions and criticism that could make software that I have used for many years that much better for myself and everyone else that uses it

Im sure many people have demo'd it and decided not to use it because of these changes. Theres also plenty of us who, despite this flaw, still saw value in the upgrade along with the hopes that since so many other people also have issues with this, that it will be fixed in the future. If not, I can deal with it and work around it for the sake of loving the workflow of live and not wanting to have to learn an entire new software package; but do I want to sit back and not try to offer up suggestions and provide examples of problems in order to try to fix it, no, thats just stupid to not try.

Its not just bitching and moaning for the sake of complaining, its an attempt to show the dev team problems that exist and offer solutions to these problems, if no one voiced their opinion along with others then the software could keep heading in a direction that could be opposite what the actual end users want, and then ableton would stop seeing more and more loot and fall behind

That's the rational response To this discussion. By all means make suggestions that make your workflow easier. But as these forums get, don't go on tirades about how a b and c are wrong and that you wasted hard earned money when its what was there upon release. These people didn't waste it, they spent it on the upgrades they like and ended up resenting the ones they didn't pay attention to.

I better understand the issues with the indexing and hope they can incorporate a better option for those who may be collaborating and moving around data. It makes more sense to add either an index cutoff or non-indexed folders. But to demand it and expect it, well you are just getting over emotional toward a company involved in an industry that frankly is getting smaller as other companies catch up. Ableton is not the only game in town anymore and as much as many of us love how they've been over the years, people need to keep their options open when it gets to a point that they are having so many disgusted moments with a faceless company.

Those who pre-ordered couldn't demo. It induces such a response from purchasers.

Good news everyone - jsut lost another drive to the Live9 browser. That benchmark test I did killed the drive. (earlier in thread) http://imgur.com/I58YclQ

Working drive, folder was dropped into Ableton. Ableton scanned (forever). Ableton closed. Drive ejected. Drive mounted later, will not mount and attached image is of the repair dialog (this is happening to all drives in all formats Ableton touches).

About to loose it here! This is beyond any reasonable doubt the Ableton browser. This time I have isolated the use pattern and no other access was on this drive besides the Finder in OSX and Ableton Live9.

file under gotcha!

Does the dive reformat? I've had the browser scan 3 different drives now, and they're all still healthy.

you seem to be suggesting that Live 9 is somehow causing hardware damage to your hard drives. that is complete bullshit.

how are you connecting these drives to your computer?

Hi,

To answer a few questions from this thread:

- Offering a 'don't scan this folder' feature is not simple and not a quick fix. The browser is build to display data from a database, only. We can imagine a way to display data from the file system only, but this has to be considered as a feature of its own. Not only is it a technical change that's not too small, but we'd also need to provide clarity in the GUI about what is behaving as a registered folder using features such as fast search, filtering contents in Hot-Swap mode, and what is just showing files on the hard drive, possibly to way to move from one to the other "worlds". It is imaginable, but at this moment we are working on improving indexer performances because that is what may potentially impact all users and will clear the ground for other desires.

- We are working on speeding up the indexer with the goals that files show as fast as possible during an initial scan, and that there is no negative impact on each start of the program while folders are already registered. So far it is known that initial scan takes way too long, and that scanning for changes on each start of Live also takes too long, and may impact playback on OSX. These are the three things we are working on addressing.

Kind regards,
Amaury

Amaury wrote:Hi,

To answer a few questions from this thread:

- Offering a 'don't scan this folder' feature is not simple and not a quick fix. The browser is build to display data from a database, only. We can imagine a way to display data from the file system only, but this has to be considered as a feature of its own. Not only is it a technical change that's not too small, but we'd also need to provide clarity in the GUI about what is behaving as a registered folder using features such as fast search, filtering contents in Hot-Swap mode, and what is just showing files on the hard drive, possibly to way to move from one to the other "worlds". It is imaginable, but at this moment we are working on improving indexer performances because that is what may potentially impact all users and will clear the ground for other desires.

- We are working on speeding up the indexer with the goals that files show as fast as possible during an initial scan, and that there is no negative impact on each start of the program while folders are already registered. So far it is known that initial scan takes way too long, and that scanning for changes on each start of Live also takes too long, and may impact playback on OSX. These are the three things we are working on addressing.

Kind regards,
Amaury

Nice to hear that you guys are investigating the problem.
Instead of a "scan/dont scan" on each folder, I could imagine that two different sections "Places (indexed)" and "Places (browsing)" could do the trick, so the user has the choice to place the folder where he wants to ...

BTW, is it normal that all samples indexed didnt show in "samples" ??

androids wrote:

Amaury wrote:...

Nice to hear that you guys are investigating the problem.
Instead of a "scan/dont scan" on each folder, I could imagine that two different sections "Places (indexed)" and "Places (browsing)" could do the trick, so the user has the choice to place the folder where he wants to ...

BTW, is it normal that all samples indexed didnt show in "samples" ??

That's a solution for the GUI part that could work, yes. Closer to what I had in mind.

As for showing in Samples, only files from Packs and the User Library show in Categories for as of now, so yes it is normal.

Kind regards,
Amaury

Right so when using push we can only use the packs, so we are forced to spend money on live packs.

beatz01 wrote:@Amaury:

What so far has been ignored by Ableton is this:

The general conscencus seems to be

Make an option to switch indexing off

As long as this is not officially adressed, complaints will not stop.

Simple as that.

I agree and if the "OFF" switch became a reality, the whole thread should become "closed".

I taled about it in a phonecall with Abe's staff but at one point I've been answered that "commercial services" arent't able to take the call at this moment, I wasn't even thinking about what as now makes me scared :

1/ Don't care about our past little disagreemends, here we both consider this OFF switch as mandatory

2/ As customers we can do MY way : do with the new browser, no problems so far, may one but can't figure out if the crash was linked with the browser itself or the index file. Or do "no my" way : wait for the old fashion OR the new CHOICE option.

3/ Worry ? Yes I worry because I like the new it's true, but why the hell am I keeping my whole Suite 8 x86 + Library available next my Suite 9 x64, although it's useful for 32-bit/M4L devices reasons, because I like browsing the old way.

Here we should consider Ableton to be in a delicate situation : they promoted that browser. Their words are "NEW" or "FEATURE". This is on the marketing point of vue named an evolution. The "bug" encountered in a phonecall besides not being stating I wanted to discuss the "CHOICE" option with commercial hotline... All this thing makes me worrying about the time we'll have to wait until they put it on the guideline.

We didn't even asked for that "feature" dudes !

I'm sure Ableton is totally aware of what's mandatory in their duty, and in OUR rights. But unfortunately the "kill indexing" swtch would effectively be seen as "We recognize we did a mistake", from Ableton Staff.

To summarize : I did something in my upgrade process (the most part being leaving indexer doing its job the rest is waiting after launching Live, for 10min, before put my hands on it). I'm not "happy" because I'm sure I'll be disturbed some day by the new feature as it's called. So Suite 8 32-bit near in case. We are trying to manage with something we never asked to, even if I may have said "I wanted an indexer", we don't have to know what's an indexer in fact.

I suggest to all the following : spending less time to figure out what we don't understand or is just a BIG flaw on our workflow >>> rename the whole thread as "TO ABLETON STAFF : MANDATORY FEATURE MISSING" and do some sort of a class-action because even if a tech agrees with you in a phone call, his com/marketing mate will state some marketing language we don't care about.

(@beatz01 : Hoping I didn't disturb you with the post dude, and apologize for the french way to write in english, indeed, it can be difficult to read.)

Warm regards

Amaury wrote:Hi,

To answer a few questions from this thread:

- Offering a 'don't scan this folder' feature is not simple and not a quick fix. The browser is build to display data from a database, only. We can imagine a way to display data from the file system only, but this has to be considered as a feature of its own. Not only is it a technical change that's not too small, but we'd also need to provide clarity in the GUI about what is behaving as a registered folder using features such as fast search, filtering contents in Hot-Swap mode, and what is just showing files on the hard drive, possibly to way to move from one to the other "worlds". It is imaginable, but at this moment we are working on improving indexer performances because that is what may potentially impact all users and will clear the ground for other desires.

- We are working on speeding up the indexer with the goals that files show as fast as possible during an initial scan, and that there is no negative impact on each start of the program while folders are already registered. So far it is known that initial scan takes way too long, and that scanning for changes on each start of Live also takes too long, and may impact playback on OSX. These are the three things we are working on addressing.

Kind regards,
Amaury

Thank you Amaury. I'm sorry for posting something like "we should have the OFF switch for the new browsing style" when you as a staff's member is trying to solve people problems. Nice work from the technical staff. Please, is there a chance the "marking/commercial staff" could take in account the "kill feature" thing, because I'm sure you don't even have the rights to make it an option or write an allusion about it ?

Thanks again and regards Amaury

androids wrote:

Amaury wrote:Hi,
BTW, is it normal that all samples indexed didnt show in "samples" ??

Yeah I've been told by support that this was supposed to work (as it's also in the manual) but there were bugs in the behaviour that made them pull this feature for now Dev team are working on it.

Rosko wrote:Right so when using push we can only use the packs, so we are forced to spend money on live packs.

Good point.

I suppose you have to make your own pack if you use push ... ??

Files --> Manage Files --> Manage Project --> Create Pack

I did a quick search and push includes samples in its browser. When added to the places section of live, it will access that area to pull out personal samples and racks.