sequencer offset layers and "hold" on frame 1?

[heyvern]

So this has been an issue for me as long as I can remember, and I've never quite solved it. I usually work around it. This is probably user error or lack of knowledge.

I use the sequencer to slide a group layer with a bunch of sub animations and keys down the timeline. I need a crossfade from the first scene and need a way to "freeze" or "hold" frame 1 of the moho layer. Is there an easy way to "freeze" or "hold" frame 1 of that layer so that it can start at a specific frame? Currently, it starts immediately at whatever frame you set it up in the layer or imported moho object. In my case, I'm importing a completed animation with lots of complicated animations that's already timed and ready to go.

When you slide a layer down the timeline frame 0 is a perfect hold frame but it's useless because it's all the setup of the rigging, etc. If you don't turn off visibility, frame 0 is visible all the way down the timeline until it starts, which is EXACTLY what I need, but ONLY if it could change frame 0 to frame 1. When using the sequencer, you really don't want frame 0 in the animation and have to set the visibility off on frame 0, and on at frame 1, but then you lose the "hold" frame before it starts.

Is there a solution to this, or should I continue to use my less-than-preferred workarounds (prerendered frame 1 image)? It kind of makes the sequencer a wee tiny bit kind of almost "useless". Useless is a really strong word for a potentially useful feature, but I have never really found a way to use it effectively to create scenes like this with cross-fades and better timing without being able to "hold" or "freeze" on frame 1.

[slowtiger]

Good point! I never noticed this although I use the sequencer quite often, but mostly in the other direction.

I can only offer a workaround: render frame #1 as image and import it again, then switch visibility when needed.

[heyvern]

...render frame #1 as image and import it again, then switch visibility when needed.

That's what I have been doing most of the time. The image trick is always a bit fiddly as I can't always get the image to exactly match the moho layer that joins up. There's a little "blip" that annoys me.

I have a script I've been fooling around with that converts bone keys to keyed points on vector layers. If I get everything keyed, I can put in a hold frame on a separate duplicate MOHO LAYER instead of using a rendered image. Then it can match perfectly. Just now thought of it. Should work.
It's very funny, I had this GREAT IDEA to create a script that keys bone keys as vector movement. Unfortunately once it worked it became clear it was useless for that purpose since I would have to key every frame for bone rotations of vectors. The points just go in a straight line. I think now I have a use for it.

[synthsin75]

I have a script I've been fooling around with that converts bone keys to keyed points on vector layers. If I get everything keyed, I can put in a hold frame on a separate duplicate MOHO LAYER instead of using a rendered image. Then it can match perfectly. Just now thought of it. Should work.

If you're willing to use a duplicate layer, no script necessary. Just move the duplicate back to frame zero in the sequencer, clear its animation after the frame you want to hold (including sublayers), and switch visibility when the original layer's first frame starts.

[heyvern]

Hahahahahaha! I always overthink this kind of thing. Yes, that works great. It's relatively easy to update if needed.