Followed directions for upgradiing to MC3 fromXpro 5.8. When launching MC3, window stops at Autoconfiguring Transport Machines. Talking to Tech, but they aren't sure yet why. Anyone hazard a guess? Tried uninstalling several times wiping out all references to Avid in HKLM software, no joy.

ATM is related to deck control configurations and decks templates.

When you unistalled did you delete the left over Avid installation folder in Program Files? (backing up projects folder of course).

Deleted everything Avid in explorer. Still hangs in the same place. Reinstalled 3 times now.....

Ran Debug view as you suggested to someone else here are the last few lines

00000045    1.59142542    [2788] DIOWinDeviceLoader[1]: Starting dynamic DIO load    
00000046    1.59174275    [2788] DIOWinDeviceLoader[2]: DIOPyromaniac.dll    
00000047    1.59177268    [2788] DIOWinDeviceLoader[3]: DIOloader - Loading DIOPyromaniac.dll    
00000048    1.59419000    [2788] DIOPyromaniac DLL Loaded    
00000049    1.59421802    [2788] DIOWinDeviceLoader[4]: DIOloader - Checking version number    
00000050    2.53688455    [2788] DIOWinDeviceLoader[5]: DIOloader - Retrieving base object    
00000051    2.53698301    [2788] DIOWinDeviceLoader[6]: DIOloader - disabling thread calls to DLL    
00000052    2.53701544    [2788] DIOWinDeviceLoader[7]: DIOloader - completed    
00000053    2.53705430    [2788] DIOWinDeviceLoader[8]: DIOPyromaniacOHCI.dll    
00000054    2.53707528    [2788] DIOWinDeviceLoader[9]: DIOloader - Loading DIOPyromaniacOHCI.dll    
00000055    2.53953123    [2788] DIOPyromaniacOHCI DLL Loaded    
00000056    2.53955913    [2788] DIOWinDeviceLoader[10]: DIOloader - Checking version number    
00000057    2.56178546    [2788] MSDVStream::BuildGraph - Cannot create video capture filter    
00000058    3.57351446    [2788] MSDVStream::BuildGraph - Cannot create video capture filter    
00000059    4.59232187    [2788] DIOWinDeviceLoader[11]: DIOloader - Retrieving base object    
00000060    4.59237766    [2788] DIOWinDeviceLoader[12]: DIOloader - disabling thread calls to DLL    
00000061    4.59239912    [2788] DIOWinDeviceLoader[13]: DIOloader - completed    
00000062    4.59242344    [2788] DIOWinDeviceLoader[14]: 2 device types loaded    
00000063    5.97107601    [2788] SharedLibrary - LoadLibrary failed on aecifs (code 126)    
00000064    12.03533936    [2788] SharedLibrary - LoadLibrary failed on DirectIOInterface (code 126)    

00000063    5.97107601    [2788] SharedLibrary - LoadLibrary failed on aecifs (code 126)    
00000064    12.03533936    [2788] SharedLibrary - LoadLibrary failed on DirectIOInterface (code 126) 

The error code for the last two errors (above) indicates that the system couldn't find those libraries (aecifs.dll and DirectIOInterface.dll respectively).  That would seem to indicate that your installation is incomplete or that something has removed the libraries.

I know that it's a pain but I would suggest using the Media Composer uninstaller to unstall everything, manually scrub the C:\Program Files\Avid tree and try again.  Remember to reboot in between the uninstall and the re-install just to be safe.

Did that several times, even went as far as downloading 3.0 from the Avid site insted of using the disc I was sent, still get the same error. Any idea where those files SHOULD  be so I can check if they are in ther proper location?

Did a search for those two files and they do not exist on my computer. Are they on anyone elses? How can I extract them if they are ?

Looking in the source code, I see the "Autoconfiguring Transport Machines" message appears after the AECifs and DIO are initialized. So the problem may not be related to the DLL errors in the DebugView log.

Here's a couple of quick things to try:

Hide (by renaming) the Site_Attributes and launch the app. The file is in

  C:\Documents and Settings\All Users\Documents\Avid Media Composer\Settings

Another thing to try is holding the "C" and "M" keys down when launching.

- Rob

Holding c and M launched it. So what does that mean problem wise? where do i look to repair?

Clement Canino:

Holding c and M launched it. So what does that mean problem wise? where do i look to repair?

you must ask yourself how you could have been so stupid as to have not anticipated that- it's soooo obvious! duh!

OK, some of us aren't as well informed as you are, what stupid thing did I miss? What does holding C and M do exactly? Please excuse my ignorance as I never had this problem with X Pro. By the way, Avid tech didn't suggest trying that either.

There is a file called Site_Attributes that, among other things, keeps track of the configuration of tape decks. The first time you run, it configures the system and writes the results into the SIte_attributes file.

Holding down the "C" and "M" keys forces a re-configuration.

Try quitting the app and launching again without the CM keys.

- Rob

that's exactly what I meant to say... sarcastically...sorry

just press C and M- but, of course! who didn't see THAT coming?! If you're coming from XPro- that's kinda unpredictable, eh?! I'm wondering how weird the MC upgrade needs to get before I pay money for it... I'm just searching the forum...

I'm kinda wary

Thanks all. I had no idea what holding the CM did. That did the trick though, on restart it worked flawlessly, even with my realtek hd audio. Go figure everyone having problems with audio cards, I get a rogue config file that doesn't fix itself in 4 reinstalls. Now lets see how long it takes to get a respnse from the tech I spoke to earlier in the day from Avid...

 HI all,

I locked this post as the issue has been solved. :) Thanks Rob G.

Marianna