That is what worked for me.  Your milage may vary.  I have an approved Dell 390 configured specifically for AXP.  I couldn't get the audio to monitor on capture.  It would record, but I couldn't hear it.  I stopped using the onboard audio and added the Audigy and now it works.

Chris

I think you just saved me 20 bucks.  I'm not using the onboard audio (though I have tried this) and mine won't even record.

The problem exists in both Avid Xpress Pro and Avid MediaComposer and has existed for way too long. I for one will be ecstatic the day it's fixed. Capturing from VHS has been the biggest pain in the... It's been enough to encourage the use of on of the "other" editing applications.

Charles

So avid support can we get any estimation in what version this bug will be fixed ?

As i think we have waited long enough to get this fix.

 

1.  This is an Avid user forum, not an Avid support team forum.

2.  Avid don't speculate in advance about bug fixes or other software releases.

3.  Check the readme for release 5.8 which has just been posted.  See if that helps.

so release 5.8 is here and still AVID didn't fix this bug so how long do we need to wait as it look to me that this will never be fix in this rate.

 

5.8, XW8000, 2 gig, Qt 7.3,

Can't capture audio from DSR45 through Mojo dv in.  Picture is fine.  Audio shows on meters on Avid but is just not captured.  No errors just no sound on playbeack.

Remove Mojo,  Patch to built in firewire card and see picture but hear no sound, no sound on Avid meters.  Try to capture get "Videon signal present but not captured" error.

 

Well the plot thickens.  It seems it must TC related.  I can capture DV tapes now no problem except....if they are copied from the firewire out of my Pionneer DVD deck with my DSR set to external TC.  Whatever the Avid doesn't like about the TC coming from my Pionneer DVR-320 obviously gets recorded on my DSR.  I just retransfered the same DVD using TC set to internal and can now capture it sans problem.  Still can't grab directly from the DVD deck via firewire like I used to!!!

So, Marianne.  Please give us an answer.  What's the deal with this ongoing problem that many of us are dealing with.  I paid for the upgrade more than an year ago and can't use it!

So, Marianna.  Please, please, please give us an answer.  Or at least give us an update.  What's the deal with this ongoing problem that many of us are dealing with?  I paid for the upgrade more than an year ago and can't use it!

Bump (Come on, Marianne.  Give us some scoop.)

this "bug" first showed up v5.5 and beyond. I've posted my observations (and the known work-arounds) but I think those older posts are lost in the ether.

It is indeed a TC issue. v5.5 and up require contiguous and continuous TC supply from a source to properly ingest audio. Just a guess but it probably has to do with the "locked" nature of how AVID handles audio (to insure sync) and why open loop (unlocked) audio cards cause such problems. using a deck as a transcoder doesn't create the needed TC feed, so AXP just doesn't process the audio. Again just a guess, but processing the video portion of the source can probably fall back on vertical blanking intervals, or some other part of the video signal.

As many have discovered the work around is to give AXP what it wants. If you drop a tape into the deck being used as a transcoder and hit "record" (so the tape is actually turning/recording as it passes the signal) you get the required TC and AXP is happy. Another version of the same fix is to put the deck in "free-run" TC. Then just tapping the record button feeds out the TC (so you don't have to actually record the signal, saving tape and head wear) while I often do this, my standard workflow is to go ahead and record the signal, giving me a re-capturable source if needed. Or I use a canopus in the field, transcoders automatically generate a free-run signal (which is why they work despite this bug)

FWIW

So Avid Support will we get an answer ??????????

in this century

Avid support does not participate in these forums. This is for users only.

There have been many threads about this problem so I'm not sure if it's in this one but both Marianna an I have posted that the problem has been found and a fix is in the works. We should see it in the next release if testing goes well.

so can you gives as and info when will this release be available
at least an estimation as days months or more ?