I agree 100%. The effects model is flawed and not consistent with how effects
are handled in many other environments, including previous Avid releases.
What you suggestion makes great sense. Effects mode should not automatically add
keyframes. This would result in parameters being adjusted to be "hold" or static
changes. No animation. You should be given the choice to manually add keyframes
or to have the application do it automatically, just as in Adobe products like
After Effects.
A real mess. However I do believe this is something we struggle with in older
versions (4.5, 4.x) as it happens with all AVX2 or advanced keyframe effects.
It is also worth mentioning that all the grief surrounding our brief test drives
of version 5 and reports from users have prevented us from pulling the trigger
on upgrades for our 7 seats (3- Symphonys, 1 Adrenaline, 2 Mojos, 1 software
only). Thats a lot of business Avid has lost over a tremendous miscalculation.
There was a lot in need of fixing, revision, and updating. Version 5 seemed to
spend valuable corporate resources pursuing some FCP induced delusions of
grandeur.
If they have run out bugs to fix, user requests or quality/performance issues to
address I have a list.
Heck can we just get a DVE that doesn't go soft in 4 pixel cadences, maintains
cleans edges, can handle scaling and movement without interlace wiggle? Ditto
for an Animatte tool that doesn't introduce interlace artifacts when objects are
too close to the edge of raster.
Anything further like addressing the color correction interface would require a
much larger internet.
Output quality trumps interface in the pecking order. Right now they both suck.
Christopher Magid
RTVF
________________________________
From: shieldsy72 <PaulShieldsAvidL@gmail.com>
To: Avid-L2@yahoogroups.com
Sent: Thu, February 3, 2011 10:04:38 AM
Subject: [Avid-L2] MC5 new keyframe behaviour + workflow
Hoping for some words of wisdom from people on this. I've only had chance to
dabble with MC5 while I wait for my facility to jump from 3.5. I can deal with
the smart tool and the new timeline behaviours but I can't work out the best way
to handle the new keyframing behaviour.
For example, I want to resize a shot so I drop a 3D Warp on and make it bigger.
Then I move elsewhere. Later I land on the resized shot and decide to adjust it,
so I move it to a new size/position. I have now created an animation between my
first size and the new one. Traditionally this wouldn't happen and I think I
read a while back an explanation, probably from Frank, that effects are now
added without start/end keyframes to save on sequence size. What's happening now
is that when I perform the first resize, a keyframe is added at the position I
clicked on and, unless I land on that frame again, a new keyframe is added for
the adjustment.
My workaround is to add a keyframe start and end every time I add a resize and
make sure they are both selected - but this is a major PITA - it reminds me of
the hoops FCP makes me jump through to do the simplest things. What are other
people doing? I'm hoping there's something really obvious to avoid this or that
it's going to be changed! I don't mind the advance keyframing becoming standard
but it looks like the current system needs to copy Premiere's clock button to
enable animation over time on effects.
Really hoping I'm missing something obvious :)
[Non-text portions of this message have been removed]
No comments:
Post a Comment