Client asks me to do a text document with the timecode where the dialogue(s) begin.
Dropped the 29.97fps file they gave me on to my timeline in premier pro with the same settings, copied the in points of the dialogue and translated to standard english to a text document.
Client now requests the video in PAL.
Ran the file thorugh Compressor 3 (Because media encoder made it jumpy).... I'm figuring I'll have to go and adjust those timecodes in the text file now...
Client wants the video embeded with Vertical Interval Timecode...
"Your file is NTSC at 29.97 and began at 00:00:00;00...."
"... But it needs to have Vertical Interval Timecode at as STMPE."
So guys, is there a difference in this sort of timecode versus the timecode embeded in the DV file?
I have never heard of VITC in a file.
I used it years ago in SVHS tapes and Premiere was able to read it.
Someone can correct me but I believe it is an analogue "protocol" and I know no way of writing it to a file from Premiere.
Good luck Jason
VITC is data stored "between frames" alongside the blanking etc. ie. on the frame outside the image frames. The black or blank areas
Not sure where or how in a digital file that this could be replicated.
Maybe your client could provide the spec and "reason / purpose" and hopefully some one with the tech knowledge could add to this for you.
I wish I could talk to the persons directly applying the subtitles, but it's through an agent(my client). I'm thinking I'm not getting the information I need. In Final Cut 7 I can manually add specific timecode values for the video to start from... But I don't see why they would need this If I did a frame accurate copy of the timecode from a timeline based on the video file's frame rate.
So a break thought... The client said the file had timecode(surprise, surprise) but apparently I said it didn't have timecode(I said I don't think it would have VITC), so now it's just for the text document to have the corrisponding timecodes in PAL... which surprisingly was only a few frames off. I just rounded frames digits off to 22 and 25 at it's highest point... which seemed to work when I checked them back in the video.