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

[johnag]

Call me crazy but I think this was possible a long time ago.

@fredwarren ??

[cnoellert]

@johnt

Merci

One that I’ll add is quite simple. If you double click on a clip that isn’t “open” on the record timeline in the media panel, it should flip to the source viewer and the source timeline, similarly to how flame opens the record viewer and timeline when you double click on a piece of media that is “open.”

I can’t tell you how often that catches me out. And it’s such an inconsistency. I swear smoke would toggle the viewer.

[fredwarren]

@cnoellert

One that I’ll add is quite simple. If you double click on a clip that isn’t “open” on the record timeline in the media panel, it should flip to the source viewer and the source timeline, similarly to how flame opens the record viewer and timeline when you double click on a piece of media that is “open.”

@cnoellert I didn’t find a request for it at flamefeedback.autodesk.com. Please submit a General Improvement request.

[fredwarren]

@johnag

Call me crazy but I think this was possible a long time ago.

Are you talking about the Alt-Click on a Clip node in Batch? I don’t think this was ever possible.

[ytf]

@allklier

… 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.

I work with the media panel open on the right. I can select any clip in the batch and it is highlighted on the right, and I can click hover to see the info. And technically I don’t need to select it in the batch schematic. I can just alt-click on any clip in the batch, but sometimes it’s hard to find them unless I select it in the schematic first

[allklier]

Right; it works well for clips.

My use case was nodes. For example the OFX node for Neat always returns 32float results. In some cases I have to put a resize node behind it to bring Neat back to the rest of the node graph without warnings.

But as I usually only have size displayed in batch I can’t readily see which nodes are 12bit, 16f or 32f. To see that you have to add all the colorspace info which is way too much text for a busy batch.

What would be nice os to Alt-click on any node and temporarily get all the node meta data, such as size, bit depth, and color space.

[PlaceYourBetts]

Yeah. I like this idea

I do work in batch with ALL of the node info which is a lot of on screen and can get busy plus not all nodes display the info.

[johnag]

@fredwarren

@cnoellert

One that I’ll add is quite simple. If you double click on a clip that isn’t “open” on the record timeline in the media panel, it should flip to the source viewer and the source timeline, similarly to how flame opens the record viewer and timeline when you double click on a piece of media that is “open.”

@cnoellert I didn’t find a request for it at flamefeedback.autodesk.com . Please submit a General Improvement request.

Ummm. Hello, 3 months ago I submitted this
FI-03089
https://feedback.autodesk.com/project/feedback/view.html?cap=5afe6c84-5cb3-447a-b36c-cbd7f0688f84&uf=8efbf546-176d-48cd-b496-20dd1b10a6b1&slsid=862eed61-06f6-4b4f-b8b9-309e3ef2b0df

[johnag]

@fredwarren

@johnag

Call me crazy but I think this was possible a long time ago.

Are you talking about the Alt-Click on a Clip node in Batch? I don’t think this was ever possible.

Maybe it was in BFX in the old days of Smoke???

[ytf]

@allklier

…t to bring Neat back to the rest of the node graph without warnings.But as I usually only have size displayed in batch I can’t readily see which nodes are 12bit, 16f or 32f. To see that you have to add all the colorspace info which is way too much text for a busy batch.What would be nice os to Alt-click on any node and temporarily get all the node meta data, such as size, bit depth, and color space.

Yeah, there was cross-talk in the conversation that referenced clips, so yours was probably not the right one to reply too.

[fredwarren]

@johnag

Ummm. Hello, 3 months ago I submitted this
FI-03089

Thanks John. I missed it because I was searching for “source” and “timeline”. Note that the double-click already works for the opened sequences.

@cnoellert No need to submit anything.

[fredwarren]

@hildebrandtbernd

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 üÄÖ.

This may be subtle, but the problem is not with Flame, it is with the Discreet font. When the font was made, the characters were not put in the proper place sequentially. All Flame does is read the sequence of characters and add them on button. I am not sure if we can “easily” fix this.

[cnoellert]

@johnag

Ummm. Hello, 3 months ago I submitted this
FI-03089

Upvoted. Thanks @johnag

[ALan]

Simple… Discreet2

[ytf]

It’s not just the Discreet font. It’s all of Discreet’s fonts. Even the ones that I have brought in from other sources.

[fredwarren]

Hmmm, having two set of fonts just to inverse that character seems overkill to me.