The Audio Engine Could Not Be Started

TelePaul

I get the above error when launching Cubase SE3 with my Alesis io 26 Firewire. Cubase doesn't laod projects and just exits. I load it up a second time, and hey presto, everything's working fine again.

Any thoughts?

frobisher

TelePaul wrote: »

I get the above error when launching Cubase SE3 with my Alesis io 26 Firewire. Cubase doesn't laod projects and just exits. I load it up a second time, and hey presto, everything's working fine again.

Any thoughts?

Can't think of an instant solution but I would see that as a sign to back up and /or duplicate files immediately!

Neurojazz

Last time i had any cubase errors like that was when i had multiple Firewire devices sharing the same buss - had months of teething problems and then had each device on a separate FW card/buss and then no problems.

Check firmware for the FW device just in case of conflict - have you installed any new software / hardware recently? (like the syncsoft stuff or a new Pci card etc...)

TelePaul

Thanks guys. I havn't installed any new software, but I consulted the sticky and set up two Hardware Profiles so I've been able to disable non-essential hardware. I'll see of this has any effect.

frobisher

Always good practise to have duplicate project file. Not the actually audio files but the cubase file. I number mine as I go so the first few hours work is called Boards Song 1, then after the next session it's saved as Boards Song 2. You end up with loads but your save and they don't take up too much space at all.

Neurojazz

There's also an autosave function that saves a file in the background (in the same folder) called 'name of song'.bak - these are useful for looking through if your project bombs out. The safest way to protect ALL project data is too save off 'Project to new folder' near a final mix and this way you can roll back should anything really nasty happen (like corrupt plugins or accidental audio deletion)

The audio engine thing really stinks of a hardware issue... it's almost as if something can't enable itself quick enough for cubase to operate... sometimes you get this phenomona when you boot windows with a USB stick in a port and it can't find the OS there

ogy

to me it would suggest that cubase or some other program is not shutting down properly, like it crashed the previous time you ran it or something? then you need to open it and let it close again before it frees up the audio resources. maybe?:)

Neurojazz

That reminds me.. the powercore is notorius for that (or used to be) - has real issues with certain Firewire chipsets and any other FW devices even near it

TelePaul

Neurojazz wrote: »

That reminds me.. the powercore is notorius for that (or used to be) - has real issues with certain Firewire chipsets and any other FW devices even near it

The Powercore? It seems my card has died on me, it's not showing up as a Hardware device.

Neurojazz

What card is failing? - if internal, power off and make sure it is seated properly - heat can make some cards pop out if not seated well.

TelePaul

Neurojazz wrote: »

What card is failing? - if internal, power off and make sure it is seated properly - heat can make some cards pop out if not seated well.

PCI Firewire Card. I already tried swapping ports.

Neurojazz

Ah, pretty cheap to fix at least - i have 2 PCI FW cards in main box - took ages to find compatible ones!