-
720 P Still not fixed in 5.0.3
Pretty amazing. I want to like this product but Apple’s rock headed-ness is hard to understand. 5.0 still has bugs from 4.0. “Incompatible compression settings” when pushing the button for edit to tape for example. The 720 bug doesn’t happen if you use capture now only when you mark ins and outs and then capture.
I used a Kona 2 with FCP 4.5 at the World Series and it worked pretty well. Only a couple of crashes and I don’t think I ever had to trash the prefs.
-
30 Replies
-
The edit to tape buttons haven’t worked since v2 as far as I can remember. The simple workaround is to drag the sequence icon from the browser over the ETT window and drop on the pop-up Assemble button (or Insert, Preview). I probably outputs three or four programs a week using this method. All are spot on frame accurate.
Can’t speak personally as to the 720p issue. However, my partner just completed a feature in FCP in which the entire project was captured and output via Kona2 and FCP 5. It took a few AJA driver updates, but the Batch Capture feature was finally accurate.What’s your exact problem with 720p in FCP 5?
Michael Alberts
Ambidextrous Productions, Inc. -
Yeah I know there is a work around on the ETT it just amazes me thqat version after version comes out and it’s still the same. The 720 problem has been discussed here before. If you capture 720 footage from HD-SDI the clip comes in black and as a subclip. You can remove subclip limitations and see the video but the clip will be twice as long as captured with one half of it black. You can re-import the clip and it is OK, but it’s pretty that this is evidently a low priority bug for Apple.
-
[Robert Brown] “You can re-import the clip and it is OK, but it’s pretty that this is evidently a low priority bug for Apple.”
FCP 5 will definitely go down as one of the buggiest software Apple has ever put out, especially since so many things that used to work are brokend now.
The 720p HD-SDI capture issue is really the most stupid thing I’ve seen in the app and basically makes it a huge chore to work with.
Yep, it’s kind of hard to keep liking the app and supporting it when Apple doesn’t seem to want to even fix the basic stuff like a simple capture bug.
Walter Biscardi, Jr.
https://www.biscardicreative.comNow editing “Good Eats” in HD for the Food Network
“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
-
In what way haven’t the edit to tape buttons worked? Where are you editing from? The work for me if the item is loaded in the viewer.
-
I think 5 is far less buggy than 4 was. That was a real dog when it was first released. Apple is having a lot of problems with the 720 format no doubt. Apple’s probably saying it’s AJA’s fault. What’s AJA saying about it? Probably that it’s Apple’s fault.
-
[Tom Wolsky] “Apple’s probably saying it’s AJA’s fault. What’s AJA saying about it? Probably that it’s Apple’s fault.”
It’s not an AJA issue. 720p HD-SDI clips are perfect on the hard drives, FCP sees them as a subclip. AJA would not cause the application to read a correctly captured clip as a subclip.
Been broken since FCP 5 first came out.
Walter Biscardi, Jr.
https://www.biscardicreative.comNow editing “Good Eats” in HD for the Food Network
“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
-
[Tom Wolsky] “I think 5 is far less buggy than 4 was.”
Have you nested Photoshop graphic lately? Bring in a 25 layered Photoshop file for use as titles in an episode and a second Photoshop file which contains the lower third element. Now take one layer from the Title file and one layer from the Lower Third file and place them above your video in the Sequence. Nest those layers together. Give that nest a name.
Now look at your Nest in the Sequence and look at the nest in your Browser. In the Sequence, it’s the name you gave it. In the Browser it has the same name as the original photoshop file that was the top layer, not the nested name. It should be the nested name and this worked in every version of FCP prior to 5. So what I end up are 25 nests in my Browser that are all the same name. Now multiply that by 22 episodes per season. That makes it oh so easy to distinguish which nest is which.
720p HD-SDI captures worked perfectly in FCP 4, now it’s broken in FCP 5.
Instead of concentrating on all this “Gee Whiz will you look at all the new features” it would be nice for the FCP team to actually keep basic functionality working.
Walter Biscardi, Jr.
https://www.biscardicreative.comNow editing “Good Eats” in HD for the Food Network
“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
-
Does this happen only on capture, or even if you import the clip, which you say is fine in QT and on the hard drive?
-
I can’t say it would ever occur to me to work like that, but yes indeed, it behaves the way you describe, and it obviously shouldn’t. What’s worse is that when you make a nest this way the naming is not recursive. You can change the name of either sequence independently, unless you replace the nest with the one in the browser, then the naming convention returns to normal, changing one name changes the other.
-
[Tom Wolsky] ”
Does this happen only on capture, or even if you import the clip, which you say is fine in QT and on the hard drive?”The happens during a logged capture, such as Capture Clip or Batch Capture. Capture Now works perfectly and importing the clip works perfectly. However, importing the clips is not the preferred workflow and I stil have to manually re-insert material because FCP does not reconnect the clips into a Sequence correctly all the time with 720p material captured HD-SDI.
Walter Biscardi, Jr.
https://www.biscardicreative.comNow editing “Good Eats” in HD for the Food Network
“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
Reply to this Discussion! Login or Sign Up