Finds preroll point just fine. Prerolls, then drops into record. Drops right out again, with error.
More testing reveals:
Same exact sequence performs flawless digital cut with same deck but from system with a Nitris DX, so I'm pretty sure it's a MC<->IO Express thing. All assemble edits, and this only happens with the Digi - tried an SR assemble edit with the IO Express and it went down fine.
I'll try flipping the deck to input video ref instead to see if that helps.
Maybe a better question now that I have a little more testing in is: anybody with an IO Express able to lay off to a digibeta?
Thanks for the suggestions,
Mark
On Dec 27, 2011, at 4:15 PM, "johnrobmoore" <bigfish@pacbell.net> wrote:
> I usually get the coincidence point error when the deck is trying to find the preroll point. I think they changed the wording to include the possibility the tape or deck is record inhibited. Any chance of a drop/non drop mismatch? Are you insert or assemble editing? Could the deck be regenerating the wrong timecode df/nd when it goes into assemble edit? For giggles see if you can do a proper machine edit while feeding the deck the Avid signal.
>
> --- In Avid-L2@yahoogroups.com, "Mark Spano" <cutandcover@...> wrote:
> >
> > Hi folks,
> >
> > Wonder if any of you have had this issue and how you got around it. I have a current issue Mac Pro running 10.6.8 and MC 5.5.3.1. Have just installed the IO Express and have the 9.0.5 drivers for it, and using a Keyspan adapter for serial control. Everything is working as expected in MC - proper video output, can change settings and lock to reference. But when I go to perform a Digital Cut to a Sony DVW-A500 DigiBeta deck, it prerolls, goes into record, and then drops right out. It gives me an error about trying to locate coincidence point on tape. I have checked this exact same setup with FCP on this system using the IO Express and Keyspan and everything goes off without a hitch. Just can't output to tape with MC. Hoping someone here has an idea.
> >
> > Thanks,
> > Mark
> >
>
>
[Non-text portions of this message have been removed]
No comments:
Post a Comment