Some very minor annoying things that never get fixed in every version ( or i need to change my ways)

Flame Flame Questions
22

Right I’ve been inspired to report some of the small bugs that I encounter.
I’ve reported all these apart from the ones with a strike through, I used the link that Fred posted.

I always forget issues when I am busy as I just use my work arounds, so I started making a list.
I’m posting this here in case someone can tell me some of this stuff is just operator error.

Action

1 Sometimes going to priority only shows “Action - Matchbox Only”
Realised this happens if you go to the priority tab while having a matchbox selected

2 When selecting an action in batch or creating a new action it sometimes automatically defaults to selecting both the bg and layer 1 as inputs. This means you can’t see the front or back with a hotkey press and when you add an image it adds one for the bg and one for the layer.

3 The axis scale parameter in the Display settings tab, continually resets.

4 Adding a gmask tracer in action after a Mono Analyzer 3D track always adds the gmask to the tracker image not the selected axis.

5 Adding a gmask in action most of the time adds random numbers into the axis position.

6 Grid sometimes stays on after Mono Analyzer 3D tracking (the old 3d tracker) until you select a node in the batch then go back to the action.
I can’t recreate this consistently enough, and I thought this was supposed to have been fixed, but I think I encountered it recently again.

7 Front centre of Matchbox FrontMatteOffset is inverted compared to the centre of the older Source front node.

Gmask Tracer.

8 New gmask node is much slower than the old one when a mask with a lot of vertices is added.
This may have been fixed, need to test it more. Maybe it’s just in certain circumstances.

9 Can’t select all vertices of gmask with CTRL-A when viewing a context.

10 Can’t add a gmask when viewing a context.

11 Why does turning “smoothing” down to 0% make the mask smoother?
This was mentioned in a thread in Logik the other day, not sure if it’s a bug

12 Can’t delete keyframes from the Softness offset in gmask tracer without going into the animation editor.

13 Adding a point to an exsiting gmask always adds a point with no tangents on each shape keyframe. Sometimes when using auto tangent on each of the shape keyframes, the handles of the tangent spin around and create unwanted animation.

Timeline

14 “New Sequence” on desktop doesn’t retain last sequence made, instead seems to take the last resolution that was worked on in batch.

15 Can’t select more than one layer in timeline if layers are empty.

Blur node

16 Doesn’t work correctly in Defocus mode when blooming is set above 1

2 Likes
23

#5- That’s because you are adding the mask while viewing the image. The numbers are where you drop the axis when you drag it in. If you add the mask within the schematic it defaults to zero. There may be a secret hotkey to zero the axis when you drop it, but I don’t know it. I’ve always been a habitual achematic adder.

24

Perfect thanks.
As soon as I read that I seem to recall Grant Kay mentioned it on one of his videos.

You have to drag it into the schematic though, you can’t double click even when in the schematic.
But that’s great to know.

25

Try setting up the viewports the way you want and save it as a layout preset.

I do this for various grading setups like 4 up with scopes on. Its easy then to select a layout in the drop down menu

1 Like
26

It’s a good point and I do this too but it doesn’t quite address my issue. Generally I’ll be in a view, be it the working camera, top view or whatever - when I switch to 2up I almost always want to retain my current view and add another - not start with a two completely reset views.

4 Likes
27

when i write my daily archive, it often happens that i go to the archive in the media hub via the Files tab and then change it to archive. Flame unfortunately does not remember the path

3 Likes
28

Yep. Happens to me all the time too. What I do to get around it is to:
1: go back into the files tab
2: go up to where the folder icons are at the top of the page, double tap on it so it opens the text input window, hit enter
3: go back to the archive tab
4: double tap in the long blank rectangle where the folder tabs normally are
5: up/down arrow to recall the path you copied from the other tab

Viola!

2 Likes
29

In general, flame almost does not remember where and what you left selected. This leads to a myriad of terribly annoying things. From the views in the schematics, to the columns view, or the mediahub. Any of us can spend more than 30-40% of our time reselecting, repositing views, and all kind of stuff when we need switch between different areas. I have seen it for 20 years now and I have no hope that any of this will be fixed.

30

Don’t get me going about font selection. . . .

4 Likes
31

And another thing you can do is just bookmark from the files tab then jump over to archive tab and call up the bookmark

32

The inconsistencies of the desktop view really confuse the eff out of me - I hate doing versioning because since AE it’s been so much more difficult - I have to constantly check what master I have because different views of the masters are not in synch - this is a showstopper in my opinion but dear old Philippe never agreed with me. Screen recording to show what I mean:

There’s an improvement logged and accepted since 2015 - howay lads, can you just fix it please? @fredwarren @Slabrie
General Improvements

FI-00277

33

Ah the AE!

Let us revisit the why and what of this behavior and we will see what could done to ensure you are not confused when working fast.

3 Likes
34

Merci

35

Praise Jesus.

36

I agree 100% . Things get incredibly confusing working with several sequences opened in tabs, making noob mistakes, like editing or exporting the wrong sequence. In addition to what johnt says, more space for the secuence’s names on the tabs (99% of the time they’re truncated), a better way to highlight which sequence is active in the project window might help.

37

Something that annoys me for years is, as a German, I need to use the special characters ‘ÜÄÖ’ 1-4 times a year for super etc.

But the Flame keyboard has the ü reversed, so the lower case flame keyboard has Üäö and the upper case has üÄÖ.

It’s so little used that I just skip it to set as bug report but still it’s some annoying minor thing and is in the software for at least 7 years :smiley:

Screenshot 2023-12-09 163357
Screenshot 2023-12-09 163337

2 Likes
38

Those Germans are way too particular :wink:

1 Like
39

Blockquote

To harp on about Smoke one more time - it had a really nice big field with the name of the active open timeline. I know the name is in tiny letters in the corner of the viewer but it really is discrete* and sometimes easy to miss. Reintroducing this might help @kily…

IMG_2630
IMG_26302532×1170 294 KB

4 Likes
40

Maybe that exist, and I don’t know about it…

I like my batch to remain readable, so I generally keep the batch pref for info to ‘no’ or ‘size only’. But here and there you need to double check color space or bit depth. Then you need to Batch Prefs, tab over, change the display preference, do what you need to do, and then undo that.

I would be great if something similar to Alt+Click on a clip that temporarily shows meta data overlay would work on batch nodes to just display all info about that specific node while you click on it, and then go back to your default preference.

1 Like
41

Agreed, alt-click hover functionality to temporarily show metadata in batch would be great. I just add a render node to whatever clip or node to see the data, then delete it.