Recent Posts

Expression Builder Plugin V2.0

Overview Installation UI Overview Expression Builder Open / Load Save Copy Search Page Keywords Copy Glossary Categories Copy to Clipboard Hints Links Expression Builder is for Davinci Resolve Studio version 18. Expression Builder lite will be available soon for Davinci Resolve. Overview Expression Builder assists those learning Fusion Expressions and contains hundreds of examples, however, expressions can be almost limitless and we are adding more every day. New expressions will be available through or update schedule, which is why it is important to include your correct email address. The plugin is capable of saving and loading your own custom expressions for modification or reuse. Expressions can be saved as a .txt .setting or .comp file but must be given a name and extension prior to 'save'. If you wish to contribute your expressions to be included in a future update then you can do so here. Submit an Expression Download and Installation Extract the Expression Builder zip f
Post a Comment

Moving Controls to a Different Page Tab

I am already losing track of what I have posted and what I haven't, after all, I am just emptying my head here.

We have repositioned controls in the inspector and now we are going to place different controls on different page tabs. 

First, what is a page tab? 

I have heard them called pages and also tabs so to clarify they are situated at the top of the inspector. The two default page tabs are "Controls" & "Settings" as they seem to be nearly always there. However, pull in a Text+ to the timeline and you see "Text" "Layout" "Transform" "Shading" "Image" and "Settings". There is also the "User" page tab which can be added in the "Edit Controls" panel, 


You may have noticed that this blog post is sponsored by "quotation marks"!

Why would I want to do this?

  • Separate categories of controls
  • Too many controls in the inspector
  • When rigging, have a "Global" settings page tab
  • It's cool!

To set this up you can start in the "Edit Controls" panel inside Fusion, however, it is likely the only page tab you can add is "User"

Page Tabs inside a Text+

I suggest you add all your controls into the "User" Page on each node you add controls. (just realized they are called pages). We can then move them and rename the pages in the code. 

You can also move existing controls into the "User" page so you have them together, however, I do not recommend this as we can move anything we want wherever we want after the macro is created and we open the .setting file. 

