Blackmagic Forum

Hey,

Having installed Fusion 8.1 (and also tested 8.2 beta) it seems by default there are no scripts under the Script menu. I remember reading this somewhere before about Fusion 8 that the release somehow was missing all its default scripts, yet I can't find that particular post anymore.

It's somewhat unfortunate the default scripts (as were available in earlier versions, 6/7) seem to be missing. Anyone has a link where I can get them and ensure they are added in?

Also, what's the particular reason they are gone? Am I doing something wrong?

Same here. I hope there's a way to fix this.

Is this what you are referring to?

viewtopic.php?f=22&t=48724

Thanks! That does indeed seem to be the topic I was referring to, even though I remembered it discussing the scripts instead of templates/macros. And I missed that their solution was to just transfer files from Fusion 7 to Fusion 8.

Did they just not update the scripts and removed them completely on purpose?
Wonder what the reason was to remove them.

I guess it's a matter of taking the scripts from older versions at this stage.

I followed those instructions in order to access the Templates folder from the old version.

I can tell you that the Scripts folder is also different between the two versions.

For example, in terms of the 3 Script subfolders that are common between the old version and the new version (Comp, Tool and Utility), the old version has a total of 55 files -- while the new version has only 1 file. For the record, the new version's Script folder also has Bin, Job, Slave subfolders (which are not found in an initial installation of the old version).

Being new to Fusion, I have not yet copied the contents of the old Script folder (Comp, Tool and Utility) -- to the new version. My reason was that I did not yet have a good understanding of the application and I was concerned that there might be some incompatibility between the versions. The fact that Blackmagic did not include those files in the new version also gave me pause.

I still don't know why these various supporting files are not included in the new version. However, it would be helpful to know if I can safely copy the Comp, Tool and Utility folders from the old version -- to the new version without any adverse consequences.

Blake LaFarm wrote:I still don't know why these various supporting files are not included in the new version. However, it would be helpful to know if I can safely copy the Comp, Tool and Utility folders from the old version -- to the new version without any adverse consequences.

Support, mostly. The scripts aren't supported, so why make extra load on tech support?

You should be fine copying them over, none of those types of scripts will run at startup.

Most likely none of the old scripts will run without modification.
Starting by the file extension (old. Eyeonscript, new. Lua)
Then the change in the library (old eyeon, new BMD), some changes between the new lua version used, etc.

@Chad
@Michael

Thank you both. So, for a novice (me) climbing the Fusion learning curve, there really is no point in copying those Script folders over as the files aren't actually immediately supported in the new version. That is useful information.

Two Questions:

1. Does the same logic apply to the Templates -- or do they not have the same compatibility issues?
2. Are there any other resources from the older version that might actually be worth copying over?

Thanks.

templates will work, because they are just fusion compositions with native tools

you can also take a look at the macro folder and the fuses

michael vorberg wrote:you can also take a look at the macro folder and the fuses

Thanks for that information.

Interestingly, the Fusion 7.7.1 Macro folder only has 13 files, almost all of which are some form of "Convert Pal NTSC" -- while the Fusion 8 Macro folder is relatively enormous with 16 subfolders containing 332 files.

In contrast, the Fusion 7.7.1 Fuses folder has six subfolders (Blackmagic, Clones, OpenCL, Ops, ViewShaders) containing 48 files -- while the Fusion 8 Fuses folder is seemingly empty.

Am I somehow confusing these file numbers?

It would be great if someone could post a link or provide a download to the older scripts. I don't have any older installations but I would like to check them out to expand my experience with fusion.

Achim Dietze wrote:It would be great if someone could post a link or provide a download to the older scripts. I don't have any older installations but I would like to check them out to expand my experience with fusion.

And greate it'd be!
Here you go: I've collected all the previous even those which are already unusful or legacy and made every macro a group to further understand the structure for learners:

https://drive.google.com/drive/mobile/f ... sp=sharing

I have copied Animated 3D Parameters.lua into ProgramFiles/Blackmagic/Fusion/scripts/tool and also under %user%/appdata/roaming/Blackmagic/Fusion/scripts/tool, but Fusion no wants show me anyone scripts under scripts menu.

Fusion 8 is not useful for me without scripts. Why still BM no have fixed this?

Tool scripts don't show up in the regular scripts menu, but only in the *tool* context menu, since they only work on...well, tools.

Here's a few fixed up that are usefull and one (fun)

comp: (place in a comp subfolder)
HighLight Animated
Tool Trippin'
Switch Motion Blur (good template for turning any setting across multiple tools)

tool (place in a tool subfolder)
Destabilize Transform !

I'm going to fix a few here when I can, plus making some other basic / usefull ones as well.

That's really great of you, Rony - Thanks!

I am going to get in on this thread.

I am thinking about trying to convert many of our scripts from fusion 7 to fusion 8 studio, and I wondered if people have been doing this?

Are there any additional tricks or syntax issues that need to be known other than replacing eyeon with bmd, and .eyeonscript with .lua?

Fred Pienkos wrote:I am going to get in on this thread.

I am thinking about trying to convert many of our scripts from fusion 7 to fusion 8 studio, and I wondered if people have been doing this?

Are there any additional tricks or syntax issues that need to be known other than replacing eyeon with bmd, and .eyeonscript with .lua?

you also need to check for:'TIME_UNDEFINED' which is now 'fu.TIME_UNDEFINED
then any user dialog "askUser" needs to be now "composition:AskUser"
all for-loops:

for i, sv in svs do

is not valid. You need to use pairs() or ipairs() when iterating through the
contents of a table, for example:

for i, sv in ipairs(svs) do

I'm finally updating our .eyeonscripts for Fusion 8. The tips in this thread fixed all but one of my scripts.

Code: Select all

shotFiles = ("C:\\renders\\*.dpx")   
dir = readdir(shotFiles)
numFrames = table.getn(dir)

Previously, numFrames would give me an accurate count of the .dpx files in the folder. Now, it always returns a value of 1.

Anyone else run into this issue?

Derek Serra wrote:I'm finally updating our .eyeonscripts for Fusion 8. The tips in this thread fixed all but one of my scripts.

Code: Select all

shotFiles = ("C:\\renders\\*.dpx")   
dir = readdir(shotFiles)
numFrames = table.getn(dir)

Previously, numFrames would give me an accurate count of the .dpx files in the folder. Now, it always returns a value of 1.

Anyone else run into this issue?

Hi. The readdir() function was part of the lua-fs module that is not present in Fusion 8.2.1's version of Lua. You will have to update your older Fusion 7 scripts to use alternate approaches that use either Lua native functions, or an OS native provided tool with a command like os.execute() to re-create the functionality.

Hi. The readdir() function was part of the lua-fs module that is not present in Fusion 8.2.1's version of Lua. You will have to update your older Fusion 7 scripts to use alternate approaches that use either Lua native functions, or an OS native provided tool with a command like os.execute() to re-create the functionality.

Thanks for the info!

I'll need to figure out how to get this done on Windows. If anyone else has solved it, I'd love to hear what you did.