Live 8.2.2 out now

[3dot...]

spoke too soon ...
back to 8.2.1

[nuxnamon]

8.2.2 definitely isn't as stable as 8.2.1.. getting random crashes of sort that wasn't happening before.. i say random because i can't reproduce them.. i'll stick to 8.2.1 for now..

[ze2be]

spoke too soon ...
back to 8.2.1

Dammit, I had my hopes on that one. Shold I still try to do it? Im to drunk atm, but tomorrow morning perhaps? (deleting prefs file)

[housemusiclover]

8.2.2 demanded a re-authorization, even though i had an authorized 8.2.2b5 installed...

[xzusa8ky]

Optimist's!

[3dot...]

spoke too soon ...
back to 8.2.1

Dammit, I had my hopes on that one. Shold I still try to do it? Im to drunk atm, but tomorrow morning perhaps? (deleting prefs file)

meh...turned out to be pretty useless.. don't bother...

[kb420]

Is there going to be another bug fix???? It seems there are still problems with 8.2.2.

[coldbuggin]

I'm getting way more crashes with this one.

[XSIMan]

Running on Windows 7 64bit
Ableton Live 8.2.2

Crash crash crash!

Whenever I tried to close U-he Zebra 2.5 vst so I could open another it would crash and the crash report doesn't work.

Seem to have solved it by starting Live 8.2.2 in administrator mode. 8.1 was unstable unless I started it in Administrator mode hope this info helps.

[ze2be]

spoke too soon ...
back to 8.2.1

Dammit, I had my hopes on that one. Shold I still try to do it? Im to drunk atm, but tomorrow morning perhaps? (deleting prefs file)

meh...turned out to be pretty useless.. don't bother...

Thanks man. Regarding the memory issue I got, Support recomended me (upon my request) to install windows 7 and get some more ram. These types of crashes are happening directly because of ram overload. By upgrading the system from 32 to 64bit, Live can use more ram. Up to 4gb, while a 32bit os gives somewhere between 2 and 3gb. If im not mixing up bits and bytes, that should mean just belove 2gb is my systems crash limit. I get this number from reading of the systems ram use (from task manager) when the crash happens. For the record, I have installed 3gb ram.

[XSIMan]

Windows Xp, Vista 32bit can only use 3- 4 gb max for all things running and only 2Gb per application.

Win 7 64bit will allow around 4 GB for Live 8 but when Live comes out as a 64bit app then we will be able to use upto 16 GB of ram.

[dayjob1111]

massive problems here on mac 10.6.6

*cannot render audio (crashes)
*cannot freeze/flatten tracks (crashes)
*most max devices not working
*pluggo plug ins not working

i sent a dozen or so status reports to ableton tech support and have been going back and forth with them. tried trashing prefs and a bunch of other stuff they suggested but still having same issues. Live is essentially crippled for me.

[ze2be]

Me and my bandmate are working on a live set where almost everything has been frozen and flattened, to prevent crashes. (plugs rendered to audio) And all the audio loads from the hard drive, almost nothing loads from ram. yet, the set still uses an enormous ammount of ram, and crashes for similare reasons as dayjobb1111 describes. Cuting time, etc. Seems to crash arround 1.8gb. I have 3gb.

This set has been worked on a lot over the last 3 months. It seems that when adding a vst and freezing then flatten it, it still push the ram usage up, everytime. The more its worked on, the more ram it uses? Dont know if it is a bug, but it is very frustrating.

So im going to upgrade to 64bit os and get some more ram. Because this track is going to be relleased, and we dont want to delay it much more.

[T.I.M.]

For the folks having trouble with Virus Control: c'mon, VC has been buggy since day 1 under all kinds of DAWs. I was a fairly early purchases of a Virus, back when the TIOS was in revision 1.x, and I stuck with it through to version 4.x, but VC never fully stabilized in all that time. Under Logic, under Live, whatever. It worked reasonably well sometimes but was never (ever) a rock-solid experience of the kind that most high-quality software plug-ins are. I don't mean to put down the Virus, I love the sound of it, but it seems to me to be quite a stretch to pin crashes associated with VC on Live.

-Luddy

Thanks for the info. I've only recently got my TI2 so didn't know that. Do you use Virus through midi then or how have you "survived" all these years?

Sorry for the delay in responding. Yes, I always used my Virus in standalone mode, sending MIDI to/from it via a MIDI interface and routing audio usually as SP/DIF into an audio interface. With that setup it was 100% reliable. The only thing I missed in that way of doing things was the patch management, but even that was no big deal for me, frankly, because there are so many RAM and ROM banks in the thing that I could easily store every patch I ever made on the unit itself and call them back up with program changes or simply dial them in by hand. I often created a multi for a song and put the various patches for the sounds I used in the song on different parts/channels in the Virus.

Every so often I would put the virus back into VC mode just to see if the stability had improved but I never found it to be an acceptable way to work. Just too many problems for my taste. I like to get on with the music and not fiddle around with buggy sw...

hth,

-Luddy

Ouch, the Virus ti2 works fine for me in stand alone and plug in mode.

[dayjob1111]

so, my issues all got traced to one plug in!

PSP N20 causes all kinds of havoc with 8.2.2

PSP are aware and have a beta fix for the plug in. they sent it to me and it works fine and all issues resolved.

awesome.