Re: Batch Render for Rhino
Let me explain things just a little bit more cause I think there's some slight confusion with the ini thing...The newest batch render tool has two components; one that creates the sequence, and one that actually renders it. Creating the sequence would involve loading up the files, selecting the views, and specifying locations/formats. The output of this component is the ini file that is tells the second component what to do. Its really easy to create these sequences, but if you're trying to batch tens or hundreds of files/views, it might be a little time consuming to do it all manually. The format of the ini file is pretty straight forward, so you could just automate creating the batch file yourself from all the 3dm files in a given directory if you wanted.
The second component, the actual render process, will read through the sequence and render everything out. A log of the render sequence is kept that will tell you a number of details about each render (how long it took, whether there was an error, whether a view was or wasn't loaded). Out of a large batch of renders there might be an issue or two, so the parsing that I was referring to was to read through that log file to check if there were any issues within the sequence. Just a suggestion if you're truly looking to automate as much as possible.
The other option is to just write your own batch renderer, which isn't really that hard, and can allow for a bunch of extra functionality (such as swapping objects, materials, settings and/or environments). Depending on how custom a solution you're looking for this may be a possible way to go. Either way you've definitely got some options.
Let me explain things just a little bit more cause I think there's some slight confusion with the ini thing...The newest batch render tool has two components; one that creates the sequence, and one that actually renders it. Creating the sequence would involve loading up the files, selecting the views, and specifying locations/formats. The output of this component is the ini file that is tells the second component what to do. Its really easy to create these sequences, but if you're trying to batch tens or hundreds of files/views, it might be a little time consuming to do it all manually. The format of the ini file is pretty straight forward, so you could just automate creating the batch file yourself from all the 3dm files in a given directory if you wanted.
The second component, the actual render process, will read through the sequence and render everything out. A log of the render sequence is kept that will tell you a number of details about each render (how long it took, whether there was an error, whether a view was or wasn't loaded). Out of a large batch of renders there might be an issue or two, so the parsing that I was referring to was to read through that log file to check if there were any issues within the sequence. Just a suggestion if you're truly looking to automate as much as possible.
The other option is to just write your own batch renderer, which isn't really that hard, and can allow for a bunch of extra functionality (such as swapping objects, materials, settings and/or environments). Depending on how custom a solution you're looking for this may be a possible way to go. Either way you've definitely got some options.
Comment