Today I learned…

Today I learned…

How expressions can get you out of a frustrating situation.

I had to comp two MoCo passes of a product to enhance some deco. Unfortunately both passes had a decent amount of jitter in it which was not in sync. A bit of a mess. Tried a few things, but nothing quite stuck well enough.

The final solution was to create two separate Axis tracks, one for pass 1 and one for pass 2, both tracking a common reference point. Using that to create an offset track.

Sidebar: I absolutely love that in Flame you can assign different media to the Axis node, so you can pick what media is used for the track separate from what that axis drives - need a pre-treatment for a difficult track? Create another input in action, pipe the standard input through a color corrector and then assign that new input as the Axis media while leaving the the rest of the schematic on the original.

Back to the MoCo situation. I then created a third Axis object that was driven by expressions to offset the jitter.

position.x = action.bg_track.position.x - action.fg_track.position.x (same for y)

That removed the jitter and the baked animation from the MoCo rig now matched between the two passes.

May this help someone else out of a frustrating corner.

11 Likes

I love a good expression . . .

1 Like

2024.1
Today I learned:
If you have a sequence thats HD and just 1 clip in it at a different res then the resize can be removed and the timeline will change to the clip res.

2 Likes

Flame 2023.3

The size that you are zoomed out dictates how wide your action node is on the batch schematic

All credit to @James for showing me this

1 Like

Can you elaborate on this? I need a visual :slight_smile:

Sure.

(Flame 2023.3) Depending what zoom size you are in your schematic, your action node width will be different when you pull a fresh one out :smile:

3 Likes

I was wondering what was going on . . . . I think that’s a 2023 thing. I never noticed it until recently.

1 Like

Arhh. thanks for solving that mysery for me.

@ PlaceYourBetts
Thanks for reporting this :slight_smile: -)

We have looked into the issue and this is a side-effect of an improvement we attempted last year when we worked on the workflow with Multi-Channel clips in Batch. By default, we are automatically setting the width of a node so the complete name of a channel/output is visible. We will tweak it so you do not end up with very wide nodes for nothing when your zoom level is low.

3 Likes

TIL thanks to @Jeff

in a timecode display the frames are seperated by different symbols depeding on the framerate, at least in flame

+ is for 23.98 or 24, : is for 25, 2997, or 30, and # is for 50 or 5994 or 60

and ; is for dropframe ?

2 Likes

only the drop frame separator is universal. I think all the others are flame centric, althought I might be wrong about #.

3 Likes

I was today years old when I discovered you can drag and drop clips from the finder to the flame desktop reels.

4 Likes

Still my favorite thread :hugs:

3 Likes

If there are [brackets] in a file name, QuickTime will open the file just fine but Flame won’t be able to read it.

Delete the brackets and Flame will be happy.

1 Like

Good to know. I think there might be a couple of other characters that behave that way.

The bad habits of writing novels in filenames. longing foe the old Linux and MS-DOS days where it was basic characters only, not even spaces or hyphens. Life was easier.

Tell that to art directors who also use localized characters. ışüğçö
I once had a file or folder name that straight up quit or crashed Flame.

2 Likes

Most funny imported character is ‘/’. When you forget to remove it, flame will create a folder during export.

1 Like

I didn’t know this. If it ignores the fact that the folder already exists, it could save a lot of mediahub navigation. I’ll test it when I have a chance.

1 Like