If I have a job in the monitor and then I change its frame range I want to render, all goes well, but in the Tasks window the frame numbers that are about to be rendered are messed up.
Say, I had a frame range initially of 1-100, the job has to render 100 frames.
Then I change it to, say, 40-50, so the job will update to render only 11 frames, but the Tasks view, though it shows the correct number of frames to render, it still shows frames from 1-11. If I keep changing the frame range, the Tasks frames will get messed up even more.
I believe this is only a minor, cosmetic, bug, but I rather re-submitted the job from scratch as I didn’t want to risk incorrect frames being rendered. So, I don’t know if it really renders the listed frames or if it renders correctly.
Changing the frame range causes the task list in the monitor to fail to update correctly. Interestingly, if you close the deadline monitor and then re-open it, the task list / frame range is correct.
Just looks like the task list is not getting updated correctly in the monitor app. It seems to be displaying the actual individual task numbers instead of the ‘real-world’ frame number after a modification takes place.
Hopefully Ryan will agree?
EDIT: actually, no need to close the monitor; just un-click (de-select) the job in question and then re-select it to get the correct frame numbers.
Ah, nice. Ok, will try next time. I just couldn’t affort to have incorrect frames rendered (these were re-renders of bad frames, so a very specific frames lits) and thus I didn’t experiment further.
Yup, this is a known UI bug in the Monitor that we’ve already fixed for the next release. It’s just a graphical issue - the frames are actually correct “under the hood”.
I just couldn’t affort to have incorrect frames rendered (these were re-renders of bad frames, so a very specific frames lits) and thus I didn’t experiment further.