Petros Kolyvas
Forum Replies Created
-
I’d say the learning curve is steeper – but like a lot of software once you get the core concepts it begins to move more quickly – I’m still a novice myself.
As far as integration goes, I’m not sure what you mean. It integrates no differently than AE would in an FCPX workflow. Give it the clips you want to work on, export clips, import them into FCPX. My experience with FCPX is, to be fair at this point, limited – I’m starting two real projects on it shortly after having completed only very small jobs using it along side PrPro CS6.
As far as Nuke is concerned the main difference would be Nuke is a compositor first and foremost (and is rather, ahem, pricey) and Blender is a 3D package first and foremost but seems to be developing some very good compositing infrastructure.
My early opinion (still being formed) is that while there 3rd party support for AE is widespread, the (familiar from my Shake days) node-based interface of Blender makes completing some compositing tasks dramatically simplified.
I don’t think there’s a “better than other” option in the end, just a solution that’s right for each of us.
I do think as FCPX and CC debacles have proved, there’s a growing interest in community driven software solutions like Blender, even if some features end up feeling a bit like they were designed by “committee.”
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Don’t discount Blender! It can do some amazing things and the compositor is node-based, very much in the vein of Shake.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
The LHe card (unless what you’re really using is a LHe Plus) was EOL’ed some time ago and so, unfortunately, the point is moot since newer NLE versions won’t have available drivers for it. 🙁
While the drivers for the current Kona lineup are Thunderbolt-chassis aware, no one knows when that could change. When you factor in the purchase of a quality Thunderbolt PCIe expansion chassis, the Io XT doesn’t look like a terribly expensive upgrade anyway and you get a lot of bang for your buck.
I do wish I had better news about the LHe, it was a shame when support was discontinued.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Oh, you may want to ask in the AE forum too – there might be others with more experience/better suggestions than my own.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Hi Asia,
I didn’t save it. But the gist of it is:
1) Duplicate the layer
2) Create a mask over an area you want to fix on the new layer so you only colour-correct the area you want to fix (like a grading mask or power-window)
3) Colour-correct as required with the appropriate tools (ones you’re familiar with)
4) Feather the mask/expand the mask appropriately to match/disguise
5) Keyframe the mask so that it moves with the discoloured areas (motion tracking will be difficult since what you would need to track isn’t an easily delineated point or set of points). This movement should be fairly consistent/cyclical, so realistically you’d only have to do it once from out of frame (top or bottom) to out of frame and then copy/paste as required.Good luck!
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
This will be a long, expensive, tedious, but doable, job.
If it were me – AE: colour-correct (whatever you need, curves, HSL, exposure, multiple times and multiple layers/mattes) the purplish areas to match the rest and then use a feathered mask to match the areas as much as possible. Then you’re going to have to keyframe the movements.
This is what 5 minutes did (it’s not even close to good enough – but with enough time and effort you can get there):
Before:
After:
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Creative cloud-only.
From the article: Adobe has decided to focus its resources on Creative Cloud and will not continue development on its Creative Suite software, reports The Next Web. While Creative Suite 6 will continue to be supported in regards to bug fixes, there will be no further updates and no Creative Suite 7.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Thanks Tom! That’s really helpful. I’m actually working on something now, just like this and will try it out immediately! 🙂
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
[walter biscardi] “Dynamic link is awesome to a certain extent. Use it too much in a long project and it’ll bog you down.”
Absolutely! Fancy/animated lower thirds could really slow down an edit and we found it quicker to render them out on a AE workstation so that they were ProRes or DNxHD on the timeline, rather than to try to work with the Dynamically-Linked compositions on the timeline, however, the OP’s solution would would the same in this case, even though we weren’t using dynamic-link we’d update the AE render, and the file would of course be updated in the edit.
There are plenty of other cases where we’d use AE comps on the timeline, especially in the cases of needing warp-stabilizer or something similar, but in the end we used it less and less as we went along preferring pre-rendered material to speed up exporting where one minor change would see AE comps re-rendered every time even if those comps weren’t involved in the change.
As always, it’s a very nice tool to have in the chest, but I completely agree that knowing when to use it and how to use it best is key (and something we really still haven’t fully figured out in our little shop.)
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
We need some more information to even begin…
– Application (s) and workflow
– OS
– System configetc etc.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger
