David Johnson
Forum Replies Created
-
It’s hard to say what you might be doing wrong without knowing how you’ve tried to do it, but you can simply save an image with transparency from PS as a .psd, open that in AI and voila.
Perhaps you just need to “show transparency grid” in AI (SHFT+CNTRL+D).
-
Just to reaffirm what John suggested, the most important technique will be to use a separate audio editing application … as with all video editing applications, FCP only has basic audio editing.
As you will find, cleaning up poorly recorded audio is not at all easy (unless the noise is only minor and the intended audio is at a decent level) so you’ll save yourself a lot of headaches and time by doing whatever is necessary to get good audio to start with (ie, never rely on a camera mic only unless you just want ambient sound).
-
I have two suggestions:
Also post this on the “JOBS Offered – Low/No Pay” COW forum.
Provide more details about your needs … how much work, how complex, deliverables format, how info and files will get from/to you, etc. You might even consider posting the actual list of titles and lower thirds you need and some sort of description of what you have in mind design-wise. Basically, what I’m getting at is are you talking an hour worth of work, a full day worth, a week? It seems most people would be reluctant to volunteer without knowing what they’re really getting themselves into … I know I am.
-
That is indeed very weird … the only thing I can think of is that I’ve heard there’s some kind of issue with AIFs in CS5 … I’m still on CS3 so I can’t confirm, but you might want to search for some info about that and, if it seems legit, transcode the AIFs to WAVs.
-
If you want to render individual clips from AE, it seems easiest to use separate comps and multiple comp viewers to see them side-by-side as you work in AE.
If you want them in one AE comp, but also want to render them separately, you can add that comp to the render queue 5 times and change the in/out points for each render in the output module. You’d also need to change the output file names since they’re all the same comp and, therefore, will default to the same file name.
You could also nest the comp you do the grading in into 5 shorter comps and adjust the portion of the graded comp that shows in each, then render each of those.
Another option is to just work in one comp, render that comp as one file, then simply cut it up as needed in FCP.
If I thought about it long enough, there’s probably a half dozen more ways to do it … along with advantages and disadvantages to each, but any of them will work … just depends on your preference.
-
Your workflow does indeed sound reasonable …
I’ve been editing in FCP with XD-CamHD footage in its native codec for the past few months and haven’t had any issues that make me want to transcode it all to PorRes.
There were driver issues up until about 6 months ago that caused some minor issues, but those are all gone now as far as I’ve experienced so I guess it depends on how up-to-date your system is.
-
[Joseph Dezordi] “I have never understood what is meant by ‘AVI is a wrapper'”
It means it is a file format/extension only so any one of very many codecs can be wrapped inside an AVI file (same as an MOV). You see people point that out a lot because it is important to know the codec you’re working with, not just the file type … especially when trying to diagnose problems.
[Joseph Dezordi] “I thought AVI meant uncompressed captured video”
That is not accurate at all … and AVI can be compressed or uncompressed … as mentioned above, it’s all about the codec.
[Joseph Dezordi] “the offending file is actually an mpg”
There are many kinds of MPEGs … MPG1, MPG2, MP3, MPG4 … and some kinds frequently contain muxed audio.Sorry I can’t be more help, but it’ll be very difficult for anyone to help you without being able to understand what the issue is since you seem to be describing it using incorrect terms and/or using terms interchangeably when they mean different things. Perhaps it’ll benefit you well beyond the current issue you’re having to Google “video codecs” and read enough to get at least a general understanding of the most common video codecs.
-
I know it shouldn’t be a problem to render and re-render various parts of a timeline in multiple passes, but I’ve found that simply rendering everything in one pass once I’m done with all my edits/pre-renders can sometimes solve strange render issues. So, the first thing I’d try is deleting all the render files for that project and re-rendering the timeline in one “render all” pass until all lines purple/blue. There are other ways to delete render files, but I prefer to do it manually by going to the Final Cut Pro Documents folder in Finder.
-
I believe it’s at the bottom of the comp viewer panel.
-
The simplest solution is to transcode the offending AVIs to another format. AVI (like MOV) is a wrapper format (rather than a codec) so they can be made with any one of very many different codecs, some of whihc are proprietary codecs or simply uncommon. It sounds like you have some AVIs that use an audio codec that you don’t have installed on your machine or that have “muxed” audio (the video and auido data are combined in one channel instead of separate).