## Archive Tool update

Moderator: SecondMan

Movalex
Fusioneer
Posts: 108
Joined: Fri Nov 03, 2017 5:36 am
Been thanked: 22 times
Contact:

### Archive Tool update

Hi!
There's a typo in Archive Comp script in EyeonLegacy Collection of Reactor.
Output file is saved without extension.
changes:

line 893:
1. - output_composition = output_root .. composition:GetAttrs().COMPS_Name
2. + output_composition = output_root .. composition:GetAttrs().COMPS_Name .. '.comp'
See the changes proposed in https://gitlab.com/WeSuckLess/Reactor/merge_requests/59
Attachments
com.wesuckless.EyeonLegacy.zip

SecondMan
Posts: 3415
Joined: Thu Jul 31, 2014 5:31 pm
Been thanked: 78 times
Contact:

### Re: Archive Tool update

Submitted, well spotted thanks!

Since the commit was lumped together with other unrelated ones I've gone ahead and done this one separately. I also changed the release date in the Atom file. Nice bit of spring cleaning there

Your Merge requests are great but I'd ask to keep things a little separate for clarity and ease.

Movalex
Fusioneer
Posts: 108
Joined: Fri Nov 03, 2017 5:36 am
Been thanked: 22 times
Contact:

### Re: Archive Tool update

Another update to Archive comp script:

https://gitlab.com/WeSuckLess/Reactor/merge_requests/92

Attachments
Archive Composition.lua
Last edited by Movalex on Tue Aug 06, 2019 5:18 am, edited 1 time in total.

SecondMan
Posts: 3415
Joined: Thu Jul 31, 2014 5:31 pm
Been thanked: 78 times
Contact:

### Re: Archive Tool update

Ah yes nice one

Looking at the merge request it seems you haven't updated your version number though. Important for updating in Reactor...

Movalex
Fusioneer
Posts: 108
Joined: Fri Nov 03, 2017 5:36 am
Been thanked: 22 times
Contact:

### Re: Archive Tool update

done!

Movalex
Fusioneer
Posts: 108
Joined: Fri Nov 03, 2017 5:36 am
Been thanked: 22 times
Contact:

### Re: Archive Tool update

I also realized, that current version os Archive Comp script incorrectly parses a movie formats if the filepath contains a . symbol in it.
For instance, if the comp is placed in C:\Users\User\Desktop\test.test\ folder, eyeon.getextension(path) will parse the extension incorrectly, and the file will be considered an image sequence instead. We should use eyeon.parseFilename(path).Extension instead.

https://gitlab.com/WeSuckLess/Reactor/c ... e1f4d8829c

AndrewHazelden
Fusionator
Posts: 1292
Joined: Fri Apr 03, 2015 3:20 pm
Location: West Dover, Nova Scotia, Canada
Been thanked: 35 times
Contact:

### Re: Archive Tool update

Movalex wrote:
Thu Aug 08, 2019 3:00 am
I also realized, that current version os Archive Comp script incorrectly parses a movie formats if the filepath contains a . symbol in it.
For instance, if the comp is placed in C:\Users\User\Desktop\test.test\ folder, eyeon.getextension(path) will parse the extension incorrectly, and the file will be considered an image sequence instead. We should use eyeon.parseFilename(path).Extension instead.

https://gitlab.com/WeSuckLess/Reactor/c ... e1f4d8829c
For your question on the GitLab commit comments section, likely only OG Eyeon staff could answer it.

So that would be WSL people like Izyk, PeterLoveday, SirEdric, or BFloch.

AndrewHazelden
Fusionator
Posts: 1292
Joined: Fri Apr 03, 2015 3:20 pm
Location: West Dover, Nova Scotia, Canada
Been thanked: 35 times
Contact:

### Re: Archive Tool update

Hi @movalex,

Would you be up to try doing a Python port of the Eyeon Legacy "Archive Composition" script? I think a lot of Fusion newcomers who are intimidated by Lua for the first time would love to see how this kind of script looks as native Python code. It would be like a rosetta stone for people to learn how to script a Fusion pipeline in Py vs what the Lua code looks like.

As an example, the SplitEXR_Ultra script port to Python done by @bryanfordney recently was pretty epic.

SecondMan
Posts: 3415
Joined: Thu Jul 31, 2014 5:31 pm
Been thanked: 78 times
Contact:

### Re: Archive Tool update

And the update is available in Reactor now!
AndrewHazelden wrote:
Thu Aug 08, 2019 5:56 am
For your question on the GitLab commit comments section, likely only OG Eyeon staff could answer it.
I'll have a try. The question was:

Code: Select all

    for i = 1, table.getn(attrs.TOOLST_Clip_Name) do
BTW, why is this for loop here? The table attrs.TOOLST_Clip_Name always have 1 element.

Clip List support in Loaders. That was another nifty feature of Fusion that didn't make the cut in Fusion 8. I used it extensively back in the day when I had written an exposure sheet converter to import Take 5 line tests in Fusion (my very first - and very, very dirty - script!).

I would still like to have that back actually, though I guess you can work around it with IFL files.

Movalex
Fusioneer
Posts: 108
Joined: Fri Nov 03, 2017 5:36 am