The Evil Mariachi
Well-known member
Hello Everyone,
Avid is driving me insane! Here's the deal: Every time I capture a tape in Composer, the capture tool will play and display as Non Drop Frame, the bin will show the NDF time code, but when it comes time to batch capture, the time code turns into Drop Frame and Avid refuses to capture!
I've looked all over the boards and while some suggest that creating a new tape does the trick, or popping in the tape and scrubbing through it before naming it works, none of that changes a thing for me. I've done all this plus restarting, with/without tape and yet nothing works!
It's just so damn bizarre--I mean, the footage is shot at 24pN with the original DVX which by default shoots NDF! You can't change it! Could it be my deck? I've been using a cheap panasonic camcorder to capture--but I've also tried with the DVX and still get the same problem.
This bug is seriously setting me back. I honestly hope I'm doing something wrong, otherwise it would mean that Avid hasn't been able to fix a bug that's been plaguing its software forever.
Thanks in advance for any help you guys can offer.
Avid is driving me insane! Here's the deal: Every time I capture a tape in Composer, the capture tool will play and display as Non Drop Frame, the bin will show the NDF time code, but when it comes time to batch capture, the time code turns into Drop Frame and Avid refuses to capture!
I've looked all over the boards and while some suggest that creating a new tape does the trick, or popping in the tape and scrubbing through it before naming it works, none of that changes a thing for me. I've done all this plus restarting, with/without tape and yet nothing works!
It's just so damn bizarre--I mean, the footage is shot at 24pN with the original DVX which by default shoots NDF! You can't change it! Could it be my deck? I've been using a cheap panasonic camcorder to capture--but I've also tried with the DVX and still get the same problem.
This bug is seriously setting me back. I honestly hope I'm doing something wrong, otherwise it would mean that Avid hasn't been able to fix a bug that's been plaguing its software forever.
Thanks in advance for any help you guys can offer.