Credit roll in Resolve/Fusion?

thoughts after re-dong a roller orignaly done in DS;
- when i re-set the project raster to 4k, i have to re-do scaleing on the logos and set the crop nodes to match
- likely i'd make a 2k roller, then copy/paste and drop the 4k roller above it, tweak that to suit and toggle the video track on/off to match the deliverable, a fail point to be aware of
- dog slow render, even when compared to DS running on the same machine, and DS is no speed demon, but a 1 min roller rendered to Dci2k in DS = 3.5 min, as close to identical roller as possiable in Resolve = 14 min
- can't get the macro to be recognised, so no way to test and see what it's about
- i can see it being a really good working tool once the code is optimised to run faster and/or cacheing becomes reliable
- working in Fusion i cannot see the master timeline, only the timelin inside Fusion DS has a toggle to select what one wants to be monitoring, i would have this set on "top timeline" to see the roller over the bg plates with the grades
- i know one workaround is to bring the bg plates into Fusion, the weak links there are needing a clean textless layer to output, and haveing to create new complete comps for each deliverable raster, then haveing to change something, would now have a bunch of layers to change one at a time, an obvious and needlss fail point

it cannot find the macro

thoughts?

You're sure you got the last closing curly brace? That's usually what fouls it up for me.

Sure would be nice if the Select All link on code blocks worked.

yea, select all would come in handy.. here's the end of the files;

fusionFail2.jpg (303.02 KiB) Viewed 6048 times

looks the same to me?

Ah, if you create a file in Notepad it automatically adds the .txt extension. And by default Windows hides the extension for known file types.

In File Explorer, click the "View" tab, then "Options". Go to the "View" tab in the window that opens up. Under "Advanced settings" you can disable "Hide extensions for known file types".

Now you can more easily see that your file is in fact named PixelPusher.setting.txt and you can rename it.

Regarding speed, I'm finding out you need to think like a programmer to really optimize the flow. But there are some things that I can't make sense of.

Instead of having the Text+ node re-render each frame as it is moved, I made the Text+ window Height high enough to contain the whole text. Then I set the duration of the Text+ node to a single frame and connected a Time Stretcher node to it.

I many cases, this stopped the Text+ node activity light from blinking after frame 0 and performance skyrocketed from 4fps to the full 25 fps of my comp. But why "in many cases" and not all the time? Sometimes it would play through the whole comp (3200 frames) without a hitch, sometimes the activity light would start blinking half way through. It seems I only got good performance if the Text+ node at frame 0 had been shown in one of the viewers, letting it cache I suppose. But why wouldn't it cache just by rendering?

There's much more to learn I guess.

Excellent, thanks for this.

Is anyone else having problems creating interlaced rollers?

If I enable 'field processing' in settings, it gets all crashy and unusable.

As a learning experience I thought I would try using an expression instead of keyframing the crop/transform node.

Just connect a Text+ node to the input of this "PixelPusher" tool:

Code: Select all

