Ableton Forum

I wanted to bring this into view again. Same thing happens here on a G4 1.5khz PowerBook running OSX 10.4.10 and lates Ableton Live version 6.0.10

Sometimes out of the blue it happens on a set - not consistent with any commands or clicks, etc. Also after a program dissapearance, and upon trying to open the same als file, this will happen again. Using two plugins only V-Station and ImpOSCar if this helps.

Amaury: does it help if we post our crash log? You know the one it sais "send to Apple"?

Gabi.

gabster wrote:I wanted to bring this into view again. Same thing happens here on a G4 1.5khz PowerBook running OSX 10.4.10 and lates Ableton Live version 6.0.10

Sometimes out of the blue it happens on a set - not consistent with any commands or clicks, etc. Also after a program dissapearance, and upon trying to open the same als file, this will happen again. Using two plugins only V-Station and ImpOSCar if this helps.

Amaury: does it help if we post our crash log? You know the one it sais "send to Apple"?

Gabi.

Hi,

yes, it would help if you send it to [email protected], giving an explanation of the problem again, with a description of your setup. You can also include a link to that thread.

Regards,
Amaury

Thanks Amaury!

I will - together with a detailed explanation of my setup.

Thanks!
Gabi.

Okay, Amaury!

It happened today simply by (if I remember correctly) trying to un-mute a track or something simple as that) twice with actually no hardware attached. As I said it doe NOT happen on the same move I make.
I strongly suspected the audio Interface (Firepod) or my Novation X-Station. But this time I was simply playing my set directly via the core audio.

So again, this is on a
- G4 1.5khz PowerBook
- OSX 10.4.10
- Ableton Live version 6.0.10
- 2Gb RAM
- Using two plugins in my set: Novation V-Station and ImpOSCar

The error log generated content is here:
http://www.mamaliga.com/error.rtf

Hope this helps troubleshooting the issue...

Thanks!
Gabi.

Just bumping this up to see if this error was looked into it...

thanks!
gab

im having EXACTLY the same, what everybody else is talking about now!

i've bought live months ago, NEVER had problems with it, and this morning when i was finalizing and mixing my new masterpiece

it started crashing, crashing, crashing, crashing, crashing, crashing.

Tried EVERYTHING, disabling plugins, disabling rewire via options.txt, reinstalled soundcard, rebooted, turned on/off, saving new versions of .als, EVERYTHING...

but it just keeps quiting all the time, also in other projects / sets!

WTF!

-Intel Quadcore Q6600
-4 Gig ram
-WinXP Pro Student 32-bit
-Ableton Live 6.10
-ATI Radeon HD x2600
-Maudio Fasttrack Pro

updated all drivers, and did not have any problems with latest updates untill this morning!!!

Does "everything" include turning off all Midi ports and Multiprocessor support?

it was the darn NI Massive that ruined everything for me...thats why everything keeps crashing (i use Massive all the time, in every project)...never expected that to be the problem.

it worked fine for half a year, and suddenly it friggin dies on me...can you believe that shit.

i just made the most amazing 11:30min epic techno-work out, and now i have to replace the main-synth and arrange everything all over

thats TOOOO sad for words.

Did you try uninstalling, and then reinstalling and updating Massive first? Would be a lot easier to give that a go than recreating everything with a new synth.

I have this also using XP

The only thing I have added is Audio Damage Richochet

Big gig coming up - very scared !!