Steve Braker
Forum Replies Created
-
Well, you may have a partially wrong perception of user bits. I can’t tell what “iterate” means in this contxt, but recording TOD like this was a very common way to “get it both ways” in the good old days.
That said, I can’t say I ever edited directly from user bits. But it was a very easy way to find and set a timecode offset so you could edit with TOD in a linear setup.
John, search here for Bouke or look at videotoolshed.com. He’s got something cooking in the way of LTC imports in FCP. Maybe it will deal with this too.
-
Well, you may have a partially wrong perception of user bits. I can’t tell what “iterate” means in this contxt, but recording TOD like this was a very common way to “get it both ways” in the good old days.
That said, I can’t say I ever edited directly from user bits. But it was a very easy way to find and set a timecode offset so you could edit with TOD in a linear setup.
John, what format is your material in?
-
Perhaps Bouke will be the one who proves me wrong:
https://forums.creativecow.net/readpost/8/927743?
-
Unfortunately I don’t believe user bits are supported in FCP. Which makes as little sense as DV data not being supported, Line 21 not being dealt with, etc.
I’m guessing there are outboard ways to convert UB to TC. But then the result, AFAIK, won’t be usable by FCP because there’s no way to import it.
Wish I could be more helpful, and I hope someone proves me wrong.
-
BTW I am still on 5.1.2 and associated QT, PB15 and OsX 10.4.8. No comments?
-
Thanks, John. If you get them I wonder what’s going wrong here, because they are simply gone for me here.
All clips default to original levels (0dB).
All fades put in using “cross dissolve” at lonely clip ends are missing.
Only crossfades (between adjacent clips in a track are maintained.Do others get this behavior?
-
Sauciness is cumulative frustration with what seem like basic video things people should know about long before getting into something like FCP. I do apologise – like I said it’s a cumulative effect and shouldn’t be directed at you.
Here’s a more normal response to the question: In short, seeing interlace jitter on a paused frame with motion is completely normal. If your Canvase / Viewer are set to 100%, you will see jagged edges in the same places that jitter on the CRT. Also normal.
If you see jitter during playback then there’s an issue of some sort.
-
Time Code Reader will do a window burn on clips of their source time code.
Time Code Generator would go on a nested sequence to show the sequence code or any time you want. It doesn’t really generate code, it just does a window burn.
-
Do you expect your viewers to be pausing your stuff on their FCP output on a CRT monitor?
Leave it alone and go learn about interlace. Search on that word in the manual, it’s pretty good with that sort of thing.
-
“The sound guy” is the best one to tell you how to prep it. Anything any of us tells you will be the exact opposite of what he wants. Go to the person you plan to work with.