Ableton Forum

hps909 wrote:

timothyallan wrote:Sonnox limiter AU cant be dragged from the browser anymore, and all stillwell AU's now crash it. :S
Two things I use all the time.


edit: yes I have filed bug reports

VST tim?

Yeah, vst works. AU's are so much warmer though

starving student wrote:

kb420 wrote:

timothyallan wrote:according to the Abes, yep.

When will this madness end?

when you fix the disk drive on your asr

How in the hell did you remember me talking about that?

Whew. It's stating the obvious but the differences in performance are always staggering.

I don't envy the Abes in these trying times one bit.

LoopStationZebra wrote:Whew. It's stating the obvious but the differences in performance are always staggering.

I don't envy the Abes in these trying times one bit.

well, since this is a kiss ass thread... It is difficult enough to keep up with developing at a strong pace on one OS with its patches/service packs and new versions, they're doing two. Yes, there are toolkits that make that easier, but still, you have a lot more work to do.

kb420 wrote: when you fix the disk drive on your asr :mrgreen:How in the hell did you remember me talking about that?

you kidding, you don't think you're just some letters and numbers on the internet now do ya




@:ok so what's the concensus here are the problems just with AUs and macs or what, everyone saying that they have no problem are you on mac or pc?

I posted my experience in the release thread.

http://forum.ableton.com/viewtopic.php? ... 2#p1051772

To sum up, my gig the other night with 8.1.1 didn't crash or glitch; yet editing parts with EastWest's Play engine has caused critical error crashes three times during session. While it worked for me in a performance situation, I had to consciously modify my set's original design and increase the buffer size to guarantee stability.

If I could go back to 8.0.9 or an earlier version, I would.

Tone Deft wrote:for me it's definitely the worst performing release yet.

I haven't had the problems you mentioned (LP has been outstanding) or crashes but I found out yesterday my previous buffer settings slow Live to a halt at 192kHz. it seems to be OK with a small buffer at 48kHz, that will be today's pet project.

I had a 'corrupt .als file' a few days ago, Ableton Support sent me a corrected .als the next day.

Werent you posting a while back saying that you were having no problems and that people who were complaining about live's performance should reconfigure their systems and learn a bit more about what was going on under the hood (paraphrased). . .

Sorry to hear that you are having issues with it, just goes to show that some of the problems that *some* of us are having are not necesarily user related. . .

I am not so sure if this development crew can continue as they do. They are fixing one problem and cause more.
I suggest that they do far more tests before releasing. This is turning into a nightmare.
Not a happy customer.

Things are working alright, but I still get lots of crashes each day. Usually either when loading a VST instrument when one is already loaded on the track, or switching presets in a VST or something.

How do you make a crash pack once it's out of beta anyways?

glitchrock-buddha wrote: How do you make a crash pack once it's out of beta anyways?

Send the log.txt and the crashlog in a zip file to Ableton.
Include the time when the crash happened so they can pinpoint the problem in the logs which keep track of all your sessions. And the regular info like what happened on what system in which version.

Here's how to find the log file (Live 6.0.9 or higher):

* Select "Get Support..." in the Help menu
* Click on the link "Show the Preferences folder" in the lessons window on the right side
* Attach the log.txt file from the preferences folder, preferably as a .zip attachment

For more info http://www.ableton.com/pages/support/co ... al_support

hoffman2k wrote:

glitchrock-buddha wrote: How do you make a crash pack once it's out of beta anyways?

Send the log.txt and the crashlog in a zip file to Ableton.
Include the time when the crash happened so they can pinpoint the problem in the logs which keep track of all your sessions. And the regular info like what happened on what system in which version.

Here's how to find the log file (Live 6.0.9 or higher):

* Select "Get Support..." in the Help menu
* Click on the link "Show the Preferences folder" in the lessons window on the right side
* Attach the log.txt file from the preferences folder, preferably as a .zip attachment

For more info http://www.ableton.com/pages/support/co ... al_support

Ok, finding the log.txt file is easy enough. But where's the crashlog?

glitchrock-buddha wrote:

hoffman2k wrote:

glitchrock-buddha wrote: How do you make a crash pack once it's out of beta anyways?

Send the log.txt and the crashlog in a zip file to Ableton.
Include the time when the crash happened so they can pinpoint the problem in the logs which keep track of all your sessions. And the regular info like what happened on what system in which version.

Here's how to find the log file (Live 6.0.9 or higher):

* Select "Get Support..." in the Help menu
* Click on the link "Show the Preferences folder" in the lessons window on the right side
* Attach the log.txt file from the preferences folder, preferably as a .zip attachment

For more info http://www.ableton.com/pages/support/co ... al_support

Ok, finding the log.txt file is easy enough. But where's the crashlog?

Its in the folder named "Crash" in the same place where the log can be found. If there isn't a .cfg file or such a folder then there is no crash log.

timothyallan wrote:Sonnox limiter AU cant be dragged from the browser anymore, and all stillwell AU's now crash it. :S
Two things I use all the time.


edit: yes I have filed bug reports

I'm glad I caught this post, I was about to upgrade.