If you're not put off using ASIO completely, you may find that it is worth trying the last-but-one beta driver from their website, V.5.10.00.29x12beta.

This version includes fixes that finally allowed the 1010 to work satsfactorily with Acid 4 and (I believe) Vegas 4. Neither the earlier non-beta versions nor the later beta version (beta31) work well with ASIO under Acid 4 and I'm pretty sure that the situation is the same with Vegas 4.

(I don't have a 1010 myself, but the above is what I believe to be the current best advice, distilled from past posts in the Acid forum.)

Mark

Thanks Mark, I'll check out that driver when I get time to test. ;)

NukleoN
www.NukleoN.com

Hi Chessmaster,

I'm having a similar problem to what you describe, but for me it's only happening for MPEG-2 files generated by Vegas (MPEG-1 files work fine). Here is the error message I get when I highlight a Vegas-generated MPEG-2 file in Windows Explorer:

http://home.cfl.rr.com/razz/images/MPGError.gif

I can't say for certain if it's related to 4.0 or 4.0b, since I downloaded 4.0b before I received my copy of Vegas; I then installed Vegas, ran it just long enough to register it, then immediately upgraded to 4.0b. I have uninstalled Vegas several times now, completely wiping out all traces of it and reinstalling (Vegas 4.0a from the CD by itself, 4.0b by itself, upgrading from 4.0a to 4.0b), and see the same problem no matter how it's installed. I'm wondering if Vegas installs any codecs into the Windows system directories that overwrite existing files, which don't get restored when Vegas is uninstalled. I also can't verify that the problem started with installing Vegas itself, since prior to installing it, I didn't have any Vegas-generated MPEG-2 files to play!

This problem also occurs if I try to open a Vegas MPEG-2 file within Windows Media Player or Adobe Premiere. Strangely, RealPlayer will open it, but in the particular clip I'm trying to play, it doesn't play the whole file, and DVDIt! opens and plays the file perfectly, as do Vegas and DVD-Architect. I can play any other MPG file I have perfectly in any of these applications, it's just the Vegas-generated ones that cause problems. In all other respects, Vegas has functioned perfectly for me, being very easy to learn, but also extremely powerful.

I do not believe this problem is hardware related, or the result of a virus; I really think it's a codec problem, but I don't have a clue as to how to go about fixing it. Does anyone know how to find out which codec XP uses when it opens an MPEG-2 file?

I have found a work-around for Windows Explorer, though. If you're using XP, you can go into Explorer, select Tools->Folder Options, then select "Use Windows classic folders" in the General tab. This at least lets you move/delete/rename the files, or attempt to open them in other programs, but it's just a fix for the symptom, not the actual problem. Unfortunately, this "fix" also affects other Windows Explorer interfaces, including the Control Panel, but you can always go back and re-select "Show common tasks in folders" to restore the original appearance. Windows Explorer, by default, seems to examine the contents of each file (calling the appropriate codec as necessary) to find out information about it when it is highlighted, and this modification turns off that functionality.

You said that you got a DLL error message--did it say what DLL file caused the error? Maybe that would give us a clue as to the root cause of this problem...

Robert

Chessmaster and razzberry,

Are you running on XP SP1 and also have Premiere installed? (I see that razzberry has Premiere).

Premiere also uses MainConcept MPEG but it installs the DLLs in the Windows system folder. Technically, Premiere should install them in the same folder as its MPEG plug-in to keep them private, they are NOT compatible with the version Vegas 4 requires (and they really aren't system files anyway). In many cases under XP SP1, Windows uses DLLs in the system folder in preference to the local folder. It's possible that this is causing your troubles. Vegas 4 works around this problem by preloading the MainConcept DLLs before it loads the plug-in, so it will use the proper DLLs for MPEG.

You could try renaming mcdsmpeg.ax to mcdsmpeg_bak.ax and see if this works around your problems with the Windows Media Player and the Explorer. This file is a DirectShow filter which I believe is used by WMP and the Explorer. You'll probably find this file under "C:\Program Files\Sonic Foundry\Shared Plug-Ins\File Formats\MCMPEG" for a standard installation.

Thanks for the information SonicTSW! I uninstalled Premiere and its MPEG encoder, but the problem persisted. But your suggestion led me to look for other MPEG-related software that might cause the problem, and after I removed something called InterVideo something-or-other (I don't recall the exact name), everything was fine! Not knowing what this InterVideo thing was, I did some searching on the web, and discovered that WinDVD had installed it. This link describes the problem, and a way to fix it without resorting to uninstalling anything:

http://www.digital-digest.com/supportfaq/mod.php?mod=userpage&page_id=46&menu=&PHPSESSID=a51ef2aba321a28c1a54411e199d541e

I don't know if Chessmaster has WinDVD installed, but from what I've read, several other products also use the InterVideo module that was causing all the trouble for me; maybe his problem is similarly based on an InterVideo incompatibility, and the fix described at the link above will help him too...

Robert