Ableton Forum

Should have posted this here, but I thought it had a simple answer.
(from General Forum)


WinXP problem with error, "A serious program error hes occured...." ........

(read more)
http://www.ableton.com/forum/viewtopic.php?t=15396

I'm not letting it get me down that I can't get it up-and-running yet......(yet.)
One could get depressed reading all these Bugs, but I'm confident there are reasons for this:

It's a popular program, more users means a longer list of problems, but doesn't mean the problems are greater than other software, just more posters.

There is no such list where people would post things like "I have no issues".......again, the same with other softwares.

I've heard too many good things about Ableton 4.

=RR=

Hi redrabbit,

please see my answer in the other thread.
http://www.ableton.com/forum/viewtopic.php?t=15396

regards,
Alex

Well, sent Log.txt files off today (friday) , no response yet. Maybe not till next week?

I've yet to hear a sound from LIVE, or start a tutorial. I will get the same error message when clicking various Menu items....Preferences, Plug-in Devices....more.
I'm concidering re-installing, but I'm afraid that effort will lead to same results. And at the same time, I'd like to help Ableton support locate the prob.
I'll TRY to use it in rewire mode via CubaseSL.

I guess I'm just anxious to use LIVE, can you blame me?

I don't understand the Log file well enough, but I'm guessing the crash happened abouts' here:

(cont'd)....
4321 ms. ASIO: AsioLatenciesChanged
15503 ms. : Logged Crash: 0
15503 ms. : 009DD916 009DD8D0 0012F7B0 0001:005DC916 F:\Program Files\Ableton\Live 4.0.5b3\Program\Live 4.0.5b3.exe
.......(cont'd)

=RR=

Try another driver:

ASIO X or Asio4All. Both free, google them

Will another ASIO driver affect my other programs? I ask because I'm trying to get RID of conflicts here. Thanks for the input everyone.

Anyway, Rewired as slave to Cubase IS working, but not as a stand-alone.

=RR=

redrabbit wrote:Will another ASIO driver affect my other programs? I ask because I'm trying to get RID of conflicts here. Thanks for the input everyone.

Anyway, Rewired as slave to Cubase IS working, but not as a stand-alone.

=RR=

I'm not sure what other programs you dont want to affect. When you're running Live standalone (not rewired) you wont be running other ASIO applications simultaneously. All of your VST's etc will be using the ASIO driver thru live.

So I dont see where this would be an issue (?)

Rewired, Live is using the driver you choose inside of Cubase. So, ASIO driver you choose in Live again is not a factor.

Asio4All and ASIOx are third party, free drivers you can use instead of the one provided by your interface manufactur.

So, download them and use them to troubleshoot. If you load one up, and Live runs fine, then you know its your interface driver that is the issue.

FIXed FIXed FIXed FIXED...

I got it working. It WAS a simple problem(s), and did not need a different ASIO driver. (thanks anyway SUPSTER!)

Here is what I did:

(Windows) In Control Panel> Sounds and Audio Devices Properties> Audio, I unchecked "Use only default devices"..........and....

.....disabled "Bluetooth Audio" (Sounds and Audio Dev.....>Hardware).

I don't know if the Bluetooth Audio was a prob, but I don't use it anyway. I could enable that again to check, but I'm pretty sure it was the former.

Now , so far, it's working in standalone mode and I'm getting sound, and it found all available VSTs and Plug-ins as well....(Halion, Battery, Soundhack, etc.).

BTW, I love that LIVE alows me to point to "Sample Editor" (wavelab). We'll have to see how flawless this function is...?

I DO HAVE one question though, ...page 40 in the manual..Overall Latency..............I have never short-circuit-ed my RME's IN/OUTs. Do I need to worry? ...safe?
Also, I'll be using external effects (reverb and compressor) ...how is that extra latency dealt with (Send/Return, pre-fader)???

=RR=

VERIFIED.......at least on my system.

It surely was the Bluetooth Audio (installed with Logitech 'DiNovo keyboard, SetPoint 2.20) .
When rolling back to 4.04 from the newer/expired (.5b3)Beta, I made sure BT Audio was enabled because I wanted to see if I got the same results (see error message in above reply). I did, same error.

UNTIL I disabled BT Audio ("Do not use this device.."). Then 4.04 allowed me to configure it's Preferences or accsess it's Plugins - works ok.
Strangly enough , after LIVE's audio driver (I use RME's asio) IS setup, I can re-enable BT Audio with no apparent problems.


I guess BT Audio is just selfish that way

=RR=