Open Mikael-Madbox opened 1 month ago
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
Hey there @Mikael-Madbox
Should be fixed in 1.52.2
Thanks 👏
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