Error 0x8004e0c1 (message missing)...HELP!!!

JukeFox wrote on 6/10/2003, 8:40 PM
I get an intermittent error message, generally when trying to resume
playback from a paused condition. The message is: "An error occured while
starting playback. Error 0x8004e0c1 (message missing)"

Once this message comes up (generally after my second or third edit or
pause), the only thing I can do is close Vegas and re-launch it, which
will then allow me to make another edit before displaying the
message again. I've tried repairing Vegas from the original 4.0c bld 184
download file, all to no avail. I don't remember having this problem with
my original Vegas 4.0, although there were some others that went away after
loading c bld 184. What's going on here and how can I fix it? Tech Support hasn't been able to help with this so far.

Product: Vegas 4.0
Product Version and Build: 4.0c Build 184
Product Serial Number: <DON'T POST YOUR SERIAL NUMBER>
Windows Version: XP professional
RAM: 384 MB
Processor Speed: 600 MHz
Sound Card: MOTU PCI 324
Video Card & Driver Ver: NVIDIA RIVA TNT, ver 6.13.0010.3087
CD Burner (make & model): Sony DVD RW DRU-500A, NEC DVD+RW ND-1000

Comments

SonyDennis wrote on 6/12/2003, 9:55 AM
What driver model are you using (Preferences > Audio Device)? Does it occur for other driver models?
///d@
efiebke wrote on 6/12/2003, 2:56 PM
I think I've had similar problems with my PCI-324 (Motu's 2408 mkII) when I use the ASIO driver.

The problem seems to go away when I make sure that I use a consistant Sample Rate to the project I'm working on and buffer size (to the project I'm working on).

For instance, if I'm doing a project using the sample rate of 48000 and my MOTU's software (MOTU Audio PCI-324 Console) is set to 44100 (with the clock source set to word clock), I get an error message. Sometimes if the buffer size is too low, I can also get an error message.

So, if I use the ASIO drive, I just make sure everything is configured out correctly with all softwares involved.

OR! I use WDM driver (set with a buffer to 64). No problems then!

I can also experience a minor crash if I start/stop/start/stop in quick successions during the editing process. . . while using the ASIO driver. Solution??? If I plan on do quick "start/stop's", I use the WDM driver.

Don't know exactly where the problem is. With Vegas? Or with MOTU? My guess is that it's a bit of both leaning more towards MOTU.

Although I'm happy with my MOTU products, it can be a bear to configure.

Hope this is helpful. . .

Ted
hugoharris wrote on 6/12/2003, 2:59 PM
I have the same problem with ASIO and my M-Audio soundcard - I use the WDM and everything has been stable since.
JukeFox wrote on 6/13/2003, 12:13 AM
Thanks Folks...I'll try going non-ASIO!
JukeFox wrote on 6/14/2003, 8:29 PM
Greetings Folks,

I cross-posted this on the Vegas Audio forum, and SonicPCH came up with a workaround that, while not perfect, has supressed the 0x8004e0c1 error. SonicPCH suggested installing PCI 424 drivers, which PCH says work with the PCI 324 and are much more stable. PCH says that Cuemix Console is not supported, which is not an issue for me as I use a d8b for most external routing and monitoring functions. Another observed effect of the 424 driver installation is that 4.0c bld 184 seems to respond more slowly. The mouse even bogs down more than it had previously, which was pretty substantial.

Anyway, while still an imperfect patch, it certainly beats having to close and reopen the application or reset the interface everytime I perform an edit. Hopefully, MOTU and SF will put their heads together and come up with a more suitable fix for this problem, especially in light of the fact that it didn't exist under Vegas 4.0a.

Thanks for all your help,
JukeFox