Specify cameras through batch 2004-06-21 - By OO's mailbot
Back
You keep this up, and we'll have another batchserve... which is sort of
how I started working on the first one. As a note the -r option is
actually a rather large script (or actually was one at some point).
With the arrival of v4.0 you should look into the scene TOC, because it
allows to change parameters without opening thee scene, and it even has
a section where you can add code that will execute once the scene is
opened.
OO
---
Olivier Ozoux's mailing list robot
mailbot@(protected)
On Jun 22, 2004, at 1:05 AM, Arvid Bj�rn wrote:
>
> You're right, scripting is far more powerful for these sort of things,
> now that I started scripting this render the thing just snowballed, so
> the script ended up almost a 100 lines long with functions and stuff
> so I can edit the render real quickly without enter XSI.
> So there you go :-)
>
> Thanks again
>
> kim aldis wrote:
>
>> I'm starting to use -script for rendering rather more than -r these
>> days,
>> simply because you get more options, as you've just found out. Latest
>> thing
>> is a modified skip frame render that validity checks frames more
>> thouroughly
>> before rendering. In youur instance though Arvid, you could just use a
>> script to generate temp scenes from a master just before rendering.
>> It might
>> just be easier.
>>
>>
>>> -- --Original Message-- --
>>> From: owner-xsi@(protected) [mailto:owner-xsi@(protected)] On
>>> Behalf Of Arvid Bj�rn
>>> Sent: 21 June 2004 09:54
>>> To: XSI@(protected)
>>> Subject: Re: Specify cameras through batch
>>>
>>>
>>> Okay scripting it is then, thanks people, too bad there isn't any
>>> -camera option in batch tho :)
>>>
>>>
>>> peterb wrote:
>>>
>>>
>>>> you could use xsibatch with the -script option.
>>>> in your script have it open your scene, select your correct
>>> camera for both
>>>
>>>> the passes, set the output paths names, and render all passes.
>>>>
>>>>
>>>> something like:
>>>>
>>>> xsibatch -r -script c:\myscript.vbs
>>>>
>>>>
>>>> myscript.vbs is just a text file with something like:
>>>>
>>>> open scene ....
>>>> set camera for pass 1
>>>> set output name for pass 1
>>>> set camera for pass 2
>>>> set output name for pass 2
>>>> render all passes
>>>>
>>>> not in front of XSI, but just check your history to see what
>>> the correct
>>>
>>>> commands are.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> No..?
>>>>>
>>>>> I have about 30 shots with at least two passes each to
>>> render from this
>>>
>>>>> scene, the only thing that differs are frames and cameras,
>>> I'd rather
>>>
>>>>> not create 60+ passes nor save 60+ scenes � 107Mb to be able to
>>>>> batchrender it.. any suggestions?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Arvid Bj�rn wrote:
>>>>>
>>>>>
>>>>>
>>>>>> I dont know if I'm stupid or blind, but is it not possible
>>>>>> to specify which camera to use in the render through xsibatch -r ?
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> cg/3d-artist | palladiumfilm
>>>>>
>>>>>
>>>>> ---
>>>>> Unsubscribe? Mail Majordomo@(protected) with the
>>> following text in body:
>>>
>>>>> unsubscribe xsi
>>>>>
>>>>>
>>>>>
>>>> ---
>>>> Unsubscribe? Mail Majordomo@(protected) with the following
>>> text in body:
>>>
>>>> unsubscribe xsi
>>>>
>>>>
>>>>
>>>>
>>> --
>>> cg/3d-artist | palladiumfilm
>>>
>>>
>>> ---
>>> Unsubscribe? Mail Majordomo@(protected) with the following text in
>>> body:
>>> unsubscribe xsi
>>>
>>>
>>>
>>
>>
>> ---
>> Unsubscribe? Mail Majordomo@(protected) with the following text in
>> body:
>> unsubscribe xsi
>>
>>
>>
>
> --
> cg/3d-artist | palladiumfilm
>
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following text in
> body:
> unsubscribe xsi
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
