[dwi] "Serious Program Error" b12

Locked
craftycurate
Posts: 500
Joined: Thu Sep 27, 2007 2:23 pm

[dwi] "Serious Program Error" b12

Post by craftycurate » Mon Feb 23, 2009 3:49 am

Was running a set with 2 tracks, each with an instance of Reaktor 5, and a Vocoder on one of the tracks, with one Reaktor as carrier and the other as modulator.

Worked fine for a bit, then I received the above error, which continued "Live will quit immediately after this message."

I didn't save the set, so can't email it, but will try to reproduce.

Once Live application quits, the Live8.0b12 process cannot be killed - I have to wait for it to exit. This may be my audio interface or something as the "not killing the process for 5 minutes" thing occasionally happens with Live 7 too.

Bug report posted (including set) using Live's internal system.

[EDIT: Yep - just happened again - same set (recovered from Undo buffer). The set is still playing though, even though the error message has appeared. Live quits after dismissing message]
Core i7 2.3GHz|Win7x64|8GB|1.5TB & Core 2 Duo T7200, XP Pro SP3,
Nio 2|4, Edirol PCR800, NanoKontrol , Komplete Synths + Reaktor 5, Cameleon, Alchemy, FabFilter 2 suite
http://www.myspace.com/richardlyallmusic http://craftycurate.blogs.com

mholloway
Posts: 1579
Joined: Sat Nov 29, 2008 7:24 pm
Location: Portland, Oregon, USA

Post by mholloway » Mon Feb 23, 2009 6:59 pm

I've gotten that "serious error has occurred" message about 3 or 4 times now with 8b12. I can't be sure, but it *may* be related to NI plugins, and your case with REaktor seems to support that. I know that in my case, at least one of those errors (possibly more) occured when I was using Guitar Rig 3....
my industrial music made with Ableton Live (as DEAD WHEN I FOUND HER): https://deadwhenifoundher.bandcamp.com/
my dark jazz / noir music made with Ableton Live: https://michaelarthurholloway.bandcamp. ... guilt-noir

dom
Posts: 936
Joined: Fri Jan 07, 2005 9:24 am
Location: Ableton Headquarters
Contact:

Post by dom » Tue Feb 24, 2009 4:06 pm

this might have been bug[4738], can you try to reproduce this in beta13 and send a new report if it still happens?

thanks,
dom
ableton support team
[email protected]

Locked