Kevin Downer
Forum Replies Created
-
I find the problem with the FCP interface is not the layout, but rather the lack of serious customization. After familiarizing oneself with things like hotkeys, who really needs the space hogging play bars under the video windows. This is one area where the AVID does allow one to make a pure bare interface and use hotkeys for everything that had a icon button
Another problem is the inability to customize the default locations of tabs. It should be possible to save a moved tab window as a default. I hate that every time a clip is loaded in the source window, the keyframes effects tab moves back to that space-constricted window. Just having the ability to initiate sticky tabs would be so useful and easy to implement.
As mentioned, darkening the interface to a neutral grey would be great as well.
Some of the few things I hope are implemented in FCP 7.
-
Yes, this has always been an obtuse and confusing workflow for Avid.
I also export RGB as well. The only problem is while it matches the digital-file colour space in AE and FCP, it also clips anything over or below those levels. So if you export something that has not been colour balanced, you might lose information.
Also, if you mix your YUV export with image files in RGB in AE and then export, your levels get messed up unless you have a workspace designations for each file.
As mentioned, make sure you import as YUV into Avid no matter what the colour space. Again, Avid just figures it out and the RGB import option just slows the process down (even though it seems correct for an RGB file to choose that option: ARGH!).
Confused yet? I do not mean to seem hot under the collar but Avid’s methodology has remained a confusing, arcane art for too long.
Avid, by maintaining backwards compatibility, seems doomed to their unique methods that do not match any other application but their own. If they just explained the workflow in their manual it might help, but for some reason they fail to do so. There is no excuse for this continual omission, resulting in frustrating editors and graphics designers for years.
-
You could also get the person who gave you the original project to export it as XML Vers. 3. You could then import that into your older version and it should translate over fine. That is probably your best bet and you don’t have to mess around.
Why FCP does not do this by default is very annoying.
-
I guess I’m not sure what you would be trying to accomplish here.
FCP seems to treat the function very much like After Effects. If one had a layer covering the whole area and something with an alpha above it, both programs would provide an alpha: It just would not be of any use. In AE, one would have to “Shy” a video clip underneath and in FCP, one would “Hide” the layer.
To get around the problem of losing one’s entire rendered timeline, one could Subclip the section of the sequence and then delete or hide the underlying video clip of that sub-sequence, export a QT with Alpha, and then re-import to replace that section of the sequence.
That is what the original person posting seemed to be trying to achieve. The issue seemed to be if it was rendered, one could not export an alpha which is not the case.
If one had the same setup layers in AE as you described in your example FCP sequence, the same situation would arise, unless one hid the underlying video clip.
Basically, if you can’t see a defining alpha displayed in FCP when switching views in the Record window, one will not successfully be able to export a useful alpha.
-
Yes, one can render or not render and will still get an alpha based QT by exporting a codec that supports them. I just did this in a rendered DV NTSC sequence just to make sure. I have no idea why some people seem to have problems. Different versions of FCP perhaps?
I am not sure about the straight only being exported from FCP. I just did both Animation and PNG QT outputs to test. While a program like AE guesses them to be straight, they actually seem to be pre-multiplied on black. Otherwise one gets black fuzz on soft edges of PIP effects, etc. If one chooses premultiplied on black, they are interpreted correctly. Something to do with the QT wrapper changing the PNG straight for some reason. Weird. Wish I could just Export Image Sequences from FCP to avoid the muddling 2-step procedure.
-
Hey Brett.
The problem is the blank space. If there is some space between clips, one cannot dynamic trim the blank to enlarge or reduce the space. It just does not work.
I think AVID treats it as black slug while FCP treats sees no way to show nothing to display in dynamic, so it won’t let one do it.
Give it a whirl and you’ll see what I mean.
AVID has it’s own share of issues but I think they really nailed the editorial assets of their software. FCP will get there soon (I hope).
-
Andy, you are partially right so don’t feel bad. The dynamic slip/slide in AVID is not currently present in FCP. There is also not the 4-Frame display mode that one may be used to. Not a bash, just a case of circumstances.
Tom, just to clarify your solution presented: While the shortcut method you described is sound, I think it only applies to the Slip function of multiple clips.
If one tries the same method with Slide, FCP for some reason, decides to slide the multiple clips but also erroneously decides to slip the cut points of the clips. The result is the clip edit points do some weird staggering duration change. It’s a real pain.
Any idea why this occurs? It sure leaves me confused and can seriously mess an edit in a big way with large sections of clips selected.
To Slide, I find it is best just to multiple highlight clips, drag and then quickly extend edit the blank space left behind. A better method would be helpful if someone knows of one.
-
I guess I was too wordy. Succinct as always Tom.
-
It may seem a little frustrating at first used to AVID.
Mr. Wolsky is great at being succinct. Unfortunately, I am not. 🙂
In my opinion, the trim tools are just more refined and elegant in AVID. Now that we got that out of the way, here are some things that might help you adjust:
-To get a more AVID style of trimming, you will want to enable “Dynamic Trimming” in the FCP User settings under the Editing sub-menu.
-There is a pretty big drawback in FCP when trimming blank space between clips. One can go into dynamic trim mode and use I or O to shuttle the space, but jkl dynamic functions will not work. I, O Shift Delete for a specific amount, diddle with the roll edit mouse/numeric keypad number method or highlight the space and Delete to lose it all.
-One could also introduce slug for blank space with clip characteristics. This allows one to manipulate the blank space a bit more and make add edits (with the blade tool) for using tail space as synch positioning for multi-layer reference.
-In roller or ripple mode, one can select unlinked clips by holding the command button while you select. Holding Shift as well changes roller to ripple if you need to. One can then promote to your more familiar dual trim windows by the Trim Edit command (Command-7 by default). This is also handy if you use G to lasso a bunch and then want to asynchronous trim to get back the dynamic mode. Sometimes it will switch out of that mode if you mouse-click erroneously.
It’s clunky compared to AVID, but FCP has some handy functions and tricks that AVID could take some lessons from.
Editing on FCP isn’t AVID, but it’s not crap either. It will hopefully improve with more fundamental editorial needs in mind with future updates.
-
Grinner, I’m a bit confused. Are you saying you did media relatives with the clips or sequence and had the option to delete the audio or video and it did the wrong one?
If so, that’s a serious problem I was not aware of.
Thoughts?