Live 6.0.1 - "Serious Program Error has occured".
Live 6.0.1 - "Serious Program Error has occured".
Was working on a set, got this message, which also said that Live would shut down after this. However, after I clicked ok, it just continued normally. I was able to save the set and restart Live. The only weird thing was that the set opened up as "dirty" right away - with a * next to it (not sure if this is related or not).
-
- Posts: 9
- Joined: Fri Sep 15, 2006 4:25 pm
- Contact:
This is basically how it happened for me when I got this pop-up error. It said it would shut down after closing the pop-up.
I had too shut Reason down 1st (ReWired) and then was able to save the Live 6 set. Closed Live and reopened but any move I made within Live said the same pop-up error.
I hope when I reboot back to that partition of my drive Live 6 will not continue to do so.
I had too shut Reason down 1st (ReWired) and then was able to save the Live 6 set. Closed Live and reopened but any move I made within Live said the same pop-up error.
I hope when I reboot back to that partition of my drive Live 6 will not continue to do so.
WindowsXP Pro SP2 / Dell Dimenson E510 / Intel Pentium D 3.2 Ghz / 2 Ghz RAM / Reason 3.0 ReWired
the "A serious program error has occurred." message box lies
I use Live 6.0.1 and am currently testing Live 6.0.2b10 on my Windows laptop computer, details are in my signature.
The "A serious program error has occurred." message box lies. It does not shut down Live after the message box is closed. A new message box is served over and over and over again. I get this one every day and i have to use Windows Task Manager to kill Live 6.
Reproducing this is not easy, it just happens when playing a song, there is no action related to this error.
edit: 6.0.2b20 is 6.0.2b10
The "A serious program error has occurred." message box lies. It does not shut down Live after the message box is closed. A new message box is served over and over and over again. I get this one every day and i have to use Windows Task Manager to kill Live 6.
Reproducing this is not easy, it just happens when playing a song, there is no action related to this error.
edit: 6.0.2b20 is 6.0.2b10
Live 6.0.3 Win XP sp2, P4 2.8 GHz, 1 GB, UXGA video, RME Multiface (1), Nord Lead 3, Korg X5D, TR-Rack, ER-1, Roland Juno 106, JV-2080, Elektron Machinedrum-UW, SidStation, SPL Charisma, Soundtracs CP6800 (40/12/24), Genelec 1030A, Furutech TP80, etc.
Change the message
Live is not shut down after the message box is closed.
Can you change the text of the message box into:
Because this is the only true text phrase for this one.
Can you change the text of the message box into:
Code: Select all
Go to Windows Task Manager and kill the Ableton Live Process.
Live 6.0.3 Win XP sp2, P4 2.8 GHz, 1 GB, UXGA video, RME Multiface (1), Nord Lead 3, Korg X5D, TR-Rack, ER-1, Roland Juno 106, JV-2080, Elektron Machinedrum-UW, SidStation, SPL Charisma, Soundtracs CP6800 (40/12/24), Genelec 1030A, Furutech TP80, etc.
-
- Posts: 26
- Joined: Thu Dec 07, 2006 11:57 pm
- Location: United States
By any chance are you running SampleTank when this happens?
I've noticed that only SampleTank 2.x projects do this to me.
Re: By any chance are you running SampleTank when this happe
I have this while using Ableton Live's own instruments.dkcalifornia wrote:I've noticed that only SampleTank 2.x projects do this to me.
Live 6.0.3 Win XP sp2, P4 2.8 GHz, 1 GB, UXGA video, RME Multiface (1), Nord Lead 3, Korg X5D, TR-Rack, ER-1, Roland Juno 106, JV-2080, Elektron Machinedrum-UW, SidStation, SPL Charisma, Soundtracs CP6800 (40/12/24), Genelec 1030A, Furutech TP80, etc.
serious
Hello all,
i could reproduce this behaviour by loading more instruments (by size) into live (sampler) than physical available RAM. Load 1,1 GB instruments on a machine with 1GB RAM produces this error (XP SP2).
i could reproduce this behaviour by loading more instruments (by size) into live (sampler) than physical available RAM. Load 1,1 GB instruments on a machine with 1GB RAM produces this error (XP SP2).
-
- Posts: 80
- Joined: Thu Aug 12, 2004 6:24 pm
- Location: züri
it happens to me when i try to render loops from reason,
so first it looked like a rewire problem.
but then again, it does the same thing when i render with vst-plugs,
or even with the live-own efx.
it does not crash then, but the "render to disc" screen will not disappear,
and the rendering does not happen.
curiously, sometimes no more rendering is possible,
and: sometimes after a few times, it`s rendering perfectly again.
i don`t try to save the whole set, because that way i am only making loops,
but it is strange and steals alot of time and nervs
so first it looked like a rewire problem.
but then again, it does the same thing when i render with vst-plugs,
or even with the live-own efx.
it does not crash then, but the "render to disc" screen will not disappear,
and the rendering does not happen.
curiously, sometimes no more rendering is possible,
and: sometimes after a few times, it`s rendering perfectly again.
i don`t try to save the whole set, because that way i am only making loops,
but it is strange and steals alot of time and nervs