[Alex Kuzelicki]

Yeah, I didn’t think it would be a common workflow, haha, but for my particular job it would be amazing.

I did play around a bit more and figured that if I Nest each each alternative edit and then drag them back in to the Freeform view, I get all my ‘versions’ neatly arranged and in the right order (inside each Nested Sequence). I suppose that’s something.

I’ll definitely put in feature request, though I’m not sure how needed they’ll think it is. Though, it does make sense that copying a series of clips to ‘anywhere’ that they should paste in the same order.

Thanks for the suggestion, Oliver. Appreciated. ☺

[Alex Kuzelicki]

Oh wow, this saved me too!

Thanks John.

🙂

[Alex Kuzelicki]

Hey Kristian,

I know it’s been a long time since you posted this… but the Internet is forever, haha.

Was wondering if you eventually found a better solution to your problem? I’ve recently been trying to understand the whole Projection Man/Camera Mapping process and it’s really hard to find a good, simple workflow.

Like you said, it should be just a simple process of applying the projected textures to the object(s) and then putting them either in Photoshop or Body Paint to clean up. Then reloading that new texture on top of the old. That makes perfect sense… but I’ve yet to figure out how to do it!

Would LOVE to know if you ever figured out an effective and straight-forward solution?

Cheers Kristian. ☺

ALEX

[Alex Kuzelicki]

Oh wow, I didn’t even realise Element had that restriction. How bizarre, seems like something they’d want to fix after all this time.

In the end, I got too frustrated and made the two cylinders in Cinema 4D then brought them in through Element as one model.

Thanks for your suggestions though. Appreciated lots. ☺

[Alex Kuzelicki]

Ah, you’re right. I was so caught up with the problem I totally forgot to include those specs.

MacBook Pro (Retina, 15- inch, Mid-2014) – 2.8 GHz Intel Core i7, with 16 GB 1600 MHz DDR3, Intel Iris Pro 1536 MB graphic card.

OS X Yosemite – Version 10.10.5

AE 2017 – 14. 2.1.34

So, all a bit behind the times, haha, but I’ve just spent 7 months on a feature and was too scared to upgrade in the middle of it. Once this particular project is done, I’ll update my whole system.

Though my problem is ‘solved enough’ to keep working, I appreciate your help, Dave.

Cheers. 🙂

[Alex Kuzelicki]

Thanks Dave, for your quick reply. I remember you have helped me much in the past. Appreciated. ☺

As for those bugs, yes, I’ve noticed some weird things off and on since CC began. Luckily, it’s usually just little ‘bugging’ stuff. Annoying though, haha.

My particular problem may or may not be one of them. I eventually noticed that the clone keyframes weren’t visible when I selected the layer, which didn’t make sense because I could see the preview (result) of those keyframes in the Layer window.

I’d split the main layer to just work on the section that needed clone work – so the main layer and the ‘clone’ layer’. The clone layer is what didn’t have the keyframes present. But… after much inspection, and clicking around, I saw the keyframes were just kinda sitting in space beneath the clone layer, not attached to it though.

That’s because they were actually attached to the main layer! Even though I’d effectively created an out-point on the main layer, and then separately did the clone work from the in-point on the clone layer, that work applied ‘invisibly’ to the main layer.

Once I realised this, I just switched off my separated clone layer, dragged out the out-point of the main layer and I could see the results in the Comp. window.

So, I don’t know if this is an Alex-error, normal AE behaviour or CC bug? I definitely selected my separate ‘clone layer’ to work on. And actually noticed all through the clone work that I had to reselect that layer every time I advanced to a new frame. Still, the work was applying to the main layer regardless of selecting the clone layer.

I’m not sure if that’s weird or normal, haha?

Anyway, thanks for taking an interest, Dave. Glad guys like you are on this forum.

Cheers,

ALEX

[Alex Kuzelicki]

Hey Jerome,

Not sure if you’ve solved your issue, but for me it was actually that I was showing through the black background beneath the layer. The paint strokes were, in fact, working correctly. I was just seeing them wrong!

Alex

[Alex Kuzelicki]

Ah, okay, cool.

Thanks for the info, Mike.

Appreciated,

ALEX

[Alex Kuzelicki]

Okay, so after looking around on different forums online I found a solution. It’s a bizarre one… but it works!

For some reason, if you have the window open that you want to assign the shortcut to then it won’t appear in the Keyboard Shortcuts menu. That is too weird but it’s true. If, say the Timeline window was open, there would be no mention of the Window > Timeline in the Keyboard Shortcuts. As soon as I closed the Timeline, however, it was magically there.

Same for the Program and Source windows.

The second thing you have to do, is to delete the default shortcut. If you don’t then your new one won’t ‘take’. It will just disappear into the ether. Might want to keep a note of what the default shortcut is, though I suspect it wouldn’t just vanish from the default settings… but, who knows? There is some goofy behaviour going on, that’s for sure.

Anyway, hopefully the result of my hours of frustration can help someone who comes across a similar problem.

Cheers,

ALEX

[Alex Kuzelicki]

Update:

With a little research I just found a solution. Might be helpful to someone else.

So, if you enable Ripple Sequence Markers in the Markers Menu they will shift with your edits – much more handy indeed.