Latest post Sat, Jan 25 2014 10:18 PM by mtahir. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • Fri, Jan 17 2014 4:24 PM

    • mtahir
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • UK
    • Posts 480
    • Points 5,865

    MC5.5.4 + Mojo + 002 problems...

    With MC5 connected to an analog Mojo and the Digi 002, when playing audio in the timeline, the audio won't play through the 002 - I eventually get a 'Adm' error. If I put caps-lock on and scrub the timeline, the audio does play through the 002. These are some of the errors that I get:

    20140117115503 FatalExcpt Exception: ADM_DIO_ERROR_OCCURRED, DIOerr:Flamethrower timeout: Transmit request timed out 200.067000 milliseconds
    20140117115505 FatalExcpt Exception: ADVAudioDev: Failed to set external sync source
    20140117115511 FatalExcpt Exception: DVAUDIO_MANAGER_LAVA_EXECUTE_ERROR
    20140117115612 Startup    Hughes_Release_R20470 (Vista Media Composer 5.5.4)
    20140117115646 Startup    Hughes_Release_R20470 (Vista Media Composer 5.5.4)
    20140117115708 Hardware   Mojo
    20140117115729 FatalExcpt Exception: ADM_ILLEGAL_SYNCSRC
    20140117115733 Ready      Application ready for user
    20140117122203 FatalExcpt Exception: Overrun on transmitting MIDI data
    20140117122237 FatalExcpt Exception: AdmAdm overrun.
    20140117122516 FatalExcpt Exception: AdmAdm overrun.

    The MIDI error is with a WAV file that I imported for testing. Typically, it's the 'AdmAdm overrun' pop-up box that appears. I've tried a whole raft of things from the video driver to re-installing but it doesn't work. I didn't have such issues with MC5.5.3.

    Dare I take the opportunity to say that ADM_ILLEGAL_SYNCSRC is still present. We've been banging on this drum for a few years now. We are getting updates and I was hoping this would be fixed by now.

    Thanks

    Mohammed


    MC2018.1 (Win7) | Dell T7500 with 2 x 6-Core Intel Xeon X5690 3.46GHz CPUs | Triple-Channel 64GB (32GB per CPU) 1333MHz DDR3 EEC FBDIMM | 3GB nVidia Quadro... [view my complete system specs]
  • Sat, Jan 18 2014 12:29 AM In reply to

    • mtahir
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • UK
    • Posts 480
    • Points 5,865

    Re: MC5.5.4 + Mojo + 002 problems...

    Here are some errors from the Event Viewer in Windows:

    Flamethrower FATAL error  Proc xmit drop frame.

    Not enough memory was available to allocate internal storage needed for the device  Acquire isoch frm acqfrm is 0.

    MC2018.1 (Win7) | Dell T7500 with 2 x 6-Core Intel Xeon X5690 3.46GHz CPUs | Triple-Channel 64GB (32GB per CPU) 1333MHz DDR3 EEC FBDIMM | 3GB nVidia Quadro... [view my complete system specs]
  • Sat, Jan 18 2014 1:08 AM In reply to

    Re: MC5.5.4 + Mojo + 002 problems...

    Flamethrower is usually asociated with Firewire problems.
    Are your issues on your MC 5.5 with Windows 64 bit?

    Have you tried Windows hereditary drivers with firewire? Somewhere around version 4 or 5 AVid changed which Firewire cards it approved. Sorry my memory is a little vague on the details of this but may give you a starting point for a forum search

  • Sun, Jan 19 2014 6:10 PM In reply to

    • mtahir
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • UK
    • Posts 480
    • Points 5,865

    Re: MC5.5.4 + Mojo + 002 problems...

    Thanks. Yes, it's how I've run it with the drivers in legacy mode. However, I have go to the bottom of it. I had installed Win7 SP1 and I thought perhaps that it may have caused problem. So, I went back to removing the variables. One thing that I found that got rid of the errors logged in Event Viewer in Windows was this hotfix for SP1 (https://support.microsoft.com/kb/2524249). Someone had posted this on this forum a while ago. This caused the 'Adm' error.

    In the end, the problem was MC5.5.4. Once I removed it, and went back to MC5.5.3, it was all working again. I've not had any luck with the patches between 5.5.3. and 5.5.4. And we still have no fix for the ADM_ILLEGAL_SYNCSRC issue either.

    MC2018.1 (Win7) | Dell T7500 with 2 x 6-Core Intel Xeon X5690 3.46GHz CPUs | Triple-Channel 64GB (32GB per CPU) 1333MHz DDR3 EEC FBDIMM | 3GB nVidia Quadro... [view my complete system specs]
  • Sat, Jan 25 2014 10:18 PM In reply to

    • mtahir
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • UK
    • Posts 480
    • Points 5,865

    Re: MC5.5.4 + Mojo + 002 problems...

    It seems that MC5.5.3.7 also causes the Mojo + 002 audio problems. It probably sneaked in one of the earlier patches. I would hazard a guess and say it's after the .3 patch as I used to have this but removed it because of an issues with audio dissolves not working correctly when rendered. I don't remember any other issues. So, it's probably somewhere in the .4 to .7 patches.

    MC2018.1 (Win7) | Dell T7500 with 2 x 6-Core Intel Xeon X5690 3.46GHz CPUs | Triple-Channel 64GB (32GB per CPU) 1333MHz DDR3 EEC FBDIMM | 3GB nVidia Quadro... [view my complete system specs]
Page 1 of 1 (5 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller