Bug: Render queue doesn't work correctly.

Hi all.

I added two jobs to the render queue and pressed Start Render. Only the last one was executed.

Then I made sure no jobs were selected, and pressed Start Render again. This time it raised a dialog that says "The selected job(s) have already been rendered."

First of all, there are no selected jobs. Second, look at Job 3.

broken render queue.png (174.85 KiB) Viewed 1110 times

This is on Mac OS, Resolve 15.1

If nothing is selected it asssumes you want the whole queue to be (re)rendered.
So either select the job(s) you want to render and press render or remove the rendered jobs from the queue (one by one or via the menu to remove all rendered jobs) and press render with nothing selected to (re)render all jobs in the queue.
Rendered jobs are left in the queue so you can repeat them with the same or slightly modified settings.

But i already feel i know where you are going with this (again , as always, post after post after post.........)

Thanks. I'm not going to debate whether that's a good or bad assumption.

But if the queue is empty and you add four jobs and press Start Render, only the last one gets rendered. That's a problem.

If that is the case then indeed that is a bug worth reporting.
With nothing selected all jobs should be rendered as was always the case.

What release DR and OS combo are you running ?

Edit : just checked on my rig (osx10.12 / latest DR) and with adding a job to the queue, the last one added is automaticaly selected. So unless you select others as well or de-select it, when adding multiple jobs only the last one gets rendered.
Not sure if i want to classify this as a bug or even a hinderence, but thats just me and so up to you to report it as such to BM if you think its worth the attention of the developers.

Thanks for the reply.

I definitely consider that a bug. If you add a bunch of jobs to a queue and then press Start and go to bed, you’re going to be righteously pissed off to wake up and find all but one job ignored.