very odd prob with saving presets.

[Stromkraft]

I did this simple test:

With Activity Monitor running with ableton in the search box:

• Add new empty effects rack
• Save rack

Result: I get the beach ball

Ableton Index in Activity Monitor only uses one percent but it's interestingly NOT responding. I kill it and beach ball goes away and rack is saved without any issues. Can you see if you can repeat this?

[topaz]

Permissions are all set ok.

I had some melda plugins in there. But it has happened before with various plugins.

Interestingly I had one Melda plug-in in my chain too. I doubt that it's an issue involving VSTs, but since I had permissions issues with it I can't rule that out and VSTs were in my chain. Hmmmm.

Can you verify your permissions? I'm redoing that now. You know how to do it?

[Stromkraft]

Permissions are all set ok.

Mine as well. But the Ableton Index does seem to be involved. Please do my test.

[topaz]

Will test at studio tomorrow

Permissions are all set ok.

Mine as well. But the Ableton Index does seem to be involved. Please do my test.

[Stromkraft]

Will test at studio tomorrow

OK, I just sent these results and an Ableton Status report file to Ableton Support. I'm not certain we are having the exact same error behavior, but if Ableton Index is involved I suppose the exact behavior could be triggered out of different reasons and also give somewhat different symptoms.

I'll try the same test 9.1.7b3now.

[topaz]

Yes, with indexer quit (before trying to save any racks) no problems so far.

I did this simple test:

With Activity Monitor running with ableton in the search box:

• Add new empty effects rack
• Save rack

Result: I get the beach ball

Ableton Index in Activity Monitor only uses one percent but it's interestingly NOT responding. I kill it and beach ball goes away and rack is saved without any issues. Can you see if you can repeat this?

[topaz]

looks like this is down to Live 9's new indexing browser.

in mine and many other users opinion one of the worse moves ableton ever made, next to not giving us a better Proper Mixer and UI.

[Stromkraft]

Interestingly, I did not get the same result in Live 9.1.7b3 where I had no such issues. Perhaps the Ableton Index has already been updated in problem areas? Can you people with these issues please also try saving the same thing in Live 9.1.7b3?

[topaz]

Thanks for all your help

I cannot risk using a beta right now (important projects) but hopefully 9.1.7 release will have fixed this.

Interestingly, I did not get the same result in Live 9.1.7b3 where I had no such issues. Perhaps the Ableton Index has already been updated in problem areas? Can you people with these issues please also try saving the same thing in Live 9.1.7b3?

[Stromkraft]

Thanks for all your help

I cannot risk using a beta right now (important projects) but hopefully 9.1.7 release will have fixed this.

Yeah, but there's no need to open your current project in it. In both Live 9.1.6 and Live 9.1.7b3 I started a new empty project and made a new empty effects rack. I'll keep communicating with support on this, but my experience and the problem behind it may be different from yours. If you and others can do the same chances are greater Ableton can nail this down.

[mholloway]

Guys,

the "Uknown File ID" message can happen when saving any kind of file to the user library. I've had it happen with clips, instrument racks, FX racks, native plugins, third-party plugins, whatever. The issue isn't the device, it's either Live's browser, or OSX (as this is clearly a Mac specific problem), or some combination of how Live's browser interacts with OSX. Since the browser is making changes to your OSX folder structure on some level, the latter option seems likely.

Other times the message appears, when using the User Library:

1. adding folders inside the user library
2. moving folders inside the user library
3. renaming items inside the user library
4. moving items inside the user library

again, this clearly isn't about the devices, it's about the Browser, and more specifically the User Library in the Browser, and the interaction between that and OSX. Somehow ableton has trouble actually updating the folders / files within OSX via the browser.

no solution here yet. the error message is hard to predict: I can get it five times in a row when attempting to save a clip (or anything else) to the browser, but then on the next try, it might work with no problem. I'd say in general it happens 60% of the time though, which is awful. I archive my stuff constantly so this is really a pain in the ass.

[David.L]

Same problem here, it's annoying...

[mholloway]

I updated to a new Mack Book Pro earlier this year, and have never received the Uknown File ID error since. Which is good, of course, but it's not a solution, because I'm sure it would still be happening every day on the old system.

It seems like there is a point on any OSX system where Ableton's User Library becomes corrupted. I fear the day when I get this message for the first time on my new system. On the old system, it now happens more often than not.

I was e-mailing directly with Ableton regarding this issue earlier this year, among other problems I was having (some of you may recall the "ableton has become unstable..." thread I started, which Ableton eventually closed). They were able to address a lot of my issues. This one, however, was never solved, and only the fact that I happened to buy a new computer has gotten me into the clear. Hopefully it stays that way!

-M

[topaz]

Almost 2 years later and this problem still exists in 9.6

will it be there in 10 ?

[Stromkraft]

Almost 2 years later and this problem still exists in 9.6

will it be there in 10 ? :mrgreen:

I'd say it still occurs, not that it exists as that denotes it's commonly happening most of the time. At least in my case, it occurs very seldom (like once a month tops) and my workarounds for this issue work out every time too so the net effect is negligible for me. Typically I save a lot of settings during some periods, though most are from the VST or AU itself. It still is irritating though.