Backburner makes me angry (again) because of awkward Job Submission

Hey,

I have written a script to render a number of images, lets say 32. This is done inside a nested for loop (lets say 4 loops nested into each other). Inside the inner loop lies my max quick render command. Everything is working fine, it renders out nicely!

I thought it might be a nice feature to have the option of creating a renderjob for Backburner for each image. Now I have simply replaced the render command with some lines like so:

--gMan holds the connected Manager, counter holds the current loop No.
local theJob = gMan.newjob() --create job	
 
if gIncludeMaps do theJob.includeMaps = true	
theJob.name = gJobName + "_" + counter as String + (create_suffix()) as String
 
theJob.submit() --submit using all servers		

It works, BUT: only every second job is submitted. There are no errors (like "Error: Duplicate File name"). I dont get it. It works fine with images and I can print out the job names, they are unique and correct for each job. But it does not get submitted. If I have 32 jobs to submit, I end up with 16 in the Backburner.
Does someone have any idea why? Does Backburner have problems accepting a number of jobs in a short time or whatever?

Cheers

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
br0t's picture

Okay it seems it was a

Okay it seems it was a problem with the naming of the backburner jobs. I appended a large suffix to it, and I think there was a typo somewhere, it now works as expected. Another thing I found was that any jobname is not allowed to have more than 101 characters, otherwise backburner will not accept it.

Never get low & slow & out of ideas

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.