Ramon Piracha
Forum Replies Created
-
Man I was so pissed at how some knobs look down on everyone that I didn’t read your post. I racked my brain for trying to understand why this issue had popped up. There’s all kind theories posted up here and you jus get sick all this crap….and then you get those who demean you like they are the authority on this planet. Sat down with an adobe tech tonight who also wanted to know where the problem lies and AE is not guilty in this instance. God Damn FCP is the pain the rear end.
My thanks and big up respect to you man. You da man!! 🙂 problem solved -
Finally spoke to the adobe tech today again. He replicated my steps on a mac and got the same problem. Even when you deselect field render option, AE pushes out Upper/odd fields on the render. Adobe’s bigdick scheduled to call tonight to discuss further and hopefully try to create a patch.
-
already have.Sitting here waiting for some dude in india to call me back.
-
yeah man, I hav fields off in FCP too. It reads everything fine. Because the minute I render out of CS3 everything comes in with correct field settings…being none. ITS A BUG! CS5 has issues
-
Regardless of getting the lingo wrong, Youre right man. I have the same issue CS5. Its a bug. I tested it out in CS3 AE and regardless of how many times you push out a render it will render with the settings you choose. But in CS5 when you tell it you switch off field render it still randomly pushes out the render with upper/odd field. But its random as some times it will push out the exact same job with field render switched off as required. I checked the item properties of multiple renders in FCP, tested between CS3 and CS5 and without fail CS5 delivers a nice pole up the backend. Stuffed up days worth of work as I checked my settings and started rendering without checking the properties for every single render…why the hell would you?? I am totally pissed. I logged it adobe but the tech was not available so have to wait a few days..