{
   Tools = ordered() {
      PixelPusher1 = MacroOperator {
         Inputs = ordered() {
            Comments = Input {
               Value = "PixelPusher - X/Y integer transform for 90 degree angles\n",
            },   
            MainInput1 = InstanceInput {
               SourceOp = "Transform1",
               Source = "Input",
            },
            Input1 = InstanceInput {
               SourceOp = "Transform1",
               Source = "Speed",
               Page = "Controls",
               Default = 2,
            },
            Input2 = InstanceInput {
               SourceOp = "Transform1",
               Source = "CrawlAngle",
               Page = "Controls",
               Default = 90,
            },
            Input3 = InstanceInput {
               SourceOp = "Transform1",
               Source = "MotionBlur",
               Page = "Controls",
               Default = 0,
            },
            Input4 = InstanceInput {
               SourceOp = "Transform1",
               Source = "Quality",
               Page = "Controls",
               Default = 2,
            },
            Input5 = InstanceInput {
               SourceOp = "Transform1",
               Source = "ShutterAngle",
               Page = "Controls",
               Default = 180,
            },
            Input6 = InstanceInput {
               SourceOp = "Transform1",
               Source = "CenterBias",
               Page = "Controls",
               Default = 0,
            },
            Input7 = InstanceInput {
               SourceOp = "Transform1",
               Source = "SampleSpread",
               Page = "Controls",
               Default = 1,
            },
         },
         Outputs = {
            MainOutput1 = InstanceOutput {
               SourceOp = "Transform1",
               Source = "Output",
            }
         },
         ViewInfo = GroupInfo {
            Name = "PixelPusher",
            Pos = { 0, 0 }
         },
         Tools = ordered() {
            Transform1 = Transform {
               CtrlWZoom = false,
               CtrlWShown = false,
               Inputs = {
                  Center = Input { Expression = "Point(0.5+cos(CrawlAngle*pi/180)*((time*Speed)/Width), 0.5+sin(CrawlAngle*pi/180)*((time*Speed)/Height))", },
                  ReferenceSize = Input { Value = 1, },
                  UseFrameFormatSettings = Input { Value = 1, },
               },
               ViewInfo = OperatorInfo { Pos = { 0, 0 } },
               UserControls = ordered() {
                  Speed = {
                     INP_MaxAllowed = 1000,
                     INP_Integer = true,
                     INPID_InputControl = "SliderControl",
                     IC_Steps = 1,
                     INP_MaxScale = 30,
                     INP_Default = 2,
                     INP_MinScale = 0,
                     INP_MinAllowed = 0,
                     LINKID_DataType = "Number",
                     ICS_ControlPage = "Controls",
                     LINKS_Name = "Speed (pixels)"
                  },
                  CrawlAngle = {
                     INP_MaxAllowed = 1000000,
                     INP_Integer = false,
                     INPID_InputControl = "ScrewControl",
                     IC_Steps = 3601,
                     INP_MaxScale = 360,
                     INP_Default = 90,
                     INPID_PreviewControl = "AngleControl",
                     INP_MinAllowed = -1000000,
                     LINKID_DataType = "Number",
                     ICS_ControlPage = "Controls",
                     INP_MinScale = 0,
                     LINKS_Name = "Angle"
                  }
               }
            }
         },
      }
   },
   ActiveTool = "PixelPusher1"
}

PixelPusher Macro.png

Hi Roger,

Thank you for the script.
I saved it as pixelpusher1.setting.

