Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image Sequence not properly loaded when name is not defined #1011

Open
Mikael-Madbox opened this issue Aug 1, 2024 · 3 comments
Open

Image Sequence not properly loaded when name is not defined #1011

Mikael-Madbox opened this issue Aug 1, 2024 · 3 comments
Labels

Comments

@Mikael-Madbox
Copy link
Contributor

On the last version of the worker (v1.57.1), when image sequences are defined in the job file definition without specifying a fixed name, the downloaded file's filename is prepended by a random number (cf line 29 in nexrender-core/src/tasks/download.js ) which break the sequence import in After Effect

Information about environment
Version of nexrender-worker-win.exe: 1.51.7 (compiled locally from the repository)
Version of nexrender-server-linux: 1.49.3 (precompiled version from the download page)

The workers are running on Windows 11 Pro
The server is running on a Debian

Expected Behavior:
The seed should be the same to ensure no collision happened and allow Adobe to load image sequences

image

@Mikael-Madbox
Copy link
Contributor Author

A quick fix is to define a fixed name for the image sequence, to ensure that there will be no random seed prepending the filename
But if it's not fixed (because of the change it implies) then it should be specified in the name field of the documention

@inlife
Copy link
Owner

inlife commented Aug 6, 2024

Hey there @Mikael-Madbox
Should be fixed in 1.52.2

@Mikael-Madbox
Copy link
Contributor Author

Thanks 👏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants