Capture - Drop Frame Tape ? HELP!

Alright. We'll pick this up tomorrow. Go worry about your math test and see if you can get IT to reinstall Avid for you.
 
Good news here. Talked to IT and she is gonna just give me the disc in the morning to reinstall Avid. So all I should do is reinstall it correct?
 
Good morning, about to get this done. Just overwrite it though right? Im going get the disc right after my morning Cap! hehe
 
Correct. You might want to back up your project folder just in case (I'm a cautious person). :)

Hm ... sounds familiar. :laugh:
 
Yes I have backed that up. What I am doing now is Repair. Is that correct sir? Its almost done.... Waiting... Waiting... Waiting.. (I dont want to submit this reply only to turn around and oppps... got an error repairing :

Component : Avid Xpress Pro
File Group : PlasmaWipes_Archive
File : \FGdummy.tar.gz\
Error : Access is denied

Clicked ok and it closed. Should I just uninstall then reinstall?
 
Ok tried to load Avid to see if it would work and when I pressed play in the capture tool, the deck makes a clicking sound and doesn't really do anything. Now this, I doubt, is the decks because it has been doing the clicking and this is the second deck I tried. Same exact kind, just different one.
 
As well since Im letting you know everything thats happening. When I tried to close Avid just now An error has occurred :

Error occurred during exit method.
"Exception: std: exception, what,{MainThread]
Threads::SendThreadMessage: No running thread to r
WinFlamethrowerBusManager::StartBusResetThread Exit Message

it has more text but id have to scroll down. I pressed the down arrow key and this msg came up :

Microsoft Visual C++ Runtime Library
Runtime Error!
Program : C:\Program Files\Avid\Avid Xpress Pro\AvidXpressPro.exe

This application has requested the runtime to terminate it in an unusual way.
Please contact the applications support team for more information.

Clicked ok, it gave the same error once again then clicked ok and Avid terminated....

Ahhh it gets worse and worse im guessing.
 
HELP!!! Uninstalled then reinstalled and now its saying No Deck even with the Mojo connected as well as only having OHCI for the Video and Audio Inputs. HELP!
 
OK. One at a time.

Component : Avid Xpress Pro
File Group : PlasmaWipes_Archive
File : \FGdummy.tar.gz\
Error : Access is denied

This is a curious error. Access is denied generally means that another program was using the film in question (unlikely), or that it's set to read only, or you don't have admin rights on your computer (possible because you have an IT department). I'm further puzzled by this because I don't recognize that file, and .tar.gz files are rarely seen in Windows. That's generally a Mac / Linux thing.

I pressed play in the capture tool, the deck makes a clicking sound and doesn't really do anything.

Clicking sound? Like Avid is trying to take control of the deck or something else?

Error occurred during exit method.
"Exception: std: exception, what,{MainThread]
Threads::SendThreadMessage: No running thread to r
WinFlamethrowerBusManager::StartBusResetThread Exit Message

Flamethrower errors are related to the subsystem in Avid that controls Firewire. This could be a good clue, but we'll have to see.

Microsoft Visual C++ Runtime Library
Runtime Error!
Program : C:\Program Files\Avid\Avid Xpress Pro\AvidXpressPro.exe

Don't worry about this one. Runtime errors are no big deal and this was likely caused by the other errors you were getting to this point.

Uninstalled then reinstalled and now its saying No Deck even with the Mojo connected as well as only having OHCI for the Video and Audio Inputs.

OK, now we're getting into gray area for me since I don't normally work with a Mojo. My first impluse is to ask if Windows has recognized the Mojo. Try closing Avid, unpluggin Mojo. Rebooting, and then plug Mojo back in. See if Windows will recognize it, then launch Avid, and proceed.

Something that is a distinct possibility (and would explain everything that's happened to you) is that you're having problems with your firewire port on the computer. If memory serves, you're on a Dell, so I'm guessing you're using the built-in firewire port. Can you confirm that? Any chance that your IT department has a TI chip-based Firewire PCI card that you could plug in and see if that solves the problem?
 
Actually im using a PCI Firewire card on the computer atm. There are motherboard firewire ports on it but its not connected that way. Windows is recognizing the Mojo. The clicking sound is something like its trying to control the deck, I was just worried that its maybe a broken sound cause its unusual compared to the normal sound it makes. Hmm. What is the next thing I should try doing? Maybe using just the deck without the mojo?
 
Maybe using just the deck without the mojo?

I suggested that three pages ago. :huh:

Try connecting Mojo to the onboard Firewire and bypass the PCI card. That will help determine if that's where the problem is coming from.
 
Yeah I know, I remember and tried just the deck, it wouldn't show up remember?

I found out it was connected onboard so I switched to PCI and reloaded avid. Now it finds the Composite, DV, Component and crap and sees the Mojo BUTTTTT The deck is not found still. Actually it used to be found, just wouldn't play. Right now, its NO DECK. What should I do to make it find the deck? I tried deck config and set to what it was but its still not found.
 
Try Manually selecting a deck.

I think there's also a setting to tell Mojo to look for incoming video through the firewire port and not componet, S-video, etc. But again, no Mojo here, so I'm not 100% sure on that.
 
Well, you can if you want to. I think I still have some help to give. I just can't be Mojo specific, but that's why the good people at Avid built the Help file. :thumbsup:

Did you try to manually select a deck?
 
Hehe, yeah I went to avids new forums. They just put the new one up last night. Im sometimes a regular there. But as you said, i like it better here so I asked here first.


BUT!! Krest, you never believe it.

I just tried again and it worked. After another reboot, which is odd, all I need was reboot but its not like i didn't do that 20 times already. So everything seems to be working in perfect order. God I hate computers. Now i will never know what part of the fixing actually ended up working since it started working by itself. But hey, atleast it works!
 
Great. Now my last piece of advice: Don't touch it ever again. Don't even work on it. Just have piece of mind that it works. :)

Is it working off of the PCI card or the onboard FW connection?
 
haha easier said than done. I always gotta mess with stuff. But yeah im hoping my shop approves getting the 5.2 upgrade for us. That will help out with my 24pa footage right?
 
Back
Top