I changed the beginning of the scipt as recommended by Bryan:
{
Tools = ordered () {
PixelPusher1 = GroupOperator {

VS yours
{
Tools = ordered () {
PixelPusher1 = MacroOperator {

I saved in
C: \ Program Files \ Blackmagic Design \ DaVinci Resolve \ Fusion \ Templates \ Fusion \ Tools

and now in the Fusion tab, I find your script in the tools.

tools.jpg

I am learning the organization of directories for Fusion ... Everything does not seem clear to me at all. I learn ...

For the script no problem. For me, I must master the content of the title, vary the duration of the title and adapt the PPF.

Content, I would like the text to be for example justify between 2 tabs like in a text editor.
Stupid but I did not find. I look for...

Still a job in perspective.

thnX, got pixelpusher re-named and all good,
buuuuut it does not seem to allow me to enter negitive values for the offset?

Instead of negative speed values you can use the angle slider to crawl the opposite direction.

Or do you mean an offset to start the crawl at a different position? You can change that on the Text+ node > Layout > Center Y. Or a bit clearer, add a Transform node between the Text+ node and the PixelPusher node.

Regarding speed, I'm finding out you need to think like a programmer to really optimize the flow. But there are some things that I can't make sense of.

Instead of having the Text+ node re-render each frame as it is moved, I made the Text+ window Height high enough to contain the whole text. Then I set the duration of the Text+ node to a single frame and connected a Time Stretcher node to it.

Thanks for testing that out. That's the way to go for sure. The new beta 2 is 100% faster than beta 1 with the less efficient way of setting up the Text+ tool, but it's still under the speed I get in standalone Fusion.

As a learning experience I thought I would try using an expression instead of keyframing the crop/transform node.

Just connect a Text+ node to the input of this "PixelPusher" tool: ...

Thank you Roger!

i'm seeing this tool re-set to 0 when ever i try to set an expression between the roller and the logoz

not seeing a faster render with it, the moblur is pretty handy tho

also not seeing the moblur slow the renders even set stupidly high..

when exporting it uses 40% of how ever many threads you can throw at it, no matter what, if it's 12 threads, 32 threads or 48 threads, all are running at 40%

GPU use is around 2%, disk is around 1%, so there's some room for improvement.. rendering a 3min roller with logoz took me around 20 min @ 2k

cacheing is somewhat slower, all threads on all machines are running around 35% when it's cacheing, so that's a 20+ min wait to see the roller at speed, kinda workable if you have a patient cleint and a bar nearby to send them off to

and one more rather LARGE issue

the font looks great in the Fusion page, totaly good, no concerns about the alsiing and fine details

but once it leaves the Fusion page, it looks like the same old super crappy, qc failing Resolve text gen.

in the edit page, the color page, the deliver page, and in exported DPX, all no better than the old text tool

i'll pull screen caps tomorrow... show-n-tell

am i the first to look close up outside the Fusion page?

this is nowhere near accepatable quality, not even close once it leaves the Fusion page...

one step forward, two steps back....

Regarding speed, I'm finding out you need to think like a programmer to really optimize the flow. But there are some things that I can't make sense of.

Instead of having the Text+ node re-render each frame as it is moved, I made the Text+ window Height high enough to contain the whole text. Then I set the duration of the Text+ node to a single frame and connected a Time Stretcher node to it.

Thanks for testing that out. That's the way to go for sure. The new beta 2 is 100% faster than beta 1 with the less efficient way of setting up the Text+ tool, but it's still under the speed I get in standalone Fusion.

If only the node disk cache worked as it should, it would make this method really fast and easy to use. I can't get that to work reliably even in Fusion 9. Instead in Fusion 9 I prerender a single frame of the Text+ node and load the rendered file back into the comp. Final render in that case runs at about 23-25 fps on my machine.

Of course, you can't use a loader in Resolve, but maybe you could nest it in a single frame cached compound clip and achieve the same result. I haven't been able to get that to work yet though.

There is something I glanced at on wesuckless that talks about making your own loader (I think). There ought to be a way to script a tool that incorporates a single frame saver and a loader (of that same frame) and rig it with a switch that selects whether you want to pass the original source or the cached frame.

What about using the time tools? Does TimeSpeed set to 0 store that frame in RAM?

TimeSpeed didn't help unfortunately. In the Fusion page I get 25fps as long as I have viewed the single frame Text+ in a viewer before playing. If I go to the Edit page it settles on about 4fps. If I then go back to the Fusion page it's still slow until I view the first frame.

Edit: You can drag a media file to the flow to get a MediaIn node that acts as a loader, but it not as fast as in Fusion 9.

I have managed to get 25fps in the Edit page now, using the node disk cache on the single frame Text+ node and making sure to visit the first frame of the clip in the Edit page, with the clip selected. If the clip isn't selected, the disk cache isn't created. Rendering on the Deliver page doesn't create the disk cache either, it has to be done on the Edit page.

Unfortunately the disk cache stops working correctly once I want to cache a single frame of a group of nodes (several Text+ nodes and images making up the credits).

good morning!

so i'm thinking speed counts for absolutly nothing if the resualts are crap, you just get un-useable crap faster

here's what i see in the Fusion page, a horriable font for readibality, but the director had to have that exact font... so she got it.... zoomed in to around 800%;

Fusion page .jpg (179.85 KiB) Viewed 5931 times

that looks really good given the weaklinks, but when i look at it in the edit page, color page or deliver page what i see is clearly un-useable, looks very much like the old text tool, and that was 100% perfect, at creating a QC fail that is;

edit page.jpg (187.56 KiB) Viewed 5931 times

deliver page.jpg (191.4 KiB) Viewed 5931 times

so am i doing something wrong?
is anyone/ everyone seeing this same crap?
is there any reason to continue beating one's head against a wall over speed and functionality given the basics appear to be well and truly broken?
thoughts?

Here, the only solution I have found so far that it works very well is:
- Fusion tab: pixelPusher1: do not use the motion Blur
- return to the Edit tab
- add a solid color under the text + (?) without solid => bad
- position the playhead on the first frame,
- render cache fusion output: OFF
- select the text +
- playback menu => delete render cache => selected clip
- playback menu => render cache => smart.

Enable playback for caching. After one pass : RT playback then at 24 fps ...

text_plus.jpg

Not a lot of explanation if I think there is a little cache problem. I normally think with - render cache fusion output: Auto or ON should be enough ..

without playback menu => delete render cache => selected clip : I had bad results sometimes

EDIT : after cache is OK : Return to Fusion TAB and pixelPusher1: use the motion Blur : 2 and all OK (sorry)

.../...

so am i doing something wrong?
is anyone/ everyone seeing this same crap?
is there any reason to continue beating one's head against a wall over speed and functionality given the basics appear to be well and truly broken?
thoughts?

I think there are fonts that are more suitable for smoothing than others ...

1007pc.jpg

the main reason i'm re-doing an existing project is to deal with real world issues, like a director insisting on useing a horriable font for reasons known only to themselves...

really in the fusion ui it's fine, in DS where i did the roller for real - it's fine, in Resolve edit/color/deliver page it's crap

and the DPX export from Resolve is crap,
same font, same size, same ledding, same everything, as close as i can get it anyway, the output from DS was ok

Is there any scaling going on in timeline vs monitoring and final output?

Roger, timeline is set to DCi2kFlat, output is set to DCi2kFlat, so no scaleing there

monitoring is specfic to the room i'm working in, yesterday i was looking at a 55" PanaPlasma with 1:1 output so it was cropping the edges, tomorrow i may be able to find time on a 2k projector

Dermot,

Fusion and Edit page output look identical to me. One is larger in my frame grab because it was hard to dial in the exact same zoom value. I chose an odd zoom factor to make problems more apparent.

EditVsFusionQuality.png (567.47 KiB) Viewed 5899 times

thnx,
good to know it's something i'm doing!

i'm on a Baselight till the weekend,
will swing back to the resolve roller in a few days
might be the timeline fusion cache

Thanks Roger!

Hi Roger,

Thank you for the script.
I saved it as pixelpusher1.setting.

I changed the beginning of the scipt as recommended by Bryan:
{
Tools = ordered () {
PixelPusher1 = GroupOperator {

VS yours
{
Tools = ordered () {
PixelPusher1 = MacroOperator {

I saved in
C: \ Program Files \ Blackmagic Design \ DaVinci Resolve \ Fusion \ Templates \ Fusion \ Tools

and now in the Fusion tab, I find your script in the tools.

I've tried to save this macro in my Tools folder as PixelPusher.setting. It appears in the Tools menu but I can't drag it into my node tree. Nothing happens. Copy and pasting code works as normal inside node window. Please advise. I am on the Mac.

Hi Roger,

Thank you for the script.
I saved it as pixelpusher1.setting.

I changed the beginning of the scipt as recommended by Bryan:
{
Tools = ordered () {
PixelPusher1 = GroupOperator {

VS yours
{
Tools = ordered () {
PixelPusher1 = MacroOperator {

I saved in
C: \ Program Files \ Blackmagic Design \ DaVinci Resolve \ Fusion \ Templates \ Fusion \ Tools

and now in the Fusion tab, I find your script in the tools.

I've tried to save this macro in my Tools folder as PixelPusher.setting. It appears in the Tools menu but I can't drag it into my node tree. Nothing happens. Copy and pasting code works as normal inside node window. Please advise. I am on the Mac.

Hello Isazaly

In the fusion tab, I click on the node of text +,
then I click on the "effect Library => templates => Tools => pixelpusher1" and automatically the pixelpusher1 is inserted just after the text +

Alternatively, drag the pixelpusher1 from the Library effect and manually bind them.

In the fusion tab, I click on the node of text +,
then I click on the "effect Library => templates => Tools => pixelpusher1" and automatically the pixelpusher1 is inserted just after the text +

Alternatively, drag the pixelpusher1 from the Library effect and manually bind them.

Hi Jean,

I am aware of how to bind Nodes and it is now inside my Tools. However, when I drag it into my Node graph, it disappears! I check the codes and they looks ok to me. If I copy and paste these text into Node graph, it works normally like any other script.

[img]

Screen%20Shot%202018-07-15%20at%203.07.45%20PM.png

[/img]

Code: Select all

{
   Tools = ordered() {
      PixelPusher1 = MacroOperator {
         Inputs = ordered() {
            Comments = Input {
               Value = "PixelPusher - X/Y integer transform for 90 degree angles\n",
            },   
            MainInput1 = InstanceInput {
               SourceOp = "Transform1",
               Source = "Input",
            },
            Input1 = InstanceInput {
               SourceOp = "Transform1",
               Source = "Speed",
               Page = "Controls",
               Default = 2,
            },
            Input2 = InstanceInput {
               SourceOp = "Transform1",
               Source = "CrawlAngle",
               Page = "Controls",
               Default = 90,
            },
            Input3 = InstanceInput {
               SourceOp = "Transform1",
               Source = "MotionBlur",
               Page = "Controls",
               Default = 0,
            },
            Input4 = InstanceInput {
               SourceOp = "Transform1",
               Source = "Quality",
               Page = "Controls",
               Default = 2,
            },
            Input5 = InstanceInput {
               SourceOp = "Transform1",
               Source = "ShutterAngle",
               Page = "Controls",
               Default = 180,
            },
            Input6 = InstanceInput {
               SourceOp = "Transform1",
               Source = "CenterBias",
               Page = "Controls",
               Default = 0,
            },
            Input7 = InstanceInput {
               SourceOp = "Transform1",
               Source = "SampleSpread",
               Page = "Controls",
               Default = 1,
            },
         },
         Outputs = {
            MainOutput1 = InstanceOutput {
               SourceOp = "Transform1",
               Source = "Output",
            }
         },
         ViewInfo = GroupInfo {
            Name = "PixelPusher",
            Pos = { 0, 0 }
         },
         Tools = ordered() {
            Transform1 = Transform {
               CtrlWZoom = false,
               CtrlWShown = false,
               Inputs = {
                  Center = Input { Expression = "Point(0.5+cos(CrawlAngle*pi/180)*((time*Speed)/Width), 0.5+sin(CrawlAngle*pi/180)*((time*Speed)/Height))", },
                  ReferenceSize = Input { Value = 1, },
                  UseFrameFormatSettings = Input { Value = 1, },
               },
               ViewInfo = OperatorInfo { Pos = { 0, 0 } },
               UserControls = ordered() {
                  Speed = {
                     INP_MaxAllowed = 1000,
                     INP_Integer = true,
                     INPID_InputControl = "SliderControl",
                     IC_Steps = 1,
                     INP_MaxScale = 30,
                     INP_Default = 2,
                     INP_MinScale = 0,
                     INP_MinAllowed = 0,
                     LINKID_DataType = "Number",
                     ICS_ControlPage = "Controls",
                     LINKS_Name = "Speed (pixels)"
                  },
                  CrawlAngle = {
                     INP_MaxAllowed = 1000000,
                     INP_Integer = false,
                     INPID_InputControl = "ScrewControl",
                     IC_Steps = 3601,
                     INP_MaxScale = 360,
                     INP_Default = 90,
                     INPID_PreviewControl = "AngleControl",
                     INP_MinAllowed = -1000000,
                     LINKID_DataType = "Number",
                     ICS_ControlPage = "Controls",
                     INP_MinScale = 0,
                     LINKS_Name = "Angle"
                  }
               }
            }
         },
      }
   },
   ActiveTool = "PixelPusher1"
}

Hello Isazaly

Thank you for rereading what I wrote on Mon Apr 30, 2018 4:40 pm

I changed the beginning of the scipt as recommended by Bryan:
{
Tools = ordered () {
PixelPusher1 = GroupOperator {

VS yours
{
Tools = ordered () {
PixelPusher1 = MacroOperator {

Can you retest after modification?

Can you retest after modification?

hi again,

Nope, still not working.

When I drag into Node Graph it has an outline shape but disappear as soon as i release my mouse.

Can you retest after modification?

hi again,

Nope, still not working.

When I drag into Node Graph it has an outline shape but disappear as soon as i release my mouse.

Hello,

try :

PixelPusher1.gif

PixelPusher2.gif

Source code :

Code: Select all

{
   Tools = ordered() {
      PixelPusher1 = GroupOperator {
         CtrlWZoom = false,
         Inputs = ordered() {
            Comments = Input { Value = "PixelPusher - X/Y integer transform for 90 degree angles\n", },
            MainInput1 = InstanceInput {
               SourceOp = "Transform1",
               Source = "Input",
            },
            Input1 = InstanceInput {
               SourceOp = "Transform1",
               Source = "Speed",
               Page = "Controls",
               Default = 2,
            },
            Input2 = InstanceInput {
               SourceOp = "Transform1",
               Source = "CrawlAngle",
               Page = "Controls",
               Default = 90,
            },
            Input3 = InstanceInput {
               SourceOp = "Transform1",
               Source = "MotionBlur",
               Page = "Controls",
               Default = 0,
            },
            Input4 = InstanceInput {
               SourceOp = "Transform1",
               Source = "Quality",
               Page = "Controls",
               Default = 2,
            },
            Input5 = InstanceInput {
               SourceOp = "Transform1",
               Source = "ShutterAngle",
               Page = "Controls",
               Default = 180,
            },
            Input6 = InstanceInput {
               SourceOp = "Transform1",
               Source = "CenterBias",
               Page = "Controls",
               Default = 0,
            },
            Input7 = InstanceInput {
               SourceOp = "Transform1",
               Source = "SampleSpread",
               Page = "Controls",
               Default = 1,
            }
         },
         Outputs = {
            MainOutput1 = InstanceOutput {
               SourceOp = "Transform1",
               Source = "Output",
            }
         },
         ViewInfo = GroupInfo {
            Pos = { 509.667, 42.9394 },
            Flags = {
               AllowPan = false,
               AutoSnap = true,
               RemoveRouters = true
            },
            Size = { 126, 66.3636, 63, 24.2424 },
            Direction = "Horizontal",
            PipeStyle = "Direct",
            Scale = 1,
            Offset = { 0, 0 }
         },
         Tools = ordered() {
            Transform1 = Transform {
               CtrlWZoom = false,
               CtrlWShown = false,
               Inputs = {
                  MotionBlur = Input { Value = 1, },
                  Center = Input {
                     Value = { 0.5, 3.2 },
                     Expression = "Point(0.5+cos(CrawlAngle*pi/180)*((time*Speed)/Width), 0.5+sin(CrawlAngle*pi/180)*((time*Speed)/Height))",
                  },
                  ReferenceSize = Input { Value = 1, },
                  Width = Input { Value = 1920, },
                  Height = Input { Value = 1080, },
                  UseFrameFormatSettings = Input { Value = 1, },
                  Input = Input {
                     SourceOp = "Template",
                     Source = "Output",
                  },
               },
               ViewInfo = OperatorInfo { Pos = { 0, 8.75758 } },
               UserControls = ordered() { Speed = { INP_MaxAllowed = 1000, INP_Integer = true, INPID_InputControl = "SliderControl", IC_Steps = 1, INP_MaxScale = 30, INP_Default = 2, INP_MinScale = 0, INP_MinAllowed = 0, LINKID_DataType = "Number", ICS_ControlPage = "Controls", LINKS_Name = "Speed (pixels)" }, CrawlAngle = { INP_MaxAllowed = 1000000, INP_Integer = false, INPID_InputControl = "ScrewControl", IC_Steps = 3601, INP_MaxScale = 360, INP_Default = 90, INPID_PreviewControl = "AngleControl", INP_MinAllowed = -1000000, LINKID_DataType = "Number", ICS_ControlPage = "Controls", INP_MinScale = 0, LINKS_Name = "Angle" } }
            }
         },
      }
   }
}


If it does not work after all this: please contact BMD or tell us a little more about the specifications of your material:
OS?
Version?
GPU?
etc ...

I do not know how to answer better now. Maybe contact BMD support?

pixel1.gif (707.45 KiB) Viewed 5515 times

I have no problems binding other tools except pixelpusher... might be about the code.

I can only do it if i copy and paste the code inside the node graph.

I have ask for BMD Engineers for help and now it works as a "tool".

Here is a working one (for Mac users)

PixelPusher.setting.zip

PixelPusher (Mac)

(1.77 KiB) Downloaded 179 times

Unzip and copy to this destination:
Library/Application Support/Blackmagic Design/DaVinci Resolve/Fusion/Templates/Fusion/Tools

Thank you roger.magnusson for the script.