Author Topic: MiGen job: Can it just process that .mi right after creation?  (Read 3369 times)

bltomato

  • Newbie
  • *
  • Posts: 1
MiGen job: Can it just process that .mi right after creation?
« on: January 14, 2010, 08:35:52 PM »
Right now when we submit a MiGen job (And how it's always been) the .mi files get produced in one job, when it's done with that job then the dependent job can start proccessing those .mi files and turning them into real files.

Is there a way to make the dependent job start processing those .mi files immediately after they are created so it doesn't have to wait until ALL the .mis are done?

So something like:

Job 1: 1 CPU just cranks on making .mi files
Job 2: Sits there and has several cpus available to pick up those .mi files right after they are generated and starts turning them into tiffs (or whatever).

That way we have some frames we can look at right away instead of having to wait for the .mi files to crank all the way through (they are fast to generate, but if there are a ton of frames its a little rough when you need results right away and our 3d guys all have advanced forms of ADD).

Thanks!

shinya

  • Administrator
  • *****
  • Posts: 232
Re: MiGen job: Can it just process that .mi right after creation?
« Reply #1 on: January 15, 2010, 02:12:00 AM »
Hi bltomato,

Thanks for your inquiry. 

With the current miGen jobtype, it is not possible to do what you describe.
In order to get the miGen jobtype to do that, it will probably need to be modified to
use frame-to-frame dependencies. 
I'll have to log this as a feature request for a future version of the jobtype.

In the meantime, you will have to manually submit a separate job to render the
first few frames (perhaps at a higher priority too), so your artists can have a
preview of those frames quicker.