Forum Replies Created
-
Danielle Warren
October 7, 2014 at 3:49 pm in reply to: jagged/pixelated/aliasing effect/whatever it’s called on exported footage (picture included!)Hi there, also having the same problem. My sequence in FCP7 is the picture below.

And I export from AE with these settings:
Format: Quicktime. Format Options: Animation
Channels: RGB+Apha
1920×1080
23.98When I bring into FCP, the field dominance of the AE file says NONE. The sequence is also set to be NONE for field dominance, but the titles are pixelated. The pixel aspect ratio of the sequence is square, as is the AE file. I really don’t understand how to fix this. Adding the anti-alias filter does help, but there must be a way to bring the text into FCP without it becoming pixelated once it’s in there.
Any other options to try?
-
Thank you, Alain. I noticed there were no responses which is a shame. I tried to do some more research and it appears there really is no way to do this other than to do a new “save as” every time you make an adjustment. Seems like a very strange way to do this. If you find out anything else, please post here and I will do the same!
-
I was wondering the exact same thing. No one knows? This is such a weird thing to happen. Basically you have to make sure everything is perfect with the custom keyboard you make before saving it. That seems ridiculous though because you may want to change something down the line.
-
Hey Jerry, thanks for the positive comments lol! I used Nattress and Sapphire a lot. Not sure what CGM is. Sounds like a lot of what I used I am now SOL. So what are the alternatives for people who use Premiere Pro?
-
Cheers Steve! I will take a look.
-
Danielle Warren
January 16, 2014 at 3:57 pm in reply to: Rolling title not playing in source monitorThanks for the reply Job. So you’re saying that any effect/title that has to be rendered can’t ever first be seen in the source window? You have to cut it into the TL first? That seems very strange, but then I’m used to working in FCP where you can always play a title before having to cut it into the TL and render it. I even tried rendering in the composer window, but that didn’t seem to do anything.
-
Right, so I’ve started a new project with some footage I had lying around. It was all Prores as I had worked with it first in FCP.
I had about 12 clips all 1920×1080, some at 23.98 and some at 29.97. I set my settings to transcode/import at 1080 23.98. I used “link to AMA” to bring all the files into the Avid project. Then I selected them all and transcoded them. (I chose to convert the ones that weren’t 23.98 as that’s what I have in my settings. I’m assuming that’s ok and the best option so all the footage is 23.98)
When it comes to those settings, I wasn’t really sure what my target video resolution should be, so I just used what came up first “DNxHD 115 MXF”. (Can anyone help explain the difference between all the resolutions they offer or why you would choose one over another?)
I then chose the drive I wanted to save the transcoded footage on and hit transcode. Took roughly 20 minutes.
So now my bin has the original files and all those files with the .new01 on the end. Can/should I delete the original ones from the bin and just use use the .new01 ones to edit with? It seems very cluttered, and I don’t think I need the original linked files in the bin to work with, correct? But deleting them from the Avid bin won’t have any effect on the original files on my drive, right?
Thanks guys! I’m getting there a bit at a time!
-
As I said before, I appreciate the advice to use Premiere, but I’m not choosing Avid because that’s what I want to use. I’m choosing it because most places either use it or want to start using it in the future, so I would like to learn it to continue working at these places. Trust me, I’d happily use FCP forever, but this is the reality and I think it will be a positive thing to know Avid as well.
-
Thanks Michael! Every little bit helps!
-
Brilliant! That is so simple and easy to remember!
And I’m sure I’m totally over thinking it, that is my unfortunate nature 🙂
Thank you, that’s the best and easiest explanation yet!