Hi all,

I just upgraded from MC 2.8 to 3.0. Followed Readme: uninstalled everything Avid, removed folders and regkeys, installed NVidia 169.47, then installed new version and successfully upgraded dongle.

When I launch 3.0 I get this error:

ErrLog_ForMC::ErrLog_ForMC()

Error [-16777178] unable to:

CreateHWC_StackWalker()

I hit OK and program exits. I uninstalled a few times with same results.

workstation is HP xw4400 with Quadro FX1500 and 4GB Ram. I run XP Pro SP2 and the only other software on this machine is Pro Tools LE 7.4

I ran DebugView, and this is the output:

00000053 2.91597557 [1880] DIOWinDeviceLoader[8]: DIOloader - Loading DIOPyromaniacOHCI.dll 
00000054 2.95340085 [1880] DIOPyromaniacOHCI DLL Loaded 
00000055 2.95342231 [1880] DIOWinDeviceLoader[9]: DIOloader - Checking version number 
00000056 3.15532088 [1880] MSDVStream::BuildGraph - Cannot create video capture filter 
00000057 4.16237783 [1880] MSDVStream::BuildGraph - Cannot create video capture filter 
00000058 5.17848015 [1880] DIOWinDeviceLoader[10]: DIOloader - Retrieving base object 
00000059 5.17852497 [1880] DIOWinDeviceLoader[11]: DIOloader - disabling thread calls to DLL 
00000060 5.17854357 [1880] DIOWinDeviceLoader[12]: DIOloader - completed 
00000061 5.17856455 [1880] DIOWinDeviceLoader[13]: 1 device types loaded 
00000062 6.39441490 [1880] DIOPyromaniacOHCI DLL Process detach 
00000063 7.53644514 [1880]    98.515671 ErrLog_ForMC::ErrLog_ForMC()    Error [-16777178] unable to:       CreateHWC_StackWalker().  

This looks to me like a video adapter problem, so I went back to NVidia 91.85, also tried different resolutions with no luck: 1280 by 768, 1440 by 900...

Any help would be greatly appreciated

wil:

I just ... installed NVidia 169.47, then installed new version and successfully upgraded dongle.

According to your equipment configuration you have an ATI display card.  Apart from not being on the Avid approved list, nVidia drivers will not work with non-nVidia display cards.  If you actually haven't updated your configuration in your profile, tell us what display card you do have and someone may be able to help.

 as stated in the message, the graphics card is a Quadro fx 1500, on a HP xw4400 workstation, which is on the Avid approved list... and I just found the link to update my profile

Hi Wil,

I wrote the MSDEVStream code way back when.  Looking at the exception log, it looks like it's unable to create the AVC capture filter.  There are two versions of the filter, one for DV and one for HDV capture.  These filters are provided by Microsoft as part of DirectShow - which is now part of DirectX.

Just in case, though, go to "C:\Program Files\Common Files\Avid" - or whatever drive you have installed, and right click on DVBuffers.ax and choose "Open With...", from there browse to your Windows\System32 directory, and choose regsvr32.  That should make certain our interface to the capture filter is installed.  Try launching again.

If that doesn't work, you should do a full uninstall of the editor - including any old versions of Xpress Pro you might have installed.  Do a search for any existing copies of DVBuffers.ax.  There should be none.  There should not be an Avid folder in the "C:\Program Files\Common Files" folder.  Then try a reinstall.

If that doesn't work, then it's most likely the needed MS DirectShow filters are missing.  You might be able to get them back with a re-install of DirectX 9.0c (provided by Microsoft), or you may need to reinstall Windows XP Pro SP2.

 Thanks for the tips Brian, there was indeed some relics of older xpress pro installations, but I still got the errors after trying all these. Before reinstalling from scratch I gave Vista a try by upgrading my current XP, and now 3.0 works OK, so I'll give Vista a shot for a while.

thanks again!

Brian Williams:

Hi Wil,

I wrote the MSDEVStream code way back when.  Looking at the exception log, it looks like it's unable to create the AVC capture filter...

Wow, by the way...

How often with the Other Guys' software do you get a direct response like that from the guy who wrote the code? Pretty friggin' cool, Brian. Cudos to Avid's 'new thinking' as well. If this is part of it, I'm impressed.

Chris

conleec:

How often with the Other Guys' software do you get a direct response like that from the guy who wrote the code?

Yes, well with the typical error messages that Avid puts out you actually need to be the programmer who wrote the code to be able to understand them... 

Morten

"Put down the Koolaid, and step away from the FCP system"

assert("with the typical error messages that Avid puts out you actually need to be the programmer who wrote the code to be able to understand them"==true)

Nice to see you back in the forum Brian with sense of humour intact. Hoped you had not been one of the lay offs!!

if ("with the typical error messages that Avid puts out you actually need to be the programmer who wrote the code to be able to understand them"==true) then {
contact_support(error_message(full));
provide_full_details(system_setup);
fixbug()}
else takeup_farming();

No lay off for me.  I am an old timer at the company, coming up to my 16th year!  For the last 2 years, I have been heads-down working on much of the multi-core scalability in 3.0.

I like to watch the forums for a few weeks after a major release to see if there are any major problems, also to see what people think of the release and features.

Brian Williams:

I like to watch the forums for a few weeks after a major release to see if there are any major problems, also to see what people think of the release and features.

It is nice to see you back Brian - wish you could dedicate more time to the forums, but completely understand how busy you are writing the Avid code.

Brian Williams:

How often with the Other Guys' software do you get a direct response like that from the guy who wrote the code? Pretty friggin' cool, Brian. Cudos to Avid's 'new thinking' as well. If this is part of it, I'm impressed.

Yeah I've got to say- Brian- seeing your presense on the forum is truly a signifigant statement to me as an Avid user. I'm watching carefully how the upgrade to MC will effect me as a XPro user- and after some upgrade nightmares it really means something that can only be called reassuring (!) having some kind of connection with a human that actually works at making the software work! We're all engineers so we understand that nothings instantly perfect, but you just do your best with what you can do for your client... so it's nice to see that attitude coming from Avid, through you- too.

I don't expect that the upgrade to MC be perfect- there's too many variables- but to see your very easy to get, transparent attitude- makes a world of difference to me. Facing the expence and down time of an upgrade to a new app is a reasonably feared thing- but having the real possibility of a better running app to earn a better living- that comes from engineers just doing their best who are available to us... well, that really does mean something.

And it's a good shift in this user's perception of the Avid platform and the company that makes it.

Nice work dude. You deserve a raise! and the dvbuffers.ax thing has been a real help to me.

thanks- much appreciation-

Ev