Live hangs

[ScottV]

I'm not sure if my case is isolated since I couldn't find any info on it in the forums.

The short of the problem is that live hangs for what seems to be forever after a crash. I'm sure it's writing the crash dump file but I've never experienced a software take so long. I always thought it was an issue that would be resolved with the release of Live 8, but now that I have it-- I'm still experiencing it.

Any input? Is this just the way it is and there's no hope for change? Is it only me?

Also, developers at live, there's no Multi-Channel VST support in this release either?!?! Still have to do the work around? That really sucks. For those of us using live for production this is one of those things that's keeping live from passing the mark. Don't get me wrong, I still think Live is the best thought out and implemented DAW on the market, but c'mon. Video support wouldn't hurt either.

Ok, enough ranting. Thanks in advance for your help.

[ScottV]

Nothing?

[cids]

Maybe it helps if you provide some more info, like the system you are working on, version info and used plug-ins...

Btw Ableton LIve has video support; Video import and export for scoring, video warping

[feyshay]

I notice the same thing. When Live crashes (I use 8.01 on a Dual Core XP with a Fireface 800), I will end the program (in Applications). But then, I see Live 8.01 remaining open in Processes. I click on closing the process (or closing the process tree), and Live fails to close. All while utilizing a lot of CPU. I'll have to reboot.
I note that Reaper and Cubase 5 do not do this. This was a problem in Live 7 also.

[ScottV]

System:
Core 2 Duo 2.4
2 gig's ram
Vista
Live 7 & 8

Plugins:
NI Massive
NI Lounge Lizard
OhmBoyz
ArtsAcoustic Reverb
Kjaerhus Audio compressors

Feyshay's problem rings true to my system. In processes, Livebin hangs for 5-10min until it eventually goes away and allows me to open a new session of Live. I have to say, I probably am running my system pretty hard when crashes occur but I can't figure out why it would take so long for it to finish crashing. The VST's mentioned above are from one of my sessions that crashed, but it has happened in other configurations. Thinking back, I'm pretty sure most of them, if not all, had NI Massive in at least one channel (Feyshay, is this the same in your case?).

About the video... I guess I just didn't look for it hard enough, but that pleases me much!

Thanks for any help.

[ScottV]

*bump*

is this just not common enough to bother with?

[ScottV]

Look, I understand that you may not have the answer. Not all the answer are sitting there at your fingertips to respond to immediately. Although, techs, you could simply say that you're not sure what the problem is and you would have to be able to replicate it in order to figure out a solution. Ignoring the problem is simply not good PR.

[feyshay]

This is still a problem. After a crash Live 8.02 (as did previous versions of 8 and 7) remains open in processes. I cannot manually end the process or process tree. I have to reboot to get the process stopped.
I have a dual core Win XP 3.2GHz 2 Gigs Ram
I run it with a Fireface 800, Novation Remote 25SL, Akai MPD24, M-Audio Trigger Finger and 02.
This hang occurs even when I have no plug-ins or anything running.

[wehkah]

I think its VISTA related, on my Notebook i*ve used VISTA and have some trouble with many applications and i know to many VISTA users has the same issues. If Windows7 is finally released i think it will be solve this or any struggles with PRO applications. If your hardware components are supported, switch to XP! I know thats a killer tip, but i told you --> DO IT!

I assure you, im not trolling! I*ve a tech. support job and i know the VISTA issues, for real.

Be sure your VSTs are up to date (VST Version!). I any cases the VST has no perfect exception handling > LIVE hangs or cannot be killed in task view - also on XP (for example in use of REAKTOR on my PC)! But XP has a more steady state, i THINK.

I hope that helps a little bit or give hope for the future.

cheers
T

I hate "klickie bunti" apps without steady state but i cant use LIVE without it. killing processes under linux are really easy, why its this a problem under windows? i dont know.

[feyshay]

Not a Vista issue only. My version of Windows is XP.

[stmaximus]

I have the solution for everyone.

The problem : Any midi device you had plugged in when live crashed didn't get the message to disengage, because live turns them off only when it quits normally.

The solution: Unplug your midi controllers. The live process will disappear.


I found this out quite by accident. I used to have to wait 10 or 15 minutes for the process to quit itself. Now I just yank my midi hub, the process quits, and I can relaunch and get back to work instantly. Crashes don't upset me so much anymore.

[feyshay]

I tried unplugging them one-by-one (including the Ilok dongles stuff). I'll try to get them all into a USB hub and unplug that to see if it works.
Of course, the best thing would be no crashes. I had a great day of work yesterday with no crashes.
I also fixed a big problem in Live (where I could not access Manage Files, Lessons or Notes within Live). I trashed preferences and rebuilt the preferences.

[stmaximus]

Yeah, the crashes don't bother me anymore, but that doesn't mean Live is bother-free.

Now I hold my breath while opening sets, because they often crash on launch. Sets that work fine for days will just suddenly not open.

So I've had to trash my preferences many times. It is quite annoying, especially since my prefs are highly customized.

Also, I always have to load my template separately once Live opens. If I load it directly, you guessed it--- it crashes.

But at LEAST I don't have to wait no 15 minutes to get back to work.

In a perfect world, Live would never crash. But that's just not going to happen. This is software we're talking about.

[ScottV]

Feyshay,

Next time this happens power off your audio interface (don't forget to turn off your speakers first to prevent a POP). If your case is the same as mine then as soon as the audio interface is off, Live.Bin will finally close. Is this a audio interface issue? Possibly. If you're running an M-Audio firewire (1814 in my case) then there's a good chance that there is a common problem with our setup. If you're running something else then I'm not sure where to begin. I'm not ruling Live out of the equation just yet but at least I've found a work around.

[chawchaw]

Not a Vista issue only