So start funelling people - give them the info

[Dennis DeSantis]

How long of a wait would seem reasonable to assume a lockup. I'm not sure what force-quit means. I've tried normal exit and ctr alt del but it seems like only alternative is hard reset of computer.

I think a reasonable amount of time would be "until it feels like something's wrong." A few seconds is probably too short, but if you have any question about whether or not the software has crashed, then there's obviously a problem.

Sorry, by "force-quit" I meant basically what you were trying to do via ctrl-alt-delete - basically killing the application via the operating system.

One possibility - do you have a USB keyboard attached? If so, try to detach it before using ctrl-alt-delete to close Live. I'd be interested to hear if this works for you.

Best,

[Pitch Black]

It's difficult to say whether or not a "lock up" is always a crash. In some cases, Live may become temporarily unreponsive, but may work again after some time.

We have had Live 8.0.9 go "temporarily unresponsive" to our MIDI controllers a few times at gigs. For periods of sometimes 10-30 seconds. However, the app was still totally responsive to input from trackpad and clicking. Does anyone know if this scenario been reported by others? Regretfully I can't file a crashlog because this is not a crash.

We had suspected a "rogue controller", or one of our USB MIDI interfaces choking temporarily, which formerly had seemed a reasonable suspect, considering mouse/click input was still ok. If there is a known issue anyone can point me to, or a specific noted bugfix, I'd be most grateful. I have not dared to use any newer version than 8.0.9 on stage up till now, so if anyone can say "yup, that's fixed" that would be the bomb.

It's scary when you open a feedback matrix for dub mixing, and then get "locked out" of control. At gig volume...

[Dennis DeSantis]

It's difficult to say whether or not a "lock up" is always a crash. In some cases, Live may become temporarily unreponsive, but may work again after some time.

We have had Live 8.0.9 go "temporarily unresponsive" to our MIDI controllers a few times at gigs. For periods of sometimes 10-30 seconds. However, the app was still totally responsive to input from trackpad and clicking. Does anyone know if this scenario been reported by others? Regretfully I can't file a crashlog because this is not a crash.

We had suspected a "rogue controller", or one of our USB MIDI interfaces choking temporarily, which formerly had seemed a reasonable suspect, considering mouse/click input was still ok. If there is a known issue anyone can point me to, or a specific noted bugfix, I'd be most grateful. I have not dared to use any newer version than 8.0.9 on stage up till now, so if anyone can say "yup, that's fixed" that would be the bomb.

It's scary when you open a feedback matrix for dub mixing, and then get "locked out" of control. At gig volume...

I'm not sure the status of this, but I'll look into it. Thanks for reporting.

Best,

[Pitch Black]

Thank you very much Dennis!

[3dot...]

How long of a wait would seem reasonable to assume a lockup. I'm not sure what force-quit means. I've tried normal exit and ctr alt del but it seems like only alternative is hard reset of computer.

I think a reasonable amount of time would be "until it feels like something's wrong." A few seconds is probably too short, but if you have any question about whether or not the software has crashed, then there's obviously a problem.

Sorry, by "force-quit" I meant basically what you were trying to do via ctrl-alt-delete - basically killing the application via the operating system.

funny thing ,,
if I try and "force-quit" on my quad-core...live always hard-crashes the os....always.
on the dual-core it doesn't...

[davepermen]

I have one bug so far on all sort of systems that i always forget to report (you quickly find out why)..

when ever i shutdown my system with live still running, i get a runtime error, and then live crashes.

now this is never an issue, as no one expect the app to continue to run when you shutdown anyways. but it's just stupid

Die Ausnahme "unknown software exception" (0x40000015) ist in der Anwendung an der Stelle 0x70a3bb47 aufgetreten.

C++ Runtime Library error


it would be cool if that would, one day, be fixed. looks sorta embarassing if you play somewhere, are done, shutdown, and the next guy looks at you "heh, it crashed"

[Poster]

We had suspected a "rogue controller", or one of our USB MIDI interfaces choking temporarily, which formerly had seemed a reasonable suspect

this might sound stupid, but have you changed USB ports recently? i.e. changing your USB MIDI interface from one port to another..

since you also have a MBP; the USB port on the left side is giving me occasional dropouts, while the one on the right side is working ok..

also when I use a powered USB hub on that faulty behaving left side port (instead of relying on the bus power) it seems to be working ok..