Hi Russell and Team
It would be helpful to have a frame average time for each Job, and use that to extrapolate an ETA which is obviously not super accurate but still helpful
thanks
Jacob
Hey Jacob,
We currently show this information in the Job Details panel:
docs.thinkboxsoftware.com/produc … ob-details
This information is currently calculated on the fly after the Tasks for the selected job are loaded. It’s because of this that we don’t show it in the job list (otherwise we’d have to load all tasks for all jobs to calculate this info).
Cheers,
Ryan
figured you might
didnt think about the load required to carry that info for every job
ive rearranged panels now so its easy to find
thanks
If you’re keen, there are ways to inject stats object based data into one or more of the ExtraInfoX columns, so the data can be ‘more’ visible in the monitor. The script link below would need to be executed somewhere in your network on a regular basis (cron/scheduled windows task) to query and inject the data back into Deadline. It’s provided ‘as is’ for studios who want to go further in a custom way 
github.com/ThinkboxSoftware/Dea … /FarmStats
It would be nice to have the option of rendering a job, skipping tasks by a certain offset number, then coming around and incrementally filling in the missing tasks with the same offset . This would usually provide a much more accurate estimate of remaining time for the job. This is especially true when an animation sequence varies significantly in required horsepower from beginning to end. So, for example, a 1000 task job might be set to render by 10s, so it would go task 1, 11, 21, 31… etc to the end, then come back and start with task 2, 12, 22, 32… etc. this way after the first round of tasks, you would have a much better chance of having a representative sample of the entire job on which to base the time estimate. With each pass the estimate would become more and more accurate, instead of occasionally saying “three hours… two hours… one hour… five hours…” as it does now, based only on a more or less linear sample from beginning to end.
I manually do something similar using Maya’s “render by frame XX” to get a first sampling pass of the entire sequence, then running the job again using the “skip existing frames” option to fill in the rest. It seems like a fairly straight forward thing to implement in Deadline.
The frame list options of Deadline already allow this.
In fact, the 3ds Max integrated submitter has a whole lot of frame order options. Someone would have to add the same to the other submitters, but you can always enter the pattern yourself:
docs.thinkboxsoftware.com/produc … -ref-label
Since Deadline does not let you accidentally enter duplicated frames, you can go wild - see the examples at the bottom of the page, e.g. “render every 10th frame between 1 to 100, then every 5th frame, then every 2nd frame, then fill in the rest”:
1-100x10,1-100x5,1-100x2,1-100Sweet! It’s a bit more hands-on than I’d like, but I can easily enough save a few render patterns as little text docs. It would be nice to have the option integrated into the Maya submitter, but this will help a lot.
Many thanks.
Frank
Hi,
The equivalent Max SMTD ‘frame list’ options are already available in the Maya in-app submitter.
docs.thinkboxsoftware.com/produc … on-options
(Make sure you click to expand the section named: “Additional Frame Options”, as it’s collapsed by default)