Re: 23.98 HD timeline downconvert to beta sp - timecode issues by David Battistella on Mar 13, 2006 at 5:11:04 pm
I think this makes sense. I believe this is also the reason you need tri-level sync when dealing with 23.98 tc. The deck is not designed to work with 23.98 timecode as it does not operate on the 59.94 or23.98 time rates.
It makes sense that when you convert the sequence to a 29.97 timeline the KONA is spot on because you are not asking to do any kind of magical Timecode math by converting 23.98 timelines to 29.97 frames rates.
This is what dedicated software programs like Cinema tools were invented for.
Downconverting video and Audio is one thing, but FCP has notoriously poor timecode handling. If FCP were to hand time code from the timeline to the KONA folks I am sure that they could find a way to make it work, but alas, FCP only hands the first frame of timecode from it's timeline. Other
Re: 23.98 HD timeline downconvert to beta sp - timecode issues by weevie833 on Mar 13, 2006 at 6:14:25 pm
The dopey, time-wasting way to do this is to output to HD first, then DC to Beta-SP. The DC board in the HD deck shoul create the NTSC TC in realtime.
Another case for doing it this way too is so WHEN the client says they menat TWO dubs, not just one, you will have the HD master ready rather than occupying your studio for another hour just for an output. At least you will know that all your dubs are the same, in terms of TC accuracy.
Re: 23.98 HD timeline downconvert to beta sp - timecode issues by Jeff Bernstein on Mar 16, 2006 at 5:33:39 pm
Just for giggles, try using this http://aja.com/ajashare/AJA_VTR_Xchange_1-0.zip and see if you get a consistent in-point. If not, the issue could very well be the driver. In which case, this would be an AJA issue.
To use VTR XChange, export your timeline as a Reference Movie out of FCP.
And one more things... GO ORANGE!
Jeff Bernstein
Digital Desktop Consulting
Apple Pro Video VAR
XSAN Certified
