Archive Composition Script

[AndrewHazelden]

I've started the collaborative process of updating the Fusion 7 "Archive Composition" script so it will also support Fusion 8.2. My goal is to add macOS and Linux compatibility to the script as well.

Here is a copy of the original script:

Archive Composition.lua

Here is my initial edited version (still has broken support for Fusion 8):

Archive Composition Patch.lua

Patch 1 Revisions:
Changed TIME_UNDEFINED to fu.TIME_UNDEFINED
Todo: Remove lua-fs dependencies like readdir

[AndrewHazelden]

Here is a further edited script:

Archive Composition Patch 2.lua

Patch 2 Revisions:

• Changed direxists(dir) function to work with Fusion 8
• Added a createdir(dir) function
• Added fu_major_version variable
• Added an operating system platform check and an os_separator variable

[AndrewHazelden]

This updated script mostly works now when I test it on Fusion 8.2 on macOS.

Archive Composition Patch 3.lua

A remaining bug I've noticed is that bmd.scriptlib will need to be used to check if a movie file is a movie so the script doesn't try and add a frame number between the video clip's base filename and the .mov extension.

PingKing has mentioned on the bug tracker that there is a bmd.scriptlib error that effects calls to the eyeon.SV_GetFrames() function. This will have to be worked around.

Patch 3 Revisions:

• changed : GetNextCompositionSave() function to work Fusion 8 and on macOS/Linux
• changed : folder paths and directory creation code to be cross platform compatible
• added : operating system platform check and an os_separator variable
• Todo: Use bmd.scriptlib to check if a clip is a movie so there isn't a dummy frame number added to the movie filename before the frame extension

[SecondMan]

This is fantastic

[nsf]

Nice Andrew!
It works on WIN7 (didnt use the video, just sequences) just tried it.

One thing to add though, even that it is a problem since F7.
Theres an option to include the FBX, which is fine, but it wont include ABC, format added to Fusion 7.

[AndrewHazelden]

Theres an option to include the FBX, which is fine, but it wont include ABC, format added to Fusion 7.

Is this what you were looking for nsf:

patch4_alembic_support_added.png

Here is patch v4 that works with AlembicMesh3D nodes:

Archive Composition Patch 4.lua

Patch 4 Revisions:

• added : alembic mesh support

[nsf]

omg, you are awesome!

[AndrewHazelden]

updated: 2017.06.12 - Pieter Van Houte - v2.1
changed: incorporated SV_GetFrames from bmd.scriptlib and adjusted to work with Fu8+
changed: replaced eyeon.SV_GetFrames() with SV_GetFrames()

Archive Composition.lua

[andromeda_girl]

okay... problem.
no matter where I create a destination folder, the script doesn't find it?

[andromeda_girl]

this is why starting a new thread gets results

[AndrewHazelden]

this is why starting a new thread gets results

Sorry for the delay in replying. Are you running into issues with the script on Fu 8 or Fu 9?

[AndrewHazelden]

Hi andromeda_girl.

Does this thread post mean you solved the issue that you were experiencing?

[andromeda_girl]

hi,
-- don't mind me, i'm just lazy and bitchy sometimes.

this is in fu9 studio on windows 10 x64 pro

oh that post- no, i found what folder the script goes into. was a bit of trial and error before i got it

but then it doesn't find the folder you create or select for the archive.
i tried it in different locations, on different drives, even just using 'new folder' instead of making it something specific and using pre-existing folders.
but the script keeps giving an error saying it 'cannot find folder [names folder] specified' right after making/selecting it, so i find it a bit confusing.
not sure if it's me doing something wrong or what, but it's pretty simple, you just create or select a folder for it and then the -only- thing you can do next is select 'open' but then it tells you it can't find it for the archive script.

thanks for helping,
Au

[SecondMan]

It's not something silly like spaces or special characters in the folder name, is it?

[AndrewHazelden]

It's not something silly like spaces or special characters in the folder name, is it?

That might be a possibility I hadn't thought of.

Is the filepath for each of the assets using all ASCII characters or do you have Unicode multi-byte glyphs in the filepath like Big5 HKSCS characters? That might be an issue that hasn't been tested thoroughly.