Shane Ross
Forum Replies Created
-
This is the forum for the old, outdate, discontinued FCP 7…for a place to get the answer you want, go to the FCPX forum….
https://forums.creativecow.net/fcpx
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Bob-Zelin like in snark? RIFE with F-bombs? Hopefully aimed at those in charge of the naming convention, and not at me. I really hate going head to head with you on this…because I know you know this stuff VERY well. I just know I’m right here…
*RUN*
🙂
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Bouke Vahl] “And yes, I do know this stuff, and perhaps a tiny bit more.”
I know you know more about this stuff that I do…I’ll admit. But in this one case, I believe you are wrong. Thus my shock in your answer…you know loads more than I do about this stuff. It’s just this terminology that causes confusion.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Bouke Vahl] “50i means 50 INTERLACED frames per second, thus 100 FIELDS per second.”
Sorry, no. You are wrong. There is no such thing as 100 fields per second. No such thing as 50frames per second, interlaced. The only interlace frame rates are 25fps…and 30fps. 50i (25fps) and 60i (29.97fps). 60i is not 60 frames per second, interlaced. There is no such thing.
The video consortium of know it alls decided to go with 1080i60 instead of the better terminology 1080i30 (or 1080i29.97) because…well, because. I know in Europe, most people don’t go with that and use 1080i25 to indicate 25fps interlaced (50 fields per second)…and I agree that’s a better thing. FCP 7 would only show 1080i 29.97, even with an AJA card…because that makes sense. But no, the correct terminology (that I don’t like) is 1080i50 is 25fps interlaced…50 images per second…two image per frame.
Sorry, you are just wrong here. I’d love ANYONE ELSE to step in and back either one of us up.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
No. Because AVCHD is a crappy format. Mainly crappy in that timecode always restarts at 00:00:00:00…clip names start over again when you put in a new card…so you can have multiple clips with the same name and same timecode start…thus why you need UNIQUE REEL numbers so that every NLE knows what is what. Resolve actually tries to solve this on it’s own by reading the creating time…this helps IT track it better. And FCP 7….eight years old and EOL…hasn’t done anything to make it better.
So what you did was the best thing…and typically what you’d do at the time of ingest so things won’t be quite as overwhelming in the end.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Bouke Vahl] “No, the framerate is the framerate. 50 runs at 50. “
Bouke…I thought you of all people would know this.
1080i50 doesn’t run at 50fps…it runs at 25fps. 1080p50 runs at 50ps
The letter preceeding the number does indeed mean IMAGES PER SECOND…but “i” means interlaced…so yes, 50 images per second, but there are two FIELDS in a FRAME…so 50 images, two per frame…25fps. The “p” means PROGRESSIVE, so 50 images per second PROGRESSIVE means 50 FPS. The “i” and “p” are important here.
[Bouke Vahl] “There is no 50i as standard, only 25i. (Perhaps it does exists if you overcrank a camera)”
https://en.wikipedia.org/wiki/1080i
“The European Broadcasting Union (EBU) prefers to use the resolution and frame rate (not field rate) separated by a slash, as in 1080i/30 and 1080i/25, likewise 480i/30 and 576i/25.[2] Resolutions of 1080i60 or 1080i50 often refers to 1080i/30 or 1080i/25 in EBU notation.”
I guess we need to ask the Original Poster…are we talking 50 full frames per second, or interlaced and 25fps. Look at the timecode to figure that out….if it goes to 24 and then to 00…it’s 25fps.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
25p runs at 25fps. 50i also runs at 25fps…just needed to have that out there. But yes, 50i has two different fields per second, so has 50 images per second, so appears smoother
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Split your clip….add the LUT to the part you want, but not to the other, and then add a dissolve between them…that’ll do what you want.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Hmmmm….question. How many audio tracks do you have on this project? If you have more than 8, go into the USER PREFERENCES (in the FINAL CUT PRO menu) and change the REALTIME MIXING number from 8 to like 32…or 64. Dunno why it defaults to 8, but you can have up to 99 in realtime.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Try converting to 16 bit…see if that does it.
Now…WAV….but not BROADCAST WAV? FCP works with AIFF and broadcast WAV…but not regular WAV files.
Shane
Little Frog Post
Read my blog, Little Frog in High Def