PDA

View Full Version : Compose: an unfinished feature


ljilekor
12-22-2003, 05:08 PM
I was very excited when I first saw the compose tab. Until I started working with it (of course).
It's easy to use and has great features: mirroring, timestretching, factors, ... But some fundamental things aren't finished yet.
I don't really like to be bound to use groups (because I can match everything to everything). But this is something I can understand.

There are other things that annoy me:

- What's the use of baking if I can only bake a clip (something I already have) and not my trackresults?

- I can't cut,copy,paste, ... a clip except thru save/load.

- Once I created the clip I can't edit it's in/out points anymore.

- I can edit the motion within a clip, that's great. But in practice I can't select, drag, keyframe in my viewports. Keys are created on the real timeline, not within currently selected clip. Everything has to be done numericaly or in the timeline.


The compose has great potential but right now it's pretty useless.

lmilton
12-26-2003, 07:42 PM
Why is it that your first impulse to post negative? Don't you think it's *way* over the top to call Compose "useless"?

The bottom line is that

- you *can* bake your track result by using the standard motion baking system (shift-return).

- you *can* get a copy of a clip by save-loading. After all, it's not exactly an interactive, often used (during a session) operation.

- you *can* edit your motion inside a clip

Granted that you can't edit the in/out of an existing clip, but that hardly makes Compose "useless". You just need to plan a little better.

Of course we have improvements planned, but you can certainly use what's already there.

-lyle

CGTalk Moderation
01-17-2006, 12:00 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.