As we can customize the code there is no need to do any of the above, the only thing required is when adding a drop-down or label, create it in the "Edit Controls" panel. (although I can show you how you don't even need to do that)

NB. I am attempted to simplify things here and I am usually referring to 1 node, however, if you have 100 nodes it is the same principle just a lot more work.

I think it is time to jump into the code, coffee ready?

For demonstration purposes, I am going to place all the Background Color controls on a "New Page", you can name the page anything you want.

There is a little bit of best practice involved as it will work by adding Page = "New Page", To the "InstanceInputs" which show the controls in the inspector. I am also going to add "ICS_ControlPage = "New Page"," into the "Label" section of the node. This is so if the end-user opens the "Edit Controls" panel they will see the page.

You will also notice that I have added Page = "New Page" to the label InstanceInput, this then takes the label as well as the controls to the new page.

So here is the code added to the background InstanceInputs.

  1. -- label instance
  2.          Label02 = InstanceInput {          SourceOp = "Background1",
  3.          Source = "Label02",
  4.                                          Page = "New Page", },
  5.                                 -- end of label instance
  6.                                Input10 = InstanceInput {
  7. SourceOp = "Background1",
  8. Source = "TopLeftRed",
  9. Name = "Color",
  10. ControlGroup = 6,
  11. Default = 0,
  12. Page = "New Page",
  13. },
  14. Input11 = InstanceInput {
  15. SourceOp = "Background1",
  16. Source = "TopLeftGreen",
  17. ControlGroup = 6,
  18. Default = 0,
  19. Page = "New Page",
  20. },
  21. Input12 = InstanceInput {
  22. SourceOp = "Background1",
  23. Source = "TopLeftBlue",
  24. ControlGroup = 6,
  25. Default = 0,
  26. Page = "New Page",
  27. },
  28. Input13 = InstanceInput {
  29. SourceOp = "Background1",
  30. Source = "TopLeftAlpha",
  31. ControlGroup = 6,
  32. Default = 0,
  33. Page = "New Page",
  34. },
And here is the code added to the "UserControls" section of the "Label".
  1.                                     UserControls = ordered() {
  2. Label02 = {
  3. LINKS_Name = "Label02",
  4. LINKID_DataType = "Number",
  5. INPID_InputControl = "LabelControl",
  6. INP_Default = 0,
  7. INP_Integer = false,
  8. LBLC_DropDownButton = true,
  9. LBLC_NumInputs = 4,
  10. LBLC_NestLevel = 4,
  11. INP_External = false,
  12. INP_Passive = true,
  13. ICS_ControlPage = "New Page",
  14. }
  15. }



That's it!

Below is the full code.

All the green text is what you see in the inspector, these are the controls we checked in the "macro editor"
The text in Fuschia is the label we added, directly to the code.
The red text is the output, in fusion this would connect to the MediaOut. In the cut & edit page resolve handles this for you.
The yellow text is the code that makes up the node.
The aqua text is the label added using "edit controls" we can seriously customize this section.
--This is a comment
  1. {
  2. Tools = ordered() {
  3. DropDown = MacroOperator { 
  4. Inputs = ordered() {
  5. -- label instance
  6. Label01 = InstanceInput {
  7. SourceOp = "Text1",
  8. Source = "Label01",
  9. },
  10. -- end of label instance
  11. Input1 = InstanceInput {
  12. SourceOp = "Text1",
  13. Source = "StyledText",
  14. },
  15. Input2 = InstanceInput {
  16. SourceOp = "Text1",
  17. Source = "Font",
  18. ControlGroup = 2,
  19. },
  20. Input3 = InstanceInput {
  21. SourceOp = "Text1",
  22. Source = "Style",
  23. ControlGroup = 2,
  24. },
  25. Input4 = InstanceInput {
  26. SourceOp = "Text1",
  27. Source = "Red1Clone",
  28. Name = "Color",
  29. ControlGroup = 3,
  30. Default = 1,
  31. },
  32. Input5 = InstanceInput {
  33. SourceOp = "Text1",
  34. Source = "Green1Clone",
  35. ControlGroup = 3,
  36. Default = 1,
  37. },
  38. Input6 = InstanceInput {
  39. SourceOp = "Text1",
  40. Source = "Blue1Clone",
  41. ControlGroup = 3,
  42. Default = 1,
  43. },
  44. Input7 = InstanceInput {
  45. SourceOp = "Text1",
  46. Source = "Alpha1Clone",
  47. ControlGroup = 3,
  48. Default = 1,
  49. },
  50. Input8 = InstanceInput {
  51. SourceOp = "Text1",
  52. Source = "Size",
  53. Default = 0.16,
  54. },
  55. Input9 = InstanceInput {
  56. SourceOp = "Text1",
  57. Source = "CharacterSpacingClone",
  58. Name = "Tracking",
  59. Default = 1,
  60. },
  61. -- label instance
  62. Label02 = InstanceInput {
  63. SourceOp = "Background1",
  64. Source = "Label02",
  65.                                  Page = "New Page",
  66. },
  67. -- end of label instance
  69.                                  Input10 = InstanceInput {
  70. SourceOp = "Background1",
  71. Source = "TopLeftRed",
  72. Name = "Color",
  73. ControlGroup = 6,
  74. Default = 0,
  75. Page = "New Page",
  76. },
  77. Input11 = InstanceInput {
  78. SourceOp = "Background1",
  79. Source = "TopLeftGreen",
  80. ControlGroup = 6,
  81. Default = 0,
  82. Page = "New Page",
  83. },
  84. Input12 = InstanceInput {
  85. SourceOp = "Background1",
  86. Source = "TopLeftBlue",
  87. ControlGroup = 6,
  88. Default = 0,
  89. Page = "New Page",
  90. },
  91. Input13 = InstanceInput {
  92. SourceOp = "Background1",
  93. Source = "TopLeftAlpha",
  94. ControlGroup = 6,
  95. Default = 0,
  96. Page = "New Page",
  97. },
  98. },
  99. Outputs = {
  100. MainOutput1 = InstanceOutput {
  101. SourceOp = "Merge1",
  102. Source = "Output",
  103. }
  104. },
  105. ViewInfo = GroupInfo { Pos = { 0, 0 } },
  106. Tools = ordered() {
  107. Text1 = TextPlus {
  108. CtrlWZoom = false,
  109. Inputs = {
  110. Width = Input { Value = 1920, },
  111. Height = Input { Value = 1080, },
  112. UseFrameFormatSettings = Input { Value = 1, },
  113. ["Gamut.SLogVersion"] = Input { Value = FuID { "SLog2" }, },
  114. StyledText = Input { Value = "DROPDOWN", },
  115. Font = Input { Value = "Open Sans", },
  116. Style = Input { Value = "Bold", },
  117. Size = Input { Value = 0.16, },
  118. VerticalJustificationNew = Input { Value = 3, },
  119. HorizontalJustificationNew = Input { Value = 3, },
  120. ManualFontKerningPlacement = Input {
  121. Value = StyledText {
  122. Array = {
  123. },
  124. Value = ""
  125. },
  126. },
  127. },
  128. ViewInfo = OperatorInfo { Pos = { 990, -16.5 } },
  129. UserControls = ordered() {
  130. Label01 = {
  131. LINKS_Name = "Label01",
  132. LINKID_DataType = "Number",
  133. INPID_InputControl = "LabelControl",
  134. INP_Integer = false,
  135. LBLC_DropDownButton = true,
  136. LBLC_NumInputs = 9,
  137. INP_External = false,
  138. INP_Passive = true,
  139. }
  140. }
  141. },
  142. Background1 = Background {
  143. Inputs = {
  144. Width = Input { Value = 1920, },
  145. Height = Input { Value = 1080, },
  146. UseFrameFormatSettings = Input { Value = 1, },
  147. ["Gamut.SLogVersion"] = Input { Value = FuID { "SLog2" }, },
  148. TopLeftAlpha = Input { Value = 0, },
  149. },
  150. ViewInfo = OperatorInfo { Pos = { 880, 49.5 } },
  151. UserControls = ordered() {
  152. Label02 = {
  153. LINKS_Name = "Label02",
  154. LINKID_DataType = "Number",
  155. INPID_InputControl = "LabelControl",
  156. INP_Integer = false,
  157. LBLC_DropDownButton = true,
  158. LBLC_NumInputs = 4,
  159. INP_External = false,
  160. INP_Passive = true,
  161.                                                         ICS_ControlPage = "New Page",
  162. }
  163. }
  164. },
  165. Merge1 = Merge {
  166. Inputs = {
  167. Background = Input {
  168. SourceOp = "Background1",
  169. Source = "Output",
  170. },
  171. Foreground = Input {
  172. SourceOp = "Text1",
  173. Source = "Output",
  174. },
  175. PerformDepthMerge = Input { Value = 0, },
  176. },
  177. ViewInfo = OperatorInfo { Pos = { 990, 49.5 } },
  178. }
  179. },
  180. }
  181. },
  182. ActiveTool = "DropDown"
  183. }

Thanks for taking the time to read this post and if you would like to buy me a coffee, pizza, narrowboat then it is greatly appreciated.

Comments

Post a Comment

Popular posts from this blog

DaVinci Resolve Expressions

DaVinci Resolve Expressions The world of expressions in both video editing and motion graphics opens up a world of possibilities. In this article, I am going to bring together expressions I have discovered and experimented with in DaVinci Resolve. This list is by no means complete but more of a working document I will come back to again and again.  When I experiment with an expression I have gotten into the habit of placing a Text Node into the composition and adding the expression in the styled text expression input. This allows me to see the output of the expression in a readable format. I can then tweak the expression to get my desired result. Another tip: Use the expression first before renaming a node as renaming a node will update the expression. Placing a “--” in a simple expression will ignore the characters to the right. As in “GetPrefs("Comp.FrameFormat.Rate") -- Returns TL FPS” It is a great way to add a reminder. What follows is a list of expressions with comments
Read more

Expression Builder Plugin V2.0

Image
Overview Installation UI Overview Expression Builder Open / Load Save Copy Search Page Keywords Copy Glossary Categories Copy to Clipboard Hints Links Expression Builder is for Davinci Resolve Studio version 18. Expression Builder lite will be available soon for Davinci Resolve. Overview Expression Builder assists those learning Fusion Expressions and contains hundreds of examples, however, expressions can be almost limitless and we are adding more every day. New expressions will be available through or update schedule, which is why it is important to include your correct email address. The plugin is capable of saving and loading your own custom expressions for modification or reuse. Expressions can be saved as a .txt .setting or .comp file but must be given a name and extension prior to 'save'. If you wish to contribute your expressions to be included in a future update then you can do so here. Submit an Expression Download and Installation Extract the Expression Builder zip f
Read more

Organising The Fonts Folder

Image
I don't know about you but the list of fonts inside resolve is longer than I need, there are so many system fonts and fonts I just don't use. In this article, I am going to walk you through setting up a dedicated Davinci Resolve fonts folder. You can place a fonts folder anywhere on the system, however, Blackmagic have provided us with a documents folder that is perfect for this. Navigate to your Documents > Blackmagic design folder, create a new folder and rename it "Fonts". Add your favourite fonts to this folder, you can do this by dragging and dropping fonts from the system fonts folder to your newly created Blackmagic fonts folder. If you get fonts supplied with an asset you have downloaded you can just place them in this folder too.  Davinci Resolve scans and loads fonts on startup, which means you can add and remove fonts from this folder as and when required. We need to set resolve up to find our new fonts folder, this is straightforward. Open Resolve Navig
Read more