Erik Lindahl
Forum Replies Created
-
This is doable with expression, which in its self is powerful, but for “alias” type of work it’s a clumsy solution.
It’s also not possible to have alias layers which is again a lacking feature. You can have two layers act identical with expression or linking but it’s again a very clumsy solution. Powerful, flexible but clumsy.
-
IMO a pre-comp and a group could be the same thing. At least the ability to “fold out” a pre-comp in the main-comp would be vital.
That said I could see them being two separate features also. I don’t however think this is an issue to talk about when dealing with “new users”: AE is one of the more complex applications to get into in the Adobe-sphere as is. This wouldn’t really change anything, just make the app more user-friendly for advanced users.
-
I agree very much with this! Two feature AE could use badly is:
– Layer grouping. This could be handled with pre-comps but we are able to “fold out” the contents of these in each comp. This would make managing complex comps much easier.
– Alias layers and effects. I don’t know how often I end up having 3-4 copies of the same matte layer which in turns is a pre-comp of some video footage. I.e the matte is locked in time to footage in the main-comp and multiple layers rely on it as for example a matte. A manually updating everything if one needs to be changed. Same goes for effects where you might want two or more elements share identlicle amounts of what ever.
Some of the above can be handled with pre-comps and scripting but this can quickly turn into a spiderweb and with pre-comp you rapidly run into overview issues.
From talks with Adobe I think my point 1 is one of the most requested features users have. It’s just a massive undertaking for Adobe to sort out (something like rewriting the whole rendering pipeline). I would imagine “alias layers” could speed things up with rendering also since AE can render once and use a cached version for all other aliases. Not sure if this happens at the moment with multiple, identnical, instances of the same elements.
-
I understand why this isn’t done as it’s probably low priority in an editing app and most have a long list of “this could / should be added”.
-
Keyframes don’t have to take that much space and can be done “nicely” in “limited reel-estate”.
Curve drawing is a different beast but could / should be modular. From small with “decent control” to full control and take more space.
Makes perfect sense yes if implemented correctly.
Yes, keyframeing sucks in other editing apps. I’m not sure if that’s really a good comparison though when they are so poor.
-
PremierPro should get AE’s keyframe engine and it would be the best editor with key framing on the planet. No need to re-invent the wheel imo.
-
Take the AE CS 6 engine or the AE 6.0 engine? 😉
Not to be bitter but it looks like it’s from the 1990’s instead of 2000’s. With the Mercury Engine PrPro could be an AMAZING online tool. It just seems to fall a bit short every time I try to do that “online” stuff there and I end up in AE for even simple things.
-
Those curves look like what AE had back in like version 6.0 (not CS6). I’m surprised Adobe doesn’t just take the AE keyframe and curves engine and build it right into PrPro.
-
I have a hard time seeing Resolve replace an editor but it does seem very interesting as an online-tool in conjunction with for example After Effects like a lot of FCP / Premier people use it.
-
Having an on-screen HUD would be nice. Show details X and Y during playback, show details X, Y and Z when paused.
I understand Apples idea of going back to basics but it’s actually more confusing now than NOT having all the TC-info everywhere.