No. Sorry.

daryl5:

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

BLKDOG:

We should see it in the next release if testing goes well.

And the key phrase here is if testing goes well.  Software development is still part art, part science.  Just because a fault has been identified doesn't mean that a fix will quickly follow.  The more complexity in a program the harder debugging becomes.  The longer the life of a program, the more legacy code you have, and again, the harder debugging becomes.

For example, the block of code that has caused this problem may be called from a wide range of places for other purposes.  Fixing this problem may introduce other problems.  For example it may cause audio sync issues or stop chroma key from working or prevent you using any codec other than DVCpro 50.

So after the fix the software must be thoroughly checked for all sorts of other unexpected side effects.  That's why BLKDOG said "if testing goes well".

i can tell you that i know how the system works as i also work in a big company that manufacture software still if a customer has report a bug and this is a huge bug the developing team will start to work on a fix ASAP , and yes it can take time as few months but we will give the customer a road map as say it will bee ready in this month.
Still  problems occur and it can bee that in the end date it is still not ready but in this case the customer again will get a new estimate when this fix will bee ready.

and this also work in big company's like Symantec this i know i have found a huge bug  in one of there release as i have this in an email that i have get from then and yes i needed to wait a few months for this fix still they didn't release any version before they have release a version that includes my fix.

so i think that if this bug is really on the development team time table they may have release a fix for that earlier in the release that came after this has been reported

or still give as any time table as when it will bee ready.

Well I'm sorry to say that it doesn't work that way with Avid. All I can say is that the problem has been reproduced and is a high priority fix for the next release.

Avid does not announce release dates for their software so we just have to sit tight.

BLKDOG:

...a high priority fix for the next release.

This is the best news I've heard in a long, long time.  Thanks for finally the positive update.

 

I'm having the same problem on a Mac with 5.8 and a Miglia's Director's Cut 2 breakout box to digitize a VHS (composite to breakout box to firewire). It was working before I upgrade from 4 to 5.8 (but I had to upgrade since 4 doesn't work on OS X 10.4.11).

I definitely think it is a timecode issue since I was able to digitize audio without a problem using a Sony DSR-25 DVCAM Deck and direct firewire. Unfortunately I only had temporary access to the DSR-25 deck so I'm not able to fake out the Avid.

Any suggestions other than digitizing with something else like FCP? I am confused about how to implement this workaround:

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)

I had problems as well that were solved by switching my deck configuration to "transcoder".  Then it didn't care about the TC issues.

Tried that.  It didn't work for me.

Sorry to hear that.  I only mentioned it because I felt like an idiot when that solved my issue.  Good luck.

I asked at least 3 different Avid guys at NAB if this problem is fixed in the forthcoming 3.0 version. The answer, "What problem? We've never heard about this problem."

Seriously.

Charles

They know about it. It's been repro'ed and a bug number has been assigned to it.

 And again Avid release a new version and still this bug is not fix

why !!!!!!!!!!!!!!!

Daryl, you have to read the release announcement. This is a CPR patch, not a full release. A CPR is released to fix very specific issues, not all but fixes make it into these point releases.

 but what happed all the time even on big release Avid development team ignore this big that was reported long ago and the fix they do fix are small bugs that very little people encounter ,

but this bug which is huge and bother a lot of people they ignore and this i really don't understand way ?