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

JukeFox wrote on 6/10/2003, 8:42 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
generally 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 we fix it?

Comments

midigod wrote on 6/11/2003, 8:31 AM
I get the same thing. I posted about it a few weeks ago, but got no response. I can get rid of it without closing Vegas if I refresh the MOTU interface manually.

craftech wrote on 6/11/2003, 6:52 PM
I got a similar message while priniting to tape using video capture. I got rid of it by re-installing the program.
John
JukeFox wrote on 6/12/2003, 2:48 PM
The re-install didn't work for me. Tech Support sent me a file (makeashorterline) to install that they thought might take care of it...it didn't. I e-mailed 'em back and they sent me a survey form, which I sent back...I'm still waiting for their reply, given the additional information they requested. The error doesn't supply a stack dump, which I suspect complicates matters a bit. Thanks for the suggestion!
JukeFox wrote on 6/12/2003, 2:54 PM
Thanks for your reply, midigod...I'm using a MOTU 324 with a 1224 and a 2408 interface, as well as a MOTU MIDI Timepiece. My principal playback is through the 2408 ADAT C 7 & 8 outputs. Are you refreshing your interface through the on-screen PCI-324 console, are you manually cycling the interface, or are you resetting your MIDI interface? Does this cure the problem for the rest of the session, or are you having to refresh the interface every other edit? Either way, it's a bug that needs to be corrected. I'll try your suggestion...Thanks!
midigod wrote on 6/12/2003, 3:16 PM
I'm refreshing using the PCI-324 console. I've found that when the problem comes along, the refresh will work for as much as a couple minutes, as little as one mouse click. But after I refresh a few (sometimes a lot) of times, the error will eventually go away for another half hour, or an hour. Whatever it feels like.

I'm not resetting the MIDI interface, nor am I refreshing using the 2408 itself, which would require a powerdown.

I was really hoping it was something to do with the BRC clock, but it still happens when using the 324 internal clock.
pwppch wrote on 6/13/2003, 8:45 AM
Are you using ASIO or Classic Wave?

What is the MOTU buffer setting?

Suggestion:
The PCI-424 drivers work with the 324 card and are far more stable. The only downside is that the 424 cue mix app does not work with the 324.

We are looking into this issue, but have not been able to reproduce.

Peter

JukeFox wrote on 6/14/2003, 8:19 PM
Hi SonicPCH,

The buffer setting is 256. I took you suggestion and installed the 424 drivers, and this seems to have stopped the 0x8004e0c1 error, although it seems to slow things down considerably. Nonetheless, it is a workaround that will help me get through the current project. Thanks for your help. I'm still not certain why I didn't have this problem before the version c build 184 update. I'll bug MOTU for updated drivers although I doubt they'll put much effort into them, since the 424 is their current flagship. I still feel that, since these problems didn't exist under Ver. 4 that SF should come up with a patch, especially based on the fact that you guys are apparently aware of the problem and a workaround.

Thanks again.
JukeFox
pwppch wrote on 6/15/2003, 12:47 PM
You didn't answer my question about ASIO or Wave Classic.!This makes a big difference.

>>I still feel that, since these problems didn't exist under Ver. 4 that SF should come up with a patch, especially based on the fact that you guys are apparently aware of the problem and a workaround.
<<
We are aware that you are having a problem, but have not reproduced this in house. We don't have a work around, I just suggested a possible solution to a problem that we don't know the cause of. That the 424 drivers fix your problem only indicate that there is a bug in the 324 drivers, not in Vegas.
midigod wrote on 6/17/2003, 8:59 AM
I'm using ASIO, and I've varied my buffer settings from 128 to 1024, with no difference. However, yesterday I switched from the BRC clock to the MOTU internal clock, and the problem SEEMS to have disappeared, although it was definitely there a couple weeks ago when I used the internal clock. I have not tried the 424 driver, but I'll give it a shot.

I'd love to send you a project, but it happens on any project, whether it's at 44.1 or 48, 16 bit or 24, two tracks or 50, no edits or hundreds. None of these seem to affect the problem in any way.

But in last night's project, I was doing a lot of time stretching, and that seemed to make the problem much worse. I'll investigate this more.

And thank you for your help.